Bug#941407: tmperamental makes ls(1) segfault

[Jakub Wilk]

Package: tmperamental
Version: 1.1
Severity: grave

tmperamental makes ls(1) crash:

   $ tmperamental ls
   Segmentation fault

Backtrace:

#0  0x in ?? ()
#1  0xf7f2850e in selinuxfs_exists_internal () at init.c:64
#2  0xf7f1fee0 in init_selinuxmnt () at init.c:99
#3  init_lib () at init.c:154
#4  0xf7f7f0ec in call_init (l=, argc=argc@entry=1, 
argv=argv@entry=0xff923a34, env=0xff923a3c) at dl-init.c:72
#5  0xf7f7f1f2 in call_init (env=0xff923a3c, argv=0xff923a34, argc=1, l=) at dl-init.c:30
#6  _dl_init (main_map=, argc=1, argv=0xff923a34, 
env=0xff923a3c) at dl-init.c:119
#7  0xf7f700fa in _dl_start_user () from /lib/ld-linux.so.2


AFAICS, libselinux has a constructor which uses fopen(), and that 
constructor runs earlier than tmperamental's one, leading to null 
pointer dereference.


-- System Information:
Architecture: i386

Versions of packages tmperamental depends on:
ii  libc6  2.29-2

--
Jakub Wilk

Processed: forcibly merging 941249 941389

[Debian Bug Tracking System]

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

> forcemerge 941249 941389
Bug #941249 [virt-manager] virt-manager: Can not open detail of connection and 
detail or console of a VM
Bug #941389 [virt-manager] virt-manager: Missing dependency from 
gir1.2-gtksource-4
Added tag(s) pending.
Merged 941249 941389
> thanks
Stopping processing here.

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

Processed: tagging 939190, tagging 939191, tagging 939192, tagging 939193

[Debian Bug Tracking System]

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

> tags 939190 + bullseye
Bug #939190 [src:movim] Incompatible to new symfony 4.x
Added tag(s) bullseye.
> tags 939191 + bullseye
Bug #939191 [src:php-robmorgan-phinx] Incompatible to new symfony 4.x
Added tag(s) bullseye.
> tags 939192 + bullseye
Bug #939192 [src:ratchetphp] Incompatible to new symfony 4.x
Added tag(s) bullseye.
> # Seems needed for the automatic removal from testing
> tags 939193 + bullseye
Bug #939193 [src:php-nesbot-carbon] Incompatible to new symfony 4.x
Added tag(s) bullseye.
> thanks
Stopping processing here.

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

Bug#908297: marked as done (libindicate FTBFS with glib 2.58)

[Debian Bug Tracking System]

Your message dated Mon, 30 Sep 2019 04:55:01 +
with message-id 
and subject line Bug#941384: Removed package(s) from unstable
has caused the Debian Bug report #908297,
regarding libindicate FTBFS with glib 2.58
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.)


-- 
908297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libindicate
Version: 0.6.92-6
Severity: serious
Tags: ftbfs

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

...
/build/1st/libindicate-0.6.92/./libindicate/server.c: In function 
'indicate_server_class_init':
/build/1st/libindicate-0.6.92/./libindicate/server.c:230:2: error: 
'g_type_class_add_private' is deprecated [-Werror=deprecated-declarations]
  g_type_class_add_private (class, sizeof (IndicateServerPrivate));
  ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /build/1st/libindicate-0.6.92/./libindicate/server.h:34,
 from /build/1st/libindicate-0.6.92/./libindicate/server.c:30:
/usr/include/glib-2.0/gobject/gtype.h:1303:10: note: declared here
 void g_type_class_add_private   (gpointerg_class,
  ^~~~
cc1: all warnings being treated as errors
make[3]: *** [Makefile:732: libindicate_la-server.lo] Error 1
--- End Message ---
--- Begin Message ---
Version: 0.6.92-6+rm

Dear submitter,

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

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

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

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

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

Bug#895025: marked as done (deprecate/remove libindicate in Debian)

[Debian Bug Tracking System]

Your message dated Mon, 30 Sep 2019 04:55:01 +
with message-id 
and subject line Bug#941384: Removed package(s) from unstable
has caused the Debian Bug report #895025,
regarding deprecate/remove libindicate in Debian
to be marked as done.

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

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


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

Package: src:libindicate
Severity: serious
User: pkg-ayatana-de...@lists.alioth.debian.org
Usertags: ubuntuindicatorremoval

The libindicate shared library (don't confuse with libindicator!!!)  
has no functionality in Debian at this point anymore. It probably  
never had. In Ubuntu, it was only used (some time ago) by the messages  
system indicator. However, the libindicate approach got substituted  
there by the libmessaging-menu API.


In Ubuntu, the libindicate shared lib has nealy no reverse  
dependencies anymore. We should work on this in Debian, too, and  
finally remove the package.


In Debian the following packages still build-depend on libindicate*-dev:

libindicate5
  Reverse Depends: gir1.2-indicate-0.7 (>= 0.6.92-6)
  Reverse Depends: libindicate-dev (= 0.6.92-6)
  Reverse Depends: libindicate-gtk3 (>= 0.6.92-6)
  Reverse Depends: libindicate-gtk3-3 (>= 0.6.92-6)
  Reverse Depends: libindicate0.1-cil (>= 0.6.92-6)
  Reverse Depends: pidgin-libnotify (>= 0.14-9)
  Reverse Depends: python-indicate (= 0.6.92-6)
gir1.2-indicate-0.7
  Reverse Depends: libindicate-dev (= 0.6.92-6)
libindicate-dev
  Reverse Depends: libindicate-gtk-dev (= 0.6.92-6)
  Reverse Depends: libindicate-gtk3-dev (= 0.6.92-6)
libindicate-gtk-dev
libindicate-gtk3-dev
  Reverse Depends: libindicate-gtk-dev (= 0.6.92-6)
libindicate-gtk3
  Reverse Depends: libindicate-gtk-dev (= 0.6.92-6)
  Reverse Depends: libindicate-gtk0.1-cil (>= 0.6.92-6)
  Reverse Depends: pidgin-libnotify (>= 0.14-9)
  Reverse Depends: python-indicate (>= 0.6.92-6)
libindicate-gtk0.1-cil
  Reverse Depends: libindicate-gtk0.1-cil-dev (= 0.6.92-6)
libindicate-gtk0.1-cil-dev
pidgin-libnotify
python-indicate
  Reverse Depends: mopidy-mpris (1.3.1-1)
mopidy-mpris
libindicate-gtk3-3
  Reverse Depends: libindicate-gtk3-dev (= 0.6.92-6)
libindicate0.1-cil
  Reverse Depends: libindicate-gtk0.1-cil (= 0.6.92-6)
  Reverse Depends: libindicate0.1-cil-dev (= 0.6.92-6)
  Reverse Depends: smuxi-frontend-gnome (>= 1.0.7-2)
libindicate0.1-cil-dev
smuxi-frontend-gnome
  Reverse Depends: smuxi (= 1.0.7-2)
smuxi

So, in a nutshell, these packages need to be addressed: smuxi,  
pidgin-libnotify and mopidy-mpris require changes to have libindicate  
removed from Debian.


Greets,
Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

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



pgp2uQ697vjIF.pgp
Description: Digitale PGP-Signatur
--- End Message ---
--- Begin Message ---
Version: 0.6.92-6+rm

Dear submitter,

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

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

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

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

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

Bug#895026: marked as done (pidgin-libnotify: Port from libindicate to libmessaging-menu)

[Debian Bug Tracking System]

Your message dated Mon, 30 Sep 2019 04:54:32 +
with message-id 
and subject line Bug#941383: Removed package(s) from unstable
has caused the Debian Bug report #895026,
regarding pidgin-libnotify: Port from libindicate to libmessaging-menu
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.)


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

Package: src:pidgin-libnotify
Severity: normal
Control: block #895025 by -1

Hi,

please port pidgin-libnotify from libindicate to libmessaging-menu.  
The src:package ayatana-indicator-messages (which ships  
libmessaging-menu) is currently in Debian's NEW queue and should soon  
be available in Debian unstable.


The libindicate shared lib is about to be removed and libindicate is  
non-functional in Debian these days.


Thanks,
Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

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



pgpxpkhm76aOT.pgp
Description: Digitale PGP-Signatur
--- End Message ---
--- Begin Message ---
Version: 0.14-9+rm

Dear submitter,

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

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

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

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

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

Bug#896368: marked as done (python3-cigi: cigi fails to import)

[Debian Bug Tracking System]

Your message dated Mon, 30 Sep 2019 04:53:46 +
with message-id 
and subject line Bug#941382: Removed package(s) from unstable
has caused the Debian Bug report #896368,
regarding python3-cigi: cigi fails to import
to be marked as done.

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

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


-- 
896368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896368
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-cigi
Version: 3.3.3a+svn818-10+b4
Severity: serious
User: helm...@debian.org
Usertags: python-import

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

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/cigi/__init__.py", line 14, in 
swig_import_helper
return importlib.import_module(mname)
  File "/usr/lib/python3.6/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 994, in _gcd_import
  File "", line 971, in _find_and_load
  File "", line 953, in _find_and_load_unlocked
ModuleNotFoundError: No module named '_cigi'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/cigi/__init__.py", line 17, in 
_cigi = swig_import_helper()
  File "/usr/lib/python3/dist-packages/cigi/__init__.py", line 16, in 
swig_import_helper
return importlib.import_module('_cigi')
  File "/usr/lib/python3.6/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
ModuleNotFoundError: No module named '_cigi'

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

Helmut
--- End Message ---
--- Begin Message ---
Version: 3.3.3a+svn818-10+rm

Dear submitter,

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

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

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

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

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

Bug#896367: marked as done (python-cigi: cigi fails to import)

[Debian Bug Tracking System]

Your message dated Mon, 30 Sep 2019 04:53:46 +
with message-id 
and subject line Bug#941382: Removed package(s) from unstable
has caused the Debian Bug report #896367,
regarding python-cigi: cigi fails to import
to be marked as done.

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

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


-- 
896367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-cigi
Version: 3.3.3a+svn818-10+b4
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-cigi importing the module cigi
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/cigi/__init__.py", line 17, in 
_cigi = swig_import_helper()
  File "/usr/lib/python2.7/dist-packages/cigi/__init__.py", line 16, in 
swig_import_helper
return importlib.import_module('_cigi')
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
ImportError: No module named _cigi

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

Helmut
--- End Message ---
--- Begin Message ---
Version: 3.3.3a+svn818-10+rm

Dear submitter,

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

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

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

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

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

Bug#832422: marked as done (albatross-gtk-theme: broken with GTK3.20)

[Debian Bug Tracking System]

Your message dated Mon, 30 Sep 2019 04:51:33 +
with message-id 
and subject line Bug#941357: Removed package(s) from unstable
has caused the Debian Bug report #832422,
regarding albatross-gtk-theme: broken with GTK3.20
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.)


-- 
832422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: albatross-gtk-theme
Version: 1.7.4-1
Severity: important
Tags; upstream
Forwarded: https://github.com/shimmerproject/Albatross/issues/10

GTK 3.20 includes a major rewrite of the theming code and broke all
existing GTK3 themes. I'm linking the upstream tracking bug for
Albatross. Since Albatross is not really maintained upstream any more,
it's unclear when someone will get around to fixing this.

Considering we still have quite a few GTK2 themes in Debian with no
GTK3 support at all, I don't think we should remove albatross at this
time. The theme is still usable on Xfce if you don't use GTK3 apps.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 1.7.4-1+rm

Dear submitter,

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

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

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

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

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

Bug#940984: marked as done (RM: python-biggles -- RoQA; low popcon; no rdeps; last MU upload in 2010; better alternatives exist)

[Debian Bug Tracking System]

Your message dated Mon, 30 Sep 2019 04:51:05 +
with message-id 
and subject line Bug#940984: Removed package(s) from unstable
has caused the Debian Bug report #940984,
regarding RM: python-biggles -- RoQA; low popcon; no rdeps; last MU upload in 
2010; better alternatives exist
to be marked as done.

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

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


-- 
940984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-biggles
Severity: serious

Hello,
as part of https://wiki.debian.org/Python/2Removal i noticed python-biggles and
i believe we should remove it from Debian:

- maybe it was sophisiticated when it was created, but there are better
  alternatives now (but i may be bias as i maintainer some of them :) )
- python2 only (in debian)
- upstream moved to https://github.com/biggles-plot/biggles with a version
  that's py3k compatible, but someone should step up and package it
- no rdeps
- low popcon
- last upload from Deepak on this package was in 2010

If i dont hear back with a good reason to keep this package in Debian within a
week, i'll file for its removal

Regards,
Sandro

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 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= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-biggles |1.6.6-3 | source
python-pybiggles | 1.6.6-3+b2 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x

--- Reason ---
RoQA; low popcon; no rdeps; last MU upload in 2010; better alternatives exist
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

The full log for this bug can be viewed at https://bugs.debian.org/940984

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

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

Bug#934931: marked as done (planet-venus: depends on cruft package)

[Debian Bug Tracking System]

Your message dated Mon, 30 Sep 2019 04:50:46 +
with message-id 
and subject line Bug#940982: Removed package(s) from unstable
has caused the Debian Bug report #934931,
regarding planet-venus: depends on cruft package
to be marked as done.

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

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


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

