Bug#983478: Bug#981513: courier: please replace fam with gamin

[Glenn Strauss]

On Wed, Mar 03, 2021 at 11:23:41AM +0100, Markus Wanner wrote:
> On 03.03.21 09:21, Glenn Strauss wrote:
> > If there is any remaining concern about upgrade compatibility,
> 
> ..none from my side.  Courier would simply depend on gamin only.  I don't
> see why that would cause issues during upgrades.
> 
> > In Bullseye, change the fam package to import the gamin source, and
> > then bump the fam package version number.  The fam package would
> > actually be the same as gamin, and upgrades would avoid any packaging
> > system deficiencies in choosing between gamin and fam for upgrade.
> 
> That sounds very confusing and outright wrong, IMO.  What's wrong with just
> dropping fam?  (Whether right now for Bullseye or at any later point in
> time...)

Almost as wrong as leaving a bug like #510368 open for 12 years? /s
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510368

Yes, I agree that FAM should be dropped.  Markus, I do not understand
why you were asked to revert the change from gamin back to FAM.

If courier and kcoreaddons change to use gamin, then FAM will not be
used and 12-year-old bug #510368 gets fixed.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981513 courier
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981515 kcoreaddons

Adrian: is there a known issue that you are trying to address by asking
courier to revert to use FAM (#983478)?  Or is that theoretical?

OTOH, there are many real bugs regarding FAM / gamin conflicts which
get resolved when FAM gets dropped.

Was #983478 filed before it was clear that remaining packages could
convert to use gamin?

(incomplete list of FAM and gamin conflicts)

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=348563 (from 2006!)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510368 (from 2009!)

courier:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599682 (from 2011!)
  (solution: replace FAM with gamin)

lighttpd conflicts with FAM and gamin
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521274
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539962
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545576
I am an upstream developer of lighttpd and the conflicts were reported
to me last Aug 2020.  I posted a patch with a solution 4 days later.
https://salsa.debian.org/debian/lighttpd/-/merge_requests/18
As an upstream developer, I am absolutely appalled at how long the
FAM/gamin conflict has remained in Debian, and subsequently Ubuntu
and derivatives.  Last Oct, I did the research for Debian in
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966273
which, of course, was ignored until Bullseye went to start freeze.

==> Markus, I ask that we give Adrian a chance to respond, but I see
no good reason to keep courier depending on FAM.  On the contrary,
using FAM is MORE LIKELY to lead to conflicts with other packages
that are using gamin (instead of FAM), which is now all of them
other than courier and kcoreaddons (#981515).

Cheers, Glenn

Bug#982035: Please consider reverting (i.e. re-adding dependency)

[Holger Wansing]

Control: tags 982043 + pending


Helge Kreutzmann  wrote (Thu, 25 Feb 2021 18:35:47 +0100):
> Hello Paul,
> hello Holger,
> manpages-it comes back, just from a new source package
> (manpages-l10n). The reason this was delayed is that I cannot get this
> through NEW myself, as I'm only a Debian Maintainer, so I needed a
> sponsor (Toddy is currently unavailable). This has been resolved, so
> now manpages-it is on it's way through Testing. I received positive
> signals from the release team that it will be accepted.
> 
> Currently manpages-l10n (and with it manpages-it) still hast to wait 5
> more days, before it can enter testing. (So it is already in unstable)

manpages-it is in testing now.
I have re-added manpages-it to task-italian in tasksel (in git).
Tagging #982043 as pending.
This also draws a final line at #982035 now.

> Please note, that manpages-l10n ships the following languages
> currently, so you might check tasksel if it follows suit:
> manpages-de
> manpages-es
> manpages-fr
> manpages-it
> manpages-mk
> manpages-nl
> manpages-pl
> manpages-bt-BR
> manpages-ro

Missing in tasksel are currently:
manpages-es
manpages-mk
manpages-nl
manpages-bt-BR
manpages-ro

Are these in a good condition for stable?
Should they be added to the respective language tasks?



Holger




-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#984526: [pkg-crosswire-devel] Bug#984526: sword-text-kjv: Package is non-free

[Bastian Germann]

Am 04.03.21 um 22:02 schrieb Bastian Germann:

Am 04.03.21 um 21:48 schrieb Bastian Germann:
If we want to keep a KJV module in main, we can replace the KJV with 
ebible's KJVCPB module, which comes with source. Then we have to think 
about the version number. We can also move kjv to non-free and 
introduce a new package sword-text-kjvcpb, which would not make it 
into bullseye obviously.


I just noticed that ebible actually has engKJV1769eb and engKJV2006eb, 
which both are distributed as public domain. So the best solution would 
be using engKJV2006eb, which is the same work that we already have but 
in public domain. It comes with source and has a greater version number: 
5.3. Problem solved.


As you can read in the originally linked thread, a CrossWire author 
claims that engKJV2006eb (and probably engKJV1769eb as well) being 
published as public domain is a wrong claim. If that proves to be true I 
would go for the KJVCPB. That comes without the Strong's numbers, which 
obviously seem to be the main addition by CrossWire.

Bug#984526: [pkg-crosswire-devel] Bug#984526: sword-text-kjv: Package is non-free

[Fr Cyrille]

Le 04/03/2021 à 20:12, Roberto C. Sánchez a écrit :

On Thu, Mar 04, 2021 at 06:04:13PM +0100, Bastian Germann wrote:

Source: sword-text-kjv
Severity: serious
Version: 2.10-1

sword-text-kjv is non-free in all of its versions. The details are in
https://gitlab.com/crosswire-bible-society/kjv/-/commit/0203c85010a9a


I read the thread (and looked at your changes).  This seems to a bit of
a tangled mess.  It will be a few days before I can take a closer look
and provide my thoughts.

Please add your thoughts. I just add mine ;)

Regards,

-Roberto

Bug#984554: libnginx-mod-stream-geoip: ngx_stream_geoip_module.so: undefined symbol: ngx_stream_add_variable

[Felix Lechner]

Package: libnginx-mod-stream-geoip
Version: 1.18.0-6+b1
Severity: grave
Justification: dependent package 'nginx-full' crashes and does not install

Hi,

When dist-upgrading from buster to bullseye, I ended up with a broken
nginx-full ("nginx-full is broken or not fully installed") due to:

/usr/share/nginx/modules/ngx_stream_geoip_module.so: undefined
symbol: ngx_stream_add_variable

in /etc/nginx/modules-enabled/70-mod-stream-geoip.conf:1.

Both libnginx-mod-geoip and libnginx-mod-geop2 are installed. Also,
both are present in ./modules-enabled but not in ./modules-available.
(Does that look like another bug?) The error is otherwise a mystery to
me because I also updated a few other nginx installations without
incident.

I filed this bug as "release critical" after asking about the
appropriate level on OFTC:#debian-release.

As a side note, I saw Bug#953034 ("nginx: improve dependency of
dynamic modules") but on first glance that did not look related.

For more detailed messages from 'apt -t bullseye dist-upgrade', please
see below. Thank you!

Kind regards
Felix Lechner

* * *

dpkg: dependency problems prevent configuration of nginx:
 nginx depends on nginx-core (<< 1.18.0-6.1~) | nginx-full (<<
1.18.0-6.1~) | nginx-light (<< 1.18.0-6.1~) | nginx-extras (<<
1.18.0-6.1~); however:
  Package nginx-core is not configured yet.
  Package nginx-full is not configured yet.
  Package nginx-light is not installed.
  Package nginx-extras is not installed.
 nginx depends on nginx-core (>= 1.18.0-6) | nginx-full (>= 1.18.0-6)
| nginx-light (>= 1.18.0-6) | nginx-extras (>= 1.18.0-6); however:
  Package nginx-core is not configured yet.
  Package nginx-full is not configured yet.
  Package nginx-light is not installed.
  Package nginx-extras is not installed.

dpkg: error processing package nginx (--configure):
 dependency problems - leaving unconfigured
Setting up node-resolve (1.19.0+~cs5.20.8-2) ...
Setting up node-ajv (6.12.6-2) ...
dpkg: dependency problems prevent configuration of python3-certbot-nginx:
 python3-certbot-nginx depends on nginx; however:
  Package nginx is not configured yet.
  Package nginx-full which provides nginx is not configured yet.
  Package nginx-core which provides nginx is not configured yet.

dpkg: error processing package python3-certbot-nginx (--configure):
 dependency problems - leaving unconfigured

* * * [and later on] * * *

Errors were encountered while processing:
 nginx-core
 nginx-full
 nginx
 python3-certbot-nginx
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up nginx-core (1.18.0-6+b1) ...
Job for nginx.service failed because the control process exited with error code.
See "systemctl status nginx.service" and "journalctl -xe" for details.
invoke-rc.d: initscript nginx, action "start" failed.
● nginx.service - A high performance web server and a reverse proxy server
 Loaded: loaded (/lib/systemd/system/nginx.service; enabled;
vendor preset: enabled)
 Active: failed (Result: exit-code) since Wed 2021-03-03 16:25:35
PST; 36ms ago
   Docs: man:nginx(8)
Process: 28896 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on;
master_process on; (code=exited, status=1/FAILURE)
CPU: 11ms

Mar 03 16:25:35 wallace-server.us-core.com systemd[1]: Starting A high
performance web server and a reverse proxy server...
Mar 03 16:25:35 wallace-server.us-core.com nginx[28896]: nginx:
[emerg] dlopen() "/usr/share/nginx/modules/ngx_stream_geoip_module.so"
failed (/usr/share/nginx/modules/ngx_stream_geoip_module.so: undefined
symbol: ngx_stream_add_variable) in
/etc/nginx/modules-enabled/70-mod-stream-geoip.conf:1
Mar 03 16:25:35 wallace-server.us-core.com nginx[28896]: nginx:
configuration file /etc/nginx/nginx.conf test failed
Mar 03 16:25:35 wallace-server.us-core.com systemd[1]: nginx.service:
Control process exited, code=exited, status=1/FAILURE
Mar 03 16:25:35 wallace-server.us-core.com systemd[1]: nginx.service:
Failed with result 'exit-code'.
Mar 03 16:25:35 wallace-server.us-core.com systemd[1]: Failed to start
A high performance web server and a reverse proxy server.

Bug#984526: [pkg-crosswire-devel] Bug#984526: sword-text-kjv: Package is non-free

[Bastian Germann]

Am 04.03.21 um 21:48 schrieb Bastian Germann:
If we want to keep a KJV module in main, we can replace the KJV with 
ebible's KJVCPB module, which comes with source. Then we have to think 
about the version number. We can also move kjv to non-free and introduce 
a new package sword-text-kjvcpb, which would not make it into bullseye 
obviously.


I just noticed that ebible actually has engKJV1769eb and engKJV2006eb, 
which both are distributed as public domain. So the best solution would 
be using engKJV2006eb, which is the same work that we already have but 
in public domain. It comes with source and has a greater version number: 
5.3. Problem solved.

Bug#984526: sword-text-kjv: Package is non-free

[Bastian Germann]

Am 04.03.21 um 21:07 schrieb Teus Benschop:
On Thu, 4 Mar 2021 at 20:56, Bastian Germann > wrote:


This was discussed in #338077 and found to be okay (because it is a
Commonwealth problem only). This is not the problem here. It is the
editions by CrossWire that are non-free.


If an earlier version was okayed by Crosswire to be put in the public 
domain, and to be distributed in Debian, even if later on Crosswire 
removed that earlier version from their repository, it looks to me that 
Debian can continue to distribute that earlier version.


As already mentioned, the Debian package is flawed in every released 
version. It was never put in the public domain from what I can see but 
is freely redistributable (not including edited versions).


If we want to keep a KJV module in main, we can replace the KJV with 
ebible's KJVCPB module, which comes with source. Then we have to think 
about the version number. We can also move kjv to non-free and introduce 
a new package sword-text-kjvcpb, which would not make it into bullseye 
obviously.

Bug#984548: movim: fails to upgrade from 'buster': package post-installation script subprocess returned error exit status 1

[Andreas Beckmann]

Package: movim
Version: 0.17.1-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'buster'.
It installed fine in 'buster', then the upgrade to 'bullseye' fails.

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

  Setting up movim (0.17.1-1.1) ...
  Installing new version of config file /etc/apache2/conf-available/movim.conf 
...
  Installing new version of config file /etc/nginx/snippets/movim.conf ...
  The originally selected database type is currently not installed, assuming 
