Bug#977864: [Pkg-javascript-devel] Bug#977864: libjs-bootstrap4: Missing maintscript blocks upgrade

[Petter Reinholdtsen]

Control: reopen -1
Control: found -1 4.5.2+dfsg1-3

It look like the fix was incomplete.  I see this in my unstable chroot
when trying to upgrade:

Preparing to unpack .../libjs-bootstrap4_4.5.2+dfsg1-3_all.deb ...
Unpacking libjs-bootstrap4 (4.5.2+dfsg1-3) over (4.5.2+dfsg1-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libjs-bootstrap4_4.5.2+dfsg1-3_all.deb (--unpack):
 unable to open 
'/usr/share/nodejs/bootstrap/dist/css/bootstrap-grid.css.dpkg-new': No such 
file or directory
Errors were encountered while processing:
 /var/cache/apt/archives/libjs-bootstrap4_4.5.2+dfsg1-3_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- 
Happy hacking
Petter Reinholdtsen

Bug#977781: [Pkg-javascript-devel] Bug#977781: Bug#977781: real issue is, it does not pull not-yet-cached modules

[Akshay S Dinesh]

   gbp:error: upstream/1.22.10+_cs18.39.16 is not a valid treeish

indeed your fork only has 33 tags, whereas js-team/node-yarnpkg has 37.
Please pull those tags and push them to your fork, then force restart the CI 
pipeline.
This would help us to see if your proposed fix works.


Pushing tags indeed helped extract sources. But build fails due to 
incompatibilities with upstream files




As to upgrading tar-fs, it is possible that some other dependency we updated 
here and there requires it.
Upstream are currently using 1.16.3:
https://github.com/yarnpkg/yarn/blob/master/yarn.lock#L7137
whereas we were already using version 2

If we want to upgrade tar-fs we need to upgrade its sources and then import 
them in upstream and master branches:
https://wiki.debian.org/Javascript/GroupSourcesTutorial



I think Praveen locked the dependency on tar-fs to version 1.x in 
https://salsa.debian.org/js-team/node-yarnpkg/-/commit/8f44f7d238f4330b89d3b62c2cc369bb909459a6


I'm unsure if that's because upstream yarn mentions 1.x tar-fs as 
dependency or because there are other dependencies to 1.x tar-fs.


The API of tar-fs doesn't change between 1.x and 2.x, but the 
dependencies do. And the dependencies we have in debian make it such 
that 1.x doesn't work.


I tried following GroupSourcesTutorial and gbp manual. It is becoming 
very confusing for me with many version numbers and tags floating 
around. So I'll have to leave this here for possibly Praveen to pick up.


Akshay

Bug#977868: osmcoastline: FTBFS in bullseye and sid

[Sebastiaan Couwenberg]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/osmcode/osmcoastline/issues/39

Thanks for reporting this issue, I've forwarded it upstream.

A possible cause may be the upgrade of GEOS to 3.9.0.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#976880: transition: dtkcore

[Arun Kumar Pariyar]

Package: release.debian.org
Followup-For: Bug #976880

On 12/20/20 4:32 PM, Sebastian Ramacher wrote:

Control: tags -1 + confirmed

On 2020-12-12 14:54:15 +0545, Arun Kumar Pariyar wrote:

Package: release.debian.org
Followup-For: Bug #976880

Dear Release Team,

Following packages need to have a sourceful upload:

dtkcore
dtkgui
dtkwidget
dtkwm
dde-qt-dbus-factory
dde-qt5integration
dde-calendar
deepin-deb-installer
deepin-menu
deepin-movie-reborn
deepin-music
deepin-screen-recorder
deepin-voice-recorder
deepin-calculator
deepin-image-viewer

And the following packages need binNMU:

deepin-shortcut-viewer
deepin-picker
deepin-notifications
deepin-screenshot

Please go ahead with the uploads to unstable and let us know once we
should schedule the binNMUs.


Dear Release Team,

Please schedule binNMU for the following packages:

deepin-shortcut-viewer
deepin-picker
deepin-notifications
deepin-screenshot

--
Arun Kumar Pariyar



OpenPGP_signature
Description: OpenPGP digital signature

Bug#977868: osmcoastline: FTBFS in bullseye and sid

[Graham Inggs]

Source: osmcoastline
Version: 2.2.4-2
Severity: serious
Tags: ftbfs bullseye sid

Hi Maintainer

As per Reproducible Builds [1], osmcoastline FTBFS in bullseye and sid.
I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/osmcoastline.html


 1/19 Test  #1: test-invalid-complex-overlap
.***Failed0.29 sec
+ cat
+ /build/1st/osmcoastline-2.2.4/obj-x86_64-linux-gnu/src/osmcoastline
--verbose --overwrite
--output-database=/build/1st/osmcoastline-2.2.4/obj-x86_64-linux-gnu/test/invalid-complex-overlap.db
/build/1st/osmcoastline-2.2.4/obj-x86_64-linux-gnu/test/invalid-complex-overlap.opl
+ RC=139
+ set -e
+ test 139 -eq 2

  Start 17: test-valid-island-from-one-way
 2/19 Test  #6: test-invalid-node-with-coastline-tag
.   Passed0.49 sec
  Start 18: test-valid-island-from-two-ways
 3/19 Test #13: test-usage-and-help
..   Passed0.44 sec
  Start 19: test-valid-two-small-islands
 4/19 Test  #4: test-invalid-duplicate-segments-2
   Passed0.51 sec
 5/19 Test  #7: test-invalid-part-reversed
...   Passed0.50 sec
 6/19 Test  #2: test-invalid-direction
...   Passed0.53 sec
 7/19 Test  #9: test-invalid-self-intersection-on-closed-ring-one-way
   Passed0.53 sec
 8/19 Test #10: test-invalid-self-intersection-on-closed-ring-two-ways
...   Passed0.59 sec
 9/19 Test  #3: test-invalid-duplicate-segments-1
   Passed0.63 sec
10/19 Test  #5: test-invalid-node-id-mismatch
   Passed0.63 sec
11/19 Test #12: test-overlapping-islands
.   Passed0.60 sec
12/19 Test #15: test-valid-inline-sea-with-island
   Passed0.64 sec
13/19 Test #14: test-valid-antimeridian
..   Passed0.70 sec
14/19 Test #16: test-valid-inline-sea
   Passed0.68 sec
15/19 Test #17: test-valid-island-from-one-way
...   Passed0.50 sec
16/19 Test #11: test-invalid-self-intersection-on-open-ring
..   Passed0.77 sec
17/19 Test #18: test-valid-island-from-two-ways
..   Passed0.45 sec
18/19 Test #19: test-valid-two-small-islands
.   Passed0.45 sec
19/19 Test  #8: test-invalid-ring-not-closed
.   Passed1.12 sec

95% tests passed, 1 tests failed out of 19

Total Test time (real) =   1.14 sec

The following tests FAILED:
 1 - test-invalid-complex-overlap (Failed)
Errors while running CTest

Bug#977852: Acknowledgement (redis: Enable systemd support to get Type=notify working again)

[Michael Prokop]

Control: tag -1 pending

The MR is available at:

  https://salsa.debian.org/lamby/pkg-redis/-/merge_requests/6

regards
-mika-


signature.asc
Description: Digital signature

Bug#977867: TAG: libzbd -- library providing functions simplifying access to zoned block device information and the execution of zone management operations

[Rishabh Chawla]

Package: wnpp
Severity:  RFP
Copyright: Western Digital Corporation or its affiliates
Url: https://github.com/westerndigitalcorporation/libzbd
License: GNU Lesser General Public License Version 3

Package Description: libzbd is a library providing functions simplifying
access to zoned block device information and the execution of zone
management operations.

Regards,
Rishabh

Bug#977781: [Pkg-javascript-devel] Bug#977781: Bug#977781: real issue is, it does not pull not-yet-cached modules

[Paolo Greppi]

Hi Akshay, many thanks for the debugging ! see below

Il 22/12/20 06:06, Akshay S Dinesh ha scritto:



There are some 4 pipes before the finish event. I'm looking through each one of 
them to see if there's a mismatch.



It seems to be tar-fs

Please see https://salsa.debian.org/js-team/node-yarnpkg/-/merge_requests/4

I've just downloaded the latest version from the github of tar-fs and replace 
in the directory. Not sure if this is the way to do it.


It's a pity the salsa Continuous Integration has failed on your fork.

I noticed this message in the extract-source job log:

  gbp:error: upstream/1.22.10+_cs18.39.16 is not a valid treeish

indeed your fork only has 33 tags, whereas js-team/node-yarnpkg has 37.
Please pull those tags and push them to your fork, then force restart the CI 
pipeline.
This would help us to see if your proposed fix works.

As to upgrading tar-fs, it is possible that some other dependency we updated 
here and there requires it.
Upstream are currently using 1.16.3:
https://github.com/yarnpkg/yarn/blob/master/yarn.lock#L7137
whereas we were already using version 2

If we want to upgrade tar-fs we need to upgrade its sources and then import 
them in upstream and master branches:
https://wiki.debian.org/Javascript/GroupSourcesTutorial

Paolo

Bug#977864: [Pkg-javascript-devel] Bug#977864: libjs-bootstrap4: Missing maintscript blocks upgrade

[Xavier]

Le 22/12/2020 à 06:30, Jonas Smedegaard a écrit :
> Quoting Xavier Guimard (2020-12-22 06:03:43)
>> Package: libjs-bootstrap4
>> Version: 4.5.2+dfsg1-3
>> Severity: serious
>>
>> Version 4.5.2+dfsg1-2 transform /usr/share/javascript/bootstrap4 from
>> symlink to dir without any maintscript. This break updates.
> 
> Thanks!
> 
> I was pulling hairs out trying to figure out how to solve that one.

Hi,

done for twitter-bootstram4 (and pushed to salsa).

Cheers,
Xavier

Bug#977864: [Pkg-javascript-devel] Bug#977864: libjs-bootstrap4: Missing maintscript blocks upgrade

[Jonas Smedegaard]

Quoting Xavier Guimard (2020-12-22 06:03:43)
> Package: libjs-bootstrap4
> Version: 4.5.2+dfsg1-3
> Severity: serious
> 
> Version 4.5.2+dfsg1-2 transform /usr/share/javascript/bootstrap4 from
> symlink to dir without any maintscript. This break updates.

Thanks!

I was pulling hairs out trying to figure out how to solve that one.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#977864: [Pkg-javascript-devel] Bug#977864: libjs-bootstrap4: Missing maintscript blocks upgrade

[Xavier]

Le 22/12/2020 à 06:03, Xavier Guimard a écrit :
> Package: libjs-bootstrap4
> Version: 4.5.2+dfsg1-3
> Severity: serious
> 
> Version 4.5.2+dfsg1-2 transform /usr/share/javascript/bootstrap4 from
> symlink to dir without any maintscript. This break updates.

I enabled CI for this package and CI reported the problem:
https://salsa.debian.org/js-team/twitter-bootstrap4/-/jobs/1266448.

Bug#977781: [Pkg-javascript-devel] Bug#977781: real issue is, it does not pull not-yet-cached modules

[Akshay S Dinesh]

There are some 4 pipes before the finish event. I'm looking through each 
one of them to see if there's a mismatch.




It seems to be tar-fs

Please see https://salsa.debian.org/js-team/node-yarnpkg/-/merge_requests/4

I've just downloaded the latest version from the github of tar-fs and 
replace in the directory. Not sure if this is the way to do it.

Bug#977864: libjs-bootstrap4: Missing maintscript blocks upgrade

[Xavier Guimard]

Package: libjs-bootstrap4
Version: 4.5.2+dfsg1-3
Severity: serious

Version 4.5.2+dfsg1-2 transform /usr/share/javascript/bootstrap4 from
symlink to dir without any maintscript. This break updates.

Bug#939018: ITA: golang-github-docopt-docopt-go

[Anthony Fok]

Control: retitle -1 ITA: golang-github-docopt-docopt-go -- implementation of 
docopt in the Go programming language
Control: owner -1 Anthony Fok 

Hello Gustavo,

On Sat, Aug 31, 2019 at 3:33 AM gustavo panizzo  wrote:
>
> Package: wnpp
> Severity: normal
>
>
> Hello
>
> I uploaded this package as a dependency of asciinema when it went from
> python to go, shortly after it went back to python.
>
> Since then I haven't work on go packages ever after, therefore I'm
> orphaning this package since I'm not up to date on go packaging practices.

Thank you for creating this package, and for explaining its backstory.

I came across this package a few days ago while trying to diagnose
some new (unrelated) FTBFS, and decided to upload a slightly newer
version and adopt it very soon now.

Cheers,

Anthony

Bug#689528: please add virtio support for cdrom at install time

[Michael Tokarev]

22.01.2020 09:18, Witold Baryluk wrote:

Package: debian-installer
Followup-For: Bug #689528

Dear Maintainer,

any progress on this, I still have this issue.


Out of curiosity, _why_ this is necessary?
For the install time, isn't it trivial to use regular ide/sata cdrom
drive or an usb flash instead of more exotic ways? Most of the time
cdrom is only needed for the installation, later on you can either
remove it entirely or switch it to virtio if needed.

We did lots of installations of various systems out there in qemu/kvm,
and we always use most common devices during this time.

Thanks,

/mjt

Bug#977856: librepository: fails to build source package

[tony mancill]

Hi Holger!

On Tue, Dec 22, 2020 at 12:45:13AM +0100, Holger Levsen wrote:
> Package: librepository
> Version: 1.1.6-3
> Severity: serious
> 
> Dear Maintainer,
> 
> I wanted to do a source only upload of librepository
> (because there are no .buildinfo files for it in the archive,
> as it has been uploaded before 2016), but it fails to build
> the source package. The binary package builds just fine.
> 
> Steps to reproduce:
> 
> $ apt source librepository
> $ cd librepository-*
> $ dpkg-buildpackage
> dpkg-buildpackage: info: source package librepository
> dpkg-buildpackage: info: source version 1.1.6-3
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Emmanuel Bourg 
> dpkg-buildpackage: info: host architecture amd64
>  dpkg-source --before-build .
>  fakeroot debian/rules clean
> dh clean --with javahelper
>dh_auto_clean
> ant -propertyfile ./debian/ant.properties clean
> /usr/bin/java: error while loading shared libraries: libjli.so: cannot open 
> shared object file: No such file or directory
> dh_auto_clean: error: ant -propertyfile ./debian/ant.properties clean 
> returned exit code 127
> make: *** [debian/rules:6: clean] Error 127
> dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
> exit status 2
> $
> 
> (This is with or without any changes to the source package.)

That's interesting.  It builds successfully for me in a clean sid chroot
using sbuild.  libjli.so is part of the JRE, which is a dependency of
default-jdk:

$ dpkg -S libjli.so 
openjdk-11-jre-headless:amd64: 
/usr/lib/jvm/java-11-openjdk-amd64/lib/jli/libjli.so

Do you mind sharing the output of `apt-cache policy default-jdk` and
`dpkg -l | grep openjdk` on your build system?  I'm curious as to how
the build dep for default-jdk can be satisfied without the file being
present.

Thank you,
tony


signature.asc
Description: PGP signature

Bug#977863: please package new upstream release 2.2.26

[John Scott]

Source: gnupg2
Version: 2.2.20-1
Severity: wishlist

This new version supports global configuration files, which IIRC might be
helpful for some Debian-specific changes (gpgsm CA's?), but I particularly
think it's worth getting into Bullseye for the improved LDAP support,
including Active Directory integration, that would suit enterprise usages.

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

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


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

Bug#920616: Agreed, keepassxc should replace keepassx

[Bruno Kleinert]

Hi,

I agree that the maintaining effort for keepassx can be saved for
something else and keepassx be removed from the archive and be replaced
by keepassxc.

The latter has a more features, a modern user interface and more active
upstream. Looking at popcon, keepassx has a decreasing number of
installations for almost 2 years:

keepassx: https://qa.debian.org/popcon.php?package=keepassx
keepassxc: https://qa.debian.org/popcon.php?package=keepassxc

From my point of view, there is no value in keeping keepassx in the
archive.

Cheers,
Bruno


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

Bug#977862: support systems without lchown, perhaps with Gnulib

[John Scott]

Source: dpkg
Severity: wishlist
Tags: upstream

Just to see what trickery I could get away with, I tried cross building dpkg
with MinGW. It fails due to lchown being missing, but it seems like this is
one of the only functions that dpkg dies on not finding:
AC_CHECK_FUNCS([memcpy lchown],
  [], [AC_MSG_ERROR([missing required function])])

I notice there's precedent for incorporating something into libcompat,
which actually looks a lot like Gnulib. From the outside it looks like
reinventing the wheel and I'm curious about that, but either way Gnulib
has a module that may help portability on other platforms.

It appears it just dies with ENOSYS on MinGW, at least for now, but I'll
take it :)
https://www.gnu.org/software/gnulib/manual/html_node/lchown.html

If you wish to avoid embedded code copies, the Gnulib Debian package has it.
Otherwise a similar libcompat function that dies might still be fun to try,
and if it bears serious consequences perhaps a flag could be required to
enable.

-- Package-specific info:
System tainted due to merged-usr-via-symlinks.

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

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

-- no debconf information


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

Bug#977781: [Pkg-javascript-devel] Bug#977781: real issue is, it does not pull not-yet-cached modules

[Akshay S Dinesh]

 > >I think the real issue is that it does not pull not-yet-cached 
modules.

 >


I did some console.log debugging yesterday.

The tarball-fetcher, for whatever be the reason, doesn't ever trigger 
the .on('finish' event


https://salsa.debian.org/js-team/node-yarnpkg/-/blob/master/src/fetchers/tarball-fetcher.js#L164

There are some 4 pipes before the finish event. I'm looking through each 
one of them to see if there's a mismatch.

Bug#977861: fwupd-amd64-signed: dpkg-vendor: not found

[Philip Wyett]

Package: fwupd-amd64-signed
Version: 1.5.3+2

Upgrade on testing/bullseye. "dpkg-vendor: not found" of package "dpkg-
dev".

Setting up fwupd (1.5.3-2) ...
Installing new version of config file /etc/fwupd/uefi.conf ...
Removing obsolete conffile /etc/modules-load.d/fwupd-msr.conf ...
Removing obsolete conffile /etc/modules-load.d/fwupd-platform-
integrity.conf ...
fwupd-offline-update.service is a disabled or a static unit not
running, not sta
rting it.
fwupd-refresh.service is a disabled or a static unit not running, not
starting i
t.
fwupd.service is a disabled or a static unit not running, not starting
it.
/var/lib/dpkg/info/fwupd.postinst: 54: dpkg-vendor: not found
Setting up libtie-ixhash-perl (1.23-2.1) ...
Setting up libencode-locale-perl (1.05-1.1) ...
Setting up libhtml-format-perl (2.12-1.1) ...
Setting up fwupd-amd64-signed (1.5.3+2) ...
/var/lib/dpkg/info/fwupd-amd64-signed.postinst: 17: dpkg-vendor: not
found

Regards

Phil

-- 
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


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

Bug#977860: fwupd: dpkg-vendor: not found

[Philip Wyett]

Package: fwupd
Version: 1.5.3-2

Upgrade on testing/bullseye. "dpkg-vendor: not found" of package "dpkg-
dev".

Setting up fwupd (1.5.3-2) ...
Installing new version of config file /etc/fwupd/uefi.conf ...
Removing obsolete conffile /etc/modules-load.d/fwupd-msr.conf ...
Removing obsolete conffile /etc/modules-load.d/fwupd-platform-
integrity.conf ...
fwupd-offline-update.service is a disabled or a static unit not
running, not sta
rting it.
fwupd-refresh.service is a disabled or a static unit not running, not
starting i
t.
fwupd.service is a disabled or a static unit not running, not starting
it.
/var/lib/dpkg/info/fwupd.postinst: 54: dpkg-vendor: not found
Setting up libtie-ixhash-perl (1.23-2.1) ...
Setting up libencode-locale-perl (1.05-1.1) ...
Setting up libhtml-format-perl (2.12-1.1) ...
Setting up fwupd-amd64-signed (1.5.3+2) ...
/var/lib/dpkg/info/fwupd-amd64-signed.postinst: 17: dpkg-vendor: not
found

Regards

Phil

-- 
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


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

Bug#976895: libasound2: regression (stops working): Alsa_driver: recover: pcm_status(): Broken pipe

[Thorsten Glaser]

tags 976895 + patch upstream
thanks

I’ve found that reverting a faulty upstream commit fixes this bug.

If there is no reaction within a week I intend to NMU this.

bye,
//mirabilos
-- 
(gnutls can also be used, but if you are compiling lynx for your own use,
there is no reason to consider using that package)
-- Thomas E. Dickey on the Lynx mailing list, about OpenSSLdiff -Nru alsa-lib-1.2.4/debian/changelog alsa-lib-1.2.4/debian/changelog
--- alsa-lib-1.2.4/debian/changelog 2020-12-07 22:02:09.0 +0100
+++ alsa-lib-1.2.4/debian/changelog 2020-12-22 02:20:29.0 +0100
@@ -1,3 +1,10 @@
+alsa-lib (1.2.4-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Revert an upstream commit breaking applications (Closes: #976895)
+
+ -- Thorsten Glaser   Tue, 22 Dec 2020 02:20:29 +0100
+
 alsa-lib (1.2.4-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru alsa-lib-1.2.4/debian/patches/976895.diff 
alsa-lib-1.2.4/debian/patches/976895.diff
--- alsa-lib-1.2.4/debian/patches/976895.diff   1970-01-01 01:00:00.0 
+0100
+++ alsa-lib-1.2.4/debian/patches/976895.diff   2020-12-22 02:20:09.0 
+0100
@@ -0,0 +1,28 @@
+# DP: revert upstream commit 4f90392f07e8822d1984ed990f622ad36022a4a3
+# DP: fixes Debian bug #976895
+
+--- a/src/pcm/pcm_plugin.c
 b/src/pcm/pcm_plugin.c
+@@ -541,20 +541,16 @@ static snd_pcm_sframes_t snd_pcm_plugin_
+ static int snd_pcm_plugin_status(snd_pcm_t *pcm, snd_pcm_status_t * status)
+ {
+   snd_pcm_plugin_t *plugin = pcm->private_data;
+-  snd_pcm_sframes_t err, avail;
++  snd_pcm_sframes_t err;
+ 
+   /* sync with the latest hw and appl ptrs */
+-  avail = snd_pcm_plugin_avail_update(pcm);
+-  if (avail < 0)
+-  return avail;
++  snd_pcm_plugin_avail_update(pcm);
+ 
+   err = snd_pcm_status(plugin->gen.slave, status);
+   if (err < 0)
+   return err;
+   status->appl_ptr = *pcm->appl.ptr;
+   status->hw_ptr = *pcm->hw.ptr;
+-  status->avail = avail;
+-  status->delay = snd_pcm_mmap_delay(pcm);
+   return 0;
+ }
+ 
diff -Nru alsa-lib-1.2.4/debian/patches/series 
alsa-lib-1.2.4/debian/patches/series
--- alsa-lib-1.2.4/debian/patches/series2020-08-20 19:56:34.0 
+0200
+++ alsa-lib-1.2.4/debian/patches/series2020-12-22 02:19:47.0 
+0100
@@ -1 +1,2 @@
 0001-Enabled-extended-namehints-in-alsa.conf.patch
+976895.diff

Bug#977859: ITP: debian-fbx -- Debian FreedomBox Pure Blend Metapackages

[Sunil Mohan Adapa]

Package: wnpp
Severity: wishlist
Owner: Sunil Mohan Adapa 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: debian-fbx
  Version : 1
  Upstream Author : FreedomBox packaging team 
* URL : https://salsa.debian.org/blends-team/fbx/
* License : GPL-3+
  Programming Lang: Debian blends framework
  Description : Debian FreedomBox Pure Blend Metapackages

FreedomBox is designed to be your own inexpensive server at home. It runs free
software and offers an increasing number of services ranging from a calendar or
jabber server to a wiki or VPN. A web interface allows you to easily install
and configure your apps. This package provides FreedomBox tasks in tasksel.

The package repository will be at:
https://salsa.debian.org/blends-team/fbx/

This package will be maintained by:
FreedomBox Packaging Team 
Debian Pure Blends Team 

It will be discussed at:
freedombox-pkg-t...@lists.alioth.debian.org
debian-ble...@lists.debian.org




-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE5xPDY9ZyWnWupXSBQ+oc/wqnxfIFAl/hTBoRHHN1bmlsQG1l
ZGhhcy5vcmcACgkQQ+oc/wqnxfImhBAAtHbeKUaOib0/cidLVAiwrAGgCTF09fO7
RmqjSQ+lGP08IdMzhlgb3iP0pvtr41eYU2c5h7ZzwbYf110PBeoqbrM6OTB+uyXH
G3lyijiRN9jaxdbkG9Ak754F+VoWXqRgziT4VIQeBOOypTKvOqPP3IqbPUJrASx8
e88RZfe46f9MZkKm/MZI5gn4Li1kvgqOYBEBTl6fO7yXOkxWhEAAWx6/g74dY+MK
q4KBAwLOcrznYQqhtHAfP2Ndv1zWKlCr89rkgdnBNsY9FBp2lgec3PlaZwDrGvxX
HIDT9OxgJMykFjDRT+a4he1Lqzn4ZhHXyrZVC3807YxbUA6lFVbLODIbRoZeAmBZ
7aLdHbxc8Yz3X69xT7U4q2nc6pv/ts6RosZQq0b1nuyNXme72vPOrsUI091Jy3kG
IzJ8piEtPhg77gZcg7gAmwJ7OlTloIky0SC1ckEqv27U9FTsICjOMNuOKPtzJ0yW
muNMEilgBRkHjs5Uk6PDy+7KNgvIMxLfymLiHdZy7OtEZrKq20YWfjyj10Fly2G5
8DUb1irDJMLmT4jDrAVSeM7Ycn9ZA3yLkSz/c8ziNKqI5PyLQ26F+u51XiqyLsLV
iO5yUJhpuamFabUEN8km1YS3IY9BMiAyo2pYdXwlTHHJi5mVMenS+KSKkI2a9G0Z
Ekx6PzxveU4=
=zAr+
-END PGP SIGNATURE-

Bug#977810: biber: Fails with exit code 9 - panic: MUTEX_LOCK (22) [Magic.xs:525] during global destruction.

[Norbert Preining]

tags 977810 + unreproducible moreinfo
thanks

Hi Pascal,

On Mon, 21 Dec 2020, Pascal Wichmann wrote:
> when running biber, it fails at properly destructing its objects,
> leading to an exit code of 9 (and therefore, breaking any other programs

I cannot reproduce this.

$ cat example.tex
\documentclass{article}
\usepackage[backend=biber]{biblatex}
\addbibresource{example.bib}
\begin{document}
I doubt that there is any useful information here~\cite{wikibook}.

All we know is limited, apart from knowing the answer we all know. Or do we? 
Wombat and Koala have discovered some interesting things~\cite{wombat2016}.

Some people are too nosy. What can happen to them is described by Laura 
Lion~\cite[9]{lion2010}.

\printbibliography
\end{document}

$ cat example.bib
@article{wombat2016,
author   = {Walther Wombat and Klaus Koala},
title= {The true meaning of 42},
journal  = {Journal of modern skepticism},
date = {2016},
keywords = {trusted},
}
@book{lion2010,
author   = {Laura Lion and  Gabrielle Giraffe and Carl Capybara},
title= {The dangers of asking the wrong question},
publisher= {publishing house},
date = {2010},
keywords = {trusted},
}
@online{wikibook,
title= {Generating Bibliographies with biblatex and biber},
organization = {Wikibooks},
date = {2016},
urldate  = {2016-03-07},
url  = 
{https://en.wikibooks.org/wiki/LaTeX/Generating_Bibliographies_with_biblatex_and_biber},
keywords = {untrusted},
}

$ latex example
This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian) 
(preloaded format=latex)
 restricted \write18 enabled.
entering extended mode
(./example.tex
LaTeX2e <2020-10-01> patch level 2
L3 programming layer <2020-10-27> xparse <2020-03-03>
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2020/04/10 v1.4m Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/biblatex.sty
(/usr/share/texlive/texmf-dist/tex/generic/pdftexcmds/pdftexcmds.sty
(/usr/share/texlive/texmf-dist/tex/generic/infwarerr/infwarerr.sty)
(/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty)
(/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty))
(/usr/share/texlive/texmf-dist/tex/latex/etoolbox/etoolbox.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
(/usr/share/texlive/texmf-dist/tex/latex/kvoptions/kvoptions.sty
(/usr/share/texlive/texmf-dist/tex/generic/kvsetkeys/kvsetkeys.sty))
(/usr/share/texlive/texmf-dist/tex/latex/logreq/logreq.sty
(/usr/share/texlive/texmf-dist/tex/latex/logreq/logreq.def))
(/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty)
(/usr/share/texlive/texmf-dist/tex/latex/url/url.sty)
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/blx-dm.def)
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/blx-compat.def)
(/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty
(/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-dvips.def))
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/blx-case-expl3.def
(/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty
(/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse-generic.tex))
) (/usr/share/texlive/texmf-dist/tex/latex/biblatex/biblatex.def)
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/bbx/numeric.bbx
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/bbx/standard.bbx))
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/cbx/numeric.cbx)
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/biblatex.cfg))
No file example.aux.
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/lbx/english.lbx)
No file example.bbl.