Package: planet-venus
Version: 0~git9de2109-4.2
Severity: serious
Tags: bullseye, sid

planet-venus depends on python-portalocker which is no longer built by the 
portalocker source package.

If you want your package to stay around you probably need to migrate to python 
3.

--- End Message ---
--- Begin Message ---
Version: 0~git9de2109-4.2+rm

Dear submitter,

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

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

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

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

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

Bug#940982: marked as done (RM: planet-venus -- RoM; RC buggy; low popcon; python2-only, upstream too; last MU in 2014)

[Debian Bug Tracking System]

Your message dated Mon, 30 Sep 2019 04:50:28 +
with message-id 
and subject line Bug#940982: Removed package(s) from unstable
has caused the Debian Bug report #940982,
regarding RM: planet-venus -- RoM; RC buggy; low popcon; python2-only, upstream 
too; last MU in 2014
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.)


-- 
940982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940982
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: planet-venus
Severity: serious

Hello,
as part of https://wiki.debian.org/Python/2Removal i noticed planet-venus, and i
believe we should remove it from Debian:

- RC buggy
- pretty low pop-con
- python2-only, also upstream
- https://github.com/rubys/venus/issues/37 showed some possible work to port it
  to py3k, but that effort never materialized
- last maintainer upload in 2014

if i dont hear a good reason to keep this package in Debian within a week, i
will file for its removal.

Regards,
Sandro

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 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= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages planet-venus depends on:
ii  python  2.7.16-1
ii  python-chardet  3.0.4-3
ii  python-feedparser   5.2.1-1
ii  python-html5lib 1.0.1-1
pn  python-htmltmpl 
ii  python-httplib2 0.11.3-2
pn  python-librdf   
ii  python-libxml2  2.9.4+dfsg1-7+b3
pn  python-portalocker  
ii  python-utidylib 0.5-2

Versions of packages planet-venus recommends:
pn  python-libxslt1  

Versions of packages planet-venus suggests:
pn  python-django  
pn  python-genshi  
ii  python-lxml4.4.1-1
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

planet-venus | 0~git9de2109-4.2 | source, all

--- Reason ---
RoM; RC buggy; low popcon; python2-only, upstream too; last MU in 2014
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

The full log for this bug can be viewed at https://bugs.debian.org/940982

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

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

Bug#940976: marked as done (RM: python-avc -- RoQA; low popcon; last upstream release 3.5 years ago; no Debian maint for 8+ years; last NMU 5 years ago)

[Debian Bug Tracking System]

Your message dated Mon, 30 Sep 2019 04:48:59 +
with message-id 
and subject line Bug#940976: Removed package(s) from unstable
has caused the Debian Bug report #940976,
regarding RM: python-avc -- RoQA; low popcon; last upstream release 3.5 years 
ago; no Debian maint for 8+ years; last NMU 5 years ago
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.)


-- 
940976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-avc
Severity: serious

Hello,
As part of https://wiki.debian.org/Python/2Removal i stumbled across this
package, and i believe we should remove it:

- popcon very low
- no maintainer upload to debian in 8 years
- last upload, NMU, 5 years ago
- last upstream release 3.5years ago

if I dont hear back with a good reason to keep this package in Debian withing a
week, i'll ask for python-avc removal.

Regards,
Sandro

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 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= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python-avc depends on:
ii  python  2.7.16-1

python-avc recommends no packages.

Versions of packages python-avc suggests:
pn  jython   
ii  python-gtk2  2.24.0-6
pn  python-qt3   
ii  python-qt4   4.12.1+dfsg-2+b1
ii  python-tk2.7.16-2
ii  python-wxgtk3.0  3.0.2.0+dfsg-8
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-avc |  0.8.3-1.1 | source, all

--- Reason ---
RoQA; low popcon; last upstream release 3.5 years ago; no Debian maint for 8+ 
years; last NMU 5 years ago
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

The full log for this bug can be viewed at https://bugs.debian.org/940976

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

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

Bug#940981: marked as done (RM: doconce -- RoQA; low popcon; last upload 7 years ago; python2 only)

[Debian Bug Tracking System]

Your message dated Mon, 30 Sep 2019 04:50:03 +
with message-id 
and subject line Bug#940981: Removed package(s) from unstable
has caused the Debian Bug report #940981,
regarding RM: doconce -- RoQA; low popcon; last upload 7 years ago; python2 only
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.)


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

Hello,
as part of https://wiki.debian.org/Python/2Removal i noticed doconce, and i
believe we should remove it from Debian:

- last upload to debian 7 years go
- low popcon
- Uploader seems to have lost interest in Debian
- python2 only (in debian)
- upstream has a new home https://github.com/hplgit/doconce that supports p3k,
  but someone has to step up and upload it

if i dont hear back with a good reason to keep this package in Debian within a
week, i will ask for its removal.

Regards,
Sandro

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 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= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages doconce depends on:
ii  python 2.7.16-1
ii  python2.7  2.7.16-2

Versions of packages doconce recommends:
pn  preprocess   
ii  python-mako  1.0.7+ds1-1

Versions of packages doconce suggests:
ii  imagemagick  8:6.9.10.23+dfsg-2.1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.23+dfsg-2.1
ii  pandoc   2.2.1-3+b2
pn  ptex2tex 
ii  python-docutils  0.14+dfsg-4
ii  python-sphinx1.8.4-1
ii  texlive-base 2018.20190227-2
pn  texlive-base-recommended 
ii  texlive-latex-base   2018.20190227-2
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   doconce |0.7.3-1 | source, all

--- Reason ---
RoQA; low popcon; last upload 7 years ago; python2 only
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

The full log for this bug can be viewed at https://bugs.debian.org/940981

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

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

Bug#940977: marked as done (RM: libfte -- RoQA; python2 only; only one MU upload immediately followed by a NMU; dead upstream, last release 5+ years ago)

[Debian Bug Tracking System]

Your message dated Mon, 30 Sep 2019 04:49:35 +
with message-id 
and subject line Bug#940977: Removed package(s) from unstable
has caused the Debian Bug report #940977,
regarding RM: libfte -- RoQA; python2 only; only one MU upload immediately 
followed by a NMU; dead upstream, last release 5+ years ago
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.)


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

Hello,
as part of https://wiki.debian.org/Python/2Removal i noticed libfte, and i
believe we should remove this package from Debian:

- single maintainer upload, immediately followed by a NMU
- python2 only, even upstream
- last upstream release 5 years ago, according to
  https://github.com/kpdyer/fteproxy/releases

If i dont hear back with a good reason to keep this package in Debian within a
week, i'll ask for this package removal.

Regards,
Sandro

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 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= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libfte |  0.1.0-1.1 | source
python-fte |  0.1.0-1.1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x

--- Reason ---
RoQA; python2 only; only one MU upload immediately followed by a NMU; dead 
upstream, last release 5+ years ago
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

The full log for this bug can be viewed at https://bugs.debian.org/940977

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

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

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

[Debian Bug Tracking System]

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

> reassign 940981 ftp.debian.org
Bug #940981 [doconce] doconce: should this package be removed?
Bug reassigned from package 'doconce' to 'ftp.debian.org'.
No longer marked as found in versions doconce/0.7.3-1.
Ignoring request to alter fixed versions of bug #940981 to the same values 
previously set
> retitle 940981 RM: doconce -- RoQA; low popcon; last upload 7 years ago; 
> python2 only
Bug #940981 [ftp.debian.org] doconce: should this package be removed?
Changed Bug title to 'RM: doconce -- RoQA; low popcon; last upload 7 years ago; 
python2 only' from 'doconce: should this package be removed?'.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

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

> reassign 940977 ftp.debian.org
Bug #940977 [src:libfte] libfte: should this package be removed?
Bug reassigned from package 'src:libfte' to 'ftp.debian.org'.
No longer marked as found in versions libfte/0.1.0-1.1.
Ignoring request to alter fixed versions of bug #940977 to the same values 
previously set
> retitle 940977 RM: libfte -- RoQA; python2 only; only one MU upload 
> immediately followed by a NMU; dead upstream, last release 5+ years ago
Bug #940977 [ftp.debian.org] libfte: should this package be removed?
Changed Bug title to 'RM: libfte -- RoQA; python2 only; only one MU upload 
immediately followed by a NMU; dead upstream, last release 5+ years ago' from 
'libfte: should this package be removed?'.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

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

> reassign 940982 ftp.debian.org
Bug #940982 [planet-venus] planet-venus: should this package be removed?
Bug reassigned from package 'planet-venus' to 'ftp.debian.org'.
No longer marked as found in versions planet-venus/0~git9de2109-4.2.
Ignoring request to alter fixed versions of bug #940982 to the same values 
previously set
> retitle 940982 RM: planet-venus -- RoM; RC buggy; low popcon; python2-only, 
> upstream too; last MU in 2014
Bug #940982 [ftp.debian.org] planet-venus: should this package be removed?
Changed Bug title to 'RM: planet-venus -- RoM; RC buggy; low popcon; 
python2-only, upstream too; last MU in 2014' from 'planet-venus: should this 
package be removed?'.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

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

> reassign 940984 ftp.debian.org
Bug #940984 [src:python-biggles] python-biggles: should this package be removed?
Bug reassigned from package 'src:python-biggles' to 'ftp.debian.org'.
No longer marked as found in versions python-biggles/1.6.6-3.
Ignoring request to alter fixed versions of bug #940984 to the same values 
previously set
> retitle 940984 RM: python-biggles -- RoQA; low popcon; no rdeps; last MU 
> upload in 2010; better alternatives exist
Bug #940984 [ftp.debian.org] python-biggles: should this package be removed?
Changed Bug title to 'RM: python-biggles -- RoQA; low popcon; no rdeps; last MU 
upload in 2010; better alternatives exist' from 'python-biggles: should this 
package be removed?'.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

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

> reassign 940976 ftp.debian.org
Bug #940976 [python-avc] python-avc: should this package be removed?
Bug reassigned from package 'python-avc' to 'ftp.debian.org'.
No longer marked as found in versions python-avc/0.8.3-1.1.
Ignoring request to alter fixed versions of bug #940976 to the same values 
previously set
> retitle 940976 RM: python-avc -- RoQA; low popcon; last upstream release 3.5 
> years ago; no Debian maint for 8+ years; last NMU 5 years ago
Bug #940976 [ftp.debian.org] python-avc: should this package be removed?
Changed Bug title to 'RM: python-avc -- RoQA; low popcon; last upstream release 
3.5 years ago; no Debian maint for 8+ years; last NMU 5 years ago' from 
'python-avc: should this package be removed?'.
> thanks
Stopping processing here.

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

Bug#941393: My bad

[submitbug]

This is the first time I post a report.
Please close #941393 and use #941394

Bug#941394: Padlock icon indicates secure TLS connection established w MitM-ed

[submitbug]

Package: firefox
Version: 69.0.1-1
Severity: grave

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831835

The same thing applies to Mozilla Firefox. This is still ongoing issue.

How to reproduce
1. Install Tor.
2. Set proxy.
3. Browse the internet.

Actual behavior
Padlock is green.

Expected behavior
Padlock is not green but a gray with exclamation mark.

Read
https://trac.torproject.org/projects/tor/ticket/24351
https://github.com/mozilla-mobile/focus-android/issues/1743
https://codeberg.org/crimeflare/cloudflare-tor/


-- System Information:
Debian Release: 10
APT prefers stable-updates

Bug#941393: Padlock icon indicates a secure TLS connection established w MitM-ed

[submitbug]

Package: firefox
Version: 68.0
Severity: grave

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831835

The same thing applies to Mozilla Firefox. This is still ongoing issue.

https://trac.torproject.org/projects/tor/ticket/24351
https://github.com/mozilla-mobile/focus-android/issues/1743
https://codeberg.org/crimeflare/cloudflare-tor/


-- System Information:
Debian Release: 10
APT prefers stable-updates

Bug#940678: Please import pools by stable device label

[Antonio Russo]

On 9/29/19 2:30 PM, Alberto Berti wrote:
> Hi Antonio,
> 
> thanks for answering.

No problem! :-)

> 
>> "Antonio" == Antonio Russo  writes:
> 
> Antonio> Could you please clarify: did you experience any data loss,
> Antonio> or were you simply unable to import your pool at one point?
> 
> The pool systematically fails to mount after the upgrade, at each boot,
> even if I manually mounted it.. 

The terminology with ZFS is a little different: pools are "imported"
and the datasets (that are filesystems rather than, say, zvols) are then
"mounted".  It sounds like you cannot import the pool, and therefore you
cannot mount the datasets.

Is your problem reproducible? By that I mean, on reboot, does the pool
import or not?

And what do you mean by "manually mounted it"? Are you talking about

# zpool import -d /dev -aN

If it's not mounting on reboot, just use -d /dev/disk/by-id next time,
and the problem should go away.

> this leads to data loss from a user pow, because the data that's not> there 
> may get re-written and generate conflicts.
If another application does not gracefully handle missing data, by all
means that is a bug for that application. That's not, however, a ZFS
bug.

I would encourage you to open a separate bug, unrelated to this, for
that issue.

