Bug#950559: marked as done (apertium-mk-bg FTBFS with apertium 3.6.1)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 04:49:10 +
with message-id 
and subject line Bug#950559: fixed in apertium-mk-bg 0.2.0~r49489-3
has caused the Debian Bug report #950559,
regarding apertium-mk-bg FTBFS with apertium 3.6.1
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.)


-- 
950559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apertium-mk-bg
Version: 0.2.0~r49489-2
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-mk-bg.html

...
make -j16
make[1]: Entering directory '/build/1st/apertium-mk-bg-0.2.0~r49489'
apertium-validate-dictionary apertium-mk-bg.mk.dix
apertium-validate-dictionary apertium-mk-bg.bg.dix
apertium-validate-dictionary apertium-mk-bg.mk-bg.dix
apertium-validate-dictionary apertium-mk-bg.mk-bg.dix
apertium-validate-dictionary apertium-mk-bg.bg.dix
apertium-validate-dictionary apertium-mk-bg.mk.dix
apertium-validate-transfer apertium-mk-bg.mk-bg.t1x
cg-comp apertium-mk-bg.mk-bg.rlx mk-bg.rlx.bin
cg-comp apertium-mk-bg.bg-mk.rlx bg-mk.rlx.bin
apertium-validate-transfer apertium-mk-bg.bg-mk.t1x
apertium-validate-dictionary apertium-mk-bg.post-mk.dix
apertium-validate-dictionary apertium-mk-bg.post-bg.dix
apertium-gen-modes modes.xml
Sections: 1, Rules: 4, Sets: 9, Tags: 58
apertium-gen-modes modes.xml
lt-comp lr apertium-mk-bg.post-mk.dix bg-mk.autopgen.bin
lt-comp lr apertium-mk-bg.post-bg.dix mk-bg.autopgen.bin
apertium-preprocess-transfer apertium-mk-bg.bg-mk.t1x bg-mk.t1x.bin
apertium-preprocess-transfer apertium-mk-bg.mk-bg.t1x mk-bg.t1x.bin
mkdir: cannot create directory ‘/build/1st/apertium-mk-bg-0.2.0~r49489/modes’: 
File exists
Sections: 2, Rules: 53, Sets: 93, Tags: 154
7 rules cannot be skipped by index.
main@standard 9 39
main@standard 20 53
Warning (520): Paths to rule 6 blocked by rule 4.
Warning (520): Paths to rule 6 blocked by rule 4.
Warning (520): Paths to rule 6 blocked by rule 4.
Warning (520): Paths to rule 6 blocked by rule 4.
Warning (520): Paths to rule 6 blocked by rule 4.
Warning (520): Paths to rule 6 blocked by rule 4.
Warning (520): Paths to rule 6 blocked by rule 4.
Warning (520): Paths to rule 6 blocked by rule 4.
Warning (520): Paths to rule 6 blocked by rule 4.
Warning (520): Paths to rule 6 blocked by rule 4.
Warning (659): Paths to rule 12 blocked by rule 11.
Warning (659): Paths to rule 12 blocked by rule 11.
Warning (1324): Paths to rule 14 blocked by rule 12.
Warning (2462): Paths to rule 23 blocked by rule 18.
Warning (2462): Paths to rule 23 blocked by rule 18.
cp *.mode modes/
cp *.mode modes/
cp: cannot stat '*.mode': No such file or directory
cp: cannot stat '*.mode': No such file or directory
make[1]: *** [Makefile:698: bg-mk.mode] Error 1
--- End Message ---
--- Begin Message ---
Source: apertium-mk-bg
Source-Version: 0.2.0~r49489-3
Done: Kartik Mistry 

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated apertium-mk-bg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 24 Mar 2020 18:45:20 +0530
Source: apertium-mk-bg
Architecture: source
Version: 0.2.0~r49489-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Kartik Mistry 
Closes: 950559
Changes:
 apertium-mk-bg (0.2.0~r49489-3) unstable; urgency=medium
 .
   * Added patch to fix FTBFS with apertium 3.6 (Closes: #950559)
   * Added debian/gitlab-ci.yml file.
   * debian/control:
 + Updated Standards-Version to 4.5.0
 + Switched to debhelper-compat
 + Added 'Rules-Requires-Root' field.
   * Added debian/upstream/metadata file.
Checksums-Sha1:
 65a31fba857bb76ff2f429c64204bd9877a2040f 2117 apertium-mk-bg_0.2.0~r49489-3.dsc
 b5c1be70822843d53dbe4ea492dbc8916fbd1402 3004 
apertium-mk-bg_0.2.0~r49489-3.debian.tar.xz
Checksums-Sha256:
 6d20bed9ea837d1861a08bc3c62e26a10d61d168c9548e6aeb28959423a8d272 2117 

Bug#954638: marked as done (golang-github-mattn-go-runewidth: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/mattn/go-runewidth returned exit code 1)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 04:49:18 +
with message-id 
and subject line Bug#954638: fixed in golang-github-mattn-go-runewidth 0.0.9-1
has caused the Debian Bug report #954638,
regarding golang-github-mattn-go-runewidth: FTBFS: dh_auto_test: error: cd 
_build && go test -vet=off -v -p 4 github.com/mattn/go-runewidth returned exit 
code 1
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.)


-- 
954638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-mattn-go-runewidth
Version: 0.0.8-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang --builddirectory=_build
>dh_update_autotools_config -O--buildsystem=golang -O--builddirectory=_build
>dh_autoreconf -O--buildsystem=golang -O--builddirectory=_build
>dh_auto_configure -O--buildsystem=golang -O--builddirectory=_build
>dh_auto_build -O--buildsystem=golang -O--builddirectory=_build
>   cd _build && go generate -v github.com/mattn/go-runewidth
> src/github.com/mattn/go-runewidth/benchmark_test.go
> src/github.com/mattn/go-runewidth/runewidth.go
> src/github.com/mattn/go-runewidth/runewidth_posix.go
> src/github.com/mattn/go-runewidth/runewidth_posix_test.go
> src/github.com/mattn/go-runewidth/runewidth_test.go
>   cd _build && go install -trimpath -v -p 4 github.com/mattn/go-runewidth
> runtime/internal/sys
> internal/cpu
> runtime/internal/atomic
> sync/atomic
> runtime/internal/math
> internal/race
> unicode
> internal/testlog
> unicode/utf8
> internal/bytealg
> math/bits
> math
> runtime
> internal/reflectlite
> sync
> errors
> sort
> internal/oserror
> io
> strconv
> syscall
> bytes
> strings
> regexp/syntax
> time
> internal/syscall/unix
> regexp
> internal/poll
> os
> github.com/mattn/go-runewidth
>dh_auto_test -O--buildsystem=golang -O--builddirectory=_build
>   cd _build && go test -vet=off -v -p 4 github.com/mattn/go-runewidth
> === RUN   TestIsEastAsian
> --- PASS: TestIsEastAsian (0.00s)
> === RUN   TestIsEastAsianLCCTYPE
> --- PASS: TestIsEastAsianLCCTYPE (0.00s)
> === RUN   TestIsEastAsianLANG
> --- PASS: TestIsEastAsianLANG (0.00s)
> === RUN   TestTableChecksums
> TestTableChecksums: runewidth_test.go:63: table = combining,
>   n = 465 want 461,
>   sha256 = 
> 3cce13deb5e23f9f7327f2b1ef162328285a7dcf277a98302a8f7cdd43971268 want 
> ef1839ee99b2707da7d5592949bd9b40d434fa6462c6da61477bae923389e263
> TestTableChecksums: runewidth_test.go:63: table = doublewidth,
>   n = 182440 want 181887,
>   sha256 = 
> 3d16eda8650dc2c92d6318d32f0b4a74fda5a278db2d4544b1dd65863394823c want 
> de2d7a29c94fb2fe471b5fd0c003043845ce59d1823170606b95f9fc8988067a
> TestTableChecksums: runewidth_test.go:63: table = emoji,
>   n = 3535 want 3791,
>   sha256 = 
> 9ec17351601d49c535658de8d129c1d0ccda2e620669fc39a2faaee7dedcef6d want 
> bf02b49f5cbee8df150053574d20125164e7f16b5f62aa5971abca3b2f39a8e6
> TestTableChecksums: runewidth_test.go:63: table = neutral,
>   n = 27333 want 26925,
>   sha256 = 
> 5455f5e75c307f70b4e9b2384dc5a8bcd91a4c5e2b24b2b185dfad4d860ee5c2 want 
> d79d8558f3cc35c633e5025c9b29c005b853589c8f71b4a72507b5c31d8a6829
> --- FAIL: TestTableChecksums (0.13s)
> === RUN   TestSorted
> --- PASS: TestSorted (0.00s)
> === RUN   TestRuneWidth
> --- PASS: TestRuneWidth (0.00s)
> === RUN   TestIsAmbiguousWidth
> --- PASS: TestIsAmbiguousWidth (0.00s)
> === RUN   TestStringWidth
> --- PASS: TestStringWidth (0.00s)
> === RUN   TestStringWidthInvalid
> --- PASS: TestStringWidthInvalid (0.00s)
> === RUN   TestTruncateSmaller
> --- PASS: TestTruncateSmaller (0.00s)
> === RUN   TestTruncate
> --- PASS: TestTruncate (0.00s)
> === RUN   TestTruncateFit
> --- PASS: TestTruncateFit (0.00s)
> === RUN   TestTruncateJustFit
> --- PASS: TestTruncateJustFit (0.00s)
> === RUN   TestWrap
> --- PASS: TestWrap (0.00s)
> === RUN   TestTruncateNoNeeded
> --- PASS: TestTruncateNoNeeded (0.00s)
> === RUN   TestIsNeutralWidth
> --- PASS: TestIsNeutralWidth (0.00s)
> === RUN   TestFillLeft
> --- PASS: TestFillLeft (0.00s)
> === RUN   TestFillLeftFit
> --- PASS: TestFillLeftFit (0.00s)
> === RUN   TestFillRight
> --- PASS: TestFillRight (0.00s)
> === RUN   TestFillRightFit
> --- PASS: TestFillRightFit (0.00s)
> 

Bug#953969: marked as done (onioncircuits: autopkgtest failure with Python 3.8 as default)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 00:15:41 -0400
with message-id <2562204.EoEBX4H4JI@l5580>
and subject line Re: Bug#953969: onioncircuits: autopkgtest failure with Python 
3.8 as default
has caused the Debian Bug report #953969,
regarding onioncircuits: autopkgtest failure with Python 3.8 as default
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.)


-- 
953969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: onioncircuits
Version:  0.6-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: needs-update

Hi Maintainer

The autopkgtests of onioncircuits started to fail with Python 3.8 as
the default Python3 interpreter [1].

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

Regards
Graham


[1] https://ci.debian.net/packages/o/onioncircuits/unstable/amd64/


