Bug#990340: glances: contains prebuilt javascript without source

2021-06-25 Thread Johannes Schauer Marin Rodrigues
Package: glances
Version: 3.1.5-1
Severity: serious
Justification: Policy 2.2.1

Hi,

the source package contains:

glances/outputs/static/public/glances.js
glances/outputs/static/public/glances.map.js

these files are copied into the binary package as:

/usr/lib/python3/dist-packages/glances/outputs/static/public/glances.js
/usr/lib/python3/dist-packages/glances/outputs/static/public/glances.map.js

they trigger the following lintian errors:

E source-is-missing glances/outputs/static/public/glances.js line 52292 is 
44264 characters long (>512)
E source-is-missing glances/outputs/static/public/glances.map.js line 2 is 
2631202 characters long (>512)

Don't distribute those files or build them from source.

Thanks!

cheers, josch



Bug#989870: marked as done (libwine-development,libwine-development-dev: both ship usr/lib/x86_64-linux-gnu/wine-development/libwine.so)

2021-06-25 Thread Debian Bug Tracking System
Your message dated Sat, 26 Jun 2021 02:48:55 +
with message-id 
and subject line Bug#989320: fixed in wine-development 5.22+repack-2
has caused the Debian Bug report #989320,
regarding libwine-development,libwine-development-dev: both ship 
usr/lib/x86_64-linux-gnu/wine-development/libwine.so
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.)


-- 
989320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwine-development,libwine-development-dev
Version: 5.22+repack-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package libwine-development:amd64.
  Preparing to unpack .../98-libwine-development_5.22+repack-1_amd64.deb ...
  Unpacking libwine-development:amd64 (5.22+repack-1) ...
  Selecting previously unselected package libwine-development-dev.
  Preparing to unpack .../99-libwine-development-dev_5.22+repack-1_amd64.deb ...
  Unpacking libwine-development-dev (5.22+repack-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-5EjfOJ/99-libwine-development-dev_5.22+repack-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/wine-development/libwine.so', 
which is also in package libwine-development:amd64 5.22+repack-1
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-5EjfOJ/99-libwine-development-dev_5.22+repack-1_amd64.deb


cheers,

Andreas


libwine-development-dev_5.22+repack-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: wine-development
Source-Version: 5.22+repack-2
Done: Michael Gilbert 

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated wine-development 
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: Sat, 26 Jun 2021 02:27:31 +
Source: wine-development
Architecture: source
Version: 5.22+repack-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party 
Changed-By: Michael Gilbert 
Closes: 989320
Changes:
 wine-development (5.22+repack-2) unstable; urgency=medium
 .
   * Fix some lintian warnings.
   * Remove libwine.so symlink from the libwine package (closes: #989320).
Checksums-Sha1:
 3f59a74d42a0b678412082ea9caf5c75b5fbe786 4704 
wine-development_5.22+repack-2.dsc
 ce4b33063040690309113d5741164fba1fe57afd 5683368 
wine-development_5.22+repack-2.debian.tar.xz
 2e5877ebad47389dce909cca0876ccc39d49b361 19344 
wine-development_5.22+repack-2_source.buildinfo
Checksums-Sha256:
 6a1cd05857888f757dda258dbb5d9e4c0c3f6cfffa8a4458e1c8244249385ccb 4704 
wine-development_5.22+repack-2.dsc
 2269fee5b7b55cc50ce9968b780b3fffd5574a086469512c83f829d3ec71739b 5683368 
wine-development_5.22+repack-2.debian.tar.xz
 0756a2a62e995bb7d3696c3ad335483d406e215919182a8a82faf6364b918696 19344 
wine-development_5.22+repack-2_source.buildinfo
Files:
 30d8ddfa16a9479ec65a2bcc5967538b 4704 otherosfs optional 
wine-development_5.22+repack-2.dsc
 4532739c71d58b4a95ae6409e1302376 5683368 otherosfs optional 
wine-development_5.22+repack-2.debian.tar.xz
 c1c0afaabad492923e7cd40b05094760 19344 otherosfs optional 
wine-development_5.22+repack-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQQzBAEBCgAdFiEEIwTlZiOEpzUxIyp4mD40ZYkUaygFAmDWkNcACgkQmD40ZYkU
ayhS5h/+IXeXLSeOBrG56I+WD1OrxIpQU4A0UVd2mLjx+2KnRGQEuV8zKQm7bTRi
QEiv8iydE6+84KnUrS2gMiGyzk0kX1++Pjy84iqbHEzDClUJ1U7ydjAjXAza4Kpl
9sUVyErTpN5j4ule57C3rMzVERRTjsy0FYyoRyNKc/A37gLWGWzcUJzA6VB6JSg+
L4LL37CYr3O7cefkils0nHeCHMVyJ+vT6Nyy5WpEAockwbE2jhaYSuMxL+Q6MM7N
IuOOapS0o/dRm1TYaEZ0ACJdDmOkNLx5Zz9sCi2Y4SBPSl7pS0kibk5TPV513vXE
XYGC8F6YOdrfMqqBxQtVt06DnHYMgRpLHuOZhjrYxe5/qOzPKjiXfRgK91g//nHC
DqbuD/eQRJYbPrIsVFvmd3MGBcLZxOdk3Xty59lAeeCCgiKZbHeBrDUCcY7YmDy7

Bug#989320: marked as done (libwine-development-dev: libwine-development and libwine-development-dev both supply libwine.so)

2021-06-25 Thread Debian Bug Tracking System
Your message dated Sat, 26 Jun 2021 02:48:55 +
with message-id 
and subject line Bug#989320: fixed in wine-development 5.22+repack-2
has caused the Debian Bug report #989320,
regarding libwine-development-dev: libwine-development and 
libwine-development-dev both supply libwine.so
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.)


-- 
989320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwine-development-dev
Version: 5.22+repack-1
Severity: normal

Dear Maintainer,

I was attempting to upgrade all installed packages. libwine-development was to 
be upgraded from 5.19+repack-1 to 5.22+repack-1, as well as 
libwine-development-dev from 5.19+repack-1 to 5.22+repack-1. 
libwine-development-dev upgraded successfully, but libwine-development did not:

roger@rogerhp:~$ sudo apt-get full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 libwine-development : Breaks: libwine-development:i386 (!= 5.19+repack-1) but 
5.22+repack-1 is installed
 libwine-development:i386 : Recommends: libodbc1:i386 (>= 2.3.1) but it is not 
installed
Recommends: gstreamer1.0-plugins-good:i386 but it 
is not installed
Breaks: libwine-development (!= 5.22+repack-1) but 
5.19+repack-1 is installed
 libwine-development-dev : Depends: libwine-development (= 5.22+repack-1) but 
5.19+repack-1 is installed
 wine64-development : Depends: libwine-development (= 5.22+repack-1) but 
5.19+repack-1 is installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).
$
$
$ sudo apt-get --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  libwine-development
The following packages will be upgraded:
  libwine-development