LaTeX Warning: Citation 'wikibook' on page 1 undefined on input line 5.


LaTeX Warning: Citation 'wombat2016' on page 1 undefined on input line 7.


Overfull \hbox (1.2478pt too wide) in paragraph at lines 7--8
\OT1/cmr/m/n/10 we? Wom-bat and Koala have dis-cov-ered some in-ter-est-ing thi
ngs [[]].

LaTeX Warning: Citation 'lion2010' on page 1 undefined on input line 9.


LaTeX Warning: Empty bibliography on input line 11.

[1] (./example.aux)

LaTeX Warning: There were undefined references.


Package biblatex Warning: Please (re)run Biber on the file:
(biblatex)example
(biblatex)and rerun LaTeX afterwards.

 )
(see the transcript file for additional information)
Output written on example.dvi (1 page, 728 bytes).
Transcript written on example.log.

$ biber example
INFO - This is Biber 2.15
INFO - Logfile is 'example.blg'
INFO - Reading 'example.bcf'
INFO - Found 3 citekeys in bib section 0
INFO - Processing section 0
INFO - Looking for bibtex format file 'example.bib' for section 0
INFO - LaTeX decoding ...
INFO - Found BibTeX data source 'example.bib'
INFO - Overriding locale 'en-US' defaults 'variable = shifted' with 

Bug#917288: (no subject)

[Josh Anders]

tags 917288 - unreproducible
found 917288 tidy/2:5.6.0-11
thanks

This is still a bug as of the version currently in sid:

josh@thinkpad-18:~$ touch test.html
josh@thinkpad-18:~$ tidy test.html
line 1 column 1 - Warning: inserting missing 'title' element
Info: Document content looks like HTML5
Tidy found 1 warning and 0 errors!
[snip]

josh@thinkpad-18:~$ chmod 400 test.html
josh@thinkpad-18:~$ tidy test.html
Document: "test.html" is not a file!
[snip]


Thanks,
Josh

Bug#976235: enlightenment: e switches off screen|monitor

[enno]

> "Ross" == Ross Vandegrift  writes:
> Do your backlight keys work?  E24 has introduced additional
> screen dimming, and it will dim the backlight fully.  Maybe
> there's a strange interaction between your video card's
> brightness control and E's behavior.
>
> It's possible to disable this, but it'll be hard without ever
> getting an E session going.  To try disabling by hand:
>
> 1) apt install libeet-bin
> 2) vieet ~/.e/e/config/standard/e_comp.cfg config
> 3) Search for "nofade"
> 4) Change the value from 0 to 1.  The line should be:
> value "nofade" uchar: 1;

Done that.  Makes no difference at all--at least none that I can detect.  Still 
enlightenment_start brings up enlightenment for a second or so, then the screen 
goes black--and is black on all VTs BUT after switching to one of VT1 to VT6, 
and typing blindly--after about 2 minutes the console lights up and is back to 
normal.

As soon as I switch to VT7, there's about half a second of seeing e, then the 
screen goes black--and again all VTs follow being black.

BTW what do you mean by backlight keys?

Anyway I don't think that there's any `strange interaction', because before I 
switched that #! switch to 90 everything was alright--apart from e-dialogs 
complaining about unconfigured screens (or so, can't really remember the 
wording).  Thus it's certainly not a problem between e and my hardware.

I suppose I'll try to try the Phabricator, it seems to be somewhat difficult to 
enter there...

C ya, e.

--
  //   enno@gmx.net
/\\\   Mag. Enno Deimel
  .\o
 \\  \ _  \Wisely and slow; they stumble that run fast.
\\\ \_/
gpg-fp: eefe b049 6fe6 fc0b 0ec4  f39e af6a c178 eb98 909a

Bug#976895: libasound2: regression (stops working): Alsa_driver: recover: pcm_status(): Broken pipe

[Thorsten Glaser]

affects 976895 musescore
affects 976895 musescore3
thanks

Thorsten Glaser dixit:

>Hello maintainers,
>
>>The latest libasound2 introduced a severe regression:
>
>ping?

ping again, after another week… *any* response would have been
welcome, more than being ignored…

>This bug makes MuseScore (2 and 3) on an ALSA-only system
>completely unusable. To have this fixed before freezing
>would be massively appreciated.

bye,
//mirabilos
-- 
15:41⎜ Somebody write a testsuite for helloworld :-)

Bug#977835: Please package the lastest version >= 3.5.2

[Thorsten Glaser]

Picca Frédéric-Emmanuel dixit:

>thanks for considering

Not before bullseye. There are many regressions and problems
with the new releases. I plan on doing (at least) one more
upload with more individual fixes backported, though ☺

My current plan is to package 3.6.x after bullseye, providing
them to users via bullseye-backports and buster-backports-sloppy
as usual.

With enough time I’ll begin packaging these in experimental.

Thanks,
//mirabilos
-- 
Yay for having to rewrite other people's Bash scripts because bash
suddenly stopped supporting the bash extensions they make use of
-- Tonnerre Lombard in #nosec

Bug#977857: libreoffice-common: On Wayland, it doesn't work without the xwayland pkg but installation does not pull xwayland as a dependency

[jman]

As an additional informaton, I've tried installing the vanilla
LibreOffice 7.0.4.2 distribution from www.libreoffice.org, installed
these three packages:

libobasis7.0-images_7.0.4.2-2_amd64.deb
libreoffice7.0_7.0.4.2-2_amd64.deb
libreoffice7.0-calc_7.0.4.2-2_amd64.deb
libreoffice7.0-writer_7.0.4.2-2_amd64.deb

and LibreOffice seems to work just fine 9even without xwayland installed)

Bug#977858: apt-listchanges: crashes with name 'syslog' is not defined

[Robert Luberda]

Package: apt-listchanges
Version: 3.22+nmu2
Severity: normal

After setting frontend  to 'syslog' in /etc/apt-listchanges.conf 
(manually, because `dpkg-reconfigure apt-listchanges' does not 
allow me to do it for some reason) apt-listchanges fails with:

  File "/usr/bin/apt-listchanges", line 323, in 