autopkgtest [12:01:09]: test gui-test: [---
waiting for Tor to settle...
Traceback (most recent call last):
  File "/usr/bin/onioncircuits", line 657, in 
app = OnionCircuitsApplication()
  File "/usr/bin/onioncircuits", line 633, in __init__
self.connect_controller()
  File "/usr/bin/onioncircuits", line 647, in connect_controller
self.controller = stem.connection.connect(**connect_args)
  File "/usr/lib/python3/dist-packages/stem/connection.py", line 291, in connect
return _connect_auth(control_connection, password,
password_prompt, chroot_path, controller)
  File "/usr/lib/python3/dist-packages/stem/connection.py", line 375,
in _connect_auth
return controller(control_socket, is_authenticated = True)
  File "/usr/lib/python3/dist-packages/stem/control.py", line 1057, in __init__
super(Controller, self).__init__(control_socket, is_authenticated)
  File "/usr/lib/python3/dist-packages/stem/control.py", line 585, in __init__
self._post_authentication()
  File "/usr/lib/python3/dist-packages/stem/control.py", line 3902, in
_post_authentication
owning_pid = self.get_conf('__OwningControllerProcess', None)
  File "/usr/lib/python3/dist-packages/stem/control.py", line 2170, in get_conf
entries = self.get_conf_map(param, default, multiple)
  File "/usr/lib/python3/dist-packages/stem/control.py", line 2273, in
get_conf_map
for key in reply:
RuntimeError: dictionary keys changed during iteration
/usr/lib/python3.8/subprocess.py:942: ResourceWarning: subprocess 3003
is still running
  _warn("subprocess %s is still running" % self.pid,
ResourceWarning: Enable tracemalloc to get the object allocation traceback
E
==
ERROR: test_has_correct_circuits (__main__.TestOnionCircuitsGUI)
--
Traceback (most recent call last):
  File "debian/tests/check-circuits", line 38, in setUp
self.rootapp = dogtail.tree.root.application('onioncircuits')
  File "/usr/lib/python3/dist-packages/dogtail/tree.py", line 1173, in
application
return root.findChild(predicate.IsAnApplicationNamed(appName),
recursive=False, retry=retry, showingOnly=False)
  File "/usr/lib/python3/dist-packages/dogtail/tree.py", line 939, in findChild
raise SearchError(describeSearch(self, pred, recursive, debugName))
dogtail.tree.SearchError: child of [desktop frame | main]:
"onioncircuits" application

--
Ran 1 test in 40.120s

FAILED (errors=1)
Creating logfile at
/tmp/dogtail-testuser/logs/check-circuits_20200314-120129_debug ...
Warning: AT-SPI's desktop is visible but it has no children. Are you
running any AT-SPI-aware applications?
searching for child of [desktop frame | main]: "onioncircuits"
application (attempt 3)
searching for child of [desktop frame | main]: "onioncircuits"
application (attempt 4)
searching for child of [desktop frame | main]: "onioncircuits"
application (attempt 5)
searching for child of [desktop frame | main]: "onioncircuits"
application (attempt 6)
searching for child of [desktop frame | main]: "onioncircuits"
application (attempt 7)
searching for child of [desktop frame | main]: "onioncircuits"
application (attempt 8)
searching for child of [desktop frame | main]: "onioncircuits"
application (attempt 9)
searching for child of [desktop frame | main]: "onioncircuits"
application (attempt 10)
searching for child of [desktop frame | main]: "onioncircuits"
application (attempt 11)
searching for child of [desktop frame | main]: "onioncircuits"
application (attempt 12)

Bug#953863: marked as done (python3-stem: "RuntimeError: dictionary keys changed during iteration" with python 3.8)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 03:05:22 +
with message-id 
and subject line Bug#953863: fixed in python-stem 1.7.1-1.2
has caused the Debian Bug report #953863,
regarding python3-stem: "RuntimeError: dictionary keys changed during 
iteration" with python 3.8
to be marked as done.

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

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


-- 
953863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-stem
Version: 1.7.1-1.1
Severity: serious

Hi,

onioncircuits fails to start on current sid:

Traceback (most recent call last):
  File "/bin/onioncircuits", line 657, in 
app = OnionCircuitsApplication()
  File "/bin/onioncircuits", line 633, in __init__
self.connect_controller()
  File "/bin/onioncircuits", line 647, in connect_controller
self.controller = stem.connection.connect(**connect_args)
  File "/usr/lib/python3/dist-packages/stem/connection.py", line 291, in connect
return _connect_auth(control_connection, password, password_prompt, 
chroot_path, controller)
  File "/usr/lib/python3/dist-packages/stem/connection.py", line 375, in 
_connect_auth
return controller(control_socket, is_authenticated = True)
  File "/usr/lib/python3/dist-packages/stem/control.py", line 1057, in __init__
super(Controller, self).__init__(control_socket, is_authenticated)
  File "/usr/lib/python3/dist-packages/stem/control.py", line 585, in __init__
self._post_authentication()
  File "/usr/lib/python3/dist-packages/stem/control.py", line 3902, in 
_post_authentication
owning_pid = self.get_conf('__OwningControllerProcess', None)
  File "/usr/lib/python3/dist-packages/stem/control.py", line 2170, in get_conf
entries = self.get_conf_map(param, default, multiple)
  File "/usr/lib/python3/dist-packages/stem/control.py", line 2273, in 
get_conf_map
for key in reply:
RuntimeError: dictionary keys changed during iteration


onionshare-gui fails to start with the same error since I upgraded to
python 3.8.

I think that's https://trac.torproject.org/projects/tor/ticket/30882,
which was fixed upstream with this commit:
https://gitweb.torproject.org/stem.git/commit/stem/control.py?id=b5aecb743d33db1a6378d59792d8e57305b6c6f2

I confirm that this commit fixes the problem I'm experiencing with
onioncircuits and onionshare.

Until you, or someone else, finds time to package the 1.8.0 upstream
release, could you please import that fix as a Debian patch?
Alternatively, would you mind if someone else did that as an NMU?


In passing, this was not caught by the autopkgtest, that I think
should be marked as superficial like this:

  Tests: version
  Restrictions: allow-stderr, superficial
  Depends: @

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

Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER
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 python3-stem depends on:
ii  python33.8.2-1
ii  python3-distutils  3.8.2-2

python3-stem recommends no packages.

python3-stem suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python-stem
Source-Version: 1.7.1-1.2
Done: Scott Kitterman 

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated python-stem package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 24 Mar 2020 16:47:02 -0400
Source: python-stem
Architecture: source
Version: 1.7.1-1.2
Distribution: unstable
Urgency: medium
Maintainer: Ulises Vitulli 
Changed-By: Scott Kitterman 
Closes: 953863
Changes:
 python-stem (1.7.1-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add fix from upstream to 

Bug#954314: marked as done (neomutt: diff for NMU version 20191207+dfsg.1-1.1)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 02:12:38 +
with message-id <20200325021145.fj567btokazud...@satie.tumbleweed.org.za>
and subject line Bug#954314: fixed in neomutt 20191207+dfsg.1-1.1
has caused the Debian Bug report #954314,
regarding neomutt: diff for NMU version 20191207+dfsg.1-1.1
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.)


-- 
954314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: neomutt
Version: 20191207+dfsg.1-1
Severity: normal
Tags: patch  pending

Dear maintainer,

I've prepared an NMU for neomutt (versioned as 20191207+dfsg.1-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Diff in git: https://salsa.debian.org/mutt-team/neomutt/-/merge_requests/2

Regards.

diff -Nru neomutt-20191207+dfsg.1/debian/changelog neomutt-20191207+dfsg.1/debian/changelog
--- neomutt-20191207+dfsg.1/debian/changelog	2020-03-02 05:04:03.0 -0800
+++ neomutt-20191207+dfsg.1/debian/changelog	2020-03-19 17:09:59.0 -0700
@@ -1,3 +1,11 @@
+neomutt (20191207+dfsg.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix segfault in pager on new message received. (Closes: #953757)
+  * Fix FTBFS in non-UTC timezone. (Closes: #948895)
+
+ -- Stefano Rivera   Thu, 19 Mar 2020 17:09:59 -0700
+
 neomutt (20191207+dfsg.1-1) unstable; urgency=medium
 
   [ Andreas Henriksson ]
diff -Nru neomutt-20191207+dfsg.1/debian/patches/series neomutt-20191207+dfsg.1/debian/patches/series
--- neomutt-20191207+dfsg.1/debian/patches/series	2020-03-02 05:01:49.0 -0800
+++ neomutt-20191207+dfsg.1/debian/patches/series	2020-03-19 17:09:59.0 -0700
@@ -2,3 +2,5 @@
 debian-specific/use_usr_bin_editor.patch
 debian-specific/document_debian_defaults.patch
 misc/smime.rc.patch
+upstream/pager-segfault.patch
+upstream/test-tz.patch
diff -Nru neomutt-20191207+dfsg.1/debian/patches/upstream/pager-segfault.patch neomutt-20191207+dfsg.1/debian/patches/upstream/pager-segfault.patch
--- neomutt-20191207+dfsg.1/debian/patches/upstream/pager-segfault.patch	1969-12-31 16:00:00.0 -0800
+++ neomutt-20191207+dfsg.1/debian/patches/upstream/pager-segfault.patch	2020-03-19 17:09:59.0 -0700
@@ -0,0 +1,27 @@
+From: Pietro Cerutti 
+Date: Sat, 14 Dec 2019 16:18:28 +0100
+Subject: Fix crash in pager (#2039)
+
+Fixes #2038
+
+Bug-Upstream: https://github.com/neomutt/neomutt/issues/2038
+Origin: upstream, https://github.com/neomutt/neomutt/commit/645189415f20857fc317bb862a5b9dba33f61fa8
+Bug-Debian: https://bugs.debian.org/953757
+---
+ pager.c | 3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/pager.c b/pager.c
+index 793cdfb..1053885 100644
+--- a/pager.c
 b/pager.c
+@@ -2422,6 +2422,9 @@ int mutt_pager(const char *banner, const char *fname, PagerFlags flags, struct P
+ rd.menu->current =
+ MIN(rd.menu->current, MAX(Context->mailbox->msg_count - 1, 0));
+ struct Email *e = mutt_get_virt_email(Context->mailbox, rd.menu->current);
++if (!e)
++  continue;
++
+ index_hint = e->index;
+ 
+ bool q = Context->mailbox->quiet;
diff -Nru neomutt-20191207+dfsg.1/debian/patches/upstream/test-tz.patch neomutt-20191207+dfsg.1/debian/patches/upstream/test-tz.patch
--- neomutt-20191207+dfsg.1/debian/patches/upstream/test-tz.patch	1969-12-31 16:00:00.0 -0800
+++ neomutt-20191207+dfsg.1/debian/patches/upstream/test-tz.patch	2020-03-19 17:09:59.0 -0700
@@ -0,0 +1,94 @@
+From: Pietro Cerutti 
+Date: Wed, 29 Jan 2020 14:44:00 +
+Subject: Make sure we use the correct timezone in tests
+
+Fixes #2100
+
+Bug-Upstream: https://github.com/neomutt/neomutt/issues/2100
+Origin: upstream, https://github.com/neomutt/neomutt/commit/8aee8ba2a2e8726bf64b95d94c77dd34512b3732
+Bug-Debian: https://bugs.debian.org/948895
+---
+ test/date/mutt_date_localtime.c| 3 +++
+ test/date/mutt_date_localtime_format.c | 3 +++
+ test/date/mutt_date_make_imap.c| 3 +++
+ test/date/mutt_date_make_time.c| 3 +++
+ 4 files changed, 12 insertions(+)
+
+diff --git a/test/date/mutt_date_localtime.c b/test/date/mutt_date_localtime.c
+index dff4a89..c573445 100644
+--- a/test/date/mutt_date_localtime.c
 b/test/date/mutt_date_localtime.c
+@@ -24,11 +24,14 @@
+ #include "acutest.h"
+ #include "config.h"
+ #include "mutt/mutt.h"
++#include 
+ 
+ void test_mutt_date_localtime(void)
+ {
+   // struct tm mutt_date_localtime(time_t t);
+ 
++  setenv("TZ", "UTC", 1);
++
+   {
+ TEST_CASE("December, 

Bug#915829: marked as done (ITP: arcp -- (Archive and Package) URI parser and generator)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 02:11:56 +
with message-id 
and subject line Bug#915829: fixed in arcp 0.2.1-1
has caused the Debian Bug report #915829,
regarding ITP: arcp -- (Archive and Package) URI parser and generator
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.)


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

Subject: ITP: arcp -- (Archive and Package) URI parser and generator
Package: wnpp
Owner: Debian Med team 
Severity: wishlist

* Package name: arcp
  Version : 0.2.0
  Upstream Author : Stian Soiland-Reyes 
* URL : http://arcp.readthedocs.io/
* License : Apache-2.0
  Programming Language: Python
  Description : (Archive and Package) URI parser and generator


 arcp provides functions for creating arcp URIs, 
 which can be used for identifying or parsing hypermedia 
 files packaged in an archive or package, like a ZIP file.
 .
 arcp URIs can be used to consume or reference hypermedia resources 
 bundled inside a file archive or an application package, as well as 
 to resolve URIs for archive resources within a programmatic framework.
 .
 This URI scheme provides mechanisms to generate a unique base URI 
 to represent the root of the archive, so that relative URI references 
 in a bundled resource can be resolved within the archive without having to
 extract the archive content on the local file system.
 .
 An arcp URI can be used for purposes of isolation (e.g. when consuming 
 multiple archives), security constraints (avoiding “climb out” from the
 archive), or for externally identiyfing sub-resources referenced by
 hypermedia formats.
 .
 Examples:
  - ``arcp://uuid,32a423d6-52ab-47e3-a9cd-54f418a48571/doc.html``
  - ``arcp://uuid,b7749d0b-0e47-5fc4-999d-f154abe68065/pics/``
  - ``arcp://ni,sha-256;F-34D4TUeOfG0selz7REKRDo4XePkewPeQYtjL3vQs0/``
  - ``arcp://name,gallery.example.org/``
 .
 The different forms of URI authority_ in arcp URIs can be used depending
 on which uniqueness constraints to apply when addressing an archive.
 See the arcp specification
 (https://tools.ietf.org/html/draft-soilandreyes-arcp-02) for details.
 .
 Note that this library only provides mechanisms to 
  *generate* and *parse* arcp URIs, and do *not* integrate with any 
 particular archive or URL handling modules like 
 "zipfile" or "urllib.request".

Needed for latest cwltool. Will be team-maintained by Debian Med
--- End Message ---
--- Begin Message ---
Source: arcp
Source-Version: 0.2.1-1
Done: michael.cru...@gmail.com (Michael R. Crusoe)

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated arcp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 12 Feb 2020 14:52:23 +0100
Source: arcp
Binary: python3-arcp
Architecture: source all
Version: 0.2.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Description:
 python3-arcp - (Archive and Package) URI parser and generator
Closes: 915829
Changes:
 arcp (0.2.1-1) unstable; urgency=low
 .
   * Initial release. (Closes: #915829)
Checksums-Sha1:
 58bc44c98f6f5ff8a9241c3c857e4c38189f3f59 1984 arcp_0.2.1-1.dsc
 c049d28e3c387752da76aaba985b5416e58c9b4e 22063 arcp_0.2.1.orig.tar.gz
 071f7b6740c889d41f5726140cd339926631d0a9 2344 arcp_0.2.1-1.debian.tar.xz
 bb6ea563c6d05ed7c1422e95005b8e811c1c71e2 6217 arcp_0.2.1-1_amd64.buildinfo
 94c01bc47384317c5e5e6d78e66170dae34b35bd 13320 python3-arcp_0.2.1-1_all.deb
Checksums-Sha256:
 0d7e514f2e136eac59fd1960c93081b19e946a3ae54a356a1cd8a170ab4b4aee 1984 
arcp_0.2.1-1.dsc
 5c17ac7972c9ef82979cc2caf2b3a87c1aefd3fefe9adb8a5dd728ada57715dd 22063 
arcp_0.2.1.orig.tar.gz
 680e4d4afb2548ccdf8ed98c0624ef52481d099449b1aaf051d1cabf60c88019 2344 
arcp_0.2.1-1.debian.tar.xz
 34c3554a5f282387e8d5f53a9856569e9135d17fc69e2b677c043b70b4c6f4e3 6217 

Bug#942132: marked as done (ITP: python-nest-asyncio -- Patch asyncio to allow nested event loops)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 02:11:58 +
with message-id 
and subject line Bug#942132: fixed in python-nest-asyncio 1.2.3-1
has caused the Debian Bug report #942132,
regarding ITP: python-nest-asyncio -- Patch asyncio to allow nested event loops
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.)


-- 
942132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: "Diego M. Rodriguez" 

* Package name: python-nest-asyncio
  Version : 1.2.0
  Upstream Author : Ewald R. de Wit 
* URL : https://github.com/erdewit/nest_asyncio
* License : BSD-2-clause
  Programming Lang: Python
  Description : Patch asyncio to allow nested event loops

 By design asyncio does not allow its event loop to be nested. This
 presents a practical problem: When in an environment where the event
 loop is already running it's impossible to run tasks and wait for the
 result. This module patches asyncio to allow nested use of asyncio.run
 and loop.run_until_complete.

This package is a dependency for updating the existing qiskit-terra
package to its newest version. The intent is to maintain this package
under the umbrella of the Debian Python Modules Team.

-- 
Diego M. Rodriguez



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-nest-asyncio
Source-Version: 1.2.3-1
Done: di...@moreda.io (Diego M. Rodriguez)

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

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

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

Debian distribution maintenance software
pp.
Diego M. Rodriguez  (supplier of updated python-nest-asyncio 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 28 Jan 2020 13:59:39 +0100
Source: python-nest-asyncio
Binary: python3-nest-asyncio
Architecture: source amd64
Version: 1.2.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Diego M. Rodriguez 
Description:
 python3-nest-asyncio - Patch asyncio to allow nested event loops
Closes: 942132
Changes:
 python-nest-asyncio (1.2.3-1) unstable; urgency=medium
 .
   * Initial release (Closes: #942132)
Checksums-Sha1:
 31eac9484908c0677c289dbddcfa016eb0b8adce 2152 python-nest-asyncio_1.2.3-1.dsc
 3b06e27e08d1faacd14175d9b4f4b50ba3e93e53 5798 
python-nest-asyncio_1.2.3.orig.tar.gz
 07b07c97e56dcea5efd5cf855d1aaa292e62fc1c 1916 
python-nest-asyncio_1.2.3-1.debian.tar.xz
 13064ba0de0e872a49502e76811ee42f2d9216e0 6725 
python-nest-asyncio_1.2.3-1_amd64.buildinfo
 ad371ac73824d18f0c4743284a464c73f4cbde08 5208 
python3-nest-asyncio_1.2.3-1_amd64.deb
Checksums-Sha256:
 81d6920650538ce121e204b1da24a6c692939f3dc0081803cb1b0ed1af6d7d06 2152 
python-nest-asyncio_1.2.3-1.dsc
 43078bf213344616a1782eb6baa36ccf88029b829cf7e6eeaececc2cc6cbf63b 5798 
python-nest-asyncio_1.2.3.orig.tar.gz
 2f6c27869ef821296727a250b0342579fac79a16d3e9c9d0f13551cc0ba81b26 1916 
python-nest-asyncio_1.2.3-1.debian.tar.xz
 ac962b77896110e6b50f974cc0adcc3490a03a840ec9490b375dd521f2ab033a 6725 
python-nest-asyncio_1.2.3-1_amd64.buildinfo
 ff9590c1a6985ed171cc9203c8b8810257b7abc0c5f1b4010450d70467aeb399 5208 
python3-nest-asyncio_1.2.3-1_amd64.deb
Files:
 9eef54ddc5a26ccaf3ab84668e0f8005 2152 python optional 
python-nest-asyncio_1.2.3-1.dsc
 dd22a2e7d1cb357681bdd22c95c4a6be 5798 python optional 
python-nest-asyncio_1.2.3.orig.tar.gz
 fc25d171c73da538d20be26344738b8f 1916 python optional 
python-nest-asyncio_1.2.3-1.debian.tar.xz
 8dc10ed532a9cbf6df3bf67e4eacd2d0 6725 python optional 
python-nest-asyncio_1.2.3-1_amd64.buildinfo
 491f6623fdf27f827631c491c38581a4 5208 python optional 
python3-nest-asyncio_1.2.3-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAl5DMWkACgkQgj6WdgbD
S5a+1RAA4Vh7X56Sj+yACUaFDo1RgKAAIqlaPK8125BBWTtKWkblPLpMwDaI/L6M
OZMNvqvt/M+OWY8dA5yUyWfd9rjnse2tBtyB2n3kV/7BsYhKIPBHIcj3B3eZ1tzQ
vqQfswHySNVHVS3YUDLwXUFxtzBia5dkereUE40lMoMs4M/Zw+kD7522x8jfkoSh

Bug#951235: marked as done (ITP: pyscrypt -- pure-python scrypt password-based key derivation function)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 02:12:02 +
with message-id 
and subject line Bug#951235: fixed in python-pyscrypt 1.6.2-1
has caused the Debian Bug report #951235,
regarding ITP: pyscrypt -- pure-python scrypt password-based key derivation 
function
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.)


-- 
951235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951235
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 

* Package name : python-pyscrypt
  Version  : 1.6.2-1
  Upstream Author  : Richard Moore 
* Url  : https://github.com/ricmoo/pyscrypt
* Licenses : Expat
  Programming Lang : Python
  Section  : python

 pyscrypt is a very simple, pure-Python implementation
 of the scrypt password-based key derivation function
 and scrypt file format libraries.

This package is (transitively) needed by etesync-dav.

I plan to maintain this package myself, keeping debianization in 
following Git repository:

 https://salsa.debian.org/debian/python-pyscrypt.git


-- 
 * 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 ---
--- Begin Message ---
Source: python-pyscrypt
Source-Version: 1.6.2-1
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated python-pyscrypt 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: Thu, 13 Feb 2020 01:49:24 +0100
Source: python-pyscrypt
Binary: python3-pyscrypt
Architecture: source all
Version: 1.6.2-1
Distribution: experimental
Urgency: low
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Description:
 python3-pyscrypt - pure-python scrypt password-based key derivation function
Closes: 951235
Changes:
 python-pyscrypt (1.6.2-1) experimental; urgency=low
 .
   * initial packaging release
 closes: bug#951235
Checksums-Sha1:
 92e99a758e404313256c50c0173548273c169ab7 1943 python-pyscrypt_1.6.2-1.dsc
 3e1ef40968d31345067dc511f64528f20c80b218 35915 
python-pyscrypt_1.6.2.orig.tar.gz
 5b367ba26ab11999303271316fd276f86f3a59d5 2864 
python-pyscrypt_1.6.2-1.debian.tar.xz
 8caf30d867f0f7f8147a98cdd80bf487fe53cb01 5989 
python-pyscrypt_1.6.2-1_amd64.buildinfo
 ec733b9f04d469125bdce674d6f82875f8f2d0c6 13692 python3-pyscrypt_1.6.2-1_all.deb
Checksums-Sha256:
 e43f3f8a3258364372cb1edb47b2a987cbdbea3839767f3a8241f402e58a56dc 1943 
python-pyscrypt_1.6.2-1.dsc
 70c79f5879a7bad661e6b71956d6e25da54bb372b53f2d91d1d3a2262b7b4d63 35915 
python-pyscrypt_1.6.2.orig.tar.gz
 c48862310b865d7ad26687ecf6488995b983469cde9f23bab2111b88823ac84e 2864 
python-pyscrypt_1.6.2-1.debian.tar.xz
 2a416dfc0f3f442f92572528a941edaf037d41a276aefb0e4b2d30ce612011f8 5989 
python-pyscrypt_1.6.2-1_amd64.buildinfo
 bfc398df88d5a7ad3d7a7edbba409a608e6ef9d86cdf33a5e435141724029d5c 13692 
python3-pyscrypt_1.6.2-1_all.deb
Files:
 e6b4efcaba38c9923b00082207bd62a4 1943 python optional 
python-pyscrypt_1.6.2-1.dsc
 fc97f195bebe03150dd5d03be9d9ffd2 35915 python optional 
python-pyscrypt_1.6.2.orig.tar.gz
 ba052f092b27e5d96332ee5f947dbdc2 2864 python optional 
python-pyscrypt_1.6.2-1.debian.tar.xz
 c3b8b3ab69e5b0ae63528015173efd95 5989 python optional 
python-pyscrypt_1.6.2-1_amd64.buildinfo
 295cdcda4b1fa933e826257947349db0 13692 python optional 
python3-pyscrypt_1.6.2-1_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl5EnnAACgkQLHwxRsGg
ASHCag//evB3UEc6nlH8tSzJAxq9iTRYVmnsCmHKPRHeI8WIPxFjByRk0X2PVoWG
MBeUs5U6n2dRNU7XyAVvlqCM+uabHouX+6O2mkAO89BrpWvCqB3nEfxsqNHS/EN/
vn7fQ+Fx/4Wx4vOYNoGOyPNt1U6O3zEGq57ulJH5da0//xi7IKHcurLcAldmwO2/
HlHa5uuh41WJJu7ADGrHrvUpO3d86HpwRnosgq0Fk6bIhwaTOnYjBBcBjZ8lSE2x
TH0cFw3qgpVkbKyBWW/QfoCe1O9QY+O7c20u/QcMmvWs9rmvBh68Q6QjLBqLXFV/

Bug#950749: marked as done (ITP: node-mqtt-connection -- Barebone Connection object for MQTT)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 01:00:11 +
with message-id 
and subject line Bug#950749: fixed in node-mqtt-connection 4.0.0-1
has caused the Debian Bug report #950749,
regarding ITP: node-mqtt-connection -- Barebone Connection object for MQTT
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.)


-- 
950749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Ying-Chun Liu (PaulLiu) 


* Package name    : node-mqtt-connection
  Version : 4.0.0
  Upstream Author : mqtt-connection contributors
* URL : https://github.com/mqttjs/mqtt-connection
* License : Expat
  Programming Lang: JavaScript
  Description : Barebone Connection object for MQTT
 This library uses mqtt-packet for generating and parsing MQTT packets. It
 works over any kind of binary Streams. For example, TCP, TLS, and
WebSocket.
 .
 Node.js is an event-based server-side JavaScript engine.





signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-mqtt-connection
Source-Version: 4.0.0-1
Done: Ying-Chun Liu (PaulLiu) 

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

Debian distribution maintenance software
pp.
Ying-Chun Liu (PaulLiu)  (supplier of updated 
node-mqtt-connection 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: Thu, 06 Feb 2020 02:30:57 +0800
Source: node-mqtt-connection
Binary: node-mqtt-connection
Architecture: source all
Version: 4.0.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Javascript Maintainers 

Changed-By: Ying-Chun Liu (PaulLiu) 
Description:
 node-mqtt-connection - Barebone Connection object for MQTT
Closes: 950749
Changes:
 node-mqtt-connection (4.0.0-1) unstable; urgency=low
 .
   [ Ying-Chun Liu (PaulLiu)  ]
   * Initial release (Closes: #950749)
Checksums-Sha1:
 a8af093af2d43ff272b0b58f4a2fbe8d894f2b90 2348 node-mqtt-connection_4.0.0-1.dsc
 f171f08edb113c880c67d5cca29b081338139f1e 11718 
node-mqtt-connection_4.0.0.orig.tar.gz
 4299e042fab35865eed50176a234a64fdb64f80f 2292 
node-mqtt-connection_4.0.0-1.debian.tar.xz
 cde6a49b9b5a0a0a0e3e6169bf7d6d6504adee00 8664 
node-mqtt-connection_4.0.0-1_all.deb
 aeed0d1ede09d91ee678f13569390f5a2cba34dc 12198 
node-mqtt-connection_4.0.0-1_amd64.buildinfo
Checksums-Sha256:
 a6de79898854e3c4dbc1d2d962a7a518a0a489fcbd1e70b984096dcd5d2a345b 2348 
node-mqtt-connection_4.0.0-1.dsc
 39c6a72790528bc62d2f6fd34e920dd0e129e0fa6f7e85f387154400d2e03dd1 11718 
node-mqtt-connection_4.0.0.orig.tar.gz
 4123dd6483ab245d26558cabf0c663d6c84982e333ed865c387a9385d0b06e90 2292 
node-mqtt-connection_4.0.0-1.debian.tar.xz
 2a2232623163c458824333ad81ae4d80433ee15463488fcf482afe055a631652 8664 
node-mqtt-connection_4.0.0-1_all.deb
 48cf87286cd75c2ce7dd4d3ea9de4d0dab738ebcc97304b8dfbde67694cfc985 12198 
node-mqtt-connection_4.0.0-1_amd64.buildinfo
Files:
 a99f36f0e2e8731309690b58136268b4 2348 javascript optional 
node-mqtt-connection_4.0.0-1.dsc
 27a5afcdd463fe3e2a119e5d641f250a 11718 javascript optional 
node-mqtt-connection_4.0.0.orig.tar.gz
 1948227c22a858467ab4c1951cb64e14 2292 javascript optional 
node-mqtt-connection_4.0.0-1.debian.tar.xz
 69d32e92b11a0742470ffd10060eaf30 8664 javascript optional 
node-mqtt-connection_4.0.0-1_all.deb
 0d97de98e58f6a8fb14e32c0cbf8cf84 12198 javascript optional 
node-mqtt-connection_4.0.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAl5Bp58THHBhdWxsaXVA
ZGViaWFuLm9yZwAKCRBEFz+hPQWIiOqwEACT3tMA/NFtPgT7+E+UPM6G1HzFNmmF
JImQrQLkdB7oClritWIPMen+g8nVJzm99r7Ukqn/iBnuPlBCE3vqIzTBdZ6Vd89v
cbFrcLCsH8ENZMYQbioAIqCJAT8Aq5vpL5kcIVJG3lkS4WLjBWy4QNY6jbJsvKv/
5CrWuEweC8jtKDp+iUuKi5pIboSNSiBTGU9VTMKAPq8c1Z9HrzH/DfXRkKRKCOfd
5eVWToB6fmPzZJSi0qa2ZitGedpcq2mPkBqOr4HF6Gq1XmHfzqcZA5IqpB0SzTMu
3hkog+TpFXUSTx4PRB6ko1Xw1aXp1iohHwlToqhImFKryCRmUCx2eaPRWcrJ1e8u
RlTJrYWUuC7LAXaOG9HWKP4BikhX8ETHF7TqPco1HWeLw3ahwaoSWfvI4Ew4ajKX

Bug#953757: marked as done (neomutt: Occasional segfault on New Message (pager.c:2425))

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 00:51:17 +
with message-id 
and subject line Bug#953757: fixed in neomutt 20191207+dfsg.1-1.1
has caused the Debian Bug report #953757,
regarding neomutt: Occasional segfault on New Message (pager.c:2425)
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.)


-- 
953757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: neomutt
Version: 20191207+dfsg.1-1
Severity: normal
Tags: patch upstream

Upstream issue https://github.com/neomutt/neomutt/issues/2038
Upstream patch: https://github.com/neomutt/neomutt/pull/2039

While reading a message, "New mail in this mailbox" appears and then *boom*.

gdb:
Program received signal SIGSEGV, Segmentation fault.
0x562c12c68ba2 in mutt_pager (banner=banner@entry=0x0, fname=, flags=flags@entry=66, 
extra=extra@entry=0x7ffe04fe0130) at ../pager.c:2425
2425../pager.c: No such file or directory.
(gdb) p e
$1 = (struct Email *) 0x0
(gdb) bt
#0  0x562c12c68ba2 in mutt_pager
(banner=banner@entry=0x0, fname=, flags=flags@entry=66, 
extra=extra@entry=0x7ffe04fe0130)
at ../pager.c:2425
#1  0x562c12c1f09a in mutt_display_message (win=, 
m=0x562c134a5e90, e=e@entry=0x562c140620b0)
at ../commands.c:362
#2  0x562c12c3edaa in mutt_index_menu () at ../index.c:2512
#3  0x562c12c15371 in main (argc=, argv=0x7ffe04fe3868, 
envp=) at ../main.c:1254
(gdb) 

-- Package-specific info:
NeoMutt 20191207
Copyright (C) 1996-2016 Michael R. Elkins and others.
NeoMutt comes with ABSOLUTELY NO WARRANTY; for details type 'neomutt -vv'.
NeoMutt is free software, and you are welcome to redistribute it
under certain conditions; type 'neomutt -vv' for details.

System: Linux 5.4.0-3-amd64 (x86_64)
ncurses: ncurses 6.2.20200212 (compiled with 6.2.20200212)
libidn: 1.33 (compiled with 1.33)
GPGme: 1.13.1-unknown
libnotmuch: 5.2.0
hcache backends: tokyocabinet

Configure options: --build=x86_64-linux-gnu --prefix=/usr 
{--includedir=${prefix}/include} {--mandir=${prefix}/share/man} 
{--infodir=${prefix}/share/info} --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules {--libdir=${prefix}/lib/x86_64-linux-gnu} 
{--libexecdir=${prefix}/lib/x86_64-linux-gnu} --disable-maintainer-mode 
--disable-dependency-tracking --mandir=/usr/share/man --libexecdir=/usr/libexec 
--with-mailpath=/var/mail --gpgme --lua --notmuch --with-ui --gnutls --gss 
--idn --mixmaster --sasl --tokyocabinet

Compilation CFLAGS: -g -O2 
-fdebug-prefix-map=/build/neomutt-KUFXeJ/neomutt-20191207+dfsg.1=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c99 
-D_ALL_SOURCE=1 -D_GNU_SOURCE=1 -D__EXTENSIONS__ -I/usr/include 
-I/usr/include/lua5.3 -DNCURSES_WIDECHAR -isystem /usr/include/mit-krb5

Default options:
  +attach_headers_color +compose_to_sender +compress +cond_date +debug 
  +encrypt_to_self +forgotten_attachments +forwref +ifdef +imap +index_color 
  +initials +limit_current_thread +multiple_fcc +nested_if +new_mail +nntp +pop 
  +progress +quasi_delete +regcomp +reply_with_xorig +sensible_browser +sidebar 
  +skip_quoted +smtp +status_color +timeout +tls_sni +trash 

Compile options:
  -autocrypt +bkgdset +color +curs_set +fcntl -flock -fmemopen +futimens 
  +getaddrinfo +gnutls +gpgme +gss +hcache -homespool +idn +inotify 
  -locales_hack +lua +meta +mixmaster +nls +notmuch -openssl +pgp +sasl +smime 
  -sqlite +start_color +sun_attachment +typeahead 
MAILPATH="/var/mail"
MIXMASTER="mixmaster"
PKGDATADIR="/usr/share/neomutt"
SENDMAIL="/usr/sbin/sendmail"
SYSCONFDIR="/etc"

To learn more about NeoMutt, visit: https://neomutt.org
If you find a bug in NeoMutt, please raise an issue at:
https://github.com/neomutt/neomutt/issues
or send an email to: 

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

Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_ZA.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 neomutt depends on:
ii  libc6 2.29-10
ii  libgnutls30   3.6.12-2
ii  libgpg-error0 1.37-1
ii  libgpgme111.13.1-6
ii  libgssapi-krb5-2  1.17-6
ii  libidn11  1.33-2.2
ii  liblua5.3-0   5.3.3-1.1+b1
ii  

Bug#948895: marked as done (neomutt: FTBFS: test failure)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 00:51:17 +
with message-id 
and subject line Bug#948895: fixed in neomutt 20191207+dfsg.1-1.1
has caused the Debian Bug report #948895,
regarding neomutt: FTBFS: test failure
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.)


-- 
948895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: neomutt
Version: 2019+dfsg.1-1
Severity: serious
Tags: ftbfs

Dear maintainer,

your package failed to rebuild in a standard sid chroot:

test/neomutt-test
Test test_mutt_addr_cat...  [ OK ]
Test test_mutt_addr_cmp...  [ OK ]
Test test_mutt_addr_copy... [ OK ]
...
Test test_mutt_date_gmtime...   [ OK ]
Test test_mutt_date_is_day_name...  [ OK ]
Test test_mutt_date_localtime...[ FAILED ]
  Case December, 2000:
mutt_date_localtime.c:36: Check tm.tm_hour == 12... failed
  Case June, 2000:
mutt_date_localtime.c:48: Check (tm.tm_hour == 12) || (tm.tm_hour == 11)... 
failed
  hour = 23
mutt_date_localtime.c:51: Check tm.tm_mday == 25... failed
mutt_date_localtime.c:54: Check tm.tm_wday == 0... failed
mutt_date_localtime.c:55: Check tm.tm_yday == 176... failed
  Case Today:
mutt_date_localtime.c:61: Check tm.tm_yday >= 119... failed
Test test_mutt_date_localtime_format... [ FAILED ]
  mutt_date_localtime_format.c:49: Check result == true... failed
Test test_mutt_date_local_tz... [ OK ]
Test test_mutt_date_make_date...[ OK ]
Test test_mutt_date_make_imap...[ FAILED ]
  mutt_date_make_imap.c:43: Check result == true... failed
Test test_mutt_date_make_time...[ FAILED ]
  Case {0,0,0,1,0,1,0} = 9223372036854775807:
mutt_date_make_time.c:74: Check result == 946684800... failed
Test test_mutt_date_make_tls... [ OK ]
Test test_mutt_date_normalize_time...   [ OK ]
Test test_mutt_date_parse_date...   [ OK ]
...
Test test_url_tobuffer...   [ OK ]
Test test_url_tostring...   [ OK ]
FAILED: 4 of 377 unit tests have failed.
make[1]: *** [Makefile:1150: test] Error 1
make[1]: Leaving directory 
'/build/1st/neomutt-2019+dfsg.1/obj-x86_64-linux-gnu'
dh_auto_test: cd obj-x86_64-linux-gnu && make -j15 test VERBOSE=1 returned exit 
code 2
make: *** [debian/rules:20: build] Error 255
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: neomutt
Source-Version: 20191207+dfsg.1-1.1
Done: Stefano Rivera 

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

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

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated neomutt 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: Thu, 19 Mar 2020 17:09:59 -0700
Source: neomutt
Architecture: source
Version: 20191207+dfsg.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Mutt maintainers 
Changed-By: Stefano Rivera 
Closes: 948895 953757
Changes:
 neomutt (20191207+dfsg.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix segfault in pager on new message received. (Closes: #953757)
   * Fix FTBFS in non-UTC timezone. (Closes: #948895)
Checksums-Sha1:
 bf99aecf42d5b235ad4cbafbb933c493140c062b 1694 neomutt_20191207+dfsg.1-1.1.dsc
 105a7dd075f196302d356e7d8e9404f1ff60b17a 21172 
neomutt_20191207+dfsg.1-1.1.debian.tar.xz
 a39727e88a10cf2fa80fb90b4bb34069e100649d 5225 
neomutt_20191207+dfsg.1-1.1_source.buildinfo
Checksums-Sha256:
 

Bug#952039: marked as done (ruby-graphviz: FTBFS: ERROR: Test "ruby2.7" failed: /<>/test/output/dot/hello_test.rb:18:in `': undefined method `graph' for nil:NilClass (NoMe

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 00:34:27 +
with message-id 
and subject line Bug#952039: fixed in ruby-graphviz 1.2.5-1
has caused the Debian Bug report #952039,
regarding ruby-graphviz: FTBFS: ERROR: Test "ruby2.7" failed: 
/<>/test/output/dot/hello_test.rb:18:in `': 
undefined method `graph' for nil:NilClass (NoMethodError)
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.)


-- 
952039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-graphviz
Version: 1.2.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> /<>/test/output/dot/hello_test.rb:18:in `': 
> undefined method `graph' for nil:NilClass (NoMethodError)
>   from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in 
> `require'
>   from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in 
> `require'
>   from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:17:in `block in 
> '
>   from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:5:in `select'
>   from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:5:in `'
> rake aborted!
> Command failed with status (1): [ruby -w -I"test"  
> "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
> "test/output/dot/hello_test.rb" "test/output/dot/test_parse.rb" 
> "test/output/rgv/test_rgv.rb" "test/test_dot_script.rb" 
> "test/test_examples.rb" "test/test_graph.rb" "test/test_search.rb" 
> "test/test_subgraph.rb" "test/test_theory.rb" "test/test_types.rb" 
> "test/test_utils_colors.rb" -v]
> 
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby2.7" failed: 

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/ruby-graphviz_1.2.3-1_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: ruby-graphviz
Source-Version: 1.2.5-1
Done: Daniel Leidert 

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

Debian distribution maintenance software
pp.
Daniel Leidert  (supplier of updated ruby-graphviz package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 25 Mar 2020 01:10:06 +0100
Source: ruby-graphviz
Architecture: source
Version: 1.2.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Daniel Leidert 
Closes: 952039
Changes:
 ruby-graphviz (1.2.5-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release.
 - Fixes Ruby2.7 build issues.
 .
   [ Debian Janitor ]
   * Bump debhelper from old 11 to 12.
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
 .
   [ Daniel Leidert ]
   * d/control: Add Rules-Requires-Root field.
 (Standards-Version): Bump to 4.5.0.
 (Depends): Remove ruby-interpreter.
   * d/copyright: Add Upstream-Contact.
 (Source): Use github release page.
   * d/ruby-graphviz.docs: Install README.md.
   * d/ruby-graphviz.lintian-overrides: Update.
   * d/ruby-tests.rake: Don't run files in sub-directories copied from the
 examples directory (closes: #952039). Be verbose and show warnings.
   * d/rules: Remove obsolete pango related G_HOME environment variable. Use gem
 install layout.
 (override_dh_installchangelogs): Install CHANGELOG.md.
   * d/watch: Use github release page.
   * d/upstream/metadata: Add YAML markup, and Archive and Changelog fields.
Checksums-Sha1:
 7c01c1dc4634c4c3e07990b77c1d27ebf82a48f6 2066 

Bug#950756: marked as done (plover: Please make another source-only upload to allow testing migration)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 00:34:12 +
with message-id 
and subject line Bug#950756: fixed in plover 4.0.0~dev8~66~g685bd33-2
has caused the Debian Bug report #950756,
regarding plover: Please make another source-only upload to allow testing 
migration
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.)


-- 
950756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plover
Version: 4.0.0~dev8~66~g685bd33-1
Severity: important

Dear plover maintainer,

Your last upload of plover in Debian was the first upload. As a result, it was
not a source-only upload. Please make another source-only upload to allow the
package to migrate to Testing. You may find details about source-only upload
at https://wiki.debian.org/SourceOnlyUpload .

-- 
Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: plover
Source-Version: 4.0.0~dev8~66~g685bd33-2
Done: Harlan Lieberman-Berg 

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

Debian distribution maintenance software
pp.
Harlan Lieberman-Berg  (supplier of updated plover 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Mar 2020 20:02:17 -0400
Source: plover
Architecture: source
Version: 4.0.0~dev8~66~g685bd33-2
Distribution: unstable
Urgency: medium
Maintainer: Harlan Lieberman-Berg 
Changed-By: Harlan Lieberman-Berg 
Closes: 950756
Changes:
 plover (4.0.0~dev8~66~g685bd33-2) unstable; urgency=medium
 .
   * Rebuild for source-only upload. (Closes: #950756)
Checksums-Sha1:
 56dd41a1cfb2afb6fde1f7b8bf72b816d7b61498 2412 
plover_4.0.0~dev8~66~g685bd33-2.dsc
 2d6a5c109f67fe0810829171dff2fbb24a0c4118 9596 
plover_4.0.0~dev8~66~g685bd33-2.debian.tar.xz
 e45f18985f7d86364f6f52590b998310619c6928 10461 
plover_4.0.0~dev8~66~g685bd33-2_amd64.buildinfo
Checksums-Sha256:
 98ea287d200b5a8e9c4fd5bb44280481674034fcab7084dfde3e775c61512d11 2412 
plover_4.0.0~dev8~66~g685bd33-2.dsc
 c3a3748ceb979903f92b0ccef524a9c23262b14c0f88f401c29ddef1e1ba54a0 9596 
plover_4.0.0~dev8~66~g685bd33-2.debian.tar.xz
 f841575ebfe0e7108426eba00dd01b511089352be0fb3e74854489a0ebf3a144 10461 
plover_4.0.0~dev8~66~g685bd33-2_amd64.buildinfo
Files:
 1daaa4adf670ebf7e61e21f88a67b136 2412 utils optional 
plover_4.0.0~dev8~66~g685bd33-2.dsc
 97ab05b95a21b2f11837fbe8d8e8979c 9596 utils optional 
plover_4.0.0~dev8~66~g685bd33-2.debian.tar.xz
 7b4b98a1e91c1e71b5cb2980e8bb267c 10461 utils optional 
plover_4.0.0~dev8~66~g685bd33-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKqBAEBCgCUFiEEYveV1JOn7SmlGhxBnX5VYE2Rn4MFAl56ozFfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy
Rjc5NUQ0OTNBN0VEMjlBNTFBMUM0MTlEN0U1NTYwNEQ5MTlGODMWHGhsaWViZXJt
YW5AZGViaWFuLm9yZwAKCRCdflVgTZGfg3AfD/94BrgHvGdE7VOwT1nvXJqlJ6mE
kyCtLAiRxx1+TgfOHx2j3kmrOlrAejnA5WyS5gObFLF/MlYARrnfkGxZddTVmK3o
Dr46iKJNP0ArJodNa9aN+7FJezFqbD1UMqO4faKF43p5JJO6F0B80HjSaUoqydPM
nfjfVrF+fjMi7ZjDATWXZlyH3ijB9Nr5AOw81peu66hdy5fRyDY2rcnK7yD9KzO/
fG6cJN2/c8wrHRzbuCNu4GnRtvBUYfNjBqYFXHjWOZHYzOTGND7BiUM9YQtUJGgx
mH+hurxZaah3erEmQUJBw83f+YHR/WdlYIG5RpjB9zpBc3IMKbY6LGHpBZz3KDET
VcpUB3oS3zPT8fdYCpKjvi2Ck63ulxuv4tC9cKgauI9Avai3/LO6wG/0AWmqBpgj
ShvBT0BUOx9NKOeLLWzwb2ucDsy9aw759d6u/9OLjmyqLkKcfZ/N44qmC+RE9Ujc
jNXrf3j3Z5AZavNbtXudITPHmvZsjDkFKF7GDHPlkANLCSku0GLQRKemjuHVRiv/
DWyIpX2QVWxWfJGEAWWnu9RZZ+rMpNj9GChtdr/6J3HeDwr/6yJRu3vF5YuETfRQ
U2KfBxAf70ffI4vG9Y9RvLi5jOV8mT3nPhhJDVD0DZE4e1M5VxIPWB/aYHJB7HtK
B3pTx7inJoxQZ+elGw==
=SMrp
-END PGP SIGNATURE End Message ---

Bug#954374: marked as done (libc6: please make maintainerscript compatible with busybox)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 22:51:36 +
with message-id 
and subject line Bug#954374: fixed in glibc 2.30-3
has caused the Debian Bug report #954374,
regarding libc6: please make maintainerscript compatible with busybox
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.)


-- 
954374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.30-2
Severity: wishlist

Hi,

would it be possible to make the libc6 preinst maintainer script
compatible with busybox? Currently the preinst script calls "readlink
-m" which is not supported by busybox. Hence the following error will be
thrown:

BusyBox v1.30.1 (Debian 1:1.30.1-4) multi-call binary.

Usage: readlink [-fnv] FILE

Display the value of a symlink

-f  Canonicalize by following all symlinks
-n  Don't add newline
-v  Verbose

I tried to prepare a patch for the preinst script but ran into a FTBFS:

x86_64-linux-gnu-gcc-9   -shared -static-libgcc -Wl,-O1  -Wl,-z,defs 
-Wl,-dynamic-linker=/lib64/ld-linux-x86-64.so.2  
-B/<>/build-tree/amd64-libc/csu/  
-Wl,--version-script=/<>/build-tree/amd64-libc/libnss_files.map 
-Wl,-soname=libnss_files.so.2 -Wl,-z,combreloc -Wl,-z,relro 
-Wl,--hash-style=both   -L/<>/build-tree/amd64-libc 
-L/<>/build-tree/amd64-libc/math 
-L/<>/build-tree/amd64-libc/elf 
-L/<>/build-tree/amd64-libc/dlfcn 
-L/<>/build-tree/amd64-libc/nss 
-L/<>/build-tree/amd64-libc/nis 
-L/<>/build-tree/amd64-libc/rt 
-L/<>/build-tree/amd64-libc/resolv 
-L/<>/build-tree/amd64-libc/mathvec 
-L/<>/build-tree/amd64-libc/support 
-L/<>/build-tree/amd64-libc/nptl 
-Wl,-rpath-link=/<>/build-tree/amd64-libc:/<>/build-tree/amd64-libc/math:/<>/build-tree/amd64-libc/elf:/<>/build-tree/amd64-libc/dlfcn:/<>/build-tree/amd64-libc/nss:/<>/build-tree/amd64-libc/nis:/<>/build-tree/amd64-libc/rt:/<>/build-tree/amd64-libc/resolv:/<>/build-tree/amd64-libc/mathvec:/<>/build-tree/amd64-libc/support:/<>/build-tree/amd64-libc/nptl
 -o /<>/build-tree/amd64-libc/nss/libnss_files.so  
/<>/build-tree/amd64-libc/csu/abi-note.o -Wl,--whole-archive 
/<>/build-tree/amd64-libc/nss/libnss_files_pic.a 
-Wl,--no-whole-archive   -Wl,--start-group 
/<>/build-tree/amd64-libc/linkobj/libc.so 
/<>/build-tree/amd64-libc/libc_nonshared.a -Wl,--as-needed 
/<>/build-tree/amd64-libc/elf/ld.so -Wl,--no-as-needed 
-Wl,--end-group
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libselinux.so: 
undefined reference to `gettid@GLIBC_2.30'
collect2: error: ld returned 1 exit status

Thus, I'm now reporting this wishlist bug here before further working on
a fix.

Would you be willing to accept a change that makes the preinst script of
libc6 compatible with readlink from busybox?

Thanks!

cheers, josch


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

Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.30-3
Done: Aurelien Jarno 

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Mar 2020 23:31:35 +0100
Source: glibc
Architecture: source
Version: 2.30-3
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 953788 954374 954393 954715
Changes:
 glibc (2.30-3) unstable; urgency=medium
 .
   * debian/patches/git-updates.diff: update from 

Bug#953788: marked as done (glibc: CVE-2020-1752: use-after-free in glob() function when expanding ~user)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 22:51:36 +
with message-id 
and subject line Bug#953788: fixed in glibc 2.30-3
has caused the Debian Bug report #953788,
regarding glibc: CVE-2020-1752: use-after-free in glob() function when 
expanding ~user
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.)


-- 
953788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.30-2
Severity: important
Tags: security upstream
Forwarded: https://sourceware.org/bugzilla/show_bug.cgi?id=25414
Control: found -1 2.16-0experimental0
Control: found -1 2.19-18+deb8u10
Control: found -1 2.24-11+deb9u1
Control: found -1 2.24-11+deb9u4
Control: found -1 2.28-10
Control: found -1 2.29-10

Hi,

The following vulnerability was published for glibc.

CVE-2020-1752[0]:
use-after-free in glob() function when expanding ~user

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-1752
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1752
[1] https://sourceware.org/bugzilla/show_bug.cgi?id=25414

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.30-3
Done: Aurelien Jarno 

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Mar 2020 23:31:35 +0100
Source: glibc
Architecture: source
Version: 2.30-3
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 953788 954374 954393 954715
Changes:
 glibc (2.30-3) unstable; urgency=medium
 .
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix a defect in the PowerPC backtrace function that could cause an
   out-of-bounds write when executed in a signal frame context
   (CVE-2020-1751).
 - Fix use-after-free vulnerability in the glob function when expanding
   ~user (CVE-2020-1752).  Closes: #953788.
   * debian/debhelper.in/libc.preinst, debian/rules.d/debhelper.mk: determine
 ld.so ELF magic at build time instead of at run time to avoid using
 "readlink -m".  Closes: #954374.
   * debian/rules.d/build.mk: unset LANGUAGE when running the testsuite.
   * debian/testsuite-xfail-debian.mk: ignore signal/tst-minsigstksz-1 and
 signal/tst-minsigstksz-2 on i386, they fail on i386 with an AVX-512 CPUs
 due to a kernel bug.  Closes: #954715.
   * debian/control.in/libc, debian/rules.d/debhelper.mk: Make libcX-dev
 declare a Breaks against libcX-dev-${DEB_HOST_ARCH}-cross
 (<< ${CURRENT_UPSTREAM_VERSION}~).  Closes: #954393.
   * debian/control.in/libc, debian/control.in/main: drop Conflicts, Breaks and
 Replaces against package version older than the one available in
 oldstable.
Checksums-Sha1:
 9fb2b38522f65cb047693cbc019c6060534eb454 8731 glibc_2.30-3.dsc
 191c5341141d90e9d23a9aa16302937d4cfe55d1 844628 glibc_2.30-3.debian.tar.xz
 a6d2d6a834be565122a56b6445ceed6a55339dc6 7589 glibc_2.30-3_source.buildinfo
Checksums-Sha256:
 31f0fd70db8c677f9f0cd526b5a43d8d719a76291181364290f4700c516395c7 8731 
glibc_2.30-3.dsc
 8995fbf0cca7ddab0d771b79c50fe78bbec9ef30a31ee0aa83d56899de83a822 844628 
glibc_2.30-3.debian.tar.xz
 f878eda4037d5e79b438ac4af7313ace941270bbbcd41b9f379db4d7bc9e1acd 7589 
glibc_2.30-3_source.buildinfo
Files:
 02306dbedb1e825fc3af27f6d474ebb3 8731 libs required glibc_2.30-3.dsc
 7cc54067c6e3ee5929dac8b489cf2c2a 844628 libs required 
glibc_2.30-3.debian.tar.xz
 2cc1c5109fd12d759019b743b197b3a7 7589 libs required 
glibc_2.30-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl56i4oACgkQE4jA+Jno
M2tkbw/+OUUbH9cXbJ6cT21m1x6s+nzyysl9667sXqBNAtrFAffzGfIRnrqoeein

Bug#954393: marked as done (please Breaks: libc6-dev-${DEB_HOST_ARCH}-cross (<< ${CURRENT_UPSTREAM_VERSION}))

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 22:51:37 +
with message-id 
and subject line Bug#954393: fixed in glibc 2.30-3
has caused the Debian Bug report #954393,
regarding please Breaks: libc6-dev-${DEB_HOST_ARCH}-cross (<< 
${CURRENT_UPSTREAM_VERSION})
to be marked as done.

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

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


-- 
954393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-dev
Version: 2.30-2
Severity: wishlist

Every time a new glibc upstream release gets uploaded,
cross-toolchain-base breaks in difficult to diagnose ways. This seems to
happen, because gcc uses the libc6-dev:somearch headers together with
libc6-dev-somearch-cross libraries.

Would you agree to have libc6-dev declare

Breaks: libc6-dev-${DEB_HOST_ARCH}-cross (<< ${CURRENT_UPSTREAM_VERSION}~)

where CURRENT_UPSTREAM_VERSION would presently be 2.30? I think that'd
spare us from diagnosing these issues in general.

Helmut
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.30-3
Done: Aurelien Jarno 

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Mar 2020 23:31:35 +0100
Source: glibc
Architecture: source
Version: 2.30-3
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 953788 954374 954393 954715
Changes:
 glibc (2.30-3) unstable; urgency=medium
 .
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix a defect in the PowerPC backtrace function that could cause an
   out-of-bounds write when executed in a signal frame context
   (CVE-2020-1751).
 - Fix use-after-free vulnerability in the glob function when expanding
   ~user (CVE-2020-1752).  Closes: #953788.
   * debian/debhelper.in/libc.preinst, debian/rules.d/debhelper.mk: determine
 ld.so ELF magic at build time instead of at run time to avoid using
 "readlink -m".  Closes: #954374.
   * debian/rules.d/build.mk: unset LANGUAGE when running the testsuite.
   * debian/testsuite-xfail-debian.mk: ignore signal/tst-minsigstksz-1 and
 signal/tst-minsigstksz-2 on i386, they fail on i386 with an AVX-512 CPUs
 due to a kernel bug.  Closes: #954715.
   * debian/control.in/libc, debian/rules.d/debhelper.mk: Make libcX-dev
 declare a Breaks against libcX-dev-${DEB_HOST_ARCH}-cross
 (<< ${CURRENT_UPSTREAM_VERSION}~).  Closes: #954393.
   * debian/control.in/libc, debian/control.in/main: drop Conflicts, Breaks and
 Replaces against package version older than the one available in
 oldstable.
Checksums-Sha1:
 9fb2b38522f65cb047693cbc019c6060534eb454 8731 glibc_2.30-3.dsc
 191c5341141d90e9d23a9aa16302937d4cfe55d1 844628 glibc_2.30-3.debian.tar.xz
 a6d2d6a834be565122a56b6445ceed6a55339dc6 7589 glibc_2.30-3_source.buildinfo
Checksums-Sha256:
 31f0fd70db8c677f9f0cd526b5a43d8d719a76291181364290f4700c516395c7 8731 
glibc_2.30-3.dsc
 8995fbf0cca7ddab0d771b79c50fe78bbec9ef30a31ee0aa83d56899de83a822 844628 
glibc_2.30-3.debian.tar.xz
 f878eda4037d5e79b438ac4af7313ace941270bbbcd41b9f379db4d7bc9e1acd 7589 
glibc_2.30-3_source.buildinfo
Files:
 02306dbedb1e825fc3af27f6d474ebb3 8731 libs required glibc_2.30-3.dsc
 7cc54067c6e3ee5929dac8b489cf2c2a 844628 libs required 
glibc_2.30-3.debian.tar.xz
 2cc1c5109fd12d759019b743b197b3a7 7589 libs required 
glibc_2.30-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl56i4oACgkQE4jA+Jno
M2tkbw/+OUUbH9cXbJ6cT21m1x6s+nzyysl9667sXqBNAtrFAffzGfIRnrqoeein
YSmQmrPJz+M0gSMrLWT+qAGhud299JXFrbSmb5FhjtgRIX+000z5xlmaD2927iaw
hRlaVeRTLJYDiDSgLeAt4xoHBRcny41TWBBj0gu7AmFUpl3AhZ9/hGCoDbm18hAm
CZZYCBMhi7XRBwqVszl9i4QYze9+NulNniAXkUK4DXMAEBqXurteq3IfpRkvl78x
U1/Qimei4BphGP4LpGb+JDF63GT6WRbTl5X8okU0NUcfD9ZkVuMTIuYgGp86rBbz
Ou1N3nDG2eBPa3PZo6mhzFvOtRHknuPjF1HbpElwJAhYTdVchH2pU0csiHBm2efb

Bug#954874: marked as done (ruby-rspec-puppet: depends on obsolete transitional package.)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 22:52:14 +
with message-id 
and subject line Bug#954874: fixed in ruby-rspec-puppet 2.7.8-3
has caused the Debian Bug report #954874,
regarding ruby-rspec-puppet: depends on obsolete transitional package.
to be marked as done.

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

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


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

Package: ruby-rspec-puppet
Version: 2.7.8-1
Severity: serious

ruby-rspec-puppet depends on "puppet-common", this has been a transitional 
package since stretch and has now been dropped by the puppet source package.

Please change your dependency to puppet.
--- End Message ---
--- Begin Message ---
Source: ruby-rspec-puppet
Source-Version: 2.7.8-3
Done: Daniel Leidert 

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

Debian distribution maintenance software
pp.
Daniel Leidert  (supplier of updated ruby-rspec-puppet 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Mar 2020 23:25:38 +0100
Source: ruby-rspec-puppet
Architecture: source
Version: 2.7.8-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Daniel Leidert 
Closes: 954874
Changes:
 ruby-rspec-puppet (2.7.8-3) unstable; urgency=medium
 .
   * Team upload.
   * d/control (Depends): Replace puppet-common by puppet (closes: #954874).
Checksums-Sha1:
 a1f5442b455293d098d89c8778d5c1406366a074 2106 ruby-rspec-puppet_2.7.8-3.dsc
 ebaa4a997bf423558933eed4ef2cc353a59e7469  
ruby-rspec-puppet_2.7.8-3.debian.tar.xz
 a7562d0755803c9ee944c698a0b08f4609506903 9961 
ruby-rspec-puppet_2.7.8-3_amd64.buildinfo
Checksums-Sha256:
 8733af7f6282080ddc5a2f83a9a83666b77e2c888ee9157ddab0d3b85239a6fc 2106 
ruby-rspec-puppet_2.7.8-3.dsc
 21a03e71e7859dd853d2f1efe5cfdc066cff7b7f708952395214a5bc6168fb70  
ruby-rspec-puppet_2.7.8-3.debian.tar.xz
 1de78082e454dffc578a1d7dcde8d217862eb0c4bb9be62c30fcb514cc6653f7 9961 
ruby-rspec-puppet_2.7.8-3_amd64.buildinfo
Files:
 4f7e4a3e90ed4ed8d3de9e9a47c84e57 2106 ruby optional 
ruby-rspec-puppet_2.7.8-3.dsc
 be1bb5343c8cc612da0e9e3092d1279c  ruby optional 
ruby-rspec-puppet_2.7.8-3.debian.tar.xz
 bccc90ad040faa7119522070031c7228 9961 ruby optional 
ruby-rspec-puppet_2.7.8-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl56i3EACgkQS80FZ8KW
0F18MQ/+MzQTvpwIGeODjvEG8tqp48NtA/mHNPQ/zTjpfaEC+zqsXY28QfdzMwai
4TOwcXFZJ9b3fobdAMmziD5NLcb33ZsyknYRKL6yjjQEWYXdCo4SmwIcwC5I3oOK
CV9AJwWwkzWKoz8q1j50k0Axhbunv0C9mESdykGUh+F31zwZ15DAKoAYlAkTvCLQ
GQyRvU0IMzVuXOh+VzZHTLf8MrUj1az8OJggXk4BqdK+DDL4rVOZvB9FSrjw6lUK
MEVh81MWldRPjCo6evYcWSb2n0U3E9eVTqgNoKvvNNgC/co4nMI3mxvJaWsRcS9h
4OPEoboCUUmZDRuIAv9DRUwcXpNMwxv2NBMIMr55Pz4cZ1x1HFAnQZsCZVi48UMt
4oWk5q5K4C6ptQ8cva+okiEVfaJ2ZPldZnnuR4SHUsLuZBHPIwYeSELh9yyMKKie
SEBiIb4OZB79/XTqKjBetTdyzm6Js0r3VY9YtEbK40501xUMn2ylsmnT8JZKh/4S
Psq5YtSLNGUWJOWnLjvcM3EqfhiW6IW2ZDdBxsCb2XiiAN1j6bVVY46b0/zGSP9m
1HHaKEEyeGr/qhIHb9rN2ozwmFU5Eje1HTs/V8JeNa5pyqnFMJc5Mf5vXfOfLUC8
kUiBdtYFwlsHiFww1i1QgnvvceXB49zeR04sUg0d3oxrqP8ADr4=
=No0X
-END PGP SIGNATURE End Message ---

Bug#954715: marked as done (glibc: FTBFS: tests failed: signal/tst-minsigstksz-1 signal/tst-minsigstksz-2)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 22:51:37 +
with message-id 
and subject line Bug#954715: fixed in glibc 2.30-3
has caused the Debian Bug report #954715,
regarding glibc: FTBFS: tests failed: signal/tst-minsigstksz-1 
signal/tst-minsigstksz-2
to be marked as done.

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

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


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

Hi,

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

> UNSUPPORTED: elf/tst-ldconfig-bad-aux-cache
> UNSUPPORTED: elf/tst-pldd
> XPASS: elf/tst-protected1a
> XPASS: elf/tst-protected1b
> UNSUPPORTED: io/tst-getcwd-abspath
> UNSUPPORTED: misc/tst-ttyname
> UNSUPPORTED: nptl/test-cond-printers
> UNSUPPORTED: nptl/test-condattr-printers
> UNSUPPORTED: nptl/test-mutex-printers
> UNSUPPORTED: nptl/test-mutexattr-printers
> UNSUPPORTED: nptl/test-rwlock-printers
> UNSUPPORTED: nptl/test-rwlockattr-printers
> XPASS: nptl/tst-cancel24-static
> XPASS: nptl/tst-cleanupx4
> XPASS: nptl/tst-create-detached
> UNSUPPORTED: nss/tst-nss-db-endgrent
> UNSUPPORTED: nss/tst-nss-db-endpwent
> UNSUPPORTED: nss/tst-nss-files-alias-leak
> UNSUPPORTED: nss/tst-nss-files-alias-truncated
> UNSUPPORTED: nss/tst-nss-files-hosts-erange
> UNSUPPORTED: nss/tst-nss-files-hosts-getent
> UNSUPPORTED: nss/tst-nss-files-hosts-long
> UNSUPPORTED: nss/tst-nss-files-hosts-multi
> UNSUPPORTED: nss/tst-nss-test3
> UNSUPPORTED: posix/tst-sysconf-empty-chroot
> UNSUPPORTED: resolv/tst-resolv-ai_idn
> UNSUPPORTED: resolv/tst-resolv-ai_idn-latin1
> UNSUPPORTED: resolv/tst-resolv-res_init
> UNSUPPORTED: resolv/tst-resolv-res_init-thread
> UNSUPPORTED: resolv/tst-resolv-threads
> XPASS: rt/tst-cpuclock2
> XPASS: rt/tst-cputimer1
> XPASS: rt/tst-timer
> FAIL: signal/tst-minsigstksz-1
> FAIL: signal/tst-minsigstksz-2
> UNSUPPORTED: sunrpc/tst-svc_register
> UNSUPPORTED: time/tst-y2039
> Summary of test results:
>   2 FAIL
>5971 PASS
>  27 UNSUPPORTED
>  17 XFAIL
>   8 XPASS
> make[2]: *** [Makefile:429: tests] Error 1
> [...]
> --
> FAIL: signal/tst-minsigstksz-1
> original exit status 1
> Didn't expect signal from child: got `Segmentation fault'
> --
> --
> FAIL: signal/tst-minsigstksz-2
> original exit status 1
> Incorrect signal from child: got `Segmentation fault', need `Aborted'
> --
> +-+
> | Encountered regressions that don't match expected failures. |
> +-+
> FAIL: signal/tst-minsigstksz-1
> FAIL: signal/tst-minsigstksz-2

The full build log is available from:
   http://qa-logs.debian.net/2020/03/22/glibc_2.30-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: glibc
Source-Version: 2.30-3
Done: Aurelien Jarno 

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Mar 2020 23:31:35 +0100
Source: glibc
Architecture: source
Version: 2.30-3
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 953788 954374 954393 954715
Changes:
 glibc (2.30-3) unstable; urgency=medium
 .
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix a defect in the PowerPC backtrace function that could cause an
   

Bug#954798: marked as done (lintian: field-too-long checksums-sha256 error)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 15:48:16 -0700
with message-id 

and subject line Re: Bug#954798: lintian: field-too-long checksums-sha256 error
has caused the Debian Bug report #954798,
regarding lintian: field-too-long checksums-sha256 error
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.)


-- 
954798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.59.0
Severity: normal

Dear Maintainer,

   * What led up to the situation?
 sbuild -d unstable for the latest version of my package budgie-extras
 threw a policy errors for this particular field

E: budgie-extras changes: field-too-long Checksums-Sha256 (5432 chars > 5000)
E: budgie-extras buildinfo: field-too-long Checksums-Sha256 (5321 chars > 5000)

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

Note - no additional binaries were added in this upload - the new
version of lintian threw up these issues
   * What was the outcome of this action?
 E: budgie-extras changes: field-too-long Checksums-Sha256 (5432
chars > 5000)
 E: budgie-extras buildinfo: field-too-long Checksums-Sha256 (5321
chars > 5000)
   * What outcome did you expect instead?
 I wasnt expecting this issue.  It does seem a little restrictive especially
 since the sha256 field checksum for each of the binaries is relatively long
 as you would expect.
 I suppose I could "split" the package rather artificially - maybe
 one python based binaries and one vala based binaries with the current
 budgie-extras package as a "metapackage" - I'm really seeking advice
 how too proceed - I don't want to upload the fixes with these
 lintian errors that break policy

attached are the changes and buildinfo files


budgie-extras_0.94.0-1_amd64.buildinfo
Description: Binary data


budgie-extras_0.94.0-1_amd64.changes
Description: Binary data
--- End Message ---
--- Begin Message ---
Hi,

On Tue, Mar 24, 2020 at 9:12 AM Mattia Rizzolo  wrote:
>
> On Tue, Mar 24, 2020 at 09:04:52AM -0700, Felix Lechner wrote:
> > I will disable this check for buildinfo files later today.
>
> (and .changes please :))

This bug will be closed by the upcoming commit:


https://salsa.debian.org/lintian/lintian/-/commit/db07aa46bd3afa61cc3508ed4f15c26db98b0c1e

Unfortunately, I mentioned the wrong bug number. Closing manually.

Kind regards
Felix Lechner--- End Message ---

Bug#890635: marked as done (chkrootkit: Errors when trying to exclude known false positives)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 23:04:42 +0100
with message-id <42ffe1dab6ec742b181da8b90cc4096e3b76cd88.ca...@gmail.com>
and subject line Bug closed
has caused the Debian Bug report #890635,
regarding chkrootkit: Errors when trying to exclude known false positives
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.)


-- 
890635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chkrootkit
Version: 0.50-4+b2
Severity: important

Dear Maintainer,

I have installed both fail2ban and chkrootkit on Debian Stretch. It is not the
system I'm writing this report from. When running chkrootkit, it complains
about hidden files from fail2ban:

===
$ sudo chkrootkit -q

/usr/lib/python3/dist-packages/fail2ban/tests/files/config/apache-
auth/basic/file/.htpasswd /usr/lib/python3/dist-
packages/fail2ban/tests/files/config/apache-auth/basic/file/.htaccess
/usr/lib/python3/dist-packages/fail2ban/tests/files/config/apache-
auth/basic/authz_owner/.htpasswd /usr/lib/python3/dist-
packages/fail2ban/tests/files/config/apache-auth/basic/authz_owner/.htaccess
/usr/lib/python3/dist-packages/fail2ban/tests/files/config/apache-
auth/digest_anon/.htpasswd /usr/lib/python3/dist-
packages/fail2ban/tests/files/config/apache-auth/digest_anon/.htaccess
/usr/lib/python3/dist-packages/fail2ban/tests/files/config/apache-
auth/digest/.htpasswd /usr/lib/python3/dist-
packages/fail2ban/tests/files/config/apache-auth/digest/.htaccess
/usr/lib/python3/dist-packages/fail2ban/tests/files/config/apache-
auth/digest_time/.htpasswd /usr/lib/python3/dist-
packages/fail2ban/tests/files/config/apache-auth/digest_time/.htaccess
/usr/lib/python3/dist-packages/fail2ban/tests/files/config/apache-
auth/digest_wrongrelm/.htpasswd /usr/lib/python3/dist-
packages/fail2ban/tests/files/config/apache-auth/digest_wrongrelm/.htaccess
/usr/lib/python3/dist-packages/fail2ban/tests/files/config/apache-
auth/noentry/.htaccess
===

When attempting to tell chkrootkit to exclude those files, chkrootkit errors
with a weird error:

===
$ sudo chkrootkit -q -e '/usr/lib/python3/dist-
packages/fail2ban/tests/files/config/apache-auth/basic/file/.htpasswd
/usr/lib/python3/dist-packages/fail2ban/tests/files/config/apache-
auth/basic/file/.htaccess /usr/lib/python3/dist-
packages/fail2ban/tests/files/config/apache-auth/basic/authz_owner/.htpasswd
/usr/lib/python3/dist-packages/fail2ban/tests/files/config/apache-
auth/basic/authz_owner/.htaccess /usr/lib/python3/dist-
packages/fail2ban/tests/files/config/apache-auth/digest_anon/.htpasswd
/usr/lib/python3/dist-packages/fail2ban/tests/files/config/apache-
auth/digest_anon/.htaccess /usr/lib/python3/dist-
packages/fail2ban/tests/files/config/apache-auth/digest/.htpasswd
/usr/lib/python3/dist-packages/fail2ban/tests/files/config/apache-
auth/digest/.htaccess /usr/lib/python3/dist-
packages/fail2ban/tests/files/config/apache-auth/digest_time/.htpasswd
/usr/lib/python3/dist-packages/fail2ban/tests/files/config/apache-
auth/digest_time/.htaccess /usr/lib/python3/dist-
packages/fail2ban/tests/files/config/apache-auth/digest_wrongrelm/.htpasswd
/usr/lib/python3/dist-packages/fail2ban/tests/files/config/apache-
auth/digest_wrongrelm/.htaccess /usr/lib/python3/dist-
packages/fail2ban/tests/files/config/apache-auth/noentry/.htaccess'

 The tty of the following user process(es) were not found
 in /var/run/utmp !
! RUID  PID TTYCMD
! grelm/.htpasswd   0 l2ban/tests/files/config/apache-augrelm/.htpasswd
/usr/lib/python3/dist-packages/fail2ban/tests/files/config/apache-
auth/digest_wrongrelm/.htaccess /usr/lib/python3/dist-
packages/fail2ban/tests/files/config/apache-auth/noentry/.htaccess
! wd  0 iles/config/apache-auth/digest_wrowd /usr/lib/python3/dist-
packages/fail2ban/tests/files/config/apache-auth/digest_wrongrelm/.htaccess
/usr/lib/python3/dist-packages/fail2ban/tests/files/config/apache-
auth/noentry/.htaccess
===

Just to assure you, those files do infact exist and there doesn't seem to be
any typo or special character in there, as ls finds those files just fine:

===
$ ls -lbh /usr/lib/python3/dist-packages/fail2ban/tests/files/config/apache-
auth/basic/file/.htpasswd /usr/lib/python3/dist-
packages/fail2ban/tests/files/config/apache-auth/basic/file/.htaccess
/usr/lib/python3/dist-packages/fail2ban/tests/files/config/apache-
auth/basic/authz_owner/.htpasswd /usr/lib/python3/dist-
packages/fail2ban/tests/files/config/apache-auth/basic/authz_owner/.htaccess
/usr/lib/python3/dist-packages/fail2ban/tests/files/config/apache-

Bug#954777: marked as done (ITP: augur -- pipeline components for real-time virus analysis)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 22:00:10 +
with message-id 
and subject line Bug#954777: fixed in augur 6.4.2-1
has caused the Debian Bug report #954777,
regarding ITP: augur -- pipeline components for real-time virus analysis
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.)


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

Subject: ITP: augur -- pipeline components for real-time virus analysis
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: augur
  Version : 6.4.2
  Upstream Author : Trevor Bedford and Richard Neher
* URL : https://github.com/nextstrain/augur
* License : AGPL-3+
  Programming Lang: Python
  Description : pipeline components for real-time virus analysis
 The nextstrain project is an attempt to make flexible informatic
 pipelines and visualization tools to track ongoing pathogen evolution as
 sequence data emerges. The nextstrain project derives from nextflu,
 which was specific to influenza evolution.
 .
 nextstrain is comprised of three components:
 .
   * fauna: database and IO scripts for sequence and serological data
   * augur: informatic pipelines to conduct inferences from raw data
   * auspice: web app to visualize resulting inferences

Remark: This package is maintained by Debian Med Packaging Team at
   https://salsa.debian.org/med-team/augur
--- End Message ---
--- Begin Message ---
Source: augur
Source-Version: 6.4.2-1
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated augur 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: Mon, 23 Mar 2020 15:03:35 +0100
Source: augur
Binary: augur
Architecture: source all
Version: 6.4.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 augur  - pipeline components for real-time virus analysis
Closes: 954777
Changes:
 augur (6.4.2-1) unstable; urgency=medium
 .
   * Initial release (Closes: #954777)
Checksums-Sha1:
 1dc078e0a6df93bd526ae054f2001475c767cb2e 2131 augur_6.4.2-1.dsc
 bc62f947d9a4e5ac8c317dd51f429b631332d6ee 10947203 augur_6.4.2.orig.tar.gz
 ef75148f8ba88c00e42d98f22091713664e56960 13120 augur_6.4.2-1.debian.tar.xz
 48dd86cffc15a75046c1ffcc1a80e53cd8dfb4d6 129800 augur_6.4.2-1_all.deb
 c694bcfed7b25d2510b7ab13c66b89b4848ebdb9 7617 augur_6.4.2-1_amd64.buildinfo
Checksums-Sha256:
 7d3cb8c3ec46a3661df9858644844138cb85b2fd3d986a04b526de6b38629d43 2131 
augur_6.4.2-1.dsc
 c25b55d15dceba639b02b5ee088d73b1e10e1698d8348def59fcdf0524c90653 10947203 
augur_6.4.2.orig.tar.gz
 d9fb8c39017311dd74f41fe2b2cdc1ab9a34cbce399283970408100b226447fd 13120 
augur_6.4.2-1.debian.tar.xz
 21fd7f4c9f382c0598a522ce24b60b770b0f5dddcb81c674bf26b63b736134bd 129800 
augur_6.4.2-1_all.deb
 0cf207c52a73aa460fc9a563ad575d6b3d5216340a7c1cfb86e5badd0b154adb 7617 
augur_6.4.2-1_amd64.buildinfo
Files:
 18c3bbc1287e66992f43b68e9826b259 2131 science optional augur_6.4.2-1.dsc
 c404b11842e225434aa4bb70613e2a30 10947203 science optional 
augur_6.4.2.orig.tar.gz
 917a10b41b030f9f27cd7e0a4b0755b1 13120 science optional 
augur_6.4.2-1.debian.tar.xz
 13ddc158a341ee270a6313a0730b7474 129800 science optional augur_6.4.2-1_all.deb
 8111810be31bb20fbf33f91095d37332 7617 science optional 
augur_6.4.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl55o3kRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtE8Ag//c+ecrewPgh5Xpi2rR4yyC2J0G2khX0X1
k14e1zt/nUPrdvxQqllWfivNS8sQHbkYejHbC/OJehzrg5ZSScDO5lOfWSxYxjlv
EcbiNcgmF2m2XFY+DkVQzaNKay4GHhC7gd3RJoMBISmXm2ZKjiPAMVlXptTDMYSa
HEBSc1n05h/XHKkDqKGoJJotJ0/wbSFJ56vQB/WgpSNWnO6gAVuAcx8uEo7bdvaj
qD5yDtSUvE0lzJHshshDEdPDAamFBwhP6kx3MNw4Wd/YTHSfaKG6VeHVXECBk90h
b+BvHhyBwloHi8IVnj2EzlgC529JgxQH6IPRMLprI/5aqT+1k1d4BC3FLIJWZFcX

Bug#882490: marked as done (gcc: Tune default --param ggc-min-expand for 32-bit arches)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:39:38 +
with message-id 
and subject line Bug#923982: Removed package(s) from unstable
has caused the Debian Bug report #882490,
regarding gcc: Tune default --param ggc-min-expand for 32-bit arches
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.)


-- 
882490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg
Version: 1.19.0.4
User: debian-m...@lists.debian.org
Usertags: mips mipsel

It would be nice if the default CFLAGS/CXXFLAGS were updated on mips &
mipsel (only) to include an additional gcc flag:

`--param ggc-min-expand=10`

This has caused multiple FTBFS in the past as for example: 849657 or 879636.

See previous discussions on debian-mips@l.d.o:

On Thu, Nov 23, 2017 at 1:14 PM, James Cowgill  wrote:
> On 23/11/17 11:42, Mathieu Malaterre wrote:
>> YunQiang,
>>
>> Do you know of any drawbacks ?
>
> This has been raised before:
> https://lists.debian.org/debian-mips/2016/10/msg00049.html
>
> I think it's generally a good idea. You wouldn't want to "enforce" this
> - you would set it as an overridable default setting.
>
> I think the disadvantages are: compilation speed, I think there is no
> official way to do this so you would have to hack the gcc source a bit,
> and deviation from upstream / other distros.
--- End Message ---
--- Begin Message ---
Version: 7.5.0-6+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#888394: marked as done (GCC bootstrap comparison failure build the D frontend on alpha)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:39:38 +
with message-id 
and subject line Bug#923982: Removed package(s) from unstable
has caused the Debian Bug report #888394,
regarding GCC bootstrap comparison failure build the D frontend on alpha
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.)


-- 
888394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gcc-7
Version: 7.2.0-20
Severity: important

Seen with the last GCC 7 build from the branch on alpha,

make[4]: Entering directory '/<>/build'
make[5]: Entering directory '/<>/build'
rm -f stage_current
make[5]: Leaving directory '/<>/build'
Comparing stages 2 and 3
warning: gcc/cc1objplus-checksum.o differs
warning: gcc/cc1obj-checksum.o differs
Bootstrap comparison failure!
gcc/d/lexer.o differs
Makefile:23293: recipe for target 'compare' failed
make[4]: *** [compare] Error 1
make[4]: Leaving directory '/<>/build'
Makefile:23272: recipe for target 'stage3-bubble' failed
make[3]: *** [stage3-bubble] Error 2

last successful build was on 20180107 (r256317). No changes in the gdc code.
--- End Message ---
--- Begin Message ---
Version: 7.5.0-6+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#901836: marked as done (-mieee-fp broken on i386)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:39:38 +
with message-id 
and subject line Bug#923982: Removed package(s) from unstable
has caused the Debian Bug report #901836,
regarding -mieee-fp broken on i386
to be marked as done.

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

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


-- 
901836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-7
Version: 7.3.0-23
Severity: important
Control: affects -1 src:plplot
Control: block 901155 by -1

Dear Maintainer,

The -mieee-fp flag is broken on i386:

 $ gcc -mieee-fp foo.c
 /usr/bin/ld: cannot find -lieee
 collect2: error: ld returned 1 exit status

libieee used to be shipped with glibc, but was removed in version 2.27.

The same bug is present is gcc-8.

Thanks,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 7.5.0-6+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#894302: marked as done (g++-7: Compiler generates wrong code with warning options)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:39:38 +
with message-id 
and subject line Bug#923982: Removed package(s) from unstable
has caused the Debian Bug report #894302,
regarding g++-7: Compiler generates wrong code with warning options
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.)


-- 
894302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: g++-7
Version: 7.3.0-12
Severity: important

This is an apparently impossible bug which nevertheless can be reliably
observed when using Debian versions of g++-7 and also i686-w64-mingw32-g++.
It consists in compiler generating different, and broken, code when
compiling the same input with only warning options -- which are, of course,
not supposed to affect the code generation at all -- added.

The upstream bug at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
contains several test cases. Using the one from
https://gcc.gnu.org/bugzilla/attachment.cgi?id=43774 it can be seen that
running

g++-7 -S -std=c++17 -O2 gcc-7.3-x86_64-linux.cpp -o nowarn.s

and

g++-7 -S -std=c++17 -O2 gcc-7.3-x86_64-linux.cpp -Wnonnull 
-Woverloaded-virtual -o warn.s

commands produces different assembly. Subsequently, Martin Liška has
created a further reduced test case which allows to reproduce the problem
using just "-O1 -Woverloaded-virtual", please see
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091#c31

The bug is really mysterious but quite worrisome, as it results in broken
code being silently generated in practice and, worse, the generated code
oscillates between correct and broken versions when any, even apparently
completely unrelated, changes are made. Another interesting detail is that
using -fchecking=2 makes the bug disappear (but -fchecking does not).

Finally, please note that the bug doesn't seem to happen with the upstream
versions nor with g++ 7.2 from Fedora, so it's highly likely that it's due
to one of the Debian-specific patches, even if I really can't see anything
that could explain it in any of them.

Thanks in advance for any help with this!

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

Kernel: Linux 4.6.0-0.bpo.1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
C.UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages g++-7 depends on:
ii  gcc-77.3.0-12
ii  gcc-7-base   7.3.0-12
ii  libc62.27-2
ii  libgmp10 2:6.1.2+dfsg-3
ii  libisl19 0.19-1
ii  libmpc3  1.1.0-1
ii  libmpfr6 4.0.1-1
ii  libstdc++-7-dev  7.3.0-12
ii  zlib1g   1:1.2.8.dfsg-5

g++-7 recommends no packages.

Versions of packages g++-7 suggests:
pn  g++-7-multilib
pn  gcc-7-doc 
pn  libstdc++6-7-dbg  

-- no debconf information


pgpzg8ElTDa59.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 7.5.0-6+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#954830: marked as done (RM: gcc-7 -- ROM; old version not used anymore)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:39:38 +
with message-id 
and subject line Bug#923982: Removed package(s) from unstable
has caused the Debian Bug report #954830,
regarding RM: gcc-7 -- ROM; old version not used anymore
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.)


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

Please remove gcc-7. superseded by gcc-9
--- End Message ---
--- Begin Message ---
Version: 7.5.0-6+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#887453: marked as done (libunwind: please disable lzma on ia64)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:39:38 +
with message-id 
and subject line Bug#923982: Removed package(s) from unstable
has caused the Debian Bug report #887453,
regarding libunwind: please disable lzma on ia64
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.)


-- 
887453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libunwind
Severity: normal
Tags: patch
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

For the ia64 port, we would like to disable lzma support for ia64, as it has 
caused several packages
to fail building when static linking is used.  (gcc doesn't know to include 
liblzma.a when it tries to
include libunwind.a).

The attached patch should accomplish this.

We will re-enable it once we've determined a good way to work through this 
problem.

Thanks,

Jason


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- debian/control.orig 2018-01-16 10:06:58.752562266 -0500
+++ debian/control  2018-01-16 10:07:19.420483094 -0500
@@ -2,8 +2,8 @@
 Priority: optional
 Section: libs
 Maintainer: Adrian Bunk 
-Build-Depends: debhelper (>= 10), liblzma-dev , 
texlive-extra-utils
-Build-Conflicts: liblzma-dev 
+Build-Depends: debhelper (>= 10), liblzma-dev [!ia64] , 
texlive-extra-utils
+Build-Conflicts: liblzma-dev [ia64] 
 Standards-Version: 4.1.1
 Homepage: http://www.nongnu.org/libunwind
 
--- End Message ---
--- Begin Message ---
Version: 7.5.0-6+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#923982: marked as done (RM: gcc-7 -- old version not used anymore)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:39:17 +
with message-id 
and subject line Bug#923982: Removed package(s) from unstable
has caused the Debian Bug report #923982,
regarding RM: gcc-7 -- old version not used anymore
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.)


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

Please remove the gcc-7, gcc-7-cross, gcc-7-cross-ports packages, superseded by
GCC 8.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 cpp-7 |7.5.0-5 | mips64el, mipsel
 cpp-7 |7.5.0-6 | amd64, arm64, armel, armhf, i386, mipsel, ppc64el, 
s390x
 g++-7 |7.5.0-5 | mips64el, mipsel
 g++-7 |7.5.0-6 | amd64, arm64, armel, armhf, i386, mipsel, ppc64el, 
s390x
g++-7-multilib |7.5.0-5 | mips64el, mipsel
g++-7-multilib |7.5.0-6 | amd64, i386, mipsel, s390x
 gcc-7 |7.5.0-5 | source, mips64el, mipsel
 gcc-7 |7.5.0-6 | source, amd64, arm64, armel, armhf, i386, mipsel, 
ppc64el, s390x
gcc-7-base |7.5.0-5 | mips64el, mipsel
gcc-7-base |7.5.0-6 | amd64, arm64, armel, armhf, i386, mipsel, ppc64el, 
s390x
gcc-7-hppa64-linux-gnu |7.5.0-6 | amd64, i386
gcc-7-locales |7.5.0-5 | all
gcc-7-locales |7.5.0-6 | all
gcc-7-multilib |7.5.0-5 | mips64el, mipsel
gcc-7-multilib |7.5.0-6 | amd64, i386, mipsel, s390x
gcc-7-offload-nvptx |7.5.0-6 | amd64
gcc-7-plugin-dev |7.5.0-5 | mips64el, mipsel
gcc-7-plugin-dev |7.5.0-6 | amd64, arm64, armel, armhf, i386, mipsel, 
ppc64el, s390x
gcc-7-source |7.5.0-5 | all
gcc-7-source |7.5.0-6 | all
gcc-7-test-results |7.5.0-5 | mips64el, mipsel
gcc-7-test-results |7.5.0-6 | amd64, arm64, armel, armhf, i386, mipsel, 
ppc64el, s390x
 gccbrig-7 |7.5.0-6 | amd64, i386
   gccgo-7 |7.5.0-5 | mips64el, mipsel
   gccgo-7 |7.5.0-6 | amd64, arm64, armel, armhf, i386, mipsel, ppc64el, 
s390x
gccgo-7-multilib |7.5.0-5 | mips64el, mipsel
gccgo-7-multilib |7.5.0-6 | amd64, i386, mipsel, s390x
 gdc-7 |7.5.0-5 | mips64el, mipsel
 gdc-7 |7.5.0-6 | amd64, arm64, armel, armhf, i386, mipsel, ppc64el, 
s390x
gdc-7-multilib |7.5.0-5 | mips64el, mipsel
gdc-7-multilib |7.5.0-6 | amd64, i386, mipsel, s390x
gfortran-7 |7.5.0-5 | mips64el, mipsel
gfortran-7 |7.5.0-6 | amd64, arm64, armel, armhf, i386, mipsel, ppc64el, 
s390x
gfortran-7-multilib |7.5.0-5 | mips64el, mipsel
gfortran-7-multilib |7.5.0-6 | amd64, i386, mipsel, s390x
gnat-7 |7.5.0-5 | mips64el, mipsel
gnat-7 |7.5.0-6 | amd64, arm64, armel, armhf, i386, mipsel, ppc64el, 
s390x
gnat-7-sjlj |7.5.0-5 | mips64el, mipsel
gnat-7-sjlj |7.5.0-6 | amd64, arm64, armel, armhf, i386, mipsel, ppc64el, 
s390x
 gobjc++-7 |7.5.0-5 | mips64el, mipsel
 gobjc++-7 |7.5.0-6 | amd64, arm64, armel, armhf, i386, mipsel, ppc64el, 
s390x
gobjc++-7-multilib |7.5.0-5 | mips64el, mipsel
gobjc++-7-multilib |7.5.0-6 | amd64, i386, mipsel, s390x
   gobjc-7 |7.5.0-5 | mips64el, mipsel
   gobjc-7 |7.5.0-6 | amd64, arm64, armel, armhf, i386, mipsel, ppc64el, 
s390x
gobjc-7-multilib |7.5.0-5 | mips64el, mipsel
gobjc-7-multilib |7.5.0-6 | amd64, i386, mipsel, s390x
lib32asan4 |7.5.0-6 | amd64, s390x
lib32cilkrts5 |7.5.0-6 | amd64
lib32gcc-7-dev |7.5.0-5 | mips64el
lib32gcc-7-dev |7.5.0-6 | amd64, s390x
lib32gfortran-7-dev |7.5.0-5 | mips64el
lib32gfortran-7-dev |7.5.0-6 | amd64, s390x
lib32gfortran4 |7.5.0-5 | mips64el
lib32gfortran4 |7.5.0-6 | amd64, s390x
 lib32go11 |7.5.0-5 | mips64el
 lib32go11 |7.5.0-6 | amd64, s390x
lib32gphobos-7-dev |7.5.0-6 | amd64
lib32gphobos71 |7.5.0-6 | amd64
lib32objc-7-dev |7.5.0-5 | mips64el
lib32objc-7-dev |7.5.0-6 | amd64, s390x
lib32stdc++-7-dev |7.5.0-5 | mips64el
lib32stdc++-7-dev |7.5.0-6 | amd64, s390x
lib32stdc++6-7-dbg |7.5.0-5 | mips64el
lib32stdc++6-7-dbg |7.5.0-6 | amd64, s390x
lib32ubsan0 |7.5.0-6 | amd64, s390x
lib64asan4 |7.5.0-6 | i386
lib64cilkrts5 |7.5.0-6 | i386
lib64gcc-7-dev |7.5.0-5 | mipsel
lib64gcc-7-dev |7.5.0-6 | i386, mipsel
lib64gfortran-7-dev |7.5.0-5 | mipsel
lib64gfortran-7-dev |7.5.0-6 | i386, mipsel
lib64gfortran4 |7.5.0-5 | mipsel
lib64gfortran4 |7.5.0-6 | i386, mipsel
 lib64go11 |7.5.0-5 | mipsel
 lib64go11 |7.5.0-6 | i386, mipsel
lib64gphobos-7-dev |7.5.0-6 | i386

Bug#881288: marked as done (gcc-7 fails to patch when old distribution detected)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:39:38 +
with message-id 
and subject line Bug#923982: Removed package(s) from unstable
has caused the Debian Bug report #881288,
regarding gcc-7 fails to patch when old distribution detected
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.)


-- 
881288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-7
Version: 7.2.0-12
Severity: normal

Dear Maintainer,

When gcc-7 detects one of many outdated distributions, it attempts to apply the 
"gcc-hash-style-both" patch,
rather than "gcc-hash-style-gnu".  gcc-hash-style-both is sufficiently crufty 
that it fails to apply.

I suggest either removing the detection, or rebasing the patch.  I have 
included a patch to remove the detection.

Thank you for your time and work.

Jason

-- System Information:
Debian Release: 7.11
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable')
Architecture: ia64

Kernel: Linux 3.2.0-4-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gcc-7 depends on:
ii  binutils  2.25-5+deb8u1
ii  cpp-7 7.2.0-12
ii  gcc-7-base7.2.0-12
ii  libc6.1   2.13-38+deb7u10
ii  libcc1-0  7.2.0-12
ii  libgcc-7-dev  7.2.0-12
ii  libgcc1   1:7.2.0-12
ii  libgmp10  2:6.1.2+dfsg-1.1
ii  libisl15  0.18-1
ii  libmpc3   1.0.3-2
ii  libmpfr4  3.1.6-1
ii  libstdc++67.2.0-12
ii  libunwind70.99-0.3
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages gcc-7 recommends:
ii  libc6.1-dev  2.13-38+deb7u10

Versions of packages gcc-7 suggests:
pn  gcc-7-doc 
pn  gcc-7-locales 
pn  libasan4-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libmpx2-dbg   
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- debconf information:
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/^(.*?)(\\)?\${ <-- HERE ([^{}]+)}(.*)$/ at 
/usr/share/perl5/Debconf/Question.pm line 72.
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/\${ <-- HERE ([^}]+)}/ at /usr/share/perl5/Debconf/Config.pm line 
30.
--- debian/rules.patch.orig	2017-11-09 12:17:23.775340303 -0500
+++ debian/rules.patch	2017-11-09 12:17:56.799340531 -0500
@@ -39,13 +39,8 @@
 	gcc-textdomain \
 	gcc-driver-extra-langs$(if $(with_linaro_branch),-linaro)
 
