Bug#970259: Weather API update

[Pavel R.]

Hello, I've fixed the plugin by bumping weather API version to 2.0

Patch is attached

--- xfce4-weather-plugin-0.8.10.orig/panel-plugin/weather.c
+++ xfce4-weather-plugin-0.8.10/panel-plugin/weather.c
@@ -619,17 +619,14 @@ update_handler(plugin_data *data)
 end_tm = *localtime(_t);
 
 /* build url */
-url = g_strdup_printf("https://api.met.no/weatherapi/sunrise/1.1/?;
+url = g_strdup_printf("https://api.met.no/weatherapi/sunrise/2.0/?;
   "lat=%s;lon=%s;"
-  "from=%04d-%02d-%02d;"
-  "to=%04d-%02d-%02d",
+  "date=%04d-%02d-%02d;"
+  "offset=00:00",
   data->lat, data->lon,
   now_tm.tm_year + 1900,
-  now_tm.tm_mon + 1,
-  now_tm.tm_mday,
-  end_tm.tm_year + 1900,
-  end_tm.tm_mon + 1,
-  end_tm.tm_mday);
+  now_tm.tm_mon + 1, 
+  now_tm.tm_mday);
 
 /* start receive thread */
 g_message(_("getting %s"), url);
@@ -647,8 +644,8 @@ update_handler(plugin_data *data)
 /* build url */
 url =
 g_strdup_printf("https://api.met.no/weatherapi;
-"/locationforecastlts/1.3/?lat=%s;lon=%s;msl=%d",
-data->lat, data->lon, data->msl);
+"/locationforecast/2.0/classic?lat=%s;lon=%s",
+data->lat, data->lon);
 
 /* start receive thread */
 g_message(_("getting %s"), url);

Bug#969835: iwatch: autopkgtest should be marked superficial

[Eriberto Mota]

Please, can you explain why this bug is marked as serious?

Regards,

Eriberto

Bug#969355: marked as done (cups-browsed.service Hangs on Shutdown)

[Debian Bug Tracking System]

Your message dated Tue, 15 Sep 2020 22:38:17 -0400
with message-id 
and subject line Re: cups-browsed.service Hangs on Shutdown
has caused the Debian Bug report #969355,
regarding cups-browsed.service Hangs on Shutdown
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.)


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

Recently, my system has taken a while to shut down. From the log, it
looks like cups-browsed is taking the maximum 90 seconds to try and
stop/sigterm (and still fails, resulting in sigkill).

Aug 29 14:39:41 hostname avahi-daemon[648]: Disconnected from D-Bus,
exiting.
Aug 29 14:41:09 hostname systemd[1]: cups-browsed.service: State
'stop-sigterm' timed out. Killing.
Aug 29 14:41:09 hostname systemd[1]: cups-browsed.service: Main process
exited, code=killed, status=9/KILL

This began earlier this week, probably upon upgrade to
cups-filters/browsed 1.28.x
Another Debian sid user confirmed the issue occurs for them.

If there is more information I can provide, let me know. Thanks.

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

Kernel: Linux 5.7.16-towo.1-siduction-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cups-browsed depends on:
ii  cups-daemon  2.3.3-2
ii  init-system-helpers  1.58
ii  libavahi-client3 0.8-3
ii  libavahi-common3 0.8-3
ii  libavahi-glib1   0.8-3
ii  libc6    2.31-3
ii  libcups2 2.3.3-2
ii  libcupsfilters1  1.28.1-1
ii  libglib2.0-0 2.64.4-1
ii  libldap-2.4-2    2.4.51+dfsg-1
ii  lsb-base 11.1.0

Versions of packages cups-browsed recommends:
ii  avahi-daemon  0.8-3

cups-browsed suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.28.2-1

I believe the bug has been fixed in 1.28.2-1. I have shut down a few
times since updating to that version, and have not been able to
reproduce the hang. I am guessing I was experiencing this upstream bug:
https://github.com/OpenPrinting/cups-filters/issues/298

Thank You.--- End Message ---

Bug#969795: marked as done (2vcard: autopkgtest should be marked superficial)

[Debian Bug Tracking System]

Your message dated Wed, 16 Sep 2020 02:33:27 +
with message-id 
and subject line Bug#969795: fixed in 2vcard 0.6-4
has caused the Debian Bug report #969795,
regarding 2vcard: autopkgtest should be marked superficial
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.)


-- 
969795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: 2vcard
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of '2vcard' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'2vcard'.

--

Sudip 
--- End Message ---
--- Begin Message ---
Source: 2vcard
Source-Version: 0.6-4
Done: Fabio Augusto De Muzio Tobich 

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

Debian distribution maintenance software
pp.
Fabio Augusto De Muzio Tobich  (supplier of updated 2vcard 
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, 15 Sep 2020 21:43:52 -0300
Source: 2vcard
Architecture: source
Version: 0.6-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Fabio Augusto De Muzio Tobich 
Closes: 969795
Changes:
 2vcard (0.6-4) unstable; urgency=medium
 .
   * QA upload.
   * debian/control: bumped 'debhelper-compat' in Build-Depends field to 13.
   * debian/copyright:
   - Added myself in packaging block.
   - Added Upstream-Contact field.
   * debian/tests/control: test marked as superficial. (Closes: #969795)
Checksums-Sha1:
 cb0dd81512bf7c21361eac023d5e5f546b5751ac 1818 2vcard_0.6-4.dsc
 252caae730212981a2b27d36d98b30ce502f14c5 4872 2vcard_0.6-4.debian.tar.xz
 7dfcb24a32368f891155aa2a71de2213e830d2c0 5189 2vcard_0.6-4_source.buildinfo
Checksums-Sha256:
 38b0f9f30555f69866556fa6a41856221d626497546514890d105827aeef0a22 1818 
2vcard_0.6-4.dsc
 cbde9c06eecbd77191a403f4d647ccf2ee683654c7e45b70bceafebeb51ab105 4872 
2vcard_0.6-4.debian.tar.xz
 67ba60b32c6dcfd86da5de92114a650fba915302924cdc35300b45bdf81e9d7d 5189 
2vcard_0.6-4_source.buildinfo
Files:
 4fda81a32e57346b6012c3cb9576d522 1818 utils optional 2vcard_0.6-4.dsc
 9e94267758f2dd936baa63805e3e1b0f 4872 utils optional 2vcard_0.6-4.debian.tar.xz
 e2b2d81194895ad59fcfdebbbe4a364f 5189 utils optional 
2vcard_0.6-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEHTjuPGJPlVzh+jyFWjA1kfjNsIsFAl9hcbgACgkQWjA1kfjN
sItM2w//VebiQR2x3p+gDwDuaOAMJeib2gZJzsLKk3hBKszSTVSn5PRKLFzFyvBe
honfB4ESl2GQ8GIOC3nRQUKk1cEZZGlJxNsfVkrGPDgsrHE8P5JaRjjD8bGdFIKA
VC/+4fNQ7/WEDl6U4mn6OBQTEN0tDg3J5mREUJleWSw3v2lctiBtVmujQdnq6Ofm
CO5dbYhxsGVHyPAX8A0x4N/8nJYsq81ZOW/ODKjn9ENbeGXf4eMXaKob8lfudBt4
ePcVtpNLyIIJB9RKGLLedU+2vqkg0IS7jHw14VRL+rYoM22x8Dnguv7i7PyDkYue
rItD0ZtPuLrCgOui7Pe5Z8TrSwY2M3NeTvXalu3r85+Uz+iQ43SlFp8tJOAYX4sx
H7YqX0DWQ9Fu+BldO888vh8zIzdbStBI/hfnI8QZFts83mYg1jCp55QXck6C4PJK
+sFp/0gJskuaC+94CafBtsYW965LUvLk07FmMso3M1gvbgFBmee3wmQFWPGc1WYw
BCaLS7qTM1HB6YcmIECFmbvn6fHkjlptVRthX6+bz+7uKtPhE78O9RBO8WUDVIoj
rF8jqnAS5Tx31u4kaguuvbpDMu7u9AX9imEHxPIKJKv2krUMKvgrSoU80v3a6I7L
W7ZJRm1XbUCrYtF5wfYKHHKXEWNzUdDywGQpivkLDh3Deo64s7Y=
=WU7j
-END PGP SIGNATURE End Message ---

Bug#970420: python: Unmet dependencies when installing python package

[Koutheir Attouchi]

Package: python
Version: 2.7.17-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: kouth...@gmail.com

Dear Maintainer,

What led up to the situation?

```
$ sudo apt-get install python
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 python : PreDepends: python-minimal (= 2.7.17-2) but it is not going to be
installed
  Depends: libpython-stdlib (= 2.7.17-2) but it is not going to be
installed
  Depends: python2 (= 2.7.17-2) but 2.7.18-2 is to be installed
E: Unable to correct problems, you have held broken packages.
```

In order to keep other python packages, I marked the `python2` and `python3`
packages as manually installed.



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

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

Versions of packages python depends on:
pn  libpython-stdlib  
pn  python-minimal
ii  python2   2.7.18-2
ii  python2.7 2.7.18-1

python recommends no packages.

Versions of packages python suggests:
pn  python-doc  
ii  python-tk   2.7.18-1

Bug#970419: lilyterm: No longer starts (likely related to VTE changes)

[James Tocknell]

Package: lilyterm
Version: 0.9.9.4+git20150208.f600c0-5
Severity: grave
Justification: renders package unusable

It appears that lilyterm is unable to start, running lilyterm gives the
following errors:

** Message: 11:20:26.198: Can NOT connect to a existing lilyterm socket!

(lilyterm:4801): Gtk-WARNING **: 11:20:26.267: Theme parsing error: 
:2:32: The style property GtkWidget:focus-line-width is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4801): Gtk-WARNING **: 11:20:26.267: Theme parsing error: 
:3:29: The style property GtkWidget:focus-padding is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4801): Gtk-WARNING **: 11:20:26.267: Theme parsing error: 
:2:32: The style property GtkWidget:focus-line-width is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4801): Gtk-WARNING **: 11:20:26.267: Theme parsing error: 
:3:29: The style property GtkWidget:focus-padding is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4801): VTE-CRITICAL **: 11:20:26.268: gboolean 
vte_terminal_spawn_sync(VteTerminal*, VtePtyFlags, const char*, char**, char**, 
GSpawnFlags, GSpawnChildSetupFunc, gpointer, GPid*, GCancellable*, GError**): 
assertion 'envv == nullptr ||_vte_pty_check_envv(envv)' failed

(lilyterm:4801): Gtk-WARNING **: 11:20:26.268: Theme parsing error: 
:2:32: The style property GtkWidget:focus-line-width is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4801): Gtk-WARNING **: 11:20:26.268: Theme parsing error: 
:3:29: The style property GtkWidget:focus-padding is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4801): Gtk-WARNING **: 11:20:26.268: Theme parsing error: 
:2:32: The style property GtkWidget:focus-line-width is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4801): Gtk-WARNING **: 11:20:26.268: Theme parsing error: 
:3:29: The style property GtkWidget:focus-padding is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4801): VTE-CRITICAL **: 11:20:26.268: void 
vte_terminal_match_set_cursor_type(VteTerminal*, int, GdkCursorType): assertion 
'tag >= 0' failed

(lilyterm:4801): VTE-CRITICAL **: 11:20:26.268: void 
vte_terminal_match_set_cursor_type(VteTerminal*, int, GdkCursorType): assertion 
'tag >= 0' failed

(lilyterm:4801): VTE-CRITICAL **: 11:20:26.269: void 
vte_terminal_match_set_cursor_type(VteTerminal*, int, GdkCursorType): assertion 
'tag >= 0' failed

(lilyterm:4801): VTE-CRITICAL **: 11:20:26.269: void 
vte_terminal_match_set_cursor_type(VteTerminal*, int, GdkCursorType): assertion 
'tag >= 0' failed

and running lilyterm with -s gives:

(lilyterm:4807): Gtk-WARNING **: 11:20:57.451: Theme parsing error: 
:2:32: The style property GtkWidget:focus-line-width is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4807): Gtk-WARNING **: 11:20:57.451: Theme parsing error: 
:3:29: The style property GtkWidget:focus-padding is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4807): Gtk-WARNING **: 11:20:57.452: Theme parsing error: 
:2:32: The style property GtkWidget:focus-line-width is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4807): Gtk-WARNING **: 11:20:57.452: Theme parsing error: 
:3:29: The style property GtkWidget:focus-padding is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4807): VTE-CRITICAL **: 11:20:57.453: gboolean 
vte_terminal_spawn_sync(VteTerminal*, VtePtyFlags, const char*, char**, char**, 
GSpawnFlags, GSpawnChildSetupFunc, gpointer, GPid*, GCancellable*, GError**): 
assertion 'envv == nullptr ||_vte_pty_check_envv(envv)' failed

(lilyterm:4807): Gtk-WARNING **: 11:20:57.453: Theme parsing error: 
:2:32: The style property GtkWidget:focus-line-width is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4807): Gtk-WARNING **: 11:20:57.453: Theme parsing error: 
:3:29: The style property GtkWidget:focus-padding is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4807): Gtk-WARNING **: 11:20:57.454: Theme parsing error: 
:2:32: The style property GtkWidget:focus-line-width is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4807): Gtk-WARNING **: 11:20:57.454: Theme parsing error: 
:3:29: The style property GtkWidget:focus-padding is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lilyterm:4807): VTE-CRITICAL **: 11:20:57.454: void 
vte_terminal_match_set_cursor_type(VteTerminal*, int, GdkCursorType): assertion 
'tag >= 0' failed

(lilyterm:4807): VTE-CRITICAL **: 

Bug#968630: marked as done (html5lib: autopkgtest regression: 995 failed)

[Debian Bug Tracking System]

Your message dated Wed, 16 Sep 2020 01:18:26 +
with message-id 
and subject line Bug#968630: fixed in html5lib 1.1-2
has caused the Debian Bug report #968630,
regarding html5lib: autopkgtest regression: 995 failed
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.)


-- 
968630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: html5lib
Version: 1.1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of html5lib the autopkgtest of html5lib fails in
testing when that autopkgtest is run with the binary packages of
html5lib from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
html5lib   from testing1.1-1
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=html5lib

https://ci.debian.net/data/autopkgtest/testing/amd64/h/html5lib/6324026/log.gz

tests/tree_construction.py:121: in runtest
assert expected == output, errorMsg
E   AssertionError:
E
E   Input:
E   1document.write("2")3
E
E   Expected:
E   
E 
E 
E   "1"
E   
E "document.write("2")"
E   "23"
E
E   Received:
E   
E 
E 
E   "1"
E   
E "document.write("2")"
E   "3"




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: html5lib
Source-Version: 1.1-2
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated html5lib 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, 15 Sep 2020 20:59:33 -0400
Source: html5lib
Architecture: source
Version: 1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 968630 970162
Changes:
 html5lib (1.1-2) unstable; urgency=medium
 .
   * debian/tests/unittests3
 - fix autopkgtests by also copying .pytest.expect, and rework the tests
   location; Closes: #968630
   * debian/control
 - remove Barry from Uploaders, thanks for your contributions;
   Closes: #970162
 - set me as Maintainer, team as Uploaders
