Bug#969950: Workaround: multipath-tools: multipath not detecting more then 128 Paths

[bugs]

Dear maintainer

After several bare-metal re-installations i found a simple workaround 
which seems to work, at least for me.


I changed the multipathd.service script in systemd as follows:

3c3
< Wants=systemd-udev-trigger.service systemd-udev-settle.service
---
> Wants=local-fs-pre.target multipathd.socket blk-availability.service


May be, there is a conflict or timeout in the udev service?

After this change, the system boots as expected, including all required 
services.


Best regards, Frank Moehle

Bug#969261: cyrus-common: bumping to debhelper 13 needs usind dh_installtmpfiles

[Jean Charles Delépine]

Package: cyrus-common
Version: 3.2.3-1
Followup-For: Bug #969261

Hello,

The file /usr/lib/tmpfile.d/cyrus-imapd.conf isn't installed anymore.
Cyrus can't start without the dirs /run/cyrus and /run/cyrus/socket
created by systemd tmpfile mechanism.

https://manpages.debian.org/testing/debhelper/dh_installsystemd.1.en.html

debian/package.tmpfile
Only used in compat 12 or earlier. In compat 13+, this file is handled by 
dh_installtmpfiles(1) instead.

If this exists, it is installed into usr/lib/tmpfiles.d/ in the package 
build directory. Note that the "tmpfiles.d" mechanism is currently only used by 
systemd.

Without this file cyrus can't start on a fresh install and can't reboot on an 
old one.

Sincerly,
Jean Charles Delépine


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

Kernel: Linux 5.7.0-1-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CRAP, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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

Versions of packages cyrus-common depends on:
ii  adduser 3.118
ii  db-upgrade-util 5.3.1+nmu1
ii  db-util 5.3.1+nmu1
ii  debconf [debconf-2.0]   1.5.74
ii  e2fsprogs   1.45.6-1
ii  gawk1:5.0.1+dfsg-1
ii  init-system-helpers 1.58
ii  libc6   2.31-3
ii  libclamav9  0.102.4+dfsg-1+b1
ii  libcom-err2 1.45.6-1
ii  libgcc-s1   10.2.0-6
ii  libical33.0.8-2
ii  libicu6767.1-4
ii  libjansson4 2.13.1-1
ii  libkrb5-3   1.17-10
ii  libldap-2.4-2   2.4.51+dfsg-1
ii  libpcre32:8.39-13
ii  libpq5  12.4-1
ii  libsasl2-2  2.1.27+dfsg-2
ii  libsasl2-modules2.1.27+dfsg-2
ii  libsnmp35   5.8+dfsg-5
ii  libsqlite3-03.33.0-1
ii  libssl1.1   1.1.1g-1
ii  libstdc++6  10.2.0-6
ii  libwrap07.6.q-30
ii  libxapian30 1.4.17-1
ii  libxml2 2.9.10+dfsg-6
ii  libzephyr4  3.1.2-1+b3
ii  lsb-base11.1.0
ii  netbase 6.1
ii  perl5.30.3-4
ii  postfix [mail-transport-agent]  3.5.6-1
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages cyrus-common recommends:
ii  cyrus-admin  3.2.3-1

Versions of packages cyrus-common suggests:
pn  apt-listchanges
ii  cyrus-admin3.2.3-1
pn  cyrus-caldav   
ii  cyrus-clients  3.2.3-1
pn  cyrus-doc  
pn  cyrus-imapd
pn  cyrus-murder   
pn  cyrus-nntpd
pn  cyrus-pop3d
pn  cyrus-replication  
ii  sasl2-bin  2.1.27+dfsg-2

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

-- debconf-show failed

Bug#970073: ITP: r-bioc-hsmmsinglecell -- Single-cell RNA-Seq for differentiating human skeletal muscle myoblasts

[Andreas Tille]

Package: wnpp
Severity: wishlist

Subject: ITP: r-bioc-hsmmsinglecell -- Single-cell RNA-Seq for differentiating 
human skeletal muscle myoblasts
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: r-bioc-hsmmsinglecell
  Version : 1.8.0
  Upstream Author : Cole Trapnell
* URL : 
https://bioconductor.org/packages/release/data/experiment/html/HSMMSingleCell.html
* License : Artistic-2.0
  Programming Lang: GNU R
  Description : Single-cell RNA-Seq for differentiating human skeletal 
muscle myoblasts
 Skeletal myoblasts undergo a well-characterized sequence of
 morphological and transcriptional changes during differentiation. In
 this experiment, primary human skeletal muscle myoblasts (HSMM) were
 expanded under high mitogen conditions (GM) and then differentiated by
 switching to low-mitogen media (DM). RNA-Seq libraries were sequenced
 from each of several hundred cells taken over a time-course of serum-
 induced differentiation. Between 49 and 77 cells were captured at each
 of four time points (0, 24, 48, 72 hours) following serum switch using
 the Fluidigm C1 microfluidic system. RNA from each cell was isolated and
 used to construct mRNA-Seq libraries, which were then sequenced to a
 depth of ~4 million reads per library, resulting in a complete gene
 expression profile for each cell.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-bioc-hsmmsinglecell

Bug#970072: ITP: r-cran-ddrtree -- GNU R learning principal graphs with DDRTree

[Andreas Tille]

Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-ddrtree -- GNU R learning principal graphs with DDRTree
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: r-cran-ddrtree
  Version : 0.1.5
  Upstream Author : Xiaojie Qiu, Cole Trapnell, Qi Mao, Li Wang
* URL : https://cran.r-project.org/package=DDRTree
* License : Artistic
  Programming Lang: GNU R
  Description : GNU R learning principal graphs with DDRTree
 Provides an implementation of the framework of reversed graph embedding
 (RGE) which projects data into a reduced dimensional space while
 constructs a principal tree which passes through the middle of the data
 simultaneously. DDRTree shows superiority to alternatives (Wishbone,
 DPT) for inferring the ordering as well as the intrinsic structure of
 the single cell genomics data. In general, it could be used to
 reconstruct the temporal progression as well as bifurcation structure of
 any datatype.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-ddrtree

Bug#969446: RFS: vguitar-2.6 [ITP] -- Play Guitar in any term window. Use with a MIDI synthesizer (qsynth).

[Hilmar Preuße]

Am 11.09.2020 um 03:18 teilte Nick Strauss mit:

Hi Nick,

>> Don't install a program into /usr/local. The package won't be accepted.
> 
> My makefile has prefix defined for vguitar exe destination.
> 
> ./Makefile:prefix = /usr/local
> ./Makefile:$(DESTDIR)$(prefix)/bin/vguitar
> 
> What should this be? 
> 
The tar ball I provided contains a patch, which changes this to "/usr".
No need to change the upstream code. If you unpack the source package
using "dpkg-source -x ..*dsc" the patch should be applied.

As I provided only the debian.tar.xz file, you need to:

hille@sid:~ $ tar xf vguitar_2.6.orig.tar.gz
hille@sid:~ $ cd vguitar_2.6.orig/
hille@sid:~/vguitar_2.6.orig $ tar xf ../vguitar_2.6-1.debian.tar.xz
hille@sid:~/vguitar_2.6.orig $ cd -
hille@sid:~ $ dpkg-source -b vguitar_2.6.orig
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying user_local
dpkg-source: info: building vguitar using existing ./vguitar_2.6.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building vguitar in vguitar_2.6-1.debian.tar.xz
dpkg-source: info: building vguitar in vguitar_2.6-1.dsc

H.
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

Bug#970061: RFS: ip2location/1.0-0 [ITP] -- IP2Location geolocation library

[IP2Location]

Package: ip2location
Severity: normal

Dear mentors,

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

* Package name : ip2location
  Version : 1.0.0
  Upstream Author : IP2Location (supp...@ip2location.com)
* URL : https://www.ip2location.com
* License : MIT
* Vcs : https://github.com/chrislim2888/IP2Location-C-Library

It builds those binary packages:

libip2location

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

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



Regards,
--
IP2Location

Bug#970061: RFS: ip2location/1.0-0 [ITP] -- IP2Location geolocation library

[Andrei POPESCU]

Control: reassign -1 sponsorship-requests

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

Reassigning to correct (pseudo-)package.

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


signature.asc
Description: PGP signature

Bug#970071: mercurial: bullseye: /updates -> -security

[Paul Wise]

Source: mercurial
Version: 5.5.1-1
Severity: minor
File: contrib/automation/hgautomation/linux.py
User: debian-de...@lists.debian.org
Usertags: bullseye-security

With the release of Debian bullseye and later, security updates are
provided in the bullseye-security suite instead of bullseye/updates.

In the mercurial source package there appears to be a script that
generates a Debian chroot/container for building packages and that
script relies on appears to write an apt sources.list that will
not provide security updates for packages installed in the
chroot/container. I suggest that this script check the version of the
Debian release in question using distro-info and then if the release is
11 or higher, then use $release-security otherwise use $release/updates
as before. It is much better to use distro-info than to hard-code the
release version numbers. It might even be a good idea to include the
security suite information in distro-info itself and look it up there.

I filed this bug at severity minor since the script in question doesn't
appear to be used for any part of the Debian packages nor for building
the Debian packages, but only for some upstream packages.

   mercurial-5.5.1 $ grep -rC4 '/updates '
   contrib/automation/hgautomation/linux.py-if [ "$LSB_RELEASE" = "stretch" -o 
"$LSB_RELEASE" = "buster" ]; then
   contrib/automation/hgautomation/linux.py-cat << EOF | sudo tee -a 
/etc/apt/sources.list
   contrib/automation/hgautomation/linux.py-# Sources are useful if we want to 
compile things locally.
   contrib/automation/hgautomation/linux.py-deb-src 
http://deb.debian.org/debian $LSB_RELEASE main
   contrib/automation/hgautomation/linux.py:deb-src 
http://security.debian.org/debian-security $LSB_RELEASE/updates main
   contrib/automation/hgautomation/linux.py-deb-src 
http://deb.debian.org/debian $LSB_RELEASE-updates main
   contrib/automation/hgautomation/linux.py-deb-src 
http://deb.debian.org/debian $LSB_RELEASE-backports main
   contrib/automation/hgautomation/linux.py-
   contrib/automation/hgautomation/linux.py-deb [arch=amd64] 
https://download.docker.com/linux/debian $LSB_RELEASE stable

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#970069: marionnet: bullseye: /updates -> -security

[Paul Wise]

Source: marionnet
Version: 0.90.6+bzr508-1
Severity: minor
File: uml/pupisto.debian/pupisto.debian.sh
User: debian-de...@lists.debian.org
Usertags: bullseye-security

With the release of Debian bullseye and later, security updates are
provided in the bullseye-security suite instead of bullseye/updates.

In the marionnet source package there appears to be a script that
generates a Debian chroot/container for building packages and that
script relies on appears to write an apt sources.list that will
not provide security updates for packages installed in the
chroot/container. I suggest that this script check the version of the
Debian release in question using distro-info and then if the release is
11 or higher, then use $release-security otherwise use $release/updates
as before. It is much better to use distro-info than to hard-code the
release version numbers. It might even be a good idea to include the
security suite information in distro-info itself and look it up there.

I filed this bug at severity minor since the script in question doesn't
appear to be used for any part of the Debian packages nor for building
the Debian packages, but only for some upstream packages.

   $ grep -B4 -A7 /updates  uml/pupisto.debian/pupisto.debian.sh
   function fix_apt_sources_update_and_upgrade {
# global DEBIANROOT HTTP_SERVER RELEASE
local ROOT=${1:-$DEBIANROOT}
local TARGET=$ROOT/etc/apt/sources.list
sudo_fprintf $TARGET "%s\n%s\n" "deb $HTTP_SERVER $RELEASE main" "deb 
http://security.debian.org/ $RELEASE/updates main"
# Update:
# sudo_careful_chroot ${ROOT} aptitude update
sudo_careful_chroot ${ROOT} apt-get update
# Upgrade:
# sudo_careful_chroot ${ROOT} aptitude -y safe-upgrade
sudo_careful_chroot ${ROOT} apt-get -y upgrade
   }

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#970068: mariadb-10.3: bullseye: /updates -> -security

[Paul Wise]

Source: mariadb-10.3
Version: 1:10.3.24-2
Severity: minor
File: storage/mroonga/packages/apt/build-deb.sh
User: debian-de...@lists.debian.org
Usertags: bullseye-security

With the release of Debian bullseye and later, security updates are
provided in the bullseye-security suite instead of bullseye/updates.

In the mariadb source package there appears to be a script that
generates a Debian chroot/container for building packages and that
script relies on appears to write an apt sources.list that will
not provide security updates for packages installed in the
chroot/container. I suggest that this script check the version of the
Debian release in question using distro-info and then if the release is
11 or higher, then use $release-security otherwise use $release/updates
as before. It is much better to use distro-info than to hard-code the
release version numbers. It might even be a good idea to include the
security suite information in distro-info itself and look it up there.

I filed this bug at severity minor since the script in question doesn't
appear to be used for any part of the Debian packages nor for building
the Debian packages, but only for some upstream packages.

   $ grep -A6 -B10 /updates  storage/mroonga/packages/apt/build-deb.sh
   distribution=$(lsb_release --id --short | tr 'A-Z' 'a-z')
   case "${distribution}" in
 debian)
   component=main
   run cat < /etc/apt/sources.list.d/groonga.list
   deb http://packages.groonga.org/debian/ ${code_name} main
   deb-src http://packages.groonga.org/debian/ ${code_name} main
   EOF
   if ! grep --quiet security /etc/apt/sources.list; then
 run cat < /etc/apt/sources.list.d/security.list
   deb http://security.debian.org/ ${code_name}/updates main
   deb-src http://security.debian.org/ ${code_name}/updates main
   EOF
   fi
   run apt-get update
   run apt-get install -y --allow-unauthenticated groonga-keyring
   run apt-get update
   ;;

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#969446: RFS: vguitar-2.6 [ITP] -- Play Guitar in any term window. Use with a MIDI synthesizer (qsynth).

[Nick Strauss]

Hi Hilmar,

> Did you get the updated debian.tar.xz I sent you? Consider to use that one.

Yes, I did. Thank you! 

