Bug#941193: filezilla: Crash on startup: undefined symbol: _ZTIN2fz6threadE

[jfp]

Package: filezilla
Version: 3.39.0-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Crashes on startup with the folloing error:

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




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

Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ: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#831925: marked as done (docbook2odf: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute)

[Debian Bug Tracking System]

Your message dated Thu, 26 Sep 2019 03:54:17 +
with message-id 
and subject line Bug#941154: Removed package(s) from unstable
has caused the Debian Bug report #831925,
regarding docbook2odf: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: 
binary build with no binary artifacts found; cannot distribute
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.)


-- 
831925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: docbook2odf
Version: 0.244-1.1
Severity: important
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160720 qa-ftbfs qa-indep
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.  This rebuild was done by building only the architecture-independent
packages.  At the same time, a normal build succeeded, which points the
problem specifically to build-indep/binary-indep targets.


The specific error below usually happens there is a binary-indep target in
debian/rules which is either empty or does not do anything useful.

If all the arch-independent packages are dummy transitional packages released
with jessie, the easy fix is to drop them now. If not, debian/rules should be
modified so that the binary-indep target generates the architecture independent
packages (and only those).

After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, this package will be suitable to be uploaded in source-only form if
you wish.

I file this bug as severity: important, but Santiago Vila, who led this
effort (kudos to him), got approval from the release team to consider those
bugs RC for stretch. The severity will be increased to 'serious' shortly.
See #830997 for details.

Relevant part (hopefully):
>  fakeroot debian/rules binary-indep
> dh_testdir
> # Add here commands to compile the package.
> #/usr/bin/make
> #docbook-to-man debian/docbook2odf.sgml > docbook2odf.1
> touch build-stamp
> dh_testdir
> dh_testroot
> dh_clean -k 
> dh_clean: dh_clean -k is deprecated; use dh_prep instead
> dh_installdirs
> # Add here commands to install the package into debian/docbook2odf.
> #/usr/bin/make DESTDIR=/<>/debian/docbook2odf install
>  dpkg-genchanges --build=all >../docbook2odf_0.244-1.1_all.changes
> dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
> distribute

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/20/docbook2odf_0.244-1.1_unstable_archallonly.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 0.244-1.1+rm

Dear submitter,

as the package docbook2odf 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/941154

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#934935: marked as done (Should docbook2odf be removed?)

[Debian Bug Tracking System]

Your message dated Thu, 26 Sep 2019 03:54:17 +
with message-id 
and subject line Bug#941154: Removed package(s) from unstable
has caused the Debian Bug report #934935,
regarding Should docbook2odf be removed?
to be marked as done.

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

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


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

Should docbook2odf be removed?

It's unmaintained (last maintainer upload in 2007), last upload in 2010
and has been dropped from testing for three years now.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 0.244-1.1+rm

Dear submitter,

as the package docbook2odf 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/941154

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#875176: marked as done ([scantailor] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Thu, 26 Sep 2019 03:50:32 +
with message-id 
and subject line Bug#941151: Removed package(s) from unstable
has caused the Debian Bug report #875176,
regarding [scantailor] 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.)


-- 
875176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875176
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scantailor
Version: 0.9.12.2-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

= 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 ---
Version: 0.9.12.2-3+rm

Dear submitter,

as the package scantailor 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/941151

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#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

[Mark Hindley]

On Thu, Sep 26, 2019 at 12:11:47AM +0200, Thorsten Glaser wrote:
> On Wed, 25 Sep 2019, Mark Hindley wrote:
> 
> > Thanks. Triggers may be an answer to the libsystemd soversion issue.
> 
> Mind that anything that runs between unpacking the new libsystemd0
> and running the trigger will use libsystemd0 instead of libelogind0.

Ah, of course!

Sam,

I don't see a way of implementing a robust dpkg-divert solution.

Sorry.

Mark

Bug#886860: marked as done (enchant: fails to clean after build)

[Debian Bug Tracking System]

Your message dated Wed, 25 Sep 2019 23:49:05 +
with message-id 
and subject line Bug#886860: fixed in enchant 1.6.0-11.2
has caused the Debian Bug report #886860,
regarding enchant: fails to clean after build
to be marked as done.

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

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


-- 
886860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: enchant
Version: 2.1.2-1~exp1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

enchant/experimental does not clean properly after a successful build:
(I didn't check the version from sid, it probably has the same problem)

 fakeroot debian/rules clean
dh_testdir
dh_testroot
dh_autoreconf_clean
rm -f build-stamp
# Add here commands to clean up after the build process.
[ ! -f Makefile ] || /usr/bin/make distclean
make[1]: Entering directory '/build/enchant-2.1.2'
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash 
/build/enchant-2.1.2/build-aux/missing aclocal-1.15 -I m4
/bin/bash: /build/enchant-2.1.2/build-aux/missing: No such file or directory
Makefile:786: recipe for target 'aclocal.m4' failed
make[1]: *** [aclocal.m4] Error 127
make[1]: Leaving directory '/build/enchant-2.1.2'
debian/rules:72: recipe for target 'clean' failed
make: *** [clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2


dh_autoreconf_clean is being called too early, it needs to be called
after all cleanup was done, right before dh_clean.


Andreas


enchant_2.1.2-1~exp1_twice.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: enchant
Source-Version: 1.6.0-11.2

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated enchant 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: Wed, 25 Sep 2019 19:23:26 -0400
Source: enchant
Architecture: source
Version: 1.6.0-11.2
Distribution: unstable
Urgency: medium
Maintainer: Prach Pongpanich 
Changed-By: Boyuan Yang 
Closes: 860888 886860
Changes:
 enchant (1.6.0-11.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control:
 + Update homepage to the new one on GitHub pages.
 + Update Vcs-* fields and use git packaging repo under
   Salsa Debian group.
 + Bump Standards-Version to 4.4.0.
 + Prefer hunspell instead of aspell. (Closes: #860888)
   * debian/rules:
 + Replace manual query of multiple variables
   with inclusion of /usr/share/dpkg/default.mk.
 + Move dh_autoreconf_clean just before dh_clean to fix
   FTBFS when building twice. (Closes: #886860)
   * debian/gbp.conf: Use new format [buildpackage] instead
 of [git-buildpackage].
   * debian/changelog: Remove trailing spaces.
   * debian/libenchant-dev.files: Do not install .la files.
 .
   [ Manuel A. Fernandez Montecelo ]
   * Triggers file removed, dh_makeshlibs already does the job
 - quells lintian error: repeated-trigger-name
 .
   [ Timo Jyrinki ]
   * Update watch file.
Checksums-Sha1:
 cfa4ff62ffd2ef782ca73131a5f2b90cf766c28b 2185 enchant_1.6.0-11.2.dsc
 5b13a009772f06ec7bc12651506c30e093797a2e 13744 enchant_1.6.0-11.2.debian.tar.xz
 e34bd70570d2e03fa5d8e0a83c2d2df3066ae8c7 8710 
enchant_1.6.0-11.2_amd64.buildinfo
Checksums-Sha256:
 1728c70fce922d3d657a7dde77e366dc587273af79cbb3b8205706d7406c9ac3 2185 
enchant_1.6.0-11.2.dsc
 3995d94116ce5473f580bf246dacb0922aae4cfdb3e554e5f95eeb5a1a29633e 13744 
enchant_1.6.0-11.2.debian.tar.xz
 3780e29820e77f894770681fda167a40aa856f6cd56b5de16dedab00df98ec33 8710 
enchant_1.6.0-11.2_amd64.buildinfo
Files:
 e6dc1ddbf26a594cd413f05341ed7fdc 2185 devel optional enchant_1.6.0-11.2.dsc
 51ca3159b71754ff2723cbe5499497cb 13744 devel optional 
enchant_1.6.0-11.2.debian.tar.xz
 ee3c634ba4704d1fe09bdb0048780349 8710 devel optional 
enchant_1.6.0-11.2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl2L93wACgkQwpPntGGC

Processed: Re: Bug#764896: sandboxgamemaker: sandbox_unix fails to start, "cannot find core textures"

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #764896 [sandboxgamemaker] sandboxgamemaker: sandbox_unix fails to start, 
"cannot find core textures"
Severity set to 'grave' from 'normal'

-- 
764896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764896
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

[Thorsten Glaser]

On Wed, 25 Sep 2019, Mark Hindley wrote:

> Thanks. Triggers may be an answer to the libsystemd soversion issue.

Mind that anything that runs between unpacking the new libsystemd0
and running the trigger will use libsystemd0 instead of libelogind0.

> > I don’t like this approach.
> 
> In this usage case, I believe I have avoided this being a problem.

I really don’t like it and I believe contrary still, see above.

> The flow to
> switch to libelogind.so goes
> 
>  1) symlink libelogind.so.0 to a temporary file.
>  2) rename temporary file to libsystemd.so.0 (I believe this is atomic).

It is, if the temporary file is housed under the same directory.

>  3) dpkg-divert libsystemd.so.0.26.0 out of the way so ldconfig can't find it.
>  4) Whenever ldconfig runs the manual symlink libsystemd.so.0 -> 
> libelogind.so.0
> is preserved.

The packages ship the symlinks as well though, so each and any update
of libsystemd0 will wreck them.

Oh… and, habe you considered Multi-Arch?

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

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

[Mark Hindley]

On Wed, Sep 25, 2019 at 10:09:15PM +0200, Thorsten Glaser wrote:
> On Wed, 25 Sep 2019, Mark Hindley wrote:
> 
> > libelogind0 can be coninstalled with libsystemd0. However, it is fragile 
> > because
> > the file that needs to be diverted out of the way is libsystemd.so.0.26.0 
> > (the
> > actual library file, not a symlink) otherwise ldconfig will still find it 
> > and
> > create symlinks. However, AFAICS dpkg-divert doesn't accept wildcards and 
> > so if
> > the minor soversion is bumped and a new version of libsystemd0 is 
> > installed, the
> > new file is installed without a divert and ldconfig redirects the symlink.
> 
> Yes, this is not a good idea.
> 
> You could do with a trigger on /usr/lib/ and a wildcard-expanding
> shell loop in postinst, which is also a tad fragile.

Thanks. Triggers may be an answer to the libsystemd soversion issue.

> dpkg-divert also has a small period in which neither is available.
> I don’t like this approach.

In this usage case, I believe I have avoided this being a problem. The flow to
switch to libelogind.so goes

 1) symlink libelogind.so.0 to a temporary file.
 2) rename temporary file to libsystemd.so.0 (I believe this is atomic).
 3) dpkg-divert libsystemd.so.0.26.0 out of the way so ldconfig can't find it.
 4) Whenever ldconfig runs the manual symlink libsystemd.so.0 -> libelogind.so.0
is preserved.

I believe using a temporary file and then renaming means there is no point at
which there is a valid libsystemd.so.0 symlink. But I could be wrong.

This isn't the same as the 'standard' dpkg-divert when a file is moved out of
the way so another can be installed in it's place

Is this still flawed?

Thanks

Mark

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

[Thorsten Glaser]

On Wed, 25 Sep 2019, Sam Hartman wrote:

> Thorsten> dpkg-divert also has a small period in which neither is
> Thorsten> available.  I don’t like this approach.
> 
> Is that only when adding a diversion or when upgrading a diverted file
> each time?

When adding a diversion. dpkg-divert is smart enough that,
when the prerm does NOT remove the diversion (e.g. if you
have it in postrm instead), when the postinst adds it to
make that to a nop.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

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

[Sam Hartman]

> "Thorsten" == Thorsten Glaser  writes:

Thorsten> On Wed, 25 Sep 2019, Mark Hindley wrote:
>> libelogind0 can be coninstalled with libsystemd0. However, it is
>> fragile because the file that needs to be diverted out of the way
>> is libsystemd.so.0.26.0 (the actual library file, not a symlink)
>> otherwise ldconfig will still find it and create
>> symlinks. However, AFAICS dpkg-divert doesn't accept wildcards
>> and so if the minor soversion is bumped and a new version of
>> libsystemd0 is installed, the new file is installed without a
>> divert and ldconfig redirects the symlink.

Thorsten> dpkg-divert also has a small period in which neither is
Thorsten> available.  I don’t like this approach.

Is that only when adding a diversion or when upgrading a diverted file
each time?

Bug#875176: [scantailor] Future Qt4 removal from Buster

[Andreas Noteng]

The package for scantailor-advanced is almost done. Since I'm only a DM I'd
need a sponsor for the first upload and (hopefully) someone to grant me
upload privileges for later revisions.
I'll wait for the next upstream release before pushing for a upload. I have
currently packaged for a pre-release.

Andreas

ons. 25. sep. 2019 kl. 20:03 skrev Moritz Mühlenhoff :

> On Tue, Sep 24, 2019 at 03:39:47PM -0600, Jason Crain wrote:
> > On Tue, Sep 24, 2019 at 10:54:01PM +0200, Moritz Mühlenhoff wrote:
> > > per Github issue 121 there's no current activity to port scantailor to
> > > Qt5. Are you planning to switch to the scantailor-advanced fork?
> Otherwise
> > > let's remove it, we're now moving forward with removal of Qt4 from
> Debian
> > > (and all non-ported reverse dependencies left)
> >
> > I will not be working on it, but Andreas Noteng has an ITP for
> > scantailor-advanced (https://bugs.debian.org/940329), which I suggested
> > could be a "Replaces" for scantailor.
>
> Ack, filing a removal bug, then. There's still a lot of time to
> package scantailor-advanced before bullseye freezes.
>
> Cheers,
> Moritz
>

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

[Thorsten Glaser]

On Wed, 25 Sep 2019, Mark Hindley wrote:

> libelogind0 can be coninstalled with libsystemd0. However, it is fragile 
> because
> the file that needs to be diverted out of the way is libsystemd.so.0.26.0 (the
> actual library file, not a symlink) otherwise ldconfig will still find it and
> create symlinks. However, AFAICS dpkg-divert doesn't accept wildcards and so 
> if
> the minor soversion is bumped and a new version of libsystemd0 is installed, 
> the
> new file is installed without a divert and ldconfig redirects the symlink.

Yes, this is not a good idea.

You could do with a trigger on /usr/lib/ and a wildcard-expanding
shell loop in postinst, which is also a tad fragile.

dpkg-divert also has a small period in which neither is available.
I don’t like this approach.

If it’s just for not switching by accident, the Important: yes
binary control field, which I mentioned in my other mail, is more
apropos.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Bug#920571: marked as done (Should this package be removed?)

[Debian Bug Tracking System]

Your message dated Wed, 25 Sep 2019 20:56:20 +0200
with message-id 

and subject line Version 7.X is compiled with OpenSSL 1.1
has caused the Debian Bug report #920571,
regarding Should this package be removed?
to be marked as done.

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

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


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

Should zorp be removed? It's incompatible with OpenSSL 1.1 and the bug has
been unacknowledged since 15 months (859840). It's one of the few remaining
packages blocking the removal at this point, so this doesn't get ported
to OpenSSL 1.1, zorp should be removed along with src:openssl1.0.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 7.0.1~alpha2-1

Version 7.X is compiled with OpenSSL 1.1

Unfortunately, it needed a lot of time to get it into the pool because it
had to go through the new queue and some iteration.
--- End Message ---

Bug#859840: marked as done (zorp: Please migrate to openssl1.1 in Buster)

[Debian Bug Tracking System]

Your message dated Wed, 25 Sep 2019 20:55:17 +0200
with message-id 

and subject line version 7 is compiled with openssl 1.1
has caused the Debian Bug report #859840,
regarding zorp: Please migrate to openssl1.1 in 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.)


-- 
859840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zorp
Version: 6.0.10-2
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle. The bug report about
the FTBFS is #828620.

Sebastian
--- End Message ---
--- Begin Message ---
Version: 7.0.1~alpha2-1

Version 7.X is compiled with OpenSSL 1.1

Unfortunately, it needed a lot of time to get it into the pool because it
had to go through the new queue and some iteration.
--- End Message ---

Bug#941155: choqok FTBFS: error: field ‘accountsList’ has incomplete type ‘QMap’

[Helmut Grohne]

Source: choqok
Version: 1.6-2.1
Severity: serious
Tags: ftbfs

choqok fails to build from source in unstable on amd64. The relevant
error from the compiler is:

| In file included from /<>/plugins/betternotify/notify.cpp:24:
| /<>/plugins/betternotify/notify.h:61:32: error: field 
‘accountsList’ has incomplete type ‘QMap’
|61 | QMap accountsList;
|   |^~~~
| In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:1194,
|  from 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:43,
|  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:43,
|  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qqueue.h:43,
|  from /usr/include/x86_64-linux-gnu/qt5/QtCore/QQueue:1,
|  from /<>/plugins/betternotify/notify.h:26,
|  from /<>/plugins/betternotify/notify.cpp:24:
| /usr/include/x86_64-linux-gnu/qt5/QtCore/qtypeinfo.h:221:1: note: declaration 
of ‘class QMap’
|   221 | Q_DECLARE_MOVABLE_CONTAINER(QMap);
|   | ^~~

Helmut

Bug#875176: [scantailor] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Tue, Sep 24, 2019 at 03:39:47PM -0600, Jason Crain wrote:
> On Tue, Sep 24, 2019 at 10:54:01PM +0200, Moritz Mühlenhoff wrote:
> > per Github issue 121 there's no current activity to port scantailor to
> > Qt5. Are you planning to switch to the scantailor-advanced fork? Otherwise
> > let's remove it, we're now moving forward with removal of Qt4 from Debian
> > (and all non-ported reverse dependencies left)
> 
> I will not be working on it, but Andreas Noteng has an ITP for
> scantailor-advanced (https://bugs.debian.org/940329), which I suggested
> could be a "Replaces" for scantailor.

Ack, filing a removal bug, then. There's still a lot of time to
package scantailor-advanced before bullseye freezes.

Cheers,
Moritz

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

[Mark Hindley]

On Mon, Sep 23, 2019 at 04:16:05PM -0400, Sam Hartman wrote:
> Mark> Anyway, I am happy to try to work up a dpkg-divert solution if
> Mark> that is likely to be more acceptable.
> 
> I don't know if it will be.
> I'm trying to be a facilitator here and make sure all sides understand
> each other.
> 
> So, the advantage of the dpkg-divert approach seems to me to be that if
> you never turn it on, it can't hurt you.
> So, for example, if you do more than install a package to trigger it, it
> could be very safe for the systemd user.
> 
> Even if you trigger from the elogind postinst, that's probably OK so
> long as very little hard depends on elogind.
> 
> The disadvantages are:
> 
> 1) Making sure you never get into a situation where you try to boot
> systemd with libelogind0.  Assuming you can dpkg-divert a symlink, you
> can presumably manage the /sbin/init link, but you cannot stop someone
> from init=/bin/systemd with libelogind0 as libsystemd0.  Although
> systemd doesn't actually link to libsystemd0, so perhaps that's not
> quite as bad as I thought, although I'm sure it isn't good..  (You may
> not need to stop this: it's a disadvantage, and sometimes the chosen
> solution has disadvantages).
> 
> 2) There was FUD about dpkg-divert being inappropriate for critical
> system functions.  I don't know whether this is still true or how big of
> a deal it is.  But for example if things are in an inconsistent state on
> upgrade between unpack phase and configure phase, that might be a
> disadvantage.  Basically, I think it's probably fine if the initial
> diversion has some fragility (where if your system crashes at that one
> point, recovery is hard).  I think it's less amazing if every time you
> upgrade systemd, elogind or similar, there is fragility.

I have got a PoC dpkg-divert solution working.  The divert created in
elogind.postinst and removed in elogind.prerm. The libsystemd.so compatibility
symlink is also handled there. It works as far as it goes and it means that
libelogind0 can be coninstalled with libsystemd0. However, it is fragile because
the file that needs to be diverted out of the way is libsystemd.so.0.26.0 (the
actual library file, not a symlink) otherwise ldconfig will still find it and
create symlinks. However, AFAICS dpkg-divert doesn't accept wildcards and so if
the minor soversion is bumped and a new version of libsystemd0 is installed, the
new file is installed without a divert and ldconfig redirects the symlink.

I can't work out a way around this at the moment, but any suggestions are
welcome.

Thanks

Mark

Bug#917905: marked as done (Fails to build for non-current kernel version)

[Debian Bug Tracking System]

Your message dated Wed, 25 Sep 2019 16:22:52 +
with message-id 
and subject line Bug#917905: fixed in xtables-addons 3.5-0.1
has caused the Debian Bug report #917905,
regarding Fails to build for non-current kernel version
to be marked as done.

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

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


-- 
917905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917905
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xtables-addons-source
Version: 3.2-1
Severity: important

When running kernel version 4.18.0-3-amd64 and building for
4.19.0-1-amd64, the build fails:

/usr/bin/make -C /lib/modules/4.19.0-1-amd64/build M=/usr/src/modules/xtables-ad
dons/extensions XA_ABSTOPSRCDIR=/usr/src/modules/xtables-addons XA_TOPSRCDIR=/us
r/src/modules/xtables-addons DEPMOD=/bin/true clean
make[2]: Entering directory '/usr/src/linux-headers-4.19.0-1-amd64'
make[2]: Leaving directory '/usr/src/linux-headers-4.19.0-1-amd64'
dh_prep
dh_clean
for templ in ; do \
cp $templ `echo $templ | sed -e 's/_KVERS_/4.19.0-1-amd64/g'` ; \
  done
for templ in `ls debian/*.modules.in` ; do \
test -e ${templ%.modules.in}.backup || cp ${templ%.modules.in} ${templ%.modu
les.in}.backup 2>/dev/null || true; \
sed -e 's/##KVERS##/4.19.0-1-amd64/g ;s/#KVERS#/4.19.0-1-amd64/g ; s/_KVERS_
/4.19.0-1-amd64/g ; s/##KDREV##/4.19.13-1/g ; s/#KDREV#/4.19.13-1/g ; s/_KDREV_/
4.19.13-1/g  ' < $templ > ${templ%.modules.in}; \
  done