this is on purpose..
  dbconfig-common: writing config to /etc/dbconfig-common/movim.conf
  Replacing config file /etc/dbconfig-common/movim.conf with new version
  Replacing config file /var/lib/movim/dbconfig.inc with new version
  dbconfig-common: flushing administrative password
  Phinx by CakePHP - https://phinx.org. [ESC][32m0.9.2-3[ESC][39m
  
  [ESC][32musing config file[ESC][39m ./phinx.php
  [ESC][32musing config parser[ESC][39m php
  [ESC][32musing migration paths[ESC][39m 
  [ESC][32m - /usr/share/movim/database/migrations[ESC][39m
  [ESC][32musing seed paths[ESC][39m 
  [ESC][32m - /usr/share/movim/database/seeds[ESC][39m
  [ESC][33mwarning[ESC][39m no environment specified, defaulting to: movim
  [ESC][32musing adapter[ESC][39m pgsql
  [ESC][32musing database[ESC][39m movim
  
  [ESC][33mIn PostgresAdapter.php line 72:[ESC][39m
  [ESC][37;41m  
 [ESC][39;49m
  [ESC][37;41m  There was a problem connecting to the database: SQLSTATE[08006] 
[7] FATAL:   [ESC][39;49m
  [ESC][37;41m   password authentication failed for user "movim"
 [ESC][39;49m
  [ESC][37;41m  FATAL:  password authentication failed for user "movim" 
 [ESC][39;49m
  [ESC][37;41m  
 [ESC][39;49m
  
  [ESC][32mmigrate [-c|--configuration CONFIGURATION] [-p|--parser PARSER] 
[-e|--environment ENVIRONMENT] [-t|--target TARGET] [-d|--date DATE] 
[-x|--dry-run][ESC][39m
  
  dpkg: error processing package movim (--configure):
   installed movim package post-installation script subprocess returned error 
exit status 1
  Processing triggers for libc-bin (2.31-9) ...
  Processing triggers for ca-certificates (20210119) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  done.
  Processing triggers for php7.4-cli (7.4.15-5+deb11u1) ...
  Errors were encountered while processing:
   movim


cheers,

Andreas


movim_0.17.1-1.1.log.gz
Description: application/gzip

Bug#984547: isenkramd failure with with "TypeError: argument should be integer or bytes-like object, not 'str'"

[Raphaël Hertzog]

Package: isenkram
Version: 0.45
Severity: serious
X-Debbugs-Cc: hert...@debian.org

I saw this in my logs:
mars 04 20:22:14 t14-buxy isenkramd.desktop[3020]: Traceback (most recent call 
last):
mars 04 20:22:14 t14-buxy isenkramd.desktop[3020]:   File "/usr/bin/isenkramd", 
line 400, in uevent_callback
mars 04 20:22:14 t14-buxy isenkramd.desktop[3020]: if not 
is_pkg_installed(pkg):
mars 04 20:22:14 t14-buxy isenkramd.desktop[3020]:   File "/usr/bin/isenkramd", 
line 340, in is_pkg_installed
mars 04 20:22:14 t14-buxy isenkramd.desktop[3020]: if 0 == line.find("ii "):
mars 04 20:22:14 t14-buxy isenkramd.desktop[3020]: TypeError: argument should 
be integer or bytes-like object, not 'str'

It looks like that the package was not fully tested in a Python 3 context
as this is a common failure when you mix binary content and text content.

Cheers,

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

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

Versions of packages isenkram depends on:
ii  gir1.2-gtk-3.0 3.24.24-3
ii  gir1.2-gudev-1.0   234-1
ii  gir1.2-notify-0.7  0.7.9-3
ii  gir1.2-packagekitglib-1.0  1.2.2-2
ii  isenkram-cli   0.45
ii  packagekit 1.2.2-2
ii  python33.9.1-1
ii  python3-gi 3.38.0-2

isenkram recommends no packages.

isenkram suggests no packages.

-- no debconf information

Bug#984526: sword-text-kjv: Package is non-free

[Teus Benschop]

On Thu, 4 Mar 2021 at 20:56, Bastian Germann 
wrote:

> This was discussed in #338077 and found to be okay (because it is a
> Commonwealth problem only). This is not the problem here. It is the
> editions by CrossWire that are non-free.
>
>
> If an earlier version was okayed by Crosswire to be put in the public
domain, and to be distributed in Debian, even if later on Crosswire removed
that earlier version from their repository, it looks to me that Debian can
continue to distribute that earlier version.

Bug#983924: GitLab 13.7.7: ERROR in 1:0 Module parse failed: Unexpected character '' (1:0)

[Mike Gabriel]

Control: tags -1 patch

Hi Praveen,

On  Mi 03 Mär 2021 16:12:47 CET, Pirate Praveen wrote:

On 2021, മാർച്ച് 3 8:17:44 PM IST, Mike Gabriel  
 wrote:

Hi Praveen,

On  Mi 03 Mär 2021 15:38:46 CET, Pirate Praveen wrote:


On 2021, മാർച്ച് 3 7:54:13 PM IST, Mike Gabriel
 wrote:

Package: gitlab
Version: 13.7.7-2~fto10+1
Severity: serious

Hi Praveen,

I can't upgrade gitlab from 13.4.7-2~fto10+1, I get the below error
messages (webpack and ttf fonts). Don't wonder about the /srv/gitlab
paths, I have symlinked /var/lib/gitlab to /srv/gitlab (which always
worked in the past) for better storage management.


Can you share output of /usr/share/gitlab/node_modules ?

It should be pointing to /var/lib/gitlab/node_modules.


It does.


There was some changes in node_modules path to adapt to yarn 2.0 and
node-modules plugin instead of yarn 1.0.


Hmmm... How can I check this. If the symlink points to
/var/lib/gitlab/node_modules, then everything is fine? Or are more
checks required?


See if old directory /var/lib/gitlab/.node_modules is still present,  
if yes, that should be removed.


If that does not fix, backup yarn.lock and truncate -s0 yarn.lock to  
regenerate it.


Try manually running yarnpkg install (see  
/usr/lib/gitlab/scripts/rake-tasks.sh ) and webpack.


Another think you can do is to remove node_modules and let yarnpkg  
recreate it.


I have now tracked this down entirely, see MR!7 on Salsa [1]. Now, the  
gitlab pkg's postinst ran through fine.


I can access my Git repos again, now, except from the source tree not  
being rendered (I see the circling circle and nothing happens). Shall  
I open a new bug for this?


Greets,
Mike

[1] https://salsa.debian.org/ruby-team/gitlab/-/merge_requests/7
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

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

>From 71152b1ab41fe622938d754c7dace079688cb769 Mon Sep 17 00:00:00 2001
From: Mike Gabriel 
Date: Thu, 4 Mar 2021 16:45:52 +0100
Subject: [PATCH 1/2] debian/patches: Use relative node_modules/ path when
 webpacking katex fonts. The libjs-katex bin:pkg brings all the required
 symlinks for webpack.js to find the font directory. (Closes: #983924).

---
 debian/patches/0740-use-packaged-modules.patch | 9 -
 1 file changed, 9 deletions(-)

diff --git a/debian/patches/0740-use-packaged-modules.patch 
b/debian/patches/0740-use-packaged-modules.patch
index 0ea35fa6f..ce31529f4 100644
--- a/debian/patches/0740-use-packaged-modules.patch
+++ b/debian/patches/0740-use-packaged-modules.patch
@@ -69,15 +69,6 @@ Use debian packaged node modules when available
  loader: 'babel-loader',
  options: {
cacheDirectory: path.join(CACHE_PATH, 'babel-loader'),
-@@ -272,7 +277,7 @@
-   },
-   {
- test: /\.(eot|ttf|woff|woff2)$/,
--include: /node_modules\/(katex\/dist\/fonts|monaco-editor)/,
-+include: 
/(node_modules\/monaco-editor|\/usr\/share\/fonts\/truetype\/katex)/,
- loader: 'file-loader',
- options: {
-   name: '[name].[contenthash:8].[ext]',
 @@ -551,19 +556,6 @@
  // enable HMR only in webpack-dev-server
  DEV_SERVER_LIVERELOAD && new webpack.HotModuleReplacementPlugin(),
-- 
2.30.1



pgpSU1MtTtxO_.pgp
Description: Digitale PGP-Signatur

Bug#984546: cpl-plugin-hawki-calib: move downloader package to contrib

[Andreas Beckmann]

Package: cpl-plugin-hawki-calib
Version: 1.8.12+dfsg-1
Severity: serious

cpl-plugin-hawki-calib is a downloader package and needs to be moved to
contrib. All other cpl-plugin-*-calib packages are already in contrib.


Andreas

Bug#984526: sword-text-kjv: Package is non-free

[Bastian Germann]

Am 04.03.21 um 20:33 schrieb Teus Benschop:

Here is an article on the copyright issues with regard to the KJV.
https://en.wikipedia.org/wiki/King_James_Version#Copyright_status

It says, among many other things that "The Authorized Version is in the
public domain in most of the world. However, in the United Kingdom, the
right to print, publish and distribute it is a royal prerogative..."

It's a bit messy, it looks. Reading over it, I am not sure that the KJV is
free to be distributed in Debian.


This was discussed in #338077 and found to be okay (because it is a 
Commonwealth problem only). This is not the problem here. It is the 
editions by CrossWire that are non-free.



Earlier faults in history are continuing to harass us and limit the word of
God somehow.
In the 17th century there was not even the concept of copyright. When 
copyright was invented, the English Crown retrospectively applied that 
concept to the KJV.

Processed: cpl-plugin-hawki-calib: hawki-kit-2.4.3*.tar.gz no longer downloadable

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2.4.6+dfsg-1
Bug #984545 [cpl-plugin-hawki-calib] cpl-plugin-hawki-calib: 
hawki-kit-2.4.3*.tar.gz no longer downloadable
Marked as fixed in versions cpl-plugin-hawki/2.4.6+dfsg-1.

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

Bug#984545: cpl-plugin-hawki-calib: hawki-kit-2.4.3*.tar.gz no longer downloadable

[Andreas Beckmann]

Package: cpl-plugin-hawki-calib
Version: 2.4.3+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: fixed -1 2.4.6+dfsg-1

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up cpl-plugin-hawki-calib (2.4.3+dfsg-1) ...
  --2021-03-04 16:54:56--  
ftp://ftp.eso.org/pub/dfs/pipelines/hawki/hawki-kit-2.4.3.tar.gz
 => '-'
  Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.54, 134.171.42.53
  Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.54|:21... connected.
  Logging in as anonymous ... Logged in!
  ==> SYST ... done.==> PWD ... done.
  ==> TYPE I ... done.  ==> CWD (1) /pub/dfs/pipelines/hawki ... done.
  ==> SIZE hawki-kit-2.4.3.tar.gz ... done.
  
  ==> PASV ... done.==> RETR hawki-kit-2.4.3.tar.gz ... 
  No such file 'hawki-kit-2.4.3.tar.gz'.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2021-03-04 16:54:56--  
ftp://ftp.eso.org/pub/dfs/pipelines/hawki/hawki-kit-2.4.3-1.tar.gz
 => '-'
  Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.53, 134.171.42.54
  Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.53|:21... connected.
  Logging in as anonymous ... Logged in!
  ==> SYST ... done.==> PWD ... done.
  ==> TYPE I ... done.  ==> CWD (1) /pub/dfs/pipelines/hawki ... done.
  ==> SIZE hawki-kit-2.4.3-1.tar.gz ... done.
  
  ==> PASV ... done.==> RETR hawki-kit-2.4.3-1.tar.gz ... 
  No such file 'hawki-kit-2.4.3-1.tar.gz'.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
[...]

cheers,

Andreas


cpl-plugin-hawki-calib_2.4.8+dfsg-2.log.gz
Description: application/gzip

Bug#984542: psgml: fails to upgrade from 'buster': install: 'psgml-api.elc' and '/usr/share/emacs/site-lisp/psgml/psgml-api.elc' are the same file

[Andreas Beckmann]

Package: psgml
Version: 1.4.0-9
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'buster'.
It installed fine in 'buster', then the upgrade to 'bullseye' fails.

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

  Setting up psgml (1.4.0-9) ...
  Install emacsen-common for emacs
  emacsen-common: Handling install of emacsen flavor emacs
  Install psgml for emacs
  install/psgml: Byte-compiling for emacs...Loading 
/etc/emacs/site-start.d/00debian.el (source)...
  
  In toplevel form:
  psgml.el:60:30:Warning: Package cl is deprecated
  psgml.el:719:26:Warning: (lambda (foo) ...) quoted with ' rather than with #'
  
  In sgml-mode:
  psgml.el:1225:52:Warning: assignment to free variable `which-func-format'
  
  In sgml-set-buffer-multibyte:
  psgml-parse.el:365:16:Warning: assignment to free variable `mc-flag'
  
  In sgml-set-active-dtd-indicator:
  psgml-parse.el:2898:47:Warning: assignment to free variable `which-func-mode'
  
  In sgml-kill-markup:
  psgml-edit.el:247:4:Warning: value returned from (/= 0 (skip-chars-forward "  
  
")) is unused
  psgml-edit.el:247:4:Warning: value returned from (= 0 (skip-chars-forward "   
  
")) is unused
  psgml-edit.el:247:4:Warning: value returned from (= (skip-chars-forward " 
  
") 0) is unused
  
  In sgml-edit-external-entity:
  psgml-edit.el:1975:62:Warning: Use `with-current-buffer' rather than
  save-excursion+set-buffer
  
  In sgml-append-to-help-buffer:
  psgml-edit.el:2177:36:Warning: Use `with-current-buffer' rather than
  save-excursion+set-buffer
  
  In sgml-show-structure:
  psgml-edit.el:2412:6:Warning: Use `with-current-buffer' rather than
  save-excursion+set-buffer
  
  In end of data:
  psgml-edit.el:2475:1:Warning: the following functions are not known to be
  defined: string-to-int, process-kill-without-query
  
  In sgml-parse-entity-type:
  psgml-dtd.el:646:8:Warning: value returned from (/= 0 (skip-chars-forward "   
  
")) is unused
  psgml-dtd.el:646:8:Warning: value returned from (= 0 (skip-chars-forward "
  
")) is unused
  psgml-dtd.el:646:8:Warning: value returned from (= (skip-chars-forward "  
  
") 0) is unused
  psgml-dtd.el:646:8:Warning: value returned from (= (skip-chars-forward "  
  
") 0) is unused
  psgml-dtd.el:646:8:Warning: value returned from (= (skip-chars-forward "  
  
") 0) is unused
  
  In sgml-write-dtd:
  psgml-dtd.el:1010:9:Warning: assignment to free variable `file-type'
  
  In end of data:
  psgml-dtd.el:1016:1:Warning: the function `string-to-int' is not known to be
  defined.
  Done compiling
  install: 'psgml-api.elc' and '/usr/share/emacs/site-lisp/psgml/psgml-api.elc' 
are the same file
  ERROR: install script from psgml package failed
  dpkg: error processing package psgml (--configure):
   installed psgml package post-installation script subprocess returned error 
exit status 1
  Processing triggers for libgdk-pixbuf-2.0-0:amd64 (2.42.2+dfsg-1) ...
  Errors were encountered while processing:
   psgml


cheers,

Andreas


psgml_1.4.0-9.log.gz
Description: application/gzip

Bug#984526: [pkg-crosswire-devel] Bug#984526: sword-text-kjv: Package is non-free

[Teus Benschop]

Here is an article on the copyright issues with regard to the KJV.
https://en.wikipedia.org/wiki/King_James_Version#Copyright_status

It says, among many other things that "The Authorized Version is in the
public domain in most of the world. However, in the United Kingdom, the
right to print, publish and distribute it is a royal prerogative..."

It's a bit messy, it looks. Reading over it, I am not sure that the KJV is
free to be distributed in Debian.

Earlier faults in history are continuing to harass us and limit the word of
God somehow.

Met vriendelijke groeten,
With kind regards,

Teus Benschop
https://freesoftwareconsultants.nl
https://bibledit.org


On Thu, 4 Mar 2021 at 20:12, Roberto C. Sánchez  wrote:

> On Thu, Mar 04, 2021 at 06:04:13PM +0100, Bastian Germann wrote:
> > Source: sword-text-kjv
> > Severity: serious
> > Version: 2.10-1
> >
> > sword-text-kjv is non-free in all of its versions. The details are in
> > https://gitlab.com/crosswire-bible-society/kjv/-/commit/0203c85010a9a
> >
> I read the thread (and looked at your changes).  This seems to a bit of
> a tangled mess.  It will be a few days before I can take a closer look
> and provide my thoughts.
>
> Regards,
>
> -Roberto
>
> --
> Roberto C. Sánchez
>
> ___
> pkg-crosswire-devel mailing list
> pkg-crosswire-de...@alioth-lists.debian.net
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-crosswire-devel
>

Bug#984526: [pkg-crosswire-devel] Bug#984526: sword-text-kjv: Package is non-free

[Roberto C . Sánchez]

On Thu, Mar 04, 2021 at 06:04:13PM +0100, Bastian Germann wrote:
> Source: sword-text-kjv
> Severity: serious
> Version: 2.10-1
> 
> sword-text-kjv is non-free in all of its versions. The details are in
> https://gitlab.com/crosswire-bible-society/kjv/-/commit/0203c85010a9a
> 
I read the thread (and looked at your changes).  This seems to a bit of
a tangled mess.  It will be a few days before I can take a closer look
and provide my thoughts.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Bug#984539: debian-security-support: dpkg hook should never fail

[Ivo De Decker]

package: debian-security-support
severity: serious

Hi,

In https://bugs.debian.org/974552 dpkg runs the debian-security-support hook
in a situation where perl is broken. This makes the hook fail, and aborts dpkg
and apt, leaving the system in a very bad state. More on the exact situation
below. Even though debian-security-support clearly isn't at fault here, the
debian-security-support should never cause dpkg/apt to fail.

Based on that, I think it might be good if debian-security-support would make
2 changes:

- in /etc/dpkg/dpkg.cfg.d/debian-security-support, make sure the hook can
  never fail (eg by adding '|| /bin/true' in the appropriate place)
- in /usr/share/debian-security-support/check-support-status.hook check if
  perl is functional before trying to do anything. If perl is not functional,
  just do nothing (and exit successfully). This would be somewhat similar to
  what glibc is doing here:
  
https://salsa.debian.org/glibc-team/glibc/commit/04373a4e6df6b3c61fa4bbf78f8409aadc7d2753

Longer term, it might be useful to investigate whether is might make more
sense to use an apt hook instead of a dpkg hook. Ideally this would allow the
user to abort the installation before the unsupported package is installed,
instead of getting a notice afterwards. Obviously this should be done in a way
that doesn't cause apt to abort in the middle of an upgrade. I don't know if
apt currently provides an appropriate hook to do this.


Some background on the issue in #974552:

In buster, libcrypt.so is shipped by libc6. In bullseye, it is shipped by
libcrypt1. During the upgrade from buster to bullseye, it seems a situation
can occur that causes the new libc6 (without libcrypt.so) to be unpacked
before the new libcrypt. At that point, libcrypt.so is missing, so anything
that needs it (like perl) is broken. Fixing this issue is what #974552 is
about.

However, it seems that in some upgrades, the debian-security-support hook is
started in such a situation where libcrypt.so is missing. The standard
assumption that perl should be functional at all times is broken by this.
Clearly, this is not caused by debian-security-support and this should be
fixed. Furthermore, there is the risk that maintainer scripts might hit the
same issue, even if debian-security-support doesn't. However, it's unclear if
the situation can be avoided in all scenarios.

If a situation occurs where the debian-security-support hook runs on a broken
system, there's no point in trying to do something useful and failing. The
best that can be done is making sure dpkg/apt can continue, hoping that the
breakage will be fixed later on.


Thanks,

Ivo

Bug#983365: [PATCH] Re: Bug#983365: linphone-desktop: chat messages

[Dennis Filder]

On Thu, Mar 04, 2021 at 12:32:20AM +0100, Bernhard Schmidt wrote:

> Cool, thanks. Would you mind discussing your findings with upstream at
> https://gitlab.linphone.org/BC/public/liblinphone ? We will need a
> freeze exception for this, having this bug confirmed by upstream would
> help a lot, cherry-picking a commit from upstream would be even better.
>
> Right now I don't plan to upload src:linphone before 4.4.21-2 has
> migrated to testing, in order to have a minimum amount of changes to be
> discussed for the freeze exception.

I'll talk to BC once my account is activated.  Also I just filed
#984534 against soci with a two-line patch that would fix the issue,
too.  The only change needed here then would be updated dependency
info.

Regards,
Dennis

Bug#983379: linux uml segfault

[Anton Ivanov]

On 04/03/2021 08:05, Benjamin Berg wrote:

On Thu, 2021-03-04 at 08:47 +0100, Johannes Berg wrote:
On Thu, 2021-03-04 at 14:38 +0900, Hajime Tazaki wrote:


Now, I don't know how to fix it (short of changing your nsswitch
configuration) - maybe we could somehow rename sem_init()? Or maybe
we
can somehow give the kernel binary a lower symbol resolution than
the
libc/libpthread.


objcopy (from binutils) can localize symbols (i.e., objcopy -L
sem_init $orig_file $new_file).  It also does renaming symbols.  But
not sure this is the ideal solution.


Yes, we started thinking about it but it was too late at night when I
replied ...

I think there's basically a way to have an external list of symbols to
export, for symbol versioning, that we could/should use to basically
not
export any of the kernel symbols out to libs.

Maybe using the ld --version-script= option here works to mark all
kernel symbols as being "local" and prevent them from being picked up
by libraries.

Benjamin


How does UML handle symbol conflicts between userspace code and Linux
kernel (like this case sem_init) ?  AFAIK, libnl has a same symbol as
Linux kernel (genlmsg_put) and others can possibly do as well.


I fear it doesn't?


I can confirm that it did and this bug is bisect-able.

with 5.7

# dd if=/dev/ubda of=/dev/null bs=1M
16384+1 records in
16384+1 records out
17179869696 bytes (17 GB, 16 GiB) copied, 10.6973 s, 1.6 GB/s

with 5.10 the speed is 2.2
5.7 with "strings from glibc" patch speed is 2.2

As we did not do anything else in this timeframe to jack up the speed from 1.6GB/s to 
2.2GB/s and as it is identical to the speed you get with the "use glibc 
strings.h" this looks like a good criteria to bisect on.

I am going to do a bisect with 5.7 "good" and 5.10 "bad" using the speed test 
as a working hypothesis.

A.




johannes


___
linux-um mailing list
linux...@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um



___
linux-um mailing list
linux...@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um



--
Anton R. Ivanov
https://www.kot-begemot.co.uk/

Processed: found 984526

[Debian Bug Tracking System]

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

> found 984526 2.9.1-4
Bug #984526 [src:sword-text-kjv] sword-text-kjv: Package is non-free
Marked as found in versions sword-text-kjv/2.9.1-4.
> found 984526 2.7-1
Bug #984526 [src:sword-text-kjv] sword-text-kjv: Package is non-free
Marked as found in versions sword-text-kjv/2.7-1.
> found 984526 2.6-1
Bug #984526 [src:sword-text-kjv] sword-text-kjv: Package is non-free
Marked as found in versions sword-text-kjv/2.6-1.
> found 984526 2.3-2
Bug #984526 [src:sword-text-kjv] sword-text-kjv: Package is non-free
Marked as found in versions sword-text-kjv/2.3-2.
>
End of message, stopping processing here.

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

Bug#984534: [PATCH] Missing type conversion hints in libsoci_sqlite3-4.0 lead to std::bad_cast exceptions in Linphone

[Dennis Filder]

Package: soci
Architecture: amd64
Version: 4.0.1-4
Severity: grave
Justification: Breaks linphone
Affects: linphone
Tags: patch upstream sid bullseye

The sqlite3 backend uses a hard-coded map of column data type names in
src/backends/sqlite3/statement.cpp as hints to convert any results
sqlite3 dynamically retyped to text to whatever the caller asked for.
Linphone uses a database schema with MySQL-specific type names that
are not in this map and thus suffers random std::bad_cast exceptions
which are at the heart of #983365 (see badcast.cpp for a reproducer).
The first attached patch adds the missing entries to the map which
fixes the issue.

The optional second patch disables the regeneration of an unneeded
config file to satisfy dpkg-source during repeated builds.

Regards,
Dennis.


badcast.cpp.gz
Description: application/gzip


02-add-mysql-ddl-types.patch.gz
Description: application/gzip


03-disable-test-access-regen.patch.gz
Description: application/gzip

Bug#984520: 'error: symbol "grub_register_command_lockdown" not found' and then lightdm fails to start

[Colin Watson]

On Thu, Mar 04, 2021 at 05:18:18PM +0100, Marco Kühnel wrote:
> after the recent update to grub2/202+dfsg1-20+deb10u4, during boot the 
> mentioned error is thrown. After that, boot continues but lightdm cannot be 
> started anymore.
> This only happens on my laptop containing two bootable hard disks. The 
> separate boot partitions share /boot/efi and from the second hard disk its 
> Ubuntu 
> installation still boots flawlessly. For the Debian installation, /boot and 
> /boot/efi are both on /dev/sda, but by default the laptop boots from /dev/sdb.

What do you mean by "the laptop boots from /dev/sdb"?  If your EFI
System Partition is on /dev/sda1, then by definition that's where the
boot loader lives, unless you're doing something else odd.  Do you just
mean that your root file system is on /dev/sdb?

> Tried: grub-install /dev/sda

In UEFI mode, grub-install ignores the device name you give it, and
always installs to the EFI System Partition on /boot/efi.

Could you please post the full output of "grub-install --debug"?

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Bug#984529: rheolef: missing Breaks+Replaces: librheolef-dev (<< 7.1)

[Andreas Beckmann]

Package: rheolef
Version: 7.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'buster'.
It installed fine in 'buster', then the upgrade to 'bullseye' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../51-rheolef_7.1-3_amd64.deb ...
  Unpacking rheolef (7.1-3) over (7.0-2+b1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-qDgNC1/51-rheolef_7.1-3_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/rheolef-config', which is also in package 
librheolef-dev 7.0-2+b1
  Preparing to unpack .../52-librheolef-dev_7.1-3_amd64.deb ...
  Unpacking librheolef-dev (7.1-3) over (7.0-2+b1) ...


cheers,

Andreas


rheolef_7.1-3.log.gz
Description: application/gzip

Processed: libcod-tools-perl: missing Breaks+Replaces: cod-tools (<< 3)

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + cod-tools
Bug #984528 [libcod-tools-perl] libcod-tools-perl: missing Breaks+Replaces: 
cod-tools (<< 3)
Added indication that 984528 affects cod-tools

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

Bug#984528: libcod-tools-perl: missing Breaks+Replaces: cod-tools (<< 3)

[Andreas Beckmann]

Package: libcod-tools-perl
Version: 3.1.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + cod-tools

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'buster'.
It installed fine in 'buster', then the upgrade to 'bullseye' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libcod-tools-perl.
  Preparing to unpack .../00-libcod-tools-perl_3.1.0+dfsg-1+b4_amd64.deb ...
  Unpacking libcod-tools-perl (3.1.0+dfsg-1+b4) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-R97pg5/00-libcod-tools-perl_3.1.0+dfsg-1+b4_amd64.deb 
(--unpack):
   trying to overwrite '/usr/share/perl5/COD/Algebra/JacobiEigen.pm', which is 
also in package cod-tools 2.3+dfsg-3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Preparing to unpack .../01-cod-tools_3.1.0+dfsg-1+b4_amd64.deb ...
  Unpacking cod-tools (3.1.0+dfsg-1+b4) over (2.3+dfsg-3) ...


cheers,

Andreas


cod-tools_3.1.0+dfsg-1+b4.log.gz
Description: application/gzip

Processed: cpl-plugin-xshoo-calib: xshoo-kit-3.2.0*.tar.gz no longer downladable

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 3.3.5+dfsg-1
Bug #984527 [cpl-plugin-xshoo-calib] cpl-plugin-xshoo-calib: 
xshoo-kit-3.2.0*.tar.gz no longer downladable
Marked as fixed in versions cpl-plugin-xshoo/3.3.5+dfsg-1.

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

Bug#984527: cpl-plugin-xshoo-calib: xshoo-kit-3.2.0*.tar.gz no longer downladable

[Andreas Beckmann]

Package: cpl-plugin-xshoo-calib
Version: 3.2.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: fixed -1 3.3.5+dfsg-1

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up cpl-plugin-xshoo-calib (3.2.0+dfsg-1) ...
  --2021-03-04 11:06:18--  
ftp://ftp.eso.org/pub/dfs/pipelines/xshooter/xshoo-kit-3.2.0.tar.gz
 => '-'
  Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.53, 134.171.42.54
  Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.53|:21... connected.
  Logging in as anonymous ... Logged in!
  ==> SYST ... done.==> PWD ... done.
  ==> TYPE I ... done.  ==> CWD (1) /pub/dfs/pipelines/xshooter ... done.
  ==> SIZE xshoo-kit-3.2.0.tar.gz ... done.
  
  ==> PASV ... done.==> RETR xshoo-kit-3.2.0.tar.gz ... 
  No such file 'xshoo-kit-3.2.0.tar.gz'.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2021-03-04 11:06:18--  
ftp://ftp.eso.org/pub/dfs/pipelines/xshooter/xshoo-kit-3.2.0-1.tar.gz
 => '-'
  Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.53, 134.171.42.54
  Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.53|:21... connected.
  Logging in as anonymous ... Logged in!
  ==> SYST ... done.==> PWD ... done.
  ==> TYPE I ... done.  ==> CWD (1) /pub/dfs/pipelines/xshooter ... done.
  ==> SIZE xshoo-kit-3.2.0-1.tar.gz ... done.
  
  ==> PASV ... done.==> RETR xshoo-kit-3.2.0-1.tar.gz ... 
  No such file 'xshoo-kit-3.2.0-1.tar.gz'.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
[...]

cheers,

Andreas


cpl-plugin-xshoo-calib_3.2.0+dfsg-1.log.gz
Description: application/gzip

Bug#984526: sword-text-kjv: Package is non-free

[Bastian Germann]

Source: sword-text-kjv
Severity: serious
Version: 2.10-1

sword-text-kjv is non-free in all of its versions. The details are in 
https://gitlab.com/crosswire-bible-society/kjv/-/commit/0203c85010a9a


For the (binary) sword module a "General public license for distribution 
for any purpose" is granted, which does not explicitly allow 
distributions of modified versions. The more verbose license text is: 
"Any copyright that might be obtained for this effort is held by 
CrossWire Bible Society (c) 2003-2016 and CrossWire Bible Society hereby 
grants a general public license to use this text for any purpose."


"Use for any purpose" does not necessarily contain modified redistribution.

The source was never in Debian versions before 2.10-1. It was recently 
published by mistake and it was assumed that the license for the binary 
module also applies to the source. Even if it did, it would still not be 
DFSG-compliant because the distribution of modified versions is not allowed.


The binary module would be perfectly fine for Debian's non-free section. 
I propose to move the last source-less version there. There is an issue 
with the version number being 2.9.1-4, which has an additional ".1" 
compared with the upstream version. This should also be fixed with the 
non-free upload, so the new non-free version should be "2.10+really2.9-1".


I prepared this suggestion at 
https://salsa.debian.org/pkg-crosswire-team/sword-text-kjv/-/tree/debian/latest 
which should be force-pushed to master (as well as the upstream and 
pristine-tar branches to their 2.9.1 versions) if we go this route.

Processed: tagging 947662

[Debian Bug Tracking System]

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

> tags 947662 - bullseye-ignore + bullseye
Bug #947662 {Done: Ying-Chun Liu (PaulLiu) } [repsnapper] 
repsnapper: depends on deprecated libpangox-1.0-0
Removed tag(s) bullseye-ignore.
Bug #947662 {Done: Ying-Chun Liu (PaulLiu) } [repsnapper] 
repsnapper: depends on deprecated libpangox-1.0-0
Added tag(s) bullseye.
> thanks
Stopping processing here.

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

Bug#984525: cpl-plugin-visir-calib: visir-kit-4.3.7*.tar.gz no longer downloadable

[Andreas Beckmann]

Package: cpl-plugin-visir-calib
Version: 4.3.7+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: fixed -1 4.3.8+dfsg-1

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up cpl-plugin-visir-calib (4.3.7+dfsg-1) ...
  --2021-03-04 11:05:30--  
ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.7.tar.gz
 => '-'
  Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.53, 134.171.42.54
  Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.53|:21... connected.
  Logging in as anonymous ... Logged in!
  ==> SYST ... done.==> PWD ... done.
  ==> TYPE I ... done.  ==> CWD (1) /pub/dfs/pipelines/visir ... done.
  ==> SIZE visir-kit-4.3.7.tar.gz ... done.
  
  ==> PASV ... done.==> RETR visir-kit-4.3.7.tar.gz ... 
  No such file 'visir-kit-4.3.7.tar.gz'.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2021-03-04 11:05:30--  
ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.7-1.tar.gz
 => '-'
  Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.53, 134.171.42.54
  Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.53|:21... connected.
  Logging in as anonymous ... Logged in!
  ==> SYST ... done.==> PWD ... done.
  ==> TYPE I ... done.  ==> CWD (1) /pub/dfs/pipelines/visir ... done.
  ==> SIZE visir-kit-4.3.7-1.tar.gz ... done.
  
  ==> PASV ... done.==> RETR visir-kit-4.3.7-1.tar.gz ... 
  No such file 'visir-kit-4.3.7-1.tar.gz'.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
[...]

cheers,

Andreas


cpl-plugin-visir-calib_4.3.7+dfsg-1.log.gz
Description: application/gzip

Processed: cpl-plugin-visir-calib: visir-kit-4.3.7*.tar.gz no longer downloadable

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 4.3.8+dfsg-1
Bug #984525 [cpl-plugin-visir-calib] cpl-plugin-visir-calib: 
visir-kit-4.3.7*.tar.gz no longer downloadable
Marked as fixed in versions cpl-plugin-visir/4.3.8+dfsg-1.

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

Bug#983365: [PATCH] Re: Bug#983365: linphone-desktop: chat messages

[David Pirotte]

Hi Bernhard,
DEnnis,

> > I finally found the bug: ...

Excellent!

Please make sure you also test a file transfer, which is part of the
chat message interface [I couldn't try since the chat msgs itself
didn't work ...], The file transfer functionality is absolutely
essential as well, afaic at least 

Thanks,
David


pgpn4RmQpxO7P.pgp
Description: OpenPGP digital signature

Bug#984524: cpl-plugin-vimos-calib: vimos-kit-3.2.3*.tar.gz no longer downloadable

[Andreas Beckmann]

Package: cpl-plugin-vimos-calib
Version: 3.2.3+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: fixed -1 3.3.0+dfsg-1

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up cpl-plugin-vimos-calib (3.2.3+dfsg-2) ...
  --2021-03-04 11:04:18--  
ftp://ftp.eso.org/pub/dfs/pipelines/vimos/vimos-kit-3.2.3.tar.gz
 => '-'
  Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.53, 134.171.42.54
  Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.53|:21... connected.
  Logging in as anonymous ... Logged in!
  ==> SYST ... done.==> PWD ... done.
  ==> TYPE I ... done.  ==> CWD (1) /pub/dfs/pipelines/vimos ... done.
  ==> SIZE vimos-kit-3.2.3.tar.gz ... done.
  
  ==> PASV ... done.==> RETR vimos-kit-3.2.3.tar.gz ... 
  No such file 'vimos-kit-3.2.3.tar.gz'.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2021-03-04 11:04:18--  
ftp://ftp.eso.org/pub/dfs/pipelines/vimos/vimos-kit-3.2.3-1.tar.gz
 => '-'
  Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.53, 134.171.42.54
  Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.53|:21... connected.
  Logging in as anonymous ... Logged in!
  ==> SYST ... done.==> PWD ... done.
  ==> TYPE I ... done.  ==> CWD (1) /pub/dfs/pipelines/vimos ... done.
  ==> SIZE vimos-kit-3.2.3-1.tar.gz ... done.
  
  ==> PASV ... done.==> RETR vimos-kit-3.2.3-1.tar.gz ... 
  No such file 'vimos-kit-3.2.3-1.tar.gz'.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
[...]

cheers,


Andreas


cpl-plugin-vimos-calib_3.2.3+dfsg-2.log.gz
Description: application/gzip

Processed: cpl-plugin-vimos-calib: vimos-kit-3.2.3*.tar.gz no longer downloadable

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 3.3.0+dfsg-1
Bug #984524 [cpl-plugin-vimos-calib] cpl-plugin-vimos-calib: 
vimos-kit-3.2.3*.tar.gz no longer downloadable
Marked as fixed in versions cpl-plugin-vimos/3.3.0+dfsg-1.

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

Processed: cpl-plugin-uves-calib: uves-kit-5.9.1*.tar.gz no longer downloadable

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 5.10.4+dfsg-1
Bug #984523 [cpl-plugin-uves-calib] cpl-plugin-uves-calib: 
uves-kit-5.9.1*.tar.gz no longer downloadable
Marked as fixed in versions cpl-plugin-uves/5.10.4+dfsg-1.

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

Bug#984523: cpl-plugin-uves-calib: uves-kit-5.9.1*.tar.gz no longer downloadable

[Andreas Beckmann]

Package: cpl-plugin-uves-calib
Version: 5.9.1+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: fixed -1 5.10.4+dfsg-1

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up cpl-plugin-uves-calib (5.9.1+dfsg-1) ...
  --2021-03-04 11:03:32--  
ftp://ftp.eso.org/pub/dfs/pipelines/uves/uves-kit-5.9.1.tar.gz
 => '-'
  Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.54, 134.171.42.53
  Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.54|:21... connected.
  Logging in as anonymous ... Logged in!
  ==> SYST ... done.==> PWD ... done.
  ==> TYPE I ... done.  ==> CWD (1) /pub/dfs/pipelines/uves ... done.
  ==> SIZE uves-kit-5.9.1.tar.gz ... done.
  
  ==> PASV ... done.==> RETR uves-kit-5.9.1.tar.gz ... 
  No such file 'uves-kit-5.9.1.tar.gz'.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2021-03-04 11:03:32--  
ftp://ftp.eso.org/pub/dfs/pipelines/uves/uves-kit-5.9.1-1.tar.gz
 => '-'
  Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.54, 134.171.42.53
  Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.54|:21... connected.
  Logging in as anonymous ... Logged in!
  ==> SYST ... done.==> PWD ... done.
  ==> TYPE I ... done.  ==> CWD (1) /pub/dfs/pipelines/uves ... done.
  ==> SIZE uves-kit-5.9.1-1.tar.gz ... done.
  
  ==> PASV ... done.==> RETR uves-kit-5.9.1-1.tar.gz ... 
  No such file 'uves-kit-5.9.1-1.tar.gz'.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
[...]


cheers,

Andreas


cpl-plugin-uves-calib_5.9.1+dfsg-1.log.gz
Description: application/gzip

Bug#984521: cpl-plugin-naco-calib: naco-kit-4.4.6*.tar.gz is no longer downloadable

[Andreas Beckmann]

Package: cpl-plugin-naco-calib
Version: 4.4.6+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: fixed -1 4.4.8+dfsg-1

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up cpl-plugin-naco-calib (4.4.6+dfsg-1) ...
  --2021-03-04 11:06:41--  
ftp://ftp.eso.org/pub/dfs/pipelines/naco/naco-kit-4.4.6.tar.gz
 => '-'
  Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.54, 134.171.42.53
  Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.54|:21... connected.
  Logging in as anonymous ... Logged in!
  ==> SYST ... done.==> PWD ... done.
  ==> TYPE I ... done.  ==> CWD (1) /pub/dfs/pipelines/naco ... done.
  ==> SIZE naco-kit-4.4.6.tar.gz ... done.
  
  ==> PASV ... done.==> RETR naco-kit-4.4.6.tar.gz ... 
  No such file 'naco-kit-4.4.6.tar.gz'.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2021-03-04 11:06:42--  
ftp://ftp.eso.org/pub/dfs/pipelines/naco/naco-kit-4.4.6-1.tar.gz
 => '-'
  Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.53, 134.171.42.54
  Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.53|:21... connected.
  Logging in as anonymous ... Logged in!
  ==> SYST ... done.==> PWD ... done.
  ==> TYPE I ... done.  ==> CWD (1) /pub/dfs/pipelines/naco ... done.
  ==> SIZE naco-kit-4.4.6-1.tar.gz ... done.
  
  ==> PASV ... done.==> RETR naco-kit-4.4.6-1.tar.gz ... 
  No such file 'naco-kit-4.4.6-1.tar.gz'.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
[...]


cheers,

Andreas


cpl-plugin-naco-calib_4.4.6+dfsg-1.log.gz
Description: application/gzip

Processed: cpl-plugin-naco-calib: naco-kit-4.4.6*.tar.gz is no longer downloadable

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 4.4.8+dfsg-1
Bug #984521 [cpl-plugin-naco-calib] cpl-plugin-naco-calib: 
naco-kit-4.4.6*.tar.gz is no longer downloadable
Marked as fixed in versions cpl-plugin-naco/4.4.8+dfsg-1.

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

Bug#984520: 'error: symbol "grub_register_command_lockdown" not found' and then lightdm fails to start

[Marco Kühnel]

Package: grub-efi-amd64
Version: 2.02+dfsg1-20+deb10u4
Severity: critical
Tags: d-i
Justification: breaks unrelated software

Hi,

after the recent update to grub2/202+dfsg1-20+deb10u4, during boot the 
mentioned error is thrown. After that, boot continues but lightdm cannot be 
started anymore.
This only happens on my laptop containing two bootable hard disks. The separate 
boot partitions share /boot/efi and from the second hard disk its Ubuntu 
installation still boots flawlessly. For the Debian installation, /boot and 
/boot/efi are both on /dev/sda, but by default the laptop boots from /dev/sdb.
Tried: grub-install /dev/sda
  
Best
Marco

-- Package-specific info:

*** BEGIN /proc/mounts
/dev/mapper/caspiansea--vg-root / ext4 rw,relatime,errors=remount-ro 0 0
/dev/mapper/caspiansea--vg-var /var ext4 rw,relatime 0 0
/dev/sda2 /boot ext2 rw,relatime 0 0
/dev/mapper/caspiansea--vg-home /home ext4 rw,relatime 0 0
/dev/mapper/caspiansea--vg-tmp /tmp ext4 rw,relatime 0 0
/dev/sdb2 /home/mac/macOS ext4 rw,relatime 0 0
/dev/sda1 /boot/efi vfat 
rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
 0 0
/dev/mapper/data_crypt /home/codecivil/data ext4 rw,relatime 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod lvm
insmod ext2
set 
root='lvmid/149bgo-7vVx-Jo0z-j1LJ-QhnL-YRKD-4hrfSc/ZGzn4Q-OPbT-4vu1-fXw5-pqed-lS5M-Ua8BXs'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root 
--hint='lvmid/149bgo-7vVx-Jo0z-j1LJ-QhnL-YRKD-4hrfSc/ZGzn4Q-OPbT-4vu1-fXw5-pqed-lS5M-Ua8BXs'
  e78fa255-2ca7-4d0b-a72e-ab2c6f4d3ea7
else
  search --no-floppy --fs-uuid --set=root e78fa255-2ca7-4d0b-a72e-ab2c6f4d3ea7
fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=1440x900
  load_video
  insmod gfxterm
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod lvm
insmod ext2
set 
root='lvmid/149bgo-7vVx-Jo0z-j1LJ-QhnL-YRKD-4hrfSc/ZGzn4Q-OPbT-4vu1-fXw5-pqed-lS5M-Ua8BXs'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root 
--hint='lvmid/149bgo-7vVx-Jo0z-j1LJ-QhnL-YRKD-4hrfSc/ZGzn4Q-OPbT-4vu1-fXw5-pqed-lS5M-Ua8BXs'
  e78fa255-2ca7-4d0b-a72e-ab2c6f4d3ea7
else
  search --no-floppy --fs-uuid --set=root e78fa255-2ca7-4d0b-a72e-ab2c6f4d3ea7
fi
insmod png
if background_image 
/usr/share/desktop-base/futureprototype-theme/grub/grub-4x3.png; then
  set color_normal=white/black
  set color_highlight=black/white
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu 
--class os $menuentry_id_option 
'gnulinux-simple-e78fa255-2ca7-4d0b-a72e-ab2c6f4d3ea7' {
load_video
outb 0x728 1
outb 0x710 2
outb 0x740 2
outb 0x750 0
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 
--hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  
d64727a5-ce33-4fd8-83be-f941be9779f9
else
  search --no-floppy --fs-uuid --set=root 
d64727a5-ce33-4fd8-83be-f94

Bug#983924: GitLab 13.7.7: ERROR in 1:0 Module parse failed: Unexpected character '' (1:0)

[Pirate Praveen]

On 2021, മാർച്ച് 4 9:31:42 PM IST, Mike Gabriel 
 wrote:
>Control: tags -1 patch
>
>Hi Praveen,
>
>On  Mi 03 Mär 2021 16:12:47 CET, Pirate Praveen wrote:
>
>> On 2021, മാർച്ച് 3 8:17:44 PM IST, Mike Gabriel  
>>  wrote:
>>> Hi Praveen,
>>>
>>> On  Mi 03 Mär 2021 15:38:46 CET, Pirate Praveen wrote:
>>>
 On 2021, മാർച്ച് 3 7:54:13 PM IST, Mike Gabriel
  wrote:
> Package: gitlab
> Version: 13.7.7-2~fto10+1
> Severity: serious
>
> Hi Praveen,
>
> I can't upgrade gitlab from 13.4.7-2~fto10+1, I get the below error
> messages (webpack and ttf fonts). Don't wonder about the /srv/gitlab
> paths, I have symlinked /var/lib/gitlab to /srv/gitlab (which always
> worked in the past) for better storage management.

 Can you share output of /usr/share/gitlab/node_modules ?

 It should be pointing to /var/lib/gitlab/node_modules.
>>>
>>> It does.
>>>
 There was some changes in node_modules path to adapt to yarn 2.0 and
 node-modules plugin instead of yarn 1.0.
>>>
>>> Hmmm... How can I check this. If the symlink points to
>>> /var/lib/gitlab/node_modules, then everything is fine? Or are more
>>> checks required?
>>
>> See if old directory /var/lib/gitlab/.node_modules is still present,  
>> if yes, that should be removed.
>>
>> If that does not fix, backup yarn.lock and truncate -s0 yarn.lock to  
>> regenerate it.
>>
>> Try manually running yarnpkg install (see  
>> /usr/lib/gitlab/scripts/rake-tasks.sh ) and webpack.
>>
>> Another think you can do is to remove node_modules and let yarnpkg  
>> recreate it.
>
>I have now tracked this down entirely, see MR!7 on Salsa [1]. Now, the  
>gitlab pkg's postinst ran through fine.

I will check it soon.

>I can access my Git repos again, now, except from the source tree not  
>being rendered (I see the circling circle and nothing happens). Shall  
>I open a new bug for this?

That looks like an issue with newer versions of ruby-rugged. Please open a bug.

>Greets,
>Mike
>
>[1] https://salsa.debian.org/ruby-team/gitlab/-/merge_requests/7

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#983748: dh-r: pkg-r-autopkgtest breaks autopkgtests

[Andreas Tille]

HI Graham,

On Thu, Mar 04, 2021 at 05:40:34PM +0200, Graham Inggs wrote:
> 
> No, the tests that britney schedules for migration are run in testing,
> and usually only the package to be tested comes from unstable.  The
> idea is to simulate what would break in testing, if this package from
> unstable were allowed to migrate.

Ahhh, this explanation is way easier to understand for me. ;-)

> > That's great anyway.  Thanks a lot for your support which makes
> > maintaining R packages way more fun. ;-)
> 
> You are welcome!

:-)

Kind regards

  Andreas.

-- 
http://fam-tille.de

Processed: cpl-plugin-giraf-calib: giraf-kit-2.16.3*.tar.gz no longer downloadable

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2.16.5+dfsg-1
Bug #984519 [cpl-plugin-giraf-calib] cpl-plugin-giraf-calib: 
giraf-kit-2.16.3*.tar.gz no longer downloadable
Marked as fixed in versions cpl-plugin-giraf/2.16.5+dfsg-1.

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

Bug#984519: cpl-plugin-giraf-calib: giraf-kit-2.16.3*.tar.gz no longer downloadable

[Andreas Beckmann]

Package: cpl-plugin-giraf-calib
Version: 2.16.3+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: fixed -1 2.16.5+dfsg-1

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up cpl-plugin-giraf-calib (2.16.3+dfsg-1) ...
  --2021-03-04 11:05:06--  
ftp://ftp.eso.org/pub/dfs/pipelines/giraffe/giraf-kit-2.16.3.tar.gz
 => '-'
  Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.53, 134.171.42.54
  Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.53|:21... connected.
  Logging in as anonymous ... Logged in!
  ==> SYST ... done.==> PWD ... done.
  ==> TYPE I ... done.  ==> CWD (1) /pub/dfs/pipelines/giraffe ... done.
  ==> SIZE giraf-kit-2.16.3.tar.gz ... done.
  
  ==> PASV ... done.==> RETR giraf-kit-2.16.3.tar.gz ... 
  No such file 'giraf-kit-2.16.3.tar.gz'.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2021-03-04 11:05:07--  
ftp://ftp.eso.org/pub/dfs/pipelines/giraffe/giraf-kit-2.16.3-1.tar.gz
 => '-'
  Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.53, 134.171.42.54
  Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.53|:21... connected.
  Logging in as anonymous ... Logged in!
  ==> SYST ... done.==> PWD ... done.
  ==> TYPE I ... done.  ==> CWD (1) /pub/dfs/pipelines/giraffe ... done.
  ==> SIZE giraf-kit-2.16.3-1.tar.gz ... done.
  
  ==> PASV ... done.==> RETR giraf-kit-2.16.3-1.tar.gz ... 
  No such file 'giraf-kit-2.16.3-1.tar.gz'.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
[...]

cheers,

Andreas


cpl-plugin-giraf-calib_2.16.3+dfsg-1.log.gz
Description: application/gzip

Bug#984474: marked as done (libbio-asn1-entrezgene-perl: missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3))

[Debian Bug Tracking System]

Your message dated Thu, 04 Mar 2021 16:33:26 +
with message-id 
and subject line Bug#984474: fixed in libbio-asn1-entrezgene-perl 1.730-2
has caused the Debian Bug report #984474,
regarding libbio-asn1-entrezgene-perl: missing Breaks+Replaces: 
libbio-perl-perl (<< 1.7.3)
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.)


-- 
984474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbio-asn1-entrezgene-perl
Version: 1.730-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'buster'.
It installed fine in 'buster', then the upgrade to 'bullseye' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libbio-asn1-entrezgene-perl.
  Preparing to unpack .../039-libbio-asn1-entrezgene-perl_1.730-1_all.deb ...
  Unpacking libbio-asn1-entrezgene-perl (1.730-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-eyjeT8/039-libbio-asn1-entrezgene-perl_1.730-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/man/man3/Bio::SeqIO::entrezgene.3pm.gz', 
which is also in package libbio-perl-perl 1.7.2-3

IIRC bioperl 1.7.3 is the version that got split up into several packages,
thus the existing B+R: libbio-perl-perl (<= 1.7.2) is insufficient.


cheers,

Andreas


bioperl-run_1.7.3-6.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libbio-asn1-entrezgene-perl
Source-Version: 1.730-2
Done: gregor herrmann 

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libbio-asn1-entrezgene-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Mar 2021 16:51:19 +0100
Source: libbio-asn1-entrezgene-perl
Architecture: source
Version: 1.730-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 984474
Changes:
 libbio-asn1-entrezgene-perl (1.730-2) unstable; urgency=medium
 .
   * Bump versioned Breaks/Replaces on libbio-perl-perl' from '<= 1.7.2' to
 '<< 1.7.3'.
 The former does not catch libbio-perl-perl 1.7.2-3 in buster.
 Thanks to Andreas Beckmann for the bug report. (Closes: #984474)
   * Update years of packaging copyright.
   * Declare compliance with Debian Policy 4.5.1.
   * Set Rules-Requires-Root: no.
   * Bump debhelper-compat to 13.
Checksums-Sha1:
 108ce5829d05c8c58f426bed01c4ce8088dfdfd6 2613 
libbio-asn1-entrezgene-perl_1.730-2.dsc
 e9cacbed6d68b6db15035dfb6108b5434702cc5c 3340 
libbio-asn1-entrezgene-perl_1.730-2.debian.tar.xz
Checksums-Sha256:
 c2055598ccf3449797b8a17d9fa4db1a7a718ed5e8710a90cbf2b4a3a24e3476 2613 
libbio-asn1-entrezgene-perl_1.730-2.dsc
 d800cfe5e006944561f660a6d39e277fccaf0f9f475c61370c158ae39ffdfd26 3340 
libbio-asn1-entrezgene-perl_1.730-2.debian.tar.xz
Files:
 bfd48d1be752b564ff89057f0e34f876 2613 perl optional 
libbio-asn1-entrezgene-perl_1.730-2.dsc
 efd6c25243fd1b293c447134cf0096c9 3340 perl optional 
libbio-asn1-entrezgene-perl_1.730-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmBBCCtfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZr5RAAg2sglXaOqPVIuEiS6HbBGwR7W6bkmD2ungyOawn8K70MZi+uaPqHKlMl
vzT17EJRfOWkATyjCknoV/CyMkXwYARqUvWDdDXZ5EMy8G/+fk36p93QE9VQ3wFe
lp3m0gISvT47Sfw0LzKVhDAzbv7Eee9ll16bqxzzku9oL8UqEZnp33E5ujExfdpn
ZrRzv74kAJD2fqxfMPuWCryH6BOaTHo0G6tjjtpDfUGTwWVQjdO7499c6dB8x8If
m1vptK1PlIWrWngUCcj1y2tZvmDXfra7Oo/GttaBWSB1LABExvrP7sTSnoO/tdv+
9291pM8Foli9Z/XVC5enVAGUYdJUs/lbCOnBVa3xEKTptXVDU

Bug#981699: thinkfan: fails on upgrade

[Evgeni Golov]

On March 4, 2021 3:50:21 PM UTC, gregor herrmann  wrote:
>On Tue, 02 Mar 2021 22:44:24 +, Thorsten Glaser wrote:
>
>> and the new one doesn’t work, and I don’t even
>> know what I’m supposed to put where. Perhaps upstream has some kind
>> of list what model needs which settings? Also, YAML is such a weird
>> format unfriendly to human editing…
>
>What "works" is to put
>
>-c /etc/thinkfan.conf
>
>into DAEMON_ARGS in /etc/default/thinkfan, i.e. use the old config.
> 
>In the meantime I've converted the old .conf to a new .yaml for my
>Thinkpad, starting from the example config in /etc and the new
>thinkfan.conf manpage.
>
>I have no good idea for handling this on upgrades; _maybe_ shipping a
>more minimal/generic /etc/thinkpad.yaml would help (the current one
>is a huge exmple file with all kinds of options and will probably not
>work for any machine); or ship it as an example and nothing in /etc
>(which of course also breaks updates but apparently there's no good
>way out of this).


Yeah, not shipping the yaml is also what David proposed in 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983727 and I think that's the 
cleanest we can go with.

FWIW, you don't need -c if there is no yaml, it will find the old conf if it's 
called thinkfan.conf automatically.

>
>
>Cheers,
>gregor
>

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

Bug#984474: marked as pending in libbio-asn1-entrezgene-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #984474 in libbio-asn1-entrezgene-perl 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/perl-team/modules/packages/libbio-asn1-entrezgene-perl/-/commit/6840411c3b47126016674ab973e01f5752368393


Bump versioned Breaks/Replaces on libbio-perl-perl' from '<= 1.7.2' to '<< 
1.7.3'.

The former does not catch libbio-perl-perl 1.7.2-3 in buster.

Thanks: Andreas Beckmann for the bug report.
Closes: #984474


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/984474

Processed: Bug#984474 marked as pending in libbio-asn1-entrezgene-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #984474 [libbio-asn1-entrezgene-perl] libbio-asn1-entrezgene-perl: missing 
Breaks+Replaces: libbio-perl-perl (<< 1.7.3)
Added tag(s) pending.

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

Processed: Re: Bug#983924: GitLab 13.7.7: ERROR in 1:0 Module parse failed: Unexpected character '' (1:0)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #983924 [gitlab] GitLab 13.7.7: ERROR in1:0 Module parse 
failed: Unexpected character '' (1:0)
Added tag(s) patch.

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

Bug#981699: thinkfan: fails on upgrade

[gregor herrmann]

On Tue, 02 Mar 2021 22:44:24 +, Thorsten Glaser wrote:

> and the new one doesn’t work, and I don’t even
> know what I’m supposed to put where. Perhaps upstream has some kind
> of list what model needs which settings? Also, YAML is such a weird
> format unfriendly to human editing…

What "works" is to put

-c /etc/thinkfan.conf

into DAEMON_ARGS in /etc/default/thinkfan, i.e. use the old config.
 
In the meantime I've converted the old .conf to a new .yaml for my
Thinkpad, starting from the example config in /etc and the new
thinkfan.conf manpage.

I have no good idea for handling this on upgrades; _maybe_ shipping a
more minimal/generic /etc/thinkpad.yaml would help (the current one
is a huge exmple file with all kinds of options and will probably not
work for any machine); or ship it as an example and nothing in /etc
(which of course also breaks updates but apparently there's no good
way out of this).


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#983748: dh-r: pkg-r-autopkgtest breaks autopkgtests

[Graham Inggs]

Hi Andreas

On Thu, 4 Mar 2021 at 16:57, Andreas Tille  wrote:
> I fail to understand this.  Before version 3.0.1+dfsg-1 has migrated to
> testing tests of this version were done in unstable, right?

No, the tests that britney schedules for migration are run in testing,
and usually only the package to be tested comes from unstable.  The
idea is to simulate what would break in testing, if this package from
unstable were allowed to migrate.

If there are breaks and versioned dependencies, britney will try to
satisfy these with additional packages from unstable.

> That's great anyway.  Thanks a lot for your support which makes
> maintaining R packages way more fun. ;-)

You are welcome!

Regards
Graham

Bug#982616: marked as done (libvoro++1: ABI break without soname change)

[Debian Bug Tracking System]

Your message dated Thu, 4 Mar 2021 15:36:21 +
with message-id <588cd250-a1b0-3934-b247-03b7a67d1...@nebulousresearch.org>
and subject line Re: [Debian-astro-maintainers] Bug#982616: Revert voro++_0.5?
has caused the Debian Bug report #982616,
regarding libvoro++1: ABI break without soname change
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.)


-- 
982616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvoro++1
Version: 0.5-1
Severity: serious
Control: affects -1 libgmsh4 src:gmsh

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gmsh/10408994/log.gz

...
gmsh: symbol lookup error: /lib/x86_64-linux-gnu/libgmsh.so.4.7: undefined 
symbol: _ZN4voro20voronoicell_neighborC1Ev
...


The missing symbol is voro::voronoicell_neighbor::voronoicell_neighbor()
--- End Message ---
--- Begin Message ---
Yes, best to revert for now, and a package with the old source has been 
uploaded as version 0.5+revert-to-0.4.6+dfsg1 to fix this bug.


Roger

On 27/02/2021 08:50, Anton Gladky wrote:

Hi,

maybe it makes sense to revert the upload of a newer version?
There is a risk of dropping this and all dependent packages from
Bullseye.

Cheers

Anton

___
Debian-astro-maintainers mailing list
debian-astro-maintain...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-astro-maintainers
--- End Message ---

Bug#982729: marked as done (octave-msh: FTBFS: msh2m_gmsh: the gmsh subprocess exited abnormally)

[Debian Bug Tracking System]

Your message dated Thu, 4 Mar 2021 15:36:21 +
with message-id <588cd250-a1b0-3934-b247-03b7a67d1...@nebulousresearch.org>
and subject line Re: [Debian-astro-maintainers] Bug#982616: Revert voro++_0.5?
has caused the Debian Bug report #982616,
regarding octave-msh: FTBFS: msh2m_gmsh: the gmsh subprocess exited abnormally
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.)


-- 
982616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: octave-msh
Version: 1.0.10-11
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>/src'
> /usr/bin/mkoctfile --verbose -Wdate-time -D_FORTIFY_SOURCE=2 mshm_refine.cc 
> -Wl,-z,relro
> /usr/bin/mkoctfile --verbose -Wdate-time -D_FORTIFY_SOURCE=2 
> mshm_dolfin_read.cc -Wl,-z,relro
> /usr/bin/mkoctfile --verbose -Wdate-time -D_FORTIFY_SOURCE=2 
> mshm_dolfin_write.cc -Wl,-z,relro
> g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/include/octave-6.1.1~hg.2021.01.26/octave/.. 
> -I/usr/include/octave-6.1.1~hg.2021.01.26/octave  -pthread -fopenmp -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security  -Wdate-time   -D_FORTIFY_SOURCE=2 mshm_refine.cc -o 
> /tmp/oct-lTKLu6.o
> g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/include/octave-6.1.1~hg.2021.01.26/octave/.. 
> -I/usr/include/octave-6.1.1~hg.2021.01.26/octave  -pthread -fopenmp -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security  -Wdate-time   -D_FORTIFY_SOURCE=2 
> mshm_dolfin_read.cc -o /tmp/oct-V6W2K9.o
> g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/include/octave-6.1.1~hg.2021.01.26/octave/.. 
> -I/usr/include/octave-6.1.1~hg.2021.01.26/octave  -pthread -fopenmp -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security  -Wdate-time   -D_FORTIFY_SOURCE=2 
> mshm_dolfin_write.cc -o /tmp/oct-9DmeLh.o
> g++ -I/usr/include/octave-6.1.1~hg.2021.01.26/octave/.. 
> -I/usr/include/octave-6.1.1~hg.2021.01.26/octave  -pthread -fopenmp -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security  -Wdate-time -o mshm_refine.oct  /tmp/oct-lTKLu6.o  
> -shared -Wl,-Bsymbolic -Wl,-z,relro  -Wl,-z,relro  
> -L/usr/lib/x86_64-linux-gnu  -Wl,-z,relro 
> g++ -I/usr/include/octave-6.1.1~hg.2021.01.26/octave/.. 
> -I/usr/include/octave-6.1.1~hg.2021.01.26/octave  -pthread -fopenmp -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security  -Wdate-time -o mshm_dolfin_read.oct  
> /tmp/oct-V6W2K9.o  -shared -Wl,-Bsymbolic -Wl,-z,relro  -Wl,-z,relro  
> -L/usr/lib/x86_64-linux-gnu  -Wl,-z,relro 
> g++ -I/usr/include/octave-6.1.1~hg.2021.01.26/octave/.. 
> -I/usr/include/octave-6.1.1~hg.2021.01.26/octave  -pthread -fopenmp -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security  -Wdate-time -o mshm_dolfin_write.oct  
> /tmp/oct-9DmeLh.o  -shared -Wl,-Bsymbolic -Wl,-z,relro  -Wl,-z,relro  
> -L/usr/lib/x86_64-linux-gnu  -Wl,-z,relro 
> make[1]: Leaving directory '/<>/src'
> copyfile /<>/./src/mshm_dolfin_read.oct 
> /<>/./src/mshm_dolfin_write.oct 
> /<>/./src/mshm_refine.oct 
> /<>/./src/mshm_dolfin_read.cc-tst 
> /<>/./src/mshm_dolfin_write.cc-tst 
> /<>/./src/mshm_refine.cc-tst 
> /<>/./inst/x86_64-pc-linux-gnu-api-v55
> For information about changes from previous versions of the msh package, run 
> 'news msh'.
> chmod: cannot access 'debian/*/usr/lib/*/octave/packages/*/*/*.mex': No such 
> file or directory
>dh_octave_check -O--buildsystem=octave
> Checking package...
> Checking m files ...
> [inst/msh2m_structured_mesh.m]
> > /<>/inst/msh2m_structured_mesh.m
> * test
>  x = y = linspace(0,1,3);
>  msh = msh2m_structured_mesh(x,y,1,[1:4]);
>  p = [0.0   0.0   0.0   0.5   0.5   0.5 ...
>   1.0   1.0   1.0
>   0.0   0.5   1.0   0.0   0.5   1.0 ...
>   0.0   0.5   1.0];
>  assert(msh.p,p)
>  e = [1   4   7   8   3   6   1   2
>   4   7   8   9   6   9   2   3
>   0   0   0   0   0   0   0   0
>   0   0   0   0   0   0   0   0
>   1   1   2   2   3   3   4   4
>   0   0   0   0   0   0   0   0
>   1   1   1   1   1   1   1   1];
>  assert(msh.e,e)
>  t =[1   2   4   5   1   2   4   5
>  4   5   

Bug#983748: dh-r: pkg-r-autopkgtest breaks autopkgtests

[Andreas Tille]

Hi Graham,

On Thu, Mar 04, 2021 at 03:27:49PM +0200, Graham Inggs wrote:
> 
> >https://ci.debian.net/packages/r/r-bioc-mutationalpatterns/
> >
> > I discussed several times with Paul Gevers about this view.  I consider
> > it not helpful to print test results of very outdated versions for
> > unstable (even older then the version in testing) and have no link to
> > the latest version.  Paul gave some reasons for this view (sorry, I
> > failed seeking my mailbox and also can't find it in the web archive).
> 
> The reason is simply that nobody has scheduled any tests for
> r-bioc-mutationalpatterns in unstable recently.

I fail to understand this.  Before version 3.0.1+dfsg-1 has migrated to
testing tests of this version were done in unstable, right?  Why can I
only see test results of the old version 2.0.0-2 in the column for
unstable?
 
> > I wonder what you think and whether you know a link where I can
> > have a simple access to the most recent test results.
> 
> After dh-r/20210303 was uploaded and built, I scheduled tests for
> r-bioc-affy in unstable, only because it was near the top of the list
> alphabetically.
> 
> https://ci.debian.net/packages/r/r-bioc-affy/
> 
> Based on those successful runs, I have marked dh-r/20210303 urgent and
> it has migrated to testing.

That's great anyway.  Thanks a lot for your support which makes
maintaining R packages way more fun. ;-)
 
Kind regards

  Andreas. 

-- 
http://fam-tille.de

Bug#984510: purging squid with squid-openssl installed removes files anyway

[Santiago Garcia Mantinan]

Hi!

I'd like to receive comments on this one, I have already pushed a solution
to salsa that involves not removing the files and noting that on the comment
we echo on postrm so that it now tells you to remove both cache and logs.

I have also explained on the NEWS file that you must have at least -6
version in order to be able to do a purge without loosing your logs and
config.

The config will get automatically removed when it must be (if you purge
squid and squid-openssl) so it shouldn't be removed on postrm anyway, so
that works as expected, also if cache and logs dirs are empty dpkg will
remove them and echo a warning that he could not remove them if they aren't
empty.

Maybe we could do better and try to remove in case we don't have any of our
packages left or similar, but I also thought that logs are important, police
may ask via judges for logs or similar, so preserving them...  is a good
thing I believe.

So... what do you guys think?

Should we upload that as -6 or do you want to do it some other way?

Regards...
--
Manty/BestiaTester -> http://manty.net

Bug#971129: shim-signed: FTBFS: build-dependency not installable: shim-unsigned (= 15+1533136590.3beb971-7)

[Steve McIntyre]

On Mon, Feb 15, 2021 at 04:35:37PM +0100, Ivo De Decker wrote:
>Hi Steve,
>
>Thanks for the info.
>
>On Mon, Feb 15, 2021 at 12:43:33AM +, Steve McIntyre wrote:
>> >Could you clarify the timing for this, especially the timeline for getting 
>> >the
>> >signature from Microsoft (as far as that can be predicted)? I'm trying to
>> >assess if this could become a blocker wrt the actual release. Is it an 
>> >option
>> >to release with the current version of shim-signed (ie the one that's also 
>> >in
>> >buster) if we don't get the signature in time?
>> 
>> It's not really an option to release with the old shim at this point,
>> I'm afraid.
>
>That's good to know. I tagged this bug 'is-blocker', to make sure we keep an
>eye on it.
>
>> But there are newer processes in place around getting new
>> builds signed, so I'm not worrying too much here about delaying the
>> release.

So, to update here...

Shim development was caught up in the work to fix more Secure Boot
holes in Grub (DSA-4867), and it's not quite ready yet. We will have
to wait for a few more upstream fixes yet, then get reviewed and
signed. At that point, this bug will be fixed.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"War does not determine who is right - only who is left."
   -- Bertrand Russell

Processed: Re: libgcc-s1 needs Breaks: libgcc1 (<< 1:10)

[Debian Bug Tracking System]

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

> # clarify issue in 972936
> retitle 972936 removal of libgcc-s1 breaks the whole system
Bug #972936 {Done: Matthias Klose } [libgcc-s1] libgcc-s1 
needs Breaks: libgcc1 (<< 1:10)
Changed Bug title to 'removal of libgcc-s1 breaks the whole system' from 
'libgcc-s1 needs Breaks: libgcc1 (<< 1:10)'.
> fixed 972936 10.2.0-16
Bug #972936 {Done: Matthias Klose } [libgcc-s1] removal of 
libgcc-s1 breaks the whole system
Marked as fixed in versions gcc-10/10.2.0-16.
> #
> # purely cosmetic, as this specific issue is fixed
> severity 964477 serious
Bug #964477 {Done: Debian FTP Masters } 
[libgcc1] Implicit conflict between libgcc1 and libgcc-s1 prevents upgrade
Bug #961990 {Done: Debian FTP Masters } 
[libgcc1] Implicit conflict between libgcc1 and libgcc-s1 prevents upgrade
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#972936: libgcc-s1 needs Breaks: libgcc1 (<< 1:10)

[Ivo De Decker]

# clarify issue in 972936
retitle 972936 removal of libgcc-s1 breaks the whole system
fixed 972936 10.2.0-16
# 
# purely cosmetic, as this specific issue is fixed
severity 964477 serious
thanks

Hi,

On Wed, Mar 03, 2021 at 11:31:07AM +0100, Matthias Klose wrote:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964477#69
> now claims this is gone with the removal of gcc-8

It seems there is some confusion between #972936 and #964477, as the bug log
of #972936 contains some info that's only relevant for #964477.


First, bug 972936:

The issue as reported in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972936#5 was fixed in gcc-10
10.2.0-16 with the change suggested by Julian in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972936#24

"Mark libgcc-sN with XB-Important/Protected: yes. Addresses: #972936"

I can reproduce the original issue when installing libgcc-s1 from bullseye
from snapshot based on this link:

deb [check-valid-until=no] 
https://snapshot.debian.org/archive/debian/20201012T00Z/ bullseye main

When installing libgcc-s1 from current bullseye, apt is no longer willing to
remove libgcc-s1 (without 'do as I say').



Now bug 964477:

This bug can be reproduced based on Ryans script:

On a buster system:

apt-get install -y --no-install-recommends gcc-8 libc6-dev libreoffice

Switch the sources.list to a bullseye snapshot from before the removal of
gcc-8 (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964477#64)

Then run
apt-get -y dist-upgrade
to get the error.


When trying to upgrade to a current version of bullseye, the issue doesn't
show up, because gcc-8 is no longer there. So it seems this issue was resolved
with the removal of gcc-8 from testing.


I also can confirm that trying to upgrade to a snapshot of bullseye that has
gcc-8 works with the packages from Ryan based on this sources entry:

deb  
http://download.opensuse.org/repositories/home:/rpavlik:/bullseye-fix/Debian_Testing/
 ./
(which needs
https://salsa.debian.org/rpavlik/gcc-upgrade-testcase/-/blob/main/workaround.asc
to be accepted by apt)

Even though the issue from 964477 is fixed, it's possible that there are
similar issue (not related to gcc-8) we are currently unaware of. So it might
still be useful to reintroduce the transitional packages, as suggested by
David in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964477#41

Finally, I think 964477 should be marked as serious (even though that's purely
cosmetic now, as the bug is fixed).


Cheers,

Ivo

Bug#983748: dh-r: pkg-r-autopkgtest breaks autopkgtests

[Graham Inggs]

Hi Andreas

On Thu, 4 Mar 2021 at 15:09, Andreas Tille  wrote:
>https://ci.debian.net/packages/r/r-bioc-mutationalpatterns/
>
> I discussed several times with Paul Gevers about this view.  I consider
> it not helpful to print test results of very outdated versions for
> unstable (even older then the version in testing) and have no link to
> the latest version.  Paul gave some reasons for this view (sorry, I
> failed seeking my mailbox and also can't find it in the web archive).

The reason is simply that nobody has scheduled any tests for
r-bioc-mutationalpatterns in unstable recently.

> I wonder what you think and whether you know a link where I can
> have a simple access to the most recent test results.

After dh-r/20210303 was uploaded and built, I scheduled tests for
r-bioc-affy in unstable, only because it was near the top of the list
alphabetically.

https://ci.debian.net/packages/r/r-bioc-affy/

Based on those successful runs, I have marked dh-r/20210303 urgent and
it has migrated to testing.

Regards
Graham

Bug#984477: marked as done (libbio-variation-perl: missing Breaks+Replaces: bioperl (<< 1.7.3))

[Debian Bug Tracking System]

Your message dated Thu, 04 Mar 2021 13:18:23 +
with message-id 
and subject line Bug#984477: fixed in libbio-variation-perl 1.7.5-2
has caused the Debian Bug report #984477,
regarding libbio-variation-perl: missing Breaks+Replaces: bioperl (<< 1.7.3)
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.)


-- 
984477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbio-variation-perl
Version: 1.7.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'buster'.
It installed fine in 'buster', then the upgrade to 'bullseye' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libbio-variation-perl.
  Preparing to unpack .../048-libbio-variation-perl_1.7.5-1_all.deb ...
  Unpacking libbio-variation-perl (1.7.5-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-eyjeT8/048-libbio-variation-perl_1.7.5-1_all.deb 
(--unpack):
   trying to overwrite '/usr/bin/bp_flanks', which is also in package bioperl 
1.7.2-3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

IIRC bioperl 1.7.3 is the version that got split up into several packages,
therefore the existing
  Breaks+Replaces: libbio-perl-perl (<= 1.7.2)
are also insufficiently versioned (should be (<< 1.7.3) as well).

cheers,

Andreas


bioperl-run_1.7.3-6.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libbio-variation-perl
Source-Version: 1.7.5-2
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libbio-variation-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Mar 2021 13:55:37 +0100
Source: libbio-variation-perl
Architecture: source
Version: 1.7.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 984477
Changes:
 libbio-variation-perl (1.7.5-2) unstable; urgency=medium
 .
   * Team upload.
   * Fix maintainer address
   * Add debian/salsa-ci.yml
   * Breaks+Replaces: bioperl (<< 1.7.3)
 Closes: #984477
Checksums-Sha1:
 2691b1240f8113942a21e750644d2cd284324e28 2286 libbio-variation-perl_1.7.5-2.dsc
 da8ec9b9f37993aebea0805f57b8a6b1f3328f3e 2052 
libbio-variation-perl_1.7.5-2.debian.tar.xz
 e497eedd383a5c47cf3ecd69f0c7d5a1129fbafe 7420 
libbio-variation-perl_1.7.5-2_amd64.buildinfo
Checksums-Sha256:
 398f6a65c2b11255b53191b6b80705e3057dce3185ec4d9781c23185be741e4f 2286 
libbio-variation-perl_1.7.5-2.dsc
 80892316d8c5916336dae5c00b71cd4efcaa36e665a44a4d2529b31af77f4ed4 2052 
libbio-variation-perl_1.7.5-2.debian.tar.xz
 93fd5f6e1be944d84cf9a98ae5d2f0ca669acc820d0f99e4f2bdc969ba13f48b 7420 
libbio-variation-perl_1.7.5-2_amd64.buildinfo
Files:
 95819385a30bb2c3a9422e585cf669be 2286 perl optional 
libbio-variation-perl_1.7.5-2.dsc
 a9554a36af420584e21916fae8778dde 2052 perl optional 
libbio-variation-perl_1.7.5-2.debian.tar.xz
 9eebf28a9a9b33b77653193fe1859cbd 7420 perl optional 
libbio-variation-perl_1.7.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmBA2SQRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGV/g//UnswyCARmFpiEqPQC1/QjBvJpyTweoVo
IJdfM01imVFjd2LC1dPwt+SUchnsbD9BYsbiJNrjxILsn2Kb7K51uPZ8sB/ZSnos
2MAkwwdikiX3NF8XXWd5uYjifpM56SXAidE4WF795NO/LnKK8IG2g28DaAYPPPZ1
44hzgIQ4frigC7TpAf7mqnBYvbyzctHonLqF2Mq8462rf8qUY8cebZ5OibhmvdGC
15/A7UfVRVCl5GD3tRlBbwEKSQhPIYnCesrjY/FpcvA57XSe6e70nwu3raMPITA+
qvGgpKYJ00XvdGRzCQvDrczDyazG+bjT8UvapvfWn8lWIbrw1Q1uoeoHXH3d5WwC
5jWKKfHHS9Oi1q8XtAKatRcNqxgZL5OSpN5OQjoaEScd2X4hLHnNukUUbqlFbCo2
7VCNr11r2

Bug#983748: dh-r: pkg-r-autopkgtest breaks autopkgtests

[Andreas Tille]

Hi Graham,

I would like to check whether my fix for dh-r was successful.
Unfortunately I'm again and again stumbling about this kind of
debci pages:

   https://ci.debian.net/packages/r/r-bioc-mutationalpatterns/

I discussed several times with Paul Gevers about this view.  I consider
it not helpful to print test results of very outdated versions for
unstable (even older then the version in testing) and have no link to
the latest version.  Paul gave some reasons for this view (sorry, I
failed seeking my mailbox and also can't find it in the web archive).

I wonder what you think and whether you know a link where I can
have a simple access to the most recent test results.

Kind regards

  Andreas.

On Wed, Mar 03, 2021 at 12:44:34PM +0200, Graham Inggs wrote:
> Hi Andreas
> 
> On Wed, 3 Mar 2021 at 12:12, Andreas Tille  wrote:
> > My motivation for the change was that for
> > example in r-bioc-mutationalpatterns (see bug #983027) the
> > autopkgtest-pkg-r script failed to install all needed packages
> > to run its test.  This was not the only package that was affected.
> 
> This sounds like #961138.
> 
> > I'd like to discuss this quickly whether I'm again on the wrong track.
> 
> In my opinion, dh-r 20210301 with the commit [1] reverted should be OK
> for bullseye.  We should be able to see the effect in unstable soon
> after your upload.
> 
> > The effect would be that *a few* tests in r-bioc- packages will become
> > superfluid but that should be bearable for the moment.
> 
> What about skipping pkg-r-autopkgtest on the few affected packages?
> We would lose a lot of test coverage if you disabled it everywhere.
> Let's hear opinions from the rest of the team.
> 
> Regards
> Graham
> 
> 
> [1] 
> https://salsa.debian.org/r-pkg-team/dh-r/-/commit/62a4128c07a17de845e9d7260504fae187c3d193
> 
> ___
> R-pkg-team mailing list
> r-pkg-t...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team
> 

-- 
http://fam-tille.de

Bug#864597: marked as done (upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers)

[Debian Bug Tracking System]

Your message dated Thu, 4 Mar 2021 14:00:11 +0100
with message-id <082eed9f-986f-4b89-d7e1-75dc280bf...@debian.org>
and subject line upgrade report for EOL Debian release
has caused the Debian Bug report #864597,
regarding upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle 
found while processing triggers
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.)


-- 
864597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: upgrade-reports
Severity: critical
Justification: makes upgrade from stable abort

[ X-D-Cc:
  debian-rele...@lists.debian.org
  pkg-java-maintain...@lists.alioth.debian.org
  pkg-gnome-maintain...@lists.alioth.debian.org ]

Hi,

Regression spotted by Pere in some debian-edu job, but also seen since
the 2nd of June in normal gnome chroot installation then upgrade from
jessie to stretch:
  
https://jenkins.debian.net/view/edu_devel/job/chroot-installation_jessie_install_education-desktop-gnome_upgrade_to_stretch/
  
https://jenkins.debian.net/job/chroot-installation_jessie_install_gnome_upgrade_to_stretch/

I've managed to reproduce it locally with basically a debootstrap of
jessie, installation of gnome, then switch sources.list from jessie to
stretch, then update & upgrade & dist-upgrade.

I've bisected the archive using snapshot.debian.org and found out:
 - 20170601T212625Z = last timestamp found to be OK;
 - 20170602T033358Z = first timestamp to be KO.

Since logs are a bit too heavy for a bug report, I've uploaded them
there:
  https://people.debian.org/~kibi/jessie2stretch/gnome/

$timestamp.log is the output of the installation & dist-upgrade process,
while $timestamp.log.clean is a cleaned version (with Get: lines edited
to remove the package indice and the timestamp, then sort them by block,
so as to avoid a huge diff).

Then I've generated upgrade.diff by diffing both clean versions:
  https://people.debian.org/~kibi/jessie2stretch/gnome/upgrade.diff

This file consists mainly of some differences which should help us
pinpoint the exact issue (first part of the diff), but also of a big
diff at the end, since the OK log goes on with the install while the KO
one is cut rather quickly. Actual error follows:
| Unpacking default-jre-headless (2:1.8-58) over (2:1.7-52) ...
| Processing triggers for libc-bin (2.24-10) ...
| Processing triggers for hicolor-icon-theme (0.15-1) ...
| Processing triggers for desktop-file-utils (0.23-1) ...
| Processing triggers for man-db (2.7.6.1-2) ...
| Processing triggers for libglib2.0-0:amd64 (2.50.3-2) ...
| (Reading database ... 129883 files and directories currently installed.)
| Removing openjdk-7-jre:amd64 (7u111-2.6.7-1~deb8u1) ...
| Removing openjdk-7-jre-headless:amd64 (7u111-2.6.7-1~deb8u1) ...
| Removing tzdata-java (2017b-0+deb8u1) ...
| Processing triggers for hicolor-icon-theme (0.15-1) ...
| dpkg: cycle found while processing triggers:
|  chain of packages whose triggers are or may be responsible:
|   gnome-menus -> desktop-file-utils
|  packages' pending triggers which are or may be unresolvable:
|   gnome-menus: /usr/share/applications
|   shared-mime-info: /usr/share/mime/packages
|   desktop-file-utils: /usr/share/applications
| dpkg: error processing package gnome-menus (--remove):
|  triggers looping, abandoned
| Processing triggers for desktop-file-utils (0.23-1) ...
| Errors were encountered while processing:
|  gnome-menus
| E: Sub-process /usr/bin/dpkg returned an error code (1)

By looking at the diff before that, this might have been triggered (no
pun intended) by the ca-certificates-java update, which included changes
in the required java version, which might explain why this block was
present in the OK log but no longer in the KO one?
| -dpkg: openjdk-7-jre-headless:amd64: dependency problems, but removing anyway 
as you requested:
| - ca-certificates-java depends on openjdk-7-jre-headless | 
java7-runtime-headless; however:
| -  Package openjdk-7-jre-headless:amd64 is to be removed.
| -  Package java7-runtime-headless is not installed.
| -  Package openjdk-8-jre-headless:amd64 which provides java7-runtime-headless 
is not configured yet.
| -  Package default-jre-headless which provides java7-runtime-headless is not 
configured yet.
| -  Package openjdk-7-jre-headless:amd64 which provides java7-runtime-headless 
is to be removed.
| - ca-certificates-java depends on openjdk-7-jre-headless | 
java7-runtime-headless; however:
| -  Package openjdk-7-jre-headless:amd64 is to be removed.
| -  Package java7-runtime-headless is not installed.
| - 

Bug#778695: marked as done (wheezy -> jessie: no gdm3 prompt, dependency loops and broken initrd)

[Debian Bug Tracking System]

Your message dated Thu, 4 Mar 2021 14:00:11 +0100
with message-id <082eed9f-986f-4b89-d7e1-75dc280bf...@debian.org>
and subject line upgrade report for EOL Debian release
has caused the Debian Bug report #778695,
regarding wheezy -> jessie: no gdm3 prompt, dependency loops and broken initrd
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.)


-- 
778695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778695
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: upgrade-reports
Severity: grave

This is the third jessie upgrade I perform from jessie. The previous one
was documented in #774314.

It seems that the dependency loop problems are still there, and there were so
many problems with the upgrade that I don't believe it would be right to
release jessie as such (hence the "grave" severity). I know that I certainly
can't spend the 6h i did on this workstation on all the workstations in the
office. :)

I followed the two-stage upgrade procedure from the install manual. My
notes are here:

https://wiki.koumbit.net/JessieUpgrade

During the `dist-upgrade` step (after the `upgrade`), there was a
failure i couldn't trace back (because i somehow got out of that ttyrec
by mistake). After that, I got the following error trying to run
`dist-upgrade` again:

root@desktop008:/# apt-get dist-upgrade -y -o Dpkg::Options::='--force-confdef' 
-o Dpkg::Options::='--force-confold'
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
 aptdaemon : Depends: python-aptdaemon (= 0.45-2) but 1.1.1-4 is installed
 auctex : Depends: emacs24 or
   emacs-snapshot but it is not installable
 cheese : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not installable
 cups : Depends: cups-core-drivers (>= 1.7.5-10) but it is not installed
Depends: cups-server-common (>= 1.7.5-10) but it is not installed
Depends: cups-client (>= 1.7.5-10) but 1.5.3-5+deb7u4 is installed
Depends: cups-filters (>= 1.0.24-3~) but 1.0.18-2.1+deb7u1 is installed
Recommends: cups-filters (>= 1.0.42) but 1.0.18-2.1+deb7u1 is installed 
or
foomatic-filters (>= 4.0)
Recommends: cups-filters (>= 1.0.36) but 1.0.18-2.1+deb7u1 is installed 
or
ghostscript-cups (>= 9.02~)
 cups-bsd : Depends: cups-client (= 1.7.5-10) but 1.5.3-5+deb7u4 is installed
 cups-client : Depends: libcups2 (= 1.5.3-5+deb7u4) but 1.7.5-10 is installed
 dpkg : Breaks: fontconfig (< 2.11.0-6.2) but 2.9.0-7.1 is installed
Breaks: man-db (< 2.6.3-6) but 2.6.2-1 is installed
 eog : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not installable
 evolution : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not installable
 evolution-plugins : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not 
installable
 foomatic-db-engine : Depends: cups-filters (>= 1.0.42) but 1.0.18-2.1+deb7u1 
is installed or
   foomatic-filters (>= 4.0)
 gdm3 : Depends: libaudit0 (>= 1.7.13) but it is not installable
 gir1.2-freedesktop : Depends: gir1.2-glib-2.0 (= 1.32.1-1) but 1.42.0-2.2 is 
installed
 gnome-color-manager : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not 
installable
 gnome-contacts : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not 
installable
 gnome-control-center : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not 
installable
 gnome-documents : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not 
installable
 gnome-panel : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not 
installable
 gnome-screensaver : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not 
installable
 gnome-settings-daemon : Depends: libgnome-desktop-3-2 (>= 3.4.0) but it is not 
installable
 gnome-themes-standard : Depends: libpangocairo-1.0-0 (>= 1.14.0) but it is not 
installed
 gtk2-engines-pixbuf : Depends: libgtk2.0-0 (= 2.24.10-2) but 2.24.25-1 is 
installed
 libc-dev-bin : Depends: libc6 (< 2.14) but 2.19-13 is installed
 libc6-dev : Depends: libc6 (= 2.13-38+deb7u7) but 2.19-13 is installed
 libcairo2-dev : Depends: libcairo2 (= 1.12.2-3) but 1.14.0-2.1 is installed
 libcupscgi1 : Depends: libcups2 (= 1.5.3-5+deb7u4) but 1.7.5-10 is installed
 libcupsdriver1 : Depends: libcups2 (= 1.5.3-5+deb7u4) but 1.7.5-10 is installed
 libcupsimage2 : Depends: libcups2 (= 1.5.3-5+deb7u4) but 1.7.5-10 is installed
 libcupsmime1 : Depends: libcups2 (= 1.5.3-5+deb7u4) but 1.7.5-10 is installed
 libcupsppdc1 : De

Bug#775560: marked as done (upgrade-reports: Wheezy -> Jessie: machine becomes unbootable due to missing Grub)

[Debian Bug Tracking System]

Your message dated Thu, 4 Mar 2021 14:00:11 +0100
with message-id <082eed9f-986f-4b89-d7e1-75dc280bf...@debian.org>
and subject line upgrade report for EOL Debian release
has caused the Debian Bug report #775560,
regarding upgrade-reports: Wheezy -> Jessie: machine becomes unbootable due to 
missing Grub
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.)


-- 
775560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: upgrade-reports
Severity: critical
Tags: d-i
Justification: breaks the whole system


Hi,

I recently upgraded a server (amd64) from Squeeze to Wheezy, and from
there to Jessie. The upgrade from Squeeze to Wheezy went fine, but after
upgrading to Jessie, the machine would not boot anymore, spewing some
messages about something not found on the screen before dropping into
the grub shell. It turned out that the new version of Grub had not been
installed on the drives, but the old version had been deleted already.

I first tried to resurrect the situation using the rescue mode of the
d-i CD to re-install Grub on the drive(s), but that failed on all
devices. I had to pop in a rescue CD (Finnix in my case) to mount all
partitions in order, chroot to the real system, then

# grub-install /dev/sda
# grub-install /dev/sdb
# grub-install /dev/md0

After that, the machine came back up properly.

The machine has the following partitioning scheme:

/dev/md/0 -> /boot
/dev/md/1 -> LVM PV

Inside the PV, I have /root , swap etc.pp.

It might have been the case that re-installing Grub failed because I
changed the mdadm configuration as instructed in the Squeeze->Wheezy
upgrade notes from

ARRAY /dev/md/0 something
ARRAY /dev/md/1 something

to

ARRAY /dev/md0 something
ARRAY /dev/md1 something

(after doing the suggested checks, as instructed).

I changed that back to

ARRAY /dev/md/0 something
ARRAY /dev/md/1 something

I think I did that before doing the grub-install dance, but after that,
the machine came back online just fine.


HTH,
--Toni++



-- System Information:
Debian Release: 7.8
  APT prefers stable
  APT policy: (990, 'stable'), (90, 'testing'), (70, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-0.bpo.4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
Dear reporter,

Thanks for taking the time long ago to submit your upgrade report. I'm
closing these reports now because the Debian releases they were reported
against have reached their end-of-life (some long ago).

Unfortunately it's possible that the report I'm now closing may still
have relevant information for the current release (bullseye). If you
believe that's the case, don't hesitate to reopen the bug, retitle it
and provide further information and it will be seen during the current
freeze period of Debian.

Paul



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---

Bug#771971: marked as done (dpkg hangs installing "init" during upgrade from wheezy to jessie)

[Debian Bug Tracking System]

Your message dated Thu, 4 Mar 2021 14:00:11 +0100
with message-id <082eed9f-986f-4b89-d7e1-75dc280bf...@debian.org>
and subject line upgrade report for EOL Debian release
has caused the Debian Bug report #771971,
regarding dpkg hangs installing "init" during upgrade from wheezy to jessie
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.)


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

Hi,

Doing and upgrade in a VM. Started from a fairly minimal wheezy
system, then ran apt-get update and apt-get dist-upgrade to do the
upgrade. Things appeared to be running smoothly, until dpkg hung at
this point:

...
Unpacking libsepol1:amd64 (2.3-2) over (2.1.4-3) ...
Setting up libsepol1:amd64 (2.3-2) ...
Selecting previously unselected package sysvinit-core.
(Reading database ... 37825 files and directories currently installed.)
Preparing to unpack .../sysvinit-core_2.88dsf-58_amd64.deb ...
Unpacking sysvinit-core (2.88dsf-58) ...
Replacing files in old package sysvinit (2.88dsf-41+deb7u1) ...
Setting up sysvinit-core (2.88dsf-58) ...
sysvinit: restarting... done.
Selecting previously unselected package init.

I've no idea what it's stuck on. Usefully, I took a complete backup of
this VM image before I started so I can start the entire upgrade again
to help debug this if desired...
--- End Message ---
--- Begin Message ---
Dear reporter,

Thanks for taking the time long ago to submit your upgrade report. I'm
closing these reports now because the Debian releases they were reported
against have reached their end-of-life (some long ago).

Unfortunately it's possible that the report I'm now closing may still
have relevant information for the current release (bullseye). If you
believe that's the case, don't hesitate to reopen the bug, retitle it
and provide further information and it will be seen during the current
freeze period of Debian.

Paul



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---

Bug#984510: purging squid with squid-openssl installed removes files anyway

[Santiago Garcia Mantinan]

Package: squid
Version: 4.13-5
Severity: serious
File: /usr/sbin/squid

Hi!

Today I tried to move from squid to squid-nossl and clean up afterwards, it
all went ok when I did the installation of squid-openssl, squid got removed
and everything worked as expected, but when I purged squid with
squid-openssl installed, squid postrm script did...

# dpkg --purge squid
(A ler a base de datos ... 605846 files and directories currently installed.)
Purging configuration files for squid (4.13-5) ...
Purging logfiles...
Removing the config-file ..
Please, remove /var/spool/squid yourself.

Which means that it removed squid.conf and the log directory without asking
anything, it is curious that it left the cache files around for me to
remove, but removed all the usefull info I had around.

The code in question is this:

echo "Purging logfiles..."
rm -rf /var/log/squid

if [ -f /etc/squid/squid.conf ]; then
echo "Removing the config-file .."
rm -f /etc/squid/squid.conf
fi

The problem here is... how to we deal with this?

Regards...


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

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

Versions of packages squid-openssl depends on:
ii  adduser  3.118
ii  init-system-helpers  1.60
ii  libc62.31-9
ii  libcap2  1:2.44-1
ii  libcom-err2  1.46.2-1
ii  libcrypt11:4.4.17-1
ii  libdb5.3 5.3.28+dfsg1-0.8
ii  libdbi-perl  1.643-3+b1
ii  libecap3 1.0.1-3.2+b1
ii  libexpat12.2.10-2
ii  libgcc-s110.2.1-6
ii  libgssapi-krb5-2 1.18.3-4
ii  libkrb5-31.18.3-4
ii  libldap-2.4-22.4.57+dfsg-2
ii  libltdl7 2.4.6-15
ii  libnetfilter-conntrack3  1.0.8-3
ii  libnettle8   3.7-2.1
ii  libnsl2  1.3.0-2
ii  libpam0g 1.4.0-6
ii  libsasl2-2   2.1.27+dfsg-2.1
ii  libssl1.11.1.1j-1
ii  libstdc++6   10.2.1-6
ii  libsystemd0  247.3-1
ii  libxml2  2.9.10+dfsg-6.3+b1
ii  logrotate3.18.0-2
ii  lsb-base 11.1.0
ii  netbase  6.2
ii  squid-common 4.13-5

Versions of packages squid-openssl recommends:
ii  ca-certificates  20210119
ii  libcap2-bin  1:2.44-1

Versions of packages squid-openssl suggests:
ii  apparmor 2.13.6-9
pn  resolvconf   
pn  smbclient
pn  squid-cgi
pn  squid-purge  
pn  squidclient  
pn  ufw  
pn  winbind  

-- Configuration Files:
/etc/squid/squid.conf [Errno 2] Non hai tal ficheiro ou directorio: 
'/etc/squid/squid.conf'

-- no debconf information

Bug#984508: cpl-plugin-amber-calibre: combined remote/local privilege escalation in maintainer script

[Helmut Grohne]

Package: cpl-plugin-amber-calib
Version: 4.4.0+dfsg-2
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

The maintainer script of cpl-plugin-amber-calib has this code:

https://sources.debian.org/src/cpl-plugin-amber/4.4.0+dfsg-2/debian/cpl-plugin-calib.postinst.in/#L23
|   wget -O- ${URL} | \
|   tar xzO ${TAR} | \
|   tar xzC ${TARGETDIR} ${COMPONENTS} --strip-components=1

The URL is an unencrypted ftp:// URL. A malicious remote could easily
replace the requested archive and supply a different version. Such a
replacement could include a setuid root binary for instance. Once
installed, a local user can use it for a local privilege escalation.

I guess that this is not the only cpl plugin affected by this kind of
vulnerability.

Helmut

Bug#984496: marked as done (lava-server: fails to install: TypeError: 'Meta.fields' must not contain non-model field names: group migration)

[Debian Bug Tracking System]

Your message dated Thu, 04 Mar 2021 12:03:25 +
with message-id 
and subject line Bug#984496: fixed in lava 2020.12-3
has caused the Debian Bug report #984496,
regarding lava-server: fails to install: TypeError: 'Meta.fields' must not 
contain non-model field names: group migration
to be marked as done.

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

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


-- 
984496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lava-server
Version: 2020.12-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up lava-server (2020.12-2) ...
  adduser: Warning: The home directory `/var/lib/lava-server/home/' does not 
belong to the user you are currently creating.
  Updating configuration:
  * generate SECRET_KEY
  * generate DATABASES
  Run fixups:
  * fix permissions:
- /var/lib/lava-server/home/
- /var/lib/lava-server/default/
- /var/lib/lava-server/default/media/
- /var/lib/lava-server/default/media/job-output/
- /etc/lava-server/dispatcher-config/
- /etc/lava-server/dispatcher.d/
- /var/lib/lava-server/default/media/job-output/2017/
- /etc/lava-server/dispatcher-config/devices/
- /etc/lava-server/dispatcher-config/devices/*
- /etc/lava-server/dispatcher-config/device-types/
- /etc/lava-server/dispatcher-config/device-types/*
- /etc/lava-server/dispatcher-config/health-checks/
- /etc/lava-server/dispatcher-config/health-checks/*
  * drop duplicated templates:
  * fix permissions:
- /etc/lava-server/settings.conf
- /etc/lava-server/instance.conf
- /var/log/lava-server/
- /var/log/lava-server/*
- /etc/lava-server/secret_key.conf
  Create database:
  /var/run/postgresql:5432 - accepting connections
  psql -q
  lava-server manage migrate --noinput --fake-initial
  Traceback (most recent call last):
File "/usr/bin/lava-server", line 68, in 
  main()
File "/usr/bin/lava-server", line 64, in main
  execute_from_command_line([sys.argv[0]] + options.command)
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 381, in execute_from_command_line
  utility.execute()
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 375, in execute
  self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
323, in run_from_argv
  self.execute(*args, **cmd_options)
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
361, in execute
  self.check()
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
387, in check
  all_issues = self._run_checks(
File 
"/usr/lib/python3/dist-packages/django/core/management/commands/migrate.py", 
line 65, in _run_checks
  issues.extend(super()._run_checks(**kwargs))
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
377, in _run_checks
  return checks.run_checks(**kwargs)
File "/usr/lib/python3/dist-packages/django/core/checks/registry.py", line 
72, in run_checks
  new_errors = check(app_configs=app_configs)
File "/usr/lib/python3/dist-packages/django/core/checks/urls.py", line 40, 
in check_url_namespaces_unique
  all_namespaces = _load_all_namespaces(resolver)
File "/usr/lib/python3/dist-packages/django/core/checks/urls.py", line 57, 
in _load_all_namespaces
  url_patterns = getattr(resolver, 'url_patterns', [])
File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 80, 
in __get__
  res = instance.__dict__[self.name] = self.func(instance)
File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 584, 
in url_patterns
  patterns = getattr(self.urlconf_module, "urlpatterns", 
self.urlconf_module)
File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 80, 
in __get__
  res = instance.__dict__[self.name] = self.func(instance)
File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 577, 
in urlconf_module
  return import_module(self.urlconf_name)
File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
  return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in

Bug#983481: marked as done (psi4: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Thu, 04 Mar 2021 12:03:33 +
with message-id 
and subject line Bug#983481: fixed in psi4 1:1.3.2+dfsg-2
has caused the Debian Bug report #983481,
regarding psi4: autopkgtest regression
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.)


-- 
983481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: psi4
Version: 1:1.3.2+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 psi4 the autopkgtest of psi4 fails in testing
when that autopkgtest is run with the binary packages of psi4 from
unstable. It passes when run with only packages from testing. In tabular
form:

   passfail
psi4   from testing1:1.3.2+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=psi4

https://ci.debian.net/data/autopkgtest/testing/amd64/p/psi4/10660550/log.gz

autopkgtest [11:09:23]: test testsuite.sh: [---
Running test psi4numpy/rhf-hessian... FAILED
LOG:


2021-02-24 11:09
Running test psi4numpy/rhf... FAILED
LOG:


2021-02-24 11:09
Running test python/energy... FAILED
LOG:


2021-02-24 11:09
Running test chemps2/scf-n2... FAILED
LOG:


2021-02-24 11:09
Skipping test pasture-ccsorttransqt2/ccenergy_driver
Running test dfmp2-1... FAILED
LOG:


2021-02-24 11:09
Running test cc1... FAILED
LOG:


2021-02-24 11:09
Running test casscf-sp... FAILED
LOG:


2021-02-24 11:09
Skipping test mrcc/ccsdt
Skipping test dftd3/energy
Skipping test dkh/molpro-2order
Skipping test gcp/hf3c
Running test tu1-h2o-energy... FAILED
LOG:


2021-02-24 11:09
Running test json/schema-1-gradient... FAILED
LOG:


2021-02-24 11:09
Skipping test v2rdm_casscf/v2rdm3
Running test erd/scf5... FAILED
LOG:


2021-02-24 11:09
 Case Study Test of all SCF algorithms/spin-degeneracies: Singlet-Triplet O2
   -Nuclear Repulsion:
Triplet nuclear repulsion energy..PASSED
Singlet nuclear repulsion energy..PASSED
Running test fcidump... FAILED
LOG:


2021-02-24 11:09
Skipping test snsmp2/he-he
Skipping test libefp/qchem-qmefp-sp
Skipping test pcmsolver/opt-fd
Skipping test pcmsolver/scf
Running test sapt1... FAILED
LOG:


2021-02-24 11:09
Running test scf-property... FAILED
LOG:


2021-02-24 11:09
Nuclear repulsion energy..PASSED
Skipping test gdma/gdma1
Skipping test cfour/sp-rhf-ccsd_t_
Running test simint/scf5... FAILED
LOG:


2021-02-24 11:09
 Case Study Test of all SCF algorithms/spin-degeneracies: Singlet-Triplet O2
   -Nuclear Repulsion:
Triplet nuclear repulsion energy..PASSED
Singlet nuclear repulsion energy..PASSED
Some tests failed
autopkgtest [11:09:40]: test testsuite.sh: ---]



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: psi4
Source-Version: 1:1.3.2+dfsg-2
Done: Graham Inggs 

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

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated psi4 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Mar 2021 11:31:06 +
Source: psi4
Architecture: source
Version: 1:1.3.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Graham Inggs 
Closes: 983481
Changes:
 psi4 (1:1.3.2+dfsg-2) unstable; urgency=medium
 .
   * Tighten dependencies on libin

Bug#984506: cpl-plugin-fors-calib: fors-kit-5.3.32*.tar.gz no longer downloadable

[Andreas Beckmann]

Package: cpl-plugin-fors-calib
Version: 5.3.32+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: fixed -1 5.4.3+dfsg-1

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up cpl-plugin-fors-calib (5.3.32+dfsg-1) ...
  --2021-03-04 05:20:13--  
ftp://ftp.eso.org/pub/dfs/pipelines/fors/fors-kit-5.3.32.tar.gz
 => '-'
  Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.53, 134.171.42.54
  Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.53|:21... connected.
  Logging in as anonymous ... Logged in!
  ==> SYST ... done.==> PWD ... done.
  ==> TYPE I ... done.  ==> CWD (1) /pub/dfs/pipelines/fors ... done.
  ==> SIZE fors-kit-5.3.32.tar.gz ... done.
  
  ==> PASV ... done.==> RETR fors-kit-5.3.32.tar.gz ... 
  No such file 'fors-kit-5.3.32.tar.gz'.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2021-03-04 05:20:13--  
ftp://ftp.eso.org/pub/dfs/pipelines/fors/fors-kit-5.3.32-1.tar.gz
 => '-'
  Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.54, 134.171.42.53
  Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.54|:21... connected.
  Logging in as anonymous ... Logged in!
  ==> SYST ... done.==> PWD ... done.
  ==> TYPE I ... done.  ==> CWD (1) /pub/dfs/pipelines/fors ... done.
  ==> SIZE fors-kit-5.3.32-1.tar.gz ... done.
  
  ==> PASV ... done.==> RETR fors-kit-5.3.32-1.tar.gz ... 
  No such file 'fors-kit-5.3.32-1.tar.gz'.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
[...]


cheers,

Andreas


cpl-plugin-fors-calib_5.3.32+dfsg-1.log.gz
Description: application/gzip

Processed: cpl-plugin-fors-calib: fors-kit-5.3.32*.tar.gz no longer downloadable

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 5.4.3+dfsg-1
Bug #984506 [cpl-plugin-fors-calib] cpl-plugin-fors-calib: 
fors-kit-5.3.32*.tar.gz no longer downloadable
Marked as fixed in versions cpl-plugin-fors/5.4.3+dfsg-1.

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

Processed: cpl-plugin-amber-calib: amber-kit-4.3.8*.tar.gz no longer downloadable

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 4.3.9+dfsg-1
Bug #984505 [cpl-plugin-amber-calib] cpl-plugin-amber-calib: 
amber-kit-4.3.8*.tar.gz no longer downloadable
Marked as fixed in versions cpl-plugin-amber/4.3.9+dfsg-1.

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

Bug#984505: cpl-plugin-amber-calib: amber-kit-4.3.8*.tar.gz no longer downloadable

[Andreas Beckmann]

Package: cpl-plugin-amber-calib
Version: 4.3.8+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: fixed -1 4.3.9+dfsg-1

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up cpl-plugin-amber-calib (4.3.8+dfsg-1) ...
  --2021-03-04 05:20:29--  
ftp://ftp.eso.org/pub/dfs/pipelines/amber/amber-kit-4.3.8.tar.gz
 => '-'
  Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.54, 134.171.42.53
  Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.54|:21... connected.
  Logging in as anonymous ... Logged in!
  ==> SYST ... done.==> PWD ... done.
  ==> TYPE I ... done.  ==> CWD (1) /pub/dfs/pipelines/amber ... done.
  ==> SIZE amber-kit-4.3.8.tar.gz ... done.
  
  ==> PASV ... done.==> RETR amber-kit-4.3.8.tar.gz ... 
  No such file 'amber-kit-4.3.8.tar.gz'.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  --2021-03-04 05:20:29--  
ftp://ftp.eso.org/pub/dfs/pipelines/amber/amber-kit-4.3.8-1.tar.gz
 => '-'
  Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.53, 134.171.42.54
  Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.53|:21... connected.
  Logging in as anonymous ... Logged in!
  ==> SYST ... done.==> PWD ... done.
  ==> TYPE I ... done.  ==> CWD (1) /pub/dfs/pipelines/amber ... done.
  ==> SIZE amber-kit-4.3.8-1.tar.gz ... done.
  
  ==> PASV ... done.==> RETR amber-kit-4.3.8-1.tar.gz ... 
  No such file 'amber-kit-4.3.8-1.tar.gz'.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
[...]

cheers,

Andreas


cpl-plugin-amber-calib_4.3.8+dfsg-1.log.gz
Description: application/gzip

Bug#976978: rust-cargo-outdated: Build dependencies are no longer fulfillable

[Lukas Märdian]

Package: rust-cargo-outdated
Version: 0.9.9-1
Followup-For: Bug #976978
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch

Dear Maintainer,

I've updated the Cargo.toml file to make use of rust-git2-curl ^0.14.0,
which is packaged in Debian/Ubuntu and can fulfill the dependency.

With this the build passes.

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

 * Fix FTBFS of rust-cargo-outdated, due to missing rust-git2-curl
   0.12.0 dependency

  * d/p/update-git2-curl-dependency.patch:
Update Cargo.toml to use rust-git2-curl 0.14.0


Thanks for considering the patch.


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

Kernel: Linux 5.8.0-44-generic (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru rust-cargo-outdated-0.9.9/debian/control 
rust-cargo-outdated-0.9.9/debian/control
--- rust-cargo-outdated-0.9.9/debian/control2020-12-05 10:22:02.0 
+0100
+++ rust-cargo-outdated-0.9.9/debian/control2021-03-03 17:02:20.0 
+0100
@@ -10,7 +10,7 @@
  librust-cargo-0.43+default-dev (>= 0.43.1-~~),
  librust-docopt-1+default-dev,
  librust-env-logger-0.7+default-dev,
- librust-git2-curl-dev (>= 0.12.0),
+ librust-git2-curl-dev,
  librust-semver-0.9+default-dev,
  librust-serde-1+default-dev (>= 1.0.11-~~),
  librust-serde-1+derive-dev (>= 1.0.11-~~),
diff -Nru rust-cargo-outdated-0.9.9/debian/patches/series 
rust-cargo-outdated-0.9.9/debian/patches/series
--- rust-cargo-outdated-0.9.9/debian/patches/series 1970-01-01 
01:00:00.0 +0100
+++ rust-cargo-outdated-0.9.9/debian/patches/series 2021-03-03 
17:00:54.0 +0100
@@ -0,0 +1 @@
+update-git2-curl-dependency.patch
diff -Nru 
rust-cargo-outdated-0.9.9/debian/patches/update-git2-curl-dependency.patch 
rust-cargo-outdated-0.9.9/debian/patches/update-git2-curl-dependency.patch
--- rust-cargo-outdated-0.9.9/debian/patches/update-git2-curl-dependency.patch  
1970-01-01 01:00:00.0 +0100
+++ rust-cargo-outdated-0.9.9/debian/patches/update-git2-curl-dependency.patch  
2021-03-03 17:01:52.0 +0100
@@ -0,0 +1,14 @@
+Description: Update Cargo.toml to use rust-git2-curl 0.14.0
+Author: Lukas Märdian 
+---
+--- rust-cargo-outdated-0.9.9.orig/Cargo.toml
 rust-cargo-outdated-0.9.9/Cargo.toml
+@@ -40,7 +40,7 @@ version = "1.0.0"
+ version = "0.7.0"
+ 
+ [dependencies.git2-curl]
+-version = "0.12.0"
++version = "0.14.0"
+ 
+ [dependencies.semver]
+ version = "0.9.0"

Bug#971713: Bug arrived in Testing?

[Joost van Baal-Ilić]

Hi Dirk,

On Thu, Mar 04, 2021 at 10:35:42AM +, dirk.j...@telekom.de wrote:
> Hi guys,
> it seems the bug from insserv now arrived in testing with the tons of 
> repeated messages. Any chance for a fix?
> Very often repeated:
> insserv: Script sysstat has overlapping Default-Start and Default-Stop 
> runlevels (2 3 4 5) and (2 3 4 5). This should be fixed.
> insserv: Script sysstat has overlapping Default-Start and Default-Stop 
> runlevels (2 3 4 5) and (2 3 4 5). This should be fixed.

This will likely get fixed automatically within 5 days from now:
https://tracker.debian.org/pkg/insserv says:

 Migration status for insserv (1.21.0-1 to 1.21.0-1.1)
 Too young, only 5 of 10 days old
 Updating insserv fixes old bugs: #971713

Bye,

Joost

Processed: this bug makes the package mostly useless on Testing

[Debian Bug Tracking System]

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

> severity 959022 grave
Bug #959022 [cgroup-tools] cgroup-tools: does not work in cgroup2 / unified 
hierarchy
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Processed: unarchiving 928226, affects 928226

[Debian Bug Tracking System]

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

> unarchive 928226
Bug #928226 {Done: Andreas Beckmann } 
[firefox-esr-dev,thunderbird-dev,lightning-l10n-bn-bd,lightning-l10n-pa-in,lightning-l10n-ta-lk,thunderbird-l10n-bn-bd,thunderbird-l10n-pa-in,thunderbird-l10n-ta-lk,linux-headers-4.9.0-8-amd64,linux-headers-4.9.0-8-rt-amd64,iceweasel-l10n-ak,iceweasel-l10n-csb,iceweasel-l10n-ku,iceweasel-l10n-lg,iceweasel-l10n-nso,iceweasel-l10n-ta-lk,iceweasel-l10n-zu,iceweasel-l10n-be]
 uninstallable cruft package
Warning: Unknown package 'linux-headers-4.9.0-8-amd64'
Warning: Unknown package 'linux-headers-4.9.0-8-rt-amd64'
Warning: Unknown package 'iceweasel-l10n-ak'
Warning: Unknown package 'iceweasel-l10n-csb'
Warning: Unknown package 'iceweasel-l10n-ku'
Warning: Unknown package 'iceweasel-l10n-lg'
Warning: Unknown package 'iceweasel-l10n-nso'
Warning: Unknown package 'iceweasel-l10n-ta-lk'
Warning: Unknown package 'iceweasel-l10n-zu'
Unarchived Bug 928226
Warning: Unknown package 'linux-headers-4.9.0-8-amd64'
Warning: Unknown package 'linux-headers-4.9.0-8-rt-amd64'
Warning: Unknown package 'iceweasel-l10n-ak'
Warning: Unknown package 'iceweasel-l10n-csb'
Warning: Unknown package 'iceweasel-l10n-ku'
Warning: Unknown package 'iceweasel-l10n-lg'
Warning: Unknown package 'iceweasel-l10n-nso'
Warning: Unknown package 'iceweasel-l10n-ta-lk'
Warning: Unknown package 'iceweasel-l10n-zu'
> affects 928226 + firefox-esr-l10n-as firefox-esr-l10n-bn-bd 
> firefox-esr-l10n-bn-in firefox-esr-l10n-en-za firefox-esr-l10n-mai 
> firefox-esr-l10n-ml firefox-esr-l10n-or calendar-google-provider
Bug #928226 {Done: Andreas Beckmann } 
[firefox-esr-dev,thunderbird-dev,lightning-l10n-bn-bd,lightning-l10n-pa-in,lightning-l10n-ta-lk,thunderbird-l10n-bn-bd,thunderbird-l10n-pa-in,thunderbird-l10n-ta-lk,linux-headers-4.9.0-8-amd64,linux-headers-4.9.0-8-rt-amd64,iceweasel-l10n-ak,iceweasel-l10n-csb,iceweasel-l10n-ku,iceweasel-l10n-lg,iceweasel-l10n-nso,iceweasel-l10n-ta-lk,iceweasel-l10n-zu,iceweasel-l10n-be]
 uninstallable cruft package
Warning: Unknown package 'linux-headers-4.9.0-8-amd64'
Warning: Unknown package 'linux-headers-4.9.0-8-rt-amd64'
Warning: Unknown package 'iceweasel-l10n-ak'
Warning: Unknown package 'iceweasel-l10n-csb'
Warning: Unknown package 'iceweasel-l10n-ku'
Warning: Unknown package 'iceweasel-l10n-lg'
Warning: Unknown package 'iceweasel-l10n-nso'
Warning: Unknown package 'iceweasel-l10n-ta-lk'
Warning: Unknown package 'iceweasel-l10n-zu'
Added indication that 928226 affects firefox-esr-l10n-as, 
firefox-esr-l10n-bn-bd, firefox-esr-l10n-bn-in, firefox-esr-l10n-en-za, 
firefox-esr-l10n-mai, firefox-esr-l10n-ml, firefox-esr-l10n-or, and 
calendar-google-provider
Warning: Unknown package 'linux-headers-4.9.0-8-amd64'
Warning: Unknown package 'linux-headers-4.9.0-8-rt-amd64'
Warning: Unknown package 'iceweasel-l10n-ak'
Warning: Unknown package 'iceweasel-l10n-csb'
Warning: Unknown package 'iceweasel-l10n-ku'
Warning: Unknown package 'iceweasel-l10n-lg'
Warning: Unknown package 'iceweasel-l10n-nso'
Warning: Unknown package 'iceweasel-l10n-ta-lk'
Warning: Unknown package 'iceweasel-l10n-zu'
> thanks
Stopping processing here.

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

Bug#971713: Bug arrived in Testing?

[Dirk.Jost]

Hi guys,
it seems the bug from insserv now arrived in testing with the tons of repeated 
messages. Any chance for a fix?
Very often repeated:
insserv: Script sysstat has overlapping Default-Start and Default-Stop 
runlevels (2 3 4 5) and (2 3 4 5). This should be fixed.
insserv: Script sysstat has overlapping Default-Start and Default-Stop 
runlevels (2 3 4 5) and (2 3 4 5). This should be fixed.
Cheers,
Dirk.

Bug#967234: marked as done (yasm: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 04 Mar 2021 10:08:11 +
with message-id 
and subject line Bug#967234: fixed in yasm 1.3.0-2.1
has caused the Debian Bug report #967234,
regarding yasm: 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.)


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

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

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

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

Please check for dependencies, build dependencies AND autopkg tests.

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

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated yasm 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: Thu, 04 Mar 2021 10:44:35 +0100
Source: yasm
Architecture: source
Version: 1.3.0-2.1
Distribution: unstable
Urgency: medium
Maintainer: Sam Hocevar 
Changed-By: Matthias Klose 
Closes: 967234 981877
Changes:
 yasm (1.3.0-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build-depend on python2. Closes: #967234.
   * Mark yasm as M-A: foreign. Closes: #981877.
Checksums-Sha1:
 514ea8893eb94c8bccc6501f3bd02234c60cae21 1895 yasm_1.3.0-2.1.dsc
 76b4297221edf076402bdc2d72cd1d302bd04141 8256 yasm_1.3.0-2.1.debian.tar.xz
 b5d8696a022f28abea2508399fd08d1db2525237 6877 yasm_1.3.0-2.1_source.buildinfo
Checksums-Sha256:
 35f87f5d8f8f123643a244d76006b6f772af72c5148ab87ec4e189aec9b37373 1895 
yasm_1.3.0-2.1.dsc
 473e9f318bd274dee92db4ee3247f7e64cd709a569ce1825fdf935cd01490409 8256 
yasm_1.3.0-2.1.debian.tar.xz
 997256a265d905d0d29118678b8edcf932a9f09e17e4a3232a7714553260c9f7 6877 
yasm_1.3.0-2.1_source.buildinfo
Files:
 cc3fda7934f6a0285e44bafd2d395b8b 1895 devel optional yasm_1.3.0-2.1.dsc
 c8cce265f0cfad7b3955ad98e6fb892e 8256 devel optional 
yasm_1.3.0-2.1.debian.tar.xz
 880db63619d5ac030617983bae06c91f 6877 devel optional 
yasm_1.3.0-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmBArSEQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9RA9D/9Zz9+6c1m01SyxX2NUxfvXqBH74VWK5Yqd
Jy/BsCTg2xx3hr4DXuLS7sc6H1YIthOdDqsDKN+eKwe2N+Ka0u4fpOXZZjCCrKpB
u7DgNDrswWumnOE21E85cXvqEGV+GRRXF0XHBkf6cLP8sgQwrO7vpf6MxCwLVtkl
WyVAkF5CuHLZV5XaBdtUahvSZvAR1nzt9bwMt7eIZaN0mOUsQnIHLnQvs3qR1z1o
qRezflqwhLUZwWjbOCxBLjSoRws14JB5sH9ZzV5Zv+rxj4LMB7CmQ+qoe402qOj2
Wnv35nl0SARAgzpeckyBYbuTh3D72A4yl3B0yAIpX3cgvKZk7dTN5SPofWV4PryK
U1RDK0dHJGHQIJOIqPnIeZRM3FbMDIDqSb+SHOd8J/lK6r6RJzvSiUhaDsMDFky4
SYcEWkqwKyDoabRX3UEODoSwtB8D1k4CnpBSjFhg5ASpm5eThfDCaysfdDGT31mz
4RJPm8IuPQztPrQt46E4trvWUiOcGEQ6pF6OLWJdFIwAk0/dIZ0g0nIQXbsCFkn8
EkqHjgGVwidWwDLLFMOy4fG/6t0DEL3smQB7xcMIeNHx54QuznUHFOC5liUAhBTd
NFUH7sDR8NZC7FTtolplhDsOVqvoygm2KHcPMrQ2BrVIAXvuvatoScKV0C18Izoi
kmhzw6nJVQ==
=m5Tp
-END PGP SIGNATURE End Message ---

Bug#967237: marked as done (zziplib: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 04 Mar 2021 09:18:29 +
with message-id 
and subject line Bug#967237: fixed in zziplib 0.13.62-3.3
has caused the Debian Bug report #967237,
regarding zziplib: 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.)


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

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

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

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

Please check for dependencies, build dependencies AND autopkg tests.

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

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated zziplib 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: Thu, 04 Mar 2021 09:54:37 +0100
Source: zziplib
Architecture: source
Version: 0.13.62-3.3
Distribution: unstable
Urgency: medium
Maintainer: Scott Howard 
Changed-By: Matthias Klose 
Closes: 856566 863892 967237
Changes:
 zziplib (0.13.62-3.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build using python2. Closes: #856566, #967237.
   * Update home page. Closes: #863892.
   * Update watch file.
Checksums-Sha1:
 a52d9c063dffd820aff35c9cf7e19bc5794003e9 2066 zziplib_0.13.62-3.3.dsc
 4fd124ca4a805febf138e247e17cde62a8a012dc 17036 
zziplib_0.13.62-3.3.debian.tar.xz
 394be391d69cbfb3aa9c4bcb0482826c8fd0c573 6753 
zziplib_0.13.62-3.3_source.buildinfo
Checksums-Sha256:
 7913767c0a6439a08f8dab05babfbaa3de9219515ab1216c3c0ba25b4c6dfc8c 2066 
zziplib_0.13.62-3.3.dsc
 7d95e46fb0ebbcb598ce4ab256ceb3a021d89859db8b36d53bafc821948ed569 17036 
zziplib_0.13.62-3.3.debian.tar.xz
 d1c82e3e00f86e061ca3672bc48854280883359d1a766e69149949172a3c95f0 6753 
zziplib_0.13.62-3.3_source.buildinfo
Files:
 7ceaa0ea74ed10d2203801a4f480c0c5 2066 libs optional zziplib_0.13.62-3.3.dsc
 49c1857880e748d1b9b48d7e506aebe1 17036 libs optional 
zziplib_0.13.62-3.3.debian.tar.xz
 e704f512ed365e5604a6d2f8410b891a 6753 libs optional 
zziplib_0.13.62-3.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmBAoogQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9cMCEACGYXzRZ6T+a3p5YXGuywohfFetY40Jic4W
TDL6vTXM4oKGdbAsOBp0o0OfVjMd71J4rxWVLMquUR9lFUxd8B3PI48ukJkbH6B5
eszUajP3LeN7ugn3E3HsNS7dBy+nIXnztuHcx3KAeEDEXjnjN4Cl8i8relwnjUZu
CiFol8UwqCPxLopho5IZF3knSj4tHpenVtP6fs/+dQZGC/KEjeaTkp2NDr7Q712H
6nncnnOmw6fOh/c6ArPdZcCarySEZNxk/RDrOdpt8TJtSgQnPpJcQZsLHRtiKqyZ
piZJGBZ4swufYlq3mE06auEDutIkIExdx3XnfuEIBIF86OtIQHx7VZ6C1cRsD12d
e6lFwmieNsOvO57S0HGGHSwpCLm+HV9gJWkPIJB43tmsH07Lkh0Vd0bC5bGrR+JP
/IKKH7MJOGpbFqA1RMkd1ZLztnOnnR/n3nIA4IfUmw4M9aMgq12TSdW6bMum8hJ+
LTDPPoejr9Q2lTCxFRjJhBsViZsXJZcFuSWAwfxkgdocru1MqWaWwmp2V2VrF4uF
Hk+JDHEQc1Gg8LawpFOWlmHXAiKbc7ggyDODhYQc4F3tGuQDEC5vyVjHD5Go0EkJ
tzKHZTGX7l1q/BbyjFLbX2wgCmv928lYxW/MBoGC8wdDD+689wOZO8/qw+7XB5w0
RQcJfwq1bg==
=qrTj
-END PGP SIGNATURE End Message ---

Processed: Change severity to important

[Debian Bug Tracking System]

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

> severity 983183 important
Bug #983183 {Done: Martijn van Brummelen } [libpam-script] 
libpam-script: Wrong path for pam_script.so
Severity set to 'important' from 'grave'
> Thanks
Stopping processing here.

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

Bug#982904: mumble: CVE-2021-27229

[Chris Knadle]

Salvatore Bonaccorso:

Hi

[Adding CC to security-team alias]

On Mon, Mar 01, 2021 at 08:31:54AM +, Chris Knadle wrote:

Salvatore Bonaccorso:

Source: mumble
Version: 1.3.3-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/mumble-voip/mumble/pull/4733
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for mumble.

CVE-2021-27229[0]:
| Mumble before 1.3.4 allows remote code execution if a victim navigates
| to a crafted URL on a server list and clicks on the Open Webpage text.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-27229
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-27229
[1] https://github.com/mumble-voip/mumble/pull/4733
[2] 
https://github.com/mumble-voip/mumble/commit/e59ee87abe249f345908c7d568f6879d16bfd648

Please adjust the affected versions in the BTS as needed.


I've reviewed the upstream git repo; there are 2 patches that are security
related -- the other is for an OCB2 XEXStarAttack on encryption, both of
which comprise the majority of the bugfix release of mumble 1.3.4. It seems
to me that the best way to proceed is to upload mumble 1.3.4 as the other
changes are incidental, and I hope that this will be acceptable during the
soft freeze.


Yes new upstream version might still be possible in the soft-freeze,
so if that's the most sensible solution then I would go for that.

https://release.debian.org/bullseye/freeze_policy.html

For buster btw we marked in no-dsa, so if you can shedule a fix via a
point release this would be great.


Yep, I'm working on this for fixing CVE-2021-27229 for Buster. It looks like the 
commit ([2], above) can apply as a patch for 1.3.0~git20190125.440b173+dfsg-2 so 
this looks straightforward as far as I can tell.


  -- Chris

--
Chris Knadle
chris.kna...@coredump.us

Bug#983379: linux uml segfault

[Benjamin Berg]

On Thu, 2021-03-04 at 08:47 +0100, Johannes Berg wrote:
On Thu, 2021-03-04 at 14:38 +0900, Hajime Tazaki wrote:

> > Now, I don't know how to fix it (short of changing your nsswitch
> > configuration) - maybe we could somehow rename sem_init()? Or maybe
> > we
> > can somehow give the kernel binary a lower symbol resolution than
> > the
> > libc/libpthread.
> 
> objcopy (from binutils) can localize symbols (i.e., objcopy -L
> sem_init $orig_file $new_file).  It also does renaming symbols.  But
> not sure this is the ideal solution.

Yes, we started thinking about it but it was too late at night when I
replied ...

I think there's basically a way to have an external list of symbols to
export, for symbol versioning, that we could/should use to basically
not
export any of the kernel symbols out to libs.

Maybe using the ld --version-script= option here works to mark all
kernel symbols as being "local" and prevent them from being picked up
by libraries.

Benjamin

> How does UML handle symbol conflicts between userspace code and Linux
> kernel (like this case sem_init) ?  AFAIK, libnl has a same symbol as
> Linux kernel (genlmsg_put) and others can possibly do as well.

I fear it doesn't?

johannes


___
linux-um mailing list
linux...@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um




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

Bug#984475: marked as done (libbio-db-ncbihelper-perl: missing Breaks+Replaces: bioperl (<< 1.7.3))

[Debian Bug Tracking System]

Your message dated Thu, 04 Mar 2021 08:18:58 +
with message-id 
and subject line Bug#984475: fixed in libbio-db-ncbihelper-perl 1.7.6-4
has caused the Debian Bug report #984475,
regarding libbio-db-ncbihelper-perl: missing Breaks+Replaces: bioperl (<< 1.7.3)
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.)


-- 
984475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbio-db-ncbihelper-perl
Version: 1.7.6-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + bioperl-run

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'buster'.
It installed fine in 'buster', then the upgrade to 'bullseye' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libbio-db-ncbihelper-perl.
  Preparing to unpack .../045-libbio-db-ncbihelper-perl_1.7.6-2_all.deb ...
  Unpacking libbio-db-ncbihelper-perl (1.7.6-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-eyjeT8/045-libbio-db-ncbihelper-perl_1.7.6-2_all.deb 
(--unpack):
   trying to overwrite '/usr/bin/bp_biofetch_genbank_proxy', which is also in 
package bioperl 1.7.2-3

IIRC bioperl 1.7.3 is the version that got split up into several packages.


cheers,

Andreas


bioperl-run_1.7.3-6.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libbio-db-ncbihelper-perl
Source-Version: 1.7.6-4
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libbio-db-ncbihelper-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Mar 2021 09:01:01 +0100
Source: libbio-db-ncbihelper-perl
Architecture: source
Version: 1.7.6-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 984475
Changes:
 libbio-db-ncbihelper-perl (1.7.6-4) unstable; urgency=medium
 .
   * Team upload.
   * Breaks+Replaces: bioperl (<< 1.7.3)
 Closes: #984475
Checksums-Sha1:
 15e8de1c11d613253a9c5e821e3c95d828030cc3 2472 
libbio-db-ncbihelper-perl_1.7.6-4.dsc
 36aa5c428d0cc5e3f599a1da951e4e999643e25d 2964 
libbio-db-ncbihelper-perl_1.7.6-4.debian.tar.xz
 74de8914317b648c49eb63aded3cd6702c9f5867 7465 
libbio-db-ncbihelper-perl_1.7.6-4_amd64.buildinfo
Checksums-Sha256:
 550b10a72d6d0f5adcabe657a6b4a85037ff0d64a6acaa8c852e9095c2ca3a70 2472 
libbio-db-ncbihelper-perl_1.7.6-4.dsc
 efbe38cae1776a0dc295b256aab480d5a48dc118632184b52bf58aa4ee4f2a5d 2964 
libbio-db-ncbihelper-perl_1.7.6-4.debian.tar.xz
 d26934b6b1108fae40c935d193e57e988f582d032a5ae9a74fd380f1ee927eda 7465 
libbio-db-ncbihelper-perl_1.7.6-4_amd64.buildinfo
Files:
 07c155031541e14c97e48513afb5e559 2472 perl optional 
libbio-db-ncbihelper-perl_1.7.6-4.dsc
 923684c5cf8af35e8e2004223fa62023 2964 perl optional 
libbio-db-ncbihelper-perl_1.7.6-4.debian.tar.xz
 cb23b39c5a037efbd8826bc160796cf4 7465 perl optional 
libbio-db-ncbihelper-perl_1.7.6-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmBAlW4RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHumhAAmEnSoJ+yeK0mGXZOg41Eaj5x+02CFLx3
byPFkwnXxWuvZOcpFSsGHxGGevfV6BOo5FfYOO4BfZLZ4O2jUauPKws9rKeKAqBG
kTo0m4xIGkFu9bNul8dC8WWjvCwOjw9kYdXSRMmwipxY4ESPJ+o/vfsyhPwzpm+Q
Vx/aqGD/26R9nsS3r1PKcT+PICKA3o3ZvBhlcM+aR9StEd0ST2fv1UprqL6Y4+zQ
kxw3+ScVDcOKiSDXzgnQJGNQ+h4bAbUcr9bm9Hg6cw/1jUOfPwG+MFxjiKt4n4V6
PTyzL3+bMM5faBdi5yVOsCIuCZdZuJTHyNU+ScYmaefxzli+plYvEaY2eRK+DiOp
1M9LZgwdGcbt9TDOQAMKq/oxwL530akJd1wOcKbk3RGi/bAjLUUrvPWHnnmJ/DwL
Ikm/WMzc3aVbExab8UnY+KOAEa4PcVn+trlFKJPmXjRdArmukP7RgN59dUSJPSsO
HtarGj1O01nm9Hwx0c1d/Qw60o7vRGJuhAPGuBiqwW4E13qjiHtqcZSMBG9iF1vR
SR7d+D

Bug#984496: lava-server: fails to install: TypeError: 'Meta.fields' must not contain non-model field names: group migration

[Andreas Beckmann]

Package: lava-server
Version: 2020.12-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up lava-server (2020.12-2) ...
  adduser: Warning: The home directory `/var/lib/lava-server/home/' does not 
belong to the user you are currently creating.
  Updating configuration:
  * generate SECRET_KEY
  * generate DATABASES
  Run fixups:
  * fix permissions:
- /var/lib/lava-server/home/
- /var/lib/lava-server/default/
- /var/lib/lava-server/default/media/
- /var/lib/lava-server/default/media/job-output/
- /etc/lava-server/dispatcher-config/
- /etc/lava-server/dispatcher.d/
- /var/lib/lava-server/default/media/job-output/2017/
- /etc/lava-server/dispatcher-config/devices/
- /etc/lava-server/dispatcher-config/devices/*
- /etc/lava-server/dispatcher-config/device-types/
- /etc/lava-server/dispatcher-config/device-types/*
- /etc/lava-server/dispatcher-config/health-checks/
- /etc/lava-server/dispatcher-config/health-checks/*
  * drop duplicated templates:
  * fix permissions:
- /etc/lava-server/settings.conf
- /etc/lava-server/instance.conf
- /var/log/lava-server/
- /var/log/lava-server/*
- /etc/lava-server/secret_key.conf
  Create database:
  /var/run/postgresql:5432 - accepting connections
  psql -q
  lava-server manage migrate --noinput --fake-initial
  Traceback (most recent call last):
File "/usr/bin/lava-server", line 68, in 
  main()
File "/usr/bin/lava-server", line 64, in main
  execute_from_command_line([sys.argv[0]] + options.command)
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 381, in execute_from_command_line
  utility.execute()
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 375, in execute
  self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
323, in run_from_argv
  self.execute(*args, **cmd_options)
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
361, in execute
  self.check()
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
387, in check
  all_issues = self._run_checks(
File 
"/usr/lib/python3/dist-packages/django/core/management/commands/migrate.py", 
line 65, in _run_checks
  issues.extend(super()._run_checks(**kwargs))
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
377, in _run_checks
  return checks.run_checks(**kwargs)
File "/usr/lib/python3/dist-packages/django/core/checks/registry.py", line 
72, in run_checks
  new_errors = check(app_configs=app_configs)
File "/usr/lib/python3/dist-packages/django/core/checks/urls.py", line 40, 
in check_url_namespaces_unique
  all_namespaces = _load_all_namespaces(resolver)
File "/usr/lib/python3/dist-packages/django/core/checks/urls.py", line 57, 
in _load_all_namespaces
  url_patterns = getattr(resolver, 'url_patterns', [])
File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 80, 
in __get__
  res = instance.__dict__[self.name] = self.func(instance)
File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 584, 
in url_patterns
  patterns = getattr(self.urlconf_module, "urlpatterns", 
self.urlconf_module)
File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 80, 
in __get__
  res = instance.__dict__[self.name] = self.func(instance)
File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 577, 
in urlconf_module
  return import_module(self.urlconf_name)
File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
  return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 790, in exec_module
File "", line 228, in _call_with_frames_removed
File "/usr/lib/python3/dist-packages/lava_server/urls.py", line 149, in 

  include("lava_rest_app.urls"),
File "/usr/lib/python3/dist-packages/django/urls/conf.py", line 34, in 
include
  urlconf_module = import_module(urlconf_module)
File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
  return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 790, in exec_module
File "", line 228, in _call_with_frames_removed
File "/usr/lib/

Processed: bug 984492 is forwarded to https://github.com/scrapy/w3lib/issues/164

[Debian Bug Tracking System]

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

> forwarded 984492 https://github.com/scrapy/w3lib/issues/164
Bug #984492 [src:python-w3lib] autopkg test failures
Set Bug forwarded-to-address to 'https://github.com/scrapy/w3lib/issues/164'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#974828: printer-driver-hpcups: SIGABRT with "free(): invalid next size (normal)" in HPCupsFilter::cleanup

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +pending
Bug #974828 [printer-driver-hpcups] printer-driver-hpcups: SIGABRT with 
"free(): invalid next size (normal)" in HPCupsFilter::cleanup
Added tag(s) pending.

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

Bug#974828: printer-driver-hpcups: SIGABRT with "free(): invalid next size (normal)" in HPCupsFilter::cleanup

[Didier 'OdyX' Raboud]

Control: tags -1 +pending

Le vendredi, 26 février 2021, 15.41:07 h CET Bernhard Übelacker a écrit :
> Dear Maintainer,
> with the original PPD and input files from Ian I could
> reproduce the issue and with the help of rr-debugger
> this is what I assume what happens:
> 
> - The buffer m_pPrinterBuffer is allocated here with
>the current sizes inside cups_header. [1]
> 
> - The first page got processed and for the second page
>a new cups_header record gets copied. [2]
>Unfortunately now the header contains higher sizes,
>but the buffer is not grown accordingly.
> 
> - Now to this buffer is written by a read function, and beyond
>where the management information of malloc got overwritten for
>some other random memory. [3]
> 
> - The defect in the management information of malloc is detected
>and the process is aborted. [4]
> 
> 
> The attached patch is an attempt to grow the buffer size
> if the header changes on a new page.
> This is just tested for the given crash, nothing more, therefore
> there might be side effects on replacing this buffer?

I have forwarded this upstream, but don't hold your breath; I don't expect any 
feedback from them, sadly. :-(

I'll apply this and upload to unstable once the current version migrated.

Thanks a lot for your work!

OdyX

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