Checksums-Sha1:
 16f360c263542b729a21ffe898d1fa73c41fbfa2 2296 html5lib_1.1-2.dsc
 cfc981b2fcdaa2ef0551ea673fe0cafc399f606e 5180 html5lib_1.1-2.debian.tar.xz
 8b8ea4935fa014aed32421e8b56fe87fc82379c2 6972 html5lib_1.1-2_source.buildinfo
Checksums-Sha256:
 0b8429cd95bfd816763763746e042b4bc428c56328c5ce52157fd1821dc58dff 2296 
html5lib_1.1-2.dsc
 b4428f3faf7c55bd91a8d2c6b8c4e993255f92f9eb5dad348ee108013230 5180 
html5lib_1.1-2.debian.tar.xz
 1c3887f0a44e6bd2919ef938f58924299c9ffa0379989073f59de091ee3a8cd1 6972 
html5lib_1.1-2_source.buildinfo
Files:
 8c5f984cc1114fb20a3374751885c0de 2296 python optional html5lib_1.1-2.dsc
 cba8ab60a4c5fa3af02e73616c90402b 5180 python optional 
html5lib_1.1-2.debian.tar.xz
 f723a9460da84e7df3e45fe7fa6a34dd 6972 python optional 
html5lib_1.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl9hY4cACgkQh588mTgB
qU958RAAsPopiuZoQEh5dUa62SGluS/HLWyC98duUy9GReBcr+b1REk/h7klq5TG
cyltzwZXYjxYfA/B6rLQHhOu6rkL6rBopnPYE/tDnH7I9jxycedaVVTwDqoPsn5t
5zEuURHII4auGQhNznv2pu5TPiDvCaXE0eX9f1mk5U+3oYBHB5WqWWVABsL1KixM
esEae9/T+9W6muxqjz7jrLf+SouxloS4OrQA9/PCMRx9UfjJcWgcdL7KT4LfghOP
GPT5aTslLUuMRWUCjSTB+7LZ9WUTB0XKndr2Dc8iD6P/KBIXvTVRttvoqNvryH9L
GdODa6Fd6NoHfbhH5t5d3uLB+iGre0yCxWlpRUjZxK8JFY34PAkXbZ7fp36SBld0

Processed: Bug#968630 marked as pending in html5lib

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #968630 [src:html5lib] html5lib: autopkgtest regression: 995 failed
Added tag(s) pending.

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

Bug#968630: marked as pending in html5lib