dh binary-arch
...
checking kernel version that we will build against... make[2]: *** 
/lib/modules/4.18.0-3-amd64/build: No such file or directory.  Stop.
0.0.0.0 in /lib/modules/4.18.0-3-amd64/build
WARNING: That kernel version is not officially supported.
...
dh_auto_build -- -C /lib/modules/4.19.0-1-amd64/build M=/usr/src/modules/xtables
-addons/extensions XA_ABSTOPSRCDIR=/usr/src/modules/xtables-addons XA_TOPSRCDIR=
/usr/src/modules/xtables-addons DEPMOD=/bin/true
make[3]: Entering directory '/usr/src/linux-headers-4.19.0-1-amd64'
...
make[3]: Leaving directory '/usr/src/linux-headers-4.19.0-1-amd64'
make[2]: Leaving directory '/usr/src/modules/xtables-addons'
make[2]: Entering directory '/usr/src/modules/xtables-addons'
Making check in extensions
make[3]: Entering directory '/usr/src/modules/xtables-addons/extensions'
make -f ../Makefile.iptrules all;
Xtables-addons 3.2 - Linux make[4]: Entering directory 
'/usr/src/modules/xtables-addons/extensions'
make[4]: *** /lib/modules/4.18.0-3-amd64/build: No such file or directory.  
Stop.
make[4]: Leaving directory '/usr/src/modules/xtables-addons/extensions'
make[3]: *** [Makefile:465: modules] Error 2
...

So building the modules is actually successful, but the following
"make check" step fails and ./configure goes wrong because they are
defaulting to the currently running kernel version.

I think you need to add override_dh_auto_configure and
override_dh_auto_test targets to debian/rules that will pass the
target kernel version to the upstream build system.

Ben.

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

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

Versions of packages xtables-addons-source depends on:
ii  bzip2 1.0.6-9
ii  debhelper 12
pn  iptables-dev  
ii  make  4.2.1-1.2
ii  pkg-config0.29-4+b1

Versions of packages xtables-addons-source recommends:
ii  module-assistant  0.11.10

xtables-addons-source suggests no packages.
--- End Message ---
--- Begin Message ---
Source: xtables-addons
Source-Version: 3.5-0.1

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

Debian distribution maintenance software
pp.
Aron Xu  (supplier of updated xtables-addons 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 

Bug#934350: marked as done (Fails to build against Linux 5.2)

[Debian Bug Tracking System]

Your message dated Wed, 25 Sep 2019 16:22:52 +
with message-id 
and subject line Bug#934350: fixed in xtables-addons 3.5-0.1
has caused the Debian Bug report #934350,
regarding Fails to build against Linux 5.2
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.)


-- 
934350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xtables-addons-dkms
Version: 3.2-1