1 upgraded, 0 newly installed, 0 to remove and 20 not upgraded.
9 not fully installed or removed.
Need to get 0 B/76.9 MB of archives.
After this operation, 36.1 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs... Done
(Reading database ... 778201 files and directories currently installed.)
Preparing to unpack .../libwine-development_5.22+repack-1_amd64.deb ...
Unpacking libwine-development:amd64 (5.22+repack-1) over (5.19+repack-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libwine-development_5.22+repack-1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/wine-development/libwine.so', 
which is also in package libwine-development-dev 5.22+repack-1
Errors were encountered while processing:
 /var/cache/apt/archives/libwine-development_5.22+repack-1_amd64.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
$

Expected result: Successful upgrade of both packages. 

-- Package-specific info:
/usr/bin/wine points to /usr/bin/wine-stable.

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

Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 libwine-development-dev depends on:
ii  libc6-dev [libc-dev]  2.31-12
ii  libwine-development   5.19+repack-1

Versions of packages libwine-development-dev recommends:
iu  wine64-development-tools  5.22+repack-1

libwine-development-dev suggests no packages.

Versions of packages wine-development depends on:
iu  wine32-development  5.22+repack-1
iu  wine64-development  5.22+repack-1

Versions of packages wine-development suggests:
pn  dosbox
pn  exe-thumbnailer | kio-extras  
pn  playonlinux   
pn  q4wine
pn  winbind   
pn  wine-binfmt   
ii  winetricks0.0+20210206-2

Versions of packages libwine-development depends on:
ii  libasound2   1.2.4-1.1
ii  libc62.31-12
ii  libfaudio0   21.02-1
ii  libfontconfig1

Processed: your mail

2021-06-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 989870 src:wine-development
Bug #989870 [libwine-development,libwine-development-dev] 
libwine-development,libwine-development-dev: both ship 
usr/lib/x86_64-linux-gnu/wine-development/libwine.so
Bug reassigned from package 'libwine-development,libwine-development-dev' to 
'src:wine-development'.
No longer marked as found in versions 5.22+repack-1.
Ignoring request to alter fixed versions of bug #989870 to the same values 
previously set
> reassign 989320 src:wine-development
Bug #989320 [libwine-development-dev] libwine-development-dev: 
libwine-development and libwine-development-dev both supply libwine.so
Bug reassigned from package 'libwine-development-dev' to 'src:wine-development'.
No longer marked as found in versions wine-development/5.22+repack-1.
Ignoring request to alter fixed versions of bug #989320 to the same values 
previously set
> forcemerge 989870 989320
Bug #989870 [src:wine-development] libwine-development,libwine-development-dev: 
both ship usr/lib/x86_64-linux-gnu/wine-development/libwine.so
Bug #989320 [src:wine-development] libwine-development-dev: libwine-development 
and libwine-development-dev both supply libwine.so
Severity set to 'serious' from 'normal'
Merged 989320 989870
>
End of message, stopping processing here.

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



Processed (with 1 error): your mail

2021-06-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forcemerge 989870 989320
Bug #989870 [libwine-development,libwine-development-dev] 
libwine-development,libwine-development-dev: both ship 
usr/lib/x86_64-linux-gnu/wine-development/libwine.so
Unable to merge bugs because:
package of #989320 is 'libwine-development-dev' not 
'libwine-development,libwine-development-dev'
Failed to forcibly merge 989870: Did not alter merged bugs.

> thanks
Stopping processing here.

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



Bug#990276: marked as done ([feature-check] Version comparisons may return the wrong result)

2021-06-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Jun 2021 21:19:01 +
with message-id 
and subject line Bug#990276: fixed in feature-check 0.2.2-7
has caused the Debian Bug report #990276,
regarding [feature-check] Version comparisons may return the wrong result
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.)


-- 
990276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: feature-check
Version: 0.2.2-6
Severity: serious
Tags: patch upstream

There are two problems in the Perl 5 implementation of feature-check as
found in the Debian archive; both are fixed upstream in a later version.

With the following setup, the first couple of queries return the correct
results:

[roam@straylight ~/tmp/v/roam/fctest]$ cat fctest.sh
#!/bin/sh

echo 'Features: fctest=3.0.beta2'
[roam@straylight ~/tmp/v/roam/fctest]$ feature-check -l ./fctest.sh
fctest  3.0.beta2
[roam@straylight ~/tmp/v/roam/fctest]$ feature-check ./fctest.sh 'fctest > 
1' && echo yes
yes
[roam@straylight ~/tmp/v/roam/fctest]$ feature-check ./fctest.sh 'fctest < 
3.1' && echo yes
yes
[roam@straylight ~/tmp/v/roam/fctest]$ feature-check ./fctest.sh 'fctest < 
3' && echo yes
[roam@straylight ~/tmp/v/roam/fctest]$ 

...but these return incorrect results and generate spurious stderr output:


[roam@straylight ~/tmp/v/roam/fctest]$ feature-check ./fctest.sh 'fctest < 
10' && echo yes
[roam@straylight ~/tmp/v/roam/fctest]$ feature-check ./fctest.sh 'fctest < 
3.0.beta3' && echo yes
Argument "beta3" isn't numeric in numeric comparison (<=>) at 
/usr/bin/feature-check line 285.
Argument "beta2" isn't numeric in numeric comparison (<=>) at 
/usr/bin/feature-check line 285.
[roam@straylight ~/tmp/v/roam/fctest]$ 

These bugs are fixed in two upstream commits:

  
https://gitlab.com/ppentchev/feature-check/-/commit/ed0da5159562fa37cf32386a1baf2a1114562822

  
https://gitlab.com/ppentchev/feature-check/-/commit/59e618baff6836f281697561f5a9cfa22ccd28df

The changes in these commits may be applied directly as patches to the
Debian source package.

G'luck,
Peter

-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-7-amd64 (SMP w/8 CPU threads)
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.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 feature-check depends on:
ii  libjson-xs-perl  4.030-1+b1
ii  perl 5.32.1-4

feature-check recommends no packages.

feature-check suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: feature-check
Source-Version: 0.2.2-7
Done: Peter Pentchev 

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