main(config)
  File "/usr/bin/apt-listchanges", line 162, in main
_display(frontend, changes, lambda: _('apt-listchanges: Changelogs'))
  File "/usr/bin/apt-listchanges", line 305, in _display
frontend.display_output(changes)
  File "/usr/share/apt-listchanges/apt_listchanges.py", line 332, in 
display_output
syslog.openlog(facility=syslog.LOG_DAEMON)
NameError: name 'syslog' is not defined


Regards,
robert


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


Versions of packages apt-listchanges depends on:
ii  apt2.1.14
ii  debconf [debconf-2.0]  1.5.74
ii  python33.9.0-4
ii  python3-apt2.1.7
ii  python3-debconf1.5.74
ii  sensible-utils 0.0.12+nmu1
ii  ucf3.0043

apt-listchanges recommends no packages.

Versions of packages apt-listchanges suggests:
ii  chromium [www-browser]83.0.4103.116-3.1+b2
ii  elinks [www-browser]  0.13.2-1+b1
ii  firefox-esr [www-browser] 78.6.0esr-1
ii  gnome-terminal [x-terminal-emulator]  3.38.1-2
ii  links [www-browser]   2.21-1
ii  lynx [www-browser]2.9.0dev.6-1
ii  postfix [mail-transport-agent]3.5.6-1
ii  python3-gi3.38.0-1+b2
ii  terminator [x-terminal-emulator]  1.92-2
ii  xterm [x-terminal-emulator]   362-1

-- Configuration Files:
/etc/apt/apt.conf.d/20listchanges changed:
DPkg::Pre-Install-Pkgs { "/usr/bin/apt-listchanges --apt"; };
DPkg::Tools::Options::/usr/bin/apt-listchanges::Version "2";
DPkg::Tools::Options::/usr/bin/apt-listchanges::InfoFD "20";
Dir::Etc::apt-listchanges-main "listchanges.conf";
Dir::Etc::apt-listchanges-parts "listchanges.conf.d";


-- debconf information:
* apt-listchanges/reverse: false
* apt-listchanges/headers: true
* apt-listchanges/confirm: true
* apt-listchanges/no-network: false
* apt-listchanges/save-seen: true
* apt-listchanges/email-format: html
* apt-listchanges/email-address: root
* apt-listchanges/frontend: pager
* apt-listchanges/which: both

Bug#977857: libreoffice-common: On Wayland, it doesn't work without the xwayland pkg but installation does not pull xwayland as a dependency

[jman]

Package: libreoffice-common
Version: 1:7.0.4~rc2-1
Severity: normal

Dear Maintainer,

I have installed Libreoffice on a Wayland+Sway system without any X11 package 
(included xwayland).

Upon starting libreoffice I get an error because the display :0 is tried:

```
$ soffice --version
LibreOffice 7.0.4.2 00(Build:2)

$ soffice
/usr/lib/libreoffice/program/soffice.bin X11 error: Can't open display:
   Set DISPLAY environment variable, use -display option
   or check permissions of your X-Server
   (See "man X" resp. "man xhost" for details)
```

I tried setting these env vars but it didn't work:

```
export _JAVA_AWT_WM_NONREPARENTING=1
export MOZ_ENABLE_WAYLAND=1
export QT_QPA_PLATFORM=wayland-egl
export QT_QPA_PLATFORMTHEME=qt5ct
export QT_WAYLAND_FORCE_DPI=96
export QT_WAYLAND_DISABLE_WINDOWDECORATION=1
export SDL_VIDEODRIVER=wayland
export SAL_USE_VCLPLUGIN=gtk3
```

In order to make Libreoffice work, the package `xwayland` should be installed 
as a dependency.

Unless I'm wrong, I believe the real issue is that Libreoffice does not work on 
a pure Wayland
installation, but this fact is not very clear to the user. I've tried searching 
for related issue on
the Libreoffice buttracker but found none.

Suggestion: make `xwayland` a required dependency of Libreoffice until the day 
that Libreoffice does
not need Xorg anymore.

Thanks,

-- Package-specific info:

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

Kernel: Linux 5.9.0-4-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 libreoffice-common depends on:
ii  libnumbertext-data 1.0.6-1
ii  libreoffice-style-colibre  1:7.0.4~rc2-1
ii  ucf3.0043
ii  ure1:7.0.4~rc2-1+b1

Versions of packages libreoffice-common recommends:
ii  apparmor2.13.5-1+b2
ii  fonts-liberation2   2.1.1-1
ii  libexttextcat-data  3.4.5-1
ii  python3-uno 1:7.0.4~rc2-1+b1
ii  xdg-utils   1.1.3-2

Versions of packages libreoffice-common suggests:
ii  libreoffice-style-colibre [libreoffice-style]  1:7.0.4~rc2-1

Versions of packages python3-uno depends on:
ii  libc62.31-5
ii  libgcc-s110.2.1-1
ii  libpython3.9 3.9.1-1
ii  libreoffice-core 1:7.0.4~rc2-1+b1
ii  libstdc++6   10.2.1-1
ii  libuno-cppu3 1:7.0.4~rc2-1+b1
ii  libuno-cppuhelpergcc3-3  1:7.0.4~rc2-1+b1
ii  libuno-sal3  1:7.0.4~rc2-1+b1
ii  libuno-salhelpergcc3-3   1:7.0.4~rc2-1+b1
ii  python3  3.9.0-4
ii  python3.93.9.1-1
ii  ucf  3.0043
ii  uno-libs-private 1:7.0.4~rc2-1+b1

-- no debconf information

Bug#974011: xmille: Incorrect license/copyright for xmille

[Keith Packard]

Adrian Bunk  writes:

> On Mon, Dec 07, 2020 at 09:12:23AM -0800, Keith Packard wrote:
>> Adrian Bunk  writes:
>> >
>> > Keith, do you remember the copyright history of this code?
>> 
>> I may have copied the underlying mille sources *before* copyrights were
>> added to each file; I started work on the X10 version of xmille around
>> 1985 or 1986. I guess I could have mistakenly removed them? Thanks for
>> discovering this error; I can fix these "upstream" and publish a new
>> version?
>
> I am just a user who would like to see this package also in bullseye.
>
> A new upstream version would be good, but it is not obvious to me 
> whether you or Steve M. Robbins or anyone else is considered upstream
> or should become upstream (again).

It looks like the version in the archive is *very* old (I mean, "new"
xmille is still old, but there is a more modern port that uses Xt at
least). I've got the newer version working, even on 64-bit systems, and
have applied suitable copyright messages.

https://keithp.com/cgit/games.git/

This package includes a bunch of games using a shared widget library,
including a raft of solitaire, another (not terribly good) reversi
implementation and even a version of dominoes. Having this build only
xmille would be fairly easy. If that seems like a reasonable way
forward, I'll go ahead and create a release of that package.

-- 
-keith


signature.asc
Description: PGP signature

Bug#977856: librepository: fails to build source package

[Holger Levsen]

Package: librepository
Version: 1.1.6-3
Severity: serious

Dear Maintainer,

I wanted to do a source only upload of librepository
(because there are no .buildinfo files for it in the archive,
as it has been uploaded before 2016), but it fails to build
the source package. The binary package builds just fine.

Steps to reproduce:

$ apt source librepository
$ cd librepository-*
$ dpkg-buildpackage
dpkg-buildpackage: info: source package librepository
dpkg-buildpackage: info: source version 1.1.6-3
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Emmanuel Bourg 
dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build .
 fakeroot debian/rules clean
dh clean --with javahelper
   dh_auto_clean
ant -propertyfile ./debian/ant.properties clean
/usr/bin/java: error while loading shared libraries: libjli.so: cannot open 
shared object file: No such file or directory
dh_auto_clean: error: ant -propertyfile ./debian/ant.properties clean returned 
exit code 127
make: *** [debian/rules:6: clean] Error 127
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2
$

(This is with or without any changes to the source package.)


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁   holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀ PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
 ⠈⠳⣄

Some people say that the climate crisis  is something that we all have created,
but  that is not true,  because if everyone is guilty  then no one is to blame.
And someone is to blame.  Some people, some companies,  some decision-makers in
particular, have known exactly what priceless values they have been sacrificing
to continue making unimaginable amounts of money. (Greta Thunberg)


signature.asc
Description: PGP signature

Bug#977855: ITP: portfolio -- Minimalist file manager for those who want to use Linux mobile devices

[Henry-Nicolas Tourneur]

Package: wnpp
Severity: wishlist
Owner: Henry-Nicolas Tourneur 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: portfolio-filemanager
  Version : 0.9.1
  Upstream Author : Martin Abente Lahaye 
* URL : https://github.com/tchx84/Portfolio
* License : GPLv3+
  Programming Lang: Python
  Description : Minimalist file manager for those who want to use Linux 
mobile devices

PortFolio is a file manager which is designed for Linux mobile devices.
It uses the libhandy toolkit to provide a mobile friendly, GTK based,
user interface.

This package will be maintained through the DebianOnMobile team.

Bug#977343: RFS: breseq/0.35.4+ds-1 [ITP] -- Find mutations relative to reference sequences

[Adam Borowski]

On Mon, Dec 14, 2020 at 08:47:42AM +0100, Gürkan Myczko wrote:
>  * Package name: breseq
>Version : 0.35.4+ds-1

> Changes for the initial release:
> 
>  breseq (0.35.4+ds-1) unstable; urgency=medium
>  .
>* Initial release. (Closes: #942845)

Alas, it fails tests -- then continues to build the package successfully:

   dh_auto_test
make -j64 test VERBOSE=1
make[1]: Entering directory '/<>'
echo "export TESTBINPREFIX=./src/c/breseq" > ./tests/test.config;
echo "export BRESEQ_DATA_PATH=./src/c/breseq" >> ./tests/test.config;
echo "export BRESEQ_TEST_THREAD_ARG=\"-j 4\"" >> ./tests/test.config;
./tests/test.sh test tests
3 
TEST: tests/lambda_mult_ref_read/testcmd.sh test

TEST DIRECTORY: tests/lambda_mult_ref_read

BRESEQ COMMAND:
./src/c/breseq/breseq -j 4 -o tests/lambda_mult_ref_read -r 
tests/lambda_mult_ref_read/../data/lambda/lambda.1-2.gbk -r 
tests/lambda_mult_ref_read/../data/lambda/lambda.3.gbk -r 
tests/lambda_mult_ref_read/../data/lambda/lambda.4.gbk -r 
tests/lambda_mult_ref_read/../data/lambda/lambda.5.gbk -l 50 
tests/lambda_mult_ref_read/../data/lambda/empty.fastq 
tests/lambda_mult_ref_read/../data/lambda/only_bad.fastq 
tests/lambda_mult_ref_read/../data/lambda/lambda_mixed_population.1.fastq 
tests/lambda_mult_ref_read/../data/lambda/lambda_mixed_population.2.fastq 
tests/lambda_mult_ref_read/../data/lambda/lambda_mixed_population.3.fastq 
tests/lambda_mult_ref_read/../data/lambda/lambda_mixed_population.4.fastq 
tests/lambda_mult_ref_read/../data/lambda/lambda_mixed_population.5.fastq
Program data path set via BRESEQ_DATA_PATH: ./src/c/breseq

breseq 0.35.4 http://barricklab.org/breseq

Active Developers: Barrick JE, Deatherage DE
Contact:   

breseq is free software; you can redistribute it and/or modify it under the
terms the GNU General Public License as published by the Free Software 
Foundation; either version 2, or (at your option) any later version.

Copyright (c) 2008-2010 Michigan State University
Copyright (c) 2011-2017 The University of Texas at Austin

If you use breseq in your research, please cite:

  Deatherage, D.E., Barrick, J.E. (2014) Identification of mutations
  in laboratory-evolved microbes from next-generation sequencing
  data using breseq. Methods Mol. Biol. 1151: 165–188.

If you use structural variation (junction) predictions, please cite:

  Barrick, J.E., Colburn, G., Deatherage D.E., Traverse, C.C.,
  Strand, M.D., Borges, J.J., Knoester, D.B., Reba, A., Meyer, A.G. 
  (2014) Identifying structural variation in haploid microbial genomes 
  from short-read resequencing data using breseq. BMC Genomics 15:1039.

---> ERROR Required executable "bowtie2" or "bowtie2-build" not found.
---> See http://bowtie-bio.sourceforge.net/bowtie2
---> ERROR Required executable "R" not found.
---> See http://www.r-project.org

Comparing files: "tests/lambda_mult_ref_read/output/evidence/annotated.gd" 
"tests/lambda_mult_ref_read/expected.gd"
/usr/bin/diff: tests/lambda_mult_ref_read/output/evidence/annotated.gd: No such 
file or directory

Failed check
/usr/bin/diff: tests/lambda_mult_ref_read/output/evidence/annotated.gd: No such 
file or directory


./src/c/breseq/gdtools COMPARE -r 
tests/lambda_mult_ref_read/../data/lambda/lambda.1-2.gbk -r 
tests/lambda_mult_ref_read/../data/lambda/lambda.3.gbk -r 
tests/lambda_mult_ref_read/../data/lambda/lambda.4.gbk -r 
tests/lambda_mult_ref_read/../data/lambda/lambda.5.gbk -o 
tests/lambda_mult_ref_read/failed_compare.html 
tests/lambda_mult_ref_read/output/evidence/annotated.gd 
tests/lambda_mult_ref_read/expected.gd
Program data path set via BRESEQ_DATA_PATH: ./src/c/breseq

breseq 0.35.4 http://barricklab.org/breseq

Active Developers: Barrick JE, Deatherage DE
Contact:   

breseq is free software; you can redistribute it and/or modify it under the
terms the GNU General Public License as published by the Free Software 
Foundation; either version 2, or (at your option) any later version.

Copyright (c) 2008-2010 Michigan State University
Copyright (c) 2011-2017 The University of Texas at Austin

If you use breseq in your research, please cite:

  Deatherage, D.E., Barrick, J.E. (2014) Identification of mutations
  in laboratory-evolved microbes from next-generation sequencing
  data using breseq. Methods Mol. Biol. 1151: 165–188.

If you use structural variation (junction) predictions, please cite:

  Barrick, J.E., Colburn, G., Deatherage D.E., Traverse, C.C.,
  Strand, M.D., Borges, J.J., Knoester, D.B., Reba, A., Meyer, 

Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

[Elana Hashman]

On Thu, Nov 19, 2020 at 09:04:00PM -0800, Elana Hashman wrote:
> 
> I caution folks from speculating too much on the maintainer's
> motivations and reasoning while they haven't yet had a chance to share
> their perspective on the bug. :)
> 
> From what I can see reading through both #964139 and #960780, no
> technical rationale has been given for why the script was removed, only
> a statement that the removal was intentional.[0]
> 
> It would be much appreciated if Michael Biebl or another maintainer from
> the Utopia team could add some context here.
> 
> [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964139#62

The maintainer, Michael Biebl, reached out to the tech-ctte privately. I
have summarized his reasoning for why he dropped support for elogind and
the init script that prompted this bug:


Less than 1% of users are installing sysvinit-core, with a steady
downward trend.[1]

If we require packages to maintain sysvinit support, then this cements
sysvinit/sysv-rc as the least common denominator for packages and blocks
the use of many of systemd's features, such as timers. This results in
an OS that is less integrated than it could be, which hurts the vast
majority of users who do not use sysvinit.

Trying to support multiple init systems generates a lot of additional
work for maintainers, who are already stretched thin. Time and energy
are limited resources, and triaging and root-causing bugs from
supporting multiple init systems take a lot of time; maintaining an init
script comprises only a small part of the support burden.

elogind is very difficult to support in its current state (see the
following bugs: [2] [3] [4] [5]), which is why Michael does not want to
maintain support for it.

[1] https://qa.debian.org/popcon.php?package=sysvinit
https://qa.debian.org/popcon-graph.php?packages=sysvinit-core
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934491
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923244
[4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968379
[5] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959920


Feel free to direct any questions to me.

- e


signature.asc
Description: PGP signature

Bug#977780: connman: wifi stopped working with net.connman.Error.NoCarrier

[Francesco Poli]

On Sun, 20 Dec 2020 19:38:52 +0100 Francesco Poli (wintermute) wrote:

[...]
> Then, after one more reboot, I suddenly became unable to connect
> to the Wireless LAN, getting the following error in a dialog window:
> 
>   Failed to toggle connection state.
> 
>   GDBus.Error:net.connman.Error.NoCarrier: No carrier
> 
> I really cannot understand what's going on.

Now I understand even less...

I performed some more tests today.
At first I had the same issue again for a while, but then I did the
following: I selected my Wireless LAN (in the connman-gtk GUI), clicked
on the button with the little gear to see its settings, went to the
"Clear settings" tab and clicked on the "Reset" button, in order to set
all properties to defaults.

Guess what?
The issue disappeared and I was able to connect to my Wireless LAN
again (without even having to re-enter my password, which was
remembered, despite the reset!). And then disconnect. And then connect
again.
Even after a reboot.
Everything seems back to normal now.

But I have no idea why.

Unfortunately, I didn't make a copy of the wireless network
configuration file, before resetting its properties.
Hence, I am not sure what changed because of the reset.

Do you happen to know what may have happened?


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpfovtcpjTxC.pgp
Description: PGP signature

Bug#975539: buku's autopkg tests fail with Python 3.9

[s3v]

Reported upstream.
https://github.com/jarun/buku/issues/490

Kind Regards

Bug#977854: German translation for the manpage (po4a)

[Pfannenstein Erik]

Package: fakeroot
Severity: wishlist
Tags: l10n patch

Dear Maintainer,

I have updated the German translation of fakeroot's manpage.
Please include it into the package as you see fit.

I found some FIXMEs in the file, maybe you'd like to take a look at them:
* Line 162: There's a period before the gaps as well as after them.
* Line 216: It should read "to be run" instead of "to be ran".
* Line 487: There's a period before the gaps as well as after them.
* Line 713: same as above
* Line 734: The name "jost witteveen" is written in lower case, should be upper 
case.
* Line 774: There's a period missing after the .
* Line 789: There are two commas missing, namely after faked and debuld.
* Line 908: There's a period before tha gaps as well as after them.
* Line 1000ff: not ordered alphabetically, which is commonly preferred

Best regards,
Erik

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

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

Versions of packages fakeroot depends on:
ii  libc62.31-4
pn  libfakeroot  

fakeroot recommends no packages.

fakeroot suggests no packages.# Translation of the fakeroot manpage to German.
# Copyright (C) 1997-2001 Joost Witteveen, 2002-2009 Clint Adams,
#   2009 Regis Duchesne.
# This file is distributed under the same license as the fakeroot package.
# Copyright (C) of this file 2011 Chris Leick.
# Copyright (C) of this file 2020 Erik Pfannenstein.
#
msgid ""
msgstr ""
"Project-Id-Version: fakeroot 1.18.1-1\n"
"Report-Msgid-Bugs-To: faker...@packages.debian.org\n"
"POT-Creation-Date: 2020-09-22 16:23-0400\n"
"PO-Revision-Date: 2020-10-06 01:14+0200\n"
"Last-Translator: Erik Pfannnenstein \n"
"Language-Team: German \n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Poedit 2.4.1\n"

# type: TH
#. type: TH
#: ../doc/fakeroot.1:16
#, no-wrap
msgid "fakeroot"
msgstr "fakeroot"

#. type: TH
#: ../doc/fakeroot.1:16
#, no-wrap
msgid "5 October 2014"
msgstr "5. Oktober 2014"

# type: TH
#. type: TH
#: ../doc/fakeroot.1:16 ../doc/faked.1:16
#, no-wrap
msgid "Debian Project"
msgstr "Debian-Projekt"

# type: TH
#. type: TH
#: ../doc/fakeroot.1:16
#, no-wrap
msgid "Debian manual"
msgstr "Debian-Handbuch"

# type: SH
#. Manpage by J.H.M. Dassen 
#. and Clint Adams
#. type: SH
#: ../doc/fakeroot.1:19 ../doc/faked.1:19
#, no-wrap
msgid "NAME"
msgstr "NAME"

# type: Plain text
#. type: Plain text
#: ../doc/fakeroot.1:22
msgid ""
"fakeroot - run a command in an environment faking root privileges for file "
"manipulation"
msgstr ""
"fakeroot - einen Befehl zur Dateimanipulation in einer Umgebung mit "
"fingierten Root-Rechten ausführen"

# type: SH
#. type: SH
#: ../doc/fakeroot.1:22 ../doc/faked.1:22
#, no-wrap
msgid "SYNOPSIS"
msgstr "ÜBERSICHT"

# type: Plain text
#. type: Plain text
#: ../doc/fakeroot.1:38
msgid ""
"B B<[-l|--lib> I B<[--faked> IB<]> B<[-i> "
"IB<]> B<[-s> IB<]> B<[-u|--unknown-is-real ]> B<[-b|--"
"fd-base ]> B<[-h|--help ]> B<[-v|--version ]> B<[--]> B<[command]>"
msgstr ""
"B B<[-l|--lib> I B<[--faked> "
"IB<]> B<[-i> IB<]> B<[-s> "
"IB<]> B<[-u|--unknown-is-real ]> B<[-b|--fd-base ]> "
"B<[-h|--help ]> B<[-v|--version ]> B<[--]> B<[Befehl]>"

# type: SH
#. type: SH
#: ../doc/fakeroot.1:38 ../doc/faked.1:30
#, no-wrap
msgid "DESCRIPTION"
msgstr "BESCHREIBUNG"

# type: Plain text
#. type: Plain text
#: ../doc/fakeroot.1:49
msgid ""
"B runs a command in an environment wherein it appears to have root "
"privileges for file manipulation.  This is useful for allowing users to "
"create archives (tar, ar, .deb etc.) with files in them with root "
"permissions/ownership.  Without B one would need to have root "
"privileges to create the constituent files of the archives with the correct "
"permissions and ownership, and then pack them up, or one would have to "
"construct the archives directly, without using the archiver."
msgstr ""
"B führt einen Befehl in einer Umgebung aus, in der es scheint, als "
"habe er Root-Rechte zur Dateimanipulation. Auf diese Weise können einfache "
"Benutzer Archive (tar, ar, .deb etc.) erstellen, welche Dateien "
"enthalten, die Root-Rechte haben/Root gehören. Ohne B wären "
"Root-Rechte nötig, um die einzelnen Dateien des Archivs mit den "
"korrekten Zugriffs- und Besitzrechten zu erstellen und sie einzuhüllen oder "
"diese Archive müssten direkt, ohne Benutzung des Archivierungsprogramms, "
"erstellt werden."

# type: Plain text
#. type: Plain text
#: ../doc/fakeroot.1:61
msgid ""
"B works by replacing the file manipulation 

Bug#977814: clazy's autopkg tests fail with llvm 11.0.1 rc2

[Pino Toscano]

retitle llvm-toolchain-11/1:11.0.1~+rc1-1 breaks behaviour with 1:11.0.0-5
reassign 977814 src:llvm-toolchain-11 llvm-toolchain-11/1:11.0.1~+rc1-1
affects 977814 src:clazy
thanks

Hi,

I did a change in clazy today, landed as 1.8-2, but we still have
failures, so I did some more research.

We currently have these versions of llvm-toolchain-11 and clazy:
- llvm-toolchain-11/testing: 1:11.0.0-5
- llvm-toolchain-11/unstable: 1:11.0.1~+rc2-1 (the same can be said for 
1:11.0.1~+rc1-1 too)
- clazy/testing: 1.8-1+b1
- clazy/unstable: 1.8-2

clazy executes its own test suite both at build time (with the just
built binaries/plugin), and as autopkgtest (with what is installed by
the 'clazy' package).

We have the following situation:
a) clazy/testing
   a.1) PASS: build against llvm-toolchain-11/testing
   a.2) PASS: autopkgtest against llvm-toolchain-11/testing
   a.3) FAIL: autopkgtest against llvm-toolchain-11/unstable
