Bug#970443: mira: FTBFS due to race condition during doc build

[Sven Mueller]

Ooops, sorry, forgot the attachment.

Am Mi., 16. Sept. 2020 um 14:58 Uhr schrieb Andreas Tille :

> Hi Sven,
>
> On Wed, Sep 16, 2020 at 02:49:54PM +0200, Sven Mueller wrote:
> > Package: mira
> > Version: 4.9.6-4
> > Tags: patch
>
> Thanks a lot for your investigation.  You promised some patch and you
> also tagged the bug that way.  But I did not found any actual patch
> attached to this bug report.  Did you possibly just forgot to attach it?
>
> Kind regards
>
>Andreas.
>
> --
> http://fam-tille.de
>
Index: mira-4.9.6/doc/docbook/Makefile.am
===
--- mira-4.9.6.orig/doc/docbook/Makefile.am
+++ mira-4.9.6/doc/docbook/Makefile.am
@@ -19,7 +19,7 @@ EXTRA_DIST = ${CHAP_XML} book_definitive
 clean-local:
 	rm -rf *html *pdf versionfile
 
-%_part.html: %_part.xml
+%_part.html: %_part.xml versionfile
 	@echo "Making .html out of _part.xml" $@
 	@$(SHELL) -ec 'xsltproc --nonet --xinclude --output $@  $(top_srcdir)/doc/docbook/mira.xsl $<'
 

Bug#970446: gstreamer1.0-plugins-base:amd64: Caught a segmentation fault libgsttypefindfunctions.so

[Kai Weber]

Package: gstreamer1.0-plugins-base
Version: 1.18.0-2
Severity: important

When running totem on any Video (mp4, avi, mov) file I get a "Segmentation 
fault". This
affects two systems running Sid. I would like to help debug this issue.

$ totem Videos/The\ secret\ behind\ many\ great\ engineering\ organizations.mp4

(totem:113386): GLib-CRITICAL **: 15:18:47.362: g_propagate_error: assertion 
'src != NULL' failed

(totem:113386): GLib-GIO-CRITICAL **: 15:18:47.362: g_task_return_error: 
assertion 'error != NULL' failed

(totem:113386): GLib-GIO-CRITICAL **: 15:18:47.374: g_task_propagate_boolean: 
assertion 'task->result_set' failed

ERROR: Caught a segmentation fault while loading plugin file:
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgsttypefindfunctions.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap --gst-disable-registry-fork and debug.
Segmentation fault



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

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

Versions of packages gstreamer1.0-plugins-base:amd64 depends on:
ii  libc6   2.31-3
ii  libcdparanoia0  3.10.2+debian-13+b1
ii  libglib2.0-02.66.0-2
ii  libgstreamer-plugins-base1.0-0  1.18.0-2
ii  libgstreamer1.0-0   1.18.0-3
ii  libogg0 1.3.2-1+b1
ii  libopus01.3-1+b1
ii  liborc-0.4-01:0.4.32-1
ii  libtheora0  1.1.1+dfsg.1-15
ii  libvisual-0.4-0 0.4.0-17
ii  libvorbis0a 1.3.6-2
ii  libvorbisenc2   1.3.6-2

gstreamer1.0-plugins-base:amd64 recommends no packages.

Versions of packages gstreamer1.0-plugins-base:amd64 suggests:
ii  gvfs  1.44.1-1+b1

-- no debconf information

Bug#970445: libfarstream-0.2-5: can't connect to video call via pidgin sipe

[Nils Reichert]

Package: libfarstream-0.2-5
Version: 0.2.8-4.1
Severity: normal
Tags: upstream

Dear Maintainer,


   * What led up to the situation?
In Pidgin, using the SIPE-Plugin, attempt to make a video call.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Attempt to make video call: in chat window/contact list select contact 
and click "voice/video-call"
   * What was the outcome of this action?
Setting up video call fails with error mesage "Error with your webcam"
   * What outcome did you expect instead?
Video call should be set up correctly
   * Possible solution:
This is a known problem documented in the plugins FAQ at 
https://sourceforge.net/p/sipe/wiki/Frequently%20Asked%20Questions/#video-call-setup-fails-with-the-error-message-error-with-your-webcam
The farstream version included in buster predates the patch mentioned 
there. Please include the patch or provide a newer version via backports.
   * Thanks:
Thank You!


-- System Information:
Distributor ID: Bunsenlabs
Description:BunsenLabs GNU/Linux 10.5 (Lithium)
Release:10.5
Codename:   buster
Architecture: x86_64

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

Versions of packages libfarstream-0.2-5 depends on:
ii  libc6   2.28-10
ii  libglib2.0-02.58.3-2+deb10u2
ii  libgstreamer-plugins-base1.0-0  1.14.4-2
ii  libgstreamer1.0-0   1.14.4-1
ii  libgupnp-1.0-4  1.0.3-3
ii  libgupnp-igd-1.0-4  0.2.5-3
ii  libnice10   0.1.14-1

Versions of packages libfarstream-0.2-5 recommends:
ii  gstreamer1.0-nice  0.1.16-1~bpo10+1
ii  gstreamer1.0-plugins-bad   1.14.4-1+b1
ii  gstreamer1.0-plugins-base  1.14.4-2
ii  gstreamer1.0-plugins-good  1.14.4-1

libfarstream-0.2-5 suggests no packages.

-- no debconf information

Bug#970444: Can't connect to httpd stream on MPD

[James Klaas]

Package: mpd
Version: 0.21.5-3

I can no longer access the httpd mpd stream and I think this happened
after I upgraded to Buster.

I'm using the version of mpd.conf from the installation.

I set the music_directory entry and set audio_output to httpd stream.
Here's my audio_output section:

audio_output {
type"httpd"
name"My HTTP Stream"
encoder "vorbis"# optional, vorbis or lame
port"8000"
bind_to_address "0.0.0.0"   # optional, IPv4 or IPv6
#   quality "5.0"   # do not define if bitrate
is defined
bitrate "128"   # do not define if quality
is defined
format  "44100:16:1"
#   max_clients "0" # optional 0=no limit
}

If I try to connect to the httpd stream with curl for testing I get
the following:

curl http://192.168.47.122:8000
curl: (7) Failed to connect to 192.168.47.122 port 8000: Connection refused

I can connect to the 6600 port without issue:

curl http://192.168.47.122:6600
OK MPD 0.21.11

If I talk to the mpd server and ask for outputs, it says the stream is enabled:

mpc -h 192.168.47.122 outputs
Output 1 (My HTTP Stream) is enabled

Bug#970443: mira: FTBFS due to race condition during doc build

[Andreas Tille]

Hi Sven,

On Wed, Sep 16, 2020 at 02:49:54PM +0200, Sven Mueller wrote:
> Package: mira
> Version: 4.9.6-4
> Tags: patch

Thanks a lot for your investigation.  You promised some patch and you
also tagged the bug that way.  But I did not found any actual patch
attached to this bug report.  Did you possibly just forgot to attach it?

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#969349: buster-pu: package chrony/3.4-4+deb10u1

[Vincent Blut]

Hi,

On 2020-08-31T21:34+0200, Vincent Blut wrote:

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

[ Reason ]
chrony versions prior to 3.5.1 are vulnerable to a symlink race when
creating the PID file. CVE-2020-14367 has been assigned to this
vulnerability.

In accordance with Salvatore Bonaccorso from the security team, no DSA
has been released.

[ Impact ]
Data loss and a denial of service due to the path traversal are possible
in some cases.
While that sounds worrisome, this vulnerabilily can’t be exploited using
the default configuration provided by chrony on Debian, that’s why the
security team marked it as “unimportant”.

[ Tests ]
I manually tested the proposed update to ensure that chronyd still runs
fine using the default PID file location and an alternative one where
the vulnerability could be exploited. I can confirm that the issue is
fixed by the proposed patch and that no regression appeared while
testing.

[ Risks ]
Most of the other major distributions provide this patch now with no
apparent problems, so the risks seem quite low.

[ Checklist ]
 [X] *all* changes are documented in the d/changelog
 [X] I reviewed all changes and I approve them
 [X] attach debdiff against the package in (old)stable
 [X] the issue is verified as fixed in unstable

[ Changes ]
Switch from fopen() to the open() function with the O_CREAT|O_EXCL flags
to avoid following a symlink and writing the PID to an unexpected file
when chronyd still has the root privileges.

[ Other info ]
I also took the oportunity to fix the autopkgtest of chrony which was
failing on Buster since quite a while.