[Sandro Tosi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/html5lib/-/commit/4c8095c057239f560740339874b6e106a69423a7


fix autopkgtests by also copying .pytest.expect, and rework the tests location; 
Closes: #968630


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/968630

Bug#969608: [Debian-med-packaging] Bug#969608: makeblastdb 2.10.x on 32-bit architectures

[Aaron M. Ucko]

Étienne Mollier  writes:

> Wow, thanks for the comprehensive background information.  In

No problem.

> case someone else (me in a not so near future for instance)
> stumbles upon this again, I keep note that reducing the size of
> BLASTDB_LMDB_MAP_SIZE a bit might help:

One final clarification: This variable is an override, not a cap, so any
unconditional settings thereof should be low enough to work on 32-bit
systems.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#970417: bind-host: missing 'host' binary

[Eldon Koyle]

Package: bind-host
Version: 1:9.13.3-1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The `bind-host` package in experimental is missing both the executable
and the manpage.

esk@esk-xps:~$ dpkg -L bind-host
/.
/usr
/usr/bin
/usr/share
/usr/share/doc
/usr/share/doc/bind-host
/usr/share/doc/bind-host/changelog.Debian.amd64.gz
/usr/share/doc/bind-host/changelog.Debian.gz
/usr/share/doc/bind-host/changelog.gz
/usr/share/doc/bind-host/copyright
/usr/share/man
/usr/share/man/man1
esk@esk-xps:~$

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

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

Versions of packages bind-host depends on:
ii  bind-libs  1:9.13.3-1+b1
ii  libc6  2.31-1
ii  libidn2-0  2.3.0-1
ii  libssl1.1  1.1.1g-1

bind-host recommends no packages.

bind-host suggests no packages.

-- debconf-show failed

-- 
Eldon Koyle

Bug#936724: closing 936724

[Unit 193]

close 936724 3.0.0-1
thanks

This bug was fixed in 3.0.0 when it was ported to python 3.  Changes below:

Changes:
 ifupdown2 (3.0.0-1) unstable; urgency=medium
 .
* New: python3 support
* New: attribute alias support
* New: bridge-always-up attribute
* New: set bridge mtu with policy default
* New: ES bond with "es-sys-mac" attribute
* New: vxlan attribute: vxlan-mcastgrp-map
* New: support for "veth-peer-name" attribute
* New: dhcp policy: dhclient_retry_on_failure
* New: support for marking interfaces as mgmt interfaces
* New: bridge-vlan-vni-map attribute (single vxlan device)
* New: dhcp: skipping dhcp configuration if link-down yes
* New: vrf-slave: keep vlan down if lower device has "link-down yes"
* New: vxlan: support for vxlan-svcnodeip6 and vxlan-mcastgrp6 (fixes #43)
* New: support for add ovs-ports-condone-regex attribute (openvswitch)
* Fix: dry-run exceptions
* Fix: bond enslavement ordering
* Fix: process MTU before addrgen
* Fix: set bridge MTU after bridge creation
* Fix: ifquery-running: incorrect displayed data
* Fix: tunnel configuration compatibility with ifupdown1
* Fix: start-networking script is back to handle mgmt & hotplug cases
* Fix: devices matching with ".{0,13}\-v" could get removed by ifreload
* Fix: mstpctl: check mstpctl-stp and bridge-stp and fix bridge cache update
* Removing python-argcomplete dependency


~Unit 193
Unit193 @ freenode
Unit193 @ OFTC

Processed: closing 967953

[Debian Bug Tracking System]

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

> close 967953 3.0.0-1
Bug #967953 [ifupdown2] Package not installable in sid due to missing 
dependencies python-argcomplete and python-ipaddr
Marked as fixed in versions ifupdown2/3.0.0-1.
Bug #967953 [ifupdown2] Package not installable in sid due to missing 
dependencies python-argcomplete and python-ipaddr
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 927134

[Debian Bug Tracking System]

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

> close 927134 3.0.0-1
Bug #927134 [src:ifupdown2] src:ifupdown2: Please port to python3
Marked as fixed in versions ifupdown2/3.0.0-1.
Bug #927134 [src:ifupdown2] src:ifupdown2: Please port to python3
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 936724

[Debian Bug Tracking System]

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

> close 936724 3.0.0-1
Bug #936724 [src:ifupdown2] ifupdown2: Python2 removal in sid/bullseye
Marked as fixed in versions ifupdown2/3.0.0-1.
Bug #936724 [src:ifupdown2] ifupdown2: Python2 removal in sid/bullseye
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#927134: closing 927134

[Unit 193]

close 927134 3.0.0-1
thanks

This bug was fixed in 3.0.0 when it was ported to python 3.  Changes below:

Changes:
 ifupdown2 (3.0.0-1) unstable; urgency=medium
 .
* New: python3 support
* New: attribute alias support
* New: bridge-always-up attribute
* New: set bridge mtu with policy default
* New: ES bond with "es-sys-mac" attribute
* New: vxlan attribute: vxlan-mcastgrp-map
* New: support for "veth-peer-name" attribute
* New: dhcp policy: dhclient_retry_on_failure
* New: support for marking interfaces as mgmt interfaces
* New: bridge-vlan-vni-map attribute (single vxlan device)
* New: dhcp: skipping dhcp configuration if link-down yes
* New: vrf-slave: keep vlan down if lower device has "link-down yes"
* New: vxlan: support for vxlan-svcnodeip6 and vxlan-mcastgrp6 (fixes #43)
* New: support for add ovs-ports-condone-regex attribute (openvswitch)
* Fix: dry-run exceptions
* Fix: bond enslavement ordering
* Fix: process MTU before addrgen
* Fix: set bridge MTU after bridge creation
* Fix: ifquery-running: incorrect displayed data
* Fix: tunnel configuration compatibility with ifupdown1
* Fix: start-networking script is back to handle mgmt & hotplug cases
* Fix: devices matching with ".{0,13}\-v" could get removed by ifreload
* Fix: mstpctl: check mstpctl-stp and bridge-stp and fix bridge cache update
* Removing python-argcomplete dependency


~Unit 193
Unit193 @ freenode
Unit193 @ OFTC

Bug#967953: closing 967953

[Unit 193]

close 967953 3.0.0-1
thanks

This bug was fixed in 3.0.0 when it was ported to python 3.  Changes below:

Changes:
 ifupdown2 (3.0.0-1) unstable; urgency=medium
 .
* New: python3 support
* New: attribute alias support
* New: bridge-always-up attribute
* New: set bridge mtu with policy default
* New: ES bond with "es-sys-mac" attribute
* New: vxlan attribute: vxlan-mcastgrp-map
* New: support for "veth-peer-name" attribute
* New: dhcp policy: dhclient_retry_on_failure
* New: support for marking interfaces as mgmt interfaces
* New: bridge-vlan-vni-map attribute (single vxlan device)
* New: dhcp: skipping dhcp configuration if link-down yes
* New: vrf-slave: keep vlan down if lower device has "link-down yes"
* New: vxlan: support for vxlan-svcnodeip6 and vxlan-mcastgrp6 (fixes #43)
* New: support for add ovs-ports-condone-regex attribute (openvswitch)
* Fix: dry-run exceptions
* Fix: bond enslavement ordering
* Fix: process MTU before addrgen
* Fix: set bridge MTU after bridge creation
* Fix: ifquery-running: incorrect displayed data
* Fix: tunnel configuration compatibility with ifupdown1
* Fix: start-networking script is back to handle mgmt & hotplug cases
* Fix: devices matching with ".{0,13}\-v" could get removed by ifreload
* Fix: mstpctl: check mstpctl-stp and bridge-stp and fix bridge cache update
* Removing python-argcomplete dependency


~Unit 193
Unit193 @ freenode
Unit193 @ OFTC

Bug#967909: Update to recent fork of editline?

[Bastian Germann]

Am 15.09.20 um 22:22 schrieb Joel Rivera:
> Bastian,
> 
> correct me if I'm wrong, but you're suggesting to remove [1] in favor of [2]?

That is right.

> I've been trying to update editline to the fork that seems to have been 
> evolved from the original debian sources at [3]. My interest in particular is 
> due to that is a dependency of the Nix package manager [4],  currently the 
> debian package of Nix is trying to work around the situation by adding 
> support to readline (but is not complete and it seems that the upstream 
> project is considering to stop/revert the integration with it). 
> 
> You can get the additional context from the emails that I sent to 
> debian-mentors like a month ago [5],  and the other one to debian-devel [6], 
> the maintainer (Sam Hocevar) seems to be on vacation or simply is not 
> responsive. I'm starting to consider to salvage the package, but that idea 
> conflicts with the current proposal of this bug report.

If you salvage this package, just close this bug.

> Currently a debian source package of the updated editline is part of the 
> upsteam repo [7]  (based on the original one in debian sources), so is mostly 
> a matter to be integrated in debian. 
> 
> Do you have any opinions this situation? I do not know more about libedit and 
> compatibility with the newer editline, I'm only trying to integrate the 
> dependency that the upstream project (Nix) seems to favor the most. 

Most libedit/editline implementations floating around, including the two
mentioned ones stem from the original version from Rich Salz.

Therefore, nix might be able to compile with libedit instead. The main
difference from [3] is that it needs ncurses. Additionally, the include
paths differ. libedit seems to try to be a bit more of a readline
drop-in replacement..

The current situation in Debian is the following: We have at least four
readline-like implementations in the archive:

readline (v8)
readline5 which is kept around for license reasons
editline
libedit

I think it would be good to reduce the number of those libraries and
apart from the effort to remove editline, I also handed in patches to
the readline5 users to build with libedit.

The main reason to get rid of editline and readline5 is their orphaned
status. But if you want to maintain the package properly after
salvaging, please go ahead.

> Thanks,
> --
> Joel Rivera
> 
> [1]: https://tracker.debian.org/pkg/editline
> [2]: https://tracker.debian.org/pkg/libedit
> [3]: https://github.com/troglobit/editline
> [4]: https://tracker.debian.org/pkg/nix
> [5]: https://lists.debian.org/debian-mentors/2020/08/msg00096.html
> [6]: https://lists.debian.org/debian-devel/2020/08/msg00187.html
> [7]: https://github.com/troglobit/editline/tree/master/debian
> 

Bug#970390: marked as done (nvidia-graphics-drivers-legacy-390xx 390.138-3 is not available for i386)

[Debian Bug Tracking System]

Your message dated Tue, 15 Sep 2020 22:48:29 +
with message-id 
and subject line Bug#970390: fixed in nvidia-graphics-drivers-legacy-390xx 
390.138-4
has caused the Debian Bug report #970390,
regarding nvidia-graphics-drivers-legacy-390xx 390.138-3 is not available for 
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.)


-- 
970390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers-legacy-390xx
Version: 390.138-1
Severity: serious

nvidia-graphics-drivers-legacy-390xx 390.138-3 is not available
for i386, so that it cannot even be installed on amd64 with i386
as a foreign architecture.

According to

  
https://buildd.debian.org/status/package.php?p=nvidia-graphics-drivers-legacy-390xx

there seems to be an issue with the patch fixing bug 969889:

Applying patch disable-module-nvidia-uvm.patch
patching file Makefile
Hunk #1 FAILED at 60.
1 out of 1 hunk FAILED -- rejects in file Makefile
Patch disable-module-nvidia-uvm.patch does not apply (enforce with -f)
make[1]: *** [debian/rules:256: kernel-source-tree] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:172: binary-arch] Error 2

armhf is affected too.

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

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

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-legacy-390xx
Source-Version: 390.138-4
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers-legacy-390xx, 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 970...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-legacy-390xx 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, 16 Sep 2020 00:22:38 +0200
Source: nvidia-graphics-drivers-legacy-390xx
Architecture: source
Version: 390.138-4
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 970390
Changes:
 nvidia-graphics-drivers-legacy-390xx (390.138-4) unstable; urgency=medium
 .
   * Do not break non-uvm architectures when disabling the uvm module.
 (Closes: #970390)
Checksums-Sha1:
 93a4f8b3eb0b9f32e52f76661c8214d10ec0 7595 
nvidia-graphics-drivers-legacy-390xx_390.138-4.dsc
 20c3a2f85530c60ee7df092113c2f894eb4b7d53 99188 
nvidia-graphics-drivers-legacy-390xx_390.138-4.debian.tar.xz
 8a8c50c4296e2e75f622bec9578b5546a5d68aa8 7557 
nvidia-graphics-drivers-legacy-390xx_390.138-4_source.buildinfo
Checksums-Sha256:
 52725b6ae944471e6c487e71393ad91298066aca9654b030873d8d38555a609a 7595 
nvidia-graphics-drivers-legacy-390xx_390.138-4.dsc
 8927043a49f1c48e3eaf9fa8211049b013c916fbcef9655ed390465f80efc1b5 99188 
nvidia-graphics-drivers-legacy-390xx_390.138-4.debian.tar.xz
 6f2aa85901cc62ee150576239ea10551b8727bb392a668c1aab954bb20947f77 7557 
nvidia-graphics-drivers-legacy-390xx_390.138-4_source.buildinfo
Files:
 e76574853f9bd1e0950ee5c149a47d8f 7595 non-free/libs optional 
nvidia-graphics-drivers-legacy-390xx_390.138-4.dsc
 73c23ee7e486c4e4a78f55dd4c7f6875 99188 non-free/libs optional 
nvidia-graphics-drivers-legacy-390xx_390.138-4.debian.tar.xz
 c04cda7f2590a186d532b28094ccb742 7557 non-free/libs optional 
nvidia-graphics-drivers-legacy-390xx_390.138-4_source.buildinfo

-BEGIN PGP SIGNATURE-

Processed: ca-certificates: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

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

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

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

Bug#951388: [akonadi-backend-postgresql] apparmor profile unsuitable

[Sandro Knauß]

Forwarded: https://invent.kde.org/pim/akonadi/-/merge_requests/32

Hey,

I have pushed the needed changes to upstream. The AppArmor profile is living 
there.

hefee

--
On Samstag, 15. Februar 2020 21:08:15 CEST Bastien Roucariès wrote:
> Package: akonadi-backend-postgresql
> Version: 4:19.08.3-1
> Severity: grave
> Justification: renders package unusable
> Tags: patch
> 
> Dear Maintainer,
> 
> Please find the following update for apparmor
> 
> Please apply
> 
> Bastien



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

Bug#970415: aseba build-depends unsatisfiable in testing and unstable.

[peter green]

Source: aseba
Version: 1.6.0-5
Severity: serious
Tags: bullseye, sid

aseba build-depends on the "python" binary package which is no longer built by the 
"python-defaults" source package.
In unstable it is present as a cruft package but said cruft package is 
uninstallable due to strictly versioned depdencies.
In testing it is gone completely. Either way your build-dependencies are 
unsatisfiable.

If you *really* need to stick with python2, you can build-depend on python2 
instead and fix any python invocations to
invoke that instead of the unversioned python. Ideally though you should be 
moving to python 3.

Bug#969663: polyphone is marked for autoremoval from testing

[Thorsten Glaser]

Felix Lechner dixit:

>Uploaded, although I am still looking for it on the buildds:

First it must be ACCEPTED, then the dak run for incoming must
run, then B-Ds are checked, then it gets into Needs-Build status,
and only then the buildds pick it up.

It’s there now: https://buildd.debian.org/status/package.php?p=wolfssl
(ports will pick it up in a bit)

bye,
//mirabilos
-- 
„Cool, /usr/share/doc/mksh/examples/uhr.gz ist ja ein Grund,
mksh auf jedem System zu installieren.“
-- XTaran auf der OpenRheinRuhr, ganz begeistert
(EN: “[…]uhr.gz is a reason to install mksh on every system.”)

Bug#969663: polyphone is marked for autoremoval from testing

[Thorsten Glaser]

Dixi quod…

>It’s there now: https://buildd.debian.org/status/package.php?p=wolfssl

… and already FTBFSing on s390x:

/usr/bin/ld: src/.libs/libwolfssl.so: undefined reference to `ByteReverseWords'

bye,
//mirabilos
-- 
[16:04:33] bkix: "veni vidi violini"
[16:04:45] bkix: "ich kam, sah und vergeigte"...

Bug#969663: polyphone is marked for autoremoval from testing

[Felix Lechner]

Hi Thorsten,

Uploaded, although I am still looking for it on the buildds:

> wolfssl_4.5.0+dfsg-1_source.changes uploaded successfully to localhost
> along with the files:
>   wolfssl_4.5.0+dfsg-1.dsc
>   wolfssl_4.5.0+dfsg.orig.tar.xz
>   wolfssl_4.5.0+dfsg-1.debian.tar.xz
>   wolfssl_4.5.0+dfsg-1_source.buildinfo
>
> Greetings,
>
> Your Debian queue daemon (running on host usper.debian.org)

Kind regards
Felix Lechner

Bug#969663: marked as done (wolfssl: CVE-2020-12457 CVE-2020-15309 CVE-2020-24585 CVE-2020-24613)

[Debian Bug Tracking System]

Your message dated Tue, 15 Sep 2020 20:48:59 +
with message-id 
and subject line Bug#969663: fixed in wolfssl 4.5.0+dfsg-1
has caused the Debian Bug report #969663,
regarding wolfssl: CVE-2020-12457 CVE-2020-15309 CVE-2020-24585 CVE-2020-24613
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.)


-- 
969663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wolfssl
Version: 4.4.0+dfsg-7
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for wolfssl.

CVE-2020-12457[0]:
| An issue was discovered in wolfSSL before 4.5.0. It mishandles the
| change_cipher_spec (CCS) message processing logic for TLS 1.3. If an
| attacker sends ChangeCipherSpec messages in a crafted way involving
| more than one in a row, the server becomes stuck in the ProcessReply()
| loop, i.e., a denial of service.


CVE-2020-15309[1]:
| An issue was discovered in wolfSSL before 4.5.0, when single precision
| is not employed. Local attackers can conduct a cache-timing attack
| against public key operations. These attackers may already have
| obtained sensitive information if the affected system has been used
| for private key operations (e.g., signing with a private key).


CVE-2020-24585[2]:
| An issue was discovered in the DTLS handshake implementation in
| wolfSSL before 4.5.0. Clear DTLS application_data messages in epoch 0
| do not produce an out-of-order error. Instead, these messages are
| returned to the application.


CVE-2020-24613[3]:
| wolfSSL before 4.5.0 mishandles TLS 1.3 server data in the
| WAIT_CERT_CR state, within SanityCheckTls13MsgReceived() in tls13.c.
| This is an incorrect implementation of the TLS 1.3 client state
| machine. This allows attackers in a privileged network position to
| completely impersonate any TLS 1.3 servers, and read or modify
| potentially sensitive information between clients using the wolfSSL
| library and these TLS servers.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-12457
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12457
[1] https://security-tracker.debian.org/tracker/CVE-2020-15309
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15309
[2] https://security-tracker.debian.org/tracker/CVE-2020-24585
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24585
[3] https://security-tracker.debian.org/tracker/CVE-2020-24613
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24613

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: wolfssl
Source-Version: 4.5.0+dfsg-1
Done: Felix Lechner 

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

Debian distribution maintenance software
pp.
Felix Lechner  (supplier of updated wolfssl 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, 15 Sep 2020 12:49:03 -0700
Source: wolfssl
Architecture: source
Version: 4.5.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Felix Lechner 
Changed-By: Felix Lechner 
Closes: 969370 969663
Changes:
 wolfssl (4.5.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream release; fixes CVE-2020-12457, CVE-2020-15309, CVE-2020-24585,
 CVE-2020-24613. (Closes: #969663)
   * Enable PKCS#11 support in d/rules. (Closes: #969370).
   * Remove patches submitted upstream and accepted:
   - rename-hash-type.patch
   - rename-validate-date-function.patch
   * Remove patches previously cherry-picked from the unreleased Git:
   - b07dfa425dc9416c4188830e79fd26.patch
   - c8b87eab5f2fe2ae2c3527bbfb33db6ed8b55999.patch
   * Refresh remaining Debian patches.
   * Marked the following patches as not needing forwarding to upstream:
   - dfsg.patch
   - disable-crl-monitor.patch
 

Processed: Re: Bug#969665 closed by Jelmer Vernooij (Fixed in newer silver-platter)

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:silver-platter 0.3.0+git20200611.b4292bf-1
Bug #969665 {Done: Jelmer Vernooij } [src:breezy-debian, 
src:silver-platter] breezy-debian breaks silver-platter autopkgtest: cannot 
import name 'MissingUpstreamTarball'
Bug reassigned from package 'src:breezy-debian, src:silver-platter' to 
'src:silver-platter'.
No longer marked as found in versions breezy-debian/2.8.41 and 
silver-platter/0.3.0+git20200611.b4292bf-1.
No longer marked as fixed in versions 
silver-platter/0.3.0+git20200906.d2bd137-1 and 
breezy-debian/0.3.0+git20200906.d2bd137-1.
Bug #969665 {Done: Jelmer Vernooij } [src:silver-platter] 
breezy-debian breaks silver-platter autopkgtest: cannot import name 
'MissingUpstreamTarball'
Marked as found in versions silver-platter/0.3.0+git20200611.b4292bf-1.
> fixed -1 0.3.0+git20200906.d2bd137-1
Bug #969665 {Done: Jelmer Vernooij } [src:silver-platter] 
breezy-debian breaks silver-platter autopkgtest: cannot import name 
'MissingUpstreamTarball'
Marked as fixed in versions silver-platter/0.3.0+git20200906.d2bd137-1.

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

Bug#969665: closed by Jelmer Vernooij (Fixed in newer silver-platter)

[Paul Gevers]

Control: reassign -1 src:silver-platter 0.3.0+git20200611.b4292bf-1
Control: fixed -1 0.3.0+git20200906.d2bd137-1

Hi Jelmer,

On 15-09-2020 13:18, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:breezy-debian, src:silver-platter package:
> 
> #969665: breezy-debian breaks silver-platter autopkgtest: cannot import name 
> 'MissingUpstreamTarball'
> 
> It has been closed by Jelmer Vernooij .

The BTS was a bit confused because the fixed version of breezy-debian
was older than the found version of breezy-debian.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#937255: pbgenomicconsensus: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

On Tue, Sep 15, 2020 at 10:56:22AM +0200, Andreas Tille wrote:
> Hi Moritz,
> 
> On Mon, Aug 31, 2020 at 08:59:37PM +0200, Moritz Mühlenhoff wrote:
> > On Fri, Aug 30, 2019 at 07:30:23AM +, Matthias Klose wrote:
> > > Package: src:pbgenomicconsensus
> > > Version: 2.3.2-5
> > > 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
> > 
> > Upstream development seems to have stalled, let's remove?
> 
> Yes, lets remove.  Nobody explicitly answered my call for comments.

Ack, I've just filed an RM bug.
 
Cheers,
Moritz

Processed: src:rust-rand-chacha: fails to migrate to testing for too long: unsatified Build-Depends on s390x

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.2.2-1
Bug #970412 [src:rust-rand-chacha] src:rust-rand-chacha: fails to migrate to 
testing for too long: unsatified Build-Depends on s390x
Marked as fixed in versions rust-rand-chacha/0.2.2-1.
Bug #970412 [src:rust-rand-chacha] src:rust-rand-chacha: fails to migrate to 
testing for too long: unsatified Build-Depends on s390x
Marked Bug as done
> block -1 by 961335
Bug #970412 {Done: Paul Gevers } [src:rust-rand-chacha] 
src:rust-rand-chacha: fails to migrate to testing for too long: unsatified 
Build-Depends on s390x
970412 was not blocked by any bugs.
970412 was not blocking any bugs.
Added blocking bug(s) of 970412: 961335

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

Bug#970412: src:rust-rand-chacha: fails to migrate to testing for too long: unsatified Build-Depends on s390x

[Paul Gevers]

Source: rust-rand-chacha
Version: 0.2.1-1
Severity: serious
Control: close -1 0.2.2-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 961335

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package
src:rust-rand-chacha in its current version in unstable has been trying
to migrate for 134 days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=rust-rand-chacha




signature.asc
Description: OpenPGP digital signature

Bug#964399: Should ganglia be removed?

[Moritz Mühlenhoff]

On Mon, Sep 14, 2020 at 12:17:00AM +0200, Marcos Fouces wrote:
> Hi Moritz!
> 
> Yes, i uploaded it to salsa.d.o and i am waiting for Frontdesk aproval
> to become DD (that should happens in a few days) in order to upload it
> myself instead of asking for sponsorship.
> 
> Its new home is here: https://salsa.debian.org/debian/ganglia.

Ack! And congrats for becoming a DD in advance :-)

Cheers,
Moritz

Bug#967909: Update to recent fork of editline?

[Joel Rivera]

Bastian,

correct me if I'm wrong, but you're suggesting to remove [1] in favor of [2]?

I've been trying to update editline to the fork that seems to have been evolved 
from the original debian sources at [3]. My interest in particular is due to 
that is a dependency of the Nix package manager [4],  currently the debian 
package of Nix is trying to work around the situation by adding support to 
readline (but is not complete and it seems that the upstream project is 
considering to stop/revert the integration with it). 

You can get the additional context from the emails that I sent to 
debian-mentors like a month ago [5],  and the other one to debian-devel [6], 
the maintainer (Sam Hocevar) seems to be on vacation or simply is not 
responsive. I'm starting to consider to salvage the package, but that idea 
conflicts with the current proposal of this bug report.

Currently a debian source package of the updated editline is part of the 
upsteam repo [7]  (based on the original one in debian sources), so is mostly a 
matter to be integrated in debian. 

Do you have any opinions this situation? I do not know more about libedit and 
compatibility with the newer editline, I'm only trying to integrate the 
dependency that the upstream project (Nix) seems to favor the most. 

Thanks,
--
Joel Rivera

[1]: https://tracker.debian.org/pkg/editline
[2]: https://tracker.debian.org/pkg/libedit
[3]: https://github.com/troglobit/editline
[4]: https://tracker.debian.org/pkg/nix
[5]: https://lists.debian.org/debian-mentors/2020/08/msg00096.html
[6]: https://lists.debian.org/debian-devel/2020/08/msg00187.html
[7]: https://github.com/troglobit/editline/tree/master/debian

Bug#970410: src:html5lib: fails to migrate to testing for too long: autopkgtest regressions

[Paul Gevers]

Source: html5lib
Version: 1.0.1-3
Severity: serious
Control: close -1 1.1-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 968630

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:html5lib in
its current version in unstable has been trying to migrate for 60 days
[2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=html5lib




signature.asc
Description: OpenPGP digital signature

Bug#970411: src:python-uvicorn: fails to migrate to testing for too long: depends on non-migrating package

[Paul Gevers]

Source: python-uvicorn
Version: 0.11.3-1
Severity: serious
Control: close -1 0.11.5-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package
src:python-uvicorn in its current version in unstable has been trying to
migrate for 61 days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=python-uvicorn




signature.asc
Description: OpenPGP digital signature

Processed: src:python-uvicorn: fails to migrate to testing for too long: depends on non-migrating package

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.11.5-1
Bug #970411 [src:python-uvicorn] src:python-uvicorn: fails to migrate to 
testing for too long: depends on non-migrating package
Marked as fixed in versions python-uvicorn/0.11.5-1.
Bug #970411 [src:python-uvicorn] src:python-uvicorn: fails to migrate to 
testing for too long: depends on non-migrating package
Marked Bug as done

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

Processed: src:html5lib: fails to migrate to testing for too long: autopkgtest regressions

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.1-1
Bug #970410 [src:html5lib] src:html5lib: fails to migrate to testing for too 
long: autopkgtest regressions
Marked as fixed in versions html5lib/1.1-1.
Bug #970410 [src:html5lib] src:html5lib: fails to migrate to testing for too 
long: autopkgtest regressions
Marked Bug as done
> block -1 by 968630
Bug #970410 {Done: Paul Gevers } [src:html5lib] 
src:html5lib: fails to migrate to testing for too long: autopkgtest regressions
970410 was not blocked by any bugs.
970410 was not blocking any bugs.
Added blocking bug(s) of 970410: 968630

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

Processed: src:google-http-client-java: fails to migrate to testing for too long: depends on non-migrating package

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.31.0-1
Bug #970409 [src:google-http-client-java] src:google-http-client-java: fails to 
migrate to testing for too long: depends on non-migrating package
Marked as fixed in versions google-http-client-java/1.31.0-1.
Bug #970409 [src:google-http-client-java] src:google-http-client-java: fails to 
migrate to testing for too long: depends on non-migrating package
Marked Bug as done

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

Bug#970409: src:google-http-client-java: fails to migrate to testing for too long: depends on non-migrating package

[Paul Gevers]

Source: google-http-client-java
Version: 1.27.0-3
Severity: serious
Control: close -1 1.31.0-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package
src:google-http-client-java in its current version in unstable has been
trying to migrate for 61 days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=google-http-client-java




signature.asc
Description: OpenPGP digital signature

Bug#970408: facter: FTBFS: cc1plus: all warnings being treated as errors

[Sebastian Ramacher]

Source: facter
Version: 3.11.0-4.3
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)

facter currently fails to build:
| cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/c++ 
-DBOOST_ALL_DYN_LINK -DBOOST_LOG_WITHOUT_WCHAR_T -DBOOST_SYSTEM_NO_DEPRECATED 
-DLEATHERMAN_I18N -DLEATHERMAN_LOGGING_NAMESPACE=\"puppetlabs.facter\" 
-DLEATHERMAN_USE_LOCALES 
-DPROJECT_DIR=\"/<>/obj-x86_64-linux-gnu\" 
-DPROJECT_NAME=\"FACTER\" -DUSE_BLKID -DUSE_CPPHOCON -DUSE_CURL -DUSE_OPENSSL 
-DUSE_YAMLCPP -Dlibfacter_EXPORTS -I/<>/lib/inc 
-I/<>/../vendor/nowide/include -Wextra -std=c++11 -Wall 
-Wno-unused-parameter -Wno-unused-local-typedefs -Wno-unknown-pragmas 
-Wno-missing-field-initializers -Werror -Wno-maybe-uninitialized -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o 
CMakeFiles/libfactersrc.dir/src/util/bsd/scoped_ifaddrs.cc.o -c 
/<>/lib/src/util/bsd/scoped_ifaddrs.cc
| In file included from /usr/include/string.h:495,
|  from /usr/include/c++/10/cstring:42,
|  from /usr/include/boost/regex/v4/regex_workaround.hpp:24,
|  from /usr/include/boost/regex/v4/regex.hpp:32,
|  from /usr/include/boost/regex.hpp:31,
|  from /<>/lib/inc/facter/facts/resolver.hpp:12,
|  from 
/<>/lib/inc/internal/facts/linux/../bsd/../posix/../resolvers/networking_resolver.hpp:7,
|  from 
/<>/lib/inc/internal/facts/linux/../bsd/../posix/networking_resolver.hpp:7,
|  from 
/<>/lib/inc/internal/facts/linux/../bsd/networking_resolver.hpp:7,
|  from 
/<>/lib/inc/internal/facts/linux/networking_resolver.hpp:7,
|  from 
/<>/lib/src/facts/linux/networking_resolver.cc:1:
| In function ‘char* strncpy(char*, const char*, size_t)’,
| inlined from ‘virtual boost::optional 
facter::facts::linux::networking_resolver::get_link_mtu(const string&, void*) 
const’ at /<>/lib/src/facts/linux/networking_resolver.cc:82:16:
| /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:34: error: ‘char* 
__builtin_strncpy(char*, const char*, long unsigned int)’ specified bound 16 
equals destination size [-Werror=stringop-truncation]
|   106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos 
(__dest));
|   |  
^~
| cc1plus: all warnings being treated as errors

See
https://buildd.debian.org/status/fetch.php?pkg=facter=amd64=3.11.0-4.3%2Bb1=1599808837=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: tagging 970379, severity of 970379 is serious

[Debian Bug Tracking System]

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

> # 
> https://buildd.debian.org/status/fetch.php?pkg=cpp-hocon=amd64=0.1.7-1%2Bb3=1599808899=0
> tags 970379 + sid bullseye ftbfs
Bug #970379 [cpp-hocon] FTBFS: cpp-hocon fails to build against boost1.71
Added tag(s) sid, bullseye, and ftbfs.
> severity 970379 serious
Bug #970379 [cpp-hocon] FTBFS: cpp-hocon fails to build against boost1.71
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: Re: Bug#970405: avw.lv2 build-depends unsatisfiable in testing and unstable.

[Debian Bug Tracking System]

Processing control commands:

> severity 942964 serious
Bug #942964 [src:avw.lv2] avw.lv2: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> forcemerge 942964 -1
Bug #942964 [src:avw.lv2] avw.lv2: Python2 removal in sid/bullseye
Bug #970405 [src:avw.lv2] avw.lv2 build-depends unsatisfiable in testing and 
unstable.
937695 was blocked by: 938393 936752 938621 938249 938049 943042 938230 938069 
938009 912495 937398 936606 943166 936556 943062 937562 953220 938269 938209 
938816 942112 943262 938871 936580 936872 938407 938467 938359 937194 938751 
938129 943026 943122 937841 938181 938711 937100 937160 938697 934852 937140 
945720 937079 938572 942972 936340 938856 937020 945650 936339 936909 936969 
936571 966742 966762 936949 936731 938689 936712 936496 945676 966759 942982 
937946 938582 937089 937499 946849 938212 937519 936952 938116 937336 938171 
938231 936172 966793 936898 937453 936276 938750 936211 936581 937297 943195 
937894 937487 936695 938829 938458 937593 937141 938418 945721 938342 936445 
937860 937800 936529 936465 936251 938180 938598 938710 937413 938362 942998 
937161 937101 938052 937609 938156 936912 936730 953372 937559 938252 936931 
936749 936361 936709 936769 936341 937021 937221 945651 936570 938326 938379 
942912 937806 936852 937019 942931 938771 938492 938716 936772 936736 937597 
938150 937822 936511 937672 945719 936532 936998 937417 937636 938488 938811 
937939 938098 937457 966797 945670 943161 936551 937940 936661 936601 937900 
937960 937330 943141 936641 937483 938780 937701 937293 938626 938756 943021 
937521 936982 947502 938642 936149 936427 953219 937059 936169 936812 937259 
966789 938509 937166 936152 937062 942969 942909 937473 937262 937202 966720 
945680 938549 937042 938425 936322 942930 945726 938478 938693 966779 936798 
937895 936346 943194 945742 937026 938850 937122 936936 936366 945702 936972 
938729 937794 938111 943140 937901 937331 937961 936464 937448 936640 943079 
937579 938781 938176 938236 938072 943279 937700 938463 938036 937312 938272 
947297 938810 937740 938443 945671 938389 937941 936444 943100 936550 936660 
937468 937408 936830 937682 936271 936216 936869 936809 937435 936467 945630 
938198 943201 942980 943061 937501 947294 938836 937541 937193 943041 938010 
936950 938622 943241 938210 936751 936447 936249 943121 938752 936170 937329 
938394 937159 938666 938556 936269 936816 939114 936856 942971 938340 938516 
938909 937119 938731 938712 938300 938360 937842 936689 937295 936181 936776 
936910 938050 937826 943197 937485 936572 966741 936880 937611 946929 936319 
936536 938076 938232 936951 937454 943040 938011 943240 966794 938211 938276 
938032 943039 937539 938581 943260 937779 936829 942981 937560 937500 943060 
943000 938695 938423 937720 936870 936424 937428 943120 936212 937475 936786 
937102 937433 937162 937006 937066 938730 938301 938361 937266 937819 937246 
937989 938438 938709 938769 942970 936326 943294 937222 942929 937610 936881 
936418 937997 937022 937126 938445 966739 938529 945746 945706 936710 937356 
936362 936932 938465 938251 936180 938051 936911 937414 938081 936929 938772 
937260 938736 936150 937000 937993 937386 937179 938511 937040 942911 937240 
945682 942976 966722 938532 937039 938852 936531 945740 966746 937671 937437 
937616 937959 936282 966766 883161 936756 937762 938270 945698 938130 938427 
938070 937889 943046 943142 943102 943006 939115 936602 938831 937742 943266 
936876 937680 942951 966801 938661 938601 936298 937726 936832 943222 936110 
947501 938641 938229 943126 937484 936981 937897 938029 937094 936321 936693 
938510 943193 937041 936850 937241 942910 938346 938694 938306 938490 938366 
937793 937261 937455 937201 938280 966795 937001 937061 936729 936569 943159 
936509 938056 936659 936916 938152 937474 945701 936770 938256 936530 937759 
938322 937670 936886 936425 937942 942986 945672 938830 945636 937719 937189 
938586 938216 938809 938131 938271 938782 936956 936619 937962 937902 938016 
883194 943119 934870 936176 936111 938464 938640 937415 938639 936132 936463 
936443 943295 942950 937926 937681 936810 938444 938660 938600 937197 966800 
943095 93 937696 939483 936938 938223 937028 943237 937304 937364 938315 
937275 937135 945658 943037 936796 948847 938476 945728 936164 937054 938411 
93 937148 939259 936335 937254 945624 966784 938432 937883 938591 936945 
938685 937168 942991 936891 938707 937422 936190 945733 938065 938374 937214 
938451 937817 912487 937033 937406 938355 937233 938924 938892 936923 938178 
966737 938125 937446 936996 936430 937638 945667 936127 938384 936578 936525 
936449 936738 936634 945647 943134 943274 937835 937157 938718 938590 943113 
936804 936864 938188 937665 937605 937848 938614 936267 936207 936745 942990 
938803 938863 936765 936247 938843 938410 936844 937808 937327 937645 926244 
849087 966755 936543 936191 938947 935358 942944 937085 938544 938450 937495 
936687 936890 938654 938564 937787 939106 942964 

Bug#970405: avw.lv2 build-depends unsatisfiable in testing and unstable.

[Sebastian Ramacher]

Control: severity 942964 serious
Control: forcemerge 942964 -1

On 2020-09-15 20:20:24 +0100, peter green wrote:
> Source: avw.lv2
> Version: 0.1.6~dfsg0-1
> Severity: serious
> Tags: bullseye, sid
> 
> avw.lv2 build-depends on the "python" binary package which is no longer built 
> by the "python-defaults" source package.
> In unstable it is present as a cruft package but said cruft package is 
> uninstallable due to strictly versioned depdencies.
> In testing it is gone completely. Either way your build-dependencies are 
> unsatisfiable.

This is already tracked in #942964. Instead of fixing this issue, it
should be replaced with ams.lv2 (see #942856)

Cheers

> 
> If you *really* need to stick with python2, you can build-depend on python2 
> instead and fix any python invocations to
> invoke that instead of the unversioned python. Ideally though you should be 
> moving to python 3.
> 
> ___
> pkg-multimedia-maintainers mailing list
> pkg-multimedia-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: severity of 968756 is important, tagging 968756

[Debian Bug Tracking System]

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

> severity 968756 important
Bug #968756 [inkscape] inkscape: Inkscape crash on multiple undo-redo actions
Severity set to 'important' from 'critical'
> tags 968756 + help - upstream
Bug #968756 [inkscape] inkscape: Inkscape crash on multiple undo-redo actions
Added tag(s) help.
Bug #968756 [inkscape] inkscape: Inkscape crash on multiple undo-redo actions
Removed tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#969608: [Debian-med-packaging] Bug#969608: makeblastdb 2.10.x on 32-bit architectures

[Étienne Mollier]

Hi Aaron,

Aaron M. Ucko, on 2020-09-14 17:36:14 -0400:
> 
> Thanks for clarifying.  AFAICT, this environment imposes a tighter limit
> than native arm64 hardware, and versions 2.10.0-1 and 2.10.0-3 both hit
> it.  Rough bisection via the BLASTDB_LMDB_MAP_SIZE environment variable
> gives an empirical limit of 20,073,607,168 bytes (4,900,783 4K pages).
> This number isn't particularly round, so it presumably reflects what
> remains of some cumulative limit.  As such, the default should probably
> be at most 20,000,000,000 bytes (4,882,812½ pages ;-) to build in more
> of a margin.  That's 1/15 upstream's default, but with any luck should
> be plenty in practice, so I'm open to making that adjustment.  Also,
> this reduced limit would still be well more than we (can) allow on
> 32-bit architectures, which is in turn much more than upstream's trunk
> allows on Windows:
> 
> https://www.ncbi.nlm.nih.gov/IEB/ToolBox/CPP_DOC/lxr/source/include/objtools/blast/seqdb_writer/writedb_lmdb.hpp#L51

Wow, thanks for the comprehensive background information.  In
case someone else (me in a not so near future for instance)
stumbles upon this again, I keep note that reducing the size of
BLASTDB_LMDB_MAP_SIZE a bit might help:

(sid-arm64-sbuild)$ makeblastdb -in NC_005816.faa -dbtype prot 
-hash_index -max_file_sz 20MB -parse_seqids -taxid 10


Building a new DB, current time: 09/15/2020 19:37:37
New DB name:   /tmp/NC_005816.faa
New DB title:  NC_005816.faa
Sequence type: Protein
Deleted existing Protein BLAST database named /tmp/NC_005816.faa
Keep MBits: T
Maximum file size: 2000B

No volumes were created.

Error: mdb_env_open: Cannot allocate memory

(sid-arm64-sbuild)$ BLASTDB_LMDB_MAP_SIZE=100 makeblastdb -in 
NC_005816.faa -dbtype prot -hash_index -max_file_sz 20MB -parse_seqids -taxid 10


Building a new DB, current time: 09/15/2020 19:37:34
New DB name:   /tmp/NC_005816.faa
New DB title:  NC_005816.faa
Sequence type: Protein
Deleted existing Protein BLAST database named /tmp/NC_005816.faa
Keep MBits: T
Maximum file size: 2000B
Adding sequences from FASTA; added 10 sequences in 0.166301 seconds.

Kind Regards,
-- 
Étienne Mollier 
Old rsa/3072: 5ab1 4edf 63bb ccff 8b54  2fa9 59da 56fe fff3 882d
New rsa/4096: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/2, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#957564: marked as done (mrbayes: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 16 Sep 2020 01:05:17 +0530
with message-id 

and subject line Re: mrbayes: ftbfs with GCC-10
has caused the Debian Bug report #957564,
regarding mrbayes: ftbfs with GCC-10
to be marked as done.

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

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


-- 
957564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mrbayes
Version: 3.2.6+dfsg-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/mrbayes_3.2.6+dfsg-2_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
  | ^~~
In file included from /usr/include/stdio.h:867,
 from bayes.h:10,
 from sumpt.c:37:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: 
‘__builtin___sprintf_chk’ output between 15 and 144 bytes into a destination of 
size 120
   36 |   return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
  |  ^~
   37 |   __bos (__s), __fmt, __va_arg_pack ());
  |   ~
sumpt.c:7161:32: warning: ‘.tree’ directive writing 5 bytes into a region of 
size between 1 and 120 [-Wformat-overflow=]
 7161 | sprintf (tFilename, "%s.tree%d.trprobs", 
sumtParams.sumtOutfile, treeNo+1);
  |^
sumpt.c:7161:29: note: directive argument in the range [-2147483647, 2147483647]
 7161 | sprintf (tFilename, "%s.tree%d.trprobs", 
sumtParams.sumtOutfile, treeNo+1);
  | ^~~
In file included from /usr/include/stdio.h:867,
 from bayes.h:10,
 from sumpt.c:37:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: 
‘__builtin___sprintf_chk’ output between 15 and 144 bytes into a destination of 
size 120
   36 |   return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
  |  ^~
   37 |   __bos (__s), __fmt, __va_arg_pack ());
  |   ~
sumpt.c: In function ‘PrintBrlensToFile’:
sumpt.c:7257:29: warning: ‘%s’ directive writing up to 119 bytes into a region 
of size 100 [-Wformat-overflow=]
 7257 | sprintf (filename, "%s.brlens", sumtParams.sumtOutfile);
  | ^~  ~~
In file included from /usr/include/stdio.h:867,
 from bayes.h:10,
 from sumpt.c:37:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: 
‘__builtin___sprintf_chk’ output between 8 and 127 bytes into a destination of 
size 100
   36 |   return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
  |  ^~
   37 |   __bos (__s), __fmt, __va_arg_pack ());
  |   ~
sumpt.c:7255:29: warning: ‘%s’ directive writing up to 119 bytes into a region 
of size 100 [-Wformat-overflow=]
 7255 | sprintf (filename, "%s.tree%d.brlens", sumtParams.sumtOutfile, 
treeNo+1);
  | ^~ ~~
sumpt.c:7255:28: note: directive argument in the range [-2147483647, 2147483647]
 7255 | sprintf (filename, "%s.tree%d.brlens", sumtParams.sumtOutfile, 
treeNo+1);
  |^~
In file included from 

Bug#970406: flowcanvas build-depends unsatisfiable in testing and unstable.

[peter green]

Source: flowcanvas
Version: 0.7.1+dfsg0-0.5
Severity: serious
Tags: bullseye, sid

flowcanvas build-depends on the "python" binary package which is no longer built by the 
"python-defaults" source package.
In unstable it is present as a cruft package but said cruft package is 
uninstallable due to strictly versioned depdencies.
In testing it is gone completely. Either way your build-dependencies are 
unsatisfiable.

If you *really* need to stick with python2, you can build-depend on python2 
instead and fix any python invocations to
invoke that instead of the unversioned python. Ideally though you should be 
moving to python 3.

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

[Debian Bug Tracking System]

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

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

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

Bug#970405: avw.lv2 build-depends unsatisfiable in testing and unstable.

[peter green]

Source: avw.lv2
Version: 0.1.6~dfsg0-1
Severity: serious
Tags: bullseye, sid

avw.lv2 build-depends on the "python" binary package which is no longer built by the 
"python-defaults" source package.
In unstable it is present as a cruft package but said cruft package is 
uninstallable due to strictly versioned depdencies.
In testing it is gone completely. Either way your build-dependencies are 
unsatisfiable.

If you *really* need to stick with python2, you can build-depend on python2 
instead and fix any python invocations to
invoke that instead of the unversioned python. Ideally though you should be 
moving to python 3.

Bug#967200: marked as done (python-coverage: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 15 Sep 2020 20:03:33 +0100
with message-id 
and subject line re: python-coverage: Unversioned Python removal in sid/bullseye
has caused the Debian Bug report #967200,
regarding python-coverage: Unversioned Python removal in sid/bullseye
to be marked as done.

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

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


-- 
967200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-coverage
Version: 5.1+dfsg.1-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

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

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

Please check for dependencies, build dependencies AND autopkg tests.

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

Version: 5.1+dfsg.1-2

I have looked at the latest version in sid and cannot find any references in 
debian/control or debian/test/control to
the "unversioned python" packages.--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> reopen 963827
Bug #963827 {Done: Gianfranco Costamagna } 
[src:virtualbox] [virtualbox] guests limited to 800x600
Bug reopened
Ignoring request to alter fixed versions of bug #963827 to the same values 
previously set
> severity 963827 important
Bug #963827 [src:virtualbox] [virtualbox] guests limited to 800x600
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#969331: marked as done (rviz: [rospack] Error: no such package media_export)

[Debian Bug Tracking System]

Your message dated Tue, 15 Sep 2020 20:41:08 +0200
with message-id <160019526899.413201.18322213813565356783@localhost>
and subject line Re: Bug#969331: rviz: [rospack] Error: no such package 
media_export
has caused the Debian Bug report #969331,
regarding rviz: [rospack] Error: no such package media_export
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.)


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

Hi,

starting rviz on Debian unstable currently yields the following output:

[ INFO] [1598885512.042478573]: rviz version 1.14.1
[ INFO] [1598885512.042531596]: compiled against Qt version 5.14.2
[ INFO] [1598885512.042547093]: compiled against OGRE version 1.9.0 (Ghadamon)
[ INFO] [1598885512.052974842]: Forcing OpenGl version 0.
[ INFO] [1598885512.592152405]: Stereo is NOT SUPPORTED
[ INFO] [1598885512.592246596]: OpenGl version: 4.6 (GLSL 4.6).
[rospack] Error: no such package media_export
[librospack]: error while executing command
zsh: segmentation fault  rviz

Maybe triggered by this line?

https://sources.debian.org/src/ros-rviz/1.14.1+dfsg-1/src/rviz/ogre_helpers/render_system.cpp/?hl=316#L318

According to the package.xml, rviz depends on media_export but that one
is not packaged yet?

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-9-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
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

Versions of packages rviz depends on:
ii  fonts-liberation   1:1.07.4-9
ii  libboost-filesystem1.71.0  1.71.0-6+b2
ii  libboost-thread1.71.0  1.71.0-6+b2
ii  libc6  2.31-2
ii  libclass-loader1d  0.5.0-1
ii  libconsole-bridge0.4   0.4.3+dfsg-1
ii  libgcc-s1  10.2.0-3
ii  libimage-transport0d   1.12.0-1+b1
ii  libinteractive-markers2d   1.12.0-3
ii  liblaser-geometry0d1.6.5-1+b1
ii  libmessage-filters1d   1.15.8+ds1-1
ii  libogre-1.9.0v51.9.0+dfsg1-12+b1
ii  libopengl0 1.3.1-1
ii  libqt5core5a   5.14.2+dfsg-4
ii  libqt5gui5 5.14.2+dfsg-4
ii  libqt5svg5 5.14.2-2
ii  libqt5widgets5 5.14.2+dfsg-4
ii  librosconsole3d1.14.2-1
ii  libroscpp-serialization0d  0.7.2-2
ii  libroscpp3d1.15.8+ds1-1
ii  libroslib0d1.15.4-2
ii  librostime1d   0.7.2-4
ii  librviz5d  1.14.1+dfsg-1
ii  libstdc++6 10.2.0-3
ii  libtf2-2d  0.7.2-3
ii  libtinyxml2-8  8.0.0+dfsg-2
ii  liburdf1d  1.13.2-2
ii  liburdfdom-world   1.0.3-1

rviz recommends no packages.

rviz suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, 31 Aug 2020 20:16:19 +0200 Jochen Sprickerhof  
wrote:
> Uhm.. https://wiki.debian.org/DontBreakDebian
> 
> Please close if you agree.

Agreed.

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

Bug#963827: closed by Gianfranco Costamagna (Re: [virtualbox] guests limited to 800x600)

[Lyndon Brown]

Re-opening. This is most certainly *not* fixed.

I have a Debian Sid installation (with a Gnome environment) in a VBox
VM, fully up-to-date, and the problem still exists with this.

When the problem surfaced, I had to restore from backup and place a
hold on kernel and virtualbox-guest-* package updates to keep the VM
usable (but insecure), while maintaining a duplicate copy that I
install the updates on to test if each new version fixes it, wasting a
chunk of my disk space. This has not been at all ideal. AS I said, I've
just double checked things, and the problem is definitely still there.

Frustratingly, when I looked at the VBox bug tracker some weeks ago,
others were in the same position; VBox guys were just asking if those
users were using wayland, and stating that the resizing simply does not
work for wayland, contradicting the simple fact that it clearly was
working fine up until the point release that broke it as people tried
to point out. There was also some suggestion of an environment variable
being involved, and possibly not used correctly by some distros, if I
recall correctly. I have not been holding my breath for a quick fix.

Interestingly I have just discovered something useful - I tried
selecting 'gnome on xorg' at the login screen, and was pleased to find
that the login environment under that at least works fine. I guess this
must have been one of the later fixes and I did not previously think to
recheck. So the problem only affects the default (wayland) environment.
This eases some of the impact upon myself - I guess I can manage with
an X11 environment for the time being.

Fundamentally though, the problem is only partially fixed, it's still
broken for wayland, which *was* working previously, despite the
illogical claims of VBox guys. And thus since the problem partially
still exists, the bug should remain open - the small login screen is
mostly just cosmetic in nature, but not being able to have a usable
wayland session is problematic.


On Tue, 2020-09-15 at 08:09 +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:virtualbox package:
> 
> #963827: [virtualbox] guests limited to 800x600
> 
> It has been closed by Gianfranco Costamagna  >.
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Gianfranco
> Costamagna  by
> replying to this email.
> 
> 

Bug#954189: Upload approval for acmetool 0.2 in buster-backports

[Ralph Giles]

As an update on this, I've gotten acmetool 0.2 to build on buster. The
following packages need backporting:

- golang-github-gofrs-uuid
- golang-golang-x-xerrors
- golang-github-google-go-cmp
- golang-gopkg-square-go-jose.v2
- golang-gopkg-hlandau-acmeapi.v2
- acmetool

The 5 golang-* packages are source-only libraries, which shouldn't
affect users of buster. They're just necessary to build the newer
version entirely from packaged software.

Of these packages, two require minor changes:

- acmetool packaging fails because dwz can't find any debug tables to
remove in the binary built by buster's golang 1.11. I suggest just
skipping this step.

- golang-gopkg-square-go-jose.v2 depends on dephelper-compat 13, but
buster has 12. Downgrading the requirement seems to work fine.

On IRC I got push-back from the go-team about reviewing changes, so I'm
unsure how to proceed. Can someone from the letsencrypt team please
comment on the proposed changes, either here, or on the salsa
repositories?

I've been recording the current state of my backport effort, including
patches, at https://gitlab.xiph.org/rillian/acmetool-backport if anyone
wants to reproduce.

Thanks,
Ralph


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

Bug#969663: polyphone is marked for autoremoval from testing

[Thorsten Glaser]

Felix Lechner dixit:

>> Is there anything I can help to ensure it’s not autoremoved?
>
>I just saw it this morning and plan to upload 4.5.0 later today. From
>what I understand, closing #969663 should postpone the autoremoval
>process?

Thanks!

The autoremoval will go on until a version with #969663 fixed
enters testing, but that is why such a long advance notice is
given (five weeks or so).

bye,
//mirabilos
-- 
Solange man keine schmutzigen Tricks macht, und ich meine *wirklich*
schmutzige Tricks, wie bei einer doppelt verketteten Liste beide
Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz
hervorragend.   -- Andreas Bogk über boehm-gc in d.a.s.r

Bug#969663: polyphone is marked for autoremoval from testing

[Felix Lechner]

Hi Thorsten,

> Is there anything I can help to ensure it’s not autoremoved?

I just saw it this morning and plan to upload 4.5.0 later today. From
what I understand, closing #969663 should postpone the autoremoval
process?

Kind regards
Felix

Bug#970232: marked as done (mir FTBFS: symbol differences)

[Debian Bug Tracking System]

Your message dated Tue, 15 Sep 2020 16:03:40 +
with message-id 
and subject line Bug#970232: fixed in mir 1.8.0+dfsg1-8
has caused the Debian Bug report #970232,
regarding mir FTBFS: symbol differences
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.)


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

https://buildd.debian.org/status/logs.php?pkg=mir=1.8.0%2Bdfsg1-6

For C++ libraries symbols files are often not worth the troubles,
unless upstream makes only exported symbols visible:
https://wiki.debian.org/UsingSymbolsFiles
--- End Message ---
--- Begin Message ---
Source: mir
Source-Version: 1.8.0+dfsg1-8
Done: Mike Gabriel 

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated mir 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, 15 Sep 2020 09:16:29 +
Source: mir
Architecture: source
Version: 1.8.0+dfsg1-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Mir Team 
Changed-By: Mike Gabriel 
Closes: 970232
Changes:
 mir (1.8.0+dfsg1-8) unstable; urgency=medium
 .
   * debian/patches:
 + Add 2001_dont-dpkg-gensymbols-by-upstream.patch. Don't touch
   debian/*.symbols files during build via upstream's CMakeLists.txt
   configuration.
   * debian/libmiral3.symbols:
 + Fix upstream version numbers. The libmiral3 bin:pkg's version is 
different
   from source:Version.
 + Mark three symbols as MISSING since libmiral3 bin:pkg verison 2.9.
   (Closes: #970232).
Checksums-Sha1:
 78743d932cf188043665ffd30bc83a8b9da27257 5678 mir_1.8.0+dfsg1-8.dsc
 a78ff94c108406bec27f67865271cb9ebf88527f 65076 mir_1.8.0+dfsg1-8.debian.tar.xz
 9645b86746996927727bf7e2bc462065083b94a1 16175 
mir_1.8.0+dfsg1-8_source.buildinfo
Checksums-Sha256:
 a70efd7a893d67bef57d9445c7ea5b626db74cf88cb5719555272cff24aa5f23 5678 
mir_1.8.0+dfsg1-8.dsc
 3c3032188f44e099565f40c3fa47b0792120844b2baecfbf54be26b7b7a2faea 65076 
mir_1.8.0+dfsg1-8.debian.tar.xz
 a2287bd5e4d964bb8c9c546b1c8f5b7a75800dd0bd1fc6362f8fdaa7de3e7d45 16175 
mir_1.8.0+dfsg1-8_source.buildinfo
Files:
 22e72a853a176c9a55ec3adf32563b22 5678 x11 optional mir_1.8.0+dfsg1-8.dsc
 cdd7c4739ebe6f4cf636fafd0e0e4ba0 65076 x11 optional 
mir_1.8.0+dfsg1-8.debian.tar.xz
 6ac1ad66d01e638983b3809e03dbf130 16175 x11 optional 
mir_1.8.0+dfsg1-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl9g4nYVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxhRIP/3mjHGP8cZYnblfhQuV49BiZtsbP
JTiK34RLKKqsZEYIL7KWD4Qq2V8RoAb+XF4/HZU6TPyFuQVQesASuweGCObqdbzx
DlPLZQeHllGw1y/Pi8ef67ZEzyUfI1rX8AQX42ZC/vCQFw8Nf/YPiYnMv8LYxOSj
9cBBNCJBloZmEbrzJXmupTKSTxYvWun5HoRZrLLCcOsF3i7RfG0bvIeJ4E1ropRP
2HfZTmLUp2ID+8VVXZZLAZraHtcwmdI8miUUjwd2CaavEx6/h+cEWZhyixjvnfe6
9OibGV0I+m1FKG4F/F3IB19xg77VAS1b0XKjRvbJg3dhSvdj22oORsezVrrNShE/
hm0ykvdJGtSsk4beW2dtfb3FpckDKSFYqrwY+WkIAvFeL7V9LXoaOis68g02t5yf
HIlXtenTK8fOS7/IDAB8SiUjrvE+fW2VI+QjmZ+xChHUML+RifR/Vnitn+w1DX7k
tDHlsOONdQ0+kfM+oeOs3yEOKnMt8EdQgch/f/WPSjSF1pbkYleOYoOWf+7igSe5
e3Yr/b803e5NIWgtzwOEi5etk7y1nX6DpRJJUoFck3hbuKMop51Hl5r1wkJPq94N
XhjY2Mj5mR6H38GNfq/MYwHg4/saOw7iP9MSceFQ7yLTF/DIwmBkje/A9mQb5mps
jUa3YGsAdTdwf3jN
=Pdsa
-END PGP SIGNATURE End Message ---

Bug#969663: polyphone is marked for autoremoval from testing

[Thorsten Glaser]

Debian testing autoremoval watch dixit:

>polyphone 2.2.0.20200612+dfsg1-1 is marked for autoremoval from testing on 
>2020-10-20
>
>It (build-)depends on packages with these RC bugs:
>969663: wolfssl: CVE-2020-12457 CVE-2020-15309 CVE-2020-24585 CVE-2020-24613
> https://bugs.debian.org/969663

Is there anything I can help to ensure it’s not autoremoved?

Thanks,
//mirabilos
-- 
  “Having a smoking section in a restaurant is like having
  a peeing section in a swimming pool.”
-- Edward Burr

Bug#963088: marked as done (bppsuite: autopkgtest failure on arm64: precision issue in reference data)

[Debian Bug Tracking System]

Your message dated Tue, 15 Sep 2020 15:18:30 +
with message-id 
and subject line Bug#963088: fixed in bppsuite 2.4.1-3
has caused the Debian Bug report #963088,
regarding bppsuite: autopkgtest failure on arm64: precision issue in reference 
data
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.)


-- 
963088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bppsuite
Version: 2.4.1-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package bppsuite, great.
However, it fails on arm64. Currently this failure is blocking the
migration to testing [1]. Can you please investigate the situation and
fix it?

I copied some of the output at the bottom of this report. It seems to
show a calculation precision issue in your reference data, but maybe the
answer is really good and it's showing an issue with your package on
arm64. (0.00762627 vs 0.00762628)

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=bppsuite

https://ci.debian.net/data/autopkgtest/testing/amd64/b/bppsuite/5887912/log.gz

<
(6.langur_Sen:0.00790177,7.langur_Tob:1e-06,8.Douc_langur_Pne:0.0233448):0.00758139,9.probiscis_Nla:0.00784523):0.0258479,5.colobus_Cgu:0.036229):0.077728,(((10.baboon_Pcy:0.0080218,11.mangabey_Cat:1e-06):1e-06,12.rhesus_Mmu:0.00761117):1e-06,13.Allen_Ani:0.015264,(14.talapoin_Mta:0.0156828,(15.patas_Epa:0.0160261,16.vervet_Cae:0.00794742):0.00762627):0.0076675):0.0173244):0.0393703,(((1.human:0.0161234,2.chimp_bonobo_gorilla:1e-06):0.00762358,3.orangutan_Ppy:1e-06):0.00723969,4.gibbon_Ggo:0.0319335):0.070116,(17.squirrel_m:0.0258088,(18.tamarin_Soe:0.0317538,19.Marmoset_Cja:0.0413489):1e-06):0.123173);
---
>
(6.langur_Sen:0.00790177,7.langur_Tob:1e-06,8.Douc_langur_Pne:0.0233448):0.00758139,9.probiscis_Nla:0.00784523):0.0258479,5.colobus_Cgu:0.036229):0.077728,(((10.baboon_Pcy:0.0080218,11.mangabey_Cat:1e-06):1e-06,12.rhesus_Mmu:0.00761117):1e-06,13.Allen_Ani:0.015264,(14.talapoin_Mta:0.0156828,(15.patas_Epa:0.0160261,16.vervet_Cae:0.00794742):0.00762628):0.0076675):0.0173244):0.0393703,(((1.human:0.0161234,2.chimp_bonobo_gorilla:1e-06):0.00762358,3.orangutan_Ppy:1e-06):0.00723969,4.gibbon_Ggo:0.0319335):0.070116,(17.squirrel_m:0.0258088,(18.tamarin_Soe:0.0317538,19.Marmoset_Cja:0.0413489):1e-06):0.123173);




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: bppsuite
Source-Version: 2.4.1-3
Done: Pranav Ballaney 

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

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

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

Debian distribution maintenance software
pp.
Pranav Ballaney  (supplier of updated bppsuite 
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, 15 Sep 2020 18:56:51 +0530
Source: bppsuite
Architecture: source
Version: 2.4.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Pranav Ballaney 
Closes: 963088
Changes:
 bppsuite (2.4.1-3) unstable; urgency=medium
 .
   * Approximate autopkgtest output. Closes: #963088.
   * Add Pranav Ballaney to Uploaders
Checksums-Sha1:
 eaf2d58f8ae84e189d749a75717508ed38a5c6fe 2214 bppsuite_2.4.1-3.dsc
 8e8b2a92541c9ebee5b5718a54fc4cdb3687eac5 67384 bppsuite_2.4.1-3.debian.tar.xz
 659a544cc2efba6f25df9f828fa14ea128b99a60 17085 
bppsuite_2.4.1-3_source.buildinfo
Checksums-Sha256:
 663c10220860b0b980d5d8a0460ea4face242ac471f95c0a170400101582fff0 2214 
bppsuite_2.4.1-3.dsc
 d48eff517ee17632ee32da981b56a725aa9f71fca4b30813fc9bd0f328afaf2f 67384 
bppsuite_2.4.1-3.debian.tar.xz
 d4f5871409c9251a2155a2bb847400f7ef6d43e9277ef20797da5ff2a9fbd4e3 17085 
bppsuite_2.4.1-3_source.buildinfo
Files:
 64c884e1103dd74238e6af378902a831 2214 science optional bppsuite_2.4.1-3.dsc
 377689bcdb82d3e6a7806f0737c0e6f4 

Bug#970340: [Debian-med-packaging] Bug#970340: rna-star: autopkgtest regression: --genomeSAindexNbases 8 is too large for the genome size=99940

[Andreas Tille]

Dear Sascha,

On Tue, Sep 15, 2020 at 04:32:02PM +0200, Sascha Steinbiss wrote:
> 
> I can confirm that that was the issue. I have pushed a fix to git and
> will make an upload later if there are no objections.

No objections for fixing a bug at all. ;-)

Thanks a lot

   Andreas.

-- 
http://fam-tille.de

Bug#970340: [Debian-med-packaging] Bug#970340: rna-star: autopkgtest regression: --genomeSAindexNbases 8 is too large for the genome size=99940

[Sascha Steinbiss]

Hi all,

>> you once wrote that test.  Do you have any idea how to fix it?
> 
> Since this is just a warning, it might be sufficient to simply add
> 
>   Restrictions: allow-stderr
> 
> That would make sure that printing a warning to stderr does not cause
> the test to fail. I will test this later and fix it if that was the problem.

I can confirm that that was the issue. I have pushed a fix to git and
will make an upload later if there are no objections.

Best regards
Sascha

Bug#970340: rna-star: autopkgtest regression: --genomeSAindexNbases 8 is too large for the genome size=99940

[Sascha Steinbiss]

Hi all,

> you once wrote that test.  Do you have any idea how to fix it?

Since this is just a warning, it might be sufficient to simply add

  Restrictions: allow-stderr

That would make sure that printing a warning to stderr does not cause
the test to fail. I will test this later and fix it if that was the problem.

Cheers
Sascha

Processed: Re: nvidia-graphics-drivers-legacy-390xx 390.138-3 is not available for i386

[Debian Bug Tracking System]

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

> notfound 970390 nvidia-graphics-drivers-legacy-390xx/390.138-1
Bug #970390 [src:nvidia-graphics-drivers-legacy-390xx] 
nvidia-graphics-drivers-legacy-390xx 390.138-3 is not available for i386
No longer marked as found in versions 
nvidia-graphics-drivers-legacy-390xx/390.138-1.
> found 970390 nvidia-graphics-drivers-legacy-390xx/390.138-3
Bug #970390 [src:nvidia-graphics-drivers-legacy-390xx] 
nvidia-graphics-drivers-legacy-390xx 390.138-3 is not available for i386
Marked as found in versions nvidia-graphics-drivers-legacy-390xx/390.138-3.
>
End of message, stopping processing here.

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

Bug#970390: nvidia-graphics-drivers-legacy-390xx 390.138-3 is not available for i386

[Vincent Lefevre]

Source: nvidia-graphics-drivers-legacy-390xx
Version: 390.138-1
Severity: serious

nvidia-graphics-drivers-legacy-390xx 390.138-3 is not available
for i386, so that it cannot even be installed on amd64 with i386
as a foreign architecture.

According to

  
https://buildd.debian.org/status/package.php?p=nvidia-graphics-drivers-legacy-390xx

there seems to be an issue with the patch fixing bug 969889:

Applying patch disable-module-nvidia-uvm.patch
patching file Makefile
Hunk #1 FAILED at 60.
1 out of 1 hunk FAILED -- rejects in file Makefile
Patch disable-module-nvidia-uvm.patch does not apply (enforce with -f)
make[1]: *** [debian/rules:256: kernel-source-tree] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:172: binary-arch] Error 2

armhf is affected too.

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

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

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

Processed: severity of 970191 is serious

[Debian Bug Tracking System]

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

> # fails to install → release critical
> severity 970191 serious
Bug #970191 [bookworm] bookworm: Python3 syntax errors at configure step
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#969809: marked as done (chafa: autopkgtest should be marked superficial)

[Debian Bug Tracking System]

Your message dated Tue, 15 Sep 2020 11:18:41 +
with message-id 
and subject line Bug#969809: fixed in chafa 1.4.1-2
has caused the Debian Bug report #969809,
regarding chafa: autopkgtest should be marked superficial
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.)


-- 
969809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: chafa
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'chafa' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'chafa'.

--

Sudip 
--- End Message ---
--- Begin Message ---
Source: chafa
Source-Version: 1.4.1-2
Done: Mo Zhou 

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

Debian distribution maintenance software
pp.
Mo Zhou  (supplier of updated chafa 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, 15 Sep 2020 19:03:33 +0800
Source: chafa
Architecture: source
Version: 1.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Mo Zhou 
Changed-By: Mo Zhou 
Closes: 969809
Changes:
 chafa (1.4.1-2) unstable; urgency=medium
 .
   * Mark autopkgtest as superficial. (Closes: #969809)
   * Bump debhelper compat level to 13.
   * Remove dh_missing override as it defaults to --fail-missing since compat 
13.
   * Specify Build-Depends-Package: libchafa-dev in the symbols control file.
Checksums-Sha1:
 d23e65e9daad4fa703e85ceebf0e6860abaed6d2 1996 chafa_1.4.1-2.dsc
 ec2e4a1771976d0f47e18f5a274b0e08add4efcc 4304 chafa_1.4.1-2.debian.tar.xz
 d12a1919a0ad7e74b91ce72bda903b7ca8bb24c8 11041 chafa_1.4.1-2_source.buildinfo
Checksums-Sha256:
 c1df53487d2be36b18fa7dbba13c2efdcd6d5bd64b7419f6eae4ab7bc692a383 1996 
chafa_1.4.1-2.dsc
 37d495124cfffb1c40e21cd65bb77deda6990a484d33f5c8f9d6359c5a885245 4304 
chafa_1.4.1-2.debian.tar.xz
 59c0aad3f066f412152c8e93cdc3130823a34d4948a3d9c778f4068eec79a22d 11041 
chafa_1.4.1-2_source.buildinfo
Files:
 8dfc5020f326d68e77dbbb929c7fe974 1996 graphics optional chafa_1.4.1-2.dsc
 e2b03fcf3dcefc752163de869c57df7f 4304 graphics optional 
chafa_1.4.1-2.debian.tar.xz
 7fb1bfb9a3d1f2778521c883e06087c5 11041 graphics optional 
chafa_1.4.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAl9goOwRHGx1bWluQGRl
Ymlhbi5vcmcACgkQYmRes19oaopCag//ULpk/YqMP54iyhdDITVSefgAXEqkLI6i
bdW7XWGwmMVQImRIR8coBPT6oWr3p8GS8mH6Jd3AExPcPNPVs2VCLpgkGCZO/RQa
tQntUmsUjpsG7y51xNCg3liz2HRvuEpz+RYdHJvJavQvjxTFuLxNuGfu7GG1yfpe
ehnCu0MazapastJ9+pscsxYW2phvt/m4GbfdAxLrq2jL8dqv8P1jjj+UdY43CVdR
fyX0rUv/ojQqt9cbJ6D6ptBIMsYJ94EMbIPVL1vI4NZDtOOpTfVOouhrzSHnaZow
kCRO4zqI7h+/Hn0KMQY/GOf+J4KqXJj4iRGXTUeS2woK2UneAW+osQCtPke07EB3
uF/KoY9LvGUQnnlU5NUR8ciHTUq8xiU8ADKfLI3WMR9bEpwAALoPZw6frsYQFUuL
Y+6+AeSTMcozdLG3FcnuJkQAZJT+cTCslc0evX6Q97ohL4/h4MqDjS6ySzK93gYS
bn64i09piTnkm6TadE/0IiZiZF6ru283lfFJrcLg7x/kqOwCr2JcmEdYbpYKmpU9
BKGpeL7mCh4FbozTHp39bHLYQEclM1yyHvIs+44SxnevIC9+lxxOI6ytfHh+rqqJ
vBACeIYA2XPnbAsXhP00o7bL3zJS/hVVwLql+5B5n9vp7vCF3v/0CNLimoLyhyu3
rHtLbkIWbRQ=
=Z54J
-END PGP SIGNATURE End Message ---

Bug#957600: marked as done (netkit-ftp: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Tue, 15 Sep 2020 11:21:21 +
with message-id 
and subject line Bug#957600: fixed in netkit-ftp 0.17-34.1.1
has caused the Debian Bug report #957600,
regarding netkit-ftp: ftbfs with GCC-10
to be marked as done.

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

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


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

CMAKE_EXPORT_NO_PACKAGE_REGISTRY
CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY
CMAKE_INSTALL_LIBDIR
CMAKE_INSTALL_LOCALSTATEDIR
CMAKE_INSTALL_SYSCONFDIR


-- Build files have been written to: /<>/obj-x86_64-linux-gnu
   dh_auto_build -O--buildsystem=cmake
cd obj-x86_64-linux-gnu && make -j4
make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu 
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start 
/<>/obj-x86_64-linux-gnu/CMakeFiles 
/<>/obj-x86_64-linux-gnu/CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
make -f ftp/CMakeFiles/netkit-ftp.dir/build.make 
ftp/CMakeFiles/netkit-ftp.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/ftp 
/<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/ftp 
/<>/obj-x86_64-linux-gnu/ftp/CMakeFiles/netkit-ftp.dir/DependInfo.cmake
 --color=
Scanning dependencies of target netkit-ftp
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f ftp/CMakeFiles/netkit-ftp.dir/build.make 
ftp/CMakeFiles/netkit-ftp.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 28%] Building C object ftp/CMakeFiles/netkit-ftp.dir/cmdtab.c.o
[ 28%] Building C object ftp/CMakeFiles/netkit-ftp.dir/cmds.c.o
[ 42%] Building C object ftp/CMakeFiles/netkit-ftp.dir/domacro.c.o
[ 57%] Building C object ftp/CMakeFiles/netkit-ftp.dir/ftp.c.o
cd /<>/obj-x86_64-linux-gnu/ftp && /usr/bin/cc   -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D__USE_READLINE__   -o 
CMakeFiles/netkit-ftp.dir/cmdtab.c.o   -c /<>/ftp/cmdtab.c
cd /<>/obj-x86_64-linux-gnu/ftp && /usr/bin/cc   -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D__USE_READLINE__   -o 
CMakeFiles/netkit-ftp.dir/cmds.c.o   -c /<>/ftp/cmds.c
cd /<>/obj-x86_64-linux-gnu/ftp && /usr/bin/cc   -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D__USE_READLINE__   -o 
CMakeFiles/netkit-ftp.dir/domacro.c.o   -c /<>/ftp/domacro.c
cd /<>/obj-x86_64-linux-gnu/ftp && /usr/bin/cc   -g -O2 
-fdebug-prefix-map=/<>=. 

Bug#969665: marked as done (breezy-debian breaks silver-platter autopkgtest: cannot import name 'MissingUpstreamTarball')

[Debian Bug Tracking System]

Your message dated Tue, 15 Sep 2020 11:15:56 +
with message-id <20200915111556.ga3512...@jelmer.uk>
and subject line Fixed in newer silver-platter
has caused the Debian Bug report #969665,
regarding breezy-debian breaks silver-platter autopkgtest: cannot import name 
'MissingUpstreamTarball'
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.)


-- 
969665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: breezy-debian, silver-platter
Control: found -1 breezy-debian/2.8.41
Control: found -1 silver-platter/0.3.0+git20200611.b4292bf-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of breezy-debian the autopkgtest of silver-platter
fails in testing when that autopkgtest is run with the binary packages
of breezy-debian from unstable. It passes when run with only packages
from testing. In tabular form:

   passfail
breezy-debian  from testing2.8.41
silver-platter from testing0.3.0+git20200611.b4292bf-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of breezy-debian to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=breezy-debian

https://ci.debian.net/data/autopkgtest/testing/amd64/s/silver-platter/6927426/log.gz

autopkgtest [05:09:59]: test testsuite: [---
EEEfailed to open trace file: [Errno 13] Permission denied:
'/you-should-use-TestCaseInTempDir-if-you-need-a-log-file'
/usr/lib/python3/dist-packages/breezy/bzr/pack_repo.py:585:
ResourceWarning: unclosed file <_io.BufferedReader
name='/tmp/testbzr-vqrhbhdy.tmp/silver_platter.tests.test_proposal.CheckProposalDiffGitTests.test_changes/work/proposal/.git/objects/pack/pack-a944217260120cc487bb613d97f39d7dd043d40d.idx'>
  self.data_access = _DirectPackAccess(self.index_to_pack,
ResourceWarning: Enable tracemalloc to get the object allocation traceback
/usr/lib/python3/dist-packages/breezy/bzr/pack_repo.py:585:
ResourceWarning: unclosed file <_io.BufferedReader
name='/tmp/testbzr-vqrhbhdy.tmp/silver_platter.tests.test_proposal.CheckProposalDiffGitTests.test_indep/work/proposal/.git/objects/pack/pack-a944217260120cc487bb613d97f39d7dd043d40d.idx'>
  self.data_access = _DirectPackAccess(self.index_to_pack,
ResourceWarning: Enable tracemalloc to get the object allocation traceback
/usr/lib/python3/dist-packages/breezy/bzr/pack_repo.py:585:
ResourceWarning: unclosed file <_io.BufferedReader
name='/tmp/testbzr-vqrhbhdy.tmp/silver_platter.tests.test_proposal.CheckProposalDiffGitTests.test_indep/work/proposal/.git/objects/pack/pack-cf8e733fc2cf0053b75a6dd2db57ab071e1bbb2b.idx'>
  self.data_access = _DirectPackAccess(self.index_to_pack,
ResourceWarning: Enable tracemalloc to get the object allocation traceback
/usr/lib/python3/dist-packages/breezy/bzr/pack_repo.py:585:
ResourceWarning: unclosed file <_io.BufferedReader
name='/tmp/testbzr-vqrhbhdy.tmp/silver_platter.tests.test_proposal.CheckProposalDiffGitTests.test_no_new_commits/work/proposal/.git/objects/pack/pack-a944217260120cc487bb613d97f39d7dd043d40d.idx'>
  self.data_access = _DirectPackAccess(self.index_to_pack,
ResourceWarning: Enable tracemalloc to get the object allocation traceback
/usr/lib/python3/dist-packages/breezy/bzr/pack_repo.py:585:
ResourceWarning: unclosed file <_io.BufferedReader
name='/tmp/testbzr-vqrhbhdy.tmp/silver_platter.tests.test_proposal.CheckProposalDiffGitTests.test_no_op_commits/work/proposal/.git/objects/pack/pack-a944217260120cc487bb613d97f39d7dd043d40d.idx'>
  self.data_access = _DirectPackAccess(self.index_to_pack,
ResourceWarning: Enable tracemalloc to get the object allocation traceback

==
ERROR: test_debian (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: test_debian
Traceback (most recent call last):
  File "/usr/lib/python3.8/unittest/loader.py", line 154, in

Bug#951508: A patch file

[Aaron Zauner (azet)]

Hi,

If anyone wants to take over I'm more than fine with that. The amount of work I 
have at the moment barely permits me from maintaining projects. It's most 
sensible that someone actively using this project on Debian maintains it, as 
is, I'm not using it much anymore and am not working in HPC at the moment. The 
bug should definitely reported upstream. Upgrading the package should be fairly 
simple though - the dependencies are already in place, as are simple tests/git 
integration etc.: https://github.com/azet/lmod-deb

Thanks,
Aaron

> On 15.09.2020, at 09:33, Lucas Nussbaum  wrote:
> 
> retitle 951508 lmod: broken on all architectures except x86_64 (wrong search 
> path)
> severity 951508 serious
> thanks
> 
> Hi,
> 
> We ran into the same bug on an arm64 system, so it looks like lmod is
> broken on all architectures except x86_64. I'm updating the bug title
> and the severity to reflect that.
> 
> I'm attaching the diffoscope output that shows that the generated
> packages are indeed different on amd64 and arm64.
> 
> A simple fix would be to turn this package into an Architecture:any
> package.  But indeed, it should probably be reported (and fixed) upstream.
> 
>> On 17/02/20 at 19:49 +0100, Aaron Zauner wrote:
>> Since I'm barely keeping this package updated I'd suggest that you use the
>> upstream Lmod project source with the dependencies that come with this
>> package, you'll get more bug fixes, Performance and features out of it in a
>> production environment. That's what we used to do on live HPC systems since
>> a lot of software needs to be built by hand outside of the distro packaging
>> anyway.
> 
> Err, if this is the case, maybe you should mark this package as orphaned
> or RFA? I'm also Ccing people who uploaded NMUs for the package. Maybe
> someone is interested in taking over.
> 
> Lucas
> 

Bug#970336: marked as done (ecl breaks cl-contextl autopkgtest: not of the expected type SYMBOL)

[Debian Bug Tracking System]

Your message dated Tue, 15 Sep 2020 09:33:32 +
with message-id 
and subject line Bug#970336: fixed in cl-contextl 1:20200201.git5d18a71-1
has caused the Debian Bug report #970336,
regarding ecl breaks cl-contextl autopkgtest: not of the expected type SYMBOL
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.)


-- 
970336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970336
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ecl, cl-contextl
Control: found -1 ecl/20.4.24+ds-1
Control: found -1 cl-contextl/1:20160313.git5894fba-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of ecl the autopkgtest of cl-contextl fails in
testing when that autopkgtest is run with the binary packages of ecl
from unstable. It passes when run with only packages from testing. In
tabular form:

   passfail
eclfrom testing20.4.24+ds-1
cl-contextlfrom testing1:20160313.git5894fba-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of ecl to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=ecl

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cl-contextl/7008359/log.gz

;;;
;;; Compiling figure-editor-2.lisp.
;;; OPTIMIZE levels: Safety=2, Space=0, Speed=3, Debug=0
;;;
;;; End of Pass 1.
;;; Finished compiling figure-editor-2.lisp.
;;;
real time : 17.420 secs
run time  : 20.101 secs
gc count  : 612 times
consed: 2707204576 bytes
real time : 18.996 secs
run time  : 21.757 secs
gc count  : 652 times
consed: 2886437424 bytes

:DONE
:DONE An error occurred during initialization:
In function SYMBOL-VALUE, the value of the only argument is
  "Dr. Jekyll"
which is not of the expected type SYMBOL.



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: cl-contextl
Source-Version: 1:20200201.git5d18a71-1
Done: =?utf-8?q?S=C3=A9bastien_Villemot?= 

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

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated cl-contextl 
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, 15 Sep 2020 11:15:37 +0200
Source: cl-contextl
Architecture: source
Version: 1:20200201.git5d18a71-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Common Lisp Team 
Changed-By: Sébastien Villemot 
Closes: 970336
Changes:
 cl-contextl (1:20200201.git5d18a71-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream snapshot
   * Bump to debhelper 13
   * Bump to S-V 4.5.0
   * Disable ecl autopkgtest, it breaks with ecl 20.4.24. In any case,
 upstream explicitly says in README.md that ecl support is currently
 broken. (Closes: #970336)
Checksums-Sha1:
 ba7a0d44b30261839bb0cc8730de208db1232d8c 2106 
cl-contextl_20200201.git5d18a71-1.dsc
 eb17f918cadf504391cdcad579fd6e44a1f7d275 22724 
cl-contextl_20200201.git5d18a71.orig.tar.xz
 62c574128a6653da3a80a2de489452f83bbb2ee9 4232 
cl-contextl_20200201.git5d18a71-1.debian.tar.xz
 5e1c19f5923fb4c4ea26a725acb06f7c4a9b2033 5451 
cl-contextl_20200201.git5d18a71-1_amd64.buildinfo
Checksums-Sha256:
 47f16866be7aac3519f23c739317142514776a5edb154641c61f23c2b08bb813 2106 
cl-contextl_20200201.git5d18a71-1.dsc
 7ad1a3cdfe1b813e6dfe6f74700462cdbc596b1afa8db5d860c5c22cd8ca7e77 22724 
cl-contextl_20200201.git5d18a71.orig.tar.xz
 b24afebb40bcf2a9a72915647a4ebf7d97ecdf84f7372996cbcae16f0c73e5e6 4232 

Bug#970340: rna-star: autopkgtest regression: --genomeSAindexNbases 8 is too large for the genome size=99940

[Andreas Tille]

Hi Sascha,

you once wrote that test.  Do you have any idea how to fix it?

Steffen, you know that package.  Any idea what to do?

Kind regards

   Andreas.

On Mon, Sep 14, 2020 at 10:15:12PM +0200, Paul Gevers wrote:
> Source: rna-star
> Version: 2.7.5c+dfsg-1
> X-Debbugs-CC: debian...@lists.debian.org
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: regression
> 
> Dear maintainer(s),
> 
> With a recent upload of rna-star the autopkgtest of rna-star fails in
> testing when that autopkgtest is run with the binary packages of
> rna-star from unstable. It passes when run with only packages from
> testing. In tabular form:
> 
>passfail
> rna-star   from testing2.7.5c+dfsg-1
> all others from testingfrom testing
> 
> I copied some of the output at the bottom of this report.
> 
> Currently this regression is blocking the migration to testing [1]. Can
> you please investigate the situation and fix it?
> 
> More information about this bug and the reason for filing it can be found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
> 
> Paul
> 
> [1] https://qa.debian.org/excuses.php?package=rna-star
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/r/rna-star/7008363/log.gz
> 
> autopkgtest [20:08:01]: test command1: [---
> Sep 13 20:08:01 . started STAR run
> Sep 13 20:08:01 ... starting to generate Genome files
> Sep 13 20:08:01 . processing annotations GTF
> ! WARNING: --genomeSAindexNbases 8 is too large for the genome
> size=99940, which may cause seg-fault at the mapping step. Re-run genome
> generation with recommended --genomeSAindexNbases 7
> Sep 13 20:08:01 ... starting to sort Suffix Array. This may take a long
> time...
> Sep 13 20:08:01 ... sorting Suffix Array chunks and saving them to disk...
> Sep 13 20:08:01 ... loading chunks from disk, packing SA...
> Sep 13 20:08:01 ... finished generating suffix array
> Sep 13 20:08:01 ... generating Suffix Array index
> Sep 13 20:08:01 ... completed Suffix Array index
> Sep 13 20:08:01 ... writing Genome to disk ...
> Sep 13 20:08:01 ... writing Suffix Array to disk ...
> Sep 13 20:08:01 ... writing SAindex to disk
> Sep 13 20:08:01 . finished successfully
> Sep 13 20:08:01 . started STAR run
> Sep 13 20:08:01 . loading genome
> Sep 13 20:08:01 . started mapping
> Sep 13 20:08:02 . finished mapping
> Sep 13 20:08:02 . finished successfully
> autopkgtest [20:08:02]: test command1: ---]
> autopkgtest [20:08:02]: test command1:  - - - - - - - - - - results - -
> - - - - - - - -
> command1 FAIL stderr: ! WARNING: --genomeSAindexNbases 8
> is too large for the genome size=99940, which may cause seg-fault at the
> mapping step. Re-run genome generation with recommended
> --genomeSAindexNbases 7
> 




> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging


-- 
http://fam-tille.de

Bug#970335: marked as done (ecl breaks cffi autopkgtest: Don't know how to REQUIRE rt..)

[Debian Bug Tracking System]

Your message dated Tue, 15 Sep 2020 09:18:26 +
with message-id 
and subject line Bug#970335: fixed in cffi 1:0.22.1-2
has caused the Debian Bug report #970335,
regarding ecl breaks cffi autopkgtest: Don't know how to REQUIRE rt..
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.)


-- 
970335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ecl, cffi
Control: found -1 ecl/20.4.24+ds-1
Control: found -1 cffi/1:0.22.1-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of ecl the autopkgtest of cffi fails in testing
when that autopkgtest is run with the binary packages of ecl from
unstable. It passes when run with only packages from testing. In tabular
form:

   passfail
eclfrom testing20.4.24+ds-1
cffi   from testing1:0.22.1-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of ecl to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=ecl

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cffi/7008137/log.gz

;;; Compiling
/usr/share/common-lisp/source/bordeaux-threads/src/impl-ecl.lisp.
;;; OPTIMIZE levels: Safety=2, Space=0, Speed=3, Debug=0
;;;
;;; End of Pass 1.
;;; Finished compiling
/usr/share/common-lisp/source/bordeaux-threads/src/impl-ecl.lisp.
;;;
;;;
;;; Compiling
/usr/share/common-lisp/source/bordeaux-threads/src/default-implementations.lisp.
;;; OPTIMIZE levels: Safety=2, Space=0, Speed=3, Debug=0
;;;
;;; End of Pass 1.
;;; Finished compiling
/usr/share/common-lisp/source/bordeaux-threads/src/default-implementations.lisp.
;;;
An error occurred during initialization:
Module error: Don't know how to REQUIRE rt..



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: cffi
Source-Version: 1:0.22.1-2
Done: =?utf-8?q?S=C3=A9bastien_Villemot?= 

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

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated cffi 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, 15 Sep 2020 10:54:27 +0200
Source: cffi
Architecture: source
Version: 1:0.22.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Common Lisp Team 
Changed-By: Sébastien Villemot 
Closes: 970335
Changes:
 cffi (1:0.22.1-2) unstable; urgency=medium
 .
   * Add Depends on cl-rt for ecl autopkgtest. Since ecl 20.4.24, the rt
 contrib is no longer built by default. (Closes: #970335)
Checksums-Sha1:
 4858853fb31f89bf2830c63c063a75c4109b0c66 2351 cffi_0.22.1-2.dsc
 1db0c1829b69b65399a225a03652f3c263216456 544184 cffi_0.22.1-2.debian.tar.xz
 59840a856c30b1e2e74713301f4de43901745dd3 7885 cffi_0.22.1-2_amd64.buildinfo
Checksums-Sha256:
 a5a68181bcb66635fbce74bb326f3b9dd42cee20a1103b8d375d5bd4b130eae8 2351 
cffi_0.22.1-2.dsc
 884f426beaa2a55d81610dbc5f8bf6063ff7f7f68cdf0965f35a0165a9d7135b 544184 
cffi_0.22.1-2.debian.tar.xz
 a48f2150a59721e84469574ffcd770e5686232af5f1f174c6e60d894e325d754 7885 
cffi_0.22.1-2_amd64.buildinfo
Files:
 3f2ce23d069129e3afb3bfa8e3711e4a 2351 lisp optional cffi_0.22.1-2.dsc
 b317bd7ca1d519df67223ca85f30acdd 544184 lisp optional 
cffi_0.22.1-2.debian.tar.xz
 c1d976e2cfd48f15720af62b7610b403 7885 lisp optional 
cffi_0.22.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAl9ggowACgkQLOzpNQ7O

Bug#969596: marked as done (src:minimap2: fails to migrate to testing for too long: FTBFS on multiple arches)

[Debian Bug Tracking System]

Your message dated Tue, 15 Sep 2020 09:18:32 +
with message-id 
and subject line Bug#969596: fixed in minimap2 2.17+dfsg-12
has caused the Debian Bug report #969596,
regarding src:minimap2: fails to migrate to testing for too long: FTBFS on 
multiple 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.)


-- 
969596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: minimap2
Version: 2.17+dfsg-9
Severity: serious
Control: close -1 2.17+dfsg-11
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:minimap2 in
its current version in unstable has been trying to migrate for 60 days
[2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=minimap2




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: minimap2
Source-Version: 2.17+dfsg-12
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated minimap2 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, 15 Sep 2020 10:54:02 +0200
Source: minimap2
Architecture: source
Version: 2.17+dfsg-12
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 969596
Changes:
 minimap2 (2.17+dfsg-12) unstable; urgency=medium
 .
   [ Michael Hudson-Doyle ]
   * d/patches/python-sse4-arch.patch: Only pass -msse4.1 to the compiler on
 amd64.
 Closes: #969596
Checksums-Sha1:
 f2441f2543e8f50d6d205ef0b3eb84367d940166 2268 minimap2_2.17+dfsg-12.dsc
 f394b7717cfc7fe3181707c2b5b4d84a346e1d2a 10708 
minimap2_2.17+dfsg-12.debian.tar.xz
 b03798eabe72817e9b97fea2b1a0bd8c68ea93ad 14432 
minimap2_2.17+dfsg-12_amd64.buildinfo
Checksums-Sha256:
 eae8e16314e59e197ac34c2007446908598c8d8644ce6c8dfd758d14d5fd0276 2268 
minimap2_2.17+dfsg-12.dsc
 78218306d62db5036bf00f0b48f01bd07492920e1aa3b5e7558ea0274e2aa147 10708 
minimap2_2.17+dfsg-12.debian.tar.xz
 e0c31d1bbf29755d5bdc6b74b4149c9a1e18d8ee7a387d43c7b4778a7dc1a881 14432 
minimap2_2.17+dfsg-12_amd64.buildinfo
Files:
 9cd0433e1e1ae827d9008ccada22c56b 2268 science optional 
minimap2_2.17+dfsg-12.dsc
 dc1b8a1ae2921c4ed1ad850e5723409f 10708 science optional 
minimap2_2.17+dfsg-12.debian.tar.xz
 debd23359f4471c8c8d72caf31644907 14432 science optional 
minimap2_2.17+dfsg-12_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl9gghERHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFF8Q/+JKx6jysCg5IoIM20UMDB6br6N380pKAT
dFiRxdcmKyQ4D20L4sBi0N//JIM33n0vaaiKuJWf53L+S6j7OUAI+PjfTQ3arod9

Processed: reassign 970336 to cl-contextl

[Debian Bug Tracking System]

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

> reassign 970336 cl-contextl 1:20160313.git5894fba-1
Bug #970336 [src:ecl, src:cl-contextl] ecl breaks cl-contextl autopkgtest: not 
of the expected type SYMBOL
Bug reassigned from package 'src:ecl, src:cl-contextl' to 'cl-contextl'.
No longer marked as found in versions cl-contextl/1:20160313.git5894fba-1 and 
ecl/20.4.24+ds-1.
Ignoring request to alter fixed versions of bug #970336 to the same values 
previously set
Bug #970336 [cl-contextl] ecl breaks cl-contextl autopkgtest: not of the 
expected type SYMBOL
Marked as found in versions cl-contextl/1:20160313.git5894fba-1.
> thanks
Stopping processing here.

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

Processed: editline: Please remove in favour of libedit

[Debian Bug Tracking System]

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

> severity 967909 serious
Bug #967909 [src:editline] editline: Please remove in favour of libedit
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

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

Processed: reassign 970335 to cffi

[Debian Bug Tracking System]

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

> reassign 970335 cffi 1:0.22.1-1
Bug #970335 [src:ecl, src:cffi] ecl breaks cffi autopkgtest: Don't know how to 
REQUIRE rt..
Bug reassigned from package 'src:ecl, src:cffi' to 'cffi'.
No longer marked as found in versions cffi/1:0.22.1-1 and ecl/20.4.24+ds-1.
Ignoring request to alter fixed versions of bug #970335 to the same values 
previously set
Bug #970335 [cffi] ecl breaks cffi autopkgtest: Don't know how to REQUIRE rt..
There is no source info for the package 'cffi' at version '1:0.22.1-1' with 
architecture ''
Unable to make a source version for version '1:0.22.1-1'
Marked as found in versions 1:0.22.1-1.
> thanks
Stopping processing here.

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

Bug#937255: pbgenomicconsensus: Python2 removal in sid/bullseye

[Andreas Tille]

Hi Moritz,

On Mon, Aug 31, 2020 at 08:59:37PM +0200, Moritz Mühlenhoff wrote:
> On Fri, Aug 30, 2019 at 07:30:23AM +, Matthias Klose wrote:
> > Package: src:pbgenomicconsensus
> > Version: 2.3.2-5
> > 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
> 
> Upstream development seems to have stalled, let's remove?

Yes, lets remove.  Nobody explicitly answered my call for comments.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#970341: rampler: autopkgtest failure on arm64:

[Pollet Obuya]

unsubscribe

On Mon, Sep 14, 2020 at 11:21 PM Paul Gevers  wrote:

> Source: rampler
> Version: 1.1.1-2
> X-Debbugs-CC: debian...@lists.debian.org
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: fails-always
>
> Dear maintainer(s),
>
> You recently added an autopkgtest to your package rampler, great.
> However, it fails on arm64. Currently this failure is blocking the
> migration to testing [1]. Can you please investigate the situation and
> fix it?
>
> I copied some of the output at the bottom of this report. The test could
> be a bit more verbose?
>
> More information about this bug and the reason for filing it can be found
> on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
>
> Paul
>
> [1] https://qa.debian.org/excuses.php?package=rampler
>
>
> https://ci.debian.net/data/autopkgtest/testing/amd64/r/rampler/6794192/log.gz
>
> autopkgtest [03:14:35]: test run-unit-test: [---
>  [93m [1mPreparation [0m
>  [92m [1mPassed [0m
>
>  [93m [1mTest 1 [0m
> autopkgtest [03:14:35]: test run-unit-test: ---]
>
>

Bug#963827: marked as done ([virtualbox] guests limited to 800x600)

[Debian Bug Tracking System]

Your message dated Tue, 15 Sep 2020 10:08:05 +0200
with message-id <816ecdb0-a1be-c34b-4e0b-a94305115...@debian.org>
and subject line Re: [virtualbox] guests limited to 800x600
has caused the Debian Bug report #963827,
regarding [virtualbox] guests limited to 800x600
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.)


-- 
963827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:virtualbox
Version: 6.1.10-dfsg-1
Severity: important

After installing a handful of updates in a Sid guest and rebooting it,
it's now stuck with an unusable display area of 800x600.
--- End Message ---
--- Begin Message ---
On Tue, 8 Sep 2020 12:55:11 +0200 Gianfranco Costamagna 
 wrote:
> Hello,
> 
> 
> On Sat, 27 Jun 2020 23:25:26 +0100 Lyndon Brown  wrote:
> > Package: src:virtualbox
> > Version: 6.1.10-dfsg-1
> > Severity: important
> > 
> > After installing a handful of updates in a Sid guest and rebooting it,
> > it's now stuck with an unusable display area of 800x600.
> > 
> 
> should be fixed now
> 
> G.

Closing

> 
> --- End Message ---

Processed: Re: Bug#951508: A patch file

[Debian Bug Tracking System]

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

> retitle 951508 lmod: broken on all architectures except x86_64 (wrong search 
> path)
Bug #951508 [lmod] lmod: wrong search path on PowerPC system
Changed Bug title to 'lmod: broken on all architectures except x86_64 (wrong 
search path)' from 'lmod: wrong search path on PowerPC system'.
> severity 951508 serious
Bug #951508 [lmod] lmod: broken on all architectures except x86_64 (wrong 
search path)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#970355: syslog-ng : segfault at 0 ip 00007fa46a2bf7b2 sp 00007ffed353fb30 error 6 in libsyslog-ng-3.19.so.0.0.0[7fa46a2a9000+5a000]

[Jean-Marc LACROIX]

Package: syslog-ng
Version: 3.19.1-5
Severity: grave

Dear maintainers,

On amd64, i have following error


==> /var/log/syslog-ng/current_logs/BY_FACILITY.kern.notice.log <==
2020-09-15T08:25:53+02:00 s_dev_kernel_kmsg@asus-190 kernel: 
6,35313,87037029084,-;syslog-ng[10311]: segfault at 0 ip 
7fa46a2bf7b2 sp 7ffed353fb30 error 6 in 
libsyslog-ng-3.19.so.0.0.0[7fa46a2a9000+5a000]
2020-09-15T08:25:53+02:00 s_dev_kernel_kmsg@asus-190 kernel: 
6,35314,87037029092,-;Code: e8 c3 9b fe ff 4c 89 e7 e8 eb dc fe ff 48 89 
c7 e8 23 ca fe ff e9 15 ff ff ff 66 0f 1f 44 00 00 48 8b 83 f0 00 00 00 
48 89 df  00 00 00 00 00 48 83 c4 08 5b 5d 41 5c 41 5d e9 b9 fc ff ff 66


About the curent configuration, there is no disc full...
ansible@asus-190:~$ df
Sys. de fichiers  blocs de 1K   Utilisé Disponible 
Uti% Monté sur
udev  6015136 06015136 
0% /dev
tmpfs 1213460  29241210536 
1% /run
/dev/mapper/vg_debian-lv_rootfs_crypt  927000134336 728360 
16% /
/dev/mapper/vg_debian-lv_usr  7511832   57149601434140 
80% /usr
tmpfs5120 4   5116 
1% /run/lock
tmpfs 2426900 571242369776 
3% /dev/shm
/dev/mapper/vg_debian-lv_boot  463826193086 242273 
45% /boot
/dev/sda2   98304 39534  58770 
41% /boot2/efi
/dev/sdb1  191551  5199 186352 
3% /boot/efi
/dev/sdb5 2817056   1688848 965392 
64% /debian_rescue
/dev/mapper/vg_debian-lv_home80388420  741911722894992 
97% /home
/dev/mapper/vg_debian-lv_tmp   943128 82076 795928 
10% /tmp
/dev/mapper/vg_debian-lv_var   860591  7183 808724 
1% /var
/dev/mapper/vg_debian-lv_var_cache 863632140484 667980 
18% /var/cache
/dev/mapper/vg_debian-lv_var_lib   959909 69128 842002 
8% /var/lib
/dev/mapper/vg_debian-lv_var_lib_apt  1057092431004 563584 
44% /var/lib/apt
/dev/mapper/vg_debian-lv_var_log   560120225992 293132 
44% /var/log
cgroup6067296 06067296 
0% /sys/fs/cgroup
/dev/sde3   862818100 120357724  698561908 
15% /mnt/backup

ansible@asus-190:~$

My syslog configuration is in attached file

Thanks in advance for your help

Jean-Marc


syslog-ng-debian-buster-10.5-bug-segfault.tar.gz
Description: application/gzip