b) clazy/unstable
   b.1) PASS: build against llvm-toolchain-11/unstable
   b.2) FAIL: autopkgtest against llvm-toolchain-11/testing
   b.3) PASS: autopkgtest against llvm-toolchain-11/unstable

So, to me it looks like we have two problems in llvm-toolchain-11:
1) something in llvm-toolchain-11/unstable breaks compatibility with
   clazy/testing, and thus it breaks the CI testing for testing
   migration of llvm-toolchain-11/unstable, case (a.3);
   in addition, clazy/unstable is now blocked for a similar situation,
   i.e. case (b.2)
2) in the dependencies of clazy I see:
Depends: libc6 (>= 2.14), libclang-cpp11, libllvm11 (>= 1:9~svn298832-1~), 
libstdc++6 (>= 9), clang-11
   that is, libllvm11 has a version as specified by shlibs, while
   libclang-cpp11 not; this sort of causes the case (b.2), as it allows
   that combination (as llvm-toolchain-11/testing is enough to satisfy
   the dependencies of clazy/unstable); a possible workaround is to make
   sure that all the libraries in llvm-toolchain-11 without symbols
   cause strict dependencies, as done by the following patch:
--- a/debian/rules
+++ b/debian/rules
@@ -724,7 +724,7 @@ override_dh_makeshlibs:
dh_makeshlibs -pliblldb-$(LLVM_VERSION) -V"liblldb-$(LLVM_VERSION) (>= 
1:9~svn298832-1~)"
dh_makeshlibs -plibllvm$(LLVM_VERSION) -V"libllvm$(LLVM_VERSION) (>= 
1:9~svn298832-1~)"
dh_makeshlibs -plibomp$(SONAME_OPENMP)-$(LLVM_VERSION) 
-V"libomp$(SONAME_OPENMP)-$(LLVM_VERSION) (>= 1:9~svn298832-1~)"
-   dh_makeshlibs --remaining-packages
+   dh_makeshlibs --remaining-packages -V

 override_dh_shlibdeps:
 # Ignore asan libraries. They would trigger dependencies to multiarch libraries

In short: I'm reassigning this to llvm-toolchain-11, because there is a
behaviour change in the new version, and because its libraries cause too
loose dependencies. In the end, the clazy autopkgtest works properly,
and it looks like it caught actual issues in llvm-toolchain-11.

LLVM maintainers: please investigate and fix, thanks.

Thanks,
-- 
Pino Toscano

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

Bug#934242: crystalhd: unusable without (available and properly working) firmware

[Jonas Smedegaard]

Hi Paul,

Quoting Paul Gevers (2020-12-21 22:49:18)
> [Release Team member watching]

Nice :-)


> On Thu, 08 Aug 2019 17:37:35 +0200 Jonas Smedegaard  wrote:
> > Source: crystalhd
> > Version: 1:0.0~git20110715.fdd2f19-1
> > Severity: grave
> > Justification: renders package unusable
> >
> > It seems that libcrystalhd3 is only really useful together with 
> > firmware-crystalhd, which was never really usable in Debian, leading 
> > to that package being dropped: https://bugs.debian.org/865978
> > 
> > If someone wants to revive CrystalHD in Debian, it seems a good 
> > place to start is 
> > https://www.mythtv.org/wiki/Broadcom_Crystal_HD#Feb._2014_Update
> 
> Can you elaborate a bit? The package has a huge popcon (hence it's not 
> autoremoved). You're saying that all those people had it installed in 
> vain? Or is that due to a (past) library dependency and didn't it 
> actually add anything?