-ifneq (,$(filter $(distrelease),etch lenny squeeze wheezy dapper hardy intrepid jaunty karmic lucid))
-  debian_patches += gcc-hash-style-both
-else
-  debian_patches += gcc-hash-style-gnu
-endif
-
 debian_patches += \
+	gcc-hash-style-gnu \
 	libstdc++-pic \
 	libstdc++-doclink \
 	libstdc++-man-3cxx \
--- End Message ---
--- Begin Message ---
Version: 7.5.0-6+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#884431: marked as done (gcc-7: miscompile pthread_barrier.c from glibc with -mcpu=ultrasparc)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:39:38 +
with message-id 
and subject line Bug#923982: Removed package(s) from unstable
has caused the Debian Bug report #884431,
regarding gcc-7: miscompile pthread_barrier.c from glibc with -mcpu=ultrasparc
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.)


-- 
884431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-7
Version: 7.2.0-17
Severity: normal

When pthread_barrier.c from glibc is compiled with gcc-7 and
-mcpu=ultrasparc (as opposed to the default -mcpu=v9), the futex
code is miscompiled. This causes the rt/tst-mqueue5, nptl/tst-signal6
and nptl/tst-tls2 to fail with:

  The futex facility returned an unexpected error code.

I haven't been able to reproduce the issue with GCC 6. That said it
looks like the issue is quite dependent of the instruction scheduling
as slightly changing the code around for debugging purpose makes the
problem to vanish.
--- End Message ---
--- Begin Message ---
Version: 7.5.0-6+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#879703: marked as done (gcc-7: static development libraries miss debug information)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:39:38 +
with message-id 
and subject line Bug#923982: Removed package(s) from unstable
has caused the Debian Bug report #879703,
regarding gcc-7: static development libraries miss debug information
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.)


-- 
879703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-7
Version: 7.2.0-11
Severity: wishlist

Dear Maintainer,

the static libraries, most importantly libstdc++, miss debug informations.
This is not ideal, and the debuginfo should be available for developers
by default. 

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (200, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, arm64

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

Versions of packages gcc-7 depends on:
ii  binutils  2.29.1-5
ii  cpp-7 7.2.0-11
ii  gcc-7-base7.2.0-11
ii  libc6 2.24-17
ii  libcc1-0  7.2.0-11
ii  libgcc-7-dev  7.2.0-11
ii  libgcc1   1:7.2.0-11
ii  libgmp10  2:6.1.2+dfsg-1.1
ii  libisl15  0.18-1
ii  libmpc3   1.0.3-2
ii  libmpfr4  3.1.6-1
ii  libstdc++67.2.0-11
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages gcc-7 recommends:
ii  libc6-dev  2.24-17

Versions of packages gcc-7 suggests:
pn  gcc-7-doc 
pn  gcc-7-locales 
ii  gcc-7-multilib7.2.0-11
pn  libasan4-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
ii  libgcc1-dbg   1:7.2.0-11
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libmpx2-dbg   
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 7.5.0-6+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#895452: marked as done (gcc-7: libquadmath is disabled for gcc 7.3.0 on powerpc64-linux-gnu)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:39:38 +
with message-id 
and subject line Bug#923982: Removed package(s) from unstable
has caused the Debian Bug report #895452,
regarding gcc-7: libquadmath is disabled for gcc 7.3.0 on powerpc64-linux-gnu
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.)


-- 
895452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-7
Version: 7.3.0-15
Severity: important

Dear Maintainer,

   * What led up to the situation?

Attempt to compile a trivial code test that uses #include 
as well as _Float128 datatype and quadmath_snprintf() call fails with

 fatal error: quadmath.h: No such file or directory

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

Wrote a trivial piece of test code and then issued a compile :

$ gcc -mcpu=970 -mno-altivec -g -m64 -std=c99 -pedantic-errors -o s s.c 
s.c:82:10: fatal error: quadmath.h: No such file or directory
 #include 
  ^~~~
compilation terminated.


   * What was the outcome of this action?

Compile can not proceed.


   * What outcome did you expect instead?

Expected a trivial to compile to generate pre-processed intermediate
file and then assembly and then an object file and then a final ELF
executable file that runs as expected.

-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ppc64

Kernel: Linux 4.15.0-2-powerpc64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=C (charmap=ANSI_X3.4-1968), 
LANGUAGE=en_CA:en (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gcc-7 depends on:
ii  binutils  2.30-15
ii  cpp-7 7.3.0-15
ii  gcc-7-base7.3.0-15
ii  libc6 2.27-3
ii  libcc1-0  8-20180402-1
ii  libgcc-7-dev  7.3.0-15
ii  libgcc1   1:8-20180402-1
ii  libgmp10  2:6.1.2+dfsg-3
ii  libisl19  0.19-1
ii  libmpc3   1.1.0-1
ii  libmpfr6  4.0.1-1
ii  libstdc++68-20180402-1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages gcc-7 recommends:
ii  libc6-dev  2.27-3

Versions of packages gcc-7 suggests:
pn  gcc-7-doc 
pn  gcc-7-locales 
ii  gcc-7-multilib7.3.0-15
pn  libasan4-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libmpx2-dbg   
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 7.5.0-6+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#866369: marked as done (gdc unittest fails to build on ARM32)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:39:38 +
with message-id 
and subject line Bug#923982: Removed package(s) from unstable
has caused the Debian Bug report #866369,
regarding gdc unittest fails to build on ARM32
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.)


-- 
866369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gcc-7
Version: 7.1.0-7

full build log at
https://buildd.debian.org/status/fetch.php?pkg=gcc-7=armel=7.1.0-7=1498249793=0

../../../../src/libphobos/src/std/math.d:4971:5: warning: statement is not 
reachable
 void ensureDefaults()
 ^