Debian distribution maintenance software
pp.
Peter Pentchev  (supplier of updated feature-check 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, 24 Jun 2021 15:33:07 +0300
Source: feature-check
Architecture: source
Version: 0.2.2-7
Distribution: unstable
Urgency: medium
Maintainer: Peter Pentchev 
Changed-By: Peter Pentchev 
Closes: 990276
Changes:
 feature-check (0.2.2-7) unstable; urgency=medium
 .
   * Add the cmp-num and cmp-rest upstream patches to fix some version
 string comparisons. Closes: #990276
Checksums-Sha1:
 3dd9b2ad6a48d7595b060121d65421fb6f02 2681 feature-check_0.2.2-7.dsc
 c93faa800a2ba513222ff76f1de9b60798f13604 8052 
feature-check_0.2.2-7.debian.tar.xz
Checksums-Sha256:
 4255db411ad5d552bb93a3b334500fe8ecef0d5d3823fc8184e7d27dd8b4b1bf 2681 
feature-check_0.2.2-7.dsc
 c35bbea37721b223dff41e120ef215ffb61de15db762962977591f5b6b2de25b 8052 
feature-check_0.2.2-7.debian.tar.xz
Files:
 985a3665d56b3e6b826b370c3635e065 2681 utils optional feature-check_0.2.2-7.dsc
 

Bug#989064: marked as done (curl: output of -w accidentally in microseconds)

2021-06-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Jun 2021 20:19:27 +
with message-id 
and subject line Bug#989064: fixed in curl 7.74.0-1.3
has caused the Debian Bug report #989064,
regarding curl: output of -w accidentally in microseconds
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.)


-- 
989064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: curl
Version: 7.74.0-1.2
Severity: serious
Tags: patch upstream

Hi,

ymmv, but as there are probably zillions of scripts out there parsing
the output of curl -w, I think switching to microseconds accidentally
will break enough things to warrant a serious bug.

Upstream bug is
https://github.com/curl/curl/issues/6321
its fixed in 7.75.0 with the patches mentioned in the github issue.

Please apply before bullseye will be relased.

Thanks,

Bernd