> 
> Antonio> As a second note, you should have done something like
> 
> Antonio> zpool import -d /dev/disks/by-id -a
> 
> Antonio> so that your import is done by labels that are stable
> Antonio> across boots (names like /dev/sdX are not necessarily
> Antonio> stable). This is a "well-known" best practice with ZFS [1]
> Antonio> (you should always create pools using these symlinks as
> Antonio> well).
> 
> good to know, thanks. Although I think that if the hardware
> configuration nor the kernel version changes between the boots, we can
> assume that each block device will get the same id... anyway I'll try it.

First off, there's typo. Use /dev/disk/by-id . Not with an extra s.

You can check this---note which device nodes are being linked by the
stable identifiers in /dev/disk/by-id. Do they change on reboot?

If you find that your device nodes are to exactly the same drives, and
yet the pool is not importing as you have found, that's definitely a bug,
and we'll have to file it upstream. You will need verbatim dmesg logs,
the zpool status $poolname output, and the output of ls -l /dev/disk/by-id
on subsequent boots.

Upstream will want to see exactly what is going on with the device nodes,
since that's the most likely cause of this problem.

> 
> Antonio> If you have only experienced an inability to import your
> Antonio> pool at boot, my guess is that you had (and continue to
> Antonio> have) the inappropriate import by device node setup. This
> Antonio> configuration error will lead to you continuing to have
> Antonio> problems importing your pool at later times, and is not a
> Antonio> bug. To fix that problem you should zpool export all your
> Antonio> pools (this might be tricky, especially if you are zfs on
> Antonio> root), and then run the above command. As always, double
> Antonio> check all this!
> 
> uhumm, Yes, that is tricky, as I read that the export operation unmounts
> every exported fs before the operation.

Yes, to export a pool, none of its datasets can be in use (e.g., mounted).
Be careful with the terminology here---exporting a filesystem (or dataset)
means something totally different than exporting a pool.

> 
> So you say that if I do that the start of the zfs-import-cache in the
> next boot will succeed?

Barring a new bug, yes.

> 
> thank you
> 
> Alberto
> 

Best,
Antonio

Bug#941389: virt-manager: Missing dependency from gir1.2-gtksource-4

[manul]

Package: virt-manager
Version: 1:2.2.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After upgrading virt-manager to the latest version, once started it is unable 
to open virtual machine details/console pop windows (as well as some other pop 
windows like connection settings etc).
Installing gir1.2-gtksource-4 fixes the issue but, it is not in the current 
dependencies of virt-manager (which I believe it must be).

Thank you.


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

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= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages virt-manager depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.34.0-1
ii  gir1.2-gtk-3.0   3.24.11-1
ii  gir1.2-gtk-vnc-2.0   0.9.0-1.1+b1
ii  gir1.2-libosinfo-1.0 1.6.0-1
ii  gir1.2-libvirt-glib-1.0  1.0.0-1
ii  gir1.2-vte-2.91  0.58.0-1
ii  librsvg2-common  2.44.14-1
ii  python3  3.7.3-1
ii  python3-dbus 1.2.12-1
ii  python3-gi   3.34.0-1
ii  python3-gi-cairo 3.34.0-1
ii  python3-libvirt  5.0.0-1
ii  virtinst 1:2.2.1-1

Versions of packages virt-manager recommends:
ii  gir1.2-spiceclientglib-2.0  0.37-1
ii  gir1.2-spiceclientgtk-3.0   0.37-1
ii  libvirt-daemon-system   5.6.0-2

Versions of packages virt-manager suggests:
pn  gir1.2-secret-1  
pn  gnome-keyring
pn  python3-guestfs  
ii  ssh-askpass  1:1.2.4.1-10+b1
pn  virt-viewer  

-- no debconf information

Bug#941363: [filezilla] Filezilla doesn't start, returns an undefined symbol error

[Diederik de Haas]

Package: filezilla
Version: 3.39.0-2
Followup-For: Bug #941363

Confirming that I have the exact same issue.
I don't remember exactly when, but this issue started somewhere between
1 and 2 weeks ago, iow not today.
My sources.list only contains http://httpredir.debian.org/debian/, thus
it is a pure Debian system.

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/16 CPU cores)
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 filezilla depends on:
ii  filezilla-common 3.39.0-2
ii  libatk1.0-0  2.34.0-1
ii  libc62.29-2
ii  libcairo21.16.0-4
ii  libdbus-1-3  1.12.16-1
ii  libfilezilla00.18.2-1
ii  libfontconfig1   2.13.1-2+b1
ii  libfreetype6 2.9.1-4
ii  libgcc1  1:9.2.1-8
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.60.6-2
ii  libgnutls30  3.6.9-5
ii  libgtk2.0-0  2.24.32-4
ii  libhogweed4  3.5.1+really3.4.1-1
ii  libnettle6   3.5.1+really3.4.1-1
ii  libpango-1.0-0   1.42.4-7
ii  libpangocairo-1.0-0  1.42.4-7
ii  libpangoft2-1.0-01.42.4-7
ii  libpugixml1v51.9-3
ii  libsqlite3-0 3.29.0-2
ii  libstdc++6   9.2.1-8
ii  libwxbase3.0-0v5 3.0.4+dfsg-12
ii  libwxgtk3.0-0v5  3.0.4+dfsg-12

Versions of packages filezilla recommends:
ii  xdg-utils  1.1.3-1

filezilla suggests no packages.

-- no debconf information

Bug#936764: jhbuild: Python2 removal in sid/bullseye

[Christoph Reiter]

On Sun, Sep 29, 2019 at 11:38 PM Jeremy Bicha  wrote:
>
> On Mon, Sep 23, 2019 at 3:03 AM Christoph Reiter
>  wrote:
> > jhbuild master now works with Python 3. There are likely still bugs as
> > the test coverage isn't that good.
> >
> > ./autogen.sh --with-python=python3
>
> It's easier to package from a tarball release than to do a git
> snapshot, so I will probably wait for a 3.35 release to package the
> new py3 jhbuild.

OK, I'll create a release next week.

Bug#936764: jhbuild: Python2 removal in sid/bullseye

[Jeremy Bicha]

On Mon, Sep 23, 2019 at 3:03 AM Christoph Reiter
 wrote:
> jhbuild master now works with Python 3. There are likely still bugs as
> the test coverage isn't that good.
>
> ./autogen.sh --with-python=python3

It's easier to package from a tarball release than to do a git
snapshot, so I will probably wait for a 3.35 release to package the
new py3 jhbuild.

> The python-pygraphviz dep can be dropped, I can't find any usage of it
> in the code base.

I uploaded jhbuild 3.34 today and changed the suggested package to
graphviz since it supplies 'dot' which is suggested for a minor
feature in the jhbuild user help. Thanks for the tip!

I'm fine with this bug being Serious and jhbuild potentially dropping
out of Testing temporarily.

The jhbuild package hasn't included the modulesets since 2010. Those
can be either referenced directly over https or downloaded locally.
The jhbuild package is useful because you don't have to manually build
and install the Python scripts and keep them up to date manually. I
hope upstream continues to do periodic tarball releases.

I still find jhbuild to be more convenient than buildstream for my
GNOME stuff, but I packaged buildstream just in case (and it's
probably useful for someone).

Thanks,
Jeremy Bicha

Bug#910679: marked as done (cegui-mk2 should build-depend on updated pyside-tools package)

[Debian Bug Tracking System]

Your message dated Sun, 29 Sep 2019 21:34:07 +
with message-id 
and subject line Bug#910679: fixed in cegui-mk2 0.8.7-3
has caused the Debian Bug report #910679,
regarding cegui-mk2 should build-depend on updated pyside-tools package
to be marked as done.

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

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


-- 
910679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cegui-mk2
Version: 0.8.7-2
Severity: important

Muammar,

   Good afternoon! I've been tracking the blockers to cegui migrating to
testing. Mostly because it is in turn blocking my ember package [0]. ;)

I see that the current version of pyside-tools depends on pyside which is
scheduled to be removed from Debian. The successor package, pyside2, was
packaged for Debian on 29 Jul 2018 [1]. There is currently a bug [2] for
packaging the new pyside-tools which will presumably be called pyside2-tools. 

Since this is preventing migration to testing and release, please update to
the new version of pyside-tools as soon as it is released. I realise that this
is presently outside your control but please let me know if you need any
assistance, I'm happy to help however I can!

Thanks!

-Olek

[0] https://qa.debian.org/excuses.php?package=ember
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877871
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881659
--- End Message ---
--- Begin Message ---
Source: cegui-mk2
Source-Version: 0.8.7-3

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

