Processed: Re: jsvc on buster doesn't support the installable openjdk version

[Debian Bug Tracking System]

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

> severity 935336 important
Bug #935336 [jsvc] jsvc on buster doesn't support the installable openjdk 
version
Severity set to 'important' from 'grave'
>
End of message, stopping processing here.

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

Bug#947371: marked as pending in dpdk

[Christian Ehrhardt]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/dpdk/commit/20fb7c12a234d4f76aa38632c8f96aed98023c99


dh-missing: ignore examples directory

It gets installed manually as ninja install doc does not work.

Closes: #947371


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/947371

Processed: Bug#947371 marked as pending in dpdk

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #947371 [src:dpdk] dpdk: FTBFS during indep-only build
Added tag(s) pending.

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

Bug#936361: marked as done (cyphesis-cpp: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 06 Jan 2020 06:19:14 +
with message-id 
and subject line Bug#936361: fixed in cyphesis-cpp 0.7.0~snap
has caused the Debian Bug report #936361,
regarding cyphesis-cpp: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:cyphesis-cpp

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

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


--- End Message ---
--- Begin Message ---
Source: cyphesis-cpp
Source-Version: 0.7.0~snap

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

Debian distribution maintenance software
pp.
Olek Wojnar  (supplier of updated cyphesis-cpp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Jan 2020 00:10:51 -0500
Source: cyphesis-cpp
Architecture: source
Version: 0.7.0~snap
Distribution: unstable
Urgency: high
Maintainer: Debian Games Team 
Changed-By: Olek Wojnar 
Closes: 936361
Changes:
 cyphesis-cpp (0.7.0~snap) unstable; urgency=high
 .
   * Transition to snap package
 - Snaps don't require Python 2 (Closes: #936361)
   * Update to compatibility level 12 and remove d/compat file
   * Update standards to 4.4.1 (no changes)
   * Specify Rules-Requires-Root: no
   * Update my email address
Checksums-Sha1:
 1e8a9e8c5ba69ba70ffa21956f1997d133c2993c 1832 cyphesis-cpp_0.7.0~snap.dsc
 9b21ffbe1cb9bd122563397ec567b52ed8004a42 8300 cyphesis-cpp_0.7.0~snap.tar.xz
 5b2f2f7ec4a9a6078975fbd5748a48cd98a8994c 5986 
cyphesis-cpp_0.7.0~snap_amd64.buildinfo
Checksums-Sha256:
 286c516102926a905f8a0362eedde81b908966a4d7f3ec1832c5c69c5103af87 1832 
cyphesis-cpp_0.7.0~snap.dsc
 

Bug#942987: marked as done (cyphesis-cpp: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 06 Jan 2020 06:19:14 +
with message-id 
and subject line Bug#936361: fixed in cyphesis-cpp 0.7.0~snap
has caused the Debian Bug report #936361,
regarding cyphesis-cpp: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
936361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cyphesis-cpp
Version: 0.6.2-3
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

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

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

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

  This is the least preferred option.

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

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

Debian distribution maintenance software
pp.
Olek Wojnar  (supplier of updated cyphesis-cpp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Jan 2020 00:10:51 -0500
Source: cyphesis-cpp
Architecture: source
Version: 0.7.0~snap
Distribution: unstable
Urgency: high
Maintainer: Debian Games Team 
Changed-By: Olek Wojnar 
Closes: 936361
Changes:
 cyphesis-cpp (0.7.0~snap) unstable; urgency=high
 .
   * Transition to snap package
 - Snaps don't require Python 2 (Closes: #936361)
   * Update to compatibility level 12 and remove d/compat file
   * Update standards to 4.4.1 (no changes)
   * Specify Rules-Requires-Root: no
   * Update my email address
Checksums-Sha1:
 1e8a9e8c5ba69ba70ffa21956f1997d133c2993c 1832 cyphesis-cpp_0.7.0~snap.dsc
 9b21ffbe1cb9bd122563397ec567b52ed8004a42 8300 cyphesis-cpp_0.7.0~snap.tar.xz
 5b2f2f7ec4a9a6078975fbd5748a48cd98a8994c 5986 
cyphesis-cpp_0.7.0~snap_amd64.buildinfo
Checksums-Sha256:
 286c516102926a905f8a0362eedde81b908966a4d7f3ec1832c5c69c5103af87 1832 
cyphesis-cpp_0.7.0~snap.dsc
 cf34d3e240949940b0bb7fcd5dd7848d10640c4bbcd323cfcfc67167e03b416c 8300 
cyphesis-cpp_0.7.0~snap.tar.xz
 26219dbbf768c8f471bfb6817fa9c63e7e35f7d4a2db12fb1a656f6e69e8ea16 5986 

Bug#946396: Missing fcrypt causes Lintian test failure

[Aurelien Jarno]

On 2020-01-05 09:43, Felix Lechner wrote:
> Hi Aurelien,
> 
> On Sun, Dec 8, 2019 at 3:08 PM Aurelien Jarno  wrote:
> >
> > Hi,
> >
> > On 2019-12-07 13:42, Felix Lechner wrote:
> > > Hi,
> > >
> > > Starting in `libc6 2.29-5`, the Lintian test
> > > `t/tags/checks/binaries/binaries-obsolete-des` fails in `unstable`:
> > >
> > > cc -g -O2 
> > > -fdebug-prefix-map=/builds/lintian/lintian/debian/test-out/packages/tags/checks/binaries/binaries-obsolete-des/binaries-obsolete-des-1.0=.
> > > -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro
> > > -Wl,-z,now uses-fcrypt.o -o uses-fcrypt -lcrypt
> > > /usr/bin/ld: uses-fcrypt.o: in function `main':
> > > ./uses-fcrypt.c:19: undefined reference to `fcrypt'
> > > collect2: error: ld returned 1 exit status
> > > make[2]: *** [Makefile:34: uses-fcrypt] Error 1
> >
> > Sorry about breaking lintian with that change.
> 
> Your suggestion worked great for two weeks, but now the fix for
> #946396 seems to have broken it again. As you can see from this build
> log, libcrypt-dev is installed in unstable, but not libcrypt1-dev:
> 
> https://salsa.debian.org/lintian/lintian/-/jobs/484947/raw
> 
> > > Perhaps is it time to remove the test (and the tag
> > > `obsolete-des-encryption`). Was `fcrypt` dropped entirely, or is it
> > > still provided by `libcrypt`?
> >
> > Yes, fcrypt is still provided by libcrypt, and like libc it is
> > not available to newly linked binaries, just for old binaries. That's
> > why you need some tricks to link against it.
> >
> > > I do not understand the impact of this commit:
> > >
> > > 
> > > https://salsa.debian.org/glibc-team/glibc/commit/e1dc23943b0a5c9e0612f8e1364a37f12b6710ef
> > >
> > > Here is the code that did not link:
> > >
> > > /* This program uses the obsolete function 'fcrypt',
> > >which is an alias for 'crypt'.  */
> > >
> > > #include 
> > > #include 
> > >
> > > /* The prototype may already have been removed from crypt.h.  */
> > > extern char *fcrypt(const char *, const char *);
> > >
> > > /* It may already not be possible to link new programs that use
> > >'fcrypt' without special magic.  */
> > > #ifdef SYMVER
> > > __asm__ (".symver fcrypt, fcrypt@" SYMVER);
> > > #endif
> > >
> > > int
> > > main(void)
> > > {
> > > puts(fcrypt("password", "Dn"));
> > > return 0;
> > > }
> >
> > The code itself works. However for that it needs to have SYMVER defined
> > to the correct version. This is done in the Makefile, and it assumes
> > that libcrypto.so is provided by libc6. The following patch makes the
> > code to link correctly:
> >
> > --- t/tags/checks/binaries/binaries-obsolete-des/orig/Makefile.orig 
> > 2019-12-08 23:05:20.520887001 +
> > +++ t/tags/checks/binaries/binaries-obsolete-des/orig/Makefile  2019-12-08 
> > 23:05:11.092888400 +
> > @@ -5,7 +5,7 @@
> >  # around, but we have to know the exact "symbol version" associated with
> >  # the obsolete functions, which has to be dug out of libcrypt.so with nm.
> >
> > -LIBCRYPT_FILE := $(shell dpkg -L libc6-dev | grep 'libcrypt\.so$$')
> > +LIBCRYPT_FILE := $(shell dpkg -L libcrypt1-dev | grep 'libcrypt\.so$$')
> >  SYMVER := $(shell nm --dynamic --with-symbol-versions $(LIBCRYPT_FILE) | \
> >  grep ' setkey@' | cut -d@ -f2)
> 
> Because the package libcrypt1-dev is not installed in unstable (only
> libcrypt-dev is), your suggestion now errors out with:
> 
>dh_auto_build
> make -j1 "INSTALL=install --strip-program=true"
> make[2]: Entering directory
> '/builds/lintian/lintian/debian/test-out/packages/tags/checks/binaries/binaries-obsolete-des/binaries-obsolete-des-1.0'
> dpkg-query: package 'libcrypt1-dev' is not installed
> Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
> nm: 'a.out': No such file
> : update target 'uses-fcrypt.o' due to: uses-fcrypt.c
> cc -g -O2 
> -fdebug-prefix-map=/builds/lintian/lintian/debian/test-out/packages/tags/checks/binaries/binaries-obsolete-des/binaries-obsolete-des-1.0=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -USYMVER  -c -o uses-fcrypt.o uses-fcrypt.c
> Makefile:38: update target 'uses-fcrypt' due to: uses-fcrypt.o
> cc -g -O2 
> -fdebug-prefix-map=/builds/lintian/lintian/debian/test-out/packages/tags/checks/binaries/binaries-obsolete-des/binaries-obsolete-des-1.0=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro
> -Wl,-z,now uses-fcrypt.o -o uses-fcrypt -lcrypt
> /usr/bin/ld: uses-fcrypt.o: in function `main':
> ./uses-fcrypt.c:19: undefined reference to `fcrypt'
> collect2: error: ld returned 1 exit status
> make[2]: *** [Makefile:38: uses-fcrypt] Error 1
> 
> Is the solution to replace libcrypt1-dev in your suggestion in the
> Makefile with libcrypt-dev?

Yes, at the end libcrypt1-dev has been removed into libcrypt-dev, so
this is the right thing to do. I don't think you need to keep
libcrypt1-dev in your check, now that everything has been migrated to
testing, I 

Bug#877106: pinta: Pinta 1.6-2 crashes on image scaling and other image manipulation.

[Beta Version]

Hi

On Sun, 05 Jan 2020 13:48:06 -0500 John Scott  wrote:
> Can you run `reportbug -p --template pinta` and send back the system
> information that appears at the bottom of that? The output of `lscpu`
might
> would also be helpful.

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

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

Versions of packages pinta depends on:
ii  gnome-icon-theme3.12.0-3
ii  libc6   2.29-7
ii  libcairo2   1.16.0-4
ii  libgdk-pixbuf2.0-0  2.40.0+dfsg-1
ii  libglib2.0-cil  2.12.40-2+b1
ii  libgtk2.0-cil   2.12.40-2+b1
ii  libmono-addins-gui0.2-cil   1.0+git20130406.adcd75b-4
ii  libmono-addins0.2-cil   1.0+git20130406.adcd75b-4
ii  libmono-cairo4.0-cil5.18.0.240+dfsg-5
ii  libmono-corlib4.5-cil   5.18.0.240+dfsg-5
ii  libmono-posix4.0-cil5.18.0.240+dfsg-5
ii  libmono-sharpzip4.84-cil5.18.0.240+dfsg-5
ii  libmono-system-core4.0-cil  5.18.0.240+dfsg-5
ii  libmono-system-xml4.0-cil   5.18.0.240+dfsg-5
ii  libmono-system4.0-cil   5.18.0.240+dfsg-5
ii  mono-runtime5.18.0.240+dfsg-5

pinta recommends no packages.

pinta suggests no packages.

-- no debconf information


lscpu

Architecture:x86_64
CPU op-mode(s):  32-bit, 64-bit
Byte Order:  Little Endian
Address sizes:   43 bits physical, 48 bits virtual
CPU(s):  12
On-line CPU(s) list: 0-11
Thread(s) per core:  2
Core(s) per socket:  6
Socket(s):   1
NUMA node(s):1
Vendor ID:   AuthenticAMD
CPU family:  23
Model:   8
Model name:  AMD Ryzen 5 2600 Six-Core Processor
Stepping:2
Frequency boost: enabled
CPU MHz: 1517.428
CPU max MHz: 3400,
CPU min MHz: 1550,
BogoMIPS:6799.20
Virtualization:  AMD-V
L1d cache:   192 KiB
L1i cache:   384 KiB
L2 cache:3 MiB
L3 cache:16 MiB
NUMA node0 CPU(s):   0-11
Vulnerability Itlb multihit: Not affected
Vulnerability L1tf:  Not affected
Vulnerability Mds:   Not affected
Vulnerability Meltdown:  Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass
disabled via prctl and
  seccomp
Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and
__user pointer san
 itization
Vulnerability Spectre v2:Mitigation; Full AMD retpoline, IBPB
conditional, STIBP dis
 abled, RSB filling
Vulnerability Tsx async abort:   Not affected
Flags:   fpu vme de pse tsc msr pae mce cx8 apic
sep mtrr pge mca cm
 ov pat pse36 clflush mmx fxsr sse sse2 ht
syscall nx mmxext
  fxsr_opt pdpe1gb rdtscp lm constant_tsc
rep_good nopl nons
 top_tsc cpuid extd_apicid aperfmperf pni
pclmulqdq monitor
 ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt
aes xsave avx f16
 c rdrand lahf_lm cmp_legacy svm extapic
cr8_legacy abm sse4
 a misalignsse 3dnowprefetch osvw skinit
wdt tce topoext per
 fctr_core perfctr_nb bpext perfctr_llc
mwaitx cpb hw_pstate
  sme ssbd sev ibpb vmmcall fsgsbase bmi1
avx2 smep bmi2 rds
 eed adx smap clflushopt sha_ni xsaveopt
xsavec xgetbv1 xsav
 es clzero irperf xsaveerptr arat npt lbrv
svm_lock nrip_sav
 e tsc_scale vmcb_clean flushbyasid
decodeassists pausefilte
 r pfthreshold avic v_vmsave_vmload vgif
overflow_recov succ
 or smca


> How do you invoke Pinta? Do you use a command in a terminal to start it
or
> click it from a menu?

Tried both methods and they lead to the same results.


> What does `mono -V` say

Mono JIT compiler version 5.18.0.240 (Debian 5.18.0.240+dfsg-5 Tue Sep 10
13:23:34 UTC 2019)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors.
www.mono-project.com
TLS:   __thread
SIGSEGV:   altstack

Processed: Re: Bug#948167: plplot: autopkgtest regression on arm64: /usr/lib/x86_64-linux-gnu/libm.so: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #948167 [src:plplot] plplot: autopkgtest regression on arm64: 
/usr/lib/x86_64-linux-gnu/libm.so: No such file or directory
Added tag(s) pending.

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

Bug#948167: plplot: autopkgtest regression on arm64: /usr/lib/x86_64-linux-gnu/libm.so: No such file or directory

[Rafael Laboissière]

Control: tags -1 pending

* Rafael Laboissière  [2020-01-05 15:28]:

1) The package will have to go through the NEW queue after upload, 
because of the new binary package.


Indeed: 
https://ftp-master.debian.org/new/plplot_5.15.0+dfsg-10+gnat8+1.html


I am hereby tagging this bug report as "pending".

Best,

Rafael

Bug#948256: FTBFS: test failures

[gregor herrmann]

Source: license-reconcile
Version: 0.17
Severity: serious
Tags: ftbfs
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As first seen on ci.d.n. [0] the package's test suite fails after the
update

- -libregexp-pattern-license-perl 3.0.31-4
+libregexp-pattern-license-perl 3.1.99-1

During autopkgtests on ci.d.n:

Test Summary Report
- ---
t/08-licensecheck.t (Wstat: 256 Tests: 3 Failed: 1)
  Failed test:  2
  Non-zero exit status: 1
t/09-nolicense.t(Wstat: 256 Tests: 2 Failed: 1)
  Failed test:  2
  Non-zero exit status: 1
t/09-tty.t  (Wstat: 256 Tests: 2 Failed: 1)
  Failed test:  2
  Non-zero exit status: 1
t/09-wtfpl.t(Wstat: 256 Tests: 2 Failed: 1)
  Failed test:  2
  Non-zero exit status: 1
t/17-rltty.t(Wstat: 65280 Tests: 0 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 8 tests but ran 0.
t/19-rules-verify.t (Wstat: 256 Tests: 3 Failed: 1)
  Failed test:  3
  Non-zero exit status: 1
t/20-copyright_extract.t (Wstat: 1536 Tests: 6 Failed: 6)
  Failed tests:  1-6
  Non-zero exit status: 6
Files=29, Tests=152, 10 wallclock secs ( 0.09 usr  0.06 sys +  8.38 cusr  0.99 
csys =  9.52 CPU)
Result: FAIL


Locally during build and also during autopkgtest this looks slighty different 
but not better:

Test Summary Report
- ---
t/08-licensecheck.t (Wstat: 256 Tests: 3 Failed: 1)
  Failed test:  2
  Non-zero exit status: 1
t/09-tty.t  (Wstat: 256 Tests: 2 Failed: 1)
  Failed test:  2
  Non-zero exit status: 1
t/09-wtfpl.t(Wstat: 256 Tests: 2 Failed: 1)
  Failed test:  2
  Non-zero exit status: 1
t/20-copyright_extract.t (Wstat: 256 Tests: 6 Failed: 1)
  Failed test:  5
  Non-zero exit status: 1
t/version.t (Wstat: 7168 Tests: 28 Failed: 28)
  Failed tests:  1-28
  Non-zero exit status: 28
Files=30, Tests=188, 14 wallclock secs ( 0.11 usr  0.04 sys + 12.51 cusr  0.82 
csys = 13.48 CPU)
Result: FAIL

[t/version.t is a local change and only fails during build]


Cheers,
gregor


[0]
https://ci.debian.net/data/packages/unstable/amd64/l/license-reconcile/3879800.log


-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl4SsgVfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZydBAAsn5VubpLTp1/TKiwxfMZM4OqW+/+K8aq0G49dLEGtia6klCh7Nn8Vfpk
gJ8nqQdo8864fuPWrrY8o3Ryauj42Xy1pFLYLAks7N7m7M4e3JMhqWepHyVnSj7O
R6Ni0m9qCdSCSzQATbSsp0G2niGJ4GnH1/IWluO2sIbVhDk1DQGFcrzFZpZoImCB
TyDJqaniZau+l4dogFtfSqawgeQCdMi9JI+ZoSiCsn3bpwnMDNC+tC5tEq5dtaWz
fslGyc6BIQXO8s3/Dewgiu6Sm0b/cXn6eAy7eXMfsVIaes7K6JIYY7EmTKSRc8Px
s9CTN+5qhMmUlyP1CR72KPY6yRjrUxocmynvCG7Ndwj1lYYmYxc7fiGrvt/AIPoB
vo01mJQe+crZCk7mjq9qYiCBcSwfUtbSetwti1JTdWUObvfdOZTta1Cpi679O0mF
VdHIklmhtTejHWJIru6L8pCS1YciF9kX9j9zmcGLv3wac+sEXi8dJQy3Fl2HdWy0
voH0hXoErKZe8W4PjewGZoVUcK8vcGCUTznqP4HyeFFL/L4BO6pOloyDsDrc0Cgg
9sp9yutyvN1YyWeqDC1wy9lePyalN9SawLXhje31BfsB5VhbvL1D+0J0LyCfa6mc
LOJvRIROR+cERuabxIB+jkb1NjzFEFR1sHMvP7eDBY0zZa3ZXTs=
=fS+o
-END PGP SIGNATURE-

Bug#945567: network-manager-strongswan FTBFS: error: G_ADD_PRIVATE

[Harald Dunkel]

This is still WIP. See https://wiki.strongswan.org/issues/3197

Bug#948252: marked as done (python3-pycares: copyright file missing (policy 12.5))

[Debian Bug Tracking System]

Your message dated Mon, 06 Jan 2020 03:34:39 +
with message-id 
and subject line Bug#948252: fixed in pycares 3.1.0-4
has caused the Debian Bug report #948252,
regarding python3-pycares: copyright file missing (policy 12.5)
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.)


-- 
948252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pycares
Version: 3.1.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

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

0m20.6s ERROR: WARN: Inadequate results from running adequate!
  python3-pycares: missing-copyright-file 
/usr/share/doc/python3-pycares/copyright

0m21.6s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmp_Ef5GP', 
'tmp/scripts/pre_remove_50_find_missing_copyright']
0m21.6s DUMP: 
  MISSING COPYRIGHT FILE: /usr/share/doc/python3-pycares/copyright
  # ls -lad /usr/share/doc/python3-pycares
  drwxr-xr-x 2 root root 80 Dec 22 19:07 /usr/share/doc/python3-pycares
  # ls -la /usr/share/doc/python3-pycares/
  total 8
  drwxr-xr-x   2 root root   80 Dec 22 19:07 .
  drwxr-xr-x 102 root root 2140 Dec 22 19:07 ..
  -rw-r--r--   1 root root 1087 Dec 22 04:33 changelog.Debian.gz
  -rw-r--r--   1 root root 2300 Dec 12 22:01 changelog.gz