../../../../src/libphobos/src/std/math.d:4979:5: warning: statement is not 
reachable
 {
 ^
../../../../src/libphobos/src/std/math.d:4982:5: warning: statement is not 
reachable
 ensureDefaults();
 ^
../../../../src/libphobos/src/std/math.d:4984:5: warning: statement is not 
reachable
 {
 ^
../../../../src/libphobos/src/std/math.d:4989:5: warning: statement is not 
reachable
 ensureDefaults();
 ^
../../../../src/libphobos/src/std/math.d:4991:5: warning: statement is not 
reachable
 if(FloatingPointControl.hasExceptionTraps)
 ^
../../../../src/libphobos/src/std/math.d:5003:5: warning: statement is not 
reachable
 ensureDefaults();
 ^
../../../../src/libphobos/src/std/math.d:5643:32: error: cannot take address of
local x in @safe function __unittestL5638_68
 auto xl = *cast(ulong*)
^
test disabled on ARM, see bug 5628
Makefile:1804: recipe for target 'std/math.t.lo' failed
make[6]: *** [std/math.t.lo] Error 1
--- End Message ---
--- Begin Message ---
Version: 7.5.0-6+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#886099: marked as done (gcc-7: backport PR target/82981)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:39:38 +
with message-id 
and subject line Bug#923982: Removed package(s) from unstable
has caused the Debian Bug report #886099,
regarding gcc-7: backport PR target/82981
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.)


-- 
886099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gcc-7
Version: 7.2.0-18

Please consider backport the patch of PR target/82981.

It fix a problem of link kernel on mips64r6.
[2] said that is also fixes an ICE on arm.

[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82981
[2] https://www.mail-archive.com/gcc-patches@gcc.gnu.org/msg178809.html
[3] 
https://github.com/gcc-mirror/gcc/commit/db382c683b735bed1adb483137055231dbed050f

-- 
YunQiang Su
--- End Message ---
--- Begin Message ---
Version: 7.5.0-6+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#881939: marked as done (gcc: disable D when cross build native GCC)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:39:38 +
with message-id 
and subject line Bug#923982: Removed package(s) from unstable
has caused the Debian Bug report #881939,
regarding gcc: disable D when cross build native GCC
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.)


-- 
881939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gcc-7
Version: 7.2.0-16

When we build native GCC with the cross gcc, D will always fails.
So please disable D in this condition.

@@ -891,6 +926,12 @@ ifeq ($(with_base_only),yes
   with_d := no
 endif

+ifneq ($(DEB_BUILD_ARCH), $(DEB_HOST_ARCH))
+ifeq ($(DEB_HOST_ARCH), $(DEB_TARGET_ARCH))
+  with_d := no
+endif
+endif
+
 ifeq ($(with_d)-$(with_separate_gdc),yes-yes)
   ifneq (,$(findstring gdc,$(PKGSOURCE)))
 languages := c c++


-- 
YunQiang Su
--- End Message ---
--- Begin Message ---
Version: 7.5.0-6+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#870375: marked as done (gcc-7: Native gdc cross-builds fail)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:39:38 +
with message-id 
and subject line Bug#923982: Removed package(s) from unstable
has caused the Debian Bug report #870375,
regarding gcc-7: Native gdc cross-builds fail
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.)


-- 
870375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-7
Version: 7.1.0-11
Severity: normal
Tags: patch

Hi!

Trying to do a cross-native build for m68k with gdc enabled fails with:

g++-o d/impcvgen d/impcnvgen.dmdgen.o
/usr/bin/ld: d/idgen.dmdgen.o: Relocations in generic ELF (EM: 4)
/usr/bin/ld: d/idgen.dmdgen.o: Relocations in generic ELF (EM: 4)
/usr/bin/ld: d/idgen.dmdgen.o: Relocations in generic ELF (EM: 4)
/usr/bin/ld: d/idgen.dmdgen.o: Relocations in generic ELF (EM: 4)
/usr/bin/ld: d/idgen.dmdgen.o: Relocations in generic ELF (EM: 4)
/usr/bin/ld: d/idgen.dmdgen.o: Relocations in generic ELF (EM: 4)
/usr/bin/ld: d/idgen.dmdgen.o: Relocations in generic ELF (EM: 4)
/usr/bin/ld: d/idgen.dmdgen.o: Relocations in generic ELF (EM: 4)
d/idgen.dmdgen.o: error adding symbols: File in wrong format
collect2: error: ld returned 1 exit status
../../src/gcc/d/Make-lang.in:254: recipe for target 'd/idgen' failed

I'm currently working around this issue by adding the following
changes to debian/rules.defs:

--- debian/rules.defs.orig  2017-08-01 15:35:52.999394076 +0200
+++ debian/rules.defs   2017-08-01 15:27:13.531269664 +0200
@@ -869,6 +869,9 @@
 ifeq ($(DEB_STAGE)-$(filter libphobos, $(with_rtlibs)),rtlibs-)
   with_d := disabled for rtlibs stage
 endif
+ifeq (,$(filter $(build_type), build-cross build-native))
+   with_d += no
+endif
 with_d := $(call envfilt, d, , , $(with_d))
 
 #with_d := not yet built for GCC 7

I'm attaching the patch just in case. I will also test whether this
affects other architectures for cross-native builds.

Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- debian/rules.defs.orig  2017-08-01 15:35:52.999394076 +0200
+++ debian/rules.defs   2017-08-01 15:27:13.531269664 +0200
@@ -869,6 +869,9 @@
 ifeq ($(DEB_STAGE)-$(filter libphobos, $(with_rtlibs)),rtlibs-)
   with_d := disabled for rtlibs stage
 endif
+ifeq (,$(filter $(build_type), build-cross build-native))
+   with_d += no
+endif
 with_d := $(call envfilt, d, , , $(with_d))
 
 #with_d := not yet built for GCC 7
--- End Message ---
--- Begin Message ---
Version: 7.5.0-6+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#427108: marked as done ([Fixed in 8] Bug box Program_Error exp_disp.adb: explicit raise)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:39:38 +
with message-id 
and subject line Bug#923982: Removed package(s) from unstable
has caused the Debian Bug report #427108,
regarding [Fixed in 8] Bug box Program_Error exp_disp.adb: explicit raise
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.)


-- 
427108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnat-4.1
Version: 4.1.1-22
Severity: normal

The following program prints FAILED; it should print PASSED
as per RM 3.4(27), which states:

-- "For the execution of a call on an inherited subprogram,
-- a call on the corresponding primitive subprogram of the
-- parent or progenitor type is performed; the normal conversion
-- of each actual parameter to the subtype of the corresponding
-- formal parameter (see 6.4.1) performs any necessary type
-- conversion as well."

with Text_IO; use Text_IO;
procedure Test1 is
   package Pak1 is
  type T1 is tagged null record;
  function Eq(X, Y: T1) return Boolean renames "=";
   end Pak1;

   package Pak2 is
  type T2 is new Pak1.T1 with record
 F1: Integer;
  end record;
   end Pak2;

   Z1: Pak2.T2 := (F1 => 1);
   Z2: Pak2.T2 := (F1 => 2);
begin
   if Pak2.Eq(Z1, Z2) = Pak1.Eq(Pak1.T1(Z1), Pak1.T1(Z2))
  then Put_Line("PASSED");
  else Put_Line("FAILED");
   end if;
end Test1;

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

Kernel: Linux 2.6.18-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gnat-4.1 depends on:
ii  gcc-4.1 4.1.1-21 The GNU C compiler
ii  gnat-4.1-base   4.1.1-22 The GNU Compiler Collection
(gnat 
ii  libc6   2.3.6.ds1-13 GNU C Library: Shared
libraries
ii  libc6-dev   2.3.6.ds1-13 GNU C Library: Development
Librari
ii  libgcc1 1:4.1.1-21   GCC support library
ii  libgnat-4.1 4.1.1-22 Runtime library for GNU Ada
applic
ii  libgnatprj4.1   4.1.1-22 GNU Ada Project Manager
ii  libgnatvsn4.1   4.1.1-22 GNU Ada compiler version
library

gnat-4.1 recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 7.5.0-6+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#853709: marked as done (xbubble: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:39:38 +
with message-id 
and subject line Bug#923982: Removed package(s) from unstable
has caused the Debian Bug report #853709,
regarding xbubble: ftbfs with GCC-7
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.)


-- 
853709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xbubble
Version: 0.5.11.2-3.3
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/xbubble_0.5.11.2-3.3_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 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-7/porting_to.html

[...]
checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking whether NLS is requested... yes
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
checking whether to enable maintainer-specific portions of Makefiles... no
checking the warning flags for this compiler... -Wall -Wunused 
-Wmissing-prototypes -Wmissing-declarations -Wshadow -Wpointer-arith 
-Wchar-subscripts -Wcomment -Wformat -Wwrite-strings -Wno-unused-variable 
-Wno-unused-function -Wno-unused-label -Werror
checking the optimization flags for this compiler...  -O3 -finline-functions 
-ffast-math -funroll-loops -fno-strict-aliasing
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating man/Makefile
config.status: creating data/Makefile
config.status: creating po/Makefile.in
config.status: creating src/config.h
config.status: executing depfiles commands
config.status: executing default-1 commands
config.status: creating po/POTFILES
config.status: creating po/Makefile
touch debian/stamp-autotools
/usr/bin/make -C . 
make[1]: Entering directory '/<>'
Making all in po
make[2]: Entering directory '/<>/po'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/<>/po'
Making all in src
make[2]: Entering directory '/<>/src'
/usr/bin/make  all-am
make[3]: Entering directory '/<>/src'
gcc -DHAVE_CONFIG_H -I. -I. -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-DDATADIR=\"/usr/share/xbubble\"  -O3 -finline-functions -ffast-math 
-funroll-loops -fno-strict-aliasing -Wall -Wunused -Wmissing-prototypes 
-Wmissing-declarations -Wshadow -Wpointer-arith -Wchar-subscripts -Wcomment 
-Wformat -Wwrite-strings -Wno-unused-variable -Wno-unused-function 
-Wno-unused-label -Werror -g -c utils.c
gcc -DHAVE_CONFIG_H -I. -I. -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-DDATADIR=\"/usr/share/xbubble\"  -O3 -finline-functions -ffast-math 
-funroll-loops -fno-strict-aliasing -Wall -Wunused -Wmissing-prototypes 
-Wmissing-declarations -Wshadow -Wpointer-arith -Wchar-subscripts -Wcomment 
-Wformat -Wwrite-strings -Wno-unused-variable -Wno-unused-function 
-Wno-unused-label -Werror -g -c rectangle.c
gcc -DHAVE_CONFIG_H -I. -I. -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-DDATADIR=\"/usr/share/xbubble\"  -O3 -finline-functions -ffast-math 
-funroll-loops -fno-strict-aliasing -Wall -Wunused -Wmissing-prototypes 
-Wmissing-declarations -Wshadow -Wpointer-arith -Wchar-subscripts -Wcomment 
-Wformat -Wwrite-strings -Wno-unused-variable -Wno-unused-function 
-Wno-unused-label -Werror -g -c cell.c
cell.c: In function 'cell_array_lower':
cell.c:138:19: error: assuming signed overflow does not occur when assuming 
that (X - c) <= X is always true [-Werror=strict-overflow]
   ca->cell[i] = EMPTY_CELL;
cc1: all warnings being treated as 

Bug#856274: marked as done (gnat-BV: gnatchop fails to execute (ARCH-)?gcc-BV-BV)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:39:38 +
with message-id 
and subject line Bug#923982: Removed package(s) from unstable
has caused the Debian Bug report #856274,
regarding gnat-BV: gnatchop fails to execute (ARCH-)?gcc-BV-BV
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.)


-- 
856274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnat-5,gnat-6,gnat-7
Severity: important
X-Debbugs-CC: Svante Signell 

The recent gcc-5 upload with the ada-gcc-name patch removed results in build
failures, because gnatmake now calls /usr/bin/gcc (which points to gcc-6), and
doesn't find an installed gnat1 binary [1]. So I think that the workaround from
#814978 only works for the default gnat version, and we should properly fix this
issue.  Just adding gnat-6 as a build dependency won't help, because we cannot
assume that a newer gnat is able to build an older gnat.

So we need to investigate where the doubled suffix comes from.

[1]
https://buildd.debian.org/status/fetch.php?pkg=gcc-5=amd64=5.4.1-6=1488135841=0
--- End Message ---
--- Begin Message ---
Version: 7.5.0-6+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#954877: marked as done (RM: ptex2tex -- RoQA; Depends on Python 2)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:34:57 +
with message-id 
and subject line Bug#954877: Removed package(s) from unstable
has caused the Debian Bug report #954877,
regarding RM: ptex2tex -- RoQA; Depends on Python 2
to be marked as done.

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

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


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

Please remove ptex2tex. It depends on Python 2, is dead upstream and
unmaintained (last upload in 2011)

Cheers,
Moritz

--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

  ptex2tex |  0.4-1 | source, all

--- Reason ---
RoQA; Depends on Python 2
--

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

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

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

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

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

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

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

Bug#954880: marked as done (RM: python-macaron -- RoQA; Depends on Python 2, unmaintained)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:35:28 +
with message-id 
and subject line Bug#954880: Removed package(s) from unstable
has caused the Debian Bug report #954880,
regarding RM: python-macaron -- RoQA; Depends on Python 2, unmaintained
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.)


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

Please remove python-macaron. It depends on Python 2, there are no
reverse deps and there hasn't been an upload since 2012.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-macaron |0.3.1-1 | source, all

--- Reason ---
RoQA; Depends on Python 2, unmaintained
--

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

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

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

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

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

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

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

Bug#954881: marked as done (RM: meshlab [armel armhf] -- RoQA; obsolete binaries)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:35:54 +
with message-id 
and subject line Bug#954881: Removed package(s) from unstable
has caused the Debian Bug report #954881,
regarding RM: meshlab [armel armhf] -- RoQA; obsolete binaries
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.)


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

Please remove meshlab on armel/armhf. These are outdated binaries and
no longer build with the new version (due to only having OpenGL-ES)

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   meshlab | 1.3.2+dfsg1-4+b1 | armel, armhf

--- Reason ---
RoQA; obsolete binaries
--

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

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

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

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

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

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

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

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

Bug#954832: marked as done (RM: node-run-sequence -- ROM; Deprecated since node-gulp 4)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:36:27 +
with message-id 
and subject line Bug#954832: Removed package(s) from unstable
has caused the Debian Bug report #954832,
regarding RM: node-run-sequence -- ROM; Deprecated since node-gulp 4
to be marked as done.

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

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


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

Hi,

node-run-sequence is a sort of plugin for gulp 3 to be able to launch
tasks in series/parallel. Since version 4, gulp has its own system
(gulp.series and gulp.parallel) and node-run-sequence isn't compatible
with it [#954557]. I fixed all reverse dependencies of node-run-sequence
and now dak is OK [2].

Cheers,
Xavier

[954557] https://bugs.debian.org/954557
[2] dak output:
  Will remove the following packages from unstable:

  node-run-sequence |2.2.1-1 | source, all

  Maintainer: Debian Javascript Maintainers 


  --- Reason ---

  --

  Checking reverse dependencies...
  No dependency problem found.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

node-run-sequence |2.2.1-1 | source, all

--- Reason ---
ROM; Deprecated since node-gulp 4
--

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

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

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

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

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

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

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

Bug#937333: marked as done (ptex2tex: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:35:00 +
with message-id 
and subject line Bug#954877: Removed package(s) from unstable
has caused the Debian Bug report #937333,
regarding ptex2tex: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:ptex2tex

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

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

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#954876: marked as done (RM: xow -- ROM; licensing issue)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:34:09 +
with message-id 
and subject line Bug#954876: Removed package(s) from unstable
has caused the Debian Bug report #954876,
regarding RM: xow -- ROM; licensing issue
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.)


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

Hi,

We recently found out there is an issue with the license of one of
xow's files, upstream discussion is available here:
https://github.com/medusalix/xow/issues/15#issuecomment-602301493

The bulk of it is that upstream has a third party binary blob with
unknown license, which upstream previously thought had a DFSG
compliant one.

I'm asking for the removal of the package until the issue is resolved,
when that happens I will submit the package to NEW once again.

This is a non-free package which is not on testing and it's not
whitelisted on our build infrastructure.

Although upstream still has the file and lists the wrong license, I'm
being cautious here and asking for the removal because it's a
confirmed issue.

$ dak rm -Rn xow
Will remove the following packages from unstable:

   xow |  0.3-3 | source

Maintainer: Samuel Henrique 

--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.


Thanks

-- 
Samuel Henrique 
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   xow |  0.3-3 | source

--- Reason ---
ROM; licensing issue
--

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

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

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

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

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

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

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

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

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:35:31 +
with message-id 
and subject line Bug#954880: Removed package(s) from unstable
has caused the Debian Bug report #937903,
regarding python-macaron: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-macaron

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

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

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#917892: marked as done (ptex2tex: /usr/bin/pygmentize moved to python3-pygments package)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:35:00 +
with message-id 
and subject line Bug#954877: Removed package(s) from unstable
has caused the Debian Bug report #917892,
regarding ptex2tex: /usr/bin/pygmentize moved to python3-pygments package
to be marked as done.

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

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


-- 
917892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ptex2tex
Version: 0.4-1
Severity: normal

Dear Maintainer,

if the dependency on python-pygments is due to pygmentize script
(and latex/styles/minted.sty suggests that)
then please replace it with python3-pygments as that the package
that provides this script now. TIA
--- End Message ---
--- Begin Message ---
Version: 0.4-1+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#953486: marked as done (xow: binaries for non-free not auto-built)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:34:13 +
with message-id 
and subject line Bug#954876: Removed package(s) from unstable
has caused the Debian Bug report #953486,
regarding xow: binaries for non-free not auto-built
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.)


-- 
953486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:xow
version: 0.3-3
severity: serious
tags: ftbfs

Hi,

The latest upload of xow to unstable has no binaries.
The buildds are not building it, because it is in non-free.

If the binaries can be auto-built, the package should be whitelisted, as
described in
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd

If not, a binary upload must be done (note that binary maintainer uploads for
sources in contrib and non-free are allowed to migrate to testing).

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Version: 0.3-3+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#954557: marked as done (node-run-sequence: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:36:30 +
with message-id 
and subject line Bug#954832: Removed package(s) from unstable
has caused the Debian Bug report #954557,
regarding node-run-sequence: FTBFS: dh_auto_test: error: /bin/sh -e 
debian/tests/pkg-js/test returned exit code 1
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.)


-- 
954557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-run-sequence
Version: 2.2.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package node-run-sequence
> dpkg-buildpackage: info: source version 2.2.1-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Pirate Praveen 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with nodejs
>dh_auto_clean --buildsystem=nodejs
>   rm -rf ./node_modules/.cache
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building node-run-sequence using existing 
> ./node-run-sequence_2.2.1.orig.tar.gz
> dpkg-source: info: building node-run-sequence in 
> node-run-sequence_2.2.1-1.debian.tar.xz
> dpkg-source: info: building node-run-sequence in node-run-sequence_2.2.1-1.dsc
>  debian/rules binary
> dh binary --with nodejs
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   /bin/sh -e debian/tests/pkg-js/test
> /usr/share/nodejs/yargs/yargs.js:1233
>   else throw err
>^
> 
> AssertionError [ERR_ASSERTION]: Task function must be specified
> at Gulp.set [as _setTask] 
> (/usr/share/nodejs/gulp/node_modules/undertaker/lib/set-task.js:10:3)
> at Gulp.task 
> (/usr/share/nodejs/gulp/node_modules/undertaker/lib/task.js:13:8)
> at Suite. (/<>/test/main.js:29:7)
> at Object.create (/usr/share/nodejs/mocha/lib/interfaces/common.js:140:19)
> at context.describe.context.context 
> (/usr/share/nodejs/mocha/lib/interfaces/bdd.js:42:27)
> at Object. (/<>/test/main.js:20:1)
> at Module._compile (internal/modules/cjs/loader.js:778:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
> at Module.load (internal/modules/cjs/loader.js:653:32)
> at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
> at Function.Module._load (internal/modules/cjs/loader.js:585:3)
> at Module.require (internal/modules/cjs/loader.js:692:17)
> at require (internal/modules/cjs/helpers.js:25:18)
> at /usr/share/nodejs/mocha/lib/mocha.js:311:36
> at Array.forEach ()
> at Mocha.loadFiles (/usr/share/nodejs/mocha/lib/mocha.js:308:14)
> at Mocha.run (/usr/share/nodejs/mocha/lib/mocha.js:849:10)
> at Object.exports.singleRun 
> (/usr/share/nodejs/mocha/lib/cli/run-helpers.js:108:16)
> at exports.runMocha 
> (/usr/share/nodejs/mocha/lib/cli/run-helpers.js:143:13)
> at Object.exports.handler.argv [as handler] 
> (/usr/share/nodejs/mocha/lib/cli/run.js:305:3)
> at Object.runCommand (/usr/share/nodejs/yargs/lib/command.js:240:40)
> at Object.parseArgs [as _parseArgs] 
> (/usr/share/nodejs/yargs/yargs.js:1173:35)
> at Object.parse (/usr/share/nodejs/yargs/yargs.js:618:25)
> at Object.exports.main (/usr/share/nodejs/mocha/lib/cli/cli.js:68:6)
> at Object. (/usr/share/nodejs/mocha/bin/mocha:133:29)
> at Module._compile (internal/modules/cjs/loader.js:778:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
> at Module.load (internal/modules/cjs/loader.js:653:32)
> at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
> at Function.Module._load (internal/modules/cjs/loader.js:585:3)
> at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
> at startup (internal/bootstrap/node.js:283:19)
> at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
> dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1

The full build log is available from:
   

Bug#951186: marked as done (Please reconsider usage of perl-Array-IntSpan in licensecheck)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 22:21:26 +0100
with message-id <158508488673.3704239.17642803147167183...@auryn.jones.dk>
and subject line Re: Bug#951186: Please reconsider usage of perl-Array-IntSpan 
in licensecheck
has caused the Debian Bug report #951186,
regarding Please reconsider usage of perl-Array-IntSpan in licensecheck
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.)


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

Package: licensecheck
Version: 3.0.41

The perl Array-IntSpan module is licensed Artistic v1 [1], but this 
license is considered a non-free license [2] and not allowed in Fedora [3].


As such, Fedora won't be able to ship newer versions of licensecheck as 
long as there is a dependency on this module. Could it's use please be 
reconsidered? Thanks.


[1] https://metacpan.org/release/Array-IntSpan
[2] https://www.gnu.org/licenses/license-list.html#ArtisticLicense
[3] 
https://fedoraproject.org/wiki/Licensing:Main?rd=Licensing#Bad_Licenses 




--- End Message ---
--- Begin Message ---
Quoting Sandro Mani (2020-03-24 21:22:18)
> So the current Array::IntSpan maintainer managed to track down the 
> original author, which has agreed to relicense to Artistic-2.0, which 
> resolves this issue.

That's great news.

Sorry I failed to switch - I really tried several alternative libraries 
without success.

Closing this bugreport as solved.


 - 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#885953: marked as done (xstarfish: \r in filename in .orig tarball)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:06:15 +
with message-id 
and subject line Bug#885953: fixed in xstarfish 1.1+ds-1
has caused the Debian Bug report #885953,
regarding xstarfish: \r in filename in .orig tarball
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.)


-- 
885953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xstarfish
Version: 1.1-11.1
Severity: normal

Hi!
There are two files with \r in name in the tarball:
starfish-1.1/portable/.AppleDouble/Icon\r
starfish-1.1/unix/.AppleDouble/Icon\r

This causes FTBFS (at unpack stage) on some filesystems, but as they are an
unheard of setup for building packages, this is currently not considered RC. 
However, I'm developing a security module that bans problematic filenames,
and in the configuration I'd like to recommend for distributions to default
to, \r is forbidden.  This would obviously break building your package.

Thus, could you please repack the .orig tarball without these two files (or
perhaps rename them)?  There's only one other package (cenon.app) with this
issue (in the same filename!), thus this should be an uncontroversial
change.


Meow!
-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.15.0-rc5-00024-g8358e4baaa66 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Source: xstarfish
Source-Version: 1.1+ds-1
Done: Adam Borowski 

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

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

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated xstarfish package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 22 Mar 2020 02:57:33 +0100
Source: xstarfish
Architecture: source
Version: 1.1+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Closes: 392396 810078 885953
Changes:
 xstarfish (1.1+ds-1) unstable; urgency=medium
 .
   * Orphan the package.
   * Repack the .orig tarball to remove binaries from a proprietary MacOS
 tool which cause errors on QA (bad filenames, masquerading as .gz),
 precompiled source, old Debian packaging.  Closes: #392396, #885953
   * Drop pre-cretaceous Provides/Replaces.
   * Ack NMU.  Closes: #810078
Checksums-Sha1:
 3de9926b1adcd7d652b9a2f762a8d835716b3975 1716 xstarfish_1.1+ds-1.dsc
 bc21a7a90074c3eb04c751d7ad77d847a45ed9dd 44964 xstarfish_1.1+ds.orig.tar.xz
 8e12fb12ac0d4bbc35793e1d8c77783b740eca13 9784 xstarfish_1.1+ds-1.debian.tar.xz
 b08b83bf00d7f2c43a39a1ab7c1b0d00e35139a1 5795 
xstarfish_1.1+ds-1_source.buildinfo
Checksums-Sha256:
 23b36139ed45266cf1608829b31464dd0e0cfa68531e31b016f8a2a0ed8cdec6 1716 
xstarfish_1.1+ds-1.dsc
 c5ef6aef3757b2c70179d6ecaa19cf14fcbcd2c04c55b9e3970e7f3e0c03d3ad 44964 
xstarfish_1.1+ds.orig.tar.xz
 d4e9c2e9161799643d48c486d496606a455f750c49140741124c14af6574ff18 9784 
xstarfish_1.1+ds-1.debian.tar.xz
 647c81d95ffd413ed290b582211aa7f295d7c71147a662ad8bc426fe7be24782 5795 
xstarfish_1.1+ds-1_source.buildinfo
Files:
 1ff5a996f262a6b1826a5b3474421d72 1716 utils optional xstarfish_1.1+ds-1.dsc
 3374d3a4ceeb6d0b3382c35eebf0dbfe 44964 utils optional 
xstarfish_1.1+ds.orig.tar.xz
 a308fc2bab7267dde7cdfaad357cbfe0 9784 utils optional 
xstarfish_1.1+ds-1.debian.tar.xz
 724f128516cc01e143f809b498068b4f 5795 utils optional 
xstarfish_1.1+ds-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl53zLIACgkQweDZLphv
fH61Fg/+Iy6hbIhVw4k3JucXFNB1fh5Hkjf+wNW6nJfhNoN2fjU4FRDZSR221DQ1
krRPUogyTJTsWUzv74HybeYcwveqSKuhdbeiMTxws9e/8WXllUXj7rG2IY3AbLXN
HHIlML1KFSGqPDo9gR8CpzKZEYSL/1bifQiYOSQHF1cnnQJstFzIM/JZfFLwVjJY

Bug#392396: marked as done (xstarfish: starfish-1.1/unix/.AppleDouble/zut-1.5.tar.gz corrupted)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:06:15 +
with message-id 
and subject line Bug#392396: fixed in xstarfish 1.1+ds-1
has caused the Debian Bug report #392396,
regarding xstarfish: starfish-1.1/unix/.AppleDouble/zut-1.5.tar.gz corrupted
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.)


-- 
392396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=392396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xstarfish
Version: 1.1
Severity: minor

While testing an automated script that scans all debian source
packages and recursively enters compressed archives I noticed that
starfish-1.1/unix/.AppleDouble/zut-1.5.tar.gz fails to unpack:

$ tar tzf wpac-applet-1.2.1.orig/doc.tar.gz
tar: wpac-applet-1.2.1.orig/doc.tar.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error exit delayed from previous errors

This is bug is really almost nitpicking but if you have extra time
please consider trying to figure out what the problem really is.
Perhaps this file is not needed at all? I would have reported this bug
to upstream but the url in debian/copyright,

http://www.redplanetsw.com/starfish

seems to be 404 nowadays.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.32sauna0
Locale: LANG=C, LC_CTYPE=fi_FI (charmap=ISO-8859-1)

--- End Message ---
--- Begin Message ---
Source: xstarfish
Source-Version: 1.1+ds-1
Done: Adam Borowski 

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated xstarfish package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 22 Mar 2020 02:57:33 +0100
Source: xstarfish
Architecture: source
Version: 1.1+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Closes: 392396 810078 885953
Changes:
 xstarfish (1.1+ds-1) unstable; urgency=medium
 .
   * Orphan the package.
   * Repack the .orig tarball to remove binaries from a proprietary MacOS
 tool which cause errors on QA (bad filenames, masquerading as .gz),
 precompiled source, old Debian packaging.  Closes: #392396, #885953
   * Drop pre-cretaceous Provides/Replaces.
   * Ack NMU.  Closes: #810078
Checksums-Sha1:
 3de9926b1adcd7d652b9a2f762a8d835716b3975 1716 xstarfish_1.1+ds-1.dsc
 bc21a7a90074c3eb04c751d7ad77d847a45ed9dd 44964 xstarfish_1.1+ds.orig.tar.xz
 8e12fb12ac0d4bbc35793e1d8c77783b740eca13 9784 xstarfish_1.1+ds-1.debian.tar.xz
 b08b83bf00d7f2c43a39a1ab7c1b0d00e35139a1 5795 
xstarfish_1.1+ds-1_source.buildinfo
Checksums-Sha256:
 23b36139ed45266cf1608829b31464dd0e0cfa68531e31b016f8a2a0ed8cdec6 1716 
xstarfish_1.1+ds-1.dsc
 c5ef6aef3757b2c70179d6ecaa19cf14fcbcd2c04c55b9e3970e7f3e0c03d3ad 44964 
xstarfish_1.1+ds.orig.tar.xz
 d4e9c2e9161799643d48c486d496606a455f750c49140741124c14af6574ff18 9784 
xstarfish_1.1+ds-1.debian.tar.xz
 647c81d95ffd413ed290b582211aa7f295d7c71147a662ad8bc426fe7be24782 5795 
xstarfish_1.1+ds-1_source.buildinfo
Files:
 1ff5a996f262a6b1826a5b3474421d72 1716 utils optional xstarfish_1.1+ds-1.dsc
 3374d3a4ceeb6d0b3382c35eebf0dbfe 44964 utils optional 
xstarfish_1.1+ds.orig.tar.xz
 a308fc2bab7267dde7cdfaad357cbfe0 9784 utils optional 
xstarfish_1.1+ds-1.debian.tar.xz
 724f128516cc01e143f809b498068b4f 5795 utils optional 
xstarfish_1.1+ds-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl53zLIACgkQweDZLphv
fH61Fg/+Iy6hbIhVw4k3JucXFNB1fh5Hkjf+wNW6nJfhNoN2fjU4FRDZSR221DQ1
krRPUogyTJTsWUzv74HybeYcwveqSKuhdbeiMTxws9e/8WXllUXj7rG2IY3AbLXN
HHIlML1KFSGqPDo9gR8CpzKZEYSL/1bifQiYOSQHF1cnnQJstFzIM/JZfFLwVjJY
sRpeZl7QUaCTMOhddpQmsvu98TOfLOjrRZC1ZeClcICyy3F8yLaJo/BwiDrwu20n
M3wwC/9oCyVcPkas1eGBsVdT0FMkl9hVXwbBzCaa0WYgam7D7Wmu7eFb7BWZQcGf
kgLqbky9mYYhpNM49ZcLcT+cYvo/PJWwJQaqYEUeRO8psGR8GjXUBQfGnmdkv6uk

Bug#810078: marked as done (xstarfish: diff for NMU version 1.1-11.1)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 21:06:15 +
with message-id 
and subject line Bug#810078: fixed in xstarfish 1.1+ds-1
has caused the Debian Bug report #810078,
regarding xstarfish: diff for NMU version 1.1-11.1
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.)


-- 
810078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810078
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xstarfish
Version: 1.1-11
Severity: normal
Tags: patch pending

Dear maintainer,