Both:

  a) It never really worked (see bug#865978), and
  b) libavcodec* linked with it in Buster, and
  c) I guess because apt-mark is not really used
 (few use aptitude which invented the concept,
 and even debian-installer fails to provide an ideal baseline -
 see bug#742977)
 most previously affected users continue to have it installed
 after ffmpeg 7:4.1.4-1 stopped linking with it
 (see bug#917292).


> elbrus@coccia:~$ dak rm --no-action -R  --suite testing crystalhd
> Will remove the following packages from testing:
> 
>  crystalhd | 1:0.0~git20110715.fdd2f19-13 | source
> gstreamer1.0-crystalhd | 1:0.0~git20110715.fdd2f19-13 | amd64, i386
> libcrystalhd-dev | 1:0.0~git20110715.fdd2f19-13 | amd64, i386
> libcrystalhd3 | 1:0.0~git20110715.fdd2f19-13 | amd64, i386
> 
> Maintainer: Debian Multimedia Maintainers
> 
> 
> --- Reason ---
> 
> --
> 
> Checking reverse dependencies...
> # Broken Depends:
> kylin-video: kylin-video [amd64 i386]
> 
> # Broken Build-Depends:
> kylin-video: libcrystalhd-dev
> 
> Dependency problem found.

Yes, there are still packages depending on it: Someone needs to work 
actively with those still believing the library is more than snakeoil - 
because our mechanisms auto-pressuring packages to to stay alert and in 
line or else get kicked from testing works only on edge packages - 
packages "well connected" in Debian are not affected.

(while the allegory is funny, I really don't mean to imply that the 
mechanisms were _intented_ to treat packages unequally, only that in 
effect it does)


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#975591: update-rc.d disable

[Lorenzo]

On Mon, 21 Dec 2020 13:19:59 -0400
Jesse Smith  wrote:

> As I understand it Thorsten is looking for a way to have a service
> installed, that can be run or stopped manually. But the service is
> never started/stopped automatically when switching runlevels. Is that
> correct?

I think he might have issues also with start/restart/stop during
package upgrades, but i'm not sure..

> 
> If it is, I wonder if insserv's "overrides" feature would work here?
> An override is a file which sets which runlevels will be used to
> start/stop a service that is kept in a separate location so as to not
> be overwritten by the package manager. If the override file was
> created and set so it had no start/stop runlevels then I think the
> service would only start/stop when manually controlled (ie with
> /etc/init.d/service-name stop).
> 
> There is a short write-up on insserv overrides in its manual page.
> Would that suit the purposes here? If so, then I think we don't need
> to extend insserv, jut add a feature to update-rc.d which would
> create a minimal overrides file for given service. Thoughts?
> 
> Jesse
> 

It will probably works but I suggest a more radical approach:
if the sysadmin doesn't want insserv to manage the symlinks, then just
don't call insserv seems the right thing to do.

I suggest something like the following

* Add a new command 

update-rc.d mask/unmask

The default state is unmask: when a service is masked the sysadmin is
supposed to take care of symlinks in all runlevels, and also he decides
when to start/stop/restart the service

* use a flag file to mark a service as masked

for example, a 'foo' service is considered masked if
/etc/init.d/.foo file exists

* update-rc.d defaults/defaults-disabled are noop when a service is
  masked (so insserv is not called during install/upgrades..)

* update-rc.d remove will remove the flag file, if any (it's called only
  on purge)

* all invoke-rc.d actions are noop when a service is masked


This way the sysadmin will be able to delete the symlinks (or set an
arbitrary boot order) without having to deal with insserv reordering
the links.  It also ensures that the service does not get
started/stopped automatically with package upgrades.

Thorsten, could you please clarify which approach you think will better
suits your needs?

Lorenzo

Bug#973315: dwww doesnt decompress documentation files

[Robert Luberda]

Calum McConnell writes:

> 
> However, DWWW wanted to download the Gziped readme.md I pointed it to.  Is 
> there
> any way that can be changed, so that it gets decompressed and then served?

The issue is related to files in a markdown format only, so I've
retitled the bug already. I'll add a work-around for it in next dwww
upload to treat markdown files as plain text files

> For instance, .gz extensions could be decompressed,

They are already. However the markdown file was sent as 'text/markdown',
and your browser did not know how to handle it.

> .md fed through kramdown (if > its installed), ect.

I'll work on providing better support next year.

Regards,
Robert

Bug#963680: dwww: Coding error setting $mime_charset

[Robert Luberda]

Howard Johnson writes:
> 
> Starts at line 504 in dwww-convert:
> 
> $mime_charset="UTF-8";

It was $mime_charset="ISO-8859-1" originally, and the code following it
had much more sense than.

Thanks for noticing it.

Regards,
Robert

Bug#946617: dwww: runman prints empty content

[Robert Luberda]

Chad Wallace writes:

Hi,

> Dear Maintainer,
> 
> After upgrading to buster, I failed to get any man pages showing in my
> dwww output.  The  tag is completely empty.
> 
> After editing dwww-convert for debugging, I found an error from man:
> man: nroff: Bad system call
> 
> Then, I found an example of that on another bug report, which led me to
> add a line to dwww-convert:
> 
> ...begin patch
> --- dwww-convert.orig 2019-12-11 14:51:25.131093890 -0800
> +++ dwww-convert  2019-12-11 15:14:02.625790098 -0800
> @@ -246,6 +246,7 @@
>  $dir =~ s/\/[^\/]*$//;
>  chdir ("$dir/..") or die "Can't chdir!\n";
>  $ENV{'MAN_KEEP_FORMATTING'} = 1;
> +$ENV{'MAN_DISABLE_SECCOMP'} = 1;
>  my $IN_FH = ("man  -EUTF-8 -P/bin/cat  -l \"$filename\" 
> 2>/dev/null | dwww-txt2html --man --utf8", "r");
>  chdir ("/");
>  while (<$IN_FH>) {
> ...end patch
> 
> That got it working... but I don't really know why. :-)

I cannot reproduce the issue myself, even after downgrading man-db to
2.8.5-2. The bug is almost a year old, can you still reproduce it yourself?

Anyway I am not sure if setting MAN_DISABLE_SECCOMP inside dwww would be
a good idea, as according to NEWS file in man-db sources, it would hide
issues which man-db wants to be notified about:

* Confine most subprocesses that handle untrusted data using
  seccomp.  This mainly deals with subprocesses that perform
  encoding conversions, (de)compressors, groff programs, and a few
  other odds and ends.  groff programs use a slightly more
  permissive filter since they need to create temporary files, so
  additional path-based confinement (e.g. using AppArmor) is still
  useful.

  If this goes wrong, then MAN_DISABLE_SECCOMP=1 can be set in the
  environment to disable it, but please report any such problem as a
  bug.

I'm adding Collin for confirmation that the above is still valid, and
for a piece of advice what should I do with this bug report.


Regards,
Robert

Bug#689528: please add virtio support for cdrom at install time

[John Paul Adrian Glaubitz]

On 12/21/20 11:10 PM, Witold Baryluk wrote:
> FYI. This happens on both alpha and arm64 from my tests. So possibly
> more architectures are affected if it is arch specific.

The virtio driver isn't arch-specific.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#977853: proftpd-core: Fails to set up

[Hilmar Preusse]

Package: proftpd-core
Version: 1.3.7a+dfsg-4
Severity: important

Dear Maintainer,

I upgraded from -3 to -4 and now the postinst script fails to run:

Setting up proftpd-core (1.3.7a+dfsg-4) ...
usage: sftp [-46AaCfNpqrv] [-B buffer_size] [-b batchfile] [-c cipher]
  [-D sftp_server_path] [-F ssh_config] [-i identity_file]
  [-J destination] [-l limit] [-o ssh_option] [-P port]
  [-R num_requests] [-S program] [-s subsystem | sftp_server]
  destination
dpkg: error processing package proftpd-core (--configure):
 installed proftpd-core package post-installation script subprocess returned 
error exit status 1
Setting up fonts-lato (2.0-2.1) ...
dpkg: dependency problems prevent configuration of proftpd-dev:
 proftpd-dev depends on proftpd-core (= 1.3.7a+dfsg-4); however:
  Package proftpd-core is not configured yet.

Not sure, why there is a call to sftp client in the postins script.

Hilmar
-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 5.9.0-5-686-pae (SMP w/2 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages proftpd-core depends on:
ii  adduser3.118
ii  debianutils4.11.2
ii  libacl12.2.53-8
ii  libc6  2.31-6
ii  libcap21:2.44-1
ii  libcrypt1  1:4.4.17-1
ii  libhiredis0.14 0.14.1-1
ii  libmemcached11 1.0.18-4.2
ii  libmemcachedutil2  1.0.18-4.2
ii  libncursesw6   6.2+20201114-1
ii  libpam-runtime 1.3.1-5
ii  libpam0g   1.3.1-5
ii  libpcre3   2:8.39-13
ii  libssl1.1  1.1.1i-1
ii  libtinfo6  6.2+20201114-1
ii  lsb-base   11.1.0
ii  netbase6.2
ii  sed4.7-1
ii  ucf3.0043
ii  zlib1g 1:1.2.11.dfsg-2

Versions of packages proftpd-core recommends:
pn  proftpd-doc  

Versions of packages proftpd-core suggests:
ii  openbsd-inetd [inet-superserver]  0.20160825-5
ii  openssl   1.1.1i-1
iu  proftpd-mod-crypto1.3.7a+dfsg-4
pn  proftpd-mod-geoip 
pn  proftpd-mod-ldap  
pn  proftpd-mod-mysql 
pn  proftpd-mod-odbc  
pn  proftpd-mod-pgsql 
pn  proftpd-mod-snmp  
pn  proftpd-mod-sqlite
iu  proftpd-mod-wrap  1.3.7a+dfsg-4

-- no debconf information

Bug#689528: please add virtio support for cdrom at install time

[Witold Baryluk]

FYI. This happens on both alpha and arm64 from my tests. So possibly
more architectures are affected if it is arch specific.

On Mon, 21 Dec 2020 at 21:52, John Paul Adrian Glaubitz
 wrote:
>
> On 12/21/20 10:42 PM, Witold Baryluk wrote:
> > The device is there and supported by kernel, I can mount things manually
> > (i.e. mount -t iso9660 /dev/vda /media), but installer simply ignores
> > this device, even if I create symlink (ln -s vda cdrom).
> >
> > The workaround to selecting driver none, and pointing to /dev/vda seems
> > still to work and only option.
> >
> > Can we get some fix in the debian installer for this?
>
> This reminds me of a similar bug we fixed in the kernel on sparc64 which
> turned out to be two missing functions in the kernel for the vio driver
> on sparc64 [1][2].
>
> So it's probably a good idea to verify first that the virtio block device
> driver behaves correctly in that sense and creates the proper mod aliases.
>
> Then debian-installer should be able to detect the CD-ROM block device 
> automatically.
>
> Adrian
>
> > [1] 
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=36128d204b81c099b5779771127a5546eac549c9
> > [2] 
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5bde2c9be701c4583f0a9243bd46590ec401bfba
>
> --
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
>

Bug#977851: gtk: AttributeError: 'BugPage' object has no attribute 'isAlive' in gtk_ui.py, 435, pulse

[Nis Martensen]

control: reassign -1 python3-reportbug
control: forcemerge 975398 -1

Bug#975480: rust-bzip2-sys: autopkgtest failure: crate directory not found: /usr/share/cargo/registry/bzip2-sys-0.1.9+1.0.8

[Daniel Kahn Gillmor]

Control: affects 975480 debcargo

On Sun 2020-11-22 19:21:45 +0100, Paul Gevers wrote:
> autopkgtest [09:47:16]: test librust-bzip2-sys-dev:
> /usr/share/cargo/bin/cargo-auto-test bzip2-sys 0.1.9+1.0.8 --all-targets
> --no-default-features
> autopkgtest [09:47:16]: test librust-bzip2-sys-dev: [---
> crate directory not found: /usr/share/cargo/registry/bzip2-sys-0.1.9+1.0.8
> autopkgtest [09:47:16]: test librust-bzip2-sys-dev: ---]

This is a bug in debcargo 2.4.3 and earlier.  in debcargo 2.4.4,
debcargo emits the debian version here, based on commit
293fb88f2156d0db6262349aa4b1c4d3a3b1186a in the debcargo repo.

Until debcargo 2.4.4 lands in unstable, i'll just work around it in
rust-bzip2-sys.

--dkg


signature.asc
Description: PGP signature

Bug#977852: redis: Enable systemd support to get Type=notify working again

[Michael Prokop]

Package: redis
Version: 5:6.0.9-1
Severity: important

Hi,

AFAICS redis versions >=6.0.3 support sd_notify() / NOTIFY_SOCKET /
READY=1 only when systemd support is explicitly enabled.

When using redis 6.0.9-1 as present in current Debian
testing/unstable with:

 [Service]
 Type=notify

... it gets stuck at `activating` and doesn't manage to start the
service at all.

I'll provide a MR once I've got a bug number.

regards
-mika-

Bug#977851: gtk: AttributeError: 'BugPage' object has no attribute 'isAlive' in gtk_ui.py, 435, pulse

[Nis Martensen]

control: forcemerge 975398 -1

On 21.12.2020 22.40, Witold Baryluk wrote:

Package: reportbug
Version: 7.8.0
Severity: normal
X-Debbugs-Cc: witold.bary...@gmail.com

When using gtk interace, and viewing the existing bug, I got this:

Traceback (most recent call last):
   File "/usr/lib/python3/dist-packages/reportbug/ui/gtk_ui.py", line 435, in 
pulse
 return self.isAlive()
AttributeError: 'BugPage' object has no attribute 'isAlive'



fix is pending upload, coming soon

Bug#689528: please add virtio support for cdrom at install time

[John Paul Adrian Glaubitz]

On 12/21/20 10:42 PM, Witold Baryluk wrote:
> The device is there and supported by kernel, I can mount things manually
> (i.e. mount -t iso9660 /dev/vda /media), but installer simply ignores
> this device, even if I create symlink (ln -s vda cdrom).
> 
> The workaround to selecting driver none, and pointing to /dev/vda seems
> still to work and only option.
> 
> Can we get some fix in the debian installer for this?

This reminds me of a similar bug we fixed in the kernel on sparc64 which
turned out to be two missing functions in the kernel for the vio driver
on sparc64 [1][2].

So it's probably a good idea to verify first that the virtio block device
driver behaves correctly in that sense and creates the proper mod aliases.

Then debian-installer should be able to detect the CD-ROM block device 
automatically.

Adrian

> [1] 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=36128d204b81c099b5779771127a5546eac549c9
> [2] 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5bde2c9be701c4583f0a9243bd46590ec401bfba

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#934242: crystalhd: unusable without (available and properly working) firmware

[Paul Gevers]

Hi Jonas,

[Release Team member watching]

On Thu, 08 Aug 2019 17:37:35 +0200 Jonas Smedegaard  wrote:
> Source: crystalhd
> Version: 1:0.0~git20110715.fdd2f19-1
> Severity: grave
> Justification: renders package unusable
>
> It seems that libcrystalhd3 is only really useful together with
> firmware-crystalhd, which was never really usable in Debian, leading to
> that package being dropped: https://bugs.debian.org/865978
> 
> If someone wants to revive CrystalHD in Debian, it seems a good place to
> start is https://www.mythtv.org/wiki/Broadcom_Crystal_HD#Feb._2014_Update

Can you elaborate a bit? The package has a huge popcon (hence it's not
autoremoved). You're saying that all those people had it installed in
vain? Or is that due to a (past) library dependency and didn't it
actually add anything?

elbrus@coccia:~$ dak rm --no-action -R  --suite testing crystalhd
Will remove the following packages from testing:

 crystalhd | 1:0.0~git20110715.fdd2f19-13 | source
gstreamer1.0-crystalhd | 1:0.0~git20110715.fdd2f19-13 | amd64, i386
libcrystalhd-dev | 1:0.0~git20110715.fdd2f19-13 | amd64, i386
libcrystalhd3 | 1:0.0~git20110715.fdd2f19-13 | amd64, i386

Maintainer: Debian Multimedia Maintainers


--- Reason ---

--

Checking reverse dependencies...
# Broken Depends:
kylin-video: kylin-video [amd64 i386]

# Broken Build-Depends:
kylin-video: libcrystalhd-dev

Dependency problem found.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#940821: linux-image-5.2.0-2-amd64: file cache corruption with nfs4

[Salvatore Bonaccorso]

Control: tags -1 + moreinfo

Hi Anton,

On Fri, Sep 20, 2019 at 11:09:29AM +0100, Anton Ivanov wrote:
> Package: src:linux
> Version: 5.2.9-2
> Severity: critical
> Justification: breaks unrelated software
> 
> Dear Maintainer,
> 
> NFSv4 caching is completely broken on SMP.
> 
> How to reproduce:
> 
> Option 1. clone openwrt, run while make clean && make -j `nproc` ; do true ; 
> done
> 
> It will break depending on number of CPUs within several runs. 
> 
> Symptoms of breakage. A directory on the client looks empty. Example (mnt is 
> an NFSv4 mount):
> 
> ls -laF 
> /mnt/src/openwrt/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/linux-4.14.125/arch/mips/include/generated/uapi/asm
> total 8
> drwxr-xr-x 2 anivanov anivanov 4096 Sep 20 10:51 ./
> drwxr-xr-x 3 anivanov anivanov 4096 Sep 20 10:51 ../
> 
> While it actually has a file in it (same on server):
> 
> ls -laF 
> /exports/work/src/openwrt/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/linux-4.14.125/arch/mips/include/generated/uapi/asm
> total 12
> drwxr-xr-x 2 anivanov anivanov 4096 Sep 20 10:51 ./
> drwxr-xr-x 3 anivanov anivanov 4096 Sep 20 10:51 ../
> -rw-r--r-- 1 anivanov anivanov   32 Sep 20 10:51 ipcbuf.h
> 
> This cache entry on the client does not expire as it should per the NFSv4 
> caching documentation - the only way of dealing with it is reboot, unmount or 
> caches drop.
> 
> Option 2. Have your $HOME on nfsv4 and use thunderbird. Move mails between 
> folders. Sooner or later (usually sooner) you will lose an email.
> 
> So this is both "breaks unrelated software" and "data loss" depending on what 
> you are doing.
> 
> Tested on:
> 
> AMD Ryzen 5 2400G, AMD Ryzen 5 1600X, AMD Ryzen 5 1600, AMD A8-6500
> 
> Shows up on all. Fastest on the 6 core 12 thread ryzens, slowest on the AMD 
> A8 (takes up to 3 iterations of make there).

Looks that noone so far was able to either confirm or pinpoint the
issue otherwise (neither here nor upstream).

Are you still able to reproduce the issue with recent kernel versions?

Regards,
Salvatore

Bug#689528: please add virtio support for cdrom at install time

[Witold Baryluk]

Package: debian-installer
Followup-For: Bug #689528
X-Debbugs-Cc: witold.bary...@gmail.com



Hi,

this is still broken with recent debian installer daily snapshots.

The device is there and supported by kernel, I can mount things manually
(i.e. mount -t iso9660 /dev/vda /media), but installer simply ignores
this device, even if I create symlink (ln -s vda cdrom).

The workaround to selecting driver none, and pointing to /dev/vda seems
still to work and only option.

Can we get some fix in the debian installer for this?

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

Kernel: Linux 5.9.0-4-amd64 (SMP w/32 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#977851: gtk: AttributeError: 'BugPage' object has no attribute 'isAlive' in gtk_ui.py, 435, pulse

[Witold Baryluk]

Package: reportbug
Version: 7.8.0
Severity: normal
X-Debbugs-Cc: witold.bary...@gmail.com

When using gtk interace, and viewing the existing bug, I got this:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/reportbug/ui/gtk_ui.py", line 435, in 
pulse
return self.isAlive()
AttributeError: 'BugPage' object has no attribute 'isAlive'



-- Package-specific info:
** Environment settings:
INTERFACE="text"

** /home/user/.reportbugrc:
reportbug_version "7.8.0"
mode standard
ui text
realname "Witold Baryluk"
email "witold.bary...@gmail.com"
no-cc
list-cc-me
smtphost reportbug.debian.org

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

Kernel: Linux 5.9.0-4-amd64 (SMP w/32 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages reportbug depends on:
ii  apt2.1.14
ii  python33.9.0-4
ii  python3-reportbug  7.8.0
ii  sensible-utils 0.0.12+nmu1

reportbug recommends no packages.

Versions of packages reportbug suggests:
ii  claws-mail 3.17.8-1+b1
pn  debconf-utils  
ii  debsums3.0.1
pn  dlocate
ii  emacs-bin-common   1:27.1+1-3
ii  exim4-daemon-light [mail-transport-agent]  4.94-10
ii  file   1:5.39-3
ii  gnupg  2.2.20-1
ii  python3-urwid  2.1.2-1
pn  reportbug-gtk  
ii  xdg-utils  1.1.3-2

Versions of packages python3-reportbug depends on:
ii  apt2.1.14
ii  file   1:5.39-3
ii  python33.9.0-4
ii  python3-apt2.1.7
ii  python3-debian 0.1.39
ii  python3-debianbts  3.1.0
ii  python3-requests   2.25.0+dfsg-1
ii  sensible-utils 0.0.12+nmu1

python3-reportbug suggests no packages.

-- no debconf information

Bug#977850: RFS: pylev/1.2.0-1 [ITP] -- pure Python Levenshtein implementation

[Emmanuel Arias]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-pyt...@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "pylev":

 * Package name: pylev
   Version : 1.2.0-1
   Upstream Author : Daniel Lindsley 
 * URL : https://github.com/toastdriven/pylev
 * License : BSD-3-Clause
 * Vcs : https://salsa.debian.org/python-team/packages/pylev
   Section : python

It builds those binary packages:

  python3-pylev - pure Python Levenshtein implementation

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/pylev/

Alternatively, one can download the package with dget using this command:

  dget -x
https://mentors.debian.net/debian/pool/main/p/pylev/pylev_1.2.0-1.dsc

Changes for the initial release:

 pylev (1.2.0-1) unstable; urgency=medium
 .
   * Initial release (Closes: #977846).

Regards,
-- 
  Emmanuel Arias

Bug#917288: tidy reports "not a file" for existing file

[Thomas Dickey]

On Wed, Dec 26, 2018 at 07:12:09AM -0500, Thomas Dickey wrote:
> On Wed, Dec 26, 2018 at 06:41:08AM -0500, Thomas Dickey wrote:
> > On Wed, Dec 26, 2018 at 12:55:01PM +0800, Boyuan Yang wrote:
> > > Control: tag -1 + moreinfo unreproducible
> > > 
> > > Hi Thomas,
> > > 
> > > I made some test and could not reproduce your problem on my laptop.

I provided more information, without getting a response.
 
> The file is readonly - that seems to be where tidy's breaking.
> 
> (if it now requires that input files are writable,
> that's a serious regression).

Since Debian 11's "soon", I started upgrading my development machines,
which makes this bug impact me directly.

There's a workaround, e.g., changing

tidy foo.html

to

tidy < foo.html

which requires (for me) a change to a few dozen scripts.

The same problem has been reported more than once, and it seems that
the upstream isn't responsive:

https://github.com/htacg/tidy-html5/issues/681

https://github.com/htacg/tidy-html5/issues/789

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: PGP signature

Bug#977849: RFP: wire-desktop -- open source secure messenger / collaboration tool

[Ferdinand Rau]

Package: wnpp
Severity: wishlist

Wire-desktop is the desktop port of the open source secure messenger "wire" 
(developed primarily by Wire Swiss GmbH).
Wire can be used for chat, file exchange, audio & video calls, conferences with 
screen sharing, etc.
According to their own marketing speech, wire is "the most secure collaboration 
platform" for individuals and companies: https://wire.com/en/
Wire has some advanced features, like temporary messages or chat bots, but 
basically it provides the same functionality as the major popular proprietary 
instant messengers.

Source code (licensed GPL v3, except for the logo) available on GitHub: 
https://github.com/wireapp/wire-desktop

Note that the app is useful only in conjunction with an appropriate server. 
Wire Swiss provides a public, free server (free as in free beer). From the DFSG 
point of view, it might not be viable to deliver the software with the Wire 
Swiss GmbH server pre-selected, though, because several legal and technical 
restrictions apply for "third party apps" using their logo and/or server, see 
https://wire.com/en/legal/#licenses

Of course, wire-desktop could be put into non-free entirely. Alternatively, it 
might be advisable to package the server as well ( 
https://github.com/wireapp/wire-server ) and let the user choose which network 
to connect to: Their own (free) or the Wire Swiss network (restrictions apply, 
the user has to consent).

Bug#921284: build-using should only include copylefted files

[Paul Gevers]

Control: severity -1 important

Hi,

On Wed, 06 Feb 2019 10:04:16 -0500 Antoine Beaupré 
wrote:
> It should be noted this is a SHOULD NOT and not a MUST NOT, so it's a
> little more relaxed

Hence I downgrade the severity. I still like this to get fixed to avoid
the unnecessary copies kept around in the archive and the unnecessary
amount of rebuilds we'll do before the release (to avoid as much as
possible copies in the stable release).

Paul




OpenPGP_signature
Description: OpenPGP digital signature

Bug#977848: libfprint: FTBFS on mips*

[Sebastian Ramacher]

Source: libfprint
Version: 1:1.90.6-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

libfprint fails to build on mipsel and mips64el:
| Summary of Failures:
|
|  5/16 libfprint:drivers / aes3500 
FAIL   0.62s (exit status 1)
|  6/16 libfprint:drivers / elan
FAIL   0.52s (exit status 1)
|  7/16 libfprint:drivers / synaptics   
FAIL   0.47s (exit status 1)
|  8/16 libfprint:drivers / vfs0050 
FAIL   0.52s (exit status 1)
|  9/16 libfprint:drivers / vfs301  
FAIL   0.52s (exit status 1)
| 10/16 libfprint:drivers / vfs5011 
FAIL   0.47s (exit status 1)
| 11/16 libfprint:drivers / goodixmoc   
FAIL   0.47s (exit status 1)
|
| Ok: 9   
| Expected Fail:  0   
| Fail:   7   
| Unexpected Pass:0   
| Skipped:0   
| Timeout:0   
| dh_auto_test: error: cd obj-mips64el-linux-gnuabi64 && LC_ALL=C.UTF-8 
MESON_TESTTHREADS=4 meson test -C /<>/obj-mips64el-linux-gnuabi64 
--timeout-multiplier 5 returned exit code 7

See
https://buildd.debian.org/status/fetch.php?pkg=libfprint=mipsel=1%3A1.90.6-2=1607673484=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#977814: closing 977814

[Gianfranco Costamagna]

control: reopen -1
control: notifxed -1 1.8-2

Reopening since the failure is not fixed.

G.

Bug#977779: geary FTBFS on mipsel: test suite failure

[Adrian Bunk]

On Mon, Dec 21, 2020 at 01:58:32PM +0100, Alberto Garcia wrote:
> On Sun, Dec 20, 2020 at 09:09:17PM +0200, Adrian Bunk wrote:
> > > Source: geary
> > > Version: 3.38.1-1
> 
> > > The latest version of geary fails to build on mipsel [1]. The test
> > > suite fails.
> > 
> > This is not specific to geary and not specific to this version of
> > geary, the search is already ongoing for the regression that makes
> > webkit2gtk and some rdeps FTBFS on some buildds on mipsel.
> 
> I see that the build eventually succeeded:
> 
>
> https://buildd.debian.org/status/logs.php?pkg=geary=3.38.1-1=mipsel
> 
> The webkit2gtk build is flaky itself in mipsel, we discussed this
> already in the past (#962616), I wonder if this is the same root
> problem?

This is the same problem.

Note that the build is not and never was flaky,
it does 100% determinisitically fail on Loongson
buildds and succeed on Octeon buildds.

Jiaxun Yang discovered this weekend that CeilingOnPageSize is wrong for 
Loongson which has 16 kB pagesize and this matches when the problems 
started in 2.28.1, but unfortunately fixing this does not seem to fix 
all problems.

> Berto

cu
Adrian

Bug#810890: caddy in Debian, git repo at Salsa created

[Geert Stappers]

On Sun, Dec 20, 2020 at 10:33:26PM -0600, Stephen Gelman wrote:
> On Dec 20, 2020, at 8:48 PM, Geert Stappers  wrote:
> > 
> > Hello Debian Go  People,
> > Hello Debian Go  People with create privilege at Salsa,
> > 
> > 
> > Please create git repo 
> > https://salsa.debian.org/go-team/packages/golang-github-caddyserver
> > in addition to 
> > https://salsa.debian.org/go-team/packages/golang-github-caddyserver-certmagic
> > 
> > It is for packaging Caddy.
> > ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810890 )
> > 
> Geert,
> 
> You should be able to create the repos with “dh-make-golang 
> create-salsa-project”
> 
> Stephen
 

Challenge accepted  :-)


stappers@trancilo:~
$ which dh-make-golang
stappers@trancilo:~
$ sudo apt install dh-make-golang
 ...
Bezig met uitpakken van dh-make-golang (0.4.0-1) ...
Instellen van dh-make-golang (0.4.0-1) ...
Bezig met afhandelen van triggers voor man-db (2.9.3-2) ...
 ...
stappers@trancilo:~
$ which dh-make-golang
/usr/bin/dh-make-golang
stappers@trancilo:~
$ 

# reading manual page

stappers@trancilo:~
$ dh-make-golang create-salsa-project golang-github-caddyserver-caddy
stappers@trancilo:~
$ echo $?
0
stappers@trancilo:~
$ 



Yes, there is now 
https://salsa.debian.org/go-team/packages/golang-github-caddyserver-caddy



Regards
Geert Stappers
-- 
What was the last time you did something for the first time?


signature.asc
Description: PGP signature

Bug#977832: fai-setup-storage: setup-storage fails if old disk setup contains a VG with plus sign in its name

[Michael Schaller]

Package: fai-setup-storage
Version: 5.9.4
Severity: normal

Dear Maintainer,

setup-storage fails to setup a disk if the disk already contains a VG with a 
plus sign in its name.

Minimized disk setup that causes the issue:
```
$ parted --script /dev/loop0 print free
Model: Loopback device (loopback)
Disk /dev/loop2: 128MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   EndSize   File system  Name Flags
 1  17.4kB  128MB  128MB   primary  lvm

$ lsblk /dev/loop0
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop27:20 122.1M  0 loop 
└─loop2p1  259:70   122M  0 part 
  └─old_vg-a+b 253:50   120M  0 lvm  
```



Minimized disk config that reproduces the issue:
```
disk_config disk1 disklabel:gpt
primary - 0- - -
disk_config lvm
```

The setup-storage error message I get for this combination:
```
Cannot satisfy pre-depends for lvremove -f /dev/old_vg/a+b: wipefs_old_vg/a+b 
-- system left untouched.
```

The impact is that setup-storage can't resetup the disk.
If I remove the `+` from `a+b` then the issue doesn't happen.
If I remove the `disk_config lvm` line then the issue doesn't happen.
We've encountered this issue with existing machines that have been previously 
installed with Debian Installer.

Best,

Michael Schaller


setup-storage debug output:
```
disklist: loop0
Starting setup-storage 2.3
Using config file: 
Input was:
disk_config disk1 disklabel:gpt
primary - 0- - -
disk_config lvm
(CMD) parted -s /dev/loop0 unit TiB print 1> /tmp/DawnyWaUqw 2> /tmp/1CdIC7E2lZ
Executing: parted -s /dev/loop0 unit TiB print
(STDOUT) Model: Loopback device (loopback)
(STDOUT) Disk /dev/loop0: 0.00TiB
(STDOUT) Sector size (logical/physical): 512B/512B
(STDOUT) Partition Table: gpt
(STDOUT) Disk Flags: 
(STDOUT) 
(STDOUT) Number  StartEnd  Size File system  Name Flags
(STDOUT)  1  0.00TiB  0.00TiB  0.00TiB   primary  lvm
(STDOUT) 
(CMD) parted -s /dev/loop0 unit B print free 1> /tmp/6y8bZKl8j9 2> 
/tmp/cRw5eJZBPo
Executing: parted -s /dev/loop0 unit B print free
(STDOUT) Model: Loopback device (loopback)
(STDOUT) Disk /dev/loop0: 12800B
(STDOUT) Sector size (logical/physical): 512B/512B
(STDOUT) Partition Table: gpt
(STDOUT) Disk Flags: 
(STDOUT) 
(STDOUT) Number  Start   End SizeFile system  Name Flags
(STDOUT)  1  17408B  127983103B  127965696B   primary  lvm
(STDOUT) 
(CMD) parted -s /dev/loop0 unit chs print free 1> /tmp/JpcgqNuRbJ 2> 
/tmp/fAQl87C8ra
Executing: parted -s /dev/loop0 unit chs print free
(STDOUT) Model: Loopback device (loopback)
(STDOUT) Disk /dev/loop0: 490,49,1
(STDOUT) Sector size (logical/physical): 512B/512B
(STDOUT) BIOS cylinder,head,sector geometry: 490,255,2.  Each cylinder is 261kB.
(STDOUT) Partition Table: gpt
(STDOUT) Disk Flags: 
(STDOUT) 
(STDOUT) Number  Start   End   File system  Name Flags
(STDOUT)  1  0,17,0  490,33,0   primary  lvm
(STDOUT) 
Ignoring volume group: dhcp-100-105-1-216-vg
Current disk layout in %current_config
$VAR1 = {
  '/dev/loop0' => {
'sector_size' => '512',
'bios_sectors_per_track' => '2',
'size' => '12800',
'partitions' => {
  '1' => {
   'flags' => 'lvm',
   'filesystem' => '',
   'count_byte' => 
'127965696',
   'is_extended' => 0,
   'begin_byte' => '17408',
   'end_byte' => '127983103'
 }
},
'begin_byte' => 0,
'bios_cylinders' => '490',
'bios_heads' => '255',
'disklabel' => 'gpt',
'end_byte' => 12799
  }
};
Current LVM layout in %current_lvm_config
$VAR1 = {
  'old_vg' => {
'physical_volumes' => [
'/dev/loop0p1'
  ],
'size' => '120.000839233398',
'volumes' => {
   'a+b' => {
  'size' => '120.000839233398'
}
 }
  }
};
Current RAID layout in %current_raid_config
$VAR1 = {};
Current device tree in %current_dev_children
$VAR1 = {
  'VG_old_vg' => [

Bug#969352: dh-python: pybuild flit: build path included in RECORD file (makes build non reproducible)

[Philip Rinn]

Hi,

I think I found a solution, I created a MR on salsa:

https://salsa.debian.org/python-team/tools/dh-python/-/merge_requests/17

Best regards
Philip

Bug#941867: qt-gstreamer FTBFS: error: invalid cast from type ‘const CapsPtr’ to type ‘GstMiniObject*’

[Paul Gevers]

Dear all,

On Sun, 6 Oct 2019 23:12:00 +0200 Helmut Grohne  wrote:
> qt-gstreamer fails to build from source in unstable on amd64. A build in
> sbuild ends with:

The reproducibility rebuilds [1] show this happening on all their
architectures. The bullseye freeze is drawing near. Can this bug please
be looked into soon?

Paul

[1]
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/qt-gstreamer.html



OpenPGP_signature
Description: OpenPGP digital signature

Bug#977831: www.debian.org: Recommends bittorrent but Unstable/Testing no longer provide it

[Helge Kreutzmann]

Hello James,
On Mon, Dec 21, 2020 at 08:11:06PM +, James Frost wrote:
> Some major BitTorrent clients now days are Deluge, qbittorrent, and
> Transmission, all of which are packaged in sid, and both deluge and
> transmission have CLI only versions. They are also all cross platform for
> people looking to download Debian on Windows or MacOS.
> 
> It is probably also worth considering tools like aria2, which provides a
> wget like interface for downloading of single files.
> 
> It would also not be amiss to move the latest BitTorrent files directly onto
> https://www.debian.org/distrib/ to improve there visibility.

Thanks for your overview. Then the "easy" fix is to simply update the
web page. Then peoply like me who haven't had any contact with those
clients know where to look (which to apt-get).

Thanks for your research.

Greetings

Helge

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#977847: RFS: meterec/0.9.3-1 [QA] -- minimalistic multi track recorder

[Leandro Cunha]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "meterec":

 * Package name: meterec
   Version : 0.9.3-1
   Upstream Author : Fabrice Lebas 
 * URL : http://meterec.sourceforge.net/
 * License : GPL-2+
 * Vcs : [fill in URL of packaging vcs]
   Section : sound

It builds those binary packages:

  meterec - minimalistic multi track recorder

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/meterec/

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/m/meterec/meterec_0.9.3-1.dsc

Changes since the last upload:

 meterec (0.9.3-1) unstable; urgency=medium
 .
   * QA upload.
   * New upstream release.
   * Updated gbp.conf to default configuration.
   * debian/control:
 - Bumped Standards-Version to 4.5.1.
   * Deleted files to repack.
   * debian/docs:
 - Added AUTHORS.
   * debian/watch:
 - Removed opts.
   * debian/copyright:
 - Added myself.
   * debian/tests:
 - Added control to autopkgtest.
   * Added salsa-ci.yml.
   * debian/upstream:
 - Remove obsolete field Name from d/u/metadata.

[1] https://salsa.debian.org/leandrocunha/meterec
[2] https://tracker.debian.org/pkg/meterec

Regards,
-- 
  Leandro Cunha

Bug#929685: ca-certificates-java,default-jre-headless,openjdk-11-jre-headless: get rid of the circular dependency

[Paul Gevers]

Hi all,

On Mon, 17 Jun 2019 14:20:43 +0200 Andreas Beckmann  wrote:
> I looked into this again and would suggest to demote the
>   ca-certificates-java -> default-jre-headless
> dependency to a recommends.
> ca-certificates-java will have to gracefully handle the case that no JRE
> is available at all and that one becomes available later.

Any objections to the patch of Andreas? If not, I propose to proceed to
fix this issue now, and still have some time before the bullseye release
to fix corner case issues caused by the fix.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#977846: ITP: pylev -- pure Python Levenshtein implementation

[Emmanuel Arias]

Package: wnpp
Severity: wishlist
Owner: Emmanuel Arias 
X-Debbugs-Cc: debian-pyt...@lists.debian.org

* Package name: pylev
  Version : 1.3.0
  Upstream Author : Daniel Lindsley 
* URL : https://github.com/toastdriven/pylev
* License : BSD-3-Clause
  Programming Lang: Python
  Description :  pure Python Levenshtein implementation

A pure Python Levenshtein implementation that's not freaking GPL'd.
Based off the Wikipedia code samples at
http://en.wikipedia.org/wiki/Levenshtein_distance.
.
This is a dependency of clickit.
.
This package is needed for poetry packaging.
.
This package will be maintained as part of the Debian Python modules team.

Cheers,
Emmanuel

Bug#977829: libzstd: Regression in 1.4.5

[Andreas Tille]

Hi Guillem,

On Mon, Dec 21, 2020 at 04:29:25PM +0100, Guillem Jover wrote:
> Source: libzstd
> Version: 1.4.5+dfsg-4
> Severity: important
> Tags: fixed-upstream
> Forwarded: https://github.com/facebook/zstd/issues/
> 
> Hi!
> 
> There's a regression in the 1.4.5 release that is affecting several
> other projects that use libzstd.
> 
> This has been reported and fixed in the latest upstream release 1.4.8,
> so updating to that should fix the issue.

I really wonder whether we could make a different team than Debian Med
the maintainer of this package.  Its definitely not in the best hands
currently.  Any NMU / Team upload is perfectly fine in any case.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#976960: systemd: Please package systemd-userdbd and systemd-homed

[Jörg Behrmann]

Thank you for your response!

On Mon, Dec 21, 2020 at 06:22:04PM +0100, Michael Biebl wrote:
> I still fail to see the use-case for homed, tbh and the current
> implementation still requires quite a few hacks (see the fosdem 2020
> talk of Lennart and the problems e.g. with SSH keys).
> 
> Atm this appears more like a tech-preview/demo and I don't feel
> comfortable yet supporting it.
> This can be reconsidered in bookworm.
> 

While this is true, for the part that Lennart gave talks about, I've been using
homed with the btrfs backend on Arch machine as a daily driver for a while and I
think the cifs backend could be interesting for multi-user setups, e.g. in
universities.


signature.asc
Description: PGP signature

Bug#977831: www.debian.org: Recommends bittorrent but Unstable/Testing no longer provide it

[James Frost]

Some major BitTorrent clients now days are Deluge, qbittorrent, and 
Transmission, all of which are packaged in sid, and both deluge and 
transmission have CLI only versions. They are also all cross platform 
for people looking to download Debian on Windows or MacOS.


It is probably also worth considering tools like aria2, which provides a 
wget like interface for downloading of single files.


It would also not be amiss to move the latest BitTorrent files directly 
onto https://www.debian.org/distrib/ to improve there visibility.


On 21/12/2020 17:15, Helge Kreutzmann wrote:

Package: www.debian.org
Severity: normal

I wanted to download an CD image on my Testing system. I went to
www.debian.org, namely https://www.debian.org/distrib/. There I was
recommended to use the bittorrent image (previously I remember jigdo
or something simliar was used).

On the dedicated download page
https://www.debian.org/CD/torrent-cd/index.en.html the following is
written:

You will need a BitTorrent client to download Debian CD/DVD images
this way. The Debian distribution includes BitTornado, KTorrent and
the original BitTorrent tools.

However, this is not true. BitTornado and the original BitTorrent
tools have been removed over a year ago from Sid (und Testing).
Requiring to install KDE just to download an image is a bit too much,
in my opinion.

So the text needs to be updated but more importantly a lightweight
toolset to download needs to be determined which is available in
Debian, preferrably on the command line for easier handling.

(And sharing bandwith is a good idea, I'm willing to support this when
I can).


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

Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.UTF-8), LANGUAGE not set

Bug#977845: dgit: unhelpful behavior in case previous upload contained new upstream release

[Paul Gevers]

Package: dgit
Version: 9.12
Severity: normal

Hi,

As discussed on IRC, I had a slightly bad experience using dgit to
prepare an NMU for f2fs-tools.

paul@mulciber ~/packages/bugs $ dgit clone f2fs-tools
canonical suite name for unstable is sid
fetching existing git history
last upload to archive: NO git hash
using existing f2fs-tools_1.11.0.orig.tar.gz
using existing f2fs-tools_1.11.0-1.1.debian.tar.xz
dpkg-source: info: extracting f2fs-tools in f2fs-tools-1.11.0
dpkg-source: info: unpacking f2fs-tools_1.11.0.orig.tar.gz
dpkg-source: info: unpacking f2fs-tools_1.11.0-1.1.debian.tar.xz
synthesised git commit from .dsc 1.11.0-1.1

Version actually in archive:   1.11.0-1.1 (older)
Last version pushed with dgit: 1.12.0-1 (newer or same)
Perhaps the upload is stuck in incoming.  Using the version from git.

HEAD is now at fa204f3 Declare fast forward from 1.11.0-1.1
dgit ok: ready for work in f2fs-tools


So apparently the previous upload was done with dgit, cool Unless
that previous upload included a new upstream version and the upload went
through new and the upload was rejected...

paul@mulciber ~/packages/bugs $ cd f2fs-tools
paul@mulciber ~/packages/bugs/f2fs-tools $ dch -i "bla"
paul@mulciber ~/packages/bugs/f2fs-tools $ dch -r ""
paul@mulciber ~/packages/bugs/f2fs-tools $ git commit -m"Commit
changelog" debian/changelog
[dgit/sid 003cb83] Commit changelog
 1 file changed, 7 insertions(+)
paul@mulciber ~/packages/bugs/f2fs-tools $ dgit build-source
Format `3.0 (quilt)', need to check/update patch stack
gzip: warning: GZIP environment variable is deprecated; use an alias or
script
dgit: split brain (separate dgit view) may be needed (--quilt=unapplied).
examining quilt state (multiple patches, unapplied mode)
dpkg-source: error: missing orig.tar or debian.tar file in v2.0 source
package
dgit: failed command: sh -ec 'exec dpkg-source --no-check --skip-patches
-x fake.dsc >/dev/null'

dgit: error: subprocess failed with error exit status 255


The new upsteam tar ball is missing, and as the upload was rejected, I
don't know where to obtain that tar ball.

Once I discovered the problem (I had initially missed the "Perhaps the
upload is stuck in incoming.  Using the version from git." part), it
would have helped if it was clear to me where to start working if I
wanted to have the version in unstable.

In the end I resorted to
paul@mulciber ~/packages/bugs $ dgit clone f2fs-tools testing
as unstable and testing have the same version, but that doesn't work if
unstable and testing don't have the same version.

Paul

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

Kernel: Linux 5.9.0-4-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 dgit depends on:
ii  apt2.1.12
ii  ca-certificates20200601
ii  coreutils  8.32-4+b1
ii  curl   7.72.0-1
ii  devscripts 2.20.5
ii  dpkg-dev   1.20.5
ii  dput-ng [dput] 1.31
ii  git [git-core] 1:2.29.2-1
ii  git-buildpackage   0.9.20
ii  libdpkg-perl   1.20.5
ii  libjson-perl   4.02000-2
ii  liblist-moreutils-perl 0.430-2
ii  liblocale-gettext-perl 1.07-4+b1
ii  libtext-csv-perl   2.00-1
ii  libtext-glob-perl  0.11-1
ii  libtext-iconv-perl 1.7-7+b1
ii  libwww-curl-perl   4.17-7+b1
ii  perl [libdigest-sha-perl]  5.32.0-6

Versions of packages dgit recommends:
ii  distro-info-data 0.45
ii  liburi-perl  5.05-1
ii  openssh-client [ssh-client]  1:8.4p1-3

Versions of packages dgit suggests:
ii  cowbuilder  0.89
ii  pbuilder0.230.4

-- no debconf information



OpenPGP_signature
Description: OpenPGP digital signature

Bug#977382: qutebrowser-qtwebengine: Most devtools tabs stay blank

[Cédric Hannotier]

On 18/12/20 22:27, Fritz Reichwald wrote:
> Hi Cédric,

Hi Fritz,

> To check if the issue is qutebrowser or webengine related usually we
> suggest to try if the bug is reprodudcible with falkon (another browser
> using webengine)
> If the bug also happens in falkon its with webengine.
> Else it might be a qb bug.

There were both affected. It took time because I needed to downgrade
qtwebengine-opensource-src and qtbase-opensource-src (5.15.2 → 5.15.1).

So it was a qt bug. But it is fixed in current version of
qtwebengine-opensource-src and qtbase-opensource-src in testing.

Since it is fixed, this can be closed. Feel free to reassign it to qt.

Regards
-- 

Cédric Hannotier

Bug#977753: apertium: FTBFS on s390x: test failures

[Tino Didriksen]

Fixed in v3.7.1, both upstream and
https://salsa.debian.org/science-team/apertium

-- Tino Didriksen

Bug#977842: openconnect: Fails to save password in my VPN account

[Josh Anders]

reassign 977842 network-manager-openconnect
retitle 977842 network-manager-openconnect: Fails to save password in my VPN 
account
thanks

I've reassigned to nm-openconnect for now. If you use nm-openconnect-gnome, it 
may be their issue instead. A couple questions:

1. If you look at /etc/NetworkManager/system-connections/[your 
VPN].nmconnection (as root), you should see a section labeled [vpn-secrets]. Is 
there a line that sets save_passwords to yes?
2. Can you take some debug logs from NetworkManager/syslog while attempting to 
connect? Here's how: 
https://wiki.gnome.org/Projects/NetworkManager/Debugging#Other_NetworkManager_Debugging
 ; feel free to redact credentials etc.


Thanks,
Josh


On Mon, 21 Dec 2020 21:00:09 +0200 Pavlos Ponos  wrote:

> Package: openconnect
> Version: 8.10-1
> Severity: normal
> X-Debbugs-Cc: pavlos.po...@gmail.com
>
> Hello,
>
> This is something that used to work, but since last week it doesn't anymore.
>
> Some months ago I created a VPN connection using the 'Cisco Anyconnect' 
option. When I setup the connection I chose to store
> the username and password. This worked perfectly find until last week. Since 
then, every time I enable the VPN connection I have
> to type the password, despite the fact that the 'save passwords' option is 
enabled.
>
> If this is a 'network-manager-openconnect' issue, feel free to tag it 
differently.
>
> Thanks for checking.
> Pavlos
>
>
> -- System Information:
> Debian Release: bullseye/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.9.0-4-amd64 (SMP w/2 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 openconnect depends on:
> ii libc6 2.31-5
> ii libgnutls30 3.6.15-4
> ii libopenconnect5 8.10-1
> ii libproxy1v5 0.4.16-2
> ii libxml2 2.9.10+dfsg-6.3+b1
> ii vpnc-scripts 0.1~git20200930-1
>
> Versions of packages openconnect recommends:
> ii python3 3.9.0-4
> ii python3-asn1crypto 1.4.0-1
> ii python3-mechanize 1:0.4.5-2
> ii python3-netifaces 0.10.9-0.2+b3
>
> Versions of packages openconnect suggests:
> ii bash-completion 1:2.11-2
>
> -- no debconf information
>
>

Bug#977844: src:libcxx-serial: libcxx-serial FTBFS with new catkin (patch attached)

[Jochen Sprickerhof]

Package: src:libcxx-serial
Version: 1.2.1-4
Severity: normal
Tags: ftbfs

Hi,

I've changed catkin to install pkg-config files to /usr/share and made
them arch independent. I've attached a patch for libcxx-serial to adopt
to those changes.

I will upload a package with the attached patch to DELAYED/10. Please
tell me if I should cancel it.

Cheers Jochen


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

Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/debian/changelog b/debian/changelog
index 0d58d86..6abf8d6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+libcxx-serial (1.2.1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Adopt to catkin installing pkgconfig to share
+
+ -- Jochen Sprickerhof   Mon, 21 Dec 2020 20:38:16 +0100
+
 libcxx-serial (1.2.1-4) unstable; urgency=medium
 
   * Add missing build-deps libgmock-dev and pkg-config. Closes: #973112
diff --git a/debian/libcxx-serial-dev.install b/debian/libcxx-serial-dev.install
index a1fc515..72c088b 100644
--- a/debian/libcxx-serial-dev.install
+++ b/debian/libcxx-serial-dev.install
@@ -1,4 +1,3 @@
 usr/include/*
 usr/lib/*/lib*.so
-usr/lib/*/pkgconfig/*
-usr/share/cxx-serial
+usr/share
diff --git a/debian/rules b/debian/rules
index 00ebf56..87b46bd 100755
--- a/debian/rules
+++ b/debian/rules
@@ -8,7 +8,6 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
 override_dh_auto_configure:
dh_auto_configure -- \
-   -DPKGCONFIGDIR=/usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig \
-DCMAKE_VERBOSE_MAKEFILE=ON
 
 override_dh_auto_test:

Bug#977830: Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1

[Simon McVittie]

On Mon, 21 Dec 2020 at 19:29:19 +0100, Michael Biebl wrote:
> Indeed. While looking at this, I also noticed that e.g. tracker is started
> within the gdm session. This doesn't strike me as a good idea.
> I'm not so firm anymore, how the gdm(3) session is setup, so I'm not sure
> whether to report such issues against gdm3 or tracker.

Probably gdm3 with an X-Debbugs-Cc to tracker - if we conclude that it's
actually tracker that should change, we can reassign, but gdm3 is probably
a better coordination point.

I'm not sure how enabling/disabling services for the greeter session is
meant to work. The greeter uses /usr/share/gdm/greeter/applications and
/usr/share/gdm/greeter/autostart to customize fd.o MIME handling and
autostarted apps, but doesn't seem to have anything to restrict activation
of D-Bus services or systemd user services.

It seems inconsistent that the "user bus" is getting used at all, in fact:
I would have expected that nothing running as Debian-gdm would be seeing
it, because everything ought to be wrapped in dbus-run-session.

Perhaps this is all triggered by services that are launched "eagerly" by
`systemd --user` as part of default.target? Of those services, I think
we probably need pulseaudio (for screen readers and other a11y), but not
the rest.

smcv

Bug#977843: RM: mariadb-10.4/experimental -- RoM; obsoleted by mariadb-10.5

[Otto Kekäläinen]

Package: ftp.debian.org
Severity: normal

Hi,

Please remove src:mariadb-10.4 from experimental.

MariaDB 10.4 has been replaced by MariaDB 10.5 and 10.4 was never
uploaded to unstable. The version in experimental will never be used
and is obsolete.

Related: Bug#977254

Bug#977842: openconnect: Fails to save password in my VPN account

[Pavlos Ponos]

Package: openconnect
Version: 8.10-1
Severity: normal
X-Debbugs-Cc: pavlos.po...@gmail.com

Hello,

This is something that used to work, but since last week it doesn't anymore.

Some months ago I created a VPN connection using the 'Cisco Anyconnect' option. 
When I setup the connection I chose to store
the username and password. This worked perfectly find until last week. Since 
then, every time I enable the VPN connection I have
to type the password, despite the fact that the 'save passwords' option is 
enabled.

If this is a 'network-manager-openconnect' issue, feel free to tag it 
differently.

Thanks for checking.
Pavlos 


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

Kernel: Linux 5.9.0-4-amd64 (SMP w/2 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 openconnect depends on:
ii  libc62.31-5
ii  libgnutls30  3.6.15-4
ii  libopenconnect5  8.10-1
ii  libproxy1v5  0.4.16-2
ii  libxml2  2.9.10+dfsg-6.3+b1
ii  vpnc-scripts 0.1~git20200930-1

Versions of packages openconnect recommends:
ii  python3 3.9.0-4
ii  python3-asn1crypto  1.4.0-1
ii  python3-mechanize   1:0.4.5-2
ii  python3-netifaces   0.10.9-0.2+b3

Versions of packages openconnect suggests:
ii  bash-completion  1:2.11-2

-- no debconf information

Bug#977841: bubblewrap: needs transition to non-setuid to accompany linux/5.10.x

[Simon McVittie]

Package: bubblewrap
Version: 0.4.1-1
Severity: important
Tags: security
X-Debbugs-Cc: debian-ker...@lists.debian.org, t...@security.debian.org

bubblewrap can operate in two modes:

- User namespace (Ubuntu, Fedora, RHEL >= 8): /usr/bin/bwrap is not setuid,
  and relies on having a kernel that allows unprivileged users without
  special capabilities in the initns to create new user namespaces, with
  the initial process in the new namespace having all capabilities.

- setuid root (Debian <= 10, RHEL <= 7): /usr/bin/bwrap is setuid root
  (or setcap CAP_SYS_ADMIN, which is almost the same thing) and therefore
  does not rely on a kernel with that feature.

According to https://bugs.debian.org/898446 the kernel team's plan is for
Debian 11 defaults to behave like Ubuntu, Fedora and RHEL 8, so that bwrap
does not need to be setuid any more.

If this plan goes ahead, to reduce attack surface and prevent attacks
similar to CVE-2020-5291, we should ensure that bwrap is not normally
setuid in Debian 11 systems.

Making bwrap unnecessarily setuid will also disable some of flatpak's
features, which already breaks certain apps when installed via flatpak,
notably Chromium (see #977758).

However, some of the packages that rely on bwrap (such as flatpak
and gnome-desktop3) have a non-technical user-base that should not be
expected to understand which mode their kernel is in or manage sysctl
values themselves. If bwrap doesn't work "out of the box", then we
will get confused or angry bug reports against packages like flatpak;
I don't really have the time or patience to provide detailed technical
support for Debian 11's release lifetime, and I'm effectively the sole
maintainer of flatpak and bubblewrap in Debian (co-maintainers welcome,
by the way). So we will need to have some sort of transition plan in
which flatpak continues to work. Because the transition freeze is soon,
we should have a plan soon.

Ideally, our transition plan should work even for users who have held back
a buster kernel, at least in the short term.

Here are some possibilities:

sysctl configuration


The simplest and most robust thing would be for bubblewrap to depend on
procps, and ship a file /usr/lib/sysctl.d/50-bubblewrap.conf containing:

kernel.unprivileged_userns_clone=1

together with a brief note about how you can copy that file into
/etc/sysctl.d and edit the copy if this setting is undesired on a hardened
system, and a reference to longer-form documentation in
/usr/share/doc/bubblewrap, on the Debian wiki or on Salsa.

This would mean that installing bullseye's bubblewrap.deb causes older
kernel packages to get the more lax behaviour of newer kernel packages.
Would the kernel and security teams consider this to be acceptable?

If they would, then I think this is my preferred route.

We should also patch bwrap so that when upstream bwrap would print an
error message suggesting toggling kernel.unprivileged_userns_clone=1,
Debian's bwrap instead prints a reference to our documentation.

Split the package
=

Arch Linux has two bubblewrap packages: 'bubblewrap' is intended to be
used with their default kernel, which has the Ubuntu/Fedora-style
behaviour; 'bubblewrap-suid' is intended to be used with their non-default
linux-hardened kernel, which has the Debian 10 behaviour (via the same
patch, even). Each has a bwrap binary (functionally equivalent, I think)
with appropriate 0755 or 04755 permissions.

This relies on users installing the right bubblewrap package for their
kernel, which seems to be a regular source of confusion even on Arch,
which explicitly does not aim to support users who don't read the
(extensive) documentation. I think we should aim higher than this in
Debian.

It might be possible to set up some sort of transitional package with
something like this:

bubblewrap Depends: bubblewrap-userns | bubblewrap-setuid,
   Recommends: linux-image (>= 5.10) | bubblewrap-setuid,

but I don't see how to make that work without some versioned Provides
in kernel packages, and it still won't do the right thing if users boot
into an older kernel to work around a driver regression or similar.

chmod at boot time
==

I hesitate to say this because I think writing to /usr would be horrible,
but we could have an init script/systemd unit that chmods /usr/bin/bwrap
04755 or 0755 during boot, depending whether the running kernel appears
to allow unprivileged creation of user namespaces.

Presumably we'd want to skip this if there was a dpkg-statoverride
configured for bwrap, to avoid trampling over sysadmin configuration.

We probably shouldn't just move the bwrap binary into /var/lib, leaving
a symlink behind, because that would cause any existing dpkg-statoverride
on the bwrap binary to get applied to the symlink rather than the binary.

A wrapper
=

I briefly looked into writing a /usr/bin/bwrap wrapper that would be
setuid, detect whether its privileges were actually 

Bug#969906: snapshot.debian.org: error 500 internal server error after some requests via Python

[Stefanos Chaliasos]

Hello, 

The IPs I am using are: 131.180.178.86, 131.180.178.88, 131.180.178.92, 
131.180.178.90, 131.180.178.188, 131.180.178.200
I have noticed that after a few hundred requests (from a single IP) I get an 
internal server error.

Cheers,

Stefanos Chaliasos

On Fri, 27 Nov 2020 at 17:41, Julien Cristau mailto:jcris...@debian.org>> wrote:
Control: tag -1 moreinfo

On Thu, Sep 24, 2020 at 10:24:56AM +0300, Stefanos Chaliasos wrote:
> Hello,
> 
> Is there any update about this issue? Should I provide more information
> or doing anything else to help with resolving this issue?
> 
Yes.  Where are you connecting from, and how many requests are we
talking about?

Cheers,
Julien
> 
> On Tue, 8 Sep 2020 17:59:41 +0300 Stefanos Chaliasos 
> mailto:stefanoshalias...@gmail.com>> wrote:
> > Package: snapshot.debian.org 
> > Severity: normal
> > Tags: a11y
> >
> > Dear Maintainer,
> >
> > I am trying to download .dsc files for many packages using the Python 
> > requests
> > module with delays and retries. After some requests, the server returns 
> > Error
> > 500 internal Server error.
> >
> > I do that because I am trying to analyze Debian C projects using sbuild
> > (with some hooks that run static analysis tools). To do so, I use sbuild [1]
> > to build and analyze Debian C packages.  I want to be able to analyze any
> > package version of a package. Hence, I give .dsc files to sbuild as an
> > argument. I use snapshot.debian.org  to 
> > download those files. For example,
> > for analyzing zlib (version 1.2.11.dfsg-2) I download it's .dsc file from
> > this URL [2]. I use snapshot.debian.org  
> > because it provides all versions of
> > each package with convenient URLs
> > (https://snapshot.debian.org/package/package_name/package_version/ 
> > ),
> > whereas other websites have more complex URL schemes.
> >
> > [1] https://wiki.debian.org/sbuild 
> > [2] 
> > https://snapshot.debian.org/archive/debian-debug/20200225T025524Z/pool/main/z/zlib/zlib_1.2.11.dfsg-2.dsc
> >  
> > 
> >
> > -- System Information:
> > Debian Release: bullseye/sid
> >   APT prefers testing
> >   APT policy: (500, 'testing'), (1, 'experimental')
> > Architecture: amd64 (x86_64)
> > Foreign Architectures: i386
> >
> > Kernel: Linux 5.7.0-3-amd64 (SMP w/12 CPU threads)
> > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: 
> > LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en
> > Shell: /bin/sh linked to /usr/bin/dash
> > Init: systemd (via /run/systemd/system)
> > LSM: AppArmor: enabled
> >
> >

Bug#977840: ring-codec-clojure : jars are not installed in maven-repo

[Louis-Philippe Véronneau]

Package: src:ring-codec-clojure
Version: 1.0.0-1
Severity: important
Owner: po...@debian.org

It seems only pom files are installed in maven-repo, and not jar files.
This means we can't currently use this package as a dependency when
building with leiningen.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄




OpenPGP_signature
Description: OpenPGP digital signature

Bug#977839: crypto-random-clojure: jars are not installed in maven-repo

[Louis-Philippe Véronneau]

Package: src:crypto-random-clojure
Version: 1.2.0-1
Severity: important
Owner: po...@debian.org

It seems only pom files are installed in maven-repo, and not jar files.
This means we can't currently use this package as a dependency when
building with leiningen.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄



OpenPGP_signature
Description: OpenPGP digital signature

Bug#977838: crypto-equality-clojure: jars are not installed in maven-repo

[Louis-Philippe Véronneau]

Package: src:crypto-equality-clojure
Version: 1.0.0-1
Severity: important
Owner: po...@debian.org

It seems only pom files are installed in maven-repo, and not jar files.
This means we can't currently use this package as a dependency when
building with leiningen.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄



OpenPGP_signature
Description: OpenPGP digital signature

Bug#977830: Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1

[Michael Biebl]

Hi Simon

Am 21.12.20 um 18:48 schrieb Simon McVittie:

comm="/usr/libexec/gsd-sharing "


In an ideal world, I suspect this service shouldn't even be started in
the greeter: there's no reason why the greeter session would want to
share anything with a LAN.


Indeed. While looking at this, I also noticed that e.g. tracker is 
started within the gdm session. This doesn't strike me as a good idea.
I'm not so firm anymore, how the gdm(3) session is setup, so I'm not 
sure whether to report such issues against gdm3 or tracker.

I don't think we need the gvfs monitors in the gdm session either:

│ │ └─user@125.service»
│ │   ├─gvfs-goa-volume-monitor.service»
│ │   │ └─812 /usr/libexec/gvfs-goa-volume-monitor
│ │   ├─pulseaudio.service»
│ │   │ └─735 /usr/bin/pulseaudio --daemonize=no --log-target=journal
│ │   ├─gvfs-daemon.service»
│ │   │ ├─751 /usr/libexec/gvfsd
│ │   │ └─769 /usr/libexec/gvfsd-fuse /run/user/125/gvfs -f -o big_writes
│ │   ├─gvfs-udisks2-volume-monitor.service»
│ │   │ └─775 /usr/libexec/gvfs-udisks2-volume-monitor
│ │   ├─init.scope»
│ │   │ ├─728 /lib/systemd/systemd --user
│ │   │ └─729 (sd-pam)
│ │   ├─gvfs-gphoto2-volume-monitor.service»
│ │   │ └─801 /usr/libexec/gvfs-gphoto2-volume-monitor
│ │   ├─dbus.service»
│ │   │ ├─740 /usr/bin/dbus-daemon --session --address=systemd: --nofork 
--nopi…

│ │   │ ├─818 /usr/libexec/goa-daemon
│ │   │ └─836 /usr/libexec/goa-identity-service
│ │   ├─tracker-miner-fs.service»
│ │   │ └─737 /usr/libexec/tracker-miner-fs
│ │   ├─gvfs-mtp-volume-monitor.service»
│ │   │ └─846 /usr/libexec/gvfs-mtp-volume-monitor
│ │   └─gvfs-afc-volume-monitor.service»
│ │ └─806 /usr/libexec/gvfs-afc-volume-monitor


gnome-online-accounts in the gdm session seems unneeded as well.

Regards,
Michael




OpenPGP_signature
Description: OpenPGP digital signature

Bug#977827: rpm: uses /usr/bin/gpg2 by default

[Imre Jonk]

Package: rpm
Version: 4.14.2.1+dfsg1-1
Severity: normal

Dear Maintainer,

I tried to sign some RPM packages with rpm --addsign, but this resulted
in the following error:

`error: Could not exec gpg: No such file or directory`

The gnupg package was installed on my system, and the gpg binary was in
my PATH. The message above turned out to be a bit misleading as rpm
tries to sign using /usr/bin/gpg2 by default, instead of /usr/bin/gpg.

My temporary workaround is to add the flag
--define='%__gpg /usr/bin/gpg'. Another option is to install the gnupg2
package which just adds a symlink. I would appreciate it if you could
make rpm use the gpg binary by default.

Kind regards,

Imre Jonk


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

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

Versions of packages rpm depends on:
ii  debugedit 4.14.2.1+dfsg1-1
ii  libc6 2.28-10
ii  libelf1   0.176-1.1
ii  libpopt0  1.16-12
ii  librpm8   4.14.2.1+dfsg1-1
ii  librpmbuild8  4.14.2.1+dfsg1-1
ii  librpmio8 4.14.2.1+dfsg1-1
ii  librpmsign8   4.14.2.1+dfsg1-1
ii  perl  5.28.1-6+deb10u1
ii  rpm-common4.14.2.1+dfsg1-1
ii  rpm2cpio  4.14.2.1+dfsg1-1

rpm recommends no packages.

Versions of packages rpm suggests:
pn  alien 
pn  elfutils  
ii  python2.7.16-1
pn  rpm-i18n  
pn  rpm2html  
pn  rpmlint   

-- no debconf information

Bug#977837: RFS: fonts-sora/0+git20201221+ds-1 [ITP] -- Sora typeface

[Gürkan Myczko]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "fonts-sora":

 * Package name: fonts-sora
   Version : 0+git20201221+ds-1
   Upstream Author : The Sora Project Authors
 * URL : https://sora.org
 * License : OFL-1.1
 * Vcs : https://salsa.debian.org/fonts-team/fonts-sora
   Section : fonts

It builds those binary packages:

  fonts-sora - Sora typeface

To access further information about this package, please visit the 
following URL:


  https://mentors.debian.net/package/fonts-sora/

Alternatively, one can download the package with dget using this 
command:


  dget -x 
https://mentors.debian.net/debian/pool/main/f/fonts-sora/fonts-sora_0+git20201221+ds-1.dsc


Changes for the initial release:

 fonts-sora (0+git20201221+ds-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #977828)

Regards,
--
  Gürkan Myczko

Bug#977807: RFS: far2l/2.2+git20201201-1 [ITP] -- Linux port of FAR v2

[Fernando Toledo]

El 21/12/20 a las 05:27, Gürkan Myczko escribió:

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "far2l":

  * Package name: far2l
Version : 2.2+git20201201-1
Upstream Author : 
  * URL : https://github.com/elfmz/far2l
  * License : GPL-2+
  * Vcs : [fill in URL of packaging vcs]
Section : non-free/utils

It builds those binary packages:

   far2l - Linux port of FAR v2

To access further information about this package, please visit the
following URL:

   https://mentors.debian.net/package/far2l/

Alternatively, one can download the package with dget using this command:

   dget -x
https://mentors.debian.net/debian/pool/non-free/f/far2l/far2l_2.2+git20201201-1.dsc

Changes for the initial release:

  far2l (2.2+git20201201-1) unstable; urgency=medium
  .
* Initial release. (Closes: #977790)

Regards,


ohhh! the mc will be scared
Cool package, i hope can be upload to debian archive!

good look!


--
Fernando Toledo
Dock Sud BBS
http://bbs.docksud.com.ar
telnet://bbs.docksud.com.ar

Bug#977830: Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1

[Simon McVittie]

Control: severity -1 minor

On Mon, 21 Dec 2020 at 16:30:40 +0100, Michael Biebl wrote:
> I noticed in my journal the following error messages
> 
> Dez 21 16:22:13 pluto /usr/libexec/gdm-wayland-session[820]: 
> dbus-daemon[820]: [session uid=109 pid=820] Activating service 
> name='org.freedesktop.systemd1' requested by ':1.27' (uid=109 pid=1090 
> comm="/usr/libexec/gsd-sharing ")
> Dez 21 16:22:13 pluto /usr/libexec/gdm-wayland-session[820]: 
> dbus-daemon[820]: [session uid=109 pid=820] Activated service 
> 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited 
> with status 1
> Dez 21 16:22:13 pluto gsd-sharing[1090]: Failed to StopUnit service: 
> GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
> org.freedesktop.systemd1 exited with status 1
> Dez 21 16:22:13 pluto gsd-sharing[1090]: Failed to StopUnit service: 
> GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
> org.freedesktop.systemd1 exited with status 1
> Dez 21 16:22:13 pluto gsd-sharing[1090]: Failed to StopUnit service: 
> GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
> org.freedesktop.systemd1 exited with status 1
> 
> I wonder if this is related to #977826 and how the session is started
> within gdm.

Almost certainly. The dbus-daemon is started on a per-greeter basis
(one per X11 or Wayland display) because on multi-seat or XDMCP systems,
gdm wants to run several independent sessions all sharing one uid; so it
can't talk to `systemd --user`.

The error message is different because gsd-sharing is still trying to
perform activation via autostarting, whereas gnome-session has been taught
not to try to do that (it won't work).

Ideally these messages shouldn't appear, but I don't think they indicate
a real bug.

> comm="/usr/libexec/gsd-sharing "

In an ideal world, I suspect this service shouldn't even be started in
the greeter: there's no reason why the greeter session would want to
share anything with a LAN.

smcv

Bug#977836: plantuml: include PDF plantuml language reference manual in package

[Richard Noble]

Package: plantuml
Version: 1:1.2018.13+ds-1
Severity: minor


There is a language reference guide for plantuml in PDF format at
http://plantuml.com/guide

The manpage included in the debian package is not very useful on
its own, it would be nice to include the PDF language reference
documentation in the package as well.

Bug#961067: Should be fixed in 1.2.0-1 (not verified)

[Bill Blough]

Support for Django 3 has been added upstream, so this should be fixed as of
the 1.2.0-1 upload.  However, I haven't had a chance to test it with
Django 3 to confirm that everything plays nicely.


-- 
GPG: 5CDD 0C9C F446 BC1B 2509  8791 1762 E022 7034 CF84

Bug#977835: Please package the lastest version >= 3.5.2

[Picca Frédéric-Emmanuel]

Package: musescore3
Severity: wishlist
X-Debbugs-Cc: pi...@debian.org

Everythings in the title :))

thanks for considering

Frederic


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

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

Bug#977834: sddm: [X11] SessionLogFile option does not work, .xsession-errors used instead

[Iris Morelle]

Package: sddm
Version: 0.19.0-2
Severity: normal
X-Debbugs-Cc: shadowm2...@gmail.com

Dear Maintainer,

sddm in Debian is currently unable to honour the SessionLogFile= option in the
[X11] section of /etc/sddm.conf. Even when the option is not present, the
default is to use ~/.local/share/sddm/xorg-session.log to write stdout/stderr
for user-launched applications, but in practice the messages end up in
~/.xsession-errors -- which I might add is allowed to grow indefinitely, as I
found the file for my user account to be approximately 28.4 GB in size after
almost 4 years.

>From a quick glance at the startup scripts after noticing that this issue does
not occur in other distributions (e.g. openSUSE), I found out that
/etc/X11/Xsession (which I assume gets sourced by sddm some way or another
during login) redirects both file descriptors to ~/.xsession-errors in append
mode without any mechanism within the script or elsewhere for changing the file
path or respecting sddm's options. I believe that this script does not count as
a configuration file so any local changes would be overwritten by apt any time
its parent package (x11-common) gets upgraded.

I can see that whether I set [X11] SessionLogFile= to a non-default value or
leave it unspecified, the file that *should* be used will be created but ends
up abandoned with a size of 0 bytes while messages get written to ~/.xsession-
errors instead.

The reason I'm filing this bug against sddm instead of x11-common is that I'm
not entirely sure if this is a bug in the sddm packaging (e.g. a Debian-
specific factor about x11-common that isn't taken into account in sddm). Since
I haven't used a different display manager in years myself I also ignore if
other display managers suffer from this same bug or deal with this situation in
a different fashion. Feel free to reassign to any other package as needed.



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

Kernel: Linux 5.9.15-hanacore-162 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sddm depends on:
ii  adduser   3.118
ii  debconf [debconf-2.0] 1.5.74
ii  libc6 2.31-5
ii  libgcc-s1 10.2.1-1
ii  libpam0g  1.3.1-5
ii  libqt5core5a  5.15.2+dfsg-2
ii  libqt5dbus5   5.15.2+dfsg-2
ii  libqt5gui55.15.2+dfsg-2
ii  libqt5network55.15.2+dfsg-2
ii  libqt5qml55.15.2+dfsg-2
ii  libqt5quick5  5.15.2+dfsg-2
ii  libstdc++610.2.1-1
ii  libsystemd0   247.1-3
ii  libxcb-xkb1   1.14-2
ii  libxcb1   1.14-2
ii  qml-module-qtquick2   5.15.2+dfsg-2
ii  x11-common1:7.7+21
ii  xauth 1:1.0.10-1
ii  xserver-xephyr [xserver]  2:1.20.10-1
ii  xserver-xorg [xserver]1:7.7+21
ii  xvfb [xserver]2:1.20.10-1

Versions of packages sddm recommends:
ii  haveged1.9.13-1
ii  libpam-systemd 247.1-3
ii  sddm-theme-breeze [sddm-theme] 4:5.20.4-3
ii  sddm-theme-debian-breeze [sddm-theme]  4:5.19.5-5+b1

Versions of packages sddm suggests:
ii  libpam-kwallet5   5.20.4-1
pn  qtvirtualkeyboard-plugin  

-- debconf information:
* shared/default-x-display-manager: sddm
  sddm/daemon_name: /usr/bin/sddm

Bug#977826: Failed to upload environment to systemd (gdm)

[Simon McVittie]

Control: severity -1 minor

On Mon, 21 Dec 2020 at 14:58:48 +0100, Michael Biebl wrote:
> looking through the journal, I see the following warning messages:
> 
> Dez 21 14:35:06 debian gnome-session[544]: gnome-session-binary[544]: 
> WARNING: Failed to upload environment to systemd: 
> GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name 
> "org.freedesktop.systemd>
> Dez 21 14:35:06 debian gnome-session-binary[544]: WARNING: Failed to upload 
> environment to systemd: 
> GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name 
> "org.freedesktop.systemd1" does not exist
> Dez 21 14:35:06 debian gnome-session[544]: gnome-session-binary[544]: 
> WARNING: Failed to reset failed state of units: 
> GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name 
> "org.freedesktop.systemd1">
> Dez 21 14:35:06 debian gnome-session-binary[544]: WARNING: Failed to reset 
> failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: 
> Name "org.freedesktop.systemd1" does not exist
> Dez 21 14:35:06 debian gnome-session[544]: gnome-session-binary[544]: 
> WARNING: Falling back to non-systemd startup procedure due to error: 
> GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.>
> Dez 21 14:35:06 debian gnome-session-binary[544]: WARNING: Falling back to 
> non-systemd startup procedure due to error: 
> GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name 
> "org.freedesktop.systemd1>
> 
> Both systemd and libpam-systemd are installed and active.
> 
> Afaics, those warnings come from gnome-session that is started by gdm3.

If this is from the gdm3 greeter session, then it's likely to be harmless.
The greeter session uses a separate dbus-daemon per greeter instance,
instead of one per uid like dbus-user-session.

This is because if the system is configured in such a way that there
needs to be more than one greeter (multi-seat, and perhaps XDMCP if gdm
still supports that), each greeter needs to behave like its own little
session; and there is currently only one Debian-gdm uid (gdm doesn't ask
systemd to generate users for it dynamically, although maybe it should).

In older versions of gdm, you would have seen a different warning about
failure to activate /bin/false to provide the org.freedesktop.systemd1
name. Newer versions of gdm turn off autostarting in an attempt to
suppress that warning.

smcv

Bug#977833: librelaxng-datatype-java: fails to build source package

[Holger Levsen]

Package: librelaxng-datatype-java
Version: 1.0+ds1-3
Severity: serious

Dear Maintainer,

I wanted to do a source only upload of librelaxng-datatype-java
(because there are no .buildinfo files for it in the archive, 
as it has been uploaded before 2016), but it fails to build
the source package. The binary package builds just fine.

Steps to reproduce:

$ apt source librelaxng-datatype-java
$ cd librelaxng-datatype-java-*
$ dpkg-buildpackage
dpkg-buildpackage: info: source package librelaxng-datatype-java
dpkg-buildpackage: info: source version 1.0+ds1-3
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Giovanni Mascellani 
dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build .
 fakeroot debian/rules clean
dh clean --with maven-repo-helper
dh: warning: Compatibility levels before 10 are deprecated (level 7 in use)
   dh_auto_clean
dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 7 
in use)
ant clean
/usr/bin/java: error while loading shared libraries: libjli.so: cannot open 
shared object file: No such file or directory
dh_auto_clean: error: ant clean returned exit code 127
make: *** [debian/rules:8: clean] Error 255
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2
$

(This is with or without any changes to the source package.)


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁   holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀ PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
 ⠈⠳⣄

In Europe there are people prosecuted by courts because they saved other people
from drowning in the  Mediterranean Sea.  That is almost as absurd  as if there
were people being prosecuted because they save humans from drowning in the sea.


signature.asc
Description: PGP signature