Processed: Re: [Help] Re: seqan autopkg test failures triggered by gcc-defaults

[Debian Bug Tracking System]

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

> tags 966433 pending
Bug #966433 [seqan3] seqan autopkg test failures triggered by gcc-defaults
Added tag(s) pending.
> tags 966270 pending
Bug #966270 [src:seqan3] seqan3 FTBFS with gcc 10
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#968383: interimap: fails to work with Dovecot v2.3.11: ERROR: 0 bytes read (got EOF)

[Jonas Smedegaard]

Package: interimap
Version: 0.5.2-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

All my 5 interimap profiles stopped working when security fix was applied
for my local Dovecot install was applied.

Example:

$ interimap --config=jones
jones_local: ERROR: 0 bytes read (got EOF)
jones_local: IMAP traffic (bytes): recv 0 sent 0


It seems there is no --verbose option (only --quiet) so I will ask you to
please guide me in how to provide more detailed data to work with.

I assume this is a general problem, and have set bug severity accordingly
- - please adjust if you disagree.


Kind regards,

 - Jonas


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

Kernel: Linux 5.7.0-1-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_DIE
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages interimap depends on:
ii  init-system-helpers  1.58
ii  libdbd-sqlite3-perl  1.64-1+b1
ii  libinterimap 0.5.2-1
ii  perl 5.30.3-4

interimap recommends no packages.

Versions of packages interimap suggests:
ii  dovecot-imapd  1:2.3.11.3+dfsg1-1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl82RbAACgkQLHwxRsGg
ASHqRw//U/ectjAbGlRA059zwGb6Gl365NufkFscm8ItYblnE1kJcbvgpGAHmg4c
dEOrIzPPMmme6PV1hzk3HDbe9+KCjvwta/kecfvJJzYbohwYf++G+yDACMJlpB4B
PWalaRLFmwRhLp98M033zF+GAH5u6O0ujoIIwe6naVEk/dvEyrHZi/UjMNCcos4e
h4Gyj0cO6xtl6c37yqBf/jmd6zQu2LDFAgToS8mnoNogeB/XMw6UCI+ccAy2gcqm
Nhjw+sN7+alZpk0lyat1Gs8TWhXtSfukk3oRPXnCFjS3ZAbx7hdQexgBEuUMWn0q
eqEnoKeQ/gdEHzmsY4DqtMkM4z5jGO6LxdWb5XX9B2jbkkj1GqFlXQKdWnYiwQKX
/rq1dHkCi7cV+K9YnPZdgwkNVymuG+BKmmoSAuAFiRNt4EZvTmkaAxs10WXHCly3
eQLOYk5/M/JtdO9n1DJp1N22A2iqWPeowQu8LVtNPx3uN/IlBhvGsECIuzaUQIHx
te99i5+Vd9qpL0iJXyPjfimkNO5FeTkSmQ90mQ8jB87Dqrt/YE60BlSoKZ9dL7gB
iM/kME3wTKjGe+fY8ypWtAR6tXMyHgkmkimRdQJvDHRQvArmnleKpWk4ubs3jDTy
Y3g6+6SSwx7qkNTcAwe9Ragerow5yjM6yRia3E9OzNe0Bt/VWAE=
=nQRJ
-END PGP SIGNATURE-

Bug#968387: apparmor: Broken printing and printer autodiscovery

[user]

Package: apparmor
Severity: grave
Justification: renders package unusable



I installed lxc on a freshly installed debian 10 (standard iso + the tasks:
desktop, kde, print-server, laptop).

- The printer was not autodiscovered in the "Print" window of any program,
  and in the "Add printer" window of system-config-printer-settings.
- Even after setting the device URI, print jobs did not make it to the printer
  and there were no info about toner levels, printer availability, etc.

I did not touch apparmor, but aa-status said it was enforcing on a lot
of programs, including /usr/sbin/{cupsd,cups-browsed}, so I ran

aa-complain /usr/sbin/cupsd
aa-complain /usr/sbin/cups-browsed

Now, the printer was autodiscovered, but printing still did not work, so I did

apt-get autopurge apparmor

Now printing works fine, I have toner level info, etc.

Processed: Re: Bug#967217: telepathy-idle: Unversioned Python removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #967217 [src:telepathy-idle] telepathy-idle: Unversioned Python removal in 
sid/bullseye
Added tag(s) patch.

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

Processed: Re: Bug#967218: telepathy-rakia: Unversioned Python removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #967218 [src:telepathy-rakia] telepathy-rakia: Unversioned Python removal 
in sid/bullseye
Added tag(s) patch.

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

Bug#967217: telepathy-idle: Unversioned Python removal in sid/bullseye

[Simon McVittie]

Control: tags -1 + patch

On Tue, 04 Aug 2020 at 09:29:22 +, Matthias Klose wrote:
> We will keep some Python2 package as discussed in
> https://lists.debian.org/debian-python/2020/07/msg00039.html
> but removing the unversioned python packages python-minimal, python,
> python-dev, python-dbg, python-doc.

This is RC, and makes telepathy-idle unbuildable in unstable, because
the python package has already been removed. It doesn't seem to be up for
autoremoval yet, perhaps because polari is relatively high-popcon, although
I suspect polari will decline rapidly now that the GNOME metapackages no
longer pull it in.

When uploading (whether maintainer or NMU) to fix this, there are several
easy fixes that can be applied at the same time. I've sent a merge request
https://salsa.debian.org/telepathy-team/telepathy-idle/-/merge_requests/2
(or see attached diff).

Note that I have only build-tested this, because I no longer use
Telepathy, so an -idle user should test it before upload.

