Bug#948647: rust-backtrace depends on non-existent librust-compiler-builtins

[Steve Langasek]

Source: rust-backtrace
Version: 0.3.40-2
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

Dear mainatiners,

The rust-backtrace package in unstable is not able to migrate to testing
because it builds binary packages that depend on a non-existent
librust-compiler-builtins-0.1+default-dev:

$ sudo apt install librust-backtrace+compiler-builtins-dev
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 librust-backtrace+compiler-builtins-dev : Depends: 
librust-compiler-builtins-0.1+default-dev (>= 0.1.2-~~) but it is not 
installable
E: Unable to correct problems, you have held broken packages.
$

There is no rust-compiler-builtins package in the Debian archive or in the
NEW queue.  And if this is because they are supposed to be /built in/, well,
it doesn't appear that there's agreement with the compiler packaging about
what Provides should exist.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#948590: marked as done (hardcoded dependency on python)

[Debian Bug Tracking System]

Your message dated Sat, 11 Jan 2020 06:49:13 +
with message-id 
and subject line Bug#948590: fixed in bedops 2.4.37+dfsg-2
has caused the Debian Bug report #948590,
regarding hardcoded dependency on python
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.)


-- 
948590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948590
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bedops
Version: 2.4.37+dfsg-1
Severity: serious
Tags: sid bullseye