I've prepared an NMU for xstarfish (versioned as 1.1-11.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru xstarfish-1.1/debian/changelog xstarfish-1.1/debian/changelog
--- xstarfish-1.1/debian/changelog  2010-08-12 21:48:02.0 +0200
+++ xstarfish-1.1/debian/changelog  2016-01-06 10:55:22.0 +0100
@@ -1,3 +1,13 @@
+xstarfish (1.1-11.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix build failure with ld --as-needed. LP: #832847, using patch from doko
+(Closes: #641274)
+  * Apply patch for libpng transistion, patch from Nobuhiro(Closes: #635704)
+  * Also, change B-D to libpng-dev (Closes: #662570)
+
+ -- Tobias Frost   Wed, 06 Jan 2016 10:55:22 +0100
+
 xstarfish (1.1-11) unstable; urgency=low
 
   * New maintainer (Closes: #486776)
diff -Nru xstarfish-1.1/debian/control xstarfish-1.1/debian/control
--- xstarfish-1.1/debian/control2010-08-12 06:18:41.0 +0200
+++ xstarfish-1.1/debian/control2016-01-06 10:48:40.0 +0100
@@ -2,7 +2,7 @@
 Section: utils
 Priority: optional
 Maintainer: Simon Fondrie-Teitler 
-Build-Depends: debhelper (>=5), libpng12-dev, libx11-dev, xbitmaps
+Build-Depends: debhelper (>=5), libpng-dev, libx11-dev, xbitmaps
 Standards-Version: 3.9.1
 
 Package: xstarfish
@@ -15,4 +15,4 @@
  XStarfish generates colourful, tiled images for your background using random
  numbers fed through mathematical functions. It does not use source image
  files, so it can generate its images nearly forever without running out of
- material. 
+ material.
diff -Nru xstarfish-1.1/debian/patches/debian-changes-1.1-11.1 
xstarfish-1.1/debian/patches/debian-changes-1.1-11.1
--- xstarfish-1.1/debian/patches/debian-changes-1.1-11.11970-01-01 
01:00:00.0 +0100
+++ xstarfish-1.1/debian/patches/debian-changes-1.1-11.12016-01-06 
10:42:30.0 +0100
@@ -0,0 +1,40 @@
+Description: Upstream changes introduced in version 1.1-11.1
+ This patch has been created by dpkg-source during the package build.
+ Here's the last changelog entry, hopefully it gives details on why
+ those changes were made:
+ .
+ xstarfish (1.1-11.1) unstable; urgency=low
+ .
+   * Non-maintainer upload.
+   * libpng transition.
+ .
+ The person named in the Author field signed this changelog entry.
+Author: Nobuhiro Iwamatsu 
+
+---
+The information above should follow the Patch Tagging Guidelines, please
+checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
+are templates for supplementary fields that you might want to add:
+
+Origin: , 
+Bug: 
+Bug-Debian: http://bugs.debian.org/
+Bug-Ubuntu: https://launchpad.net/bugs/
+Forwarded: 
+Reviewed-By: 
+Last-Update: 
+
+--- xstarfish-1.1.orig/unix/makepng.c
 xstarfish-1.1/unix/makepng.c
+@@ -79,7 +79,11 @@ void MakePNGFile(StarfishRef tex, const
+   if(theInfoPtr)
+   {
+   /* set up the png error handling. */
++#if PNG_LIBPNG_VER_MAJOR >= 1 && PNG_LIBPNG_VER_MINOR >= 4
++  if (setjmp(png_jmpbuf((theWritePtr
++#else
+   if (setjmp(theWritePtr->jmpbuf))
++#endif
+   {
+   png_destroy_write_struct(, );
+   fclose(theFile);
diff -Nru xstarfish-1.1/debian/patches/debian-changes-1.1-11ubuntu1 
xstarfish-1.1/debian/patches/debian-changes-1.1-11ubuntu1
--- xstarfish-1.1/debian/patches/debian-changes-1.1-11ubuntu1   1970-01-01 
01:00:00.0 +0100
+++ xstarfish-1.1/debian/patches/debian-changes-1.1-11ubuntu1   2016-01-06 
10:43:46.0 +0100
@@ -0,0 +1,47 @@
+Description: Upstream changes introduced in version 1.1-11ubuntu1
+ This patch has been created by dpkg-source during the package build.
+ Here's the last changelog entry, hopefully it gives details on why
+ those changes were made:
+ .
+ xstarfish (1.1-11ubuntu1) oneiric; urgency=low
+ .
+   * Fix build failure with ld --as-needed. LP: #832847.
+ .
+ The person named in the Author field signed this changelog entry.
+Author: Matthias Klose 
+Bug-Ubuntu: 

Bug#954887: marked as done (Returning UPnP response with 200 items out of 246 total matches)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 22:03:54 +0100
with message-id 

and subject line Re: Bug#954887: Acknowledgement (Returning UPnP response with 
200 items out of 246 total matches)
has caused the Debian Bug report #954887,
regarding Returning UPnP response with 200 items out of 246 total matches
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.)


-- 
954887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vlc
Version: 3.0.8-0+deb10u1

It seems that VLC cannot display all the Movies from my kodi
installation (over UPnP).

For some reason I see in the debug log of kodi that only a portion of
the files are being send, it looks as if this is chunked into section
of 200 movies, the remaining should be requested.

Log from kodi:

LibreELEC # grep UPnP /storage/.kodi/temp/kodi.log | grep -v videodb
2020-03-24 21:35:20.840 T:1484030848   DEBUG: UPnP Translated id to
'virtualpath://upnproot/'
2020-03-24 21:35:20.841 T:1484030848INFO: UPnP: Received Browse
DirectChildren request for object '0', with sort criteria
2020-03-24 21:35:20.843 T:1484030848   DEBUG: Building UPnP response
with filter '*', starting @ 0 with 5000 requested
2020-03-24 21:35:20.843 T:1484030848   DEBUG: UPnP: Building didl for
object 'musicdb://'
2020-03-24 21:35:20.844 T:1484030848   DEBUG: UPnP: Building didl for
object 'library://video/'
2020-03-24 21:35:20.844 T:1484030848   DEBUG: Returning UPnP response
with 2 items out of 2 total matches
2020-03-24 21:35:31.209 T:1484030848   DEBUG: UPnP Translated id to
'library://video/'
2020-03-24 21:35:31.210 T:1484030848INFO: UPnP: Received Browse
DirectChildren request for object 'library://video/', with sort
criteria
2020-03-24 21:35:31.231 T:1484030848   DEBUG: Building UPnP response
with filter '*', starting @ 0 with 5000 requested
2020-03-24 21:35:31.281 T:1484030848   DEBUG: UPnP: Building didl for
object 'library://video/movies/'
2020-03-24 21:35:31.301 T:1484030848   DEBUG: UPnP: Building didl for
object 'library://video/musicvideos/'
2020-03-24 21:35:31.313 T:1484030848   DEBUG: UPnP: Building didl for
object 'library://video/files.xml/'
2020-03-24 21:35:31.326 T:1484030848   DEBUG: UPnP: Building didl for
object 'library://video/playlists.xml/'
2020-03-24 21:35:31.327 T:1484030848   DEBUG: Returning UPnP response
with 4 items out of 4 total matches
2020-03-24 21:35:47.962 T:1484030848   DEBUG: UPnP Translated id to
'library://video/movies/'
2020-03-24 21:35:47.962 T:1484030848INFO: UPnP: Received Browse
DirectChildren request for object 'library://video/movies/', with sort
criteria
2020-03-24 21:35:47.990 T:1484030848   DEBUG: Building UPnP response
with filter '*', starting @ 0 with 5000 requested
2020-03-24 21:35:48.037 T:1484030848   DEBUG: UPnP: Building didl for
object 'library://video/movies/recentlyaddedmovies.xml/'
2020-03-24 21:35:48.054 T:1484030848   DEBUG: UPnP: Building didl for
object 'library://video/movies/genres.xml/'
2020-03-24 21:35:48.066 T:1484030848   DEBUG: UPnP: Building didl for
object 'library://video/movies/titles.xml/'
2020-03-24 21:35:48.079 T:1484030848   DEBUG: UPnP: Building didl for
object 'library://video/movies/years.xml/'
2020-03-24 21:35:48.091 T:1484030848   DEBUG: UPnP: Building didl for
object 'library://video/movies/actors.xml/'
2020-03-24 21:35:48.103 T:1484030848   DEBUG: UPnP: Building didl for
object 'library://video/movies/directors.xml/'
2020-03-24 21:35:48.116 T:1484030848   DEBUG: UPnP: Building didl for
object 'library://video/movies/studios.xml/'
2020-03-24 21:35:48.128 T:1484030848   DEBUG: UPnP: Building didl for
object 'library://video/movies/sets.xml/'
2020-03-24 21:35:48.140 T:1484030848   DEBUG: UPnP: Building didl for
object 'library://video/movies/country.xml/'
2020-03-24 21:35:48.152 T:1484030848   DEBUG: UPnP: Building didl for
object 'library://video/movies/tags.xml/'
2020-03-24 21:35:48.153 T:1484030848   DEBUG: Returning UPnP response
with 10 items out of 10 total matches
2020-03-24 21:35:54.498 T:1484030848   DEBUG: UPnP Translated id to
'library://video/movies/titles.xml/'
2020-03-24 21:35:54.498 T:1484030848INFO: UPnP: Received Browse
DirectChildren request for object
'library://video/movies/titles.xml/', with sort criteria
2020-03-24 21:35:54.722 T:1484030848   DEBUG: Building UPnP response
with filter '*', starting @ 0 with 5000 requested
2020-03-24 21:35:55.648 T:1484030848   DEBUG: Returning UPnP response
with 200 items out of 246 total matches
--- End Message ---
--- Begin Message ---
Turns out this is a server side 

Bug#940369: marked as done (RFA: golang-github-influxdata-influxql)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 20:45:46 +
with message-id 
and subject line Bug#940369: fixed in golang-github-influxdata-influxql 1.1.0-1
has caused the Debian Bug report #940369,
regarding RFA: golang-github-influxdata-influxql
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.)


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

Hello!

I'd like to find new maintainers for some of my packages because I have
had less time for Debian. I'd like to focus the small amount of time
that I have for Debian on other things.

For now, I intend to do my best to keep maintaining this package.
However, I will probably retitle this bug with the 'O:' prefix at some
point, indicating that I have orphaned it.

Feel free to upload a new version of the package and remove me from the
uploaders in debian/control.

Feel free to contact me with any questions. Also note that I always
willing to sponsor uploads!

Cheers,

-- 
Aleaxandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: golang-github-influxdata-influxql
Source-Version: 1.1.0-1
Done: Nilesh Patra 

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

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

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated 
golang-github-influxdata-influxql package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 21 Mar 2020 15:51:23 +0530
Source: golang-github-influxdata-influxql
Architecture: source
Version: 1.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Nilesh Patra 
Closes: 940369
Changes:
 golang-github-influxdata-influxql (1.1.0-1) unstable; urgency=medium
 .
   [ Nilesh Patra ]
   * New upstream version 1.1.0
   * Drop compat, switch to debhelper-compat version 12
   * Add upstream/metadata
   * Add myself to uploaders (Closes: #940369)
 + Remove Alexandre from uploaders
 + Thank you Alexandre for your work so far
   * Bump standards version to 4.5.0
   * Fix copyright
   * Fix control with cme
 .
   [ Utkarsh Gupta ]
   * Remove needless Files-Excluded section from d/copyright
Checksums-Sha1:
 e07e8de72f1e660a0db795410783ef5743e6f9f9 2341 
golang-github-influxdata-influxql_1.1.0-1.dsc
 39b3bc4a1320b8436f45f399d447a087f6e87732 95012 
golang-github-influxdata-influxql_1.1.0.orig.tar.gz
 21446d9a6d2b4617eb37c9abfc11c93209bbd34b 3040 
golang-github-influxdata-influxql_1.1.0-1.debian.tar.xz
 ed8ab24ece4f9407debbc0be586f893feabb9af3 6162 
golang-github-influxdata-influxql_1.1.0-1_amd64.buildinfo
Checksums-Sha256:
 616fd9bd0ff4e332306a3f3d5a9d65ae0b87fc97f0574f4c4850282f3a2d11cb 2341 
golang-github-influxdata-influxql_1.1.0-1.dsc
 400cab3a640af99fc658d39be4d862b51973dd0d9f0ca274474c91c45b14e1a2 95012 
golang-github-influxdata-influxql_1.1.0.orig.tar.gz
 9ffdcf2dbdd14a76667f18cdd3971f09224b6674007b388d96b3d7175aa32bf6 3040 
golang-github-influxdata-influxql_1.1.0-1.debian.tar.xz
 03a4d168be5a5c52d8420d1a14cfacfcab3d9414ab41ca98b1aa99ded9f674a7 6162 
golang-github-influxdata-influxql_1.1.0-1_amd64.buildinfo
Files:
 abb06c7b9aff517219bb5c8a98c63998 2341 devel optional 
golang-github-influxdata-influxql_1.1.0-1.dsc
 986d50d6d934d1cf60864923ee54a3a8 95012 devel optional 
golang-github-influxdata-influxql_1.1.0.orig.tar.gz
 043e20b6d65ca78197a9feabc6e469d3 3040 devel optional 
golang-github-influxdata-influxql_1.1.0-1.debian.tar.xz
 280c81c2e3734e6569beefc9aa4b4b83 6162 devel optional 
golang-github-influxdata-influxql_1.1.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAl56aOoACgkQgj6WdgbD
S5bRXBAAk0PcSfnTWn8KG7CvtRgas5L1SjzeB/3Vjrf3mIKFXlaNxcVj31bQqlWi
PNrYTyNhnMPha7TMJCtkKejqJpaMuG4AboNiZneKRGfPA55pE/ySSL6jsyXjyQuH
GQULkkynHRRz+WELQOAEup92NzMKhKKLP29xuP7HzUN4raUiSzQSvO5E5OZSXJoG
1rzgSEC8jBWHj8t4eFILOsWKMiaORaMRJXrc0ORSeQYriWux5aHit6Xs75E9LTqY

Bug#954750: marked as done (libgcc-9-dev: Missing include/sanitizer/)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 20:45:20 +
with message-id 
and subject line Bug#954750: fixed in gcc-9 9.3.0-8
has caused the Debian Bug report #954750,
regarding libgcc-9-dev: Missing include/sanitizer/
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.)


-- 
954750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgcc-9-dev
Version: 9.3.0-6

Hi,

Since last upgrade of my sid chroot, the include directory
"include/sanitizer/" is missing from libgcc-9-dev:amd64.

Before, there was:
/usr/lib/gcc/x86_64-linux-gnu/9/include/sanitizer/asan_interface.h
/usr/lib/gcc/x86_64-linux-gnu/9/include/sanitizer/common_interface_defs.h
/usr/lib/gcc/x86_64-linux-gnu/9/include/sanitizer/lsan_interface.h
/usr/lib/gcc/x86_64-linux-gnu/9/include/sanitizer/tsan_interface.h

Regards,
Arnaud Giersch
--- End Message ---
--- Begin Message ---
Source: gcc-9
Source-Version: 9.3.0-8
Done: Matthias Klose 

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-9 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 18:41:59 +0100
Source: gcc-9
Architecture: source
Version: 9.3.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 954750
Changes:
 gcc-9 (9.3.0-8) unstable; urgency=medium
 .
   * Update to git 20200324 from the gcc-9 branch.
 - Fix PR tree-optimization/94125, PR target/90763 (PPC).
   * libgcc-N-dev: Include sanitizer headers again. Closes: #954750.
   * gm2: Define lang_register_spec_functions for jit. Addresses: #954438.
   * Generate dependencies on libgcc-sN if not building the common packages.
Checksums-Sha1:
 6ce74a2bb6216d0187e654fc1bf94fb2cd1318d1 22427 gcc-9_9.3.0-8.dsc
 13f6cf28f51175b786efc7798240f118b9eca053 584896 gcc-9_9.3.0-8.debian.tar.xz
 4213983c8b2180ae004808bb35308d60803d4b97 10146 gcc-9_9.3.0-8_source.buildinfo
Checksums-Sha256:
 34e2aefd2df0862cfb5ba2872eefca24867107a4b14f042c07da2eced1b679b5 22427 
gcc-9_9.3.0-8.dsc
 69dc0f53f2f67f2a773a7a36520bdbb2decd5ad94ed9af55317e15723b4c2c13 584896 
gcc-9_9.3.0-8.debian.tar.xz
 c0668ceed98ab4968c2a28d22cb1c5991cbe3b22bc5f9ade161f81c497c6e251 10146 
gcc-9_9.3.0-8_source.buildinfo
Files:
 85f697e4bf88fe1123107bab74ecc5af 22427 devel optional gcc-9_9.3.0-8.dsc
 46bdd8c8a4fb311c369fc70baa23395e 584896 devel optional 
gcc-9_9.3.0-8.debian.tar.xz
 8abe7bfa72bb87da5b1e140f5bd15cda 10146 devel optional 
gcc-9_9.3.0-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl56ZEQQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9ZhMEADLErA/FbXr+ZU9r3fPervAoIb53ychn22W
oVm6xaiCrJYVI5mMYEYuSl1Gqs65uGh6ZYnnyrN9/SFYtKcVJ5mI6PaXKzgvDBDv
FRKDirARG99NTgHQukxfp/ZaZhqMv0KF3nmFPAjDsS27QsRinw0hR3dMMpeS1IrI
3ufqzMKsl2YCiuU3oLUeHIBvca+Y+bgPfUAjfqgzYQlcf+eb2sjJGVr8/UG+C5qu
XhV6ezcE+g/LzfpMdH2ur1sR5ohwaP0J9PVrcrt6zkZlMO/uy07t7K7+CfKPXs5f
iU+d+Wr+bhZsWNctA/LFS/FiNzICRS49PwfNLsbUIdHajM2GHd5G7Y2pas2qsQCc
o32SS2eXRxxlxdzPHYpi+hzPzmf09mqJIllzEuTXa03arlzKVrkjNNHqvW30eyFn
0CS/efODE4oC7+HpRevl5rY4FNC/POxu3zWxbt5Z1/zd8Dmcf4vwlqDLYgU/6cog
hcnfJZWETSLWafUuErTFkaD8dU4hd6rS0NniG/cS4EvweESIcx/miOQC9Zje6J5m
68brvb0srpUbMurMVTNhYJLoNCG+I9SSHRzStW+XPxNdZNN/vhuZp5KRJ+4fP/+n
WJ3oAmjNWCT1akpYhmuu/FUi/89cSmaMnuOPusnPD09WpMv6f8jmtheTHL7oDU7u
DPkM0tTW2g==
=/hIh
-END PGP SIGNATURE End Message ---

Bug#940359: marked as done (RFA: golang-github-glycerine-go-unsnap-stream)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 20:45:38 +
with message-id 
and subject line Bug#940359: fixed in golang-github-glycerine-go-unsnap-stream 
0.0~git20190901.81cf024-1
has caused the Debian Bug report #940359,
regarding RFA: golang-github-glycerine-go-unsnap-stream
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.)


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

Hello!

I'd like to find new maintainers for some of my packages because I have
had less time for Debian. I'd like to focus the small amount of time
that I have for Debian on other things.

For now, I intend to do my best to keep maintaining this package.
However, I will probably retitle this bug with the 'O:' prefix at some
point, indicating that I have orphaned it.

Feel free to upload a new version of the package and remove me from the
uploaders in debian/control.

Feel free to contact me with any questions. Also note that I always
willing to sponsor uploads!

Cheers,

-- 
Aleaxandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: golang-github-glycerine-go-unsnap-stream
Source-Version: 0.0~git20190901.81cf024-1
Done: Nilesh Patra 

We believe that the bug you reported is fixed in the latest version of
golang-github-glycerine-go-unsnap-stream, which is due to be installed in the 
Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated 
golang-github-glycerine-go-unsnap-stream package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 21 Mar 2020 15:15:00 +0530
Source: golang-github-glycerine-go-unsnap-stream
Architecture: source
Version: 0.0~git20190901.81cf024-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Nilesh Patra 
Closes: 940359
Changes:
 golang-github-glycerine-go-unsnap-stream (0.0~git20190901.81cf024-1) unstable; 
urgency=medium
 .
   [ Nilesh Patra ]
   * New upstream version 0.0~git20190901.81cf024
   * Drop compat, switch to debhelper-compat version 12
   * Add upstream/metadata
   * Add "Rules-Requires-Root:no"
   * Bump standards version to 4.5.0
   * Add myself to uploaders (Closes: #940359)
 + Remove Alexandre from uploaders
 + Thank you Alexandre for your work so far
   * Fix copyright
 .
   [ Utkarsh Gupta ]
   * Remove needless Files-Excluded section from d/copyright
Checksums-Sha1:
 607894ecad4f3254a6af1596aafdacc308021a44 2547 
golang-github-glycerine-go-unsnap-stream_0.0~git20190901.81cf024-1.dsc
 06c6b8ca129834db9f59be23cb2b928758e8c1df 18032 
golang-github-glycerine-go-unsnap-stream_0.0~git20190901.81cf024.orig.tar.xz
 45c7e48dc5ba1f61ce855c843b0a22d533ff652d 2988 
golang-github-glycerine-go-unsnap-stream_0.0~git20190901.81cf024-1.debian.tar.xz
 f323e8f2e6ffece798423e19a710a8743b0bd861 6209 
golang-github-glycerine-go-unsnap-stream_0.0~git20190901.81cf024-1_amd64.buildinfo
Checksums-Sha256:
 4b627ea567b571958b45389c799a0c374871ac49cc1f71557c1ee9acc37bbc9f 2547 
golang-github-glycerine-go-unsnap-stream_0.0~git20190901.81cf024-1.dsc
 506ccf745937d954f2d57fa97f39efcedc60bf9ee2a3517c46ef35b80731ff1e 18032 
golang-github-glycerine-go-unsnap-stream_0.0~git20190901.81cf024.orig.tar.xz
 62b38e40a14b4a32d458ed29da7c696c4224fc9aee925941f02de7db877328f2 2988 
golang-github-glycerine-go-unsnap-stream_0.0~git20190901.81cf024-1.debian.tar.xz
 a8fd9080720739d11e0dd023e1b14a7e2c5f7d493f93df0b288dd0ec89259a36 6209 
golang-github-glycerine-go-unsnap-stream_0.0~git20190901.81cf024-1_amd64.buildinfo
Files:
 00515a2b674a9666d6ad59bb49c2f344 2547 devel optional 
golang-github-glycerine-go-unsnap-stream_0.0~git20190901.81cf024-1.dsc
 f210d3b73e5ab3f9f611fcd0d5310bb3 18032 devel optional 
golang-github-glycerine-go-unsnap-stream_0.0~git20190901.81cf024.orig.tar.xz
 e5699e85d5823f67f32541204654daae 2988 devel optional 
golang-github-glycerine-go-unsnap-stream_0.0~git20190901.81cf024-1.debian.tar.xz
 19d70ccee64f5e1370a5793fc145fdf1 6209 devel optional 

Bug#940442: marked as done (RFA: golang-go.uber-zap)

[Debian Bug Tracking System]

Your message dated Wed, 25 Mar 2020 01:32:02 +0530
with message-id 

and subject line Re: RFA: golang-go.uber-zap
has caused the Debian Bug report #940442,
regarding RFA: golang-go.uber-zap
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.)


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

Hello!

I'd like to find new maintainers for some of my packages because I have
had less time for Debian. I'd like to focus the small amount of time
that I have for Debian on other things.

For now, I intend to do my best to keep maintaining this package.
However, I will probably retitle this bug with the 'O:' prefix at some
point, indicating that I have orphaned it.

Feel free to upload a new version of the package and remove me from the
uploaders in debian/control.

Feel free to contact me with any questions. Also note that I always
willing to sponsor uploads!

Cheers,

-- 
Aleaxandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi,
I have taken up the ownership for this package, updated in salsa[1] and
Andreas Henriksson sponsored an upload as well.
It had a long standing RC bug which has been closed as well.

[1]: https://salsa.debian.org/go-team/packages/golang-go.uber-zap

Regards,
Nilesh
--- End Message ---

Bug#940374: marked as done (RFA: golang-github-jackpal-gateway)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 19:34:58 +
with message-id 
and subject line Bug#940374: fixed in golang-github-jackpal-gateway 1.0.4-5
has caused the Debian Bug report #940374,
regarding RFA: golang-github-jackpal-gateway
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.)


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

Hello!

I'd like to find new maintainers for some of my packages because I have
had less time for Debian. I'd like to focus the small amount of time
that I have for Debian on other things.

For now, I intend to do my best to keep maintaining this package.
However, I will probably retitle this bug with the 'O:' prefix at some
point, indicating that I have orphaned it.

Feel free to upload a new version of the package and remove me from the
uploaders in debian/control.

Feel free to contact me with any questions. Also note that I always
willing to sponsor uploads!

Cheers,

-- 
Aleaxandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: golang-github-jackpal-gateway
Source-Version: 1.0.4-5
Done: Nilesh Patra 

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

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

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated 
golang-github-jackpal-gateway package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 21 Mar 2020 16:09:35 +0530
Source: golang-github-jackpal-gateway
Architecture: source
Version: 1.0.4-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Nilesh Patra 
Closes: 940374
Changes:
 golang-github-jackpal-gateway (1.0.4-5) unstable; urgency=medium
 .
   [ Michael Stapelberg ]
   * update debian/gitlab-ci.yml (using salsa.debian.org/go-team/ci/cmd/ci)
 .
   [ Nilesh Patra ]
   * Drop compat, switch to debhelper-compat
   * Add upstream/metadata
   * Use https
   * Bump standards version to 4.5.0
   * Add myself to uploaders (Closes: #940374)
 - Remove Alexandre from Uploaders field.
   - Thank you, Alexandre, for your work so far.
   * Fix control with cme
Checksums-Sha1:
 a3fea77d2084227f49aebb1da325d8f8736efc56 2273 
golang-github-jackpal-gateway_1.0.4-5.dsc
 155a32cef0f5bd04838f87ecfb0a2220d1972d50 3084 
golang-github-jackpal-gateway_1.0.4-5.debian.tar.xz
 badf8c7e37032c83a347a1cfd1d097089cacca4e 5977 
golang-github-jackpal-gateway_1.0.4-5_amd64.buildinfo
Checksums-Sha256:
 d8c79766c12e90c8166416b97d5618e0df3ef59c190d208240b3202a03a58364 2273 
golang-github-jackpal-gateway_1.0.4-5.dsc
 aecf0babe724bce5c61e175a3c6fde137bdfd31964e89a56990efa52ec14eac0 3084 
golang-github-jackpal-gateway_1.0.4-5.debian.tar.xz
 f99d05b90a7e1d479e671c6fa1bbe2e57c307670ff884acfb9396f87ebe7c5b3 5977 
golang-github-jackpal-gateway_1.0.4-5_amd64.buildinfo
Files:
 d17a4f5e999b9998fe81ebdeb2da46a0 2273 devel optional 
golang-github-jackpal-gateway_1.0.4-5.dsc
 d6bb439182c87daf16fa3e089345e11c 3084 devel optional 
golang-github-jackpal-gateway_1.0.4-5.debian.tar.xz
 c49200650e70c11963e89ef9c1fddf59 5977 devel optional 
golang-github-jackpal-gateway_1.0.4-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAl56W6MACgkQgj6WdgbD
S5b0hg/8DhcRHXqjZVSlxQYN6O42l41lFUSZJuAVCyAm5Cb4i8WgY2vcwNtXpHRq
YTtkD3KBYz+CzzEtatCBIm2hy2mtEug+F311sX6I2TyC5MkNdCGMsDHj3zjM5P35
ZCULc+WF++AZ9SN3ulieqV3Yb0Vpbja1NB6Nq87cCS1rMWIeOSKEVdfYis9S+qA3
A3hl6j7bUfB7oBRlUwQ4AccyStTDeEgIMy/0pBcwDNynT8tLn4Aj6+oMtyw4MHDx
Z9ljuoCJduUKBhJge0TnK+cg4QuU6Q16c56D9ZbT9o4iMbntELssm296S+ZWlRw2
cISL6MHJ8fOkQRsbqmJdP3sw5zT+3YdvUDMiCwUPeP3M81rYAYvIV8LsFJOL/q5M
rO3op56XHxWM6Y3gFgVhVtb3laz+wwmjbmIOxeDfi0MqqeaM2ohmv5prMit4wBfk
0X8CHUUeV/Nn5EMAQWpbBoCOU9I0dpdqjOZ0apPLqiR2YaJpzxDV856w7pIfbbf0
VZL9SUTO/Gnqt3X3lTsrz3Dynu5UKDEFPg3auZlsHDES4N5UzjiUdyLBGSINW6yQ
dWyt+bUiPjA+4TvbUjRzCYcDNkFup6kBVKHY1VYS6i6sYDp6uv1yAQpurtJOzauv

Bug#954642: marked as done (fonttools: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.7 3.8" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 19:19:39 +
with message-id 
and subject line Bug#954642: fixed in fonttools 4.5.0-1
has caused the Debian Bug report #954642,
regarding fonttools: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p "3.7 3.8" returned exit code 13
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.)


-- 
954642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fonttools
Version: 4.4.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 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 '/<>'
> python3 MetaTools/buildUCD.py --ucd-path=/usr/share/unicode
> loading 'Blocks.txt' from local directory '/usr/share/unicode'
> saved new file: '/<>/Lib/fontTools/unicodedata/Blocks.py'
> loading 'PropertyValueAliases.txt' from local directory '/usr/share/unicode'
> loading 'Scripts.txt' from local directory '/usr/share/unicode'
> saved new file: '/<>/Lib/fontTools/unicodedata/Scripts.py'
> loading 'ScriptExtensions.txt' from local directory '/usr/share/unicode'
> saved new file: 
> '/<>/Lib/fontTools/unicodedata/ScriptExtensions.py'
> PYTHONPATH="./Lib" python3 MetaTools/buildTableList.py
> dh_auto_build
> I: pybuild base:217: /usr/bin/python3.7 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.7/build/fontTools
> copying Lib/fontTools/unicode.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools
> copying Lib/fontTools/__init__.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools
> copying Lib/fontTools/fontBuilder.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools
> copying Lib/fontTools/agl.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools
> copying Lib/fontTools/__main__.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools
> copying Lib/fontTools/merge.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools
> copying Lib/fontTools/ttx.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools
> copying Lib/fontTools/afmLib.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools
> creating /<>/.pybuild/cpython3_3.7/build/fontTools/encodings
> copying Lib/fontTools/encodings/__init__.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/encodings
> copying Lib/fontTools/encodings/MacRoman.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/encodings
> copying Lib/fontTools/encodings/codecs.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/encodings
> copying Lib/fontTools/encodings/StandardEncoding.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/encodings
> creating /<>/.pybuild/cpython3_3.7/build/fontTools/unicodedata
> copying Lib/fontTools/unicodedata/OTTags.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/unicodedata
> copying Lib/fontTools/unicodedata/__init__.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/unicodedata
> copying Lib/fontTools/unicodedata/Scripts.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/unicodedata
> copying Lib/fontTools/unicodedata/ScriptExtensions.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/unicodedata
> copying Lib/fontTools/unicodedata/Blocks.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/unicodedata
> creating /<>/.pybuild/cpython3_3.7/build/fontTools/subset
> copying Lib/fontTools/subset/__init__.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/subset
> copying Lib/fontTools/subset/__main__.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/subset
> copying Lib/fontTools/subset/cff.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/subset
> creating /<>/.pybuild/cpython3_3.7/build/fontTools/misc
> copying Lib/fontTools/misc/encodingTools.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/misc
> copying Lib/fontTools/misc/testTools.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/misc
> copying Lib/fontTools/misc/fixedTools.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/misc
> copying Lib/fontTools/misc/psCharStrings.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/misc
> copying Lib/fontTools/misc/__init__.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/misc
> copying Lib/fontTools/misc/etree.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/misc
> copying Lib/fontTools/misc/intTools.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/misc
> copying Lib/fontTools/misc/xmlReader.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/misc
> copying Lib/fontTools/misc/classifyTools.py -> 
> /<>/.pybuild/cpython3_3.7/build/fontTools/misc
> copying 

Bug#919387: marked as done (autopkgtest: missing build dependency on sysvinit-utils)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 20:18:41 +0100
with message-id 
and subject line Re: Bug#919387: autopkgtest: missing build dependency on 
sysvinit-utils
has caused the Debian Bug report #919387,
regarding autopkgtest: missing build dependency on sysvinit-utils
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.)


-- 
919387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: autopkgtest
Version: 5.7
Severity: important

One of the build time test cases make a call to the pidof command.
This command is provided through the sysvinit-utils package.

So, either the sysvinit-utils package needs to be added as a dependency
or the test case be changed to get rid of the pidof call

rrs@priyasi:/var/tmp/Debian-Build/development/autopkgtest/autopkgtest-5.7$ grep 
-Ri pidof *
ssh-setup/adb:adb $ADBOPTS shell 'while ! pidof accounts-daemon >/dev/null; 
do sleep 1; done'
ssh-setup/adb:adb $ADBOPTS shell 'kill `pidof system-settings-wizard` 
2>/dev/null'
ssh-setup/adb:while ! pidof powerd-cli >/dev/null; do 
sleep 0.1; done"
ssh-setup/adb:adb $ADBOPTS shell 'while ! pidof NetworkManager >/dev/null; 
do sleep 1; done'
tests/autopkgtest:self.assertEqual(subprocess.getoutput('pidof ' + 
procname), '')
17:58 ♒♒♒   ☺ 


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

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

Versions of packages autopkgtest depends on:
ii  apt-utils   1.8.0~alpha3
ii  libdpkg-perl1.19.2
ii  procps  2:3.3.15-2
ii  python3 3.7.1-3
ii  python3-debian  0.1.33

Versions of packages autopkgtest recommends:
pn  autodep8  

Versions of packages autopkgtest suggests:
pn  lxc   
pn  lxd   
ii  ovmf  0~20181115.85588389-2
ii  qemu-efi-aarch64  0~20181115.85588389-2
pn  qemu-efi-arm  
ii  qemu-system   1:3.1+dfsg-2+b1
ii  qemu-utils1:3.1+dfsg-2+b1
pn  schroot   
pn  vmdb2 
--- End Message ---
--- Begin Message ---
Hi Ritesh,

Thanks for the reply...

On 24-03-2020 06:59, Ritesh Raj Sarraf wrote:
> So yes, I think for this bug report, it can be closed given the
> package's attributes are set correct.

So, doing so now.

Paul



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

Processed: bts

[Debian Bug Tracking System]

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

> close 946439 2020.01.24-0.1
Bug #946439 [youtube-dl] youtube-dl needs python3.8 for dailymotion.com
Marked as fixed in versions youtube-dl/2020.01.24-0.1.
Bug #946439 [youtube-dl] youtube-dl needs python3.8 for dailymotion.com
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Re: Bug#925816: marked as done (qxw: ftbfs with GCC-9)

[Debian Bug Tracking System]

Processing control commands:

> reopen 925816
Bug #925816 [src:qxw] qxw: ftbfs with GCC-9
Bug 925816 is not marked as done; doing nothing.
> close 925826 15+1533136590.3beb971-8
Bug #925826 {Done: Steve McIntyre } [src:shim] shim: ftbfs 
with GCC-9
The source 'shim' and version '15+1533136590.3beb971-8' do not appear to match 
any binary packages
Ignoring request to alter fixed versions of bug #925826 to the same values 
previously set
Bug #925826 {Done: Steve McIntyre } [src:shim] shim: ftbfs 
with GCC-9
Bug 925826 is already marked as done; not doing anything.

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

Processed: Re: Bug#925816: marked as done (qxw: ftbfs with GCC-9)

[Debian Bug Tracking System]

Processing control commands:

> reopen 925816
Bug #925816 {Done: Steve McIntyre <93...@debian.org>} [src:qxw] qxw: ftbfs with 
GCC-9
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions qxw/20140331-1.1 and 
shim/15+1533136590.3beb971-8.
> close 925826 15+1533136590.3beb971-8
Bug #925826 [src:shim] shim: ftbfs with GCC-9
The source 'shim' and version '15+1533136590.3beb971-8' do not appear to match 
any binary packages
Marked as fixed in versions shim/15+1533136590.3beb971-8.
Bug #925826 [src:shim] shim: ftbfs with GCC-9
Marked Bug as done

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

Bug#950723: marked as done (dh_installsystemd: NOOP promise is unsafe)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 18:19:09 +
with message-id 
and subject line Bug#950723: fixed in debhelper 12.10
has caused the Debian Bug report #950723,
regarding dh_installsystemd: NOOP promise is unsafe
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.)


-- 
950723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 12
Severity: normal
Tags: d-i

Hello,
i was trying to build Serf locally for stretch using debhelper 12.
I started with golang-github-hashicorp-serf
(0.8.1+git20171021.c20a0b1~ds1-4~bpo9+1),
which is on the offical debain repo and did the following:

* Renamed `serf.service` inside debian/ to `serf@.service`
* in `debian/rules` i added `override_dh_installinit:`

When building the package it built but it didn't copy the templete unit
file `serf@.service`.
In DH_INSTALLSYSTEMD(1) is wriiten if `debian/package@.service` it
should be installed into lib/systemd/system/.

Then this was tested against unstable it didn't copy the templete
unit.

Adding :
```override_dh_installsystemd:
dh_installsystemd -pserf serf@.service
```
to `debian\rules` fixed the issue.

Thanks.
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 12.10
Done: Niels Thykier 

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Mar 2020 15:55:09 +
Source: debhelper
Architecture: source
Version: 12.10
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Closes: 939656 950723 951819 951917
Changes:
 debhelper (12.10) unstable; urgency=medium
 .
   [ Niels Thykier ]
   * dh_installsystemd.1: Improve documentation about tmpfiles that
 are now handled by dh_installtmpfiles in compat 13.
   * dh_installtmpfiles: Prefer debian/package.tmpfiles over
 debian/package.tmpfile, but accept the old path with a warning.
 Thanks to Michael Biebl for suggesting the change.
   * dh_strip: Automatically strip Link-Time Optimization (LTO)
 symbols from static archives.  The format is not stable between
 compiler versions.  Thanks to Matthias Klose for the
 suggestion and for providing the exact options.
 (Closes: #939656)
   * dh: Tweak the command-skipping optimization to skip commands
 in a few more cases when the command is known not to react to
 command line options.
   * dh,dh_installsytemd*: Work around broken NOOP promise caused by
 dh_installsystemd* using nonstandard "package@" prefix for
 pkgfiles.  Thanks to Badreddin Aboubakr and Andy Caldwell for
 reporting it.  (Closes: #950723, #951819)
 .
   [ Nicholas Guriev ]
   * cmake: Verbose autogen rules.
   * cmake: Skip install all dependency with compatibility level 13 and
 above.
 .
   [ Andy Caldwell ]
   * dh_installsystemduser: Fix bug that prevented dh_installsystemduser
 from installing parameterized services.  (Closes: #951819)
 .
   [ Translations ]
   * Update German translation (Chris Leick)  (Closes: #951917)
Checksums-Sha1:
 adef1db05ca8f20d5b93d1fec71524a7d5b0c885 1839 debhelper_12.10.dsc
 8171da063f17d95a74b23c87bb2bd1a98c4652b3 525416 debhelper_12.10.tar.xz
 75e0d34be7ca464dfdd9ba52182aa122a9763679 4606 debhelper_12.10_source.buildinfo
Checksums-Sha256:
 934871f9a113f24616d10dcfb3d3a39d916cb7a80e478b93656164f5d27995ab 1839 
debhelper_12.10.dsc
 74ef66f33d0a1ac8d854f9476b3ae8d08a65fadb6c7fa7e6155e62c52439676a 525416 
debhelper_12.10.tar.xz
 451b679c0d242580e656aceb7834dcffa8d5ad7101f43b67bc8308e332db8e25 4606 
debhelper_12.10_source.buildinfo
Files:
 3acd0bd939678b2c65986c4adc9eba70 1839 devel optional debhelper_12.10.dsc
 2e8b9ef9ed4a36b9b38cb3f453e900b7 525416 devel optional debhelper_12.10.tar.xz
 3e1de02e9214f38444b2cde00cceb2d3 4606 devel optional 
debhelper_12.10_source.buildinfo

-BEGIN PGP 

Bug#951819: marked as done (debhelper: dh_installsystemduser can't install parameterized services)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 18:19:09 +
with message-id 
and subject line Bug#951819: fixed in debhelper 12.10
has caused the Debian Bug report #951819,
regarding debhelper: dh_installsystemduser can't install parameterized services
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.)


-- 
951819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951819
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 12.1.1ubuntu1~ubuntu18.04.1
Severity: important
Tags: upstream

Dear Maintainer,

Attempting to use `dh_installsystemduser` to create a package with a
parameterized service/timer/etc. (e.g. package@.user.service) installs
the service definition file into a temporary directory for a package
called "package@", rather than "package".  This leads to the service not
being included in the final debian package.

Although I discovered this on the Ubuntu repackaging of the debhelper
package, the issue is still present in the trunk codebase:

https://salsa.debian.org/debian/debhelper/blob/master/dh_installsystemduser#L115-125

The fix is to copy what `dh_installsystemd` does, and to pass the
temporary directory through to `install_user_unit` so that all the
package files end up in the right place.

```perl
sub install_user_unit {
  my ($package, $name, $suffix, $path) = @_;

  my $unit = pkgfile($package, "user.$suffix");
  return if $unit eq '';

  install_dir($path);
  install_file($unit, "$path/$name.$suffix");
}
```

And (at the call site):

```perl
  for my $type (qw(service target socket path timer)) {
install_user_unit($package, $name, $type, "$tmpdir/usr/lib/systemd/user");
install_user_unit("${package}@", "${name}@", $type, 
"$tmpdir/usr/lib/systemd/user");
  }
```

Thanks,

Andy

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

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

Versions of packages debhelper depends on:
ii  autotools-dev20180224.1
ii  dh-autoreconf17
ii  dh-strip-nondeterminism  0.040-1.1~build1
ii  dpkg 1.19.0.5ubuntu2.3
ii  dpkg-dev 1.19.0.5ubuntu2.3
ii  dwz  0.12-2
ii  file 1:5.32-2ubuntu0.3
ii  libdpkg-perl 1.19.0.5ubuntu2.3
ii  man-db   2.8.3-2ubuntu0.1
ii  perl 5.26.1-6ubuntu0.3
ii  po-debconf   1.0.20

debhelper recommends no packages.

Versions of packages debhelper suggests:
ii  dh-make  2.201701

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 12.10
Done: Niels Thykier 

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Mar 2020 15:55:09 +
Source: debhelper
Architecture: source
Version: 12.10
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Closes: 939656 950723 951819 951917
Changes:
 debhelper (12.10) unstable; urgency=medium
 .
   [ Niels Thykier ]
   * dh_installsystemd.1: Improve documentation about tmpfiles that
 are now handled by dh_installtmpfiles in compat 13.
   * dh_installtmpfiles: Prefer debian/package.tmpfiles over
 debian/package.tmpfile, but accept the old path with a warning.
 Thanks to Michael Biebl for suggesting the change.
   * dh_strip: Automatically strip Link-Time Optimization (LTO)
 symbols from static archives.  The format is not stable between
 compiler versions.  Thanks to Matthias Klose for the
 

Bug#954726: marked as done (mftrace: FTBFS: dh_auto_test: error: make -j4 test VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 18:19:44 +
with message-id 
and subject line Bug#954726: fixed in mftrace 1.2.20+git20191022.3b4bc2e-2
has caused the Debian Bug report #954726,
regarding mftrace: FTBFS: dh_auto_test: error: make -j4 test VERBOSE=1 returned 
exit code 2
to be marked as done.

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

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


-- 
954726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mftrace
Version: 1.2.20+git20191022.3b4bc2e-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 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 '/<>'
> /usr/bin/python3 mftrace.py --glyphs 65 -V ecbi0900 &&  /usr/bin/python3 
> mftrace.py --glyphs 65 -V logo10 &&  /usr/bin/python3 mftrace.py --glyphs 65 
> -V cmr11 &
> This is METAFONT, Version 2.7182818 (TeX Live 2019/Debian) (preloaded base=mf)
> 
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/ecbi0900.mf
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exbase.mf)
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/ecbi.mf
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/extextit.mf
>  Ok (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exaccess.mf
>  Ok) (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/expseudo.mf
>  Ok) (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exileast.mf
>  Ok [158] [160] [161] [162] [163] [164] [165] [166] [167] [168] [169] [170]
> [171] [172] [173] [174] [175] [176] [177] [178] [179] [180] [181] [182]
> [183] [184] [185] [186] [187] [188])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exilwest.mf
>  Ok [224] [225] [226] [227] [228] [229] [230] [231] [232] [233] [234] [235]
> [236] [237] [238] [239] [240] [241] [242] [243] [244] [245] [246] [247]
> [248] [249] [250] [251] [252] [253] [254] [255])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exruwest.mf
>  Ok [192] [193] [194] [195] [196] [197] [198] [199] [200] [201] [202] [203]
> [204] [205] [206] [207] [208] [209] [210] [211] [212] [213] [214] [215]
> [216] [217] [218] [219] [220] [221] [222] [223])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exrueast.mf
>  Ok [128] [129] [130] [131] [132] [133] [134] [135] [136] [137] [138] [139]
> [140] [141] [142] [143] [144] [145] [146] [147] [148] [149] [150] [151]
> [152] [153] [154] [155] [156] [157])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exbraces.mf
>  Ok [94] [126] [23] [40] [41] [60] [124] [62] [91] [93] [92] [123] [125]
> [95] [127] [32])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/expunct.mf
>  Ok [14] [15] [19] [20] [13] [18] [33] [39] [42] [43] [44] [46] [47] [58]
> [59] [61] [96] [189] [17] [45] [16] [21] [22])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exaccent.mf
>  Ok [0] [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exsign.mf
>  Ok [24] [34] [35] [36] [37] [64] [191] [159])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exilig.mf
>  Ok [25] [26] [27] [28] [29] [30] [31])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exitalp.mf
>  Ok [38] [63] [190])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exrulett.mf
>  Ok [65] [66] [67] [68] [69] [70] [71] [72] [73] [74] [75] [76] [77] [78]
> [79] [80] [81] [82] [83] [84] [85] [86] [87] [88] [89] [90])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exillett.mf
>  Ok [97] [98] [99] [100] [101] [102] [103] [104] [105] [106] [107] [108]
> [109] [110] [111] [112] [113] [114] [115] [116] [117] [118] [119] [120]
> [121] [122])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exidigit.mf
>  Ok [48] [49] [50] [51] [52] [53] [54] [55] [56] [57])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exiligtb.mf
>  Ok) ) ) )
> Font metrics written on ecbi0900.tfm.
> Output written on ecbi0900.8030gf (256 characters, 1150484 bytes).
> Transcript written on ecbi0900.log.
> Cannot find your hotkey definition file!
> mftrace @VERSION@
> Font `ecbi0900'...
> Opening pipe `kpsewhich ecbi0900.tfm'
> Temporary directory is `/tmp/tmpj8y7r0db'
> Opening pipe `kpsewhich tex256.enc'
> Using encoding file: 
> `/usr/share/texlive/texmf-dist/fonts/enc/dvips/base/tex256.enc'
> Running Metafont...Invoking `mf '\mode:=lexmarks; mag:=6.691667; nonstopmode; 
> input ecbi0900''
> 
> 
> Tracing bitmaps...
> Invoking `/<>/gf2pbm -n 65 -o 

Bug#925816: marked as done (qxw: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 18:19:58 +
with message-id 
and subject line Bug#925816: fixed in shim 15+1533136590.3beb971-8
has caused the Debian Bug report #925816,
regarding qxw: ftbfs with GCC-9
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.)


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

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-9/g++-9, but succeeds to build with gcc-8/g++-8. 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/gcc9-20190321/qxw_20140331-1_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 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-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
  |   ^~~~
gui.c:2072:94: note: ...this statement, but the latter is misleadingly indented 
as if it were guarded by the 'else'
 2072 |   else strcpy (s,"  Mean length: -");   
 gtk_label_set_text(GTK_LABEL(st_r[1]),s);
  | 
 ^~
gui.c:2074:3: warning: this 'else' clause does not guard... 
[-Wmisleading-indentation]
 2074 |   else  strcpy (s,"  Checked light letters: -");
  gtk_label_set_text(GTK_LABEL(st_r[2]),s);
  |   ^~~~
gui.c:2074:95: note: ...this statement, but the latter is misleadingly indented 
as if it were guarded by the 'else'
 2074 |   else  strcpy (s,"  Checked light letters: -");
  gtk_label_set_text(GTK_LABEL(st_r[2]),s);
  | 
  ^~
gui.c:2076:3: warning: this 'else' clause does not guard... 
[-Wmisleading-indentation]
 2076 |   else  strcpy (s,"  Checked grid cells: -");   
  gtk_label_set_text(GTK_LABEL(st_r[3]),s);
  |   ^~~~
gui.c:2076:95: note: ...this statement, but the latter is misleadingly indented 
as if it were guarded by the 'else'
 2076 |   else  strcpy (s,"  Checked grid cells: -");   
  gtk_label_set_text(GTK_LABEL(st_r[3]),s);
  | 
  ^~
gui.c: In function 'updatefeas':
gui.c:2241:45: warning: '%s' directive writing up to 999 bytes into a region of 
size between 978 and 979 [-Wformat-overflow=]
 2241 | else sprintf(p1," Feasible character%s: 
%s",(strlen(p0)==1)?"":"s",p0);
  | ^~ 
~~
gui.c:2241:10: note: 'sprintf' output between 22 and 1022 bytes into a 
destination of size 1000
 2241 | else sprintf(p1," Feasible character%s: 
%s",(strlen(p0)==1)?"":"s",p0);
  |  
^
gcc -Wall -fstack-protector --param=ssp-buffer-size=4 -Wformat 
-Wformat-security -Werror=format-security `pkg-config --cflags glib-2.0` 
`pkg-config --cflags gtk+-2.0` -I/opt/local/include -O9 -c draw.c -o draw.o
draw.c: In function 'draw_finit':
draw.c:460:3: warning: this 'if' clause does not guard... 
[-Wmisleading-indentation]
  460 |   if(sfb) cairo_surface_destroy(sfb);  sfb=0;
  |   ^~
draw.c:460:40: note: ...this statement, but the latter is 

Bug#939656: marked as done (dh_strip should strip sections with LTO information from .a and .o files / lintian should warn about these)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 18:19:09 +
with message-id 
and subject line Bug#939656: fixed in debhelper 12.10
has caused the Debian Bug report #939656,
regarding dh_strip should strip sections with LTO information from .a and .o 
files / lintian should warn about these
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.)


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

Package: debhelper,lintian
Severity: important

Some packages build with link time optimizations enabled, which is ok, whoever 
then these packages may ship with static libs which still have the LTO 
information in some sections of the object files (e.g. ext2fsprogs).  This is 
not desired in most cases, so this information should be removed from these 
files, and not shipped in the archive. Plus the streaming format for the LTO 
information changes (even in GCC minor releases), and leads to build errors when 
you try to use an old streaming format with a newer compiler.  I'm asking for


 - dh_strip removing sections, as in

 strip -R .gnu.lto_* -R .gnu.debuglto_* -N __gnu_lto_slim -N __gnu_lto_v1

   which is turned on by default.

 - dh_strip providing an option not to remove these sections.

 - lintian warning about object files and static archives having such
   sections.

I'd like to see that implemented in debhelper, because LTO builds are also 
sometimes enabled in upstream sources.


LTO is turned on by default in Suse, and their dh_strip equivalent provides the 
functionality above for the removal of the LTO information.


Please feel free to split this issue into separate debhelper and lintian tasks 
once a solution is agree upon.
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 12.10
Done: Niels Thykier 

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

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

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Mar 2020 15:55:09 +
Source: debhelper
Architecture: source
Version: 12.10
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Closes: 939656 950723 951819 951917
Changes:
 debhelper (12.10) unstable; urgency=medium
 .
   [ Niels Thykier ]
   * dh_installsystemd.1: Improve documentation about tmpfiles that
 are now handled by dh_installtmpfiles in compat 13.
   * dh_installtmpfiles: Prefer debian/package.tmpfiles over
 debian/package.tmpfile, but accept the old path with a warning.
 Thanks to Michael Biebl for suggesting the change.
   * dh_strip: Automatically strip Link-Time Optimization (LTO)
 symbols from static archives.  The format is not stable between
 compiler versions.  Thanks to Matthias Klose for the
 suggestion and for providing the exact options.
 (Closes: #939656)
   * dh: Tweak the command-skipping optimization to skip commands
 in a few more cases when the command is known not to react to
 command line options.
   * dh,dh_installsytemd*: Work around broken NOOP promise caused by
 dh_installsystemd* using nonstandard "package@" prefix for
 pkgfiles.  Thanks to Badreddin Aboubakr and Andy Caldwell for
 reporting it.  (Closes: #950723, #951819)
 .
   [ Nicholas Guriev ]
   * cmake: Verbose autogen rules.
   * cmake: Skip install all dependency with compatibility level 13 and
 above.
 .
   [ Andy Caldwell ]
   * dh_installsystemduser: Fix bug that prevented dh_installsystemduser
 from installing parameterized services.  (Closes: #951819)
 .
   [ Translations ]
   * Update German translation (Chris Leick)  (Closes: #951917)
Checksums-Sha1:
 adef1db05ca8f20d5b93d1fec71524a7d5b0c885 1839 debhelper_12.10.dsc
 8171da063f17d95a74b23c87bb2bd1a98c4652b3 525416 debhelper_12.10.tar.xz
 75e0d34be7ca464dfdd9ba52182aa122a9763679 4606 debhelper_12.10_source.buildinfo
Checksums-Sha256:
 

Processed: Re: ERROR: Signature extraction failed + WARNING: Unable to extract video title

[Debian Bug Tracking System]

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

> close 945405 2020.01.24-0.1
Bug #945405 [youtube-dl] ERROR: Signature extraction failed + WARNING: Unable 
to extract video title
Marked as fixed in versions youtube-dl/2020.01.24-0.1.
Bug #945405 [youtube-dl] ERROR: Signature extraction failed + WARNING: Unable 
to extract video title
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Re: Bug#954010: improvements to mbox viewer

[Debian Bug Tracking System]

Processing control commands:

> close -1
Bug #954010 [nm.debian.org] improvements to mbox viewer
Marked Bug as done

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

Bug#949387: marked as done (nagivs: New upstream release 1.19.17)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 17:11:59 +
with message-id 
and subject line Bug#949387: fixed in nagvis 1:1.9.18-1
has caused the Debian Bug report #949387,
regarding nagivs: New upstream release 1.19.17
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.)


-- 
949387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nagivs
Version: 1:1.9.11-1
Severity: wishlist
Tags: patch

Dear Maintainer,

Several upstream versions have been released and the latest one is 1.9.17.

Between current Debian's version and latest upstream there are several changes
but the following are important to me:
 * Performance improvments
 * Ability to pass a custom Openstreetmap WMS server

I'll provided a PR on Salsa in a few minutes.

Best regards, Adam.



-- System Information:
Debian Release: 10.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: nagvis
Source-Version: 1:1.9.18-1
Done: Markus Frosch 

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

Debian distribution maintenance software
pp.
Markus Frosch  (supplier of updated nagvis package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Mar 2020 17:48:25 +0100
Source: nagvis
Architecture: source
Version: 1:1.9.18-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Nagios Maintainer Group 

Changed-By: Markus Frosch 
Closes: 788187 949387
Changes:
 nagvis (1:1.9.18-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * Use secure copyright file specification URI.
   * Use secure URI in Homepage field.
   * Bump debhelper from old 9 to 12.
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Repository, Repository-Browse.
   * Update standards version to 4.4.1, no changes needed.
 .
   [ Bas Couwenberg ]
   * Add Bug-* fields to upstream metadata.
   * Add gbp.conf to use pristine-tar & --source-only-changes by default.
   * Add icinga2 option to configure its livestatus path.
 (closes: #788187)
   * Bump Standards-Version to 4.5.0, no changes.
 .
   [ Adam Cecile ]
   * New upstream release (Closes: #949387).
   * Add myself to uploaders.
 .
   [ Markus Frosch ]
   * [23754f8] New upstream version 1.9.18
   * [4fb1411] Remove dependency on php-php-gettext.
 Upstream has a vulnerability with CVE-2016-6175
 NagVis uses a patched version, which works since NagVis does not use the
 vulnerable feature.
 Once upstream fixes this, and it gets uploaded to Debian, we should
 revert this.
   * [b5df31f] Update config patch
   * [eb70f60] Document source of ExtNicEdit
Checksums-Sha1:
 56a0b2cfb6d4e6c4c61038019aa602b00b6527e9 1743 nagvis_1.9.18-1.dsc
 05986b3de178c60c5d6bbd915f6aa1ec7b61aca4 1813073 nagvis_1.9.18.orig.tar.gz
 e35fb9133ce7cec347a2cdf415833d0f0baee183 173656 nagvis_1.9.18-1.debian.tar.xz
 1db7cc16d5f29391c44ee20cf5233832569b28de 5570 nagvis_1.9.18-1_amd64.buildinfo
Checksums-Sha256:
 e43d61d958073a24ac7b1f3a0996cf12383fe5c17bf3190eb490f96f93d18942 1743 
nagvis_1.9.18-1.dsc
 fedf92d7e13ecc709a86884efe34152fa473ade1b13a79e8678da3ae98a4616d 1813073 
nagvis_1.9.18.orig.tar.gz
 1b8128d04326ef6be960fbe2e40f5941d38f05f7a68cf7ce1c318a678f36f412 173656 
nagvis_1.9.18-1.debian.tar.xz
 663ed9e7014006519f5c473af3b8647e5fc189c5ecb22b748abbe8fa2f6c2a6a 5570 
nagvis_1.9.18-1_amd64.buildinfo
Files:
 aa5165bc539536aefc3d4271011ca4f9 1743 net optional nagvis_1.9.18-1.dsc
 3bcc79438abfcf84ee58608833e9f2aa 1813073 net optional nagvis_1.9.18.orig.tar.gz
 3e06200d5e181a33d63b7a62da4ea653 173656 net optional 
nagvis_1.9.18-1.debian.tar.xz
 4f83ccf0297e7ca40c63d72e05cedd34 5570 net 

Bug#788187: marked as done (Missing option for icinga2 on configure backend)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 17:11:59 +
with message-id 
and subject line Bug#788187: fixed in nagvis 1:1.9.18-1
has caused the Debian Bug report #788187,
regarding Missing option for icinga2 on configure backend
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.)


-- 
788187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nagvis
Version: 1.7.10+dfsg1-3

When the configure backend prompt appears after installing nagivs, there is
no option to configure it to use Icinga2 as a backend and the user is
forced to select "other" and then configure the backend manually.

The fix is to add the path to icinga2's livestatus socket as an option:
name: icinga2
path: /var/run/icinga2/cmd/livestatus

I'm using Debian Jessie 8.1, 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1
(2015-05-24) x86_64 GNU/Linux with icinga2 package from debmon:
icinga2_2.3.4-3~debmon80+1_amd64
--- End Message ---
--- Begin Message ---
Source: nagvis
Source-Version: 1:1.9.18-1
Done: Markus Frosch 

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

Debian distribution maintenance software
pp.
Markus Frosch  (supplier of updated nagvis package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Mar 2020 17:48:25 +0100
Source: nagvis
Architecture: source
Version: 1:1.9.18-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Nagios Maintainer Group 

Changed-By: Markus Frosch 
Closes: 788187 949387
Changes:
 nagvis (1:1.9.18-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * Use secure copyright file specification URI.
   * Use secure URI in Homepage field.
   * Bump debhelper from old 9 to 12.
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Repository, Repository-Browse.
   * Update standards version to 4.4.1, no changes needed.
 .
   [ Bas Couwenberg ]
   * Add Bug-* fields to upstream metadata.
   * Add gbp.conf to use pristine-tar & --source-only-changes by default.
   * Add icinga2 option to configure its livestatus path.
 (closes: #788187)
   * Bump Standards-Version to 4.5.0, no changes.
 .
   [ Adam Cecile ]
   * New upstream release (Closes: #949387).
   * Add myself to uploaders.
 .
   [ Markus Frosch ]
   * [23754f8] New upstream version 1.9.18
   * [4fb1411] Remove dependency on php-php-gettext.
 Upstream has a vulnerability with CVE-2016-6175
 NagVis uses a patched version, which works since NagVis does not use the
 vulnerable feature.
 Once upstream fixes this, and it gets uploaded to Debian, we should
 revert this.
   * [b5df31f] Update config patch
   * [eb70f60] Document source of ExtNicEdit
Checksums-Sha1:
 56a0b2cfb6d4e6c4c61038019aa602b00b6527e9 1743 nagvis_1.9.18-1.dsc
 05986b3de178c60c5d6bbd915f6aa1ec7b61aca4 1813073 nagvis_1.9.18.orig.tar.gz
 e35fb9133ce7cec347a2cdf415833d0f0baee183 173656 nagvis_1.9.18-1.debian.tar.xz
 1db7cc16d5f29391c44ee20cf5233832569b28de 5570 nagvis_1.9.18-1_amd64.buildinfo
Checksums-Sha256:
 e43d61d958073a24ac7b1f3a0996cf12383fe5c17bf3190eb490f96f93d18942 1743 
nagvis_1.9.18-1.dsc
 fedf92d7e13ecc709a86884efe34152fa473ade1b13a79e8678da3ae98a4616d 1813073 
nagvis_1.9.18.orig.tar.gz
 1b8128d04326ef6be960fbe2e40f5941d38f05f7a68cf7ce1c318a678f36f412 173656 
nagvis_1.9.18-1.debian.tar.xz
 663ed9e7014006519f5c473af3b8647e5fc189c5ecb22b748abbe8fa2f6c2a6a 5570 
nagvis_1.9.18-1_amd64.buildinfo
Files:
 aa5165bc539536aefc3d4271011ca4f9 1743 net optional nagvis_1.9.18-1.dsc
 3bcc79438abfcf84ee58608833e9f2aa 1813073 net optional nagvis_1.9.18.orig.tar.gz
 3e06200d5e181a33d63b7a62da4ea653 173656 net optional 
nagvis_1.9.18-1.debian.tar.xz
 4f83ccf0297e7ca40c63d72e05cedd34 5570 net optional 
nagvis_1.9.18-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE51PRnEwqQtexjRSC8mFdmquYe24FAl56Oj8ACgkQ8mFdmquY
e27yjQgA0NzSR+qgl2pxuSJj5twAzdApQM04qKvaDkWoG81bJmRRjqYcUxIogjm5
7XnByBy4Td/xfoq/2dhy6Pg7d9fcAItQ8zGRZsjhLRDh1k2/iK1+o/yOBxMdt2M2

Bug#954669: marked as done (Please update shared-mime-info to 1.15, and update the watch file)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 16:45:50 +
with message-id 
and subject line Bug#954669: fixed in shared-mime-info 1.15-1
has caused the Debian Bug report #954669,
regarding Please update shared-mime-info to 1.15, and update the watch file
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.)


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

Please update shared-mime-info to 1.15, and update the watch file to better 
track upstream releases.

Releases:
https://gitlab.freedesktop.org/xdg/shared-mime-info/-/releases

NEWS:
https://gitlab.freedesktop.org/xdg/shared-mime-info/-/blob/master/NEWS

shared-mime-info 1.15 (2019-30-10)
* Add Kindle 8 eBook format
* Fix some HTML files being detected as XML

shared-mime-info 1.14 (2019-20-09)
* Add mime-type for QCOW images
* Fix matching SVG files in some circumstances (again)

shared-mime-info 1.13.1 (2019-11-09)
* Fix matching SVG files in some circumstances

shared-mime-info 1.13 (2019-11-09)
* Add code of conduct document
* Use itstool and gettext to generate translations
* Add content-tree type for OSTree USB repositories
* Add match for MPEG-4 v1 videos
* Adjust a lot of user readable mime-type descriptions
* Fix WOFF/WOFF2 mime-types
* Prefer text/html to XHTML for *.html files
* Better magic for text/html files
* Fix SVG magic for files embedded in HTML
* Add *.sgd as a glob for Mega Drive ROMs

Specification:
- Mention that sub-class-of can be aliases

Tools:
- Enable Large File Support in update-mime-database

Test suite:
- Make test suite failures fatal
- Add test for duplicate mime-types
- Fix WarpScript test
- Generate the specification in the CI, to avoid it becoming syntactically 
invalid

shared-mime-info 1.12 (2019-17-01)
* Fix build from tarball

shared-mime-info 1.11 (2019-17-01)
* Add mime-type for reStructuredText
* Add mime-type for Groovy scripting language
* Add mime-type for Gradle build tool
* Add mime-type for Maven
* Add mime-type for WarpScript source code
* Add mime-type for zstd and tar.zst archives
* Change the preferred suffix for image/jpeg from .jpeg to .jpg
* Assign *.html to XHTML pages
* Better detection for *.key files (Apple Keynote vs. GPG keys)
* Give weight to one of the appimage patterns

Tools:
- Link to GitLab for contributions and bug reports
- Loads of memory and file descriptor leak fixes

Spec:
- Clarify the availability of C character escape support

--- End Message ---
--- Begin Message ---
Source: shared-mime-info
Source-Version: 1.15-1
Done: Emilio Pozuelo Monfort 

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

Debian distribution maintenance software
pp.
Emilio Pozuelo Monfort  (supplier of updated shared-mime-info 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 24 Mar 2020 16:58:21 +0100
Source: shared-mime-info
Architecture: source
Version: 1.15-1
Distribution: unstable
Urgency: medium
Maintainer: Debian freedesktop.org maintainers 

Changed-By: Emilio Pozuelo Monfort 
Closes: 954669
Changes:
 shared-mime-info (1.15-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #954669.
   * Update watch file for gitlab.freedesktop.org.
   * Update build-dependencies.
   * Remove ancient patches changing the magic database. Those should be
 reported upstream if they're still present.
   * Switch to debhelper-compat and bump compat to 12.
   * Don't hardcode full command path in postinst.
Checksums-Sha1:
 5ff6fc689125daec697f49c2d8e025ab7a40e4f7 2198 shared-mime-info_1.15-1.dsc
 2579f9763a6efb31c6343408874051ed93646e94 772708 
shared-mime-info_1.15.orig.tar.xz
 28acacfdd312ffaf4890218de7e55a48101c134c 9728 
shared-mime-info_1.15-1.debian.tar.xz
 25d8f03b56ff8e42a6ae6172119cdd06f7797e38 5257 
shared-mime-info_1.15-1_source.buildinfo
Checksums-Sha256:
 dca6ea0156110b4a2694dd96a721d34ad4f42b51f3d3a20d0d711b77bde5115d 2198 
shared-mime-info_1.15-1.dsc
 

Bug#954550: marked as done (libprelude: FTBFS: Prelude.cxx:1263:85: error: call of overloaded ‘rb_define_virtual_variable(const char [21], VALUE (&)(...), NULL)’ is ambiguous)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 16:11:07 +
with message-id 
and subject line Bug#954550: fixed in libprelude 5.1.1-5
has caused the Debian Bug report #954550,
regarding libprelude: FTBFS: Prelude.cxx:1263:85: error: call of overloaded 
‘rb_define_virtual_variable(const char [21], VALUE (&)(...), NULL)’ is ambiguous
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.)


-- 
954550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libprelude
Version: 5.1.1-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 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=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
> -I../..  -I/usr/include/x86_64-linux-gnu/ruby-2.7.0 -I/usr/include/ruby-2.7.0 
> -g -O2 -fdebug-prefix-map=/build/ruby2.7-cMhIdS/ruby2.7-2.7.0=. 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I../.. 
> -I../../src/include -I../../src/include -I../../src/libprelude-error 
> -I../../bindings/c++/include -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o Prelude_la-Prelude.lo `test -f 'Prelude.cxx' || 
> echo './'`Prelude.cxx
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. 
> -I/usr/include/x86_64-linux-gnu/ruby-2.7.0 -I/usr/include/ruby-2.7.0 -g -O2 
> -fdebug-prefix-map=/build/ruby2.7-cMhIdS/ruby2.7-2.7.0=. 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I../.. 
> -I../../src/include -I../../src/include -I../../src/libprelude-error 
> -I../../bindings/c++/include -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c Prelude.cxx  -fPIC -DPIC -o 
> .libs/Prelude_la-Prelude.o
> Prelude.cxx: In function ‘void SWIG_RubyInitializeTrackings()’:
> Prelude.cxx:1263:85: error: call of overloaded 
> ‘rb_define_virtual_variable(const char [21], VALUE (&)(...), NULL)’ is 
> ambiguous
>  1263 |   rb_define_virtual_variable("SWIG_TRACKINGS_COUNT", 
> swig_ruby_trackings_count, NULL);
>   |   
>   ^
> In file included from /usr/include/ruby-2.7.0/ruby/ruby.h:2863,
>  from /usr/include/ruby-2.7.0/ruby.h:33,
>  from Prelude.cxx:879:
> /usr/include/ruby-2.7.0/ruby/backward/cxxanyargs.hpp:59:1: note: candidate: 
> ‘void ruby::backward::cxxanyargs::rb_define_virtual_variable(const char*, 
> VALUE (*)(...), void (*)(...))’
>59 | rb_define_virtual_variable(const char *q, type *w, void_type *e)
>   | ^~
> /usr/include/ruby-2.7.0/ruby/backward/cxxanyargs.hpp:90:1: note: candidate: 
> ‘void ruby::backward::cxxanyargs::rb_define_virtual_variable(const char*, 
> VALUE (*)(...), void (*)(VALUE, ID, VALUE*))’
>90 | rb_define_virtual_variable(const char *q, type *w, rb_gvar_setter_t 
> *e)
>   | ^~
> Prelude.cxx: In function ‘void SWIG_RubyIterateTrackings(void (*)(void*, 
> VALUE))’:
> Prelude.cxx:1317:106: warning: ‘int 
> ruby::backward::cxxanyargs::rb_st_foreach(st_table*, int (*)(...), 
> st_data_t)’ is deprecated: Use of ANYARGS in this function is deprecated 
> [-Wdeprecated-declarations]
>  1317 |   st_foreach(swig_ruby_trackings, (int 
> (*)(ANYARGS))_ruby_internal_iterate_callback, (st_data_t)meth);
>   |   
>^
> In file included from /usr/include/ruby-2.7.0/ruby/intern.h:39,
>  from /usr/include/ruby-2.7.0/ruby/ruby.h:2148,
>  from /usr/include/ruby-2.7.0/ruby.h:33,
>  from Prelude.cxx:879:
> /usr/include/ruby-2.7.0/ruby/st.h:142:20: note: declared here
>   142 | #define st_foreach rb_st_foreach
>   |^
> /usr/include/ruby-2.7.0/ruby/backward/cxxanyargs.hpp:362:1: note: in 
> expansion of macro ‘st_foreach’
>   362 | st_foreach(st_table *q, int_type *w, st_data_t e)
>   | ^~
> Prelude.cxx:1317:106: warning: ‘int 
> ruby::backward::cxxanyargs::rb_st_foreach(st_table*, int (*)(...), 
> st_data_t)’ is deprecated: Use of ANYARGS in this function is deprecated 
> [-Wdeprecated-declarations]
>  1317 |   st_foreach(swig_ruby_trackings, (int 
> (*)(ANYARGS))_ruby_internal_iterate_callback, (st_data_t)meth);
>   | 

Bug#954785: marked as done (libprelude FTBFS against ruby 2.7)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 16:11:07 +
with message-id 
and subject line Bug#954785: fixed in libprelude 5.1.1-5
has caused the Debian Bug report #954785,
regarding libprelude FTBFS against ruby 2.7
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.)


-- 
954785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libprelude
Version: 5.1.1-4
Severity: serious
User pkg-ruby-extras-maintain...@lists.alioth.debian.org
Usertags: ruby2.7-transition

Dear Maintainer,

We are removing ruby 2.5 support and src:libprelude FTBFS against ruby 2.7, 
check this build log:

https://buildd.debian.org/status/fetch.php?pkg=libprelude=amd64=5.1.1-4%2Bb2=1584634713=0

The attached debdiff adds ruby 2.7 support, fixing the FTBFS.

Thanks for considering the patch!

-- 
Lucas Kanashiro

diff -Nru libprelude-5.1.1/debian/changelog 
libprelude-5.1.1.new/debian/changelog
--- libprelude-5.1.1/debian/changelog   2019-11-17 07:07:24.0 -0300
+++ libprelude-5.1.1.new/debian/changelog   2020-03-23 10:27:52.863826694 
-0300
@@ -1,3 +1,11 @@
+libprelude (5.1.1-5) unstable; urgency=medium
+
+  * Add support to Ruby 2.7.
++ d/p/020-ruby27_support.patch: add patch to avoid ambiguity in
+  rb_define_virtual_variable call.
+
+ -- Lucas Kanashiro   Mon, 23 Mar 2020 10:26:52 
-0300
+
 libprelude (5.1.1-4) unstable; urgency=medium
 
   * d/rules
diff -Nru libprelude-5.1.1/debian/patches/020-ruby27_support.patch 
libprelude-5.1.1.new/debian/patches/020-ruby27_support.patch
--- libprelude-5.1.1/debian/patches/020-ruby27_support.patch1969-12-31 
21:00:00.0 -0300
+++ libprelude-5.1.1.new/debian/patches/020-ruby27_support.patch
2020-03-23 10:29:08.063904212 -0300
@@ -0,0 +1,28 @@
+Description: Add support to Ruby 2.7
+ Type cast the parameters of rb_define_virtual_variable call to avoid 
ambiguity:
+ .
+ /usr/include/ruby-2.7.0/ruby/backward/cxxanyargs.hpp:59:1: note: candidate: 
‘void ruby::backward::cxxanyargs::rb_define_virtual_variable(const char*, VALUE 
(*)(...), void (*)(...))’
+   59 | rb_define_virtual_variable(const char *q, type *w, void_type *e)
+  | ^~
+/usr/include/ruby-2.7.0/ruby/backward/cxxanyargs.hpp:90:1: note: candidate: 
‘void ruby::backward::cxxanyargs::rb_define_virtual_variable(const char*, VALUE 
(*)(...), void (*)(VALUE, ID, VALUE*))’
+   90 | rb_define_virtual_variable(const char *q, type *w, rb_gvar_setter_t *e)
+Author: Lucas Kanashiro 
+Forwarded: No
+X-Not-Forwarded-Reason: Waiting for upstream approval to create my account in 
their BTS
+Last-Updated: 2020-03-03
+
+--- a/bindings/ruby/Prelude.cxx
 b/bindings/ruby/Prelude.cxx
+@@ -1260,7 +1260,12 @@
+ swig_ruby_trackings = (st_table*)NUM2SWIG(trackings_value);
+   }
+ 
++#if RUBY_VERSION_MAJOR == 2 && RUBY_VERSION_MINOR < 7
+   rb_define_virtual_variable("SWIG_TRACKINGS_COUNT", 
swig_ruby_trackings_count, NULL);
++#else
++  rb_define_virtual_variable("SWIG_TRACKINGS_COUNT", (rb_gvar_getter_t 
*)swig_ruby_trackings_count, (rb_gvar_setter_t *)NULL);
++#endif
++
+ }
+ 
+ /* Add a Tracking from a C/C++ struct to a Ruby object */
diff -Nru libprelude-5.1.1/debian/patches/series 
libprelude-5.1.1.new/debian/patches/series
--- libprelude-5.1.1/debian/patches/series  2019-11-15 18:30:15.0 
-0300
+++ libprelude-5.1.1.new/debian/patches/series  2020-03-23 10:26:39.971750566 
-0300
@@ -10,3 +10,4 @@
 017-enable_detection_new_python3.patch
 018-fix_gtkdoc_1.32.patch
 019-fix_path_max_on_hurd.patch
+020-ruby27_support.patch
--- End Message ---
--- Begin Message ---
Source: libprelude
Source-Version: 5.1.1-5
Done: Thomas Andrejak 

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

Debian distribution maintenance software
pp.
Thomas Andrejak  (supplier of updated libprelude 
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: Mon, 23 Mar 2020 12:07:24 +0200
Source: libprelude
Architecture: source
Version: 5.1.1-5
Distribution: unstable

Bug#928059: marked as done (lighttpd: setenv missing from conf-available)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 11:44:00 -0400
with message-id <20200324154400.GA861240@xps13>
and subject line 928059-done
has caused the Debian Bug report #928059,
regarding lighttpd: setenv missing from conf-available
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.)


-- 
928059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lighttpd
Version: 1.4.53-4
Severity: normal

Hi,

server.modules = ( "mod_setenv" ) was removed from lighttpd.conf but no setenv 
conf file appears to be available in the conf-available dir.

Greetings,

Olaf

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

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

Versions of packages lighttpd depends on:
ii  libattr1  1:2.4.48-4
ii  libbz2-1.01.0.6-9
ii  libc6 2.28-9
ii  libfam0   2.7.0-17.3
ii  libpcre3  2:8.39-12
ii  libssl1.1 1.1.1b-2
ii  lsb-base  10.2019031300
ii  mime-support  3.62
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages lighttpd recommends:
pn  lighttpd-modules-ldap   
pn  lighttpd-modules-mysql  
ii  perl5.28.1-6
pn  spawn-fcgi  

Versions of packages lighttpd suggests:
pn  apache2-utils  
pn  lighttpd-doc   
ii  openssl1.1.1b-2
pn  php-cgi
pn  rrdtool

-- no debconf information
--- End Message ---
--- Begin Message ---
Package: lighttpd
Version: lighttpd/1.4.55-1

added debian/conf-available/05-setenv.conf in lighttpd 1.4.55-1--- End Message ---

Bug#715205: marked as done ([lighttpd]: Running lighttpd as another user)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 11:31:49 -0400
with message-id <20200324153149.GB860795@xps13>
and subject line 715205-done
has caused the Debian Bug report #715205,
regarding [lighttpd]: Running lighttpd as another user
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.)


-- 
715205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715205
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lighttpd
Version: 1.4.31-4

Hi,

I wanted to run lighttpd as a different user (than www-data). I
thought modifying /etc/lighttpd.conf would be the only thing required,
but the package really wants to run lighttpd as www-data:
- The default log dir /var/log/lighttpd is owned by www-data:ww-data.
I had to change the location where lighttpd logs to a file where my
user could write.
- For the sake of coherence, I also changed the pid file location in
/etc/lighttpd.conf. Bad idea! The init script /etc/init.d/lighttpd was
referencing this file and was relying on it for killing lighttpd.
After a while, I understood that modifying the location of this pid
file was the reason why I could not stop lighttpd anymore.
- When I tried to set up lighttpd for php, I discovered that lighttpd
was not able to php, because /var/run/lighttpd/php.socket-0 was not
writable by my user. The cause of this was that the init script was
creating the directory /var/run/lighttpd as owned by
www-data:www-data. I ended up modifying the init script to use my
user/group, but it is not a viable solution regarding future upgrades.

TL;DR It would be nice if the init script was loading the user/group
of lighttpd from a unique config file (the same way it is done for
apache).

Some relevant informations about my system:
$ cat /etc/debian_version
7.1
$ uname -a
Linux chmd.fr 3.8.13--grs-ipv6-64 #3 SMP Wed May 29 11:57:43 CEST
2013 x86_64 GNU/Linux

Regards,
Christophe-Marie
--- End Message ---
--- Begin Message ---
wontfix

lighttpd can be run as any user if the necessary directories are set up.

The Debian package provides a template and runs as user www-data.

If you would like something different and do not want to interfere with
the Debian package for lighttpd, then clone and modify the init script
and the systemd unit, and customize as necessary, e.g. create something
like 'lighttpd-custom'.  Most of this is one-time create of directories
with proper ownership.  The init script will probably have to create
/run/lighttpd-custom each time the init script is run, since /run is in
tmpfs and does not persist across boots.--- End Message ---

Bug#943193: marked as done (neurodebian: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 11:19:55 -0400
with message-id <20200324151955.gv5...@lena.dartmouth.edu>
and subject line Re: Processed: found 943193 in 0.38.3
has caused the Debian Bug report #943193,
regarding neurodebian: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
943193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: neurodebian
Version: 0.39.0
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

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

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

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

  This is the least preferred option.

If 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 ---
Version: 0.40.0

Forgot to properly close issues in the changelog.
This version migrated code from python2 to python3, and depends were
fixed up

$> grep python debian/control
   python3-html5lib,
Depends: python3,
python3,


-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik


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

Bug#937009: marked as done (mercurial: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 14:44:51 +
with message-id 
and subject line Bug#937009: fixed in mercurial 5.3.1-1+exp1
has caused the Debian Bug report #937009,
regarding mercurial: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:mercurial

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

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

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

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

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated mercurial package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Mar 2020 15:21:35 +0100
Source: mercurial
Architecture: source
Version: 5.3.1-1+exp1
Distribution: experimental
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Julien Cristau 
Closes: 937009
Changes:
 mercurial (5.3.1-1+exp1) experimental; urgency=medium
 .
   * Use python3 (closes: #937009).
   * mercurial Provides python3-mercurial so extensions can depend on
 that instead of a hazardous versioned dependency.
   * Add Breaks on all extensions.  To be updated as we don't know what
 version will use python3.
   * Pull patches from upstream repo to fix python3.8 compat.
Checksums-Sha1:
 92cafdf91b0f60a025846eaa783f65553aed4ead 2802 mercurial_5.3.1-1+exp1.dsc
 1e71fd1ac5ddfde60ea9d3ed4eb145353bd7a913 60380 
mercurial_5.3.1-1+exp1.debian.tar.xz
Checksums-Sha256:
 17ab261591a316839e301c01ff358b3a0e8ffadf38ae52f85cf8e0e80ea7fafa 2802 
mercurial_5.3.1-1+exp1.dsc
 

Bug#952335: marked as done (uglify-js: FTBFS: ERROR: `m` is not a supported option)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 14:45:11 +
with message-id 
and subject line Bug#952335: fixed in node-commander 4.0.1+really2.20.0-1
has caused the Debian Bug report #952335,
regarding uglify-js: FTBFS: ERROR: `m` is not a supported option
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.)


-- 
952335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uglify-js
Version: 3.6.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 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 '/<>'
> NODE_PATH=lib node test/mocha.js \
>   
> arguments
>   √ Should known that arguments in functions are local scoped
>   √ Should recognize when a function uses arguments
> bin/uglifyjs
>   × Should produce a functional build when using --self
>   √ Should be able to filter comments correctly with `--comments 
> all`
>   √ Should be able to filter comments correctly with `--comment 
> `
>   √ Should be able to filter comments correctly with just 
> `--comment`
>   √ Should give sensible error against invalid input source map
>   √ Should append source map to output when using --source-map 
> url=inline
>   √ Should not append source map to output when not using 
> --source-map url=inline
>   √ Should not consider source map file content as source map file 
> name (issue #2082)
>   √ Should not load source map before finish reading from STDIN
>   √ Should work with --keep-fnames (mangle only)
>   √ Should work with --keep-fnames (mangle & compress)
>   √ Should work with keep_fnames under mangler options
>   √ Should work with --define (simple)
>   √ Should work with --define (nested)
>   √ Should work with --define (AST_Node)
>   √ Should work with `--beautify`
>   √ Should work with `--beautify braces`
>   × Should process inline source map
>   √ Should warn for missing inline source map
>   √ Should handle multiple input and inline source map
>   √ Should fail with acorn and inline source map
>   √ Should fail with SpiderMonkey and inline source map
>   √ Should fail with invalid syntax
>   √ Should fail with correct marking of tabs
>   √ Should fail with correct marking at start of line
>   √ Should fail with a missing loop body
>   √ Should throw syntax error (5--)
>   √ Should throw syntax error (Math.random() /= 2)
>   √ Should throw syntax error (++this)
>   √ Should throw syntax error (++null)
>   √ Should throw syntax error (a.=)
>   √ Should throw syntax error (%.a)
>   √ Should throw syntax error (a./();)
>   √ Should throw syntax error ({%: 1})
>   √ Should throw syntax error (delete x)
>   √ Should throw syntax error (function g(arguments))
>   √ Should throw syntax error (function eval())
>   √ Should throw syntax error (iife arguments())
>   √ Should throw syntax error (catch (eval))
>   √ Should throw syntax error (var eval)
>   √ Should throw syntax error (else)
>   √ Should throw syntax error (return)
>   √ Should throw syntax error (for-in init)
>   √ Should throw syntax error (for-in var)
>   √ Should handle literal string as source map input
>   √ Should include function calls in source map
>   × Should dump AST as JSON
>   √ Should print supported options on invalid option syntax
>   √ Should work with --mangle reserved=[]
>   √ Should work with --mangle reserved=false
>   √ Should fail with --mangle-props reserved=[in]
>   √ Should work with mangle.properties.regex from --config-file
>   √ Should fail with --define a-b
>   √ Should work with explicit --rename
>   × Should work with explicit --no-rename
>   × Should work with implicit --rename
>   √ Should work with implicit --no-rename
>   √ Should work with --enclose
>   √ Should work with --enclose arg
>   √ Should work with --enclose arg:value
>   √ Should work with --enclose & --wrap
>   

Bug#952206: marked as done (golang-go.uber-zap: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 go.uber.org/zap go.uber.org/zap/buffer go.uber.org/zap/internal/bufferpo

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 14:43:24 +
with message-id 
and subject line Bug#952206: fixed in golang-go.uber-zap 1.14.1-1
has caused the Debian Bug report #952206,
regarding golang-go.uber-zap: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 4 go.uber.org/zap 
go.uber.org/zap/buffer go.uber.org/zap/internal/bufferpool 
go.uber.org/zap/internal/color go.uber.org/zap/internal/exit 
go.uber.org/zap/internal/readme go.uber.org/zap/internal/ztest 
go.uber.org/zap/zapcore go.uber.org/zap/zapgrpc go.uber.org/zap/zaptest 
go.uber.org/zap/zaptest/observer returned exit code 1
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.)


-- 
952206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-go.uber-zap
Version: 1.9.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 go.uber.org/zap 
> go.uber.org/zap/buffer go.uber.org/zap/internal/bufferpool 
> go.uber.org/zap/internal/color go.uber.org/zap/internal/exit 
> go.uber.org/zap/internal/readme go.uber.org/zap/internal/ztest 
> go.uber.org/zap/zapcore go.uber.org/zap/zapgrpc go.uber.org/zap/zaptest 
> go.uber.org/zap/zaptest/observer
> internal/race
> internal/cpu
> runtime/internal/sys
> runtime/internal/atomic
> sync/atomic
> runtime/internal/math
> unicode
> unicode/utf8
> encoding
> internal/bytealg
> math/bits
> internal/testlog
> math
> unicode/utf16
> container/list
> crypto/internal/subtle
> runtime
> crypto/subtle
> vendor/golang.org/x/crypto/cryptobyte/asn1
> internal/nettrace
> vendor/golang.org/x/crypto/internal/subtle
> runtime/cgo
> vendor/golang.org/x/crypto/curve25519
> internal/reflectlite
> sync
> internal/singleflight
> math/rand
> errors
> sort
> io
> strconv
> internal/oserror
> syscall
> vendor/golang.org/x/net/dns/dnsmessage
> bytes
> reflect
> strings
> go.uber.org/zap/buffer
> go.uber.org/zap/internal/bufferpool
> bufio
> hash
> internal/syscall/unix
> time
> hash/crc32
> crypto
> crypto/internal/randutil
> crypto/hmac
> crypto/rc4
> vendor/golang.org/x/crypto/hkdf
> vendor/golang.org/x/text/transform
> path
> internal/fmtsort
> encoding/binary
> go.uber.org/atomic
> internal/poll
> context
> crypto/cipher
> crypto/sha512
> encoding/base64
> os
> crypto/ed25519/internal/edwards25519
> crypto/aes
> crypto/des
> crypto/md5
> crypto/sha1
> fmt
> go.uber.org/zap/internal/exit
> path/filepath
> crypto/sha256
> encoding/pem
> net
> io/ioutil
> vendor/golang.org/x/crypto/internal/chacha20
> vendor/golang.org/x/crypto/poly1305
> vendor/golang.org/x/sys/cpu
> encoding/json
> flag
> go.uber.org/multierr
> go.uber.org/zap/internal/color
> log
> compress/flate
> math/big
> go.uber.org/zap/zapcore
> compress/gzip
> encoding/hex
> net/url
> vendor/golang.org/x/crypto/chacha20poly1305
> vendor/golang.org/x/text/unicode/bidi
> crypto/rand
> crypto/elliptic
> encoding/asn1
> crypto/ed25519
> crypto/rsa
> crypto/dsa
> crypto/ecdsa
> crypto/x509/pkix
> vendor/golang.org/x/crypto/cryptobyte
> vendor/golang.org/x/text/secure/bidirule
> vendor/golang.org/x/text/unicode/norm
> vendor/golang.org/x/net/http2/hpack
> mime
> mime/quotedprintable
> net/http/internal
> os/exec
> text/template/parse
> vendor/golang.org/x/net/idna
> go.uber.org/zap/internal/ztest
> go.uber.org/zap/zaptest/observer
> net/textproto
> crypto/x509
> vendor/golang.org/x/net/http/httpproxy
> text/template
> vendor/golang.org/x/net/http/httpguts
> mime/multipart
> go.uber.org/zap/internal/readme
> crypto/tls
> net/http/httptrace
> net/http
> go.uber.org/zap
> go.uber.org/zap/zapgrpc
> go.uber.org/zap/zaptest
>dh_auto_test -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 go.uber.org/zap 
> go.uber.org/zap/buffer go.uber.org/zap/internal/bufferpool 
> go.uber.org/zap/internal/color go.uber.org/zap/internal/exit 
> go.uber.org/zap/internal/readme go.uber.org/zap/internal/ztest 
> go.uber.org/zap/zapcore go.uber.org/zap/zapgrpc go.uber.org/zap/zaptest 
> go.uber.org/zap/zaptest/observer
> === RUN   TestArrayWrappers
> --- PASS: TestArrayWrappers (0.00s)
> 

Bug#934805: marked as done (lintian: probably shouldn't emit package-supports-alternative-init-but-no-init.d-script for instanced systemd services (foo@.service))

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 13:41:44 +
with message-id <0473ec0e-2b45-4944-a1ea-1803fceb8f02@sloti26t01>
and subject line Re: lintian: probably shouldn't emit 
package-supports-alternative-init-but-no-init.d-script for instanced systemd 
services (foo@.service)
has caused the Debian Bug report #934805,
regarding lintian: probably shouldn't emit 
package-supports-alternative-init-but-no-init.d-script for instanced systemd 
services (foo@.service)
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.)


-- 
934805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.18.0
Severity: minor

Some packages contain "instanced" systemd units named like foo@.service,
which represent a family of possible systemd units foo@bar.service for
arbitrary values of bar. For example, quake2-server in contrib is one of
these: you can run any number of servers on different ports by creating
more than one configuration file and enabling multiple instances of
the unit.

This is not a feature that exists in LSB init scripts, so I don't think
maintainers can be expected to provide it. I can see two possible
improvements here:

- do not emit package-supports-alternative-init-but-no-init.d-script for
  foo@.service at all, on the basis that the feature does not exist in
  LSB init, so feature parity is not implementable

- do not emit package-supports-alternative-init-but-no-init.d-script for
  foo@.service if /etc/init.d/foo exists, on the assumption that
  /etc/init.d/foo is equivalent to one of the instances of foo@.service

If a package contains /etc/init.d/foo and foo@.service, then it should
likely also either contain foo.service (e.g. quake2-server follows this
pattern), or "mask" foo.service by making it a symlink to /dev/null to
avoid both /etc/init.d/foo and instances of foo@.service being invoked
under systemd.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 2.25.0

Hi,

> lintian: probably shouldn't emit package-supports-alternative-init-
> but-no-init.d-script for instanced systemd services (foo@.service)

I believe this was fixed in:

  
https://salsa.debian.org/lintian/lintian/commit/705488630772c04fa8c474fd01791b0ef5edd516


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   ` End Message ---