smcv
diff --git a/debian/changelog b/debian/changelog
index 135fab6..b84c678 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,19 @@
+telepathy-idle (0.2.0-3) UNRELEASED; urgency=medium
+
+  [ Simon McVittie ]
+  * Remove myself from Uploaders
+  * Update Vcs-Git (Closes: #907465)
+  * Remove Dafydd Harries from Uploaders.
+Thanks for your past work on this package, Daf! (Closes: #965395)
+  * Explicitly use python2.
+The unversioned python executable is going away for Debian 11.
+(Closes: #967217)
+
+  [ Jonny Lamb ]
+  * Remove myself from Uploaders.
+
+ -- Simon McVittie   Fri, 14 Aug 2020 09:20:58 +0100
+
 telepathy-idle (0.2.0-2) unstable; urgency=medium
 
   * debian/watch: don't watch for development or 1.0-branch versions
diff --git a/debian/control b/debian/control
index 7c435a8..efe2c75 100644
--- a/debian/control
+++ b/debian/control
@@ -2,12 +2,9 @@ Source: telepathy-idle
 Section: net
 Priority: optional
 Maintainer: Debian Telepathy maintainers 
-Uploaders: Dafydd Harries ,
-   Riccardo Setti ,
-   Simon McVittie ,
+Uploaders: Riccardo Setti ,
Sjoerd Simons ,
-   Laurent Bigonville ,
-   Jonny Lamb 
+   Laurent Bigonville 
 Build-Depends: debhelper (>= 9),
dh-autoreconf,
dpkg-dev (>= 1.16.1),
@@ -15,11 +12,11 @@ Build-Depends: debhelper (>= 9),
libdbus-1-dev,
libdbus-glib-1-dev (>= 0.51),
libtelepathy-glib-dev (>= 0.22),
-   xsltproc,
-   python
+   python2,
+   xsltproc
 Standards-Version: 3.9.5
-Vcs-Git: git://anonscm.debian.org/pkg-telepathy/telepathy-idle.git
-Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-telepathy/telepathy-idle.git
+Vcs-Git: https://salsa.debian.org/telepathy-team/telepathy-idle.git
+Vcs-Browser: https://salsa.debian.org/telepathy-team/telepathy-idle
 Homepage: http://sourceforge.net/projects/telepathy-idle
 
 Package: telepathy-idle
diff --git a/debian/rules b/debian/rules
index 99456a0..8c440db 100755
--- a/debian/rules
+++ b/debian/rules
@@ -14,6 +14,7 @@ override_dh_auto_configure:
 		--libdir="\$${prefix}/lib" \
 		--libexecdir="\$${libdir}/telepathy" \
 		--disable-static \
+		PYTHON=python2 \
 $(NULL)
 
 # The regression tests are too prone to race conditions for the buildds,

Bug#967218: telepathy-rakia: Unversioned Python removal in sid/bullseye

[Simon McVittie]

Control: tags -1 + patch

On Tue, 04 Aug 2020 at 09:29:23 +, Matthias Klose wrote:
> We will keep some Python2 package as discussed in
> https://lists.debian.org/debian-python/2020/07/msg00039.html
> but removing the unversioned python packages python-minimal, python,
> python-dev, python-dbg, python-doc.

This is RC, and makes telepathy-rakia unbuildable in unstable, because
the python package has already been removed. It is now up for autoremoval
as a result.

When uploading (whether maintainer or NMU) to fix this, there are several
easy fixes that can be applied at the same time. I've sent a merge request
https://salsa.debian.org/telepathy-team/telepathy-rakia/-/merge_requests/1
(or see attached diff).

Note that I have only build-tested this, because I no longer use
Telepathy, so a -rakia user should test it before upload.

smcv
diff --git a/debian/changelog b/debian/changelog
index 9f354da..ca502d1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,20 @@
+telepathy-rakia (0.8.0-4) UNRELEASED; urgency=medium
+
+  [ Simon McVittie ]
+  * Remove myself from Uploaders
+  * Update Vcs-Git (Closes: #907463)
+  * Remove Dafydd Harries from uploaders.
+Thanks for your past work on this package, Daf! (Closes: #965399)
+  * Explicitly use python2 for build.
+The unversioned python executable is going away for Debian 11.
+(Closes: #967218)
+  * Remove telepathy-sofiasip transitional package (Closes: #878985)
+
+  [ Jonny Lamb ]
+  * Remove myself from Uploaders.
+
+ -- Simon McVittie   Fri, 14 Aug 2020 09:41:12 +0100
+
 telepathy-rakia (0.8.0-3) unstable; urgency=medium
 
   * debian/watch: only watch for 0.x stable branches
diff --git a/debian/control b/debian/control
index 0a6e31e..0f2b9c9 100644
--- a/debian/control
+++ b/debian/control
@@ -2,12 +2,9 @@ Source: telepathy-rakia
 Section: net
 Priority: optional
 Maintainer: Debian Telepathy maintainers 
-Uploaders: Dafydd Harries ,
-   Simon McVittie ,
-   Sjoerd Simons ,
+Uploaders: Sjoerd Simons ,
Laurent Bigonville ,
-   Loic Minier ,
-   Jonny Lamb 
+   Loic Minier 
 Build-Depends: debhelper (>= 9),
dh-autoreconf,
libglib2.0-dev (>= 2.30),
@@ -16,11 +13,11 @@ Build-Depends: debhelper (>= 9),
libsofia-sip-ua-glib-dev (>= 1.12.11),
libtelepathy-glib-dev (>= 0.17.7),
libssl-dev,
-   xsltproc,
-   python
+   python2,
+   xsltproc
 Standards-Version: 3.9.5
-Vcs-Git: git://anonscm.debian.org/pkg-telepathy/telepathy-rakia.git
-Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-telepathy/telepathy-rakia.git
+Vcs-Git: https://salsa.debian.org/telepathy-team/telepathy-rakia.git
+Vcs-Browser: https://salsa.debian.org/telepathy-team/telepathy-rakia
 Homepage: http://telepathy.freedesktop.org/
 
 Package: telepathy-rakia
@@ -33,13 +30,3 @@ Provides: telepathy-connection-manager, telepathy-sofiasip
 Description: SIP connection manager for the Telepathy framework
  telepathy-rakia is a SIP connection manager for the Telepathy framework
  (http://telepathy.freedesktop.org) based on the SofiaSIP-stack.
-
-Package: telepathy-sofiasip
-Architecture: all
-Section: oldlibs
-Priority: extra
-Depends: telepathy-rakia,
- ${misc:Depends}
-Description: Transitional package for telepathy-rakia
- This is a transitional package to ease upgrades to the telepathy-rakia
- package. It can safely be removed.
diff --git a/debian/rules b/debian/rules
index 99cb3d3..62a60ca 100755
--- a/debian/rules
+++ b/debian/rules
@@ -11,11 +11,9 @@ override_dh_auto_configure:
 		--libdir="\$${prefix}/lib" \
 		--libexecdir="\$${libdir}/telepathy" \
 		--disable-static \
+		PYTHON=python2 \
 $(NULL)
 
-override_dh_install:
-	dh_install --list-missing
-
 # The regression tests are too prone to race conditions for the buildds,
 # and don't work when autoreconf'd with Automake 1.13.
 override_dh_auto_test:
diff --git a/debian/telepathy-rakia.install b/debian/telepathy-rakia.install
deleted file mode 100644
index 0148204..000
--- a/debian/telepathy-rakia.install
+++ /dev/null
@@ -1,5 +0,0 @@
-usr/include/
-usr/lib/telepathy/
-usr/share/dbus-1/services/
-usr/share/man/man8/
-usr/share/telepathy/managers/

Bug#966270: [Help] Re: seqan autopkg test failures triggered by gcc-defaults

[Andreas Tille]

Hi Michael,

On Fri, Aug 14, 2020 at 09:01:19AM +0200, Michael Crusoe wrote:
> I've got a fixed version of a release candidate of seqan3 3.0.2 in salsa.
> However it needs an updated range-v3 which has yet to be uploaded: see
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968053

If the new version you prepared would fix RC bug #966900 as well I'd
say go for an upload.
 
> I can upload the seqan3 3.0.2 release candidate with a code copy of the
> fixed range-v3, but as no packages build-depend on seqan3 I don't see the
> rush. Please feel free to correct my mis-understanding.

I agree that rush is not really needed.  However, our team has currently
lots of RC bugs and these create noise and developer time if the bug
report does not reflect the full story (specifically when different
people try to build this heavy package at the same time to check the
status.
 
Thanks a lot for your work on this

  Andreas.

-- 
http://fam-tille.de

Bug#968124: marked as done (diffoscope: FTBFS with fpc 3.2.0)

[Debian Bug Tracking System]

Your message dated Fri, 14 Aug 2020 09:18:55 +
with message-id 
and subject line Bug#968124: fixed in diffoscope 156
has caused the Debian Bug report #968124,
regarding diffoscope: FTBFS with fpc 3.2.0
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.)


-- 
968124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: diffoscope
Version: 155
Severity: serious
Tags: ftbfs sid
X-Debbugs-CC: pkg-pascal-de...@alioth-lists.debian.net

Hi Maintainer

As can be seen on reproducible builds [1], this package FTBFS since
the upload of fpc 3.2.0+dfsg-5 to unstable.

I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope.html


=== FAILURES ===
_ test_identification __

file1 = <
/build/1st/diffoscope-155/.pybuild/cpython3_3.8/build/tests/data/test1.ppu>

@skip_unless_tools_exist("ppudump")
def test_identification(file1):
>   assert isinstance(file1, PpuFile)
E   AssertionError: assert False
E+  where False = isinstance(<
/build/1st/diffoscope-155/.pybuild/cpython3_3.8/build/tests/data/test1.ppu>,
PpuFile)

file1  = <
/build/1st/diffoscope-155/.pybuild/cpython3_3.8/build/tests/data/test1.ppu>

tests/comparators/test_ppu.py:51: AssertionError
__ test_diff ___

differences = []

@skip_unless_tool_is_at_least("ppudump", ppudump_version, "3.0.0")
def test_diff(differences):
expected_diff = get_data("ppu_expected_diff")
>   assert differences[0].unified_diff == expected_diff
E   IndexError: list index out of range

differences = []
expected_diff = ('@@ -15,15 +15,15 @@\n'
 ' Definitions stored  : 121\n'
 ' Symbols stored  : 398\n'
 ' \n'
 ' Interface section\n'
 ' --\n'
 ' Module Name: CastleGenericLists\n'
 ' \n'
 '-Source file 1 : castlegenericlists.pas 2016/02/17 15:03:46\n'
 '+Source file 1 : castlegenericlists.pas 2016/02/17 15:04:53\n'
 ' Uses unit: System (Crc: 09C1FD4E, IntfcCrc: 3A093E2F, IndCrc: FEDD6E0A)\n'
 ' Uses unit: objpas (Crc: 663BC437, IntfcCrc: CA7886A2, IndCrc: 64D020AC)\n'
 ' Uses unit: fgl (Crc: C38E0A5A, IntfcCrc: 470D2834, IndCrc: 0764D076)\n'
 ' Link unit object file: castlegenericlists.o (static )\n'
 ' DerefMapsize: 2\n'
 ' DerefMap[0] = FGL\n'
 ' DerefMap[1] = SYSTEM\n')

tests/comparators/test_ppu.py:67: IndexError
__ test_compare_non_existing ___

monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x7f1522be2520>
file1 = <
/build/1st/diffoscope-155/.pybuild/cpython3_3.8/build/tests/data/test1.ppu>

@skip_unless_tool_is_at_least("ppudump", ppudump_version, "3.0.0")
def test_compare_non_existing(monkeypatch, file1):
>   assert_non_existing(monkeypatch, file1, has_null_source=False)

file1  = <
/build/1st/diffoscope-155/.pybuild/cpython3_3.8/build/tests/data/test1.ppu>
monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x7f1522be2520>

tests/comparators/test_ppu.py:72:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x7f1522be2520>
fixture = <
/build/1st/diffoscope-155/.pybuild/cpython3_3.8/build/tests/data/test1.ppu>
has_null_source = False, has_details = True

def assert_non_existing(
monkeypatch, fixture, has_null_source=True, has_details=True
):
monkeypatch.setattr(Config(), "new_file", True)
assert Config().new_file, "Did not get patched"

difference = fixture.compare(MissingFile("/nonexisting", fixture))

assert difference.source2 == "/nonexisting"
>   assert not has_details or len(difference.details) > 0
E   AssertionError

difference = 
fixture= <
/build/1st/diffoscope-155/.pybuild/cpython3_3.8/build/tests/data/test1.ppu>
has_details = True
has_null_source = False
monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x7f1522be2520>

tests/utils/nonexisting.py:35: AssertionError
--- End Message ---
--- Begin Message ---
Source: diffoscope
Source-Version: 156
Done: Chris Lamb 

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

Bug#968383: marked as done (interimap: fails to work with Dovecot v2.3.11: ERROR: 0 bytes read (got EOF))

[Debian Bug Tracking System]

Your message dated Fri, 14 Aug 2020 11:30:39 +0200
with message-id <159739743993.3529538.372973373822306...@auryn.jones.dk>
and subject line Re: interimap: fails to work with Dovecot v2.3.11: ERROR: 0 
bytes read (got EOF)
has caused the Debian Bug report #968383,
regarding interimap: fails to work with Dovecot v2.3.11: ERROR: 0 bytes read 
(got EOF)
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

All my 5 interimap profiles stopped working when security fix was applied
for my local Dovecot install was applied.

Example:

$ interimap --config=jones
jones_local: ERROR: 0 bytes read (got EOF)
jones_local: IMAP traffic (bytes): recv 0 sent 0


It seems there is no --verbose option (only --quiet) so I will ask you to
please guide me in how to provide more detailed data to work with.

I assume this is a general problem, and have set bug severity accordingly
- - please adjust if you disagree.


Kind regards,

 - Jonas


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

Kernel: Linux 5.7.0-1-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_DIE
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages interimap depends on:
ii  init-system-helpers  1.58
ii  libdbd-sqlite3-perl  1.64-1+b1
ii  libinterimap 0.5.2-1
ii  perl 5.30.3-4

interimap recommends no packages.

Versions of packages interimap suggests:
ii  dovecot-imapd  1:2.3.11.3+dfsg1-1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl82RbAACgkQLHwxRsGg
ASHqRw//U/ectjAbGlRA059zwGb6Gl365NufkFscm8ItYblnE1kJcbvgpGAHmg4c
dEOrIzPPMmme6PV1hzk3HDbe9+KCjvwta/kecfvJJzYbohwYf++G+yDACMJlpB4B
PWalaRLFmwRhLp98M033zF+GAH5u6O0ujoIIwe6naVEk/dvEyrHZi/UjMNCcos4e
h4Gyj0cO6xtl6c37yqBf/jmd6zQu2LDFAgToS8mnoNogeB/XMw6UCI+ccAy2gcqm
Nhjw+sN7+alZpk0lyat1Gs8TWhXtSfukk3oRPXnCFjS3ZAbx7hdQexgBEuUMWn0q
eqEnoKeQ/gdEHzmsY4DqtMkM4z5jGO6LxdWb5XX9B2jbkkj1GqFlXQKdWnYiwQKX
/rq1dHkCi7cV+K9YnPZdgwkNVymuG+BKmmoSAuAFiRNt4EZvTmkaAxs10WXHCly3
eQLOYk5/M/JtdO9n1DJp1N22A2iqWPeowQu8LVtNPx3uN/IlBhvGsECIuzaUQIHx
te99i5+Vd9qpL0iJXyPjfimkNO5FeTkSmQ90mQ8jB87Dqrt/YE60BlSoKZ9dL7gB
iM/kME3wTKjGe+fY8ypWtAR6tXMyHgkmkimRdQJvDHRQvArmnleKpWk4ubs3jDTy
Y3g6+6SSwx7qkNTcAwe9Ragerow5yjM6yRia3E9OzNe0Bt/VWAE=
=nQRJ
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Quoting Jonas Smedegaard (2020-08-14 10:05:10)
> All my 5 interimap profiles stopped working when security fix was applied
> for my local Dovecot install was applied.

False alarm: Turned out to be a change in dovecot configuration files 
incompatible with my accessing it via tunnel.

Revealed by manually running the underlying doveadm command.

Sorry for the noise!


 - Jonas

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

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

signature.asc
Description: signature
--- End Message ---

Bug#966301: guile OOM test failures on ppc64el

[Matthias Klose]

I'm now NMUing both guile-2.2 and guile-3.0 to just ignore the test results on
ppc64el, without closing the bug reports.  It's blocking the gcc-10 migration to
testing.

Bug#963049: [Pkg-freeipa-devel] Bug#963049: pki-base: syntax error in /usr/share/pki/scripts/config

[Timo Aaltonen]

severity normal
thanks

On 18.6.2020 13.31, Laurent Bonnaud wrote:
> 
> Package: pki-base
> Version: 10.9.0~a2-2
> Severity: serious
> 
> 
> Dear Maintainer,
> 
> here is the problem:
> 
> # source /usr/share/pki/scripts/config
> -bash: break: only meaningful in a `for', `while', or `until' loop

This isn't a fatal error. This is caused by forcing the scripts to use
bash, and without that pki-tomcatd wouldn't even start. You may check
where the actual bashism is and fix that, then we'd be able to drop
forcing bash.

-- 
t

Bug#967197: marked as done (pspp: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 14 Aug 2020 09:53:40 +
with message-id 
and subject line Bug#967197: fixed in pspp 1.2.0-6
has caused the Debian Bug report #967197,
regarding pspp: Unversioned Python 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.)


-- 
967197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pspp
Version: 1.2.0-5
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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: pspp
Source-Version: 1.2.0-6
Done: Friedrich Beckmann 

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

Debian distribution maintenance software
pp.
Friedrich Beckmann  (supplier of updated pspp 
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: Fri, 14 Aug 2020 06:29:56 +0200
Source: pspp
Binary: pspp pspp-dbgsym
Architecture: source amd64
Version: 1.2.0-6
Distribution: unstable
Urgency: low
Maintainer: Friedrich Beckmann 
Changed-By: Friedrich Beckmann 
Description:
 pspp   - Statistical analysis tool
Closes: 966858 967197
Changes:
 pspp (1.2.0-6) unstable; urgency=low
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Repository.
   * Drop unnecessary dependency on dh-autoreconf.
 .
   [ Friedrich Beckmann ]
   * add patch widget.patch to fix FTBFS
 Closes: #966858
   * add patch delimiter.patch to fix regression failure
 see: https://savannah.gnu.org/bugs/?58943
   * remove elpa - pspp-mode.el moved to elpa repository
   * moved from python to python2 package name
 Closes: #967197
   * change maintainer to Beckmann - received no emails
Checksums-Sha1:
 9ce1b24e477239f35709cb7da8dd52ba8af8ed20 2057 pspp_1.2.0-6.dsc
 210e537cbffea8de319c7e5e03e4cfbf5b34012a 36312 pspp_1.2.0-6.debian.tar.xz
 e2b7a0e030cfaf3928770560af1e98abece03a44 3089448 pspp-dbgsym_1.2.0-6_amd64.deb
 c4eb445e5072e28533f853e2974ee3e8bac6973d 15096 pspp_1.2.0-6_amd64.buildinfo
 e7499c22b09726f3ee02ffa48788910843c7ce6e 3822908 pspp_1.2.0-6_amd64.deb
Checksums-Sha256:
 c16c54404483d8510bd9652a39314697c5b337b6ea14dc166b70a010b6e11bee 2057 
pspp_1.2.0-6.dsc
 1c3f572e0685528cfd882903764aec1f92f9919347fc41f39f23d5cb4cf68f57 36312 
pspp_1.2.0-6.debian.tar.xz
 f984c1e956dd789565abad2eeb48c77708ce4ca3c5f4ba283b99bfe0094e5e1c 3089448 
pspp-dbgsym_1.2.0-6_amd64.deb
 c379ad90f16878affdf2e08e0b976db33cf3ca67dda56f6b41c5fbc7896c43cc 15096 
pspp_1.2.0-6_amd64.buildinfo
 c64812c317c5048d792097415de48bcb27cb869169ea69b5107cdb078e305ebe 3822908 
pspp_1.2.0-6_amd64.deb
Files:
 65285fa92cc8d41a008dc2224ef2041c 2057 math optional pspp_1.2.0-6.dsc
 b3c2c04182073c56d2c0747c9d922c2b 36312 math optional pspp_1.2.0-6.debian.tar.xz
 e1409e51d2338725cd2dc7d37076bc56 3089448 debug optional 
pspp-dbgsym_1.2.0-6_amd64.deb
 5cbf903cc362cf3dc7f24791c227ce6c 15096 math optional 
pspp_1.2.0-6_amd64.buildinfo
 32401242fea61527e4c21243a1116e21 3822908 math optional pspp_1.2.0-6_amd64.deb

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEGp+TZe9/EUJidSaxzHnYClu

Bug#965308: jackd won't start

[Simon McVittie]

On Fri, 14 Aug 2020 at 10:51:46 +0200, Arnaldo Pirrone wrote:
> I would like to point out that the error is not showing up any more after the
> updates, now the error is different

It seems it's now failing to open the configured ALSA PCM devices (which
probably also shouldn't happen?). From the strace output, it seems the
configured ALSA devices doesn't exist in /dev/snd:

> strace -efile jackd -d alsa
...
> openat(AT_FDCWD, "/dev/snd/pcmC0D0p", O_RDWR|O_NONBLOCK|O_CLOEXEC) = -1 
> ENOENT (File o directory non esistente)
> stat("/usr/share/alsa/alsa.conf", {st_mode=S_IFREG|0644, st_size=9623, ...}) 
> = 0
> openat(AT_FDCWD, "/dev/snd/controlC0", O_RDONLY|O_CLOEXEC) = 6
> openat(AT_FDCWD, "/dev/snd/controlC0", O_RDWR|O_CLOEXEC) = 6
> openat(AT_FDCWD, "/dev/snd/pcmC0D0c", O_RDWR|O_NONBLOCK|O_CLOEXEC) = -1 
> ENOENT (File o directory non esistente)
> ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to 
> capture-only mode

That seems like a completely different failure mode.

smcv

Bug#966858: marked as done (pspp: FTBFS: ld: src/ui/gui/psppire-widgets.o:./src/ui/gui/widgets.c:174: multiple definition of `align_enum_type'; src/ui/gui/psppire-psppire-dict.o:./src/ui/gui/psppire-d

[Debian Bug Tracking System]

Your message dated Fri, 14 Aug 2020 09:53:40 +
with message-id 
and subject line Bug#966858: fixed in pspp 1.2.0-6
has caused the Debian Bug report #966858,
regarding pspp: FTBFS: ld: 
src/ui/gui/psppire-widgets.o:./src/ui/gui/widgets.c:174: multiple definition of 
`align_enum_type'; 
src/ui/gui/psppire-psppire-dict.o:./src/ui/gui/psppire-dict.c:45: first defined 
here
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.)


-- 
966858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pspp
Version: 1.2.0-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> /bin/bash ./libtool  --tag=CC   --mode=link gcc -pthread 
> -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 
> -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid 
> -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/gtksourceview-3.0 -I/usr/include/libxml2 
> -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 
> -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid 
> -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 
> -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid 
> -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wall 
> -DGDK_MULTIHEAD_SAFE=1 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security-rpath 
> /usr/lib/x86_64-linux-gnu/pspp -Wl,-z,relro -Wl,-z,now -o src/ui/gui/psppire 
> src/ui/gui/psppire-psppire-dialog.o src/ui/gui/psppire-psppire-keypad.o 
> src/ui/gui/psppire-psppire-selector.o src/ui/gui/psppire-psppire-buttonbox.o 
> src/ui/gui/psppire-psppire-scanf.o src/ui/gui/psppire-psppire-acr.o 
> src/ui/gui/psppire-psppire-import-assistant.o 
> src/ui/gui/psppire-builder-wrapper.o src/ui/gui/psppire-dialog-common.o 
> src/ui/gui/psppire-dict-display.o src/ui/gui/psppire-entry-dialog.o 
> src/ui/gui/psppire-executor.o src/ui/gui/psppire-find-dialog.o 
> src/ui/gui/psppire-goto-case-dialog.o src/ui/gui/psppire-helper.o 
> src/ui/gui/psppire-help-menu.o src/ui/gui/psppire-main.o 
> src/ui/gui/psppire-missing-val-dialog.o src/ui/gui/psppire-options-dialog.o 
> src/ui/gui/psppire-psppire.o src/ui/gui/psppire-psppire-checkbox-treeview.o 
> src/ui/gui/psppire-psppire-conf.o src/ui/gui/psppire-psppire-data-editor.o 
> src/ui/gui/psppire-psppire-data-store.o 
> src/ui/gui/psppire-psppire-data-window.o 
> src/ui/gui/psppire-psppire-dialog-action.o 
> src/ui/gui/psppire-psppire-dialog-action-aggregate.o 
> src/ui/gui/psppire-psppire-dialog-action-autorecode.o 
> src/ui/gui/psppire-psppire-dialog-action-1sks.o 
> src/ui/gui/psppire-psppire-dialog-action-barchart.o 
> src/ui/gui/psppire-psppire-dialog-action-binomial.o 
> src/ui/gui/psppire-psppire-dialog-action-chisquare.o 
> src/ui/gui/psppire-psppire-dialog-action-compute.o 
> src/ui/gui/psppire-psppire-dialog-action-comments.o 
> src/ui/gui/psppire-psppire-dialog-action-count.o 
> src/ui/gui/psppire-psppire-dialog-action-correlation.o 
> src/ui/gui/psppire-psppire-dialog-action-crosstabs.o 
> src/ui/gui/psppire-psppire-di

Bug#963048: marked as done (pki-base: postinst failure because of incorrect use of --silent option of pki-upgrade)

[Debian Bug Tracking System]

Your message dated Fri, 14 Aug 2020 10:03:37 +
with message-id 
and subject line Bug#963048: fixed in dogtag-pki 10.9.1-2
has caused the Debian Bug report #963048,
regarding pki-base: postinst failure because of incorrect use of --silent 
option of pki-upgrade
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.)


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

Package: pki-base
Version: 10.9.0~a2-2
Severity: serious


Dear Maintainer,

here is the problem:

Setting up pki-base (10.9.0~a2-2) ...
dpkg: error processing package pki-base (--configure):
 installed pki-base package post-installation script subprocess returned error 
exit status 1
Errors were encountered while processing:
 pki-base


The problem comes from the postinst script that tries to execute this command:

# pki-upgrade --silent
[...]
ERROR: option --silent not recognized
Usage: pki-upgrade [OPTIONS]

  --status   Show upgrade status only. Do not perform 
upgrade.
  --revert   Revert the last version.
  --validate Validate upgrade status.

  -X Show advanced options.
  -v, --verbose  Run in verbose mode.
  --debugRun in debug mode.
  -h, --help Show this help message.


Removing the --silent option fixes the problem.


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

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

Versions of packages pki-base depends on:
ii  python3-pki-base  10.9.0~a2-2

pki-base recommends no packages.

pki-base suggests no packages.

-- no debconf information

-- 
Laurent.
--- End Message ---
--- Begin Message ---
Source: dogtag-pki
Source-Version: 10.9.1-2
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated dogtag-pki 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: Fri, 14 Aug 2020 12:43:32 +0300
Source: dogtag-pki
Architecture: source
Version: 10.9.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Closes: 963048
Changes:
 dogtag-pki (10.9.1-2) unstable; urgency=medium
 .
   * pki-base.postinst: Drop --silent. (Closes: #963048)
Checksums-Sha1:
 d20a575c9d18a9706944cf8a14dd843c2bf1da5f 3832 dogtag-pki_10.9.1-2.dsc
 fe2af112ac5f6c632d9405c6784f584910615d14 33648 
dogtag-pki_10.9.1-2.debian.tar.xz
 79f57278567ebac430f282ec1778cb98de583f2a 15497 
dogtag-pki_10.9.1-2_source.buildinfo
Checksums-Sha256:
 eee928d7ff2d19f2a771a430805aa8eb60cae84251f7c2326676c673d29898df 3832 
dogtag-pki_10.9.1-2.dsc
 f3251a00a7c0c667bb4db2f8b2e18be78cd4cdc02596c700e56b6f7ba98c9a95 33648 
dogtag-pki_10.9.1-2.debian.tar.xz
 9486cd93c4d74530aedd67465ea617657f25b6bd39d9fa5b3f6237140d589d5e 15497 
dogtag-pki_10.9.1-2_source.buildinfo
Files:
 1ed60b081220e4cf730d3341847a4ff8 3832 java optional dogtag-pki_10.9.1-2.dsc
 e7f37ded6c523447a4d3daf9d999d636 33648 java optional 
dogtag-pki_10.9.1-2.debian.tar.xz
 d2f7833af55a6fca0c8b72d5e6535b3c 15497 java optional 
dogtag-pki_10.9.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl82XO0ACgkQy3AxZaiJ
hNyG1w/+Kybp1SLDSjHYqWXGEPAP1Rl32HX/TwMVm6D0JiO7NqwUFGgN1eG2SMvn
L5JxOr7xTy2NAmDHxCKLqF8Ar4cCMNwp6J449fE0yNPDLP4ME/6ONizR6MJG9enD
fSgiTLHMWj5qx1ZGUrGg7dc6qSWAVi+GuMIWT4trv3qL8MpYmABC4YVePshiZ3gb
1EhWVYy3w8BUJH2tHv1rJpTWIjE+8uk+oRuHJHe3EmMcszPS2SVke5Xn+t0aXzwW
fMVwIrT7puKvGohd9fPNbnPZFeOgbd7LiLOuX+ov2JcK0xORA49BwbfpLNaaggbh
Qs

Bug#968395: Stretch update of {{ package }}?

[Emilio Pozuelo Monfort]

Package: terminator
Severity: grave
Tags: security

Dear maintainer(s),

The Debian LTS team would like to fix the security issues which are
currently open in the Stretch version of {{ package }}:
{%- if cve -%}
{% for entry in cve %}
https://security-tracker.debian.org/tracker/{{ entry }}
{%- endfor -%}
{%- else %}
https://security-tracker.debian.org/tracker/source-package/{{ package }}
{%- endif %}

Would you like to take care of this yourself?

If yes, please follow the workflow we have defined here:
https://wiki.debian.org/LTS/Development

If that workflow is a burden to you, feel free to just prepare an
updated source package and send it to debian-...@lists.debian.org
(via a debdiff, or with an URL pointing to the source package,
or even with a pointer to your packaging repository), and the members
of the LTS team will take care of the rest. Indicate clearly whether you
have tested the updated package or not.

If you don't want to take care of this update, it's not a problem, we
will do our best with your package. Just let us know whether you would
like to review and/or test the updated package before it gets released.

You can also opt-out from receiving future similar emails in your
answer and then the LTS Team will take care of {{ package }} updates
for the LTS releases.

Thank you very much.

{{ sender }},
  on behalf of the Debian LTS team.

PS: A member of the LTS team might start working on this update at
any point in time. You can verify whether someone is registered
on this update in this file:
https://salsa.debian.org/security-tracker-team/security-tracker/raw/master/data/dla-needed.txt

Processed: Bug#964854 marked as pending in npm

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #964854 [src:npm] npm: autopkgtests failures on s390x
Bug #964880 [src:npm] npm: test failures in ppc64el and s390x
Added tag(s) pending.
Added tag(s) pending.

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

Bug#964854: marked as pending in npm

[Xavier Guimard]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/npm/-/commit/7129b816a7ab814b6e42c8fdd27ecb98cfb76859


Add s390x and ppc64el in supported platforms list

Closes: #964854


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/964854

Bug#968383: marked as done (interimap: fails to work with Dovecot v2.3.11: ERROR: 0 bytes read (got EOF))

[Guilhem Moulin]

On Fri, 14 Aug 2020 at 09:33:03 +, Debian Bug Tracking System wrote:
>> All my 5 interimap profiles stopped working when security fix was applied
>> for my local Dovecot install was applied.
> 
> False alarm: Turned out to be a change in dovecot configuration files 
> incompatible with my accessing it via tunnel.
> 
> Revealed by manually running the underlying doveadm command.

Thanks for the update, Jonas!  Mind sharing what you had to change in
Dovecot?  1:2.3.11.3+dfsg1-1 doesn't break the test suite, so maybe you
have a setup it'd be worth having test covering for.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#966983: marked as pending in sphinx

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/sphinx/-/commit/d36f7f31bb0fc6ef056f59cca361eab2e402c4f1


New upstream release.

Fixes a crash when documenting extension modules.

Closes: #966983.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/966983

Processed: Bug#966983 marked as pending in sphinx

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #966983 [python3-sphinx] python-skbio: FTBFS: dh_sphinxdoc: error: 
debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/search.html does 
not load searchindex.js
Added tag(s) pending.

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

Bug#968395: Stretch update of {{ package }}?

[Markus Frosch]

Hi Emilio,

On Fri, 2020-08-14 at 12:40 +0200, Emilio Pozuelo Monfort wrote:
> The Debian LTS team would like to fix the security issues which are
> currently open in the Stretch version of {{ package }}:
> 

I'm not aware of any security issues with Terminator.

Not sure why went wrong here, apart from the template rendering.

Cheers
Markus
-- 
lazyfro...@debian.org
https://lazyfrosch.de

Bug#968339: Accept

[Vasyl Gello]

Control: owner -1 !

Hi Gianfranco!

Thanks for reporting this! I will investigate the issue and file it upstream.
-- 
Vasyl Gello
==
Certified SolidWorks Expert

Mob.:+380 (98) 465 66 77

E-Mail: vasek.ge...@gmail.com

Skype: vasek.gello
==
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다

Processed: Accept

[Debian Bug Tracking System]

Processing control commands:

> owner -1 !
Bug #968339 [src:kodi] kodi: FTBFS in sid (test failures)
Owner recorded as Vasyl Gello .

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

Bug#964854: marked as done (npm: autopkgtests failures on s390x)

[Debian Bug Tracking System]

Your message dated Fri, 14 Aug 2020 11:51:03 +
with message-id 
and subject line Bug#964854: fixed in npm 6.14.7+ds-1
has caused the Debian Bug report #964854,
regarding npm: autopkgtests failures on s390x
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.)


-- 
964854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: npm
Version: 6.14.5+ds-1
Severity: serious

Hello, looks like npm is failing again its autopkgtests...

On armhf there is a timeout that I "fixed" with: 
https://github.com/npm/cli/pull/1454

on ppc64el there is another failure:
https://ci.debian.net/data/autopkgtest/unstable/ppc64el/n/npm/6017343/log.gz

and I also spot a s390x failure on Ubuntu:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/s390x/n/npm/20200505_235736_15e60@/log.gz

can you please have another look?
(in the meanwhile I'm marking that test as flaky in Ubuntu)

thanks!

Gianfranco
--- End Message ---
--- Begin Message ---
Source: npm
Source-Version: 6.14.7+ds-1
Done: Xavier Guimard 

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated npm 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: Fri, 14 Aug 2020 13:26:21 +0200
Source: npm
Architecture: source
Version: 6.14.7+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 964854
Changes:
 npm (6.14.7+ds-1) unstable; urgency=medium
 .
   * Team upload
   * Add s390x and ppc64el in supported platforms list (Closes: #964854)
   * New upstream version 6.14.7+ds
   * Update copyright
   * Update lintian overrides
Checksums-Sha1: 
 64864237a2da564ab1575716241dc9180bf27769 6736 npm_6.14.7+ds-1.dsc
 83de3a66bca8d8b5a14b84fa5d8dba4c4fcf3b6c 1435316 npm_6.14.7+ds.orig.tar.xz
 f7c7cb7180e23d12c0e514e1a268eba3a7f44f78 42932 npm_6.14.7+ds-1.debian.tar.xz
Checksums-Sha256: 
 4665b9a121cff3111535ba2725744b009e6dea43e9408e80c5572c3f4eefab32 6736 
npm_6.14.7+ds-1.dsc
 8f009f973ed4f1c29cc1775f9873fce0af0f15e5e900de2c8e56bccb282f4760 1435316 
npm_6.14.7+ds.orig.tar.xz
 9f49897ad17b853f0a429237604eee7e74930a348144d6ba40350086693274ed 42932 
npm_6.14.7+ds-1.debian.tar.xz
Files: 
 153ded4ee1d106a11ccedeb5fa3dc8cc 6736 javascript optional npm_6.14.7+ds-1.dsc
 04c16dc4e164272da83915c4730c3463 1435316 javascript optional 
npm_6.14.7+ds.orig.tar.xz
 f41bf145fa9708298856b9f962bd27ce 42932 javascript optional 
npm_6.14.7+ds-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl82dr8ACgkQ9tdMp8mZ
7uloTRAAhAAfTi75xPorDZrmvHcvjSkBZrqXdLIHcPt5ksbDDoXxfRaeop4Ilh7P
vzYcwLlhq5pT+w9CKg6iUS7P8jpbRj58rSOhhB/dqOAIWJ3ULEQ2YGBAzOM/iazU
6qg2nbVBI7Bbo3GGB4BCNbuG/Xe5jiJ2O3VBkLaLEVrGo/FE4W8JpmM5UkybcOAv
0385DbaIVSyy/kgJHy6S7M1RIiayw73/uUd+Plt/G7xGwnflOF+w1oHEhGaY1HpA
Z4sYXgTm4gov6PSuut5NpVUOUFMc2TX76IM7U4A3LMKJVDkJzA++KmQNsAlJh4jw
+vzLzkXID2ex07Sa81niTaXEhiZ4AUAaJVdjejbCyvB11z2XIoOS2c5QgIgwtUOc
zMtgFwAIyx1XaaknqU9uOjW9jjhFYVF0BJ9xgMauQISBof7iUBhjTrFNeyEWpc3G
/GIBCarpn4NxLAL2jU0hUUzz+Lkxct10DTtxv/R998z2XUY9LYhaEjIsZwCWmh6X
OYDx41N2M4HjeNBzkQjSlYTviIcaZmmmFPg+k67KZ8NEkSNxlKsKpYLb9DM1ZS6S
F717TRuCB3Hu4T5DAIWI7v+iVRAWAweB0Ixuut6ryqoiboht9wN+ptz/FoBYIMz0
lHMXeuOEatfmC6EpE6fkfA478+rLFCBI0bIlpHnWN3JqDNvfOoU=
=OVl4
-END PGP SIGNATURE End Message ---

Bug#964880: marked as done (npm: test failures in ppc64el and s390x)

[Debian Bug Tracking System]

Your message dated Fri, 14 Aug 2020 11:51:03 +
with message-id 
and subject line Bug#964854: fixed in npm 6.14.7+ds-1
has caused the Debian Bug report #964854,
regarding npm: test failures in ppc64el and s390x
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.)


-- 
964854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: npm
Version: 6.14.6+ds-1
Severity: serious

Hello, looks like one test is failing on ppc64el and s390x.
Could you please have a look?

this on s390x
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/s390x/n/npm/20200711_092356_eb5fd@/log.gz
# Subtest: test/tap/legacy-platform-all.js
# Subtest: setup
1..0
ok 1 - setup # time=2.926ms

# Subtest: platform-all
not ok 1 - no error messages
  ---
  found: >
npm ERR! code EBADPLATFORM
  
npm ERR! notsup Unsupported platform for 
npm-test-platform-all@9.9.9-9: wanted

{"os":"darwin,linux,win32,solaris,haiku,sunos,freebsd,openbsd,netbsd","arch":"arm,arm64,mips,ia32,x64,sparc"}
(current: {"os":"linux","arch":"s390x"})
  
npm ERR! notsup Valid OS:   
darwin,linux,win32,solaris,haiku,sunos,freebsd,openbsd,netbsd
  
npm ERR! notsup Valid Arch:  arm,arm64,mips,ia32,x64,sparc
  
npm ERR! notsup Actual OS:   linux
  
npm ERR! notsup Actual Arch: s390x
  
  
npm ERR! A complete log of this run can be found in:
  
npm ERR!

/tmp/autopkgtest.TwzxSV/autopkgtest_tmp/smokeh0DzIy/test/npm_cache_legacy-platform-all/_logs/2020-07-11T09_18_58_795Z-debug.log
  wanted: ''
  compare: ===
  at:
line: 55
column: 7
file: test/tap/legacy-platform-all.js
type: global
function: installCheckAndTest
  stack: |
installCheckAndTest (test/tap/legacy-platform-all.js:55:7)
f (/usr/lib/nodejs/once/once.js:25:25)
ChildProcess. (test/common-tap.js:175:5)
  source: |
t.is(stderr, '', 'no error messages')
  ...

not ok 2 - install went ok
  ---
  found: 1
  wanted: 0
  compare: ===
  at:
line: 56
column: 7
file: test/tap/legacy-platform-all.js
type: global
function: installCheckAndTest
  stack: |
installCheckAndTest (test/tap/legacy-platform-all.js:56:7)
f (/usr/lib/nodejs/once/once.js:25:25)
ChildProcess. (test/common-tap.js:175:5)
  source: |
t.is(code, 0, 'install went ok')
  ...

1..2
# failed 2 of 2 tests
not ok 2 - platform-all # time=767.548ms

# Subtest: cleanup
1..0
ok 3 - cleanup # time=1.651ms

1..3
# failed 1 of 3 tests
# time=782.166ms
not ok 103 - test/tap/legacy-platform-all.js # time=1350.563ms


and this on ppc64el
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/ppc64el/n/npm/20200711_093200_7007f@/log.gz
# Subtest: test/tap/legacy-platform-all.js
# Subtest: setup
1..0
ok 1 - setup # time=4.916ms

# Subtest: platform-all
not ok 1 - no error messages
  ---
  found: >
npm ERR! code EBADPLATFORM
  
npm ERR! notsup Unsupported platform for 
npm-test-platform-all@9.9.9-9: wanted

{"os":"darwin,linux,win32,solaris,haiku,sunos,freebsd,openbsd,netbsd","arch":"arm,arm64,mips,ia32,x64,sparc"}
(current: {"os":"linux","arch":"ppc64"})
  
npm ERR! notsup Valid OS:   
darwin,linux,win32,solaris,haiku,sunos,freebsd,openbsd,netbsd
  
npm ERR! notsup Valid Arch:  arm,arm64,mips,ia32,x64,sparc
  
npm ERR! notsup Actual OS:   linux
  
npm ERR! notsup Actual Arch: ppc64
  
  
npm ERR! A complete log of this run can be found in:
  
npm ERR!

/tmp/autopkgtest.RvsIrP/autopkgtest_tmp/smokevhVLkX/test/npm_cache_legacy-platform-all/_logs/2020-07-11T09_24_22_560Z-debug.log
  wanted: ''
  compare: ===
  at:
line: 55
column: 7
  

Bug#968383: marked as done (interimap: fails to work with Dovecot v2.3.11: ERROR: 0 bytes read (got EOF))

[Jonas Smedegaard]

Quoting Guilhem Moulin (2020-08-14 12:53:54)
> On Fri, 14 Aug 2020 at 09:33:03 +, Debian Bug Tracking System wrote:
> >> All my 5 interimap profiles stopped working when security fix was applied
> >> for my local Dovecot install was applied.
> > 
> > False alarm: Turned out to be a change in dovecot configuration files 
> > incompatible with my accessing it via tunnel.
> > 
> > Revealed by manually running the underlying doveadm command.
> 
> Thanks for the update, Jonas!  Mind sharing what you had to change in
> Dovecot?  1:2.3.11.3+dfsg1-1 doesn't break the test suite, so maybe you
> have a setup it'd be worth having test covering for.

I have interimap config files all containing this:

[local]
type = tunnel
command = doveadm exec imap -o mail_location=maildir:~/Maildir/jones
null-stderr = YES


Normally, my wrapper script for all accounts look like this:

$ mymailsync 
debian_local: IMAP traffic (bytes): recv 9.12K sent 104
debian_remote: IMAP traffic (bytes): recv 9.34K sent 104
purism_local: IMAP traffic (bytes): recv 1.15K sent 104
purism_remote: IMAP traffic (bytes): recv 1.15K sent 212
jones_remote(INBOX): Updated flags ($HasNoAttachment \Seen) for UID 636246
jones_local(INBOX): Added 34 UID(s) 129072:129105 <- 636254:636287
jones_local: IMAP traffic (bytes): recv 21.84K sent 413.29K
jones_remote: IMAP traffic (bytes): recv 437.54K sent 355
hb_local(INBOX): Added 9 UID(s) 309233:309241 <- 299787:299795
hb_local: IMAP traffic (bytes): recv 5.88K sent 61.12K
hb_remote: IMAP traffic (bytes): recv 67.21K sent 266
Processed 43 total files in 1s (33 files/sec.).
Added 41 new messages to the database.


After the Dovecot update, it looked like this:

$ mymailsync 
debian_local: ERROR: 0 bytes read (got EOF)
debian_local: IMAP traffic (bytes): recv 0 sent 0
jones_local: ERROR: 0 bytes read (got EOF)
jones_local: IMAP traffic (bytes): recv 0 sent 0
purism_local: ERROR: 0 bytes read (got EOF)
purism_local: IMAP traffic (bytes): recv 0 sent 0
hb_local: ERROR: 0 bytes read (got EOF)
hb_local: IMAP traffic (bytes): recv 0 sent 0


After fumbling with "man interimap" looking for a "--verbose" option, 
and shouting out to you on irc, I tried running the inner command 
directly:

$ doveadm exec imap -o mail_location=maildir:~/Maildir/jones
doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf 
line 12: ssl_cert: Can't open file /etc/dovecot/private/dovecot.pem: Permission 
denied


Annoyingly, this failed as well:

$ doveadm exec imap -o mail_location=maildir:~/Maildir/jones -o ssl_cert= -o 
ssl_key=
doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf 
line 12: ssl_cert: Can't open file /etc/dovecot/private/dovecot.pem: Permission 
denied


Now it works, after aplying this patch:

--- /etc/dovecot/conf.d/10-ssl.conf.orig
+++ /etc/dovecot/conf.d/10-ssl.conf
@@ -9,8 +9,8 @@
 # dropping root privileges, so keep the key file unreadable by anyone but
 # root. Included doc/mkcert.sh can be used to easily generate self-signed
 # certificate, just make sure to update the domains in dovecot-openssl.cnf
-ssl_cert = http://dr.jones.dk/

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

signature.asc
Description: signature

Bug#966983: marked as done (python-skbio: FTBFS: dh_sphinxdoc: error: debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/search.html does not load searchindex.js)

[Debian Bug Tracking System]

Your message dated Fri, 14 Aug 2020 12:24:45 +
with message-id 
and subject line Bug#966983: fixed in sphinx 3.2.1-1
has caused the Debian Bug report #966983,
regarding python-skbio: FTBFS: dh_sphinxdoc: error: 
debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/search.html does 
not load searchindex.js
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.)


-- 
966983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-skbio
Version: 0.5.6-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_link --package=python-skbio-doc \
>   /usr/share/javascript/mathjax/MathJax.js \
>   /usr/share/doc/python-skbio-doc/html/_static/MathJax.js
> dh_sphinxdoc --package=python-skbio-doc
> dh_sphinxdoc: error: 
> debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/search.html does 
> not load searchindex.js
> make[1]: *** [debian/rules:41: override_dh_sphinxdoc] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/python-skbio_0.5.6-2_unstable.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 ---
Source: sphinx
Source-Version: 3.2.1-1
Done: Dmitry Shachnev 

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated sphinx 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: Fri, 14 Aug 2020 14:06:07 +0300
Source: sphinx
Architecture: source
Version: 3.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Dmitry Shachnev 
Closes: 966983
Changes:
 sphinx (3.2.1-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fixes crashes when documenting extension modules (closes: #966983).
Checksums-Sha1:
 24fd0ee1bca5d1ee9ea300b45cbe17d5424598cc 3471 sphinx_3.2.1-1.dsc
 00491c562965c8e9d5f14fe83eef9a2211fa5ea5 5970067 sphinx_3.2.1.orig.tar.gz
 d06da4946b5a6100eb4f028321721bf8414f0d70 833 sphinx_3.2.1.orig.tar.gz.asc
 3bfdf40b6b0c33542acc933af1480810e444db84 39088 sphinx_3.2.1-1.debian.tar.xz
 cdf58b92ee772d0d8aac813d49e5fa38ed200e29 5672 sphinx_3.2.1-1_source.buildinfo
Checksums-Sha256:
 b16de87786f760c7c1294d4fead8af6551e62d229f8a36c63080ff12ff59be44 3471 
sphinx_3.2.1-1.dsc
 321d6d9b16fa381a5306e5a0b76cd48ffbc588e6340059a729c6fdd66087e0e8 5970067 
sphinx_3.2.1.orig.tar.gz
 78efee330b77f8fce3aa967a999c47c85e5e6d49fde1644cbfecf0b1b7178bac 833 
sphinx_3.2.1.orig.tar.gz.asc
 9eda2bb3703cd3f8b347e9933cd8e56cb16a7d808e89c4e29c77b5da57a70e0f 39088 
sphinx_3.2.1-1.debian.tar.xz
 dfe97ffd1b6247c4f268b62bdffcd84f97cadf1df0970d9b99d5e7bf41101a1c 5672 
sphinx_3.2.1-1_source.buildinfo
Files:
 acf7a91461247c47d484f81a639792df 3471 python optional sphinx_3.2.1-1.dsc
 84aab02c279697e9414cbeed1c5c4b22 5970067 python optional 
sphinx_3.2.1.orig.tar.gz
 e9e8835e6f4c61631cbfae4dc7a741d8 833 python optional 
sphinx_3.2.1.orig.tar.gz.asc
 47faf656c37cbb20bccc8fd096086fae 39088 python optional 
sphinx_3.2.1-1.debian.tar.xz
 12c7b94bde6c9ae671ca649fa19cd200 5672 python optional 
sphinx_3.2.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAl82ek8THG1pdHlhNTdA
ZGViaWFuLm9yZwAKCRBmRiZbWGuDywclD/oCHWYGerPGRwETBTfAxaWxN/UJSW3Z
/Xyaua+pux1YllPA+FjR61bo5yjpl1hMr3xD/JkQuml5wMttZAf8LEBijrj2R/D7
w1r613s6+JaU/ooRXrHcfIYAsquIf8B7JhDKWEg0CD8djpDFPbn+LYsS2qbI2bHo
6sAiv8UGK41eD91M2Nj2NQ4CK2oklwVIm09xrX3scyYmPyc8EpuaeR71+CtoO1D

Bug#968149: mysql-router-dbgsym,mysql-server-core-8.0-dbgsym: file conflict due to shared build-id

[Robie Basak]

Thank you for the report.

On Sun, Aug 09, 2020 at 09:48:13PM +0200, Andreas Beckmann wrote:
> This is likely caused by the corresponding binary packages shipping
> identical binaries (or librariesi, ...) with different names.

Looks like this is because this file is shipped in both mysql-router
and mysql-server-core:

/usr/lib/mysql/private/libprotobuf-lite.so.*
/usr/lib/mysql-router/libprotobuf-lite.so.*


signature.asc
Description: PGP signature

Processed: Re: Bug#968394: gnome-shell: No UI option to switch between users even when there are multiple non-system user accounts

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libaccountsservice 0.6.55-1
Bug #968394 [gnome-shell,libaccountsservice0] gnome-shell: No UI option to 
switch between users even when there are multiple non-system user accounts
Bug reassigned from package 'gnome-shell,libaccountsservice0' to 
'libaccountsservice'.
Warning: Unknown package 'libaccountsservice'
Warning: Unknown package 'libaccountsservice'
No longer marked as found in versions gnome-shell/3.36.4-1 and 
accountsservice/0.6.55-1.
Warning: Unknown package 'libaccountsservice'
Warning: Unknown package 'libaccountsservice'
Ignoring request to alter fixed versions of bug #968394 to the same values 
previously set
Warning: Unknown package 'libaccountsservice'
Bug #968394 [libaccountsservice] gnome-shell: No UI option to switch between 
users even when there are multiple non-system user accounts
Warning: Unknown package 'libaccountsservice'
There is no source info for the package 'libaccountsservice' at version 
'0.6.55-1' with architecture ''
Unable to make a source version for version '0.6.55-1'
Marked as found in versions 0.6.55-1.
Warning: Unknown package 'libaccountsservice'
> affects -1 + gnome-shell
Bug #968394 [libaccountsservice] gnome-shell: No UI option to switch between 
users even when there are multiple non-system user accounts
Warning: Unknown package 'libaccountsservice'
Added indication that 968394 affects gnome-shell
Warning: Unknown package 'libaccountsservice'
> severity -1 serious
Bug #968394 [libaccountsservice] gnome-shell: No UI option to switch between 
users even when there are multiple non-system user accounts
Warning: Unknown package 'libaccountsservice'
Severity set to 'serious' from 'normal'
Warning: Unknown package 'libaccountsservice'
> tags -1 + pending
Bug #968394 [libaccountsservice] gnome-shell: No UI option to switch between 
users even when there are multiple non-system user accounts
Warning: Unknown package 'libaccountsservice'
Added tag(s) pending.
Warning: Unknown package 'libaccountsservice'

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

Bug#964908: tomcat9/9.0./37-3 in buster backports

[Adrian Heath]

Do you know when this fix will appear in the Buster backports repository?

Thank you in advance

Processed: reassign 968394 to libaccountsservice0

[Debian Bug Tracking System]

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

> reassign 968394 libaccountsservice0 0.6.55-1
Bug #968394 [libaccountsservice] gnome-shell: No UI option to switch between 
users even when there are multiple non-system user accounts
Warning: Unknown package 'libaccountsservice'
Bug reassigned from package 'libaccountsservice' to 'libaccountsservice0'.
No longer marked as found in versions 0.6.55-1.
Ignoring request to alter fixed versions of bug #968394 to the same values 
previously set
Bug #968394 [libaccountsservice0] gnome-shell: No UI option to switch between 
users even when there are multiple non-system user accounts
Marked as found in versions accountsservice/0.6.55-1.
> thanks
Stopping processing here.

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

Bug#966301: guile OOM test failures on ppc64el

[Matthias Klose]

On 8/14/20 11:33 AM, Matthias Klose wrote:
> I'm now NMUing both guile-2.2 and guile-3.0 to just ignore the test results on
> ppc64el, without closing the bug reports.  It's blocking the gcc-10 migration 
> to
> testing.

now, the NMUs fail with the same OOM error on armhf (3.0) and armhf/i386 (2.2)
as well... Maybe just don't run the OOM tests, instead of ignoring the test 
results?

Bug#968399: pyxdg ftbfs, test failure

[Matthias Klose]

Package: src:pyxdg
Version: 0.26-3
Severity: serious
Tags: sid bullseye

seen in unstable, in the build, and in the autopkg tests:

[...]
==
ERROR: test_rule_from_node (test-menu-rules.RulesTest)
--
Traceback (most recent call last):
  File
"/packages/tmp/pyxdg-0.26/.pybuild/cpython3_3.8_xdg/build/test/test-menu-rules.py",
line 166, in test_rule_from_node
rule = parser.parse_rule(root)
  File "/packages/tmp/pyxdg-0.26/.pybuild/cpython3_3.8_xdg/build/xdg/Menu.py",
line 768, in parse_rule
return Rule(type, tree)
  File "/packages/tmp/pyxdg-0.26/.pybuild/cpython3_3.8_xdg/build/xdg/Menu.py",
line 421, in __init__
self.code = compile(self.expression, '', 'eval')
ValueError: Name node can't be used with 'False' constant

--
Ran 55 tests in 2.178s

FAILED (errors=1)
E: pybuild pybuild:352: test: plugin distutils failed with: exit code=1: cd
/packages/tmp/pyxdg-0.26/.pybuild/cpython3_3.8_xdg/build; python3.8 -m nose -v 
test
dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.8
returned exit code 13
make: *** [debian/rules:7: build] Error 25

Bug#968383: marked as done (interimap: fails to work with Dovecot v2.3.11: ERROR: 0 bytes read (got EOF))

[Guilhem Moulin]

On Fri, 14 Aug 2020 at 13:57:32 +0200, Jonas Smedegaard wrote:
> and shouting out to you on irc,

Oh, if that was recently I'm afraid I missed it.

> Now it works, after aplying this patch:
> 
> --- /etc/dovecot/conf.d/10-ssl.conf.orig
> +++ /etc/dovecot/conf.d/10-ssl.conf
> @@ -9,8 +9,8 @@
> # dropping root privileges, so keep the key file unreadable by anyone but
> # root. Included doc/mkcert.sh can be used to easily generate self-signed
> # certificate, just make sure to update the domains in dovecot-openssl.cnf
> -ssl_cert =  -ssl_key =  +#ssl_cert =  +#ssl_key =  .
> # If key file is password protected, give the password here. Alternatively
> # give it when starting dovecot with -p parameter. Since this file is often

I see, thanks.  Seems a regression from Dovecot upstream, which was also
reported at https://dovecot.org/pipermail/dovecot/2020-August/119642.html .

The test suite didn't catch this since we don't run the IMAPd with the
stock configuration (intentionally — don't want to depend too much on a
specific server), and instead run `doveadm -c /path/to/dovecot.conf exec
imap` as tunnel command.  That's also the workflow advertised at
/usr/share/doc/interimap/getting-started.md.gz.

I'll see if upstream fixes the regression, and add a note to the
aforementioned document otherwise.  (Explicitly setting ‘ssl=no’ doesn't
seem to have an effect anymore, so that document should probably be
revisited anyway.)

-- 
Guilhem.


signature.asc
Description: PGP signature

Processed: tagging 966020

[Debian Bug Tracking System]

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

> # https://github.com/jekyll/jekyll/releases/tag/v3.9.0
> tags 966020 + patch fixed-upstream
Bug #966020 [jekyll] jekyll: ftbfs with ruby-kramdown 2.x in experimental
Ignoring request to alter tags of bug #966020 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: tagging 966020

[Debian Bug Tracking System]

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

> # 
> https://github.com/jekyll/jekyll/commit/575f4b66de0326386f6185fa9e7f089c1d2e22e4
> tags 966020 + patch fixed-upstream
Bug #966020 [jekyll] jekyll: ftbfs with ruby-kramdown 2.x in experimental
Added tag(s) patch and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#966020: Fixed in 3.9.0

[Daniel Leidert]

This has been fixed upstream by version 3.9.0
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966020

Uploading this will also fix #961194.

Regards, Daniel
-- 
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

If you like my work consider sponsoring me via
https://www.patreon.com/join/dleidert


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

Bug#968383: marked as done (interimap: fails to work with Dovecot v2.3.11: ERROR: 0 bytes read (got EOF))

[Jonas Smedegaard]

Quoting Guilhem Moulin (2020-08-14 17:28:04)
> On Fri, 14 Aug 2020 at 13:57:32 +0200, Jonas Smedegaard wrote:
> > and shouting out to you on irc,
> 
> Oh, if that was recently I'm afraid I missed it.

It was earlier today, and you even responded.  Maybe "shouting" is too 
strong word... :-)


> > Now it works, after aplying this patch:
> > 
> > --- /etc/dovecot/conf.d/10-ssl.conf.orig
> > +++ /etc/dovecot/conf.d/10-ssl.conf
> > @@ -9,8 +9,8 @@
> > # dropping root privileges, so keep the key file unreadable by anyone but
> > # root. Included doc/mkcert.sh can be used to easily generate self-signed
> > # certificate, just make sure to update the domains in dovecot-openssl.cnf
> > -ssl_cert =  > -ssl_key =  > +#ssl_cert =  > +#ssl_key =  > .
> > # If key file is password protected, give the password here. Alternatively
> > # give it when starting dovecot with -p parameter. Since this file is often
> 
> I see, thanks.  Seems a regression from Dovecot upstream, which was also
> reported at https://dovecot.org/pipermail/dovecot/2020-August/119642.html .
> 
> The test suite didn't catch this since we don't run the IMAPd with the
> stock configuration (intentionally — don't want to depend too much on a
> specific server), and instead run `doveadm -c /path/to/dovecot.conf exec
> imap` as tunnel command.  That's also the workflow advertised at
> /usr/share/doc/interimap/getting-started.md.gz.

Thanks - I saw it earlier but prefer relying on Debian default settings 
most possible.


 - Jonas

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

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

signature.asc
Description: signature

Bug#968372: sylpheed: crash on startup

[Bernhard Übelacker]

Dear Maintainer,
I could reproduce it inside a i386 VM and found the crash
happens in [1], when it tries to dereference the "state".

This state is retrieved from the renderer of type _PangoRendererPrivate.


I tried to follow where this state is last set and found
this memory is last written in location [2].

But here this memory is used as _GdkPangoRendererPrivate,
which looks quite different.


Kind regards,
Bernhard



[1]
(rr) bt
#0  0xb7391ebf in handle_line_state_change 
(part=PANGO_RENDER_PART_OVERLINE, renderer=0x10470c0) at 
../pango/pango-renderer.c:315
#1  pango_renderer_part_changed (renderer=0x10470c0, 
part=PANGO_RENDER_PART_OVERLINE) at ../pango/pango-renderer.c:1414
#2  0xb7392194 in pango_renderer_set_alpha (renderer=0x10470c0, 
part=PANGO_RENDER_PART_OVERLINE, alpha=0) at ../pango/pango-renderer.c:1357
#3  0xb7392335 in pango_renderer_default_prepare_run (renderer=0x10470c0, 
run=0xf55a98) at ../pango/pango-renderer.c:1525
#4  0xb756b7cd in gdk_pango_renderer_prepare_run (renderer=0x10470c0, 
run=0xf55a98) at ../../../../gdk/gdkpango.c:456
#5  0xb73925f9 in pango_renderer_prepare_run (run=0xf55a98, 
renderer=0x10470c0) at ../pango/pango-renderer.c:1435
#6  pango_renderer_draw_layout_line (renderer=0x10470c0, line=0xf50e08, 
x=34816, y=51200) at ../pango/pango-renderer.c:611
...

(rr) list
296 handle_line_state_change (PangoRenderer  *renderer,
297   PangoRenderPart part)
298 {
299   LineState *state = renderer->priv->line_state;
...
314
315   if (part == PANGO_RENDER_PART_OVERLINE &&
316   state->overline != PANGO_OVERLINE_NONE)
317 {


https://sources.debian.org/src/pango1.0/1.46.0-1/pango/pango-renderer.c/#L315


[2]
(rr) bt
#0  gdk_pango_renderer_prepare_run (renderer=0x10470c0, run=0xf55a98) at 
../../../../gdk/gdkpango.c:443
#1  0xb73925f9 in pango_renderer_prepare_run (run=0xf55a98, 
renderer=0x10470c0) at ../pango/pango-renderer.c:1435
#2  pango_renderer_draw_layout_line (renderer=0x10470c0, line=0xf50e08, 
x=34816, y=51200) at ../pango/pango-renderer.c:611
#3  0xb739301d in pango_renderer_draw_layout (renderer=0x10470c0, 
layout=0xf379f0, x=34816, y=37888) at ../pango/pango-renderer.c:197
...

(rr) list
441   if (embossed != gdk_renderer->priv->embossed)
442 {
443   gdk_renderer->priv->embossed = embossed;
444   changed = TRUE;
445 }

https://sources.debian.org/src/gtk+2.0/2.24.32-4/gdk/gdkpango.c/#L443

# Unstable i386 qemu VM 2020-08-14

apt update
apt dist-uprade


apt install systemd-coredump sddm xserver-xorg openbox xterm gdb git sylpheed 
sylpheed-dbgsym libgtk2.0-0-dbgsym libglib2.0-0-dbgsym libpango-1.0-0-dbgsym
apt build-dep rr


echo 1 > /proc/sys/kernel/perf_event_paranoid




mkdir /home/benutzer/source/libpango-1.0-0/orig -p
cd/home/benutzer/source/libpango-1.0-0/orig
apt source libpango-1.0-0
cd

mkdir /home/benutzer/source/libgtk2.0-0/orig -p
cd/home/benutzer/source/libgtk2.0-0/orig
apt source libgtk2.0-0
cd





$ export DISPLAY=:0
$ sylpheed 
Speicherzugriffsfehler (Speicherabzug geschrieben)


# dmesg
...
[   29.789450] sylpheed[992]: segfault at 2d ip b73e0ebf sp bf890760 error 4 in 
libpango-1.0.so.0.4600.0[b73bd000+29000]
[   29.789458] Code: c4 10 83 c4 1c 5b 5e 5f 5d c3 90 8b 4e 18 85 c9 7e 79 8b 
46 20 8b 78 44 85 ff 74 4f 83 fd 02 74 7a 83 fd 04 0f 85 b1 00 00 00 <8b> 47 2c 
89 44 24 08 85 c0 74 36 8b 4f 40 8b 57 30 c7 47 2c 00 00


# coredumpctl list
TIMEPID   UID   GID SIG COREFILE  EXE
Fri 2020-08-14 18:33:29 CEST992  1000  1000  11 present   /usr/bin/sylpheed

# coredumpctl gdb 992
   PID: 992 (sylpheed)
   UID: 1000 (benutzer)
   GID: 1000 (benutzer)
Signal: 11 (SEGV)
 Timestamp: Fri 2020-08-14 18:33:29 CEST (2min 10s ago)
  Command Line: sylpheed
Executable: /usr/bin/sylpheed
 Control Group: /user.slice/user-1000.slice/session-6.scope
  Unit: session-6.scope
 Slice: user-1000.slice
   Session: 6
 Owner UID: 1000 (benutzer)
   Boot ID: 4c238d8aaaba40d19b8c886c81502ce0
Machine ID: 45f49504b47f4e5690bc479adf67aa5b
  Hostname: debian
   Storage: 
/var/lib/systemd/coredump/core.sylpheed.1000.4c238d8aaaba40d19b8c886c81502ce0.992.1597422809.zst
   Message: Process 992 (sylpheed) of user 1000 dumped core.

Stack trace of thread 992:
#0  0xb73e0ebf pango_renderer_part_changed 
(libpango-1.0.so.0 + 0x2debf)
#1  0xb73e1194 pango_renderer_set_alpha 
(libpango-1.0.so.0 + 0x2e194)
#2  0xb73e1335 n/a (libpango-1.0.so.0 + 0x2e335)
#3  0xb75ba7cd n/a (libgdk-x11-2.0.so.0 + 0x247cd)
#4  0xb73e15f9 pango_renderer_draw_layout_line 
(libpango-1.0.so.0 + 0x2e5f9)

Bug#968403: numbers.test fails on i386

[Matthias Klose]

Package: src:guile-3.0
Version: 3.0.4-1
Severity: serious
Tags: sid bullseye

only seen on i386, not on other architectures.

[...]
Running numbers.test
FAIL: numbers.test: Number-theoretic division: euclidean/: mixed types: (130.0 
10/7)
FAIL: numbers.test: Number-theoretic division: euclidean/: mixed types: (130.0
-10/7)
FAIL: numbers.test: Number-theoretic division: floor/: mixed types: (130.0 10/7)
FAIL: numbers.test: Number-theoretic division: floor/: mixed types: (-130.0 
-10/7)
FAIL: numbers.test: Number-theoretic division: ceiling/: mixed types: (130.0 
-10/7)
FAIL: numbers.test: Number-theoretic division: ceiling/: mixed types: (-130.0 
10/7)
FAIL: numbers.test: Number-theoretic division: truncate/: mixed types: (130.0 
10/7)
FAIL: numbers.test: Number-theoretic division: truncate/: mixed types: (130.0 
-10/7)
FAIL: numbers.test: Number-theoretic division: truncate/: mixed types: (-130.0 
10/7)
FAIL: numbers.test: Number-theoretic division: truncate/: mixed types: (-130.0
-10/7)

Bug#968383: Info received and FILED only (Bug#968383: marked as done (interimap: fails to work with Dovecot v2.3.11: ERROR: 0 bytes read (got EOF)))

[Jonas Smedegaard]

Quoting Debian Bug Tracking System (2020-08-14 18:45:04)
> Thank you for the additional information you have supplied regarding
> this Bug report.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message has not been forwarded to the package maintainers or
> other interested parties; you should ensure that the developers are
> aware of the problem you have entered into the system - preferably
> quoting the Bug reference number, #968383.
> 
> If you wish to submit further information on this problem, please
> send it to 968383-qu...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.

Arrgh - I _know_ who you are, and that there are both a Guillem and a 
Guilhem in Debian - I know you both.

...but yes, indeed, I flipped around who is spelled how.  And indeed, I 
just shouted at and later had a nice conversation with Guillem - without 
realizing throughout our conversation that I was talking to the other 
one...

Sorry!

(I imagine you experience that from time to time...)

 - Jonas

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

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

signature.asc
Description: signature

Bug#968383: Info received and FILED only (Bug#968383: marked as done (interimap: fails to work with Dovecot v2.3.11: ERROR: 0 bytes read (got EOF)))

[Guilhem Moulin]

On Fri, 14 Aug 2020 at 19:54:31 +0200, Jonas Smedegaard wrote:
> Arrgh - I _know_ who you are, and that there are both a Guillem and a 
> Guilhem in Debian - I know you both.
> 
> ...but yes, indeed, I flipped around who is spelled how.  And indeed, I 
> just shouted at and later had a nice conversation with Guillem - without 
> realizing throughout our conversation that I was talking to the other 
> one...

Aha :-D

> (I imagine you experience that from time to time...)

Indeed!  And folks get confused with username auto-completion when we
both show up in the same room ;-)

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#968394: marked as done (gnome-shell: No UI option to switch between users even when there are multiple non-system user accounts)

[Debian Bug Tracking System]

Your message dated Fri, 14 Aug 2020 18:18:28 +
with message-id 
and subject line Bug#968394: fixed in accountsservice 0.6.55-3
has caused the Debian Bug report #968394,
regarding gnome-shell: No UI option to switch between users even when there are 
multiple non-system user accounts
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.)


-- 
968394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell
Version: 3.36.4-1
Severity: normal
X-Debbugs-Cc: chandru...@gmail.com

Dear Maintainer,

There is no option in the status menu to switch to another user on the
system. There is no option to login as another user on the lock screen
either.

There are multiple non-system user accounts on the machine and I'm
logged into the laptop locally (not a remote connection). In such a
scenario, I expect an option to switch between users without having to
log out of the current user's session.

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

Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
ii  evolution-data-server3.36.4-1
ii  gir1.2-accountsservice-1.0   0.6.55-2
ii  gir1.2-atspi-2.0 2.36.0-3
ii  gir1.2-freedesktop   1.64.1-1
ii  gir1.2-gcr-3 3.36.0-2
ii  gir1.2-gdesktopenums-3.0 3.36.1-1
ii  gir1.2-gdm-1.0   3.36.2-1
ii  gir1.2-geoclue-2.0   2.5.6-1
ii  gir1.2-glib-2.0  1.64.1-1
ii  gir1.2-gnomebluetooth-1.03.34.1-1
ii  gir1.2-gnomedesktop-3.0  3.36.4-1
ii  gir1.2-gtk-3.0   3.24.20-1
ii  gir1.2-gweather-3.0  3.36.0-1
ii  gir1.2-ibus-1.0  1.5.22-5
ii  gir1.2-mutter-6  3.36.4-1
ii  gir1.2-nm-1.01.26.0-1
ii  gir1.2-nma-1.0   1.8.30-1
ii  gir1.2-pango-1.0 1.44.7-4
ii  gir1.2-polkit-1.00.105-29
ii  gir1.2-rsvg-2.0  2.48.7-1
ii  gir1.2-soup-2.4  2.70.0-1
ii  gir1.2-upowerglib-1.00.99.11-2
ii  gjs  1.64.3-1
ii  gnome-backgrounds3.36.0-1
ii  gnome-settings-daemon3.36.1-1
ii  gnome-shell-common   3.36.4-1
ii  gsettings-desktop-schemas3.36.1-1
ii  libatk-bridge2.0-0   2.34.1-3
ii  libatk1.0-0  2.36.0-2
ii  libc62.31-3
ii  libcairo21.16.0-4
ii  libecal-2.0-13.36.4-1
ii  libedataserver-1.2-243.36.4-1
ii  libgcr-base-3-1  3.36.0-2
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-5
ii  libgirepository-1.0-11.64.1-1
ii  libgjs0g 1.64.3-1
ii  libgles2 1.3.2-1
ii  libglib2.0-0 2.64.4-1
ii  libglib2.0-bin   2.64.4-1
ii  libgnome-autoar-0-0  0.2.4-2
ii  libgnome-desktop-3-193.36.4-1
ii  libgraphene-1.0-01.10.2-1
ii  libgstreamer1.0-01.16.2-2
ii  libgtk-3-0   3.24.20-1
ii  libical3 3.0.8-2
ii  libjson-glib-1.0-0   1.4.4-2
ii  libmutter-6-03.36.4-1
ii  libnm0   1.26.0-1
ii  libpango-1.0-0   1.44.7-4
ii  libpangocairo-1.0-0  1.44.7-4
ii  libpolkit-agent-1-0  0.105-29
ii  libpolkit-gobject-1-00.105-29
ii  libpulse-mainloop-glib0  13.0-5
ii  libpulse0 

Bug#957298: marked as done (gom: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Fri, 14 Aug 2020 19:03:37 +
with message-id 
and subject line Bug#957298: fixed in gom 0.30.2-9.1
has caused the Debian Bug report #957298,
regarding gom: ftbfs with GCC-10
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.)


-- 
957298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gom
Version: 0.30.2-9
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/gom_0.30.2-9_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
config.status: creating src/Makefile
config.status: creating src/gomconfig
config.status: creating src/gom.1
config.status: creating src/gomconfig.8
config.status: creating config.h
config.status: executing depfiles commands
   dh_auto_build
make -j1
make[1]: Entering directory '/<>'
make  all-recursive
make[2]: Entering directory '/<>'
Making all in src
make[3]: Entering directory '/<>/src'
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c gom_info.c
In file included from /usr/include/string.h:495,
 from gom.h:40,
 from gom_info.c:28:
In function ‘strncat’,
inlined from ‘gom_info’ at gom_info.c:133:3:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:136:10: warning: 
‘__builtin___strncat_chk’ specified bound 255 equals destination size 
[-Wstringop-overflow=]
  136 |   return __builtin___strncat_chk (__dest, __src, __len, __bos (__dest));
  |  ^~
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c gom_driver_oss.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c gom_mixer.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c gom_gomii.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c gom_file.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c gom_action.c
gom_action.c: In function ‘gom_action_license’:
gom_action.c:380:23: warning: macro "__DATE__" might prevent reproducible 
builds [-Wdate-time]
  380 |"  Compile time: " __DATE__ " " __TIME__,
  |   ^~~~
gom_action.c:380:36: warning: macro "__TIME__" might prevent reproducible 
builds [-Wdate-time]
  380 |"  Compile time: " __DATE__ " " __TIME__,
  |^~~~
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c gom_iface_c.c
gom_iface_c.c: In function ‘gom_iface_c_question’:
gom_iface_c.c:59:2: warning: ignoring return value of ‘scanf’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
   59 |  scanf("%c", &answer);
  |  ^~~~
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-We

Processed: Re: Bug#966900: range-v3: FTBFS: cc1plus: error: command-line option ‘-Wno-missing-prototypes’ is valid for C/ObjC but not for C++ [-Werror]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #966900 [src:range-v3] range-v3: FTBFS: cc1plus: error: command-line option 
‘-Wno-missing-prototypes’ is valid for C/ObjC but not for C++ [-Werror]
Added tag(s) help.

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

Bug#968410: python3-setuptools: ModuleNotFoundError: No module named '_distutils_hack'

[Christian Kastner]

Package: python3-setuptools
Version: 49.3.1-1
Severity: grave
Justification: Package is unusable

The most recent upload broke something badly, setuptools can no longer
be imported:

$ python3 -c 'import setuptools'
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 8, in 

import _distutils_hack.override  # noqa: F401
ModuleNotFoundError: No module named '_distutils_hack'


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

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

Versions of packages python3-setuptools depends on:
ii  python33.8.2-3
ii  python3-distutils  3.8.5-1
ii  python3-pkg-resources  49.3.1-1

python3-setuptools recommends no packages.

Versions of packages python3-setuptools suggests:
pn  python-setuptools-doc  

-- debconf-show failed

Bug#957010: marked as done (artha: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Fri, 14 Aug 2020 21:05:06 +
with message-id 
and subject line Bug#957010: fixed in artha 1.0.5-1
has caused the Debian Bug report #957010,
regarding artha: ftbfs with GCC-10
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.)


-- 
957010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:artha
Version: 1.0.3-3
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/artha_1.0.3-3_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
checking for uint16_t... yes
checking for uint8_t... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating data/Makefile
config.status: creating src/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
configure: WARNING: unrecognized options: --disable-maintainer-mode

Artha is now configured!

  Installation directory:   /usr

  To build and install Artha:

make
make install (root previlages required)

  Once installed, type `artha` to run.

Refer INSTALL file for further details.

   dh_auto_build
make -j4
make[1]: Entering directory '/<>'
make  all-recursive
make[2]: Entering directory '/<>'
Making all in data
make[3]: Entering directory '/<>/data'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<>/data'
Making all in src
make[3]: Entering directory '/<>/src'
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra 
-std=c99 -pedantic -Wno-unused-parameter -fstrict-aliasing 
-Wno-missing-field-initializers -pthread -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/fribidi -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DGTK_DISABLE_DEPRECATED=1 
-DGDK_DISABLE_DEPRECATED=1 -DGDK_PIXBUF_DISABLE_DEPRECATED=1 
-DG_DISABLE_DEPRECATED=1 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-securi
 ty -c -o mod_notify.o mod_notify.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra 
-std=c99 -pedantic -Wno-unused-parameter -fstrict-aliasing 
-Wno-missing-field-initializers -pthread -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/fribidi -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DGTK_DISABLE_DEPRECATED=1 
-DGDK_DISABLE_DEPRECATED=1 -DGDK_PIXBUF_DISABLE_DEPRECATED=1 
-DG_DISABLE_DEPRECATED=1 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/g

Bug#966515: scons: Some upstream sources are missing

[Ben Hutchings]

On Thu, 2020-07-30 at 06:17 -0700, Bill Deegan wrote:
> Ok
> 
> Can you check the 4.0.1 tarballs and see if they provide in each what you
> need?
> We completely reimplemented packaging in 4.0.0

I can't find a scons-src tarball for 4.0.1.

Ben.

-- 
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
 Manchester, M1 2HF, United Kingdom

Bug#968413: failes to build on ppc64el with binutils 2.35

[Thadeu Lima de Souza Cascardo]

Source: oss4
Version: 4.2-build2017-1
Severity: serious
Tags: patch

/tmp/ccGBTa5R.s: Assembler messages:
/tmp/ccGBTa5R.s: Error: invalid attempt to declare external version name as 
default in symbol
`.snd_pcm_hw_params_set_rate_near@@ALSA_0.9.0rc4'

oss4 started failing to build on ppc64el with binutils 2.35 because it
was setting an undefined symbol as the default version. It was doing that
in order to support dot-symbols/function descriptors on ppc, which is not
used by userspace ABI since a while, and not supported with ABIv2, the one
used by ppc64el, at all.

As this header comes from alsa, I looked at its history and, for different
reasons, it has been fixed there already. So, sending a patch based on that one
here to fix the build.

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

Kernel: Linux 5.7.0-1-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#966515: marked as done (scons: Some upstream sources are missing)

[Debian Bug Tracking System]

Your message dated Fri, 14 Aug 2020 22:05:13 +
with message-id 
and subject line Bug#966515: fixed in scons 3.1.2+dfsg-0.1
has caused the Debian Bug report #966515,
regarding scons: Some upstream sources are missing
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.)


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

Dear Maintainer,

The current source package uses the 'production' tarballs
(scons-.tar.gz) as the orig tarball, whereas the upstream
source tarballs are released as scons-src-.tar.gz.

The 'production' tarballs contain many generated or preprocessed files.
In particular, the manual pages there are generated from the doc/man/
subdirectory of the upstream source, which is *not* included in the
production tarballs.

Ben.

-- System Information:
Debian Release: 10.4
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, arm64

Kernel: Linux 4.19.0-9-amd64 (SMP w/2 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

-- 
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
 Manchester, M1 2HF, United Kingdom
--- End Message ---
--- Begin Message ---
Source: scons
Source-Version: 3.1.2+dfsg-0.1
Done: Ben Hutchings 

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated scons 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: Fri, 14 Aug 2020 22:34:32 +0100
Source: scons
Architecture: source
Version: 3.1.2+dfsg-0.1
Distribution: unstable
Urgency: medium
Maintainer: Jörg Frings-Fürst 
Changed-By: Ben Hutchings 
Closes: 966515
Changes:
 scons (3.1.2+dfsg-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Use full upstream source tarball instead of 'production' tarball as
 upstream source (Closes: #966515):
 - debian/watch: Change URL regex
 - debian/copyright: Exclude minified jQuery library
 - debian/control: Build-Depend on fop and python3-lxml
 - debian/docs, debian/manpages, debian/patches/*.patch: Adjust filenames
 - debian/patches/0600-manpage-spelling.patch: Rewrite to apply to source
   files
 - debian/rules: Rewrite to use bootstrap.py
   * docbook: lxml: Fix man-page generation
   * debian/copyright: Add myself
Checksums-Sha1:
 21ec93b1cb966f0bbefa983fbe6ad83670c3ce50 1936 scons_3.1.2+dfsg-0.1.dsc
 dcb58741ca21c989d369a064be8cfb1b74bb 2898396 scons_3.1.2+dfsg.orig.tar.xz
 50a2d4c7d67961ff6abaecd098a26ae76655ea6b 14452 
scons_3.1.2+dfsg-0.1.debian.tar.xz
 d22250fca5b75a56edf1c76cb17f8818b452a63d 6443 
scons_3.1.2+dfsg-0.1_source.buildinfo
Checksums-Sha256:
 1b6cfa832fbcfdee0d1b650eccb30b8283e97904bb1dcea1cf5038731a00a8f9 1936 
scons_3.1.2+dfsg-0.1.dsc
 817121e00ff191773d96996e288cef37099e6155161b0e547bec3f3b0edd7f63 2898396 
scons_3.1.2+dfsg.orig.tar.xz
 6d5668ce367ad084a5a9a8edd641da8b9cc5d421e073dd8f504c67baf28c67ad 14452 
scons_3.1.2+dfsg-0.1.debian.tar.xz
 104153f93d2fcf70c5012df46a9ed5ab5f807c398b6c71accd57ccb306e2c5a4 6443 
scons_3.1.2+dfsg-0.1_source.buildinfo
Files:
 c722b3986421de1824f073b53900f981 1936 devel optional scons_3.1.2+dfsg-0.1.dsc
 e9aa69f482bd7870508b312ba3adaa76 2898396 devel optional 
scons_3.1.2+dfsg.orig.tar.xz
 cef9492550f4472b6f7d4632386647ff 14452 devel optional 
scons_3.1.2+dfsg-0.1.debian.tar.xz
 224b0a461879494c6b69ed0fb27bfb77 6443 devel optional 
scons_3.1.2+dfsg-0.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAl83BqoACgkQ57/I7JWG
EQnmfg//XndDxCGR9+8iN81qSDoog7dXDhjt8L2oo3n6dlXeV7zgMdg+o1OkXnNW
ha89QFebaRxu1WoXJnAih5N

Bug#968413: failes to build on ppc64el with binutils 2.35

[Thadeu Lima de Souza Cascardo]

Source: oss4
Followup-For: Bug #968413

Patch is attached.

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

Kernel: Linux 5.7.0-1-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru oss4-4.2-build2017/debian/changelog 
oss4-4.2-build2017/debian/changelog
--- oss4-4.2-build2017/debian/changelog 2019-01-08 20:51:07.0 -0200
+++ oss4-4.2-build2017/debian/changelog 2020-08-14 19:03:06.0 -0300
@@ -1,3 +1,10 @@
+oss4 (4.2-build2017-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix build on ppc64el with binutils 2.35 (Closes: #968413)
+
+ -- Thadeu Lima de Souza Cascardo   Fri, 14 Aug 2020 
19:03:06 -0300
+
 oss4 (4.2-build2017-1) unstable; urgency=low
 
   [ Sébastien Noel ]
diff -Nru 
oss4-4.2-build2017/debian/patches/libsalsa_drop_ppc64_specific_workaround_for_versioned_symbols.patch
 
oss4-4.2-build2017/debian/patches/libsalsa_drop_ppc64_specific_workaround_for_versioned_symbols.patch
--- 
oss4-4.2-build2017/debian/patches/libsalsa_drop_ppc64_specific_workaround_for_versioned_symbols.patch
   1969-12-31 21:00:00.0 -0300
+++ 
oss4-4.2-build2017/debian/patches/libsalsa_drop_ppc64_specific_workaround_for_versioned_symbols.patch
   2020-08-14 18:44:27.0 -0300
@@ -0,0 +1,54 @@
+Description: Drop ppc64-specific workaround for versioned symbols
+ Based on a patch by Breno Leitao applied to the original file from
+ alsa-lib.
+ oss4 started failing to build on ppc64el with binutils 2.35 because it
+ was setting an undefined symbol as the default version. It was doing that
+ in order to support dot-symbols/function descriptors on ppc, which is not
+ used by userspace ABI since a while, and not supported with ABIv2, the one
+ used by ppc64el, at all.
+Author: Thadeu Lima de Souza Cascardo 
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/1891565
+Last-Update: 2020-08-14
+---
+Index: oss4-4.2-build2010/lib/libsalsa/alsa-symbols.h
+===
+--- oss4-4.2-build2010.orig/lib/libsalsa/alsa-symbols.h
 oss4-4.2-build2010/lib/libsalsa/alsa-symbols.h
+@@ -29,19 +29,10 @@
+ #define INTERNAL_CONCAT2_2(Pre, Post) Pre##Post
+ #define INTERNAL(Name) INTERNAL_CONCAT2_2(__, Name)
+ 
+-#ifdef __powerpc64__
+-# define symbol_version(real, name, version)  \
+-  __asm__ (".symver " #real "," #name "@" #version);  \
+-  __asm__ (".symver ." #real ",." #name "@" #version)
+-# define default_symbol_version(real, name, version)  \
+-  __asm__ (".symver " #real "," #name "@@" #version); \
+-  __asm__ (".symver ." #real ",." #name "@@" #version)
+-#else
+ # define symbol_version(real, name, version) \
+   __asm__ (".symver " #real "," #name "@" #version)
+ # define default_symbol_version(real, name, version) \
+   __asm__ (".symver " #real "," #name "@@" #version)
+-#endif
+ 
+ #ifdef USE_VERSIONED_SYMBOLS
+ #define use_symbol_version(real, name, version) \
+@@ -50,17 +41,9 @@
+   default_symbol_version(real, name, version)
+ #else
+ #define use_symbol_version(real, name, version)   /* nothing */
+-#ifdef __powerpc64__
+-#define use_default_symbol_version(real, name, version) \
+-  __asm__ (".weak " #name);   \
+-  __asm__ (".weak ." #name);  \
+-  __asm__ (".set " #name "," #real);  \
+-  __asm__ (".set ." #name ",." #real)
+-#else
+ #define use_default_symbol_version(real, name, version) \
+   __asm__ (".weak " #name); \
+   __asm__ (".set " #name "," #real)
+ #endif
+-#endif
+ 
+ #endif /* __ALSA_SYMBOLS_H */
diff -Nru oss4-4.2-build2017/debian/patches/series 
oss4-4.2-build2017/debian/patches/series
--- oss4-4.2-build2017/debian/patches/series2019-01-08 19:48:00.0 
-0200
+++ oss4-4.2-build2017/debian/patches/series2020-08-14 18:44:34.0 
-0300
@@ -20,3 +20,4 @@
 502_linux_io.patch
 reproducible-build.patch
 503_glibc_2.28.patch
+libsalsa_drop_ppc64_specific_workaround_for_versioned_symbols.patch

Bug#968279: marked as done (rust-gdb: ships /usr/share/rust-lldb/rust_types.py)

[Debian Bug Tracking System]

Your message dated Fri, 14 Aug 2020 23:05:54 +
with message-id 
and subject line Bug#968279: fixed in rustc 1.46.0~beta.2+dfsg1-1~exp5
has caused the Debian Bug report #968279,
regarding rust-gdb: ships /usr/share/rust-lldb/rust_types.py
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.)


-- 
968279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968279
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rust-gdb
Version: 1.46.0~beta.2+dfsg1-1~exp4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package rust-lldb.
  Preparing to unpack .../28-rust-lldb_1.46.0~beta.2+dfsg1-1~exp4_all.deb ...
  Unpacking rust-lldb (1.46.0~beta.2+dfsg1-1~exp4) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-gMmkNG/28-rust-lldb_1.46.0~beta.2+dfsg1-1~exp4_all.deb 
(--unpack):
   trying to overwrite '/usr/share/rust-lldb/rust_types.py', which is also in 
package rust-gdb 1.46.0~beta.2+dfsg1-1~exp4
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-gMmkNG/28-rust-lldb_1.46.0~beta.2+dfsg1-1~exp4_all.deb

The -lldb path seems to be wrong for a -gdb package.

cheers,

Andreas


rust-gdb=1.46.0~beta.2+dfsg1-1~exp4_rust-lldb=1.46.0~beta.2+dfsg1-1~exp4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: rustc
Source-Version: 1.46.0~beta.2+dfsg1-1~exp5
Done: Ximin Luo 

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

Debian distribution maintenance software
pp.
Ximin Luo  (supplier of updated rustc 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: Fri, 14 Aug 2020 23:45:25 +0100
Source: rustc
Architecture: source
Version: 1.46.0~beta.2+dfsg1-1~exp5
Distribution: experimental
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Ximin Luo 
Closes: 955774 968279
Changes:
 rustc (1.46.0~beta.2+dfsg1-1~exp5) experimental; urgency=medium
 .
   * Fix rust-gdb install path. (Closes: #968279)
   * Drop powerpc allowed-failures to 12. (Closes: #955774)
   * Update d-fix-mips64el-bootstrap.patch for newer LLVM.
Checksums-Sha1:
 0a235fb27bf6331264a385a2a094d4aadfe14841 2724 
rustc_1.46.0~beta.2+dfsg1-1~exp5.dsc
 2df8fe5df3a104cbd2e13657716e1a6d9cc8cfec 76024 
rustc_1.46.0~beta.2+dfsg1-1~exp5.debian.tar.xz
 e91459c09a179a63e1cbddbcaf6454c9f094fab5 7475 
rustc_1.46.0~beta.2+dfsg1-1~exp5_source.buildinfo
Checksums-Sha256:
 52d698864ef1b72f0f84d8be62e406d80828f9016852a4ffb37e00b1f7f7a024 2724 
rustc_1.46.0~beta.2+dfsg1-1~exp5.dsc
 36dd6161a3fe13f54bf4c6773876cbe22c2f4d744c3e166b649863a91345b777 76024 
rustc_1.46.0~beta.2+dfsg1-1~exp5.debian.tar.xz
 13837bc542f808820a309e62f7b3b05844cea454f5b6c389dd66a257c334ddd1 7475 
rustc_1.46.0~beta.2+dfsg1-1~exp5_source.buildinfo
Files:
 0d8123e6a4629afd42b01d2284290b3b 2724 devel optional 
rustc_1.46.0~beta.2+dfsg1-1~exp5.dsc
 1c586b9f62b74ea1e92dc0647c27db9b 76024 devel optional 
rustc_1.46.0~beta.2+dfsg1-1~exp5.debian.tar.xz
 bea5f92a1f2c2cf8e6a511dbf9d88573 7475 devel optional 
rustc_1.46.0~beta.2+dfsg1-1~exp5_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQReYinNQ9GpZ9TYcRrrH8jaRfspMAUCXzcUuAAKCRDrH8jaRfsp
MKZYAP9Jeh/XTPSLVMVPK9T2XowyhilG1pO/zCY5syIqTjUuVQEAtRA0flFTxri0
OV9pL3KUdcMgvCssTNnNJm0a2FeGRwQ=
=VMMA
-END PGP SIGNATURE End Message ---

Bug#968420: ruby-bunny: FTBFS due to faulty testcase

[Sergio Durigan Junior]

Source: ruby-bunny
Version: 2.14.4-3
Severity: serious
Tags: ftbfs sid

I've just noticed that ruby-bunny FTBFS when building using a pristine
schroot on sbuild:

--8<---cut here---start->8---
Waiting for pid file '/tmp/d20200814-17660-k3x0b6/mnesia/bunny.pid' to appear

  ##  ##  RabbitMQ 3.8.5
  ##  ##
  ##  Copyright (c) 2007-2020 VMware, Inc. or its affiliates.
  ##  ##
  ##  Licensed under the MPL 1.1. Website: https://rabbitmq.com

  Doc guides: https://rabbitmq.com/documentation.html
  Support:https://rabbitmq.com/contact.html
  Tutorials:  https://rabbitmq.com/getstarted.html
  Monitoring: https://rabbitmq.com/monitoring.html

  Logs: /tmp/d20200814-17660-k3x0b6/log/bu...@paluero.log
/tmp/d20200814-17660-k3x0b6/log/bunny@paluero_upgrade.log

  Config file(s): /tmp/d20200814-17660-k3x0b6/rabbitmq.conf

  Starting broker... completed with 4 plugins.
Error: operation wait on node bunny@paluero timed out. Timeout value used: 1
rake aborted!
command failed: ["/usr/lib/rabbitmq/bin/rabbitmqctl", "wait", 
"/tmp/d20200814-17660-k3x0b6/mnesia/bunny.pid"]
/<>/debian/ruby-tests.rake:53:in `run'
/<>/debian/ruby-tests.rake:62:in `start_rabbitmq_server'
/<>/debian/ruby-tests.rake:75:in `block in '
/usr/share/rubygems-integration/all/gems/rake-13.0.1/exe/rake:27:in `'
Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.7" failed. Exiting.
dh_auto_install: error: dh_ruby --install /<>/debian/ruby-bunny 
returned exit code 1
make[1]: *** [debian/rules:10: override_dh_auto_install] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--8<---cut here---end--->8---

If we try to build in a container/VM using dpkg-buildpackage and a
non-root user, the error happens even earlier:

--8<---cut here---start->8---
Waiting for pid file '/tmp/d20200814-28938-5mzc2m/mnesia/bunny.pid' to appear
23:47:37.895 [error] 

23:47:37.899 [error] BOOT FAILED
BOOT FAILED
23:47:37.899 [error] ===
===
23:47:37.900 [error] ERROR: distribution port 25672 in use by rabbit@magical-boa
ERROR: distribution port 25672 in use by rabbit@magical-boa
23:47:37.900 [error] 

23:47:38.902 [error] Supervisor rabbit_prelaunch_sup had child prelaunch 
started with rabbit_prelaunch:run_prelaunch_first_phase() at undefined exit 
with reason {dist_port_already_used,25672,"rabbit","magical-boa"} in context 
start_error
23:47:38.903 [error] CRASH REPORT Process <0.153.0> with 0 neighbours exited 
with reason: 
{{shutdown,{failed_to_start_child,prelaunch,{dist_port_already_used,25672,"rabbit","magical-boa"}}},{rabbit_prelaunch_app,start,[normal,[]]}}
 in application_master:init/4 line 138
{"Kernel pid 
terminated",application_controller,"{application_start_failure,rabbitmq_prelaunch,{{shutdown,{failed_to_start_child,prelaunch,{dist_port_already_used,25672,\"rabbit\",\"magical-boa\"}}},{rabbit_prelaunch_app,start,[normal,[]]}}}"}
Kernel pid terminated (application_controller) 
({application_start_failure,rabbitmq_prelaunch,{{shutdown,{failed_to_start_child,prelaunch,{dist_port_already_used,25672,"rabbit","magical-boa"}}},{rabbi

Crash dump is being written to: erl_crash.dump...done
Error: operation wait on node bunny@magical-boa timed out. Timeout value used: 
1
rake aborted!
command failed: ["/usr/lib/rabbitmq/bin/rabbitmqctl", "wait", 
"/tmp/d20200814-28938-5mzc2m/mnesia/bunny.pid"]
/home/sergio/ruby-bunny/debian/ruby-tests.rake:53:in `run'
/home/sergio/ruby-bunny/debian/ruby-tests.rake:62:in `start_rabbitmq_server'
/home/sergio/ruby-bunny/debian/ruby-tests.rake:75:in `block in '
/usr/share/rubygems-integration/all/gems/rake-13.0.1/exe/rake:27:in `'
Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.7" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/home/sergio/ruby-bunny/debian/ruby-bunny returned exit code 1
--8<---cut here---end--->8---

There are a few problems with the testcase:

- As stated above, it can't run under as a non-root user.  For example,
  this won't work:

def start_rabbitmq_server
  fork do
exec('/usr/lib/rabbitmq/bin/rabbitmq-server')
  end

  pidfile = File.join($tmpdir, 'mnesia', 'bunny.pid')
  run('/usr/lib/rabbitmq/bin/rabbitmqctl', 'wait', pidfile)

  run('./bin/ci/before_build')
end

- The file "bunny.pid" isn't (always) named like that.  Here, for
  example, it's named "bunny@${HOST}.pid".  This will break the
  following code:

pidfile = File.join($tmpdir, 'mnesia', 'bunny.pid')
run('/usr/lib/rabbitmq/bin/rabbitmqctl', 'wait', pidfile)

- It tries to "pkill epmd", which also won't work when run as non-root.

It seems to me like this test should be executed by autopkgtest, because
the o

Bug#961584: lxc-stop fails with exit code 1

[Harald Dunkel]

PS, just to be sure: You do have mounted cgroupv2 on the Docker
host and in the Docker container?

Bug#968427: Variables declared without extern in cairo_ocaml.h cause FTBFS

[Stéphane Glondu]

Source: libcairo2-ocaml-dev
Severity: serious
Tags: ftbfs
Control: affects -1 why3 lablgtk3

Dear Maintainer,

/usr/lib/ocaml/cairo2/cairo_ocaml.h declares variables without extern,
causing multiple definitions if this file is included in multiple .c
files, which is an error with gcc-10. This causes lablgtk3 (which
includes cairo_ocaml.h) to have multiple definitions, which in turn
causes why3 to FTBFS.

Cheers,

-- 
Stéphane


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

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

Processed: Variables declared without extern in cairo_ocaml.h cause FTBFS

[Debian Bug Tracking System]

Processing control commands:

> affects -1 why3 lablgtk3
Bug #968427 [src:libcairo2-ocaml-dev] Variables declared without extern in 
cairo_ocaml.h cause FTBFS
Warning: Unknown package 'src:libcairo2-ocaml-dev'
Added indication that 968427 affects why3 and lablgtk3
Warning: Unknown package 'src:libcairo2-ocaml-dev'

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