It arrived moments after I sent my last post.

> Don't install a program into /usr/local. The package won't be accepted.

My makefile has prefix defined for vguitar exe destination.

./Makefile:prefix = /usr/local
./Makefile:$(DESTDIR)$(prefix)/bin/vguitar

What should this be? 

Nick Strauss
https://www.nick-strauss.com

Bug#970067: lxc-templates: bullseye: /updates -> -security

[Paul Wise]

Package: lxc-templates
Version: 3.0.4-3
Severity: serious
File: /usr/share/lxc/templates/lxc-debian
User: debian-de...@lists.debian.org
Usertags: bullseye-security

With the release of Debian bullseye and later, security updates are
provided in the bullseye-security suite instead of bullseye/updates.

The lxc-debian script appears to write an apt sources.list that will
not provide security updates for sources.list scripts created in order
to cater to Debian bullseye images. I suggest that this script check
the version of the Debian release in question using distro-info and
then if the release is 11 or higher, then use $release-security
otherwise use $release/updates as before. It is much better to use
distro-info than to hard-code the release version numbers. It might
even be a good idea to include the security suite information in
distro-info itself and look it up from there.

   $ grep -A3 -B23 /updates /usr/share/lxc/templates/lxc-debian
   write_sourceslist()
   {
   local rootfs="$1";  shift
   local release="$1"; shift
   local arch="$1";shift

   local prefix="deb"
   if [ -n "${arch}" ]; then
   prefix="deb [arch=${arch}]"
   fi

   if [ "$mainonly" = 1 ]; then
 non_main=''
   else
 non_main=' contrib non-free'
   fi

   cat >> "${rootfs}/etc/apt/sources.list" << EOF
   ${prefix} $MIRROR  ${release} main${non_main}
   EOF

   if [ "$release" != "unstable" -a "$release" != "sid" ]; then
 cat >> "${rootfs}/etc/apt/sources.list" << EOF
   ${prefix} $SECURITY_MIRROR ${release}/updates main${non_main}
   EOF
   fi
   }

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#970066: atftp: CVE-2020-6097

[Salvatore Bonaccorso]

Source: atftp
Version: 0.7.git20120829-3.1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for atftp.

CVE-2020-6097[0]:
| An exploitable denial of service vulnerability exists in the atftpd
| daemon functionality of atftp 0.7.git20120829-3.1+b1. A specially
| crafted sequence of RRQ-Multicast requests trigger an assert() call
| resulting in denial-of-service. An attacker can send a sequence of
| malicious packets to trigger this vulnerability.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-6097
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6097
[1] https://talosintelligence.com/vulnerability_reports/TALOS-2020-1029

Regards,
Salvatore

Bug#970065: golang-pault-go-archive: bullseye: /updates -> -security

[Paul Wise]

Source: golang-pault-go-archive
Version: 1.0-1
Severity: minor
File: release.go
User: debian-de...@lists.debian.org
Usertags: bullseye-security

With the release of Debian bullseye references to stable/updates need
to be replaced with stable-security.

In one of the comments in the release.go file, there is a comment that
references stable/updates so will become broken after bullseye becomes
the next stable Debian release. It also references the URL to the
stable/updates Release file, which will also no longer work.

   golang-pault-go-archive-1.0 $ grep -rC5 /updates 
   release.go-  // May also include be prefixed by parts of the path following 
the
   release.go-  // directory beneath dists, if the Release file is not in a 
directory
   release.go-  // directly beneath dists/. As an example, security updates are 
specified
   release.go-  // in APT as:
   release.go-  //
   release.go:  // deb http://security.debian.org/ stable/updates main)
   release.go-  //
   release.go-  // The Release file would be located at
   release.go:  // http://security.debian.org/dists/stable/updates/Release and 
look like:
   release.go-  //
   release.go-  //   Suite: stable
   release.go-  //   Components: updates/main updates/contrib updates/non-free
   release.go-  Components []string `delim:" "`
   release.go-

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#970064: fai-doc: bullseye: /updates -> -security

[Paul Wise]

Package: fai-doc
Version: 5.9.4
Severity: minor
File: /usr/share/doc/fai-doc/examples/simple/files/etc/apt/sources.list/GNOME
File: /usr/share/doc/fai-doc/examples/simple/scripts/LAST/50-misc
User: debian-de...@lists.debian.org
Usertags: bullseye-security

The above two files reference $release/updates but the files don't
appear to take account of the fact that from the Debian bullseye
release onwards /updates must be replaced by -security otherwise the
apt sources.list being generated will no longer work.

   $ grep -r /updates /usr/share/doc/fai-doc/examples/simple/
   /usr/share/doc/fai-doc/examples/simple/files/etc/apt/sources.list/GNOME:deb 
{%security_cdn%}/debian-security {%release%}/updates main
   /usr/share/doc/fai-doc/examples/simple/scripts/LAST/50-misc:deb 
$apt_cdn/debian-security $release/updates main contrib non-free

For the GNOME file, I suggest replacing {%release%}/updates with a new
{%release-security%} variable and similar for the 50-misc script.

I've filed this at severity minor since it is just example files.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#949297: Patch for preferences

[Archisman Panigrahi]

In addition to Cinnamon, I can confirm that the above mentioned patch fixes
the bug in XFCE as well.
I intended to post a different link in the last paragraph of the above
message, but mistakenly posted a single link twice.

For more details, see https://askubuntu.com/a/1274106/124466

Archisman Panigrahi



On Fri, Sep 11, 2020 at 4:17 AM Archisman Panigrahi 
wrote:

> A patch for enabling preferences in the headerbar has been proposed at
> https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/34
>
> While I can't say whether (or when) the patch will be accepted in the
> upstream, I can confirm that the patch fixes the issue in Cinnamon.
>
> A debian package incorporating this patch has been made, and available at
> https://launchpad.net/~dtl131/+archive/ubuntu/mediahacks2/+packages
>
> It would be great if the patch is applied to the Debian Cheese package,
> and possibly backported to Buster (even if the upstream does not accept it).
>
> For more details, see
> https://launchpad.net/~dtl131/+archive/ubuntu/mediahacks2/+packages
>
> Archisman Panigrahi
>
>

Bug#970063: debian-paketmanagement-buch: bullseye: /updates -> -security

[Paul Wise]

Package: debian-paketmanagement-buch
Version: 0~2019.03.01
Severity: normal
File: 
/usr/share/doc/debian-paketmanagement-buch/debian-paketmanagement.allinone.html
File: /usr/share/doc/debian-paketmanagement-buch/debian-paketmanagement.mobi
User: debian-de...@lists.debian.org
Usertags: bullseye-security

In the section "Inhalt der automatisch generierten Liste der
Paketmirrors" there is a reference to stable/updates but with the
release of Debian bullseye this reference will be broken since Debian
has switched to using bullseye-security for bullseye.

   $ w3m -dump 
/usr/share/doc/debian-paketmanagement-buch/debian-paketmanagement.allinone.html 
| grep -B11 -A1 stable/updates
   Inhalt der automatisch generierten Liste der Paketmirrors

   # cat sources.list

   # Debian packages for stable
   deb http://artfiles.org/debian/ stable main contrib
   # Uncomment the deb-src line if you want 'apt-get source'
   # to work with most packages.
   # deb-src http://artfiles.org/debian/ stable main contrib

   # Security updates for stable
   deb http://security.debian.org/ stable/updates main contrib
   #

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#970054: fwupd: Missing Depends (or Recommends) on udisks2 for UEFI update

[Limonciello, Mario]

Thanks for the report, and submitting the fix upstream!

I agree, it should probably be a recommends and we should pull that patch in
for safety.  I'll include it in a 1.4.6-2 upload once we merge it upstream.

Thanks!

> -Original Message-
> From: Jochen Sprickerhof 
> Sent: Thursday, September 10, 2020 17:08
> To: Debian Bug Tracking System
> Subject: Bug#970054: fwupd: Missing Depends (or Recommends) on udisks2 for
> UEFI update
> 
> 
> [EXTERNAL EMAIL]
> 
> Package: fwupd
> Version: 1.4.6-1
> Severity: normal
> 
> Hi,
> 
> starting with 1.4.6 (or 25ba4157) fwupdmgr connects to
> /org/freedesktop/UDisks2/Manager to get the ESP. You can see this by
> running
> 
> dbus-monitor --system
> 
> while doing a
> 
> fwupdtool esp-list
> 
> with out udisks2 installed I get a segfault and fwupdmgr does not opt to
> update the UEFI. I proposed a fix to the segfault here:
> 
> https://github.com/fwupd/fwupd/pull/2384
> 
> Still there should be a dependency on udisks2 (or a way to work without
> it).
> 
> Cheers Jochen
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.8.0-1-amd64 (SMP w/8 CPU threads)
> 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 fwupd depends on:
> ii  libc6  2.31-3
> ii  libefiboot137-5
> ii  libefivar1 37-5
> ii  libelf10.180-1+b1
> ii  libflashrom1   1.2-5
> ii  libfwupd2  1.4.6-1
> ii  libfwupdplugin11.4.6-1
> ii  libglib2.0-0   2.64.4-1
> ii  libgudev-1.0-0 233-1
> ii  libgusb2   0.3.4-0.2
> ii  libjcat1   0.1.3-2
> ii  libjson-glib-1.0-0 1.4.4-2
> ii  libpolkit-gobject-1-0  0.105-29
> ii  libsmbios-c2   2.4.3-1
> ii  libsoup2.4-1   2.70.0-1
> ii  libsqlite3-0   3.33.0-1
> ii  libtss2-esys0  3.0.0-1
> ii  libxmlb1   0.1.15-2
> ii  shared-mime-info   1.15-1
> 
> Versions of packages fwupd recommends:
> pn  bolt  
> pn  fwupd-signed  
> ii  python3   3.8.2-3
> 
> fwupd suggests no packages.
> 
> -- no debconf information

Bug#969940: docker.io: bullseye: switch from /updates to -security

[Paul Wise]

On Thu, 2020-09-10 at 14:22 +1000, Dmitry Smirnov wrote:

> This is an upstream/vendor script that I did not even know exists.
> I doubt maintainers of "docker.io" package used it...
> 
> I don't know who uses Docker's "debootstrap" script (and how) so it may be 
> an upstream-only issue. I'm not even sure we should be providing/shipping
> this script...

I see, I guess this bug can be downgraded to minor then. 

I'm only doing drive-by reporting of the issue [1], so I won't be doing
any forwarding of this issue upstream, so I hope you are able to ask
them about fixing the issue.

1. 
https://lists.debian.org/msgid-search/4f31193c69f5976a2922d5736576d060570baa42.ca...@debian.org

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#949297: Patch for preferences

[Archisman Panigrahi]

A patch for enabling preferences in the headerbar has been proposed at
https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/34

While I can't say whether (or when) the patch will be accepted in the
upstream, I can confirm that the patch fixes the issue in Cinnamon.

A debian package incorporating this patch has been made, and available at
https://launchpad.net/~dtl131/+archive/ubuntu/mediahacks2/+packages

It would be great if the patch is applied to the Debian Cheese package, and
possibly backported to Buster (even if the upstream does not accept it).

For more details, see
https://launchpad.net/~dtl131/+archive/ubuntu/mediahacks2/+packages

Archisman Panigrahi

Bug#969319: [Pkg-utopia-maintainers] Bug#969319: Bug#969319: wifi cannot connect after combined suspend & gateway reboot

[Lyndon Brown]

On Tue, 2020-09-08 at 23:35 +0200, Michael Biebl wrote:
> In any case, it might be a good idea to involve NM upstream and file
> an
> issue at
> https://gitlab.freedesktop.org/NetworkManager/NetworkManager

done:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/531

also:
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/550

Bug#966098: systemd: 'systemctl status' reports "access denied" after upgrade

[Dima Kogan]

Hi. Thanks for replying.

I just ran some tests, and I don't think sudo is the problem. And to be
clear, this isn't a "dist-upgrade". This machine is running sid, and an
"apt upgrade" triggered this issue.

The current state is that the machine is up-to-date with the exception
of systemd. Upgrading systemd causes the issue being reported, so I
downgrade it back to keep the box usable.

Latest sequence:

1. I logged in as root WITHOUT sudo, as suggested, and I upgraded the
   systemd packages:


   dima@snarky:~$ su

   Password: 


   root@snarky:/home/dima# sudo aptitude install systemd

   The following NEW packages will be installed:
 systemd-timesyncd{a} 
   The following packages will be upgraded:
 libsystemd0 systemd 
   2 packages upgraded, 1 newly installed, 0 to remove and 515 not upgraded.
   Need to get 0 B/4817 kB of archives. After unpacking 2802 kB will be used.
   The following packages have unmet dependencies:
libpam-systemd : Depends: systemd (= 239-15) but 246.4-1 is to be installed
libnss-systemd : Depends: systemd (= 239-15) but 246.4-1 is to be installed
   The following actions will resolve these dependencies:

Upgrade the following packages:  
   1) libnss-systemd [239-15 (now) -> 246.4-1 (unstable)]
   2) libpam-systemd [239-15 (now) -> 246.4-1 (unstable)]



   Accept this solution? [Y/n/q/?] 
   The following NEW packages will be installed:
 systemd-timesyncd{a} 
   The following packages will be upgraded:
 libnss-systemd libpam-systemd libsystemd0 systemd 
   4 packages upgraded, 1 newly installed, 0 to remove and 513 not upgraded.
   Need to get 0 B/5285 kB of archives. After unpacking 2957 kB will be used.
   Do you want to continue? [Y/n/?] y
   Reading changelogs... Done
   debconf: unable to initialize frontend: Dialog
   debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell 