Bug#950654: marked as done (node-eslint-plugin-html seems unusable without eslint)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 13:34:24 +
with message-id 
and subject line Bug#950654: fixed in node-eslint-plugin-html 3.2.1-2
has caused the Debian Bug report #950654,
regarding node-eslint-plugin-html seems unusable without eslint
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.)


-- 
950654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-eslint-plugin-html
Version: 3.2.1-1
Severity: serious

This package seems unusable without eslint. See
https://ci.debian.net/data/autopkgtest/unstable/amd64/n/node-eslint-plugin-html/3801441/log.gz
--- End Message ---
--- Begin Message ---
Source: node-eslint-plugin-html
Source-Version: 3.2.1-2
Done: Xavier Guimard 

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-eslint-plugin-html 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Mar 2020 14:21:07 +0100
Source: node-eslint-plugin-html
Architecture: source
Version: 3.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 950654
Changes:
 node-eslint-plugin-html (3.2.1-2) unstable; urgency=medium
 .
   * Team upload
   * Declare compliance with policy 4.5.0
   * Bump debhelper compatibility level to 12
   * Add dependency to eslint (Closes: #950654)
   * Add simple autopkgtest test
Checksums-Sha1: 
 3d26b0fa4746b3d95c69a0d89273d1db5e86f191 2290 
node-eslint-plugin-html_3.2.1-2.dsc
 832d1d11ca42ebab2752a4c38fb6910c0858a01e 2204 
node-eslint-plugin-html_3.2.1-2.debian.tar.xz
Checksums-Sha256: 
 61526bef9ce6be805080cb4ca8f20eafdb013000f89772faa1a5f02678ec1e7b 2290 
node-eslint-plugin-html_3.2.1-2.dsc
 3f478c6a54eacd169c5901526eebce2bbc54970431319424fc642088fbe91d44 2204 
node-eslint-plugin-html_3.2.1-2.debian.tar.xz
Files: 
 9b20e4c615f71ffda4a2ee4d4e2894a1 2290 javascript optional 
node-eslint-plugin-html_3.2.1-2.dsc
 46354fa5628058eb2e2190c8cb7a0d6d 2204 javascript optional 
node-eslint-plugin-html_3.2.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl56CZgACgkQ9tdMp8mZ
7unpKBAAmdcoCgtJl2M+g89wwA0ZJgGojyKp82a6Ghjy2CipYoBS7SosV6kMITZb
atnucWEuWYO/si2p1gMfsmPSBv5fCKbvDFK5aoZFO6gwZ7yz4cU4mqKvey45LA32
W+vGu9XBgtOQ0DDMcCvF4v+1K0borcGZ48Y24Teokid/Fj7BZjuc5PwzO+6lNB8X
LXCF0hhntIXUDP14a9ZeRaw+8kcWgC6m01Q2wdogIZY/kvcDOH/jIrI7dKzOmQgB
WVmelsgyG51Ga+lhYhR+OcUc4OrnRY6WbnEJlcNOZ98E+6xXGFY/95zcuqFm8JEC
LZpr1h8z07ey2BoLn+JGVJFP0qIc9PRxpDX+LvYbS0ATCO9qxaNPo0zXNuAZL9qv
NYxrxjCfvjcQxgGRlkf9FEdr0NY4oCbFj4TeUVK3q+E8v+gnzL4oFqz7V9gcqIUB
qCZVKwY+N+L5jbeRwms1xcL3EVBSO5c4mGorTzBtB7apiUl2y0ANl+0qzyRLwMhX
nFOIbbu0Rq2oB/MCoURFgfZVucap8Mrf3fYLYLgYu99+6wXunk+uKDV8quzyEf4Y
Ysjf03P8S1mXo5XjRXkbs6RP+Royxax0MXNPLelioktVEzLOIcEi372cx2QoefBn
Ij2mCCgwYnnsHuiVSdH2nhOqHQprYEFFvLld3wbHHPqdTVMSkY4=
=QsOS
-END PGP SIGNATURE End Message ---

Bug#954751: marked as done (libgcc-10-dev: Missing include/sanitizer/)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 13:06:10 +
with message-id 
and subject line Bug#954751: fixed in gcc-10 10-20200324-1
has caused the Debian Bug report #954751,
regarding libgcc-10-dev: Missing include/sanitizer/
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.)