the package still has a hardcoded dependency on python.
--- End Message ---
--- Begin Message ---
Source: bedops
Source-Version: 2.4.37+dfsg-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 11 Jan 2020 07:24:20 +0100
Source: bedops
Architecture: source
Version: 2.4.37+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 948590
Changes:
 bedops (2.4.37+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * Depends: s/python/python3/ + fix shebang lines in Python scripts
 Closes: #948590
   * Remove trailing whitespace in debian/changelog
   * Set upstream metadata fields: Bug-Database, Bug-Submit.
   * Remove obsolete field Name from debian/upstream/metadata (already
 present in machine-readable debian/copyright).
Checksums-Sha1:
 845adc8c32469171ab2e2eff0169a8f91f8b5a50 2143 bedops_2.4.37+dfsg-2.dsc
 5f8499424075bedcca0d075cd3f30253a8d0bebb 10496 
bedops_2.4.37+dfsg-2.debian.tar.xz
 f7222e38b1688470969962d73f60f755626bacc2 7701 
bedops_2.4.37+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 c7518ac1b9252fef956f4833c273360d4873d231ca3910c525b0f6d66e0e54dc 2143 
bedops_2.4.37+dfsg-2.dsc
 da380efcb5008d501ac686ddef2d41166445c39a7ea6bced9ffa2154879a0928 10496 
bedops_2.4.37+dfsg-2.debian.tar.xz
 f9f4542d9841914da506e19735abd51a86480447d8e0696fcfa3553edd62c1eb 7701 
bedops_2.4.37+dfsg-2_amd64.buildinfo
Files:
 7dc1e70eb2a62e4ebab9871c498e06c9 2143 science optional bedops_2.4.37+dfsg-2.dsc
 cfb4cbcc0b989400ef5256f3335f7521 10496 science optional 
bedops_2.4.37+dfsg-2.debian.tar.xz
 0f82db50894df0f5b267a1ed8112ea4e 7701 science optional 
bedops_2.4.37+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl4ZbSERHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGS/g/+MtZIAUhhwLu+qs+SedOUjW6hbDxi2GBV
q1Tk1hFO3i5QxjcDs6HZ9RyjEfZblxxpyHGSVL0TC7+capuIwCv3FqvD8gWfbZTW
UGk+TwYP9EL2GDyubeu86TnDvNO0uxF81HOeT/HHo+C9GsbLqaX1rmby5L/u8KPd
+S42xmtxc5jT5NCmSfXdi05hGYbqbmhFzY95n/u/x6QXz/qkmX12A7CU52TIKlzS
srEakJVpK0FAz1bxxwGPHLKRhX7v9cIVwDRvvx1UElNQXfZN+LHu/qbG+ld7h1d5
QLKT37pqp+jqKLqT+x0dOlEBW7Oi9DWAajpDJudHs1luylrsQfjpqzRMI7ofb6GY
OiftxcLSjlBD+ppN3Yd6W1JpPLKnvA5bNODm/Z55Okq+rGJDjoKlqV0ZuYiTVjj3
O9cPBK51luQ/fdv+6BPcq1Myt11CXAGsbJG+QYeMumAL/188p5yRELm3ASdhdoK0
M5+GzIGDWMdzEwP0ohzmrXOSP2pD9ofYQxTcce6IWX5/MqJDAaqnVy69vnJHr5j0
2N7CmfM1WkeyeQZcACmU8ugyyuhUQSnLKOENwVAxxWyMqA6tLH3kUkgwzqKkevBA
eEJJe9yGvu7t1nqZk1Leu+WEiQnVeFOFAtzZgDyaLNkKzeYg73yTT4G4bwYkA6CN
yOCIMWTMY0w=
=0BKK
-END PGP SIGNATURE End Message ---

Bug#948645: pesign FTBFS: nss-induced error: unsigned conversion from ‘int’ to ‘unsigned char’ changes value from ‘496’ to ‘240’ [-Werror=overflow]

[Helmut Grohne]

Source: pesign
Version: 0.112-5
Severity: serious

pesign fails to build from source in unstable:

| /usr/bin/gcc -g -O2 -ffile-prefix-map=/build/1st/pesign-0.112=. 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror 
-Wno-cpp  -Wsign-compare -Wno-unused-result -Wno-unused-function -std=gnu11 
-fshort-wchar -fPIC -flto -fno-strict-aliasing -fno-merge-constants 
-fkeep-inline-functions -D_GNU_SOURCE -DCONFIG_x86_64 
-I/build/1st/pesign-0.112/include -I/usr/include/efivar -I/usr/include/nss 
-I/usr/include/nspr -I/usr/include/uuid -Werror -Wdate-time -D_FORTIFY_SOURCE=2 
-c -o efikeygen.o efikeygen.c
| In file included from /usr/include/nss/cert.h:22,
|  from efikeygen.c:39:
| efikeygen.c: In function 'add_cert_type':
| /usr/include/nss/certt.h:460:5: error: unsigned conversion from 'int' to 
'unsigned char' changes value from '496' to '240' [-Werror=overflow]
|   460 | (NS_CERT_TYPE_SSL_CLIENT | NS_CERT_TYPE_SSL_SERVER | 
NS_CERT_TYPE_EMAIL | \
|   | ^
| efikeygen.c:208:23: note: in expansion of macro 'NS_CERT_TYPE_APP'
|   208 |  unsigned char type = NS_CERT_TYPE_APP;
|   |   ^~~~
| cc1: all warnings being treated as errors
| make[2]: *** [/build/1st/pesign-0.112/Make.rules:33: efikeygen.o] Error 1
| make[2]: Leaving directory '/build/1st/pesign-0.112/src'
| make[1]: *** [Makefile:25: all] Error 2
| make[1]: Leaving directory '/build/1st/pesign-0.112'
| dh_auto_build: make -j1 returned exit code 2
| make: *** [debian/rules:15: build] Error 255
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Observed by crossqa:
http://crossqa.subdivi.de/build/pesign_0.112-5_arm64_20200111051741.log
Reproduced by reproducible builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/pesign_0.112-5.rbuild.log.gz

Very likely, this failure is due to a change in nss. I've Cced the
mozilla team.

Helmut

Bug#948643: apt-file: fails to update

[Anthony M.R. Alvis]

Package: apt-file
Version: 3.2.2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I have attached a text file containing what happens after i run sudo apt-file 
update;

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 10 (buster)
Release:10
Codename:   buster
Architecture: armv7l

Kernel: Linux 4.19.75-v7l+ (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages apt-file depends on:
ii  apt  1.8.2
ii  libapt-pkg-perl  0.1.34+b1
ii  liblist-moreutils-perl   0.416-1+b3
ii  libregexp-assemble-perl  0.36-1
ii  perl 5.28.1-6

apt-file recommends no packages.

apt-file suggests no packages.

-- no debconf information
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Get:3 http://archive.raspberrypi.org/debian buster/main armhf Contents (deb) 
[998 kB]
Get:4 http://raspbian.raspberrypi.org/raspbian buster/main armhf Contents (deb) 
[39.8 MB]
Get:5 http://raspbian.raspberrypi.org/raspbian buster/contrib armhf Contents 
(deb) [211 kB]  

Get:6 http://raspbian.raspberrypi.org/raspbian buster/non-free armhf Contents 
(deb) [780 kB]  
   
Get:7 http://raspbian.raspberrypi.org/raspbian buster/rpi armhf Contents (deb) 
[307 B] 
  
Fetched 41.8 MB in 1min 40s (418 kB/s)  

 
Traceback (most recent call last):
  File "/usr/lib/cnf-update-db", line 26, in 
col.create(db)
  File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line 94, 
in create
self._fill_commands(con)
  File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line 132, 
in _fill_commands
self._parse_single_contents_file(con, f, fp.stdout)
  File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line 271, 
in _parse_single_contents_file
priority = component_priorities[component]
KeyError: 'rpi'
Reading package lists... Done
E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test 
-w /var/lib/command-not-found/ -a -e /usr/lib/cnf-update-db; then 
/usr/lib/cnf-update-db > /dev/null; fi'
E: Sub-process returned an error code

Bug#948597: marked as done (fasta3-doc: missing Breaks+Replaces: fasta3 (<< 36.3.8h))

[Debian Bug Tracking System]

Your message dated Sat, 11 Jan 2020 06:19:14 +
with message-id 
and subject line Bug#948597: fixed in fasta3 36.3.8h-2
has caused the Debian Bug report #948597,
regarding fasta3-doc: missing Breaks+Replaces: fasta3 (<< 36.3.8h)
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.)


-- 
948597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fasta3-doc
Version: 36.3.8h-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Preparing to unpack .../fasta3-doc_36.3.8h-1_all.deb ...
  Unpacking fasta3-doc (36.3.8h-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/fasta3-doc_36.3.8h-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/fasta3/fasta_guide.pdf', which is also 
in package fasta3 36.3.8g-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/fasta3-doc_36.3.8h-1_all.deb


cheers,

Andreas


fasta3=36.3.8g-1_fasta3-doc=36.3.8h-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: fasta3
Source-Version: 36.3.8h-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 11 Jan 2020 06:55:15 +0100
Source: fasta3
Binary: fasta3 fasta3-dbgsym fasta3-doc
Architecture: source amd64 all
Version: 36.3.8h-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 fasta3 - tools for searching collections of biological sequences
 fasta3-doc - user guide for FASTA tools
Closes: 948597
Changes:
 fasta3 (36.3.8h-2) unstable; urgency=medium
 .
   * Team upload.
   * Breaks+Replaces: fasta3 (<< 36.3.8h)
 Closes: #948597
   * Remove trailing whitespace in debian/copyright
   * Remove trailing whitespace in debian/rules
   * Trim trailing whitespace.
   * Use secure URI in Homepage field.
   * Fix regexp in d/copyright
   * Package fasta3-doc in section non-free/doc
Checksums-Sha1:
 7c4117d46a6007c8e182fbd0c63c83bcf9230d79 2031 fasta3_36.3.8h-2.dsc
 21df9c9529d98f5b13458159711bd01195c8c399 4592 fasta3_36.3.8h-2.debian.tar.xz
 18e845ba91dab18b0187011b581eac594cc970cb 3103832 
fasta3-dbgsym_36.3.8h-2_amd64.deb
 09d3b0606d48513961db77dea881833584fb410e 267888 fasta3-doc_36.3.8h-2_all.deb
 2debdf8d00d065cf8b27e9dca39b301ebb57a890 6021 fasta3_36.3.8h-2_amd64.buildinfo
 1f0db9974ba79d0a02841ebc2b04e2ff984edc35 456176 fasta3_36.3.8h-2_amd64.deb
Checksums-Sha256:
 4234358938ffd55e7534a2c5f66cc94b65600b57f178ece33aaa7bf9c718f66a 2031 
fasta3_36.3.8h-2.dsc
 fab9b548d20d59a22deb124e3a7f843eb04f89e3fce169b8aad8be835382cf24 4592 
fasta3_36.3.8h-2.debian.tar.xz
 d33c5e6774d8d5346c32501ba99e04151f65c2fcf7963175b6a3ee3b76ceabac 3103832 
fasta3-dbgsym_36.3.8h-2_amd64.deb
 88818f2c8f2b5482fdb047986fc59119129c2a7f138b05037f661cef816cf799 267888 
fasta3-doc_36.3.8h-2_all.deb
 d4f4191d924b538c51cef8e6b5c9cde5da69e1bcadc262567d43fa17a0e35683 6021 
fasta3_36.3.8h-2_amd64.buildinfo
 4ebf9c83d0c1705dd931671c1fa5371aaed43e4e9e6c9de7dfe308847bcd91dd 456176 
fasta3_36.3.8h-2_amd64.deb
Files:
 28b3372816e2f87a2dbaf35db293575c 2031 non-free/science optional 
fasta3_36.3.8h-2.dsc
 e7931ff101bccb79eaf7f4e0249d3d17 4592 non-free/science optional 
fasta3_36.3.8h-2.debian.tar.xz
 eee6c92d2f8c25b29ecd46e0c4938932 3103832 non-free/debug optional 
fasta3-dbgsym_36.3.8h-2_amd64.deb
 

Bug#948642: rust-cookie: Depends on older rust-ring than is in unstable

[Steve Langasek]

Source: rust-cookie
Version: 0.12.0-4
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

rust-cookie depends on rust-ring 0.14, but rust-ring is now at version 0.16
in unstable:

$ sudo apt install librust-cookie+ring-dev
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 librust-cookie+ring-dev : Depends: librust-ring-0.14+default-dev but it is not 
installable
E: Unable to correct problems, you have held broken packages.
$

Please update rust-cookie for compatibility with the current rust-ring.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#948641: rust-extprim: Build-depends on older rust-rand than is in unstable

[Steve Langasek]

Source: rust-extprim
Version: 0.4.1-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

rust-extprim build-depends on librust-rand-0.6+default-dev, but
rust-rand is now at version 0.7 in unstable:

$ sudo apt build-dep rust-extprim
Reading package lists... Done
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 builddeps:rust-extprim : Depends: librust-rand-0.6+default-dev but it is not 
installable
E: Unable to correct problems, you have held broken packages.
$

Please update rust-extprim for compatibility with the current rust-rand.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#948600: marked as done (fastahack: missing Breaks+Replaces: libfastahack0 (<< 1.0.0+dfsg-4))

[Debian Bug Tracking System]

Your message dated Sat, 11 Jan 2020 06:32:29 +0100
with message-id <20200111053229.gk8...@an3as.eu>
and subject line Re: Bug#948600: fastahack: missing Breaks+Replaces: 
libfastahack0 (<< 1.0.0+dfsg-4)
has caused the Debian Bug report #948600,
regarding fastahack: missing Breaks+Replaces: libfastahack0 (<< 1.0.0+dfsg-4)
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.)


-- 
948600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fastahack
Version: 1.0.0+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'buster'.
It installed fine in 'buster', then the upgrade to 'bullseye' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Preparing to unpack .../fastahack_1.0.0+dfsg-4_amd64.deb ...
  Unpacking fastahack (1.0.0+dfsg-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/fastahack_1.0.0+dfsg-4_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/fastahack.1.gz', which is also in 
package libfastahack0 0.0+git20160702.bbc645f+dfsg-6
  Errors were encountered while processing:
   /var/cache/apt/archives/fastahack_1.0.0+dfsg-4_amd64.deb


cheers,

Andreas


libfastahack0=0.0+git20160702.bbc645f+dfsg-6_fastahack=1.0.0+dfsg-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Issue is solved in 1.0.0+dfsg-5.--- End Message ---

Bug#948640: rust-migrations-internals: depends on older rust-barrel than is in unstable

[Steve Langasek]

Source: rust-migrations-internals
Version: 1.4.0-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

rust-migrations-internals depends on librust-barrel+default-dev (<<
0.2.1-~~), but rust-barrel is now at version 0.6.2 in unstable:

$ sudo apt install librust-migrations-internals+barrel-dev
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 librust-migrations-internals+barrel-dev : Depends: librust-barrel+default-dev 
(< 0.2.1-~~)
   Depends: 
librust-barrel+diesel-filled-dev (< 0.2.1-~~) but it is not installable
E: Unable to correct problems, you have held broken packages.
$

Please update rust-migrations-internals for compatibility with the current
rust-barrel.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#948639: rust-log depends on non-existent librust-sval-0.4+fmt-dev

[Steve Langasek]

Source: rust-log
Version: 0.4.8-2
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

Hi Sylvestre,

The rust-log package in unstable is not able to migrate to testing because
it builds binary packages that depend on a non-existent rust-sval:

librust-log+kv-unstable-sval-dev/amd64 unsatisfiable Depends: 
librust-sval-0.4+fmt-dev (>= 0.4.2-~~)
librust-log+sval-dev/amd64 unsatisfiable Depends: librust-sval-0.4-dev (>= 
0.4.2-~~)

There is no rust-sval package in the Debian archive or in the NEW queue.

Please take care to make sure your packages' dependencies are met.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#925749: Debug build is ok

[Andreas Tille]

On Sat, Jan 11, 2020 at 11:13:30AM +0800, Feng Zhao wrote:
> lgf_reader_writer_test passes when I build the program in Debug mode. However,
> Release mode build will fail to run, which is the default build in packaging.

While it is strange that it does not build in Release mode I wonder why
you think it is default mode.  We usually include debug symbols that are
stripped afterwards.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#874880: FreeMedForms projet

[Andreas Tille]

On Sat, Jan 11, 2020 at 08:39:48AM +0800, Paul Wise wrote:
> 
> The bigger problem for entering Debian is what Andreas mentions, that
> the software uses Qt4 instead of Qt5. Once you have released a new
> version that uses Qt5 it could potentially enter Debian.

To be correct: Version 0.9.4 in Debian is Qt4, but Version 1.0.0 in Git
is Qt5.  It just does not build successfully[1] ... and since monthes
nobody was able fix this.  Eric said he can not reproduce this build
issue (in private mail) and non of the Debian maintainers found a clue
so far.

Kind regards
 Andreas.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874880#104

-- 
http://fam-tille.de

Bug#936924: Moving libsvm to Debian Science team

[Andreas Tille]

On Fri, Jan 10, 2020 at 11:45:15PM +0100, Christian Kastner wrote:
> 
> @Andreas: I can't push my changes to master, I get a protected branch
> error. Could you please grant me the necessary privileges?

Strange.  I did not intentionally set the branch protection.  Hope it
works now.
 
> There's a lintian info about a missing JAR, but I suspect that has more
> to do with the symlink from libsvm-java pointing to libsvm3-java.
> 
> I added a simple autopkgtest and it passed. Seeing as the symbols didn't
> change a bit, I can see no reason why this couldn't be uploaded as-is,
> but I'm tired and I'd like to check it again tomorrow with a fresh pair
> of eyes, lest we break something.

Thanks for your detailed work on this.

Kind regards

   Andreas. 

-- 
http://fam-tille.de

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

[Debian Bug Tracking System]

Your message dated Sat, 11 Jan 2020 04:35:05 +
with message-id 
and subject line Bug#938050: fixed in python-psutil 5.6.7-2
has caused the Debian Bug report #938050,
regarding python-psutil: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-psutil

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

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

We believe that the bug you reported is fixed in the latest version of
python-psutil, 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 python-psutil package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 10 Jan 2020 23:13:29 -0500
Source: python-psutil
Architecture: source
Version: 5.6.7-2
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 938050
Changes:
 python-psutil (5.6.7-2) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #938050
Checksums-Sha1:
 b57caf2a4e021f9806297d780d130e7053959e56 2294 python-psutil_5.6.7-2.dsc
 bff1b2364d44209c53ab4cb31ffd9796dcee9f2d 6144 
python-psutil_5.6.7-2.debian.tar.xz
 a3d7dedfebfefadac71fa02fec8793a8e827886a 8141 
python-psutil_5.6.7-2_source.buildinfo
Checksums-Sha256:
 1cec45d62f76e825619dc57641683f3664f7eee2afef6ff9b31a32b5e29583a5 2294 
python-psutil_5.6.7-2.dsc
 f5b6b699b276db7958404d70c0fa14211fa4fec68203ab00f51eb8c2c2c26e32 6144 
python-psutil_5.6.7-2.debian.tar.xz
 a58b2f274803056e3a0b0ab6693292e9e85414afb3d0fd4fd35c4bfb197a8cc2 8141 
python-psutil_5.6.7-2_source.buildinfo
Files:
 120219afa24b02fef9ae4bfa28a7bbbc 2294 

Bug#938050: marked as pending in python-psutil

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #938050 in python-psutil 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/python-psutil/commit/dadf5c376f8b82b35e5083b788e3995a5a731682


Drop python2 support; Closes: #938050


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/938050

Processed: Bug#938050 marked as pending in python-psutil

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#945920: Random Chromium crashes

[nozzy123nozzy]

Tags: patch

Sorry for disturbing all of you, but the tag of this report didn't
become change. I'm not sure why.

This mail is the last trial sending command tag + patch. In this time,
I attach my patch (derived from Eloston's patch), which is the same as
I posted on 8th Jan.

Takahide Nojima

On Sat, 11 Jan 2020 12:20:40 +0900 nozzy123no...@gmail.com wrote:
> tag 945920 + patch
> thanks

diff -r -N -u a/debian/control b/debian/control
--- a/debian/control	2019-12-15 03:47:43.0 +0900
+++ b/debian/control	2020-01-05 23:10:06.035727253 +0900
@@ -82,6 +82,7 @@
  libgcrypt20-dev,
  fonts-ipafont-gothic,
  fonts-ipafont-mincho,
+ libx11-xcb-dev
 
 Package: chromium
 Architecture: i386 amd64 arm64 armhf
diff -r -N -u a/debian/copyright b/debian/copyright
--- a/debian/copyright	2019-12-15 03:47:43.0 +0900
+++ b/debian/copyright	2020-01-01 20:02:46.319322326 +0900
@@ -37,7 +37,6 @@
  chrome/installer/launcher_support
  chrome/common/extensions/docs
  chrome/common/safe_browsing/rar_analyzer.*
- chrome/browser/tracing
  chrome/browser/resources/chromeos
  chrome/browser/resources/default_apps
  chrome/test/data/android
@@ -45,7 +44,6 @@
  chrome/test/data/extensions
  chrome/test/data/webui/i18n_process_css_test.html
  chrome/chrome_cleaner/test/resources/signed_dll
- services/tracing
  tools/emacs
  tools/luci-go
  tools/android
@@ -116,7 +114,6 @@
  third_party/expat/src
  third_party/*rjsmin/bench
  third_party/unrar
- third_party/perfetto
  third_party/checkstyle
  third_party/swiftshader
  third_party/apache-win32
@@ -150,23 +147,6 @@
  third_party/devtools-node-modules
  third_party/blanketjs/src/blanket.js
  third_party/accessibility-audit/axs_testing.js
- third_party/catapult/tracing
- third_party/catapult/third_party/flot
- third_party/catapult/third_party/chai
- third_party/catapult/third_party/vinn
- third_party/catapult/third_party/mocha
- third_party/catapult/third_party/coverage
- third_party/catapult/third_party/polymer2
- third_party/catapult/third_party/polymer3
- third_party/catapult/third_party/polymer/components
- third_party/catapult/third_party/d3/d3.min.js
- third_party/catapult/third_party/redux/redux.min.js
- third_party/catapult/experimental/heatmap/power.js
- third_party/catapult/experimental/heatmap/smoothness.js
- third_party/catapult/experimental/trace_on_tap/third_party/pako/pako_deflate.min.js
- third_party/catapult/third_party/gsutil
- third_party/catapult/third_party/Paste/paste/evalexception/media/MochiKit.packed.js
- third_party/catapult/telemetry/telemetry/internal/testing/perf_report_output.txt
  third_party/webrtc/sdk
  third_party/webrtc/data
  third_party/webrtc/examples
diff -r -N -u a/debian/patches/series b/debian/patches/series
--- a/debian/patches/series	2019-12-15 03:47:43.0 +0900
+++ b/debian/patches/series	2020-01-02 17:32:16.998129815 +0900
@@ -39,11 +39,9 @@
 disable/signin.patch
 disable/android.patch
 disable/fuzzers.patch
-disable/tracing.patch
 disable/openh264.patch
 disable/buildbot.patch
 disable/chromeos.patch
-disable/perfetto.patch
 disable/installer.patch
 disable/font-tests.patch
 disable/swiftshader.patch
@@ -81,3 +79,4 @@
 
 buster/icu63.patch
 buster/vpx17.patch
+system/force_system_zlib.patch
diff -r -N -u a/debian/patches/system/force_system_zlib.patch b/debian/patches/system/force_system_zlib.patch
--- a/debian/patches/system/force_system_zlib.patch	1970-01-01 09:00:00.0 +0900
+++ b/debian/patches/system/force_system_zlib.patch	2020-01-02 17:37:30.344621702 +0900
@@ -0,0 +1,11 @@
+--- a/third_party/perfetto/gn/BUILD.gn
 b/third_party/perfetto/gn/BUILD.gn
+@@ -305,7 +305,7 @@
+ "//buildtools:zlib",
+   ]
+ } else {
+-  public_configs = [ "//third_party/zlib:zlib_config" ]
++  public_configs = [ "//third_party/zlib:system_zlib" ]
+   public_deps = [
+ "//third_party/zlib",
+   ]
diff -r -N -u a/debian/rules b/debian/rules
--- a/debian/rules	2019-12-15 03:47:43.0 +0900
+++ b/debian/rules	2020-01-01 20:02:46.319322326 +0900
@@ -199,16 +199,14 @@
 	patch -p1 < debian/scripts/mk-origtargz.patch
 	date +%s > $(seconds)
 	perl debian/scripts/mk-origtargz ../$(tarball) > $(removed)
+	echo $(extract)/third_party/perfetto/ui/src/gen >> $(removed)
 	echo $$(($$(date +%s) - $$(cat $(seconds seconds
 	test ! -e $(extract) || rm -rf $(extract)
 	tar xf ../$(tarball)
 	echo $$(($$(date +%s) - $$(cat $(seconds seconds
-	while read line; do rm -rf $$line; done < $(removed)
+	xargs rm -rf < $(removed)
 	cd $(extract) && ../debian/scripts/check-upstream
-	echo $$(($$(date +%s) - $$(cat $(seconds seconds
-	test ! -e $(origtxz) || rm -f $(origtxz)
-	tar cf - $(extract) | xz -6 -T $(njobs) - > $(origtxz)
-	echo $$(($$(date +%s) - $$(cat $(seconds seconds
-	rm -rf $(extract)
 	echo $$(($$(date +%s) - $$(cat $(seconds seconds | tee seconds
 	@mv -f seconds $(seconds)
+	test ! -e $(extract)/debian || rm -rf $(extract)/debian
+	cp -r debian $(extract)/.

Bug#945920: Random Chromium crashes

[nozzy123nozzy]

tag 945920 + patch
thanks

Bug#925749: Debug build is ok

[Feng Zhao]

lgf_reader_writer_test passes when I build the program in Debug mode. However,
Release mode build will fail to run, which is the default build in packaging.

Bug#945920: Random Chromium crashes

[nozzy123nozzy]

tags 945920 + patch
thanks

Hi Maintainer,

I forgot to add tag of patch, then I added.
 
Additionally, I've been testing chromium 79.0.3945.79 which applied
Eloston's patch, it is still quite stable, no crash.

Takahide Nojima.


On Wed, 08 Jan 2020 02:28:51 +0900 nozzy123no...@gmail.com wrote:
> Hi Maintainer,
> 
>  A few days ago, I built chromium according to the way of Eloston's,
> too. But I also needed to slightly modify Eloston's patch to finish
to
> compile whole chromium source. I attached my version of the patch to
> this report.
> 
>  Until now, I'm testing this version of chromium by usual browsing,
but
> it seems to be highly stable than before! At least, it seems never to
> crash in my Debian box.
> 
>  Before Elostion's patch, in browsing some site, chromium almost
always
> crashed viewing within a few pages.
> 
>  I'm really looking forward to newer version of chromium package
> applied Eloston's patch.
> 
> Thank in advance,
> Takahide Nojima.

Bug#948632: rust-bcder: Build-depends on older rust-smallvec than is in unstable

[Steve Langasek]

Source: rust-bcder
Version: 0.4.1-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

rust-bcder build-depends on librust-smallvec-0.6+default-dev, but
rust-smallvec is now at version 1.1 in unstable:

$ sudo apt build-dep rust-bcder
Reading package lists... Done
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 builddeps:rust-bcder : Depends: librust-smallvec-0.6+default-dev (>= 
0.6.10-~~) but it is not installable
E: Unable to correct problems, you have held broken packages.
$

Please update rust-bcder for compatibility with the current
rust-smallvec.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#948631: rust-web-sys: Build-depends on older rust-wasm-bindgen-webidl than is in unstable

[Steve Langasek]

Source: rust-web-sys
Version: 0.3.28-1.1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

rust-web-sys build-depends on
librust-wasm-bindgen-webidl-0.2.51+default-dev, but rust-wasm-bindgen-webidl
is now at version 0.2.58 in unstable:

$ sudo apt build-dep rust-web-sys
Reading package lists... Done
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 builddeps:rust-web-sys : Depends: librust-failure-0.1+default-dev (>= 0.1.2-~~)
  Depends: 
librust-wasm-bindgen-webidl-0.2.51+default-dev but it is not installable
E: Unable to correct problems, you have held broken packages.
$

Please update rust-web-sys for compatibility with the current
rust-wasm-bindgen-webidl.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

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

[Debian Bug Tracking System]

Your message dated Sat, 11 Jan 2020 01:53:58 +
with message-id 
and subject line Bug#938081: fixed in python-pyo 1.0.0-2.1
has caused the Debian Bug report #938081,
regarding python-pyo: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-pyo

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

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

We believe that the bug you reported is fixed in the latest version of
python-pyo, 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 python-pyo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 10 Jan 2020 20:23:01 -0500
Source: python-pyo
Architecture: source
Version: 1.0.0-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sandro Tosi 
Closes: 938081
Changes:
 python-pyo (1.0.0-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #938081
Checksums-Sha1:
 b104b1ee80445da9b80c20628430651eea1c6631 2093 python-pyo_1.0.0-2.1.dsc
 a5d4309029beadbecac067e54a17616316a7afd6 7588 
python-pyo_1.0.0-2.1.debian.tar.xz
 1131f818459198fa76e669cb9b3a5cb9208b9ff7 6922 
python-pyo_1.0.0-2.1_source.buildinfo
Checksums-Sha256:
 93db3e661934a32abf6e814aa5b7f9f7fe856fd7434e48c3918771f9f41124c5 2093 
python-pyo_1.0.0-2.1.dsc
 9b7acb8bc030e05f8dc8095476707267fa1afcbc7b8b12163578aba19d2b3cf6 7588 
python-pyo_1.0.0-2.1.debian.tar.xz
 612438f6705dac48005c17e496c49adb5f4a1e388414128546a647d7cb45cd9a 6922 
python-pyo_1.0.0-2.1_source.buildinfo
Files:
 

Processed: python-pyo: diff for NMU version 1.0.0-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 938081 + patch
Bug #938081 [src:python-pyo] python-pyo: Python2 removal in sid/bullseye
Added tag(s) patch.

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

Bug#938081: python-pyo: diff for NMU version 1.0.0-2.1

[Sandro Tosi]

Control: tags 938081 + patch


Dear maintainer,

I've prepared an NMU for python-pyo (versioned as 1.0.0-2.1). The diff
is attached to this message.

Regards.

diff -Nru python-pyo-1.0.0/debian/changelog python-pyo-1.0.0/debian/changelog
--- python-pyo-1.0.0/debian/changelog	2019-10-05 14:58:39.0 -0400
+++ python-pyo-1.0.0/debian/changelog	2020-01-10 20:23:01.0 -0500
@@ -1,3 +1,10 @@
+python-pyo (1.0.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #938081
+
+ -- Sandro Tosi   Fri, 10 Jan 2020 20:23:01 -0500
+
 python-pyo (1.0.0-2) unstable; urgency=medium
 
   * Fix epyo script overwriting.
diff -Nru python-pyo-1.0.0/debian/control python-pyo-1.0.0/debian/control
--- python-pyo-1.0.0/debian/control	2019-10-05 13:51:19.0 -0400
+++ python-pyo-1.0.0/debian/control	2020-01-10 20:22:37.0 -0500
@@ -3,34 +3,12 @@
 Priority: optional
 Maintainer: Debian Multimedia Maintainers 
 Uploaders: Tiago Bortoletto Vaz 
-Build-Depends: debhelper (>= 10), portaudio19-dev, libportmidi-dev, liblo-dev, libsndfile1-dev, libjack-jackd2-dev, dh-python, python-all-dev, python-setuptools, python3-all-dev, python3-setuptools
+Build-Depends: debhelper (>= 10), portaudio19-dev, libportmidi-dev, liblo-dev, libsndfile1-dev, libjack-jackd2-dev, dh-python, python3-all-dev, python3-setuptools
 Standards-Version: 3.9.6
 Vcs-Browser: https://salsa.debian.org/multimedia-team/python-pyo
 Vcs-Git: https://salsa.debian.org/multimedia-team/python-pyo.git
 Homepage: http://ajaxsoundstudio.com/software/pyo/
 
-Package: python-pyo
-Architecture: any
-Depends: python (>= 2.6), ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}
-Recommends: python-tk, python-imaging-tk, python-wxgtk3.0, jackd2
-Description: Python module written in C to help digital signal processing script creation
- pyo is a Python module containing classes for a wide variety of audio signal
- processing types. With pyo, user will be able to include signal processing
- chains directly in Python scripts or projects, and to manipulate them in real
- time through the interpreter. Tools in pyo module offer primitives, like
- mathematical operations on audio signal, basic signal processing (filters,
- delays, synthesis generators, etc.), but also complex algorithms to create
- sound granulation and others creative audio manipulations.
- .
- pyo supports OSC protocol (Open Sound Control), to ease communications between
- softwares, and MIDI protocol, for generating sound events and controlling
- process parameters.
- .
- pyo allows creation of sophisticated signal processing chains with all the
- benefits of a mature, and wildly used, general programming language.
- .
- This package installs the library for Python 2.
-
 Package: python3-pyo
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}
diff -Nru python-pyo-1.0.0/debian/python3-pyo.install python-pyo-1.0.0/debian/python3-pyo.install
--- python-pyo-1.0.0/debian/python3-pyo.install	2019-10-05 13:49:41.0 -0400
+++ python-pyo-1.0.0/debian/python3-pyo.install	1969-12-31 19:00:00.0 -0500
@@ -1,3 +0,0 @@
-debian/epyo3  usr/bin
-debian/E-Pyo-py3.desktop  usr/share/applications
-debian/E-Pyo-py3.xpm  usr/share/pixmaps
diff -Nru python-pyo-1.0.0/debian/python-pyo.install python-pyo-1.0.0/debian/python-pyo.install
--- python-pyo-1.0.0/debian/python-pyo.install	2019-10-05 13:47:31.0 -0400
+++ python-pyo-1.0.0/debian/python-pyo.install	1969-12-31 19:00:00.0 -0500
@@ -1,3 +0,0 @@
-debian/epyo2 usr/bin
-debian/E-Pyo-py2.desktop  usr/share/applications
-debian/E-Pyo-py2.xpm  usr/share/pixmaps
diff -Nru python-pyo-1.0.0/debian/rules python-pyo-1.0.0/debian/rules
--- python-pyo-1.0.0/debian/rules	2019-10-05 14:47:11.0 -0400
+++ python-pyo-1.0.0/debian/rules	2020-01-10 20:22:45.0 -0500
@@ -3,7 +3,7 @@
 export PYBUILD_NAME=pyo
 
 %:
-	dh $@ --with python2,python3 --buildsystem=pybuild
+	dh $@ --with python3 --buildsystem=pybuild
 
 #override_dh_auto_build:
 #	set -e; \

Bug#874880: FreeMedForms projet

[Michael Lustfield]

It looks like this bug went from "Qt4->Qt5" to "no longer DFSG-free."

On Fri, 10 Jan 2020 17:34:35 +0100
Eric Maeker  wrote:

> Oh! There is a misunderstanding here!
> Let me correct my words:
> -> full code of each stable released version is packaged and freely  
> available (but undocumented since v1.0.0).

From: https://freemedforms.com/en/downloads/root

"Downloads are 100% compatible with the Debian social contract."

From: https://freemedforms.com/fr/downloads/root (translated)

"Since v1.1.0, some files are available under a license incompatible with
the social contract of Debian . If you are looking for software 100%
compatible with this contract, please refer to v1.0.0."

Without digging in too deep...
- You mentioned documentation removal in 1.0.0
- This page mentions DFSG-freeness was broken in 1.1.0

If these were two distinct periods of time, that would lead me to suspect
additional files were added that broke compatibility with the DFSG.

> We know that at least two forks exists (this is what our private data
> server's log tells us). We do not receive any patch, invitation to git
> repos, or any kind of official informations or queries.

This could definitely be a language barrier problem, but I don't follow. Why
are you concerned about forks? If you have quality open source software, then
people will fork it. Sometimes patches will be sent back upstream, other times
they won't be.

Take a look here: https://people.debian.org/~bap/dfsg-faq.html
Particularly at 9a (The Desert Island Test)

Demanding that all modifications be shared with you very clearly fails this
test, and is not actually part of the license you applied to the software.

> In consequence, we decide that our git repository will not be freely
> accessible. Approval does only concern the FreeMedForms' git and the
> ability to join the project as member (coder, tester, communication
> manager...).

It's probably worth noting, a public repository is recommended, but not
required for inclusion in Debian repositories. However, inclusion of source is
an absolute requirement.

This "documentation" that was removed seems to be much more than just developer
docs; I'm unable to find any non-header comments in any file.

If you look at how javascript is handled, any minified version is considered
compiled source. You are essentially doing the exact same to your source when
you release it. It's not the actual source... it's just some partial version of
it. In this case, with intentional obfuscation.



This could still make it into non-free, however, I'd urge you to reconsider
your motivations for releasing obfuscated source and refusing to share. Is it
really your desire to make software that's (per DFSG) not free?


-- 
Michael Lustfield

Bug#948630: rust-grcov: Build-depends on older rust-crossbeam than is in unstable

[Steve Langasek]

Source: rust-grcov
Version: 0.4.1-2
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

As seen at https://buildd.debian.org/status/package.php?p=rust%2dgrcov,
rust-grcov 0.4.1-2 is not built on any architectures, because it
build-depends on librust-crossbeam-0.4+default-dev but rust-crossbeam in
unstable is now at version 0.7.

Please update rust-grcov for compatibility with the current rust-crossbeam.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#924310: xrdp: post-install script fails

[Thorsten Glaser]

Hi,

it says “A dependency job for xrdp.service failed.” so I believe that
some *other* service xrdp.service depends on had failed earlier and
so your system is in a weird state, maybe?

bye,
//mirabilos
-- 
15:39⎜«mika:#grml» mira|AO: "mit XFree86® wär’ das nicht passiert" - muhaha
15:48⎜ also warum machen die xorg Jungs eigentlich alles
kaputt? :)15:49⎜ thkoehler: weil sie als Kinder nie den
gebauten Turm selber umschmeissen durften?  -- ~/.Xmodmap wonders…

Bug#947373: marked as done (python3-guestfs: missing Breaks+Replaces: python-guestfs)

[Debian Bug Tracking System]

Your message dated Sat, 11 Jan 2020 00:34:54 +
with message-id 
and subject line Bug#947373: fixed in libguestfs 1:1.40.2-5
has caused the Debian Bug report #947373,
regarding python3-guestfs: missing Breaks+Replaces: python-guestfs
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.)


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

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Preparing to unpack .../python3-guestfs_1%3a1.40.2-4_amd64.deb ...
  Unpacking python3-guestfs (1:1.40.2-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-guestfs_1%3a1.40.2-4_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/ja/man3/guestfs-python.3.gz', which is 
also in package python-guestfs 1:1.40.2-2+b12
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-guestfs_1%3a1.40.2-4_amd64.deb


cheers,

Andreas


python-guestfs=1:1.40.2-2+b12_python3-guestfs=1:1.40.2-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libguestfs
Source-Version: 1:1.40.2-5

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 11 Jan 2020 01:13:06 +0100
Source: libguestfs
Architecture: source
Version: 1:1.40.2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Libvirt Maintainers 

Changed-By: Hilko Bengen 
Closes: 947373 948017
Changes:
 libguestfs (1:1.40.2-5) unstable; urgency=medium
 .
   * Add missing slash to debian/clean
   * Add missing Breaks/Replaces for python3-guestfs (Closes: #947373)
   * Add/bump build dependencies for virt-v2v
   * Patch build system to ensure that Python 3.8+ modules are built (Closes: 
#948017)
   * Attempt to fix FTBFS issues by updating handling of autogenerated OCaml 
config files
Checksums-Sha1:
 8b5638cea789f5dfef139961aa605a64ea7006f7 5990 libguestfs_1.40.2-5.dsc
 dd0f69259a1a402dd847c7e50041bbd2048dcd1e 35456 
libguestfs_1.40.2-5.debian.tar.xz
 c75d9c1834c0499dab7745683d9b03a439c33cfd 24339 
libguestfs_1.40.2-5_source.buildinfo
Checksums-Sha256:
 b9a3667a486603af6ef2ce961b19bbca045c83fdb3325c6f35aa98887a8f7202 5990 
libguestfs_1.40.2-5.dsc
 d960398198c7d5a0f502c0b0847b912d16cd9619b831de2265b66b21b285107b 35456 
libguestfs_1.40.2-5.debian.tar.xz
 92bed28a7e3c1dc343c8bb507826e0644c01f7e7131c8d7197daf09e26d1d008 24339 
libguestfs_1.40.2-5_source.buildinfo
Files:
 a516a4767371efe08145cac50d3c407e 5990 libs optional libguestfs_1.40.2-5.dsc
 39b666ace28e53b1043810fb6a50885e 35456 libs optional 
libguestfs_1.40.2-5.debian.tar.xz
 aaf707c20fe3526c0fb1602d7a4cb23c 24339 libs optional 
libguestfs_1.40.2-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAl4ZE28ACgkQdbcQY1wh
On4g/w//XV8OClh6KYcpIU/AQimOzBwgTXSxzT8GtZEN/hZjuTvylbXbxuUjrjBe
ePGcBxBfJH2wfRQHC4W7uSwd/+OgGcEToK3G5LzC8rAkTpmuEjpux34mXFVthX6k
8olNl+TRONsuNa4OkGWQG0tqvJUlq86QMrQbiBYwnvLv9CLdA1E5BDkn3wsOlAQ0
WimLk4+CTthh3OdEbsdbyXL5EAK0QsbQ4vsS6OqbgDYQJ2tFu9+w2Nd7Tzz2VCEI
oLhWasWT/OGaRqQPRn5O7y+eE5Fpadiw8K2BsoSLcyj6W61Vjkkwt+d+EysIxmUJ
sOGuu1m2f9Toe+TfAp8L5eI90x6mlgpi8fUoqB35UFrtx7Yadm1opQCjImhkTVD6
V8UYlLkbiOXT8c6kleB2EKOeNh0uMWQov1QR6utYxnwvRshQDgij9YanddAxChtP
/iIafVNTi8AygObXcZxTWkMXKZl2cKk/rnYb5H6YApk4WICW7DNPxX+zwutvMAIu
+rRSj8IjZp1bTiXwX3Vov8JG2zdq8CAs8Hj+U4dTcPGyYl9V65wfYbhaVxz9V1As

Bug#948627: xwayland: Double pointer and application freeze if I use lenovo pen

[Teo]

Package: xwayland
Version: 2:1.20.6-1
Severity: grave
Tags: upstream
Justification: renders package unusable

I am using a lenovo yoga 520 equipped with a lenovo pen. When I use the latter,
two pointers are created, the first is stopped in the last position that I gave
it from the touchpad, while the second, follows the pen. So far nothing
serious. Except that after a while everything becomes unusable, because single
touches with the pen are detected as a hold (as if the left touchpad button was
held down), then start dragging application icons here and there, until it
doesn't even respond plus the touches, as if it were all freeze. I can't even
anymore restart it normally and I am forced to restart forcefully. I am on
Debian testing, but on the stable branch I had the same problem. I confirm that
everything works properly on xorg, I don't even know the double pointer
problem.



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

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

Versions of packages xwayland depends on:
ii  libaudit1   1:2.8.5-2+b1
ii  libbsd0 0.10.0-1
ii  libc6   2.29-7
ii  libdrm2 2.4.100-4
ii  libepoxy0   1.5.4-1
ii  libgbm1 19.2.6-1
ii  libgcrypt20 1.8.5-3
ii  libgl1  1.1.0-1+b1
ii  libpixman-1-0   0.36.0-1
ii  libselinux1 3.0-1
ii  libsystemd0 244-3
ii  libunwind8  1.2.1-9
ii  libwayland-client0  1.17.0-1
ii  libxau6 1:1.0.8-1+b2
ii  libxdmcp6   1:1.1.2-3
ii  libxfont2   1:2.0.3-1
ii  libxshmfence1   1.3-1
ii  xserver-common  2:1.20.6-1

xwayland recommends no packages.

xwayland suggests no packages.

-- no debconf information

Processed: Bug is also in stretch

[Debian Bug Tracking System]

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

> unarchive 907008
Bug #907008 {Done: Daniel Kahn Gillmor } 
[src:mod-gnutls] mod-gnutls FTBFS: FAIL: test-16_view-status.bash
Unarchived Bug 907008
> found 907008 0.8.2-3
Bug #907008 {Done: Daniel Kahn Gillmor } 
[src:mod-gnutls] mod-gnutls FTBFS: FAIL: test-16_view-status.bash
Marked as found in versions mod-gnutls/0.8.2-3.
> thanks
Stopping processing here.

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

Bug#936924: Moving libsvm to Debian Science team

[Christian Kastner]

Hi all,

On 10.01.20 15:33, Chen-Tse Tsai wrote:
> Yes, my changes are merged.

I checked the package and everything looks pretty good. I just added
some minor polishing of my own.

Very surprisingly, not a single symbol has changed since 3.21 -- no
additions, no removals, no changes. It looks as we will be spared a
transition!

@Andreas: I can't push my changes to master, I get a protected branch
error. Could you please grant me the necessary privileges?

> I won't be able to work on it in the next few days. Thanks for your
> help! If you want, it would be great to add you as an Uploader since you
> know these packages really well.

Done!

There's a lintian info about a missing JAR, but I suspect that has more
to do with the symlink from libsvm-java pointing to libsvm3-java.

I added a simple autopkgtest and it passed. Seeing as the symbols didn't
change a bit, I can see no reason why this couldn't be uploaded as-is,
but I'm tired and I'd like to check it again tomorrow with a fresh pair
of eyes, lest we break something.

Christian

Processed: unarchiving 909216

[Debian Bug Tracking System]

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

> unarchive 909216
Bug #909216 {Done: Emmanuel Bourg } [src:libjaxen-java] 
libjaxen-java FTBFS: java.lang.IllegalArgumentException: Illegal character in 
local name: 'pre:foo'
Bug #934032 {Done: Emmanuel Bourg } [src:libjaxen-java] 
libjaxen-java: FTBFS in stretch (failing tests, IllegalArgumentException)
Unarchived Bug 909216
Unarchived Bug 934032
> thanks
Stopping processing here.

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

Bug#936535: flup: Python2 removal in sid/bullseye

[Emmanuel Arias]

Hi,

The last upstream release version was on 2009 [1]. Seems to be not longer
supported.

And there is not python3 version.

I believe that should be use the forks mentioned on:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873492

[1] https://www.saddi.com/software/flup/dist/ChangeLog


Cheers,
Arias Emmanuel
@eamanu
yaerobi.com

Processed: Also in stretch

[Debian Bug Tracking System]

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

> unarchive 924650
Bug #924650 {Done: Tobias Frost } [src:epsilon] epsilon ftbfs 
and fails autopkg tests on the buster kernel
Unarchived Bug 924650
> tags 924650 stretch
Bug #924650 {Done: Tobias Frost } [src:epsilon] epsilon ftbfs 
and fails autopkg tests on the buster kernel
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: py2removal bugs severity updates - 2020-01-10 21:35:55.600438+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
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # python-flup is a module and has 0 external rdeps or not in testing
> severity 936535 serious
Bug #936535 [src:flup] flup: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-cherrypy is a module and has 0 external rdeps or not in testing
> severity 937644 serious
Bug #937644 [src:python-cherrypy] python-cherrypy: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> # python-pyo is a module and has 0 external rdeps or not in testing
> severity 938081 serious
Bug #938081 [src:python-pyo] python-pyo: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-simpletal is a module and has 0 external rdeps or not in testing
> severity 938485 serious
Bug #938485 [src:simpletal] simpletal: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#937166: nuitka: Python2 removal in sid/bullseye

[Scott Kitterman]

On Fri, 30 Aug 2019 07:28:47 + Matthias Klose  wrote:
> Package: src:nuitka
> Version: 0.6.1.1+ds-1

I emailed the maintainer and an upload switching the package to python3 is 
expected this month (waiting on python3.8 compatibility from upstream).

Scott K

Bug#948613: wcc: autopkgtests try to dlopen PIE executables

[Aurelien Jarno]

Package: wcc
Version: 0.0.2+dfsg-3
Severity: serious

Dear wcc maintainers,

The wcc autopkgtests try to dlopen some PIE executables (namely
/usr/bin/ssh). This has never been really supported, and this fails with
an error message in recent glibc versions. This cause the autopkgtest to
fail:

| autopkgtest [11:11:14]: test command1: ./debian/tests/wsh-ssl.wsh /usr/bin/ssh
| autopkgtest [11:11:14]: test command1: [---
| ERROR: dlopen() /usr/bin/ssh: cannot dynamically load position-independent 
executable 
| ERROR: dlopen() of patched file! //tmp/.wsh-1902/ssh: cannot dynamically load 
position-independent executable 
| WARNING: No binary loaded in memory. Try loadbin(). For help type 
help("loadbin").
| lua_pcall() failed with ./debian/tests/wsh-ssl.wsh:6: attempt to call a nil 
value (global 'MD5_Init'), for: ./debian/tests/wsh-ssl.wsh
| init
|  ** libifying /usr/bin/ssh to //tmp/.wsh-1902/ssh (760616 bytes)
| -- input: my best friend is a little poney !
| -- md5 hexdump
| autopkgtest [11:11:15]: test command1: ---]
| autopkgtest [11:11:15]: test command1:  - - - - - - - - - - results - - - - - 
- - - - -
| command1 FAIL non-zero exit status 42

(see https://ci.debian.net/data/autopkgtest/testing/amd64/w/wcc/3942223/log.gz)

You can see reason for disabling dlopening PIE binaries in this upstream
bug report:
https://sourceware.org/bugzilla/show_bug.cgi?id=24323

It is unclear to me what this change means for the wcc testsuite and for
the usability of the wcc package. Could you please explain me how is it
used?

Thanks,
Aurelien

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

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

Versions of packages wcc depends on:
ii  libbinutils   2.33.1-6
ii  libc6 2.29-7
ii  libcapstone3  4.0.1+really+3.0.5-1+b1
ii  libelf1   0.176-1.1
ii  liblua5.3-0   5.3.3-1.1+b1

wcc recommends no packages.

Versions of packages wcc suggests:
pn  lua  

Processed: Re: from PIL import Image ModuleNotFoundError No module named PIL

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #947032 {Done: Julien Puydt } [mnemosyne] from PIL 
import Image ModuleNotFoundError No module named PIL
Added tag(s) pending.

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

Processed: Re: Bug#948610: mercurial: calls python instead of python2

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #948610 [src:mercurial] mercurial: calls python instead of python2
Severity set to 'wishlist' from 'serious'

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

Bug#948610: mercurial: calls python instead of python2

[Julien Cristau]

Control: severity -1 wishlist

On Fri, Jan 10, 2020 at 08:54:07PM +0100, Gianfranco Costamagna wrote:
> Severity: serious

Why?

Cheers,
Julien

Bug#947032: from PIL import Image ModuleNotFoundError No module named PIL

[Andreas Beckmann]

Followup-For: Bug #947032
Control: tag -1 pending

buster-pu request: https://bugs.debian.org/948609


Andreas

Bug#948610: mercurial: calls python instead of python2

[Gianfranco Costamagna]

Source: mercurial
Version: 5.2.2-1
Severity: serious
tags: patch

Hello, the following patch should make the package compile with python binary 
removed from the system:

--- mercurial-5.2.2/debian/rules2020-01-10 08:14:46.0 +
+++ mercurial-5.2.2/debian/rules2020-01-10 08:14:48.0 +
@@ -7,6 +7,7 @@
 %:
dh $@ --with python2,bash-completion
 
+export PYTHON=python2
 PYVERS=$(shell pyversions -vs)
 PYVER_DEFAULT=$(shell pyversions -vd)
 DEB_HOST_ARCH := $(shell dpkg-architecture -qDEB_HOST_ARCH)
@@ -46,7 +46,7 @@
http_proxy='' dh_auto_test -- TESTFLAGS="--verbose --timeout 1440 
$(PARALLEL_TEST_JOBS) --blacklist $(CURDIR)/debian/mercurial.test_blacklist"
file-rename 's/\.deb-backup$$//' $(CURDIR)/tests/*
# run blacklisted tests but ignore their results
-   -cd tests && python run-tests.py --verbose `grep ^test 
../debian/mercurial.test_blacklist`
+   -cd tests && python2 run-tests.py --verbose `grep ^test 
../debian/mercurial.test_blacklist`
 endif
 
 override_dh_auto_install: $(PYVERS:%=install-python%)

thanks for considering it

Gianfranco

Bug#936238: marked as done (brial: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 10 Jan 2020 19:34:07 +
with message-id 
and subject line Bug#936238: fixed in brial 1.2.5-2.1
has caused the Debian Bug report #936238,
regarding brial: 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.)


-- 
936238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:brial
Version: 1.2.4-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:brial

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: brial
Source-Version: 1.2.5-2.1

We believe that the bug you reported is fixed in the latest version of
brial, 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 brial package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 10 Jan 2020 14:06:12 -0500
Source: brial
Architecture: source
Version: 1.2.5-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Sandro Tosi 
Closes: 936238
Changes:
 brial (1.2.5-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #936238
Checksums-Sha1:
 298d13863acff0233c0c82796212cffe8f58de22 2349 brial_1.2.5-2.1.dsc
 d3942e59cf67f03bfd52137af794c6e8498fe26a 6604 brial_1.2.5-2.1.debian.tar.xz
 81657a7811c157942d8c40c46b0602fd310e3a82 8551 brial_1.2.5-2.1_source.buildinfo
Checksums-Sha256:
 fb7c3bfa885980e1d7a32e2969601ebb68a69a166e64fe9f69d72ac55d46af04 2349 
brial_1.2.5-2.1.dsc
 cbfb1008c850218f624f280c1b256867a741af3314b4e6b61cb1597a11c7393d 6604 
brial_1.2.5-2.1.debian.tar.xz
 d13ad4179da6085fe3af1550ab9b8389993cfb5403009fe56f10f71fa3d60581 8551 
brial_1.2.5-2.1_source.buildinfo
Files:
 d3022abf932bdfc18fe6db47bc9f1450 2349 math optional brial_1.2.5-2.1.dsc
 

Processed: brial: diff for NMU version 1.2.5-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 936238 + patch
Bug #936238 [src:brial] brial: Python2 removal in sid/bullseye
Added tag(s) patch.

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

Bug#936238: brial: diff for NMU version 1.2.5-2.1

[Sandro Tosi]

Control: tags 936238 + patch


Dear maintainer,

I've prepared an NMU for brial (versioned as 1.2.5-2.1). The diff
is attached to this message.

Regards.

diff -Nru brial-1.2.5/debian/changelog brial-1.2.5/debian/changelog
--- brial-1.2.5/debian/changelog	2019-11-10 15:15:02.0 -0500
+++ brial-1.2.5/debian/changelog	2020-01-10 14:06:12.0 -0500
@@ -1,3 +1,10 @@
+brial (1.2.5-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #936238
+
+ -- Sandro Tosi   Fri, 10 Jan 2020 14:06:12 -0500
+
 brial (1.2.5-2) unstable; urgency=medium
 
   * Rebuild with gcc-9 (required to fix segfaults in sagemath).
diff -Nru brial-1.2.5/debian/control brial-1.2.5/debian/control
--- brial-1.2.5/debian/control	2019-11-10 15:14:55.0 -0500
+++ brial-1.2.5/debian/control	2020-01-10 14:05:50.0 -0500
@@ -10,7 +10,6 @@
libboost-python-dev,
libboost-test-dev,
libm4ri-dev (>= 20120613),
-   python-all-dev,
python3-all-dev,
libgd-dev,
libjpeg-dev,
@@ -21,30 +20,6 @@
 Vcs-Browser: https://salsa.debian.org/science-team/brial
 Homepage: https://github.com/BRiAl
 
-Package: python-brial
-Architecture: any
-Section: python
-Replaces: python-polybori (<< 0.8.5)
-Breaks: python-polybori (<< 0.8.5), sagemath (<< 8.1~)
-Depends: ${shlibs:Depends},
- ${misc:Depends},
- libbrial3 (= ${binary:Version}),
- libbrial-groebner3 (= ${binary:Version}),
- ${python:Depends}
-Description: polynomials over Boolean Rings, Python 2 module
- The core of BRiAl is a C++ library, which provides high-level data
- types for Boolean polynomials and monomials, exponent vectors, as
- well as for the underlying polynomial rings and subsets of the
- powerset of the Boolean variables. As a unique approach, binary
- decision diagrams are used as internal storage type for polynomial
- structures. On top of this C++-library a Python interface
- is provided. This allows parsing of complex polynomial systems, as well
- as sophisticated and extendable strategies for Groebner base
- computation. BRiAl features a powerful reference implementation
- for Groebner basis computation.
- .
- This package contains the BRiAl Python 2 module.
-
 Package: python3-brial
 Architecture: any
 Section: python
diff -Nru brial-1.2.5/debian/python-brial.install brial-1.2.5/debian/python-brial.install
--- brial-1.2.5/debian/python-brial.install	2019-09-01 04:03:40.0 -0400
+++ brial-1.2.5/debian/python-brial.install	1969-12-31 19:00:00.0 -0500
@@ -1,2 +0,0 @@
-usr/lib/python2.*/
-
diff -Nru brial-1.2.5/debian/rules brial-1.2.5/debian/rules
--- brial-1.2.5/debian/rules	2019-09-01 04:03:40.0 -0400
+++ brial-1.2.5/debian/rules	2020-01-10 14:06:05.0 -0500
@@ -5,7 +5,7 @@
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
 
 %:
-	dh $@ --with python2,python3
+	dh $@ --with python3
 
 override_dh_auto_build:
 	dh_auto_build

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

[Debian Bug Tracking System]

Your message dated Fri, 10 Jan 2020 19:19:59 +
with message-id 
and subject line Bug#937620: fixed in python-bottle 0.12.15-2.1
has caused the Debian Bug report #937620,
regarding python-bottle: 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.)


-- 
937620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-bottle
Version: 0.12.15-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:python-bottle

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

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

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-bottle package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 10 Jan 2020 13:51:29 -0500
Source: python-bottle
Architecture: source
Version: 0.12.15-2.1
Distribution: unstable
Urgency: medium
Maintainer: Federico Ceratto 
Changed-By: Sandro Tosi 
Closes: 937620
Changes:
 python-bottle (0.12.15-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #937620
Checksums-Sha1:
 6b61b4463958cb5998887519e86065057532667d 2262 python-bottle_0.12.15-2.1.dsc
 239c84f8fefa736899306693e0ec2c494fb6eb83 6096 
python-bottle_0.12.15-2.1.debian.tar.xz
 7f1d6fe8152add78b147afe9bbde60fc077df89b 5673 
python-bottle_0.12.15-2.1_source.buildinfo
Checksums-Sha256:
 607aa560330e4bedbdca576a912ac42ff1c6a271e07fba0f6f649ef6465ec51f 2262 
python-bottle_0.12.15-2.1.dsc
 63fb14c4ec0aae4afa9a42930256d8d699c1dc3defe5dee9d83ea46e9676d862 6096 
python-bottle_0.12.15-2.1.debian.tar.xz
 fa2209a60443219d7a135011e17a72e5a54412238dd8ccd2f7cb41cb1654690f 5673 

Bug#946829: Patch works!

[Magnus Holmgren]

torsdag 19 december 2019 kl. 11:41:21 CET skrev du:
> I can confirm that patch works as expected.
> 
> Patch does not apply cleanly on my SA (3.4.2-1~deb9u2) but only for
> cosmetic differences, attached a patch that wok on SA 3.4.2-1~deb9u2.
> 
> 
> Thanks!

I came up with the following RE loop to parse the options string. It should 
allow a few more things that admins might potentially be using, like non-
integer values (for dontgreylistthreshold), while barfing on bad syntax.

while ($optionhash =~ /(?:\G(?(?['"])(?.*?)
\g{quot1})
   \s*=>\s*
   (?>(?['"])(?.*?)\g{quot2}
  |
  (?-?(?:\d+(?:\.\d*)?|(?:\d*\.)?\d+))
   )\s*(?:;?\s*\)\s*$|;(?!$))/gxc) {
$option{$+{opt}} = $+{val};
}
if ((pos($optionhash) // 0) < length $optionhash) {
die "Syntax error";
}

I just need to add the variable untainting.

-- 
Magnus Holmgrenholmg...@debian.org
Debian Developer 

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

Bug#937620: python-bottle: diff for NMU version 0.12.15-2.1

[Sandro Tosi]

Control: tags 937620 + patch


Dear maintainer,

I've prepared an NMU for python-bottle (versioned as 0.12.15-2.1). The diff
is attached to this message.

please consider maintaining this package in the DPMT team

Regards.

diff -Nru python-bottle-0.12.15/debian/changelog python-bottle-0.12.15/debian/changelog
--- python-bottle-0.12.15/debian/changelog	2019-03-26 19:43:08.0 -0400
+++ python-bottle-0.12.15/debian/changelog	2020-01-10 13:51:29.0 -0500
@@ -1,3 +1,10 @@
+python-bottle (0.12.15-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #937620
+
+ -- Sandro Tosi   Fri, 10 Jan 2020 13:51:29 -0500
+
 python-bottle (0.12.15-2) unstable; urgency=medium
 
   * Update tox dependency (Closes: #924836)
diff -Nru python-bottle-0.12.15/debian/control python-bottle-0.12.15/debian/control
--- python-bottle-0.12.15/debian/control	2019-03-26 19:43:08.0 -0400
+++ python-bottle-0.12.15/debian/control	2020-01-10 13:51:18.0 -0500
@@ -4,26 +4,24 @@
 Maintainer: Federico Ceratto 
 Build-Depends: debhelper (>= 11~)
 Build-Depends-Indep:
- python-all (>= 2.6.6-3~)
- , python3-all
- , python-doc
+ python3-all
+ , python3-doc
  , dh-python
- , python-sphinx
- , python-setuptools
+ , python3-sphinx
  , python3-setuptools
 # needed for build-time tests
- , python-cherrypy
- , python-eventlet
- , python-flup
- , python-gevent
- , python-jinja2
- , python-mako
- , python-paste
- , python-simpletal
- , python-tornado
+ , python3-cherrypy3
+ , python3-eventlet
+# , python3-flup #py3k version not packaged yet
+ , python3-gevent
+ , python3-jinja2
+ , python3-mako
+ , python3-paste
+ , python3-simpletal
+ , python3-tornado
  , tox
- , python-twisted
- , python-werkzeug
+ , python3-twisted
+ , python3-werkzeug
  , gunicorn
 Standards-Version: 4.2.1
 Homepage: http://bottlepy.org
@@ -31,18 +29,6 @@
 Vcs-Browser: https://salsa.debian.org/debian/python-bottle
 Testsuite: autopkgtest-pkg-python
 
-Package: python-bottle
-Architecture: all
-Depends:
- ${python:Depends}
- , ${misc:Depends}
-Provides: ${python:Provides}
-Description: fast and simple WSGI-framework for Python
- Bottle is a fast and simple WSGI-framework for the Python programming
- language. It offers request dispatching with url parameter support
- (routes), templates, key/value databases, a built-in HTTP server and
- adapters for many third party WSGI/HTTP-server and template engines.
-
 Package: python3-bottle
 Architecture: all
 Depends:
diff -Nru python-bottle-0.12.15/debian/rules python-bottle-0.12.15/debian/rules
--- python-bottle-0.12.15/debian/rules	2019-03-26 19:43:08.0 -0400
+++ python-bottle-0.12.15/debian/rules	2020-01-10 13:51:29.0 -0500
@@ -5,12 +5,12 @@
 export PYBUILD_NAME=bottle
 
 %:
-	dh $@ --with python2,python3,sphinxdoc --buildsystem=pybuild --test-tox
+	dh $@ --with python3,sphinxdoc --buildsystem=pybuild --test-tox
 
 override_dh_auto_build:
 	dh_auto_build
-	PYTHONPATH=. http_proxy='http://127.0.0.1:9/' sphinx-build -N -E -bhtml docs build/html
-	PYTHONPATH=. http_proxy='http://127.0.0.1:9/' sphinx-build -N -E -bman docs build/man
+	PYTHONPATH=. http_proxy='http://127.0.0.1:9/' python3 -m sphinx -N -E -bhtml docs build/html
+	PYTHONPATH=. http_proxy='http://127.0.0.1:9/' python3 -m sphinx -N -E -bman docs build/man
 	rm -rf ./build/html/.doctrees
 
 override_dh_sphinxdoc:
@@ -25,5 +25,6 @@
 ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS)))
 	# Run only "fast" tests, see #834918 and
 	# https://github.com/bottlepy/bottle/commit/9752ca1bd464371db0217a0681cd67d9a7a8dcda
-	python test/testall.py fast
+	# skip tests for now
+	#PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{interpreter} test/testall.py fast" dh_auto_test
 endif

Processed: python-bottle: diff for NMU version 0.12.15-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 937620 + patch
Bug #937620 [src:python-bottle] python-bottle: Python2 removal in sid/bullseye
Added tag(s) patch.

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

Bug#942760: marked as done (tesseract-ocr: Needs newer libtesseract4)

[Debian Bug Tracking System]

Your message dated Fri, 10 Jan 2020 18:37:33 +
with message-id 
and subject line Bug#942760: fixed in tesseract 4.1.1-1
has caused the Debian Bug report #942760,
regarding tesseract-ocr: Needs newer libtesseract4
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.)


-- 
942760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tesseract-ocr
Version: 4.1.0-2
Severity: grave
Justification: renders package unusable

tesseract-ocr 4.1.0-2 depends on libtesseract4 >= 4.0.0.

However, invokation fails with libtesseract4 4.0.0:

tesseract: symbol lookup error: tesseract: undefined symbol:
_ZN9tesseract10SIMDDetect15avx2_available_E

After upgrading libtesseract4 to 4.1.0-2, it works for me.



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

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

Versions of packages tesseract-ocr depends on:
ii  libc62.29-2
ii  libcairo21.16.0-4
ii  libfontconfig1   2.13.1-2+b1
ii  libgcc1  1:9.2.1-8
ii  libglib2.0-0 2.62.1-1
ii  libicu63 63.2-2
ii  liblept5 1.76.0-1
ii  libpango-1.0-0   1.42.4-7
ii  libpangocairo-1.0-0  1.42.4-7
ii  libpangoft2-1.0-01.42.4-7
ii  libstdc++6   9.2.1-8
ii  libtesseract44.0.0-2
ii  tesseract-ocr-eng1:4.00~git30-7274cfa-1
ii  tesseract-ocr-osd1:4.00~git30-7274cfa-1

tesseract-ocr recommends no packages.

tesseract-ocr suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: tesseract
Source-Version: 4.1.1-1

We believe that the bug you reported is fixed in the latest version of
tesseract, 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 Pozdnyakov  (supplier of updated tesseract package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 10 Jan 2020 19:36:23 +0300
Source: tesseract
Architecture: source
Version: 4.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Alexander Pozdnyakov 
Changed-By: Alexander Pozdnyakov 
Closes: 942760
Changes:
 tesseract (4.1.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * Update debian/control:
 - delete build dependency from autoconf-archive
 - add build dependency on libarchive-dev
 - update dependency libtesseract4 for tesseract-ocr (closes: #942760)
   * Bump Standards-Version to 4.4.1
   * URL: git://github.com/tesseract-ocr/tesseract.git
   * Branch: 4.1
   * Commit: f4ef2f2050f4c25b28bdbf0063b7d2eb30f41cf7
   * Date: 1577374826
   * git changelog:
   *  f4ef2f20 - 4.1.1 Release
   *  01fb4c7f - BlockPolygon: clip to image rectangle
   *  36664031 - BlockPolygon: unrotate from internal to image
 coordinates
   *  0ab9839a - Use /W4 instead of /Wall for MSVC (fix issue #2816)
   *  6343f0ab - Added ComposedBlock level to Alto output
   *  42ec3137 - ignore qtcreator help files
   *  88174fea - backport changes pagesegmode_test.cc from master
   *  7389a275 - Provide more details for successful running of
 unittests.
   *  9d967cb1 - unittest: Fix build and simplify build rules
   *  69cbda61 - unittest: Initialize non-static class members in
 RecodeBeamTest (CID 1402765)
   *  85477214 - unittest: Fix two issues reported by Coverity Scan (CID
 1402761, 1402755)
   *  bdad0686 - unittest: Add missing precision specifiers (CID 1402752)
   *  95733433 - unittest: Don't build tatweel_test when TensorFlow is
 disabled
   *  2b04ff76 - unittest: Add missing libraries to fix linker errors
   *  16b1e5d2 - Update test submodule and fix pagesegmode_test
   *  50a41b63 - Update test submodule and fix tatweel_test
   *  

Processed: Re: fails to start because no wrapper missing

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #940611 {Done: Andreas Tille } [beagle] fails to start 
because no wrapper missing
Added tag(s) pending.

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

Bug#940611: fails to start because no wrapper missing

[Andreas Beckmann]

Followup-For: Bug #940611
Control: tag -1 pending

buster-pu request: https://bugs.debian.org/948601


Andreas

Processed: found 918163 in 0.3.0+dfsg-1

[Debian Bug Tracking System]

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

> found 918163 0.3.0+dfsg-1
Bug #918163 [xul-ext-sieve] Broken in Stretch
Marked as found in versions sieve-extension/0.3.0+dfsg-1; no longer marked as 
fixed in versions sieve-extension/0.3.0+dfsg-1.
> thanks
Stopping processing here.

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

Bug#948602: openturns-examples has a hard-coded dependency on python

[Matthias Klose]

Package: openturns-examples
Version: 1.14-1
Severity: serious
Tags: sid bullseye

openturns-examples has a hard-coded dependency on python, after the conversion
to Python3.

Bug#947514: marked as done (midori: build-depends on obsolete libunique-dev)

[Debian Bug Tracking System]

Your message dated Fri, 10 Jan 2020 17:39:27 +
with message-id 
and subject line Bug#947514: fixed in midori 7.0-2.1
has caused the Debian Bug report #947514,
regarding midori: build-depends on obsolete libunique-dev
to be marked as done.

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

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


-- 
947514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: midori
Version: 7.0-2
Severity: serious
Justification: inheriting severity from 895520
Control: block 895520 by -1

src:midori Build-Depends on libunique-dev, which is obsolete and
unmaintained upstream (see #895520 for more details). Its Debian
maintainers, the GNOME team, do not consider libunique to be suitable
for inclusion in the bullseye (Debian 11) stable release.

The midori binary package does not appear to have a Depends on
libunique-1.0-0, which suggests that the build-dependency is no longer
necessary. (Also, midori now depends on GTK 3, but libunique is part of
the older and incompatible GTK 2 stack, so I don't think midori could
be using libunique successfully.)

Please remove this build-dependency, so that the GNOME team can be a
step closer to removing libunique.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: midori
Source-Version: 7.0-2.1

We believe that the bug you reported is fixed in the latest version of
midori, 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.
Boyuan Yang  (supplier of updated midori 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:50:31 -0500
Source: midori
Architecture: source
Version: 7.0-2.1
Distribution: unstable
Urgency: medium
Maintainer: Dominik George 
Changed-By: Boyuan Yang 
Closes: 947514
Changes:
 midori (7.0-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: Drop obsolete Build-Depends on libunique-dev.
 (Closes: #947514)
Checksums-Sha1:
 018b190ba91c6848266f97166ae5d8193b2e7247 2169 midori_7.0-2.1.dsc
 c93dcbeb1076ff6e91391fdfa0f3b53242d0af51 13020 midori_7.0-2.1.debian.tar.xz
 cb4bfdcb6e9a81a31e33957ac4ad7562a02c59b4 17661 midori_7.0-2.1_amd64.buildinfo
Checksums-Sha256:
 91fd3da1945a5a39def730db122ae8d1d3cd799f7b9e5a6ca51b31d08b07d98b 2169 
midori_7.0-2.1.dsc
 e238ed83d1b16ac64bb39d3aea191b1f8d903a3b384285968b01246496e99429 13020 
midori_7.0-2.1.debian.tar.xz
 f7ff0bf6049fa4f995dd88301dfd48b1f28fdcdd2edcc79d9eee385df424490f 17661 
midori_7.0-2.1_amd64.buildinfo
Files:
 cde85a2357740fd84a87058effe0365f 2169 web optional midori_7.0-2.1.dsc
 e81a2cc705a9f4805fdcca8a7243bcf3 13020 web optional 
midori_7.0-2.1.debian.tar.xz
 a87c64fba1538da3dece4461b781141b 17661 web optional 
midori_7.0-2.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl4SU30ACgkQwpPntGGC
Ws4A9Q//SvecYew1ufhNoWajJ5UBfPSc1kzz78Hb8EnVMSYAb1B3FL2lF2MnkavI
gGPsOD79hNAVwDXptDdBJIiip5VQmzGo8ayM1bks3nB4v3/sgHwGCMcvEZwbkfjP
Kg/MbC0s0hGpH3wnzCn7mtbj5blLm6zsASSXFqYaMjkXr4QTcsxQjnOusuk7IAVR
5Hhq3GAxH/9vym46ySLxEp5l1XLChtgoY3OOggOuFwrZ0S3OvTvsvoIIgGDIVd8P
hXkMZTjnN9yfVhPCcEZT0yveBOCuKjgafMpPlt+4zcUBdfPuI6P0IiFCfUlncK3R
OlDKGzldmsZUKkwcrpzd30ueQ0pxceptkmTj3zH0Q538Te3w28o9kjDYdxpeMvbe
i+zDYgyiXgZoQqmWwydgKE4Dcw5jvIkvFANs5z+dfbSyg8sFacV2s46h/NWxo18e
WkpRTGhMgYek8nDzgowLZdnKIZKONeCKhWCFdF/lh3rq1/pkoL8FRIoxNxcBL2vf
htLSLoOyCvLp7JOgxoat5yZPQYDNbpYz1fibpOBdym8IOnhov+4mVNzAFx37ty47
DEJYP9fcBjuDdx9pp1Dr8IBr6SKdtp3ggre8rpSF+isBtH2rdhNkjzn+IXCuCzdO
53IDUTyc8Vk16Iastndym20nILrWiXks7tg0ttE90O5QVFaSsT0=
=yXuD
-END PGP SIGNATURE End Message ---

Processed: tagging 948555

[Debian Bug Tracking System]

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

> tags 948555 + sid bullseye
Bug #948555 [python-soappy] python-soappy: should this package be removed?
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Bug#948600: fastahack: missing Breaks+Replaces: libfastahack0 (<< 1.0.0+dfsg-4)

[Andreas Beckmann]

Package: fastahack
Version: 1.0.0+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'buster'.
It installed fine in 'buster', then the upgrade to 'bullseye' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Preparing to unpack .../fastahack_1.0.0+dfsg-4_amd64.deb ...
  Unpacking fastahack (1.0.0+dfsg-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/fastahack_1.0.0+dfsg-4_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/fastahack.1.gz', which is also in 
package libfastahack0 0.0+git20160702.bbc645f+dfsg-6
  Errors were encountered while processing:
   /var/cache/apt/archives/fastahack_1.0.0+dfsg-4_amd64.deb


cheers,

Andreas


libfastahack0=0.0+git20160702.bbc645f+dfsg-6_fastahack=1.0.0+dfsg-4.log.gz
Description: application/gzip

Bug#948597: fasta3-doc: missing Breaks+Replaces: fasta3 (<< 36.3.8h)

[Andreas Beckmann]

Package: fasta3-doc
Version: 36.3.8h-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Preparing to unpack .../fasta3-doc_36.3.8h-1_all.deb ...
  Unpacking fasta3-doc (36.3.8h-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/fasta3-doc_36.3.8h-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/fasta3/fasta_guide.pdf', which is also 
in package fasta3 36.3.8g-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/fasta3-doc_36.3.8h-1_all.deb


cheers,

Andreas


fasta3=36.3.8g-1_fasta3-doc=36.3.8h-1.log.gz
Description: application/gzip

Bug#874880: FreeMedForms projet

[Eric Maeker]

Oh! There is a misunderstanding here!
Let me correct my words:
-> full code of each stable released version is packaged and freely
available (but undocumented since v1.0.0).

Code is considered 100% stable (and released) when :
- it perfectly passes every the unit-tests in debug mode with MacOs,
Win32/64, Debian 64,
- it perfectly builds in each platform and
- it perfectly passes manual tests on the release bin for each platform.
Manual tests are available on our main website : freemedforms.com
-> This is because we do not have time to test and pack all sub-versions
like before.
Currently v1.1.0 does passes all tests under MacOs, does build correctly on
Debian in debug mode but not in release, and is not tested on Win32/64
(build process, unit-tests, installation process, config process...)
because WinDevs quit the project. So it is considered as a pre-version
available only to testers (MacOs).

We know that at least two forks exists (this is what our private data
server's log tells us). We do not receive any patch, invitation to git
repos, or any kind of official informations or queries.

In consequence, we decide that our git repository will not be freely
accessible. Approval does only concern the FreeMedForms' git and the
ability to join the project as member (coder, tester, communication
manager...).

I hope that the situation is clearer for you.

Belle journée
Cordialement


 *Dr Maeker Éric*

*Gériatre, psychogériatre*
eric.mae...@gmail.com
Twitter  @DrMaeker 
RPPS 10002307964

maeker.fr  Site personnel
empathies.fr  Association Emp@thies
freemedforms.com  Logiciel médical

La gériatrie, c'est la médecine pour les pères et les mères Noël


Le ven. 10 janv. 2020 à 14:26, Daniel Hakimi  a
écrit :

> If the package is available under the GPL, it strikes me that requiring
> any non-trivial approval to obtain source under that license would not be
> allowed. If the form is just a check box verifying that you have received
> object code, maybe, but this sounds like it may be a license violation. Can
> we clarify what the approval process entails? How much information is
> required, and for what reasons might people be rejected?
>
> However, if some third party were to obtain this source, build from it,
> and make it available, that version of the code would be perfectly Free.
>
> On Fri, Jan 10, 2020, 08:15 Andreas Tille  wrote:
>
>> On Fri, Jan 10, 2020 at 07:45:34AM -0500, Daniel Hakimi wrote:
>> > Can you please clarify -- you said the license was the same, but you
>> didn't
>> > say what that license actually was. What license is your code available
>> > under?
>>
>> GPL-3+ [1]
>>
>> BTW, I think if a Debian package is published the requirement to sign
>> anything to get the source code is useless since interested parties can
>> easily download the Debian source package.
>>
>> This is for instance true for the latest source in Git which just has a
>> compile bug which we desperately try to fix to finalise the Qt4
>> removal[2].
>>
>> Kind regards
>>
>>   Andreas.
>>
>> [1]
>> https://salsa.debian.org/med-team/freemedforms-project/blob/master/COPYING.txt
>> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874880#104
>>
>> > On Fri, Jan 10, 2020, 07:18 Eric Maeker  wrote:
>> >
>> > > Hi,
>> > >
>> > > For now, our NPO is too poor to engage in consulting or to pay
>> external
>> > > developments and we awfully miss time to manage all aspects of a
>> widely
>> > > collaborative project.
>> > > Sounds like we are travelling to "contrib" or "non-free" package ? Or
>> may
>> > > be "non-debian" ?
>> > >
>> > > Belle journée
>> > > Cordialement
>> > >
>> > >
>> > >  *Dr Maeker Éric*
>> > >
>> > > *Gériatre, psychogériatre*
>> > > eric.mae...@gmail.com
>> > > Twitter  @DrMaeker 
>> > > RPPS 10002307964
>> > >
>> > > maeker.fr  Site personnel
>> > > empathies.fr  Association Emp@thies
>> > > freemedforms.com  Logiciel médical
>> > >
>> > > La gériatrie, c'est la médecine pour les pères et les mères Noël
>> > >
>> > >
>> > > Le ven. 10 janv. 2020 à 03:03, Paul Wise  a écrit :
>> > >
>> > >> On Thu, Jan 9, 2020 at 8:00 PM Eric Maeker wrote:
>> > >>
>> > >> > Free Source code is provided to any demander approved by the NPO,
>> code
>> > >> licence is still the same.
>> > >>
>> > >> I don't like this, people seeking source code should not have to get
>> > >> approval first. That said, I note that the source code is available
>> > >> directly from the site without approval.
>> > >>
>> > >> > But, the code documentation is only reserved to approved
>> developers by
>> > >> this NPO.
>> > >>
>> > >> I definitely don't like this, it would be much better to publish the
>> > >> code documentation to everyone under a free license.
>> > >>
>> > >> > We do encourage new dev to apply to our NPO and to sign a CLA
>> (which is
>> > >> still a draft piece of text actually).
>> > >>
>> > >> I don't like this either, 

Bug#946018: marked as done (opencpn: FTBFS due to trying to use removed wx GTK2 flavour)

[Debian Bug Tracking System]

Your message dated Fri, 10 Jan 2020 16:09:24 +
with message-id 
and subject line Bug#946018: fixed in opencpn 5.0.0+dfsg-1
has caused the Debian Bug report #946018,
regarding opencpn: FTBFS due to trying to use removed wx GTK2 flavour
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.)


-- 
946018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946018
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opencpn
Version: 4.8.8+dfsg.2-1
Severity: grave
Justification: renders package unusable

opencpn build-depends on libwxgtk3.0-dev, but that's been dropped
(there are still some crufty remnants in unstable, but libwxgtk3.0-dev
is no longer built by the wxwidgets3.0 source package, and isn't
installable in unstable).

The removal happened while opencpn was in NEW, so it's never built
since being accepted, hence the grace severity - as-is this package is
not usable by anyone simply because there's no build of it to install!

As well as updating libwxgtk3.0-dev to libwxgtk3.0-gtk3-dev, the
B-D on libgtk2.0-dev will need updating to libgtk-3-dev.  I suspect
libgdk-pixbuf2.0-dev will too.  There may also be code changes needed
to update for API changes between GTK2 and GTK3 if opencpn upstream
isn't GTK3 ready.

Sorry to be the bearer of bad news.

Cheers,
Olly
--- End Message ---
--- Begin Message ---
Source: opencpn
Source-Version: 5.0.0+dfsg-1

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

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

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

Debian distribution maintenance software
pp.
Alec Leamas  (supplier of updated opencpn package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 19 Nov 2019 08:49:56 -0500
Source: opencpn
Architecture: source
Version: 5.0.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Alec Leamas 
Closes: 946018
Changes:
 opencpn (5.0.0+dfsg-1) unstable; urgency=medium
 .
   [ Alec Leamas ]
   * New upstream release
   * Move to gtk3
 (closes: #946018)
   * Drop all patches besides two after being upstreamed
   * Drop some lintian overrides after upstream fixes.
   * Add a patch for broken include paths.
   * Add a patch for broken FIND_WXWIDGETS in CMakeLists
   * Disable assertion messages using the standard NDEBUG flag.
   * Move appstream data to new location, relicense
 and clean up rules.
   * Bump Standards-Version to 4.4.1, no changes.
   * Move to compat level 12, use new compat scheme
   * Drop dfsg.N suffix to reflect local habits.
   * Move around some docs.
 .
   [ Bas Couwenberg ]
   * Restructure control file with cme.
   * Change libgtk2.0-dev build dependency to libgtk-3-dev.
   * Update watch file to handle common issues.
   * Rename install file to opencpn.install.
   * Drop obsolete include-binaries file.
   * Fix typo in lintian override comment.
   * Drop Name field from upstream metadata.
Checksums-Sha1:
 13d4f0cbe6b286245172dd9d60546139af457c3f 2344 opencpn_5.0.0+dfsg-1.dsc
 e8c52c1d8cc0720d10022de00a3a558a1c258b53 18018964 
opencpn_5.0.0+dfsg.orig.tar.xz
 614d4c421e9dea33a1491520c3e83d26af6fec0a 13820 
opencpn_5.0.0+dfsg-1.debian.tar.xz
 ee1dbf9300d0e3106b432a5973d8e7d9d9a95513 16742 
opencpn_5.0.0+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 7196ebeaad080e6594e8fa0d70df65721db62ec94fb194510283b13f848ea985 2344 
opencpn_5.0.0+dfsg-1.dsc
 4842c8d82c4448a4eec0137f23ac4b89dba35466cb18dfb805febc381635 18018964 
opencpn_5.0.0+dfsg.orig.tar.xz
 2dd9508858ba41583e0b9487d541bb68cde0d64ad24aeccb34ed2f5b2ad4e340 13820 
opencpn_5.0.0+dfsg-1.debian.tar.xz
 ae471845474ccaf394846ad2cba3175ee9f9edd74f08b24da042cad4f9d2e0a2 16742 
opencpn_5.0.0+dfsg-1_amd64.buildinfo
Files:
 a95c061a48996d74776be6fb6fa999de 2344 misc optional opencpn_5.0.0+dfsg-1.dsc
 14104cd121776ee86c5d5d25bb1c9326 18018964 misc optional 
opencpn_5.0.0+dfsg.orig.tar.xz
 403ed98794ed4c98e072f79624b711cb 13820 misc optional 
opencpn_5.0.0+dfsg-1.debian.tar.xz
 3c94ac014ca0fbd74c4be9a2db5f1eee 16742 misc optional 
opencpn_5.0.0+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#948590: hardcoded dependency on python

[Matthias Klose]

Package: bedops
Version: 2.4.37+dfsg-1
Severity: serious
Tags: sid bullseye

the package still has a hardcoded dependency on python.

Bug#923772: marked as done (adapterremoval ftbfs on i386)

[Debian Bug Tracking System]

Your message dated Fri, 10 Jan 2020 15:35:01 +
with message-id 
and subject line Bug#923772: fixed in adapterremoval 2.3.1-3
has caused the Debian Bug report #923772,
regarding adapterremoval ftbfs on i386
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.)


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

[...]
~~~
main is a Catch v2.6.0 host application.
Run with -? for options

---
Identical nucleotides gets higher qualities
---
tests/unit/alignment_test.cpp:833
...

tests/unit/alignment_test.cpp:841: FAILED:
  REQUIRE( collapsed_result == collapsed_expected )
with expansion:
  '@Rec1\nGCATGATATATACAAC\n+\n012345'FBcEFGHIJ\n'
  ==
  '@Rec1\nGCATGATATATACAAC\n+\n012345(FBcEFGHIJ\n'

---
Higher quality nucleotide is selected
---
tests/unit/alignment_test.cpp:857
...

tests/unit/alignment_test.cpp:865: FAILED:
  REQUIRE( collapsed_result == collapsed_expected )
with expansion:
  '@Rec1\nGCATGATAATTACAAC\n+\n012345'%5%EFGHIJ\n'
  ==
  '@Rec1\nGCATGATAATTACAAC\n+\n012345(%5%EFGHIJ\n'

===
test cases: 209 | 207 passed | 2 failed
assertions: 612 | 610 passed | 2 failed

make[2]: *** [Makefile:170: test] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:19: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:10: build-arch] Error 2
--- End Message ---
--- Begin Message ---
Source: adapterremoval
Source-Version: 2.3.1-3

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated adapterremoval package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 10 Jan 2020 15:43:41 +0100
Source: adapterremoval
Architecture: source
Version: 2.3.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 923772
Changes:
 adapterremoval (2.3.1-3) unstable; urgency=medium
 .
   * Fix build on some architectures
 Closes: #923772
   * Set upstream metadata fields: Bug-Submit.
Checksums-Sha1:
 61317f35ad1b071cf22fee6bb5636a06035e9852 2211 adapterremoval_2.3.1-3.dsc
 c2979fce39fa9a1e02594d9556f8b354e04022c3 10800 
adapterremoval_2.3.1-3.debian.tar.xz
 7326b9d09c267b5fc7fd215cff874b24c541346a 6260 
adapterremoval_2.3.1-3_amd64.buildinfo
Checksums-Sha256:
 5eb28a5c4f326aaa9a44e539b911c1ca304ec62bfd569291007fe2636d336902 2211 
adapterremoval_2.3.1-3.dsc
 c8f59f7335a4173e3c2bbca79630192458f6527ef9fc19598b7f5eb814d6da25 10800 
adapterremoval_2.3.1-3.debian.tar.xz
 65d353219089192ab21b0b8957fc35914ba43be2fa826f67a0ce293cea9cf000 6260 
adapterremoval_2.3.1-3_amd64.buildinfo
Files:
 7eaffe6df3b81c9c63ede606e5a1383a 2211 science optional 
adapterremoval_2.3.1-3.dsc
 5ce4db0eb9f0efc226ac65adc3514ab0 10800 science optional 
adapterremoval_2.3.1-3.debian.tar.xz
 730fc6ee40627cc80bda225effc01f92 6260 science optional 
adapterremoval_2.3.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl4YkakRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFf+xAAgpLZfmjRZ0kDj1QgERglq+CZJwyIl84m
a7GxudLPUo+sHfdHFsSSDKHRcRFe+QbQtLHVaXA9n9Xxq9n5uEXp0qPm8Mky4v5U
4MfGO0XPcW3nhUTOlTObGLA6hDFD0BG7eykCKewHWSHc1zyLsDC04jgK9kF26yzx
vuFGQYTRRtsuIxy4F8yszKKMWWGDdsw6/FT3+ZKKwkCWF3TD8rt8qRbCD6tAl8mp

Processed: py2removal bugs severity updates - 2020-01-10 15:35:43.233793+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
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # python-brial is a module and has 0 external rdeps or not in testing
> severity 936238 serious
Bug #936238 [src:brial] brial: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-bottle is a module and has 0 external rdeps or not in testing
> severity 937620 serious
Bug #937620 [src:python-bottle] python-bottle: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-psutil is a module and has 0 external rdeps or not in testing
> severity 938050 serious
Bug #938050 [src:python-psutil] python-psutil: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#948491: centengine crashes regulary

[Bernhard Übelacker]

Dear Maintainer,
I guess I found the issue here.
It looks like centengine is crashing with an unmodified
default configuration after 60 minutes running.

By changing "retention_update_interval" from 60 to 1 this could
be lowered to 1 minute.

Further it looks like having null pointers in "custom_variables"
member is not unusual.

But because 'dump::customvariables' receives the 'obj' by reference,
the compiler removes in an optimized build the null check,
I guess because it assumes that a reference has to be valid by definition.

Attached patch changes the argument by reference to a pointer.
A package build with that patch checks like expected for null and
leaves the function.

Upstream seems to have changed obj.custom_variables to a container type,
which might therefore not suffer from this problem anymore.

Kind regards,
Bernhard


(gdb) print obj.custom_variables 
$3 = (customvariablesmember_struct *) 0x0

  
https://sources.debian.org/src/centreon-engine/18.10.0-4/src/retention/dump.cc/#L127
(gdb) list 121,133
121 std::ostream& dump::customvariables(
122 std::ostream& os,
123 customvariablesmember_struct const& obj) {
124   for (customvariablesmember const* member();
125member;
126member = member->next)
127 if (member->variable_name)
128   os << "_" << member->variable_name << "="
129  << member->has_been_modified << ","
130  << (member->variable_value ? member->variable_value : "")
131  << "\n";
132   return (os);
133 }

  
https://sources.debian.org/src/centreon-engine/18.10.0-4/src/retention/dump.cc/#L454
(gdb) list 389,455
389 std::ostream& dump::service(std::ostream& os, service_struct const& 
obj) {
...
454   dump::customvariables(os, *obj.custom_variables);
455   os << "}\n";


(gdb) bt
#0  com::centreon::engine::retention::dump::customvariables (os=..., obj=...) 
at ./src/retention/dump.cc:127
#1  0x559743899013 in com::centreon::engine::retention::dump::host (os=..., 
obj=...) at ./src/retention/dump.cc:264
#2  0x55974389a62b in com::centreon::engine::retention::dump::hosts 
(os=...) at ./src/retention/dump.cc:278
#3  com::centreon::engine::retention::dump::save (path=...) at 
./src/retention/dump.cc:359
#4  0x55974386126b in _exec_event_retention_save (event=) at 
./src/events/timed_event.cc:176
#5  0x559743860b5d in handle_timed_event (event=event@entry=0x559744b5ea90) 
at ./src/events/timed_event.cc:752
#6  0x55974385becb in com::centreon::engine::events::loop::_dispatching 
(this=0x559744b396a0) at ./src/events/loop.cc:233
#7  0x55974385c9e9 in com::centreon::engine::events::loop::run 
(this=0x559744b396a0) at ./src/events/loop.cc:90
#8  0x559743784774 in main (argc=, argv=) at 
./src/main.cc:410



Unmodified Debian: || With 
patch applied:
...7c0 <+0>: push   %r14   || ...530 
<+0>: push   %r14
...7c2 <+2>: lea0x290a5(%rip),%r14# 0x5597438c086e ||
...7c9 <+9>: push   %r13   || ...532 
<+2>: push   %r13
...7cb <+11>:push   %r12   || ...534 
<+4>: push   %r12
...7cd <+13>:push   %rbp   || ...536 
<+6>: push   %rbp
...7ce <+14>:mov%rdi,%rbp  || ...537 
<+7>: mov%rdi,%rbp
...7d1 <+17>:push   %rbx   || ...53a 
<+10>:push   %rbx
   || ...53b 
<+11>:test   %rsi,%rsi <<< null check
   || ...53e 
<+14>:je 0x560648b46630 <...customvariables...+256><<< jump
...7d2 <+18>:mov%rsi,%rbx  || ...544 
<+20>:mov%rsi,%rbx
...7d5 <+21>:jmpq   0x559743897868 <...customvariables...+168> ||   
   ...
 ...   ||   
   ...
...868 <+168>:   cmpq   $0x0,(%rbx)   <<< crash||   
   ...
 ...   || ...630 
<+256>:   pop%rbx
   || ...631 
<+257>:   mov%rbp,%rax
   || ...634 
<+260>:   pop%rbp
   || ...635 
<+261>:   pop%r12
   || ...637 
<+263>:   pop%r13
  ...639 
<+265>:   pop%r14
 

Bug#936924: Moving libsvm to Debian Science team

[Chen-Tse Tsai]

Hi Christian,

Yes, my changes are merged.

I won't be able to work on it in the next few days. Thanks for your help!
If you want, it would be great to add you as an Uploader since you know
these packages really well.

Thanks,
Chen-Tse


On Fri, Jan 10, 2020 at 8:14 AM Christian Kastner  wrote:

> On 10.01.20 11:07, Andreas Tille wrote:
> > since my upload was a bit questionable this gives us the chance
> > to discuss it again.  What option would you prefer:
> >
> >1. I just re-upload what is in Git right now to new queue
> >2. Somebody who feels more competent takes over
> >3. Something else
>
> I dropped the ball on this when I got back from the holidays, but I can
> look into it now.
>
> Chen-Tse, is your work already in the git repo on Salsa?
>

Bug#936509: fdsend: Python2 removal in sid/bullseye

[Philipp Kern]

reassign 936509 ftp.debian.org
retitle 936509 RM: fdsend -- RoM; obsoleted by built-in functionality
affects 936509 + src:fdsend
severity 936509 important
thanks

On Fri, Aug 30, 2019 at 07:17:00AM +, Matthias Klose wrote:
> 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.

While there is a somewhat high popcon count, all of this is due to ganeti.
Python 3 provides all facilities required for sendfd support natively and
documents them as such in [1] and [2]. The latter even contains a one-liner
that's all that is required at this point.

Ganeti has also been fixed upstream to make use of the native functionality:

commit 493c901bd23c9a891a3426b0468a4db462058af3
Author: Apollon Oikonomopoulos 
Date:   Thu Jun 20 10:26:58 2019 +0200

Implement SendFds

fdsend does not support Python 3; luckily, Python 3's socket library
exposes everything we need to re-implement it in pure Python, so add
utils.SendFds which sends a bunch of fds, along with data, over a
socket.

Signed-off-by: Apollon Oikonomopoulos 

Thus this package should be removed in favor of the built-in methods rather
than be ported to Python 3 (which has happened but will now not be uploaded
here). Users should follow the documentation to migrate.

Kind regards and thanks
Philipp Kern

[1] https://docs.python.org/3/library/socket.html#socket.socket.recvmsg 
[2] https://docs.python.org/3/library/socket.html#socket.socket.sendmsg

Processed: Re: Bug#936509: fdsend: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

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

> reassign 936509 ftp.debian.org
Bug #936509 [src:fdsend] fdsend: Python2 removal in sid/bullseye
Bug reassigned from package 'src:fdsend' to 'ftp.debian.org'.
No longer marked as found in versions fdsend/0.2.1-2.
Ignoring request to alter fixed versions of bug #936509 to the same values 
previously set
> retitle 936509 RM: fdsend -- RoM; obsoleted by built-in functionality
Bug #936509 [ftp.debian.org] fdsend: Python2 removal in sid/bullseye
Changed Bug title to 'RM: fdsend -- RoM; obsoleted by built-in functionality' 
from 'fdsend: Python2 removal in sid/bullseye'.
> affects 936509 + src:fdsend
Bug #936509 [ftp.debian.org] RM: fdsend -- RoM; obsoleted by built-in 
functionality
Added indication that 936509 affects src:fdsend
> severity 936509 important
Bug #936509 [ftp.debian.org] RM: fdsend -- RoM; obsoleted by built-in 
functionality
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: tagging 948549, retitle 948549 to pgadmin3: Segfault in query tool

[Debian Bug Tracking System]

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

> tags 948549 + help
Bug #948549 [pgadmin3] pgadmin3: Segfault when trying toi start query tool
Added tag(s) help.
> retitle 948549 pgadmin3: Segfault in query tool
Bug #948549 [pgadmin3] pgadmin3: Segfault when trying toi start query tool
Changed Bug title to 'pgadmin3: Segfault in query tool' from 'pgadmin3: 
Segfault when trying toi start query tool'.
> thanks
Stopping processing here.

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

Processed: found 948549 in 1.22.2-6

[Debian Bug Tracking System]

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

> found 948549 1.22.2-6
Bug #948549 [pgadmin3] pgadmin3: Segfault when trying toi start query tool
Marked as found in versions pgadmin3/1.22.2-6.
> thanks
Stopping processing here.

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

Bug#948549: pgadmin3: Segfault when trying toi start query tool

[Christoph Berg]

Re: Erwin Brandstetter 2020-01-10 
<157862519463.9993.8745255910335394793.reportbug@brsanuc5>
> Package: pgadmin3
> Version: 1.22.2-6.pgdg100+1
> Severity: grave
> Justification: renders package unusable
> 
> Introduced with installing pgadmin3 1.22.2-6.pgdg18.04+1
> Now it segfaults every time when trying to open the essential query tool. 
> Tried
> with Postgres 10, 11, 12.

Not good. I can reproduce the problem here on bullseye.

I can revert to the old wxgtk package on the older distributions, but
maybe we have to accept that pgadmin3 is dead now and ultimately
remove it from unstable.

There's this https://github.com/Symbiatch/pgAdmin3 fork but that
doesn't support PG12 either, and didn't even compile for reasons I
forgot about.

Christoph

Bug#874880: FreeMedForms projet

[Daniel Hakimi]

If the package is available under the GPL, it strikes me that requiring any
non-trivial approval to obtain source under that license would not be
allowed. If the form is just a check box verifying that you have received
object code, maybe, but this sounds like it may be a license violation. Can
we clarify what the approval process entails? How much information is
required, and for what reasons might people be rejected?

However, if some third party were to obtain this source, build from it, and
make it available, that version of the code would be perfectly Free.

On Fri, Jan 10, 2020, 08:15 Andreas Tille  wrote:

> On Fri, Jan 10, 2020 at 07:45:34AM -0500, Daniel Hakimi wrote:
> > Can you please clarify -- you said the license was the same, but you
> didn't
> > say what that license actually was. What license is your code available
> > under?
>
> GPL-3+ [1]
>
> BTW, I think if a Debian package is published the requirement to sign
> anything to get the source code is useless since interested parties can
> easily download the Debian source package.
>
> This is for instance true for the latest source in Git which just has a
> compile bug which we desperately try to fix to finalise the Qt4
> removal[2].
>
> Kind regards
>
>   Andreas.
>
> [1]
> https://salsa.debian.org/med-team/freemedforms-project/blob/master/COPYING.txt
> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874880#104
>
> > On Fri, Jan 10, 2020, 07:18 Eric Maeker  wrote:
> >
> > > Hi,
> > >
> > > For now, our NPO is too poor to engage in consulting or to pay external
> > > developments and we awfully miss time to manage all aspects of a widely
> > > collaborative project.
> > > Sounds like we are travelling to "contrib" or "non-free" package ? Or
> may
> > > be "non-debian" ?
> > >
> > > Belle journée
> > > Cordialement
> > >
> > >
> > >  *Dr Maeker Éric*
> > >
> > > *Gériatre, psychogériatre*
> > > eric.mae...@gmail.com
> > > Twitter  @DrMaeker 
> > > RPPS 10002307964
> > >
> > > maeker.fr  Site personnel
> > > empathies.fr  Association Emp@thies
> > > freemedforms.com  Logiciel médical
> > >
> > > La gériatrie, c'est la médecine pour les pères et les mères Noël
> > >
> > >
> > > Le ven. 10 janv. 2020 à 03:03, Paul Wise  a écrit :
> > >
> > >> On Thu, Jan 9, 2020 at 8:00 PM Eric Maeker wrote:
> > >>
> > >> > Free Source code is provided to any demander approved by the NPO,
> code
> > >> licence is still the same.
> > >>
> > >> I don't like this, people seeking source code should not have to get
> > >> approval first. That said, I note that the source code is available
> > >> directly from the site without approval.
> > >>
> > >> > But, the code documentation is only reserved to approved developers
> by
> > >> this NPO.
> > >>
> > >> I definitely don't like this, it would be much better to publish the
> > >> code documentation to everyone under a free license.
> > >>
> > >> > We do encourage new dev to apply to our NPO and to sign a CLA
> (which is
> > >> still a draft piece of text actually).
> > >>
> > >> I don't like this either, it would be much better for devs to release
> > >> their contributions under the same license that you do, then you can
> > >> incorporate their changes, preserving their copyright over their
> > >> changes and passing on their license to you to downstream users. So
> > >> the whole of the software is then owned by a variety of copyright
> > >> holders, each of whom also have to abide by the license given to them
> > >> by the other contributors. The license on the software then cannot be
> > >> changed without contributor consensus, so it becomes a much more solid
> > >> project from a user perspective. Single-owner projects are much more
> > >> easy to turn proprietary.
> > >>
> > >> http://ebb.org/bkuhn/blog/2014/06/09/do-not-need-cla.html
> > >>
> > >> > The problem is that FreeMedForms EHR needs access to private data
> > >>
> > >> Could you explain why this data needs to be private? It would be much
> > >> better to release it publicly under a free license.
> > >>
> > >> > The private data are only available to paying partners to the NPO.
> > >>
> > >> Is this the only form of income that the NPO has available to it? It
> > >> sounds like the NPO is seeking what is called an "Open Core" business
> > >> model, where the core part of the project is public and freely
> > >> licensed but addons are proprietary. The incentives here can be quite
> > >> perverse, often companies seek to prevent outside contributions to the
> > >> core or even remove features from the core so that more people start
> > >> paying them for the proprietary addons. So I encourage you to consider
> > >> alternative income streams.
> > >>
> > >> I think the best option for the would be to consult with as many of
> > >> the practices, clinics, hospitals and emergency departments that you
> > >> know about that use the software and find out the best way for the NPO
> > >> to have 

Processed: tagging 947292, found 948473 in 1.10+dfsg-3, tagging 948473, found 944542 in 0.2.1-1, tagging 944542 ...

[Debian Bug Tracking System]

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

> tags 947292 + pending
Bug #947292 {Done: Andreas Beckmann } [nyancat-server] 
nyancat-server: package does not include needed systemd file
Added tag(s) pending.
> found 948473 1.10+dfsg-3
Bug #948473 [src:cain] keep cain out of testing
Marked as found in versions cain/1.10+dfsg-3.
> tags 948473 + sid bullseye
Bug #948473 [src:cain] keep cain out of testing
Added tag(s) sid and bullseye.
> found 944542 0.2.1-1
Bug #944542 [aws-shell] aws-shell: prompt_toolkit 2.x support
Marked as found in versions aws-shell/0.2.1-1.
> tags 944542 + sid bullseye
Bug #944542 [aws-shell] aws-shell: prompt_toolkit 2.x support
Added tag(s) sid and bullseye.
> tags 948493 + experimental
Bug #948493 [src:libxml2] the Python2 -dbg package should depend on python2-dbg
Added tag(s) experimental.
> tags 945674 + experimental
Bug #945674 {Done: Sandro Knauß } [src:nextcloud-desktop] 
nextcloud-desktop: Python2 removal in sid/bullseye
Added tag(s) experimental.
> found 948541 1.8-4
Bug #948541 [src:decoratortools] decoratortools: should this package be removed?
Marked as found in versions decoratortools/1.8-4.
> tags 948541 + sid bullseye
Bug #948541 [src:decoratortools] decoratortools: should this package be removed?
Added tag(s) sid and bullseye.
> tags 948494 + experimental
Bug #948494 [src:libxslt] the Python2 -dbg package should depend on 
python2-dbg, instead of python-dbg
Added tag(s) experimental.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
944542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944542
945674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945674
947292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947292
948473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948473
948493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948493
948494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948494
948541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#874880: FreeMedForms projet

[Andreas Tille]

On Fri, Jan 10, 2020 at 07:45:34AM -0500, Daniel Hakimi wrote:
> Can you please clarify -- you said the license was the same, but you didn't
> say what that license actually was. What license is your code available
> under?

GPL-3+ [1]

BTW, I think if a Debian package is published the requirement to sign
anything to get the source code is useless since interested parties can
easily download the Debian source package.

This is for instance true for the latest source in Git which just has a
compile bug which we desperately try to fix to finalise the Qt4
removal[2].

Kind regards

  Andreas.

[1] 
https://salsa.debian.org/med-team/freemedforms-project/blob/master/COPYING.txt
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874880#104
 
> On Fri, Jan 10, 2020, 07:18 Eric Maeker  wrote:
> 
> > Hi,
> >
> > For now, our NPO is too poor to engage in consulting or to pay external
> > developments and we awfully miss time to manage all aspects of a widely
> > collaborative project.
> > Sounds like we are travelling to "contrib" or "non-free" package ? Or may
> > be "non-debian" ?
> >
> > Belle journée
> > Cordialement
> >
> >
> >  *Dr Maeker Éric*
> >
> > *Gériatre, psychogériatre*
> > eric.mae...@gmail.com
> > Twitter  @DrMaeker 
> > RPPS 10002307964
> >
> > maeker.fr  Site personnel
> > empathies.fr  Association Emp@thies
> > freemedforms.com  Logiciel médical
> >
> > La gériatrie, c'est la médecine pour les pères et les mères Noël
> >
> >
> > Le ven. 10 janv. 2020 à 03:03, Paul Wise  a écrit :
> >
> >> On Thu, Jan 9, 2020 at 8:00 PM Eric Maeker wrote:
> >>
> >> > Free Source code is provided to any demander approved by the NPO, code
> >> licence is still the same.
> >>
> >> I don't like this, people seeking source code should not have to get
> >> approval first. That said, I note that the source code is available
> >> directly from the site without approval.
> >>
> >> > But, the code documentation is only reserved to approved developers by
> >> this NPO.
> >>
> >> I definitely don't like this, it would be much better to publish the
> >> code documentation to everyone under a free license.
> >>
> >> > We do encourage new dev to apply to our NPO and to sign a CLA (which is
> >> still a draft piece of text actually).
> >>
> >> I don't like this either, it would be much better for devs to release
> >> their contributions under the same license that you do, then you can
> >> incorporate their changes, preserving their copyright over their
> >> changes and passing on their license to you to downstream users. So
> >> the whole of the software is then owned by a variety of copyright
> >> holders, each of whom also have to abide by the license given to them
> >> by the other contributors. The license on the software then cannot be
> >> changed without contributor consensus, so it becomes a much more solid
> >> project from a user perspective. Single-owner projects are much more
> >> easy to turn proprietary.
> >>
> >> http://ebb.org/bkuhn/blog/2014/06/09/do-not-need-cla.html
> >>
> >> > The problem is that FreeMedForms EHR needs access to private data
> >>
> >> Could you explain why this data needs to be private? It would be much
> >> better to release it publicly under a free license.
> >>
> >> > The private data are only available to paying partners to the NPO.
> >>
> >> Is this the only form of income that the NPO has available to it? It
> >> sounds like the NPO is seeking what is called an "Open Core" business
> >> model, where the core part of the project is public and freely
> >> licensed but addons are proprietary. The incentives here can be quite
> >> perverse, often companies seek to prevent outside contributions to the
> >> core or even remove features from the core so that more people start
> >> paying them for the proprietary addons. So I encourage you to consider
> >> alternative income streams.
> >>
> >> I think the best option for the would be to consult with as many of
> >> the practices, clinics, hospitals and emergency departments that you
> >> know about that use the software and find out the best way for the NPO
> >> to have enough resources to continue development consistent with the
> >> interests of the community of folks who use the software. Examples of
> >> potential income models could include: large grants/sponsorships that
> >> cover development and other costs, a membership subscriber base that
> >> pays for all maintenance and development costs, or more of a
> >> crowd-funding model where folks interested in specific features pay
> >> for their development, or a community of consultants that do all work
> >> on the project as requested by their customers or possibly a
> >> combination of these and other options.
> >>
> >> > Forks trie to access our private data using the open sourced server
> >> protocol (query to a php script).
> >>
> >> I would suggest to just make the data public and under a free license,
> >> but if you don't 

Bug#936924: Moving libsvm to Debian Science team

[Christian Kastner]

On 10.01.20 11:07, Andreas Tille wrote:
> since my upload was a bit questionable this gives us the chance
> to discuss it again.  What option would you prefer:
> 
>1. I just re-upload what is in Git right now to new queue
>2. Somebody who feels more competent takes over
>3. Something else

I dropped the ball on this when I got back from the holidays, but I can
look into it now.

Chen-Tse, is your work already in the git repo on Salsa?

Bug#948491: centengine crashes regulary

[Pascal Vibet - ADACIS]

No problem.

I send result in centengine-debug.txt

Regards

Le ven. 10 janv. 2020 à 12:01, Bernhard Übelacker  a
écrit :

> Hello Pascal,
> now I see one thing that would be even better:
>
>   coredumpctl gdb
> info reg
> thread apply all bt full
>
> Sorry for not saying this sooner.
>
> Kind regards,
> Bernhard
>
>
sudo coredumpctl gdb
   PID: 27474 (centengine)
   UID: 108 (centreon-engine)
   GID: 114 (centreon-engine)
Signal: 11 (SEGV)
 Timestamp: Fri 2020-01-10 12:17:01 CET (35min ago)
  Command Line: /usr/sbin/centengine /etc/centreon-engine/centengine.cfg
Executable: /usr/sbin/centengine
 Control Group: /system.slice/centengine.service
  Unit: centengine.service
 Slice: system.slice
   Boot ID: 068a3a77b53f4210a7823cda9709b7a9
Machine ID: 603b330df8caf777338241c98800e15e
  Hostname: x-centreon-loc-01
   Storage: 
/var/lib/systemd/coredump/core.centengine.108.068a3a77b53f4210a7823cda9709b7a9.27474.157865502100.lz4
   Message: Process 27474 (centengine) of user 108 dumped core.

Stack trace of thread 27474:
#0  0x556c06643868 
_ZN3com8centreon6engine9retention4dump15customvariablesERSoRK28customvariablesmember_struct
 (centengine)
#1  0x556c0664629b 
_ZN3com8centreon6engine9retention4dump7serviceERSoRK14service_struct 
(centengine)
#2  0x556c06646653 
_ZN3com8centreon6engine9retention4dump8servicesERSo (centengine)
#3  0x556c0660d26b _exec_event_retention_save (centengine)
#4  0x556c0660cb5d handle_timed_event (centengine)
#5  0x556c06607ecb 
_ZN3com8centreon6engine6events4loop12_dispatchingEv (centengine)
#6  0x556c066089e9 
_ZN3com8centreon6engine6events4loop3runEv (centengine)
#7  0x556c06530774 main (centengine)
#8  0x7f50e905c09b __libc_start_main (libc.so.6)
#9  0x556c065312aa _start (centengine)

Stack trace of thread 27477:
#0  0x7f50e90fe720 __nanosleep (libc.so.6)
#1  0x7f50e9129874 usleep (libc.so.6)
#2  0x7f50e87a92d5 
_ZN3com8centreon6broker10processing8failover3runEv (cbmod.so)
#3  0x7f50e7fb2726 n/a (libQtCore.so.4)
#4  0x7f50e955ffa3 start_thread (libpthread.so.0)
#5  0x7f50e91314cf __clone (libc.so.6)

Stack trace of thread 27476:
#0  0x7f50e9126819 __poll (libc.so.6)
#1  0x7f50e5bc14cb poll (externalcmd.so)
#2  0x7f50e955ffa3 start_thread (libpthread.so.0)
#3  0x7f50e91314cf __clone (libc.so.6)

Stack trace of thread 27475:
#0  0x7f50e9126819 __poll (libc.so.6)
#1  0x7f50e9535778 _ZN3com8centreon15process_manager4_runEv 
(libcentreon_clib.so)
#2  0x7f50e953bfff 
_ZN3com8centreon11concurrency6thread8_executeEPv (libcentreon_clib.so)
#3  0x7f50e955ffa3 start_thread (libpthread.so.0)
#4  0x7f50e91314cf __clone (libc.so.6)

GNU gdb (Debian 8.2.1-2+b3) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/centengine...Reading symbols from 
/usr/lib/debug/.build-id/cb/8977dc4da718ea120bcd5c48dfa7cf9c7e25d5.debug...done.
done.
[New LWP 27474]
[New LWP 27477]
[New LWP 27476]
[New LWP 27475]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/sbin/centengine 
/etc/centreon-engine/centengine.cfg'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  com::centreon::engine::retention::dump::customvariables (os=..., obj=...) 
at ./src/retention/dump.cc:127
127 ./src/retention/dump.cc: Aucun fichier ou dossier de ce type.
[Current thread is 1 (Thread 0x7f50e9025c80 (LWP 27474))]
(gdb) info reg
rax0x7ffd3223d890  140725444663440
rbx0x0 0
rcx0xa 10
rdx0x556c066b7fb8  93922452537272
rsi0x0 0
rdi

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 948003 1.8.2+ds-1
Bug #948003 [src:prometheus-squid-exporter] prometheus-squid-exporter FTBFS in 
testing/unstable
Marked as fixed in versions prometheus-squid-exporter/1.8.2+ds-1.
>
End of message, stopping processing here.

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

Bug#948491: centengine crashes regulary

[Bernhard Übelacker]

Hello Pascal,
now I see one thing that would be even better:

  coredumpctl gdb
info reg
thread apply all bt full

Sorry for not saying this sooner.

Kind regards,
Bernhard

Processed: retitle 948538 to ldm: CVE-2019-20373

[Debian Bug Tracking System]

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

> retitle 948538 ldm: CVE-2019-20373
Bug #948538 [src:ldm] ldm: privilege escalation
Changed Bug title to 'ldm: CVE-2019-20373' from 'ldm: privilege escalation'.
> thanks
Stopping processing here.

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

Bug#947004: S4Vectors Segmentation fault after r-base-core update (Was: Bug#947004: Tests segfaults (since the r-base-core update?))

[Pages, Herve]

Good to know. Thanks!

Bug#936924: Moving libsvm to Debian Science team

[Andreas Tille]

Hi folks,

I somehow missed

   
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2019-December/076981.html

since my upload was a bit questionable this gives us the chance
to discuss it again.  What option would you prefer:

   1. I just re-upload what is in Git right now to new queue
   2. Somebody who feels more competent takes over
   3. Something else

In any case I consider the situation urgent to react in the next couple
of days to fix bug #936924 (which affects several other packages).

Any opinions?

Kind regards

 Andreas.

-- 
http://fam-tille.de

Processed: Re: Bug#948552: nmu: schroedinger-coordgenlibs_1.3-1

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #948552 [release.debian.org] nmu: schroedinger-coordgenlibs_1.3-1
Severity set to 'serious' from 'normal'
> reassign -1 libschroedinger-maeparser1 1.2.2-1
Bug #948552 [release.debian.org] nmu: schroedinger-coordgenlibs_1.3-1
Bug reassigned from package 'release.debian.org' to 
'libschroedinger-maeparser1'.
Ignoring request to alter found versions of bug #948552 to the same values 
previously set
Ignoring request to alter fixed versions of bug #948552 to the same values 
previously set
Bug #948552 [libschroedinger-maeparser1] nmu: schroedinger-coordgenlibs_1.3-1
Marked as found in versions schroedinger-maeparser/1.2.2-1.
> retitle -1 libschroedinger-maeparser1: SONAME change without package name 
> change
Bug #948552 [libschroedinger-maeparser1] nmu: schroedinger-coordgenlibs_1.3-1
Changed Bug title to 'libschroedinger-maeparser1: SONAME change without package 
name change' from 'nmu: schroedinger-coordgenlibs_1.3-1'.

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

Processed: limit source to indigo, tagging 936733

[Debian Bug Tracking System]

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

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

> tags 936733 + pending
Bug #936733 [src:indigo] indigo: Python2 removal in sid/bullseye
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#948497: marked as done (clang-tools-9: python2 shebang's)

[Debian Bug Tracking System]

Your message dated Fri, 10 Jan 2020 08:48:26 +
with message-id 
and subject line Bug#948497: fixed in llvm-toolchain-9 1:9.0.1-6
has caused the Debian Bug report #948497,
regarding clang-tools-9: python2 shebang's
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.)


-- 
948497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clang-tools-9
Version: 1:9.0.1-5
Severity: serious

The following files contain a python2 shebang, making them unusable on
a python3 only system:

$ grep -Ri '/usr/bin/env' /usr/bin | grep -iw python
/usr/bin/scan-view-9:#!/usr/bin/env python
/usr/bin/scan-build-py-9:#!/usr/bin/env python
/usr/bin/git-clang-format-9:#!/usr/bin/env python
/usr/bin/hmaptool-9:#!/usr/bin/env python

$ scan-view /tmp/scan-build-2020-01-09-150248-22678-1
/usr/bin/env: ‘python’: No such file or directory
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-9
Source-Version: 1:9.0.1-6

We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-9, 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.
Gianfranco Costamagna  (supplier of updated 
llvm-toolchain-9 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 10 Jan 2020 09:37:55 +0100
Source: llvm-toolchain-9
Binary: clang-9 clang-tools-9 clang-format-9 clang-tidy-9 clangd-9 clang-9-doc 
libclang1-9 libclang-9-dev libclang-common-9-dev libclang-cpp1-9 libclang-cpp9 
libfuzzer-9-dev python3-clang-9 python-clang-9 clang-9-examples libllvm9 llvm-9 
llvm-9-runtime llvm-9-dev llvm-9-tools libllvm-9-ocaml-dev llvm-9-doc 
llvm-9-examples lld-9 liblld-9 liblld-9-dev lldb-9 liblldb-9 python3-lldb-9 
liblldb-9-dev libomp-9-dev libomp5-9 libomp-9-doc libc++1-9 libc++-9-dev 
libc++abi1-9 libc++abi-9-dev
Architecture: source
Version: 1:9.0.1-6
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Gianfranco Costamagna 
Description:
 clang-9- C, C++ and Objective-C compiler
 clang-9-doc - C, C++ and Objective-C compiler - Documentation
 clang-9-examples - Clang examples
 clang-format-9 - Tool to format C/C++/Obj-C code
 clang-tidy-9 - clang-based C++ linter tool
 clang-tools-9 - clang-based tools for C/C++ developments
 clangd-9   - Language server that provides IDE-like features to editors
 libc++-9-dev - LLVM C++ Standard library (development files)
 libc++1-9  - LLVM C++ Standard library
 libc++abi-9-dev - LLVM low level support for a standard C++ library 
(development fi
 libc++abi1-9 - LLVM low level support for a standard C++ library
 libclang-9-dev - Clang library - Development package
 libclang-common-9-dev - Clang library - Common development package
 libclang-cpp1-9 - transitional package
 libclang-cpp9 - C++ interface to the Clang library
 libclang1-9 - C interface to the Clang library
 libfuzzer-9-dev - Library for coverage-guided fuzz testing
 liblld-9   - LLVM-based linker, library
 liblld-9-dev - LLVM-based linker, header files
 liblldb-9  - Next generation, high-performance debugger, library
 liblldb-9-dev - Next generation, high-performance debugger, header files
 libllvm-9-ocaml-dev - Modular compiler and toolchain technologies, OCaml 
bindings
 libllvm9   - Modular compiler and toolchain technologies, runtime library
 libomp-9-dev - LLVM OpenMP runtime - dev package
 libomp-9-doc - LLVM OpenMP runtime - Documentation
 libomp5-9  - LLVM OpenMP runtime
 lld-9  - LLVM-based linker
 lldb-9 - Next generation, high-performance debugger
 llvm-9 - Modular compiler and toolchain technologies
 llvm-9-dev - Modular compiler and toolchain technologies, libraries and header
 llvm-9-doc - Modular compiler and toolchain technologies, documentation
 llvm-9-examples - Modular compiler and toolchain technologies, examples
 llvm-9-runtime - Modular compiler and toolchain technologies, IR interpreter
 llvm-9-tools - Modular compiler and toolchain technologies, tools
 python-clang-9 - transitional package to python3-clang-9
 python3-clang-9 - Clang Python Bindings
 

Bug#942472: marked as done (r-cran-shiny: wrong link to nodejs files)

[Debian Bug Tracking System]

Your message dated Fri, 10 Jan 2020 08:49:57 +
with message-id 
and subject line Bug#942472: fixed in r-cran-shiny 1.4.0+dfsg-1
has caused the Debian Bug report #942472,
regarding r-cran-shiny: wrong link to nodejs files
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.)


-- 
942472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-shiny
Version: 1.3.2+dfsg-1
Severity: normal

  Hi,

  r-cran-shiny installs to symlinks (from debian/links) to nodejs files.
However, some nodejs files are in /usr/share and not /usr/lib :

$ tail -n 2 debian/links
usr/lib/nodejs/normalize.css/normalize.css  
usr/lib/R/site-library/shiny/www/shared/ionrangeslider/css/normalize.css
usr/lib/nodejs/html5shiv/dist/html5shiv.min.js  
usr/lib/R/site-library/shiny/www/shared/bootstrap/shim/html5shiv.min.js
$ ls -l /usr/lib/nodejs/normalize.css/normalize.css 
/usr/lib/nodejs/html5shiv/dist/html5shiv.min.js
ls: impossible d'accéder à '/usr/lib/nodejs/html5shiv/dist/html5shiv.min.js': 
Aucun fichier ou dossier de ce type
-rw-r--r-- 1 root root 6138 nov.   5  2018 
/usr/lib/nodejs/normalize.css/normalize.css
$ ls -l /usr/share/nodejs/html5shiv/dist/html5shiv.min.js
-rw-r--r-- 1 root root 3474 sept. 16 00:05 
/usr/share/nodejs/html5shiv/dist/html5shiv.min.js

=> the path for html5shiv.min.js must be fixed

PS: due to #942469, you might wish to add a
"Breaks: r-cran-rmarkdown (<< version that fix 942469)" in your package

  Regards,
Vincent

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

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

Versions of packages r-cran-shiny depends on:
ii  fonts-font-awesome5.0.10+really4.7.0~dfsg-1
ii  libjs-bootstrap   3.4.1+dfsg-1
ii  libjs-d3  3.5.17-2
ii  libjs-es5-shim4.5.13-2
ii  libjs-highlight.js9.12.0+dfsg1-4
ii  libjs-jquery  3.3.1~dfsg-3
ii  libjs-jquery-datatables   1.10.20+dfsg-1
ii  libjs-jquery-selectize.js 0.12.6+dfsg-1
ii  libjs-jquery-ui   1.12.1+dfsg-5
ii  libjs-json0~20190826-1
ii  libjs-twitter-bootstrap-datepicker1.3.1+dfsg1-4
ii  node-html5shiv3.7.3+dfsg-3
ii  node-normalize.css [libjs-normalize.css]  8.0.1-3
ii  r-base-core [r-api-3.5]   3.6.1-6
ii  r-cran-crayon 1.3.4-4
ii  r-cran-digest 0.6.21-1
ii  r-cran-htmltools  0.4.0-1
ii  r-cran-httpuv 1.5.2+dfsg-1
ii  r-cran-jsonlite   1.6+dfsg-1
ii  r-cran-later  1.0.0+dfsg-1
ii  r-cran-mime   0.7-1
ii  r-cran-promises   1.1.0-1
ii  r-cran-r6 2.4.0-1
ii  r-cran-rlang  0.4.0-1
ii  r-cran-sourcetools0.1.7-2
ii  r-cran-xtable 1:1.8-4-1

Versions of packages r-cran-shiny recommends:
ii  r-cran-testthat  2.2.1-1

Versions of packages r-cran-shiny suggests:
pn  r-cran-cairo  
ii  r-cran-ggplot23.2.1+dfsg-1
ii  r-cran-knitr  1.25+dfsg-1
ii  r-cran-magrittr   1.5-5
ii  r-cran-markdown   1.1+dfsg-1
ii  r-cran-rmarkdown  1.16+dfsg-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: r-cran-shiny
Source-Version: 1.4.0+dfsg-1

We believe that the bug you reported is fixed in the latest version of
r-cran-shiny, 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.
Andreas Tille  (supplier of updated