buffer, or without a controlling terminal.)
   debconf: falling back to frontend: Readline
   (Reading database ... 208114 files and directories currently installed.)
   Preparing to unpack .../libnss-systemd_246.4-1_amd64.deb ...
   Unpacking libnss-systemd:amd64 (246.4-1) over (239-15) ...
   Preparing to unpack .../libpam-systemd_246.4-1_amd64.deb ...
   Unpacking libpam-systemd:amd64 (246.4-1) over (239-15) ...
   Preparing to unpack .../systemd_246.4-1_amd64.deb ...
   Unpacking systemd (246.4-1) over (239-15) ...
   Preparing to unpack .../systemd-timesyncd_246.4-1_amd64.deb ...
   Unpacking systemd-timesyncd (246.4-1) ...
   Preparing to unpack .../libsystemd0_246.4-1_amd64.deb ...
   Unpacking libsystemd0:amd64 (246.4-1) over (239-15) ...
   Setting up libsystemd0:amd64 (246.4-1) ...
   Setting up systemd (246.4-1) ...
   Installing new version of config file /etc/systemd/journald.conf ...
   Installing new version of config file /etc/systemd/resolved.conf ...
   Installing new version of config file /etc/systemd/system.conf ...
   Installing new version of config file /etc/systemd/user.conf ...
   Failed to enable unit: Access denied
   Failed to reload daemon: Access denied
   Failed to stop systemd-networkd.socket: Access denied
   See system logs and 'systemctl status systemd-networkd.socket' for details.
   Failed to try-restart systemd-networkd.service: Access denied
   See system logs and 'systemctl status systemd-networkd.service' for details.
   Failed to try-restart systemd-resolved.service: Access denied
   See system logs and 'systemctl status systemd-resolved.service' for details.
   Failed to try-restart systemd-journald.service: Access denied
   See system logs and 'systemctl status systemd-journald.service' for details.
   Setting up systemd-timesyncd (246.4-1) ...
   Failed to reload daemon: Access denied
   Failed to preset unit: Access denied
   /usr/bin/deb-systemd-helper: error: systemctl preset failed on 
systemd-timesyncd.service: No such file or directory
   Failed to reload daemon: Access denied
   Failed to get unit file state for systemd-timesyncd.service: Access denied
   Failed to retrieve unit state: Access denied
   systemd-timesyncd.service is a disabled or a static unit not running, not 
starting it.
   Setting up libpam-systemd:amd64 (246.4-1) ...
   debconf: unable to initialize frontend: Dialog
   debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell 
buffer, or without a controlling terminal.)
   debconf: falling back to frontend: Readline
   Setting up libnss-systemd:amd64 (246.4-1) ...
   Processing triggers for man-db (2.9.3-2) ...
   Processing triggers for dbus (1.12.20-1) ...
   Processing triggers for libc-bin (2.31-1) ...
   [master 8c809f6] committing changes in /etc made by "aptitude install 
systemd"
5 files changed, 21 insertions(+), 10 deletions(-)
delete mode 12 systemd/system/systemd-timesyncd.service

   Current status: 513 (-4) upgradable.


You can see the errors in the upgrade. I can confirm that at this point
I can't talk to sy

Bug#966253: RFS: devtodo/0.1.20-8 [QA] -- hierarchical, prioritised todo list manager

[Carlos Henrique Lima Melara]

Hi.

On Tue, 1 Sep 2020 08:27:34 +0300 Adrian Bunk  wrote:
> please always Cc people in the BTS, except for the maintainer noone gets 
> automatically subscribed.

Will do.

> > On Thu, 27 Aug 2020 11:41:48 +0300 Adrian Bunk  wrote:
> > > >* debian/rules: replaced override_dh_auto_install with 
> > > > dh_bash-completion
> > > >  for the installation of bash-completion code.
> > > 
> > > This is not the correct name for the installed file:
> > > /usr/share/bash-completion/completions/devtodo.bash-completion
> > 
> > I think that the phrase just looks a bit confusing (my bad). What
> > I meant is replaced override_dh_auto_install with dh_bash-completion
> > addon.
> 
> But it isn't doing the same.
> 
> What I meant is that debdiff says when comparing 0.1.20-7 with 0.1.20-8:
> 
> Files in first .deb but not in second
> -
> -rw-r--r--  root/root   /usr/share/bash-completion/completioins/devtodo
> 
> Files in second .deb but not in first
> -
> -rw-r--r--  root/root   
> /usr/share/bash-completion/completions/devtodo.bash-completion
> 
> Your change fixes the typo in the directory name (good),
> but it installs the file with the wrong name (bad).

Yes, I really missed that filename on the debdiff. It's fixed now, thanks.

Regards,
Charles

Bug#970062: ecryptfs-utils: Consider providing package in buster-backports?

[Boyuan Yang]

Source: ecryptfs-utils
Severity: wishlist
X-Debbugs-CC:g...@debian.org

Hi,

I just noticed that ecryptfs-utils was not in buster repository. Since
the previous bugs are now solved in Testing, can we provide it in
buster-backports to benefit Debian 10 users?

Since I am not familiar with the tool, I can make a no-change backport
if you find it okay. It would be even greater if you can directly
provide a buster-backports upload.

Thanks,
Boyuan Yang



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

Bug#969782: RFS: jag/0.3.8-1 -- arcade and puzzle 2D game

[Carlos Donizete Froes]

Hi Reiner,

> I think the test is not yet working.
> 
> jag is a graphical application, but you are not instructing autopkgtest
> to start a (virtual) X server.
> And even if this was working, what would this actually be testing?
> 
> I think the autopkgtest is only passing because of the & which starts it
> in the background (where it fails to start) and then the shell process exits
> successfully?
> 
> I would recommend to remove the test as it's currently not testing
> anything (not even "superficially"). Writing a proper test for a game
> is probablby quite difficult, though maybe someone else has a better
> idea how this could be tested.

I see, I removed the autopkgtest from the package. But in future updates I will 
see if I
can deploy correctly.

Whoever sponsors this package, I will be very grateful.

Thanks!

-- 
⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
⣾⠁⢠⠒⠀⣿⡁ Debian Wiki: https://wiki.debian.org/coringao
⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
⠈⠳⣄⠀⠀⠀  2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780


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

Bug#970060: ITP: r-cran-pkgdown -- Make Static HTML Documentation for a Package

[Steffen Moeller]

Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-pkgdown -- Make Static HTML Documentation for a Package
Package: wnpp
Owner: Steffen Moeller 
Severity: wishlist

* Package name: r-cran-pkgdown
  Version : 1.6.0
  Upstream Author : Hadley Wickham
* URL : https://cran.r-project.org/package=pkgdown
* License : MIT
  Programming Lang: GNU R
  Description : Make Static HTML Documentation for a Package
 Generate an attractive and useful website from a source package.
 'pkgdown' converts your documentation, vignettes, 'README', and more to
 'HTML' making it easy to share information about your package online.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-pkgdown

Bug#970059: RFP: librust-gstreamer-player -- gstreamer's Rust bindings for the Player crate

[Francisco M Neto]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: fmn...@fmneto.com

* Package name: librust-gstreamer-player
  Version : 0.16.3
  Upstream Author : Sebastian Dröge 
* URL : https://crates.io/crates/gstreamer-player/0.16.3
* License : LGPL
  Programming Lang: Rust
  Description : gstreamer's Rust bindings for the Player crate

GStreamer (Player library) bindings for Rust. Documentation can be found here.

These bindings are providing a safe API that can be used to interface with
GStreamer, e.g. for writing GStreamer-based applications and GStreamer plugins.

The bindings are mostly autogenerated with gir based on the GObject-
Introspection API metadata provided by the GStreamer project.


It is part of the gstreamer "suite", and provides a programming interface
for applications using gstreamer to play media. In particular, it is a
dependency for applications like gnome-podcasts, which I intend to package once
this is made available.

Ideally, it should be maintained by the Debian Rust team (had a brief
conversation about it in IRC).

Bug#969543: solaar: Solaar should autostart with --window=hide

[Matthew Gabeler-Lee]

repoen 969543
thanks

Package: solaar
Version: 1.0.3+dfsg-2
Followup-For: Bug #969543

Unfortunately 1.0.3+dfsg-2 didn't actually fix this, I suspect due to 
some issue with the rules around debconf and replacing symlinks with 
files.  When upgrading from 1.0.3+dfsg-1 to the new version, what 
happened is I ended up with /etc/xdg/autostart/solaar.desktop.dpkg-new, 
but the old symlink to the other file still in place unmodified.


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

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), LANGUAGE 
not set

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages solaar depends on:
ii  adduser  3.118
ii  debconf [debconf-2.0]1.5.74
ii  gir1.2-ayatanaappindicator3-0.1  0.5.5-2
ii  gir1.2-gtk-3.0   3.24.22-1
ii  gir1.2-notify-0.70.7.9-1
ii  passwd   1:4.8.1-1
ii  python3  3.8.2-3
ii  python3-gi   3.36.1-1
ii  python3-pyudev   0.21.0-3
ii  udev 246.4-1

Versions of packages solaar recommends:
ii  python3-dbus  1.2.16-3
ii  upower0.99.11-2

solaar suggests no packages.

-- debconf information excluded

Bug#969752: lists.debian.org: Request for a new list: debian-scheme

[Rob Browning]

Looks like my email address might have been slightly off, but for the
record, I'd have been fine with it too.

(Thanks to Vagrant for pointing this out to me.)

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#966535: transition: pipewire 0.3

[Simon McVittie]

On Wed, 09 Sep 2020 at 13:17:05 +0100, Simon McVittie wrote:
>   + weston
> * Either upload experimental version to unstable, or disable
>   pipewire integration in unstable (as was already done in experimental)
>   + krfb
> * Maintainers say they will apply
>   https://salsa.debian.org/qt-kde-team/kde/krfb/-/merge_requests/2 in
>   unstable when the transition goes ahead, but do not want to upload it
>   to experimental right now
> * Contingency plan: disable its pipewire support instead
>   + xdg-desktop-portal-kde
> * The KDE team tell me the version in experimental is not yet suitable
>   for unstable
> * Maintainers say they will apply
>   
> https://salsa.debian.org/qt-kde-team/kde/xdg-desktop-portal-kde/-/merge_requests/5
>   in unstable when the transition goes ahead
> * Contingency plan: disable its pipewire support instead

pipewire 0.3 is in unstable and built on all release architectures, so
please upload weston, krfb and xdg-desktop-portal-kde to unstable, either
with a build-dependency on libpipewire-0.3-dev or with their pipewire
support disabled.

(For xdg-desktop-portal-kde: a version of xdg-desktop-portal with
Pipewire support enabled is also already available in unstable on all
release architectures.)

I'm looking into also re-enabling Pipewire support in GNOME 3.36. I couldn't
get it to work in a test VM, but that might just be because the VM is using
QXL graphics, which until recently didn't work with GNOME screencasting
due to driver limitations (3.37.x has a workaround). If it works on real
hardware, I'll upload. If not, we'll have to wait for 3.37.x (which I have
already confirmed does work).

Thanks,
smcv

Bug#970058: ITP: r-cran-ggseqlogo -- ggplot2 Extension for Publication-Ready Sequence Logos

[Steffen Moeller]

Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-ggseqlogo -- ggplot2 Extension for Publication-Ready 
Sequence Logos
Package: wnpp
Owner: Steffen Moeller 
Severity: wishlist

* Package name: r-cran-ggseqlogo
  Version : 0.1
  Upstream Author : Omar Wagih
* URL : https://cran.r-project.org/package=ggseqlogo
* License : LGPL-2
  Programming Lang: GNU R
  Description : ggplot2 Extension for Publication-Ready Sequence Logos
 The extensive range of functions provided by this package makes it
 possible to draw highly versatile sequence logos.  Features include,
 but not limited to, modifying colour schemes and fonts used to draw the
 logo, generating multiple logo plots, and aiding the visualisation with
 annotations. Sequence logos can easily be combined with other plots
 'ggplot2' plots.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-ggseqlogo

Bug#955783: netgen-lvs: please make the build reproducible

[Chris Lamb]

Dear Maintainer,

> Source: netgen-lvs
> Version: 1.5.118-1
> Tags: patch

There hasn't seem to be any update on this bug in 158 days, in which
time the Reproducible Builds effort has come on a long way.

Would you consider applying this patch and uploading?


Regards,

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

Bug#960591: mistral: please make the build reproducible

[Chris Lamb]

Chris Lamb wrote:

> [..]

Friendly ping on this?


Regards,

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

Bug#952493: xavs2: please make the build reproducible

[Chris Lamb]

Dear Maintainer,

> Source: xavs2
> Version: 1.3-1~exp2
> Tags: patch

There hasn't seem to be any update on this bug in 198 days, in which
time the Reproducible Builds effort has come on a long way.

Would you consider applying this patch and uploading?


Regards,

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

Bug#953071: ndisc6: please make the build reproducible

[Chris Lamb]

Dear Maintainer,

> Source: ndisc6
> Version: 1.0.3-3
> Tags: patch

There hasn't seem to be any update on this bug in 190 days, in which
time the Reproducible Builds effort has come on a long way.

Would you consider applying this patch and uploading?


Regards,

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

Bug#968603: memcached should enable TLS by default

[Chris Lamb]

Hi Moises,

> We run the tests afterward on a dedicated machine..

The question here is not when or where these tests are run - can you
reproduce these test failures at all on this other machine? I can
reproduce them locally here (NB. with TLS enabled during the build).

If you can/cannot, sharing the test log would be a good next step.

> ...we do not run memcacheds test suite during build because it is cpu
> load dependent and not stable enough for us to rely on it during build.

As an unrelated remark, if the tests are CPU-load dependent (and
therefore non-deterministic) I would suggest you file that as an
upstream issue. A randomly-failing testsuite is, as I am sure you are
aware, not good software engineering practice.

Thanks for looking into this so far.

Regards,

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

Bug#960607: python-watcherclient: please make the build reproducible

[Chris Lamb]

Dear Maintainer,

> Source: python-watcherclient
> Version: 0.25.1-1
> Tags: patch

There hasn't seem to be any update on this bug in 118 days, in which
time the Reproducible Builds effort has come on a long way.

Would you consider applying this patch and uploading?


Regards,

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

Bug#956591: gpick: please make the build reproducible

[Chris Lamb]

Dear Maintainer,

> Source: gpick
> Version: 0.2.5-2
> Tags: patch

There hasn't seem to be any update on this bug in 149 days, in which
time the Reproducible Builds effort has come on a long way.

Would you consider applying this patch and uploading?


Regards,

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

Bug#946331: gtk-doc: please make the output reproducible