-- 
954751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgcc-10-dev
Version: 10-20200321-1

Hi,

Since last upgrade of my sid chroot, the include directory
"include/sanitizer/" is missing from libgcc-10-dev:amd64.

Before, there was:
/usr/lib/gcc/x86_64-linux-gnu/10/include/sanitizer/asan_interface.h
/usr/lib/gcc/x86_64-linux-gnu/10/include/sanitizer/common_interface_defs.h
/usr/lib/gcc/x86_64-linux-gnu/10/include/sanitizer/lsan_interface.h
/usr/lib/gcc/x86_64-linux-gnu/10/include/sanitizer/tsan_interface.h

Regards,
Arnaud Giersch
--- End Message ---
--- Begin Message ---
Source: gcc-10
Source-Version: 10-20200324-1
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-10 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 24 Mar 2020 13:38:16 +0100
Source: gcc-10
Architecture: source
Version: 10-20200324-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 954438 954751
Changes:
 gcc-10 (10-20200324-1) unstable; urgency=medium
 .
   * GCC snapshot, taken from the trunk (20200324, 906b3eb9df6).
   * libgcc-N-dev: Include sanitizer headers again. Closes: #954751.
   * gm2: Define lang_register_spec_functions for jit. Closes: #954438.
Checksums-Sha1:
 e66b24bc8f97a541f47fa47ea71c0105574cae78 27934 gcc-10_10-20200324-1.dsc
 70b8e9a9d898b6f2b317eaeacbb2f39ea8cac9f6 89049019 
gcc-10_10-20200324.orig.tar.gz
 6ae7b254c119337627f621a7a107c3a64ed77ed4 556696 
gcc-10_10-20200324-1.debian.tar.xz
 51fef4c5773c19369520755b3fca51c14cf77987 11070 
gcc-10_10-20200324-1_source.buildinfo
Checksums-Sha256:
 86f6cd672db6314c23cbf3d66cc6ab3d9d8b319ea538c9d586f318409c567e4e 27934 
gcc-10_10-20200324-1.dsc
 7ea222fbf7d6eea9e0a288a6ea92d72b023349a060a62adb032db2931fb9e1b8 89049019 
gcc-10_10-20200324.orig.tar.gz
 701bebb749971eabfde28214096e001cc066732d846e4056ca2967b92f1de606 556696 
gcc-10_10-20200324-1.debian.tar.xz
 db390d19c0a772c14a6d998c2fd708ca23426a3efe20101c2c43b314f7caf5fb 11070 
gcc-10_10-20200324-1_source.buildinfo
Files:
 691a90d9eb6218a5e4d7024f0d17dc5a 27934 devel optional gcc-10_10-20200324-1.dsc
 f6aeb8a31c0d9fe680ba01f3a4ed9758 89049019 devel optional 
gcc-10_10-20200324.orig.tar.gz
 b45e049bfdfe375847bc18beeb8dc601 556696 devel optional 
gcc-10_10-20200324-1.debian.tar.xz
 45dacdb38bc1ef6ce2b29f423372ca01 11070 devel optional 
gcc-10_10-20200324-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl56AlUQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9S5QEADLGyMKUjc5epuUOHqiXcWQLJ0cj4oupCm5
p7MUBJe++N3XGO32b29OddUHy1sRh2SpEg3HogSuwG2JiZeEGw28E7Q+sVRPtNjD
ulP70wD0YNRjYEJZCp9wF1yz7su9Q9VbFtgRX1i4pSl+4D9kTJnYDXQx4xMnhCq4
QQEsnhi3rWib1eZptV8jiwhT5vWNcsGChRNUQXeKVyqaX/tmT8qYED0MtEunIY6G
oAF2sKps5K+OR82FjM9+8i/mNRUvPgNhH+wmOaVMVw08eZYDm1sgvQLNsh+zl+ni
M3jjCRAuFSBPNE/09kGHGUQcAiN7R/r8WUDXDvch6ZxblsGmnvPGvNCBq9gnReeQ
e5dVs4bn5cx2Oap4hvXJGYjLwPx54QgjpIYB1RBlbfS5paeV4rUp9qE9TBEOh9sR
rIr6MxkZ9eV/6EmsDaDDhwXjSi4LABP2nBCtw0HLaxIVsTA8e7flarlpAcJidOuc
bUr8Tq8zcK+xQz8JDahpCgjpCiATqEaLK9ySZwz9+WZtJOy2YJj1uwksFdtDFsK0
NRKRO3P6I4qNKEcV18hXdTMx2QnjlBLdVfFg5UDxWy9ayOaO58lodgtAZwjW+Iga
MX5DZs8hfvrSQI5R2Mi/asA9kGmuWzeK9oetXB1ZXfMzt7OZNw0LvlPgDR0H2fqi
xALmvQyaZg==
=KSOL
-END PGP SIGNATURE End Message ---

Bug#954438: marked as done (libgccjit0: GCCJIT leads to linking error)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 13:06:09 +
with message-id 
and subject line Bug#954438: fixed in gcc-10 10-20200324-1
has caused the Debian Bug report #954438,
regarding libgccjit0: GCCJIT leads to linking error
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.)


-- 
954438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgccjit0
Version: 10-20200312-2
Severity: important

Dear Maintainer,

libgccjit0 leads to linking error, I have the following C source code: 

#include 
#include 
#include 

int main(int argc, char **argv) {
gcc_jit_context *ctxt;
ctxt = gcc_jit_context_acquire();
gcc_jit_rvalue *args[2]; 
printf("%5.8lf\n", sin(30)); 
return 0;
}


and I compiled it using the following command line:

gcc-10 test.c -o test -lgccjit

or 

gcc-10 test.c -lgccjit -o test 

leads to the same error message:

/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/libgccjit.so: undefined reference 
to `lang_register_spec_functions()'
collect2: error: ld returned 1 exit status

However, exactly the same gcc and gccjit version on Fedora Rawhide work as 
intened. 

It seems a gccjit issue rather than a ld issue. 

Thanks, 
Gong-Yi. 



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

Kernel: Linux 5.4.0-0.bpo.3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libgccjit0 depends on:
ii  binutils   2.34-5
ii  gcc-10-base10-20200312-2
ii  libc6  2.30-2
ii  libgcc-10-dev  10-20200312-2
ii  libgmp10   2:6.2.0+dfsg-4
ii  libisl22   0.22.1-1
ii  libmpc31.1.0-1
ii  libmpfr6   4.0.2-1
ii  libzstd1   1.4.4+dfsg-3
ii  zlib1g 1:1.2.11.dfsg-2

libgccjit0 recommends no packages.

libgccjit0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gcc-10
Source-Version: 10-20200324-1
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-10 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 24 Mar 2020 13:38:16 +0100
Source: gcc-10
Architecture: source
Version: 10-20200324-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 954438 954751
Changes:
 gcc-10 (10-20200324-1) unstable; urgency=medium
 .
   * GCC snapshot, taken from the trunk (20200324, 906b3eb9df6).
   * libgcc-N-dev: Include sanitizer headers again. Closes: #954751.
   * gm2: Define lang_register_spec_functions for jit. Closes: #954438.
Checksums-Sha1:
 e66b24bc8f97a541f47fa47ea71c0105574cae78 27934 gcc-10_10-20200324-1.dsc
 70b8e9a9d898b6f2b317eaeacbb2f39ea8cac9f6 89049019 
gcc-10_10-20200324.orig.tar.gz
 6ae7b254c119337627f621a7a107c3a64ed77ed4 556696 
gcc-10_10-20200324-1.debian.tar.xz
 51fef4c5773c19369520755b3fca51c14cf77987 11070 
gcc-10_10-20200324-1_source.buildinfo
Checksums-Sha256:
 86f6cd672db6314c23cbf3d66cc6ab3d9d8b319ea538c9d586f318409c567e4e 27934 
gcc-10_10-20200324-1.dsc
 7ea222fbf7d6eea9e0a288a6ea92d72b023349a060a62adb032db2931fb9e1b8 89049019 
gcc-10_10-20200324.orig.tar.gz
 701bebb749971eabfde28214096e001cc066732d846e4056ca2967b92f1de606 556696 
gcc-10_10-20200324-1.debian.tar.xz
 db390d19c0a772c14a6d998c2fd708ca23426a3efe20101c2c43b314f7caf5fb 11070 
gcc-10_10-20200324-1_source.buildinfo
Files:
 691a90d9eb6218a5e4d7024f0d17dc5a 27934 devel optional gcc-10_10-20200324-1.dsc
 f6aeb8a31c0d9fe680ba01f3a4ed9758 89049019 devel optional 
gcc-10_10-20200324.o

Bug#951893: marked as done (subversion FTBFS with swig 4.0.1)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 12:52:28 +
with message-id 
and subject line Bug#951893: fixed in subversion 1.13.0-3
has caused the Debian Bug report #951893,
regarding subversion FTBFS with swig 4.0.1
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.)


-- 
951893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: subversion
Version: 1.13.0-2
Severity: serious
Tags: ftbfs

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

...
/usr/bin/swig -I/build/1st/subversion-1.13.0/BUILD/subversion 
-I/build/1st/subversion-1.13.0/subversion/include 
-I/build/1st/subversion-1.13.0/subversion/bindings/swig 
-I/build/1st/subversion-1.13.0/subversion/bindings/swig/include 
-I/build/1st/subversion-1.13.0/subversion/bindings/swig/proxy 
-I/build/1st/subversion-1.13.0/BUILD/subversion/bindings/swig/proxy 
-I/usr/include/apr-1.0  -I/usr/include/apr-1.0 -I/usr/include  -python  
-classic -o subversion/bindings/swig/python/core.c 
/build/1st/subversion-1.13.0/subversion/bindings/swig/core.i
Deprecated command line option: -classic. This option is no longer supported.
make[1]: *** [/build/1st/subversion-1.13.0/build-outputs.mk:290: 
subversion/bindings/swig/python/core.c] Error 1
--- End Message ---
--- Begin Message ---
Source: subversion
Source-Version: 1.13.0-3
Done: James McCoy 

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

Debian distribution maintenance software
pp.
James McCoy  (supplier of updated subversion package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Mar 2020 08:33:36 -0400
Source: subversion
Architecture: source
Version: 1.13.0-3
Distribution: unstable
Urgency: medium
Maintainer: James McCoy 
Changed-By: James McCoy 
Closes: 951893
Changes:
 subversion (1.13.0-3) unstable; urgency=medium
 .
   [ James McCoy ]
   * rules: Use "pyversions -s" instead of "pyversions -i"
   * Build with swig3.0 to fix FTBFS with swig4.0 (Closes: #951893)
   * Declare compliance with Policy 4.5.0, no changes needed
   * Build-Depend on debhelper-compat (= 12)
 .
   [ Dimitri John Ledkov ]
   * swig.m4: Do not include ruby include subdir
Checksums-Sha1:
 ca4a88b5f09d0b62842c4a407aafbe5abbb40c7f 3650 subversion_1.13.0-3.dsc
 cfefa5fce1fed37db86c9f4e75625aeeb72ba331 421004 
subversion_1.13.0-3.debian.tar.xz
Checksums-Sha256:
 60a21b226bfec8c6c81da3ab0049866298481da1898db8304a0c718dcb157d84 3650 
subversion_1.13.0-3.dsc
 4bae277b8c9622ed8475f1b3172239854b5de5d603f6491a11f9fcdc6ce9d04f 421004 
subversion_1.13.0-3.debian.tar.xz
Files:
 43ba9047d4bfa34592a76b1886ce62e4 3650 vcs optional subversion_1.13.0-3.dsc
 a4e655a1b758aad0a0fa214d79b28650 421004 vcs optional 
subversion_1.13.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKoBAEBCgCSFiEEkb+/TWlWvV33ty0j3+aRrjMbo9sFAl55/w1fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDkx
QkZCRjRENjk1NkJENURGN0I3MkQyM0RGRTY5MUFFMzMxQkEzREIUHGphbWVzc2Fu
QGRlYmlhbi5vcmcACgkQ3+aRrjMbo9tSGA/+KbGGaSy0+7VSkGGb15DzU/JmhGYI
0hs1+Dnuqy3Dxpy4IVVJZuFmyWyHXbpI3ymUDFCmR5Nbwt4hhdcn4hYBcAK6EZHf
4SOwZt4CqR7CZ8YWYOqTo0Pbb2QGouynyszg1aK1liwcEW9rcAYs1IaiahBejW0e
TYwN9qb0tEXBoESnHvTpMUwizR5X6OS5dg2jjFHBqtcje6Vb28MPU8gBTCeIbyR6
JoUb11LAgg/UWer8o2nFsVWxxpTxc7vi7bb08YUfKYTPPRXnsQYMyl/a4n2pHUPO
N6gMocwZPFneaIOAcj2JLksda+K6y8rPgGDI4S/adfG8sOIi1BOOZcEi9rh2XYfm
BcVwKSpnR9ocFwp3Uo9hKBfdqJaELaS1UcvziCAC9Ylx1yLE06VStb6oqI3MFrzd
VSKR6cRTkW3bwLixx/CLfaGGnx16FaiQ5l6DFVClvoaI6RMCebW5/vVsWcNtWIC/
HepNUISpy5JhTOpM3BTj5s2rsNoG2GcurG0ljA24dCTm/zBqZdrRWUiNkZBL/nhj
xQAC4/DWAz+euoNteVKA1Ja5d4gRKFjyPmebd6TmfJvCKQNhrP4hZiewZO7FecCF
ihb0T9bzT6S4qek7Lu8TF8PPP1ClJ9vcRHtrUrzEaRJ0Vcx/dmL+CqqhFIF+Acsq
F5+X0lChmPeDvdM=
=FfCQ
-END PGP SIGNATURE End Message ---

Bug#953057: marked as done (subversion: FTBFS against swig 4)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 12:52:28 +
with message-id 
and subject line Bug#951893: fixed in subversion 1.13.0-3
has caused the Debian Bug report #951893,
regarding subversion: FTBFS against swig 4
to be marked as done.

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

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


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

Dear Maintainer,

While trying to rebuild src:subversion in a clean unstable amd64 chroot
I got the following error:

...
Wrote subversion/bindings/swig/proxy/swig_python_external_runtime.swg
/usr/bin/swig -I/<>/BUILD/subversion
-I/<>/subversion/include
-I/<>/subversion/bindings/swig
-I/<>/subversion/bindings/swig/include
-I/<>/subversion/bindings/swig/proxy
-I/<>/BUILD/subversion/bindings/swig/proxy
-I/usr/include/apr-1.0  -I/usr/include/apr-1.0 -I/usr/include  -python 
-classic -o subversion/bindings/swig/python/core.c
/<>/subversion/bindings/swig/core.i
Deprecated command line option: -classic. This option is no longer
supported.
make[1]: *** [/<>/build-outputs.mk:290:
subversion/bindings/swig/python/core.c] Error 1
make[1]: Leaving directory '/<>/BUILD'
make: *** [debian/rules:228: debian/stamp-build-arch] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit
status 2

This is a known open upstream bug [1]. Just dropping the '-classic'
option does not work, other errors pop up.

[1] https://issues.apache.org/jira/browse/SVN-4818

-- 
Lucas Kanashiro
--- End Message ---
--- Begin Message ---
Source: subversion
Source-Version: 1.13.0-3
Done: James McCoy 

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

Debian distribution maintenance software
pp.
James McCoy  (supplier of updated subversion package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Mar 2020 08:33:36 -0400
Source: subversion
Architecture: source
Version: 1.13.0-3
Distribution: unstable
Urgency: medium
Maintainer: James McCoy 
Changed-By: James McCoy 
Closes: 951893
Changes:
 subversion (1.13.0-3) unstable; urgency=medium
 .
   [ James McCoy ]
   * rules: Use "pyversions -s" instead of "pyversions -i"
   * Build with swig3.0 to fix FTBFS with swig4.0 (Closes: #951893)
   * Declare compliance with Policy 4.5.0, no changes needed
   * Build-Depend on debhelper-compat (= 12)
 .
   [ Dimitri John Ledkov ]
   * swig.m4: Do not include ruby include subdir
Checksums-Sha1:
 ca4a88b5f09d0b62842c4a407aafbe5abbb40c7f 3650 subversion_1.13.0-3.dsc
 cfefa5fce1fed37db86c9f4e75625aeeb72ba331 421004 
subversion_1.13.0-3.debian.tar.xz
Checksums-Sha256:
 60a21b226bfec8c6c81da3ab0049866298481da1898db8304a0c718dcb157d84 3650 
subversion_1.13.0-3.dsc
 4bae277b8c9622ed8475f1b3172239854b5de5d603f6491a11f9fcdc6ce9d04f 421004 
subversion_1.13.0-3.debian.tar.xz
Files:
 43ba9047d4bfa34592a76b1886ce62e4 3650 vcs optional subversion_1.13.0-3.dsc
 a4e655a1b758aad0a0fa214d79b28650 421004 vcs optional 
subversion_1.13.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKoBAEBCgCSFiEEkb+/TWlWvV33ty0j3+aRrjMbo9sFAl55/w1fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDkx
QkZCRjRENjk1NkJENURGN0I3MkQyM0RGRTY5MUFFMzMxQkEzREIUHGphbWVzc2Fu
QGRlYmlhbi5vcmcACgkQ3+aRrjMbo9tSGA/+KbGGaSy0+7VSkGGb15DzU/JmhGYI
0hs1+Dnuqy3Dxpy4IVVJZuFmyWyHXbpI3ymUDFCmR5Nbwt4hhdcn4hYBcAK6EZHf
4SOwZt4CqR7CZ8YWYOqTo0Pbb2QGouynyszg1aK1liwcEW9rcAYs1IaiahBejW0e
TYwN9qb0tEXBoESnHvTpMUwizR5X6OS5dg2jjFHBqtcje6Vb28MPU8gBTCeIbyR6
JoUb11LAgg/UWer8o2nFsVWxxpTxc7vi7bb08YUfKYTPPRXnsQYMyl/a4n2pHUPO
N6gMocwZPFneaIOAcj2JLksda+K6y8rPgGDI4S/adfG8sOIi1BOOZcEi9rh2XYfm
BcVwKSpnR9ocFwp3Uo9hKBfdqJaELaS1UcvziCAC9Ylx1yLE06VStb6oqI3MFrzd
VSKR6cRTkW3bwLixx/CLfaGGnx16FaiQ5l6DFVClvoaI6RMCebW5/vVsWcNtWIC/
HepNUISpy5JhTOpM3BTj5s2rsNoG2GcurG0ljA24dCTm/zBqZdrRWUiNkZBL/nhj
xQAC4/DWAz+euoNteVKA1Ja5d4gRKFjyPmebd6TmfJvCKQNhrP4hZiewZO7FecCF
ihb0T9bzT6S4qek7Lu8TF8PPP1ClJ9vcRHtrUrzEaRJ0Vcx/dmL+CqqhFIF+Acsq
F5+X0lChmPeDvdM=
=FfCQ
-END PGP SIGNATURE End 

Bug#954617: marked as done (golang-github-mendersoftware-log: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/mendersoftware/log returned exit code 2)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 12:49:33 +
with message-id 
and subject line Bug#954617: fixed in golang-github-mendersoftware-log 
0.0~git20191210.25ea5b7-1
has caused the Debian Bug report #954617,
regarding golang-github-mendersoftware-log: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/mendersoftware/log 
returned exit code 2
to be marked as done.

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

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


-- 
954617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-mendersoftware-log
Version: 0.0~git20180403.f608c95-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> github.com/mendersoftware/log
> math/bits
> runtime/internal/sys
> runtime/internal/atomic
> internal/cpu
> runtime/internal/math
> unicode/utf8
> internal/race
> sync/atomic
> internal/bytealg
> math
> unicode
> internal/testlog
> container/list
> encoding
> unicode/utf16
> runtime
> internal/nettrace
> runtime/cgo
> internal/reflectlite
> sync
> internal/singleflight
> math/rand
> errors
> sort
> io
> strconv
> internal/oserror
> vendor/golang.org/x/net/dns/dnsmessage
> strings
> syscall
> reflect
> bytes
> bufio
> time
> internal/syscall/unix
> internal/poll
> context
> encoding/binary
> internal/fmtsort
> os
> encoding/base64
> golang.org/x/sys/unix
> net
> fmt
> github.com/mendersoftware/scopestack
> log
> encoding/json
> github.com/sirupsen/logrus
> log/syslog
> github.com/sirupsen/logrus/hooks/syslog
> github.com/mendersoftware/log
>dh_auto_test -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
> github.com/mendersoftware/log
> # github.com/mendersoftware/log [github.com/mendersoftware/log.test]
> src/github.com/mendersoftware/log/log_test.go:41:2: undefined: 
> mendertesting.AssertTrue
> src/github.com/mendersoftware/log/log_test.go:61:2: undefined: 
> mendertesting.AssertTrue
> src/github.com/mendersoftware/log/log_test.go:64:2: undefined: 
> mendertesting.AssertTrue
> src/github.com/mendersoftware/log/log_test.go:65:2: undefined: 
> mendertesting.AssertTrue
> src/github.com/mendersoftware/log/log_test.go:76:2: undefined: 
> mendertesting.AssertTrue
> src/github.com/mendersoftware/log/log_test.go:211:2: undefined: 
> mendertesting.AssertTrue
> src/github.com/mendersoftware/log/log_test.go:215:2: undefined: 
> mendertesting.AssertTrue
> src/github.com/mendersoftware/log/log_test.go:216:2: undefined: 
> mendertesting.AssertTrue
> src/github.com/mendersoftware/log/log_test.go:218:2: undefined: 
> mendertesting.AssertStringEqual
> src/github.com/mendersoftware/log/log_test.go:287:2: undefined: 
> mendertesting.AssertTrue
> src/github.com/mendersoftware/log/log_test.go:287:2: too many errors
> FAIL  github.com/mendersoftware/log [build failed]
> FAIL
> dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
> github.com/mendersoftware/log returned exit code 2

The full build log is available from:
   
http://qa-logs.debian.net/2020/03/21/golang-github-mendersoftware-log_0.0~git20180403.f608c95-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: golang-github-mendersoftware-log
Source-Version: 0.0~git20191210.25ea5b7-1
Done: Lluis Campos 

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

Debian distribution maintenance software
pp.

Bug#952199: marked as done (golang-github-boltdb-bolt: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 -short github.com/boltdb/bolt github.com/boltdb/bolt/cmd/bolt ret

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 12:49:18 +
with message-id 
and subject line Bug#952199: fixed in golang-github-boltdb-bolt 1.3.1-7
has caused the Debian Bug report #952199,
regarding golang-github-boltdb-bolt: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 4 -short github.com/boltdb/bolt 
github.com/boltdb/bolt/cmd/bolt returned exit code 1
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.)


-- 
952199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-boltdb-bolt
Version: 1.3.1-6
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 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_auto_test -- -short
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 -short 
> github.com/boltdb/bolt github.com/boltdb/bolt/cmd/bolt
> flag provided but not defined: -test.testlogfile
> Usage of /tmp/go-build232881692/b001/bolt.test:
>   -quick.count int
>(default 5)
>   -quick.maxitems int
>(default 1000)
>   -quick.maxksize int
>(default 1024)
>   -quick.maxvsize int
>(default 1024)
>   -quick.seed int
>(default 4109)
>   -quickchecks int
>   The default number of iterations for each check (default 100)
>   -stats
>   show performance stats
> FAIL  github.com/boltdb/bolt  0.002s
> === RUN   TestInfoCommand_Run
> --- PASS: TestInfoCommand_Run (0.00s)
> === RUN   TestStatsCommand_Run_EmptyDatabase
> --- PASS: TestStatsCommand_Run_EmptyDatabase (0.00s)
> === RUN   TestStatsCommand_Run
> --- PASS: TestStatsCommand_Run (0.01s)
> === RUN   TestCompactCommand_Run
> --- PASS: TestCompactCommand_Run (0.30s)
> PASS
> okgithub.com/boltdb/bolt/cmd/bolt 0.318s
> FAIL
> dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
> -short github.com/boltdb/bolt github.com/boltdb/bolt/cmd/bolt returned exit 
> code 1

The full build log is available from:
   
http://qa-logs.debian.net/2020/02/22/golang-github-boltdb-bolt_1.3.1-6_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: golang-github-boltdb-bolt
Source-Version: 1.3.1-7
Done: Nilesh Patra 

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated 
golang-github-boltdb-bolt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 22 Mar 2020 15:16:56 +0530
Source: golang-github-boltdb-bolt
Architecture: source
Version: 1.3.1-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Nilesh Patra 
Closes: 952199
Changes:
 golang-github-boltdb-bolt (1.3.1-7) unstable; urgency=medium
 .
   * Team Upload.
   * Initialize test to fix flag parsing issue (Closes: #952199)
   * Drop compat, switch to debhelper-compat
   * Bump standards version to 4.5.0
   * Add "Rules-Requires-Root:no"
   * Add upstream/metadata
Checksums-Sha1:
 c1c6b01020c92df218803f876f64c32bcb171f36 2244 
golang-github-boltdb-bolt_1.3.1-7.dsc
 9c980195c4d00259ccc4f8dbfe51d07f52176505 4808 
golang-github-boltdb-bolt_1.3.1-7.debian.tar.xz
 bbb9bfeae0cde535ef0b8d10fa9e2ed2eb3096a7 5857 
golang-github-boltdb-bolt_1.3.1-7_amd64.buildinfo
Checksums-Sha256:
 f33df268715b1f4740ba96d8cfebf472b24371dd4330f05bd7f405fd0a87de19 2244 
golang-github-boltdb-bolt_1.3.1-7.dsc
 1f98330a7e5734860819dc9647723f632c5e3fe185b50fb6c1cd41a68655 4808 
golang-github-boltdb-bolt_1.3.1-7.debian.tar.xz
 

Bug#952321: marked as done (golang-github-akrennmair-gopcap: FTBFS: dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 1 github.com/akrennmair/gopcap returned exit code 2)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 12:19:51 +
with message-id 
and subject line Bug#952321: fixed in golang-github-akrennmair-gopcap 
0.0~git20150728.0.00e1103-3
has caused the Debian Bug report #952321,
regarding golang-github-akrennmair-gopcap: FTBFS: dh_auto_build: error: cd 
obj-x86_64-linux-gnu && go install -trimpath -v -p 1 
github.com/akrennmair/gopcap returned exit code 2
to be marked as done.

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

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


-- 
952321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-akrennmair-gopcap
Version: 0.0~git20150728.0.00e1103-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 1 
> github.com/akrennmair/gopcap
> internal/cpu
> internal/bytealg
> runtime/internal/atomic
> runtime/internal/sys
> runtime/internal/math
> runtime
> internal/reflectlite
> errors
> internal/race
> sync/atomic
> sync
> io
> math/bits
> math
> unicode/utf8
> strconv
> unicode
> reflect
> encoding/binary
> sort
> internal/fmtsort
> internal/oserror
> syscall
> time
> internal/poll
> internal/syscall/unix
> internal/testlog
> os
> fmt
> context
> vendor/golang.org/x/net/dns/dnsmessage
> internal/nettrace
> internal/singleflight
> math/rand
> runtime/cgo
> net
> strings
> github.com/akrennmair/gopcap
> # github.com/akrennmair/gopcap
> src/github.com/akrennmair/gopcap/pcap.go:129:13: identifier 
> "_Ctype_struct_pcap_stat" may conflict with identifiers generated by cgo
> src/github.com/akrennmair/gopcap/pcap.go:142:10: identifier 
> "_Ctype_struct_bpf_program" may conflict with identifiers generated by cgo
> src/github.com/akrennmair/gopcap/pcap.go:216:34: identifier 
> "_Ctype_struct_pcap_addr" may conflict with identifiers generated by cgo
> src/github.com/akrennmair/gopcap/pcap.go:219:56: identifier 
> "_Ctype_struct_pcap_addr" may conflict with identifiers generated by cgo
> dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 1 
> github.com/akrennmair/gopcap returned exit code 2
> make: *** [debian/rules:6: build] Error 25

The full build log is available from:
   
http://qa-logs.debian.net/2020/02/22/golang-github-akrennmair-gopcap_0.0~git20150728.0.00e1103-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: golang-github-akrennmair-gopcap
Source-Version: 0.0~git20150728.0.00e1103-3
Done: Nilesh Patra 

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated 
golang-github-akrennmair-gopcap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 22 Mar 2020 17:36:28 +0530
Source: golang-github-akrennmair-gopcap
Architecture: source
Version: 0.0~git20150728.0.00e1103-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Nilesh Patra 
Closes: 952321
Changes:
 golang-github-akrennmair-gopcap (0.0~git20150728.0.00e1103-3) unstable; 
urgency=medium
 .
   * Team Upload.
 .
   [ Alexandre Viau ]
   * Point Vcs-* urls to salsa.debian.org.
 .
   [ Jelmer Vernooij ]
   * Use secure copyright file specification URI.
 .
   [ Nilesh Patra ]
   * Fix syntax to fix FTBFS (Closes: #952321)
   * 

Bug#899088: marked as done (gcc-8-cross-ports: provide riscv32 cross compiler)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 12:09:06 +
with message-id 
and subject line Bug#954831: Removed package(s) from unstable
has caused the Debian Bug report #899088,
regarding gcc-8-cross-ports: provide riscv32 cross compiler
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.)


-- 
899088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-8-cross-ports
Version: 8.1.0-1cross2
Severity: wishlist

Dear Maintainer,

cross compiling for boards using a 32bit RISC-V processor (like
AndesCore NX25) requires a corresponding compiler.

We already build a gcc cross compiler for 64bit RISC-V. Please, add a
32bit cross compiler too.

Best regards

Heinrich

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

Kernel: Linux 4.16.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 27+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#928424: marked as done (gcc-8-cross: Does not honor parallel=n properly in DEB_BUILD_OPTIONS)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 12:07:34 +
with message-id 
and subject line Bug#954831: Removed package(s) from unstable
has caused the Debian Bug report #928424,
regarding gcc-8-cross: Does not honor parallel=n properly in DEB_BUILD_OPTIONS
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.)


-- 
928424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-8-cross
Version: 28

Dear Matthias:

I see this in debian/rules:

  ifeq ($(JOBS),1)
JOBS := 2
  endif

This was made in commit a4c6cdfc25368c1c86dfd215db99669f93f1f096
but the changelog does not say anything about it.

I believe this is related to the Makefile bug I reported in #924325,
but that will certainly not fix it, just hide it.

More to the point: If we know there is a Makefile bug and we don't
know why it does not show that way, we have no warranty at all that it
will work, it will do so by pure chance.

Thanks.
--- End Message ---
--- Begin Message ---
Version: 33+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#954831: marked as done (RM: gcc-8, superseded by gcc-9)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 12:07:22 +
with message-id 
and subject line Bug#954831: Removed package(s) from unstable
has caused the Debian Bug report #954831,
regarding RM: gcc-8, superseded by gcc-9
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.)


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

Please remove gcc-8, gcc-8-cross and gcc-8-cross-ports. superseded by gcc-9
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

cpp-8-aarch64-linux-gnu | 8.4.0-1cross1 | amd64, i386, ppc64el
cpp-8-arm-linux-gnueabi | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
cpp-8-arm-linux-gnueabihf | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
cpp-8-i686-linux-gnu | 8.4.0-1cross1 | amd64, arm64, ppc64el
cpp-8-powerpc64le-linux-gnu | 8.4.0-1cross1 | amd64, arm64, i386
cpp-8-s390x-linux-gnu | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
cpp-8-x86-64-linux-gnu | 8.4.0-1cross1 | arm64, i386, ppc64el
g++-8-aarch64-linux-gnu | 8.4.0-1cross1 | amd64, i386, ppc64el
g++-8-arm-linux-gnueabi | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
g++-8-arm-linux-gnueabihf | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
g++-8-i686-linux-gnu | 8.4.0-1cross1 | amd64, arm64, ppc64el
g++-8-multilib-i686-linux-gnu | 8.4.0-1cross1 | amd64, arm64, ppc64el
g++-8-multilib-s390x-linux-gnu | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
g++-8-multilib-x86-64-linux-gnu | 8.4.0-1cross1 | arm64, i386, ppc64el
g++-8-powerpc64le-linux-gnu | 8.4.0-1cross1 | amd64, arm64, i386
g++-8-s390x-linux-gnu | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
g++-8-x86-64-linux-gnu | 8.4.0-1cross1 | arm64, i386, ppc64el
gcc-8-aarch64-linux-gnu | 8.4.0-1cross1 | amd64, i386, ppc64el
gcc-8-aarch64-linux-gnu-base | 8.4.0-1cross1 | amd64, i386, ppc64el
gcc-8-arm-linux-gnueabi | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
gcc-8-arm-linux-gnueabi-base | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
gcc-8-arm-linux-gnueabihf | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
gcc-8-arm-linux-gnueabihf-base | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
gcc-8-cross | 33 | source
gcc-8-cross-base | 8.4.0-1cross1 | all
gcc-8-i686-linux-gnu | 8.4.0-1cross1 | amd64, arm64, ppc64el
gcc-8-i686-linux-gnu-base | 8.4.0-1cross1 | amd64, arm64, ppc64el
gcc-8-multilib-i686-linux-gnu | 8.4.0-1cross1 | amd64, arm64, ppc64el
gcc-8-multilib-s390x-linux-gnu | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
gcc-8-multilib-x86-64-linux-gnu | 8.4.0-1cross1 | arm64, i386, ppc64el
gcc-8-plugin-dev-aarch64-linux-gnu | 8.4.0-1cross1 | amd64, i386, ppc64el
gcc-8-plugin-dev-arm-linux-gnueabi | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
gcc-8-plugin-dev-arm-linux-gnueabihf | 8.4.0-1cross1 | amd64, arm64, i386, 
ppc64el
gcc-8-plugin-dev-i686-linux-gnu | 8.4.0-1cross1 | amd64, arm64, ppc64el
gcc-8-plugin-dev-powerpc64le-linux-gnu | 8.4.0-1cross1 | amd64, arm64, i386
gcc-8-plugin-dev-s390x-linux-gnu | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
gcc-8-plugin-dev-x86-64-linux-gnu | 8.4.0-1cross1 | arm64, i386, ppc64el
gcc-8-powerpc64le-linux-gnu | 8.4.0-1cross1 | amd64, arm64, i386
gcc-8-powerpc64le-linux-gnu-base | 8.4.0-1cross1 | amd64, arm64, i386
gcc-8-s390x-linux-gnu | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
gcc-8-s390x-linux-gnu-base | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
gcc-8-x86-64-linux-gnu | 8.4.0-1cross1 | arm64, i386, ppc64el
gcc-8-x86-64-linux-gnu-base | 8.4.0-1cross1 | arm64, i386, ppc64el
gccbrig-8-i686-linux-gnu | 8.4.0-1cross1 | amd64, arm64, ppc64el
gccbrig-8-x86-64-linux-gnu | 8.4.0-1cross1 | arm64, i386, ppc64el
gccgo-8-aarch64-linux-gnu | 8.4.0-1cross1 | amd64, i386, ppc64el
gccgo-8-arm-linux-gnueabi | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
gccgo-8-arm-linux-gnueabihf | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
gccgo-8-i686-linux-gnu | 8.4.0-1cross1 | amd64, arm64, ppc64el
gccgo-8-multilib-i686-linux-gnu | 8.4.0-1cross1 | amd64, arm64, ppc64el
gccgo-8-multilib-s390x-linux-gnu | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
gccgo-8-multilib-x86-64-linux-gnu | 8.4.0-1cross1 | arm64, i386, ppc64el
gccgo-8-powerpc64le-linux-gnu | 8.4.0-1cross1 | amd64, arm64, i386
gccgo-8-s390x-linux-gnu | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
gccgo-8-x86-64-linux-gnu | 8.4.0-1cross1 | arm64, i386, ppc64el
gdc-8-aarch64-linux-gnu | 8.4.0-1cross1 | amd64, i386, ppc64el
gdc-8-arm-linux-gnueabi | 8.4.0-1cross1 | amd64, arm64, i386, ppc64el
gdc-8-arm-linux-gnueabihf | 8.4.0-1cross1 | amd64, 

Bug#954515: marked as done (gcc-8-cross: FTBFS: x86_64-linux-gnu-ld: /lib/x86_64-linux-gnu/libpthread.so.0: undefined reference to `__twalk_r@GLIBC_PRIVATE')

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 12:07:34 +
with message-id 
and subject line Bug#954831: Removed package(s) from unstable
has caused the Debian Bug report #954515,
regarding gcc-8-cross: FTBFS: x86_64-linux-gnu-ld: 
/lib/x86_64-linux-gnu/libpthread.so.0: undefined reference to 
`__twalk_r@GLIBC_PRIVATE'
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.)


-- 
954515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-8-cross
Version: 33
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[5]: Entering directory '/<>/gcc/build/gotools'
> /<>/gcc/build/./gcc/gccgo -B/<>/gcc/build/./gcc/ 
> -B/usr/x86_64-linux-gnu/bin/ -B/usr/x86_64-linux-gnu/lib/ -isystem 
> /usr/x86_64-linux-gnu/include -isystem /usr/x86_64-linux-gnu/sys-include 
> -isystem /<>/gcc/build/sys-include   -g -O2 -I 
> ../x86_64-linux-gnu/libgo -static-libstdc++ -static-libgcc -Wl,-z,relro -L 
> ../x86_64-linux-gnu/libgo -L ../x86_64-linux-gnu/libgo/.libs -o go 
> ../../src/gotools/../libgo/go/cmd/go/alldocs.go 
> ../../src/gotools/../libgo/go/cmd/go/go11.go 
> ../../src/gotools/../libgo/go/cmd/go/main.go 
> ../x86_64-linux-gnu/libgo/libgotool.a  
> /<>/gcc/build/./gcc/gccgo -B/<>/gcc/build/./gcc/ 
> -B/usr/x86_64-linux-gnu/bin/ -B/usr/x86_64-linux-gnu/lib/ -isystem 
> /usr/x86_64-linux-gnu/include -isystem /usr/x86_64-linux-gnu/sys-include 
> -isystem /<>/gcc/build/sys-include   -g -O2 -I 
> ../x86_64-linux-gnu/libgo -static-libstdc++ -static-libgcc -Wl,-z,relro -L 
> ../x86_64-linux-gnu/libgo -L ../x86_64-linux-gnu/libgo/.libs -o gofmt 
> ../../src/gotools/../libgo/go/cmd/gofmt/doc.go 
> ../../src/gotools/../libgo/go/cmd/gofmt/gofmt.go 
> ../../src/gotools/../libgo/go/cmd/gofmt/internal.go 
> ../../src/gotools/../libgo/go/cmd/gofmt/rewrite.go 
> ../../src/gotools/../libgo/go/cmd/gofmt/simplify.go  
> echo 'package main' > zdefaultcc.go.tmp
> echo 'func defaultGCCGO(goos, goarch string) string { return 
> "/usr/bin/x86_64-linux-gnu-gccgo-8" }' >> zdefaultcc.go.tmp
> /<>/gcc/build/./gcc/gccgo -B/<>/gcc/build/./gcc/ 
> -B/usr/x86_64-linux-gnu/bin/ -B/usr/x86_64-linux-gnu/lib/ -isystem 
> /usr/x86_64-linux-gnu/include -isystem /usr/x86_64-linux-gnu/sys-include 
> -isystem /<>/gcc/build/sys-include   -g -O2 -I 
> ../x86_64-linux-gnu/libgo -static-libstdc++ -static-libgcc -Wl,-z,relro -L 
> ../x86_64-linux-gnu/libgo -L ../x86_64-linux-gnu/libgo/.libs -o vet 
> ../../src/gotools/../libgo/go/cmd/vet/asmdecl.go 
> ../../src/gotools/../libgo/go/cmd/vet/assign.go 
> ../../src/gotools/../libgo/go/cmd/vet/atomic.go 
> ../../src/gotools/../libgo/go/cmd/vet/bool.go 
> ../../src/gotools/../libgo/go/cmd/vet/buildtag.go 
> ../../src/gotools/../libgo/go/cmd/vet/cgo.go 
> ../../src/gotools/../libgo/go/cmd/vet/composite.go 
> ../../src/gotools/../libgo/go/cmd/vet/copylock.go 
> ../../src/gotools/../libgo/go/cmd/vet/deadcode.go 
> ../../src/gotools/../libgo/go/cmd/vet/dead.go 
> ../../src/gotools/../libgo/go/cmd/vet/doc.go 
> ../../src/gotools/../libgo/go/cmd/vet/httpresponse.go 
> ../../src/gotools/../libgo/go/cmd/vet/lostcancel.go 
> ../../src/gotools/../libgo/go/cmd/vet/main.go 
> ../../src/gotools/../libgo/go/cmd/vet/method.go 
> ../../src/gotools/../libgo/go/cmd/vet/nilfunc.go 
> ../../src/gotools/../libgo/go/cmd/vet/print.go 
> ../../src/gotools/../libgo/go/cmd/vet/rangeloop.go 
> ../../src/gotools/../libgo/go/cmd/vet/shadow.go 
> ../../src/gotools/../libgo/go/cmd/vet/shift.go 
> ../../src/gotools/../libgo/go/cmd/vet/structtag.go 
> ../../src/gotools/../libgo/go/cmd/vet/tests.go 
> ../../src/gotools/../libgo/go/cmd/vet/types.go 
> ../../src/gotools/../libgo/go/cmd/vet/unsafeptr.go 
> ../../src/gotools/../libgo/go/cmd/vet/unused.go 
> ../x86_64-linux-gnu/libgo/libgotool.a  
> echo 'func defaultCC(goos, goarch string) string { return 
> "x86_64-linux-gnu-gcc-8" }' >> zdefaultcc.go.tmp
> echo 'func defaultCXX(goos, goarch string) string { return 
> "x86_64-linux-gnu-g++-8" }' >> zdefaultcc.go.tmp
> echo 'const defaultPkgConfig = "pkg-config"' >> zdefaultcc.go.tmp
> /bin/bash ../../src/gotools/../move-if-change zdefaultcc.go.tmp zdefaultcc.go
> echo timestamp > s-zdefaultcc 
> /<>/gcc/build/./gcc/gccgo -B/<>/gcc/build/./gcc/ 
> -B/usr/x86_64-linux-gnu/bin/ -B/usr/x86_64-linux-gnu/lib/ -isystem 
> /usr/x86_64-linux-gnu/include -isystem /usr/x86_64-linux-gnu/sys-include 
> -isystem 

Bug#924325: marked as done (gcc-8-cross: FTBFS for unknown reasons)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 12:07:34 +
with message-id 
and subject line Bug#954831: Removed package(s) from unstable
has caused the Debian Bug report #924325,
regarding gcc-8-cross: FTBFS for unknown reasons
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.)


-- 
924325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gcc-8-cross
Version: 26
Tags: ftbfs

Hello Matthias.

I have been unable to build this package for the last 12 months:

Status: failed  gcc-8-cross_4_amd64-20180218T093520Z
Status: failed  gcc-8-cross_5_amd64-20180224T160324Z
Status: failed  gcc-8-cross_6_amd64-20180321T020921Z
Status: failed  gcc-8-cross_7_amd64-20180328T034559Z
Status: failed  gcc-8-cross_10_amd64-20180415T171623Z
Status: failed  gcc-8-cross_10_amd64-20180606T232216Z
Status: failed  gcc-8-cross_10_amd64-20180613T100719Z
Status: failed  gcc-8-cross_17_amd64-20180614T074203Z
Status: failed  gcc-8-cross_17_amd64-20180630T065556Z
Status: failed  gcc-8-cross_17_amd64-20180710T095437Z
Status: failed  gcc-8-cross_18_amd64-20180729T173009Z
Status: failed  gcc-8-cross_20_amd64-20180820T070711Z
Status: failed  gcc-8-cross_20_amd64-20180920T075713Z
Status: failed  gcc-8-cross_21_amd64-20180924T034119Z
Status: failed  gcc-8-cross_21_amd64-20181015T100546Z
Status: failed  gcc-8-cross_22_amd64-20181105T035318Z
Status: failed  gcc-8-cross_22_amd64-20181209T162522.011Z
Status: failed  gcc-8-cross_24_amd64-20181216T102727.612Z
Status: failed  gcc-8-cross_24_amd64-20190207T101228.086Z
Status: failed  gcc-8-cross_25_amd64-20190220T042620.026Z
Status: failed  gcc-8-cross_26_amd64-20190309T042203.371Z


This is how it fails:

[...]
 debian/rules build-indep
gcc: 8.3.0-2 / 8.3.0-2cross1

old gcc version: 8.3.0-2 / 1

new gcc version: 8.3.0-2cross1
START stamp-dir/init-gcc
mkdir -p gcc
set -ex; \
cd gcc ; \
ln -sf /usr/src/gcc-8/gcc-8.3.0-dfsg.tar.xz gcc-8.3.0-dfsg.tar.xz ;\
cp -a  /usr/src/gcc-8/debian/ . ; \
if [ -n "$(grep -v '^\#' /<>/debian/patches/gcc-8/series)" ]; then 
\
  QUILT_PATCHES=/<>/debian/patches/gcc-8 quilt push --quiltrc 
/dev/null -a ; \

[... snipped ...]

#define HAVE_ICONV 1
#define ICONV_CONST 
#define HAVE_GETIPINFO 1
#define HAVE_LINUX_FUTEX 1
#define _GLIBCXX_SYMVER_GNU 1
#define _GLIBCXX_SYMVER 1
#define HAVE_AS_SYMVER_DIRECTIVE 1
#define HAVE_SYMVER_SYMBOL_RENAMING_RUNTIME_SUPPORT 1
#define _GLIBCXX_X86_RDRAND 1
#define HAVE_UNISTD_H 1
#define HAVE_SYS_TIME_H 1
#define HAVE_SYS_RESOURCE_H 1
#define HAVE_LIMIT_DATA 1
#define HAVE_LIMIT_RSS 1
#define HAVE_LIMIT_VMEM 0
#define HAVE_LIMIT_AS 1
#define HAVE_LIMIT_FSIZE 1
#define _GLIBCXX_RES_LIMITS 1
#define HAVE_SETENV 1
#define _GTHREAD_USE_MUTEX_TIMEDLOCK 1
#define _GLIBCXX_HAS_GTHREADS 1
#define _GLIBCXX_USE_PTHREAD_RWLOCK_T 1
#define HAVE_FCNTL_H 1
#define HAVE_DIRENT_H 1
#define HAVE_SYS_STATVFS_H 1
#define HAVE_UTIME_H 1
#define HAVE_STRUCT_DIRENT_D_TYPE 1
#define _GLIBCXX_USE_REALPATH 1
#define _GLIBCXX_USE_UTIMENSAT 1
#define _GLIBCXX_USE_ST_MTIM 1
#define _GLIBCXX_USE_FCHMOD 1
#define _GLIBCXX_USE_FCHMODAT 1
#define _GLIBCXX_USE_SENDFILE 1
#define _GLIBCXX_MANGLE_SIZE_T m
#define HAVE_EXCEPTION_PTR_SINCE_GCC46 1

configure: exit 0
LOGFILE END /<>/gcc/build/x86_64-linux-gnu/libstdc++-v3/config.log
make[2]: *** [debian/rules2:1221: stamps/05-build-stamp] Error 1
make[2]: Leaving directory '/<>/gcc'
make[1]: *** [debian/rules:44: build-indep] Error 2
make[1]: Leaving directory '/<>/gcc'
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2
make: *** [debian/rules:397: stamp-dir/build-gcc.amd64] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


This is just how the build ends and probably meaningless, so I've put
all my build logs here:

https://people.debian.org/~sanvila/build-logs/gcc-8-cross/

The only unusual thing is that I'm using a single-CPU virtual machine
for the build, not a desktop computer, but I fail to see why that
would make any difference, as the only processor-related thing
I found is this in debian/rules:

NJOBS =
# Support parallel= in DEB_BUILD_OPTIONS (see #209008)
ifneq (,$(filter parallel=%,$(subst $(,), ,$(DEB_BUILD_OPTIONS
  NJOBS := -j $(subst parallel=,,$(filter parallel=%,$(subst 
$(,),$(space),$(DEB_BUILD_OPTIONS
endif

Bug#919141: marked as done (gcc-8-cross: please support binnmu)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 12:07:34 +
with message-id 
and subject line Bug#954831: Removed package(s) from unstable
has caused the Debian Bug report #919141,
regarding gcc-8-cross: please support binnmu
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.)


-- 
919141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gcc-8-cross
Version: 24

In this patch, I retrieve the version of current and
compose our local version from changelog.

Then compare these 2 versions, if local is not greater than the version in repo,
then $(error ...)

With this patch, we can support binnmu, or just edit changelog to rebuild.

-- 
YunQiang Su


gcc-8-cross-binnmu.diff
Description: Binary data
--- End Message ---
--- Begin Message ---
Version: 33+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#604453: marked as done (reproducible way to crash the system with kernel.function("*@*/*.c"))

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 12:44:31 +0100
with message-id <20200324114431.GA13762@ariel>
and subject line Re: #604453 reproducible way to crash the system with 
kernel.function("*@*/*.c")
has caused the Debian Bug report #604453,
regarding reproducible way to crash the system with kernel.function("*@*/*.c")
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.)


-- 
604453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-27
Severity: minor

[ Note that I have applied a patch from #602273 so this is not a
completely unmodified linux-2.6 package.]

Steps to reproduce:
1) cat > mmap-trace.stp <0?"->":"<-"),
  probefunc())
}

probe syscall.execve {
#  printf("%s\n", filename);
  if (filename != "./mmap") next
  trace[tid()] = 1
  trace(1)
}
#probe syscall.execve.return {
#   trace(-1)
#   delete trace[tid()]
#}
#probe kernel.function("*@mm/*.c").call { trace(1) }
#probe kernel.function("*@mm/*.c").return { trace(-1) }

probe kernel.function("*@*/*.c").call { trace(1) }
probe kernel.function("*@*/*.c").return { trace(-1) }

probe begin {
printf("begin\n");
}
EOF
2) sudo stap ./mmap-trace.stp

Expected results:
2) The system does not crash

Actual results:
2) The system hangs and does not respond to ping.

More info:
1) dmesg from a crasdump shows

[   15.529018] br0: no IPv6 routers present
[   15.669525] eth0: no IPv6 routers present
[  216.773795] stap_db2bea815fe5469cb8137996bcbc994c_6678582: systemtap: 
1.2/0.148, base: a012c000, memory: 
13010data/22text/64ctx/13net/377alloc kb, probes: 31451
[  216.774296] [ cut here ]
[  216.774312] WARNING: at 
/local/lindi/debian/linux-2.6-2.6.32/debian/build/source_amd64_none/arch/x86/kernel/kprobes.c:508
 kprobe_exceptions_notify+0x21d/0x5f8()
[  216.774324] Modules linked in: stap_db2bea815fe5469cb8137996bcbc994c_6678582 
binfmt_misc nfs lockd fscache nfs_acl auth_rpcgss sunrpc bridge stp fuse loop 
evdev pcspkr ext3 jbd mbcache dm_mod xen_netfront xen_blkfront
[  216.774368] Pid: 1936, comm: stapio Not tainted 2.6.32-5+lindi.5-amd64 #1
[  216.774375] Call Trace:
[  216.774382]  [] ? kprobe_exceptions_notify+0x21d/0x5f8
[  216.774389]  [] ? kprobe_exceptions_notify+0x21d/0x5f8
[  216.774398]  [] ? warn_slowpath_common+0x77/0xa3
[  216.774407]  [] ? check_events+0x12/0x20
[  216.774414]  [] ? kprobe_exceptions_notify+0x21d/0x5f8
[  216.774422]  [] ? notifier_call_chain+0x29/0x4c
[  216.774431]  [] ? notify_die+0x2d/0x32
[  216.774438]  [] ? do_int3+0x2f/0x98
[  216.774447]  [] ? xen_int3+0x1b/0x20
[  216.774454]  [] ? __raw_callee_save_xen_pgd_val+0x11/0x1e
[  216.774462]  [] ? xen_get_debugreg+0x1/0x9
[  216.774470]  [] ? do_debug+0x25/0x13e
[  216.774477]  [] ? xen_debug+0x1b/0x20
[  216.774484]  [] ? __raw_callee_save_xen_pgd_val+0x11/0x1e
[  216.774493]  [] ? xen_mc_entry+0x2e/0x33
[  216.774500]  [] ? xen_flush_tlb_single+0x19/0x6d
[  216.774508]  [] ? xen_set_pte+0x12/0x1b
[  216.774516]  [] ? set_pte_vaddr_pud+0x41/0x4b
[  216.774524]  [] ? __native_set_fixmap+0x24/0x2c
[  216.774532]  [] ? xen_set_fixmap+0x86/0xb5
[  216.774539]  [] ? __xen_mc_entry+0x0/0xb8
[  216.774546]  [] ? text_poke+0x13d/0x19b
[  216.774554]  [] ? arch_arm_kprobe+0x1c/0x21
[  216.774561]  [] ? register_kprobe+0x452/0x4ad
[  216.774569]  [] ? __xen_mc_entry+0x0/0xb8
[  216.774578]  [] ? _stp_ctl_write_cmd+0x770/0x84e 
[stap_db2bea815fe5469cb8137996bcbc994c_6678582]
[  216.774589]  [] ? vfs_write+0xa9/0x102
[  216.774596]  [] ? sys_write+0x45/0x6e
[  216.774604]  [] ? stub_clone+0x13/0x20
[  216.774611]  [] ? system_call_fastpath+0x16/0x1b
[  216.774617] ---[ end trace 6100392551b72adc ]---
[  216.774625] int3:  [#1] SMP 
[  216.774633] last sysfs file: /sys/module/xen_netfront/sections/__bug_table
[  216.774639] CPU 0 
[  216.774644] Modules linked in: stap_db2bea815fe5469cb8137996bcbc994c_6678582 
binfmt_misc nfs lockd fscache nfs_acl auth_rpcgss sunrpc bridge stp fuse loop 
evdev pcspkr ext3 jbd mbcache dm_mod xen_netfront xen_blkfront
[  216.774687] Pid: 1936, comm: stapio Tainted: GW  
2.6.32-5+lindi.5-amd64 #1 
[  216.774694] RIP: e030:[]  [] 
xen_get_debugreg+0x1/0x9
[  216.774704] RSP: e02b:88003778dc20  EFLAGS: 0086
[  216.774710] RAX: c570 RBX: 0001 RCX: 8101154e
[  216.774717] RDX: 8800020a RSI:  RDI: 0006
[  216.774724] RBP: 88003778dc68 R08: 0001 R09: 0040
[  216.774731] R10: 8100c157 R11: 

Bug#935199: marked as done (network-manager-openconnect: New upstream release 1.2.6 support protocol selector (newest Palo Alto and Juniper devices))

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 11:36:06 +
with message-id 
and subject line Bug#935199: fixed in network-manager-openconnect 1.2.6-1
has caused the Debian Bug report #935199,
regarding network-manager-openconnect: New upstream release 1.2.6 support 
protocol selector (newest Palo Alto and Juniper devices)
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.)


-- 
935199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager-openconnect
Version: 1.2.6-0~bpo10+1
Severity: wishlist
Tags: upstream

Hello maintainer,

Once bug http:/bugs.debian.org/935198 has been fixed, could you please update
to 1.2.6 ?
It's required to support latest Palo Alto and Juniper devices.

I built the package myself and I had to add "libgcr-3-dev" build dependency,
and of course built against openconnect 8.04.

Thanks in advance,

Adam.



-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages network-manager-openconnect depends on:
ii  adduser  3.118
ii  libc62.28-10
ii  libglib2.0-0 2.58.3-2
ii  libnm0   1.14.6-2
ii  libopenconnect5  8.04-0~bpo10+0
ii  network-manager  1.14.6-2
ii  openconnect  8.04-0~bpo10+0

network-manager-openconnect recommends no packages.

network-manager-openconnect suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: network-manager-openconnect
Source-Version: 1.2.6-1
Done: Luca Boccassi 

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

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated 
network-manager-openconnect package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Mar 2020 10:43:26 +
Source: network-manager-openconnect
Architecture: source
Version: 1.2.6-1
Distribution: unstable
Urgency: medium
Maintainer: Mike Miller 
Changed-By: Luca Boccassi 
Closes: 935199 953752
Changes:
 network-manager-openconnect (1.2.6-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Repository, Repository-Browse.
 .
   [ Luca Boccassi ]
   * Update upstream source from tag 'upstream/1.2.6'
 Closes: #935199, #953752
   * Drop patches directory, all merged in 1.2.6
   * Add Build-Depends on libgcr-3-dev, new requirement of 1.2.6
   * Drop --without-libnm-glib, removed upstream
   * Delete *.la files before dh_install runs
   * Set hardening=+all to enable BindNow
   * Add d/copyright entry for appdata file
   * Install metainfo in /usr/share/metainfo
   * Fix capitalization-error-in-description
   * Update package description to mention more protocols
   * Add Lintian overrides for executable-in-usr-lib
   * Add Lintian override for testsuite-autopkgtest-missing
Checksums-Sha1:
 be99d3a32dbc9e5cefbd4eac87b6f8bae7bc1030 1987 
network-manager-openconnect_1.2.6-1.dsc
 9ef08aa0692e92e9a15f420b2ef35735dd8c5b9f 713464 
network-manager-openconnect_1.2.6.orig.tar.xz
 1cddf2cf8b693ae99b8936b5f8f72f8bd3cd5391 6744 
network-manager-openconnect_1.2.6-1.debian.tar.xz
 6193f195401dbddac277e8cbd5d5d022fdf729ec 15780 
network-manager-openconnect_1.2.6-1_source.buildinfo
Checksums-Sha256:
 36a2d0048f7e5d2dbd6078ce40646ef0e54d8bf712c8e6560aa7eb465ed9909c 1987 
network-manager-openconnect_1.2.6-1.dsc
 95109803596a9782680a5dca3b51c4ad8ff7e126169d5431278cab694112975a 713464 
network-manager-openconnect_1.2.6.orig.tar.xz
 a877d18bb05417501ddbd71511f850878981b2c2d3b84642d15ced2884b8f265 6744 
network-manager-openconnect_1.2.6-1.debian.tar.xz
 07dad012a300c071ebe8cc8c4c6d7cb9c18bfe6d1bc8e515905ae214731cb2b1 15780 

Bug#953752: marked as done (Add Palo Alto Global Protect support to the GUI)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 11:36:06 +
with message-id 
and subject line Bug#953752: fixed in network-manager-openconnect 1.2.6-1
has caused the Debian Bug report #953752,
regarding Add Palo Alto Global Protect support to the GUI
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.)


-- 
953752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953752
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager-openconnect-gnome
Version: 1.2.4-2
Severity: wishlist

There is a patch out there for adding this already, but it would be nice to 
have the 
added functionality, since the openconnect currently in testing already 
supports GP
protocol.

https://gitlab.gnome.org/GNOME/NetworkManager-openconnect/merge_requests/6

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

Kernel: Linux 4.19.0-2-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.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 network-manager-openconnect-gnome depends on:
ii  libatk1.0-0  2.30.0-2
ii  libc62.28-8
ii  libcairo-gobject21.16.0-3
ii  libcairo21.16.0-3
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-1
ii  libgtk-3-0   3.24.5-1
ii  libnm0   1.14.6-2
ii  libopenconnect5  8.02-1
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libsecret-1-00.18.7-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  network-manager-openconnect  1.2.4-2

network-manager-openconnect-gnome recommends no packages.

network-manager-openconnect-gnome suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: network-manager-openconnect
Source-Version: 1.2.6-1
Done: Luca Boccassi 

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

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated 
network-manager-openconnect package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Mar 2020 10:43:26 +
Source: network-manager-openconnect
Architecture: source
Version: 1.2.6-1
Distribution: unstable
Urgency: medium
Maintainer: Mike Miller 
Changed-By: Luca Boccassi 
Closes: 935199 953752
Changes:
 network-manager-openconnect (1.2.6-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Repository, Repository-Browse.
 .
   [ Luca Boccassi ]
   * Update upstream source from tag 'upstream/1.2.6'
 Closes: #935199, #953752
   * Drop patches directory, all merged in 1.2.6
   * Add Build-Depends on libgcr-3-dev, new requirement of 1.2.6
   * Drop --without-libnm-glib, removed upstream
   * Delete *.la files before dh_install runs
   * Set hardening=+all to enable BindNow
   * Add d/copyright entry for appdata file
   * Install metainfo in /usr/share/metainfo
   * Fix capitalization-error-in-description
   * Update package description to mention more protocols
   * Add Lintian overrides for executable-in-usr-lib
   * Add Lintian override for testsuite-autopkgtest-missing
Checksums-Sha1:
 be99d3a32dbc9e5cefbd4eac87b6f8bae7bc1030 1987 
network-manager-openconnect_1.2.6-1.dsc
 9ef08aa0692e92e9a15f420b2ef35735dd8c5b9f 713464 
network-manager-openconnect_1.2.6.orig.tar.xz
 1cddf2cf8b693ae99b8936b5f8f72f8bd3cd5391 6744 
network-manager-openconnect_1.2.6-1.debian.tar.xz
 6193f195401dbddac277e8cbd5d5d022fdf729ec 15780 
network-manager-openconnect_1.2.6-1_source.buildinfo
Checksums-Sha256:
 36a2d0048f7e5d2dbd6078ce40646ef0e54d8bf712c8e6560aa7eb465ed9909c 1987