0m21.6s DEBUG: Command ok: ['chroot', '/srv/piuparts/tmp/tmp_Ef5GP', 
'tmp/scripts/pre_remove_50_find_missing_copyright']


cheers,

Andreas


python3-pycares_3.1.0-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pycares
Source-Version: 3.1.0-4

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated pycares package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 05 Jan 2020 22:15:36 -0500
Source: pycares
Architecture: source
Version: 3.1.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Scott Kitterman 
Closes: 948252
Changes:
 pycares (3.1.0-4) unstable; urgency=medium
 .
   * Run dh_installdocs on all binaries also so debian/copyright is installed
 in all packages (Closes: #948252)
   * Update doc-base for current documentation location and package name
Checksums-Sha1:
 6782cde48faaba8e35995aee168a11b8456cae92 2256 pycares_3.1.0-4.dsc
 6db13958ea3cd2ec3c726a9549a488ec623983f3 4072 pycares_3.1.0-4.debian.tar.xz
 3364d4ae9bfd8cfff572c9404f452897cd8b2506 6904 pycares_3.1.0-4_source.buildinfo
Checksums-Sha256:
 cb1320c8c1e0b7d10847f98de62d8be68db00a526fbc72c60a58281c3fd32bc3 2256 
pycares_3.1.0-4.dsc
 1a048b64f3e8173ab94e91e16e94a03ad6c590aabe9144f87e1738f2bf0a1078 4072 
pycares_3.1.0-4.debian.tar.xz
 f65676005aebe6222ecb7c3018b3f6f6f5841f1921e09bc167e76e5f76a65d7a 6904 
pycares_3.1.0-4_source.buildinfo
Files:
 d9742a3ae3c88215342c63f20e1ebc29 2256 python optional pycares_3.1.0-4.dsc
 5af2a46bdebe874af2532c6b8ee61ac4 4072 python optional 
pycares_3.1.0-4.debian.tar.xz
 97cc60e0aca1f8b1b42d416999301829 6904 python optional 
pycares_3.1.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE53Kb/76FQA/u7iOxeNfe+5rVmvEFAl4SpoQACgkQeNfe+5rV
mvEhEA/8CuXTrHDBCyfDWt9PgYYXJrF+IQ4j7pW29jnzGemTva/1m69RHAyWPv86
5hY2Uat/Cc+V+n82Xf9sq2CSzlJACtliH5xkL0GGQ7F3syk/75Ld7TEELgwUQeyw
Bh0VGdXbAWcOTG5jXb5E79LRTAFpNHGgtlaJ2Fq06/9Ww6kvys81NhUhpAtadskJ
SKF8vgVQceuobzXFG+VpzqD5fv3M1/1jgpoY7Ro/6RxobTw4DA14wBn624OThufJ
AoyNt/Qh/XzwXqdjoaiXAzraq+e0tJ/A2QerkqyYG9F1vVPPhzbNd2w5jWxA4o5/
Fd9klDJrs9eqRo3eRxoEumPcEToOnp1XOAMJoAKzOlprtCE6XzXLgw8Q+0DQVO67
v/YellnXO90xXSEB0Tz0BHsb9aZ8HfO4+6Kifr7u7IxsJENVC1BD1geWLS/D184C
IduzSmJTt/aTn5LFz4W0+SAnaE1A8JkbO0Gt0N7Q299jnyplLGLUcLfFZ9Xl31bc
U2m/eZBF6/BDnao16HGN/Uk/nsEVYbrhUt0vReWZfHNi2Xf0Zk40I1l3DCxB29b5

Bug#948195: nvidia-legacy-340xx-driver: Xorg fails to start with a kernel panic after the upgrade to 340.108-1

[Andreas Beckmann]

On Sun, 05 Jan 2020 08:16:36 +0200 jim_p  wrote:
> After todays upgrade to 340.108, the system fails to boot in the desktop
> enviroment and dmesg reports a kernel panic, as seen on the paste here
> https://paste.debian.net/1124712

[9.046508] resource sanity check: requesting [mem 0x000c-0x000f], 
which spans more than PCI Bus :00 [mem 0x000c-0x000d window]
[9.046663] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs
[9.612094] usercopy: Kernel memory exposure attempt detected from SLUB 
object 'nvidia_stack_t' (offset 11864, size 3)!
[9.612107] [ cut here ]
[9.612108] kernel BUG at mm/usercopy.c:99!
[9.612116] invalid opcode:  [#1] SMP PTI
[9.612120] CPU: 1 PID: 583 Comm: Xorg Tainted: P   OE 
5.4.0-1-amd64 #1 Debian 5.4.6-1
[9.612122] Hardware name: Gigabyte Technology Co., Ltd. P35-DS3R/P35-DS3R, 
BIOS F13 06/19/2009
[9.612128] RIP: 0010:usercopy_abort+0x77/0x79
[9.612131] Code: 4c 0f 45 de 51 4c 89 d1 48 c7 c2 1c 06 6c 83 57 48 c7 c6 
11 d9 6a 83 48 c7 c7 e8 06 6c 83 48 0f 45 f2 4c 89 da e8 20 ac e6 ff <0f> 0b 4c 
89 e1 49 89 d8 44 89 ea 31 f6 48 29 c1 48 c7 c7 5e 06 6c
[9.612133] RSP: 0018:c18bc082fba8 EFLAGS: 00010246
[9.612136] RAX: 006b RBX: 0003 RCX: 
[9.612137] RDX:  RSI: a0836ba97688 RDI: a0836ba97688
[9.612139] RBP: a0835ed55e5b R08: a0836ba97688 R09: 007a
[9.612141] R10: c18bc082fa58 R11:  R12: a0835ed55e58
[9.612143] R13: 0001 R14: a0835ed55e58 R15: a0835ed55ea0
[9.612145] FS:  7f4c2182af00() GS:a0836ba8() 
knlGS:
[9.612147] CS:  0010 DS:  ES:  CR0: 80050033
[9.612149] CR2: 7f4c1ccc4de0 CR3: 00011ec7e000 CR4: 06e0
[9.612151] Call Trace:
[9.612157]  __check_heap_object+0xe5/0x120
[9.612160]  __check_object_size+0x136/0x147
[9.612312]  os_memcpy_to_user+0x23/0x50 [nvidia]
[9.612432]  _nv001372rm+0xa5/0x260 [nvidia]
[9.612544]  ? _nv004782rm+0x4eba/0x5500 [nvidia]
[9.612655]  ? _nv004329rm+0xec/0xf0 [nvidia]
[9.612764]  ? _nv004324rm+0xca/0x650 [nvidia]
[9.612880]  ? _nv015124rm+0x576/0x5c0 [nvidia]
[9.612998]  ? _nv000694rm+0x2e/0x60 [nvidia]
[9.613109]  ? _nv000789rm+0x5f5/0x8b0 [nvidia]
[9.613218]  ? rm_ioctl+0x73/0x100 [nvidia]
[9.613289]  ? nvidia_ioctl+0x14e/0x470 [nvidia]
[9.613363]  ? nvidia_frontend_ioctl+0x32/0x50 [nvidia]
[9.613435]  ? nvidia_frontend_unlocked_ioctl+0x19/0x20 [nvidia]
[9.613439]  ? do_vfs_ioctl+0x40e/0x670
[9.613442]  ? ksys_ioctl+0x5e/0x90
[9.613445]  ? ksys_write+0x5f/0xe0
[9.613448]  ? __x64_sys_ioctl+0x16/0x20
[9.613451]  ? do_syscall_64+0x52/0x160
[9.613455]  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
[9.613457] Modules linked in: cpufreq_conservative cpufreq_powersave 
cpufreq_userspace snd_hda_codec_hdmi sr_mod cdrom iTCO_wdt iTCO_vendor_support 
watchdog snd_hda_codec_realtek ata_generic snd_hda_codec_generic ledtrig_audio 
snd_hda_intel snd_intel_nhlt i2c_i801 snd_hda_codec pcspkr joydev snd_hda_core 
sg snd_hwdep lpc_ich snd_pcm mfd_core r8169 realtek snd_timer libphy 
pata_jmicron snd ehci_pci soundcore button acpi_cpufreq nvidia(POE) drm it87 
hwmon_vid coretemp ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 
crc32c_generic sd_mod hid_generic usbhid hid ahci libahci uhci_hcd libata 
ehci_hcd evdev scsi_mod serio_raw usbcore usb_common
[9.613492] ---[ end trace 1ab91063006ad044 ]---
[9.613495] RIP: 0010:usercopy_abort+0x77/0x79
[9.613497] Code: 4c 0f 45 de 51 4c 89 d1 48 c7 c2 1c 06 6c 83 57 48 c7 c6 
11 d9 6a 83 48 c7 c7 e8 06 6c 83 48 0f 45 f2 4c 89 da e8 20 ac e6 ff <0f> 0b 4c 
89 e1 49 89 d8 44 89 ea 31 f6 48 29 c1 48 c7 c7 5e 06 6c
[9.613500] RSP: 0018:c18bc082fba8 EFLAGS: 00010246
[9.613502] RAX: 006b RBX: 0003 RCX: 
[9.613503] RDX:  RSI: a0836ba97688 RDI: a0836ba97688
[9.613505] RBP: a0835ed55e5b R08: a0836ba97688 R09: 007a
[9.613507] R10: c18bc082fa58 R11:  R12: a0835ed55e58
[9.613509] R13: 0001 R14: a0835ed55e58 R15: a0835ed55ea0
[9.613511] FS:  7f4c2182af00() GS:a0836ba8() 
knlGS:
[9.613513] CS:  0010 DS:  ES:  CR0: 80050033
[9.613514] CR2: 7f4c1ccc4de0 CR3: 00011ec7e000 CR4: 06e0
[9.615888] BUG: kernel NULL pointer dereference, address: 0277
[9.615893] #PF: supervisor read access in kernel mode
[9.615894] #PF: error_code(0x) - not-present page
[9.615896] PGD 0 P4D 0 
[9.615900] Oops:  [#2] SMP PTI
[9.615903] CPU: 1 PID: 583 Comm: Xorg Tainted: P  DOE 
5.4.0-1-amd64 #1 Debian 5.4.6-1
[9.615905] Hardware 

Bug#935276: marked as done (scamper: FTBFS)

[Debian Bug Tracking System]

Your message dated Mon, 06 Jan 2020 01:04:44 +
with message-id 
and subject line Bug#935276: fixed in scamper 20191102-1
has caused the Debian Bug report #935276,
regarding scamper: FTBFS
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.)


-- 
935276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:scamper
version: 20181219-1
severity: serious
tags: ftbfs

Hi,

A binnmu of scamper in unstable fails on most architectures:

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

It's unclear to my why armel succeeded, but it was built against the old
linux kernel, maybe that's related.

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: scamper
Source-Version: 20191102-1

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

Debian distribution maintenance software
pp.
Ana Custura  (supplier of updated scamper package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 02 Jan 2020 20:59:32 +
Source: scamper
Architecture: source
Version: 20191102-1
Distribution: unstable
Urgency: medium
Maintainer: Internet Measurement Packaging Team 

Changed-By: Ana Custura 
Closes: 935276
Changes:
 scamper (20191102-1) unstable; urgency=medium
 .
   * New upstream version 20191102 (Closes: #935276)
   * Bumps DH version, removes legacy compat file
   * Update S-V to 4.4.1 (no changes needed)
Checksums-Sha1:
 78e6c1ddd6f5c7725db4ef884a7eff485b6ba49d 2249 scamper_20191102-1.dsc
 3678b1d5a1b9bf42b126a2a31c1005d234970864 1837731 scamper_20191102.orig.tar.gz
 56b85c7d48edd49eef58213ff0bd1489c8120708 5192 scamper_20191102-1.debian.tar.xz
 0833e311e6868ac6b62c97ab97405bc8e5c10646 6669 
scamper_20191102-1_amd64.buildinfo
Checksums-Sha256:
 b743a9cf22e4be101d33e88d40dd95d85fafd00db70b40f22918d1ccc29188b8 2249 
scamper_20191102-1.dsc
 a5f1856546a30d8362377a1489de8c566c31c3b93744909cf6bea5b7cbd92645 1837731 
scamper_20191102.orig.tar.gz
 ec2919192bc4850976cc37b6e0eb6430ac7c2481e908512336a47f0084c198e5 5192 
scamper_20191102-1.debian.tar.xz
 7573c6fd5c9bbf4a4c19bc0ac86d1d40b560d7059c59f9f30c5d0655c9a83c18 6669 
scamper_20191102-1_amd64.buildinfo
Files:
 c9ed6194023a7b368c1818413cc9c229 2249 admin optional scamper_20191102-1.dsc
 4a96d43fb446e9011e32d186fc34 1837731 admin optional 
scamper_20191102.orig.tar.gz
 664885680a086428ffeee707a3482804 5192 admin optional 
scamper_20191102-1.debian.tar.xz
 35c40dfdfbfa94271d5ebc77574c0ec7 6669 admin optional 
scamper_20191102-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEMEVxS8/NmLlMBvgk0AURaWEueyoFAl4Sg5kTHGFuYUBuZXRz
dGF0Lm9yZy51awAKCRDQBRFpYS57KuBLD/4xEVs6TL3xXKOXhYz/zxCey6gPglXZ
FdFJfnRzbMsXlOQU15Di/73vXU1Y7x3Zde5qs5GYS+MbymCUKdu9/E0QtjceP0wl
kSQWfLfyH61mfCqdQdpAgFnX0gjSyAW9c35g3ilcRrO5wfbqIgdTTX8ZfY9NpEwb
7SpOoBOGHhB4q8ElUs5DpEolJGFfPorj1WGKAtLPEI+Ffg7ii0ve2ZsBidlsfi6g
/oEeAIyrFqS3hr3iJS52QcflbigObHWoHjpkQQnRbCH4nKaelvqENhtRktoOqbeJ
u5qLvvd53d6e5ZeHJFAJVu2vjdksqtL/KEIcbt7YjbQIdHhUd15avSlSQ3FK9SSo
Ojn/noWOUdmTAGUis8XsfYIvyNacIigF63gPKlTEI2vDABZjoy1y//3Cj7ONet0N
DSBz8m8qMZwmjLb0/KOHjSofEyVPM2I6D8H2v4Njd87CgtGy+P1+dOliJX5pgjOV
vHX3lhkPXtUIc/i5Ak4MGKVifgq9gtwOR1YXcNjbhSAPJcRVM+0uOpCMA0/0ZLaJ
9jP2yZewcZQqIgxD0hZtozO+13/0XzjkPUjn54Q9IvP/6mO/nAi6dZ724wo+i5H9
s4eRC1mMMQXIpRpkl3DdzsQEca5Hmyi6XXNgsQKcvC9LSVD2JYrL3gUWMfqKuEqC
98JB3hwaEB8RZQ==
=yUD2
-END PGP SIGNATURE End Message ---

Bug#946926: pysparse: should this package be removed?

[Scott Kitterman]

On Tue, 17 Dec 2019 20:22:18 -0500 Sandro Tosi  wrote:
> Source: pysparse
> Severity: serious
> 
> Hello,
> it looks like pysparse is no longer fit to remain in debian:
> 
> * python2 only
> * no upstream release in 8+ years
> * python3-sparse exists, as a possible alternative?
> 
> If i dont hear back within a week with a good reason to keep this package, i
> will file for its removal.

There is an rdepend that needs to be addressed first:

Checking reverse dependencies...
# Broken Depends:
sfepy: python-sfepy

# Broken Build-Depends:
sfepy: python-sparse

Dependency problem found.

Please remove the moreinfo tag once that's resolved.

Scott K

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

Processed: tagging 946926

[Debian Bug Tracking System]

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

> tags 946926 + moreinfo
Bug #946926 [ftp.debian.org] RM: pysparse -- RoQA; python2-only; no upstream 
release in 8+ years; python3-sparse exists
Added tag(s) moreinfo.
> merge 946926 947757
Bug #946926 [ftp.debian.org] RM: pysparse -- RoQA; python2-only; no upstream 
release in 8+ years; python3-sparse exists
Bug #946926 [ftp.debian.org] RM: pysparse -- RoQA; python2-only; no upstream 
release in 8+ years; python3-sparse exists
Added tag(s) bullseye and sid.
Bug #947757 [ftp.debian.org] RM: pysparse -- RoQA; python2-only; upstream 
dormant since 9+ years; python3-sparse provided by a nother src package
Added tag(s) moreinfo.
Merged 946926 947757
> thanks
Stopping processing here.

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

Processed: found 948160 in 1.2-6.3, tagging 948160, found 948162 in 20160204-1, tagging 948162, tagging 948158

[Debian Bug Tracking System]

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

> found 948160 1.2-6.3
Bug #948160 [python-id3] python-id3: should this package be removed?
Marked as found in versions python-id3/1.2-6.3.
> tags 948160 + sid bullseye
Bug #948160 [python-id3] python-id3: should this package be removed?
Added tag(s) sid and bullseye.
> found 948162 20160204-1
Bug #948162 [src:python-peak.util] python-peak.util: should this package be 
removed?
Marked as found in versions python-peak.util/20160204-1.
> tags 948162 + sid bullseye
Bug #948162 [src:python-peak.util] python-peak.util: should this package be 
removed?
Added tag(s) bullseye and sid.
> tags 948158 + experimental
Bug #948158 [src:radare2-cutter] radare2-cutter ftbfs with radare2 3.9
Added tag(s) experimental.
> thanks
Stopping processing here.

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

Bug#948252: python3-pycares: copyright file missing (policy 12.5)

[Andreas Beckmann]

Package: python3-pycares
Version: 3.1.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

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

0m20.6s ERROR: WARN: Inadequate results from running adequate!
  python3-pycares: missing-copyright-file 
/usr/share/doc/python3-pycares/copyright

0m21.6s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmp_Ef5GP', 
'tmp/scripts/pre_remove_50_find_missing_copyright']
0m21.6s DUMP: 
  MISSING COPYRIGHT FILE: /usr/share/doc/python3-pycares/copyright
  # ls -lad /usr/share/doc/python3-pycares
  drwxr-xr-x 2 root root 80 Dec 22 19:07 /usr/share/doc/python3-pycares
  # ls -la /usr/share/doc/python3-pycares/
  total 8
  drwxr-xr-x   2 root root   80 Dec 22 19:07 .
  drwxr-xr-x 102 root root 2140 Dec 22 19:07 ..
  -rw-r--r--   1 root root 1087 Dec 22 04:33 changelog.Debian.gz
  -rw-r--r--   1 root root 2300 Dec 12 22:01 changelog.gz
0m21.6s DEBUG: Command ok: ['chroot', '/srv/piuparts/tmp/tmp_Ef5GP', 
'tmp/scripts/pre_remove_50_find_missing_copyright']


cheers,

Andreas


python3-pycares_3.1.0-3.log.gz
Description: application/gzip

Bug#948179: marked as done (gcc-8-doc: Build-Depends on no longer available texlive-generic-recommended)

[Debian Bug Tracking System]

Your message dated Mon, 06 Jan 2020 00:19:54 +
with message-id 
and subject line Bug#948179: fixed in gcc-8-doc 8.3.0-3
has caused the Debian Bug report #948179,
regarding gcc-8-doc: Build-Depends on no longer available 
texlive-generic-recommended
to be marked as done.

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

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


-- 
948179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-8-doc
Version: 8.3.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

gcc-8-doc cannot be built in bullseye any longer since the obsolete
package texlive-generic-recommended is no longer available in bullseye.


Andreas
--- End Message ---
--- Begin Message ---
Source: gcc-8-doc
Source-Version: 8.3.0-3

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

Debian distribution maintenance software
pp.
Dmitry Eremin-Solenikov  (supplier of updated gcc-8-doc 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Jan 2020 02:24:24 +0300
Source: gcc-8-doc
Architecture: source
Version: 8.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Eremin-Solenikov 
Changed-By: Dmitry Eremin-Solenikov 
Closes: 948179
Changes:
 gcc-8-doc (8.3.0-3) unstable; urgency=medium
 .
   * d/changelog: remove duplicated entries from changelog
   * d/control: cleanup texlive dependencies (Closes: #948179)
Checksums-Sha1:
 1bd2ff7f2ee105390f19eedd2c3cdee190cd95f9 2216 gcc-8-doc_8.3.0-3.dsc
 27bc03f65cd9af1b33dbcdbe1f2a6996c5c4e62e 95460 gcc-8-doc_8.3.0-3.debian.tar.xz
 27c7236907f49faff7790421860f1e90051356c5 5819 
gcc-8-doc_8.3.0-3_source.buildinfo
Checksums-Sha256:
 5c354ea310fa17b33e618291a933b6737d691e6df0d0934cf0eef69a82c281f2 2216 
gcc-8-doc_8.3.0-3.dsc
 654a12cd5401738226566ff5fec981b392edeb0de87a91f3c384602542b013d2 95460 
gcc-8-doc_8.3.0-3.debian.tar.xz
 e2faebe2008698e67da73554f1196545f8f51ccd117210d4fe48f73a0e878aa1 5819 
gcc-8-doc_8.3.0-3_source.buildinfo
Files:
 ac9369de80fe00fa4b38a7cb46258128 2216 non-free/doc optional 
gcc-8-doc_8.3.0-3.dsc
 3d2a2112c9b01251c848ccec2f62d550 95460 non-free/doc optional 
gcc-8-doc_8.3.0-3.debian.tar.xz
 d00716dd0cbded078618154e7ee9bb1f 5819 non-free/doc optional 
gcc-8-doc_8.3.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl4Sd/gACgkQweDZLphv
fH4q3hAAmH/8/HN0PlKatpAVSH3ZoZiPA1QXqHLHou211MCnn2UK2Np4oK3Z3JM6
We2epUW12LaioJmiUAJWLhF/EFj3EU0lRPI7rTOw/ba27Bk+W99bvg+u7I21Ysy6
Uh3x+UyxF1VSooFyWrhhoV3JPjQHNfWt/ql+DjcCW/okfyXPf+VnVkb6fzmS3qaT
gCWrzENa5Y9kWqpP+z7woIikVKix1mNqu0mJWAo+0AGtT6Da6+72PsUFse9+nwqO
k+bNXk0hukgLYN1Q/sZ+kAR2ABMHH24ualh6KT/h/pQfG+WPTCgEaGYurY20+jNV
PevH9dylcDzfQd1BVdR/jlpAD01CmwHnsLNoa1tPZ1o4X4imXZpANVMjEoukQCwM
gKvLm+3m+dJyVpYTw53PN8Edbl6/8MRHgAGsO6i44lpFwsRk4SAFLSa9P1PtcSKo
F/ab1Hj9pZUWPWowRgbOorDQmwDmpbgPrJriSNJB7HBBWDXWeHjjdS51U6MB93Dv
6365j+mVrbcGBUFmy9peMLhTq3buPGmeF+i1EGWaXNYZiKuqsRZwkF4qi+Z6ZJI8
hhLjnj8EUx8IbLLnrPRh2+xoF5tQ9mw3JLz1Mgvt8bJlvYXFoToWS4uKynHDsYgv
AuPEkkIo+1d3u5oL+J2zZWWJTeYC2eRHidvowpef4aC+wHBeJfc=
=9cEt
-END PGP SIGNATURE End Message ---

Bug#947292: marked as done (nyancat-server: package does not include needed systemd file)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jan 2020 23:34:28 +
with message-id 
and subject line Bug#947292: fixed in nyancat 1.5.1-1+build1
has caused the Debian Bug report #947292,
regarding nyancat-server: package does not include needed systemd file
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.)


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

Dear Maintainer,

After installing nyancat-server and connecting to the socket, the client is 
disconnected
and the following log entries are produced:

nyancat-server.socket: Failed to queue service startup job (Maybe the service 
file is missing or not a template unit?): Invalid argument
nyancat-server.socket: Failed with result 'resources'.

Found the package does not include the file 
/lib/systemd/system/nyancat-server@.service

This file is in the source, and is included when rebuilding the package.


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

Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.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

Versions of packages nyancat-server depends on:
ii  init-system-helpers  1.57
ii  nyancat  1.5.1-1+b1

nyancat-server recommends no packages.

nyancat-server suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: nyancat
Source-Version: 1.5.1-1+build1

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

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

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nyancat package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 05 Jan 2020 22:54:15 +0100
Source: nyancat
Architecture: source
Version: 1.5.1-1+build1
Distribution: unstable
Urgency: medium
Maintainer: Jonathan McCrohan 
Changed-By: Andreas Beckmann 
Closes: 947292
Changes:
 nyancat (1.5.1-1+build1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * No-change rebuild in a clean environment to add the systemd unit for
 nyancat-server.  (Closes: #947292)
Checksums-Sha1:
 096e069e697392828a8b3980015a0ad2776a09e8 1821 nyancat_1.5.1-1+build1.dsc
 01b269a2bee133dfba44462da517d35f76a5bb30 4616 
nyancat_1.5.1-1+build1.debian.tar.xz
 eb5cb32489f4691716030f0fffa87db53892b059 5187 
nyancat_1.5.1-1+build1_source.buildinfo
Checksums-Sha256:
 562340428a756801296d9c5f696c63ff28bfb57039712c2fa5b8679f7c385f74 1821 
nyancat_1.5.1-1+build1.dsc
 34775e941298b13ae89e88285696be9553881e55c414c4285616045fffb498be 4616 
nyancat_1.5.1-1+build1.debian.tar.xz
 f1a02f76f0185e9b19adb2456188c521eb157dddb977e2a4cf69241ef03457ab 5187 
nyancat_1.5.1-1+build1_source.buildinfo
Files:
 2818a4232b70828fdb24a133c5ee52af 1821 misc extra nyancat_1.5.1-1+build1.dsc
 556e68204aafc2ad2f77dc400f090f28 4616 misc extra 
nyancat_1.5.1-1+build1.debian.tar.xz
 374dfa4fc914f0783ca811853e6c406f 5187 misc extra 
nyancat_1.5.1-1+build1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAl4SbfQQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCMz0D/9uligxFjEpy3WXi6avC4ZfEOC87NEub6mi
h2bkh0TF9xq4NGqjy9cQqcEWn9ZS9jMMa+yQJXCACdV7slaRtuiKqWVSqnC7USFI
i47kyNBviwecpevD/QE69yrvFGK8B67+rVsLEt5P8DBtU55l1BfJhsGkh78/1FtI
tZyRFbTdsc8VOJjTIDu+wOcrnRFBXxT+Uy6emfRPEXPdu3574Och5RcLZj96mEwN
v63mwkPcmne2/97kbImoO/CgBG6QmekFex56wCrxhGQxN5sDmEZZY0Uh+y79d7K/
G2gOtcK+7ijLLZI4OB/OMykf+kn09sc0ZGRg12O5K3VfJ0BNx5lzFLiTO9UxVywP
H9cUwvr2TSW36UF0n1dg5dNa46NkBOY8eL3DpedtljukPf0e+XelHHz3CMOvwVFv
PdkPkOjPSMC9dy+GZ2YRC3JpfTVAX0CShIpq3j5Y86tsSp2EKXeTurHiFymnjDmY
rVaX3lVn7fq0Vd/mjMqtI8ZLcd06jyOFW4ZOTy0gp8J4+V95lCow1YW+OHJrJeUZ

Bug#945646: Python 3 port

[Antonio Russo]

Control: tag -1 patch

The attached patch ports simg_dump.py to Python 3.

As far as I can tell, android-sdk-libsparse-utils is the only package requiring 
Python 2, and the only python file in that package is
simg_dump.

I've tested this by comparing the output on a valid sparse image file (both 
verbose, and csv).  They are identical.

Antonio
Description: Port simg_dump to Python 3.
Author: Antonio Russo 
Forwarded: no
Last-Update: 2019-01-05

Index: android-platform-system-core/libsparse/simg_dump.py
===
--- android-platform-system-core.orig/libsparse/simg_dump.py
+++ android-platform-system-core/libsparse/simg_dump.py
@@ -1,4 +1,4 @@
-#! /usr/bin/env python
+#! /usr/bin/env python3
 
 # Copyright (C) 2012 The Android Open Source Project
 #
@@ -14,7 +14,7 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-from __future__ import print_function
+
 import csv
 import getopt
 import hashlib
@@ -47,7 +47,7 @@ def main():
 opts, args = getopt.getopt(sys.argv[1:],
"vsc:",
["verbose", "showhash", "csvfile"])
-  except getopt.GetoptError, e:
+  except getopt.GetoptError as e:
 print(e)
 usage(me)
   for o, a in opts:
@@ -66,7 +66,7 @@ def main():
 usage(me)
 
   if csvfilename:
-csvfile = open(csvfilename, "wb")
+csvfile = open(csvfilename, "w", newline='')
 csvwriter = csv.writer(csvfile)
 
   output = verbose or csvfilename or showhash
@@ -121,7 +121,7 @@ def main():
   "output offset", "output blocks", "type", "hash"])
 
 offset = 0
-for i in xrange(1, total_chunks + 1):
+for i in range(1, total_chunks + 1):
   header_bin = FH.read(12)
   header = struct.unpack("<2H2I", header_bin)
   chunk_type = header[0]
@@ -160,7 +160,7 @@ def main():
   if showhash:
 h = hashlib.sha1()
 data = fill_bin * (blk_sz / 4);
-for block in xrange(chunk_sz):
+for block in range(chunk_sz):
   h.update(data)
 curhash = h.hexdigest()
   elif chunk_type == 0xCAC3:

Processed: Python 3 port

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #945646 [src:android-platform-system-core] android-platform-system-core: 
Python2 removal in sid/bullseye
Added tag(s) patch.

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

Bug#947330: marked as done (cb2bib: FTBFS: *** No rule to make target 'libc2b.a', needed by '../bin/cb2bib'. Stop.)

[Debian Bug Tracking System]

Your message dated Sun, 5 Jan 2020 23:43:11 +0100
with message-id <9a88bc31-7438-8bf0-45e4-51da352f9...@debian.org>
and subject line Re: FTBFS: *** No rule to make target 'libc2b.a', needed by 
'../bin/cb2bib'. Stop.
has caused the Debian Bug report #947330,
regarding cb2bib: FTBFS: *** No rule to make target 'libc2b.a', needed by 
'../bin/cb2bib'. Stop.
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.)


-- 
947330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cb2bib
Version: 1.9.9-1
Severity: serious
Justification: FTBFS

Hi! During a rebuild of your package it FTBFS with the following error:

g++ -pipe -g -O2 -fdebug-prefix-map=/<>/debian/build/src=. 
-fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W -dM -E -o 
moc_predefs.h /usr/lib/x86_64-linux-gnu/qt5/mkspecs/features/data/dummy.cpp
make[3]: *** No rule to make target 'libc2b.a', needed by '../bin/cb2bib'.  
Stop.

Thanks for your work, Lisandro.

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

Kernel: Linux 5.3.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
On Tue, 24 Dec 2019 15:59:10 -0300
=?utf-8?q?Lisandro_Dami=C3=A1n_Nicanor_P=C3=A9rez_Meyer?=
 wrote:
> Hi! During a rebuild of your package it FTBFS with the following error:
> 
> g++ -pipe -g -O2 -fdebug-prefix-map=/<>/debian/build/src=. 
> -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W -dM -E -o 
> moc_predefs.h /usr/lib/x86_64-linux-gnu/qt5/mkspecs/features/data/dummy.cpp
> make[3]: *** No rule to make target 'libc2b.a', needed by '../bin/cb2bib'.  
> Stop.

This was a transient failure.

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


Andreas--- End Message ---

Bug#946625: scipy: autopkgtest regularly times out

[Håvard Flaget Aasen]

I might be way off here, but if you want to skip test you can create a
patch with this above the class or function you want to skip.

--
@pytest.mark.skip(reason="no way of currently testing this")
--

More info here [1]
This will of course skip the tests at build time as well.

I also saw some tests that was marked '@pytest.mark.slow'. These can also
be skipped using 'pytest -k-slow' though you might skip over more tests 
than you want.


I must admit I'm on thin ice here, cause I don't even know how your 
script runs..



[1]: https://docs.pytest.org/en/latest/skipping.html#skip

Processed: found 947964 in 1.4.1+git20190813.a73b6dd+dfsg-1

[Debian Bug Tracking System]

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

> found 947964 1.4.1+git20190813.a73b6dd+dfsg-1
Bug #947964 {Done: michael.cru...@gmail.com (Michael R. Crusoe)} 
[src:gatb-core] gatb-core: hardcoded libcppunit-1.14-0 (and libhdf5-103) 
dependency instead of shlibs:Depends
Marked as found in versions gatb-core/1.4.1+git20190813.a73b6dd+dfsg-1.
> thanks
Stopping processing here.

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

Processed: Re: Bug#947852 closed by Sandro Tosi (Bug#947852: fixed in networkx 2.4-3)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #947852 {Done: Sandro Tosi } [src:networkx] 
python3-networkx needs Breaks on packages in buster it breaks
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions networkx/2.4-3.

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

Bug#947852: closed by Sandro Tosi (Bug#947852: fixed in networkx 2.4-3)

[Adrian Bunk]

Control: reopen -1

On Wed, Jan 01, 2020 at 08:57:12AM +, Debian Bug Tracking System wrote:
>...
>  networkx (2.4-3) unstable; urgency=medium
>  .
>* debian/control
>  - add Breaks on current buster versions of androguard and hyperkitty, as
>they require updates for the new networkx; Closes: #947852
>...

Breaks: androguard (<< 3.3.5-1), hyperkitty (<< 1.3.0-1)

Unfortunately this is not correct.

For androguard it is off-by-one and should be
  Breaks: androguard (<< 3.3.5-2~)

For hyperkitty the package name is also wrong, this should be
  Breaks: python3-django-hyperkitty (<< 1.3.0-1.1~)

Looking at #945393, additionally
  Breaks: python3-skimage (<< 0.16.2-1~)
is required.

Thanks
Adrian

Bug#947964: marked as done (gatb-core: hardcoded libcppunit-1.14-0 (and libhdf5-103) dependency instead of shlibs:Depends)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jan 2020 22:06:15 +
with message-id 
and subject line Bug#947964: fixed in gatb-core 1.4.1+git20191209.9398f28+dfsg-2
has caused the Debian Bug report #947964,
regarding gatb-core: hardcoded libcppunit-1.14-0 (and libhdf5-103) dependency 
instead of shlibs:Depends
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.)


-- 
947964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gatb-core
Version: 1.4.1+git20191209.9398f28+dfsg-1
Severity: important

$ cat debian/control
Maintainer: Debian Med Packaging Team 

Uploaders: Nadiya Sitdykova ,
   Andreas Tille 
Section: science
Priority: optional
Build-Depends: debhelper-compat (= 12),
   d-shlibs,
   cmake,
   libcppunit-dev,
   libhdf5-dev,
   libboost-dev,
   libjsoncpp-dev,
   doxygen,
   graphviz
Standards-Version: 4.4.1
Vcs-Browser: https://salsa.debian.org/med-team/gatb-core
Vcs-Git: https://salsa.debian.org/med-team/gatb-core.git
Homepage: https://github.com/GATB/gatb-core

Package: gatb-core
Architecture: any
Depends: ${shlibs:Depends},
 ${misc:Depends},
 libhdf5-103,
 libcppunit-1.14-0
 ^
Description: Genome Analysis Toolbox with de-Bruijn graph
[...]

Why is libcppunit-1.14-0 (and libhdf5-103 fwiw) harcoded and not applied with
${shlibs:Depends}?

At least for cppunit there is now a transition
libcppunit-1.14-0 -> libcppunit-1.15-0 ongoing and because of this the bin-NMUs
didn't have a real effect.

Regards,

Rene
--- End Message ---
--- Begin Message ---
Source: gatb-core
Source-Version: 1.4.1+git20191209.9398f28+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated gatb-core 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 05 Jan 2020 22:40:32 +0100
Source: gatb-core
Architecture: source
Version: 1.4.1+git20191209.9398f28+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 947964
Changes:
 gatb-core (1.4.1+git20191209.9398f28+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * Add -latomic where needed to fix the build on armel, mipsel & powerpc.
   * new patch to avoid "-msse2" on build hosts that use qemu
   * Simplify library dependencies. Closes: #947964.
Checksums-Sha1:
 7d3837b44e48f7a80fbe916cb6be47c235a3a095 2435 
gatb-core_1.4.1+git20191209.9398f28+dfsg-2.dsc
 a4864a736b61cfceae2d43da72c73b9e125b536c 100896 
gatb-core_1.4.1+git20191209.9398f28+dfsg-2.debian.tar.xz
 5598e82e48364bcf5d6f80dc3a924ea193fdbfab 10775 
gatb-core_1.4.1+git20191209.9398f28+dfsg-2_source.buildinfo
Checksums-Sha256:
 f24c6728eb8ad03c05e8fd9e95381badc1dfc81f94756b8897cdd2884c28da41 2435 
gatb-core_1.4.1+git20191209.9398f28+dfsg-2.dsc
 9a3b2ed1b0fa211509a81934ed3e7115a02071616a2f5c783ee8704f83812c9b 100896 
gatb-core_1.4.1+git20191209.9398f28+dfsg-2.debian.tar.xz
 8f6f1f02aa5308825e82577a8361e097c8dde45291293c335676deddd3a487de 10775 
gatb-core_1.4.1+git20191209.9398f28+dfsg-2_source.buildinfo
Files:
 a8ddc409b60af8f4192122de19e0c5e3 2435 science optional 
gatb-core_1.4.1+git20191209.9398f28+dfsg-2.dsc
 1d8a53a0f60bedc888cab86eee24d88a 100896 science optional 
gatb-core_1.4.1+git20191209.9398f28+dfsg-2.debian.tar.xz
 2fd638e632ae832d460e2c6abc6781b4 10775 science optional 
gatb-core_1.4.1+git20191209.9398f28+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl4SV+4ACgkQPCZ2P2xn
5uLX3g/9HzvWRa4KMAbCULar3iLgCN3kak6HmgGCr3dIeO3OBtjD9FkfGDvEpLYZ
bOT1EfbPDsjEsV+BfCC6/1TXDG3XXPWZ8wiTu1l3eTZyVuyG1zPg6hv934BxiD2o
DX9gTvmFg1oAY5j8ny83eF555YVuEzoyNrAgZKnL/PFfRPglaYkXRp2PV+2wAGdN
J3PA3IXWwMbmKVN3E0rVQwBFP6aAkp5UotudHh+RwEPnJsHtyXNxAA/VpWWxx5Wi
rR2K85FvW5XvpYeni5aCPzL0urk6cO9R89UwRDyKfd7oFhHlW5O5KQEnz2gKLs5S

Bug#885815: marked as done (fcitx-configtool-gtk2: Depends on libunique)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jan 2020 21:49:04 +
with message-id 
and subject line Bug#885815: fixed in fcitx-configtool 0.4.10-3
has caused the Debian Bug report #885815,
regarding fcitx-configtool-gtk2: Depends on libunique
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.)


-- 
885815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fcitx-configtool-gtk2
Version: 0.4.9-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libunique
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on libunique.

Please consider dropping fcitx-configtool-gtk2 to help us achieve this
goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: fcitx-configtool
Source-Version: 0.4.10-3

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated fcitx-configtool 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, 05 Jan 2020 15:56:13 -0500
Source: fcitx-configtool
Architecture: source
Version: 0.4.10-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Closes: 885815
Changes:
 fcitx-configtool (0.4.10-3) unstable; urgency=medium
 .
   * Team upload.
   * debian/control:
 + Bump Standards-Version to 4.4.1.
 + Bump debhelper compat to v12.
 + Set upstream project url back to GitHub project.
 .
   [ Jeremy Bicha ]
   * Drop fcitx-config-gtk2. The gtk3 version has been recommended for years.
 (Closes: #885815)
Checksums-Sha1:
 90ff5b9103b2db1ea175f3e9e5c7c602d30a47d7 2239 fcitx-configtool_0.4.10-3.dsc
 6173b132c1fc115816fae54840b6e1a95e571ece 3680 
fcitx-configtool_0.4.10-3.debian.tar.xz
 7d91f7b76b93edba48e51d5c8a11b54f408d461c 14824 
fcitx-configtool_0.4.10-3_amd64.buildinfo
Checksums-Sha256:
 c8794ea809d483cddbf883319d2669c3c50ed8d0d4b5d94ca769c5c92d3eb4eb 2239 
fcitx-configtool_0.4.10-3.dsc
 3d2e7458dcc6cc62251cd5546b98c0e71ab7aa928e468435ef3b444a625c5bf3 3680 
fcitx-configtool_0.4.10-3.debian.tar.xz
 39e4ab7dcb4980924608cb844f9055f6f24c8a82fc05b279b31ec631fdcd0ee6 14824 
fcitx-configtool_0.4.10-3_amd64.buildinfo
Files:
 46d4ab1e817fefb83ed291902daf6b1d 2239 utils optional 
fcitx-configtool_0.4.10-3.dsc
 b2ad7d7af2dae84bf8fb2babd3f15bb6 3680 utils optional 
fcitx-configtool_0.4.10-3.debian.tar.xz
 23fec5b8f38316a979eda0ccda2c5a7f 14824 utils optional 
fcitx-configtool_0.4.10-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl4SU3AACgkQwpPntGGC
Ws5YFBAAlqziNR+5x53miO3Rz7IHV83Fq5NKQfqF1uSNnNt+CRikwx/jsYGzDh/i
jaCZlnYeYLx7y+JwYn9q9WzEpao0LhX9MIR/8+JZudZdxPirn9voz1geJhMNjsQq
WcybXJJhV3CKwblqSMCPsOyuYsuUYWPX/Xptp5ZsbEbJkb22YBTO4F5fl7R1CtPL
Rml10IU1MZBBcuH1zgnWaipSN9ACN0nI7/g3MihoRcdYwNsUinEq5QN8KCwmu8aL
A02OqKn4LmQCtitpL7aHYkhKd+LxJgv4dMphdSBthy+1TCOlOksobG2oiuMcpip0
R5c07XPm/KmRep0U+6GDedu61eUqO74QY3noLAjNjDCu2f8Ahm1hji4u/ANYlemW
XQB3oRilRIuf1m5858BBCnr9ythjcy1STZ1n1M+CtV0StTYGmWAGaH7eYMa0ykkY
4GRTh0VgUvci0dSFXnm9RF0IEQKkJzZB44UcGvEDavwjzBuNWoTM/Mov04+4L35X
Xsj7zCPG2OpWpXfDbdAOgLFn/Kt1UR/qBmGd5iMF9oxwKTtQaF/Gceif1o523yBu
8cdY9zOJOJ9K1DMRrei8Ew9zZCEuSmA+QcyqE34d6nuhyhFBrKQWMuQ/kLYLmUix
Z8fvDQIkINgY2216EEJY5Z5yLkNMgMiOAhYerQ1ot92oQRzTWhA=
=U/F/
-END PGP SIGNATURE End Message ---

Bug#948244: tracker.debian.org has off-by-one in the releases for packages not in stable

[Adrian Bunk]

Package: tracker.debian.org
Severity: serious

Example:
https://tracker.debian.org/pkg/monotone-viz
versions
oldstable:  1.0.2-3
stable:  1.0.2-4
unstable:  1.0.2-4

$ rmadison -a source monotone-viz
monotone-viz | 1.0.2-3   | oldoldstable   | source
monotone-viz | 1.0.2-4   | oldstable  | source
monotone-viz | 1.0.2-4   | unstable   | source
monotone-viz | 1.0.2-4   | unstable-debug | source
$

Processed: duplicated bug

[Debian Bug Tracking System]

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

> fixed 934037 sorl-thumbnail/12.3+git20170708-2
Bug #934037 [src:sorl-thumbnail] sorl-thumbnail: FTBFS in stretch 
(RuntimeError: Magick: Unable to deduce image format)
Marked as fixed in versions sorl-thumbnail/12.3+git20170708-2.
> --
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> notfound 934037 12.5.0-1
Bug #934037 [src:sorl-thumbnail] sorl-thumbnail: FTBFS in stretch 
(RuntimeError: Magick: Unable to deduce image format)
Ignoring request to alter found versions of bug #934037 to the same values 
previously set
>
End of message, stopping processing here.

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

Bug#940687: marked as done (ucblogo: Missing corresponding source for configure)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jan 2020 21:06:58 +
with message-id 
and subject line Bug#940687: fixed in ucblogo 6.1-0.1
has caused the Debian Bug report #940687,
regarding ucblogo: Missing corresponding source for configure
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.)


-- 
940687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940687
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ucblogo
Version: 6.0+dfsg-2
Severity: serious
Tags: upstream
Justification: Policy 2.1.2

I noticed this comment in debian/rules:

# don't autoreconf, as configure is newer than configure.in
# -> configure.in doesn't contain wxwidgets related checks
dh $@ --without autoreconf

I've checked and this comment still seems to be correct for the current
package in unstable.

But that means we don't actually have the source code for configure,
which is required by DFSG2.

GPL2 (which is upstream's licence) also requires "complete corresponding
machine-readable source code" and includes "the scripts used to control
compilation and installation of the executable" in its definition of
that.

Have you tried asking upstream to fix this configure/configure.in
mismatch?

Cheers,
Olly
--- End Message ---
--- Begin Message ---
Source: ucblogo
Source-Version: 6.1-0.1

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated ucblogo 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, 05 Jan 2020 15:23:12 -0500
Source: ucblogo
Architecture: source
Version: 6.1-0.1
Distribution: unstable
Urgency: medium
Maintainer: Barak A. Pearlmutter 
Changed-By: Boyuan Yang 
Closes: 823867 933478 940687
Changes:
 ucblogo (6.1-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release.
 + Proper 64bit support. (Closes: #823867)
 + No longer need a repacked dfsg tarball since all files
   seem to be dfsg-comaptible.
   * debian/patches: Refresh all patches.
   * debian/rules:
 + Use autoreconf again with the help of custom patches on
   Autotools buildsystem. (Closes: #940687)
   * debian/control:
 + Bump debhelper compat to v12.
 + Bump Standards-Version to 4.4.1.
 + Let the whole package build against wxWidgets GTK3 library.
   (Closes: #933478)
 + Update Vcs-* fields to use git packaging repo under Salsa
   Debian group.
 + Use secure URI in the homepage field.
   * debian/install: Install icons into /usr/share/pixmaps/ and
 /usr/share/icons/.
Checksums-Sha1:
 e70d49e2148e0586596585c259920e0048028eec 1939 ucblogo_6.1-0.1.dsc
 484a595638128260b07cdfd3ac24de5040c7a67c 1988705 ucblogo_6.1.orig.tar.gz
 e337f18a3b27c3473f6611c0723f04b0a5374567 8316 ucblogo_6.1-0.1.debian.tar.xz
 05b70525d13d577fd22df36dd13e34d7e5e87d67 11868 ucblogo_6.1-0.1_amd64.buildinfo
Checksums-Sha256:
 197ff4ce75cc8148b6a3c53dd455a70e6a44040367a931e87bac063f966885d2 1939 
ucblogo_6.1-0.1.dsc
 f35d8faf2dd8c4347ff67816570b20d935c19e4f6acb5301708ef2b81d9f9339 1988705 
ucblogo_6.1.orig.tar.gz
 24d9b072e9cfafec9641cc6c71786fa4de8830afa0ace27c4d0932de1a1334a8 8316 
ucblogo_6.1-0.1.debian.tar.xz
 b00185ff69dd61abc1769636e7ac8e15e38f696907dd084a543e77fb83638562 11868 
ucblogo_6.1-0.1_amd64.buildinfo
Files:
 4ab0379e9e9fd803c86f2a0d94e18a62 1939 devel optional ucblogo_6.1-0.1.dsc
 6c58a4e0d168357d4bfb6f3098f62fc8 1988705 devel optional ucblogo_6.1.orig.tar.gz
 64c7673de44ebd85c2d7571dbb09aea5 8316 devel optional 
ucblogo_6.1-0.1.debian.tar.xz
 4b7841570dd20a644fd7536f29e75676 11868 devel optional 
ucblogo_6.1-0.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl4SSRAACgkQwpPntGGC
Ws6PDxAAqP8feGY2d8bJQW2zNZocCgsUKRClIbX4MVjP4Vc9yuQx1bOh31PUn66D
YCXFZgT8fFmd9ViquoQK+PRg1TV9QwpmqqIczW5TXjBO7Y+ia9bN9fzXY6K8kndH
CYW3iZ1R6ujqd++4lFiRau2ZeVtVRu1Oez9gSUDTiW7NH9/YluE3DM0y3XeKD4rj
w3q55MgO/GSQoMFKOwKGVU370C/lw6hFIjE9DU9NK7easVDdc33rbROGuTwZwsk0

Bug#933478: marked as done (ucblogo: Please rebuild against wxWidgets GTK 3 package)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jan 2020 21:06:58 +
with message-id 
and subject line Bug#933478: fixed in ucblogo 6.1-0.1
has caused the Debian Bug report #933478,
regarding ucblogo: Please rebuild against wxWidgets GTK 3 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.)


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

Hi,

Your package appears to be using the wxWidgets GTK 2 implementation.  In 
Debian, we have had a GTK 3 implementation of wxWidgets for some time.  
For the bullseye release, the wxWidgets package maintainers plan to 
remove the GTK 2 version, so we kindly request that you switch your 
package to use the GTK 3 version.  We have a transition tracker [1] 
setup to track progress.

Switching to the GTK 3 version may be as simple as:
1) Update your Build-Depends
   libwxgtk3.0-dev -> libwxgtk3.0-gtk3-dev
   libwxgtk-media3.0-dev -> libwxgtk-media3.0-gtk3-dev
2) Rebuild
3) Test

If everything seems to be working fine, that's probably all you need to do.

There are a couple of known issues:
1) If your package uses wxGLCanvas, this doesn't currently work when running
under Wayland.  As a workaround, you can force use of X.  See bug: [2]
2) If your package uses graphics contexts, it may encounter a problem with
coordinate overflow.  See bug: [3]