Debian distribution maintenance software
pp.
Olek Wojnar  (supplier of updated cegui-mk2 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, 02 Apr 2019 19:54:03 -0400
Source: cegui-mk2
Architecture: source
Version: 0.8.7-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Olek Wojnar 
Closes: 739074 855515 910679 924190
Changes:
 cegui-mk2 (0.8.7-3) unstable; urgency=medium
 .
   * Update d/copyright:
 - Use secure URLs
 - Add myself to debian/*
 - Update debian/* copyright dates
 - Consolidate license information
 - Clarify an unnamed license as BSD-3-clause (char-for-char match)
   * Update d/control:
 - Move package maintenance under Debian Games Team
 - Add myself as secondary uploader
 - Update build-depend from pyside-tools to pyside2-tools (Closes: #910679)
 - Update VCS URLs
 - Update standards to 4.3.0 (no changes)
 - Add missing depends for -doc package (Closes: #924190)
 - Remove unnecessary build-depend on libdirectfb-dev (Closes: #855515)
 - Mark -doc package as Multi-Arch foreign, mark lib and -dev as MA same
   * Update d/rules:
 - Add fixfilepath to DEB_BUILD_MAINT_OPTIONS for build reproducibility
 - Use jdupes to replace duplicate documentation files with softlinks
   * Update d/debian/patches/xerces32_changes:
 - Add missing DEP 3 info
 - Add missing blank line at EOF
   * Update to compatibility level 11:
 - Update d/compat to 11
 - Update d/control build-deps: debhelper to >= 11 and remove dh-autoreconf
   * Add d/upstream/metadata: for DEP 12 compliance
   * Move from CDBS to debhelper:
 - Update d/control and d/rules
 - Remove unnecessary d/dirs files
 - Update d/install files
 - Update doxygenout patch
   * Enable support for both python2 and python3 (Closes: #739074):
 -- Update d/control, d/rules, and d/*libcegui-mk2-0.8.7.install
 -- Add d/patches/python3.patch
 -- Add python- and python3- .install files
   * Convert to automatic debug package: update d/control and d/rules
   * Remove obsolete patches
   * Create manpages and separate package for two bundled binaries
   * Move library data from -doc package to new -data and fonts- packages
   * Add lintian override for package-name-doesnt-match-sonames
   * Add d/patches/mizufalp.patch: Eliminate code references to removed font
   * Add d/patches/multi-arch.patch: Add support for Multi-Arch to CMake
   * Add d/r

Bug#932975: marked as done (octave build-depends on cruft package.)

[Debian Bug Tracking System]

Your message dated Sun, 29 Sep 2019 21:05:33 +
with message-id 
and subject line Bug#932975: fixed in octave 5.1.0-2
has caused the Debian Bug report #932975,
regarding octave build-depends on cruft package.
to be marked as done.

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

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


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

Package: octave
Version: 3.5.2-1
Tags: bullseye, sid, patch
Severity: serious

octave build-depends on texlive-generic-reccomended which is no longer built by 
the texlive-base source package. Please build-depend on texlive-plain-generic 
instead.
--- End Message ---
--- Begin Message ---
Source: octave
Source-Version: 5.1.0-2

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

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated octave 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, 29 Sep 2019 22:03:24 +0200
Source: octave
Architecture: source
Version: 5.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Octave Group 
Changed-By: Sébastien Villemot 
Closes: 926047 932975
Changes:
 octave (5.1.0-2) unstable; urgency=medium
 .
   [ Sébastien Villemot ]
   * d/copyright: add entry for etc/fonts/* (Closes: #926047)
   * Bump to S-V 4.4.1
 .
   [ Rafael Laboissiere ]
   * d/control: Build-depend on texlive-plain-generic, instead of
 -generic-recommended (Closes: #932975)
Checksums-Sha1:
 e5e6e4e49fd194e1f6b23a93d25fbba6c0541cdc 3387 octave_5.1.0-2.dsc
 27d412dc9d7b3a6602c1fc0742ec31a47ae98653 72016 octave_5.1.0-2.debian.tar.xz
 28ff14a90bcfcbba1d8e0597b741eef20fdd8978 21555 octave_5.1.0-2_amd64.buildinfo
Checksums-Sha256:
 88a22582fb6f909eab8a95099c9883af87ffdae9ad5fe1ac41dbfb9cf7f9b69d 3387 
octave_5.1.0-2.dsc
 7a8ba08be4aeeb1280e20e7bc8266a22bd3acb5b53e0fa162b606bdb52e50320 72016 
octave_5.1.0-2.debian.tar.xz
 b2cb41d54470577fceb80791faa3707a42d789a71808f4c6e88c0c60d2e5 21555 
octave_5.1.0-2_amd64.buildinfo
Files:
 5cade59220d3e7ca2d2818c0d77a5345 3387 math optional octave_5.1.0-2.dsc
 e98b642bfb5590f4b08a24f450889331 72016 math optional 
octave_5.1.0-2.debian.tar.xz
 02fc0f3b2addb37b328a140c7f4a9748 21555 math optional 
octave_5.1.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAl2RFi4ACgkQLOzpNQ7O
vkrMixAAjL5NMbtWqNpwIir7Y0hHWEp17KpDwJpMVXsZ+zlbhhvcyhZjwNXjzvcX
PogJYq11XCtKIL9gM4/9Uq36BhVqqYPoj0cbYo9yFa1bhKA/tvPKVhlQOieQUGp4
uLwiyKFAu4vggEgEbS4LYbePJi+QDCYZpst2FOaJAqv4oorVXEp4CsrUCGisbJ/B
8Z2xWAut+6p+1gcKsomS9tFlJ9ZpkAPuCeUd8ey/wr/hf0YdfCVz8VwAS13zZBcz
sNNb8QOdFjpBjvSSk9PnnTNFZJqEuZ+NavDMPKtm+eNO1c00Cd5zaMV8tUPac6vM
yCr8IsX5ZCKX6ZXsKnDBAu5FR6CeTqLYlf+6G2/OBduq++0Ubf/RoECG9B/MFO3K
z5hQfz781J2AyawGHECWhRKz6494l4+WW9D759+pW0jSDoWiu2+ZlDN0HF2AGVtr
aprbntlNnIIgG3XXLet4GgkeTA6pN2W+Zk0qLneuZpmXRNR/rKsdN9aegGYpfpon
FMbXBb1sZEFZQXFjcMn0swx4s5tyzzzvIB0r8QjC9BopS3AChbwR+WNIY+AoRKZT
b78Y16r5FR9fo911kHpNT5nUqBjUmptm/NIboHt4r3c333eSc0DaBoZeUJ8KYbeI
vvDbQoeeNQVNUsfl1VMjui0IVir7N0EBMWjdFo/iLjpSA+xWk7Y=
=jheo
-END PGP SIGNATURE End Message ---

Bug#926047: marked as done (missing licenses)

[Debian Bug Tracking System]

Your message dated Sun, 29 Sep 2019 21:05:33 +
with message-id 
and subject line Bug#926047: fixed in octave 5.1.0-2
has caused the Debian Bug report #926047,
regarding missing licenses
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.)


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

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

Please add the missing licenses of:
 etc/fonts/*.otf
to your debian/copyright.

While you are at it, our hardworking trainees found:
  ./display-available.h:Copyright (C) 2012-2019 John W. Eaton
  ./main.in.cc:Copyright (C) 2012-2019 John W. Eaton
  ./main-gui.cc:Copyright (C) 2012-2019 John W. Eaton
  ./main-cli.cc:Copyright (C) 2012-2019 John W. Eaton
  ./display-available.c:Copyright (C) 2012-2019 John W. Eaton

Thanks!
  Thorsten
--- End Message ---
--- Begin Message ---
Source: octave
Source-Version: 5.1.0-2

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

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated octave 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, 29 Sep 2019 22:03:24 +0200
Source: octave
Architecture: source
Version: 5.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Octave Group 
Changed-By: Sébastien Villemot 
Closes: 926047 932975
Changes:
 octave (5.1.0-2) unstable; urgency=medium
 .
   [ Sébastien Villemot ]
   * d/copyright: add entry for etc/fonts/* (Closes: #926047)
   * Bump to S-V 4.4.1
 .
   [ Rafael Laboissiere ]
   * d/control: Build-depend on texlive-plain-generic, instead of
 -generic-recommended (Closes: #932975)
Checksums-Sha1:
 e5e6e4e49fd194e1f6b23a93d25fbba6c0541cdc 3387 octave_5.1.0-2.dsc
 27d412dc9d7b3a6602c1fc0742ec31a47ae98653 72016 octave_5.1.0-2.debian.tar.xz
 28ff14a90bcfcbba1d8e0597b741eef20fdd8978 21555 octave_5.1.0-2_amd64.buildinfo
Checksums-Sha256:
 88a22582fb6f909eab8a95099c9883af87ffdae9ad5fe1ac41dbfb9cf7f9b69d 3387 
octave_5.1.0-2.dsc
 7a8ba08be4aeeb1280e20e7bc8266a22bd3acb5b53e0fa162b606bdb52e50320 72016 
octave_5.1.0-2.debian.tar.xz
 b2cb41d54470577fceb80791faa3707a42d789a71808f4c6e88c0c60d2e5 21555 
octave_5.1.0-2_amd64.buildinfo
Files:
 5cade59220d3e7ca2d2818c0d77a5345 3387 math optional octave_5.1.0-2.dsc
 e98b642bfb5590f4b08a24f450889331 72016 math optional 
octave_5.1.0-2.debian.tar.xz
 02fc0f3b2addb37b328a140c7f4a9748 21555 math optional 
octave_5.1.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAl2RFi4ACgkQLOzpNQ7O
vkrMixAAjL5NMbtWqNpwIir7Y0hHWEp17KpDwJpMVXsZ+zlbhhvcyhZjwNXjzvcX
PogJYq11XCtKIL9gM4/9Uq36BhVqqYPoj0cbYo9yFa1bhKA/tvPKVhlQOieQUGp4
uLwiyKFAu4vggEgEbS4LYbePJi+QDCYZpst2FOaJAqv4oorVXEp4CsrUCGisbJ/B
8Z2xWAut+6p+1gcKsomS9tFlJ9ZpkAPuCeUd8ey/wr/hf0YdfCVz8VwAS13zZBcz
sNNb8QOdFjpBjvSSk9PnnTNFZJqEuZ+NavDMPKtm+eNO1c00Cd5zaMV8tUPac6vM
yCr8IsX5ZCKX6ZXsKnDBAu5FR6CeTqLYlf+6G2/OBduq++0Ubf/RoECG9B/MFO3K
z5hQfz781J2AyawGHECWhRKz6494l4+WW9D759+pW0jSDoWiu2+ZlDN0HF2AGVtr
aprbntlNnIIgG3XXLet4GgkeTA6pN2W+Zk0qLneuZpmXRNR/rKsdN9aegGYpfpon
FMbXBb1sZEFZQXFjcMn0swx4s5tyzzzvIB0r8QjC9BopS3AChbwR+WNIY+AoRKZT
b78Y16r5FR9fo911kHpNT5nUqBjUmptm/NIboHt4r3c333eSc0DaBoZeUJ8KYbeI
vvDbQoeeNQVNUsfl1VMjui0IVir7N0EBMWjdFo/iLjpSA+xWk7Y=
=jheo
-END PGP SIGNATURE End Message ---

Bug#940498: marked as done (jackson-databind: CVE-2019-14540 CVE-2019-16335)

[Debian Bug Tracking System]

Your message dated Sun, 29 Sep 2019 20:42:24 +
with message-id 
and subject line Bug#940498: fixed in jackson-databind 2.10.0-1
has caused the Debian Bug report #940498,
regarding jackson-databind: CVE-2019-14540 CVE-2019-16335
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.)


-- 
940498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jackson-databind
Version: 2.9.9.3-1
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

The following vulnerabilities were published for jackson-databind.

CVE-2019-14540[0]:
| A Polymorphic Typing issue was discovered in FasterXML jackson-
| databind before 2.9.10. It is related to
| com.zaxxer.hikari.HikariConfig.


CVE-2019-16335[1]:
| A Polymorphic Typing issue was discovered in FasterXML jackson-
| databind before 2.9.10. It is related to
| com.zaxxer.hikari.HikariDataSource. This is a different vulnerability
| than CVE-2019-14540.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-14540
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14540
[1] https://security-tracker.debian.org/tracker/CVE-2019-16335
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16335
[1] https://github.com/FasterXML/jackson-databind/issues/2410
[2] https://github.com/FasterXML/jackson-databind/issues/2449

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

p.s.: wondering where that will going to end ;-)
--- End Message ---
--- Begin Message ---
Source: jackson-databind
Source-Version: 2.10.0-1

We believe that the bug you reported is fixed in the latest version of
jackson-databind, 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.
Markus Koschany  (supplier of updated jackson-databind 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, 29 Sep 2019 21:51:57 +0200
Source: jackson-databind
Architecture: source
Version: 2.10.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Closes: 898140 940498
Changes:
 jackson-databind (2.10.0-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 2.10.0.
 -Fix CVE-2019-14540 and CVE-2019-16335: Polymorphic Typing issues.
 (Closes: #940498) Thanks to Salvatore Bonaccorso for the report.
   * Declare compliance with Debian Policy 4.4.1.
   * Update base-pom.patch for new release.
   * Remove Wolodja Wentland from Uploaders. Add myself to it. (Closes: #898140)
Checksums-Sha1:
 007bc9bc870c07686543b945531601564c00dc61 2689 jackson-databind_2.10.0-1.dsc
 0d29a12dd73e668f9b00688a0ddbb932211be705 1306929 
jackson-databind_2.10.0.orig.tar.gz
 033df104b8bb65e2a6a44247fe80aee662c2ee4b 5336 
jackson-databind_2.10.0-1.debian.tar.xz
 0335d4cf4afcc7d43e30197c95fe22ccd59d272d 16723 
jackson-databind_2.10.0-1_amd64.buildinfo
Checksums-Sha256:
 00101f834a2cf7adaa09d5e77c063518c351eaf1f6f4e876ae028c750a002426 2689 
jackson-databind_2.10.0-1.dsc
 8d00ebf75a4e1e615762e35c8bdb1f4980b6141a75ae2c8234e3cd671994abae 1306929 
jackson-databind_2.10.0.orig.tar.gz
 27b1c1c9c010ec8c3972985d757c86498a1ae7391df612e04271ebe7a1e78c0c 5336 
jackson-databind_2.10.0-1.debian.tar.xz
 81df14b5c7f8114824ff0908e4b25605fd26501146c10c0b66b177eb572e01c9 16723 
jackson-databind_2.10.0-1_amd64.buildinfo
Files:
 796dce3ecd99fd4930b2f2fe85d20ab7 2689 java optional 
jackson-databind_2.10.0-1.dsc
 9d65f85cd5665de881904565fe30ae13 1306929 java optional 
jackson-databind_2.10.0.orig.tar.gz
 ab6e161fe2aeb522b304bcfccd6b7197 5336 java optional 
jackson-databind_2.10.0-1.debian.tar.xz
 7424c9ba8922b94bcef9a38e15b1 16723 java optional 
jackson-databind_2.10.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl2REApfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYz

Bug#875172: [rlplot] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sat, Sep 09, 2017 at 11:09:19PM +0200, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Source: rlplot
> Version: 1.5-3
> Severity: wishlist
> User: debian-qt-...@lists.debian.org
> Usertags: qt4-removal
> 
> 
> Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> as [announced] in:
> 
> [announced] 
> 
> 
> Currently Qt4 has been dead upstream and we are starting to have problems
> maintaining it, like for example in the [OpenSSL 1.1 support] case.
> 
> [OpenSSL 1.1 support] 
> 
> 
> In order to make this move, all packages directly or indirectly depending on
> the Qt4 libraries have to either get ported to Qt5 or eventually get
> removed from the Debian repositories.
> 
> Therefore, please take the time and:
> - contact your upstream (if existing) and ask about the state of a Qt5
> port of your application
> - if there are no activities regarding porting, investigate whether there are
> suitable alternatives for your users
> - if there is a Qt5 port that is not yet packaged, consider packaging it
> - if both the Qt4 and the Qt5 versions already coexist in the Debian
> archives, consider removing the Qt4 version

rlplot is dead upstream, does anyone intend to port it themselves? Otherwise
let's remove it, we're moving forward with the Qt4 removal.

Cheers,
Moritz

Bug#874870: Version 2.x is qt5-based

[Moritz Mühlenhoff]

On Sun, Mar 18, 2018 at 09:11:24PM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Hi! Version 2.x is qt5-based. Please check if you can update this game. Feel 
> free to ask for help with Qt5 if needed.

It's been 1.5 years and we're now moving forward with the Qt4 removal. The 
package
hasn't been uploaded since 2017, does anyone plan to update in the next weeks,
otherwise it'll be removed along with Qt4.

Cheers,
Moritz

Processed: tagging 939651

[Debian Bug Tracking System]

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

> tags 939651 + buster
Bug #939651 [meteo-qt] meteo-qt/buster crashes immediately because of changed 
openweathermap data structure
Added tag(s) buster.
> thanks
Stopping processing here.

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

Bug#941376: Should monotone be removed?

[Moritz Muehlenhoff]

Source: monotone
Severity: serious

Should monotone be removed? Dead upstream, last upload three years ago
and removed from testing since 1.5 years.

Cheers,
Moritz

Bug#940498: jackson-databind: CVE-2019-14540 CVE-2019-16335

[Markus Koschany]

Control: tags -1 pending

On Mon, 16 Sep 2019 15:14:37 +0200 Salvatore Bonaccorso
 wrote:
> Source: jackson-databind
> Version: 2.9.9.3-1
> Severity: grave
> Tags: security upstream
> Justification: user security hole

[...]

> p.s.: wondering where that will going to end ;-)

Hi,

I also think it is starting to get silly now. I will upload 2.10.0 to
unstable shortly but I suggest to address these kind of issues from now
on only via stable-updates. This can be done two or three times per
year. It is basically just adding new classes to the blacklist. I
believe the whole approach of blacklisting classes is not very
sophisticated.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Processed: Re: jackson-databind: CVE-2019-14540 CVE-2019-16335

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #940498 [src:jackson-databind] jackson-databind: CVE-2019-14540 
CVE-2019-16335
Added tag(s) pending.

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

Bug#935042: Patch for avoid phoning home

[marcos]

Hello

The CheckUpdates() function is executed every time an audit is done. It
makes a DNS query and uses the TXT field of the DNS record for  this.
You can check if you have latest version by running "dig -t TXT
lynis-latest-version.cisofy.com" but you  would be "phoning home"
yourself :-).

The package will be removed soon if the bug isn't fixed, so i cc the
pkg-security team asking for sponsorship in case the maintainer is not
available.

Greetings,

Marcos

Description: The CheckUpdates() function is executed every time an audit is done. It makes a DNS query and uses the TXT field of the DNS record for this. This patch cancels this function. You can check if you have latest version by running "dig -t TXT lynis-latest-version.cisofy.com" but you would be "phoning home" yourself :-).  
Author: Marcos Fouces 
Debian-Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935042
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/

--- a/include/functions
+++ b/include/functions
@@ -254,29 +254,7 @@
 
 
 CheckUpdates() {
-PROGRAM_LV="00"; DB_MALWARE_LV="00"; DB_FILEPERMS_LV="00"
-if [ ${RUN_UPDATE_CHECK} -eq 1 ]; then
-LYNIS_LV_RECORD="lynis-latest-version.cisofy.com."
-FIND=$(which dig 2> /dev/null | grep -v "no [^ ]* in")
-if [ ! -z "${FIND}" ]; then
-PROGRAM_LV=$(dig +short +time=3 -t txt lynis-latest-version.cisofy.com 2> /dev/null | grep -v "connection timed out" | sed 's/[".]//g' | grep "^[1-9][0-9][0-9]$")
-else
-FIND=$(which host 2> /dev/null | grep -v "no [^ ]* in ")
-if [ ! -z "${FIND}" ]; then
-PROGRAM_LV=$(host -t txt -W 3 lynis-latest-version.cisofy.com 2> /dev/null | grep -v "connection timed out" | awk '{ if ($1=="lynis-latest-version.cisofy.com" && $3=="text") { print $4 }}' | sed 's/"//g' | grep "^[1-9][0-9][0-9]$")
-if [ "${PROGRAM_LV}" = "" ]; then PROGRAM_LV=0; fi
-else
-FIND=$(which drill 2> /dev/null | grep -v "no [^ ]* in ")
-if [ ! -z "${FIND}" ]; then
-PROGRAM_LV=$(drill txt ${LYNIS_LV_RECORD} | awk '{ if ($1=="lynis-latest-version.cisofy.com." && $4=="TXT") { print $5 }}' | tr -d '"' | grep "^[1-9][0-9][0-9]$")
-if [ -z "${PROGRAM_LV}" ]; then PROGRAM_LV=0; fi
-else
-LogText "Result: dig, drill or host not installed, update check skipped"
-UPDATE_CHECK_SKIPPED=1
-fi
-fi
-fi
-fi
+echo "In Debian distro package, check for updates are disabled."
 }
 
 

Bug#941008: marked as done (loggerhead, multiple dependency issues.)

[Debian Bug Tracking System]

Your message dated Sun, 29 Sep 2019 18:49:38 +
with message-id 
and subject line Bug#941008: fixed in loggerhead 1.19~bzr494-1
has caused the Debian Bug report #941008,
regarding loggerhead, multiple dependency issues.
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.)


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

Package: loggerhead
Version: 1.19~bzr479+dfsg-3
Severity: serious

Loggerhead has multiple dependency issues.

The loggerhead source package build-depends on python-subunit which is no 
longer built by the subunit source package.

The loggerhead source package build-depends on python-bzrlib.tests || bzr (<< 
2.4.0~beta1-2), the former is no longer built by the bzr source package and the 
latter fails version constraints (the current version of bzr is 2.7.0+bzr6622+brz )

The loggerhead binary package depends on python-bzrlib, which is no longer 
built by the bzr source package.

I notice these issues seem to be fixed in experimental by turning loggerhead 
into a transitional package to loggerhead-breezy. Should the experimental 
package simply be uploaded to unstable?
--- End Message ---
--- Begin Message ---
Source: loggerhead
Source-Version: 1.19~bzr494-1

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

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

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

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated loggerhead 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, 29 Sep 2019 18:28:06 +
Source: loggerhead
Architecture: source
Version: 1.19~bzr494-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Bazaar Maintainers 
Changed-By: Jelmer Vernooij 
Closes: 941008
Changes:
 loggerhead (1.19~bzr494-1) unstable; urgency=medium
 .
   * New upstream snapshot. Closes: #941008
   * Use set -e rather than passing -e on the shebang-line.
   * Bump debhelper from old 11 to 12.
   * Remove obsolete fields Name from debian/upstream/metadata.
   * Bump standards version to 4.4.0.
   * Use secure URI in debian/watch.
   * Trim trailing whitespace.
   * Use secure copyright file specification URI.
   * Bump standards version to 4.2.1 (no changes).
   * Add autokgtest test that runs the testsuite.
   * Remove unnecessary X-Python{,3}-Version field in debian/control.
Checksums-Sha1:
 65a8fceed4cedabc4aa03998ebe44a8b64c032d8 2576 loggerhead_1.19~bzr494-1.dsc
 87a3166f0d75867dd1a44ae7493a49e5e940cbc9 717634 
loggerhead_1.19~bzr494.orig.tar.gz
 adb504a508edd735408c92105a95754381756b53 10080 
loggerhead_1.19~bzr494-1.debian.tar.xz
 d1b240dc65b696f043153ab53f71b244cb4bc28d 8037 
loggerhead_1.19~bzr494-1_amd64.buildinfo
Checksums-Sha256:
 15146c142b1fa9d123c63a3f4b1ce4b655e6299b4eaf9cdddb947593a39b76fc 2576 
loggerhead_1.19~bzr494-1.dsc
 8ab988b90d6f5abfcefbc88265bdc9531fbd532bfc9253916aa9e9ebd486ce77 717634 
loggerhead_1.19~bzr494.orig.tar.gz
 0ecfedf5f28390802e81bc18e8d1c21a7815dc5c8b84f93c71c67abddbb69efc 10080 
loggerhead_1.19~bzr494-1.debian.tar.xz
 7548b74083204a7506f4997c773e7e1f961204d3159579cf22ac9bea1d57aa8e 8037 
loggerhead_1.19~bzr494-1_amd64.buildinfo
Files:
 5067c1e246df1d0fa9170e1a909cae6b 2576 devel optional 
loggerhead_1.19~bzr494-1.dsc
 181bae838240c0d672cb35ed76fe8eb6 717634 devel optional 
loggerhead_1.19~bzr494.orig.tar.gz
 9c5737bff370d6a22626fb32fd21d471 10080 devel optional 
loggerhead_1.19~bzr494-1.debian.tar.xz
 a59eaab38a25fe1ccf38760fbf8e92c2 8037 devel optional 
loggerhead_1.19~bzr494-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAl2Q+GkACgkQV5wWDUye
I+ig4g/+ODOmw7WYgSJIAzfMb4OCm0rZJRE3mRM5lcqPN6dPoCcCHoSYnVKtAZH0
mN3bFWZ4iUqr+GXHT81YeuklzHZpxvocbrDx29PC355xQ8ywQ21dBrszs+XrZqb5
UxwTuta/rELHkv2Z4zxXSxpygQ7q76WLPPQIFzFf2pHqSdl2TucxNVzo6793ckP8
LiRodV6VIT0iU5qdGgPJXD+Ns9hQbmgRDn0rw01p/PywiArwgAIk44CmaMk8PhqN
s9e05deaj/Bj0s4jGFI8KSG+18Zkk7xjIJpqzIOrtfXGc96H1QSJ9nQYQUgy6T8T
ts3wn+ag8+ZCFK1acr13sKk2s8CWA/4FMQBwWijUElyVUVw6+GmXjpBkFTiRMatI
AfuJHWDsXevmqWyLXzP/SfRW8mZ8kKw/xYJs8u6xXY2Qyl

Bug#923190: marked as done (ghdl: Allow building against LLVM 8)

[Debian Bug Tracking System]

Your message dated Sun, 29 Sep 2019 17:34:43 +
with message-id 
and subject line Bug#923190: fixed in ghdl 0.35+git20181129+dfsg-4
has caused the Debian Bug report #923190,
regarding ghdl: Allow building against LLVM 8
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.)


-- 
923190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ghdl
Version: 0.35+git20181129+dfsg-3
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch

Dear Maintainer,

Please allow building against LLVM 8 in the configure file. We've done
this in Ubuntu, and it builds successfully. We needed to make this
change because LLVM 8 is now default in our development release, and it
likely will change soon for Debian as well with the final release out
shortly.

In Ubuntu, the attached patch was applied to achieve the following:

  * Allow building against LLVM 8, which was recently made default in Ubuntu.

Thanks for considering the patch.

Logan Rosen

-- System Information:
Debian Release: buster/sid
  APT prefers cosmic-updates
  APT policy: (500, 'cosmic-updates'), (500, 'cosmic-security'), (500, 
'cosmic'), (400, 'cosmic-proposed'), (100, 'cosmic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-15-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru ghdl-0.35+git20181129+dfsg/debian/patches/allow-llvm-8 
ghdl-0.35+git20181129+dfsg/debian/patches/allow-llvm-8
--- ghdl-0.35+git20181129+dfsg/debian/patches/allow-llvm-8  1969-12-31 
19:00:00.0 -0500
+++ ghdl-0.35+git20181129+dfsg/debian/patches/allow-llvm-8  2019-02-22 
22:17:32.0 -0500
@@ -0,0 +1,10 @@
+--- a/configure
 b/configure
+@@ -238,6 +238,7 @@
+check_version 5.0 $llvm_version ||
+check_version 6.0 $llvm_version ||
+check_version 7.0 $llvm_version ||
++   check_version 8.0 $llvm_version ||
+false; then
+   echo "Debugging is not enabled with llvm $llvm_version"
+   llvm_be=llvm4-nodebug
diff -Nru ghdl-0.35+git20181129+dfsg/debian/patches/series 
ghdl-0.35+git20181129+dfsg/debian/patches/series
--- ghdl-0.35+git20181129+dfsg/debian/patches/series2018-12-11 
16:37:29.0 -0500
+++ ghdl-0.35+git20181129+dfsg/debian/patches/series2019-02-22 
22:16:56.0 -0500
@@ -3,3 +3,4 @@
 modify-install-paths
 adjust-compile-flags
 extend-ghdl-manpage
+allow-llvm-8
--- End Message ---
--- Begin Message ---
Source: ghdl
Source-Version: 0.35+git20181129+dfsg-4

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

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

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

Debian distribution maintenance software
pp.
Jonathan McDowell  (supplier of updated ghdl 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, 29 Sep 2019 18:05:58 +0100
Source: ghdl
Architecture: source
Version: 0.35+git20181129+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Jonathan McDowell 
Closes: 923190
Changes:
 ghdl (0.35+git20181129+dfsg-4) unstable; urgency=medium
 .
   * Team upload.
   * Allow building with LLVM 8+. Patch thanks to Logan Rosen (Closes: #923190)
Checksums-Sha1:
 926a71b677ae9aaee4f3ef2c5ea9ac14c09c6bd3 2555 ghdl_0.35+git20181129+dfsg-4.dsc
 0df465ab13fb3e6147d5af53da10e85b258c228c 18476 
ghdl_0.35+git20181129+dfsg-4.debian.tar.xz
 793a3450bd7f69e48e3550ae1af5ecb3a992b115 9000 
ghdl_0.35+git20181129+dfsg-4_amd64.buildinfo
Checksums-Sha256:
 6224443b5a543558a223e17411077573c4399dad14b2458d274eb058e6896764 2555 
ghdl_0.35+git20181129+dfsg-4.dsc
 c00fcf8e7ee12557fc5629d49268bf1a3f324d7fc80a820784ee73bd608dfd21 18476 
ghdl_0.35+git20181129+dfsg-4.debian.tar.xz
 faeaeb66d08d8aef6f12fcd6c17a9981ee72d7ee249381cf9ec1885da8a8ca61 9000 
ghdl_0.35+git20181129+dfsg-4_amd64.bu

Processed: Fixup GHDL LLVM issue bugs correctly

[Debian Bug Tracking System]

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

> severity 930890 wishlist
Bug #930890 [src:ghdl] Update GHDL packaging for newer releases
Severity set to 'wishlist' from 'serious'
> severity 923190 serious
Bug #923190 [ghdl] ghdl: Allow building against LLVM 8
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#941363: [filezilla] Filezilla doesn't start, returns an undefined symbol error

[rastersoft]

Package: filezilla
Version: 3.39.0-2
Severity: grave

--- Please enter the report below this line. ---

When trying to launch it, nothing happens. When launching from a command 
line, it returns:


    filezilla: symbol lookup error: filezilla: undefined symbol: 
_ZTIN2fz6threadE


Tried to uninstall (and purge) the package and reinstall, but still fails.

Tried the binary (version 3.44.2) downloaded directly from Filezilla 
home page (dinamically linked, and links against the libfilezilla file 
from debian itself) and works fine.



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

Debian Release: bullseye/sid
500 unstable-debug debug.mirrors.debian.org
500 unstable ftp.debian.org
500 suldr www.bchemnet.com
500 stable repo.skype.com
500 stable linux.teamviewer.com
500 stable dl.google.com

--- Package information. ---
Depends (Version) | Installed
===-+-
filezilla-common (= 3.39.0-2) | 3.39.0-2
libatk1.0-0 (>= 1.12.4) | 2.34.0-1
libc6 (>= 2.28) |
libcairo2 (>= 1.2.4) |
libdbus-1-3 (>= 1.9.14) |
libfilezilla0 (>= 0.15.1) |
libfontconfig1 (>= 2.12.6) |
libfreetype6 (>= 2.2.1) |
libgcc1 (>= 1:3.0) |
libgdk-pixbuf2.0-0 (>= 2.22.0) |
libglib2.0-0 (>= 2.16.0) |
libgnutls30 (>= 3.6.5) |
libgtk2.0-0 (>= 2.10.0) |
libhogweed4 |
libnettle6 |
libpango-1.0-0 (>= 1.14.0) |
libpangocairo-1.0-0 (>= 1.14.0) |
libpangoft2-1.0-0 (>= 1.14.0) |
libpugixml1v5 (>= 1.7) |
libsqlite3-0 (>= 3.5.9) |
libstdc++6 (>= 5.2) |
libwxbase3.0-0v5 (>= 3.0.4+dfsg) |
libwxgtk3.0-0v5 (>= 3.0.4+dfsg) |


Recommends (Version) | Installed
=-+-===
xdg-utils | 1.1.3-1


Package's Suggests field is empty.

--
Nos leemos
 RASTER(Linux user #228804)
ras...@rastersoft.com  http://www.rastersoft.com

Processed: tagging 940564

[Debian Bug Tracking System]

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

> tags 940564 + ftbfs
Bug #940564 [src:racon] racon: FTBFS against libspoa3
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#941362: openimageio: FTBFS on armel and mipsel with openexr 2.3.0-6

[Paul Gevers]

Source: openimageio
Version: 2.0.10~dfsg0-1
Severity: serious
Tags: ftbfs
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainer,

Your package is part of the openexr transition, but it fails to build on armel
and mipsel.

Paul

Tail of log for openimageio on armel:

[ 77%] Building CXX object 
src/libOpenImageIO/CMakeFiles/OpenImageIO.dir/__/include/OpenImageIO/pugixml.cpp.o
cd "/<>/build/src/libOpenImageIO" && /usr/bin/c++  
-DEMBED_PLUGINS=1 -DOpenImageIO_EXPORTS -DUSE_BOOST_ASIO=1 -DUSE_DCMTK=1 
-DUSE_FFMPEG -DUSE_FREETYPE -DUSE_GIF -DUSE_LIBRAW=1 -DUSE_OCIO=1 -DUSE_OPENCV 
-DUSE_OPENJPEG -DUSE_OPENVDB=1 -DUSE_STD_REGEX -DUSE_TBB=1 -DUSE_WEBP=1 
-D__STDC_CONSTANT_MACROS -D__STDC_LIMIT_MACROS 
-I"/<>/build/include" -I"/<>/src/include" 
-I/usr/include/arm-linux-gnueabi -I/usr/include/OpenEXR 
-I/usr/include/openjpeg-2.3 -I/usr/include/freetype2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC   -Wall 
-fno-math-errno -Wno-unused-local-typedefs -Wno-unused-result -Wno-aligned-new 
-Wno-noexcept-type -std=c++11 -UUSE_FIELD3D -o 
CMakeFiles/OpenImageIO.dir/__/include/OpenImageIO/pugixml.cpp.o -c 
"/<>/src/include/OpenImageIO/pugixml.cpp"
[ 77%] Linking CXX shared library libOpenImageIO.so
cd "/<>/build/src/libOpenImageIO" && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/OpenImageIO.dir/link.txt --verbose=1
/usr/bin/c++ -fPIC -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -latomic -shared 
-Wl,-soname,libOpenImageIO.so.2.0 -o libOpenImageIO.so.2.0.10 
CMakeFiles/OpenImageIO.dir/imagebufalgo.cpp.o 
CMakeFiles/OpenImageIO.dir/imagebufalgo_pixelmath.cpp.o 
CMakeFiles/OpenImageIO.dir/imagebufalgo_channels.cpp.o 
CMakeFiles/OpenImageIO.dir/imagebufalgo_compare.cpp.o 
CMakeFiles/OpenImageIO.dir/imagebufalgo_copy.cpp.o 
CMakeFiles/OpenImageIO.dir/imagebufalgo_deep.cpp.o 
CMakeFiles/OpenImageIO.dir/imagebufalgo_draw.cpp.o 
CMakeFiles/OpenImageIO.dir/imagebufalgo_addsub.cpp.o 
CMakeFiles/OpenImageIO.dir/imagebufalgo_muldiv.cpp.o 
CMakeFiles/OpenImageIO.dir/imagebufalgo_mad.cpp.o 
CMakeFiles/OpenImageIO.dir/imagebufalgo_orient.cpp.o 
CMakeFiles/OpenImageIO.dir/imagebufalgo_xform.cpp.o 
CMakeFiles/OpenImageIO.dir/imagebufalgo_yee.cpp.o 
CMakeFiles/OpenImageIO.dir/imagebufalgo_opencv.cpp.o 
CMakeFiles/OpenImageIO.dir/deepdata.cpp.o CMakeFiles/OpenImageIO.dir/exif.cpp.o 
CMakeFiles/OpenImageIO.dir/exif-canon.cpp.o 
CMakeFiles/OpenImageIO.dir/formatspec.cpp.o 
CMakeFiles/OpenImageIO.dir/imagebuf.cpp.o 
CMakeFiles/OpenImageIO.dir/imageinput.cpp.o 
CMakeFiles/OpenImageIO.dir/imageio.cpp.o 
CMakeFiles/OpenImageIO.dir/imageioplugin.cpp.o 
CMakeFiles/OpenImageIO.dir/imageoutput.cpp.o 
CMakeFiles/OpenImageIO.dir/iptc.cpp.o CMakeFiles/OpenImageIO.dir/xmp.cpp.o 
CMakeFiles/OpenImageIO.dir/color_ocio.cpp.o 
CMakeFiles/OpenImageIO.dir/maketexture.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libutil/argparse.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libutil/benchmark.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libutil/errorhandler.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libutil/filesystem.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libutil/farmhash.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libutil/filter.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libutil/hashes.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libutil/paramlist.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libutil/plugin.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libutil/SHA1.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libutil/strutil.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libutil/sysutil.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libutil/thread.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libutil/timer.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libutil/typedesc.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libutil/ustring.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libutil/xxhash.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libtexture/texturesys.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libtexture/texture3d.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libtexture/environment.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libtexture/texoptions.cpp.o 
CMakeFiles/OpenImageIO.dir/__/libtexture/imagecache.cpp.o 
CMakeFiles/OpenImageIO.dir/__/bmp.imageio/bmpinput.cpp.o 
CMakeFiles/OpenImageIO.dir/__/bmp.imageio/bmpoutput.cpp.o 
CMakeFiles/OpenImageIO.dir/__/bmp.imageio/bmp_pvt.cpp.o 
CMakeFiles/OpenImageIO.dir/__/cineon.imageio/cineoninput.cpp.o 
CMakeFiles/OpenImageIO.dir/__/cineon.imageio/libcineon/Cineon.cpp.o 
CMakeFiles/OpenImageIO.dir/__/cineon.imageio/libcineon/OutStream.cpp.o 
CMakeFiles/OpenImageIO.dir/__/cineon.imageio/libcineon/Codec.cpp.o 
CMakeFiles/OpenImageIO.dir/__/cineon.imageio/libcineon/Reader.cpp.o 
CMakeFiles/OpenImageIO.dir/__/cineon.imageio/libcineon/Writer.cpp.o 
CMakeFiles/OpenImageIO.dir/__/cineon.imageio/libcineon/CineonHeader.cpp.o 
CMakeFiles/OpenImageIO.dir/__/cineon.imageio/libcineon/ElementReadStream.cpp.o 
CMakeFiles/OpenImageIO.dir/__/cineon.imageio/libcineon/InStream.cpp.o 
CMa

Bug#941361: Can not detect external monitor which is connected to hybrid graphics

[gulfstream]

Package: xserver-xorg-video-intel
Version: 2:2.99.917+git20190815-1
Severity: grave

Hello, my laptop is Thinkpad P1 which has hybrid graphics. The one is Intel 
graphic card, the other is Nvidia P2000. It can not detect any external monitor 
which
connect to the Thinkpad P1's HDMI port.

How can I use the external monitor with my laptop?


Best regards,
Gulfstream



-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

Diversions concerning libGL are in place

diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/libGLESv2.so.2 to /usr/lib/mesa-diverted/libGLESv2.so.2 
by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLX_indirect.so.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLX_indirect.so.0 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.1.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2.1.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2.1.0 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLX_indirect.so.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so.2.1.0 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2.1.0 by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.2.0 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 
by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so.1.2.0 to 
/usr/lib/mesa-diverted/libGLESv1_CM.so.1.2.0 by glx-diversions
diversion of /usr/lib/libGLESv2.so to /usr/lib/mesa-diverted/libGLESv2.so by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by 
glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions
diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.7.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.7.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.0.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.0.0 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so by glx-diversions
diversion of /usr/lib/libGLX_indirect.so.0 to 
/usr/lib/mesa-diverted/libGLX_indirect.so.0 by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so to /usr/lib/mesa-diverted/libGLESv1_CM.so 
by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.

Bug#941128: xorg-server FTBFS

[Sven Joachim]

Control: found -1 2:1.19.1-1
Control: tags -1 bullseye sid

On 2019-09-28 19:06 +, Niels Thykier wrote:

> Control: reassign -1 xorg-server
> Control: retitle -1 xorg-server: build target must depend on build-*
> Control: tags -1 ftbfs
>
> Timo Aaltonen:
>> Package: debhelper
>> Severity: important
>>
>> Hi, debhelper 12.4 was fine but the current one broke xorg-server build,
>> build-indep isn't run at all. With the old version it was run right in
>> the beginning:
>>
>> dh build --with quilt,autoreconf --parallel
>>debian/rules build-indep
>> make[1]: Entering directory '/<>'
>> mkdir -p build-source
>> tar \
>> --owner=0 --group=0 \
>> --transform 's,^,xorg-server/,' \
>> --exclude=debian \
>> --exclude=autom4te.cache \
>> -cf - * | xz > build-source/xorg-server.tar.xz
>> tar: build-source/xorg-server.tar.xz: file changed as we read it
>>> build-source-stamp
>> dh build-indep --with quilt,autoreconf --parallel
>>dh_quilt_patch -i -O--parallel
>> Applying patch 001_fedora_extramodes.patch
>> patching file hw/xfree86/common/extramodes
>> ...
>>
>> but now it's skipped:
>>
>> dh build --with quilt,autoreconf --parallel
>>dh_quilt_patch -O--parallel
>> Applying patch 001_fedora_extramodes.patch
>> patching file hw/xfree86/common/extramodes
>> ...
>>
> This problem is fundamentally caused by xorg-server's "build" target not
> invoking build-arch and build-indep (eventually).  The xorg-server
> package is assumed to invoke all relevant build steps as a part of the
> build target itself but it fails to do the build-arch and build-indep
> steps as a part of its build target.

It seem this has been present since xorg-server's rules file was
switched to dh, but it only has become serious recently.

I had a look how to fix that, here is what I tried.

Naive approach 1:

--8<---cut here---start->8---
diff --git a/debian/rules b/debian/rules
index 7365fed6c..c5d5e5e03 100755
--- a/debian/rules
+++ b/debian/rules
@@ -34,8 +34,8 @@ override_dh_auto_build:
 override_dh_auto_test:
dh_auto_test -- -j1 VERBOSE=1

-build: abibumpcheck
-build-indep: build-source-stamp
+build build-arch: abibumpcheck
+build build-indep: build-source-stamp

 override_dh_auto_install:
dh_auto_install --builddirectory=debian/build/main \
--8<---cut here---end--->8---

Result was that make processed the build-source-stamp target first
before running dh_quilt_patch and dh_autoreonf.  This is bad, because
xorg-server-source is supposed to contain the patched and autoreconfed
source.

Naive approach 2:

--8<---cut here---start->8---
diff --git a/debian/rules b/debian/rules
index 7365fed6c..cbdd15c31 100755
--- a/debian/rules
+++ b/debian/rules
@@ -34,8 +34,9 @@ override_dh_auto_build:
 override_dh_auto_test:
dh_auto_test -- -j1 VERBOSE=1

-build: abibumpcheck
+build-arch: abibumpcheck
 build-indep: build-source-stamp
+build: build-arch build-indep

 override_dh_auto_install:
dh_auto_install --builddirectory=debian/build/main \
--8<---cut here---end--->8---

This seems to work, but now a full (arch+indep) build configures and
builds the source tree twice, which wastes quite a bit of time.

In the end I decided to remove the build and build-indep targets
altogether[1], which does the trick for me (tested full, arch-only and
indep-only builds).

Cheers,
   Sven


1. 
https://salsa.debian.org/xorg-team/xserver/xorg-server/commit/c119638422dbb051d6f575e12df353b2cc3a0f44

Processed: Re: Bug#941128: xorg-server FTBFS

[Debian Bug Tracking System]

Processing control commands:

> found -1 2:1.19.1-1
Bug #941128 [xorg-server] xorg-server: build target must depend on build-*
There is no source info for the package 'xorg-server' at version '2:1.19.1-1' 
with architecture ''
Unable to make a source version for version '2:1.19.1-1'
Marked as found in versions 2:1.19.1-1.
> tags -1 bullseye sid
Bug #941128 [xorg-server] xorg-server: build target must depend on build-*
Added tag(s) sid and bullseye.

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

Bug#875047: marked as done ([midisnoop] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 29 Sep 2019 13:04:05 +
with message-id 
and subject line Bug#875047: fixed in midisnoop 0.1.2+git20141108.bc30f600187e-1
has caused the Debian Bug report #875047,
regarding [midisnoop] Future Qt4 removal from Buster
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.)


-- 
875047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: midisnoop
Version: 0.1.2~repack0-5
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: midisnoop
Source-Version: 0.1.2+git20141108.bc30f600187e-1

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

Debian distribution maintenance software
pp.
Dmitry Eremin-Solenikov  (supplier of updated midisnoop 
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, 29 Sep 2019 14:40:54 +0300
Source: midisnoop
Architecture: source
Version: 0.1.2+git20141108.bc30f600187e-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Dmitry Eremin-Solenikov 
Closes: 875047 937045
Changes:
 midisnoop (0.1.2+git20141108.bc30f600187e-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Felipe Sateler ]
   * Change maintainer address to debian-multime...@lists.debian.org
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat
 .
   [ Dmitry Eremin-Solenikov ]
   * New upstream version 0.1.2+git20141108.bc30f600187e
   * Update to qt5 (Closes: #875047)
   * Refresh debian patches
   * Add 0005-src-engine.h-another-qt5-fix.patch to fix compilation with qt5
   * d/gbp.conf: disable pristine tar for snapshot builds
   * d/control: Bump Standards-Version to 4.4.0 (no changes needed)
   * Switch to python3 (Closes: #937045)
   * d/control: add myself to uploaders
Checksums-Sha1:
 42614790221f6900b57a1980376b41d8820a6e2b 2264 
midisnoop_0.1.2+git20141108.bc30f600187e-1.dsc
 0001b6cb5b64b1fbc59ae318425af6b92324e659 47663 
midisnoop_0.1.2+git20141108.bc30f600187e.orig.tar.gz
 41996dd7816e3b8eb92c99354ff5353998493ff3 5628 
midisnoop_0.1.2+git20141108.bc30f600187e-1.deb

Bug#933091: node-rollup-plugin-typescript seems incompatible with rollup/typescript

[Pirate Praveen]

On Fri, 26 Jul 2019 21:06:12 +0530 Pirate Praveen
 wrote:
> package: node-rollup-plugin-typescript
> Version: 0.8.1-1
> Severity: serious
> Justification: the package is not usable
> 
> Got same error in node-locate-character and node-sourcemap-codec  (tried with 
> node-rollup-plugin-typescript 1.0.0 in git as well and got same error)
> 
> node-sourcemap-codec$ rollup -c   
>   src/sourcemap-codec.ts → 
> dist/sourcemap-codec.umd.js, dist/sourcemap-codec.es.js... [!] 
> Error: Unexpected token src/sourcemap-codec.ts (1:7)  
>   1: export type SourceMapSegment = ^ 
> 2:   | [number]   
>   3:   | [number, number, number, number]
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.

When running rollup -c in node-vlq repo (at tag debian/1.0.1-3), there
is another failure. I think this goes all the way down to
node-snapdragon incompatible update in experimental.

$ rollup -c
[!] TypeError: brackets.parser.capture is not a function
TypeError: brackets.parser.capture is not a function
at Snapdragon.parsers
(/usr/lib/nodejs/expand-brackets/lib/parsers.js:22:6)
at Snapdragon.use (/usr/lib/nodejs/snapdragon/index.js:60:6)
at parsers (/usr/lib/nodejs/extglob/lib/parsers.js:26:11)
at new Extglob (/usr/lib/nodejs/extglob/lib/extglob.js:30:3)
at create (/usr/lib/nodejs/extglob/index.js:220:15)
at Object.utils.memoize (/usr/lib/nodejs/extglob/lib/utils.js:36:13)
at Function.extglob.create (/usr/lib/nodejs/extglob/index.js:225:16)
at Object.extglob (/usr/lib/nodejs/extglob/index.js:37:18)
at Glob.extglob (/usr/lib/nodejs/micromatch/lib/glob.js:100:26)
at expand (/usr/lib/nodejs/micromatch/lib/expand.js:110:10)

After downgrading node-snapdragon to the version in unstable (0.8.1),
this error goes away we again get the same error as before.

Processed: tagging 939454

[Debian Bug Tracking System]

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

> tags 939454 + ftbfs
Bug #939454 [src:link-grammar] link-grammar ftbfs (symbols file mismatches)
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#832422: albatross-gtk-theme: broken with GTK3.20

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, 2019-09-29 at 07:10 -0400, Jeremy Bicha wrote:
> Control: severity -1 serious
> 
> I propose that we remove albatross-gtk-theme from Unstable & Bullseye.
> A GTK theme that doesn't work with GTK3 isn't very helpful any more.
> 
> https://github.com/shimmerproject/Albatross
> 
That'd be ok with me. I don't really have time or interest for this as a
maintainer, unfortunately.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl2QmowACgkQ3rYcyPpX
RFso3Qf6AmuxPvSVSuJzeM0iILrKNq4w4QrSloGkWZkk8QKkJdamfaH0v+ZylokZ
KpGnQXVUJTNHyPmxNuPU7AVo1t42xo3cUk/UbzYvjpQIMVV8QHaU7+umi4wNRONN
IRuvAWSku8IojA69TrmsRqwHtsyd13p51jJtfZizeiCUHfSkcD3YRd9aGkapR5bD
/3e356phzFYU0zsGmbkNKQrSiKAyMnPuZwq7X2flxHW6nxYdSnUfIXeakrwj+DcV
Bl/ND5+pVcttWdX6tUzO7Xgy/4t1BlCHIyV9DZezFc3HjtY8ykSFSAsuv3oMfvO2
pcPv/S+OFyrrncKTOxsdWrUXs+TBKA==
=hCB/
-END PGP SIGNATURE-

Processed: Re: [Pkg-javascript-devel] Bug#930634: Build failures with rollup 0.56

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 933091
Bug #930634 [rollup] Update rollup to new upstream release
930634 was blocked by: 941353 930635
930634 was not blocking any bugs.
Added blocking bug(s) of 930634: 933091

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

Bug#941353: Object.defineProperty should be used to set value to exports.__esModule

[Pirate Praveen]

Package: node-vlq, node-magic-string
severity: serious
justification: breaks rollup
Control: block 930634 by -1

See 

This line "exports.__esModule = true;" should be changed to
"Object.defineProperty(exports, '__esModule', { value: true });"

Processed: Object.defineProperty should be used to set value to exports.__esModule

[Debian Bug Tracking System]

Processing control commands:

> block 930634 by -1
Bug #930634 [rollup] Update rollup to new upstream release
930634 was blocked by: 930635
930634 was not blocking any bugs.
Added blocking bug(s) of 930634: 941353

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

Bug#941351: peruse: Peruse fails to start

[Matteo Settenvini]

Package: peruse
Version: 1.2+dfsg+20190713-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

attempting to run peruse (or perusecreator) from the command line
results in the following output:

~$ peruse
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use 
QT_QPA_PLATFORM=wayland to run on Wayland anyway.

(peruse:9225): Gtk-WARNING **: 13:14:48.393: Theme parsing error: gtk.css:6:20: 
The 'gtk-key-bindings' property has been renamed to '-gtk-ke
y-bindings'
Failed to load the component from disk. Reported error was: 
"file:///usr/share/peruse/qml/Main.qml:26 Type PeruseMain unavailable\nfile:///u
sr/share/peruse/qml/PeruseMain.qml:300 Type Settings 
unavailable\nfile:///usr/share/peruse/qml/Settings.qml:82 Type 
Kirigami.SwipeListItem u
navailable\nfile:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop/SwipeListItem.qml:25
 Type T.SwipeListItem una
vailable\nfile:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/SwipeListItem.qml:264
 Syntax error\n"

Peruse then fails to start and crashes.

Apparently this is an issue with
/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/SwipeListItem.qml:

   function updateVisibleActions(definitelyVisible = false) {

Default values for function parameters are not supported.
It should be:

   function updateVisibleActions(definitelyVisible) {
if (definitelyVisible === undefined) definitelyVisible = false;

Unfortunately, then it fails on a missing component:

(peruse:10096): Gtk-WARNING **: 13:24:30.678: Theme parsing error: 
gtk.css:6:20: The 'gtk-key-bindings' property has been renamed to '-gtk-k
ey-bindings'
Failed to load the component from disk. Reported error was: 
"file:///usr/share/peruse/qml/Main.qml:26 Type PeruseMain unavailable\nfile:///u
sr/share/peruse/qml/PeruseMain.qml:300 Type Settings 
unavailable\nfile:///usr/share/peruse/qml/Settings.qml:82 Type 
Kirigami.SwipeListItem u
navailable\nfile:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop/SwipeListItem.qml:25
 Type T.SwipeListItem una
vailable\nfile:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/SwipeListItem.qml:22
 module \"QtQuick.Controls\" version 2.7
 is not installed\n"

Cheers,
Matteo Settenvini

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

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

Versions of packages peruse depends on:
ii  kio 5.62.1-1
ii  libc6   2.29-2
ii  libgcc1 1:9.2.1-8
ii  libkf5archive5  5.62.0-1
ii  libkf5baloo55.62.0-2
ii  libkf5configcore5   5.62.0-1
ii  libkf5coreaddons5   5.62.0-1
ii  libkf5declarative5  5.62.0-1
ii  libkf5filemetadata3 5.62.0-1
ii  libkf5i18n5 5.62.0-1
ii  libkf5kiocore5  5.62.1-1
ii  libkf5kiowidgets5   5.62.1-1
ii  libqt5core5a5.11.3+dfsg1-4
ii  libqt5gui5  5.11.3+dfsg1-4
ii  libqt5qml5  5.11.3-4
ii  libqt5quick55.11.3-4
ii  libqt5sql5  5.11.3+dfsg1-4
ii  libqt5widgets5  5.11.3+dfsg1-4
ii  libstdc++6  9.2.1-8
ii  peruse-common   1.2+dfsg+20190713-1
ii  qml-module-org-kde-kirigami25.62.0-2
ii  qml-module-org-kde-newstuff 5.62.0-1
ii  qml-module-qt-labs-folderlistmodel  5.11.3-4
ii  qml-module-qt-labs-settings 5.11.3-4
ii  qml-module-qtquick-controls 5.11.3-2
ii  qml-module-qtquick-dialogs  5.11.3-2
ii  qml-module-qtquick-layouts  5.11.3-4

peruse recommends no packages.

peruse suggests no packages.

-- no debconf information

Processed: tagging 934382

[Debian Bug Tracking System]

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

> tags 934382 + ftbfs
Bug #934382 [src:cvxopt] cvxopt: FTBFS on non-amd64 architectures
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#934519: stretch-pu: package fence-agents/4.0.25-1+deb9u2

[Valentin Vidic]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Hi,

Please allow an update for fence-agents package fixing occasional FTBFS
reported in #934519. Patch for the change follows below.

diff -Nru fence-agents-4.0.25/debian/changelog 
fence-agents-4.0.25/debian/changelog
--- fence-agents-4.0.25/debian/changelog2019-06-30 19:01:55.0 
+0200
+++ fence-agents-4.0.25/debian/changelog2019-09-29 12:27:01.0 
+0200
@@ -1,3 +1,9 @@
+fence-agents (4.0.25-1+deb9u2) stretch; urgency=medium
+
+  * Update patch for removing fence_amt_ws (Closes: #934519)
+
+ -- Valentin Vidic   Sun, 29 Sep 2019 12:27:01 +0200
+
 fence-agents (4.0.25-1+deb9u1) stretch; urgency=medium
 
   * fence_rhevm: add patch for CVE-2019-10153 (Closes: #930887)
diff -Nru fence-agents-4.0.25/debian/patches/remove-fence_amt_ws 
fence-agents-4.0.25/debian/patches/remove-fence_amt_ws
--- fence-agents-4.0.25/debian/patches/remove-fence_amt_ws  2019-06-30 
19:01:55.0 +0200
+++ fence-agents-4.0.25/debian/patches/remove-fence_amt_ws  2019-09-29 
12:27:01.0 +0200
@@ -1,16 +1,16 @@
 --- a/configure.ac
 +++ b/configure.ac
-@@ -142,6 +142,9 @@ if test "x$AGENTS_LIST" = xall; then
-   AGENTS_LIST=`find $srcdir/fence/agents -mindepth 2 -maxdepth 2 -name 
'*.py' -printf '%P ' | sed -e 's#lib/[A-Za-z_.]* ##g' -e 
's#nss_wrapper/[A-Za-z_.]* ##g' -e 's#autodetect/[A-Za-z_.]* ##g'`
+@@ -139,7 +139,8 @@
+ fi
+ 
+ if test "x$AGENTS_LIST" = xall; then
+-  AGENTS_LIST=`find $srcdir/fence/agents -mindepth 2 -maxdepth 2 -name 
'*.py' -printf '%P ' | sed -e 's#lib/[A-Za-z_.]* ##g' -e 
's#nss_wrapper/[A-Za-z_.]* ##g' -e 's#autodetect/[A-Za-z_.]* ##g'`
++  # remove fence_amt_ws because we don't have openwsman (and sblim-sfcc) 
in Debian
++  AGENTS_LIST=`find $srcdir/fence/agents -mindepth 2 -maxdepth 2 -name 
'*.py' ! -name 'fence_amt_ws.py' -printf '%P ' | sed -e 's#lib/[A-Za-z_.]* ##g' 
-e 's#nss_wrapper/[A-Za-z_.]* ##g' -e 's#autodetect/[A-Za-z_.]* ##g'`
  fi
  
-+# remove fence_amt_ws because we don't have openwsman (and sblim-sfcc) in 
Debian
-+AGENTS_LIST=$(echo $AGENTS_LIST | sed -e "s!amt_ws/fence_amt_ws.py !!")
-+
  XENAPILIB=0
- if echo "$AGENTS_LIST" | grep -q xenapi; then
-   XENAPILIB=1
-@@ -163,7 +166,8 @@ AC_PYTHON_MODULE(suds, 1)
+@@ -163,7 +164,8 @@
  AC_PYTHON_MODULE(pexpect, 1)
  AC_PYTHON_MODULE(pycurl, 1)
  AC_PYTHON_MODULE(requests, 1)

Processed: tagging 933992

[Debian Bug Tracking System]

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

> tags 933992 + ftbfs
Bug #933992 [src:obus] obus FTBFS because it depends on lwt.syntax
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 933993

[Debian Bug Tracking System]

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

> tags 933993 + ftbfs
Bug #933993 [src:ocaml-usb] ocaml-usb FTBFS because it depends on lwt.syntax
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 940068

[Debian Bug Tracking System]

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

> tags 940068 + ftbfs
Bug #940068 [gr-gsm] gr-gsm FTBFS in unstable
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 931944

[Debian Bug Tracking System]

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

> tags 931944 + ftbfs
Bug #931944 [src:vtk7] vtk7: FTBFS with PROJ 6
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 935822

[Debian Bug Tracking System]

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

> tags 935822 + ftbfs
Bug #935822 [src:gr-dab] gr-dab: FTBFS with latest gnuradio
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 858774

[Debian Bug Tracking System]

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

> tags 858774 + ftbfs
Bug #858774 [gr-air-modes] modes_rx: ImportError: cannot import name QtWebKit
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 940071

[Debian Bug Tracking System]

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

> tags 940071 + ftbfs
Bug #940071 [gr-radar] gr-radar FTBFS in unstable.
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 925729

[Debian Bug Tracking System]

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

> tags 925729 + ftbfs
Bug #925729 [src:lammps] lammps: ftbfs with GCC-9
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: Re: albatross-gtk-theme: broken with GTK3.20

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #832422 [albatross-gtk-theme] albatross-gtk-theme: broken with GTK3.20
Severity set to 'serious' from 'important'

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

Processed: tagging 939826

[Debian Bug Tracking System]

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

> tags 939826 + ftbfs
Bug #939826 [src:bustle] bustle: ftbfs with new cabal
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#875047: marked as pending in midisnoop

[Dmitry Eremin-Solenikov]

Control: tag -1 pending

Hello,

Bug #875047 in midisnoop 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/multimedia-team/midisnoop/commit/b4b06a8b8d0f3dce361c0b03db4c2cff3420d97f


Update to qt5 (Closes: #875047)

Signed-off-by: Dmitry Eremin-Solenikov 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/875047

Processed: Bug#875047 marked as pending in midisnoop

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #875047 [src:midisnoop] [midisnoop] Future Qt4 removal from Buster
Ignoring request to alter tags of bug #875047 to the same tags previously set

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

Bug#934519: buster-pu: package fence-agents/4.3.3-2+deb10u1

[Valentin Vidic]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

Hi,

Please allow an update for fence-agents package fixing ocassional FTBFS
reported in #934519. Patch for the change follows below.

diff -Nru fence-agents-4.3.3/debian/changelog 
fence-agents-4.3.3/debian/changelog
--- fence-agents-4.3.3/debian/changelog 2019-06-23 19:53:35.0 +0200
+++ fence-agents-4.3.3/debian/changelog 2019-09-29 11:54:16.0 +0200
@@ -1,3 +1,9 @@
+fence-agents (4.3.3-2+deb10u1) buster; urgency=medium
+
+  * Update patch for removing fence_amt_ws (Closes: #934519)
+
+ -- Valentin Vidic   Sun, 29 Sep 2019 11:54:16 +0200
+
 fence-agents (4.3.3-2) unstable; urgency=high
 
   * fence_rhevm: add patch for CVE-2019-10153 (Closes: #930887)
diff -Nru fence-agents-4.3.3/debian/patches/remove-fence_amt_ws 
fence-agents-4.3.3/debian/patches/remove-fence_amt_ws
--- fence-agents-4.3.3/debian/patches/remove-fence_amt_ws   2018-10-06 
22:30:46.0 +0200
+++ fence-agents-4.3.3/debian/patches/remove-fence_amt_ws   2019-09-29 
11:52:14.0 +0200
@@ -6,13 +6,13 @@
 This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
 --- a/configure.ac
 +++ b/configure.ac
-@@ -176,6 +176,9 @@
-   AGENTS_LIST=`find $srcdir/agents -mindepth 2 -maxdepth 2 -name 
'fence_*.py' -print0 | xargs -0 | sed -e 's#[^ ]*/agents/##g' -e 
's#lib/[A-Za-z_.]* ##g' -e 's#nss_wrapper/[A-Za-z_.]* ##g' -e 
's#autodetect/[A-Za-z_.]* ##g'`
+@@ -175,7 +175,8 @@
+ fi
+ 
+ if test "x$AGENTS_LIST" = xall; then
+-  AGENTS_LIST=`find $srcdir/agents -mindepth 2 -maxdepth 2 -name 
'fence_*.py' -print0 | xargs -0 | sed -e 's#[^ ]*/agents/##g' -e 
's#lib/[A-Za-z_.]* ##g' -e 's#nss_wrapper/[A-Za-z_.]* ##g' -e 
's#autodetect/[A-Za-z_.]* ##g'`
++  # remove fence_amt_ws because we don't have openwsman (and sblim-sfcc) 
in Debian
++  AGENTS_LIST=`find $srcdir/agents -mindepth 2 -maxdepth 2 -name 
'fence_*.py' ! -name fence_amt_ws.py -print0 | xargs -0 | sed -e 's#[^ 
]*/agents/##g' -e 's#lib/[A-Za-z_.]* ##g' -e 's#nss_wrapper/[A-Za-z_.]* ##g' -e 
's#autodetect/[A-Za-z_.]* ##g'`
  fi
  
-+# remove fence_amt_ws because we don't have openwsman (and sblim-sfcc) in 
Debian
-+AGENTS_LIST=$(echo $AGENTS_LIST | sed -e "s!amt_ws/fence_amt_ws.py !!")
-+
  XENAPILIB=0
- if echo "$AGENTS_LIST" | grep -q xenapi; then
-   XENAPILIB=1

Processed: Bug#936248: RM: bubbros -- ROM; python2 removal; dead upstream

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #936248 [src:bubbros] bubbros: Python2 removal in sid/bullseye
Severity set to 'normal' from 'serious'
> reassign -1 ftp.debian.org
Bug #936248 [src:bubbros] bubbros: Python2 removal in sid/bullseye
Bug reassigned from package 'src:bubbros' to 'ftp.debian.org'.
No longer marked as found in versions bubbros/1.6.2-1.
Ignoring request to alter fixed versions of bug #936248 to the same values 
previously set
> retitle -1 RM: bubbros -- ROM; python2 removal; dead upstream
Bug #936248 [ftp.debian.org] bubbros: Python2 removal in sid/bullseye
Changed Bug title to 'RM: bubbros -- ROM; python2 removal; dead upstream' from 
'bubbros: Python2 removal in sid/bullseye'.

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

Bug#940034: libpam-systemd: Please relax Depends: systemd-sysv (was: Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful)

[Cristian Ionescu-Idbohrn]

On Sun, 29 Sep 2019, Mark Hindley wrote:
> On Sat, Sep 28, 2019 at 11:41:56AM +0200, Thorsten Glaser wrote:
> > On Sat, 28 Sep 2019, Cristian Ionescu-Idbohrn wrote:
> > 
> > > 1. install sysvinit-core; that removes systemd-sysv but nothing else 
> > >systemd related
> > 
> > > Souldn't that work?
> > 
> > It would, if but for libpam-systemd having a (somewhat questionable
> > but understandable) dependency on systemd-sysv. This is basically
> > what spawned this thread.
> > 
> > So we'll not be going there.
> 
> Thorsten is quite right.
> 
> There is already a separate bug concerning the libpam-systemd 
> systemd-sysv dependency. See https://bugs.debian.org/935304. That 
> would be a more appropriate place for you to add any comments you 
> may have regarding this aspect of the behaviour you have observed.

Following Mark's advice, here are my findings:

On Sun, 29 Sep 2019, Cristian Ionescu-Idbohrn wrote:
> 
> Right.  I see now what happens on my systems.  I have an older 
> version of systemd packages installed:
> 
> ,
> | Version: 238-5
> `
> 
> which depends on:
> 
> ,
> | systemd-shim (>= 10-3~) | systemd-sysv
> `
> 
> as I stopped systemd related package updates:
> 
> , [ /etc/apt/preferences.d/no-systemd ]
> | Package: systemd systemd-sysv systemd-sysv:i386 libsystemd0 libpam-systemd 
> | Pin: release o=Debian
> | Pin-Priority: -1
> `
> 
> at the point when systemd-shim was removed.