[Chris Lamb]

Chris Lamb wrote:

> Would you consider applying this patch and uploading?

Friendly ping on this? Seems like there hasn't been any update on this bug in
261 days now (!).


Regards,

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

Bug#953646: node-nodedbi: please make the build reproducible

[Chris Lamb]

Chris Lamb wrote:

> Would you consider applying this patch and uploading?

Friendly ping on this? Seems like there hasn't been any update on this bug in
182 days now (!).


Regards,

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

Bug#970057: ITP: r-cran-ggseqlogo -- ggplot2 Extension for Publication-Ready Sequence Logos

[Steffen Moeller]

Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-ggseqlogo -- ggplot2 Extension for Publication-Ready 
Sequence Logos
Package: wnpp
Owner: Steffen Moeller 
Severity: wishlist

* Package name: r-cran-ggseqlogo
  Version : 0.1
  Upstream Author : Omar Wagih
* URL : https://cran.r-project.org/package=ggseqlogo
* License : LGPL-2
  Programming Lang: GNU R
  Description : ggplot2 Extension for Publication-Ready Sequence Logos
 The extensive range of functions provided by this package makes it
 possible to draw highly versatile sequence logos.  Features include,
 but not limited to, modifying colour schemes and fonts used to draw the
 logo, generating multiple logo plots, and aiding the visualisation with
 annotations. Sequence logos can easily be combined with other plots
 'ggplot2' plots.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-ggseqlogo

Bug#970056: ITP: r-cran-ggalluvial -- Alluvial Plots in 'ggplot2'

[Steffen Moeller]

Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-ggalluvial -- Alluvial Plots in 'ggplot2'
Package: wnpp
Owner: Steffen Moeller 
Severity: wishlist

* Package name: r-cran-ggalluvial
  Version : 0.12.2
  Upstream Author : Jason Cory Brunson
* URL : https://cran.r-project.org/package=ggalluvial
* License : GPL-3
  Programming Lang: GNU R
  Description : Alluvial Plots in 'ggplot2'
 Alluvial plots use variable-width ribbons and stacked bar plots to
 represent multi-dimensional or repeated-measures data with categorical or
 ordinal variables; see Riehmann, Hanfler, and Froehlich (2005)
  and Rosvall and Bergstrom (2010)
 .
 Alluvial plots are statistical graphics in the sense of Wilkinson (2006)
 ; they share elements with Sankey diagrams and
 parallel sets plots but are uniquely determined from the data and a small
 set of parameters. This package extends Wickham's (2010)
  layered grammar of graphics to generate
 alluvial plots from tidy data.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-ggalluvial

Bug#970055: New upstream version 2.46 - please package

[Marc Meledandri]

Package: keepass2
Version: 2.45+dfsg-1

Dear Maintainer,

Please package KeePass 2.46. List of fixes and improvements:
https://keepass.info/news/n200910_2.46.html

Thanks!

Bug#970054: fwupd: Missing Depends (or Recommends) on udisks2 for UEFI update

[Jochen Sprickerhof]

Package: fwupd
Version: 1.4.6-1
Severity: normal

Hi,

starting with 1.4.6 (or 25ba4157) fwupdmgr connects to
/org/freedesktop/UDisks2/Manager to get the ESP. You can see this by
running

dbus-monitor --system

while doing a

fwupdtool esp-list

with out udisks2 installed I get a segfault and fwupdmgr does not opt to
update the UEFI. I proposed a fix to the segfault here:

https://github.com/fwupd/fwupd/pull/2384

Still there should be a dependency on udisks2 (or a way to work without
it).

Cheers Jochen

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

Kernel: Linux 5.8.0-1-amd64 (SMP w/8 CPU threads)
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 fwupd depends on:
ii  libc6  2.31-3
ii  libefiboot137-5
ii  libefivar1 37-5
ii  libelf10.180-1+b1
ii  libflashrom1   1.2-5
ii  libfwupd2  1.4.6-1
ii  libfwupdplugin11.4.6-1
ii  libglib2.0-0   2.64.4-1
ii  libgudev-1.0-0 233-1
ii  libgusb2   0.3.4-0.2
ii  libjcat1   0.1.3-2
ii  libjson-glib-1.0-0 1.4.4-2
ii  libpolkit-gobject-1-0  0.105-29
ii  libsmbios-c2   2.4.3-1
ii  libsoup2.4-1   2.70.0-1
ii  libsqlite3-0   3.33.0-1
ii  libtss2-esys0  3.0.0-1
ii  libxmlb1   0.1.15-2
ii  shared-mime-info   1.15-1

Versions of packages fwupd recommends:
pn  bolt  
pn  fwupd-signed  
ii  python3   3.8.2-3

fwupd suggests no packages.

-- no debconf information

Bug#970053: ITP: r-cran-upsetr -- A More Scalable Alternative to Venn and Euler Diagrams for

[Steffen Moeller]

Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-upsetr -- A More Scalable Alternative to Venn and Euler 
Diagrams for
Package: wnpp
Owner: Steffen Moeller 
Severity: wishlist

* Package name: r-cran-upsetr
  Version : 1.4.0
  Upstream Author : Jake Conway,
* URL : https://cran.r-project.org/package=UpSetR
* License : MIT
  Programming Lang: GNU R
  Description : A More Scalable Alternative to Venn and Euler Diagrams for
   Visualizing Intersecting Sets
 Creates visualizations of intersecting sets using a novel matrix
 design, along with visualizations of several common set, element and attribute
 related tasks (Conway 2017) .

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-upsetr

Bug#961862: debrebuild: should assemble the source for binNMUs

[Holger Levsen]

On Sat, Aug 29, 2020 at 11:15:11AM +0200, Niels Thykier wrote:
[...]

as discussed on irc, I think debrebuild should automatically imply
the --download-sources option if a .buildinfo file from a binNMU
is given...


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

There are no jobs on a dead planet. (Also many other things but people mostly
seem to care about jobs.)


signature.asc
Description: PGP signature

Bug#969592: sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

forwarded 969592 https://gitlab.com/sane-project/backends/-/issues/352
thanks


Hello Sebastian,

the version 1.0.31-1~experimental1 was build successful on armel and armhf.But
qcam wasn't build. So I forward this bug to upstream.


CU
Jörg 


- -- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl9alPAACgkQCfifPIyh
0l01Qw/8DTpeg9WfVZDd2fS7Sd1rccGNfM4fJ2+nbRNzfEOHQrfvD0SO+Oiv6T2d
swDqw/gKYuoSDeZh/hO1bkWXn/rsEQPj1jsU5bAF2k22UqZD733EugmzKk1a+kWC
qyglt/sN4AUIX50K+WsFrGfDSYcJ/Yy/uGrWbiuHy4w/rRya+qzIiXm/MjchGvRJ
ORNkoVC66lXHAUR3elLsttRALOo9E5r7HUgPtBthvwasdjL7g3qQC8IbhWjb5OL8
QjJ361X150hbxFWa/HcBUNFkgihtSak/AFeElfkUaEjwjliDjz6Kl+aEdasUDIfc
9fluf1EoBzOFA2zXWo100F9b888TbCNq6cEpH345ZYoCKcoe5gGJvfbrtMO5IkCN
PBi4mRmIieHS+03EKkgTitD84jzEr19N+as4dkB8yc+GfOJVKAFPFwhcZMxivZLM
ITg2xESSlUt5CQgF5UArCkFW7MuuQsnfuGsO+S2rL8XIVeWwgxGCD7lMYfT39Crw
KgGF9bc+nVXSqf0PTtkoLSOM9LzSNZsvj3Hl2TNLGkW9o9xJb6Z1m9Py/yPd/tlu
KfzByorTKLy4dc40RxZKBylmVrQiFoA7EGDfSyQ3JJx3r/gVuedgIzoZetTMI6qp
QyC34Vy5B9i2hEZHoaAzF39qzqKahR0GAls8kHumJb6260Rxi8Y=
=wQwI
-END PGP SIGNATURE-

Bug#970052: nm.debian.org: Wrong text on DAM approval page

[Joerg Jaspert]

Package: nm.debian.org
Severity: normal

Dear Maintainer,

on the DAM approval "add" page it tells me "The statement will be sent 
to debian-newmaint list as jo...@debian.org"


Nah, its not. Its going to RT.

--
bye, Joerg


signature.asc
Description: PGP signature

Bug#966088: mailinglist debian-r...@lists.debian.org

[Geert Stappers]

Hello Listmasters,


And hello pkg-rust-maintainers mailinglist subscribers,

On Thu, Sep 10, 2020 at 09:58:51PM +0200, Alexander Wirt wrote:
> Please provide us with the information described in
> https://www.debian.org/MailingLists/HOWTO_start_list (Description,
> Category and so on).

Basic purpose: 
  Email discussion channel for Rust in Debian.

(Secundaire purpose:
  Preventing that humans get flooded
  by all the automatic emails from builds and such)

Interested audience:
  People interested in Rust and Debian
  plus the overlap they both have.


> Unless you come up with at least 3 moderators we will create the list
> as on open list (which we prefer anyhow).

Reporting myself for moderator duty.   :-)
E-mail address:  stapp...@stappers.nl
so others wanting to help with this
don't feel the hurdle of having a   @debian.org address.

Wednesday september 23th is a meeting in #debian-rust
there I want get consensus for open list versus moderated list

So accept next contact after that monthly meeting.

Meanwhile we, debian-rust team, will check for apetide
on moderation or open list.


Thank you for making it possible.



Regards
Geert Stappers
Debian Developer

P.S.
The Cc: to pkg-rust-maintain...@alioth-lists.debian.net
is for asking more moderators.
And a way for voting   "open list"  versus "moderated list"
-- 
Silence is hard to parse


signature.asc
Description: PGP signature

Bug#866945: tinymux: please make the build reproducible

[Stephen Dennis]

Yes. This is obviously a good thing. I'll include it in my pending mentors
submission.

On Wed, Sep 9, 2020 at 5:09 PM Chris Lamb  wrote:

> Dear Maintainer,
>
> > Source: tinymux
> > Version: 2.10.1.14-1
> > Tags: patch
>
> There hasn't seem to be any update on this bug in 1164 days, in which
> time the Reproducible Builds effort has come on a long way.
>
> Would you consider applying this patch and uploading?
>
>
> Regards,
>
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-
>

Bug#970051: gr-gsm: FTBFS on mips64el

[Sebastian Ramacher]

Source: gr-gsm
Version: 0.42.2.20200214-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)

The rebuild of gr-gsm for the gnuradio transition failed to build on
mips64el:
| 14/19 Test #14: qa_tch_f_chans_demapper ***Failed1.31 sec
| .F
| ==
| FAIL: test_sacch_tf (__main__.qa_tch_f_chans_demapper)
| SACCH/TF tests
| --
| Traceback (most recent call last):
|   File "/<>/python/qa_tch_f_chans_demapper.py", line 147, in 
test_sacch_tf
| self.assertEqual(odd,  self.sacch_fr_test(ts=3, frames=[38, 51, 64, 77, 
90, 103, 116, 129], bursts=bursts))
| AssertionError: Lists differ: ['010[445 chars]', 
'000100[107 chars]000'] != ['010[445 
chars]']
|
| First list contains 1 additional elements.
| First extra element 3:
| 
'0001'
|
| Diff is 1087 characters long. Set self.maxDiff to None to see it.
|
| --
| Ran 2 tests in 0.085s
|
| FAILED (failures=1)
|
|   Start 15: qa_tch_h_chans_demapper
| 15/19 Test #15: qa_tch_h_chans_demapper    Passed1.42 sec
|   Start 16: qa_gsm_bcch_ccch_demapper
| 16/19 Test #16: qa_gsm_bcch_ccch_demapper ..   Passed1.85 sec
|   Start 17: qa_gsm_bcch_ccch_sdcch4_demapper
| 17/19 Test #17: qa_gsm_bcch_ccch_sdcch4_demapper ...   Passed1.85 sec
|   Start 18: qa_gsm_sdcch8_demapper
| 18/19 Test #18: qa_gsm_sdcch8_demapper .   Passed1.85 sec
|   Start 19: qa_txtime_setter
| 19/19 Test #19: qa_txtime_setter ...   Passed1.21 sec
|
| 95% tests passed, 1 tests failed out of 19
|
| Total Test time (real) =  25.60 sec
|
| The following tests FAILED:
|14 - qa_tch_f_chans_demapper (Failed)
| Errors while running CTest
| make[2]: *** [Makefile:152: test] Error 8

See
https://buildd.debian.org/status/fetch.php?pkg=gr-gsm&arch=mips64el&ver=0.42.2.20200214-1%2Bb3&stamp=1599727226&raw=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#970050: haskell-gi-gtk: FTBFS: ghc: out of memory (requested 1048576 bytes)

[Sebastian Ramacher]

Source: haskell-gi-gtk
Version: 3.0.36-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)

haskell-gi-gtk failed to build on armhf:
| [472 of 504] Compiling GI.Gtk.Objects.TextTagTable ( 
GI/Gtk/Objects/TextTagTable.hs, dist-ghc/build/GI/Gtk/Objects/TextTagTable.o )
| [473 of 504] Compiling GI.Gtk.Objects.TextBuffer ( 
GI/Gtk/Objects/TextBuffer.hs, dist-ghc/build/GI/Gtk/Objects/TextBuffer.o )
| ghc: out of memory (requested 1048576 bytes)
| make: *** [/usr/share/cdbs/1/class/hlibrary.mk:147: build-ghc-stamp] Error 251
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

See 
https://buildd.debian.org/status/fetch.php?pkg=haskell-gi-gtk&arch=armhf&ver=3.0.36-1&stamp=1599676696&raw=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#970049: ipwatchd FTCBFS: does not pass cross tools to make

[Helmut Grohne]

Source: ipwatchd
Version: 1.2.1-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

ipwatchd fails to cross build from source, because it does not pass
cross tools to make. The easiest way of doing so - using dh_auto_build -
makes ipwatchd cross buildable. Please consider applying the attached
patch.