If you have any questions, or need assistance with the conversion, please
contact the wxWidgets team, team...@tracker.debian.org.

[1] https://release.debian.org/transitions/html/wxwidgets3.0-gtk3.html
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900678
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906060
--- End Message ---
--- Begin Message ---
Source: ucblogo
Source-Version: 6.1-0.1

We believe that the bug you reported is fixed in the latest version of
ucblogo, 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.
Boyuan Yang  (supplier of updated ucblogo 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, 05 Jan 2020 15:23:12 -0500
Source: ucblogo
Architecture: source
Version: 6.1-0.1
Distribution: unstable
Urgency: medium
Maintainer: Barak A. Pearlmutter 
Changed-By: Boyuan Yang 
Closes: 823867 933478 940687
Changes:
 ucblogo (6.1-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release.
 + Proper 64bit support. (Closes: #823867)
 + No longer need a repacked dfsg tarball since all files
   seem to be dfsg-comaptible.
   * debian/patches: Refresh all patches.
   * debian/rules:
 + Use autoreconf again with the help of custom patches on
   Autotools buildsystem. (Closes: #940687)
   * debian/control:
 + Bump debhelper compat to v12.
 + Bump Standards-Version to 4.4.1.
 + Let the whole package build against wxWidgets GTK3 library.
   (Closes: #933478)
 + Update Vcs-* fields to use git packaging repo under Salsa
   Debian group.
 + Use secure URI in the homepage field.
   * debian/install: Install icons into /usr/share/pixmaps/ and
 /usr/share/icons/.
Checksums-Sha1:
 e70d49e2148e0586596585c259920e0048028eec 1939 ucblogo_6.1-0.1.dsc
 484a595638128260b07cdfd3ac24de5040c7a67c 1988705 ucblogo_6.1.orig.tar.gz
 e337f18a3b27c3473f6611c0723f04b0a5374567 8316 ucblogo_6.1-0.1.debian.tar.xz
 05b70525d13d577fd22df36dd13e34d7e5e87d67 11868 ucblogo_6.1-0.1_amd64.buildinfo
Checksums-Sha256:
 197ff4ce75cc8148b6a3c53dd455a70e6a44040367a931e87bac063f966885d2 1939 
ucblogo_6.1-0.1.dsc
 f35d8faf2dd8c4347ff67816570b20d935c19e4f6acb5301708ef2b81d9f9339 1988705 
ucblogo_6.1.orig.tar.gz
 24d9b072e9cfafec9641cc6c71786fa4de8830afa0ace27c4d0932de1a1334a8 8316 
ucblogo_6.1-0.1.debian.tar.xz
 b00185ff69dd61abc1769636e7ac8e15e38f696907dd084a543e77fb83638562 11868 
ucblogo_6.1-0.1_amd64.buildinfo
Files:
 4ab0379e9e9fd803c86f2a0d94e18a62 1939 devel optional ucblogo_6.1-0.1.dsc
 6c58a4e0d168357d4bfb6f3098f62fc8 1988705 devel optional ucblogo_6.1.orig.tar.gz
 64c7673de44ebd85c2d7571dbb09aea5 8316 devel optional 

Processed: Re: Bug#948159: mmdebstrap: autopkgtest issue: +libcrypt1:amd64 in chroot

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - moreinfo
Bug #948159 [src:mmdebstrap] mmdebstrap: autopkgtest issue: +libcrypt1:amd64 in 
chroot
Removed tag(s) moreinfo.
> severity -1 important
Bug #948159 [src:mmdebstrap] mmdebstrap: autopkgtest issue: +libcrypt1:amd64 in 
chroot
Severity set to 'important' from 'serious'

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

Bug#948159: mmdebstrap: autopkgtest issue: +libcrypt1:amd64 in chroot

[Paul Gevers]

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

On 05-01-2020 21:34, Paul Gevers wrote:
> Control: tags -1 moreinfo

Grr, no idea how I typed that instead of what I had in mind.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#942182: marked as done (keepalived: gets stuck when receive queue of the raw socket fills up, fixed upstream in 2.0.12)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jan 2020 20:51:50 +
with message-id 
and subject line Bug#942182: fixed in keepalived 1:2.0.19-1
has caused the Debian Bug report #942182,
regarding keepalived: gets stuck when receive queue of the raw socket fills up, 
fixed upstream in 2.0.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.)


-- 
942182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942182
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: keepalived
Version: 1:2.0.10-1
Severity: important

Dear Maintainer,

we've encountered the following bug in a setup with several unicast 
vrrp_instances:

https://github.com/acassen/keepalived/issues/1080

This is fixed upstream since 2.0.12



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

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages keepalived depends on:
ii  iproute2  4.20.0-2
ii  libc6 2.28-10
ii  libglib2.0-0  2.58.3-2+deb10u1
ii  libip4tc0 1.8.2-4
ii  libip6tc0 1.8.2-4
ii  libjson-c30.12.1+ds-2
ii  libnl-3-200   3.4.0-1
ii  libnl-genl-3-200  3.4.0-1
ii  libsnmp30 5.7.3+dfsg-5
ii  libssl1.1 1.1.1d-0+deb10u1
ii  libxtables12  1.8.2-4

Versions of packages keepalived recommends:
pn  ipvsadm  

keepalived suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: keepalived
Source-Version: 1:2.0.19-1

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

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

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

Debian distribution maintenance software
pp.
Alexander Wirt  (supplier of updated keepalived 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, 05 Jan 2020 18:45:43 +0100
Source: keepalived
Binary: keepalived keepalived-dbgsym
Architecture: source amd64
Version: 1:2.0.19-1
Distribution: unstable
Urgency: medium
Maintainer: Alexander Wirt 
Changed-By: Alexander Wirt 
Description:
 keepalived - Failover and monitoring daemon for LVS clusters
Closes: 775868 859142 878241 931617 940036 942182 947472
Changes:
 keepalived (1:2.0.19-1) unstable; urgency=medium
 .
   * [3e69686] New upstream version 2.0.19 (Closes: #947472)
 - fixes execution of scripts with /bin/sh (Closes: #931617)
 - fixes configuration parsing for SMTP sections (Closes: #859142)
 - fixes stuck in receive queue (Closes: #942182)
 - close netlink in checker (Closes: #775868)
 - fix infinite loop when tracker script times out (Closes: #940036)
 - fix loading of libipset (Closes: #878241)
   * [6a81734] Move to debhelper(-compat) 12
   * [02d9f5d] Bump standards version
   * [239c70f] Fix location of the ip_vs header file
   * [495b6e5] Disable dbus create instance feature
   * [ec5c22c] Enable iptc support
Checksums-Sha1:
 ee4bce546944cbc31b1e07cfb0b88976e398 2091 keepalived_2.0.19-1.dsc
 42c4ba1ae53acdd72f0f73ba275ae884f3ff73bb 1025062 keepalived_2.0.19.orig.tar.gz
 42564b5fd9a48c432076922702f49c0ad3395682 10820 
keepalived_2.0.19-1.debian.tar.xz
 60e7f0b2736fea4e813a334773896657177aa2e1 912124 
keepalived-dbgsym_2.0.19-1_amd64.deb
 77d8c5de13ebd1048649acec7a77f0b8f978499d 7981 
keepalived_2.0.19-1_amd64.buildinfo
 4f2fed8c53acabc7f72dc28bd6de52bab21528b1 523004 keepalived_2.0.19-1_amd64.deb
Checksums-Sha256:
 b20037249f7a48fc4ccffcf5e28545f733b5d71576c2da21ef7fc79200333742 2091 
keepalived_2.0.19-1.dsc
 0e2f8454765bc6a5fa26758bd9cec18aae42882843cdd24848aff0ae65ce4ca7 1025062 
keepalived_2.0.19.orig.tar.gz
 bbb0eaf620901aaec4cd82c07839ba88d529380c9290eafa9a15eef41337d7ea 10820 
keepalived_2.0.19-1.debian.tar.xz
 9eb59e6690dfcbeff7412fc46eeefbfc9070f89a9228903efcbfcbed50979048 912124 
keepalived-dbgsym_2.0.19-1_amd64.deb
 5aa0a94cc8a7641690ed646bcdb0005afbb794e4bcd48a892327c24b9af09edc 7981 

Bug#948159: mmdebstrap: autopkgtest issue: +libcrypt1:amd64 in chroot

[Johannes Schauer]

Hi Paul,

Quoting Paul Gevers (2020-01-05 21:34:07)
> On 04-01-2020 22:13, Johannes Schauer wrote:
> > yes, I was aware of the introduction of libcrypt, that's why I uploaded 
> > 0.5.1-3
> > which addresses precisely this change. My naive assumption was, that once
> > libcrypt migrates to testing, mmdebstrap would migrate just fine.
> 
> True, if you only look at mmdebstrap.
> 
> > Thanks a lot for opening this bug report because apparently I have a
> > misunderstanding about how our CI and migration work together with automatic
> > migration and maybe you can help me clear up my understanding of it? :)
> 
> However, there are cases where other packages are blocked due to the
> failure of mmdebstrap. Two examples:
> 
> The last couple of days: shadow. shadow somehow triggers britney to add
> libcrypt from unstable to the set of packages to test, but NOT
> mmdebstrap. The test thus has delayed shadow from migration for about 10
> days. Hence, tests like this are harmful for others.
> 
> Now libcrypt1 migrated, but mmdebstrap did not (due to this bug, hence
> downgrading). The old package now fails in testing and that's something
> that we consider RC already. However, until the reference test is run,
> all packages that run mmdebstrap as test will be believed to cause
> regressions.
> 
> Now, you can argue that changes to the base chroot are rare. I don't
> know but I could take your word for it. However, *if* they happen, like
> now, they do cause issues, like for shadow. If the situation prolongs,
> it triggers investigation by others that are not familiar with your test
> and it would require an overwrite from the release team if the situation
> was critical (e.g. shadow needed to migrate fast) or if it would have
> taken longer for libcrypt to finally migrate.
> 
> Please consider your options carefully. I can live with you choosing to
> keep the test, but I think its smarter to not have these kind of tests
> as potential gating for migration of other package unless it's really
> worth it and rare.

I don't think that there is any disagreement. Your arguments make perfect sense
to me. Thank you for explaining the situation so thoroughly. I rewrote that
test such that this kind of situation should not happen in the future, unless
any of the packages dpkg, busybox, libc-bin, base-files, base-passwd or
debianutils is no longer part of the archive.

Version 0.5.1-4 of mmdebstrap that should fix this issue has been uploaded to
unstable already.

Thanks a lot!

cheers, josch


signature.asc
Description: signature

Processed: your mail

[Debian Bug Tracking System]

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

> notfound #934037 12.5.0-2
Bug #934037 [src:sorl-thumbnail] sorl-thumbnail: FTBFS in stretch 
(RuntimeError: Magick: Unable to deduce image format)
Ignoring request to alter found versions of bug #934037 to the same values 
previously set
> --
Stopping processing here.

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

Bug#942472: r-cran-shiny: wrong link to nodejs files

[Andreas Tille]

Control: tags -1 pending
Control: block -1 by 944723

The bug is fixed in Git but besides fixing the bug there is also
a new upstream version that needs r-cran-fastmap.

Kind regards, Andreas.


-- 
http://fam-tille.de

Processed: Re: r-cran-shiny: wrong link to nodejs files

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #942472 [r-cran-shiny] r-cran-shiny: wrong link to nodejs files
Added tag(s) pending.
> block -1 by 944723
Bug #942472 [r-cran-shiny] r-cran-shiny: wrong link to nodejs files
942472 was not blocked by any bugs.
942472 was not blocking any bugs.
Added blocking bug(s) of 942472: 944723

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

Bug#948159: mmdebstrap: autopkgtest issue: +libcrypt1:amd64 in chroot

[Paul Gevers]

Control: tags -1 moreinfo

Hi josch,

On 04-01-2020 22:13, Johannes Schauer wrote:
> yes, I was aware of the introduction of libcrypt, that's why I uploaded 
> 0.5.1-3
> which addresses precisely this change. My naive assumption was, that once
> libcrypt migrates to testing, mmdebstrap would migrate just fine.

True, if you only look at mmdebstrap.

> Thanks a lot for opening this bug report because apparently I have a
> misunderstanding about how our CI and migration work together with automatic
> migration and maybe you can help me clear up my understanding of it? :)

However, there are cases where other packages are blocked due to the
failure of mmdebstrap. Two examples:

The last couple of days: shadow. shadow somehow triggers britney to add
libcrypt from unstable to the set of packages to test, but NOT
mmdebstrap. The test thus has delayed shadow from migration for about 10
days. Hence, tests like this are harmful for others.

Now libcrypt1 migrated, but mmdebstrap did not (due to this bug, hence
downgrading). The old package now fails in testing and that's something
that we consider RC already. However, until the reference test is run,
all packages that run mmdebstrap as test will be believed to cause
regressions.

Now, you can argue that changes to the base chroot are rare. I don't
know but I could take your word for it. However, *if* they happen, like
now, they do cause issues, like for shadow. If the situation prolongs,
it triggers investigation by others that are not familiar with your test
and it would require an overwrite from the release team if the situation
was critical (e.g. shadow needed to migrate fast) or if it would have
taken longer for libcrypt to finally migrate.

Please consider your options carefully. I can live with you choosing to
keep the test, but I think its smarter to not have these kind of tests
as potential gating for migration of other package unless it's really
worth it and rare.

Paul



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#948159: mmdebstrap: autopkgtest issue: +libcrypt1:amd64 in chroot

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #948159 [src:mmdebstrap] mmdebstrap: autopkgtest issue: +libcrypt1:amd64 in 
chroot
Added tag(s) moreinfo.

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

Processed: Re: forwarded tag

[Debian Bug Tracking System]

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

> forwarded 948078 https://github.com/autoconf-archive/autoconf-archive/pull/213
Bug #948078 [src:autoconf-archive] autoconf-archive: please apply patch to fix 
boost_python library link
Changed Bug forwarded-to-address to 
'https://github.com/autoconf-archive/autoconf-archive/pull/213' from 
'https://github.com/autoconf-archive/autoconf-archive/pull/213thanks'.
> thanks
Stopping processing here.

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

Bug#947613: [Pkg-utopia-maintainers] Bug#947613: network-manager: Wi-Fi not working (does not get IPv4 address) with 1.22.2-1

[Vincent Bernat]

 ❦ 29 décembre 2019 13:40 +01, Michael Biebl :

> Can you provide a full, verbose debug log:
>
> https://wiki.gnome.org/Projects/NetworkManager/Debugging
>
> Which dhcp client do you use: internal, isc-dhcp-client, ...?

I am using the internal client. Unfortunately, I am not able to
reproduce the problem anymore. Once I get it again, I'll send the logs.
-- 
Test programs at their boundary values.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Processed: Re: py2removal RC severity updates - 2019-12-20 03:37:11.274621+00:00

[Debian Bug Tracking System]

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

> severity 938834 normal
Bug #938834 [src:wxpython3.0] wxpython3.0: Python2 removal in sid/bullseye
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed (with 5 errors): Re: forwarded tag

[Debian Bug Tracking System]

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

> forwarded 948078 
> https://github.com/autoconf-archive/autoconf-archive/pull/213thanks
Bug #948078 [src:autoconf-archive] autoconf-archive: please apply patch to fix 
boost_python library link
Changed Bug forwarded-to-address to 
'https://github.com/autoconf-archive/autoconf-archive/pull/213thanks' from 
'https://github.com/autoconf-archive/autoconf-archive/pull/198/files'.
> Sent from Yahoo Mail on Android
Unknown command or malformed arguments to command.
>   On Sun, 5 Jan 2020 at 21:13, Gianfranco 
> Costamagna wrote:   forwarded 908078 
> https://github.com/autoconf-archive/autoconf-archive/pull/213thanks
Unknown command or malformed arguments to command.
> Sent from Yahoo Mail on Android
Unknown command or malformed arguments to command.
>   On Sun, 5 Jan 2020 at 21:11, Gianfranco 
> Costamagna wrote:   forwarded 908078 
> ax_boost_python.m4: fix missing "-l" parameter, resulting into a link… by 
> LocutusOfBorg · Pull Request #213 · autoconf-archive/autoconf-archive
Unknown command or malformed arguments to command.
> |
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

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

Bug#942146: koji: CVE-2019-17109

[Salvatore Bonaccorso]

Hi Holger!

On Thu, Oct 10, 2019 at 10:57:50PM +0200, Salvatore Bonaccorso wrote:
> The following vulnerability was published for koji.
> 
> CVE-2019-17109[0]:
> | Koji through 1.18.0 allows remote Directory Traversal, with resultant
> | Privilege Escalation.
> 
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> 
> For further information see:
> 
> [0] https://security-tracker.debian.org/tracker/CVE-2019-17109
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17109
> [1] https://pagure.io/koji/issue/1634
> [2] https://docs.pagure.org/koji/CVE-2019-17109/
> 
> Please adjust the affected versions in the BTS as needed.

Any news on this issue? AFAICT, the issue is fixed as well in 1.16.3,
so the smaller jump should be possible. Once fixed in unstable, can
you adress the issue as well via point release? (I just have marked it
as no-dsa in the security-tracker now, but let us know if you disagree
and think we should release a DSA).

Regards,
Salvatore

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

[Rob Browning]

shirish शिरीष  writes:

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

OK, 2.2.4+1-2+deb10u1 uploaded to buster (if I did it right), and will
hopefully fix the problem.

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

Processed: reassign 947757 to ftp.debian.org ...

[Debian Bug Tracking System]

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

> reassign 947757 ftp.debian.org
Bug #947757 [src:pysparse] pysparse: should this package be removed?
Bug reassigned from package 'src:pysparse' to 'ftp.debian.org'.
No longer marked as found in versions pysparse/1.1.1-2.
Ignoring request to alter fixed versions of bug #947757 to the same values 
previously set
> retitle 947757 RM: pysparse -- RoQA; python2-only; upstream dormant since 9+ 
> years; python3-sparse provided by a nother src package
Bug #947757 [ftp.debian.org] pysparse: should this package be removed?
Changed Bug title to 'RM: pysparse -- RoQA; python2-only; upstream dormant 
since 9+ years; python3-sparse provided by a nother src package' from 
'pysparse: should this package be removed?'.
> thanks
Stopping processing here.

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

Bug#936730: marked as done (impacket: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jan 2020 19:49:19 +
with message-id 
and subject line Bug#936730: fixed in impacket 0.9.20-5
has caused the Debian Bug report #936730,
regarding impacket: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:impacket

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated impacket package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 05 Jan 2020 14:19:48 -0500
Source: impacket
Architecture: source
Version: 0.9.20-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 936730
Changes:
 impacket (0.9.20-5) unstable; urgency=medium
 .
   * Team upload.
   * Drop python2 support; Closes: #936730
Checksums-Sha1:
 39db99db8aeb3996ac1f3582d0907f9578329c76 2118 impacket_0.9.20-5.dsc
 349f7989657d4fa2f24255dea658ba6ca83871e2 6808 impacket_0.9.20-5.debian.tar.xz
 d9b864aa46798ec3dfe4072985eedc1de9007a8d 6887 
impacket_0.9.20-5_source.buildinfo
Checksums-Sha256:
 290381e62db2d43b5de182794d32defdb6edcc144b23625f1c1ef334cdf45a2e 2118 
impacket_0.9.20-5.dsc
 f03eabb0af073ac2027a1d444da6c6ce91378f2e8da0beda06b0f30190f0ac94 6808 
impacket_0.9.20-5.debian.tar.xz
 bc5b82f2cb42acceacc2e3ce326ea81a920a107911379f48bd30b03548dde481 6887 
impacket_0.9.20-5_source.buildinfo
Files:
 8ef04301a356609ddf3d520628d428c7 2118 python optional 

Bug#948167: plplot: autopkgtest regression on arm64: /usr/lib/x86_64-linux-gnu/libm.so: No such file or directory

[Rafael Laboissière]

* Rafael Laboissière  [2020-01-05 15:28]:

3) Since 5.15.0+dfsg-11 has been already uploaded to experimental, 
that version cannot be used for uploading to unstable.  I will use the 
versioning scheme 5.15.0+dfsg-10+unstable1, unless you have any 
objections.


I changed my mind.  I just uploaded version 5.15.0+dfsg-10+gnat8+1 to 
unstable . This is a more sensible versioning scheme, because it reflects 
what the unstable branch actually is: a build against gnat-8 instead of 
gnat-9 (as with version 5.15.0+dfsg-11 in experimental).


Rafael

Bug#936730: marked as pending in impacket

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #936730 in impacket 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/impacket/commit/aa336861eaa4b6e29dea11d470eba6e18b439375


Drop python2 support; Closes: #936730


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/936730

Processed: Bug#936730 marked as pending in impacket

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #936730 [src:impacket] impacket: Python2 removal in sid/bullseye
Added tag(s) pending.

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

Bug#938653: marked as done (testresources: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jan 2020 19:19:43 +
with message-id 
and subject line Bug#938653: fixed in testresources 2.0.0-3
has caused the Debian Bug report #938653,
regarding testresources: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:testresources

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

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

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated testresources package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 05 Jan 2020 14:02:41 -0500
Source: testresources
Architecture: source
Version: 2.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Sandro Tosi 
Closes: 920505 938653
Changes:
 testresources (2.0.0-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Use team+openst...@tracker.debian.org as maintainer
   * Use debhelper-compat instead of debian/compat.
 .
   [ Mattia Rizzolo ]
   * Remove Robert Collins from uploader, as he has retired.  Closes: #920505
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #938653
Checksums-Sha1:
 e7787cacbb44a15b0cd11e980f409a1293371003 2171 testresources_2.0.0-3.dsc
 f725476293073d3a7bdb78959939a4b351c6ece0 5628 
testresources_2.0.0-3.debian.tar.xz
 632374a62c05edc649490e2414e7c022f4c23d8b 6472 
testresources_2.0.0-3_source.buildinfo
Checksums-Sha256:
 5a0cbbc2c9364a4168b07791bebbbcb2520608b0e62d0f4fd58b560abe0b4991 2171 

Bug#938653: marked as pending in testresources

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #938653 in testresources 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/testresources/commit/4dc2786a46ad79b2fea6a8951f3044d5af29f2d6


Drop python2 support; Closes: #938653


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/938653

Bug#938529: marked as done (sphinx-bootstrap-theme: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jan 2020 19:04:16 +
with message-id 
and subject line Bug#938529: fixed in sphinx-bootstrap-theme 0.6.5-2
has caused the Debian Bug report #938529,
regarding sphinx-bootstrap-theme: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:sphinx-bootstrap-theme

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

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

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated sphinx-bootstrap-theme 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 05 Jan 2020 13:44:53 -0500
Source: sphinx-bootstrap-theme
Architecture: source
Version: 0.6.5-2
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 938529
Changes:
 sphinx-bootstrap-theme (0.6.5-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Convert git repository from git-dpm to gbp layout
   * Use debhelper-compat instead of debian/compat.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #938529
Checksums-Sha1:
 3b637d77db7399361ce3c270627322666befc037 2175 
sphinx-bootstrap-theme_0.6.5-2.dsc
 8ae4e7fb367140a75e63729802d2554ddc08f09a 76848 
sphinx-bootstrap-theme_0.6.5-2.debian.tar.xz
 eb734e3457116bfe755e96a53be3b1b1ec5de2db 6210 
sphinx-bootstrap-theme_0.6.5-2_source.buildinfo
Checksums-Sha256:
 0d788c19671a0268bd94e4f7234347358b441f061b6babb4789da6a2ab889c8e 2175 
sphinx-bootstrap-theme_0.6.5-2.dsc

Processed: Bug#938653 marked as pending in testresources

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #938653 [src:testresources] testresources: Python2 removal in sid/bullseye
Added tag(s) pending.

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

Bug#877106: pinta: Pinta 1.6-2 crashes on image scaling and other image manipulation.

[John Scott]

> Yes, it still crashes after opening any of images and trying to edit it or
> just usin program GUI.

If you had sent mail to the bug report before, it seems you're using a 
different email address now and I don't know if you have sent any debugging 
information before. Regardless, the following should be helpful.

Can you run `reportbug -p --template pinta` and send back the system 
information that appears at the bottom of that? The output of `lscpu` might 
would also be helpful.

How do you invoke Pinta? Do you use a command in a terminal to start it or 
click it from a menu? What does `mono -V` say? Do you use GNOME 3?
Do you use any non-default graphics drivers, and does
`mono /usr/lib/pinta/Pinta.exe --render-threads=1` fare any better?

Are you usually working with a saved file when it crashes, and if you are, does 
opening a new window with an unsaved document make a difference?

Sorry to bombard you with questions, but I hope these details shed light on 
the issue so you can figure out this puzzle.

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

Processed: Bug#938529 marked as pending in sphinx-bootstrap-theme

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #938529 [src:sphinx-bootstrap-theme] sphinx-bootstrap-theme: Python2 
removal in sid/bullseye
Added tag(s) pending.

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

Bug#938529: marked as pending in sphinx-bootstrap-theme

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #938529 in sphinx-bootstrap-theme 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/sphinx-bootstrap-theme/commit/1c10fc394be2c6b0a2516f73e4601c8aa3cbf46a


Drop python2 support; Closes: #938529


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/938529

Bug#947969: marked as pending in ceph

[Bernd Zeimetz]

Control: tag -1 pending

Hello,

Bug #947969 in ceph 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/ceph-team/ceph/commit/010db9a30458a6417ff667c3c11a3870edb8ee0c


Fix ceph-mgr - indefinite queue growth hangs

Applying the backport for the fix
https://github.com/ceph/ceph/pull/32466

Closes: #947969
Thanks: Milan Kupcevic


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/947969

Processed: Bug#947969 marked as pending in ceph

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #947969 [ceph-mgr] ceph-mgr: indefinite queue growth causing commands to 
hang
Ignoring request to alter tags of bug #947969 to the same tags previously set

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

Bug#947964: gatb-core: hardcoded libcppunit-1.14-0 (and libhdf5-103) dependency instead of shlibs:Depends

[Michael Crusoe]

Hello,

I've fixed this at https://salsa.debian.org/med-team/gatb-core and it is
available for sponsoring by any Debian Developer.

gbp clone g...@salsa.debian.org:med-team/gatb-core

Or I can be given permission to upload the fixed package

dcut dm --uid 724D609337113C710550D7473C26763F6C67E6E2 --allow gatb-core

Thanks for the report!

Processed: Re: hfsprogs is not DFSG-Free

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #666707 [hfsprogs] hfsprogs is not DFSG-Free
Severity set to 'serious' from 'normal'

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

Bug#946396: Missing fcrypt causes Lintian test failure

[Felix Lechner]

Hi Aurelien,

On Sun, Dec 8, 2019 at 3:08 PM Aurelien Jarno  wrote:
>
> Hi,
>
> On 2019-12-07 13:42, Felix Lechner wrote:
> > Hi,
> >
> > Starting in `libc6 2.29-5`, the Lintian test
> > `t/tags/checks/binaries/binaries-obsolete-des` fails in `unstable`:
> >
> > cc -g -O2 
> > -fdebug-prefix-map=/builds/lintian/lintian/debian/test-out/packages/tags/checks/binaries/binaries-obsolete-des/binaries-obsolete-des-1.0=.
> > -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro
> > -Wl,-z,now uses-fcrypt.o -o uses-fcrypt -lcrypt
> > /usr/bin/ld: uses-fcrypt.o: in function `main':
> > ./uses-fcrypt.c:19: undefined reference to `fcrypt'
> > collect2: error: ld returned 1 exit status
> > make[2]: *** [Makefile:34: uses-fcrypt] Error 1
>
> Sorry about breaking lintian with that change.

Your suggestion worked great for two weeks, but now the fix for
#946396 seems to have broken it again. As you can see from this build
log, libcrypt-dev is installed in unstable, but not libcrypt1-dev:

https://salsa.debian.org/lintian/lintian/-/jobs/484947/raw

> > Perhaps is it time to remove the test (and the tag
> > `obsolete-des-encryption`). Was `fcrypt` dropped entirely, or is it
> > still provided by `libcrypt`?
>
> Yes, fcrypt is still provided by libcrypt, and like libc it is
> not available to newly linked binaries, just for old binaries. That's
> why you need some tricks to link against it.
>
> > I do not understand the impact of this commit:
> >
> > 
> > https://salsa.debian.org/glibc-team/glibc/commit/e1dc23943b0a5c9e0612f8e1364a37f12b6710ef
> >
> > Here is the code that did not link:
> >
> > /* This program uses the obsolete function 'fcrypt',
> >which is an alias for 'crypt'.  */
> >
> > #include 
> > #include 
> >
> > /* The prototype may already have been removed from crypt.h.  */
> > extern char *fcrypt(const char *, const char *);
> >
> > /* It may already not be possible to link new programs that use
> >'fcrypt' without special magic.  */
> > #ifdef SYMVER
> > __asm__ (".symver fcrypt, fcrypt@" SYMVER);
> > #endif
> >
> > int
> > main(void)
> > {
> > puts(fcrypt("password", "Dn"));
> > return 0;
> > }
>
> The code itself works. However for that it needs to have SYMVER defined
> to the correct version. This is done in the Makefile, and it assumes
> that libcrypto.so is provided by libc6. The following patch makes the
> code to link correctly:
>
> --- t/tags/checks/binaries/binaries-obsolete-des/orig/Makefile.orig 
> 2019-12-08 23:05:20.520887001 +
> +++ t/tags/checks/binaries/binaries-obsolete-des/orig/Makefile  2019-12-08 
> 23:05:11.092888400 +
> @@ -5,7 +5,7 @@
>  # around, but we have to know the exact "symbol version" associated with
>  # the obsolete functions, which has to be dug out of libcrypt.so with nm.
>
> -LIBCRYPT_FILE := $(shell dpkg -L libc6-dev | grep 'libcrypt\.so$$')
> +LIBCRYPT_FILE := $(shell dpkg -L libcrypt1-dev | grep 'libcrypt\.so$$')
>  SYMVER := $(shell nm --dynamic --with-symbol-versions $(LIBCRYPT_FILE) | \
>  grep ' setkey@' | cut -d@ -f2)

Because the package libcrypt1-dev is not installed in unstable (only
libcrypt-dev is), your suggestion now errors out with:

   dh_auto_build
make -j1 "INSTALL=install --strip-program=true"
make[2]: Entering directory
'/builds/lintian/lintian/debian/test-out/packages/tags/checks/binaries/binaries-obsolete-des/binaries-obsolete-des-1.0'
dpkg-query: package 'libcrypt1-dev' is not installed
Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
nm: 'a.out': No such file
: update target 'uses-fcrypt.o' due to: uses-fcrypt.c
cc -g -O2 
-fdebug-prefix-map=/builds/lintian/lintian/debian/test-out/packages/tags/checks/binaries/binaries-obsolete-des/binaries-obsolete-des-1.0=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -USYMVER  -c -o uses-fcrypt.o uses-fcrypt.c
Makefile:38: update target 'uses-fcrypt' due to: uses-fcrypt.o
cc -g -O2 
-fdebug-prefix-map=/builds/lintian/lintian/debian/test-out/packages/tags/checks/binaries/binaries-obsolete-des/binaries-obsolete-des-1.0=.
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro
-Wl,-z,now uses-fcrypt.o -o uses-fcrypt -lcrypt
/usr/bin/ld: uses-fcrypt.o: in function `main':
./uses-fcrypt.c:19: undefined reference to `fcrypt'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:38: uses-fcrypt] Error 1

Is the solution to replace libcrypt1-dev in your suggestion in the
Makefile with libcrypt-dev?

Kind regards
Felix Lechner

Bug#948119: [schroot] does not work for non-root user

[tony mancill]

On Sat, Jan 04, 2020 at 09:32:22PM -0800, Steve Langasek wrote:
> It is a latent bug in debian/rules, which failed to run the install-arch:
> target when run under dpkg-buildpackage -b (instead of -B), which is how I
> did my test build for upload to the archive.
> 
> I was surprised to find that the archive did not discard my binaries and
> rebuild them, which I understood was now the standard upload workflow in
> Debian, but instead published them as-is, which is how this bug made it out
> to the world.
> 
> I have pushed a fix for this bug to the git repository; however, the other
> thing that was failing to happen due to this bug, aside from not setting the
> binary setuid root, was that the testsuite was not being run.  So I'm in the
> process now of fixing various testsuite regressions.

Hi Steve,

Thank you for the quick turn-around and the explanation.  AIUI, the
binaries you uploaded would not have migrated to testing, but binary
uploads are still permitted for unstable and in some cases are required
- e.g., if the package is NEW.  But that's a topic for a different bug.

Thanks again!
tony

Processed: py2removal RC severity updates - 2020-01-05 17:36:15.202655+00:00

[Debian Bug Tracking System]

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

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

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

Processed: limit source to keepalived, tagging 931617, tagging 878241, tagging 940036, tagging 859142 ...

[Debian Bug Tracking System]

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

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

> tags 931617 + pending
Bug #931617 [keepalived] Scripts are not executed with /bin/sh when they should
Added tag(s) pending.
> tags 878241 + pending
Bug #878241 [keepalived] log error message: Unable to load ipset library
Added tag(s) pending.
> tags 940036 + pending
Bug #940036 [keepalived] keepalived: cpu 100% infinite loop when track script  
timed out
Added tag(s) pending.
> tags 859142 + pending
Bug #859142 [keepalived] keepalived: if host section in SMPT_CHECK, 
healthchecker process segfaults
Added tag(s) pending.
> tags 775868 + pending
Bug #775868 [keepalived] keepalived: reload leaks file descriptors
Added tag(s) pending.
> tags 947472 + pending
Bug #947472 [keepalived] keepalived: new upstream version 2.0.19 fixes several 
bugs
Added tag(s) pending.
> tags 942182 + pending
Bug #942182 [keepalived] keepalived: gets stuck when receive queue of the raw 
socket fills up, fixed upstream in 2.0.12
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
775868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775868
859142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859142
878241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878241
931617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931617
940036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940036
942182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942182
947472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: another one fixed already

[Debian Bug Tracking System]

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

> fixed 948097 3.01-3
Bug #948097 [src:libbio-db-hts-perl] libbio-db-hts-perl: autopkgtest failure: 
Can't locate Bio/SeqFeature/Lite.pm in @INC
Marked as fixed in versions libbio-db-hts-perl/3.01-3.
> --
Stopping processing here.

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

Bug#945969: marked as done (tinyeartrainer: Intent to remove from Debian)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jan 2020 16:58:28 +
with message-id 
and subject line Bug#947893: Removed package(s) from unstable
has caused the Debian Bug report #945969,
regarding tinyeartrainer: Intent to remove from Debian
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.)


-- 
945969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tinyeartrainer
Version: 0.1.0-4
Severity: serious
Tags: bullseye sid

tinyeartrainer was recently removed from Testing as part of the
Python2 removals.

It looks to me like tinyeartrainer's last release was a decade ago and
that it is unlikely to be ported away from pygtk and Python 2.

Therefore, I or someone else will file a bug soon to request that
tinyeartrainer be removed from Debian Unstable.

This package can easily be added back to Debian if someone does port
it to use supported libraries.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 0.1.0-4+rm

Dear submitter,

as the package tinyeartrainer 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/947893

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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#885488: marked as done (tinyeartrainer: Depends on unmaintained pygtk)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jan 2020 16:58:28 +
with message-id 
and subject line Bug#947893: Removed package(s) from unstable
has caused the Debian Bug report #885488,
regarding tinyeartrainer: Depends on unmaintained pygtk
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.)


-- 
885488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tinyeartrainer
Version: 0.1.0-4
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings (and gtk3).

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 0.1.0-4+rm

Dear submitter,

as the package tinyeartrainer 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/947893

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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#938669: marked as done (tinyeartrainer: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jan 2020 16:58:28 +
with message-id 
and subject line Bug#947893: Removed package(s) from unstable
has caused the Debian Bug report #938669,
regarding tinyeartrainer: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:tinyeartrainer

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

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

Dear submitter,

as the package tinyeartrainer 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/947893

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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#885277: marked as done (emma: Depends on unmaintained pygtk)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jan 2020 16:59:03 +
with message-id 
and subject line Bug#947905: Removed package(s) from unstable
has caused the Debian Bug report #885277,
regarding emma: Depends on unmaintained pygtk
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.)


-- 
885277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emma
Version: 0.6-5
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 0.6-5+rm

Dear submitter,

as the package emma 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/947905

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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#943056: marked as done (emma: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jan 2020 16:59:03 +
with message-id 
and subject line Bug#947905: Removed package(s) from unstable
has caused the Debian Bug report #943056,
regarding emma: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
943056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emma
Version: 0.6-5
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

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

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

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

  This is the least preferred option.

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

Dear submitter,

as the package emma 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/947905

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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 ---

Processed: retitle 948224 to pillow: CVE-2019-19911 CVE-2020-5310 CVE-2020-5311 CVE-2020-5312 CVE-2020-5313

[Debian Bug Tracking System]

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

> # fix error in previous sent control message
> retitle 948224 pillow: CVE-2019-19911 CVE-2020-5310 CVE-2020-5311 
> CVE-2020-5312 CVE-2020-5313
Bug #948224 [pillow] pillow: CVE-2020-5310 CVE-2020-5311 CVE-2020-5312 
CVE-2020-5313
Changed Bug title to 'pillow: CVE-2019-19911 CVE-2020-5310 CVE-2020-5311 
CVE-2020-5312 CVE-2020-5313' from 'pillow: CVE-2020-5310 CVE-2020-5311 
CVE-2020-5312 CVE-2020-5313'.
> thanks
Stopping processing here.

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

Processed (with 1 error): Re: Bug#948224: pillow: CVE-2020-5310 CVE-2020-5311 CVE-2020-5312 CVE-2020-5313

[Debian Bug Tracking System]

Processing control commands:

> found -1 6.2.1-2
Bug #948224 [pillow] pillow: CVE-2020-5310 CVE-2020-5311 CVE-2020-5312 
CVE-2020-5313
There is no source info for the package 'pillow' at version '6.2.1-2' with 
architecture ''
Unable to make a source version for version '6.2.1-2'
Marked as found in versions 6.2.1-2.
> retitle pillow: CVE-2019-19911 CVE-2020-5310 CVE-2020-5311 CVE-2020-5312 
> CVE-2020-5313
Unknown command or malformed arguments to command.


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

Bug#948224: pillow: CVE-2020-5310 CVE-2020-5311 CVE-2020-5312 CVE-2020-5313

[Salvatore Bonaccorso]

Control: found -1 6.2.1-2
Control: retitle pillow: CVE-2019-19911 CVE-2020-5310 CVE-2020-5311 
CVE-2020-5312 CVE-2020-5313

Hi,

On Sun, Jan 05, 2020 at 04:30:36PM +0100, Markus Koschany wrote:
> The following vulnerabilities were published for pillow. It appears they
> are fixed in version 6.2.2.

Additionally there is CVE-2019-19911, fixed by
https://github.com/python-pillow/Pillow/commit/774e53bb132461d8d5ebefec1162e29ec0ebc63d
as well adressed in 6.2.2. Thus track it here with same bug.

Regards,
Salvatore

Processed: retitle 948215 to FTBFS after ruby-i18n has been updated to version 1.x

[Debian Bug Tracking System]

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

> retitle 948215 FTBFS after ruby-i18n has been updated to version 1.x
Bug #948215 [jekyll] FTBFS after rubny-i18n has been updated to version 1.x
Changed Bug title to 'FTBFS after ruby-i18n has been updated to version 1.x' 
from 'FTBFS after rubny-i18n has been updated to version 1.x'.
> thanks
Stopping processing here.

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

Bug#934119: marked as done (torbrowser-launcher: Erroneously manages /etc/apparmor.d/local/torbrowser.* as conffiles)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jan 2020 16:21:31 +
with message-id 
and subject line Bug#934119: fixed in torbrowser-launcher 0.3.2-5
has caused the Debian Bug report #934119,
regarding torbrowser-launcher: Erroneously manages 
/etc/apparmor.d/local/torbrowser.* as conffiles
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.)


-- 
934119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934119
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: torbrowser-launcher
Version: 0.3.2-1
Severity: normal

With this version, /etc/apparmor.d/local/torbrowser.Browser.firefox
and /etc/apparmor.d/local/torbrowser.Tor.tor are managed as conffiles
again, while they should not: they're supposed to be created/deleted
as needed by bits of maintainer scripts generated by dh_apparmor.

A problematic consequence is that if I have local tweaks in those
files (which is their actual intended purpose), I'm asked on upgrade
to resolve the conflict between my configuration and the empty one
shipped by the package.

I believe we've had the same bug in the past, that got fixed in
d0deb2f923edbaf3c2801c46d74b7925c5605593. I'm not sure what
exact rm_conffile call would be suitable here (depends on which
upgrade paths we shall support).

Cheers,
-- 
intrigeri
--- End Message ---
--- Begin Message ---
Source: torbrowser-launcher
Source-Version: 0.3.2-5

We believe that the bug you reported is fixed in the latest version of
torbrowser-launcher, 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.
Roger Shimizu  (supplier of updated torbrowser-launcher 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Jan 2020 01:07:36 +0900
Source: torbrowser-launcher
Architecture: source
Version: 0.3.2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers 

Changed-By: Roger Shimizu 
Closes: 934119
Changes:
 torbrowser-launcher (0.3.2-5) unstable; urgency=medium
 .
   * debian/maintscript:
 - Move from torbrowser-launcher.maintscript to maintscript.
 - The following files are still shipped by this package, so removed them
   from rm_conffile line:
 /etc/apparmor.d/local/torbrowser.Browser.firefox
 /etc/apparmor.d/local/torbrowser.Tor.tor
   * debian/manpages:
 - Move from torbrowser-launcher.manpages to manpages.
   * debian/rules:
 - Remove copying apparmor profile, since this is handled by setup.py.
   * debian/preinst:
 - Remove old apparmor profiles shipped not as conffile before, only
   if the checksum matches, which means without user modification:
 /etc/apparmor.d/local/torbrowser.Browser.firefox
 /etc/apparmor.d/local/torbrowser.Tor.tor
   (Closes: #934119)
Checksums-Sha1:
 c941a28f2c6ec4a4818b0c5e38bf44b36ff401fa 2213 torbrowser-launcher_0.3.2-5.dsc
 c164e6774739d3c856a6ac151ea6db2dfde0e76c 21696 
torbrowser-launcher_0.3.2-5.debian.tar.xz
 151f678a125819b4dac91a6988ab784113ce56a3 5895 
torbrowser-launcher_0.3.2-5_source.buildinfo
Checksums-Sha256:
 b06748ca57e9174a01e27589a403cb04b0aaefb55d0c4021cfea504b18496980 2213 
torbrowser-launcher_0.3.2-5.dsc
 2124426ab7e0c18d7625062c92ca206f53e6e48d2a954025d3ccb4db1044acfd 21696 
torbrowser-launcher_0.3.2-5.debian.tar.xz
 5c8a758e9805e5b1096eac8163e97db69f71916e1531f33d1b2068ba55f8d26e 5895 
torbrowser-launcher_0.3.2-5_source.buildinfo
Files:
 8a9afd4d53043ebec6f8435158b9887f 2213 contrib/web optional 
torbrowser-launcher_0.3.2-5.dsc
 2a1b44bd922fe9d08624e41d1425251f 21696 contrib/web optional 
torbrowser-launcher_0.3.2-5.debian.tar.xz
 682f0fcfd4550fe3ca7969e481b62669 5895 contrib/web optional 
torbrowser-launcher_0.3.2-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAl4SCfwQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qFqzD/97BkGbsrztfA+k1o38EWdAQC23VJ+ta+Qk
70FACQCGtgwP3FXFSmgRH/uciYeV6BDTefN5mnbK7rgNJiF7vAq/tHQam7D2Ru0s
ZzP9Fyje1kQlOkwU3gjrzIJPr9hAEUKBOwcaTzKgBYnDbgWngDSMX8D8PARGdrN1
F8E/u3OFuYYi/tjKDbSRksqo/1i2cPDbFL8jwKJEjPV2o0p+bZ616bj0hOk8/PeJ

Bug#948224: pillow: CVE-2020-5310 CVE-2020-5311 CVE-2020-5312 CVE-2020-5313

[Markus Koschany]

Package: pillow
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for pillow. It appears they
are fixed in version 6.2.2.

CVE-2020-5310[0]:
| libImaging/TiffDecode.c in Pillow before 6.2.2 has a TIFF decoding
| integer overflow, related to realloc.


CVE-2020-5311[1]:
| libImaging/SgiRleDecode.c in Pillow before 6.2.2 has an SGI buffer
| overflow.


CVE-2020-5312[2]:
| libImaging/PcxDecode.c in Pillow before 6.2.2 has a PCX P mode buffer
| overflow.


CVE-2020-5313[3]:
| libImaging/FliDecode.c in Pillow before 6.2.2 has an FLI buffer
| overflow.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-5310
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5310
[1] https://security-tracker.debian.org/tracker/CVE-2020-5311
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5311
[2] https://security-tracker.debian.org/tracker/CVE-2020-5312
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5312
[3] https://security-tracker.debian.org/tracker/CVE-2020-5313
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5313

Please adjust the affected versions in the BTS as needed.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Processed: Bug#948215 marked as pending in jekyll

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #948215 [jekyll] FTBFS after rubny-i18n has been updated to version 1.x
Added tag(s) pending.

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

Bug#948215: marked as pending in jekyll

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #948215 in jekyll 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/ruby-team/jekyll/commit/61d388999dbc3b077164a718eee8b29f3804d58c


Add patch to allow Jekyll to run with ruby-i18n 1.x too

* d/p/0017-allow-jekyll-to-run-with-ruby-i18n-1.x.patch: Add patch.
  - Allow ruby-i18n 0.x and 1.x (closes: #948215).
* d/p/series: Add patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/948215

Processed: Re: Bug#948167: plplot: autopkgtest regression on arm64: /usr/lib/x86_64-linux-gnu/libm.so: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #948167 [src:plplot] plplot: autopkgtest regression on arm64: 
/usr/lib/x86_64-linux-gnu/libm.so: No such file or directory
Added tag(s) confirmed.

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

Bug#948167: plplot: autopkgtest regression on arm64: /usr/lib/x86_64-linux-gnu/libm.so: No such file or directory

[Rafael Laboissière]

Control: tags -1 confirmed

* Ole Streicher  [2020-01-05 14:19]:


On 05.01.20 10:32, Rafael Laboissière wrote:

A "simple" solution would be to create a new package plplot-examples, 
with Arch:any, containing the examples/ directory that is currently in 
/usr/share/doc/plplot-doc/.


@Ole: would you agree with this change?


I agree that this is the best solution, so feel free to implement it.


Ok, I will do it.  Just three comments:

1) The package will have to go through the NEW queue after upload, 
because of the new binary package.


2) The master branch in the Git repository contains the version currently 
in experimental.  I created a new branch "unstable" for updating the 
package in unstable.  In particular, for generating the d/changelog 
entries, one needs to do: "gbp dch --debian-branch=unstable".


3) Since 5.15.0+dfsg-11 has been already uploaded to experimental, that 
version cannot be used for uploading to unstable.  I will use the 
versioning scheme 5.15.0+dfsg-10+unstable1, unless you have any 
objections.


Best,

Rafael

Bug#947794: python-apt: autopkgtest fails on deprecation *warnings* to stderr

[Julian Andres Klode]

Version: 1.9.1
On Mon, Dec 30, 2019 at 09:18:50PM +0100, Paul Gevers wrote:
> Source: python-apt
> Version: 1.8.4
> Severity: serious
> Tags: sid bullseye
> User: debian...@lists.debian.org
> Usertags: needs-update
> Control: affects -1 src:python3-defaults
> 
> Dear maintainers,
> 
> With a recent upload of python3-defaults the autopkgtest of python-apt
> fails in testing when that autopkgtest is run with the binary packages
> of python3-defaults from unstable. It passes when run with only packages
> from testing. In tabular form:
>passfail
> python3-defaults   from testing3.7.5-3
> python-apt from testing1.8.4
> all others from testingfrom testing
> 
> I copied some of the output at the bottom of this report. I seems your
> test fails only on deprecation *warnings* to stderr. Please, either
> disable deprecation warnings in your autopkgtest or allow output to
> stderr (the allow-stderr restriction). Autopkgtest is not the place to
> catch deprecation warnings.
> 
> Currently this regression is blocking the migration of python3-defaults
> to testing [1], although we will ignore this failure for this migration.

This was fixed agos ago in 1.9.1 in experimental. Unfortunately, we're
a bit behind on schedule. I hope to get it into unstable in a month or
two, there are more pressing concerns for this package atm. I might just
allow-stderr in the meantime.

The unfortunate situation is that unstable shares the branch with
stable, and things get really messy now, because I do not really want
to maintain two branches of 1.8.y. Ugh.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#948180: found 948180 in 4.1.2+dfsg-5, closing 948180

[Salvatore Bonaccorso]

Hi Markus,

On Sun, Jan 05, 2020 at 02:15:41PM +0100, Markus Koschany wrote:
> 
> Am 05.01.20 um 13:39 schrieb Salvatore Bonaccorso:
> > Hi Markus,
> > 
> > On Sun, Jan 05, 2020 at 01:26:37PM +0100, Markus Koschany wrote:
> >> Am 05.01.20 um 06:44 schrieb Salvatore Bonaccorso:
> >>> found 948180 4.1.2+dfsg-5
> >>> close 948180 4.2.0+dfsg-1
> >>> thanks
> >>
> >> You could have kept the bug report open until the issue is really fixed
> >> in unstable. I didn't see the new version in experimental until after I
> >> filed the bug report but sometimes such versions will stay there a long
> >> time for various reasons. There are tools like apt-listbugs that will
> >> warn unstable users about RC bugs but only if someone files bug reports.
> > 
> > The BTS (ans various tools) can handle the version tracking (and even
> > close a bug with multiple versions, this is actually what for instance
> > happends if a fix goes in as well via stable and oldstable and
> > contains a respective bug closer as well) -- this is the reason why I
> > first marked 4.1.2+dfsg-5 as found (which contains the bug), and then
> > one can close the bug (BTS will still see that it's unfixed in
> > unstable accordingly).
> > 
> > So either the fix then goes in by cherry-picking fixes for unstable on
> > top of 4.1.2+dfsg-5 or it goes in via a subsequent upload to unstable
> > of the 4.2.0 version.
> > 
> > See as well the respective graph the BTS know: 
> > https://bugs.debian.org/cgi-bin/version.cgi?absolute=0;fixed=4.2.0%2Bdfsg-1;found=4.1.2%2Bdfsg-5;info=1;package=opencv;collapse=1
> 
> By closing the bug report it disappeared from
> 
> https://tracker.debian.org/pkg/opencv
> 
> There is no "action required" bullet point and the RC bug count is zero
> now. The bug is also marked as resolved now.
> 
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=opencv
> 
> I know the BTS but it was completely sufficient to mark the bug as fixed
> in experimental, you didn't have to close it. People usually don't look
> up the BTS graph to understand if their version is affected and they
> will check the most obvious places first. If bugs are getting closed in
> stable and oldstable, then those have been fixed in nearly all cases in
> unstable as well already.

Right, both approaches have their legitimations. I hear your arguments
and I value your opinion. And I have as well explained my position.
So, if you think there is more benefit in only mark it as fixed then
feel free to reopen it removing the closed status and close the bug
only once the fix entered unstable.

Downside: There is slight chance that then the bug will not be closed,
and will continue to be marked as unresolved, see #924884 for an
example what I mean, which I now just closed retrospectively.

Regards,
Salvatore

Bug#934119: [Pkg-privacy-maintainers] Bug#934119: torbrowser-launcher: Erroneously manages /etc/apparmor.d/local/torbrowser.* as conffiles

[intrigeri]

Hi,

Roger Shimizu (2020-01-05):
> I find this is due to below files were shipped by previous version of
> torbrowser-launcher, but not as conffile.
>   /etc/apparmor.d/local/torbrowser.Tor.tor
>   /etc/apparmor.d/local/torbrowser.Browser.firefox

Yes.

> But now they're shipped with conffile, though in size zero.

That's indeed the problem IMO. See below for my reasoning.

> So new conffiles complain they don't match with existing ones.

Right.

> It can be fixed by removing the old files when they match the checksum
> of old shipped ones.
> The fix will be uploaded soon.

I think this can help for files under /etc/apparmor.d/local/ that the
package does not install at all anymore (be it via dh-apparmor or as
conffiles). This would clean up stuff and that's good :)

But I don't think it will help for local/torbrowser.Tor.tor and
local/torbrowser.Browser.firefox, which this bug report was initially
about.

FYI, the very purpose of the files under /etc/apparmor.d/local/ is to
be modified by the system administrator, that is, to diverge from
what's shipped by packages under /etc/apparmor.d/. The content of
these files will, by design, always be: local changes, done manually,
and that packages and dpkg should not fiddle with.

So, if /etc/apparmor.d/local/* are conffiles, and if the administrator
is using this facility, upon upgrades their local changes will
necessarily conflict with the (empty) version installed by the
package, and dpkg will ask what to do. That would be pretty annoying,
since the answer to dpkg's question in this case will always be "keep
my local changes, because that's what this file is for after all :)".

I hope this clarifies the drawback I see in handling these files
as conffiles.

Are there advantages in treating them as conffiles, that outweigh
this drawback?

Cheers,
-- 
intrigeri

Bug#936463: python3-ecasound: Upstream are working on Python 3 support

[Ross Gammon]

Hi,

There is a pull request to add Python3 support:
https://github.com/kaivehmanen/ecasound/pull/1

It was updated 18 hours ago. We should keep an eye on that.

Ross



signature.asc
Description: OpenPGP digital signature

Bug#948215: FTBFS after rubny-i18n has been updated to version 1.x

[Daniel Leidert]

Package: jekyll
Version: 3.8.3+dfsg-6
Severity: serious
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

After ruby-i18n has been updated to version 1.x jekyll fails to build because
it requires ruby-i18n ~> 0.7. It seems the fix is as trivial as allowing
i18n >= 0.7 and < 2.

Upstream only fixed Jekyll 4 to work with i18n < 2:
https://github.com/jekyll/jekyll/pull/6931
https://github.com/jekyll/jekyll/pull/7044

Fixing this issue should also finally fix the testing migration for all packages
depending on Jekyll.

The fix is already prepared in the ruby team's git repository.

Regards, Daniel


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

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

Versions of packages jekyll depends on:
ii  bundler 1.17.3-3
ii  ruby1:2.5.2
ii  ruby-addressable2.7.0-1
ii  ruby-classifier-reborn  2.2.0-1
ii  ruby-colorator  1.1.0-3
ii  ruby-em-websocket   0.5.1-2
ii  ruby-i18n   1.5.3-2
ii  ruby-jekyll-coffeescript1.2.2-2
ii  ruby-jekyll-feed0.12.1-3
ii  ruby-jekyll-gist1.5.0-2
ii  ruby-jekyll-paginate1.1.0-3
ii  ruby-jekyll-sass-converter  1.5.2-1
ii  ruby-jekyll-watch   2.2.1-1
ii  ruby-kramdown   1.17.0-1
ii  ruby-launchy-shim   2.3.0.1
ii  ruby-liquid 4.0.3-1
ii  ruby-mercenary  0.3.6-1
ii  ruby-mime-types 3.2.2-1
ii  ruby-pathutil   0.16.1-1
ii  ruby-pygments.rb1.2.0-4
ii  ruby-rdiscount  2.1.8-1+b5
ii  ruby-redcarpet  3.4.0-4+b1
ii  ruby-rouge  3.14.0-1
ii  ruby-safe-yaml  1.0.5-1
ii  ruby-toml   0.2.0-3
ii  xdg-utils   1.1.3-1

Versions of packages jekyll recommends:
pn  ruby-mysql  
pn  ruby-sequel 
pn  ruby-sequel-pg  

jekyll suggests no packages.

- -- no debconf information

- -- debsums errors found:
debsums: changed file 
/usr/share/rubygems-integration/all/specifications/jekyll-3.8.3.gemspec (from 
jekyll package)

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl4R6VEACgkQS80FZ8KW
0F0zdw//bs9AtdRwaCfpuL1jU3fB5hmcxYk2eQkPJ9bIkAGsBRQ3IKXOji+q1gDX
+CC4OknqgQoCbNjw9UDSqRu6zxS6ERVLwl6HoKquP1fiwcU2scjy6oSmCP6xf+tz
s/jEmAnVnXqRdjg6J0tdD8Vw8C6xgAkPB/Id2X6TeOAcMkiz16oUym/zixKTySS9
lMCML8sEQIWbuEYHNa2eIQmv6jWmbZUAzlWphK5GuZ7hM6CjRpe46zClbvWWEawA
mHqF/OJcCt3Zxz3UVj4uqG3Xe1df+AiMVidUcH77JM6JuTA7dUO0PeyUbdvAJy/L
lvfzvQkVoDc+YuWCaMXIjorEWezSIdw8tY2PzjRxZjOvG48vNhmkWd8ORqx6z5Ap
aYsN2yt4a4yWo/p6e/arnSN8/W7zoHNRwy5NjylLyKb2zvyWGogsM66plVGm4+JX
QO8o7P/e3B6LCh+9nbZj98N2SoOSCt3rCsDW6XXoYRF0JvdwWuHwdexVA+u8k6zP
2eZyeyi/TaYR3QaY9b/jRSmEV25jYIzJQ1e0QqoLj+0nuy9bM/sOcOgxgFO2rBS4
I3iwn85w/WauozIzMJX4dOilOgKaudS0Ja8SzNTOMlbr5mvWBUMTKC7PMQoIpLUH
DNNCnktr41i2NHhwAucankfwrvYV3ym2T2zIHBlXkwDJzh83rlU=
=3prK
-END PGP SIGNATURE-

Bug#948214: barriers sometimes runs with high load and use all memory

[Jörg Frings-Fürst]

Package: barrier
Version: 2.3.2+dfsg-1+b1
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

some times the prozess barriers run with high load and use all memory:

[quote]
$  cat /proc/5819/status | grep VmSize
VmSize: 22716804 kB
[/quote]

[quote]
PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+  COMMAND
5819 jff   20   0   22,3g  13,1g   1352 R  95,0  84,2 130:18.66 barriers
[/quote]


If you need more infos please ask.


CU
Jörg



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

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

Versions of packages barrier depends on:
ii  libavahi-compat-libdnssd1  0.7-5
ii  libc6  2.29-3
ii  libgcc11:9.2.1-21
ii  libqt5core5a   5.12.5+dfsg-2
ii  libqt5gui5 5.12.5+dfsg-2
ii  libqt5network5 5.12.5+dfsg-2
ii  libqt5widgets5 5.12.5+dfsg-2
ii  libssl1.1  1.1.1d-2
ii  libstdc++6 9.2.1-21
ii  libx11-6   2:1.6.8-1
ii  libxext6   2:1.3.3-1+b2
ii  libxi6 2:1.7.9-1
ii  libxinerama1   2:1.1.4-2
ii  libxrandr2 2:1.5.1-1
ii  libxtst6   2:1.2.3-1
ii  openssl1.1.1d-2

barrier recommends no packages.

barrier suggests no packages.

- -- debconf-show failed

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl4R53YACgkQCfifPIyh
0l0xQBAAzbFfMs5ymYYIAZA9V0dVHn+aL6pEyItcX+5QWW+yy3kSB9gWpF0ALU1O
tw169Byku/NTF4pz3kGTnutAapY1q1E8R1B+LVnOcAKNHrEyuYcdsPh8zzALMsAn
TA7c5OMaC7QjDez+Dx+C4HCPAEbvU87A/ZwA42x0OUbtRbJpQc+A5gxBx4c1OV1s
+bD3Hg4oQLaSY5h02wMv/cab3Ee8m82KRW6BOorejQ2Bm4HU012olXYy7+yGwKdD
tETdZPSr0jM4Eoh6ycKJvXoakoC//HfwfuwK4cfJTsYnUdKqnEt63S0jsNevdPxB
kCzEhfalvcAH7T/zpmdoapTmEzF59Wk1/G6PiNr7RveqG2k/egyVMmn6FX1Xfp2r
+BurbzUCGzJBaDTJ+a4SgpjPj5AuVfbJSTHfF52oacczyuaTbVMve8OSJ7n55egE
NzAyxx9nyFbyhXF1h4SY5gdKNoL4RORLTzn6Xfh3bDpGXrkaV/0QWD79pRyHL6kQ
VThDO6lhuQfELR+Zqy/g20ljPxeTHy510Q/JxRNsLK5NVgiIKO5P2YrQveuCE8i8
SQbLMLa387haEz717yt9C+blAj2KJfeot2U4NLgYSmnxOYI5Ew240wQ7+g0G+sy2
42t91JtKR8X5PlNouOSBhIOLmiPYRaGUYdbeXGoVtd5bdgbmsuM=
=jv8t
-END PGP SIGNATURE-

Bug#936891: python3-libmapper: latest upstream release supports Python 3

[Ross Gammon]

Hi,

According to the upstream Github repo, Python 3 support was added in 2017.

https://github.com/libmapper/libmapper

We should package the latest release.

Regards,

Ross



signature.asc
Description: OpenPGP digital signature

Bug#948167: plplot: autopkgtest regression on arm64: /usr/lib/x86_64-linux-gnu/libm.so: No such file or directory

[Ole Streicher]

Hi Rafael,

On 05.01.20 10:32, Rafael Laboissière wrote:
> A "simple" solution would be to create a new package plplot-examples,
> with Arch:any, containing the examples/ directory that is currently in
> /usr/share/doc/plplot-doc/.
> 
> @Ole: would you agree with this change?

I agree that this is the best solution, so feel free to implement it.

Cheers

Ole

Bug#948180: found 948180 in 4.1.2+dfsg-5, closing 948180

[Markus Koschany]

Am 05.01.20 um 13:39 schrieb Salvatore Bonaccorso:
> Hi Markus,
> 
> On Sun, Jan 05, 2020 at 01:26:37PM +0100, Markus Koschany wrote:
>> Am 05.01.20 um 06:44 schrieb Salvatore Bonaccorso:
>>> found 948180 4.1.2+dfsg-5
>>> close 948180 4.2.0+dfsg-1
>>> thanks
>>
>> You could have kept the bug report open until the issue is really fixed
>> in unstable. I didn't see the new version in experimental until after I
>> filed the bug report but sometimes such versions will stay there a long
>> time for various reasons. There are tools like apt-listbugs that will
>> warn unstable users about RC bugs but only if someone files bug reports.
> 
> The BTS (ans various tools) can handle the version tracking (and even
> close a bug with multiple versions, this is actually what for instance
> happends if a fix goes in as well via stable and oldstable and
> contains a respective bug closer as well) -- this is the reason why I
> first marked 4.1.2+dfsg-5 as found (which contains the bug), and then
> one can close the bug (BTS will still see that it's unfixed in
> unstable accordingly).
> 
> So either the fix then goes in by cherry-picking fixes for unstable on
> top of 4.1.2+dfsg-5 or it goes in via a subsequent upload to unstable
> of the 4.2.0 version.
> 
> See as well the respective graph the BTS know: 
> https://bugs.debian.org/cgi-bin/version.cgi?absolute=0;fixed=4.2.0%2Bdfsg-1;found=4.1.2%2Bdfsg-5;info=1;package=opencv;collapse=1

By closing the bug report it disappeared from

https://tracker.debian.org/pkg/opencv

There is no "action required" bullet point and the RC bug count is zero
now. The bug is also marked as resolved now.

https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=opencv

I know the BTS but it was completely sufficient to mark the bug as fixed
in experimental, you didn't have to close it. People usually don't look
up the BTS graph to understand if their version is affected and they
will check the most obvious places first. If bugs are getting closed in
stable and oldstable, then those have been fixed in nearly all cases in
unstable as well already.

Markus




signature.asc
Description: OpenPGP digital signature

Bug#948165: marked as pending in ceph

[Bernd Zeimetz]

On 1/5/20 1:05 AM, Andreas Beckmann wrote:
> Don't you need .maintscript files to rm_conffile the now (again)
> obsolete conffiles? Or if you already have them, bump the version?

I'm not keen on maintaining extra stuff for an upload that was for a
week in unstable. The more interesting thing would be to figure out if
they should be added to an upload to buster (if I get that monster diff
of the next upstream release trough the release team).

> That crafted piuparts test should actually investigate missing B+R for
> the potential move of some files from ceph-mds 14.2.4-8 to ceph-common
> 14.2.5-1:
>   usr/bin/cephfs-data-scan
>   usr/bin/cephfs-journal-tool
>   usr/bin/cephfs-table-tool
> but got stopped early when it stomped over the bash completions.

thanks, fixing right now.
piuparts doesn't work properly in the CI at the moment, so I'm missing
such issues :(



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

Bug#938072: python-pyknon latest upstream release supports Python 3

[Ross Gammon]

Hi.

It looks like the watchfile needs fixing. According to upstream, Python
3 is supported in the latest release.

https://github.com/kroger/

Regards,

Ross



signature.asc
Description: OpenPGP digital signature

Bug#948195: nvidia-legacy-340xx-driver: Xorg fails to start with a kernel panic after the upgrade to 340.108-1

[KeyofBlueS]

Yes I'm on unstable. I upgraded on December 31th but I waited a few days to
check that the problem just wasn't on my side.
I labeled it as important because it seemed right to me (it doesn't cause
data loss or introduces a security hole ecc...).
Among the various tests that I did, I disabled lightdm too and it can be
enabled again with "dpkg-reconfigure lightdm".
I made that script because I needed to easly switch between 340.107-8 and
340.108-1 for troubleshooting.

Processed: bug 948180 is forwarded to https://github.com/opencv/opencv/issues/15857

[Debian Bug Tracking System]

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

> forwarded 948180 https://github.com/opencv/opencv/issues/15857
Bug #948180 {Done: Salvatore Bonaccorso } [opencv] opencv: 
CVE-2019-5063 and CVE-2019-5064
Set Bug forwarded-to-address to 'https://github.com/opencv/opencv/issues/15857'.
> thanks
Stopping processing here.

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

Bug#948180: found 948180 in 4.1.2+dfsg-5, closing 948180

[Salvatore Bonaccorso]

Hi Markus,

On Sun, Jan 05, 2020 at 01:26:37PM +0100, Markus Koschany wrote:
> Am 05.01.20 um 06:44 schrieb Salvatore Bonaccorso:
> > found 948180 4.1.2+dfsg-5
> > close 948180 4.2.0+dfsg-1
> > thanks
> 
> You could have kept the bug report open until the issue is really fixed
> in unstable. I didn't see the new version in experimental until after I
> filed the bug report but sometimes such versions will stay there a long
> time for various reasons. There are tools like apt-listbugs that will
> warn unstable users about RC bugs but only if someone files bug reports.

The BTS (ans various tools) can handle the version tracking (and even
close a bug with multiple versions, this is actually what for instance
happends if a fix goes in as well via stable and oldstable and
contains a respective bug closer as well) -- this is the reason why I
first marked 4.1.2+dfsg-5 as found (which contains the bug), and then
one can close the bug (BTS will still see that it's unfixed in
unstable accordingly).

So either the fix then goes in by cherry-picking fixes for unstable on
top of 4.1.2+dfsg-5 or it goes in via a subsequent upload to unstable
of the 4.2.0 version.

See as well the respective graph the BTS know: 
https://bugs.debian.org/cgi-bin/version.cgi?absolute=0;fixed=4.2.0%2Bdfsg-1;found=4.1.2%2Bdfsg-5;info=1;package=opencv;collapse=1

HTH,

Regards,
Salvatore

Bug#948180: found 948180 in 4.1.2+dfsg-5, closing 948180

[Markus Koschany]

Am 05.01.20 um 06:44 schrieb Salvatore Bonaccorso:
> found 948180 4.1.2+dfsg-5
> close 948180 4.2.0+dfsg-1
> thanks

You could have kept the bug report open until the issue is really fixed
in unstable. I didn't see the new version in experimental until after I
filed the bug report but sometimes such versions will stay there a long
time for various reasons. There are tools like apt-listbugs that will
warn unstable users about RC bugs but only if someone files bug reports.

Regards,

Markus




signature.asc
Description: OpenPGP digital signature