-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F
--- End Message ---
--- Begin Message ---
Source: curl
Source-Version: 7.74.0-1.3
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated curl 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: Fri, 25 Jun 2021 20:59:54 +0200
Source: curl
Architecture: source
Version: 7.74.0-1.3
Distribution: unstable
Urgency: medium
Maintainer: Alessandro Ghedini 
Changed-By: Paul Gevers 
Closes: 989064
Changes:
 curl (7.74.0-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add upstream patch bc7ecc7 so curl -w times shown as seconds with
 fractions (Closes: #989064)
Checksums-Sha1:
 97356889b8180f6309a5edd62111a3b18995ba41 2435 curl_7.74.0-1.3.dsc
 536b3e82ef129252c88a8b6d6191f85eea630913 36944 curl_7.74.0-1.3.debian.tar.xz
Checksums-Sha256:
 5b2743bad178f7d682ec8067e292ae2e6fb3039d5c6fe94dc1ecbae23fbed9df 2435 
curl_7.74.0-1.3.dsc
 9013432cb208df97d20c0dfb05c4ba0b93807c17744891a6528d1173eb58d95d 36944 
curl_7.74.0-1.3.debian.tar.xz
Files:
 6bd1315ec94c7b3aa944f4ae0888e6d6 2435 web optional curl_7.74.0-1.3.dsc
 583b6fbc8ccea3731a99c71133dc405e 36944 web optional 
curl_7.74.0-1.3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmDWMfgACgkQnFyZ6wW9
dQrLCQf/ZZnRjvrtKinfoL6joOfOHmtH4TZRUZXOYGOGuaL6DVMI2J7UkZL0Mj6q
6iLGUdGE4fSPWmenwt1SniC/cwReHLj0qIz2YR1umvNEWTv5aUaSA0PJQHiUY+Om
I6fG/opG/oIwoyT1GAxZ5efE6YIEHA+eff6qYUTj3bEU0+em1oNU465ae4p9m6x5
RgNwr3sWWgy22MamZdjSTdtdWbFtyDd/VKRaeG9PylEuTMPxuykIXBhWbRlB3ZpQ
Qj3uM+T7i76qCpE8uWJca+7DoJ/E1VrDn8TX3YcBwI7gvRi0+DLYWVMAh3yqUnHr
nxbALLabOWgo1+8vkUucxIC+O60/cw==
=KRRw
-END PGP SIGNATURE End Message ---


Processed: Re: [Pkg-openssl-devel] Bug#990228: Bug#990228: Bug#990228: Bug#990228: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a

2021-06-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 990228 ssl-cert
Bug #990228 [openssl] openssl: breaks ssl-cert installation: 
8022CB35777F:error:127A:random number generator:RAND_write_file:Not a 
regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom
Bug reassigned from package 'openssl' to 'ssl-cert'.
No longer marked as found in versions openssl/3.0.0~~alpha16-1.
Ignoring request to alter fixed versions of bug #990228 to the same values 
previously set
> severity 990228 normal
Bug #990228 [ssl-cert] openssl: breaks ssl-cert installation: 
8022CB35777F:error:127A:random number generator:RAND_write_file:Not a 
regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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



Bug#990228: [Pkg-openssl-devel] Bug#990228: Bug#990228: Bug#990228: Bug#990228: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a reg

2021-06-25 Thread Kurt Roeckx
reassign 990228 ssl-cert
severity 990228 normal
thanks

So I think there is no bug in OpenSSL and the additional check
being done in 3.0 makes sense. So I'm reassigning this to
ssl-cert.


Kurt



Bug#990320: sssd - Fails after upgrade from Buster

2021-06-25 Thread Bastian Blank
Package: sssd
Version: 2.4.1-2
Severity: serious

After upgrade from Buster, several components of sssd simply fail:

| ● sssd-nss.socket  loaded failed failed
SSSD NSS Service responder socket
|   sssd-pac.socket  loaded active listening 
SSSD PAC Service responder socket
| ● sssd-pam-priv.socket loaded failed failed
SSSD PAM Service responder private socket
| ● sssd-ssh.socket  loaded failed failed
SSSD SSH Service responder socket
| ● sssd-sudo.socket loaded failed failed
SSSD Sudo Service responder socket

So all the sockets are broken and the system is in degraded mode due to
failed units.

Bastian

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

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

Versions of packages sssd depends on:
pn  python3-sss  
pn  sssd-ad  
pn  sssd-common  
pn  sssd-ipa 
pn  sssd-krb5
pn  sssd-ldap
pn  sssd-proxy   

sssd recommends no packages.

sssd suggests no packages.


Bug#990318: python-pkg-resources: please add Breaks against the unversioned python packages

2021-06-25 Thread Andreas Beckmann
Package: python-pkg-resources
Version: 44.1.1-1
Severity: serious
Tags: patch

Hi,

in some upgrade scenarios the unversioned python packages don't get
removed despite of the Breaks existing in python2.7 and friends.
This is caused by the unversioned python packages getting higher scores
and apt-get therefore prefers to keep them installed. Often
python-pkg-resources is installed in these scenarios, too, and (as a
"surviving" python2 package) has the highest score of all python2
packages, making it the ideal candidate for a copy of the Breaks to make
them effective.


Andreas
diff -Nru python-setuptools-44.1.1/debian/changelog 
python-setuptools-44.1.1/debian/changelog
--- python-setuptools-44.1.1/debian/changelog   2020-08-02 14:20:55.0 
+0200
+++ python-setuptools-44.1.1/debian/changelog   2021-06-18 02:53:40.0 
+0200
@@ -1,3 +1,13 @@
+python-setuptools (44.1.1-2) UNRELEASED; urgency=medium
+
+  * python-pkg-resources: Copy Breaks: python (<< 2.7.18),
+python-minimal (<< 2.7.18), libpython-stdlib (<< 2.7.18) from python2.7
+for smoother upgrades from buster. In some upgrade scenarios these Breaks
+in python2.7 were ineffective because the unversioned python packages got
+higher scores. Closes: #-1.
+
+ -- Andreas Beckmann   Fri, 18 Jun 2021 02:53:40 +0200
+
 python-setuptools (44.1.1-1) unstable; urgency=medium
 
   * New upstream version.
diff -Nru python-setuptools-44.1.1/debian/control 
python-setuptools-44.1.1/debian/control
--- python-setuptools-44.1.1/debian/control 2020-08-02 14:20:55.0 
+0200
+++ python-setuptools-44.1.1/debian/control 2021-06-18 02:53:23.0 
+0200
@@ -19,6 +19,10 @@
 Architecture: all
 Multi-Arch: foreign
 Depends: ${misc:Depends}, ${python:Depends}
+Breaks:
+ python (<< 2.7.18),
+ python-minimal (<< 2.7.18),
+ libpython-stdlib (<< 2.7.18),
 Description: Package Discovery and Resource Access using pkg_resources
  The pkg_resources module provides an API for Python libraries to
  access their resource files, and for extensible applications and


Bug#892275: marked as done (redshift shouldn't start itself via systemd)

2021-06-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Jun 2021 13:33:51 +
with message-id 
and subject line Bug#892275: fixed in redshift 1.12-4.2
has caused the Debian Bug report #892275,
regarding redshift shouldn't start itself via systemd
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.)


-- 
892275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: redshift
Version: 1.11-1
Severity: grave

--- Please enter the report below this line. ---

Redshift (and -gtk) crash at startup.

Error message is the next : 

Failed to run Redshift
Trying location provider 'geoclue2' …
Unable to connect to GeoClue.
Unable to get location from provider.


A bug is open upstream with some (geo)clues.

https://github.com/jonls/redshift/issues/158

--- System information. ---
Architecture:
Kernel: Linux 4.14.0-3-amd64

500 testing ftp.fr.debian.org
500 stable linux.teamviewer.com
500 preview linux.teamviewer.com

--- Package information. ---
Depends (Version) | Installed
==-+-
libc6 (>= 2.17) |
libdrm2 (>= 2.4.3) |
libglib2.0-0 (>= 2.26.0) |
libx11-6 |
libxcb-randr0 (>= 1.3) |
libxcb-render0 |
libxcb1 |
libxxf86vm1 |


Recommends (Version) | Installed
==-+-===
geoclue-2.0 | 2.4.7-1


Package's Suggests field is empty.


0x0364AB34.asc
Description: application/pgp-keys
<>--- End Message ---
--- Begin Message ---
Source: redshift
Source-Version: 1.12-4.2
Done: Adam Borowski 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 23 Jun 2021 14:55:39 +0200
Source: redshift
Architecture: source
Version: 1.12-4.2
Distribution: unstable
Urgency: medium
Maintainer: nicoo 
Changed-By: Adam Borowski 
Closes: 892275
Changes:
 redshift (1.12-4.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop broken systemd-based startup, without a replacement for now.
 Closes: #892275
Checksums-Sha1:
 64eaabdadb890f1644fcc3f7d41ce46b345ef64a 2059 redshift_1.12-4.2.dsc
 77de41ae5d4d3512124537700a104324516a9029 355472 redshift_1.12-4.2.debian.tar.xz
 af47edce578ed919e919429407bd431c7802bc09 8535 
redshift_1.12-4.2_source.buildinfo
Checksums-Sha256:
 adb72d93f28529c16efa8b8daa35814757ac74001b0286d8b93397ef268ec256 2059 
redshift_1.12-4.2.dsc
 77fd2707c634de69ccecdde0031eb27fb3689407cbced86ecfaac09f9621f067 355472 
redshift_1.12-4.2.debian.tar.xz
 2c58afa97b65fce02759fcee0525c3d41b2cbe6a78e86757ba85ccd37f4a3b5a 8535 
redshift_1.12-4.2_source.buildinfo
Files:
 0b9f9cf006cb988a82d919019bbc59d0 2059 x11 optional redshift_1.12-4.2.dsc
 769c3be6423842c2ba8fda631b40844f 355472 x11 optional 
redshift_1.12-4.2.debian.tar.xz
 3cb24c5efb3de8d68067857a592dd723 8535 x11 optional 
redshift_1.12-4.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmDTMOAACgkQweDZLphv
fH6Wdw/+NsePvsdI0+C++1Y2DnCozL7Pq8cVKgkrafPD0LGtwtCxtVZJd3+wR7AI
pGBAzxT4N7O9LXEPKcjpm7Fr45NMSiNjPlQ62IOw+JRpysATnR/fv4EpBfkgIYa4
4BsKvpVvfcNSGok/ucMcbx68z1TDwPkzPikC73snj6Bb6AnN5e7JeAYlQ+CgAcec
eqsltoIjtOuJCYX+l/IpqfXLp4akHE/CStVdW7DGPjZQPVUkRVKVW6iTEn3nyErz
7b/84F/8TnD3lnp2Z79FBAY+AIPv2X6DfDepvs+S4pvvYqjg7m3TQl7qTSrIoFpt
hQo0Uf90npuomQQznSB8zENdgCB89ZeSgU9gEadfsC6TX+nWxq+AwwPtl744IIDG
T1Ccu+p5+Iuatz25Z2bxwr/aMnnwk5dBBEDFoYQdx0IdyG5DVXJ0+C1BN26+a+EO
Llc5CGKGvNA8mZliliJyByJ4WfcQLzt37G/JLuJF/J3MD3NrlWLnmRNnS/fjtb78
T4LH1xgLeeHfa0iA8fd/IubN9SkKqIEA8szsLIqo1oZrF512uiBCiAqFxnlNISSD
h5igQ73wIl9MHhx6b2hZMSQrvjcZbsOPndDw/ix73wJcLDXewwFWu0rvI2n9Xn+I
MZ92GA9IEL14QRNpgHD3NZZsSXm5IRI5zqK169G/Z18Xi2Va4jY=
=a4tE
-END PGP SIGNATURE End Message ---


Bug#990317: librust-object+compression-dev: please use a versioned dependency for librust-flate2-1+default-dev

2021-06-25 Thread Andreas Beckmann
Package: librust-object+compression-dev
Version: 0.12.0-3
Severity: serious
Tags: patch

librust-object+compression-dev depends on librust-flate2-1+default-dev
which is a (versioned) virtual package provided by
librust-flate2+zlib-dev in buster and by librust-flate2+rust-backend-dev
in bullseye. apt-get has problems exchanging these two packages during an
upgrade from buster to bullseye and prefers to keep the already installed
provider installed. This can be fixed by making the dependency versioned
s.t. the old provider from buster is no longer considered as a valid
solution.

Bad problem resolution by apt-get:

  Starting 2 pkgProblemResolver with broken count: 5
  Investigating (0) librust-goblin+pe32-dev:amd64 < 0.0.19-1 @ii mK Ib >
  Broken librust-goblin+pe32-dev:amd64 Depends on librust-goblin-dev:amd64 < 
0.0.19-1 -> 0.2.1-4 @ii umU > (= 0.0.19-1)
Considering librust-goblin-dev:amd64 5 as a solution to 
librust-goblin+pe32-dev:amd64 -2
Removing librust-goblin+pe32-dev:amd64 rather than change 
librust-goblin-dev:amd64
  Investigating (0) librust-goblin+pe64-dev:amd64 < 0.0.19-1 @ii mK Ib >
  Broken librust-goblin+pe64-dev:amd64 Depends on librust-goblin-dev:amd64 < 
0.0.19-1 -> 0.2.1-4 @ii umU > (= 0.0.19-1)
Considering librust-goblin-dev:amd64 5 as a solution to 
librust-goblin+pe64-dev:amd64 -2
Removing librust-goblin+pe64-dev:amd64 rather than change 
librust-goblin-dev:amd64
  Investigating (0) librust-goblin+mach64-dev:amd64 < 0.0.19-1 @ii mK Ib >
  Broken librust-goblin+mach64-dev:amd64 Depends on librust-goblin-dev:amd64 < 
0.0.19-1 -> 0.2.1-4 @ii umU > (= 0.0.19-1)
Considering librust-goblin-dev:amd64 5 as a solution to 
librust-goblin+mach64-dev:amd64 -2
Removing librust-goblin+mach64-dev:amd64 rather than change 
librust-goblin-dev:amd64
  Investigating (0) librust-parity-wasm+std-dev:amd64 < 0.35.5-1 @ii mK Ib >
  Broken librust-parity-wasm+std-dev:amd64 Depends on 
librust-parity-wasm-dev:amd64 < 0.35.5-1 -> 0.41.0-1 @ii umU > (= 0.35.5-1)
Considering librust-parity-wasm-dev:amd64 0 as a solution to 
librust-parity-wasm+std-dev:amd64 -2
Removing librust-parity-wasm+std-dev:amd64 rather than change 
librust-parity-wasm-dev:amd64
  Investigating (0) librust-flate2+zlib-dev:amd64 < 1.0.6-1 @ii mK Ib >
  Broken librust-flate2+zlib-dev:amd64 Depends on librust-flate2-dev:amd64 < 
1.0.6-1 -> 1.0.13-3 @ii umU > (= 1.0.6-1)
Considering librust-flate2-dev:amd64 0 as a solution to 
librust-flate2+zlib-dev:amd64 -2
Removing librust-flate2+zlib-dev:amd64 rather than change 
librust-flate2-dev:amd64
  Investigating (1) librust-object+compression-dev:amd64 < 0.11.0-1 -> 0.12.0-3 
@ii umU Ib >
  Broken librust-object+compression-dev:amd64 Depends on 
librust-flate2-1+default-dev:amd64 < none @un H >
Considering librust-flate2+zlib-dev:amd64 -2 as a solution to 
librust-object+compression-dev:amd64 2
Added librust-flate2+zlib-dev:amd64 to the remove list
Fixing librust-object+compression-dev:amd64 via keep of 
librust-flate2+zlib-dev:amd64
  Investigating (1) librust-flate2+zlib-dev:amd64 < 1.0.6-1 @ii mK Ib >
  Broken librust-flate2+zlib-dev:amd64 Depends on librust-flate2-dev:amd64 < 
1.0.6-1 -> 1.0.13-3 @ii umU > (= 1.0.6-1)
Considering librust-flate2-dev:amd64 0 as a solution to 
librust-flate2+zlib-dev:amd64 -2
Removing librust-flate2+zlib-dev:amd64 rather than change 
librust-flate2-dev:amd64
  Investigating (2) librust-object+compression-dev:amd64 < 0.11.0-1 -> 0.12.0-3 
@ii umU Ib >
  Broken librust-object+compression-dev:amd64 Depends on 
librust-flate2-1+default-dev:amd64 < none @un H >
Considering librust-flate2+zlib-dev:amd64 -2 as a solution to 
librust-object+compression-dev:amd64 2
Added librust-flate2+zlib-dev:amd64 to the remove list
Fixing librust-object+compression-dev:amd64 via keep of 
librust-flate2+zlib-dev:amd64
  Investigating (2) librust-flate2+zlib-dev:amd64 < 1.0.6-1 @ii mK Ib >
  Broken librust-flate2+zlib-dev:amd64 Depends on librust-flate2-dev:amd64 < 
1.0.6-1 -> 1.0.13-3 @ii umU > (= 1.0.6-1)
Considering librust-flate2-dev:amd64 0 as a solution to 
librust-flate2+zlib-dev:amd64 2
Added librust-flate2-dev:amd64 to the remove list
Fixing librust-flate2+zlib-dev:amd64 via keep of librust-flate2-dev:amd64
   Try to Re-Instate (3) librust-flate2-dev:amd64
  Done
  
  The following packages were automatically installed and are no longer 
required:
libperl5.28 librust-byteorder-dev librust-cfg-if-dev
librust-rustc-version-dev librust-semver-dev librust-semver-parser-0.7-dev
perl-modules-5.28
  Use 'sudo apt autoremove' to remove them.
  The following packages will be REMOVED:
librust-goblin+mach64-dev librust-goblin+pe32-dev librust-goblin+pe64-dev
librust-parity-wasm+std-dev
  The following NEW packages will be installed:
gcc-10-base libapt-pkg6.0 libcrypt-dev libcrypt1 libffi7 libgcc-s1
libgssapi-krb5-2 libhogweed6 libk5crypto3 libkeyutils1 libkrb5-3

Bug#990284: marked as done (atlas-ecmwf: please build for ppc64el)

2021-06-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Jun 2021 12:18:33 +
with message-id 
and subject line Bug#990284: fixed in atlas-ecmwf 0.25.0-3
has caused the Debian Bug report #990284,
regarding atlas-ecmwf: please build for ppc64el
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.)


-- 
990284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: atlas-ecmwf
Version: 0.25.0-2
Severity: serious
tags: patch

Hello, please enable build for ppc64el, by correctly writing the architecture 
name
sed s/ppc54el/ppc64el/g -i debian/control
should be enough to fix the typo

thanks

Gianfranco
--- End Message ---
--- Begin Message ---
Source: atlas-ecmwf
Source-Version: 0.25.0-3
Done: Alastair McKinstry 

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated atlas-ecmwf 
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, 24 Jun 2021 16:58:21 +0100
Source: atlas-ecmwf
Binary: libatlas-ecmwf-0 libatlas-ecmwf-0-dbgsym libatlas-ecmwf-dev 
libatlas-ecmwf-utils libatlas-ecmwf-utils-dbgsym
Architecture: source amd64
Version: 0.25.0-3
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libatlas-ecmwf-0 - Numerical weather prediction and climate modelling library
 libatlas-ecmwf-dev - Numerical weather prediction and climate modelling 
library - dev
 libatlas-ecmwf-utils - Numerical weather prediction and climate modelling 
library - util
Closes: 990284
Changes:
 atlas-ecmwf (0.25.0-3) unstable; urgency=medium
 .
   * Fix typo in arch name s/ppc54el/ppc64el/ . Closes: #990284
   * Drop OMP suppport for riscv64, sparc64 archs.
   * Enable tests for logging
Checksums-Sha1:
 bdf89378c5c5fb2b8b181087b5a47de8b177674f 2725 atlas-ecmwf_0.25.0-3.dsc
 14a19c8e1482c5ad01c05b52eb6b5a467a93d6ae 11460 
atlas-ecmwf_0.25.0-3.debian.tar.xz
 79ce53f70924394ba721b867e864067cbd9632f2 16755 
atlas-ecmwf_0.25.0-3_amd64.buildinfo
 e9b936d7adc2dcdf30c2e025590067e4f64921fb 35819496 
libatlas-ecmwf-0-dbgsym_0.25.0-3_amd64.deb
 4ca368244cbbec53580f219bcc7c53d78f6d5e9e 1879496 
libatlas-ecmwf-0_0.25.0-3_amd64.deb
 1d800650fa25fce861dfad7c2ebd4cebd6e489ea 161708 
libatlas-ecmwf-dev_0.25.0-3_amd64.deb
 6d769b1ec1a72178d5fb7cca29bd443042a58280 1018912 
libatlas-ecmwf-utils-dbgsym_0.25.0-3_amd64.deb
 0c965d0f380f55dc2731514d79a710d387b239e4 83916 
libatlas-ecmwf-utils_0.25.0-3_amd64.deb
Checksums-Sha256:
 718bf3ba74a1fadcc750e6ae0d4bfc2b84532c136603b2c1f6a2ce2a9dd1be8c 2725 
atlas-ecmwf_0.25.0-3.dsc
 2b1ea3e190017aee3ede6b95cefad65f71ac39d819f525ed5857c3b95de1a117 11460 
atlas-ecmwf_0.25.0-3.debian.tar.xz
 2ac5ee9c862179ac450f0e68ad12d4af45a6786e7e472883f00a1a415f37dd29 16755 
atlas-ecmwf_0.25.0-3_amd64.buildinfo
 a583d9357f5ae9eaa0e16fbdc3f74cf517275ad0861d215808f02c6d9fa6df53 35819496 
libatlas-ecmwf-0-dbgsym_0.25.0-3_amd64.deb
 901be888a4906b604340ee20b5b4c0a0794efc8ef79a95be4f6a5ad8c97a8a2f 1879496 
libatlas-ecmwf-0_0.25.0-3_amd64.deb
 632b07a9ffbd52e67c6c40640727313ff1b0a96d2cdc387499a1d96349c77efe 161708 
libatlas-ecmwf-dev_0.25.0-3_amd64.deb
 e93e4dbdecd1da54cc614a39675026af7f62969345b19960ae577057d5ebb568 1018912 
libatlas-ecmwf-utils-dbgsym_0.25.0-3_amd64.deb
 b035ed1db4a4557e19a5f6fb2552ea0769400a505549f3a1506622dc55bb29f0 83916 
libatlas-ecmwf-utils_0.25.0-3_amd64.deb
Files:
 03156d526115eccb66dd79cf4d609372 2725 science optional atlas-ecmwf_0.25.0-3.dsc
 b43fdce06d7e9216174775d222816e08 11460 science optional 
atlas-ecmwf_0.25.0-3.debian.tar.xz
 a7d373ec0f0e3fa0c4ba8184ebf8e785 16755 science optional 
atlas-ecmwf_0.25.0-3_amd64.buildinfo
 fb2c879f213e1610f3a982a2753ba108 35819496 debug optional 
libatlas-ecmwf-0-dbgsym_0.25.0-3_amd64.deb
 1af901ff59f82b87a420969c28987d9c 1879496 libs optional 
libatlas-ecmwf-0_0.25.0-3_amd64.deb
 9fde589794da285cef6725add110067f 161708 libdevel optional 
libatlas-ecmwf-dev_0.25.0-3_amd64.deb
 4493aa6f5e40902cc34f1bafdabe7258 

Bug#989674: netselect-apt was unable to obtain a list of valids hosts

2021-06-25 Thread Marcos Raúl Carot
Please close, this is a duplicate of #920907

Cheers,
Marcos


Bug#976343: marked as done (ruby-diaspora-federation: ftbfs with ruby-faraday 1.0)

2021-06-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Jun 2021 11:03:29 +
with message-id 
and subject line Bug#976343: fixed in ruby-diaspora-federation 0.2.6-3
has caused the Debian Bug report #976343,
regarding ruby-diaspora-federation: ftbfs with ruby-faraday 1.0
to be marked as done.

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

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


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

Package: ruby-diaspora-federation
Severity: serious
Version: 0.2.6-2

ruby-diaspora-federation ftbfs/fails autopkgtest with ruby-faraday 1.0

/usr/lib/ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not 
find 'faraday' (< 0.18.0, >= 0.9.0) - did find: [faraday-1.1.0] 
(Gem::MissingSpecVersionError)


Full log 
https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-diaspora-federation/8611484/log.gz
--- End Message ---
--- Begin Message ---
Source: ruby-diaspora-federation
Source-Version: 0.2.6-3
Done: Pirate Praveen 

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated 
ruby-diaspora-federation package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 25 Jun 2021 15:03:51 +0530
Source: ruby-diaspora-federation
Architecture: source
Version: 0.2.6-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Pirate Praveen 
Closes: 976343
Changes:
 ruby-diaspora-federation (0.2.6-3) unstable; urgency=medium
 .
   [ Cédric Boutillier ]
   * Update team name
   * Add .gitattributes to keep unwanted files out of the source package
 .
   [ Pirate Praveen ]
   * Relax dependency on faraday in gemspec to allow version 1 (Closes: #976343)
   * Bump Standards-Version to 4.5.1 (no changes needed)
Checksums-Sha1:
 effa2309162a60e0750d527aafd847292a811212 2278 
ruby-diaspora-federation_0.2.6-3.dsc
 8474e5313f1a592c15ffe19b3f424144b66420c5 14244 
ruby-diaspora-federation_0.2.6-3.debian.tar.xz
 83eaa5ad443acb52e0c6d9e8a3def792c358da84 9707 
ruby-diaspora-federation_0.2.6-3_amd64.buildinfo
Checksums-Sha256:
 ed0c8c3a564a9f4a6fa3ca9208ee5e54c2014306708d0e06a31c0436fd641736 2278 
ruby-diaspora-federation_0.2.6-3.dsc
 001b3330c80a04a08e9a4abaf1e65d8290f71b5afe28ba85c7bb95e34e1160c1 14244 
ruby-diaspora-federation_0.2.6-3.debian.tar.xz
 c4bd27a1043126135a5b48a62323698781784496416e2ed1e601038ad63f8488 9707 
ruby-diaspora-federation_0.2.6-3_amd64.buildinfo
Files:
 23dfe316e13b8d8454ef5aeddcf3e7b9 2278 ruby optional 
ruby-diaspora-federation_0.2.6-3.dsc
 ea4ed0b7f35e93a827791bd77e5626d3 14244 ruby optional 
ruby-diaspora-federation_0.2.6-3.debian.tar.xz
 5f7dee34e9374c74c71ab7290c19e2dd 9707 ruby optional 
ruby-diaspora-federation_0.2.6-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0whj4mAg5UP0cZqDj1PgGTspS3UFAmDVteQACgkQj1PgGTsp
S3XLqw//c2YpepSbG+txrTCELdPUPua4rD8A6SCjtf3MJOml1sr1TF/Eb0qfFpPT
yL6Rjm+4T7mLdi+uBqY75YjTaTXLqoO/6xPkztR8TD89hMnpJUbcdhJgom9QZezD
huaKBuBR+il9k1o8cC6VytcjIhpS9tm6+V3vIk75miJooqqULUsjGcNLXYl+OPGl
DG0zZrozGjBevPSqLBIbMrIYpgPL/msR4qE+Femm4gfzBqSXNsFqBkulURb/yHuJ
0S0vaGw75yB+cQboYWNhCH6cS/LylxxkZkzsEYFu7RuaPqkQKjbEORQ1ramE4sHo
d9td6Vlg/kipfsiSQledHcL+fpTSYoPNggUtk2BcYoXUc34Va604tIO6rhcJmon3
TjXxTGyQ7/9B6qciyLjJcBFGtzOhaoQSXXR46Tmv1uKwmqDEUfgtNGjC+KxNUZda
+u8h6CCkdsCCYDk7UhzmFnVYfkoEKmxXiB90VPsU46YEfzNgOShrPz0PTo04qpUm
L1OmUmU2zED9Ge+iN2sXRmi8tWCmk7rKgZ2LDljZCA7F6rPIY20aixbihBvoEAoa
cmnPUp1zFNz3u7nNWQWVx/9xLVsBwLNV+wlMKBYCErp9xeA9A2gLsaThRIblr2YI
PIGZTWRvDuYnJc5wObdX/YRlKRQT0d4RN8rS2VM0+12Hmj3rQt8=
=bQ0x
-END PGP SIGNATURE End Message ---


Bug#990303: trafficserver: Apache Traffic Server is vulnerable to various HTTP/1.x and HTTP/2 attacks

2021-06-25 Thread Moritz Muehlenhoff
On Fri, Jun 25, 2021 at 08:59:25AM +0200, Lorenzo Maurizi wrote:
> Package: trafficserver
> Version: 8.0.2+ds-1+deb10u4
> Severity: grave
> Tags: security
> Justification: user security hole
> 
> CVE:
> CVE-2021-27577 Incorrect handling of url fragment leads to cache poisoning
> CVE-2021-32565 HTTP Request Smuggling, content length with invalid charters
> CVE-2021-32566 Specific sequence of HTTP/2 frames can cause ATS to crash
> CVE-2021-32567 Reading HTTP/2 frames too many times
> CVE-2021-35474 Dynamic stack buffer overflow in cachekey plugin

For 8.1.x these are fixed by 
https://github.com/apache/trafficserver/commit/b82a3d192f995fb9d78e1c44d51d9acca4783277

I've add full references to the Security Tracker:
https://security-tracker.debian.org/tracker/CVE-2021-35474
https://security-tracker.debian.org/tracker/CVE-2021-32567
https://security-tracker.debian.org/tracker/CVE-2021-32566
https://security-tracker.debian.org/tracker/CVE-2021-32565
https://security-tracker.debian.org/tracker/CVE-2021-27577

Jean Baptiste, can prepare updates for buster-security?

Cheers,
Moritz



Processed: add forwarded info

2021-06-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 976343 github.com/diaspora/diaspora_federation/pull/116
Bug #976343 [ruby-diaspora-federation] ruby-diaspora-federation: ftbfs with 
ruby-faraday 1.0
Set Bug forwarded-to-address to 
'github.com/diaspora/diaspora_federation/pull/116'.
>
End of message, stopping processing here.

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



Processed: severity 985967 serious

2021-06-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 985967 serious
Bug #985967 [freeradius] freeradius: Fails to start with permission denied when 
configuring to use privileged ports
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

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



Processed: severity 985967 serious

2021-06-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 985967 serious
Bug #985967 [freeradius] freeradius: Fails to start with permission denied when 
configuring to use privileged ports
Ignoring request to change severity of Bug 985967 to the same value.
> thanks
Stopping processing here.

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



Bug#976343: ruby-diaspora-federation: ftbfs with ruby-faraday 1.0

2021-06-25 Thread Pirate Praveen
Control: forwarded -1 
https://github.com/diaspora/diaspora_federation/pull/116


On Thu, 03 Dec 2020 23:25:20 +0530 Pirate Praveen 
 wrote:
> ruby-diaspora-federation ftbfs/fails autopkgtest with ruby-faraday 
1.0


Reported upstream
https://github.com/diaspora/diaspora_federation/pull/116



Bug#989929: Suddenly restarting fetchmail started to fail with error about its global pidfile

2021-06-25 Thread Francesco P. Lovergine

On Thu, Jun 24, 2021 at 07:11:02PM +0200, László Böszörményi (GCS) wrote:

Control: tags -1 +pending moreinfo

On Wed, Jun 16, 2021 at 10:00 AM Francesco P. Lovergine
 wrote:

This is currently run on testing since ages. I had to restart due to a changed
fingerprint and the global service started to fail with:

[...]

giu 16 08:07:28 klecker fetchmail[846499]: fetchmail: lock creation failed, pidfile 
"/run/fetchmail/fetchmail.pid": File o directory non esistente

Thanks for the report and the proposed fix! Can you please check if
the updated package[1] is fine for you now?

Cheers,
Laszlo/GCS
[1] dget -x https://people.debian.org/~gcs/fetchmail_6.4.16-2.dsc



Yes it is working. 


--
Francesco P. Lovergine



Processed: found 990303 in 8.1.1+ds-1

2021-06-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 990303 8.1.1+ds-1
Bug #990303 [trafficserver] trafficserver: Apache Traffic Server is vulnerable 
to various HTTP/1.x and HTTP/2 attacks
Marked as found in versions trafficserver/8.1.1+ds-1.
> thanks
Stopping processing here.

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



Processed: tagging 990303

2021-06-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 990303 + upstream
Bug #990303 [trafficserver] trafficserver: Apache Traffic Server is vulnerable 
to various HTTP/1.x and HTTP/2 attacks
Added tag(s) upstream.
> thanks
Stopping processing here.

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



Processed: Re: Bug#982758: webext-browserpass: Failed to install on upgrade to bullseye

2021-06-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 982758 important
Bug #982758 [webext-browserpass] webext-browserpass: Failed to install on 
upgrade to bullseye
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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



Bug#982758: webext-browserpass: Failed to install on upgrade to bullseye

2021-06-25 Thread Michael Meskes
severity 982758 important
thanks

> I tried with a stable chroot, then installed all the webext* packages you have
> installed and then upgraded webext-browserpass. Works like a charm.

By now I've ran more test up to a full system dist-upgrade with all webext* 
packages installed, not a single failure.

> > Good question. My gut feeling at least says that the RC severity is
> > justified as quite some people ran into it and it actually causes apt
> > to abort in a quite nasty way.
> 
> I see your point, the problem is with this setting nobody is getting the
> software because of some of us having issues in the upgrade. I'd love to get
> this fixed before the freeze, but no matter what I tried I cannot reproduce.

Given that freeze is nearing and nobody's volunteering any additional
information and the bug has proven to be not reproducible, at least for me, I
downgrade it again. Yes, it can be very severe but removing the package for
everyone doesn't seem right either. Maybe by keeping it in we will get more
data to find out where the problem lies.

I'm more than willing to look into it again and fix it once we identify the 
reason.

Thanks,
Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De
Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org



Bug#990303: trafficserver: Apache Traffic Server is vulnerable to various HTTP/1.x and HTTP/2 attacks

2021-06-25 Thread Lorenzo Maurizi
Package: trafficserver
Version: 8.0.2+ds-1+deb10u4
Severity: grave
Tags: security
Justification: user security hole



-- System Information:
Debian Release: 10.10
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages trafficserver depends on:
ii  adduser  3.118
ii  libbrotli1   1.0.7-2+deb10u1
ii  libc62.28-10
ii  libcap2  1:2.25-2
ii  libcurl4 7.64.0-4+deb10u2
ii  libgcc1  1:8.3.0-6
ii  libgeoip11.6.12-1
ii  libhwloc51.11.12-3
ii  libluajit-5.1-2  2.1.0~beta3+dfsg-5.1
ii  liblzma5 5.2.4-1
ii  libncursesw6 6.1+20181013-2+deb10u2
ii  libpcre3 2:8.39-12
ii  libssl1.11.1.1d-0+deb10u6
ii  libstdc++6   8.3.0-6
ii  libtcl8.68.6.9+dfsg-2
ii  libtinfo66.1+20181013-2+deb10u2
ii  libunwind8   1.2.1-10~deb10u1
ii  libyaml-cpp0.6   0.6.2-4
ii  lsb-base 10.2019051400
ii  perl 5.28.1-6+deb10u1
ii  zlib1g   1:1.2.11.dfsg-1

trafficserver recommends no packages.

Versions of packages trafficserver suggests:
pn  trafficserver-experimental-plugins  

-- Configuration Files:
/etc/trafficserver/ip_allow.config changed [not included]
/etc/trafficserver/records.config changed [not included]

-- no debconf information

Description:
ATS is vulnerable to various HTTP/1.x and HTTP/2 attacks

CVE:
CVE-2021-27577 Incorrect handling of url fragment leads to cache poisoning
CVE-2021-32565 HTTP Request Smuggling, content length with invalid charters
CVE-2021-32566 Specific sequence of HTTP/2 frames can cause ATS to crash
CVE-2021-32567 Reading HTTP/2 frames too many times
CVE-2021-35474 Dynamic stack buffer overflow in cachekey plugin

Version Affected:
ATS 7.0.0 to 7.1.12
ATS 8.0.0 to 8.1.1
ATS 9.0.0 to 9.0.1

Mitigation:
7.x users should upgrade to 8.1.2 or 9.0.2, or later versions 8.x users should 
upgrade to 8.1.2 or later versions 9.x users should upgrade to 9.0.2 or later 
versions