Processed: libsopt-dev: missing dependency on libopenmpi-dev

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:purify
Bug #943812 [libsopt-dev] libsopt-dev: missing dependency on libopenmpi-dev
Added indication that 943812 affects src:purify

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

Bug#943812: libsopt-dev: missing dependency on libopenmpi-dev

[Helmut Grohne]

Package: libsopt-dev
Version: 3.0.1-7
Severity: serious
Justification: missing required dependency
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + src:purify

The headers shipped in libsopt-dev #include , but they fail
depending on an mpi implementation. This is a bug.

Moreover, /usr/share/cmake/sopt/SoptCPPTargets.cmake declares an
imported library "sopt" whose INTERFACE_INCLUDE_DIRECTORIES contain
/usr/lib/arm-linux-gnueabi/openmpi/include/openmpi. Any use of this
target fails at the cmake level unless libopenmpi-dev is installed. Here
is an example of how it breaks purify.

| CMake Error in cpp/purify/CMakeLists.txt:
|   Imported target "sopt" includes non-existent path
|
| "/usr/lib/arm-linux-gnueabi/openmpi/include/openmpi"
|
|   in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:
|
|   * The path was deleted, renamed, or moved to another location.
|
|   * An install or uninstall procedure did not complete successfully.
|
|   * The installation package was faulty and references files it does not
|   provide.

A quick glimpse at the package also suggests that libeigen3-dev very
likely should also be a dependency.

Helmut

Bug#943623: Any idea how to fix this?

[Shmerl]

This issue currently breaks building Mesa master with llvm10 snapshot from
http://apt.llvm.org/unstable (in Debian testing).

Processed: Bug#941018 marked as pending in glib2.0

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #941018 [libglib2.0-0] libglib2.0-0: libdbus clients fail to authenticate 
with private GDBusServer
Added tag(s) pending.

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

Processed: Bug#941018 marked as pending in glib2.0

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #941018 [libglib2.0-0] libglib2.0-0: libdbus clients fail to authenticate 
with private GDBusServer
Ignoring request to alter tags of bug #941018 to the same tags previously set

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

Bug#941018: marked as pending in glib2.0

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #941018 in glib2.0 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/gnome-team/glib/commit/783c31a53888f18c0e6136ede78e5167bd0949ff


Update to upstream commit 2.62.2-14-gfcbb88823

* Update to upstream commit 2.62.2-14-gfcbb88823:
  - d/p/gdesktopappinfo-Allocate-DesktopFileDir-structs-dynamical.patch,