In the meantime, Matt Corallo encountered a limitation in our AppArmor 
profile, which prevents the use of the “tempcomp” directive (#970421).


Updated debdiff attached.

Cheers,
Vincent
diff -Nru chrony-3.4/debian/changelog chrony-3.4/debian/changelog
--- chrony-3.4/debian/changelog 2019-03-18 19:35:34.0 +0100
+++ chrony-3.4/debian/changelog 2020-09-16 13:44:04.0 +0200
@@ -1,3 +1,19 @@
+chrony (3.4-4+deb10u1) buster; urgency=medium
+
+  * debian/patches/:
+- Add create-new-file-when-writing-pidfile.patch to prevent symlink race
+when writing to PID file (CVE-2020-14367).
+
+  * debian/tests/:
+- Fix a regression when running upstream-simulation-test-suite autopkgtest
+on Buster.
+
+  [ Matt Corallo ]
+  * debian/usr.sbin.chronyd:
+- Fix temperature reading. (Closes: #970421)
+
+ -- Vincent Blut   Wed, 16 Sep 2020 13:44:04 +0200
+
 chrony (3.4-4) unstable; urgency=medium
 
   * debian/patches/*:
diff -Nru chrony-3.4/debian/.gitlab-ci.yml chrony-3.4/debian/.gitlab-ci.yml
--- chrony-3.4/debian/.gitlab-ci.yml2019-03-18 19:35:34.0 +0100
+++ chrony-3.4/debian/.gitlab-ci.yml2020-09-16 13:40:06.0 +0200
@@ -1,20 +1,7 @@
-include: 
https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml
+include:
+  - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml
+  - 
https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml
 
-build:
-extends: .build-unstable
 
-reprotest:
-extends: .test-reprotest
-
-lintian:
-extends: .test-lintian
-
-autopkgtest:
-extends: .test-autopkgtest
-allow_failure: true
-
-piuparts:
-extends: .test-piuparts
-
-blhc:
-extends: .test-blhc
+variables:
+  RELEASE: 'buster'
diff -Nru chrony-3.4/debian/patches/create-new-file-when-writing-pidfile.patch 
chrony-3.4/debian/patches/create-new-file-when-writing-pidfile.patch
--- chrony-3.4/debian/patches/create-new-file-when-writing-pidfile.patch
1970-01-01 01:00:00.0 +0100
+++ chrony-3.4/debian/patches/create-new-file-when-writing-pidfile.patch
2020-09-16 13:40:06.0 +0200
@@ -0,0 +1,187 @@
+From f00fed20092b6a42283f29c6ee1f58244d74b545 Mon Sep 17 00:00:00 2001
+From: Miroslav Lichvar 
+Date: Thu, 6 Aug 2020 09:31:11 +0200
+Subject: main: create new file when writing pidfile
+
+When writing the pidfile, open the file with the O_CREAT|O_EXCL flags
+to avoid following a symlink and writing the PID to an unexpected file,
+when chronyd still has the root privileges.
+
+The Linux open(2) man page warns about O_EXCL not working as expected on
+NFS versions before 3 and Linux versions before 2.6. Saving pidfiles on
+a distributed filesystem like NFS is not generally expected, but if
+there is a reason to do that, these old kernel and NFS versions are not
+considered to be supported for saving files by chronyd.
+
+This is a minimal backport specific to this issue of the following
+commits:
+- commit 2fc8edacb810 ("use PATH_MAX")
+- commit f4c6a00b2a11 ("logging: call exit() in LOG_Message()")
+- commit 7a4c396bba8f ("util: add functions for common file operations")
+- commit e18903a6b563 ("switch to new util file functions")
+
+Reported-by: Matthias Gerstner 
+
+--- a/logging.c
 

Bug#970443: mira: FTBFS due to race condition during doc build

[Sven Mueller]

Package: mira
Version: 4.9.6-4
Tags: patch

When building concurrently, the doc/docbook/*_part.html files can fail to
generate. The reason is - as far as I can tell, that the %_part.html rule
in doc/docbook/Makefile.in doesn't list versionfile as a dependency, but
several of the _part.xml files actually depend on the file to be both
present and parsable. The error actually indicates the "could not load
versionfile" error - It is unclear though if it is not present or not
completely generated. But with "make -j 8", this is fails reproducibly (not
always, but very often). Changing Makefile.am as in the attached patch
seems to fix this.

Site note: Strictly speaking, most rules should also have a dependency on
the copyright file, as the output would change if the
copyrightfile changes. But since there is no rule to re-generate that file
and no generated files are shipped with the package, that seems minor.

Here is the snippet from the build log:

make[2]: Entering directory '/<>/doc'
Making all in docbook
make[3]: Entering directory '/<>/doc/docbook'
Making versionfile
Making .html out of _part.xml chap_bitsandpieces_part.html
Making .html out of _part.xml chap_mirautils_part.html
Making .html out of _part.xml chap_est_part.html
Making .html out of _part.xml chap_faq_part.html
Making .html out of _part.xml chap_hard_part.html
Making .html out of _part.xml chap_logfiles_part.html
Making .html out of _part.xml chap_maf_part.html
versionfile:3: parser error : Start tag expected, '<' not found

^
chap_bitsandpieces_part.xml:5: element include: XInclude error : could not
load versionfile, and no fallback was found
Making .html out of _part.xml chap_reference_part.html
versionfile:3: parser error : Start tag expected, '<' not found

^
chap_est_part.xml:5: element include: XInclude error : could not load
versionfile, and no fallback was found
make[3]: *** [Makefile:484: chap_bitsandpieces_part.html] Error 6
make[3]: *** Waiting for unfinished jobs
make[3]: *** [Makefile:484: chap_est_part.html] Error 6
make[3]: Leaving directory '/<>/doc/docbook'
make[2]: *** [Makefile:381: all-recursive] Error 1
make[2]: Leaving directory '/<>/doc'
dh_auto_build: error: cd doc && make -j8 "INSTALL=install
--strip-program=true" returned exit code 2
make[1]: *** [debian/rules:37: override_dh_auto_build-indep] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:14: build] Error 2

Bug#970442: libopenmpi-dev/sid and openmpi-bin/stable ship the same file

[Uwe Kleine-König]

Package: libopenmpi-dev
Version: 4.0.5-3
Severity: serious
Justification: Policy 7.4

During an apt run on a machine that runs a mix of stable and
testing/unstable I hit:

dpkg: error processing archive 
/tmp/apt-dpkg-install-HP9Wwp/08-libopenmpi-dev_4.0.5-3_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man1/oshmem_info.1.gz', which is 
also in package openmpi-bin 3.1.3-11 

This was also already noticed by piuparts:

https://piuparts.debian.org/stable2sid/fail/libopenmpi-dev_4.0.5-3.log

which can be consulted for a complete apt log.

Best regards
Uwe

Bug#858201: planning to drop compass-bootstrap-sass-plugin binary package

[Pirate Praveen]

Hi Jonas,

I'm going to remove compass-bootstrap-sass-plugin binary from 
ruby-bootstrap-sass, but thought of just checking with you before I 
proceed.


Also I will be uploading version 3.4.1 in experimental to unstable soon.

Thanks
Praveen

Bug#970441: libnuspell-dev: typo in long description: germand

[Jonas Smedegaard]

Package: libnuspell-dev
Version: 3.0.0-1
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Long description contains this:

> Support complex compounds (for example, Hungarian, Germand and Dutch)

There is no "d" in german.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl9iA7wACgkQLHwxRsGg
ASHeAg//V3goux+uG4Wld7p784lj5whj0Pc6/nw1sHXo6KAjlBJgzbivtmE/giRs
R18Rr8qKmn69VBoUbWZcoyCZaq1eC4PbxBCsQ96rFlBggBtxRW/Q5jlDuURh/4qu
QabjXyJxrpixVLX+nU5emKodGno6QLgeT/Jx+ZCi4+wTcti+bXZXVeLGUn8EEdto
zYmhdI3po+zNQsa/kaPHLmYIgJ0CuzKJwBHagRqeg/m5iAJ4OH1HUjpT6P9WeynP
OeQ7Rf6sKTKEkLRlNHN0SlyNF++3PpwpttlC/4YGVh7fhBmLHC2Ol96YGua9yysQ
SO/WZemNmgsoJ6cGebDH2wlZcwVMwfskrpDs6yrf5d+4pLylVLLi0L4is4dKF4gl
QVvlCKBK/TpCjIVEo7ZdwawywJGeQjF992nwjECXWQ4aEY++zjnlxtKR/A1QWBx2
PusELi7qwK8QualmRjpQWGD8tpsaOxc7/TDYVvB3OryXiED5YrwO+MHxbb+aEGyd
+HNjSJQfkBBgMQT+BZiUEu2OI29zuMg5HzIPti16SKvarD8TyUpD9LBLIP6ReN9t
AXmBzE5UkEsplnCaMvv5nVj3VoErtJp71BUMhw1Fcbsi4QLyCNGP1wZGzExXASGi
dioMqt/wRPvwaOf7g8pV3o6FCIQTVffU+zOMe5hy5IYcqdAjkQQ=
=Bqvm
-END PGP SIGNATURE-

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

[Koutheir Attouchi]

If the package is gone, but it was the only manually installed package to
get Python, then the whole Python distribution becomes auto-removable,
unless people manually mark the python2 and/or python3 as manually
installed.

Many people will just find out that they don't have python support anymore,
even though they installed python manually in the past. There should have
been some change log to notify people about this change and the needed
manual intervention.

On Wed, Sep 16, 2020 at 4:50 AM Matthias Klose  wrote:

> Control: severity -1 important
> Control: merge -1 970375
>
> On 9/16/20 3:45 AM, Koutheir Attouchi wrote:
> > Package: python
> > Version: 2.7.17-2
> > Severity: grave
> > Justification: renders package unusable
> > X-Debbugs-Cc: kouth...@gmail.com
> >
> > Dear Maintainer,
> >
> > What led up to the situation?
> >
> > ```
> > $ sudo apt-get install python
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > Some packages could not be installed. This may mean that you have
> > requested an impossible situation or if you are using the unstable
> > distribution that some required packages have not yet been created
> > or been moved out of Incoming.
> > The following information may help to resolve the situation:
> >
> > The following packages have unmet dependencies:
> >  python : PreDepends: python-minimal (= 2.7.17-2) but it is not going to
> be
> > installed
> >   Depends: libpython-stdlib (= 2.7.17-2) but it is not going to
> be
> > installed
> >   Depends: python2 (= 2.7.17-2) but 2.7.18-2 is to be installed
> > E: Unable to correct problems, you have held broken packages.
> > ```
> >
> > In order to keep other python packages, I marked the `python2` and
> `python3`
> > packages as manually installed.
>
>
> no, the python package is gone.
>


-- 
Dr. Koutheir Attouchi.

Bug#970440: apt-get update could show that not running as root when it fails

[Jonny Grant]

Package: apt
Version: 2.0.2ubuntu0.1 

Current output:

$ apt-get update
Reading package lists... Done
E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission 
denied)
E: Unable to lock directory /var/lib/apt/lists/
W: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: 
Permission denied)
W: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches 
(13: Permission denied)


Expected output:

$ apt-get update
Reading package lists... Done
E: Could not open lock file /var/lib/apt/lists/lock not running as root - open 
Permission denied
E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission 
denied)
E: Unable to lock directory /var/lib/apt/lists/
W: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: 
Permission denied)
W: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches 
(13: Permission denied)


it's easy enough to check uid is 0 by calling getuid()

There's no real reason to show the errno value 13, we don't all know these by 
heart. you could put EPERM if you wish to use the macro name

Bug#970424: llvm-toolchain-7 7.0.1-8+deb10u1 flagged for acceptance

[Julien Cristau]

package release.debian.org
tags 970424 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: llvm-toolchain-7
Version: 7.0.1-8+deb10u1

Explanation: fix bugs affecting rustc build

Bug#970439: ITP: ruby-rqrcode-core -- library to encode QR Codes

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 

Package https://rubygems.org/gems/rqrcode_core

rqrcode_core is a Ruby library for encoding QR Codes. The simple
interface (with no runtime dependencies) allows you to create QR Code 
data

structures.
.
Features:
 * rqrcode_core is a ruby only library. It requires no native 
libraries. Just

 Ruby!
 * It is an encoding library. It cannot be used to decode QR codes.
 * The interface is simple and assumes the user just want to encode a 
string

 into a QR code.
.
rqrcode_core is the basis of the popular rqrcode library, which allows 
one
to generate different renderings of your QR code, including png, svg 
and

ansi.

This is a new dependency for ruby-qrcode 1.x

Bug#970438: imagemagick-6.q16: typo in manpage of montage-im6.q16

[Sven Dreyer]

Package: imagemagick-6.q16
Version: 8:6.9.10.23+dfsg-2.1+deb10u1
Severity: minor
Tags: upstream

Dear Maintainer,

the manpage of montage-im6.q16 contains a typo:


  -colorspace type alternate image colorsapce


Replace "colorsapce" with "colorspace".

Thanks!
Sven


-- Package-specific info:
ImageMagick program version
---
animate:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
compare:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
convert:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
composite:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
conjure:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
display:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
identify:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
import:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
mogrify:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
montage:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
stream:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org

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

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

Versions of packages imagemagick-6.q16 depends on:
ii  hicolor-icon-theme 0.17-2
ii  libc6  2.28-10
ii  libmagickcore-6.q16-6  8:6.9.10.23+dfsg-2.1+deb10u1
ii  libmagickwand-6.q16-6  8:6.9.10.23+dfsg-2.1+deb10u1

Versions of packages imagemagick-6.q16 recommends:
ii  ghostscript  9.27~dfsg-2+deb10u4
pn  libmagickcore-6.q16-6-extra  
ii  netpbm   2:10.0-15.3+b2

Versions of packages imagemagick-6.q16 suggests:
pn  autotrace   
pn  cups-bsd | lpr | lprng  
ii  curl7.64.0-4+deb10u1
pn  enscript
ii  ffmpeg  7:4.1.6-1~deb10u1
pn  gimp
pn  gnuplot 
pn  grads   
pn  graphviz
ii  groff-base  1.22.4-3
pn  hp2xx   
pn  html2ps 
pn  imagemagick-doc 
pn  libwmf-bin  
pn  mplayer 
pn  povray  
pn  radiance
ii  sane-utils  1.0.27-3.2
pn  texlive-base-bin
pn  transfig
pn  ufraw-batch 
pn  xdg-utils   

-- no debconf information

Bug#970402: transition: log4cxx

[Tobias Frost]

On Tue, 15 Sep 2020 21:29:50 +0200 Emilio Pozuelo Monfort 
 > > Waiting for the green light from you ;-)
> 
> Go ahead.

the new log4xx 0.11 is now in unstable and has built on all release archs.

(So, I guess the binmnu party can start now ;-) 


Cheers,
-- 
tobi

Bug#970437: libpcap0.8: typo in manpage of pcap-filter

[Sven Dreyer]

Package: libpcap0.8
Version: 1.8.1-6
Severity: minor
Tags: upstream

Dear Maintainer,

the manpage of pcap-filter contains a typo:


mpls [label_num]
   True  if  the  packet  is  an MPLS packet.  If [label_num] is specified, 
only true is the packet has the specified label_num.


Replace "true is" with "true if".

Thanks!
Sven


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

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

Versions of packages libpcap0.8 depends on:
ii  libc6  2.28-10

libpcap0.8 recommends no packages.

libpcap0.8 suggests no packages.

-- no debconf information

Bug#970436: vsftpd: typo in manpage of vsftpd.conf

[Sven Dreyer]

Package: vsftpd
Version: 3.0.3-12
Severity: minor
Tags: upstream

Dear Maintainer,

the manpage of vsftpd.conf contains a typo:


user_sub_token
   This option is useful is conjunction with virtual users.


Replace "is conjunction" with "in conjunction".

Thanks!
Sven


-- Package-specific info:

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

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

Versions of packages vsftpd depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.71
ii  libc6  2.28-10
ii  libcap21:2.25-2
ii  libpam-modules 1.3.1-5
ii  libpam0g   1.3.1-5
ii  libssl1.1  1.1.1d-0+deb10u3
ii  libwrap0   7.6.q-28
ii  lsb-base   10.2019051400
ii  netbase5.6
ii  procps 2:3.3.15-2

Versions of packages vsftpd recommends:
ii  logrotate  3.14.0-4
ii  ssl-cert   1.0.39

vsftpd suggests no packages.

-- Configuration Files:
/etc/vsftpd.conf changed [not included]

-- debconf information excluded

Bug#970428: ITP: golang-gopkg-cheggaaa-pb.v3 -- Console progress bar for Golang

[Andreas Henriksson]

On Wed, Sep 16, 2020 at 11:28:03AM +0200, Andreas Henriksson wrote:
> * Package name: golang-gopkg-cheggaaa-pb.v3
>   Version : 1.0.29-1
[...]

Actually 'version' is 3.0.7 this confusion seems to be related
to what I'm about to mention next. (Can I call it the 'go import path
circus'?)

First see https://github.com/cheggaaa/pb/issues/155

So apparently now all code has moved into a v3 subdirectory
(unlike v1 and v2), for the potential benefit of the go mod tool I
guess.
Also note that the root directory of the git repo still contains
some pre-v3 implementation of cheggaaa's pb (with a different API).

This possibly means that using gopkg(.in) in the package name
as well as the pb.v3 naming should be abandoned in the
debian package name? Possibly it should now instead become:
- golang-github-cheggaaa-pb(-dev)
unlike previous versions in the debian archive which are named:
- golang-gopkg-cheggaaa-pb.v1(-dev)
- golang-gopkg-cheggaaa-pb.v2(-dev)

I've asked for advice on the #debian-golang channel. Feedback welcome
if anyone knows the best way to handle this problem.

Sigh. As mentioned, If anyone else wants to do this package... - please!

Regards,
Andreas Henriksson

Bug#970430: libpython-stdlib: unresolvable dependency libpython2-stdlib (= 2.7.17-2), actual libpython2-stdlib (2.7.18-2)

[Matthias Klose]

On 9/16/20 11:34 AM, Egor Sokolenko wrote:
> libpython-stdlib cannot be installed on bullseye/sid because it depends on  
> libpython2-stdlib (= 2.7.17-2), but current is libpython2-stdlib (2.7.18-2)

correct. See https://lists.debian.org/debian-python/2020/07/msg00039.html

Bug#900958: ITP: barebox-host-tools -- useful development tools from the barebox source tree

[Uwe Kleine-König]

Control: retitle 900958 ITP bareobx -- a bootloader and its host tools
Control: owner 900958 !

Hello,

On Thu, Nov 29, 2018 at 11:14:36AM +0100, Roland Hieber wrote:
> For the record, the current problem is assembling debian/copyright
> automatically according to DEP-5. The file headers and copyright holders
> are not always recognizable by licensecheck, but upstream is discussing
> about using SPDX in the future, so I'll wait if that helps.

I'm working on this (again) and intend to package barebox not only to
provide a tools package but also some bootloader images.

Roland told me that he currently doesn't find the time to maintain
barebox, so I'm taking over this ITP.

Best regards
Uwe

-- 
Pengutronix e.K.   | Uwe Kleine-König|
Industrial Linux Solutions | https://www.pengutronix.de/ |


signature.asc
Description: PGP signature

Bug#446036: Hi

[Adams]

Hello,

I'm Adams, did you receive my previous correspondence concerning a relative
of your country who died in a car accident with his family? Please get back
to me to receive more details of his fund worth $9.2 million dollars.

Regards,
Adams.

Bug#970434: mira: FTBFS with current docbook

[Sven Mueller]

Looks like the error isn't caused by docbook. Trying to track this down
some more and hopefully also provide a fix.

Bug#970435: debmirror: manpage of debmirror contains wrong example

[Sven Dreyer]

Package: debmirror
Version: 1:2.32
Severity: minor

Dear Maintainer,

the manpage of debmirror contains examples of how to call debmirror.

For one of the examples, the explanation does not match the example code:


Make a mirror of i386 and sparc binaries, main only, and include both unstable 
and testing versions of Debian; download from 'ftp.kernel.org':

  debmirror -a i386,sparc -d sid -d etch -s main --nosource \
-h ftp.nl.debian.org --progress $HOME/mirror/debian


The explanation says that download starts from ftp.kernel.org, but the example 
downloads from ftp.nl.debian.org.

Either the example or the explanation needs to be corrected.

Thanks!
Sven


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

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

Versions of packages debmirror depends on:
ii  bzip21.0.6-9.2~deb10u1
pn  libdigest-md5-perl   
pn  libdigest-sha-perl   
ii  liblockfile-simple-perl  0.208-1
ii  libwww-perl  6.36-2
ii  perl [libnet-perl]   5.28.1-6+deb10u1
ii  rsync3.1.3-6
ii  xz-utils 5.2.4-1

Versions of packages debmirror recommends:
pn  ed 
ii  gpgv   2.2.12-1+deb10u1
ii  patch  2.7.6-3+deb10u1

Versions of packages debmirror suggests:
ii  gnupg  2.2.12-1+deb10u1

-- no debconf information

Bug#970427: buster-pu: package rust-cbindgen/0.14.4-1~deb10u1

[Emilio Pozuelo Monfort]

On 16/09/2020 12:12, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Wed, 2020-09-16 at 11:24 +0200, Emilio Pozuelo Monfort wrote:
>> This updates rust-cbindgen to 0.14. In order to do that we have to
>> embed the build-deps, like we did for 0.8.7 in stretch.
>>
>> I have disabled the -dev packages. buster only has librust-cbindgen-
>> dev, which has no (build-)rdeps, so we could decruft the old version
>> with this update.
>> The alternative would be to keep building it, but I'm not sure how
>> that would work given the deps are not available in buster. We'd
>> probably need to ship the vendored deps in the -dev, possibly causing
>> upgrade issues due to file overwrites when installing the standalone
>> packages from bullseye, so I didn't bother investigating that route.
>> pkg-rust-maintainers@ in Cc in case they have any comments.
>>
>> Debdiff from 0.14 in [1] due to the size. I haven't uploaded it yet,
>> please let me know if the plan to not build and decruft librust-
>> cbindgen-dev is good and I'll proceed with the upload.
> 
> Under the circumstances it seems like a reasonable plan. Please go
> ahead.

Thanks. Uploaded after bumping the rustc and cargo build-dependencies
(it won't build with the old rust at least).

Cheers,
Emilio

Bug#970421: apparmor limit blocks temperature reading

[Vincent Blut]

Hello Matt,

On 2020-09-15T23:11-0400, Matt Corallo wrote:

Package: chrony
Version: 3.4-4

Current apparmor profile for chrony lists
@{sys}/class/hwmon/hwmon[0-9]*/temp[0-9]*_input r,

which is great (and even how I have mine configured -
tempcomp /sys/class/hwmon/hwmon0/temp1_input 1 0 0 0 0) but it doesn't actually 
work. It results in lots of log lines like

Sep 15 23:06:37 gw.as397444.net audit[24397]: AVC apparmor="DENIED" 
operation="open" profile="/usr/sbin/chronyd" 
name="/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input" 
pid=24397 comm="chronyd" requested_mask="r" denied_mask="r" fsuid=112 
ouid=0

Sep 15 23:06:37 gw.as397444.net chronyd[24397]: Could not read temperature from 
/sys/class/hwmon/hwmon0/temp1_input
Sep 15 23:06:37 gw.as397444.net kernel: audit: type=1400 
audit(1600225597.313:127): apparmor="DENIED" operation="open" 
profile="/usr/sbin/chronyd" 
name="/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input" 
pid=24397 comm="chronyd" requested_mask="r" denied_mask="r" fsuid=112 
ouid=0


Indeed, same behaviour here. AFAIR, when I wrote the aforementioned 
rule, it was sufficient for the proper functioning of the “tempcomp” 
directive, so this might be related to some changes in the kernel.


Looks like somehow apparmor is resolving the file to a different path, 
checking, and then failing it.


An extra line like the following fixes it:
@{sys}/devices/virtual/thermal/thermal_zone[0-9]*/hwmon[0-9]*/temp[0-9]*_input 
r,


Looks good!


Matt


Cheers,
Vincent


signature.asc
Description: PGP signature

Bug#970427: buster-pu: package rust-cbindgen/0.14.4-1~deb10u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Wed, 2020-09-16 at 11:24 +0200, Emilio Pozuelo Monfort wrote:
> This updates rust-cbindgen to 0.14. In order to do that we have to
> embed the build-deps, like we did for 0.8.7 in stretch.
> 
> I have disabled the -dev packages. buster only has librust-cbindgen-
> dev, which has no (build-)rdeps, so we could decruft the old version
> with this update.
> The alternative would be to keep building it, but I'm not sure how
> that would work given the deps are not available in buster. We'd
> probably need to ship the vendored deps in the -dev, possibly causing
> upgrade issues due to file overwrites when installing the standalone
> packages from bullseye, so I didn't bother investigating that route.
> pkg-rust-maintainers@ in Cc in case they have any comments.
> 
> Debdiff from 0.14 in [1] due to the size. I haven't uploaded it yet,
> please let me know if the plan to not build and decruft librust-
> cbindgen-dev is good and I'll proceed with the upload.

Under the circumstances it seems like a reasonable plan. Please go
ahead.

Regards,

Adam

Bug#970434: mira: FTBFS with current docbook

[Sven Mueller]

Package: mira
Version: 4.9.6-4

Making all in docbook
make[3]: Entering directory '/<>/doc/docbook'
Making versionfile
Making .html out of _part.xml chap_bitsandpieces_part.html
Making .html out of _part.xml chap_mirautils_part.html
Making .html out of _part.xml chap_est_part.html
Making .html out of _part.xml chap_faq_part.html
Making .html out of _part.xml chap_hard_part.html
Making .html out of _part.xml chap_logfiles_part.html
Making .html out of _part.xml chap_maf_part.html
versionfile:3: Making .html out of _part.xml chap_reference_part.html
parser error : Start tag expected, '<' not found

^
chap_bitsandpieces_part.xml:5: element include: XInclude error : could not
load versionfile, and no fallback was found
versionfile:3: parser error : Start tag expected, '<' not found

^
chap_est_part.xml:5: element include: XInclude error : could not load
versionfile, and no fallback was found
make[3]: *** [Makefile:484: chap_est_part.html] Error 6
make[3]: *** Waiting for unfinished jobs
make[3]: *** [Makefile:484: chap_bitsandpieces_part.html] Error 6
make[3]: Leaving directory '/<>/doc/docbook'
make[2]: *** [Makefile:381: all-recursive] Error 1
make[2]: Leaving directory '/<>/doc'

Bug#970433: ITP: kuserfeedback -- Framework for collecting user feedback for applications via telemetry and surveys.

[Sandro Knauß]

Package: wnpp
Severity: wishlist
Owner: Sandro Knauß 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-qt-...@lists.debian.org

* Package name: kuserfeedback
  Version : 1.0.0
  Upstream Author : Volker Krause 
* URL : https://invent.kde.org/libraries/kuserfeedback
* License : MIT
  Programming Lang: C++, QML
  Description : Framework for collecting user feedback for applications via 
telemetry and surveys.

 Telemetry
  * Extensible set of data sources for telemetry.
  * Full control for the user on what data to contribute.
 Surveys
  * Distribute surveys and offer users to participate in them.
  * Survey targeting based on telemetry data.
  * Allow the user to configure how often they want to participate in surveys.
 .
 This package contains the management and analytics applications.

KDE is usring this Framework to get statistics form users. It is planned to
mantain it under the QT/KDE Maintainers team.

hefee

Bug#958754: gtg: GTG shows an error when I click on Edit - Preferences

[Antonio Ospite]

On Fri, 24 Apr 2020 20:10:07 -0300
Leandro Ramos  wrote:

[...]
>   File "/usr/share/gtg/GTG/tools/shortcut.py", line 50, in get_saved_binding
> list_keys = call_subprocess().splitlines()

Hi Leandro,

I am not the maintainer but maybe I can help.

This error indicates that the CHECK_VERSION command failed and looking
at the code we can see that:

CHECK_VERSION = "gsettings list-keys " \
"org.gnome.settings-daemon.plugins.media-keys"

So maybe you are missing the 'gsettings' binary.

$ dpkg -S /usr/bin/gsettings
libglib2.0-bin: /usr/bin/gsettings

Try installing the libglib2.0-bin package.

Probably the package should have depended on it, but with a new
upstream version available I don't know if that's worth fixing.

Ciao,
   Antonio

-- 
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?

Bug#970431: wxwidgets3.0: Links in documentation points to build path, not installed path

[Chris Lamb]

Package: wxwidgets3.0
Version: 3.0.5.1+dfsg-2
Severity: normal
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

It looks like a number of internal references in the documentation point
to their build-time location. For example:

For more information on socket events see wxSocketFlags
 . 

This is incorrect because it links to under /build/1st, or whatever
directory the package was built from. As this directory will not exist
when the package is installed, the links cannot resolve.

(The exact path in the Debian archive will differ from the above, but
the same problem will be there.)

This was found during reproducibility testing.


Regards,

--
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#970432: RM: python-py2bit [s390x hppa powerpc ppc64 sparc64] -- ROM; some architectures are not supported

[Andreas Tille]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: 969...@bugs.debian.org

Hi ftpmasters,

a new upload excluded those architectures that are failing the build
time test of this package.  Please remove these architectures to enable
testing migration.

Kind regards

 Andreas.

Bug#717300: mdadm: probably use --freeze-reshape in initramfs and startup scripts

[Felix Lechner]

Hi Christoph,

> can we add this to the initramfs scripts and the
> init.d scripts?

Your suggestion sounds like a good idea, although many people now use
systemd. Also, I can only find two relevant calls to --assemble. Both
are located in the same initramfs hook [1]. Are there more?

Kind regards
Felix Lechner

[1] 
https://sources.debian.org/src/mdadm/4.1-6/debian/initramfs/script.local-block/

Bug#970430: libpython-stdlib: unresolvable dependency libpython2-stdlib (= 2.7.17-2), actual libpython2-stdlib (2.7.18-2)

[Egor Sokolenko]

Package: libpython-stdlib
Version: 2.7.17-2
Severity: normal
Tags: a11y
X-Debbugs-Cc: e.sokole...@gmail.com



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

Kernel: Linux 5.8.0-9.3-liquorix-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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

libpython-stdlib cannot be installed on bullseye/sid because it depends on  
libpython2-stdlib (= 2.7.17-2), but current is libpython2-stdlib (2.7.18-2)

Bug#858344: mdadm: Please allow suppressing initramfs warning about active arrays that are not listed in mdadm.conf

[Felix Lechner]

Hi Benjamin,

> We have a setup, where we need exactly one mdadm array for booting, but
> assemble more arrays dynamically while running.

How often do you assemble "dynamic" arrays, and why? I have never
heard of such a use case. Can you capture the output from
'update-initramfs -u' and apply 'grep -v'?

I believe that the warning is appropriate for the vast majority of
users, including myself.

Kind regards
Felix Lechner

Bug#970429: claws-mail-smime-plugin: Error loading claws-mail-smime-plugin on debian/bullseye

[Martin L]

Package: claws-mail-smime-plugin
Version: 3.17.6-1
Severity: normal
X-Debbugs-Cc: de...@public-files.de

Hi,

Upon loading the claws-mail-smime-plugin, the following error occurs,
hence the plugin is not loadable.

The following error occurred while loading smime.so:
/usr/lib/x86_64-linux-gnu/claws-mail/plugins/smime.so: undefined symbol: 
prefs_gpg_auto_check_signatures

A workaround is to load pgpmime (also loads pgpcore) which seem to
include the missing symbol. Loading smime afterwards works.


Best wishes,
Martin


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

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

Versions of packages claws-mail-smime-plugin depends on:
ii  claws-mail   3.17.6-1
ii  claws-mail-pgpmime [claws-mail-pgpcore]  3.17.6-1
ii  gpgsm2.2.20-1
ii  libc62.31-3
ii  libglib2.0-0 2.66.0-1
ii  libgpg-error01.38-2
ii  libgpgme11   1.14.0-1

claws-mail-smime-plugin recommends no packages.

claws-mail-smime-plugin suggests no packages.

-- no debconf information

Bug#970428: ITP: golang-gopkg-cheggaaa-pb.v3 -- Console progress bar for Golang

[Andreas Henriksson]

Package: wnpp
Severity: wishlist
Owner: Andreas Henriksson 

* Package name: golang-gopkg-cheggaaa-pb.v3
  Version : 1.0.29-1
  Upstream Author : Sergey Cherepanov
* URL : https://github.com/cheggaaa/pb
* License : BSD-3-clause
  Programming Lang: Go
  Description : Console progress bar for Golang

 Terminal progress bar for Go. The v1 and v2 is already packaged
 in debian, but now projects are starting to port to v3 so it's
 needed as a dependency for other things I'm thus considering
 packaging it. If someone else wants to take it over, please
 go for it!

Bug#970427: buster-pu: package rust-cbindgen/0.14.4-1~deb10u1

[Emilio Pozuelo Monfort]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

Hi,

This updates rust-cbindgen to 0.14. In order to do that we have to embed the
build-deps, like we did for 0.8.7 in stretch.

I have disabled the -dev packages. buster only has librust-cbindgen-dev, which
has no (build-)rdeps, so we could decruft the old version with this update.
The alternative would be to keep building it, but I'm not sure how that would
work given the deps are not available in buster. We'd probably need to ship
the vendored deps in the -dev, possibly causing upgrade issues due to file
overwrites when installing the standalone packages from bullseye, so I didn't
bother investigating that route. pkg-rust-maintainers@ in Cc in case they have
any comments.

Debdiff from 0.14 in [1] due to the size. I haven't uploaded it yet, please
let me know if the plan to not build and decruft librust-cbindgen-dev is good
and I'll proceed with the upload.

Cheers,
Emilio

[1] https://people.debian.org/~pochu/rust-cbindgen.debdiff.xz

Bug#970426: gtg: New upstream version 4.0 available

[Antonio Ospite]

Package: gtg
Version: 0.3.1-4
Severity: wishlist

Dear Maintainer,

a new upstream version of gtg is available, here is the NEWS file:
https://github.com/getting-things-gnome/gtg/blob/v0.4/NEWS

This version has been ported to pyhton3 and GTK3 and it would be good to
have it in Debian Unstable.

Thanks for your time.

Ciao,
   Antonio

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

Kernel: Linux 5.7.0-3-amd64 (SMP w/2 CPU threads)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 gtg depends on:
ii  python2.7.17-2
ii  python-configobj  5.0.6-3
ii  python-dbus   1.2.16-2
ii  python-glade2 2.24.0-6
ii  python-gtk2   2.24.0-6
ii  python-liblarch   2.1.0-4
ii  python-notify 0.1.1-4+b2
ii  python-xdg0.26-1

Versions of packages gtg recommends:
pn  python-simplejson  
ii  yelp   3.38.0-1

Versions of packages gtg suggests:
pn  bugz 
pn  python-appindicator  
ii  python-cairo 1.16.2-3
pn  python-cheetah   
pn  python-dateutil  
pn  python-evolution 
pn  python-geoclue   
pn  python-gnomekeyring  
pn  python-launchpadlib  
pn  python-suds  

-- no debconf information
-- 
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?

Bug#964038: ping

[Thomas Goirand]

ping

Bug#964636: ping

[Thomas Goirand]

ping

Bug#970268: mksh: autopkgtests fail on s390x because /usr/lib/klibc/bin/mksh is not +x

[Michael Hudson-Doyle]

Hi, thanks for the quick fix, unfortunately the tests now fail because
there is output on stderr:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/s390x/m/mksh/20200915_225445_fb4b8@/log.gz

Bug#970425: ITP: what-is-python - packages providing unversioned python symlinks

[Matthias Klose]

Package: wnpp
Severity: wishlist

These are packages providing unversioned python symlinks, intended for users to
use the python command in Debian.  The packages are discussed in

  https://lists.debian.org/debian-python/2020/07/msg00042.html

The python package is now removed in testing, so we can continue with that.

Bug#970424: buster-pu: package llvm-toolchain-7/1:7.0.1-8+deb10u1

[Emilio Pozuelo Monfort]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

Hi,

This should fix the rustc's i386 and mips* builds. I tested the i386 part,
for mips* will have to see how it goes (and request assistance from the
porters if it's not enough).

Debdiff attached, and package uploaded.

Thanks,
Emilio
diff -Nru llvm-toolchain-7-7.0.1/debian/changelog 
llvm-toolchain-7-7.0.1/debian/changelog
--- llvm-toolchain-7-7.0.1/debian/changelog 2019-02-28 13:50:21.0 
+0100
+++ llvm-toolchain-7-7.0.1/debian/changelog 2020-09-15 13:36:29.0 
+0200
@@ -1,3 +1,11 @@
+llvm-toolchain-7 (1:7.0.1-8+deb10u1) buster; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix for unordered cmpxchg instructions when building rustc.
+  * Disable nomadd4 instructions on mips*.
+
+ -- Emilio Pozuelo Monfort   Tue, 15 Sep 2020 13:36:29 +0200
+
 llvm-toolchain-7 (1:7.0.1-8) unstable; urgency=medium
 
   * Fix a segfault in autopkgtest by brining
diff -Nru 
llvm-toolchain-7-7.0.1/debian/patches/AtomicExpand-Fix-a-crash-bug-when-lowering-unordered-loads.patch
 
llvm-toolchain-7-7.0.1/debian/patches/AtomicExpand-Fix-a-crash-bug-when-lowering-unordered-loads.patch
--- 
llvm-toolchain-7-7.0.1/debian/patches/AtomicExpand-Fix-a-crash-bug-when-lowering-unordered-loads.patch
  1970-01-01 01:00:00.0 +0100
+++ 
llvm-toolchain-7-7.0.1/debian/patches/AtomicExpand-Fix-a-crash-bug-when-lowering-unordered-loads.patch
  2020-09-15 13:33:01.0 +0200
@@ -0,0 +1,28 @@
+From 2153c4b8281c1e5f25887ef9183947198c50a9d2 Mon Sep 17 00:00:00 2001
+From: Philip Reames 
+Date: Tue, 19 Mar 2019 17:20:49 +
+Subject: [PATCH] [AtomicExpand] Fix a crash bug when lowering unordered loads
+ to cmpxchg
+
+Add tests for wider atomic loads and stores.  In the process, fix a crasher 
where we appearently handled unorder stores, but not loads, when lowering to 
cmpxchg idioms.
+
+llvm-svn: 356482
+---
+ llvm/lib/CodeGen/AtomicExpandPass.cpp |   3 +
+ llvm/test/CodeGen/X86/atomic-unordered.ll | 234 +++---
+ 2 files changed, 213 insertions(+), 24 deletions(-)
+
+diff --git a/lib/CodeGen/AtomicExpandPass.cpp 
b/lib/CodeGen/AtomicExpandPass.cpp
+index 10dd21d1ef9d..7a8013abccfb 100644
+--- a/lib/CodeGen/AtomicExpandPass.cpp
 b/lib/CodeGen/AtomicExpandPass.cpp
+@@ -430,6 +430,9 @@ bool AtomicExpand::expandAtomicLoadToLL(LoadInst *LI) {
+ bool AtomicExpand::expandAtomicLoadToCmpXchg(LoadInst *LI) {
+   IRBuilder<> Builder(LI);
+   AtomicOrdering Order = LI->getOrdering();
++  if (Order == AtomicOrdering::Unordered)
++Order = AtomicOrdering::Monotonic;
++
+   Value *Addr = LI->getPointerOperand();
+   Type *Ty = cast(Addr->getType())->getElementType();
+   Constant *DummyVal = Constant::getNullValue(Ty);
diff -Nru llvm-toolchain-7-7.0.1/debian/patches/mips-force-nomadd4.diff 
llvm-toolchain-7-7.0.1/debian/patches/mips-force-nomadd4.diff
--- llvm-toolchain-7-7.0.1/debian/patches/mips-force-nomadd4.diff   
1970-01-01 01:00:00.0 +0100
+++ llvm-toolchain-7-7.0.1/debian/patches/mips-force-nomadd4.diff   
2020-09-15 13:34:42.0 +0200
@@ -0,0 +1,18 @@
+The MIPS port aims to support the Loongson 3 family of CPUs in addition
+of the other MIPS CPUs. On the Loongson 3 family the MADD4 instructions
+are fused, while they are not fused on the other MIPS CPUs. In order to
+support both, we have to disabled those instructions.
+
+For that, the patch below basically corresponds to the --with-madd4=no
+used on the GCC side.
+
+--- a/clang/lib/Basic/Targets/Mips.h
 b/clang/lib/Basic/Targets/Mips.h
+@@ -306,6 +306,7 @@ public:
+ FloatABI = HardFloat;
+ DspRev = NoDSP;
+ HasFP64 = isFP64Default();
++DisableMadd4 = true;
+ 
+ for (const auto  : Features) {
+   if (Feature == "+single-float")
diff -Nru llvm-toolchain-7-7.0.1/debian/patches/series 
llvm-toolchain-7-7.0.1/debian/patches/series
--- llvm-toolchain-7-7.0.1/debian/patches/series2019-02-28 
13:49:26.0 +0100
+++ llvm-toolchain-7-7.0.1/debian/patches/series2020-09-15 
13:31:10.0 +0200
@@ -161,3 +161,5 @@
 kfreebsd/lldb_source_Plugins_Process_FreeBSD.diff
 kfreebsd/tools_llvm-shlib_CMakeLists.txt.diff
 kfreebsd/include_llvm_MC_MCELFObjectWriter.h.diff
+AtomicExpand-Fix-a-crash-bug-when-lowering-unordered-loads.patch
+mips-force-nomadd4.diff

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

[Matthias Klose]

Control: severity -1 important
Control: merge -1 970375

On 9/16/20 3:45 AM, Koutheir Attouchi wrote:
> Package: python
> Version: 2.7.17-2
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: kouth...@gmail.com
> 
> Dear Maintainer,
> 
> What led up to the situation?
> 
> ```
> $ sudo apt-get install python
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  python : PreDepends: python-minimal (= 2.7.17-2) but it is not going to be
> installed
>   Depends: libpython-stdlib (= 2.7.17-2) but it is not going to be
> installed
>   Depends: python2 (= 2.7.17-2) but 2.7.18-2 is to be installed
> E: Unable to correct problems, you have held broken packages.
> ```
> 
> In order to keep other python packages, I marked the `python2` and `python3`
> packages as manually installed.


no, the python package is gone.

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

[SZALAY Attila]

Hi Jean-Marc,

Please check if a core file is available related to the segmentation
fault. If there is any please make it available for me/us.

Also, can you run syslog-ng-debun with the -r parameter and send the
generated report bundle?

Another question, is the segmentation fault reproducible? Is syslog-ng
crashing frequently?


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

Bug#917643: bug fix ready

[Sebastian Spaeth]

I took the liberty to fix this code in jcc's salsa repository and file a
merge request.

https://salsa.debian.org/jcc/zram-tools/-/merge_requests/4

The diff *looks* big because it pulls the "packaging" branch over to
"master", but this is really this patch

commit_id=ba29e5f4963c2e7fca088eaa98beed3e70cfe039
2 files + 22 - 23 (including config changes)

Using the "CORES" approach is not needed anymore, a single device can
make use of multiple cores just fine.

I would appreciate if this could go in and a new release pulled into
debian. It really hurts us on the pinephone that we cannot use an
upstream version right now.

Bug#970423: icingaweb2-module-recommends - metapackage for icingaweb2 modules

[David Kunz]

Package: wnpp
Owner: david.k...@dknet.ch

* Package name: icingaweb2-module-recommends recommended packages
  Description : icingaweb2 metapackage for

  Icinga Web 2 is a very modular, fast and simple web interface for
  your Icinga monitoring environment.
  .
  Metapckage to install recommended packages.

Greetings,
David

Bug#970348: RFS: libip2location/8.0.9 [ITP] -- IP2Location geolocation library

[Andrei POPESCU]

Control: reassign -1 sponsorship-requests

On Ma, 15 sep 20, 10:54:58, IP2Location wrote:
> Package: libip2location

Hello,

Sponsorship requests must be assigned to the pseudo-package 
'sponsorship-requests', reassigning now.

> Version: 8.0.9
> Severity: normal
> 
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "libip2location":
> 
> * Package name : libip2location
>   Version : 8.0.9
>   Upstream Author : IP2Location (supp...@ip2location.com)
> * URL : https://www.ip2location.com
> * License : MIT
> * Vcs : https://github.com/chrislim2888/IP2Location-C-Library
> 
> It builds those binary packages:
> 
> libip2location
> 
> To access further information about this package, please visit the following 
> URL:
> 
> https://mentors.debian.net/package/libip2location/
> 
> 
> 
> Regards,
> --
> IP2Location

Kind regards,
Andrei
-- 
Looking after bugs assigned to unknown packages


signature.asc
Description: PGP signature

Bug#598913: FW

[Micheal Lawson]

[image: image.png]

Bug#969223: Can't rm directory on overlayfs in userns

[Nicolas Schier]

On Wed, Sep 02, 2020 at 11:52:41AM +0800, Shengjing Zhu wrote:
> On Sat, Aug 29, 2020 at 10:13 PM Shengjing Zhu  wrote:
> >
> > Source: linux
> > Version: 5.7.10-1
> > Severity: normal
> >
> > Hi,
> >
> > After enabling overlayfs for userns, I find it doesn't work as expected.
> >
> > $ cat /sys/module/overlay/parameters/permit_mounts_in_userns
> > Y
> >
> > zsj@debian:~/test$ pwd
> > /home/zsj/test
> > zsj@debian:~/test$ tree
> > .
> > ├── lower
> > │   └── a
> > │   └── a
> > ├── merged
> > ├── upper
> > └── work
> >
> > zsj@debian:~/test$ unshare -m -U -r
> > root@debian:~/test# mount -t overlay -o 
> > rw,lowerdir=/home/zsj/test/lower,upperdir=/home/zsj/test/upper,workdir=/home/zsj/test/work
> >  overlay /home/zsj/test/merged
> > root@debian:~/test# rm -rf merged/a
> > rm: cannot remove 'merged/a': Input/output error
> >

Hi,

overlayfs uses filesystem xattrs to mark "whiteouts" and redirects of
directories, which are only accessable for root (CAP_SYS_ADMIN), thus,
not when overlay is mounted in a user namespace, cp. e.g. [1,2].

Ubuntu kernel "solves" this by skipping the "trusted."-xattr check, thus
allowing setting and removal of 'trusted.overlay.*' xattrs from within
user namespaces; but those are still visible in all other namespaces.  A
following overlayfs mount done by the real root user will use these
modified xattrs.

To me it would seem to be more adequate if overlayfs would use
'overlay.*' instead of 'trusted.overlay.*', if it is mounted in an
unpriviledged user namespace.  But this would make overlay mounts done
by root incompatible with those done in a user namespace.

Maybe you find #836211 to be related to this.


[1]: 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/fs/xattr.c?h=linux-5.7.y#n113
[2]: 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/fs/xattr.c?h=linux-5.7.y#n1049
[3]: 
https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=111cd1a9840ce187e28b49fe4e77b9b5e84386b1

> If I upgrade a debian10 VM to testing, it seems to work.
> However if I boot a new debian testing VM, it seems not to work.
> Both VMs are downloaded from http://cdimage.debian.org/cdimage/cloud/
> What can be the difference here? I'm lost on debugging this..

This confuses me.  Are you sure, you used the same kernel version on
both VMs when mounting overlayfs in userns?

Kind regards,
Nicolas

-- 
epost: nico...@fjasle.eu   irc://oftc.net/nsc
↳ gpg: 18ed 52db e34f 860e e9fb  c82b 7d97 0932 55a0 ce7f
 -- frykten for herren er opphav til kunnskap --

Bug#963341: fixed 873699 in 3.15.2-3, fixed 963341 in 3.15.2-3

[Gian Piero Carrubba]

fixed 873699 3.15.2-3
fixed 963341 3.15.2-3
thanks

Sorry, it seems I've messed up the changelog entries for 3.15.2-3.
This must now be closed manually.

Bug#909436: libdrm 2.4.102-1: FTBFS on hurd-i386 (updated patches)

[Svante Signell]

On Tue, 2020-09-15 at 23:49 +0300, Timo Aaltonen wrote:
> On 15.9.2020 19.50, Svante Signell wrote:
> > 
> > Both patches (somewhat modified) submitted upstream to the old
> > issues:
> > https://gitlab.freedesktop.org/mesa/drm/-/issues/23
> > https://gitlab.freedesktop.org/mesa/drm/-/issues/24
> 
> thanks, but I'm afraid they don't get noticed unless they're sent as
> merge-requests..

I don't know how to create a merge request. Maybe you can do that?
Alternately, what hinders you from applying the patches in Debian until
upstream responds?

Thanks!

Bug#968603: memcached should enable TLS by default

[Tomas Korbar]

Thanks for cooperation Chriss. I hope that there will be no
further complications.


On Tue, Sep 15, 2020 at 3:28 PM Chris Lamb  wrote:

> Hi Tomas,
>
> > I believe it is a race condition because most issues with this suite are.
> > I created vm with 4 virtual cpus and unstable debian to simulate your
> > environment but again the suite did not hang. Can you please change
> > the "-j" options value passed to make to 1?
>
> I just tried this and the testsuite has now passed four times in a row.
> Thanks for the tip, I think you got it.
>
> Uploading this change to Debian now in order to see how it works on
> the official build machines, although I will limit the parallelization
> to 1 CPU only when running the tests; no need to do this in the
> build/configure stages, after all.
>
>
>
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org  chris-lamb.co.uk
>`-
>
>

Bug#970258: Same on sid

[Malte Eggers]

I'm (unsurprisingly) experiencing the same problem on sid. This appears to be 
the relevant section of the make.log

  CC [M]  
/var/lib/dkms/openafs/1.8.6/build/src/libafs/MODLOAD-5.8.0-1-amd64-SP/rx_kmutex.o
In file included from 
/var/lib/dkms/openafs/1.8.6/build/src/libafs/MODLOAD-5.8.0-1-amd64-SP/rx_kmutex.c:24:
/var/lib/dkms/openafs/1.8.6/build/src/afs/LINUX/osi_compat.h: In function 
‘kernel_setsockopt’:
/var/lib/dkms/openafs/1.8.6/build/src/afs/LINUX/osi_compat.h:326:12: error: 
implicit declaration of function ‘get_ds’; did you mean ‘get_fs’? 
[-Werror=implicit-function-declaration]
  326 | set_fs(get_ds());
  |^~
  |get_fs
/var/lib/dkms/openafs/1.8.6/build/src/afs/LINUX/osi_compat.h:326:12: error: 
incompatible type for argument 1 of ‘set_fs’
  326 | set_fs(get_ds());
  |^~~~
  ||
  |int
In file included from 
/usr/src/linux-headers-5.8.0-1-common/include/linux/uaccess.h:11,
 from 
/usr/src/linux-headers-5.8.0-1-common/include/linux/crypto.h:21,
 from 
/usr/src/linux-headers-5.8.0-1-common/include/crypto/hash.h:11,
 from 
/usr/src/linux-headers-5.8.0-1-common/include/linux/uio.h:10,
 from 
/usr/src/linux-headers-5.8.0-1-common/include/linux/socket.h:8,
 from 
/var/lib/dkms/openafs/1.8.6/build/src/libafs/MODLOAD-5.8.0-1-amd64-SP/./h/socket.h:1,
 from /var/lib/dkms/openafs/1.8.6/build/src/rx/rx_kcommon.h:51,
 from 
/var/lib/dkms/openafs/1.8.6/build/src/libafs/MODLOAD-5.8.0-1-amd64-SP/rx_kmutex.c:20:
/usr/src/linux-headers-5.8.0-1-common/arch/x86/include/asm/uaccess.h:29:40: 
note: expected ‘mm_segment_t’ but argument is of type ‘int’
   29 | static inline void set_fs(mm_segment_t fs)
  |   ~^~
In file included from 
/var/lib/dkms/openafs/1.8.6/build/src/libafs/MODLOAD-5.8.0-1-amd64-SP/rx_kmutex.c:24:
/var/lib/dkms/openafs/1.8.6/build/src/afs/LINUX/osi_compat.h: In function 
‘kernel_getsockopt’:
/var/lib/dkms/openafs/1.8.6/build/src/afs/LINUX/osi_compat.h:339:12: error: 
incompatible type for argument 1 of ‘set_fs’
  339 | set_fs(get_ds());
  |^~~~
  ||
  |int
In file included from 
/usr/src/linux-headers-5.8.0-1-common/include/linux/uaccess.h:11,
 from 
/usr/src/linux-headers-5.8.0-1-common/include/linux/crypto.h:21,
 from 
/usr/src/linux-headers-5.8.0-1-common/include/crypto/hash.h:11,
 from 
/usr/src/linux-headers-5.8.0-1-common/include/linux/uio.h:10,
 from 
/usr/src/linux-headers-5.8.0-1-common/include/linux/socket.h:8,
 from 
/var/lib/dkms/openafs/1.8.6/build/src/libafs/MODLOAD-5.8.0-1-amd64-SP/./h/socket.h:1,
 from /var/lib/dkms/openafs/1.8.6/build/src/rx/rx_kcommon.h:51,
 from 
/var/lib/dkms/openafs/1.8.6/build/src/libafs/MODLOAD-5.8.0-1-amd64-SP/rx_kmutex.c:20:
/usr/src/linux-headers-5.8.0-1-common/arch/x86/include/asm/uaccess.h:29:40: 
note: expected ‘mm_segment_t’ but argument is of type ‘int’
   29 | static inline void set_fs(mm_segment_t fs)
  |   ~^~
cc1: some warnings being treated as errors
make[5]: *** [/usr/src/linux-headers-5.8.0-1-common/scripts/Makefile.build:286: 
/var/lib/dkms/openafs/1.8.6/build/src/libafs/MODLOAD-5.8.0-1-amd64-SP/rx_kmutex.o]
 Error 1
make[4]: *** [/usr/src/linux-headers-5.8.0-1-common/Makefile:1768: 
/var/lib/dkms/openafs/1.8.6/build/src/libafs/MODLOAD-5.8.0-1-amd64-SP] Error 2
make[3]: *** [/usr/src/linux-headers-5.8.0-1-common/Makefile:185: __sub-make] 
Error 2
make[3]: Leaving directory '/usr/src/linux-headers-5.8.0-1-amd64'
FAILURE: make exit code 2
make[2]: *** [Makefile.afs:279: openafs.ko] Error 1
make[2]: Leaving directory 
'/var/lib/dkms/openafs/1.8.6/build/src/libafs/MODLOAD-5.8.0-1-amd64-SP'
make[1]: *** [Makefile:186: linux_compdirs] Error 2
make[1]: Leaving directory '/var/lib/dkms/openafs/1.8.6/build/src/libafs'
make: *** [Makefile:15: all] Error 2

Bug#970384: ITP: image-factory -- Image factory for the IONOS customers images

[Benjamin Drung]

Am Dienstag, den 15.09.2020, 12:51 -0400 schrieb Sandro Tosi:
> > * Package name: image-factory
> >   Version : 1.0.0
> >   Upstream Author : Benjamin Drung 
> > * URL : 
> > https://github.com/ionos-enterprise/image-factory
> > * License : ISC
> >   Programming Lang: Python
> >   Description : Image factory for the IONOS customers images
> 
> isnt `image-factory` a way too generic name for something that seems
> IONOS specific? or does the short description not need to mention
> IONOS if it's actually a tool to "build golden Linux images" (But
> actually use that in the short descr)?

This tool is not IONOS specific. The only "specific" part is that the
package ships the preseed/kickstarter files used by IONOS so that you c
an rebuild the package yourself.

So I will change the short description.

-- 
Benjamin Drung

DevOps Engineer and Debian & Ubuntu Developer
Platform Integration (IONOS Cloud)

1&1 IONOS SE | Greifswalder Str. 207 | 10405 Berlin | Germany
E-mail: benjamin.dr...@cloud.ionos.com | Web: www.ionos.de

Hauptsitz Montabaur, Amtsgericht Montabaur, HRB 24498

Vorstand: Dr. Christian Böing, Hüseyin Dogan, Dr. Martin Endreß, Hans-
Henning Kettler, Arthur Mai, Matthias Steinberg, Achim Weiß
Aufsichtsratsvorsitzender: Markus Kadelke


Member of United Internet

Diese E-Mail kann vertrauliche und/oder gesetzlich geschützte
Informationen enthalten. Wenn Sie nicht der bestimmungsgemäße Adressat
sind oder diese E-Mail irrtümlich erhalten haben, unterrichten Sie
bitte den Absender und vernichten Sie diese E-Mail. Anderen als dem
bestimmungsgemäßen Adressaten ist untersagt, diese E-Mail zu speichern,
weiterzuleiten oder ihren Inhalt auf welche Weise auch immer zu
verwenden.

This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient of this e-mail, you are hereby
notified that saving, distribution or use of the content of this e-mail 
in any way is prohibited. If you have received this e-mail in error,
please notify the sender and delete the e-mail.

Bug#214257: TO-YOU !!!

[Jacqueline van der Schoor]

From: Jacqueline van der Schoor
Sent: Tuesday, September 15, 2020 10:42 PM
To: Jacqueline van der Schoor 
Subject: TO-YOU !!!


The waiting period is over. you are the Recipîent of a donatîon. for better 
understanding, contact email ( wmavis...@gmail.com )

This is the second time I have been contacting you on this.

Sincerely,

























































































"De informatie in deze mail is uitsluitend bestemd voor de geadresseerde en 
bevat mogelijk vertrouwelijke informatie. Het is voor een ander dan de 
geadresseerde niet toegestaan de informatie openbaar te maken, te kopiëren, te 
verspreiden of anderszins te gebruiken. Indien deze mail u bij vergissing 
bereikt, stel dan de afzender hiervan op de hoogte en verwijder de mail van uw 
systeem. De inhoud van de e-mail kan onjuist of onvolledig zijn. Aan de inhoud 
van de e-mail kunnen geen rechten ontleend worden. The information in this 
e-mail is meant for the exclusive use of the addressee and may contain 
confidential information. No part of this information may be made public, 
copied, spread, or used in other way, by anyone apart from the addressee. If 
this mail should reach you by accident, inform the sender and remove the mail 
from your system. The contents of the e-mail may be wrong or incomplete. No 
rights can be derived from the contents of the e-mail."

Bug#970422: ansible: broken-symlink /usr/bin/ansible-connection -> ../lib/ansible/cli/scripts/ansible_connection_cli_stub.py

[Paul Wise]

Package: ansible
Version: 2.9.13+dfsg-1
Severity: normal
File: /usr/bin/ansible-connection
User: debian...@lists.debian.org
Usertags: adequate broken-symlink

The recent upgrade introduced a broken ansible-connection symlink.
Looking at the debian/ dir it seems that ansible-connection should move
from debian/ansible.install to debian/ansible.links.

Also I recommend leaving the installation of /usr/bin/ansible-* to the
upstream build system instead of using dh_install to hack around it.

This bug report brought to you by adequate:

https://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/

   $ adequate ansible
   ansible: broken-symlink /usr/bin/ansible-connection -> 
../lib/ansible/cli/scripts/ansible_connection_cli_stub.py

   $ ls -l /usr/bin/ansible-connection
   lrwxrwxrwx 1 root root 57 Sep 11 13:32 /usr/bin/ansible-connection -> 
../lib/ansible/cli/scripts/ansible_connection_cli_stub.py

   $ chase /usr/bin/ansible-connection
   chase: ../lib/ansible/cli/scripts: No such file or directory

   $ dpkg -L ansible | grep ansible_connection_cli_stub.py
   
/usr/lib/python3/dist-packages/ansible/cli/scripts/ansible_connection_cli_stub.py

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages ansible depends on:
ii  openssh-client1:8.3p1-1
ii  python3   3.8.2-3
ii  python3-crypto2.6.1-13.1+b1
ii  python3-cryptography  3.0-1
ii  python3-distutils 3.8.5-1
ii  python3-dnspython 2.0.0-1
ii  python3-httplib2  0.18.1-1
ii  python3-jinja22.11.2-1
ii  python3-netaddr   0.7.19-4
ii  python3-paramiko  2.7.2-1
ii  python3-yaml  5.3.1-2

Versions of packages ansible recommends:
ii  python3-argcomplete  1.8.1-1.3
ii  python3-jmespath 0.10.0-1
ii  python3-kerberos 1.1.14-3.1+b1
pn  python3-libcloud 
pn  python3-selinux  
pn  python3-winrm
pn  python3-xmltodict

Versions of packages ansible suggests:
ii  cowsay   3.03+dfsg2-8
pn  sshpass  

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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