Installing xtables-addons-dkms on Debian bullseye with linux 5.2.7-1 leads
to:
...
--
Deleting module version: 3.2
completely from the DKMS tree.
--
Done.
Unpacking xtables-addons-dkms (3.2-1+11) over (3.2-1+11) ...
Setting up xtables-addons-dkms (3.2-1+11) ...
Loading new xtables-addons-3.2 DKMS files...
Building for 5.2.0-2-amd64
Building initial module for 5.2.0-2-amd64
Error!  Build of xt_ACCOUNT.ko failed for: 5.2.0-2-amd64 (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/xtables-addons/3.2/build/ for more information.
dpkg: error processing package xtables-addons-dkms (--configure):
 installed xtables-addons-dkms package post-installation script subprocess
returned error exit status 7
Errors were encountered while processing:
 xtables-addons-dkms

more /var/lib/dkms/xtables-addons/3.2/build/make.log:
DKMS make.log for xtables-addons-3.2 for kernel 5.2.0-2-amd64 (x86_64)
Sat 10 Aug 2019 08:56:41 AM CEST
make: Entering directory '/usr/src/linux-headers-5.2.0-2-amd64'
make -C /usr/src/linux-headers-5.2.0-2-amd64 -f
/usr/src/linux-headers-5.2.0-2-common/Makefile modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo >&2; \
echo >&2 "  ERROR: Kernel configuration is invalid."; \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf
are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to
fix it."; \
echo >&2 ; \
/bin/false)
mkdir -p /var/lib/dkms/xtables-addons/3.2/build/extensions/.tmp_versions ;
rm -f /var/lib/dkms/xtables-addons/3.2/build/extensions/.tmp_versions/*
make -f /usr/src/linux-headers-5.2.0-2-common/scripts/Makefile.build
obj=/var/lib/dkms/xtables-addons/3.2/build/extensions
make -f /usr/src/linux-headers-5.2.0-2-common/scripts/Makefile.build
obj=/var/lib/dkms/xtables-addons/3.2/build/extensions/ACCOUNT need-builtin=
make -f /usr/src/linux-headers-5.2.0-2-common/scripts/Makefile.build
obj=/var/lib/dkms/xtables-addons/3.2/build/extensions/pknock need-builtin=
   gcc-8
-Wp,-MD,/var/lib/dkms/xtables-addons/3.2/build/extensions/.xt_CHAOS.o.d
 -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/8/include
-I/usr/src/linux-
headers-5.2.0-2-common/arch/x86/include -I./arch/x86/include/generated
-I/usr/src/linux-headers-5.2.0-2-common/include -I./include
-I/usr/src/linux-headers-5.
2.0-2-common/arch/x86/include/uapi -I./arch/x86/include/generated/uapi
-I/usr/src/linux-headers-5.2.0-2-common/include/uapi
-I./include/generated/uapi -includ
e /usr/src/linux-headers-5.2.0-2-common/include/linux/kconfig.h -include
/usr/src/linux-headers-5.2.0-2-common/include/linux/compiler_types.h
-D__KERNEL__ -Wa
ll -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing
-fno-common -fshort-wchar -fno-PIE -Werror=implicit-function-declaration
-Werror=impl
icit-int -Wno-format-security -std=gnu89 -mno-sse -mno-mmx -mno-sse2
-mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387
-mno-fp-ret-in-387 -m
preferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone
-mcmodel=kernel -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1
-DCONFIG_AS_CFI_SIGNAL_FRAME=1
 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_AVX=1
-DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1
-DCONFIG_AS_SHA256_NI=1 -Wno-s
ign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern
-mindirect-branch-register -fno-jump-tables -fno-delete-null-pointer-checks
-Wno-fr
ame-address -Wno-format-truncation -Wno-format-overflow -O2
--param=allow-store-data-races=0 -Wframe-larger-than=2048
-fstack-protector-strong -Wno-unused-but
-set-variable -Wno-unused-const-variable -fno-var-tracking-assignments -g
-pg -mrecord-mcount -mfentry -DCC_USING_FENTRY
-Wdeclaration-after-statement -Wvla -
Wno-pointer-sign -Wno-stringop-truncation -fno-strict-overflow
-fno-merge-all-constants -fmerge-constants -fno-stack-check
-fconserve-stack -Werror=date-time
-Werror=incompatible-pointer-types -Werror=designated-init
-fmacro-prefix-map=/usr/src/linux-headers-5.2.0-2-common/=
-Wno-packed-not-aligned  -DMODULE  -DKBU

Processed: found 941139 in 1.43.4-2

[Debian Bug Tracking System]

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

> found 941139 1.43.4-2
Bug #941139 [src:e2fsprogs] CVE-2019-5094: malicious fs can cause buffer 
overrun in e2fsck
Marked as found in versions e2fsprogs/1.43.4-2.
> thanks
Stopping processing here.

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

Processed: reassign 941139 to src:e2fsprogs, found 941139 in 1.44.5-1, fixed 941139 in 1.45.4-1, tagging 941139

[Debian Bug Tracking System]

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

> reassign 941139 src:e2fsprogs 1.44.5-1+deb10u1
Bug #941139 [debian] CVE-2019-5094: malicious fs can cause buffer overrun in 
e2fsck
Warning: Unknown package 'debian'
Bug reassigned from package 'debian' to 'src:e2fsprogs'.
No longer marked as found in versions 1.44.5-1+deb10u1.
Ignoring request to alter fixed versions of bug #941139 to the same values 
previously set
Bug #941139 [src:e2fsprogs] CVE-2019-5094: malicious fs can cause buffer 
overrun in e2fsck
Marked as found in versions e2fsprogs/1.44.5-1+deb10u1.
> found 941139 1.44.5-1
Bug #941139 [src:e2fsprogs] CVE-2019-5094: malicious fs can cause buffer 
overrun in e2fsck
Marked as found in versions e2fsprogs/1.44.5-1.
> fixed 941139 1.45.4-1
Bug #941139 [src:e2fsprogs] CVE-2019-5094: malicious fs can cause buffer 
overrun in e2fsck
Marked as fixed in versions e2fsprogs/1.45.4-1.
> tags 941139 + upstream fixed-upstream
Bug #941139 [src:e2fsprogs] CVE-2019-5094: malicious fs can cause buffer 
overrun in e2fsck
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#939702: marked as done (imapfilter: CVE-2016-10937: does not validate hostname)

[Debian Bug Tracking System]

Your message dated Wed, 25 Sep 2019 15:43:30 +
with message-id 
and subject line Bug#939702: fixed in imapfilter 1:2.6.13-1
has caused the Debian Bug report #939702,
regarding imapfilter: CVE-2016-10937: does not validate hostname
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.)


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

Package: imapfilter
Version: 1:2.6.12-1
Severity: grave
Tags: security upstream
Justification: user security hole

Dear maintainer,

imapfilter does not validate the hostname while validating the 
certificate, as explained in the upstream issue:


https://github.com/lefcha/imapfilter/issues/142


-- System Information:
Debian Release: 10.1
 APT prefers stable-updates
 APT policy: (500, 'stable-updates'), (500, 'stable'), (90, 'testing'), (80, 
'stable'), (70, 'testing'), (60, 'unstable'), (50, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages imapfilter depends on:
ii  libc62.28-10
ii  liblua5.2-0  5.2.4-1.1+b2
ii  libpcre3 2:8.39-12
ii  libssl1.11.1.1c-1

imapfilter recommends no packages.

imapfilter suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: imapfilter
Source-Version: 1:2.6.13-1

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated imapfilter package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Sep 2019 16:10:51 +0200
Source: imapfilter
Architecture: source
Version: 1:2.6.13-1
Distribution: unstable
Urgency: medium
Maintainer: Francesco Paolo Lovergine 
Changed-By: Sylvestre Ledru 
Closes: 939702
Changes:
 imapfilter (1:2.6.13-1) unstable; urgency=medium
 .
   * New upstream release
 - Validates the hostname (Closes: #939702)
Checksums-Sha1:
 286821cde8cf2d080be8296bdf5b6a8f2f2f593f 1948 imapfilter_2.6.13-1.dsc
 94fed16e7902d3eb8d58194e964a7b5742f9e11d 59467 imapfilter_2.6.13.orig.tar.gz
 d24defbbbd71ea5943f675d38f8148a6f68f6e63 5384 imapfilter_2.6.13-1.debian.tar.xz
 34ee504c315e4b418387058ea77394463c631f56 6017 
imapfilter_2.6.13-1_amd64.buildinfo
Checksums-Sha256:
 1b0885268245947ca5bc85a32c293cd02f634bfd073259d0393f6808dc08bb8c 1948 
imapfilter_2.6.13-1.dsc
 8ad94b94ddd47bd051ec875a3ba347bf3427f98ca4b63d60f38ea3a704c8afb2 59467 
imapfilter_2.6.13.orig.tar.gz
 1287875fb904d964b452e8a3a9e7a06e09f750b043a2738a3325975e0bcc65d6 5384 
imapfilter_2.6.13-1.debian.tar.xz
 ac6c4184cf643778c89d0b77c7db01aaebc6f3801bc02abda832bc3a83fb8b75 6017 
imapfilter_2.6.13-1_amd64.buildinfo
Files:
 a29bff9ac31efef4bc1b3271723d3d12 1948 mail optional imapfilter_2.6.13-1.dsc
 6398609530556a4e52a0bae0d438a833 59467 mail optional 
imapfilter_2.6.13.orig.tar.gz
 2ab3fcc00aa5b27891f3f0a8f5e6a8ac 5384 mail optional 
imapfilter_2.6.13-1.debian.tar.xz
 197c142788bb2ade2aca9c5f499ffe72 6017 mail optional 
imapfilter_2.6.13-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAl2LfdkACgkQfmUo2nUv
G+Gf0w/7BkKkPx0EfnsBaORm2qGCabznOCWZNQJZkpdhXnLGy1pHjt3OoDw9aEBM
AfYAm9jRL8KQ/BqnkbsV1kPohO84GIXMVdHw/DxxnO6/KMMiutF3hGRk8guarkr1
r3LSxVuzWc+ycfFxfWehNxu/EV4umTtL2Qq+ve4Q4tj4LG+ipXgxxyn6SokmiPoa
WFLB2bwywVaQI3lv5Xv5NqV17YMZC2waVogeUOY2AjwTl0GeDKPUUEN+PajDFNvB
Ew1tQik59AwcG1KwDioR9+0sIxpO7p7Rsr1NHCXCp1UzTC9ikFHVWyLcwD4mMqtf
uUdN41GUBMvVrN7HDszbWCzYmozWX0uOq29JFF2qLzpcl7EfORvyYI9AuPZkhSaO
8fXqka0aR10CqihR92N9Fl9TK69Wqbdrtac8JdmLPgIA8BhCSpx464BV8MuhuEOr
Da+hS8yYkkhtCCKGnGhDLlhkndMHN7SUgNZSPDOUkQJAI5Al/j7q5v/R51K8+SSZ
WLW+5mSQdTlOyKHdoM22IS8bB4qwXd9qAUcGxpOBMhm/pZxGfI22n4BWNmQ3DxUD

Bug#941139: CVE-2019-5094: malicious fs can cause buffer overrun in e2fsck

[Theodore Y. Ts'o]

Package: debian
Version: 1.44.5-1+deb10u1
Severity: grave
Tags: security
Justification: user security hole

E2fsprogs 1.45.4 contains a bugfix for CVE-2019-5094 / TALOS-2019-0887.
We need to backport commit 8dbe7b475ec5: "libsupport: add checks to
prevent buffer overrun bugs in quota code" to the versions of e2fsprogs
found in Debian Buster and Stretch.

The impact of this bug is that if an attacker can tricker the system
into running e2fsck on an untrustworthy file system as root, a
maliciously crafted file system could result in a buffer overflow that
can result in arbitrary userspace memory modification.

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

Kernel: Linux 5.3.0-00068-g7ec6dbcda3db (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

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

[Thorsten Glaser]

On Mon, 23 Sep 2019, Sam Hartman wrote:

> Mark> #935910 is now fixed in apt 1.8.4 in unstable and with that
> Mark> installed I can no longer reproduce #934491. The APT
> Mark> maintainers have said that adding a Breaks for the fixed
> Mark> version of apt is not useful.
> 
> Normally in a situation like this we would wait until the next stable
> release for depending on the change in apt.

The change can be backported to buster-updates, though. AFAIR we even
require (in the install/upgrade/release notes) that people upgrade the
old distro version to the fullest before attempting an upgrade to the
new one.

> So, I think I understand Julian's issues better after trying to write my
> bits from the DPL mail.
> You haven't really tried to address them at all.

AIUI the problem is that the elogind people tried to do X after trying
to get advice, which didn’t fly, then someone told the elogind people
to do Y, and they did it, and now Julien says “don’t do Y”. I understand
this is all tricky, but the elogind people are caught between several
places of mutually mismatching expectations.

> Foo-package depends on the latest libsystemd0.  I'm running unstable or
> testing.  The latest libsystemd0 isn't building on my arch yet.  But
> elogind is simpler and has build fine on my arch.  I install foo-package
> and suddenly end up with libelogind0 instead of libsystemd0

If you add XB-Important: yes to the libsystemd0 binary package stanza
in debian/control in src:systemd, APT will not do that. It will then
furthermore require “Yes, do as I say!” instead of a simple y or Enter
when switching away from libsystemd0.

(That being said, I’d expect the elogind package to not be the first
to have a bump of the versioned Provides.) This is probably a good
idea independent of what else will be done?

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**

Bug#938874: yum-metadata-parser: Python2 removal in sid/bullseye

[Kentaro Hayashi]

On Mon, 23 Sep 2019 09:36:24 -0700 Mike Miller  wrote:
> Much more helpful long term would be to contribute to getting
> createrepo_c (#912338) and dnf (no ITP yet) into Debian so these Python
> 2 packages can be dropped.

It seems that waiting #912338 task is better in long term surely.

Regards,

Processed: Re: Processed: Re: Bug#936270: calibre: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

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

> reassign 941135 python-cherrypy3
Bug #941135 [src:python-cherrypy3] removal of p2 version breaks rdepends
Warning: Unknown package 'src:python-cherrypy3'
Bug reassigned from package 'src:python-cherrypy3' to 'python-cherrypy3'.
Ignoring request to alter found versions of bug #941135 to the same values 
previously set
Ignoring request to alter fixed versions of bug #941135 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#925745: Bug#925745: [Help] libgtextutils: ftbfs with GCC-9

[Olivier Sallou]

On 9/25/19 1:22 PM, Andreas Tille wrote:
> Hi again,
>
> On Wed, Sep 11, 2019 at 02:16:04PM +0200, Andreas Tille wrote:
>>> commenting in text_line_reader.h:
>>>
>>>         // operator const std::string& () const { return
>>> line_string() ; }
>>>
>>> do the job and test pass
>>>
>>>
>>> but I would prefer a c++ friend to acknowledge this It works but I
>>> do not if there are side effects
>> Any news about this?
> Were you able to contact your c++ friend?

have non  :-(

was expecting something from debian mentors which was in cc...

>
> Kind regards
>
>   Andreas.
>
-- 
Olivier Sallou
Univ Rennes, Inria, CNRS, IRISA
Irisa, Campus de Beaulieu
F-35042 RENNES - FRANCE
Tel: 02.99.84.71.95

gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Processed: Re: Bug#936270: calibre: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

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

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

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

Bug#936270: calibre: Python2 removal in sid/bullseye

[Norbert Preining]

severity 936270 normal
thanks

As long as the rdepends is in place the p2 version will not be removed from 
unstable nor testing, and thus the package still builds and works, nothing 
serious here but the fact that cherrypi maintainers didn't consider rdepends.

Adjusting severity.

Thanks

On September 25, 2019 8:31:25 PM GMT+09:00, peter green  
wrote:
>severity 936270 serious
>thanks
>
>calibre depends on python-cherrypy3 which has already been dropped by
>the cherrypy3 source package.


--
PREINING Norbert http://www.preining.info
Accelia Inc. + JAIST + TeX Live + Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Processed: Re: Bug#936270: calibre: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

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

> clone 936270 -1
Bug #936270 [src:calibre] calibre: Python2 removal in sid/bullseye
Bug 936270 cloned as bug 941135
936196 was blocked by: 937965 938718 937967 936790 938006 936678 939260 938575 
939259 936596 934876 936641 938458 937236 936973 936835 938816 936153 937850 
936270 934852
936196 was blocking: 938518
Added blocking bug(s) of 936196: 941135
936371 was blocked by: 938595 938642 938583 940945 781914 937339 938581 936987 
936757 936104 938503 936297 938329 937388 938596 894806 937073 938637 612636 
937044 936812 938749 937321 938667 937956 938799 937224 936594 935358 938592 
892359 936721 938327 938593 938584 937233 938823 938316 936981 936813 938591 
936173 938160 937137 938884 938586 937513 849086 938944 938945 936166 936948 
937870 937125 936270 938588 937338 938947 938114 937325 936555 937688 938643 
938604 936531
936371 was blocking: 937448 938625
Added blocking bug(s) of 936371: 941135
937513 was blocked by: 937481 938679 938481 937338 936130 936633 938389 936270 
937745 938088 938317 938629 938859 938116 938262 938117 937478 937436 938318
937513 was blocking: 936371
Added blocking bug(s) of 937513: 941135
937815 was blocked by: 935358 936270
937815 was not blocking any bugs.
Added blocking bug(s) of 937815: 941135
937907 was blocked by: 936381 937170 936801 936270 936525 936313 936293 938467 
936930 936815 937139 938561 938560
937907 was not blocking any bugs.
Added blocking bug(s) of 937907: 941135
> reassign -1 src:python-cherrypy3
Bug #941135 [src:calibre] calibre: Python2 removal in sid/bullseye
Bug reassigned from package 'src:calibre' to 'src:python-cherrypy3'.
Warning: Unknown package 'src:python-cherrypy3'
Warning: Unknown package 'src:python-cherrypy3'
No longer marked as found in versions calibre/3.46.0+dfsg-1.
Warning: Unknown package 'src:python-cherrypy3'
Warning: Unknown package 'src:python-cherrypy3'
Ignoring request to alter fixed versions of bug #941135 to the same values 
previously set
Warning: Unknown package 'src:python-cherrypy3'
> retitle -1 removal of p2 version breaks rdepends
Bug #941135 [src:python-cherrypy3] calibre: Python2 removal in sid/bullseye
Warning: Unknown package 'src:python-cherrypy3'
Changed Bug title to 'removal of p2 version breaks rdepends' from 'calibre: 
Python2 removal in sid/bullseye'.
Warning: Unknown package 'src:python-cherrypy3'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
936196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936196
936270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936270
936371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936371
937513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937513
937815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937815
937907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937907
941135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941135
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#936270: calibre: Python2 removal in sid/bullseye

[Norbert Preining]

clone 936270 -1 
reassign -1 src:python-cherrypy3
retitle -1 removal of p2 version breaks rdepends
thanks

Dear cherrypi maintainers,

I strongly recommend checking on rdepends before dropping packages, thanks.

Norbert

On September 25, 2019 8:31:25 PM GMT+09:00, peter green  
wrote:
>severity 936270 serious
>thanks
>
>calibre depends on python-cherrypy3 which has already been dropped by
>the cherrypy3 source package.


--
PREINING Norbert http://www.preining.info
Accelia Inc. + JAIST + TeX Live + Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#941076: debsign crashes gnome on wayland session

[Simon McVittie]

On Wed, 25 Sep 2019 at 17:23:30 +0530, Pirate Praveen wrote:
> 
> 
> On Wed, 25 Sep, 2019 at 16:59, Pirate Praveen 
> wrote:
> > Let me try downgrading libgcr-base-3-1 and reproduce the crash.

> Do I need to install some -dbgsym packages?

Yes, please install at least gdb, libgcr-base-3-1-dbgsym and
libglib2.0-0-dbgsym (the versions corresponding to the libraries you
already have installed), then use

coredumpctl gdb 1648

to use gdb to inspect the core dump that was captured by
systemd-coredump. The stack traces printed by systemd-coredump are only
intended as a brief summary of the core dump, and detailed debugging
(including use of detached debug symbols) is outside the scope of
systemd-coredump itself.

For more details see .

> Attaching core dump.

FYI that's a stack trace, not a core dump. A core dump is a large binary
file, and is not usually useful or desirable to send to bugs (it is likely
to contain information that you would prefer to keep confidential).
You can get a more detailed stack trace from the core dump by using
gdb and -dbgsym packages, and that more detailed stack trace is what
maintainers will usually need to be able to act on crash reports.

smcv

Bug#930178: salt-master: install fails if salt-minion was installed first

[Santiago Vila]

severity 930178 serious
thanks

This also happens when installing salt-master and salt-minion at the same time:

 apt-get install salt-master salt-minion
 [...]
 Setting up salt-master (2018.3.4+dfsg1-6) ...
 adduser: Warning: The home directory /var/lib/salt' does not belong to  the 
user you are currently creating.
 Job for salt-master.service failed because the control process exited with 
error code.
 See "systemctl status salt-master.service" and "journalctl -xe" for details.
 invoke-rc.d: initscript salt-master, action "start" failed.


Discovered this today while upgrading a system from stretch to buster.

I consider this to be a serious bug and I also believe we should try
to fix it in a point release of buster as well.

Thanks.

Processed: Re: salt-master: install fails if salt-minion was installed first

[Debian Bug Tracking System]

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

> severity 930178 serious
Bug #930178 [salt-master] salt-master: install fails if salt-minion was 
installed first
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#941115: linux-image-4.19.0-6-686: cat /proc/acpi/ibm/video ,computer dead !thinkpad_acpi bug?

[Ben Hutchings]

Control: severity -1 normal
Control: tag -1 moreinfo

On Wed, 2019-09-25 at 15:10 +0800, xiao shengwen wrote:
> Package: src:linux
> Version: 4.19.67-2+deb10u1
> Severity: critical
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
>My notebook type is:IBM ThinkPad R50e, model 1834LC4.
> 
> When I use the command: cat /proc/acpi/ibm/video ,my computer will dead,
> no any error info display on screen,network is can't ping,keyboard no 
> response.
> no any error log in /var/log/* .
> 
> I think my notebook is dead.
[...]

But you have to be root to do that, right?

Ben.

-- 
Ben Hutchings
Reality is just a crutch for people who can't handle science fiction.



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

Bug#941076: debsign crashes gnome on wayland session

[Pirate Praveen]

On Wed, 25 Sep, 2019 at 16:59, Pirate Praveen 
 wrote:

Let me try downgrading libgcr-base-3-1 and reproduce the crash.


Attaching core dump. Do I need to install some -dbgsym packages?

Sep 25 17:10:18 andhaka systemd-coredump[3731]: Process 1648 (gnome-shell) of user 1001 dumped core.

Stack trace of thread 1648:
#0  0x7f34debe1468 n/a (libgcr-base-3.so.1)
#1  0x7f34de1858ee ffi_call_unix64 (libffi.so.6)
#2  0x7f34de1852bf ffi_call (libffi.so.6)
#3  0x7f34e064c6dc g_cclosure_marshal_generic (libgobject-2.0.so.0)
#4  0x7f34e064beb2 g_closure_invoke (libgobject-2.0.so.0)
#5  0x7f34e065f4d4 n/a (libgobject-2.0.so.0)
#6  0x7f34e066818f g_signal_emit_valist (libgobject-2.0.so.0)
#7  0x7f34e066881f g_signal_emit (libgobject-2.0.so.0)
#8  0x7f34debe13c7 n/a (libgcr-base-3.so.1)
#9  0x7f34debe28f3 n/a (libgcr-base-3.so.1)
#10 0x7f34e0797600 n/a (libgio-2.0.so.0)
#11 0x7f34e0562d8e g_main_context_dispatch (libglib-2.0.so.0)
#12 0x7f34e0563140 n/a (libglib-2.0.so.0)
#13 0x7f34e0563413 g_main_loop_run (libglib-2.0.so.0)
#14 0x7f34df973c6c meta_run (libmutter-5.so.0)
#15 0x560194238865 n/a (gnome-shell)
#16 0x7f34df722bbb __libc_start_main (libc.so.6)
#17 0x560194238a4a n/a (gnome-shell)

Stack trace of thread 1660:
#0  0x7f34df7ebd2f __poll (libc.so.6)
#1  0x7f34e05630ae n/a (libglib-2.0.so.0)
#2  0x7f34e0563413 g_main_loop_run (libglib-2.0.so.0)
#3  0x7f34e07a7676 n/a (libgio-2.0.so.0)
#4  0x7f34e058bd1d n/a (libglib-2.0.so.0)
#5  0x7f34de191fb7 start_thread (libpthread.so.0)
#6  0x7f34df7f62ef __clone (libc.so.6)

Stack trace of thread 1658:
#0  0x7f34df7ebd2f __poll (libc.so.6)
#1  0x7f34e05630ae n/a (libglib-2.0.so.0)
#2  0x7f34e05631cf g_main_context_iteration (libglib-2.0.so.0)
#3  0x7f34e0563221 n/a (libglib-2.0.so.0)
#4  0x7f34e058bd1d n/a (libglib-2.0.so.0)
#5  0x7f34de191fb7 start_thread (libpthread.so.0)
#6  0x7f34df7f62ef __clone (libc.so.6)

Stack trace of thread 1687:
#0  0x7f34de197db5 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x7f34dd7554ff _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-60.so.0)
#2  0x7f34dd7556e5 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-60.so.0)
#3  0x7f34dd4d2ef4 n/a (libmozjs-60.so.0)
#4  0x7f34dd4cda42 n/a (libmozjs-60.so.0)
#5  0x7f34de191fb7 start_thread (libpthread.so.0)
#6  0x7f34df7f62ef __clone (libc.so.6)

Stack trace of thread 1662:

Processed: Re: Bug#941115: linux-image-4.19.0-6-686: cat /proc/acpi/ibm/video ,computer dead !thinkpad_acpi bug?

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #941115 [src:linux] linux-image-4.19.0-6-686: cat /proc/acpi/ibm/video 
,computer dead !thinkpad_acpi bug?
Severity set to 'normal' from 'critical'
> tag -1 moreinfo
Bug #941115 [src:linux] linux-image-4.19.0-6-686: cat /proc/acpi/ibm/video 
,computer dead !thinkpad_acpi bug?
Added tag(s) moreinfo.

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

Processed: re: ceph: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

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

> Severity 936282 serious
Bug #936282 [src:ceph] ceph: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> Thanks
Stopping processing here.

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

Bug#941076: debsign crashes gnome on wayland session

[Pirate Praveen]

On Wed, 25 Sep, 2019 at 08:54, Simon McVittie  wrote:

gnome-shell in experimental was compiled against gcr from unstable,
so a higher version in dpkg-shlibdeps wouldn't have helped here; and I
don't see any recent source changes that should have prompted a higher
build-dependency.

Not much has changed in gcr between 3.28 and 3.33 at all, although 
there

are some annotation fixes that might affect gnome-shell. Did you also
upgrade gir1.2-gcr-3, or just libgcr-base-3-1?



Just libgcr-base-3-1.

2019-09-25 11:51:40 status installed libglib2.0-0:amd64 2.62.0-1
2019-09-25 12:13:51 startup archives unpack
2019-09-25 12:13:52 upgrade libgcr-base-3-1:amd64 3.28.0-1 3.33.4-2
2019-09-25 12:13:52 status triggers-pending libc-bin:amd64 2.29-2
2019-09-25 12:13:52 status half-configured libgcr-base-3-1:amd64 
3.28.0-1

2019-09-25 12:13:52 status unpacked libgcr-base-3-1:amd64 3.28.0-1
2019-09-25 12:13:52 status half-installed libgcr-base-3-1:amd64 3.28.0-1
2019-09-25 12:13:53 status unpacked libgcr-base-3-1:amd64 3.33.4-2
2019-09-25 12:13:53 startup packages configure
2019-09-25 12:13:53 configure libgcr-base-3-1:amd64 3.33.4-2 
2019-09-25 12:13:53 status unpacked libgcr-base-3-1:amd64 3.33.4-2
2019-09-25 12:13:53 status half-configured libgcr-base-3-1:amd64 
3.33.4-2

2019-09-25 12:13:53 status installed libgcr-base-3-1:amd64 3.33.4-2
2019-09-25 12:13:53 trigproc libc-bin:amd64 2.29-2 
2019-09-25 12:13:53 status half-configured libc-bin:amd64 2.29-2
2019-09-25 12:13:53 status installed libc-bin:amd64 2.29-2



Which gcr-related packages did you upgrade in the transaction that
triggered these crashes? For example, did you upgrade gcr or 
libgcr-ui-3-1

from experimental?



See attached dpkg.log for the transaction that triggered the crash.


Which version of gnome-keyring did you have when this crash existed?



3.31.91-2 and 3.31.91-1 (both crashed, update did not fix the crash).

Presumably you already had gnome-settings-daemon 3.34.x from 
experimental

in order to satisfy gnome-shell's dependencies?



yes, 3.34.0-2

Are you able to get a backtrace from this crash? (If you install 
packages

from experimental, I would suggest installing systemd-coredump, or
corekeeper if you don't use systemd, so that you can get post-mortem
backtraces.)



Let me try downgrading libgcr-base-3-1 and reproduce the crash.


Thanks,
smcv


2019-09-22 19:12:17 startup archives unpack
2019-09-22 19:12:17 upgrade libc-l10n:all 2.28-4 2.29-2
2019-09-22 19:12:17 status half-configured libc-l10n:all 2.28-4
2019-09-22 19:12:17 status unpacked libc-l10n:all 2.28-4
2019-09-22 19:12:17 status half-installed libc-l10n:all 2.28-4
2019-09-22 19:12:18 status unpacked libc-l10n:all 2.29-2
2019-09-22 19:12:18 upgrade locales:all 2.28-8 2.29-2
2019-09-22 19:12:18 status half-configured locales:all 2.28-8
2019-09-22 19:12:18 status unpacked locales:all 2.28-8
2019-09-22 19:12:18 status half-installed locales:all 2.28-8
2019-09-22 19:12:18 status triggers-pending man-db:amd64 2.8.5-2
2019-09-22 19:12:18 status unpacked locales:all 2.29-2
2019-09-22 19:12:18 upgrade libc6:amd64 2.28-4 2.29-2
2019-09-22 19:12:18 status triggers-pending libc-bin:amd64 2.28-4
2019-09-22 19:12:18 status half-configured libc6:amd64 2.28-4
2019-09-22 19:12:18 status unpacked libc6:amd64 2.28-4
2019-09-22 19:12:18 status half-installed libc6:amd64 2.28-4
2019-09-22 19:12:19 status unpacked libc6:amd64 2.29-2
2019-09-22 19:12:19 startup packages configure
2019-09-22 19:12:19 configure libc6:amd64 2.29-2 
2019-09-22 19:12:19 status unpacked libc6:amd64 2.29-2
2019-09-22 19:12:19 status half-configured libc6:amd64 2.29-2
2019-09-22 19:12:22 status installed libc6:amd64 2.29-2
2019-09-22 19:12:22 startup archives unpack
2019-09-22 19:12:22 upgrade libc-bin:amd64 2.28-4 2.29-2
2019-09-22 19:12:22 status half-configured libc-bin:amd64 2.28-4
2019-09-22 19:12:22 status unpacked libc-bin:amd64 2.28-4
2019-09-22 19:12:22 status half-installed libc-bin:amd64 2.28-4
2019-09-22 19:12:22 status unpacked libc-bin:amd64 2.29-2
2019-09-22 19:12:22 startup packages configure
2019-09-22 19:12:22 configure libc-bin:amd64 2.29-2 
2019-09-22 19:12:22 status unpacked libc-bin:amd64 2.29-2
2019-09-22 19:12:22 status half-configured libc-bin:amd64 2.29-2
2019-09-22 19:12:24 status installed libc-bin:amd64 2.29-2
2019-09-22 19:12:24 startup archives unpack
2019-09-22 19:12:24 upgrade libc-dev-bin:amd64 2.28-4 2.29-2
2019-09-22 19:12:24 status half-configured libc-dev-bin:amd64 2.28-4
2019-09-22 19:12:24 status unpacked libc-dev-bin:amd64 2.28-4
2019-09-22 19:12:24 status half-installed libc-dev-bin:amd64 2.28-4
2019-09-22 19:12:24 status unpacked libc-dev-bin:amd64 2.29-2
2019-09-22 19:12:24 upgrade libc6-dev:amd64 2.28-4 2.29-2
2019-09-22 19:12:24 status half-configured libc6-dev:amd64 2.28-4
2019-09-22 19:12:24 status unpacked libc6-dev:amd64 2.28-4
2019-09-22 19:12:24 status half-installed libc6-dev:amd64 2.28-4
2019-09-22 19:12:25 status unpacked libc6-dev:amd64 2.29-2
2019-09-22 

Processed: calibre: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

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

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

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

Bug#925745: Bug#925745: [Help] libgtextutils: ftbfs with GCC-9

[Andreas Tille]

Hi again,

On Wed, Sep 11, 2019 at 02:16:04PM +0200, Andreas Tille wrote:
> > commenting in text_line_reader.h:
> > 
> >         // operator const std::string& () const { return
> > line_string() ; }
> > 
> > do the job and test pass
> > 
> > 
> > but I would prefer a c++ friend to acknowledge this It works but I
> > do not if there are side effects
> 
> Any news about this?

Were you able to contact your c++ friend?

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#940105: linux: serious corruption issue with btrfs

[Salvatore Bonaccorso]

Hi,

On Wed, Sep 25, 2019 at 02:17:23AM +0200, Christoph Anton Mitterer wrote:
> Hey.
> 
> Is there anything one can help to speed this up?
> 
> A patch is available for two weeks now, while Debian users of testing
> and unstable are left with the danger of catastrophic btrfs corruption
> without even any warning to them (so that they could at least downgrade
> to <5.2).

Status is as follows: We have the fix pending in the packaging git
repository, where the next steps are eiher avoid the current ABI
changes we have with the bump to 5.2.14 as well or do an ABI bump +
importing additionally changes up to 5.2.17. 

Currently planned for the latter.

Salvatore

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

[Debian Bug Tracking System]

Your message dated Wed, 25 Sep 2019 08:47:51 +
with message-id 
and subject line Bug#938089: fixed in python-pyramid 1.10.2+dfsg-3
has caused the Debian Bug report #938089,
regarding python-pyramid: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-pyramid

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

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

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

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

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

Debian distribution maintenance software
pp.
Andrey Rahmatullin  (supplier of updated python-pyramid 
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: Wed, 25 Sep 2019 11:57:12 +0500
Source: python-pyramid
Architecture: source
Version: 1.10.2+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andrey Rahmatullin 
Closes: 938089
Changes:
 python-pyramid (1.10.2+dfsg-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat.
   * Bump Standards-Version to 4.4.0.
 .
   [ Andrey Rahmatullin ]
   * Drop Python 2 support (Closes: #938089).
Checksums-Sha1:
 52e4e13286017ce76db78a89ce135eb379b5 2426 python-pyramid_1.10.2+dfsg-3.dsc
 c8329440285cfece15e631e7b3150b2eeaf00286 7460 
python-pyramid_1.10.2+dfsg-3.debian.tar.xz
 1e2a0889f4cf8dd72f2d208e06a30e8b50b5b6b7 6846 
python-pyramid_1.10.2+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 9cb84286a4be20876d722c2cfb7a30d159440fdf912b349aeddf5d7f37d36159 2426 
python-pyramid_1.10.2+dfsg-3.dsc
 

Bug#941076: debsign crashes gnome on wayland session

[Simon McVittie]

On Wed, 25 Sep 2019 at 12:33:08 +0530, Pirate Praveen wrote:
> On Wed, 25 Sep, 2019 at 12:13, Pirate Praveen 
> wrote:
> > I think I found the relevant part from the log. Attaching log from the
> > point of crash.
> > 
> > Sep 25 11:44:47 andhaka kernel: gnome-shell[1634]: segfault at 8 ip
> > 7f85dbfdf468 sp 7ffda39321c0 error 4 in
> > libgcr-base-3.so.1.0.0[7f85dbfa2000+8c000]
> > 
> 
> After upgrading libgcr-base-3-1, it does not crash anymore.
> 2019-09-25 12:13:52 upgrade libgcr-base-3-1:amd64 3.28.0-1 3.33.4-2
> 
> I tried rebooting and running debsign again. So probably gcr should bump its
> dependency version.

gnome-shell in experimental was compiled against gcr from unstable,
so a higher version in dpkg-shlibdeps wouldn't have helped here; and I
don't see any recent source changes that should have prompted a higher
build-dependency.

Not much has changed in gcr between 3.28 and 3.33 at all, although there
are some annotation fixes that might affect gnome-shell. Did you also
upgrade gir1.2-gcr-3, or just libgcr-base-3-1?

Which gcr-related packages did you upgrade in the transaction that
triggered these crashes? For example, did you upgrade gcr or libgcr-ui-3-1
from experimental?

Which version of gnome-keyring did you have when this crash existed?

Presumably you already had gnome-settings-daemon 3.34.x from experimental
in order to satisfy gnome-shell's dependencies?

Are you able to get a backtrace from this crash? (If you install packages
from experimental, I would suggest installing systemd-coredump, or
corekeeper if you don't use systemd, so that you can get post-mortem
backtraces.)

Thanks,
smcv

Processed: Re: Bug#940679: pandas: random test crashes

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - patch
Bug #940679 [src:pandas] pandas: random test crashes
Removed tag(s) patch.

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

Bug#940679: pandas: random test crashes

[Rebecca N. Palmer]

Control: tags -1 - patch

That's not the problem: cdef classes _can_ have non-cdef class (not 
instance) attributes. https://github.com/cython/cython/issues/3154


On further inspection, the actual problem is that we have a Timedelta 
(full Python class, has a dict) allocated in a memory space sized for 
its parent _Timedelta (cdef class, no dict).


I don't know how this happened: the _Timedelta C struct is only created 
via its tp_new, which is passed the subclass (the standard Python 
mechanism for allowing subclasses to be larger in memory than their 
parent class - 
https://docs.python.org/3/c-api/typeobj.html#c.PyTypeObject.tp_new).

Bug#941115: linux-image-4.19.0-6-686: cat /proc/acpi/ibm/video ,computer dead !thinkpad_acpi bug?

[xiao shengwen]

Package: src:linux
Version: 4.19.67-2+deb10u1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   My notebook type is:IBM ThinkPad R50e, model 1834LC4.

When I use the command: cat /proc/acpi/ibm/video ,my computer will dead,
no any error info display on screen,network is can't ping,keyboard no response.
no any error log in /var/log/* .

I think my notebook is dead.

-- Package-specific info:
** Version:
Linux version 4.19.0-6-686 (debian-ker...@lists.debian.org) (gcc version 8.3.0 
(Debian 8.3.0-6)) #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-686 
root=UUID=7537896e-1170-47df-8b4f-231cdbb646e3 ro quiet

** Tainted: OE (12288)
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.

** Kernel log:
[0.00] Linux version 4.19.0-6-686 (debian-ker...@lists.debian.org) (gcc 
version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20)
[0.00] Disabled fast string operations
[0.00] x86/fpu: x87 FPU will use FXSAVE
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009efff] usable
[0.00] BIOS-e820: [mem 0x0009f000-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000dc000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x2f6d] usable
[0.00] BIOS-e820: [mem 0x2f6e-0x2f6f6fff] ACPI data
[0.00] BIOS-e820: [mem 0x2f6f7000-0x2f6f8fff] ACPI NVS
[0.00] BIOS-e820: [mem 0x2f70-0x2fff] reserved
[0.00] BIOS-e820: [mem 0xff80-0x] reserved
[0.00] Notice: NX (Execute Disable) protection missing in CPU!
[0.00] SMBIOS 2.3 present.
[0.00] DMI: IBM 1834LC4/1834LC4, BIOS 1WET88WW (2.08 ) 03/03/2006
[0.00] tsc: Fast TSC calibration using PIT
[0.00] tsc: Detected 1495.203 MHz processor
[0.015385] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.015392] e820: remove [mem 0x000a-0x000f] usable
[0.015402] last_pfn = 0x2f6e0 max_arch_pfn = 0x10
[0.015414] MTRR default type: uncachable
[0.015416] MTRR fixed ranges enabled:
[0.015419]   0-9 write-back
[0.015421]   A-B uncachable
[0.015423]   C-C write-protect
[0.015425]   D-DBFFF uncachable
[0.015427]   DC000-D write-back
[0.015429]   E-F write-protect
[0.015431] MTRR variable ranges enabled:
[0.015433]   0 base 0 mask FE000 write-back
[0.015436]   1 base 02000 mask FF000 write-back
[0.015438]   2 base 02FF0 mask 0 uncachable
[0.015439]   3 disabled
[0.015441]   4 disabled
[0.015442]   5 disabled
[0.015444]   6 disabled
[0.015445]   7 disabled
[0.016386] x86/PAT: PAT not supported by CPU.
[0.016567] x86/PAT: Configuration [0-7]: WB  WT  UC- UC  WB  WT  UC- UC  
[0.030233] initial memory mapped: [mem 0x-0x1eff]
[0.030303] BRK [0x1eaf3000, 0x1eaf3fff] PGTABLE
[0.030336] RAMDISK: [mem 0x2ca03000-0x2e99dfff]
[0.030346] ACPI: Early table checksum verification disabled
[0.030501] ACPI: RSDP 0x000F6E40 24 (v02 IBM   )
[0.030508] ACPI: XSDT 0x2F6EF33D 4C (v01 IBMTP-1W
2080  LTP )
[0.030519] ACPI: FACP 0x2F6EF400 F4 (v03 IBMTP-1W
2080 IBM  0001)
[0.030529] ACPI BIOS Warning (bug): 32/64X length mismatch in 
FADT/Gpe0Block: 64/32 (20180810/tbfadt-569)
[0.030535] ACPI BIOS Warning (bug): Optional FADT field Gpe1Block has valid 
Address but zero Length: 0x102C/0x0 (20180810/tbfadt-624)
[0.030544] ACPI: DSDT 0x2F6EF5E7 007865 (v01 IBMTP-1W
2080 MSFT 010E)
[0.030551] ACPI: FACS 0x2F6F8000 40
[0.030557] ACPI: FACS 0x2F6F8000 40
[0.030563] ACPI: SSDT 0x2F6EF5B4 33 (v01 IBMTP-1W
2080 MSFT 010E)
[0.030570] ACPI: ECDT 0x2F6F6E4C 52 (v01 IBMTP-1W
2080 IBM  0001)
[0.030577] ACPI: TCPA 0x2F6F6E9E 32 (v01 IBMTP-1W
2080 PTL  0001)
[0.030584] ACPI: BOOT 0x2F6F6FD8 28 (v01 IBMTP-1W
2080  LTP 0001)
[0.030605] 0MB HIGHMEM available.
[0.030608] 758MB LOWMEM available.
[0.030609]   mapped low ram: 0 - 2f6e
[0.030611]   low ram: 0 - 2f6e
[0.030621] BRK [0x1eaf4000, 0x1eaf4fff] PGTABLE
[0.030626] Zone ranges:
[0.030628]   DMA  [mem 0x1000-0x00ff]
[0.030631]   Normal   [mem 0x0100-0x2f6d]
[0.030634]   HighMem  empty
[0.030636] Movable zone start for each node
[0.030637] Early memory node ranges
[0.030640]   node   0: [mem 0x1000-0x0009efff]
[0.030642]   node   0: [mem 

Processed: found 941076 in libgcr-base-3-1/3.28.0-1

[Debian Bug Tracking System]

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

> found 941076 libgcr-base-3-1/3.28.0-1
Bug #941076 [gnome-session,pinentry-gnome3] [GNOME 3.34] debsign crashes gnome 
on wayland session
The source libgcr-base-3-1 and version 3.28.0-1 do not appear to match any 
binary packages
Marked as found in versions libgcr-base-3-1/3.28.0-1.
> thanks
Stopping processing here.

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

Processed: fixed 941076 in libgcr-base-3-1/3.33.4-2

[Debian Bug Tracking System]

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

> fixed 941076 libgcr-base-3-1/3.33.4-2
Bug #941076 [gnome-session,pinentry-gnome3] [GNOME 3.34] debsign crashes gnome 
on wayland session
The source libgcr-base-3-1 and version 3.33.4-2 do not appear to match any 
binary packages
Marked as fixed in versions libgcr-base-3-1/3.33.4-2.
> thanks
Stopping processing here.

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

Bug#875150: Should we file a removal bug?

[Moritz Muehlenhoff]

On Wed, Sep 25, 2019 at 07:57:47AM +0200, Andreas Tille wrote:
> Hi,
> 
> On Tue, Sep 24, 2019 at 10:48:24PM +0200, Moritz Mühlenhoff wrote:
> > On Tue, Sep 17, 2019 at 12:05:17PM -0300, Lisandro Damián Nicanor Pérez 
> > Meyer wrote:
> > > Hi! It seems there is no activity on this bug, should we file a removal 
> > > bug?
> > 
> > Adding the last two uploaders to CC.
> 
> ... as well as Uploaders in d/control in CC.
>  
> > Is anyone of you planning to upload a Qt5 compatible release candidate of 
> > qtiplot?
> > Otherwise we'll file a removal bug as we're closing in on the Qt5 
> > removalnow.
> > 
> > (Upload also happen to experimental to avoid a later roundtrip through NEW 
> > when a final
> > 1.0 comes out)
> 
> While the website[1] is announcing
> 
> 2019/09/18 - QtiPlot 1.0.0-rc10 release available. New features and 
> improvements: 
> 
> (without mentioning a Qt 5 port explicitly :-() the download area[2]
> does not contain any source download of this.  It seems upstream changed
> to a closed source model since you can only download binaries with
> restricted functionality or you need to buy a license.

Ah yes, the Sourceforge page states:

Posted 2019-02-12
QtiPlot is no longer open source, therefore your comment is out of scope. We 
have tried to
keep it open source as long as possible. Unfortunately this was made impossible 
by people
insisting to distribute prebuilt binaries for Windows, without taking into 
account the fact
that this was our only source of revenu allowing to finance our work.

So seems best to remove it, then.

Cheers,
Moritz

Bug#941076: debsign crashes gnome on wayland session

[Pirate Praveen]

On Wed, 25 Sep, 2019 at 12:13, Pirate Praveen 
 wrote:
I think I found the relevant part from the log. Attaching log from 
the point of crash.


Sep 25 11:44:47 andhaka kernel: gnome-shell[1634]: segfault at 8 ip 
7f85dbfdf468 sp 7ffda39321c0 error 4 in 
libgcr-base-3.so.1.0.0[7f85dbfa2000+8c000]




After upgrading libgcr-base-3-1, it does not crash anymore.
2019-09-25 12:13:52 upgrade libgcr-base-3-1:amd64 3.28.0-1 3.33.4-2

I tried rebooting and running debsign again. So probably gcr should 
bump its dependency version.

Bug#941076: debsign crashes gnome on wayland session

[Pirate Praveen]

I think I found the relevant part from the log. Attaching log from the 
point of crash.


Sep 25 11:44:47 andhaka kernel: gnome-shell[1634]: segfault at 8 ip 
7f85dbfdf468 sp 7ffda39321c0 error 4 in 
libgcr-base-3.so.1.0.0[7f85dbfa2000+8c000]


11:44:47 andhaka systemd[1532]: Started GnuPG cryptographic agent and passphrase cache.
Sep 25 11:44:47 andhaka gpg-agent[2869]: gpg-agent (GnuPG) 2.2.17 starting in supervised mode.
Sep 25 11:44:47 andhaka gpg-agent[2869]: using fd 3 for std socket (/run/user/1001/gnupg/S.gpg-agent)
Sep 25 11:44:47 andhaka gpg-agent[2869]: using fd 4 for browser socket (/run/user/1001/gnupg/S.gpg-agent.browser)
Sep 25 11:44:47 andhaka gpg-agent[2869]: using fd 5 for ssh socket (/run/user/1001/gnupg/S.gpg-agent.ssh)
Sep 25 11:44:47 andhaka gpg-agent[2869]: using fd 6 for extra socket (/run/user/1001/gnupg/S.gpg-agent.extra)
Sep 25 11:44:47 andhaka gpg-agent[2869]: listening on: std=3 extra=6 browser=4 ssh=5
Sep 25 11:44:47 andhaka kernel: gnome-shell[1634]: segfault at 8 ip 7f85dbfdf468 sp 7ffda39321c0 error 4 in libgcr-base-3.so.1.0.0[7f85dbfa2000+8c000]
Sep 25 11:44:47 andhaka kernel: Code: 00 00 48 83 c4 28 5b 5d 41 5c 41 5d c3 0f 1f 44 00 00 48 8b 44 24 08 48 8d 15 74 13 03 00 48 8d 3d 5f b2 02 00 be 80 00 00 00 <4c> 8b 40 08 48 8b 08 31 c0 e8 6a 6d fe ff eb b4 0f 1f 84 00 00 00
Sep 25 11:44:47 andhaka gsd-keyboard[1701]: Error reading events from display: Broken pipe
Sep 25 11:44:47 andhaka evolution-alarm[1752]: Error reading events from display: Broken pipe
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: DEBUG(+): GsmXsmpServer: ice_io_error_handler (0x55beb2fda320)
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmXsmpServer: ice_io_error_handler (0x55beb2fda320)
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmXSMPClient: IceProcessMessagesIOError on '0x55beb2feb880 [gnome-shell 10560d616c8277f60d15693920738597020016180069]'
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmManager: disconnect client
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client14
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmManager: unable to find application for client - not restarting
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmStore: Unreffing object: 0x55beb2feb880
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmManager: Client removed: /org/gnome/SessionManager/Client14
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmClient: disposing /org/gnome/SessionManager/Client14
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmXSMPClient: xsmp_finalize (0x55beb2feb880 [gnome-shell 10560d616c8277f60d15693920738597020016180069])
Sep 25 11:44:47 andhaka gsd-wacom[1690]: Error reading events from display: Broken pipe
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: DEBUG(+): GsmXSMPClient: IceProcessMessagesIOError on '0x55beb2feb880 [gnome-shell 10560d616c8277f60d15693920738597020016180069]'
Sep 25 11:44:47 andhaka gsd-color[1671]: Error reading events from display: Broken pipe
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: DEBUG(+): GsmManager: disconnect client
Sep 25 11:44:47 andhaka gnome-terminal-[2496]: Error reading events from display: Broken pipe
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client14
Sep 25 11:44:47 andhaka systemd[1532]: gsd-wacom.service: Main process exited, code=exited, status=1/FAILURE
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: DEBUG(+): GsmManager: unable to find application for client - not restarting
Sep 25 11:44:47 andhaka systemd[1532]: gsd-wacom.service: Failed with result 'exit-code'.
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmManager: disconnect client
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client19
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmManager: disconnect for app 'wacom'
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmManager: unable to find application for client - not restarting
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmStore: Unreffing object: 0x7fcc78003420
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: DEBUG(+): GsmManager: Client removed: /org/gnome/SessionManager/Client19
Sep 25 11:44:47 andhaka gnome-session-binary[1618]: gnome-session-binary[1618]: 

Processed: found 941076 in gnome-session/3.34.0-1

[Debian Bug Tracking System]

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

> found 941076 gnome-session/3.34.0-1
Bug #941076 [gnome-session,pinentry-gnome3] [GNOME 3.34] debsign crashes gnome 
on wayland session
Marked as found in versions gnome-session/3.34.0-1.
> thanks
Stopping processing here.

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

Processed: found 941076 in pinentry-gnome3/1.1.0-3

[Debian Bug Tracking System]

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

> found 941076 pinentry-gnome3/1.1.0-3
Bug #941076 [gnome-session,pinentry-gnome3] [GNOME 3.34] debsign crashes gnome 
on wayland session
The source pinentry-gnome3 and version 1.1.0-3 do not appear to match any 
binary packages
Marked as found in versions pinentry-gnome3/1.1.0-3.
> thanks
Stopping processing here.

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

Bug#941076: debsign crashes gnome on wayland session

[Pirate Praveen]

From sudo journalctl -ab >journal.log Is there another specific thing 
I should check in the log?


Sep 25 11:18:09 andhaka gsd-keyboard[18299]: Unable to init server: 
Could not connect: Connection refused

Sep 25 11:18:09 andhaka gsd-keyboard[18299]: Cannot open display:
Sep 25 11:18:09 andhaka systemd[17334]: gsd-keyboard.service: Main 
process exited, code=exited, status=1/FAILURE
Sep 25 11:18:09 andhaka systemd[17334]: gsd-keyboard.service: Failed 
with result 'exit-code'.
Sep 25 11:18:09 andhaka systemd[17334]: Failed to start GNOME Keyboard 
handling.
Sep 25 11:18:09 andhaka systemd[17334]: Dependency failed for GNOME 
Keyboard handling.
Sep 25 11:18:09 andhaka systemd[17334]: gsd-keyboard.target: Job 
gsd-keyboard.target/start failed with result 'dependency'.
Sep 25 11:18:09 andhaka gnome-session-failed[18294]: Unable to init 
server: Could not connect: Connection refused

Sep 25 11:18:09 andhaka unknown[18294]: Cannot open display:
Sep 25 11:18:09 andhaka systemd[17334]: gnome-session-failed.service: 
Main process exited, code=exited, status=1/FAILURE
Sep 25 11:18:09 andhaka systemd[17334]: Stopped target GNOME Session 
Failed.

Bug#782952: marked as done (Please replace with a python3 module or remove the package)

[Debian Bug Tracking System]

Your message dated Wed, 25 Sep 2019 06:00:10 +
with message-id 
and subject line Bug#782952: fixed in python-pyramid-zcml 1.0.0-1.1
has caused the Debian Bug report #782952,
regarding Please replace with a python3 module or remove the 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.)


-- 
782952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782952
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pyramid-zcml
Severity: wishlist
User: py3porters-de...@lists.alioth.debian.org
Usertags: patchme-python3
thanks

Hello there!

This package contains a trove classifier[1] in its `setup.py` like
"Programming Language :: Python :: 3". This means that the package's upstream
developers consier this package to be ready for Python 3. This is wonderful!


As part of an ongoing process to migrate as much as we can to Python 3 to
ensure we're ready for our glorious Python 3 future, please build a Python 3
module.


If you need help doing this, please feel free to contact the Debian Python
Modules Team (DPMT), and we can help! If you would welcome a NMU, please do
let the team know (py3porters-de...@lists.alioth.debian.org).

Please upload any new versions before Jessie's release to experimental, the
Release Team has been doing such great work, it'd be a shame to see unstable
out of sync before we release!



If the reason you've not built a Python 3 module is due to the dependency
chain below you, just let me know, and I can add it to our list, or feel
free to file a bug in coordination with the team!


Have a great day, and thanks for your work!
  Paul, on behalf of the Python 3 Embetterment Squad


[1]: https://pypi.python.org/pypi?%3Aaction=list_classifiers

-- 
 .''`.  Paul Tagliamonte   |   Proud Debian Developer
: :'  : 4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
`. `'`  http://people.debian.org/~paultag
 `- http://people.debian.org/~paultag/conduct-statement.txt


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: python-pyramid-zcml
Source-Version: 1.0.0-1.1

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

Debian distribution maintenance software
pp.
Andrey Rahmatullin  (supplier of updated python-pyramid-zcml 
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, 17 Sep 2019 22:37:08 +0500
Source: python-pyramid-zcml
Binary: python3-pyramid-zcml
Architecture: source all
Version: 1.0.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Free Ekanayaka 
Changed-By: Andrey Rahmatullin 
Description:
 python3-pyramid-zcml - Declarative configuration for the Pyramid web framework
Closes: 782952
Changes:
 python-pyramid-zcml (1.0.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Switch from Python 2 to Python 3 (Closes: #782952).
   * Add support for Python 3.7.
   * Add support for Pyramid 1.8 and other modern libs.
   * Disable tests using mako as pyramid_mako is not packaged.
   * Update the priority from extra to optional.
Checksums-Sha1:
 7baa0c7a5f03b4731c048ee31929d0084e6f0a48 1935 python-pyramid-zcml_1.0.0-1.1.dsc
 856b0ad66e2c479b0660d935f96fc728f75d0153 5432 
python-pyramid-zcml_1.0.0-1.1.debian.tar.xz
 e0dadac38fa26b7f6bee987d8861d471475e7df8 7020 
python-pyramid-zcml_1.0.0-1.1_amd64.buildinfo
 fb8a63df02d06f5f707bc1d98fc38a2e4375c2f5 75104 
python3-pyramid-zcml_1.0.0-1.1_all.deb
Checksums-Sha256:
 1a1ee17d1cadedecc3d0b03aa469fe7cb3edcf127c9b2d76cdcff339825cd8b4 1935 
python-pyramid-zcml_1.0.0-1.1.dsc
 8bcd7a070da8ea7905cac2056c7005b8eefff9fbae7e93067aa9279b28fab482 5432 
python-pyramid-zcml_1.0.0-1.1.debian.tar.xz
 a75840021b4faeffeeb6998f00fd09e9f4c62ef267fe8da08a40dc8dd4b1c49e 7020 
python-pyramid-zcml_1.0.0-1.1_amd64.buildinfo
 959896944a048086d6a25106aa33baf4ce5823a02b758a20e3dc09c2b98d80ce 75104 
python3-pyramid-zcml_1.0.0-1.1_all.deb
Files:
 b10ad105c4efc69bcaf8334a7da6fef3 1935 python optional 
python-pyramid-zcml_1.0.0-1.1.dsc
 b9149b1a96ebf2bfc25da958fbc0cef5 5432 python optional 

Bug#782951: marked as done (Please replace with a python3 module or remove the package)

[Debian Bug Tracking System]

Your message dated Wed, 25 Sep 2019 06:00:10 +
with message-id 
and subject line Bug#782951: fixed in python-pyramid-tm 0.5-1.1
has caused the Debian Bug report #782951,
regarding Please replace with a python3 module or remove the 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.)


-- 
782951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pyramid-tm
Severity: wishlist
User: py3porters-de...@lists.alioth.debian.org
Usertags: patchme-python3
thanks

Hello there!

This package contains a trove classifier[1] in its `setup.py` like
"Programming Language :: Python :: 3". This means that the package's upstream
developers consier this package to be ready for Python 3. This is wonderful!


As part of an ongoing process to migrate as much as we can to Python 3 to
ensure we're ready for our glorious Python 3 future, please build a Python 3
module.


If you need help doing this, please feel free to contact the Debian Python
Modules Team (DPMT), and we can help! If you would welcome a NMU, please do
let the team know (py3porters-de...@lists.alioth.debian.org).

Please upload any new versions before Jessie's release to experimental, the
Release Team has been doing such great work, it'd be a shame to see unstable
out of sync before we release!



If the reason you've not built a Python 3 module is due to the dependency
chain below you, just let me know, and I can add it to our list, or feel
free to file a bug in coordination with the team!


Have a great day, and thanks for your work!
  Paul, on behalf of the Python 3 Embetterment Squad


[1]: https://pypi.python.org/pypi?%3Aaction=list_classifiers

-- 
 .''`.  Paul Tagliamonte   |   Proud Debian Developer
: :'  : 4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
`. `'`  http://people.debian.org/~paultag
 `- http://people.debian.org/~paultag/conduct-statement.txt


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: python-pyramid-tm
Source-Version: 0.5-1.1

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

Debian distribution maintenance software
pp.
Andrey Rahmatullin  (supplier of updated python-pyramid-tm 
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, 17 Sep 2019 21:22:59 +0500
Source: python-pyramid-tm
Binary: python3-pyramid-tm
Architecture: source all
Version: 0.5-1.1
Distribution: unstable
Urgency: medium
Maintainer: Free Ekanayaka 
Changed-By: Andrey Rahmatullin 
Description:
 python3-pyramid-tm - Transaction management for the Pyramid web framework
Closes: 782951
Changes:
 python-pyramid-tm (0.5-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Switch from Python 2 to Python 3 (Closes: #782951).
   * Update the priority from extra to optional.
Checksums-Sha1:
 83c3e5211e2304895cf52af39476219278d70b3f 1874 python-pyramid-tm_0.5-1.1.dsc
 a594dc1b4f9194f9bbd067897a3888fb54679174 2340 
python-pyramid-tm_0.5-1.1.debian.tar.xz
 00e64c2301d8adfe62f1fce67997a6a1f80edbac 6899 
python-pyramid-tm_0.5-1.1_amd64.buildinfo
 537ac1ee47319730dc58b559bff92bc9aadf443d 12900 
python3-pyramid-tm_0.5-1.1_all.deb
Checksums-Sha256:
 2f882ec41c3baf4801b6f3f26986759a4c3e90c0489bad22745fe94bbb88773f 1874 
python-pyramid-tm_0.5-1.1.dsc
 3b06639ec84f7432b061275a184a9aeffd40f5c492f45ea942f3671ad17c0730 2340 
python-pyramid-tm_0.5-1.1.debian.tar.xz
 d028ad3433ab73150df2b506f1295ad2aa40a2465c23addcfea56519ed994f72 6899 
python-pyramid-tm_0.5-1.1_amd64.buildinfo
 ff893b0d9a5dd6c65b59ca76a1a485f62e687bc029d0d4ca3043b78c7ea157aa 12900 
python3-pyramid-tm_0.5-1.1_all.deb
Files:
 104525cdef9dd1ca6e2eb8b8764a0f54 1874 python optional 
python-pyramid-tm_0.5-1.1.dsc
 7fce50b304cca08e09a060bae34cc2bb 2340 python optional 
python-pyramid-tm_0.5-1.1.debian.tar.xz
 2e76c0ae90f32364c271c9f787504ad1 6899 python optional 
python-pyramid-tm_0.5-1.1_amd64.buildinfo
 50438e5c354041eaebf3cf6d609a567e 12900 python optional 

Bug#875150: Should we file a removal bug?

[Andreas Tille]

Hi,

On Tue, Sep 24, 2019 at 10:48:24PM +0200, Moritz Mühlenhoff wrote:
> On Tue, Sep 17, 2019 at 12:05:17PM -0300, Lisandro Damián Nicanor Pérez Meyer 
> wrote:
> > Hi! It seems there is no activity on this bug, should we file a removal bug?
> 
> Adding the last two uploaders to CC.

... as well as Uploaders in d/control in CC.
 
> Is anyone of you planning to upload a Qt5 compatible release candidate of 
> qtiplot?
> Otherwise we'll file a removal bug as we're closing in on the Qt5 removalnow.
> 
> (Upload also happen to experimental to avoid a later roundtrip through NEW 
> when a final
> 1.0 comes out)

While the website[1] is announcing

2019/09/18 - QtiPlot 1.0.0-rc10 release available. New features and 
improvements: 

(without mentioning a Qt 5 port explicitly :-() the download area[2]
does not contain any source download of this.  It seems upstream changed
to a closed source model since you can only download binaries with
restricted functionality or you need to buy a license.

I've found several clones of qtiplot at Github, one of these[3] seems to
have some interesting patches others seem to be dedicated for certain
distributions but the latest commits seem to be aged for all and I have
not found any Qt 5 related comments (after a **quick** view).

I admit its a shame but I personally can not spent any time on a Qt 5
port of the existing code.

Kind regards

Andreas.


[1] https://www.qtiplot.com/news.html
[2] https://www.qtiplot.com/download.html
[3] https://github.com/aldomann/qtiplot/

-- 
http://fam-tille.de