d/p/gdesktopappinfo-Cancel-file-monitor-when-resetting-a-Desk.patch,
d/p/glocalfilemonitor-Keep-a-weak-ref-to-the-monitor-in-GFile.patch:
Fix intermittent test failures for GDesktopAppInfo (Closes: #941550)
  - d/p/gvariant-Limit-recursion-in-g_variant_parse.patch:
Ensure that parsing a text-format GVariant does not run out of stack
space
  - d/p/tests-Use-objcopy-from-the-cross-compilation-file-if-conf.patch,
d/p/docs-Add-objcopy-to-example-cross-compilation-file.patch:
Use the appropriate architecture's objcopy when cross-compiling
  - d/p/gtestutils-Add-additional-non-NULL-check-in-g_assert_cmpm.patch:
Avoid false positive NULL dereference warnings in g_assert_cmpmem()
  - d/p/gspawn-Port-to-g_poll-from-select.patch:
Fix launching subprocesses when a very large number of fds are open
  - d/p/gcredentialsprivate-Document-the-various-private-macros.patch,
d/p/credentials-Invalid-Linux-struct-ucred-means-no-informati.patch,
d/p/GDBus-prefer-getsockopt-style-credentials-passing-APIs.patch:
Ensure libdbus clients can authenticate with a GDBusServer like the
one in ibus (Closes: #941018)
* d/p/Add-a-test-for-GDBusServer-authentication.patch:
  Backport regression test for #941018 from upstream git master
* d/p/gdbus-peer-test-Improve-diagnostics-if-g_rmdir-fails.patch,
  d/p/gdbus-peer-test-Stop-GDBusServer-before-tearing-down-temp.patch,
  d/p/gdbus-peer-test-Use-unix-dir-address-if-exact-format-does.patch,
  d/p/gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch:
  Add some proposed patches to improve GDBus unit tests

Closes: #941550
Closes: #941018


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/941018

Bug#941018: marked as pending in glib2.0

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #941018 in glib2.0 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/gnome-team/glib/commit/783c31a53888f18c0e6136ede78e5167bd0949ff


Update to upstream commit 2.62.2-14-gfcbb88823

* Update to upstream commit 2.62.2-14-gfcbb88823:
  - d/p/gdesktopappinfo-Allocate-DesktopFileDir-structs-dynamical.patch,
d/p/gdesktopappinfo-Cancel-file-monitor-when-resetting-a-Desk.patch,
d/p/glocalfilemonitor-Keep-a-weak-ref-to-the-monitor-in-GFile.patch:
Fix intermittent test failures for GDesktopAppInfo (Closes: #941550)
  - d/p/gvariant-Limit-recursion-in-g_variant_parse.patch:
Ensure that parsing a text-format GVariant does not run out of stack
space
  - d/p/tests-Use-objcopy-from-the-cross-compilation-file-if-conf.patch,
d/p/docs-Add-objcopy-to-example-cross-compilation-file.patch:
Use the appropriate architecture's objcopy when cross-compiling
  - d/p/gtestutils-Add-additional-non-NULL-check-in-g_assert_cmpm.patch:
Avoid false positive NULL dereference warnings in g_assert_cmpmem()
  - d/p/gspawn-Port-to-g_poll-from-select.patch:
Fix launching subprocesses when a very large number of fds are open
  - d/p/gcredentialsprivate-Document-the-various-private-macros.patch,
d/p/credentials-Invalid-Linux-struct-ucred-means-no-informati.patch,
d/p/GDBus-prefer-getsockopt-style-credentials-passing-APIs.patch:
Ensure libdbus clients can authenticate with a GDBusServer like the
one in ibus (Closes: #941018)
* d/p/Add-a-test-for-GDBusServer-authentication.patch:
  Backport regression test for #941018 from upstream git master
* d/p/gdbus-peer-test-Improve-diagnostics-if-g_rmdir-fails.patch,
  d/p/gdbus-peer-test-Stop-GDBusServer-before-tearing-down-temp.patch,
  d/p/gdbus-peer-test-Use-unix-dir-address-if-exact-format-does.patch,
  d/p/gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch:
  Add some proposed patches to improve GDBus unit tests

Closes: #941550
Closes: #941018


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/941018

Bug#943526: [Pkg-javascript-devel] Bug#943526: Bug#943526: Bug#943526: node-tslib: directory vs. symlink conflict: /usr/share/nodejs/tslib

[Jonas Smedegaard]

Quoting Julien Puydt (2019-10-29 22:11:34)
> Le mardi 29 octobre 2019 à 12:45 +0100, Xavier a écrit :
> > Control: reassign -1 node-typescript
> > 
> > Le 29/10/2019 à 08:29, Julien Puydt a écrit :
> > > Le mardi 29 octobre 2019 à 07:49 +0100, Xavier a écrit :
> > > > Hi JS team,
> > > > 
> > > > why did node-typescript have such link ?
> > > > 
> > > >   /usr/share/nodejs/tslib -> typescript/lib
> > > > 
> > > > This creates this conflict.
> > > > 
> > > 
> > > Well, isn't node-typescript supposed to provide that lib?
> > > 
> > > JP
> > 
> > When installing using `npm install typescript`, there is no
> > "node_modules/tslib", so there is no reason to provide such link IMO.
> > 
> 
> Would that break anything if node-typescript didn't provide the link?
> 
> I don't remember why I added it, but I most certainly didn't add it
> just like this...

Well, did you write a sensible commit message to go along with your 
change?

If not then I think we wil never know (at least I cannot read your 
mind).


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#938804: libvtk6.3 still depends on libpython2.7

[Aleksey Kliger]

Package: libvtk6.3
Version: 6.3.0+dfsg2-4
Followup-For: Bug #938804



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

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

Versions of packages libvtk6.3 depends on:
ii  libavcodec587:4.1.4-1+b3
ii  libavformat58   7:4.1.4-1+b3
ii  libavutil56 7:4.1.4-1+b3
ii  libc6   2.29-2
ii  libexpat1   2.2.9-1
ii  libfontconfig1  2.13.1-2+b1
ii  libfreetype62.10.1-2
ii  libgcc1 1:9.2.1-8
ii  libgdal20 [gdal-abi-2-4-0]  2.4.2+dfsg-2
ii  libgl1  1.1.0-1+b1
ii  libgl2ps1.4 1.4.0+dfsg1-2
ii  libhdf5-openmpi-103 1.10.4+repack-10
ii  libjpeg62-turbo 1:1.5.2-2+b1
ii  libjsoncpp1 1.7.4-3+b1
ii  libmariadb3 1:10.3.18-1
ii  libnetcdf-c++4  4.2-11+b1
ii  libnetcdf13 1:4.6.2-1+b1
ii  libodbc12.3.6-0.1+b1
ii  libogg0 1.3.2-1+b1
ii  libopenmpi3 3.1.3-11
ii  libpng16-16 1.6.37-1
ii  libpq5  12.0-1+b1
ii  libpython2.72.7.17-1
ii  libsqlite3-03.30.1-1
ii  libstdc++6  9.2.1-8
ii  libswscale5 7:4.1.4-1+b3
ii  libtheora0  1.1.1+dfsg.1-15
ii  libtiff54.0.10+git191003-1
ii  libx11-62:1.6.8-1
ii  libxml2 2.9.4+dfsg1-7+b3
ii  libxt6  1:1.1.5-1+b3
ii  zlib1g  1:1.2.11.dfsg-1+b1

libvtk6.3 recommends no packages.

Versions of packages libvtk6.3 suggests:
pn  mpi-default-bin  

-- no debconf information

Bug#943526: [Pkg-javascript-devel] Bug#943526: Bug#943526: node-tslib: directory vs. symlink conflict: /usr/share/nodejs/tslib

[Julien Puydt]

Le mardi 29 octobre 2019 à 12:45 +0100, Xavier a écrit :
> Control: reassign -1 node-typescript
> 
> Le 29/10/2019 à 08:29, Julien Puydt a écrit :
> > Le mardi 29 octobre 2019 à 07:49 +0100, Xavier a écrit :
> > > Hi JS team,
> > > 
> > > why did node-typescript have such link ?
> > > 
> > >   /usr/share/nodejs/tslib -> typescript/lib
> > > 
> > > This creates this conflict.
> > > 
> > 
> > Well, isn't node-typescript supposed to provide that lib?
> > 
> > JP
> 
> When installing using `npm install typescript`, there is no
> "node_modules/tslib", so there is no reason to provide such link IMO.
> 

Would that break anything if node-typescript didn't provide the link?

I don't remember why I added it, but I most certainly didn't add it
just like this...

JP

Processed: libvncserver: CVE-2019-15681

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.9.11+dfsg-1.3~deb9u1
Bug #943793 [src:libvncserver] libvncserver: CVE-2019-15681
Marked as found in versions libvncserver/0.9.11+dfsg-1.3~deb9u1.

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

Bug#943793: libvncserver: CVE-2019-15681

[Salvatore Bonaccorso]

Source: libvncserver
Version: 0.9.11+dfsg-1.3
Severity: grave
Tags: security upstream
Control: found -1 0.9.11+dfsg-1.3~deb9u1

Hi,

The following vulnerability was published for libvncserver, severity
is choosen to be rather on safe side and issue has not been fully
checked/investigated for impact/attack vector.

CVE-2019-15681[0]:
| LibVNC commit before d01e1bb4246323ba6fcee3b82ef1faa9b1dac82a contains
| a memory leak (CWE-655) in VNC server code, which allow an attacker to
| read stack memory and can be abused for information disclosure.
| Combined with another vulnerability, it can be used to leak stack
| memory and bypass ASLR. This attack appear to be exploitable via
| network connectivity. These vulnerabilities have been fixed in commit
| d01e1bb4246323ba6fcee3b82ef1faa9b1dac82a.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-15681
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15681

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#943649: marked as done (apparmor ignores errors in debian/rules)

[Debian Bug Tracking System]

Your message dated Tue, 29 Oct 2019 20:56:09 +
with message-id 
and subject line Bug#943649: fixed in apparmor 2.13.3-6
has caused the Debian Bug report #943649,
regarding apparmor ignores errors in debian/rules
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.)


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

Package: src:apparmor
Version: 2.13.3-5
Severity: serious
Tags: sid bullseye

debian/rules has lots of

set -e && 

starting the set in one shell and  in the next one. Please fix all those.
Seen while trying to build for multiple python3 versions.

set -e; 

is the right thing to do.
--- End Message ---
--- Begin Message ---
Source: apparmor
Source-Version: 2.13.3-6

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

Debian distribution maintenance software
pp.
intrigeri  (supplier of updated apparmor 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: Tue, 29 Oct 2019 18:57:51 +
Source: apparmor
Architecture: source
Version: 2.13.3-6
Distribution: unstable
Urgency: medium
Maintainer: Debian AppArmor Team 
Changed-By: intrigeri 
Closes: 943649 943657
Changes:
 apparmor (2.13.3-6) unstable; urgency=medium
 .
   [ Matthias Klose ]
   * debian/rules: ensure "set -e" is honored (Closes: #943649).
   * Add upstream-mr-430-Fix-a-Python-3.8-autoconf-check.patch (Closes: 
#943657).
Checksums-Sha1:
 a10ed3706411b8072e85dccd12eaa6c6f579fc8b 3600 apparmor_2.13.3-6.dsc
 4ee628bac709dd21f0fb6231212b1294a0059837 99260 apparmor_2.13.3-6.debian.tar.xz
Checksums-Sha256:
 a3f89895358fb26161121ffcf7f42ca2a18f49a1c974d77025951acef9b7277a 3600 
apparmor_2.13.3-6.dsc
 4f46952566ca3c996dadc4ef9a56cfe9572c5a7de5fe1e7f9cbce9e6ccd960fd 99260 
apparmor_2.13.3-6.debian.tar.xz
Files:
 29dcd5512499faf389f958608d590b4c 3600 admin optional apparmor_2.13.3-6.dsc
 cb633910a3209ddfc7b29cecb3682d00 99260 admin optional 
apparmor_2.13.3-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEHRt1x6SY9ZXd6PxEAfr306of05kFAl24lsUVHGludHJpZ2Vy
aUBkZWJpYW4ub3JnAAoJEAH699OqH9OZZtMP/3y1euD11kKj9xSJGyskSyS5x6m+
ODBbMIiijcNehn5cQadHpZbvRFRNZHDsHcSeAQBAXPcpUffyvNT0yX7+Vg47pUMK
L/ZugpscE1hELkh1D6WMyu50sr+poweKYwJwGMkN+/pTJMKSjFKETEyjoH8YQnLJ
SnTEhskZjX7yLBUzblE32T79t2ExQekKWEAJq4CclSXYiZzmX9cUzFQchDBmcUad
1Ajx0yqcxKxG0q1erRkQxVdh+0psCXgpeTDKaG6OnwRg7Cmn1aUXxv0SKCt6aJjA
TDshWwJuCJtHuXarTupBnl6IqMP7JNrdbyCht6oK5iMZBfkRD4RaaxA+MWc+Z11G
rZtfuRS6xLXQlt9+if9ScbejQXf5QPntffMdX+1fHG4y7KNlELIlZ6m98IDvUNp+
Om1Dverx/0aqK1AFJTun+p2JZR6qisVfwnkAXOqFO5St4gTaKGnp6SuZApTPf9hM
Ts6wq+qGwcDoCkUS/Fg+njBnUIRG7Mmpe0YIrSiZqYix2F0Dzd7o6av5YquORBFu
zqF3VrXDuQ3IZoYmpbQCbUO1Pu3rRXAcvTqXHnqLvtKZJHbro6N0/TYmi8xoAFxb
fP9DOMvr3fX1pkRB7RwONgDoyGQ6Ky63t7hnZVLKZ7cpTQ/f7b8VWioycsyFBDGn
/Mii6Ue1T161Lt6T
=MWh8
-END PGP SIGNATURE End Message ---

Bug#941018: ibus 1.5.21-1 does not work with qt5 applications

[Gunnar Hjalmarsson]

On 2019-10-27 16:32, Boyuan Yang wrote:

While we are waiting for the response of glib upstream (no response
from glib authors yet), I'd like to mention that current ibus in both
stable-security and Testing/Sid are already broken. With next stable
point release, we would break everyone's ibus whenever they are using
Debian 10. As pointed out in
https://lists.debian.org/debian-input-method/2019/10/msg00047.html ,
there are already some bug reports against qt5-based software.


Simon's glib MR has now been reviewed and committed upstream.

--
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj

Bug#943789: seafile-gui depends on seafile-daemon <= 7.0.2-1 while unstable has 7.0.2-1+b1

[Paul Gevers]

Package: seafile-gui
Version: 7.0.2-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainer,

The source package seafile is part of the nettle transition and got rebuild as
part of it. However the binNMU-ed packages aren't migrating to testing because
it would make seafile-gui uninstallable in testing as seafile-gui has this in
its Depends field:
 seafile-daemon (>= ${source:Upstream-Version}),
 seafile-daemon (<= ${source:Version}),

This relation isn't fullfiled anymore in unstable, making your package
uninstallable. Please fix your Depends relation to be binNMU safe.

Paul

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

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

Versions of packages seafile-gui depends on:
ii  libc62.29-2
ii  libgcc1  1:9.2.1-8
ii  libglib2.0-0 2.62.1-1
ii  libjansson4  2.12-1
ii  libqt5core5a 5.11.3+dfsg1-4
ii  libqt5dbus5  5.11.3+dfsg1-4
ii  libqt5gui5   5.11.3+dfsg1-4
ii  libqt5network5   5.11.3+dfsg1-4
ii  libqt5webenginewidgets5  5.11.3+dfsg-2+b1
ii  libqt5widgets5   5.11.3+dfsg1-4
pn  libquazip5-1 
pn  libseafile0  
pn  libsearpc1   
ii  libsqlite3-0 3.30.1-1
ii  libstdc++6   9.2.1-8
pn  seafile-daemon   

seafile-gui recommends no packages.

Versions of packages seafile-gui suggests:
pn  seafile-cli  

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl24mWkACgkQnFyZ6wW9
dQqDJwgAiysi3vD5oBdLTdlNqDfGjz5TvWc6F9wU67YZTfdeOfmAAj6aljLPWw5F
K3GnQkHqS28V0wkAqqAP4pF6X98W7b51d8lkZDNpuiB2xZniOYERQXWe3gQrXKu3
8bQJ/487u4LesEtW5+ruT/oJJPQ/Sk8c0VsHA8hJdT9xl4o5teJVA7NSJ+dv7poj
qVzBhhBg9laBxOmEeb1VMQJ6bzTJxPU1v63eR8CiNdac4J3Ngi0gNLB5edvBrXR3
s1fwDXEi9hbA5tH/FgTaeg5h40cZoWBE4sZ5Avs8e4wSwLcfIBceskB/YFQHpnZ/
pmIEh/0F4cLKe8hRFqPGWBMoR5Upeg==
=BLKr
-END PGP SIGNATURE-

Bug#943470: marked as done (webext-ublock-origin: Version in stable not working after [DSA 4549-1] firefox-esr security update)

[Debian Bug Tracking System]

Your message dated Tue, 29 Oct 2019 19:51:33 +
with message-id 
and subject line Bug#943470: fixed in ublock-origin 1.22.2+dfsg-1~deb9u1
has caused the Debian Bug report #943470,
regarding webext-ublock-origin: Version in stable not working after [DSA 
4549-1] firefox-esr security update
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.)


-- 
943470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: webext-ublock-origin
Version: 1.18.4+dfsg-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

After updating Firefox in Debian stable ([DSA 4549-1] firefox-esr security
update), I can use Firefox but the ublock origin extension disappeared.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

With a new profile, I still cannot see the extension.
I have tried to remove and reinstall the package (from stable, version
1.18.4+dfsg-2) but it didn't solve the issue.
I have tried to remove the folder storage/default/moz-extension+++whatever as
suggested in 931640, with no luck.

I have installed the version in testing (1.22.2+dfsg-1), and the problem was
solved for new firefox profiles (although it appears disabled). Then, I have
removed the folder "browser-extension-data" of my old profile, and then ublock
origin also appeared in my old profile (and enabled).

I have then tried to remove the testing version (1.22.2+dfsg-1) and reinstall
the stable version (1.18.4+dfsg-2) but the extension disappeared again.

Thanks

-- 
Laura Arjona
https://wiki.debian.org/LauraArjona



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

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

webext-ublock-origin depends on no packages.

Versions of packages webext-ublock-origin recommends:
ii  chromium 76.0.3809.100-1~deb10u1
ii  firefox-esr  68.2.0esr-1~deb10u1

Versions of packages webext-ublock-origin suggests:
pn  ublock-origin-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ublock-origin
Source-Version: 1.22.2+dfsg-1~deb9u1

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated ublock-origin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Oct 2019 17:04:27 +0200
Source: ublock-origin
Binary: xul-ext-ublock-origin chromium-ublock-origin ublock-origin-doc 
webext-ublock-origin
Architecture: source all
Version: 1.22.2+dfsg-1~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Markus Koschany 
Description:
 chromium-ublock-origin - general-purpose lightweight ads, malware, trackers 
blocker (Chrom
 ublock-origin-doc - general-purpose lightweight ads, malware, trackers blocker 
- docu
 webext-ublock-origin - general-purpose lightweight ads, malware, trackers 
blocker (Web E
 xul-ext-ublock-origin - general-purpose lightweight ads, malware, trackers 
blocker
Closes: 925337 943470
Changes:
 ublock-origin (1.22.2+dfsg-1~deb9u1) stretch; urgency=medium
 .
   * Backport of 1.22.2+dfsg-1 to Stretch. (Closes: #943470, #925337)
Checksums-Sha1:
 9af7736bb1eacdc50fdeeb2a3a0b85f6f01d782b 2482 
ublock-origin_1.22.2+dfsg-1~deb9u1.dsc
 3c2b275cab00f2f81703d71100bc88325740b34c 40952 
ublock-origin_1.22.2+dfsg-1~deb9u1.debian.tar.xz
 fb91db0ba4cdf2ea74917b755949c1345a4ff1d5 51660 
chromium-ublock-origin_1.22.2+dfsg-1~deb9u1_all.deb
 e3557d5408524de34732e913d313ebdd8eba5228 5695678 
ublock-origin-doc_1.22.2+dfsg-1~deb9u1_all.deb
 31518f27d46523977681f3803ff875727d8d8205 7558 
ublock-origin_1.22.2+dfsg-1~deb9u1_amd64.buildinfo
 

Bug#925337: marked as done (webext-ublock-origin: deactivated with Firefox 66)

[Debian Bug Tracking System]

Your message dated Tue, 29 Oct 2019 19:51:33 +
with message-id 
and subject line Bug#925337: fixed in ublock-origin 1.22.2+dfsg-1~deb9u1
has caused the Debian Bug report #925337,
regarding webext-ublock-origin: deactivated with Firefox 66
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.)


-- 
925337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: webext-ublock-origin
Version: 1.18.4+dfsg-2
Severity: normal

Dear Markus,

uBlock Origin becomes deactivated with Firefox 66.0-1.

With Firefox ESR 60.6.0esr-1 it works okay.

With Firefox 65 it also worked.

Maybe the extension needs an update.

In Buster AFAIK there will only be Firefox ESR. So there does not seem
to be a need to have an updated version in Buster. But for those users
who use Debian Unstable an updated version in experimental would ne nice.

Thanks,
Martin

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

Kernel: Linux 5.0.0-tp520 (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

webext-ublock-origin depends on no packages.

Versions of packages webext-ublock-origin recommends:
ii  chromium 73.0.3683.75-1
ii  firefox  66.0-1
ii  firefox-esr  60.6.0esr-1

Versions of packages webext-ublock-origin suggests:
ii  ublock-origin-doc  1.18.4+dfsg-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ublock-origin
Source-Version: 1.22.2+dfsg-1~deb9u1

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated ublock-origin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Oct 2019 17:04:27 +0200
Source: ublock-origin
Binary: xul-ext-ublock-origin chromium-ublock-origin ublock-origin-doc 
webext-ublock-origin
Architecture: source all
Version: 1.22.2+dfsg-1~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Markus Koschany 
Description:
 chromium-ublock-origin - general-purpose lightweight ads, malware, trackers 
blocker (Chrom
 ublock-origin-doc - general-purpose lightweight ads, malware, trackers blocker 
- docu
 webext-ublock-origin - general-purpose lightweight ads, malware, trackers 
blocker (Web E
 xul-ext-ublock-origin - general-purpose lightweight ads, malware, trackers 
blocker
Closes: 925337 943470
Changes:
 ublock-origin (1.22.2+dfsg-1~deb9u1) stretch; urgency=medium
 .
   * Backport of 1.22.2+dfsg-1 to Stretch. (Closes: #943470, #925337)
Checksums-Sha1:
 9af7736bb1eacdc50fdeeb2a3a0b85f6f01d782b 2482 
ublock-origin_1.22.2+dfsg-1~deb9u1.dsc
 3c2b275cab00f2f81703d71100bc88325740b34c 40952 
ublock-origin_1.22.2+dfsg-1~deb9u1.debian.tar.xz
 fb91db0ba4cdf2ea74917b755949c1345a4ff1d5 51660 
chromium-ublock-origin_1.22.2+dfsg-1~deb9u1_all.deb
 e3557d5408524de34732e913d313ebdd8eba5228 5695678 
ublock-origin-doc_1.22.2+dfsg-1~deb9u1_all.deb
 31518f27d46523977681f3803ff875727d8d8205 7558 
ublock-origin_1.22.2+dfsg-1~deb9u1_amd64.buildinfo
 4a72ed29ef24caae21252624372d3b7295a4eccd 1607094 
webext-ublock-origin_1.22.2+dfsg-1~deb9u1_all.deb
 5c4f2b3ac710db402b2e17835d982f588e6ecf4f 51638 
xul-ext-ublock-origin_1.22.2+dfsg-1~deb9u1_all.deb
Checksums-Sha256:
 e12b459119d3fbf4a33e888b58d2956ab1ac755e161ea24e5794c72e9cbab584 2482 
ublock-origin_1.22.2+dfsg-1~deb9u1.dsc
 5928e4e129aa113cdbcf83afd735c7bc6d14b839510371683f6e6acf9fd87ab5 40952 
ublock-origin_1.22.2+dfsg-1~deb9u1.debian.tar.xz
 f026c09e4291fda98bd31fa6576bf75fba8f675b7e8d83d69cab32e35703362b 51660 
chromium-ublock-origin_1.22.2+dfsg-1~deb9u1_all.deb
 1bdce7d26d2129e14435e7ec8d2e274a699d5546efdb4ec24479fd2ea86dffd6 

Bug#943470: marked as done (webext-ublock-origin: Version in stable not working after [DSA 4549-1] firefox-esr security update)

[Debian Bug Tracking System]

Your message dated Tue, 29 Oct 2019 19:49:57 +
with message-id 
and subject line Bug#943470: fixed in ublock-origin 1.22.2+dfsg-1~deb10u1
has caused the Debian Bug report #943470,
regarding webext-ublock-origin: Version in stable not working after [DSA 
4549-1] firefox-esr security update
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.)


-- 
943470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: webext-ublock-origin
Version: 1.18.4+dfsg-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

After updating Firefox in Debian stable ([DSA 4549-1] firefox-esr security
update), I can use Firefox but the ublock origin extension disappeared.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

With a new profile, I still cannot see the extension.
I have tried to remove and reinstall the package (from stable, version
1.18.4+dfsg-2) but it didn't solve the issue.
I have tried to remove the folder storage/default/moz-extension+++whatever as
suggested in 931640, with no luck.

I have installed the version in testing (1.22.2+dfsg-1), and the problem was
solved for new firefox profiles (although it appears disabled). Then, I have
removed the folder "browser-extension-data" of my old profile, and then ublock
origin also appeared in my old profile (and enabled).

I have then tried to remove the testing version (1.22.2+dfsg-1) and reinstall
the stable version (1.18.4+dfsg-2) but the extension disappeared again.

Thanks

-- 
Laura Arjona
https://wiki.debian.org/LauraArjona



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

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

webext-ublock-origin depends on no packages.

Versions of packages webext-ublock-origin recommends:
ii  chromium 76.0.3809.100-1~deb10u1
ii  firefox-esr  68.2.0esr-1~deb10u1

Versions of packages webext-ublock-origin suggests:
pn  ublock-origin-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ublock-origin
Source-Version: 1.22.2+dfsg-1~deb10u1

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated ublock-origin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Oct 2019 16:57:24 +0200
Source: ublock-origin
Binary: chromium-ublock-origin ublock-origin-doc webext-ublock-origin 
xul-ext-ublock-origin
Architecture: source all
Version: 1.22.2+dfsg-1~deb10u1
Distribution: buster
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Markus Koschany 
Description:
 chromium-ublock-origin - general-purpose lightweight ads, malware, trackers 
blocker (Chrom
 ublock-origin-doc - general-purpose lightweight ads, malware, trackers blocker 
- docu
 webext-ublock-origin - general-purpose lightweight ads, malware, trackers 
blocker (Web E
 xul-ext-ublock-origin - general-purpose lightweight ads, malware, trackers 
blocker
Closes: 925337 943470
Changes:
 ublock-origin (1.22.2+dfsg-1~deb10u1) buster; urgency=medium
 .
   * Backport of 1.22.2+dfsg-1 to Buster. (Closes: #943470, #925337)
Checksums-Sha1:
 3e8711a40313bc3ff885b1cda0b7aaaf29ec039c 2508 
ublock-origin_1.22.2+dfsg-1~deb10u1.dsc
 3152f7cbb2720671fee4cbdfaad2ecb731f63dd5 39744 
ublock-origin_1.22.2+dfsg-1~deb10u1.debian.tar.xz
 43db4722849c75e72f9bca2804ace072d3df602a 51708 
chromium-ublock-origin_1.22.2+dfsg-1~deb10u1_all.deb
 ade01eeefc4f9ea6ec96f858020092437a869a75 5695664 
ublock-origin-doc_1.22.2+dfsg-1~deb10u1_all.deb
 bbf881fcc351c027c4b14578f551f0831b481ad3 7101 
ublock-origin_1.22.2+dfsg-1~deb10u1_amd64.buildinfo
 

Bug#942830: marked as done (CVE-2019-18218)

[Debian Bug Tracking System]

Your message dated Tue, 29 Oct 2019 19:47:09 +
with message-id 
and subject line Bug#942830: fixed in file 1:5.35-4+deb10u1
has caused the Debian Bug report #942830,
regarding CVE-2019-18218
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.)


-- 
942830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: file
Severity: grave
Tags: security

This was assigned CVE-2019-18218:
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16780
https://github.com/file/file/commit/46a8443f76cec4b41ec736eca396984c74664f84

Cheers,
Moritz

--- End Message ---
--- Begin Message ---
Source: file
Source-Version: 1:5.35-4+deb10u1

We believe that the bug you reported is fixed in the latest version of
file, 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.
Christoph Biedl  (supplier of updated file 
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: Tue, 22 Oct 2019 21:57:17 +0200
Source: file
Binary: file file-dbgsym libmagic-dev libmagic-mgc libmagic1 libmagic1-dbgsym
Architecture: source armel
Version: 1:5.35-4+deb10u1
Distribution: buster-security
Urgency: high
Maintainer: Christoph Biedl 
Changed-By: Christoph Biedl 
Description:
 file   - Recognize the type of data in a file using "magic" numbers
 libmagic-dev - Recognize the type of data in a file using "magic" numbers - 
deve
 libmagic-mgc - File type determination library using "magic" numbers (compiled 
m
 libmagic1  - Recognize the type of data in a file using "magic" numbers - libr
Closes: 942830
Changes:
 file (1:5.35-4+deb10u1) buster-security; urgency=high
 .
   * Cherry-pick commit to restrict the number of CDF_VECTOR elements.
 Closes: #942830 [CVE-2019-18218]
Checksums-Sha1:
 4bed535708f7b2bcaf6a7dcd5e13e339a79b914d 1984 file_5.35-4+deb10u1.dsc
 c9b0ca4143177c785225ffd01bf0d79ad166f98d 643268 file_5.35.orig.tar.xz
 8d153cf634f90a40818f3ecc9abd4ed788530f5e 56264 
file_5.35-4+deb10u1.debian.tar.xz
 121d249785bc6d21579b1ac178afca5715346749 16820 
file-dbgsym_5.35-4+deb10u1_armel.deb
 8fb11ba9166bcc9751a834ff61590ae4e017da42 6695 
file_5.35-4+deb10u1_armel.buildinfo
 38fd942a747001bfc2c287303ea237a35239f940 65608 file_5.35-4+deb10u1_armel.deb
 e96d3ed510f1643d5957d163cd630bd219c97826 120820 
libmagic-dev_5.35-4+deb10u1_armel.deb
 b956d54d68af3f49a03840e869e870958024988c 242244 
libmagic-mgc_5.35-4+deb10u1_armel.deb
 fa7cca2e8a3bc4aa33bee1ca6d3ae479b455db55 199624 
libmagic1-dbgsym_5.35-4+deb10u1_armel.deb
 cdd5804ce7d991c8cf016fc013aa9090bd8c6af1 110732 
libmagic1_5.35-4+deb10u1_armel.deb
Checksums-Sha256:
 d1e2d532fc2cf5cfd947b98152916b28c7a6f2c0d6b5da460dea4bc34ca01607 1984 
file_5.35-4+deb10u1.dsc
 60b5b8bc762d35452c7995f3db7e8a5e2004d736b8763f086585a5b1af57a632 643268 
file_5.35.orig.tar.xz
 7bbb38f82e1d461d923ca9a3bd9691ebca1920d04d2d78199b098c40474e9dcb 56264 
file_5.35-4+deb10u1.debian.tar.xz
 c791064ecfa0a9b943457609d4bdfd24b655e10e1bf2679c61403c26cb8f6ccc 16820 
file-dbgsym_5.35-4+deb10u1_armel.deb
 1cc118796732afcc35b74517075150605c16a454ced330af6b9703f27062be8e 6695 
file_5.35-4+deb10u1_armel.buildinfo
 0d006fbbe917f9d54d600b4c6da8d972c740bbcf4eac46709a3aab444c2b5a91 65608 
file_5.35-4+deb10u1_armel.deb
 ddb1c474fb652e1418c82addce8c9bf847e2474eebf5688c1fad9bb006822ed2 120820 
libmagic-dev_5.35-4+deb10u1_armel.deb
 64a2ffb92a7aece24b691aa7380614e2a9ebf4b21793a0ba3734448f9980c967 242244 
libmagic-mgc_5.35-4+deb10u1_armel.deb
 621420e7f5030f30e0d6356b8a94545c5c9d7dac39a7eeebbed0aad3cad77922 199624 
libmagic1-dbgsym_5.35-4+deb10u1_armel.deb
 fd8f90e34a0c828c10aad4f27755bd034427713a79c237292625b5d3de58670f 110732 
libmagic1_5.35-4+deb10u1_armel.deb
Files:
 09af6654a52f2c86c68bc419368d8f72 1984 utils standard file_5.35-4+deb10u1.dsc
 186a9b910e68547dac02cd2b8579e0b8 643268 utils standard file_5.35.orig.tar.xz
 96bbc2a41c1651524055574d99efad7b 56264 utils standard 
file_5.35-4+deb10u1.debian.tar.xz
 bb5704b3a38297e8067f65915a3cf20a 16820 debug optional 
file-dbgsym_5.35-4+deb10u1_armel.deb
 

Bug#925337: marked as done (webext-ublock-origin: deactivated with Firefox 66)

[Debian Bug Tracking System]

Your message dated Tue, 29 Oct 2019 19:49:57 +
with message-id 
and subject line Bug#925337: fixed in ublock-origin 1.22.2+dfsg-1~deb10u1
has caused the Debian Bug report #925337,
regarding webext-ublock-origin: deactivated with Firefox 66
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.)


-- 
925337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: webext-ublock-origin
Version: 1.18.4+dfsg-2
Severity: normal

Dear Markus,

uBlock Origin becomes deactivated with Firefox 66.0-1.

With Firefox ESR 60.6.0esr-1 it works okay.

With Firefox 65 it also worked.

Maybe the extension needs an update.

In Buster AFAIK there will only be Firefox ESR. So there does not seem
to be a need to have an updated version in Buster. But for those users
who use Debian Unstable an updated version in experimental would ne nice.

Thanks,
Martin

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

Kernel: Linux 5.0.0-tp520 (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

webext-ublock-origin depends on no packages.

Versions of packages webext-ublock-origin recommends:
ii  chromium 73.0.3683.75-1
ii  firefox  66.0-1
ii  firefox-esr  60.6.0esr-1

Versions of packages webext-ublock-origin suggests:
ii  ublock-origin-doc  1.18.4+dfsg-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ublock-origin
Source-Version: 1.22.2+dfsg-1~deb10u1

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated ublock-origin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Oct 2019 16:57:24 +0200
Source: ublock-origin
Binary: chromium-ublock-origin ublock-origin-doc webext-ublock-origin 
xul-ext-ublock-origin
Architecture: source all
Version: 1.22.2+dfsg-1~deb10u1
Distribution: buster
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Markus Koschany 
Description:
 chromium-ublock-origin - general-purpose lightweight ads, malware, trackers 
blocker (Chrom
 ublock-origin-doc - general-purpose lightweight ads, malware, trackers blocker 
- docu
 webext-ublock-origin - general-purpose lightweight ads, malware, trackers 
blocker (Web E
 xul-ext-ublock-origin - general-purpose lightweight ads, malware, trackers 
blocker
Closes: 925337 943470
Changes:
 ublock-origin (1.22.2+dfsg-1~deb10u1) buster; urgency=medium
 .
   * Backport of 1.22.2+dfsg-1 to Buster. (Closes: #943470, #925337)
Checksums-Sha1:
 3e8711a40313bc3ff885b1cda0b7aaaf29ec039c 2508 
ublock-origin_1.22.2+dfsg-1~deb10u1.dsc
 3152f7cbb2720671fee4cbdfaad2ecb731f63dd5 39744 
ublock-origin_1.22.2+dfsg-1~deb10u1.debian.tar.xz
 43db4722849c75e72f9bca2804ace072d3df602a 51708 
chromium-ublock-origin_1.22.2+dfsg-1~deb10u1_all.deb
 ade01eeefc4f9ea6ec96f858020092437a869a75 5695664 
ublock-origin-doc_1.22.2+dfsg-1~deb10u1_all.deb
 bbf881fcc351c027c4b14578f551f0831b481ad3 7101 
ublock-origin_1.22.2+dfsg-1~deb10u1_amd64.buildinfo
 3fa8d65e5c572536e58e0a746ae5daa9252ed236 1606132 
webext-ublock-origin_1.22.2+dfsg-1~deb10u1_all.deb
 bf15d952620694bee3c6e238bb6efa6a11080d63 51708 
xul-ext-ublock-origin_1.22.2+dfsg-1~deb10u1_all.deb
Checksums-Sha256:
 3f7026826a47dad9b2ec02a10111fb7e546fc87815c0b1a5700f057d3a995e46 2508 
ublock-origin_1.22.2+dfsg-1~deb10u1.dsc
 798fc0d08bef30db96819836768704690db47e43e9393afb8129fd25712c6c72 39744 
ublock-origin_1.22.2+dfsg-1~deb10u1.debian.tar.xz
 5a2d7220e8e227ac3669ccce671e86de7a49015b234eccfe6ce62baf45000377 51708 
chromium-ublock-origin_1.22.2+dfsg-1~deb10u1_all.deb
 

Processed: tagging 941522

[Debian Bug Tracking System]

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

> tags 941522 + pending
Bug #941522 [gawk-doc] gawk-doc: build-depend on texlive-plain-generic, not 
obsolete texlive-generic-recommended
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: reassign 943401 to g++-9, found 943401 in 9.2.1-12

[Debian Bug Tracking System]

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

> reassign 943401 g++-9
Bug #943401 [gcc-9] libreoffice C++ Unit tests failing when built with gcc >= 
9.2.1-12 (Failure instantiating exceptionprotector)
Bug reassigned from package 'gcc-9' to 'g++-9'.
No longer marked as found in versions gcc-9/9.2.1-12.
Ignoring request to alter fixed versions of bug #943401 to the same values 
previously set
> found 943401 9.2.1-12
Bug #943401 [g++-9] libreoffice C++ Unit tests failing when built with gcc >= 
9.2.1-12 (Failure instantiating exceptionprotector)
Marked as found in versions gcc-9/9.2.1-12.
> thanks
Stopping processing here.

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

Processed: libreoffice C++ Unit tests failing when built with gcc >= 9.2.1-12 (Failure instantiating exceptionprotector) (was: Re: Bug#943401: libreoffice C++ Unit tests failing since gcc) 9.2.1-12 ((

[Debian Bug Tracking System]

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

> reassign 943401 gcc-9
Bug #943401 [libstdc++6] libreoffice C++ Unit tests failing since 9.2.1-12 
((Failure instantiating exceptionprotector)
Bug reassigned from package 'libstdc++6' to 'gcc-9'.
No longer marked as found in versions gcc-9/9.2.1-12.
Ignoring request to alter fixed versions of bug #943401 to the same values 
previously set
> found 943401 9.2.1-12
Bug #943401 [gcc-9] libreoffice C++ Unit tests failing since 9.2.1-12 ((Failure 
instantiating exceptionprotector)
Marked as found in versions gcc-9/9.2.1-12.
> retitle 943401 libreoffice C++ Unit tests failing when built with gcc >= 
> 9.2.1-12 (Failure instantiating exceptionprotector)
Bug #943401 [gcc-9] libreoffice C++ Unit tests failing since 9.2.1-12 ((Failure 
instantiating exceptionprotector)
Changed Bug title to 'libreoffice C++ Unit tests failing when built with gcc >= 
9.2.1-12 (Failure instantiating exceptionprotector)' from 'libreoffice C++ Unit 
tests failing since 9.2.1-12 ((Failure instantiating exceptionprotector)'.
> thanks
Stopping processing here.

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

Bug#943401: libreoffice C++ Unit tests failing when built with gcc >= 9.2.1-12 (Failure instantiating exceptionprotector) (was: Re: Bug#943401: libreoffice C++ Unit tests failing since gcc) 9.2.1-12 (

[Rene Engelhard]

reassign 943401 gcc-9
found 943401 9.2.1-12
retitle 943401 libreoffice C++ Unit tests failing when built with gcc >= 
9.2.1-12 (Failure instantiating exceptionprotector)
thanks

On Tue, Oct 29, 2019 at 03:09:50PM +0100, Vincent Lefevre wrote:
> 1. Build smoketest with the old g++-9 / libstdc++6.

In testing against 6.3.2 there:

== Starting smoketest with 1 job against 
path:/usr/lib/libreoffice/program/soffice ==
S=/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2 && 
I=/usr/lib/libreoffice && W=$S/workdir &&  touch 
$W/Headers/CppunitTest/libtest_smoketest.so
[CXX] smoketest/smoketest_too.cxx
S=/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2 && 
I=/usr/lib/libreoffice && W=$S/workdir &&  mkdir -p $W/CxxObject/smoketest/ 
$W/Dep/CxxObject/smoketest/ && cd 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2 &&
x86_64-linux-gnu-g++ -DBOOST_ERROR_CODE_HEADER_ONLY 
-DBOOST_SYSTEM_NO_DEPRECATED -DCPPU_ENV=gcc3 -DLINUX -DNDEBUG 
-DOSL_DEBUG_LEVEL=0 -DUNIX -DUNX -DX86_64 -D_FORTIFY_SOURCE=2 -D_PTHREADS 
-D_REENTRANT -Wdate-time   -DCPPUNIT_PLUGIN_EXPORT='extern "C" 
SAL_DLLPUBLIC_EXPORT'   -fvisibility=hidden-Wall -Wno-missing-braces 
-Wnon-virtual-dtor -Wendif-labels -Wextra -Wundef -Wunreachable-code 
-Wunused-macros -finput-charset=UTF-8 -fmessage-length=0 -fno-common -pipe  
-Wno-maybe-uninitialized -Wduplicated-cond -Wlogical-op -Wshift-overflow=2 
-Wunused-const-variable=1 -Wno-cast-function-type -fvisibility-inlines-hidden 
-fPIC -Wshadow -Woverloaded-virtual -std=gnu++2a -pthread   -DEXCEPTIONS_ON 
-fexceptions -fno-enforce-eh-specs -g -O2 
-fdebug-prefix-map=/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2=.
 -fstack-protector-strong -Wformat -Werror=format-security
-DLIBO_INTERNAL_ONLY  -c $S/smoketest/smoketest_too.cxx -o 
$W/CxxObject/smoketest/smoketest_too.o  -I$S/include  
-I/usr/lib/jvm/default-java/include -I/usr/lib/jvm/default-java/include/linux 
-I$S/config_host   -I/usr/include  -I$W/UnoApiHeadersTarget/udkapi/normal 
-I$W/UnoApiHeadersTarget/offapi/normal   
[LNK] CppunitTest/libtest_smoketest.so
S=/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2 && 
I=/usr/lib/libreoffice && W=$S/workdir &&  x86_64-linux-gnu-g++ -pthread 
-shared -Wl,-z,noexecstack   -Wl,-z,origin '-Wl,-rpath,$ORIGIN/../Library' 
-Wl,-rpath-link,$I/program -Wl,-z,defs -Wl,-rpath-link,/lib:/usr/lib 
-Wl,-z,combreloc  -Wl,--hash-style=gnu  -Wl,-Bsymbolic-functions 
-L$W/LinkTarget/StaticLibrary -L$I/sdk/lib  -L$S/instdir/program  
-L$S/instdir/program  -L$W/LinkTarget/Library -Wl,-z,relro
$W/CxxObject/smoketest/smoketest_too.o  -Wl,--start-group-lcppunit   
-Wl,--end-group -Wl,--no-as-needed -luno_cppu -luno_cppuhelpergcc3 -luno_sal 
-lunotest  -o $W/LinkTarget/CppunitTest/libtest_smoketest.so 
TEMPFILE=/tmp/gbuild.ptBn7D &&  mv ${TEMPFILE} 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/LinkTarget/CppunitTest/libtest_smoketest.so.objectlist
rm -rf 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/CustomTarget/smoketest
mkdir -p 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/CustomTarget/smoketest/user
cp 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/qadevOOo/qa/registrymodifications.xcu
 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/CustomTarget/smoketest/user
mkdir -p 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/Zip/
touch 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/Zip/smoketestdoc.prepare
[ZIP] smoketestdoc
S=/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2 && 
I=/usr/lib/libreoffice && W=$S/workdir &&   RESPONSEFILE=/tmp/gbuild.jGkR3E && 
cd $S/smoketest/data && cat ${RESPONSEFILE} | tr "[:space:]" "\n" | zip  -D 
-@rX --filesync --must-match $W/Zip/smoketestdoc.zip && rm -f ${RESPONSEFILE} 
&& touch $W/Zip/smoketestdoc.zip   
  adding: mimetype (stored 0%)
  adding: content.xml (deflated 77%)
  adding: meta.xml (deflated 55%)
  adding: settings.xml (deflated 80%)
  adding: styles.xml (deflated 77%)
  adding: META-INF/manifest.xml (deflated 73%)
  adding: Basic/script-lc.xml (deflated 47%)
  adding: Basic/Standard/script-lb.xml (deflated 52%)
  adding: Basic/Standard/Events.xml (deflated 54%)
  adding: Basic/Standard/Global.xml (deflated 78%)
  adding: Basic/Standard/Test_10er.xml (deflated 80%)
  adding: Basic/Standard/Test_DB.xml (deflated 68%)
  adding: Basic/Standard/Test_Ext.xml (deflated 47%)
  adding: Dialogs/dialog-lc.xml (deflated 47%)
  adding: Dialogs/Standard/dialog-lb.xml (deflated 47%)
  adding: Dialogs/Standard/OptionsDlg.xml (deflated 73%)
cp 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/Zip/smoketestdoc.zip
 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/Zip/smoketestdoc.sxw
[CUT] 

Bug#943732: pandas: test failures on non-Intel

[Rebecca N. Palmer]

and 14 on riscv64, not investigated yet.

Bug#942040: marked as done (tstools: /usr/bin/tsfilter is already provided by opencaster)

[Debian Bug Tracking System]

Your message dated Tue, 29 Oct 2019 18:06:41 +
with message-id 
and subject line Bug#942040: fixed in tstools 1.13~git20151030-2
has caused the Debian Bug report #942040,
regarding tstools: /usr/bin/tsfilter is already provided by opencaster
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.)


-- 
942040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tstools
Version: 1.13~git20151030-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package tstools.
  Preparing to unpack .../tstools_1.13~git20151030-1_amd64.deb ...
  Unpacking tstools (1.13~git20151030-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tstools_1.13~git20151030-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/tsfilter', which is also in package opencaster 
3.2.2+dfsg-1.1+b1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/tstools_1.13~git20151030-1_amd64.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/bin/tsfilter
  usr/share/man/man1/tsfilter.1.gz

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


opencaster=3.2.2+dfsg-1.1+b1_tstools=1.13~git20151030-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: tstools
Source-Version: 1.13~git20151030-2

We believe that the bug you reported is fixed in the latest version of
tstools, 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.
Boyuan Yang  (supplier of updated tstools 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: Tue, 29 Oct 2019 13:30:38 -0400
Source: tstools
Architecture: source
Version: 1.13~git20151030-2
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Boyuan Yang 
Closes: 942040
Changes:
 tstools (1.13~git20151030-2) unstable; urgency=high
 .
   * QA upload.
   * debian/rules: Install tsfilter tool as tsfilter.tstools at
 this moment since tsfilter has already been provided by
 openraster. (Closes: #942040)
   * debian/control: Use "Rules-Requires-Root: no".
Checksums-Sha1:
 43ae38223ba3b3b591cd338b65aceb236ea5238c 1898 tstools_1.13~git20151030-2.dsc
 0ba3a60ea7532b72ede49fd1f69ac16374262e49 11484 
tstools_1.13~git20151030-2.debian.tar.xz
 b8951d460fede3a91b7c2f9e3af62cd6bbb74ccc 5884 
tstools_1.13~git20151030-2_amd64.buildinfo
Checksums-Sha256:
 3ff0ef5f5374e7ceb5c965693aadb6b1837bc00fd7a74b0b84012ff115fbdbe4 1898 
tstools_1.13~git20151030-2.dsc
 a117b534ff2a7aea4c71bef9e13c0af382d0d48b2476b176857789318420f45f 11484 
tstools_1.13~git20151030-2.debian.tar.xz
 29d2225a6cc4ebe825a1091ce21f2ad5ce0291653b989c99c16c1cd210ead34b 5884 

Bug#943649: [pkg-apparmor] Bug#943649: apparmor ignores errors in debian/rules

[intrigeri]

Hi Matthias,

Matthias Klose:
> debian/rules has lots of

>   set -e && 

> starting the set in one shell and  in the next one. Please fix all 
> those.
> Seen while trying to build for multiple python3 versions.

>   set -e; 

> is the right thing to do.

I confess I was not able to reproduce the problem myself: I've tried
inserting "false" in various places where I would naively expect
"set -e" to fail the build, and I did not manage to find a case when
"set -e" did not fail the build.

Still, I'm not good Makefile and I'm very much inclined to trust your
expertise on this front, so I've applied your suggestion (locally for
now).

I would greatly appreciate a practical example in which "set -e &&
" does not behave as I thought it would :)

Thanks!

Cheers,
-- 
intrigeri

Processed: found 943526 in 3.6.2-1

[Debian Bug Tracking System]

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

> found 943526 3.6.2-1
Bug #943526 [node-typescript] node-tslib: directory vs. symlink conflict: 
/usr/share/nodejs/tslib
Marked as found in versions node-typescript/3.6.2-1.
> thanks
Stopping processing here.

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

Processed: limit source to codeblocks, tagging 933407, tagging 886062

[Debian Bug Tracking System]

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

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

> tags 933407 + pending
Bug #933407 [codeblocks] codeblocks: Please rebuild against wxWidgets GTK 3 
package
Added tag(s) pending.
> tags 886062 + pending
Bug #886062 [codeblocks] codeblocks: Please consider updating to codeblocks 
17.12
Ignoring request to alter tags of bug #886062 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: affects 943526

[Debian Bug Tracking System]

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

> affects 943526 node-tslib
Bug #943526 [node-typescript] node-tslib: directory vs. symlink conflict: 
/usr/share/nodejs/tslib
Added indication that 943526 affects node-tslib
> thanks
Stopping processing here.

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

Bug#943776: missing gir1.2-rsvg-2.0 Depends

[Jörg Frings-Fürst]

Package: scour
Version: 0.37-3
Severity: grave
Tags: newcomer

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

build simple-scan produces this errors:

[quote]
Scour processed file "icon.svg" in 32 ms: 7227/14298 bytes new/orig -> 50.5%
Traceback (most recent call last):
  File "/usr/share/scour/cmpsvg", line 13, in 
gi.require_version('Rsvg', '2.0')
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 129, in
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Rsvg not available
dh_scour: scour was not able to process icon.svg
[/quote]


gir1.2-rsvg-2.0 is requested for a proper use of scour.

Please switch them from Suggests to Depends.


CU
Jörg



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

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

Versions of packages scour depends on:
ii  python33.7.5-1
ii  python3-scour  0.37-3

scour recommends no packages.

Versions of packages scour suggests:
ii  gir1.2-rsvg-2.0   2.44.14-1
ii  python3-gi-cairo  3.34.0-1

- -- debconf-show failed

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl24dX8ACgkQCfifPIyh
0l0BERAArLqg1cnc0/g+XnViIMo4RJ+VfELYkjPOppAPGnGducIHzw/ePR0OARw4
5Zfqx5dmvw2KTpC7V9jEp5jSYBmfPdJyqmeilPbs7ED4//Gf4CmK65b+bGZZYJnf
vfebVMUexdrcntiSQzD8WhI7GixPqIum7HA2w8bpTT72t2XhWi9ScfCxpWjRRm1I
W8ByVrvL3Rbx7UmL3SLHrE45Jvw9jajyA+dy9q00ihnIPN9Rj+UTv2SwM9W+3HzF
a9Xt4lrZ1PBdbJLZSyYF/lwf8VWN5tP6A6ohg4LaMQtbQO58517Uf6Iywb9WMhNp
dV36RibB4fcq3is5RGKlCm2fMoZd2a9iMbNqBoW4pYnXR3K/+es4i4zMbjzRtPtb
z95hYH6wwU2dz6oaVE1PXHbaLh/OzXyK1mAav6W3aQaC/h5wqi2VDGUk2PzYWDNv
qO4TfwANqvyD1kwoxkdLYigKiHu3YSGX3dEQd+GPWZA5nQOk4VzSeQx3eWl7Tuvf
ViPf/vrM7WVt6VKv2qbdAIsxrllzpWbUo2C+nvOPz7TltolOPLlJ4w4FEPlZ2Cfh
2ifxMA/Ub8KSbinTpob5FVMx3DdsI3KVPJqel3NzTfcfhHmtoR7bYfd5RoBg8UuU
3ht/upVbBU5rHCjmVSXlvOkd+Xxe0AAJ2rLv1s244oiqueiWQwg=
=4RIn
-END PGP SIGNATURE-

Bug#943437: src:meson: Please update/remove libwxgtk3.0-dev build-dependency

[Jussi Pakkanen]

On Mon, Oct 28, 2019 at 11:15 PM Scott Talbert  wrote:

> The fpga test failure is also occurring with autopkgtest:
> https://ci.debian.net/data/packages/unstable/amd64/m/meson/latest-autopkgtest/log.gz
>
> Jussi also mentioned it.  Perhaps it's related to the recent upload of
> fpga-icestorm?

This is a bug in either yosys or arachne-pnr, I reported it here:

https://github.com/YosysHQ/yosys/issues/1467

Bug#943765: libvtkgdcm3-dev: missing Breaks+Replaces: libvtkgdcm2-dev

[Mathieu Malaterre]

On Tue, Oct 29, 2019 at 3:39 PM Andreas Beckmann  wrote:
>
> Followup-For: Bug #943765
>
> and furthermore libgdcm3-dev is missing breaks+Replaces: libgdcm2-dev
>
>   Preparing to unpack .../libgdcm3-dev_3.0.3-1~exp1_amd64.deb ...
>   Unpacking libgdcm3-dev (3.0.3-1~exp1) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/libgdcm3-dev_3.0.3-1~exp1_amd64.deb (--unpack):
>trying to overwrite '/usr/lib/x86_64-linux-gnu/libgdcmCommon.so', which is 
> also in package libgdcm2-dev 2.8.8-9+b1
>   Errors were encountered while processing:
>/var/cache/apt/archives/libgdcm3-dev_3.0.3-1~exp1_amd64.deb

I believe this is the right time to finally kill libgdcm2-dev. Just
like what was done for dcmtk, time is now to releave a libgdcm-dev
package and get rid of this issue forever.

As a side note libgdcm3-dev, should really be libgdcm3.0-dev, since
SOVERSION is 3.0. I belive this is mandated in the dev reference
handbook.

2cts

Processed: Re: Processed: Re: gri: FTBFS: Malformed UTF-8 character (fatal) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364.

[Debian Bug Tracking System]

Processing control commands:

> affects 941557 - src:maxima-sage
Bug #941557 [src:gri] texi file need @documentencoding
Removed indication that 941557 affects src:maxima-sage

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

Bug#941557: Processed: Re: gri: FTBFS: Malformed UTF-8 character (fatal) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364.

[Tobias Hansen]

Control: affects 941557 - src:maxima-sage

Thanks for providing the solution for the problem!

Best,
Tobias

On 10/29/19 2:24 PM, Norbert Preining wrote:
> reassign 941557 src:gri
> tags 941557 + patch
> retitle 941557 texi file need @documentencoding
> thanks
> 
> With texinfo 6.7 finally the default encoding is UTF-8, thus gri.texi
> fails to compile since it is in ISO-8859-1. If files in other encodings
> are to be translated @documentencoding needs to be used - this has been
> the case since ... version 6.0 or so (?).
> 
> Please add
>   @documentencoding ISO-8859-1
> after the 
>   \input texinfo
> so that it reads
>   \input texinfo
>   @documentencoding ISO-8859-1
> to fix it.
> 
> Thanks
> 
> Norbert
> 
> --
> PREINING Norbert   http://www.preining.info
> Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
> GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
> 

Bug#940207: marked as done (python3-zc.buildout: missing Breaks+Replaces: python-zc.buildout)

[Debian Bug Tracking System]

Your message dated Tue, 29 Oct 2019 14:53:44 +
with message-id 
and subject line Bug#940207: fixed in zc.buildout 2.13.2-4
has caused the Debian Bug report #940207,
regarding python3-zc.buildout: missing Breaks+Replaces: python-zc.buildout
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.)


-- 
940207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-zc.buildout
Version: 2.13.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...):

  Selecting previously unselected package python3-zc.buildout.
  Preparing to unpack .../python3-zc.buildout_2.13.2-3_all.deb ...
  Unpacking python3-zc.buildout (2.13.2-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-zc.buildout_2.13.2-3_all.deb (--unpack):
   trying to overwrite '/usr/bin/buildout', which is also in package 
python-zc.buildout 1.7.1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-zc.buildout_2.13.2-3_all.deb


cheers,

Andreas


python-zc.buildout=1.7.1-1_python3-zc.buildout=2.13.2-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: zc.buildout
Source-Version: 2.13.2-4

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated zc.buildout 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, 29 Oct 2019 15:02:49 +0100
Source: zc.buildout
Architecture: source
Version: 2.13.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Thomas Goirand 
Closes: 940207
Changes:
 zc.buildout (2.13.2-4) unstable; urgency=medium
 .
   * Add missing Breaks+Replaces: python-zc.buildout (Closes: #940207).
Checksums-Sha1:
 24ae670592dbf451a768f396bfba73b0583ec0b9 1876 zc.buildout_2.13.2-4.dsc
 5c24c4d0c953bcb99def3f245900d695fdfdae8a 4168 
zc.buildout_2.13.2-4.debian.tar.xz
 26f695e56a692f4f77bf539e0aeae7b706c1c002 5999 
zc.buildout_2.13.2-4_amd64.buildinfo
Checksums-Sha256:
 3736b58ce6021b6449bde743700e9dd86074110e67b5640043b6ea4aad833f1b 1876 
zc.buildout_2.13.2-4.dsc
 a170844cc67f3232d4e269247cc879a2e704278a0c7a45fc0c9c37cc6522e917 4168 
zc.buildout_2.13.2-4.debian.tar.xz
 4cfd54793c9b46c7657b65419cb7ac7bebd6d16ad1d08817bd6a7ef4bec2b090 5999 
zc.buildout_2.13.2-4_amd64.buildinfo
Files:
 3e90bfcb3cc3afa86275a290ec355304 1876 zope optional zc.buildout_2.13.2-4.dsc
 aeb3795b8101228868b6a1c762707bad 4168 zope optional 
zc.buildout_2.13.2-4.debian.tar.xz
 c1ee75d53e57e08ef129c5d0d014206d 5999 zope optional 
zc.buildout_2.13.2-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl24R5oACgkQ1BatFaxr
Q/7R7Q/9HTa6Twytk6Fdg7zJehCH9vB1GvJbiOZn3mJPxK0lf5z76XTejgisrZyQ
35k86PIZq0W6jCc++8C36RDxvaztNzAMy/F4DICtPtrUCv44fSC8JwnKf/z1oQaY
HXVrf4bjLoQ5rTSVJ5fb327iaIx1xYlpFV4vqZ27ZVwc5HTStC1YuoWfc6jc44Um
yi+4odJ/3Fb0SjO9FDel35BYci9jeHudjGxOTAVkpjAXTgU7VF0T3/aPou/4cyDm
7Xlctim+bWFLzfjBtHxkDDQkQHTGkheLRDtW4B4S2TjucHZYQ4d/6FpQ4qL8zSzl
ENV9uV/rPUUeBzJMNCyL6+AcZ6NLxgUo1SuGTsnfzCZGnOdL+YStdCJFA6gID9dY
Qi17ECXs6T7X3ilbD4UjMGy/9jfM+WESrLhHduBRdAseeiZ+VhTXxHzQBxNPfSxv
sA6vNGKc6Tm/11bNmJCHaeqd+JtexonPCjTiaA2jtWK+Qgf4OD4qpiLGbBNWaawq
GGMCGAtFS0Bc+pjwvS3SGMeRx9Su0sVZiHrb5YLBdE29SIGPZ/LDZmMD2/wH2MyX
m4XcaCDsJQK0MIxV4FSKEZvvARSVtmeNy8J3AM5dBXTK7Pa75aiX5pjUUFMKVKhc
gFdyF0VRy3Df6gY2jZV9NkbJfP2clpZla/esxDJwZRlVE263Mgo=
=s3w3
-END PGP SIGNATURE End Message ---

Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)

[rene . engelhard]

Hi,

Am 29. Oktober 2019 15:09:50 MEZ schrieb Vincent Lefevre :
>On 2019-10-29 13:09:46 +0100, rene.engelh...@mailbox.org wrote:
>> Am 29. Oktober 2019 12:49:44 MEZ schrieb Vincent Lefevre
>:
>> >In case makefile magic triggers some rebuild, you can also run the
>> >generated executable directly (with the right environment variables,
>> >in case this matters). If the programs honors the system ABI, this
>> >is allowed, and you'll effectively test the new libstdc++6.
>> 
>> No, if the rebuild rebuilds cppunittester or one of the
>> exceptionprotectors or the smoketest so or similar we are at the
>> same situation as with the autopkgtest (that's what it builds) and
>> are not sure whether it's g++-9 or libstdc++6. Neither LO nor the
>> test are an executable it's a executable with gazillions of .sos.
>
>I meant running the generated program (smoketest) without rebuilding
>it:

Smoketest is not a program but also a libsmoketest.so "ran" by cppunittester.

>1. Build smoketest with the old g++-9 / libstdc++6.
>2. Upgrade g++-9 / libstdc++6.
>3. Run smoketest directly.

That would need to copy the longish command from the old log, but yeah.

>(I assume that the smoketest executable does not invoke g++-9 to
>rebuild things on the fly.)

No, but make check in smokest might rebuild stuff. That was what I was aiming 
at. This already happens in "normal" builds.

Regards

Rene

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

Bug#943765: libvtkgdcm3-dev: missing Breaks+Replaces: libvtkgdcm2-dev

[Andreas Beckmann]

Followup-For: Bug #943765

and furthermore libgdcm3-dev is missing breaks+Replaces: libgdcm2-dev

  Preparing to unpack .../libgdcm3-dev_3.0.3-1~exp1_amd64.deb ...
  Unpacking libgdcm3-dev (3.0.3-1~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgdcm3-dev_3.0.3-1~exp1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libgdcmCommon.so', which is 
also in package libgdcm2-dev 2.8.8-9+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/libgdcm3-dev_3.0.3-1~exp1_amd64.deb


Andreas

Bug#943767: yotta: FTBFS

[Thomas Goirand]

Source: yotta
Version: 0.19.0-1
Severity: serious

Hi,

Your package fails to build in Sid since the upload of SQLAlchemy 1.3.5:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
python3 setup.py egg_info
running egg_info
creating yotta.egg-info
writing yotta.egg-info/PKG-INFO
writing dependency_links to yotta.egg-info/dependency_links.txt
writing requirements to yotta.egg-info/requires.txt
writing top-level names to yotta.egg-info/top_level.txt
writing manifest file 'yotta.egg-info/SOURCES.txt'
reading manifest file 'yotta.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'yotta.egg-info/SOURCES.txt'
HOME=/tmp/ PYTHONPATH=/<> nosetests3 -s -v \
--where=yotta/test \
--exclude=test_git_access.py \
--exclude=test_github_access.py \
--exclude=test_hg_access.py \
--exclude=test_vcs.py \
--exclude=test_account.py \
--exclude=test_build.py \
--exclude=test_debug.py \
--exclude=test_install.py \
--exclude=test_link.py \
--exclude=test_minversion.py \
--exclude=test_outdated.py \
--exclude=test_owners.py \
--exclude=test_publish.py \
--exclude=test_search.py \
--exclude=test_shrinkwrap.py \
--exclude=test_start.py \
--exclude=test_target.py \
--exclude=test_test.py \
--exclude=test_update.py \
--exclude=test_version.py
testUnlinkModule (yotta.test.cli.test_unlink.TestCLIUnLink) ... ok
testUnlinkModuleGlobally (yotta.test.cli.test_unlink.TestCLIUnLink) ... ok
testUnlinkNonexistentModule (yotta.test.cli.test_unlink.TestCLIUnLink) ... ok
testUnlinkNonexistentTarget (yotta.test.cli.test_unlink.TestCLIUnLink) ... ok
testUnlinkNotLinkedModuleGlobally (yotta.test.cli.test_unlink.TestCLIUnLink) 
... ok
testUnlinkNotLinkedTargetGlobally (yotta.test.cli.test_unlink.TestCLIUnLink) 
... ok
testUnlinkTarget (yotta.test.cli.test_unlink.TestCLIUnLink) ... ok
testUnlinkTargetGlobally (yotta.test.cli.test_unlink.TestCLIUnLink) ... ok
test_moduleConfigIgnored (yotta.test.test_config.ConfigTest) ... ERROR
test_targetAppConfigMerge (yotta.test.test_config.ConfigTest) ... ERROR
test_targetConfigMerge (yotta.test.test_config.ConfigTest) ... ERROR
test_absolute_ignores (yotta.test.test_ignores.TestPackIgnores) ... ok
test_build (yotta.test.test_ignores.TestPackIgnores) ... SKIP: No network access
test_comments (yotta.test.test_ignores.TestPackIgnores) ... ok
test_default_ignores (yotta.test.test_ignores.TestPackIgnores) ... ok
test_glob_ignores (yotta.test.test_ignores.TestPackIgnores) ... ok
test_relative_ignores (yotta.test.test_ignores.TestPackIgnores) ... ok
test_test (yotta.test.test_ignores.TestPackIgnores) ... SKIP: No network access
test_envvars (yotta.test.test_settings.TestSettings) ... ok
test_merging (yotta.test.test_settings.TestSettings) ... ok
test_setting (yotta.test.test_settings.TestSettings) ... ok
test_writing (yotta.test.test_settings.TestSettings) ... ok
test_GitRefs (yotta.test.test_sourceparse.TestParseModuleNameAndSpec) ... ok
test_GithubRefs (yotta.test.test_sourceparse.TestParseModuleNameAndSpec) ... ok
test_HGRefs (yotta.test.test_sourceparse.TestParseModuleNameAndSpec) ... ok
test_ShorthandRefs (yotta.test.test_sourceparse.TestParseModuleNameAndSpec) ... 
ok
test_atVersion (yotta.test.test_sourceparse.TestParseModuleNameAndSpec) ... ok
test_validNames (yotta.test.test_sourceparse.TestParseModuleNameAndSpec) ... ok
test_gitURLs (yotta.test.test_sourceparse.TestParseSourceURL) ... ok
test_githubURLs (yotta.test.test_sourceparse.TestParseSourceURL) ... ok
test_hgURLs (yotta.test.test_sourceparse.TestParseSourceURL) ... ok
test_invalid (yotta.test.test_sourceparse.TestParseSourceURL) ... ok
test_registryURLs (yotta.test.test_sourceparse.TestParseSourceURL) ... ok
test_shorthandURLs (yotta.test.test_sourceparse.TestParseSourceURL) ... ok
test_moduleFromDirname 
(yotta.test.test_test_subcommand.TestTestSubcommandModule) ... ok
test_componentNameCoerced (yotta.test.test_validation.TestValidation) ... ok
test_looksLikeAnEmail (yotta.test.test_validation.TestValidation) ... ok
test_validateSourceDirNames (yotta.test.test_validation.TestValidation) ... ok
test_validateSourceDirSuggestions (yotta.test.test_validation.TestValidation) 
... ok
test_hash (yotta.test.test_versions.VersionTestCase) ... ok
test_matches (yotta.test.test_versions.VersionTestCase) ... ERROR

==
ERROR: test_moduleConfigIgnored (yotta.test.test_config.ConfigTest)

Bug#943764: php7.3: CVE-2019-11043

[Salvatore Bonaccorso]

Source: php7.3
Version: 7.3.10-1
Severity: grave
Tags: security upstream
Justification: user security hole
Control: fixed -1 7.3.11-1~deb10u1

Hi,

The following vulnerability was published for php7.3, but this is mant
basically just as tracking item for stable -> testing updates as
DSA-4553-1 with 7.3.11-1~deb10u1 fixing this issue in stable to have
it at some point in testing. That said php7.3 is anyway specially
handled.

CVE-2019-11043[0]:
| In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below
| 7.3.11 in certain configurations of FPM setup it is possible to cause
| FPM module to write past allocated buffers into the space reserved for
| FCGI protocol data, thus opening the possibility of remote code
| execution.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-11043
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11043

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: php7.3: CVE-2019-11043

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 7.3.11-1~deb10u1
Bug #943764 [src:php7.3] php7.3: CVE-2019-11043
Marked as fixed in versions php7.3/7.3.11-1~deb10u1.

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

Bug#943765: libvtkgdcm3-dev: missing Breaks+Replaces: libvtkgdcm2-dev

[Andreas Beckmann]

Package: libvtkgdcm3-dev
Version: 3.0.3-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' 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 .../libvtkgdcm3-dev_3.0.3-1~exp1_amd64.deb ...
  Unpacking libvtkgdcm3-dev (3.0.3-1~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libvtkgdcm3-dev_3.0.3-1~exp1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libvtkgdcm.so', which is also 
in package libvtkgdcm2-dev 2.8.8-9+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/libvtkgdcm3-dev_3.0.3-1~exp1_amd64.deb


cheers,

Andreas


libvtkgdcm2-dev=2.8.8-9+b1_libvtkgdcm3-dev=3.0.3-1~exp1.log.gz
Description: application/gzip

Processed: python3-jaraco.itertools,python3-jaraco.functools: both ship /usr/lib/python3/dist-packages/jaraco/__init__.py

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.0-1
Bug #943763 [python3-jaraco.itertools,python3-jaraco.functools] 
python3-jaraco.itertools,python3-jaraco.functools: both ship 
/usr/lib/python3/dist-packages/jaraco/__init__.py
There is no source info for the package 'python3-jaraco.itertools' at version 
'2.0-1' with architecture ''
Marked as found in versions python-jaraco.functools/2.0-1.
> found -1 2.0.1-4
Bug #943763 [python3-jaraco.itertools,python3-jaraco.functools] 
python3-jaraco.itertools,python3-jaraco.functools: both ship 
/usr/lib/python3/dist-packages/jaraco/__init__.py
There is no source info for the package 'python3-jaraco.functools' at version 
'2.0.1-4' with architecture ''
Marked as found in versions jaraco.itertools/2.0.1-4.

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

Bug#943763: python3-jaraco.itertools,python3-jaraco.functools: both ship /usr/lib/python3/dist-packages/jaraco/__init__.py

[Andreas Beckmann]

Package: python3-jaraco.itertools,python3-jaraco.functools
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 2.0-1
Control: found -1 2.0.1-4

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Preparing to unpack .../python3-jaraco.functools_2.0-1_all.deb ...
  Unpacking python3-jaraco.functools (2.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-jaraco.functools_2.0-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/jaraco/__init__.py', 
which is also in package python3-jaraco.itertools 2.0.1-4
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-jaraco.functools_2.0-1_all.deb

cheers,

Andreas


python3-jaraco.itertools=2.0.1-4_python3-jaraco.functools=2.0-1.log.gz
Description: application/gzip

Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)

[Vincent Lefevre]

On 2019-10-29 13:09:46 +0100, rene.engelh...@mailbox.org wrote:
> Am 29. Oktober 2019 12:49:44 MEZ schrieb Vincent Lefevre :
> >In case makefile magic triggers some rebuild, you can also run the
> >generated executable directly (with the right environment variables,
> >in case this matters). If the programs honors the system ABI, this
> >is allowed, and you'll effectively test the new libstdc++6.
> 
> No, if the rebuild rebuilds cppunittester or one of the
> exceptionprotectors or the smoketest so or similar we are at the
> same situation as with the autopkgtest (that's what it builds) and
> are not sure whether it's g++-9 or libstdc++6. Neither LO nor the
> test are an executable it's a executable with gazillions of .sos.

I meant running the generated program (smoketest) without rebuilding
it:

1. Build smoketest with the old g++-9 / libstdc++6.
2. Upgrade g++-9 / libstdc++6.
3. Run smoketest directly.

(I assume that the smoketest executable does not invoke g++-9 to
rebuild things on the fly.)

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#926997: marked as done (mistral-dashboard: FTBFS: TypeError: 'Cell' object is not subscriptable)

[Debian Bug Tracking System]

Your message dated Tue, 29 Oct 2019 14:55:40 +0100
with message-id 
and subject line Closing bug
has caused the Debian Bug report #926997,
regarding mistral-dashboard: FTBFS: TypeError: 'Cell' object is not 
subscriptable
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.)


-- 
926997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mistral-dashboard
Version: 8.0.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

mistral-dashboard/experimental FTBFS with

ERROR: test_index (mistraldashboard.tasks.tests.TasksTest)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 882, in 
_resolve_lookup
current = current[bit]
TypeError: 'Cell' object is not subscriptable

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/build/mistral-dashboard-8.0.0/mistraldashboard/tasks/tests.py", line 
28, in test_index
res = self.client.get(INDEX_URL)
  File "/usr/lib/python3/dist-packages/django/test/client.py", line 536, in get
**extra)
  File "/usr/lib/python3/dist-packages/django/test/client.py", line 340, in get
return self.generic('GET', path, secure=secure, **r)
  File "/usr/lib/python3/dist-packages/django/test/client.py", line 416, in 
generic
return self.request(**r)
[removel several pages of traceback]
  File "/usr/lib/python3/dist-packages/horizon/tables/base.py", line 873, in 
get_default_classes
if not self.url:
  File "/usr/lib/python3/dist-packages/horizon/tables/base.py", line 836, in url
url = self.column.get_link_url(self.datum)
  File "/build/mistral-dashboard-8.0.0/mistraldashboard/tasks/tables.py", line 
51, in get_link_url
if datum.type == "ACTION":
AttributeError: 'Task' object has no attribute 'type'


Hint: if you do source-only uploads (unless you have to get something
through NEW), you should be able to run into these errors earlier on
the buildds.


Andreas


mistral-dashboard_8.0.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
closing bug--- End Message ---

Bug#941513: c-graph: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended

[Adrienne G. Thompson]

Hi Steve:

I've been tied up with dealing with the ongoing attacks against RMS and the
GNU project. I'll deal with the build dependency problem over the next few
days.

Cheers
Adrienne

On Tue, Oct 1, 2019 at 2:00 PM Steve Langasek 
wrote:

> Package: c-graph
> Version: 2.0.1-3.1
> Severity: serious
> Tags: patch
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu eoan ubuntu-patch
>
> Hi Adrienne,
>
> The texlive-generic-recommended transitional package has been dropped from
> texlive-base in sid.  Please update your build-dependency to
> texlive-plain-generic instead.
>
> --
> 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
>


-- 
Freedom - no pane, all gaiGN!

GNU C-Graph - http://www.gnu.org/software/c-graph
Code Art Now - http://codeartnow.com
Abertheid Campaign - http://www.abertheid.info
Follow me on Twitter @AdrienneGT @GNUcgraph

Processed: Re: Processed: Re: gri: FTBFS: Malformed UTF-8 character (fatal) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364.

[Debian Bug Tracking System]

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

> reassign 941557 src:gri
Bug #941557 [src:texinfo] texinfo: Malformed UTF-8 character in ParserNonXS.pm
Bug reassigned from package 'src:texinfo' to 'src:gri'.
No longer marked as found in versions texinfo/6.7.0.dfsg.2-5.
Ignoring request to alter fixed versions of bug #941557 to the same values 
previously set
> tags 941557 + patch
Bug #941557 [src:gri] texinfo: Malformed UTF-8 character in ParserNonXS.pm
Added tag(s) patch.
> retitle 941557 texi file need @documentencoding
Bug #941557 [src:gri] texinfo: Malformed UTF-8 character in ParserNonXS.pm
Changed Bug title to 'texi file need @documentencoding' from 'texinfo: 
Malformed UTF-8 character in ParserNonXS.pm'.
> thanks
Stopping processing here.

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

Processed: Re: gri: FTBFS: Malformed UTF-8 character (fatal) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364.

[Debian Bug Tracking System]

Processing control commands:

> reassign 941557 src:texinfo 6.7.0.dfsg.2-5
Bug #941557 [src:gri] gri: FTBFS: Malformed UTF-8 character (fatal) at 
/usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364.
Bug reassigned from package 'src:gri' to 'src:texinfo'.
No longer marked as found in versions gri/2.12.26-1.
Ignoring request to alter fixed versions of bug #941557 to the same values 
previously set
Bug #941557 [src:texinfo] gri: FTBFS: Malformed UTF-8 character (fatal) at 
/usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364.
Marked as found in versions texinfo/6.7.0.dfsg.2-5.
> affects 941557 + src:gri src:maxima-sage
Bug #941557 [src:texinfo] gri: FTBFS: Malformed UTF-8 character (fatal) at 
/usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364.
Added indication that 941557 affects src:gri and src:maxima-sage
> retitle 941557 texinfo: Malformed UTF-8 character in ParserNonXS.pm
Bug #941557 [src:texinfo] gri: FTBFS: Malformed UTF-8 character (fatal) at 
/usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364.
Changed Bug title to 'texinfo: Malformed UTF-8 character in ParserNonXS.pm' 
from 'gri: FTBFS: Malformed UTF-8 character (fatal) at 
/usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364.'.

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

Bug#941557: gri: FTBFS: Malformed UTF-8 character (fatal) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364.

[Tobias Hansen]

Control: reassign 941557 src:texinfo 6.7.0.dfsg.2-5
Control: affects 941557 + src:gri src:maxima-sage
Control: retitle 941557 texinfo: Malformed UTF-8 character in ParserNonXS.pm

This is probably a bug in texinfo, since both the program giving the error 
(makeinfo) and the file it is complaining about (ParserNonXS.pm) are part of 
texinfo. The same error also causes maxima-sage to FTBFS at the moment. 
maxima-sage builds without changes when using texinfo from stable which is 
6.5.0.dfsg.1-4, so this is a regression.

Best,
Tobias

On Tue, 1 Oct 2019 15:49:30 -0700 Steve Langasek  
wrote:
> Source: gri
> Version: 2.12.26-1
> Severity: serious
> Justification: FTBFS
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu eoan
> 
> Hi Peter,
> 
> The gri package appears to fail to build from source in unstable:
> 
> [...]
> cd tst_suite ; make
> make[2]: Entering directory '/tmp/gri-2.12.26/doc/tst_suite'
> perl ./../gri2html tst_IO.gri tst_IO.html
> perl ./../gri2html tst_control.gri tst_control.html
> perl ./../gri2html tst_rpn.gri tst_rpn.html
> perl ./../gri2html tst_var_syn.gri tst_var_syn.html
> make[2]: Leaving directory '/tmp/gri-2.12.26/doc/tst_suite'
> makeinfo   -I. gri.texi
> utf8 "\xF3" does not map to Unicode at 
> /usr/share/texinfo/Texinfo/ParserNonXS.pm line 1796,  line 19280.
> Malformed UTF-8 character: \xf3\x70\x65\x7a (unexpected non-continuation byte 
> 0x70, immediately after start byte 0xf3; need 4 bytes, got 1) in pattern 
> match (m//) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364.
> Malformed UTF-8 character (fatal) at 
> /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364.
> make[1]: *** [Makefile:975: html] Error 25
> make[1]: Leaving directory '/tmp/gri-2.12.26/doc'
> make: *** [debian/rules:83: build-indep] Error 2
> dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
> debuild: fatal error at line 1182:
> dpkg-buildpackage -us -uc -ui -b failed
> [...]
> 
> -- 
> 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

Bug#943761: python3-nototools: fails to install: Sorry: IndentationError: unexpected indent (lint_cmap_reqs.py, line 56)

[Andreas Beckmann]

Package: python3-nototools
Version: 0.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up python3-nototools (0.2.0-1) ...
  Sorry: IndentationError: unexpected indent (lint_cmap_reqs.py, line 56)
  dpkg: error processing package python3-nototools (--configure):
   installed python3-nototools package post-installation script subprocess 
returned error exit status 1
  Processing triggers for libc-bin (2.29-2) ...
  Errors were encountered while processing:
   python3-nototools


cheers,

Andreas

Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)

[rene . engelhard]

Hi,

Am 29. Oktober 2019 12:49:44 MEZ schrieb Vincent Lefevre :
>In case makefile magic triggers some rebuild, you can also run the
>generated executable directly (with the right environment variables,
>in case this matters). If the programs honors the system ABI, this
>is allowed, and you'll effectively test the new libstdc++6.

No, if the rebuild rebuilds cppunittester or one of the exceptionprotectors or 
the smoketest so or similar we are at the same situation as with the 
autopkgtest (that's what it builds) and are not sure whether it's g++-9 or 
libstdc++6. Neither LO nor the test are an executable it's a executable with 
gazillions of .sos.

Regards

Rene

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)

[Vincent Lefevre]

On 2019-10-29 11:52:55 +0100, rene.engelh...@mailbox.org wrote:
> Hi again,
> 
> Am 29. Oktober 2019 11:26:41 MEZ schrieb rene.engelh...@mailbox.org:
> >Hi,
> >
> >Am 29. Oktober 2019 10:59:07 MEZ schrieb Vincent Lefevre
> >:
> >> If you build LO
> >>with an older gcc-9 version, upgrade libstdc++6, and run the test
> >>again (without rebuilding it), does it fail?
> >
> >This is impossible. This is a C++ unit test and the stuff assumes too
> >much of the build tree. You need to actually build the test libs etc to
> >run it. 
> >
> >That is why autopkgtest does only smoketest [...]
> 
> Well, thinking about it it might be possible. Build on testing,
> debian/tests/smoketest, dist-upgrade to did and rerun it and hope
> some makefile magic doesn't trigger some rebuild...

In case makefile magic triggers some rebuild, you can also run the
generated executable directly (with the right environment variables,
in case this matters). If the programs honors the system ABI, this
is allowed, and you'll effectively test the new libstdc++6.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: Re: [Pkg-javascript-devel] Bug#943526: node-tslib: directory vs. symlink conflict: /usr/share/nodejs/tslib

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 node-typescript
Bug #943526 [node-tslib] node-tslib: directory vs. symlink conflict: 
/usr/share/nodejs/tslib
Bug reassigned from package 'node-tslib' to 'node-typescript'.
No longer marked as found in versions node-tslib/1.10.0-2.
Ignoring request to alter fixed versions of bug #943526 to the same values 
previously set

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

Bug#943526: [Pkg-javascript-devel] Bug#943526: node-tslib: directory vs. symlink conflict: /usr/share/nodejs/tslib

[Xavier]

Control: reassign -1 node-typescript

Le 29/10/2019 à 08:29, Julien Puydt a écrit :
> Le mardi 29 octobre 2019 à 07:49 +0100, Xavier a écrit :
>> Hi JS team,
>>
>> why did node-typescript have such link ?
>>
>>   /usr/share/nodejs/tslib -> typescript/lib
>>
>> This creates this conflict.
>>
> 
> Well, isn't node-typescript supposed to provide that lib?
> 
> JP

When installing using `npm install typescript`, there is no
"node_modules/tslib", so there is no reason to provide such link IMO.

Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)

[rene . engelhard]

Hi again,

Am 29. Oktober 2019 11:26:41 MEZ schrieb rene.engelh...@mailbox.org:
>Hi,
>
>Am 29. Oktober 2019 10:59:07 MEZ schrieb Vincent Lefevre
>:
>> If you build LO
>>with an older gcc-9 version, upgrade libstdc++6, and run the test
>>again (without rebuilding it), does it fail?
>
>This is impossible. This is a C++ unit test and the stuff assumes too
>much of the build tree. You need to actually build the test libs etc to
>run it. 
>
>That is why autopkgtest does only smoketest [...]

Well, thinking about it it might be possible. Build on testing, 
debian/tests/smoketest, dist-upgrade to did and rerun it and hope some makefile 
magic doesn't trigger some rebuild...

The smokest (except the cppunit blurb)  just does "run lo, open 
smoketestdoc.sxw, run some macros to test basic stuff".

Will try...

Regards

Rene

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)

[rene . engelhard]

Hi,

Am 29. Oktober 2019 10:59:07 MEZ schrieb Vincent Lefevre :
> If you build LO
>with an older gcc-9 version, upgrade libstdc++6, and run the test
>again (without rebuilding it), does it fail?

This is impossible. This is a C++ unit test and the stuff assumes too much of 
the build tree. You need to actually build the test libs etc to run it. 

That is why autopkgtest does only smoketest instead of all c++ unit tests even 
though the latter would be helpful.
Tried to decouple it once but failed as it always either wanted something 
present it write in the "instdir".

Regards

Rene

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)

[Vincent Lefevre]

On 2019-10-28 23:34:11 +0100, Rene Engelhard wrote:
> You like to make other people bad where this is not the case. In this
> case this is not a LO bug since the exact same LO version worked until
> said gcc upload.

If the LO code has some undefined behavior, it could also be a LO bug
triggered by some new optimization or other change in the compiler.

That said, when seeing a new failure with a new GCC version for MPFR,
in (almost) all cases, this was due to a bug in GCC (after I spent
some time to build a simple testcase). But note that I also test MPFR
with sanitizer options, so that if there is some UB in MPFR, I would
probably notice it first.

I notice that this bug is assigned to libstdc++6. Do you think that
it is a library issue rather than a compiler issue? If you build LO
with an older gcc-9 version, upgrade libstdc++6, and run the test
again (without rebuilding it), does it fail?

If this is due to the compilation step, I would suggest to check LO
with sanitizer options. I also notice that the logs show the that
-fno-enforce-eh-specs option is used, which might also hide issues,
I suppose.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#922587: FTBFS against opencv 4.0.1 (exp)

[Ying-Chun Liu (PaulLiu)]

Hi all,


It is not easy to fix this bug. Change pkg-config to use opencv4 doesn't
solve the problem.

We actually need to port this package to opencv 4.

And I believe that the upstream of this package doesn't have the will to
do that.

The successor seems to be https://www.npmjs.com/package/opencv4nodejs

We should remove this package from Debian and package that opencv4nodejs
instead.

However opencv4nodejs has more dependencies than this one so it might
take some time.


Correct me if I'm wrong.


Yours,
Paul




signature.asc
Description: OpenPGP digital signature

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

[Debian Bug Tracking System]

Your message dated Tue, 29 Oct 2019 08:47:38 +
with message-id 
and subject line Bug#937720: fixed in python-easydev 0.9.38-1
has caused the Debian Bug report #937720,
regarding python-easydev: 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.)


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

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-easydev
Source-Version: 0.9.38-1

We believe that the bug you reported is fixed in the latest version of
python-easydev, 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.
Olivier Sallou  (supplier of updated python-easydev 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: Mon, 28 Oct 2019 15:56:52 +
Source: python-easydev
Binary: python3-easydev
Architecture: source all
Version: 0.9.38-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Olivier Sallou 
Description:
 python3-easydev - common utilities to ease the development of Python packages 
(Pyth
Closes: 937720
Changes:
 python-easydev (0.9.38-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #937720).
Checksums-Sha1:
 48087280ad06e1f275d12c6bbf9ac17da6ae4a1a 2209 python-easydev_0.9.38-1.dsc
 384634788051140952cfa5772a27883329035381 40748 
python-easydev_0.9.38.orig.tar.xz
 5d3e99f56166a599aac7f6078a7dcd5f24c58c23 4740 
python-easydev_0.9.38-1.debian.tar.xz
 6372388a71bec8ddbecb07878f9401f177b5 6933 
python-easydev_0.9.38-1_amd64.buildinfo
 e9581dc85e44c8c506723772ad8feec60ecb0940 39896 python3-easydev_0.9.38-1_all.deb
Checksums-Sha256:
 

Bug#943526: [Pkg-javascript-devel] Bug#943526: node-tslib: directory vs. symlink conflict: /usr/share/nodejs/tslib

[Julien Puydt]

Le mardi 29 octobre 2019 à 07:49 +0100, Xavier a écrit :
> Hi JS team,
> 
> why did node-typescript have such link ?
> 
>   /usr/share/nodejs/tslib -> typescript/lib
> 
> This creates this conflict.
> 

Well, isn't node-typescript supposed to provide that lib?

JP

Bug#885261: marked as done (bleachbit: Depends on unmaintained pygtk)

[Debian Bug Tracking System]

Your message dated Tue, 29 Oct 2019 07:34:17 +
with message-id 
and subject line Bug#885261: fixed in bleachbit 3.0-1
has caused the Debian Bug report #885261,
regarding bleachbit: Depends on unmaintained pygtk
to be marked as done.

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

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


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

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

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

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

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

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

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

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

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

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

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

Debian distribution maintenance software
pp.
Hugo Lefeuvre  (supplier of updated bleachbit 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, 27 Oct 2019 10:33:08 +0100
Source: bleachbit
Architecture: source
Version: 3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Hugo Lefeuvre 
Changed-By: Hugo Lefeuvre 
Closes: 885261
Changes:
 bleachbit (3.0-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
 .
   [ Hugo Lefeuvre ]
   * New upstream release.
   * Run wrap-and-sort -a.
   * Refresh manpage for new upstream release.
   * Refresh patches for new upstream release.
   * Remove debian/lintian-overrides: warning not present anymore.
   * debian/copyright: Add missing CC0-1.0 entry for bleachbit.appdata.xml.
   * debian/control:
 - Remove pygtk dependency, upstream moved to GTK 3 as part of the 3.0
   release (Closes: #885261).
 - Add missing python-chardet, python-gi, python-requests and python-scandir
   dependencies.
 - Bump Standards-Version to 4.4.1.
 - Move python-setuptools to Build-Depends-Indep.
   * debian/install: Add rule to install data/app-menu.ui.
Checksums-Sha1:
 258a62177c3b385e16594434be2933e4d0a449e4 1879 bleachbit_3.0-1.dsc
 2974a6164a24fa31d4fee077e96d8646d19f2a99 1027826 bleachbit_3.0.orig.tar.gz
 384035f57fecfbe48eb9037769da91a96553652a 10028 bleachbit_3.0-1.debian.tar.xz
 86510e620cbffe87736ded3e2e75ac0f65465b2e 6248 bleachbit_3.0-1_amd64.buildinfo
Checksums-Sha256:
 05a4001d76ed43272b076f05465071945880378d1788bd7a006cb0a146a80da3 1879 
bleachbit_3.0-1.dsc
 63efa7e0a77021d897c4460461e605e775edae50ae22281282cefb248d7bab40 1027826 
bleachbit_3.0.orig.tar.gz
 4cde3e4c1418e718fb52ead0a76e8a634831f17b9b008225b4e50b79853b29fc 10028 
bleachbit_3.0-1.debian.tar.xz
 651134f604ed8b2dc7ab7615c55cfb0a65241d936471f354b8bff9f2fc88bc2e 6248 
bleachbit_3.0-1_amd64.buildinfo
Files:
 f9e1664da0597af027f07a1d279a6ae9 1879 admin optional bleachbit_3.0-1.dsc
 deb971fcb4fc371f3885fca48d01f65d 1027826 admin optional 
bleachbit_3.0.orig.tar.gz
 d8c9c121ff090bdebdce1a81033509d1 10028 admin optional 
bleachbit_3.0-1.debian.tar.xz
 9baa4b3cc605f53764ebe673891e5eae 6248 admin optional 
bleachbit_3.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQHDBAEBCgAtFiEEeDb9QWtkMa2LX4zREeMFjl5EGkIFAl235gEPHGhsZUBkZWJp
YW4ub3JnAAoJEBHjBY5eRBpC87EL/Rc0ecCV840EC2dNiFjn375uw/LwOu0Q7Pxh
Dxe1LFqCJNQxm2JRU4H1zOKUDae2BYtH2p99YQ/I+hOTWVVnBocTjH61vgtx2w1G
E70G9loLYIrcxDWXBoF8odcvvBBD1+2Mhpjv4ZaPZggn4jRSgFAf1olunSMTdqxb
vUdyHl19ua6WihsxUT066w4MCadzsJ3KhxvRCFJhgeQJD2yEN1wrClKNO1B/XcTj
tSXzZppF4TM2rNzavdbc/rQC/oRe2Q7bzxpzGUXjSDiDISmcRIL/zNp/kP3/3IXh
pV82rm3ucnHZYPjRjhN4+unHqbW9KPwGif1kuChh3B0l7jjU4mNPQNNrfATLLV4L
utIR8NXcDHzcgRlhC3+ewRQYJLK3ZXPzkXWMScp2ItsMdfQVSeH2kBeA8T1eZCUv

Bug#943526: node-tslib: directory vs. symlink conflict: /usr/share/nodejs/tslib

[Xavier]

Hi JS team,

why did node-typescript have such link ?

  /usr/share/nodejs/tslib -> typescript/lib

This creates this conflict.