Does it mean that, in my case, the transition to elogind would be 
easier?


Cheers,

-- 
Cristian

Bug#936248: RM: bubbros -- ROM; python2 removal; dead upstream

[Juhani Numminen]

Control: severity -1 normal
Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: bubbros -- ROM; python2 removal; dead upstream

Dear FTP masters,

Please remove bubbros from unstable.

Bubbros requires Python 2 which is going to be removed and there have been
no upstream releases since 2013.

Regards,
Juhani Numminen

Processed: bug 939527 is forwarded to https://lists.gnu.org/archive/html/bug-vcdimager/2019-09/msg00000.html

[Debian Bug Tracking System]

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

> forwarded 939527 
> https://lists.gnu.org/archive/html/bug-vcdimager/2019-09/msg0.html
Bug #939527 [src:vcdimager] vcdimager contains one file with different license
Set Bug forwarded-to-address to 
'https://lists.gnu.org/archive/html/bug-vcdimager/2019-09/msg0.html'.
> thanks
Stopping processing here.

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

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

[Mark Hindley]

Cristian,

On Sat, Sep 28, 2019 at 11:41:56AM +0200, Thorsten Glaser wrote:
> On Sat, 28 Sep 2019, Cristian Ionescu-Idbohrn wrote:
> 
> > 1. install sysvinit-core; that removes systemd-sysv but nothing else 
> >systemd related
> 
> > Souldn't that work?
> 
> It would, if but for libpam-systemd having a (somewhat questionable
> but understandable) dependency on systemd-sysv. This is basically
> what spawned this thread.
> 
> So we’ll not be going there.