Helmut
diff --minimal -Nru ipwatchd-1.2.1/debian/changelog 
ipwatchd-1.2.1/debian/changelog
--- ipwatchd-1.2.1/debian/changelog 2011-07-24 21:08:59.0 +0200
+++ ipwatchd-1.2.1/debian/changelog 2020-09-10 22:21:29.0 +0200
@@ -1,3 +1,10 @@
+ipwatchd (1.2.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 10 Sep 2020 22:21:29 +0200
+
 ipwatchd (1.2.1-1) unstable; urgency=low
 
   * Updated to upstream release 1.2.1
diff --minimal -Nru ipwatchd-1.2.1/debian/rules ipwatchd-1.2.1/debian/rules
--- ipwatchd-1.2.1/debian/rules 2011-07-24 21:51:47.0 +0200
+++ ipwatchd-1.2.1/debian/rules 2020-09-10 22:21:20.0 +0200
@@ -9,7 +9,7 @@
 
 build-stamp: 
dh_testdir
-   $(MAKE) -C src
+   dh_auto_build --sourcedirectory=src
touch $@
 
 # Added just to remove lintian warning debian-rules-missing-recommended-target

Bug#970047: RFS: xsd/4.0.0-9 [RC] -- XML Data Binding for C++

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: sponsorship-requests
Severity: important

Dear mentors,

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

   Package name: xsd
   Version : 4.0.0-9
   Upstream Author : xsd-user Maillist 
   URL : http://codesynthesis.com
   License : public-domain, GFDL-1.2, GPL-2+ and FLOSS
   Vcs : https://jff.email/cgit/xsd.git/
   Section : devel

It builds those binary packages:

  xsdcxx - XML Data Binding for C++

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

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

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

 dget -x https://mentors.debian.net/debian/pool/main/x/xsd/xsd_4.0.0-9.dsc

or from 

 git https://jff.email/cgit/xsd.git/?h=release%2Fdebian%2F4.0.0-9


Changes since the last upload:

 xsd (4.0.0-9) unstable; urgency=medium
 .
   * Fix FTBFS with gcc-10 (Closes: #957999):
 - New debian/patches/0120-g++10.patch.
   * Migrate to debhelper 13:
 - Bump minimum debhelper-compat version in debian/control to = 13.
   * Fix FTCBFS: Use dpkg's buildtools.mk to export tools for make
 install. (Closes: #955728). Thanks to Helmut Grohne .
   * Declare compliance with Debian Policy 4.5.0 (No changes needed).
   * Use jdupes to change duplicate files into symlinks:
 - debian/rules: Add override_dh_link.
 - debian/control: Add Build-Depend jdupes.
 - debian/xsdcxx.lintian-overrides: Remove duplicate-files.
   * Switch to debhelper-compat:
 - debian/control: Replace debhelper with debhelper-compat.
 - Remove debian/compat.
   * debian/control:
 - Switch Vcs-* to new location.
 - Add Rules-Requires-Root: no.
   * debian/copyright:
 - Add year 2020 to debian/*.
 - Use secure URI.
 - Change Source to directory listing.
 - Add paragraph for FLOSS.
 - Fix lintian *-globbing-patterns errors.
   * debian/changelog:
 - Remove EOL before EOF.


CU
Jörg


- -- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl9ajH0ACgkQCfifPIyh
0l39RQ//a9gYhyduaGa2YBuApNPlIdmhgCueFRF9+aSc0oa8hR4Ac+49kwB2taJx
TJ0e/GJESnW1arhW9UzcxFGSTFmSojLAF4aDCIItzjtLoNdhmTRg6c6Imf6sQ6rE
eZRAzWrEU6iQ8+I7Snx/DH06EL5SIGK3vSq5zG9TuHG5+vTDX4Nelp/7wrXyN2u+
X6nbxVjdXg082s7YPAPxhSs9soz9IpcwnejNhURL8uBktE99xvoR6mzeWpr2JYVb
E4EEv02nbLkZnNXfX0axdtYs8XzEHfXwN1nHBD6qQdxCjtB2f4B6BBZzUKwjGZcQ
20Kv3CKZweUC8wD/zgJaEpfYFdgS0m7Vkp6t3Z/ydWi8mwTuo+kDbg0+XEwP4m7g
oiVNqIUtL1T2ln/lfLYdMGGwm993MLsK/rDo0SEESAEAcCnIDUsKw30O+bdbwR9g
pyCN4jI9QJmEmChRZpunjTNBYEVDimiwXcG4f/NH+ZMd5InWPtnci2Y7jknQf50/
k3F7CrdQ5HraIvuoGjRbHplp4sB2p5pkvcFh284hlH+oj2NiNUgzLvnxdpL3a2Om
Zf/ASFd8QwR0iUY5errUsSw7WddcWxxdHPdf0eX/DpOVSaBtMJhWq6kgzbXUhs6D
6pcqtu/RryNJL/XFLTg2zEkuCAKtIhbHYUYituNsGKdfMi74hNk=
=jxF7
-END PGP SIGNATURE-

Bug#970048: binfmtc FTCBFS: builds for the build architecture

[Helmut Grohne]

Source: binfmtc
Version: 0.17-2
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

binfmtc fails to cross build from source, because it configures for the
build architecture. The easiest way of passing the relevant --host flag
is using dh_auto_configure. Even then, the build fails during
installation as the packaging passes -s to install and it uses the build
architecture strip by default. Beyond breaking cross compilation, this
also breaks generation of -dbgsym packages. dh_strip already takes care
of stripping and handling DEB_BUILD_OPTIONS=nostrip. Simply skipping it
at the installation phase is the way to go. Please consider applying the
attached patch to fix all mentioned issues.

Helmut
diff -u binfmtc-0.17/debian/changelog binfmtc-0.17/debian/changelog
--- binfmtc-0.17/debian/changelog
+++ binfmtc-0.17/debian/changelog
@@ -1,3 +1,12 @@
+binfmtc (0.17-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Let dh_auto_configure pass --host to ./configure.
++ Defer stripping to dh_strip.
+
+ -- Helmut Grohne   Thu, 10 Sep 2020 22:24:22 +0200
+
 binfmtc (0.17-2) unstable; urgency=medium
 
   * Update debheper compat level 9, and check with debdiff.
diff -u binfmtc-0.17/debian/rules binfmtc-0.17/debian/rules
--- binfmtc-0.17/debian/rules
+++ binfmtc-0.17/debian/rules
@@ -17,16 +17,12 @@
 else
 CFLAGS += -O2
 endif
-ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
-INSTALL_PROGRAM += -s
-endif
-
 
 configure: configure-stamp
 configure-stamp:
dh_testdir
INSTALL_PROGRAM='${INSTALL_PROGRAM}' CFLAGS='${CFLAGS}' \
-./configure --prefix=/usr --mandir=/usr/share/man
+dh_auto_configure
touch configure-stamp
 
 build: build-stamp

Bug#969592: sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25

[Sebastian Ramacher]

Control: tags -1 - moreinfo

On 2020-09-10 18:37:24 +0200, Jörg Frings-Fürst wrote:
> tags 969592 +moreinfo
> thanks
> 
> Hello Sebastian,
> 
> from the log I see 
> 
> *** qcam backend requires (ioperm, inb and outb) or portaccess functions -
> disabling
> 
> which comes through  
> 
> checking for ioperm... no
> checking for i386_set_ioperm... no
> 
> I don't have a arm* machine for checking this. But I think that the kernel
> dosn't support ioperm() at buildtime. 

glibc removed support for ioperm on arm in 2.30:
https://github.com/bminor/glibc/commit/6b33f373c7b9199e00ba5fbafd94ac9bfb4337b1

Cheers

> 
> 
> CU 
> Jörg
> 
> 
> Am Samstag, den 05.09.2020, 18:11 +0200 schrieb Sebastian Ramacher
> > Source: sane-backends
> > Version: 1.0.27-3.2
> > Severity: serious
> > Tags: ftbfs sid bullseye
> > Justification: fails to build from source (but built successfully in the 
> > past)
> > 
> > sane-backends FTBFS on armel and armhf:
> > > @@ -7204,7 +7151,7 @@
> > >   sanei_pp_outb_addr@Base 1.0.25
> > >   sanei_pp_outb_ctrl@Base 1.0.25
> > >   sanei_pp_outb_data@Base 1.0.25
> > > - sanei_pp_outb_epp@Base 1.0.25
> > > +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25
> > >   sanei_pp_release@Base 1.0.25
> > >   sanei_pp_set_datadir@Base 1.0.25
> > >   sanei_pp_setmode@Base 1.0.25
> > > dh_makeshlibs: error: failing due to earlier errors
> > > make[1]: *** [debian/rules:139: override_dh_makeshlibs-arch] Error 25
> > > make[1]: Leaving directory '/<>'
> > > make: *** [debian/rules:25: binary-arch] Error 2
> > 
> > See
> > https://buildd.debian.org/status/fetch.php?pkg=sane-backends&arch=armel&ver=1.0.27-3.2%2Bb2&stamp=1599315993&raw=0
> > 
> > Cheers
> -- 
> New:
> GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
> GPG key (long) : 09F89F3C8CA1D25D
> GPG Key: 8CA1D25D
> CAcert Key S/N : 0E:D4:56
> 
> Old pgp Key: BE581B6E (revoked since 2014-12-31).
> 
> Jörg Frings-Fürst
> D-54470 Lieser
> 
> 
> git:  https://jff.email/cgit/
> 
> Threema:  SYR8SJXB
> Wire: @joergfringsfuerst
> Skype:joergpenguin
> Ring: jff
> Telegram: @joergfringsfuerst
> 
> 
> My wish list: 
>  - Please send me a picture from the nature at your home.
> 
> 

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#969606: bilibop: lockfs autopkgtest is not portable, consistently fails in Ubuntu

[quidame]

Hi Steve,

> [...]
> # df --output=source,fstype,target
> Filesystem Type Mounted on
> udev   devtmpfs /dev
> tmpfs  tmpfs/run
> tmpfs  tmpfs/aufs/rw
> /dev/vda1  ext4 /aufs/ro
> aufs   aufs /
> tmpfs  tmpfs/dev/shm
> tmpfs  tmpfs/run/lock
> tmpfs  tmpfs/sys/fs/cgroup
> tmpfs  tmpfs/aufs/rw/boot/efi
> /dev/vda15 vfat /aufs/ro/boot/efi
> aufs   aufs /boot/efi
> tmpfs  tmpfs/run/user/1000

sounds good, until there...

> STAGE 1: unexpected error

you're right, there is a lack of portability in the autopkgtest script:
only 'overlay' is expected somewhere, not 'aufs', and so the test script
fails even if the bootscripts did the job.

This will be fixed soon.

Thank you for this report.
quidame



signature.asc
Description: OpenPGP digital signature

Bug#946979: lists.debian.org: Have a mailing list archive for the JavaScript team.

[Alexander Wirt]

On Thu, Dec 19, 2019 at 12:35:18AM +0530, Utkarsh Gupta wrote:
> Package: lists.debian.org
> Severity: wishlist
> 
> Hiya,
> 
> The JavaScript team is still using the old archive (that is,
> alioth-lists.debian.net) which gets very messy and noisy since there are
> a lot (hundres each month) of auto-generated emails from the FTP Masters.
> Moreover, all the other teams have switched to
> lists.debian.org/debian-.
> 
> That said, I hereby request a slot for the JavaScript team, that is,
> debian...@lists.debian.org.
> Thank you :)
Please follow the instructions in 
https://www.debian.org/MailingLists/HOWTO_start_list
and provide me with the needed information (Name, Rationale,
Descriptions and so on). 

Alex

Bug#966088: mailinglist debian-r...@lists.debian.org

[Alexander Wirt]

On Wed, Jul 22, 2020 at 11:16:47PM +0200, Geert Stappers wrote:
> Package: lists.debian.org
> Severity: wishlist
> 
> 
> Hello Listmasters,
> 
> The rust packaging team is in need for a mailinglist for human
> interaction.
> 
> The ML pkg-rust-maintain...@alioth-lists.debian.net is getting more and
> more automated traffic due the succes of the team. Downside is the human
> messages are flooded. Hence this request.
> 
> 
> I volunteering for moderator of debian-r...@lists.debian.org or/and
> taking responseblity for this new mailinglist.
> 
> 
> If I recall correct is a request from a single person is not enough
> for getting an ML created. So I'll share the bugreportnumber
> with rust team members and ask for "votes" on this BR.
Please provide us with the information described in
https://www.debian.org/MailingLists/HOWTO_start_list (Description,
Category and so on). Unless you come up with at least 3 moderators we
will create the list as on open list (which we prefer anyhow).

Alex

Bug#905456: Please create new list debian-clojure

[Alexander Wirt]

Hi,

> I realize that alioth-lists.debian.net is only a temporary service and
> will be going away within the next couple of years[1]. It would be
> better to move the Clojure packaging list
>  sooner versus later.
> I'm currently the admin of that list.
> 
> This has been proposed as part of our team's overall Alioth
> migration[2].
> 
> The details...
> 
> Name: debian-cloj...@lists.debian.org
> Rationale: see above
> Short description: Clojure packages and maintenance
> Long description: Coordination of the maintenance of Clojure packages
> in Debian.
> Category: Developers
> Subscription Policy: open
> Post Policy: open
> Web Archive: yes
> Moving an existing list: Attachment has an encrypted list of current
> subscribers in the correct format (one email per line). I
> encrypted it for Alex's key as he is listed as responsible for
> list creation.[3]
Sorry for joining late. Could you please upgrade the list of subscribers
and provide me with the archive of the old alioth list?

Thanks in advance

Alex

Bug#970046: ITP: r-cran-formattable -- GNU R create 'formattable' data structures

[Andreas Tille]

Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-formattable -- GNU R create 'formattable' data structures
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: r-cran-formattable
  Version : 0.2.0.1
  Upstream Author : Kun Ren,
* URL : https://cran.r-project.org/package=formattable
* License : MIT
  Programming Lang: GNU R
  Description : GNU R create 'formattable' data structures
 Provides functions to create formattable vectors and data frames.
 'Formattable' vectors are printed with text formatting, and formattable
 data frames are printed with multiple types of formatting in HTML
 to improve the readability of data presented in tabular form rendered in
 web pages.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-formattable

Bug#970045: galera-4: Use user "_galera" instead of "nobody" to run the daemon

[Otto Kekäläinen]

Source: galera-4
Version: 26.4.5-1
Severity: wishlist

Using nobody and nogroup is currently discouraged:
>The specified systemd service file declares a User= or Group= that references 
>nobody or nogroup.
> This is discouraged, and systemd versions 246 and above will log a warning 
> about this.
https://lintian.debian.org/tags/systemd-service-file-uses-nobody-or-nogroup.html

W systemd-service-file-uses-nobody-or-nogroup
lib/systemd/system/garb.service User=nobody
W systemd-service-file-uses-nobody-or-nogroup
lib/systemd/system/garbd.service User=nobody

According to 
https://www.debian.org/doc/debian-policy/ch-opersys.html#users-and-groups
it seems the proper solution would be to have a new user "_galera" for
this daemon instead.

Bug#969931: ITP: bpfmon -- BPF based visual packet rate monitor

[Boian Bonev]

Initial packaging is done and uploaded to mentors.d-n

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

Bug#969927: ITP: yascreen -- Yet Another Screen Library (curses replacement for daemons and embedded apps)

[Boian Bonev]

Initial packaging is done and uploaded to mentors.d-n

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

Bug#913542: teckit: Fails to build on Ubuntu's ppc64el (symbols)

[Hilmar Preuße]

Control: tags -1 - patch



signature.asc
Description: OpenPGP digital signature

Bug#961841: fontforge FTBFS on 64bit big endian: test failures

[John Paul Adrian Glaubitz]

Hello!

This bug blocks a couple of packages from being built on big-endian targets
in Debian Ports and also causes the package to be still affected by an
RC for too long.

Any chance this can be fixed the next days? Apparently the necessary changes
have already been merged in Salsa.

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#970044: galera-4: FTBFS on hppa: Failure 'uuid == WSREP_UUID_UNDEFINED' occurred

[Otto Kekäläinen]

Source: galera-4
Version: 26.4.5-1
Severity: normal
Justification: unofficial architecture
User: debian-h...@lists.debian.org
Usertags: hppa
Forwarded: https://github.com/codership/galera/issues/558

The hppa build at
https://buildd.debian.org/status/fetch.php?pkg=galera-4&arch=hppa&ver=26.4.5-1%2Bb1&stamp=1596453402&raw=0
failed with

***
33%: Checks: 3, Failures: 1, Errors: 1
galera/tests/saved_state_check.cpp:47:E:saved_state:test_unsafe:0:
(after this point) Test timeout expired
galera/tests/saved_state_check.cpp:162:F:saved_state:test_corrupt:0:
Failure 'uuid == WSREP_UUID_UNDEFINED' occurred
***

Help from hppa experts on why this happens on hppa but not other
platforms would be appreciated.

Contributions are welcome in this bug report or via Salsa:
https://wiki.debian.org/Teams/MySQL/patches

Bug#913542: teckit: Fails to build on Ubuntu's ppc64el (symbols)

[Hilmar Preuße]

tags -1 - patch

Am 12.11.2018 um 03:12 teilte Jeremy Bicha mit:

Hi Jeremy,

> teckit fails to build on Ubuntu's ppc64el because the symbols don't
> match. A few symbols are added and several are missing.
> 
> Notably, Ubuntu's ppc64el uses -O3 by default which occasionally leads
> to symbols differences compared to all other release architectures
> which default to -O2.
> 
We stopped provide a symbols files, instead we use shlibs now. Does that
eventually solve your issue? Remove the tag patch for now.

H.
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

Bug#970042: galera-4: FTBFS on powerpc: R_PPC_REL24 relocation at 0x00b16a7c for symbol `strcmp' out of range

[Otto Kekäläinen]

Source: galera-4
Version: 26.4.5-1
Severity: normal
Justification: unofficial architecture
User: debian-powe...@lists.debian.org
Usertags: powerpc
Forwarded: https://github.com/codership/galera/issues/558

The powerpc build at
https://buildd.debian.org/status/fetch.php?pkg=galera-4&arch=powerpc&ver=26.4.5-1&stamp=1595636409&raw=0
fails with

***
g++ -o gcache/src/GCache_memops.os -c -Wold-style-cast -Weffc++
-std=c++11 -pipe -Wno-long-long -Wno-deprecated -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -g -O3 -DNDEBUG -pthread -fPIC -Wall
-Wextra -Wno-unused-parameter -fPIC -Wdate-time -D_FORTIFY_SOURCE=2
-D_XOPEN_SOURCE=600 -DHAVE_COMMON_H -DGALERA_USE_GU_NETWORK
-DHAVE_BYTESWAP_H -DHAVE_ENDIAN_H -DHAVE_EXECINFO_H -DHAVE_STD_ARRAY
-DHAVE_BOOST_SHARED_PTR_HPP -DHAVE_STD_UNORDERED_MAP
-DBOOST_DATE_TIME_POSIX_TIME_STD_CONFIG=1 -DHAVE_ASIO_HPP
-DOPENSSL_HAS_SET_ECDH_AUTO -Iasio -Iwsrep/src -Icommon
-Igalerautils/src gcache/src/GCache_memops.cpp
builder_unit_test(["galerautils/tests/gu_tests++.passed"],
["galerautils/tests/gu_tests++"])
/<>/galerautils/tests/gu_tests++: error while loading
shared libraries: R_PPC_REL24 relocation at 0x00b16a7c for symbol
`strcmp' out of range
scons: *** [galerautils/tests/gu_tests++.passed] Error 1
***

Help from powerpc experts on why this happens on powerpc but not other
platforms would be appreciated.

Contributions are welcome in this bug report or via Salsa:
https://wiki.debian.org/Teams/MySQL/patches

Bug#970041: galera-4: FTBFS on sparc64: Received signal 10 (Bus error)

[Otto Kekäläinen]

Source: galera-4
Version: 26.4.5-1
Severity: normal
Justification: unofficial architecture
User: debian-i...@lists.debian.org
Usertags: sparc64
Forwarded: https://github.com/codership/galera/issues/558

The sparc64 build at
https://buildd.debian.org/status/fetch.php?pkg=galera-4&arch=sparc64&ver=26.4.5-1&stamp=1593565379&raw=0
failed with

***
Running suite(s): DataSet
0%: Checks: 2, Failures: 0, Errors: 2
galera/tests/data_set_check.cpp:243:E:DataSet:ver1:0: (after this
point) Received signal 10 (Bus error)
galera/tests/data_set_check.cpp:143:E:DataSet:ver2:0: (after this
point) Received signal 10 (Bus error)
Running suite(s): KeySet
0%: Checks: 4, Failures: 0, Errors: 4
galera/tests/key_set_check.cpp:54:E:KeySet:ver1_3:0: (after this
point) Received signal 10 (Bus error)
galera/tests/key_set_check.cpp:235:E:KeySet:ver2_3:0: (after this
point) Received signal 10 (Bus error)
galera/tests/key_set_check.cpp:235:E:KeySet:ver2_4:0: (after this
point) Received signal 10 (Bus error)
galera/tests/key_set_check.cpp:235:E:KeySet:ver2_5:0: (after this
point) Received signal 10 (Bus error)
Running suite(s): WriteSet
60%: Checks: 5, Failures: 0, Errors: 2
galera/tests/write_set_ng_check.cpp:83:E:WriteSet
basic:ver3_basic_rsv1:0: (after this point) Received signal 10 (Bus
error)
galera/tests/write_set_ng_check.cpp:307:E:WriteSet
annotation:ver3_annotation_rsv1:0: (after this point) Received signal
10 (Bus error)
Running suite(s): certification
100%: Checks: 5, Failures: 0, Errors: 0
Running suite(s): trx_handle
100%: Checks: 4, Failures: 0, Errors: 0
Running suite(s): service_thd
100%: Checks: 3, Failures: 0, Errors: 0
Running suite(s): ist
100%: Checks: 2, Failures: 0, Errors: 0
Running suite(s): saved_state
100%: Checks: 3, Failures: 0, Errors: 0
Running suite(s): Defaults
100%: Checks: 1, Failures: 0, Errors: 0
Total tests failed: 8
scons: *** [galera/tests/galera_check.passed] Error 1
scons: building terminated because of errors.
***

Help from sparc64 experts on why this happens on sparc64 but not other
platforms would be appreciated.

Contributions are welcome in this bug report or via Salsa:
https://wiki.debian.org/Teams/MySQL/patches

Bug#970043: galera-4: FTBFS on ia64: [libgalera_smm.so] Error 1

[Otto Kekäläinen]

Source: galera-4
Version: 26.4.5-1
Severity: normal
Justification: unofficial architecture
User: debian-i...@lists.debian.org
Usertags: ia64
Forwarded: https://github.com/codership/galera/issues/558

The ia64 build at
https://buildd.debian.org/status/fetch.php?pkg=galera-4&arch=ia64&ver=26.4.5-1&stamp=1593485338&raw=0
failed with

***
Checking dynamic symbols for 'libgalera_smm.so'...
000f1a80 lDF .text 0010
_ZN4asio6detail10service_idINS0_13epoll_reactorEED1Ev
00305980 lDF .text 00d0
_ZN4asio3ssl6detail6engine9do_acceptEPvm

000612c0 lDF .text 18c0
_GLOBAL__sub_I_asio_tcp.cpp
00055400 lDF .text 1500
_GLOBAL__sub_I_gu_asio.cpp
000e6040 lDF .text 00a0
_ZN4asio3ssl6detail17password_callbackIN5boost3_bi6bind_tINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEENS3_4_mfi4cmf0ISB_N12_GLOBAL__N_119SSLPasswordCallbackEEENS4_5list1INS4_5valueIPSF_EEE4callEmNS0_12context_base16password_purposeE
scons: *** Error 1
scons: *** [libgalera_smm.so] Error 1
scons: building terminated because of errors.
***

Help from ia64 experts on why this happens on ia64 but not other
platforms would be appreciated.

Contributions are welcome in this bug report or via Salsa:
https://wiki.debian.org/Teams/MySQL/patches

Bug#965219: Recipe for reproduction

[Paul Gevers]

Hi all,

On Fri, 17 Jul 2020 21:05:16 +0200 Antoni Villalonga 
wrote:> Package: dbconfig-common

> It worked fine before, at 2.0.11 version.

Interesting. I don't think anything changed in this area between 2.0.11
and 2.0.13, which were MySQL and translation changes.

On 10-09-2020 12:58, Thomas Braun wrote:
> I can reproduce the problem when upgrading the tango-db package from
> unstable to the one from experimental.

So, thanks for the report and the reproducer. I'll try to look into it soon.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#920483: The keyboard layout displays “us” whatever the current layout until a key is pressed

[Dennis Filder]

Control: tags -1 patch

The attached patch fixed the issue for me for 0.18.0-1, but should
also work for 0.18.1-1.  It requires 2 additional dependencies on
x11-xkb-utils and xinput.

Regards,
Dennis.Description: Set keymaps for virtual devices before login prompt.
 For this to work Depends: on x11-xkb-utils and xinput are needed.
Author: Dennis Filder 
Bug-Debian: https://bugs.debian.org/920483
Last-Update: 2020-09-10
--- a/sddm-0.18.1/data/scripts/Xsetup
+++ b/sddm-0.18.1/data/scripts/Xsetup
@@ -1,3 +1,19 @@
 #!/bin/sh
 # Xsetup - run as root before the login dialog appears

+# Here we have to set the keymap of virtual keyboards to that of the
+# first-found physical one since the X server doesn't (#920483).
+#
+# This is also important for autologin setups in combination with
+# programs that take a snapshot of the current keymap to restore it
+# later (e.g. Orca).
+if [ -x /usr/bin/setxkbmap -a -x /usr/bin/xinput ]; then
+PHYNAME="$(xinput --list --name-only | grep keyboard | grep -v '^Virtual core' | head -n 1)"
+PHYID="$(xinput --list --id-only "${PHYNAME}" | head -n 1)"
+VCKID="$(xinput --list --id-only "Virtual core keyboard" | head -n 1)"
+XTESTID="$(xinput --list --id-only "Virtual core XTEST keyboard" | head -n 1)"
+KEYMAP="$(setxkbmap -device "$PHYID" -query |grep ^layout|cut -d : -f 2|tr -d ' ')"
+for id in "$VCKID" "$XTESTID"; do
+setxkbmap -device "$id" -layout "$KEYMAP"
+done
+fi

Bug#970040: rails: CVE-2020-15169

[Salvatore Bonaccorso]

Source: rails
Version: 2:6.0.3.2+dfsg-11
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for rails.

CVE-2020-15169[0]:
| Cross-site scripting in translation helpers

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-15169
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15169
[1] https://groups.google.com/g/rubyonrails-security/c/b-C9kSGXYrc?pli=1
[2] 
https://github.com/rails/rails/commit/e663f084460ea56c55c3dc76f78c7caeddeeb02e

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#970038: r-cran-seurat: dependency is missing (hdf5r)

[Lucas Kanashiro]

Source: r-cran-seurat
Version: 3.2.0-1
Severity: important

Dear Maintainer,

r-cran-remotes has not migrated to testing because of a regression detected by 
autopkgtest:

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-seurat/6977467/log.gz

This is the important part:

── 1. Error: (unknown) (@test_load_10X.R#34)  ──
Please install hdf5r to read HDF5 files
Backtrace:
 1. Seurat::Load10X_Spatial(data.dir = "../testdata/visium")
 2. Seurat::Read10X_h5(...)

══ testthat results  ═══
[ OK: 392 | SKIPPED: 0 | WARNINGS: 0 | FAILED: 1 ]
1. Error: (unknown) (@test_load_10X.R#34)


After some digging I noticed that the main change in version 3.2 is "Support 
for analysis and visualization of spatially resolved datasets", and the 
Seurat::Load10X_Spatial and Seurat::Read10X_h5 pre-processing functions depend 
on the hdf5r R package. AFAICS this new dependency it is not available in the 
archive. So in order to enable this feature the hdf5r package is needed. As 
soon as we have this package in the archive it should be added as a test and 
runtime dependency.

Cheers!

-- 
Lucas Kanashiro

Bug#970039: mysql-8.0: [INTL:nl] Dutch translation of debconf messages

[Frans Spiesschaert]

 
 
Package: mysql-8.0 
Severity: wishlist 
Tags: l10n patch 
 
 
 
Dear Maintainer, 
 
 
Please find attached the updated Dutch translation of mysql-8.0 debconf
messages. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
 
-- 
Kind regards,
Frans Spiesschaert



nl.po.gz
Description: application/gzip

Bug#969788: nextcloud-desktop: Upgrade removed part of configuration

[Tobias Frost]

On Thu, 10 Sep 2020 19:27:37 +0200 Tobias Frost  wrote:
> I'll see if I can find some logs…

Ok, it seems so that my instance deletes its configuration itself…

But I think that needs a word on my configuration:
~/Documents is synced with my Nextcloud intance
I have setup XDG_DATA and XDG_CONFIG to be on
~/Documents/XDG/$hostname/{XDG_DATA XDG_CONFIG}
(to be able to share XDG configurations files on complicant apps more easy
between PCs)

~/Documents/XDG/isildor/XDG_CONFIG/Nextcloud is a symlink to ~/.config/Nextcloud
 (so it is not on the share)

It seems that nextcloud app is deleting that file, (following the symlink)

Of course this could be a read herring, as I naively tried to reconfigure 
the nextcloud without deleting Documents and I just got conflict everywhere now.

It is possible the the app is following the symlink and thinks, hey , file not
on the nextcloud server, delete it… Could be another bug though; (I guess it
should not follow symlinks, at least it used to ignore symlinks when syncing to
servers)

Next step I'll try a fresh resync…

-- 
tobi

Bug#970036: libopenmpi-dev fails to install

[Gianfranco Costamagna]

control: tags -1 patch

On Thu, 10 Sep 2020 21:05:09 +0300 Adrian Bunk  wrote:
> Package: libopenmpi-dev
> Version: 4.0.5-2
> Severity: grave
> Tags: ftbfs
> Control: affects -1 src:scotch src:starpu
> 
> ...
> Setting up libopenmpi-dev:amd64 (4.0.5-2) ...
> update-alternatives: error: alternative path 
> /usr/lib/$[DEB_HOST_MULTIARCH}/openmpi/include doesn't exist
> dpkg: error processing package libopenmpi-dev:amd64 (--configure):
> 
> 

grep DEB_HOST_MULTIARCH . -R |grep "\["
./debian/libopenmpi-dev.postinst:   --install 
/usr/include/$[DEB_HOST_MULTIARCH}/mpi mpi-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/openmpi/include 50 \
./debian/libopenmpi-dev.postinst:   --slave 
/usr/lib/$[DEB_HOST_MULTIARCH}/libmpi.so libmpi.so-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/openmpi/lib/libmpi.so \
./debian/libopenmpi-dev.postinst:   --slave 
/usr/lib/$[DEB_HOST_MULTIARCH}/libmpi++.so libmpi++.so-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/openmpi/lib/libmpi_cxx.so \
./debian/libopenmpi-dev.postinst:   --slave 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/mpi.pc mpi.pc-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/ompi.pc \
./debian/libopenmpi-dev.postinst:   --slave 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/mpi-fort.pc 
mpi-fort.pc-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/ompi-fort.pc \
./debian/libopenmpi-dev.postinst:   --slave 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/mpi-c.pc 
mpi-c.pc-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/ompi-c.pc \
./debian/libopenmpi-dev.postinst:   --slave 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/mpi-cxx.pc 
mpi-cxx.pc-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/ompi-cxx.pc


sed "s/\$\[DEB_HOST_MULTIARCH}/\${DEB_HOST_MULTIARCH}/g" -i 
./debian/libopenmpi-dev.postinst
*might* do the trick here :)

G.

Bug#966653: Any progress?

[GCS]

Hi Thomas,

On Wed, Sep 9, 2020 at 8:42 AM Thomas Goirand  wrote:
> On 9/8/20 5:20 PM, László Böszörményi (GCS) wrote:
> > I even suspect the real bug is in GitLab itself, it
> > may not (correctly) handle the new gRPC version.
>
> If so, can we lower the severity of the bug to important?
 It's about GitLab so Pirate should be in charge here. On the other
hand, as I see he can't provide a small reproduction case and as
GitLab is a Sid only package (due to other reasons) I would say go
ahead and lower the severity.

Cheers,
Laszlo/GCS

Bug#970036: libopenmpi-dev fails to install

[Adrian Bunk]

Package: libopenmpi-dev
Version: 4.0.5-2
Severity: grave
Tags: ftbfs
Control: affects -1 src:scotch src:starpu

...
Setting up libopenmpi-dev:amd64 (4.0.5-2) ...
update-alternatives: error: alternative path 
/usr/lib/$[DEB_HOST_MULTIARCH}/openmpi/include doesn't exist
dpkg: error processing package libopenmpi-dev:amd64 (--configure):

Bug#970035: ITP: python-cyborgclient -- Python client for cyborg API

[Thomas Goirand]

Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 

* Package name: python-cyborgclient
  Version : 1.2.1
  Upstream Author : OpenStack 
* URL : https://opendev.org/openstack/python-cyborgclient
* License : Apache-2.0
  Programming Lang: Python
  Description : Python client for cyborg API

 Python-cyborgclient is a Python bindings to the OpenStack Cyborg API. There's
 a Python API (the cyborgclient module), and a command-line script (cyborg).
 Each implements 100% of the OpenStack Cyborg API.

Bug#970034: ITP: r-cran-factoextra -- Extract and Visualize the Results of Multivariate Data Analyses

[Steffen Moeller]

Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-factoextra -- Extract and Visualize the Results of 
Multivariate Data Analyses
Package: wnpp
Owner: Steffen Moeller 
Severity: wishlist

* Package name: r-cran-factoextra
  Version : 1.0.7
  Upstream Author : Alboukadel Kassambara
* URL : https://cran.r-project.org/package=factoextra
* License : GPL-2
  Programming Lang: GNU R
  Description : Extract and Visualize the Results of Multivariate Data 
Analyses
 Provides some easy-to-use functions to extract and visualize the output
 of multivariate data analyses, including 'PCA' (Principal Component
 Analysis), 'CA' (Correspondence Analysis), 'MCA' (Multiple
 Correspondence Analysis), 'FAMD' (Factor Analysis of Mixed Data), 'MFA'
 (Multiple Factor Analysis) and 'HMFA' (Hierarchical Multiple Factor
 Analysis) functions from different R packages. It contains also
 functions for simplifying some clustering analysis steps and provides
 'ggplot2' - based elegant data visualization.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-factoextra

Bug#969788: nextcloud-desktop: Upgrade removed part of configuration

[Tobias Frost]

> 
> Can anyone confirm the problems of Erwan?

\o

I had 3 server configuration; after upgrade and reboot 
all those configurations were gone. I was prompted with an 
"first run" wizard.

apt.log says I was updating nextcloud-desktop:amd64 (2.6.4-1 -> 3.0.1-1)

Obersvations:
- I did not instantly reboot after instantly.
- Today, before the reboot, I had the nextcloud app hanging and needed to kill
it. 

I'll see if I can find some logs…

--
tobi

Bug#970033: ITP: r-cran-dtplyr -- Data Table Back-End for 'dplyr'

[Steffen Moeller]

Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-dtplyr -- Data Table Back-End for 'dplyr'
Package: wnpp
Owner: Steffen Moeller 
Severity: wishlist

* Package name: r-cran-dtplyr
  Version : 1.0.1
  Upstream Author : Lionel Henry
* URL : https://cran.r-project.org/package=dtplyr
* License : GPL-3
  Programming Lang: GNU R
  Description : Data Table Back-End for 'dplyr'
 Provides a data.table backend for 'dplyr'. The goal of 'dtplyr'
 is to allow you to write 'dplyr' code that is automatically translated to
 the equivalent, but usually much faster, data.table code.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-dtplyr

Bug#968707: thunderbird: Please allow Enigmail 2.2.x with Thunderbird 78

[Carsten Schoenert]

Hello Daniel,

any idea when Enigmail 2.2.x will finds it's way into unstable? Ubuntu 
already is using this version in Groovy Gorilla.


Thunderbrid 78.2.2 will get released within the next hours and I like to 
do a first upload of this version into unstable. But this isn't helpful 
as Thunderbird will break now every Enigmail version below 2.2. So the 
current installed Enigmail package would get removed.



Am 22.08.20 um 09:48 schrieb Carsten Schoenert:

Hello intrigeri,

Am 20.08.20 um 15:04 schrieb intrig...@debian.org:

Hi,

I see that on the debian/experimental branch, where the upgrade to
Thunderbird 78 is being prepared (many thanks for this!), the
thunderbird package has an unversioned "Breaks: enigmail":

 commit 8adec8f0bd5eff09cffa8ec8fb579989640e001f
 Author: Carsten Schoenert 
 Date:   Sat Jun 20 17:04:54 2020 +0200

 enigmail: let any version of Enigmail break
 
 The Enigmail functionality for managing OpenPGP keys and encryption is

 now included within Thunderbird, means we want to break every existing
 enigmal package version so it will get removed by newer thunderbird
 packages.

I don't think that's correct:


I've no doubt that this specific on TB packaging side isn't fully ready
and will need some fine tuning.
My intend in late of May and in the beginning of June was to have a in
principle working TB 78 package which is able to write and receive
emails. At this time it wasn't clear how the PGP part will move to.

But now more than two months later we see much more light and also did
get more and more information. So yes, thanks for having a critical look
at this.


in order to import existing secret keys
from the GnuPG keyring, and previously used Enigmail configuration,
one needs Enigmail 2.2.x (which does nothing more that providing
a migration wizard):
https://wiki.mozilla.org/Thunderbird:OpenPGP:Migration-From-Enigmail.
My own testing, both with and without Enigmail 2.2.x installed,
confirmed this.


I haven't followed the development of Enigmail in detail, but I assumed
that 2.1.x will be the last version of Enigmail which is provided by the
Enigmail team. So I'm a bit surprised that Enigmail will do a version
2.2. I'm not really happy about the spreading of news around inclusion
of Enigmail functionality into Thunderbird.


So:

1. I think the correct control field for thunderbird would be:

Breaks: enigmail (<< 2:2.2.0~),

2. To support users who currently use Thunderbird + Enigmail in
Debian, ideally we would have Enigmail 2.2.x in Debian at about the
same time as Thunderbird 78, i.e. presumably around 2020-09-22,
when the 68 series will be EOL'ed.

dkg, how likely is it that this happens?

If this does not happen, a plan B could be to set the
mail.openpgp.allow_external_gnupg pref to true by default, so that
Thunderbird's own OpenPGP code falls back to using GnuPG when it
cannot find a secret key it needs.

Thoughts?


I trust you enough to add the suggested version to the Breaks entry for
enigmail. And I can add this rather quickly as version 78.2.0 is in the
door, should be released officially at the beginning of the next week I
guess.
But of course it would be nice to hear also the opinions of Daniel to
this problem.



--
Regards
Carsten Schoenert

Bug#970032: ITP: r-cran-airr -- AIRR Data Representation Reference Library

[Steffen Moeller]

Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-airr -- AIRR Data Representation Reference Library
Package: wnpp
Owner: Steffen Moeller 
Severity: wishlist

* Package name: r-cran-airr
  Version : 1.3.0
  Upstream Author : Jason Vander Heiden
* URL : https://cran.r-project.org/package=airr
* License : CC-BY-4.0
  Programming Lang: GNU R
  Description : AIRR Data Representation Reference Library
 Schema definitions and read, write and validation tools for data
 formatted in accordance with the AIRR Data Representation schemas defined
 by the AIRR Community .

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-airr

Bug#887085: systemd units are pushed to salsa

[Pirate Praveen]

The systemd units are pushed here

https://salsa.debian.org/ruby-team/diaspora-installer/-/commit/c40f18f363a35a967690e8bbff382330638b2755

We currently use debhelper compat 10 for this (like gitlab), but we 
need to find out how to do it in newer debhelper compat versions.


Another thing is we need to properly manage /etc/diaspora.conf 
migration to /etc/diaspora/diaspora.conf and find a way to export these 
variables for the init script (gitlab does that already and we can use 
the same strategy here).

Bug#969592: sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

tags 969592 +moreinfo
thanks

Hello Sebastian,

from the log I see 

*** qcam backend requires (ioperm, inb and outb) or portaccess functions -
disabling

which comes through  

checking for ioperm... no
checking for i386_set_ioperm... no

I don't have a arm* machine for checking this. But I think that the kernel
dosn't support ioperm() at buildtime. 


CU 
Jörg


Am Samstag, den 05.09.2020, 18:11 +0200 schrieb Sebastian Ramacher
> Source: sane-backends
> Version: 1.0.27-3.2
> Severity: serious
> Tags: ftbfs sid bullseye
> Justification: fails to build from source (but built successfully in the past)
> 
> sane-backends FTBFS on armel and armhf:
> > @@ -7204,7 +7151,7 @@
> >   sanei_pp_outb_addr@Base 1.0.25
> >   sanei_pp_outb_ctrl@Base 1.0.25
> >   sanei_pp_outb_data@Base 1.0.25
> > - sanei_pp_outb_epp@Base 1.0.25
> > +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25
> >   sanei_pp_release@Base 1.0.25
> >   sanei_pp_set_datadir@Base 1.0.25
> >   sanei_pp_setmode@Base 1.0.25
> > dh_makeshlibs: error: failing due to earlier errors
> > make[1]: *** [debian/rules:139: override_dh_makeshlibs-arch] Error 25
> > make[1]: Leaving directory '/<>'
> > make: *** [debian/rules:25: binary-arch] Error 2
> 
> See
> https://buildd.debian.org/status/fetch.php?pkg=sane-backends&arch=armel&ver=1.0.27-3.2%2Bb2&stamp=1599315993&raw=0
> 
> Cheers
- -- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl9aVkQACgkQCfifPIyh
0l1QXw//ec5SAyJBzhMcetEKS9ZzSIuVayVz7uBNp5+y24lkYQWHP65RSJfzZGZ4
nx4BLAS/8sYjvHSAAMt5uPQ0SkcyzJVkDpzfi6iqckKYinvYIrZUgFU/NIOgamo3
9REatQltfVMh93MqVUFkQjt78aJfvoGgYoNtbCCmxYpwNcLmYxc6rbBRarKTDvYW
JQ/rMYBM4UuziRhSxpwqd3XFA0NAl4PpyfHW7T2sDXUINLJTc862amxKaiILLM/J
1ED1HDrj29thTQN0KNkkhCyQfAkOzZLbrk+TNMc/2WzPUXJ8HAyJTdN3L4JgPOYm
UySUQ+Xv/2hATUKQgNOr/HFkXlXIi4Ov7mwWT5Qo/jyu6tIRxorI0AD+WWKYzQC/
seAjEKYyQMtPDnZ6eNWcf8xkkIDLXdzksDlYBYt0lx87ydh6x+jfiJh/xFVb/BZk
clL0CniYx7QUnCA3x0wEYSZNtzFlQPiTbJnERBMH5r1R9654JAb8zCvRjc2pvQYi
CBCYO2I4az7A+ABn5TTH4y5cANXjLc6P0bQO/zLi968VXD4yfm7d8mVVA7zAO7f+
z+TCAww5iUbLfzwJ6Wf8+ygdERSTQpswMQwfygQal9xF88v9bp+gcCNaYFqG0B5T
b0qOZMx2ZM15yctIaLB54MkvvuAxxeuIZvlWRCmJ3fQT432/MGI=
=BswM
-END PGP SIGNATURE-

Bug#878332: linux > 4.11: Raspberry pi 2 hangs at boot with lpae kernel

[Gunnar Wolf]

Philip Rinn dijo [Thu, Sep 10, 2020 at 12:09:29PM +0200]:
> Hi Gunnar,
> 
> thanks for testing - but your message leaves me a little confused. You claim, 
> the
> bug is fixed but you say
> 
> > we have used only regular linux-image-armmp kernels (and have no
> > reason to suppose -lpae is needed).
> 
> So, my question, did you actually test with an "-lpae" kernel?

At the time of my bug report, I had not tested it yet. I checked right
now, downloading an image from raspi.debian.net, and installing the
-lpae kernel, I can confirm it boots correctly all the way to:

root@rpi2-20200910:~# uname -a
Linux rpi2-20200910 4.19.0-10-armmp-lpae #1 SMP Debian 4.19.132-1 
(2020-07-24) armv7l GNU/Linux

> While being technically correct that an "-lpae" kernel is not needed, the 
> kernel
> should still also work on an rpi2 _with_ an "-lpae" kernel.

OK, I'm happy to have understood this correctly :-)


signature.asc
Description: PGP signature

Bug#966295: lintian: False positive with bogus email address

[Anthony Fok]

Hello Eriberto,

On Sat, Jul 25, 2020 at 9:45 PM Eriberto Mota  wrote:
>
> Dear Maintainer,
>
> lintian produces a false positive in mmorph package. I think the problem is a
> comma used by an old maintainer.
>
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG 
> 
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG 
> 
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG 
> 
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG 
> 
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG 
> 
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG 
> 
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG 
> 
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG 
> 
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG 
> 
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG 
> 
> E: mmorph: bogus-mail-host-in-debian-changelog Thomas Bushnell, BSG 
> 

I ran into the same problem with the lilypond package too, though
after adding double quotes around the display name of the email
address like so:

"Thomas Bushnell, BSG" 

the Lintian errors went away.

This makes sense to me because the comma is used for separating
multiple email recipients, so Lintian is right in splitting it up at
the comma, i.e. trying to parse the string "Thomas Busnell" as an
email address, and "BSG " as another.

That said, perhaps the Lintian info message could be a little more
explicit, as the current text:

   The changelog file contains an invalid email address: the domain needs
   at least one dot. This looks like a mistake.

does not say that a comma isn't allowed anywhere in the display name.

Just my two cents.  :-)

Cheers,
Anthony

Bug#970031: emacs: (set-language-environment 'Japanese) causes ELPA archive signature verification to fail

[Ryo IGARASHI]

Package: emacs
Version: 1:26.1+1-3.2+deb10u1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

Current Emacs in buster fails to verify archive signature of ELPA when
language-environment is set to Japanese (posibly other languages, too).

At first, I thought this bug comes from #965291, or #969971, but turned out
to be the separate issue.

steps to reproduce:
1. emacs -Q
2. eval following 2 lines:
(set-language-environment 'Japanese)
(setq gnutls-algorithm-priority "NORMAL:-VERS-TLS1.3") ;; See #969971
3. M-x package-list-packages shows following error:

Failed to verify signature archive-contents.sig:
Bad signature from 066DAFCB81E42C40 GNU ELPA Signing Agent (2019) 

Command output:
gpg: Signature made Thu Sep 10 18:05:02 2020 JST
gpg:using RSA key C433554766D3DDC64221BFAA066DAFCB81E42C40
gpg: BAD signature from "GNU ELPA Signing Agent (2019) " 
[unknown]

I also found that this problem never occurs on 26.3 in sid, therefore this is
only a stable issue.

Best regards,
- -- 
Ryo Igarashi, Ph.D.
rigar...@gmail.com


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

Kernel: Linux 4.19.104-microsoft-standard (SMP w/8 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), 
LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages emacs depends on:
ii  emacs-gtk  1:26.1+1-3.2+deb10u1

emacs recommends no packages.

emacs suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iIkEARYKADEWIQSQVQWnJ6dEuIxNmESAtgFFC/hXNwUCX1pO1hMccmlnYXJhc2hA
Z21haWwuY29tAAoJEIC2AUUL+Fc3C3ABAIBLl384AA077dEyncEAuBQHX35Vl+Kg
nIUJhJ4ZQiKcAP4/COLnGHF2HFx405OMgougfOzIgu5FO4kkZo0FwRKCBA==
=kD5q
-END PGP SIGNATURE-

Bug#964734: Confirmed workaround: enable MSI

[Bernhard Turmann]

After enabling MSI within /etc/modprobe.d/ the card is working as expected:

 options ddbridge msi=1

Upstream bug report has been updated accordingly.

Regards
Berni

Bug#965352: libopenmpi3: breaks tests in client programs

[Drew Parsons]

Source: openmpi
Followup-For: Bug #965352

As far as the client programs go (dolfin mpi4py petsc4py scalapack),
they are all building now (with mpi4py now patched to ignore the
bug).

Please close this bug if we don't need to monitor the problem any more.

Bug#962596: ca-certificates: Removal of GeoTrust Global CA requires investigation

[Michael Holloway]

Happy three-month bug birthday!  Any news?

Thanks,
Michael

Bug#968589: PPP name resolver service not restarted upon upgrade

[積丹尼 Dan Jacobson]

Bug still affecting several of my machines. Forwarding to
https://github.com/systemd/systemd/issues/17004 .

Bug#964862: RFS: git-revise/0.6.0-1 -- handy git tool for doing efficient in-memory commit rebases & fixups

[Nicolas Schier]

Hei,

På fr. 28. aug. 2020 kl. 22.54 + skrev Nicolas Schier:
> On Fri, Aug 28, 2020 at 01:28:00PM +0300, Adrian Bunk wrote:
> > Control: tags -1 moreinfo
> > 
> > On Sat, Jul 11, 2020 at 02:02:43PM +0200, Nicolas Schier wrote:
> > >...
> > > Changes since the last upload:
> > >...
> > >* Enable autopkgtest by using upstream tests (Closes: #944957)
> > 
> > This likely worked when you posted the sponsorship request,
> > but new pylint makes it fail:
> > 
> > ...
> > lint run-test: commands[0] | pylint gitrevise
> > * Module gitrevise.merge
> > gitrevise/merge.py:207:12: W0707: Consider explicitly re-raising using the 
> > 'from' keyword (raise-missing-from)
> > gitrevise/merge.py:225:12: W0707: Consider explicitly re-raising using the 
> > 'from' keyword (raise-missing-from)
> > * Module gitrevise.utils
> > gitrevise/utils.py:73:8: W0707: Consider explicitly re-raising using the 
> > 'from' keyword (raise-missing-from)
> > gitrevise/utils.py:89:12: W0707: Consider explicitly re-raising using the 
> > 'from' keyword (raise-missing-from)
> > 
> > --
> > Your code has been rated at 9.96/10 (previous run: 9.96/10, +0.00)
> > 
> > ERROR: InvocationError for command 
> > /tmp/autopkgtest.SDfHIM/tree/.tox/lint/bin/pylint gitrevise (exited with 
> > code 4)
> > ...
> 

finally, I uploaded a new version.  Since I did not get any feedback 
from upstream, yet, I am going open an issue for upstream.

Adrian, can you please have a look at the freshly uploaded version?

Thanks and kind regards,
Nicolas

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


signature.asc
Description: PGP signature

Bug#962327: ansible: apt module doesn't respect 'default_release' for already installed packages

[Andrei POPESCU]

On Mi, 09 sep 20, 11:36:16, Lee Garrett wrote:
> 
> it seems you have a typo. It should be "default_release" (with an
> underscore, not hyphen). Can you verify that it fixes your issue?

Hello,

Thank you for looking into this. Changing '-' to '_' doesn't make any 
difference.

I'm guessing the module (or ansible?) accepts both or it should have 
issued an error for an unsupported option.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Bug#969084: Added that

[Wouter Verhelst]

FYI: I added a "policy-rcd-declarative-deny-all" package that contains
an alternative default policy denying all service startup requests. As
soon as it passes my tests, I'll upload that to unstable.

You might want to update the script then to install
policy-rcd-declarative-deny-all (which depends on
policy-rcd-declarative) and drop the manual policy config file.

If wanted, I could also upload this to backports?

Regards,

-- 
To the thief who stole my anti-depressants: I hope you're happy

  -- seen somewhere on the Internet on a photo of a billboard

Bug#965363: RFS: opencpn/5.2.0+dfsg-1 [RC] -- Open Source Chartplotter and Marine GPS Navigation Software

[Tobias Frost]

On Thu, Sep 10, 2020 at 12:12:29PM +0200, Alec Leamas wrote:
> On Thu, 10 Sep 2020 05:12:34 -0400 The Wanderer 
> wrote:
> > On 2020-09-10 at 01:45, Tobias Frost wrote:
> > 
> > > On Wed, Sep 09, 2020 at 10:53:37PM +0200, Alec Leamas wrote:
> > >
> 
> > > Well, actually, all those lines probably should be removed:
> > > debian/changelog is intended to record changes to the packaging part
> > > only, it is not to record changes made upstream; more generally: Only
> > > stuff that changes files in the debian directory should be mentioned
> > > in d/changelog. (See
> > > https://www.debian.org/doc/debian-policy/ch-source.html#debian-changelog-debian-changelog
> > > for some better/more accurate wording in the Policy)
> > 
> > I'm not sure I read that section as meaning that. Could you point more
> > specifically to the exact wording there which you understand as
> > reflecting this rule?
> > 
> > Regardless, I'm fairly sure there are exceptions to this in practice.
> > For example, if a new upstream release includes a change which closes an
> > open Debian bug report or fixes a particular CVE, a notation in the
> > changelog recording that fact seems to be de rigueur, and in fact as I
> > understand matters the tooling recognizes and parses notes such as
> > "Closes: #123456" or "CVE-1000-123-1234" to auto-close the given bug
> > report or to mark a newly-packaged version as unaffected by the given
> > CVE.
> > 
> > For that matter, look at the Linux kernel packages
> > (linux-image-VERSION-ARCH, among others). They don't seem to ship a
> > changelog.Debian.gz, but the changelog.gz which they do ship seems to be
> >
> 
> This seems to be a Deep Philosophical Discussion between Debian
> Developers. I should thus basically stay quiet, but I feel the
> discussion is a little bit off in this case.

(Sorry that this RFS has been hijacked. I try keep on topic now; I'm not sure
whether The Wanderer is DD or package maintainer, but its not relevant anyway)

 
> I'm working tight with upstream, so the upstream/downstream boundaries
> are a little obscured. 

>The references was a result (all cases) of a
> workflow like
> 
> - Packaging, I find a bug and make a patch in d/patches
> - The bug is filed upstream.
> - The patch is converted to an upstream PR.
> - The PR is merged on upstream master branch, to be included in next
> release.
> - The patch in d/patches is updated with DEP-5 info (yes, did that).
> - The line in the changelog is (was) updated with the upstream bug #.
> 
> So, these references stem from my downstream work. They do (did) *not*
> reference anything in the release tag, only changes after that.

Srry, EPARSE, can you expand?
Oh wait, I guess I see the misunderstanding now… Oops, totally sorry, I misread
the changelog entries all the time and missing the word "patch"… Actually those
changes _are_ changes to the debian package, so of course they need to be in
d/changelog.  However, May I propose a better structuring like:
 
 * New patches:
   - udev rule installation patch.
   - metadata installation patch.
   - Remove bogus svg file patch. (**)
   - Patch to fix cmake parallel execution.
   - Add two plugin compatiblity patches (#1997).

(in my packages I usually write "New patch $patch-filename.", because details
would be the dep3 headers of the patch. This allow sometime better to understand
which patch is what change. But thats personal taste)

While having the changelog open:
 * Handle some lintian informational warnings.
is not a good changelog entry, because it does have enough information what has
been changed (and why))
 * Remove bogus svg file patch.
Its unclear to me why are you removing it? (If it doesn't cause problems I
would leave it…)

I will continue later, I need some food first ;-)
But I'm glad this knot in my brain has been sliced ;-)

> Having these lines, with or without upstream references is no big thing,
> at least not for me. Just trying to clarify


> Cheers!
> --alec
> 

Bug#970029: llvm-toolchain-8: should not be part of bullseye

[Sylvestre Ledru]

Le 10/09/2020 à 15:25, Sebastian Ramacher a écrit :

Source: llvm-toolchain-8
Version: 1:8.0.1-10
Severity: serious
Tags: sid bullseye

So I think it's time to get llvm-toolchain-8 removed from testing (and
from sid in the long run).



Agreed, many thanks for filling this bug. It was on my todo list for a while :)

Cheers,
Sylvestre