Thorsten is quite right.

There is already a separate bug concerning the libpam-systemd systemd-sysv
dependency. See https://bugs.debian.org/935304. That would be a more appropriate
place for you to add any comments you may have regarding this aspect of the
behaviour you have observed.

Mark

Processed: fixed 923592 in marble/4:19.08.1-1

[Debian Bug Tracking System]

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

> fixed 923592 marble/4:19.08.1-1
Bug #923592 {Done: Niels Thykier } [src:marble] marble: 
FTBFS dh_install: Cannot find (any matches for) 
"usr/share/metainfo/org.kde.plasma.worldmap.appdata.xml"
Bug #922639 {Done: Niels Thykier } [src:marble] marble-qt: 
building process does not complete
Marked as fixed in versions marble/4:19.08.1-1.
Marked as fixed in versions marble/4:19.08.1-1.
> thanks
Stopping processing here.

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

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

[Cristian Ionescu-Idbohrn]

On Sat, 28 Sep 2019, Thorsten Glaser wrote:
> On Sat, 28 Sep 2019, Cristian Ionescu-Idbohrn wrote:
> 
> > 1. install sysvinit-core; that removes systemd-sysv but nothing else 
> >systemd related
> 
> > Souldn't that work?
> 
> It would, if but for libpam-systemd having a (somewhat questionable
> but understandable) dependency on systemd-sysv. This is basically
> what spawned this thread.
> 
> So we'll not be going there.

Right.  I see now what happens on my systems.  I have an older version 
of systemd packages installed:

,
| Version: 238-5
`

which depends on:

,
| systemd-shim (>= 10-3~) | systemd-sysv
`

as I stopped systemd related package updates:

, [ /etc/apt/preferences.d/no-systemd ]
| Package: systemd systemd-sysv systemd-sysv:i386 libsystemd0 libpam-systemd 
| Pin: release o=Debian
| Pin-Priority: -1
`

at the point when systemd-shim was removed.


Cheers,

-- 
Cristian