Bug#998813: ITP: node-carto -- Mapnik stylesheet compiler

[Johannes Schauer Marin Rodrigues]

Package: wnpp
Severity: wishlist
Owner: Johannes Schauer Marin Rodrigues 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: node-carto
  Version : 1.2.0
  Upstream Author : MapBox 
* URL : http://github.com/mapbox/carto.git
* License : Apache-2.0
  Programming Lang: Javascript
  Description : Mapnik stylesheet compiler

Carto is a stylesheet renderer for Mapnik.  It's an evolution of the
Cascadenik idea and language, with an emphasis on speed and flexibility.

Carto got removed this September because a new version could not be
packaged as nodejs dependencies chroma-js and hsluv were missing. I now
packaged chroma-js and hsluv and both are already in NEW. I packaged the
new upstream version of node-carto and verified that it is working
correctly: https://salsa.debian.org/js-team/node-carto

I'd like to bring back carto into Debian because it is needed for a
prospective new package that I develop as its upstream.

Bug#997218: keepalived: FTBFS: if.h:44:5: error: redeclaration of enumerator ‘IFF_UP’

[Vincent Bernat]

 ❦ 23 October 2021 21:13 +02, Lucas Nussbaum:

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

This bug has been fixed in later versions. I have uploaded 2.2.4-0.1 to
DELAYED/10. Here is the diff compared to what is actually in master on
Salsa.

diff --git a/debian/changelog b/debian/changelog
index a11fb75cca2d..f9c585865a56 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,17 @@
-keepalived (1:2.2.1-1) UNRELEASED; urgency=medium
+keepalived (1:2.2.4-0.1) unstable; urgency=medium
 
+  [ Alexander Wirt ]
   * [61cbc18] New upstream version 2.2.1
   * [ecf662d] Keepalived has now support for systemd notify
 
- -- Alexander Wirt   Mon, 25 Jan 2021 09:04:08 +0100
+  [ Vincent Bernat ]
+  * Non-maintainer upload.
+  * New upstream version 2.2.4. Closes: #980563.
+- Fix FTFBS. Closes: #997218.
+  * d/rules: enable systemd as an init to get systemd features.
+  * d/rules: remove use of custom-specified include directory for kernel.
+
+ -- Vincent Bernat   Sun, 07 Nov 2021 17:57:44 +0100
 
 keepalived (1:2.1.5-0.2) unstable; urgency=medium
 
diff --git a/debian/include/linux/linux/ip_vs.h b/debian/include/linux/linux/ip_vs.h
deleted file mode 100644
index 4102ddcb4e14..
--- a/debian/include/linux/linux/ip_vs.h
+++ /dev/null
@@ -1,474 +0,0 @@
-/* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
-/*
- *  IP Virtual Server
- *  data structure and functionality definitions
- */
-
-#ifndef _IP_VS_H
-#define _IP_VS_H
-
-#include 	/* For __beXX types in userland */
-
-#define IP_VS_VERSION_CODE	0x010201
-#define NVERSION(version)			\
-	(version >> 16) & 0xFF,			\
-	(version >> 8) & 0xFF,			\
-	version & 0xFF
-
-/*
- *  Virtual Service Flags
- */
-#define IP_VS_SVC_F_PERSISTENT	0x0001		/* persistent port */
-#define IP_VS_SVC_F_HASHED	0x0002		/* hashed entry */
-#define IP_VS_SVC_F_ONEPACKET	0x0004		/* one-packet scheduling */
-#define IP_VS_SVC_F_SCHED1	0x0008		/* scheduler flag 1 */
-#define IP_VS_SVC_F_SCHED2	0x0010		/* scheduler flag 2 */
-#define IP_VS_SVC_F_SCHED3	0x0020		/* scheduler flag 3 */
-
-#define IP_VS_SVC_F_SCHED_SH_FALLBACK	IP_VS_SVC_F_SCHED1 /* SH fallback */
-#define IP_VS_SVC_F_SCHED_SH_PORT	IP_VS_SVC_F_SCHED2 /* SH use port */
-
-/*
- *  Destination Server Flags
- */
-#define IP_VS_DEST_F_AVAILABLE	0x0001		/* server is available */
-#define IP_VS_DEST_F_OVERLOAD	0x0002		/* server is overloaded */
-
-/*
- *  IPVS sync daemon states
- */
-#define IP_VS_STATE_NONE	0x		/* daemon is stopped */
-#define IP_VS_STATE_MASTER	0x0001		/* started as master */
-#define IP_VS_STATE_BACKUP	0x0002		/* started as backup */
-
-/*
- *  IPVS socket options
- */
-#define IP_VS_BASE_CTL		(64+1024+64)		/* base */
-
-#define IP_VS_SO_SET_NONE	IP_VS_BASE_CTL		/* just peek */
-#define IP_VS_SO_SET_INSERT	(IP_VS_BASE_CTL+1)
-#define IP_VS_SO_SET_ADD	(IP_VS_BASE_CTL+2)
-#define IP_VS_SO_SET_EDIT	(IP_VS_BASE_CTL+3)
-#define IP_VS_SO_SET_DEL	(IP_VS_BASE_CTL+4)
-#define IP_VS_SO_SET_FLUSH	(IP_VS_BASE_CTL+5)
-#define IP_VS_SO_SET_LIST	(IP_VS_BASE_CTL+6)
-#define IP_VS_SO_SET_ADDDEST	(IP_VS_BASE_CTL+7)
-#define IP_VS_SO_SET_DELDEST	(IP_VS_BASE_CTL+8)
-#define IP_VS_SO_SET_EDITDEST	(IP_VS_BASE_CTL+9)
-#define IP_VS_SO_SET_TIMEOUT	(IP_VS_BASE_CTL+10)
-#define IP_VS_SO_SET_STARTDAEMON (IP_VS_BASE_CTL+11)
-#define IP_VS_SO_SET_STOPDAEMON (IP_VS_BASE_CTL+12)
-#define IP_VS_SO_SET_RESTORE(IP_VS_BASE_CTL+13)
-#define IP_VS_SO_SET_SAVE   (IP_VS_BASE_CTL+14)
-#define IP_VS_SO_SET_ZERO	(IP_VS_BASE_CTL+15)
-#define IP_VS_SO_SET_MAX	IP_VS_SO_SET_ZERO
-
-#define IP_VS_SO_GET_VERSION	IP_VS_BASE_CTL
-#define IP_VS_SO_GET_INFO	(IP_VS_BASE_CTL+1)
-#define IP_VS_SO_GET_SERVICES	(IP_VS_BASE_CTL+2)
-#define IP_VS_SO_GET_SERVICE	(IP_VS_BASE_CTL+3)
-#define IP_VS_SO_GET_DESTS	(IP_VS_BASE_CTL+4)
-#define IP_VS_SO_GET_DEST	(IP_VS_BASE_CTL+5)	/* not used now */
-#define IP_VS_SO_GET_TIMEOUT	(IP_VS_BASE_CTL+6)
-#define IP_VS_SO_GET_DAEMON	(IP_VS_BASE_CTL+7)
-#define IP_VS_SO_GET_MAX	IP_VS_SO_GET_DAEMON
-
-
-/*
- *  IPVS Connection Flags
- *  Only flags 0..15 are sent to backup server
- */
-#define IP_VS_CONN_F_FWD_MASK	0x0007		/* mask for the fwd methods */
-#define IP_VS_CONN_F_MASQ	0x		/* masquerading/NAT */
-#define IP_VS_CONN_F_LOCALNODE	0x0001		/* local node */
-#define IP_VS_CONN_F_TUNNEL	0x0002		/* tunneling */
-#define IP_VS_CONN_F_DROUTE	0x0003		/* direct routing */
-#define IP_VS_CONN_F_BYPASS	0x0004		/* cache bypass */
-#define IP_VS_CONN_F_SYNC	0x0020		/* entry created by sync */
-#define IP_VS_CONN_F_HASHED	0x0040		/* hashed entry */
-#define IP_VS_CONN_F_NOOUTPUT	0x0080		/* no output packets */
-#define IP_VS_CONN_F_INACTIVE	0x0100		/* not established */
-#define IP_VS_CONN_F_OUT_SEQ	0x0200		/* must do output seq adjust */
-#define IP_VS_CONN_F_IN_SEQ	0x0400		/* must do input seq adjust */
-#define IP_VS_CONN_F_SEQ_MASK	0x0600		/* in/out sequence mask */
-#define IP_VS_CONN_F_NO_CPORT	0x0800		/* no client port set yet */

Bug#954354: ITP: golang-github-audriusbutkevicius-recli -- Reflection based CLI (command line interface) generator for Golang

[Aloïs Micard]

Hello there!

I'm currently working on getting the next version of Syncthing on the archive
and I would need to package this library.

A quick lookup on Salsa show that a repository exists but nothing has been 
pushed.
Have you done the packaging? Do you need a sponsor?

Or should I done it by myself?

Thanks !

Cheers,

On Fri, 20 Mar 2020 18:40:00 +0100 "Quentin Hibon"  wrote:

Package: wnpp
Severity: wishlist
Owner: hiq 

* Package name: golang-github-audriusbutkevicius-recli
  Version : 0.0.5-1
  Upstream Author : Audrius Butkevicius
* URL : https://github.com/AudriusButkevicius/recli
* License : MPL-2.0
  Programming Lang: Go
  Description : Reflection based CLI (command line interface) generator for 
Golang

 recli - Reflection based CLI (command line interface) generator for
 Golang GoDoc (https://godoc.org/github.com/AudriusButkevicius/recli)
 .
 For a given struct, builds a set of urfave/cli
 (https://github.com/urfave/cli) commands which allows you to modify it
 from the command line.
 .
 Useful for generating command line clients for your application
 configuration that is stored in a Go struct.  Features•
 Nested struct support• Enum/Custom complex type support via
 MarshalText/UnmarshalText• Slice support, including complex types•
 Slice indexing by struct field• Map support• Default primitive value
 support when adding items to slicesKnown limitations• Adding new
 struct to a slice only allows setting primitive fields (use add-json
 as a work-around)• Only primitive types supported for map keys and
 values• No defaults for mapsExamples Example config
 .
 ``go type Config struct {
 Address  stringusage:"Address on which to listen"`
 // Description printed in -help AuthMode AuthMode
 // Enum support ThreadingOptions ThreadingOptions
 // Nested struct support Backends []Backend
 // Slice support EnvVars  map[string]string
 // Map support
 }
 .
 type Backend struct {
 Hostname string recli:"id" // Constructs commands
 for indexing into the array based on the value of this field Port
 intdefault:"2019" // Default support BackoffIntervals []int
 default:"10,20"// Slice default support IPAddressCached  net.IP
 recli:"-" json:"-" // Skips the field
 }
 .
 type ThreadingOptions struct {
 MaxThreads int
 } ```
 .
 Sample input data json {
"Address":"http://website.com";, "AuthMode":"static",
"ThreadingOptions":{
   "MaxThreads":10
}, "Backends":[
   {
  "Hostname":"backend1.com", "Port":1010
   }, {
  "Hostname":"backend2.com", "Port":2020
   }


--
Aloïs Micard 

GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2



OpenPGP_signature
Description: OpenPGP digital signature

Bug#982381: AttributeError: lowlevel due to trio usage in s3ql/block_cache.py

[Lorentz Kim]

I believe s3ql 3.8.0 just released, and it now states it requires trio >=
0.15.

https://github.com/s3ql/s3ql/commit/105dd0d62670570cd0e77cf9cbfa967f7f4130fe

Although, that's just the documentation I think. Actual "requirement" was
set here:

https://github.com/s3ql/s3ql/commit/7c955eda5d058dcbf59c7c63066fcccdbac13494#diff-60f61ab7a8d1910d86d9fda2261620314edcae5894d5aaa236b821c7256badd7

On Wed, 17 Mar 2021 at 03:54, Andrey Rahmatullin  wrote:

> On Thu, Feb 18, 2021 at 03:28:36PM +0100, Francesco P. Lovergine wrote:
> > I'm pretty sure this release should depend on >= 0.15,
> > even due to #981906. Unfortunately, it is not expressed in the package
> From setup.py:
>
>  # Need trio.lowlevel
>  'trio >= 0.15',
>
> So it's expressed upstream but ignored in the Debian package, because
> dh_python3 ignores version reqs by default.
>
>
> --
> WBR, wRAR
>

Bug#998812: libnode93: Overwrites file in libnode83

[Matthias Urlichs]

Package: libnode93
Version: 16.13.0~dfsg-1
Severity: serious
Justification: 7.6.1
X-Debbugs-Cc: sm...@smurf.noris.de


Unpacking libnode93:amd64 (16.13.0~dfsg-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-SEFJsk/4-libnode93_16.13.0~dfsg-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/systemtap/tapset/node.stp', which is also in 
package libnode83:amd64 14.17.0~dfsg-2


-- System Information:
Debian Release: 11.1
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'testing'), (600, 'oldstable'), (500, 
'unstable'), (450, 'focal'), (350, 'oldoldstable'), (300, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 5.10.0-9-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_USER
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 libnode93 depends on:
ii  libbrotli1 1.0.9-2+b2
ii  libc-ares2 1.17.1-1+deb11u1
ii  libc6  2.32-4
ii  libgcc-s1  10.2.1-6
ii  libicu70   70.1-2
ii  libnghttp2-14  1.43.0-1
ii  libssl1.1  1.1.1k-1+deb11u1
ii  libstdc++6 11.2.0-10
ii  libuv1 1.40.0-2
ii  zlib1g 1:1.2.11.dfsg-2

libnode93 recommends no packages.

libnode93 suggests no packages.

-- debconf-show failed

Bug#998367: perlcritic: "Code not tidy' after perltidy

[intrigeri]

Control: severity -1 important

Hi,

Felix Lechner (2021-11-03):
>> https://github.com/Perl-Critic/Perl-Critic/issues/925
>
> That has not seen any activity in over two years.

FWIW, there has been renewed activity a few days ago on the
corresponding PR: https://github.com/Perl-Critic/Perl-Critic/pull/876

> Would you consider marking the version in unstable as unfit for
> release,

With the data I have in hand, this looks like severity important to
me; RC-buggy seems a bit strong handed unless a large subset of source
files these programs are run on do include UTF-8 in some place that
triggers the bug.

> The version in bullseye does not have the issue.

In combination with which version of perltidy?

(The bug lies in the interaction between these 2 tools. At first
glance, my hunch is that the problem was introduced by changes in
perltidy between Bullseye and sid.)

Cheers,
-- 
intrigeri

Bug#998811: [INTL:sv] Swedish strings for mrtg debconf

[Martin Bagge / brother]

package: mrtg
severity: wishlist
tags: patch l10n

Please consider to add this file to translation of debconf.

--
brother# Translation of mrtg debconf template to Swedish
# Copyright (C) 2021 Martin Bagge 
# This file is distributed under the same license as the mrtg package.
#
# Martin Bagge , 2021
msgid ""
msgstr ""
"Project-Id-Version: mrtg\n"
"Report-Msgid-Bugs-To: m...@packages.debian.org\n"
"POT-Creation-Date: 2021-10-25 19:27-0300\n"
"PO-Revision-Date: 2021-11-05 09:31+0100\n"
"Last-Translator: Martin Bagge \n"
"Language-Team: Swedish \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../mrtg.templates:1001
msgid "Fix owner, group and permissions for /var/www/html/mrtg?"
msgstr ""
"Ska ägare, grupp och rättigheter för sökvägen /var/www/html/mrtg justeras?"

#. Type: boolean
#. Description
#: ../mrtg.templates:1001
msgid ""
"By default MRTG writes all graphics in /var/www/html/mrtg/ directory. This "
"directory is present at this moment, but it is insecure. Is needed to make "
"this directory owned by 'mrtg' user and 'www-data' group. The recommended "
"permission is 0750."
msgstr ""
"I standardutförande sparar MRTG all grafik i /var/www/html/mrtg/. Sökvägen "
"existerar dock redan men med fel rättigheter. För att det inte ska leda till "
"ett säkerhetshål så behöver sökvägen ägas av användaren mrtg och gruppen www-"
"data. Föreslagen rättighetsinställning är 0750 - fullt skrivbar av mrtg, "
"läsbar av www-data-gruppen och otillgänglig för övriga."

#. Type: boolean
#. Description
#: ../mrtg.templates:2001
msgid "Create /var/www/html/mrtg?"
msgstr "Ska /var/www/html/mrtg skapas?"

#. Type: boolean
#. Description
#: ../mrtg.templates:2001
msgid ""
"By default MRTG writes all graphics in /var/www/html/mrtg/ directory. "
"However, at this moment, this directory doesn't exist. Is also needed to "
"make this directory owned by 'mrtg' user and 'www-data' group. The "
"recommended permission is 0750."
msgstr ""
"I standardutförande sparar MRTG all grafik i /var/www/html/mrtg/. Sökvägen "
"existerar dock inte ännu. För att det inte ska leda till ett säkerhetshål så "
"behöver sökvägen ägas av användaren mrtg och gruppen www-data. Föreslagen "
"rättighetsinställning är 0750 - fullt skrivbar av mrtg, läsbar av www-data-"
"gruppen och otillgänglig för övriga."

#. Type: boolean
#. Description
#: ../mrtg.templates:2001
msgid ""
"Alternatively, you can use another path for generated graphics. Note that "
"keeping this directory empty when using another path is not a problem."
msgstr ""
"Ett alternativ är att du anger en annan sökväg där grafikfilerna ska "
"placeras. Det är inte ett besvär att låta originalsökvägen vara tom."

Bug#998810: debspawn: does not honor InjectedPkgsDir

[Ritesh Raj Sarraf]

Package: debspawn
Version: 0.5.0-1
Severity: normal
X-Debbugs-Cc: r...@debian.org

As per the manual page, settings defined in /etc/debspawn/global.json
should override the defaults.

On my machine, I have the following in `/etc/debspawn/global.json`: 

{
"APTCacheDir": "/var/tmp/Debian-Build/temp/",
"TempDir": "/var/tmp/Debian-Build/Build/",
"ResultsDir": "/var/tmp/Debian-Build/Result/",
"InjectedPkgsDir": "/var/tmp/Debian-Build/pbuilder-deps/"
}

But the same is not honored by debspawn. It does not pick the local debs
from the specified InjectedPkgsDir path. OTOH, if I go with the
defaults, i.e. `/var/lib/debspawn/injected-pkgs/`, it works.


IN fact, while looking at the setup on my host machine, it looks like
the settings aren't honored at all. To workaround it, I have been adding
symlinks instead:

```
rrs@priyasi:.../debspawn$ file *
aptcache:  symbolic link to /var/tmp/Debian-Build/temp/
images:directory
injected-pkgs: directory
results:   symbolic link to /var/tmp/Debian-Build/Result/
```

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

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

Versions of packages debspawn depends on:
ii  debootstrap1.0.125
ii  python33.9.7-1
ii  python3-toml   0.10.2-1
ii  systemd-container  249.5-2
ii  zstd   1.4.8+dfsg-3

Versions of packages debspawn recommends:
ii  build-essential  12.9
ii  devscripts   2.21.4

Versions of packages debspawn suggests:
ii  sudo  1.9.5p2-3

-- no debconf information

Bug#998809: jami: No echo cancellation on pipewire-pulse

[Bruno Kleinert]

Package: jami
Version: 20210112.2.b757bac~ds1-1
Severity: normal
X-Debbugs-Cc: fu...@debian.org

Hi,

I'm using Jami with speakers and webcam microphone. When I use pipewire-pulse
instead of pulseaudio, there is no echo cancellation applied in Jami (People I
call tell me they hear an echo of themselves).

When I use Jami on pulseaudio, /usr/lib/pulse-15.0+dfsg1/modules/module-echo-
cancel.so is used to cancel the echo. Instead, on pipewire-pulse
/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-echo-cancel.so seems
to be available, but is not used to cancel the echo. I would expect echo
cancellation to work on both audio daemons.

I report the bug against jami because I observe and reproduce it with this
package. If it is an issue in one of the pipewire packages, please forward
accordingly.

Cheers,
Bruno



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

Kernel: Linux 5.14.0-4-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.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 jami depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-2
ii  jami-daemon  20210112.2.b757bac~ds1-1
ii  libayatana-appindicator3-1   0.5.5-3
ii  libc62.32-4
ii  libcairo21.16.0-5
ii  libcanberra-gtk3-0   0.30-8
ii  libcanberra0 0.30-8
ii  libclutter-1.0-0 1.26.4+dfsg-3
ii  libclutter-gtk-1.0-0 1.8.4-4+b1
ii  libgcc-s111.2.0-10
ii  libgdk-pixbuf-2.0-0  2.42.6+dfsg-2
ii  libglib2.0-0 2.70.1-1
ii  libgtk-3-0   3.24.30-3
ii  libnm0   1.32.12-1
ii  libnotify4   0.7.9-3
ii  libpango-1.0-0   1.48.10+ds1-1
ii  libqrencode4 4.1.1-1
ii  libqt5core5a 5.15.2+dfsg-12
ii  libqt5dbus5  5.15.2+dfsg-12
ii  libqt5gui5   5.15.2+dfsg-12
ii  libqt5sql5   5.15.2+dfsg-12
ii  libqt5sql5-sqlite5.15.2+dfsg-12
ii  libstdc++6   11.2.0-10
ii  libwebkit2gtk-4.0-37 2.34.1-1
ii  libx11-6 2:1.7.2-2+b1

jami recommends no packages.

jami suggests no packages.

-- no debconf information

Bug#984063: Please lets coordinate itk4/itk5 issues (Was: Bug#984063)

[Andreas Tille]

Hi,

this mail from Jose 

Am Sat, Nov 06, 2021 at 01:33:29AM +0100 schrieb Jose Luis Rivero:
> Hello! Gazebo maintainer here, affected by this RC bug. Looking into
> upstream repository there is a potential commit that can be used to patch
> this problem until new versions land in Debian:
> 
> https://github.com/InsightSoftwareConsortium/ITK/commit/840f22feb351739359a8fdb55304124823a3a8c9

caused me having a look into the Git repository of insighttoolkit4[1].
It is missing the NMU 4.13.3withdata-dfsg1-4.1 by Andreas Beckmann and
there are now the first commits done by Steve for insighttoolkit5
version 5.2.1 which was ITPed by Ghislain[2].

I think we need to discuss whether

  1. We want to simply replace insighttoolkit4 (which makes the
 usage of the existing repository[1] sensible - but please inject
 the NMU changes at least in d/changelog

  2. We should start ITK5 in a new repository and maintain both
 versions at least for some time in parallel until all packages
 that currently use ITK4 are migrated.

In any case people who are interested in ITK should coordinate their
work and talk to each other which I'd like to kindly invite you to
do here on the Debian Med mailing list (any other channel is fine for
sure).

> Let me know if you need more help or assistance.

Every assistance is welcome.  BTW, I tried to apply the mentioned patch
to insighttoolkit4  4.13.3withdata-dfsg1-4.1  but it does not apply.  I
did not investigated why since I think some things should be clarified
first.

Kind regards

  Andreas.

[1] https://salsa.debian.org/med-team/insighttoolkit
[2] https://bugs.debian.org/995829

-- 
http://fam-tille.de

Bug#998757: security.debian.org: OVAL feed issues

[Sébastien Delafond]

On 07/11 10:22, Noah Meyerhans wrote:
> [...]  These two OVAL definitions list essentially identical criteria,
> yet their actual status in bullseye is quite different:
> 
> CVE-2020-28200 is still present in bullseye and is a legitimate
> finding by any scanner based on these definitions:
> https://security-tracker.debian.org/tracker/CVE-2020-28200
> 
> CVE-2012-0833 is not present in any bullseye and should not trigger a
> finding from a scanner:
> https://security-tracker.debian.org/tracker/CVE-2012-0833
> 
> If we look at the security-tracker's JSON feed [2], we see some
> details that should be reflected in the OVAL feed but aren't, in
> particular the "status" field:
> 
> "CVE-2012-0833": { ...
>   "releases": { ...
> "bullseye": { "status": "resolved", "repositories": {
>   "bullseye": "1.4.4.11-2" }, "fixed_version": "0", "urgency":
>   "unimportant"
> }, ...  } and
> 
> "CVE-2020-28200": {
>   "releases": { ...
> "bullseye": { "status": "open", "repositories": { "bullseye":
>   "1:2.3.13+dfsg1-2" }, "urgency": "not yet assigned"
> }, ...  },
> 
> I'm not super familiar with the semantic expectations of OVAL, but I
> think logically we want to represent CVE-2012-0833 somewhat
> differently in OVAL using logic similar to:
> 
> if status == resolved: if fixed_version == 0:
> # All versions of this package in this release's repos are fixed:
> OVAL_criterion = "package is earlier than
> min(values.repositories)"
>   else OVAL_criterion = "package is earlier than fixed_version"
> 
> In this case the criterion for CVE-2012-0833 would be:
> 
>  test_ref="oval:org.debian.oval:tst:4696"/>
> 
> Which I believe is correct.  If a system is running bullseye and has
> 1.4.4.11-2 or later installed, then a scanner should determine that
> this vulnerability is not present.

Thanks for the detailed report.

I agree the current "greater than 0" criterion in OVAL isn't right, and
ideally the JSON export would correctly list "min(version for version in
all_versions_ever_in(repository)" in fixed_version instead of the
current "0": the current OVAL code would then expose the correct result
automatically.

I'm not sure how feasible that is, as I'm not familiar with the JSON
export code, but what I would *most* like to avoid here, is having that
min() computation be performed on the OVAL side: it doesn't belong
there, IMO.

The other approach is for the OVAL code to simply skip a CVE entirely if
the target distribution was never affected: it would remove the current
false positives, and the only downside would be the lack of an alert is
someone was to accidentally downgrade or hang on to a vulnerable version
(from a previous stable suite for instance). I'm not sure if our OVAL
exports should really for such a scenario, so maybe that's the better
option here.

Cheers,

-- 
Seb

Bug#996668: Acknowledgement (cinnamon-settings-daemon: cinnamon shutdown hang)

[Matt Yates]

I had the Nextcloud client app running.  Disabling it had no effect.

Removing systemd seems to eliminate the problem.  Although not really a
solution, I installed Devuan and tried running their version of Debian
Testing with sysvinit instead of systemd.  Cinnamon shuts down as
expected.  So far, I have not missed systemd, so I will probably just keep
using Devuan.

On Sun, Oct 17, 2021 at 1:27 AM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 996668:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996668.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> As you requested using X-Debbugs-CC, your message was also forwarded to
>   matthew.z.ya...@gmail.com
> (after having been given a Bug report number, if it did not have one).
>
> Your message has been sent to the package maintainer(s):
>  Debian Cinnamon Team 
>
> If you wish to submit further information on this problem, please
> send it to 996...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 996668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996668
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#998677: bash: Segfault when starting gnome-session

[Ben Finney]

On 06-Nov-2021, Ben Finney wrote:
> When I invoke GDB on the core dump, this is the session:
> 
> =
> $ coredumpctl gdb
> […]
>PID: 45094 (bash)
>UID: 1000 (bignose)
>GID: 1000 (bignose)
> Signal: 11 (SEGV)
>  Timestamp: Sat 2021-11-06 23:01:32 AEDT (54s ago)
>   Command Line: -/bin/bash -c $'/usr/bin/gnome-session -l '
> Executable: /usr/bin/bash
> […]
> #62 0x55c7801d075b execute_command_internal (bash + 
> 0x4a75b)
> #63 0x55c780222bd9 parse_and_execute (bash + 0x9cbd9)

After a lot of narrowing down what in this user's session could cause
Bash to segmentation fault, I've found that this makes the difference:

* When the user's home directory contains ‘$HOME/.gnomerc’, the Bash
  segmentation fault occurs.

  The content of ‘$HOME/.gnomerc’ is:

=
# $HOME/.gnomerc
# Roaming profile: User specific configuration for GNOME session.

. ~/.profile
=

  which simply “sources” the user's shell profile script.

  This file (and the ‘$HOME/.profile’) has been present for years with
  the same content, without incident on previous Gnome or Bash
  versions.

* When the user's home directory does not contain ‘$HOME/.gnomerc’,
  the user login works fine, as it did a month ago.

So the Gnome session is (I assume) invoking that script, which in turn
sources the ‘$HOME/.profile’ script; and somehow that causes Bash to
segfault.

This same ‘$HOME/.profile’ script is large and somewhat sensitive; but
it should never cause Bash to crash, and never does cause it to crash
when logging in outside Gnome.

-- 
 \ “In any great organization it is far, far safer to be wrong |
  `\  with the majority than to be right alone.” —John Kenneth |
_o__)Galbraith, 1989-07-28 |
Ben Finney 


signature.asc
Description: PGP signature

Bug#956713: closed by Debian FTP Masters (reply to Ying-Chun Liu (PaulLiu) ) (Bug#956713: fixed in telegram-cli 1.3.1+git20160323.6547c0b21-3)

[Helmut Grohne]

Control: reopen -1
Control: affects -1 - src:telegram-cli

On Sun, Nov 07, 2021 at 12:09:10PM +, Debian Bug Tracking System wrote:
> #956713: autoconf-archive: AX_LUA_HEADERS uses AC_RUN_IFELSE
> 
> It has been closed by Debian FTP Masters  
> (reply to Ying-Chun Liu (PaulLiu) ).

This is a bug in autoconf-archive. You fixed a copy of the bug in
telegram-cli. As such, it no longer affects telegram-cli, but the bug is
still there in autoconf-archive.

Helmut

Bug#991443: wolfssl: CVE-2021-37155

[Felix Lechner]

Control: tags -1 + pending

Hi,

This upload of wolfssl version 5.0.0-1 to the NEW queue [1] will close
your bug in the near future. Thanks!

Kind regards
Felix Lechner

[1] https://ftp-master.debian.org/new/wolfssl_5.0.0-1.html

Bug#992174: wolfssl: CVE-2021-38597

[Felix Lechner]

Control: tags -1 + pending

Hi,

This upload of wolfssl version 5.0.0-1 to the NEW queue [1] will close
your bug in the near future. Thanks!

Kind regards
Felix Lechner

[1] https://ftp-master.debian.org/new/wolfssl_5.0.0-1.html

Bug#991663: wolfssl: CVE-2021-24116

[Felix Lechner]

Control: tags -1 + pending

Hi,

This upload of wolfssl version 5.0.0-1 to the NEW queue [1] will close
your bug in the near future. Thanks!

Kind regards
Felix Lechner

[1] https://ftp-master.debian.org/new/wolfssl_5.0.0-1.html

Bug#995820: wolfssl: Import new upstream version

[Felix Lechner]

Control: tags -1 + pending

Hi,

This upload of wolfssl version 5.0.0-1 to the NEW queue [1] will close
your bug in the near future. Thanks!

Kind regards
Felix Lechner

[1] https://ftp-master.debian.org/new/wolfssl_5.0.0-1.html

Bug#982426: moosefs: FTBFS when systemd is installed

[Logan Rosen]

Control: tags -1 patch

Hi,

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

  * Pass --with-systemdsystemunitdir=no to configure script to fix FTBFS in
Ubuntu (see Debian: #982426).

This explicitly tells the configure script not to create the systemd
service files, avoiding the FTBFS. Thanks for considering the patch.

Logan
diff -Nru moosefs-3.0.116/debian/rules moosefs-3.0.116/debian/rules
--- moosefs-3.0.116/debian/rules2020-02-19 16:50:24.0 -0500
+++ moosefs-3.0.116/debian/rules2021-11-07 21:07:51.0 -0500
@@ -26,6 +26,7 @@
 --with-default-user=mfs \
 --with-default-group=mfs \
 --localstatedir=/var/lib  \
+   --with-systemdsystemunitdir=no \
 ;
 
 override_dh_makeshlibs:

Bug#827889: formatting information shown on screen but not formatting

[Paul Wise]

On Wed, 22 Jun 2016 08:24:15 +0200 Erik Thiele wrote:

> LANG=C gwakeonlan
> --> all OK
> press the + button and see first line of window in bold letters.
> 
> LANG=de_DE.UTF-8 gwakeonlan
> -->
> /usr/bin/gwakeonlan:435: GtkWarning: Failed to set text from markup due
> to error parsing markup: Fehler in Zeile 1, Zeichen 73: Element
> »markup« wurde geschlossen, aber das derzeit offene Element ist »b«
> builder.add_from_file(__searchPath('ui', '%s.glade' % APP_NAME))
> 
> press the + button and see first line of window
> shown as "Rechnername und die MACAdresse eingeben"
> 
> there are probably the / missing in the closing tags.

gwakeonlan was reintroduced to Debian unstable.

Please check if the new version fixes the issue you reported.

If the bug is fixed already, please let us know or close the
bug report in the version where the bug was fixed.

If the bug is not yet fixed, please file an issue upstream on GitHub
and mark this bug report as forwarded to the upstream issue.

https://github.com/muflone/gwakeonlan

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#734254: gwakeonlan: Show machine on/off status in list

[Paul Wise]

On Sun, 05 Jan 2014 10:52:42 +0100 Andreas Tscharner wrote:

> I'd like to see the on/off status of a/ll machine/s in the list (a column
> or different colors, etc.), maybe unsing some sort of ping (which does not
> require root prvileges).

gwakeonlan was reintroduced into Debian unstable.

Please check if the new version implements the feature you requested.

If the feature is implemented already, please let us know or close the
bug report in the version where the feature was added.

If the feature is not yet implemented, please file a request upstream
on GitHub and mark this bug report as forwarded to the upstream issue.

https://github.com/muflone/gwakeonlan

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#795425: gwakeonlan: improvements to desktop file and icon location

[Paul Wise]

On Thu, 13 Aug 2015 23:24:08 +0200 Ronny Standtke wrote:

> The gwakeonlan icon looks very blurry on desktops with larger icons
> (e.g. GNOME). I noticed that the svg icon is installed in a non-standard
> folder. When adding a link to the correct location (just add the
> attached file
> gwakeonlan.links to the debian directory) and change the desktop file
> accordingly (see attached diff), the gwakeonlan icon looks much better.
> The diff also adds a GenericName to the desktop file.

gwakeonlan was reintroduced to Debian unstable.

The SVG icon has moved to the correct location.

The desktop file has changed a bit so your patch no longer applies.

Please check the new desktop file and if it needs any changes,
then please send upstream a pull request on GitHub:

https://github.com/muflone/gwakeonlan

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#984224: lomiri-app-launch: ftbfs with GCC-11

[peter green]

tags 984224 +patch
thanks

I started off by removing -Werror, IMO -Werror combined with -Wall
is only appropriate for use during development as it is likely to cause
failures wen new compilers are released.

I then ran into a bunch of errors like.


In file included from /usr/include/glib-2.0/glib/glib-typeof.h:39,
 from /usr/include/glib-2.0/glib/gatomic.h:28,
 from /usr/include/glib-2.0/glib/gthread.h:32,
 from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
 from /usr/include/glib-2.0/glib.h:32,
 from 
/lomiri-app-launch-0.0.90/liblomiri-app-launch/lomiri-app-launch.h:20,
 from 
/lomiri-app-launch-0.0.90/liblomiri-app-launch/application.cpp:21:
/usr/include/c++/10/type_traits:2930:3: error: template with C linkage
 2930 |   template
  |   ^~~~
/lomiri-app-launch-0.0.90/liblomiri-app-launch/application.cpp:20:1: note: âextern 
"C"â linkage started here
   20 | extern "C" {
  |


Which i fixed by changing the header includes to ensure glib.h was included outside of 
any extern "C" block.

At this point I realised I was in-fact testing with gcc 10, so I moved from 
testing in a raspbian
bookworm-staging environment to a Debian bookworm arm64 environment.

The build then failed with a symbols file error.


- (arch=!alpha !amd64 !hppa !i386 !m68k !mips64el !mipsel !powerpc !ppc64 
!ppc64el !riscv64 !s390x !sh4 !x32)_ZN6lomiri10app_launch5AppIDC1ERKS1_@Base 
0.0.90
+#MISSING: 0.0.90-8+rpi1# (arch=!alpha !amd64 !hppa !i386 !m68k !mips64el 
!mipsel !powerpc !ppc64 !ppc64el !riscv64 !s390x !sh4 
!x32)_ZN6lomiri10app_launch5AppIDC1ERKS1_@Base 0.0.90
- (arch=!alpha !amd64 !hppa !i386 !m68k !mips64el !mipsel !powerpc !ppc64 
!ppc64el !riscv64 !s390x !sh4 !x32)_ZN6lomiri10app_launch5AppIDC2ERKS1_@Base 
0.0.90
+#MISSING: 0.0.90-8+rpi1# (arch=!alpha !amd64 !hppa !i386 !m68k !mips64el 
!mipsel !powerpc !ppc64 !ppc64el !riscv64 !s390x !sh4 
!x32)_ZN6lomiri10app_launch5AppIDC2ERKS1_@Base 0.0.90


I fed these symbols (with the @Base removed) through a demangler and curiously 
they both demangled to the same thing.

lomiri::app_launch::AppID::AppID(lomiri::app_launch::AppID const&)

I can't find any reference to this constructor in the definition of AppID. 
Therefore
I think this is an auto-generated copy constructor that may be inlined and 
hence not
show up in the symbols depending on compiler optimization. The fact it has 
negated
architecture specifiers for a whole load of architectures reinforces this idea. 
As
such I marked the symbols as "optional=inline".

A debdiff has been attatched and an upload has been made to raspbian, no intent 
to NMU
in Debian.
diff -Nru lomiri-app-launch-0.0.90/debian/changelog 
lomiri-app-launch-0.0.90/debian/changelog
--- lomiri-app-launch-0.0.90/debian/changelog   2021-05-23 22:41:04.0 
+
+++ lomiri-app-launch-0.0.90/debian/changelog   2021-11-08 00:26:53.0 
+
@@ -1,3 +1,13 @@
+lomiri-app-launch (0.0.90-8+rpi1) bookworm-staging; urgency=medium
+
+  * Remove -Werror, it breaks the build with gcc-11 (Closes: 984224).
+  * Adjust includes to avoid including glib.h inside extern "C" as
+this causes build failures.
+  * Mark a couple of symbols that disappeard with gcc-11 as
+optional=inline
+
+ -- Peter Michael Green   Mon, 08 Nov 2021 00:26:53 
+
+
 lomiri-app-launch (0.0.90-8) unstable; urgency=medium
 
   * debian/control:
diff -Nru lomiri-app-launch-0.0.90/debian/liblomiri-app-launch0.symbols 
lomiri-app-launch-0.0.90/debian/liblomiri-app-launch0.symbols
--- lomiri-app-launch-0.0.90/debian/liblomiri-app-launch0.symbols   
2021-05-23 22:38:47.0 +
+++ lomiri-app-launch-0.0.90/debian/liblomiri-app-launch0.symbols   
2021-11-08 00:26:53.0 +
@@ -17,10 +17,10 @@
  
_ZN6lomiri10app_launch5AppID8discoverERKSt10shared_ptrINS0_8RegistryEERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESE_NS1_15VersionWildcardE@Base
 0.0.90
  
_ZN6lomiri10app_launch5AppID8discoverERKSt10shared_ptrINS0_8RegistryEERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESE_SE_@Base
 0.0.90
  
_ZN6lomiri10app_launch5AppIDC1ENS0_10TypeTaggerINS1_10PackageTagENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcENS2_INS1_10AppNameTagES9_EENS2_INS1_10VersionTagES9_EE@Base
 0.0.90
- (arch=!alpha !amd64 !hppa !i386 !m68k !mips64el !mipsel !powerpc !ppc64 
!ppc64el !riscv64 !s390x !sh4 !x32)_ZN6lomiri10app_launch5AppIDC1ERKS1_@Base 
0.0.90
+ (optional=inline|arch=!alpha !amd64 !hppa !i386 !m68k !mips64el !mipsel 
!powerpc !ppc64 !ppc64el !riscv64 !s390x !sh4 
!x32)_ZN6lomiri10app_launch5AppIDC1ERKS1_@Base 0.0.90
  _ZN6lomiri10app_launch5AppIDC1Ev@Base 0.0.90
  
_ZN6lomiri10app_launch5AppIDC2ENS0_10TypeTaggerINS1_10PackageTagENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcENS2_INS1_10AppNameTagES9_EENS2_INS1_10VersionTagES9_EE@Base
 0.0.90
- (arch=!alpha !amd64 !hppa !i386 !m68k !mips64el !mipsel !powerpc !ppc64 
!ppc64el !riscv64 !s390x !sh4 

Bug#402740: stone: fails to start with xhost/bitmask

[Paul Wise]

On Tue, 12 Dec 2006 12:31:16 + Tobias Richter wrote:

> The manual advertizes:
>    xhost/mask
> Only  machines  on  specified  networks  are  permitted  to  connect  
> to the program.  
> In the case of class C network 192.168.1.0, for example, use 
> 192.168.1.0/255.255.255.0.
> 
> doing so stone says:
> 
> $ stone proxy  10.9.11.0/255.255.255.0
> Dec 12 12:25:08.910949 46931893356240 start (2.3c) [15589]
> Dec 12 12:25:08.911258 46931893356240 netmask by bits pattern is 
> deprecated: 10.9.11.0/255.255.255.0
> 
> and quits. 'deprecated' does not say forbidden. Using 10.9.11.0/24 works, 
> though.

stone has been reintroduced to Debian unstable with version 2.4-1,
please test if this issue occurs with the new version.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#402740: stone: fails to start with xhost/bitmask

[Paul Wise]

On Tue, 12 Dec 2006 12:31:16 + "root" wrote:

> The manual advertizes:
>xhost/mask
>   Only  machines  on  specified  networks  are  permitted  to  connect  
> to the program.  
>   In the case of class C network 192.168.1.0, for example, use 
> 192.168.1.0/255.255.255.0.
> 
> doing so stone says:
> 
>   $ stone proxy  10.9.11.0/255.255.255.0
>   Dec 12 12:25:08.910949 46931893356240 start (2.3c) [15589]
>   Dec 12 12:25:08.911258 46931893356240 netmask by bits pattern is 
> deprecated: 10.9.11.0/255.255.255.0
> 
> and quits. 'deprecated' does not say forbidden. Using 10.9.11.0/24 works, 
> though.

stone has been reintroduced to Debian unstable with version 2.4-1,
please test if this issue occurs with the new version.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#403401: stone: FTBFS on GNU/Hurd

[Paul Wise]

Control: found -1 2.4-1

On Sun, 17 Dec 2006 06:55:46 +0900 (JST) Tatsuya Kinoshita wrote:

> The build log in stone_2.3-1_hurd-i386
> 
> http://experimental.debian.net/fetch.php?&pkg=stone&ver=2.3-1&arch=hurd-i386&stamp=1154810389&file=log&as=raw
> 
> seems that stone has an FTBFS bug on GNU/Hurd.  The cause of this
> bug is "error: sys/prctl.h: No such file or directory".  This is
> similar to #374771, "FTBFS on GNU/kFreeBSD".

I note this still occurs with the reintroduced 2.4-1 version:

https://buildd.debian.org/status/fetch.php?pkg=stone&arch=hurd-i386&ver=2.4-1&stamp=1636226817&raw=0

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#995393: fakeroot: FTBFS on ppc64el

[Clint Adams]

On Thu, Sep 30, 2021 at 04:46:47PM +0200, Frédéric Bonnard wrote:
> Not sure what optimization breaks, I just tried changing openat() to
> modify some aggressive optimization on that function and it helped.

The optimization seems to break with -O1, but not with
-O0 -fcombine-stack-adjustments -fcompare-elim -fcprop-registers -fdefer-pop 
-fforward-propagate -fguess-branch-probability -fipa-profile -fipa-pure-const 
-fipa-reference -fipa-reference-addressable -fmerge-constants 
-fomit-frame-pointer -freorder-blocks -fshrink-wrap -fsplit-wide-types 
-ftree-builtin-call-dce -ftree-ccp -ftree-ch -ftree-coalesce-vars 
-ftree-copy-prop -ftree-dce -ftree-dominator-opts -ftree-fre -ftree-sink 
-ftree-slsr -ftree-ter -fbranch-count-reg -fdelayed-branch -fdse 
-fif-conversion -fif-conversion2 -finline-functions-called-once 
-fmove-loop-invariants -fssa-phiopt -fipa-modref -ftree-bit-ccp -ftree-dse 
-ftree-pta -ftree-sra

It also seems fine at -O2 if fprintf(stderr, "%i, %s, %x\n", dir_fd, pathname, 
flags);
is called prior to next_openat.

Bug#997203: gigedit: FTBFS: ../compat.h:194:21: error: ‘const Pango::Alignment Pango::ALIGN_LEFT’ redeclared as different kind of entity

[peter green]

Tags 997203 +patch
Thanks

I ran into this issue in Raspbian and found I could fix it by disabling the 
block in question
in compat.h. I have uploaded this change to raspbian, A debdiff should appear 
soon at
https://debdiffs.raspbian.org/main/g/gigedit No intent to NMU in Debian.

Bug#998807: draco: please mark some symbols as optional to fix s390x build in Ubuntu

[Gianfranco Costamagna]

Source: draco
Version: 1.4.3+dfsg-2
tags: patch

Hello, please find and check the attached patch to fix the build failure in 
Ubuntu s390x architecture.

thanks,

Gianfranco
diff -Nru draco-1.4.3+dfsg/debian/changelog draco-1.4.3+dfsg/debian/changelog
--- draco-1.4.3+dfsg/debian/changelog   2021-10-28 22:58:50.0 +0200
+++ draco-1.4.3+dfsg/debian/changelog   2021-11-07 22:39:18.0 +0100
@@ -1,3 +1,9 @@
+draco (1.4.3+dfsg-2ubuntu2) jammy; urgency=medium
+
+  * Refresh s390x symbols
+
+ -- Gianfranco Costamagna   Sun, 07 Nov 2021 
22:39:18 +0100
+
 draco (1.4.3+dfsg-2) unstable; urgency=medium
 
   * Upload to unstable.
diff -Nru draco-1.4.3+dfsg/debian/libdraco1a.symbols 
draco-1.4.3+dfsg/debian/libdraco1a.symbols
--- draco-1.4.3+dfsg/debian/libdraco1a.symbols  2021-10-16 20:20:29.0 
+0200
+++ draco-1.4.3+dfsg/debian/libdraco1a.symbols  2021-11-07 22:39:18.0 
+0100
@@ -128,11 +128,11 @@
  
_ZN5draco11PlyPropertyC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEENS_8DataTypeES9_@Base
 1.4.3+dfsg
  
(arch-bits=32|optional)_ZN5draco12CrossProductIxEENS_7VectorDIT_Li3EEERKS3_S5_@Base
 1.4.3+dfsg
  
(arch-bits=64|optional)_ZN5draco12CrossProductIlEENS_7VectorDIT_Li3EEERKS3_S5_@Base
 1.4.3+dfsg
- 
_ZN5draco12DracoOptionsINS_17GeometryAttribute4TypeEE19GetAttributeOptionsERKS2_@Base
 1.4.3+dfsg
- _ZN5draco12DracoOptionsIiE19GetAttributeOptionsERKi@Base 1.4.3+dfsg
- _ZN5draco12EncodeVarintIjEEbT_PNS_13EncoderBufferE@Base 1.4.3+dfsg
+ 
(optional)_ZN5draco12DracoOptionsINS_17GeometryAttribute4TypeEE19GetAttributeOptionsERKS2_@Base
 1.4.3+dfsg
+ (optional)_ZN5draco12DracoOptionsIiE19GetAttributeOptionsERKi@Base 1.4.3+dfsg
+ (optional)_ZN5draco12EncodeVarintIjEEbT_PNS_13EncoderBufferE@Base 1.4.3+dfsg
  (arch-bits=32)_ZN5draco12EncodeVarintIyEEbT_PNS_13EncoderBufferE@Base 
1.4.3+dfsg
- (arch-bits=64)_ZN5draco12EncodeVarintImEEbT_PNS_13EncoderBufferE@Base 
1.4.3+dfsg
+ 
(arch-bits=64|optional)_ZN5draco12EncodeVarintImEEbT_PNS_13EncoderBufferE@Base 
1.4.3+dfsg
  _ZN5draco13DecodeSymbolsEjiPNS_13DecoderBufferEPj@Base 1.4.3+dfsg
  _ZN5draco13DecoderBuffer10BitDecoderC1Ev@Base 1.4.3+dfsg
  _ZN5draco13DecoderBuffer10BitDecoderC2Ev@Base 1.4.3+dfsg
@@ -229,7 +229,7 @@
  _ZN5draco15StdioFileWriterD0Ev@Base 1.4.3+dfsg
  _ZN5draco15StdioFileWriterD1Ev@Base 1.4.3+dfsg
  _ZN5draco15StdioFileWriterD2Ev@Base 1.4.3+dfsg
- 
_ZN5draco16DecodeRawSymbolsINS_17RAnsSymbolDecoderEEEbjPNS_13DecoderBufferEPj@Base
 1.4.3+dfsg
+ 
(optional)_ZN5draco16DecodeRawSymbolsINS_17RAnsSymbolDecoderEEEbjPNS_13DecoderBufferEPj@Base
 1.4.3+dfsg
  _ZN5draco16DirectBitDecoder13StartDecodingEPNS_13DecoderBufferE@Base 
1.4.3+dfsg
  _ZN5draco16DirectBitDecoder5ClearEv@Base 1.4.3+dfsg
  _ZN5draco16DirectBitDecoderC1Ev@Base 1.4.3+dfsg
@@ -243,7 +243,7 @@
  _ZN5draco16DirectBitEncoderC2Ev@Base 1.4.3+dfsg
  _ZN5draco16DirectBitEncoderD1Ev@Base 1.4.3+dfsg
  _ZN5draco16DirectBitEncoderD2Ev@Base 1.4.3+dfsg
- 
_ZN5draco16EncodeRawSymbolsINS_17RAnsSymbolEncoderEEEbPKjijiPKNS_7OptionsEPNS_13EncoderBufferE@Base
 1.4.3+dfsg
+ 
(optional)_ZN5draco16EncodeRawSymbolsINS_17RAnsSymbolEncoderEEEbPKjijiPKNS_7OptionsEPNS_13EncoderBufferE@Base
 1.4.3+dfsg
  
_ZN5draco16GeometryMetadata20AddAttributeMetadataESt10unique_ptrINS_17AttributeMetadataESt14default_deleteIS2_EE@Base
 1.4.3+dfsg
  _ZN5draco16GeometryMetadataC1ERKS0_@Base 1.4.3+dfsg
  _ZN5draco16GeometryMetadataC2ERKS0_@Base 1.4.3+dfsg
@@ -388,8 +388,8 @@
  
(arch-bits=64)_ZN5draco17WriteBufferToFileEPKvmRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 1.4.3+dfsg
  
_ZN5draco18AttributeTransform24InitTransformedAttributeERKNS_14PointAttributeEi@Base
 1.4.3+dfsg
  _ZN5draco18IsDataTypeIntegralENS_8DataTypeE@Base 1.4.3+dfsg
- 
_ZN5draco19DecodeTaggedSymbolsINS_17RAnsSymbolDecoderEEEbjiPNS_13DecoderBufferEPj@Base
 1.4.3+dfsg
- 
_ZN5draco19EncodeTaggedSymbolsINS_17RAnsSymbolEncoderEEEbPKjiiRKSt6vectorIjSaIjEEPNS_13EncoderBufferE@Base
 1.4.3+dfsg
+ 
(optional)_ZN5draco19DecodeTaggedSymbolsINS_17RAnsSymbolDecoderEEEbjiPNS_13DecoderBufferEPj@Base
 1.4.3+dfsg
+ 
(optional)_ZN5draco19EncodeTaggedSymbolsINS_17RAnsSymbolEncoderEEEbPKjiiRKSt6vectorIjSaIjEEPNS_13EncoderBufferE@Base
 1.4.3+dfsg
  
_ZN5draco19RemoveFileExtensionERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 1.4.3+dfsg
  
_ZN5draco20ReplaceFileExtensionERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES7_@Base
 1.4.3+dfsg
  _ZN5draco21ComputeShannonEntropyEPKjiiPi@Base 1.4.3+dfsg
@@ -454,9 +454,9 @@
  
_ZN5draco22ReadPointCloudFromFileERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 1.4.3+dfsg
  _ZN5draco22SelectPredictionMethodEiPKNS_17PointCloudEncoderE@Base 1.4.3+dfsg
  
_ZN5draco23KdTreeAttributesDecoder24DecodePortableAttributesEPNS_13DecoderBufferE@Base
 1.4.3+dfsg
- 
_ZN5draco23KdTreeAttributesDecoder34TransformAttributeBackToSignedTypeIaEEbPNS_14PointAttributeEi@Base
 1.4.3+dfsg
+ 
(optional)_ZN5draco23KdTreeAttributesDecoder34TransformAttributeBackToSignedTypeIaEEbPNS_14PointAttributeEi@B

Bug#998718: Brasero fails (on Testing) burning an ISO image on a CD-RW

[Mauro Sacchetto]

==
samiel@darkstar:~$ isoimage=/home/samiel/debian-11.1.0-amd64-netinst.iso
samiel@darkstar:~$ xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed 
$isoimage

xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project.

xorriso : NOTE : Disc status unsuitable for writing
Drive current: -outdev '/dev/sr0'
Media current: CD-RW
Media status : is written , is closed
Media summary: 1 session, 193536 data blocks,  378m data, 0 free
Beginning to blank medium in mode 'fast'.
xorriso : UPDATE : Blanking  ( 1.0% done in 1 seconds )
...
xorriso : UPDATE : Blanking  ( 97.8% done in 53 seconds )
Blanking done
xorriso : NOTE : Re-assessing -outdev '/dev/sr0'
Drive current: -outdev '/dev/sr0'
Media current: CD-RW
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data,  703m free
Beginning to write data track.
xorriso : UPDATE : Thank you for being patient. Working since 0 seconds.
...
xorriso : UPDATE : Thank you for being patient. Working since 43 seconds.
xorriso : UPDATE :    0 of  378 MB written (fifo 99%) [buf 100%] 3.8x.
...
xorriso : UPDATE :  378 of  378 MB written (fifo  0%) [buf 100%] 0.0x.
xorriso : UPDATE : Thank you for being patient. Working since 728 seconds.
Writing to '/dev/sr0' completed successfully.

xorriso : NOTE : Re-assessing -outdev '/dev/sr0'
xorriso : NOTE : Disc status unsuitable for writing
Drive current: -outdev '/dev/sr0'
Media current: CD-RW
Media status : is written , is closed
Media summary: 1 session, 193686 data blocks,  378m data, 0 free
==
It's all ok!
Than I try to burn the ISO woth Brasero launching it by console:
==
samiel@darkstar:~$ brasero

** (brasero:2837): WARNING **: 01:07:35.934: Could not establish a 
connection to Tracker: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.Tracker3.Miner.Files was not provided by any .service files


(brasero:2837): Gtk-WARNING **: 01:08:01.131: Failed to fetch network 
locations: È stato raggiunto il timeout
Sense key: 0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x0a 0x00 0x40 0xa0 0x03 
0x21 0x04 0x00 0x00 0x00 0x00 0x00

Segmentazion fault
==
and Brasero crashes
dmesg:
==
[ 1657.332142] sr 5:0:0:0: [sr0] tag#10 FAILED Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[ 1657.332151] sr 5:0:0:0: [sr0] tag#10 CDB: Prevent/Allow Medium 
Removal 1e 00 00 00 01 00
[ 1657.332231] brasero[2837]: segfault at 2f400 ip 7fc57b9e0231 sp 
7ffecc8f6368 error 4 in libc-2.32.so[7fc57b8a7000+149000]
[ 1657.332268] Code: 84 00 00 00 00 00 0f 1f 00 31 c0 c5 f8 77 c3 66 2e 
0f 1f 84 00 00 00 00 00 89 f9 48 89 fa c5 f9 ef c0 83 e1 3f 83 f9 20 77 
1f  fd 74 0f c5 fd d7 c1 85 c0 0f 85 df 00 00 00 48 83 c7 20 83 e1

==
I eject the CD-RW, inser it again and try to mount it:
==
root@darkstar:~# mount /home/samiel/debian-11.1.0-amd64-netinst.iso 
/media/cdrom

mount: /media/cdrom0: WARNING: source write-protected, mounted read-only.
==
In Nemo -- Devices now I see twice the CD-RW, the old one (not 
inspectable) and the new one (inspectable).
But If I try to mount it not by console, but from Nemo (when there is 
only an occurence of the device) I receive:

==
Impossible to mount debiam-11iso
Error mounting /dev/sr0 at /media/samiel7Debian...: no medium found on 
/dev/sro

After this:
==
samiel@darkstar:~$ isoimage=/home/samiel/debian-11.1.0-amd64-netinst.iso
samiel@darkstar:~$ xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed 
$isoimage

xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project.

libburn : FAILURE : SCSI command 12h yielded host problem: 0x4 
SG_ERR_DID_BAD_TARGET (Bad target, device not responding ?)

libburn : FAILURE : Command: INQUIRY : 12 00 00 00 24 00  : dxfer_len= 36
libburn : FATAL : Lost connection to drive
xorriso : FAILURE : Cannot acquire drive '/dev/sr0'
xorriso : FAILURE : -as cdrecord: Job could not be performed properly.
xorriso : aborting : -abort_on 'FAILURE' encountered 'FATAL'
==


Il 07/11/21 22:34, Thomas Schmitt ha scritto:
Did you already try what happens if you eject the CD and insert it 
again after spoiling the drive state with Brasero and before using the 
drive for mounting or for xorriso -toc ?

Bug#998333: RFS: lebiniou/3.63.1-1 -- user-friendly, powerful music visualization / VJing tool

[Bastian Germann]

Just copy and paste the thing down there to the copyright file, name it MIT-variant and use it in the two paragraphs 
that actually have that license.


Am 08.11.21 um 00:48 schrieb Olivier Girondel:

Hi Bastian,

Can you elaborate on what needs to be done/fixed please ?

I must admit I'm not a lawyer so I'm kind of lost there..

Best regards,

On November 7, 2021 11:38:58 PM GMT+01:00, Bastian Germann  
wrote:

Control: tags -1 moreinfo

Please check bug #998617 again.

The MIT-like license is that is still missing:

   * Permission to use, copy, modify, and distribute this software and its
   * documentation for any purpose and without fee is hereby granted,
   * provided that the above copyright notice appear in all copies and that
   * both that copyright notice and this permission notice appear in
   * supporting documentation.
   *
   * This file is provided AS IS with no warranties of any kind.  The author
   * shall have no liability with respect to the infringement of copyrights,
   * trade secrets or any patents by this file or any part thereof.  In no
   * event will the author be liable for any lost revenue or profits or
   * other special, indirect and consequential damages.

Which is NOT Expat.

Expat (that you still call "MIT" but should be renamed) must still be 
included for the
net.biniou.LeBiniou.appdata.xml.

--
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma 
brièveté.

Bug#998333: RFS: lebiniou/3.63.1-1 -- user-friendly, powerful music visualization / VJing tool

[Olivier Girondel]

Hi Bastian,

Can you elaborate on what needs to be done/fixed please ?

I must admit I'm not a lawyer so I'm kind of lost there..

Best regards, 

On November 7, 2021 11:38:58 PM GMT+01:00, Bastian Germann  
wrote:
>Control: tags -1 moreinfo
>
>Please check bug #998617 again.
>
>The MIT-like license is that is still missing:
>
>  * Permission to use, copy, modify, and distribute this software and its
>  * documentation for any purpose and without fee is hereby granted,
>  * provided that the above copyright notice appear in all copies and that
>  * both that copyright notice and this permission notice appear in
>  * supporting documentation.
>  *
>  * This file is provided AS IS with no warranties of any kind.  The author
>  * shall have no liability with respect to the infringement of copyrights,
>  * trade secrets or any patents by this file or any part thereof.  In no
>  * event will the author be liable for any lost revenue or profits or
>  * other special, indirect and consequential damages.
>
>Which is NOT Expat.
>
>Expat (that you still call "MIT" but should be renamed) must still be included 
>for the 
>net.biniou.LeBiniou.appdata.xml.
>

-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma 
brièveté.

Bug#996569: getmail6 naming issues

[Charles Cazabon]

Sudip Mukherjee  wrote:
> 
> 1) The Debian maintainers of getmail have offered to help with
> supporting python3 and have even submitted patches or pointed to their
> wip branches in github which I think were all rejected.

I have not rejected anything.  I have asked questions of people who submitted
patches *which currently do nothing except kill support for Python < 2.7*.

> 2) The previous Debian maintainers have also requested Charles to do
> the python3 development in open so that the effort is not duplicated.

I do not currently use a public forge for getmail development.  I have
reasons.

> 3) Reading https://marc.info/?l=getmail&m=151542154628352&w=2 I am not
> really convinced that Charles will ever support Python3.

You're wrong, then -- I'm not sure what you're basing that opinion on, besides
your own unsupported supposition.  I have already done part of the rewrite for
Python 3; I just don't have 10+ hours a week to devote to open-source/free
software the way I did two decades ago.

That message just says getmail would not be Python 3 compatible that year - it
says nothing whatsoever about getmail never supporting Python 3.

> 4) Charles says his getmail users' mailing list has been inundated
> with support requests. I have gone through the last 1 year history of
> the mailing list and could only find the last one from Michael and
> another one in December,2020 

Then you missed some.

> 5) Also noticed getmail user's positive experience upgrading to
> getmail6 at https://marc.info/?l=getmail&m=160131249528542&w=2

So some users have *not* hit bugs when running "getmail6".  I never said
differently.

> 6) https://marc.info/?l=getmail&m=160060476624283&w=2 shows the plight
> of a user who tried to continue using getmail with Debin testing.

That problem does not appear to actually be related to getmail.  It appears to
be a user running with a Python 2.7 that was compiled without SSL support.  I
thought getmail caught this error and issued a diagnostic, but maybe not --
it's been a long, long time since I used a Python that didn't have SSL.

There is no "plight" to running getmail on current Debian.  The complete
process is:

1. apt-get install python2.7
2. install real getmail, or don't even install it, just unpack it

That's it.  It works.  See:

/tmp/getmail-test$ tar xzf 
~/projects/getmail-trunk/dist/getmail-5.16.tar.gz 
/tmp/getmail-test$ dpkg -l python2.7

Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description

+++-==---==>
ii  python2.7  2.7.18-8 amd64Interactive high-level 
object-orie>

charlesc@vetinari:/tmp/getmail-test$ cd getmail-5.16/
charlesc@vetinari:/tmp/getmail-test/getmail-5.16$ ./getmail --help
Usage: getmail [options]

Options:
  --version show program's version number and exit
  -h, --helpshow this help message and exit
  -g DIR, --getmaildir=DIR
look in DIR for config/data files
  -r FILE, --rcfile=FILE
load configuration from FILE (may be given multiple
times)
  --dumpdump configuration and exit (debugging)
  --trace   print extended trace information (extremely verbose)
  -i FOLDER, --idle=FOLDER
maintain connection and listen for new messages in
FOLDER. Only applies if a single rc file is given 
with
a connection to an IMAP server that supports the 
IDLE
command

  Overrides:
The following options override those specified in any getmailrc file.

-v, --verbose   operate more verbosely (may be given multiple times)
--fingerprint   show SSL/TLS fingerprint and connection information
-q, --quiet operate quietly (only report errors)
-d, --deletedelete messages from server after retrieving
-l, --dont-delete   do not delete messages from server after retrieving
-a, --all   retrieve all messages
-n, --new   retrieve only unread messages


> 1) Since the development of getmail is not in the open it's possible
> that users have sent personal mail to Charles asking for support and

It's not "possible", it actually happens.  A lot.  About a lot of different
bugs.  See the "getmail6" changelog for the number of fixes, each one of which
I've probably received multiple support requests about.

> We think the best way is to remove the transitional package which will
> break the link between getmail and getmail6 so that Debian users who
> are using getmail will not automatically be upg

Bug#998744: calibre: Python byte-compile error when installing calibre

[yokota]

Hello Sajith,

> This is the relevant part from `apt install calibre`:
>
> 
> Setting up calibre (5.12.0+dfsg-1) ...
> Failed to byte-compile /usr/lib/calibre/calibre/utils/formatter.py:   File 
> "/usr/lib/calibre/calibre/utils/formatter.py", line 659
> if v := self.expr(expr):
>   ^
> SyntaxError: invalid syntax
> 

This error comes from obsolete python syntax.
This error was also reported at:
  https://bugs.launchpad.net/calibre/+bug/1942463

Fixes are:
  
https://github.com/kovidgoyal/calibre/commit/884839a691e800e56e185e10019a66b12feea640
and
  
https://github.com/kovidgoyal/calibre/commit/ed32130ca4cbbf235f5560e7c53f78c01eab1106

We must fix soon.

--
YOKOTA

Bug#996807: tinydns stops replying to queries after a few hours

[Eric Krohn]

Emil,

I ran into this problem with an old self-maintained dbndjb 1.05-9
package's tinydns, but mine hung after just one or two queries after a
recent upgrade (including libc6 2.32-4) and reboot.

My ./run file was:
exec envuidgid tinydns envdir ./env softlimit -d30 /usr/bin/tinydns

I tried running manually with strace interspersed, but that refused to
start until I dropped the softlimit -d30 (data segment size), and
then it ran fine. That got me to thinking that the problem is running out
of memory. So I bumped up -d30 to -d35 in ./run and tinydns runs
quite well now.

The tinydns 1.05-13 package uses chpst (from runit) instead of softlimit
(from daemontools), but I think the intent is the same.

I conjecture that something in libc6 2.32 increased the size of the data
segment. The work around/fix is to increase the data segment limit in
tinydns package's ./run file.

Ideally, tinydns should detect the problem and complain. That would have
saved a lot of frustration.

Bug#996569: getmail6 naming issues

[Sudip Mukherjee]

I have thought about it again while going through all the old mails of
getmail mailing list and also https://bugs.debian.org/936604 and these
are my thoughts:

1) The Debian maintainers of getmail have offered to help with
supporting python3 and have even submitted patches or pointed to their
wip branches in github which I think were all rejected.
2) The previous Debian maintainers have also requested Charles to do
the python3 development in open so that the effort is not duplicated.
3) Reading https://marc.info/?l=getmail&m=151542154628352&w=2 I am not
really convinced that Charles will ever support Python3.
4) Charles says his getmail users' mailing list has been inundated
with support requests. I have gone through the last 1 year history of
the mailing list and could only find the last one from Michael and
another one in December,2020 -
https://marc.info/?l=getmail&m=160716812508287&w=2 (but more on this
below)
5) Also noticed getmail user's positive experience upgrading to
getmail6 at https://marc.info/?l=getmail&m=160131249528542&w=2
6) https://marc.info/?l=getmail&m=160060476624283&w=2 shows the plight
of a user who tried to continue using getmail with Debin testing.

I have also discussed about this issue with few other DDs and we think:

1) Since the development of getmail is not in the open it's possible
that users have sent personal mail to Charles asking for support and
that is really not fair if Charles receives a support request about
another project.
2) Removing getmail6 is not an option as:
  a) getmail and getmail6 are considered as separate upstream projects.
  b) Debian users who are using getmail6 will be left without anything.
  c) I personally know a few users of getmail/getmail6 whose
employer's corporate policy forbids them to install anything which is
not in Debian. If getmail6 is removed then these types of users will
not have anything.
3) Renaming getmail6 package is not going to help anything if the
transitional package continues to link getmail with getmail6 (or
whatever the renamed package is).

We think the best way is to remove the transitional package which will
break the link between getmail and getmail6 so that Debian users who
are using getmail will not automatically be upgraded to getmail6 and
they will explicitly need to install getmail6 if they want to. That
should solve the problem for which Charles has opened this bug report
as the users will already know that they do not have getmail and they
are installing something else.

I will use this bug to remove the transitional package and will also
ask the release team if this can be included in the next Point
Release.


-- 
Regards
Sudip

Bug#998806: deprecated which

[積丹尼 Dan Jacobson]

Package: apt-listchanges
Version: 3.24

Setting up apt-listchanges (3.24) ...
/usr/bin/which: this version of `which' is deprecated; use `command -v' in 
scripts instead.

Bug#998333: RFS: lebiniou/3.63.1-1 -- user-friendly, powerful music visualization / VJing tool

[Bastian Germann]

Control: tags -1 moreinfo

Please check bug #998617 again.

The MIT-like license is that is still missing:

 * Permission to use, copy, modify, and distribute this software and its
 * documentation for any purpose and without fee is hereby granted,
 * provided that the above copyright notice appear in all copies and that
 * both that copyright notice and this permission notice appear in
 * supporting documentation.
 *
 * This file is provided AS IS with no warranties of any kind.  The author
 * shall have no liability with respect to the infringement of copyrights,
 * trade secrets or any patents by this file or any part thereof.  In no
 * event will the author be liable for any lost revenue or profits or
 * other special, indirect and consequential damages.

Which is NOT Expat.

Expat (that you still call "MIT" but should be renamed) must still be included for the 
net.biniou.LeBiniou.appdata.xml.

Bug#996951:

[Daniel Black]

Marko tested this is fixed in linux-image-5.14.0-4-amd64 (5.14.16-1).

Thanks for the update.

https://jira.mariadb.org/browse/MDEV-26674?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&focusedCommentId=204907#comment-204907

Bug#998805: empty /etc/polkit-1/rules.d remains after purge

[積丹尼 Dan Jacobson]

Package: policykit-1
Version: 0.105-31

Purging configuration files for policykit-1 (0.105-31) ...
dpkg: warning: while removing policykit-1, directory '/etc/polkit-1' not empty 
so not removed

Bug#998804: busybox: please enable bas64

[Christoph Anton Mitterer]

Package: busybox
Version: 1:1.30.1-7+b1
Severity: wishlist


Hi.

Could you please enable CONFIG_BASE64?

base64 is normally guaranteed to be avialble because it's part of coreutils.
But it is not in e.g. the initramfs.

While Debian’s busybox has in principle uuencode/uudecode as alternatives
enabled, these have a number of disadvantages, mostly their unsafe in interace
(see e.g. #995833).

busybox' base64 seems to reuse the functions from it's uuencode/uudecode, so I
guess the impact on additionally required space will be very little.


Thanks,
Chris

Bug#998803: busybox: Debian’s busybox’ tr violates POSIX

[Christoph Anton Mitterer]

Package: busybox
Version: 1:1.30.1-7+b1
Severity: important


Hey.

Unlike mandated by POSIX:
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/tr.html

busybox' tr in Debian doesn't seem to understand any of the character 
classes,...
and I'd guess neither the other formats given in the EXTENDED DESCRIPTION of 
POSIX.

Not only does it not understand this, but it even takes such characters literal 
so e.g. when using
busybox tr -d '[:alpha:]' it will remove 'a' and so on.


It seems that this comes from:
# CONFIG_FEATURE_TR_CLASSES is not set

in the various configs.


And I guess:
# CONFIG_FEATURE_TR_EQUIV is not set

should be set as well.


Actually, this bug has probably severity grave, since it may easily break any
unrelated package which expects tr to work as it should.


Cheers,
Chris.

Bug#998802: which deprecated

[積丹尼 Dan Jacobson]

Package: libdebuginfod-common
Version: 0.185-2

Purging configuration files for libdebuginfod-common (0.185-2) ...
/usr/bin/which: this version of `which' is deprecated; use `command -v' in 
scripts instead.

Bug#993553: myst-parser: update?

[Sylvestre Ledru]

Hello Emannuel,

Do you have an update on myst packaging?

it is now a dependency of black!

Thanks
Sylvestre

Bug#998768: anymeal: bashism in configure script

[Jan Wedekind]

Hi Andrej,
Thanks for reporting the problem with the configure script.
I am uploading the bugfix and will get my package sponsor to review it.

Cheers,
Jan

On Sun, 7 Nov 2021, Andrej Shadura wrote:


Source: anymeal
Version: 1.15-1
Severity: normal
Tags: ftbfs
User: d...@packages.debian.org
Usertags: lineno-bashism

Hi,

Your package uses configure script with bash features not present in
POSIX without explicitly declaring the need to bash shell; this
currently works as configure scripts select bash, but when dash enables
LINENO support, your configure script will start failing:

./configure: 17099: test: xno: unexpected operator
./configure: 17108: test: x: unexpected operator
configure: error: Could not find /src/gtest-all.cc
tail -v -n \+0 config.log

To test this, you can install dash from experimental and re-run the
configure script.

Please replace non-POSIX features with their equivalents to make sure
the script runs with dash. Most common ones are usage of == instead of =
and for with arrays (not lists).

--
Cheers,
 Andrej


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

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

Bug#998801: peruse: Missing dependency on kcm - unable to start

[Carl Suster]

Package: peruse
Version: 1.80+dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When launching peruse from a terminal, it fails to launch, printing this
message:

Failed to load the component from disk. Reported error was: 
"qrc:/qml/Main.qml:26 Type PeruseMain unavailable\nqrc:/qml/PeruseMain.qml:357 
Type Settings unavailable\nqrc:/qml/Settings.qml:29 module \"org.kde.kcm\" is 
not installed\n"

If I manually install qml-module-org-kde-kcm it works, so I assume this is
a missing dependency.


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

Kernel: Linux 5.14.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_DIE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.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 peruse depends on:
ii  kio5.86.0-1
ii  libc6  2.32-4
ii  libgcc-s1  11.2.0-10
ii  libkf5archive5 5.86.0-1
ii  libkf5baloo5   5.86.0-1
ii  libkf5configcore5  5.86.0-1
ii  libkf5coreaddons5  5.86.0-1
ii  libkf5crash5   5.86.0-1
ii  libkf5declarative5 5.86.0-1
ii  libkf5filemetadata35.86.0-1
ii  libkf5guiaddons5   5.86.0-1
ii  libkf5i18n55.86.0-1
ii  libkf5kiocore5 5.86.0-1
ii  libkf5kiowidgets5  5.86.0-1
ii  libkf5newstuffcore55.86.0-3
ii  libqt5core5a   5.15.2+dfsg-12
ii  libqt5gui5 5.15.2+dfsg-12
ii  libqt5qml5 [qtdeclarative-abi-5-15-2]  5.15.2+dfsg-8
ii  libqt5quick5   5.15.2+dfsg-8
ii  libqt5sql5 5.15.2+dfsg-12
ii  libqt5widgets5 5.15.2+dfsg-12
ii  libstdc++6 11.2.0-10
ii  peruse-common  1.80+dfsg-1
ii  qml-module-org-kde-kirigami2   5.86.0-1
ii  qml-module-org-kde-newstuff5.86.0-3
ii  qml-module-qt-labs-folderlistmodel 5.15.2+dfsg-8
ii  qml-module-qt-labs-settings5.15.2+dfsg-8
ii  qml-module-qtquick-controls5.15.2-2
ii  qml-module-qtquick-dialogs 5.15.2-2
ii  qml-module-qtquick-layouts 5.15.2+dfsg-8

peruse recommends no packages.

peruse suggests no packages.

-- no debconf information

Bug#938794: vmm: Python2 removal in sid/bullseye

[Pascal Volk]

On 25/05/2020 20.05, Pascal Volk wrote:
> 
> Hi Martin and Moritz,
> 
> vmm is in a `beauty sleep' - not yet dead.
> There's the v0.7.x¹ branch which requires Python (≥ 3.2).
> 
> I hope I'll find some time for vmm soon

Hi Martin and Moritz,

I finally had the time to release vmm-0.7.0. :-)
The code is available at:
https://bitbucket.org/pvo/vmm/commits/tag/vmm-0.7.0


Regards,
Pascal
-- 
Ubuntu is an ancient African word meaning “I can’t install Debian.”
 -- unknown

Bug#998718: Brasero fails (on Testing) burning an ISO image on a CD-RW

[Thomas Schmitt]

Hi,

(No need to Cc: me, i am subscribed to the bug report 998718.
If you are subscribed too and don't want to be Cc:ed, then tell me.)

> thanx for your quick reply

That's because new udevadm said "XORRISO". I found the bug report by my
evening patrol with Google.

---
Diagnosis:

The unusable drive state looks like a bad relationship between drive
and kernel. Regrettably the dmesg log does not tell how Brasero brought
this relationship in its bad shape.


What to do next:

Did you already try what happens if you eject the CD and insert it again
after spoiling the drive state with Brasero and before using the drive
for mounting or for xorriso -toc ?
If not yet, then please do.

> xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project.

I guess this means you are running Debian "testing".
("stable" has version 1.5.2.)

To outrule the possibility that libburn underneath Brasero is to blame,
please use xorriso to burn an image by this drive:

  isoimage=...path.to.your.ISO.image.file...

  xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed $isoimage

Then try whether the drive is still usable.
(Crossing fingers now.)

-
Just in case somebody is interested in details of my diagnosis:

Mauro Sacchetto wrote:
> dmesg tell me:
> [23315.697087] sr 5:0:0:0: [sr0] tag#16 FAILED Result:
> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
> [23315.697092] sr 5:0:0:0: [sr0] tag#16 CDB: Prevent/Allow Medium Removal 1e
> 00 00 00 01 00

The drive did not respond to a SCSI command from the kernel's SCSI
driver. Brasero obviously tried to lock the drive tray so that pressing
the eject button would have no effect. (At least with motorized trays.)

> [23315.697128] brasero[9154]: segfault at 2f400 ip 7fb6350a5231 sp
> 7fff0e805918 error 4 in libc-2.32.so[7fb634f6c000+149000]

This might be due to a bug in Brasero, which would not react properly
on the failure of the tray locking attempt.


> xorriso tells me only
> TEST UNIT READY
> 00 00 00 00 00 00
>   19 us [ 1091 ]

The drive obviously responded to this SCSI command (indicating that it
is ready for work).


> INQUIRY
> 12 00 00 00 24 00
> From drive: 36b
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>    10 us [ 1207 ]
> --- SG_IO: host_status= 0x4 SG_ERR_DID_BAD_TARGET (Bad target, device not
> responding ?)
> --- SG_IO: Gave up connection to drive

Here the drive did not respond to the kernel, which thus reported the
DID_BAD_TARGET to libburn. The Linux SG_IO adapter of libburn then gave
up the connection.

> libburn : FATAL : Lost connection to drive
> xorriso : FAILURE : Cannot acquire drive '/dev/sr0'
> xorriso : aborting : -abort_on 'FAILURE' encountered 'FATAL'

But xorriso at least found a way out without producing a segmentation
fault in libc or elsewhere.


> Better than my previous report:
> xorriso -scsi_log on -outdev /dev/sr0 -toc
> [... longer list of SCSI transactions ...]
> Media current: CD-RW
> [...]
> Media product: 97m26s65f/79m59s74f , CMC Magnetics Corporation
> Media status : is written , is closed
> [...]
> TOC layout   : Idx ,  sbsector ,   Size , Volume Id
> ISO session  :   1 , 0 ,    193536s , Debian 11.1.0 amd64 n
> Media summary: 1 session, 193536 data blocks,  378m data, 0 free

All seems well. The drive responds to commands in reasonable time,
the medium is recognized as CD-RW, and the filesystem is recognized
as ISO 9660.


Have a nice day :)

Thomas

Bug#998800: fractgen: New upstream versions available

[Bastian Germann]

Source: fractgen

Hi,

Please note that upstream released several new versions, which are only 
available as *.tar.xz.
The d/watch file scans for *.tar.gz which should be fixed.

Please import the latest version into the archive.
There was a package hijack upload to mentors today by the upstream maintainer:
https://mentors.debian.net/package/fractgen. Maybe you find useful package 
changes there.

Thanks,
Bastian

Bug#997171: Patch

[Dima Kogan]

Here's a patch. After applying this I see the build complete
successfully on sid. The patch is simple. Each failure was complaining
about something like this:

  string xxx;
  printf(xxx.c_str());

The attached patch changes each failing instance to

  string xxx;
  printf("%s", xxx.c_str());


diff --git a/userspace/libsinsp/cursescomponents.cpp b/userspace/libsinsp/cursescomponents.cpp
index 4003cb4e..9a9138d4 100644
--- a/userspace/libsinsp/cursescomponents.cpp
+++ b/userspace/libsinsp/cursescomponents.cpp
@@ -877,6 +877,7 @@ void curses_textbox::print_no_data()
 	string wstr = "No Data For This Selection";
 	mvprintw(m_parent->m_screenh / 2,
 		m_parent->m_screenw / 2 - wstr.size() / 2,
+"%s",
 		wstr.c_str());
 
 	refresh();
@@ -1100,6 +1101,7 @@ void curses_textbox::render()
 		attrset(m_parent->m_colors[sinsp_cursesui::LARGE_NUMBER]);
 		mvprintw(0,
 			m_parent->m_screenw / 2 - wstr.size() / 2,
+"%s",
 			wstr.c_str());
 	}
 
diff --git a/userspace/libsinsp/cursesspectro.cpp b/userspace/libsinsp/cursesspectro.cpp
index 6858bc95..fddc09cf 100644
--- a/userspace/libsinsp/cursesspectro.cpp
+++ b/userspace/libsinsp/cursesspectro.cpp
@@ -227,6 +227,7 @@ void curses_spectro::print_error(string wstr)
 	mvwprintw(m_tblwin, 
 		m_parent->m_screenh / 2,
 		m_parent->m_screenw / 2 - wstr.size() / 2, 
+"%s",
 		wstr.c_str());	
 }
 
diff --git a/userspace/libsinsp/cursestable.cpp b/userspace/libsinsp/cursestable.cpp
index 69c2aa32..6fef5a4c 100644
--- a/userspace/libsinsp/cursestable.cpp
+++ b/userspace/libsinsp/cursestable.cpp
@@ -254,6 +254,7 @@ void curses_table::print_line_centered(string line, int32_t off)
 		mvwprintw(m_tblwin, 
 			m_parent->m_screenh / 2 + off,
 			m_parent->m_screenw / 2 - line.size() / 2, 
+"%s",
 			line.c_str());
 	}
 	else
@@ -268,6 +269,7 @@ glogf("2, %d %s\n", spos, ss.c_str());
 			mvwprintw(m_tblwin, 
 m_parent->m_screenh / 2 + off + j,
 0,
+"%s",
 ss.c_str());
 
 			spos += m_parent->m_screenw;
@@ -328,6 +330,7 @@ void curses_table::print_error(string wstr)
 	mvwprintw(m_tblwin, 
 		m_parent->m_screenh / 2,
 		m_parent->m_screenw / 2 - wstr.size() / 2, 
+"%s",
 		wstr.c_str());	
 }
 
diff --git a/userspace/libsinsp/cursesui.cpp b/userspace/libsinsp/cursesui.cpp
index 1eeb0864..2427e54d 100644
--- a/userspace/libsinsp/cursesui.cpp
+++ b/userspace/libsinsp/cursesui.cpp
@@ -825,6 +825,7 @@ void sinsp_cursesui::render_header()
 		attrset(m_colors[sinsp_cursesui::LARGE_NUMBER]);
 		mvprintw(0,
 			m_screenw / 2 - wstr.size() / 2, 
+"%s",
 			wstr.c_str());	
 	}
 
@@ -1123,7 +1124,7 @@ void sinsp_cursesui::render_filtersearch_main_menu()
 
 		m_cursor_pos = cursor_pos;
 
-		mvprintw(m_screenh - 1, m_cursor_pos, str->c_str());
+		mvprintw(m_screenh - 1, m_cursor_pos, "%s", str->c_str());
 
 		m_cursor_pos += str->size();
 	}
@@ -2189,6 +2190,7 @@ void sinsp_cursesui::print_progress(double progress)
 	string wstr = "Processing File";
 	mvprintw(m_screenh / 2,
 		m_screenw / 2 - wstr.size() / 2, 
+"%s",
 		wstr.c_str());	
 
 	//
@@ -2199,6 +2201,7 @@ void sinsp_cursesui::print_progress(double progress)
 	wstr = "Progress: " + string(numbuf);
 	mvprintw(m_screenh / 2 + 1,
 		m_screenw / 2 - wstr.size() / 2, 
+"%s",
 		wstr.c_str());
 
 	refresh();
@@ -2308,6 +2311,7 @@ sysdig_table_action sinsp_cursesui::handle_textbox_input(int ch)
 		attrset(m_colors[sinsp_cursesui::FAILED_SEARCH]);
 		mvprintw(m_screenh / 2,
 			m_screenw / 2 - wstr.size() / 2, 
+"%s",
 			wstr.c_str());	
 
 		//
@@ -2363,6 +2367,7 @@ sysdig_table_action sinsp_cursesui::handle_textbox_input(int ch)
 
 	mvprintw(m_screenh / 2,
 		m_screenw / 2 - wstr.size() / 2, 
+"%s",
 		wstr.c_str());
 
 	render();
@@ -2436,6 +2441,7 @@ sysdig_table_action sinsp_cursesui::handle_textbox_input(int ch)
 
 mvprintw(m_screenh / 2,
 	m_screenw / 2 - wstr.size() / 2, 
+"%s",
 	wstr.c_str());
 
 render();

Bug#997894: pyqt5-sip: appears to declare the wrong API version (should be 12.9)

[Dmitry Shachnev]

Control: tags -1 + moreinfo

Hi Alex, and sorry for the late response!

On Tue, Oct 26, 2021 at 08:10:37AM -0700, Alex Relis wrote:
> I'm on version 5.30.0+dfsg-1 and I am still experiencing this bug.
> It hasn't been fixed quite yet. Here's the error I seem to be getting:
>
> alex@alex-pc:~$ calibre
> Traceback (most recent call last):
>   File "/usr/bin/calibre", line 21, in 
> sys.exit(calibre())
>   File "/usr/lib/calibre/calibre/gui_launch.py", line 64, in calibre
> main(args)
>   File "/usr/lib/calibre/calibre/gui2/main.py", line 533, in main
> app, opts, args = init_qt(args)
>   File "/usr/lib/calibre/calibre/gui2/main.py", line 124, in init_qt
> app = Application(args, override_program_name=override, 
> windows_app_uid=MAIN_APP_UID)
>   File "/usr/lib/calibre/calibre/gui2/__init__.py", line 894, in __init__
> from calibre_extensions import progress_indicator
> RuntimeError: the sip module implements API v12.0 to v12.8 but the 
> progress_indicator module requires API v12.9

I cannot reproduce this on a fresh sid system. Calibre imports and runs
successfully.

Can you please make sure that you don't have a custom PyQt5.sip installation
somewhere? Can you run this command and see what it prints?

  python3 -c 'import PyQt5.sip; print(PyQt5.sip.__file__)'

Nicholas, are you experiencing this bug too?

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#998797: mrtg: [INTL:fr] French templates translation

[Eriberto Mota]

Thank you Jean-Pierre!

Bug#998799: linux-image-5.14.0-4-amd64: Regression causing graphics slowness (`amdgpu: failed to write reg`)

[Paul Menzel]

Package: linux-image-5.14.0-4-amd64
Version: 5.14.16-1
Severity: important
Forwarded: https://gitlab.freedesktop.org/drm/amd/-/issues/1770
Tag: fixed-upstream


Dear Linux folks,


The upgrade from 5.14.12 to 5.14.16 makes systems with AMD graphics 
devices unusable caused by a regression in 5.14.15 [1].


amdgpu :26:00.0: amdgpu: failed to write reg 28b4 wait reg 28c6
amdgpu :26:00.0: amdgpu: failed to write reg 1a6f4 wait reg 1a706

The fix was supposedly applied to Linux 5.14.17, so it’d be great if you 
uploaded new packages.



Kind regards,

Paul


[1]: https://gitlab.freedesktop.org/drm/amd/-/issues/1770

Bug#998798: ITP: golang-github-juju-usso -- Ubuntu single sign-on library

[Mathias Gibbens]

Package: wnpp
Severity: wishlist
Owner: Mathias Gibbens 
X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org

* Package name: golang-github-juju-usso
  Version : 1.0.1-1
  Upstream Author : Canonical Inc
* URL : https://github.com/juju/usso
* License : LGPL-3.0-with-exception
  Programming Lang: Go
  Description : Ubuntu single sign-on library

 Provides an interface to Ubuntu's single sign-on service. 

This package is a dependency of golang-github-canonical-candid (ITP
#998752), which is needed for packaging LXD (ITP #768073). From a quick
inspection of the Candid source, it looks like a non-trivial amount of
work to patch out Candid's use of this library, so I'm going to package
it, even though it's Ubuntu specific.

This package will be team-maintained within the Debian Go Packaging
Team.


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

Bug#998766: aide: bashism in configure script

[Marc Haber]

tags 998766 upstream
forwarded 998766 https://github.com/aide/aide/issues/113
thanks

I have forwarded this upstream, and upstream has already addressed the
issue.

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#998797: mrtg: [INTL:fr] French templates translation

[Jean-Pierre Giraud]

Package: mrtg
Severity: wishlist
Tags: patch l10n

Hi!

Please find attached the french templates translation, proofread
by the debian-l10n-french mailing list contributors.

This file should be put as debian/po/fr.po in your package build tree.

Kind Regards

Jean-Pierre Giraud


fr.po.xz
Description: application/xz


OpenPGP_signature
Description: OpenPGP digital signature

Bug#998718: (no subject)

[Mauro Sacchetto]

Better than my previous report:

Putting the CD-RW into drivee:

v
root@darkstar:~# xorriso -scsi_log on -outdev /dev/sr0 -toc 2>&1 | tee 
-i /tmp/xorriso.log

xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project.


TEST UNIT READY
00 00 00 00 00 00
 2915 us [ 6174 ]

INQUIRY
12 00 00 00 24 00
From drive: 36b
05 80 05 32 5b 00 00 00 41 53 55 53 20 20 20 20 44 52 57 2d
32 34 44 35 4d 54 20 20 20 20 20 20 32 2e 30 30
 2729 us [ 9018 ]

GET CONFIGURATION
46 00 00 00 00 00 00 00 08 00
From drive: 8b
00 00 01 7c 00 00 00 0a
 3910 us [ 12968 ]

GET CONFIGURATION
46 00 00 00 00 00 00 01 80 00
From drive: 384b
00 00 01 7c 00 00 00 0a 00 00 03 38 00 15 00 00 00 16 00 00
00 2b 00 00 00 1b 00 00 00 1a 00 00 00 14 00 00 00 13 00 00
00 12 00 00 00 11 00 00 00 10 00 00 00 0a 01 00 00 09 00 00
00 08 01 00 00 02 00 00 00 01 0b 08 00 00 00 07 01 00 00 00
00 02 07 04 02 00 00 00 00 03 0b 04 3b 00 00 00 00 04 08 04
02 00 00 00 00 10 01 08 00 00 08 00 00 01 01 00 00 1d 01 00
00 1e 09 04 03 00 00 00 00 1f 08 04 01 00 01 00 00 20 04 0c
00 00 00 00 00 00 08 00 00 00 01 00 00 21 0c 08 3d 0f 03 01
07 00 00 00 00 23 09 08 00 00 00 00 00 00 00 00 00 24 04 04
80 00 00 00 00 26 00 00 00 2a 04 04 01 00 00 00 00 2b 00 04
01 00 00 00 00 2c 00 04 03 00 00 00 00 2d 08 04 5f 00 00 00
00 2e 04 04 7f 00 0d 00 00 2f 08 04 4e 00 00 00 00 33 00 08
00 00 00 01 10 00 00 00 00 37 01 04 00 07 00 00 00 3b 00 04
01 00 00 00 01 00 07 04 00 00 00 00 01 01 00 04 00 00 00 00
01 03 00 04 03 00 01 00 01 04 04 04 00 00 00 00 01 05 07 04
00 00 00 00 01 06 00 04 00 00 00 01 01 07 15 04 1f 00 00 00
01 08 03 10 4b 4c 4a 4c 31 36 38 35 37 34 34 20 20 20 20 20
01 0a 00 0c 46 44 43 00 53 44 43 00 54 4f 43 00 01 0b 00 04
00 00 00 01 01 0c 03 10 32 30 31 39 30 36 31 37 31 30 34 39
20 20 00 00
 3776 us [ 17057 ]

MODE SENSE
5a 00 2a 00 00 00 00 00 1e 00
From drive: 30b
00 4a 21 00 00 00 00 00 2a 42 3f 37 f1 77 2b 23 1b 90 01 00
02 00 10 8a 00 10 02 c2 02 c2
 5111 us [ 3 ]

MODE SENSE
5a 00 2a 00 00 00 00 00 4c 00
From drive: 76b
00 4a 21 00 00 00 00 00 2a 42 3f 37 f1 77 2b 23 1b 90 01 00
02 00 10 8a 00 10 02 c2 02 c2 00 01 00 00 00 00 02 c2 00 01
00 00 02 c2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 2926 us [ 25256 ]

GET PERFORMANCE
ac 00 00 00 00 00 00 00 00 00 03 00
From drive: 8b
00 00 00 14 00 00 00 00
 2187 us [ 27482 ]

GET PERFORMANCE
ac 00 00 00 00 00 00 00 00 01 03 00
From drive: 24b
00 00 00 14 00 00 00 00 00 00 00 00 00 05 7d a9 00 00 10 89
00 00 02 c1
 1616 us [ 29158 ]

GET PERFORMANCE
ac 00 00 00 00 00 00 00 00 01 03 00
From drive: 24b
00 00 00 14 00 00 00 00 00 00 00 00 00 05 7d a9 00 00 10 89
00 00 02 c1
 1516 us [ 30725 ]

GET PERFORMANCE
ac 10 00 00 00 00 00 00 00 00 00 00
From drive: 8b
00 00 00 14 00 00 00 00
 1012 us [ 31764 ]

GET PERFORMANCE
ac 10 00 00 00 00 00 00 00 01 00 00
From drive: 24b
00 00 00 14 00 00 00 00 00 00 00 00 00 00 0b 7c 00 02 f3 ff
00 00 1b 90
 1053 us [ 32855 ]

GET PERFORMANCE
ac 10 00 00 00 00 00 00 00 01 00 00
From drive: 24b
00 00 00 14 00 00 00 00 00 00 00 00 00 00 0b 7c 00 02 f3 ff
00 00 1b 90
  965 us [ 33860 ]

MODE SENSE
5a 00 01 00 00 00 00 00 0c 00
From drive: 12b
00 12 21 00 00 00 00 00 01 0a 80 c0
  582 us [ 34472 ]

PREVENT/ALLOW MEDIA REMOVAL
1e 00 00 00 00 00
  510 us [ 34991 ]

START/STOP UNIT
1b 00 00 00 03 00
  374 us [ 35390 ]

TEST UNIT READY
00 00 00 00 00 00
 1387 us [ 536936 ]

PREVENT/ALLOW MEDIA REMOVAL
1e 00 00 00 01 00
 2893 us [ 539878 ]

START/STOP UNIT
1b 01 00 00 01 00
 3156 us [ 543076 ]

TEST UNIT READY
00 00 00 00 00 00
 5605 us [ 1048864 ]

START/STOP UNIT
1b 00 00 00 01 00
  1562894 us [ 2611828 ]

INQUIRY
12 00 00 00 24 00
From drive: 36b
05 80 05 32 5b 00 00 00 41 53 55 53 20 20 20 20 44 52 57 2d
32 34 44 35 4d 54 20 20 20 20 20 20 32 2e 30 30
  524 us [ 2612573 ]

MODE SENSE
5a 00 2a 00 00 00 00 00 1e 00
From drive: 30b
00 4a 21 00 00 00 00 00 2a 42 3f 37 f1 77 2b 23 1b 90 01 00
02 00 10 8a 00 10 02 c2 02 c2
 3773 us [ 2616506 ]

MODE SENSE
5a 00 2a 00 00 00 00 00 4c 00
From drive: 76b
00 4a 21 00 00 00 00 00 2a 42 3f 37 f1 77 2b 23 1b 90 01 00
02 00 10 8a 00 10 02 c2 02 c2 00 01 00 00 00 00 02 c2 00 01
00 00 02 c2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 5770 us [ 2622414 ]

GET PERFORMANCE
ac 00 00 00 00 00 00 00 00 00 03 00
From drive: 8b
00 00 00 14 00 00 00 00
 1529 us [ 2623993 ]

GET PERFORMANCE
ac 00 00 00 00 00 00 00 00 01 03 00
From drive: 24b
00 00 00 14 00 00 00 00 00 00 00 00 00 05 7d a9 00 00 10 89
00 00 02 c1
 1491 us [ 2625571 ]

GET PERFORMANCE
ac 00 00 00 00 00 00 00 00 01 03 00
From drive: 24b
00 00 00 14 00 00 00 00 00 00 00 00 00 05 7d a9 00 00 10 89
00 00 02 c1
 1500 us [ 2627186 ]

GET PERFORMANCE
ac 10 00 00 00 00 00 00 00 00 00 00

Bug#998796: ITP: pybeam -- Python module to parse Erlang BEAM files

[Boyuan Yang]

Package: wnpp
Severity: wishlist
Owner: Boyuan Yang 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: pybeam
  Version : 0.7
  Upstream Author : Matwey V. Kornilov 
* URL : https://github.com/matwey/pybeam/
* License : MIT
  Programming Lang: Python
  Description : Python module to parse Erlang BEAM files

 This library provides functionality to parse Erlang BEAM files.
 .
 It is a build-dependency for new releases of rpmlint
 ( https://github.com/rpm-software-management/rpmlint ).

I will maintain this package under Debian Python team umbrella
( https://salsa.debian.org/python-team/packages/pybeam ).

Thanks,
Boyuan Yang


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

Bug#998766: aide: bashism in configure script

[Marc Haber]

tags -1 upstream
forwarded -1 https://github.com/aide/aide/issues/113
thanks

I have forwarded this upstream

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#998718: Brasero fails (on Testing) burning an ISO image on a CD-RW

[Mauro Sacchetto]

thanx for your quick reply

dmesg tell me:

=

[23315.697087] sr 5:0:0:0: [sr0] tag#16 FAILED Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[23315.697092] sr 5:0:0:0: [sr0] tag#16 CDB: Prevent/Allow Medium 
Removal 1e 00 00 00 01 00
[23315.697128] brasero[9154]: segfault at 2f400 ip 7fb6350a5231 sp 
7fff0e805918 error 4 in libc-2.32.so[7fb634f6c000+149000]
[23315.697136] Code: 84 00 00 00 00 00 0f 1f 00 31 c0 c5 f8 77 c3 66 2e 
0f 1f 84 00 00 00 00 00 89 f9 48 89 fa c5 f9 ef c0 83 e1 3f 83 f9 20 77 
1f  fd 74 0f c5 fd d7 c1 85 c0 0f 85 df 00 00 00 48 83 c7 20 83 e1


=

xorriso tells me only

=

root@darkstar:~# xorriso -scsi_log on -outdev /dev/sr0 -toc 2>&1 | tee 
-i /tmp/xorriso.log

xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project.


TEST UNIT READY
00 00 00 00 00 00
   19 us [ 1091 ]

INQUIRY
12 00 00 00 24 00
From drive: 36b
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   10 us [ 1207 ]
--- SG_IO: host_status= 0x4 SG_ERR_DID_BAD_TARGET (Bad target, device 
not responding ?)

--- SG_IO: Gave up connection to drive
libburn : FAILURE : SCSI command 12h yielded host problem: 0x4 
SG_ERR_DID_BAD_TARGET (Bad target, device not responding ?)

libburn : FAILURE : Command: INQUIRY : 12 00 00 00 24 00  : dxfer_len= 36
libburn : FATAL : Lost connection to drive
xorriso : FAILURE : Cannot acquire drive '/dev/sr0'
xorriso : aborting : -abort_on 'FAILURE' encountered 'FATAL'

=



Il 07/11/21 19:37, Thomas Schmitt ha scritto:

Hi,

i am upstream programmer of libburn, which might be in charge of
burning underneath Brasero. Regrettably i cannot interpret Brasero's
messages unless they come from libburn or libisofs. So i am not sure
whether i can help with fixing Brasero.

The statement by other software that no medium is found in /dev/sr0
surprises me. Such a status assessment is usually done by the drive
and i am not aware of any regular means to let a drive ignore or deny
its loaded medium.

Do you see anything in dmesg that occured when Brasero failed and looks
related to "sr" or "cdrom" ?

Can i talk you into inquring the drive by xorriso and logging its
SCSI transactions when the drive has gone mad from Brasero and a medium
is still inserted ?

   xorriso -scsi_log on -outdev /dev/sr0 -toc 2>&1 | tee -i /tmp/xorriso.log

This would give insight into what the drive tells about its status
without the programs-in-the-middle. The log is quite verbose and will
have several hundred lines. Please post /tmp/xorriso.log as attachment
or send it to me by private mail.

(I wonder why udevadm monitor of Testing is so eager to insert blanks
everywhere. But that would be a different bug, if it is not a copy+paste
artefact.)


Have a nice day :)

Thomas


--
Prof. Mauro Sacchetto
Santa Croce 1332a
30135 Venezia
tel.: 041 722938
cell.: 348 9690575
e-mail:mauro.sacche...@gmail.com
Linux user no.: 353546
public key athttp://keyserver.linux.it

Bug#987996: RFS: hipercontracer [ITP]

[Bastian Germann]

Control: tags -1 - moreinfo

Bug#998795: ITP: mrcal -- Camera calibration toolkit

[Dima Kogan]

Package: wnpp
Owner: Dima Kogan 
Severity: wishlist

* Package name: mrcal
  Version : 2.0
  Upstream Author : Dima Kogan
* URL or Web page : http://mrcal.secretsauce.net
* License : Apache 2.0
  Description : Camera calibration toolkit

Bug#998794: ITP: mrgingham -- chessboard detector for camera calibration

[Dima Kogan]

Package: wnpp
Owner: Dima Kogan 
Severity: wishlist

* Package name: mrgingham
  Version : 1.20
  Upstream Author : Dima Kogan
* URL or Web page : https://github.com/dkogan/mrgingham/
* License : LGPL-2.1+
  Description : chessboard detector for camera calibration

Bug#987996: RFS: hipercontracer [ITP]

[Thomas Dreibholz]

Hi,

version ~test4 should solve the issues:

  * Using dh_installman for the manpages.
  * Removed unused tests/control as well as changelog.dist.

Den 06.11.2021 19:58, skrev Bastian Germann:
> On 06.11.21 19:51, Thomas Dreibholz wrote:
>> Hi,
>>
>> the remaining issues should be fixed in version test2:
>>
>>   * The only remaining changelog item is the ITP closing #997090
>>   * Dependencies without BOOST version
>>   * dh_installexamples is now installing the example files
>>
>> Already in version test1 were fixed:
>>
>>   * Removal of compat file
>>   * Rewrite of the postinst/postrm scripts
>>   * Removed cmake3 dependency alternative
>>   * Commented the lintian override
>
>
> This still leaves us with:
>
> - manpages should not be installed via *.install but via *.manpages.
> - drop the empty d/tests/control and d/changelog.dist files.

-- 
Best regards / Mit freundlichen Grüßen / Med vennlig hilsen

===
 Thomas Dreibholz

 SimulaMet -- Simula Metropolitan Centre for Digital Engineering
 Centre for Resilient Networks and Applications
 Pilestredet 52
 0167 Oslo, Norway
---
 E-Mail: dre...@simula.no
 Homepage:   http://simula.no/people/dreibh
===



OpenPGP_signature
Description: OpenPGP digital signature

Bug#998793: src:netgen: fails to migrate to testing for too long: autopkgtest failure

[Paul Gevers]

Source: netgen
Version: 6.2.2006+really6.2.1905+dfsg-2.1
Severity: serious
Control: close -1 6.2.2006+really6.2.1905+dfsg-4
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 995416

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:netgen has been trying to migrate for 61
days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bookworm, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=netgen




OpenPGP_signature
Description: OpenPGP digital signature

Bug#982975: RFS: rsplib/3.3.3~test2-1 [ITP] -- Reliable Server Pooling

[Bastian Germann]

Control: tags -1 - moreinfo

Bug#998792: src:gmsh: fails to migrate to testing for too long: unresolved RC bug

[Paul Gevers]

Source: gmsh
Version: 4.7.1+ds1-5
Severity: serious
Control: close -1 4.8.4+ds1-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 995424

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:gmsh has been trying to migrate for 61
days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bookworm, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=gmsh




OpenPGP_signature
Description: OpenPGP digital signature

Bug#998791: src:fakeroot: fails to migrate to testing for too long: ftbfs on ppc64el

[Paul Gevers]

Source: fakeroot
Version: 1.25.3-1.1
Severity: serious
Control: close -1 1.26-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 995393

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:fakeroot has been trying to migrate for 61
days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bookworm, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=fakeroot




OpenPGP_signature
Description: OpenPGP digital signature

Bug#998790: firefox: Video not playing

[Christophe Troestler]

Subject: firefox: Video not playing
Package: firefox
Version: 94.0-1
Severity: normal

Dear Maintainer,

Playing videos on, say, youtube (e.g. ) 
does not work: the “loading circle” keeps turning but nothing happens (even 
with troubleshoot mode turned on).

-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (900, 'testing'), (400, 'unstable'), (300, 'stable'), (100, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages firefox depends on:
ii  debianutils  4.11.2
ii  fontconfig   2.13.1-4.2
ii  libatk1.0-0  2.36.0-2
ii  libc62.32-4
ii  libcairo-gobject21.16.0-5
ii  libcairo21.16.0-5
ii  libdbus-1-3  1.12.20-3
ii  libdbus-glib-1-2 0.112-2
ii  libevent-2.1-7   2.1.12-stable-1
ii  libffi8  3.4.2-3
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.11.0+dfsg-1
ii  libgcc-s111.2.0-10
ii  libgdk-pixbuf-2.0-0  2.42.6+dfsg-2
ii  libglib2.0-0 2.70.0-3
ii  libgtk-3-0   3.24.30-3
ii  libnspr4 2:4.32-1
ii  libnss3  2:3.72-1
ii  libpango-1.0-0   1.48.10+ds1-1
ii  libstdc++6   11.2.0-10
ii  libvpx7  1.11.0-2
ii  libx11-6 2:1.7.2-2+b1
ii  libx11-xcb1  2:1.7.2-2+b1
ii  libxcb-shm0  1.14-3
ii  libxcb1  1.14-3
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.4-1
ii  libxfixes3   1:5.0.3-2
ii  libxrandr2   2:1.5.2-1
ii  procps   2:3.3.17-5
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages firefox recommends:
ii  libavcodec57  7:3.4.3-1
ii  libavcodec58  7:4.4.1-1+b1

Versions of packages firefox suggests:
ii  fonts-lmodern  2.004.5-6.1
ii  fonts-stix [otf-stix]  1.1.1-4.1
ii  libcanberra0   0.30-8
ii  libgssapi-krb5-2   1.18.3-7
ii  pulseaudio 15.0+dfsg1-2

-- no debconf information

Bug#998767: mkdocs: readthedocs theme is not self contained

[Dmitry Shachnev]

Hi Salvo!

On Sun, Nov 07, 2021 at 08:26:58PM +0100, Salvo 'LtWorf' Tomaselli wrote:
> Package: mkdocs
> Version: 1.1.2+dfsg-2
> Severity: normal
> Tags: upstream
> X-Debbugs-Cc: tipos...@tiscali.it
>
> Hello,
>
> I use mkdocs for typedload (python3-typedload) and to generate the website
> from markdown text files.
>
> However I realised that my adblock in the browser complains, because the
> "readthedocs" theme included with mkdocs uses css and js files from
> cloudflare and is not self contained.
>
> The js file in question is highlight.js, which seems to be present in
> copious copies in the debian archive, mostly in documentation packages.
>
> For me the ideal would be to align mkdocs with the other packages and vendor
> the file rather than link it to an external domain I have no control over.
>
> The even better solution would probably be to have a package with it, which
> can be symlinked by all the packages which use the file.

Please try using dh_mkdocs helper. Its main goal is exactly what you say:
replacing use of highlight.js from CDN with a packaged version.

https://manpages.debian.org/unstable/mkdocs/dh_mkdocs.1.en.html

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#982975: RFS: rsplib/3.3.3~test2-1 [ITP] -- Reliable Server Pooling

[Thomas Dreibholz]

Hi,

version ~test3 should fix the issues:

  * Updated debian/copyright with information about src/sha1.c.
src/storage/ was obsolete and now deleted completely.
  * Removed changelog.dist and tests/control.
  * Using dh_installman for the manpages instead of the dh_install.

Den 07.11.2021 00:42, skrev Bastian Germann:
> Control: tags -1 moreinfo
>
> debian/copyright: copyright info missing. See src/sha1.c and
> src/storage/sha512.c.
>
> Remove changelog.dist and empty *.manpages, and empty d/tests/control.

-- 
Best regards / Mit freundlichen Grüßen / Med vennlig hilsen

===
 Thomas Dreibholz

 SimulaMet -- Simula Metropolitan Centre for Digital Engineering
 Centre for Resilient Networks and Applications
 Pilestredet 52
 0167 Oslo, Norway
---
 E-Mail: dre...@simula.no
 Homepage:   http://simula.no/people/dreibh
===



OpenPGP_signature
Description: OpenPGP digital signature

Bug#998787: crac: bashism in configure script

[Andrej Shadura]

Source: crac
Version: 2.5.2+dfsg-4
Severity: normal
Tags: ftbfs
User: d...@packages.debian.org
Usertags: lineno-bashism

Hi,

Your package uses configure script with bash features not present in
POSIX without explicitly declaring the need to bash shell; this
currently works as configure scripts select bash, but when dash enables
LINENO support, your configure script will start failing:

 ./configure: 3479: test: x-g -O2 
-ffile-prefix-map=/usr/src/packages/BUILD=. -fstack-protector-strong -Wformat 
-Werror=format-security: unexpected operator
 ./configure: 3483: test: x-Wdate-time -D_FORTIFY_SOURCE=2: unexpected 
operator
 ./configure: 3487: test: x-g -O2 
-ffile-prefix-map=/usr/src/packages/BUILD=. -fstack-protector-strong -Wformat 
-Werror=format-security: unexpected operator
 ./configure: 3491: test: x-Wl,-z,relro -Wl,-z,now: unexpected operator
 checking for a BSD-compatible install... /usr/bin/install -c
 checking whether build environment is sane... yes
 checking for a race-free mkdir -p... /bin/mkdir -p
 ...
 checking for uint8_t... yes
 checking for ptrdiff_t... yes
 yes
 checking for GNU libc compatible realloc... yes
 checking for floor... yes
 checking for gettimeofday... yes
 checking for memchr... yes
 checking for memmove... yes
 checking for memset... yes
 checking for mkfifo... yes
 checking for pow... yes
 checking for select... yes
 checking for sqrt... yes
 checking for strrchr... yes
 checking for strstr... yes
 checking for strtol... yes
 ./configure: 18564: test: xcheck: unexpected operator
 ./configure: 18574: test: xcheck: unexpected operator
 ./configure: 18606: test: xcheck: unexpected operator
 ./configure: 18616: test: xcheck: unexpected operator
 checking for pkg-config... /usr/bin/pkg-config
 checking pkg-config is at least version 0.9.0... yes
 checking for libProgressBar... yes
 ./configure: 18870: test: xcheck: unexpected operator
 ./configure: 18880: test: xcheck: unexpected operator
 checking for libProgressBarVersion in -lProgressBar... yes
 ./configure: 18949: test: 1: unexpected operator
 ./configure: 18956: test: xcheck: unexpected operator
 checking for gzread in -lz... yes
 checking for hts_hopen in -lhts... yes
 checking for libGkArrays... yes
 checking for libGkArraysVersion in -lGkArrays... yes
 ./configure: 19199: test: 1: unexpected operator
 configure: WARNING: Library GkArrays not found
 checking for libJellyfishVersion in -ljellyfish-2.0... no
 ./configure: 19259: test: 0: unexpected operator
 configure: WARNING: Library jellyfish-2.0 not found
 ./configure: 19270: test: 0: unexpected operator
 ./configure: 19279: test: xcheck: unexpected operator
 ./configure: 19287: test: 1: unexpected operator
 ./configure: 19296: test: xcheck: unexpected operator
 ./configure: 19304: test: 0: unexpected operator
 ./configure: 19313: test: xyes: unexpected operator
 ./configure: 19319: test: xno: unexpected operator
 checking that generated files are newer than configure... done
 configure: creating ./config.status
 config.status: creating control
 config.status: creating crac.spec
 config.status: creating Makefile
 config.status: creating src/Makefile
 config.status: creating scripts/Makefile
 config.status: creating src/libReadsInfo/Makefile
 config.status: creating src/libSSA/Makefile
 config.status: creating src/libReadsReader/Makefile
 config.status: creating src/libReadsReader/kseq/Makefile
 config.status: creating man/Makefile
 config.status: creating man/crac.1
 config.status: creating scripts/crac-client
 config.status: creating test_f/Makefile
 config.status: creating test_f/bug/Makefile
 config.status: creating test_f/causes/Makefile
 config.status: creating test_f/cigar/Makefile
 config.status: creating test_f/splices_adjust/Makefile
 config.status: creating config/config.h
 config.status: executing depfiles commands
 config.status: executing libtool commands

To test this, you can install dash from experimental and re-run the
configure script.

Please replace non-POSIX features with their equivalents to make sure
the script runs with dash. Most common ones are usage of == instead of =
and for with arrays (not lists).

-- 
Cheers,
  Andrej


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

Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (v

Bug#998786: cpm: bashism in configure script

[Andrej Shadura]

Source: cpm
Version: 0.32-1.3
Severity: normal
Tags: ftbfs
User: d...@packages.debian.org
Usertags: lineno-bashism

Hi,

Your package uses configure script with bash features not present in
POSIX without explicitly declaring the need to bash shell; this
currently works as configure scripts select bash, but when dash enables
LINENO support, your configure script will start failing:

 ./configure: 4172: test: yes: unexpected operator
 : error: can not find the selected ncursesw/ncurses library.
tail -v -n \+0 config.log

To test this, you can install dash from experimental and re-run the
configure script.

Please replace non-POSIX features with their equivalents to make sure
the script runs with dash. Most common ones are usage of == instead of =
and for with arrays (not lists).

-- 
Cheers,
  Andrej


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

Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
[0s] Memory limit set to 46776712KB
[0s] Using BUILD_ROOT=/srv/obs/worker/root_6
[0s] Using BUILD_ARCH=x86_64:i686:i586:i486:i386
[0s] 
[1s] 
[1s] potassium started "build cpm_0.32-1.3.dsc" at Fri Nov  5 01:24:24 UTC 
2021.
[1s] build version: 20180831-2co3debian9.1
[1s] 
[1s] Building cpm for project 'home:andrewsh:sid' repository 'main' arch 
'x86_64' srcmd5 'db96c361d1f01a5974cb9cf417318c1a'
[1s] 
[1s] processing recipe 
/srv/obs/worker/root_6/.build-srcdir/cpm_0.32-1.3.dsc ...
[1s] running changelog2spec --target debian --file 
/srv/obs/worker/root_6/.build-srcdir/cpm_0.32-1.3.dsc
[1s] init_buildsystem --configdir 
/srv/obs/worker/run/worker/6/build/configs --cachedir /var/cache/obs-build 
--clean --create-build-binaries --rpmlist /srv/obs/worker/root_6/.build.rpmlist 
/srv/obs/worker/root_6/.build-srcdir/cpm_0.32-1.3.dsc build rpmlint-Factory ...
[1s] init_buildsystem version: 20180831-2co3debian9.1
[5s] cycle: libc6 -> libgcc-s1
[5s]   breaking dependency libgcc-s1 -> libc6
[5s] [1/45] preinstalling libgcc-s1...
[5s] Version: 11.2.0-10
[5s] [2/45] preinstalling libc6...
[5s] Version: 2.32-4
[6s] [3/45] preinstalling debianutils...
[6s] Version: 5.5-1
[6s] [4/45] preinstalling diffutils...
[6s] Version: 1:3.7-5
[6s] [5/45] preinstalling insserv...
[6s] Version: 1.23.0-1
[6s] [6/45] preinstalling libacl1...
[6s] Version: 2.3.1-11.1
[6s] [7/45] preinstalling libattr1...
[6s] Version: 1:2.5.1-11.1
[6s] [8/45] preinstalling libbz2-1.0...
[6s] Version: 1.0.8-4
[6s] [9/45] preinstalling libc-bin...
[6s] Version: 2.32-4
[6s] [10/45] preinstalling libcrypt1...
[7s] Version: 1:4.4.25-2
[7s] [11/45] preinstalling libdbus-1-3...
[7s] Version: 1.12.20-3
[7s] [12/45] preinstalling libdebconfclient0...
[7s] Version: 0.2601.1
[7s] [13/45] preinstalling libgmp10...
[7s] Version: 2:6.2.1+dfsg-2
[7s] [14/45] preinstalling liblzma5...
[7s] Version: 5.2.5-2
[7s] [15/45] preinstalling libpcre2-8-0...
[7s] Version: 10.36-2
[7s] [16/45] preinstalling libpcre3...
[7s] Version: 2:8.39-13
[7s] [17/45] preinstalling libsepol1...
[7s] Version: 3.1-1
[7s] [18/45] preinstalling libsigsegv2...
[7s] Version: 2.13-1
[7s] [19/45] preinstalling libtinfo5...
[7s] Version: 6.2+20210905-1
[7s] [20/45] preinstalling mawk...
[7s] Version: 1.3.4.20200120-2
[7s] [21/45] preinstalling zlib1g...
[7s] Version: 1:1.2.11.dfsg-2
[7s] [22/45] preinstalling libstdc++6...
[7s] Version: 11.2.0-10
[7s] [23/45] preinstalling base-passwd...
[7s] Version: 3.5.521.1
[7s] [24/45] preinstalling libncurses5...
[7s] Version: 6.2+20210905-1
[8s] [25/45] preinstalling libselinux1...
[8s] Version: 3.1-3+b1
[8s] [26/45] preinstalling login...
[8s] Version: 1:4.8.1-1.1
[8s] [27/45] preinstalling xz-utils...
[8s] Version: 5.2.5-2
[8s] [28/45] preinstalling base-files...
[8s] Version: 12
[8s] [29/45] preinstalling findutils...
[8s] Version: 4.8.0-1
[9s] [30/45] preinstalling passwd...
[9s] Version: 1:4.8.1-1.1
[9s] [31/45] preinstalling sed...
[9s] Version: 4.8-1
[9s] [32/45] preinstalling tar...
[9s] Version: 1.34+dfsg-1
[9s] [33/45] preinstalling util-linux...
[9s] Version: 2.37.2-4
[9s] [34/45] preinstalling coreutils...
[9s] Version: 8.32-4.11.1
[   10s] [35/45] preinstalling bash...
[   10s] Version: 5.1-3.11.1
[   10s] [36/45] preinstalling dpkg..

Bug#995452: libpam-ssh breaks the agent-forwarding of normal ssh

[Jerome BENOIT]

On Sun, 3 Oct 2021 03:25:54 +0300 Matti Kurkela  wrote:

Dear Kurkela, thanks for your report.

I apologies for my late reply.

Actually I agree with your comments.
My current set up on my main computer follows your comment below.

So far I can remember, I have never revisited the pam-auth-update(8)
configuration file of this package since I begun to maintain it.

Meanwhile, note that I put some warning in the README.Debian file.

Can you share your /etc/pam.d/login and /etc/pam.d/*dm files so that
I can compare with my set up ?


The workaround/fix for this would be to not let pam-auth-update add 
pam_ssh.so into common-auth and common-session, but add the necessary 
lines *selectively* only to services that handle local logins like 
/etc/pam.d/login and /etc/pam.d/*dm, but *not* to /etc/pam.d/sshd.


That should allow libpam-ssh to start the agent on initial login, but 
leave the SSH sessions and their agent forwarding alone.


If you need the "authentication by SSH key passphrase" functionality on 
SSH connections, you could add only the "auth optional pam_ssh.so 
try_first_pass" line to /etc/pam.d/sshd. (Note that this line should not 
be the first authentication module, to prevent an information leak, as 
described in the pam_ssh(8) man page.)





Cheers,
Jerome

--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B

Bug#950271: netperfmeter: can't start netperfmeter (passive) without DCCP

[Stephen Kitt]

Hi Thomas,

On Sun, 7 Nov 2021 19:50:34 +0100, Thomas Dreibholz
 wrote:
> I created an updated package for "unstable" on the mentors server:
> https://mentors.debian.net/package/netperfmeter/ .
> 
> How is the procedure for submitting a backport package for buster? The
> backport is probably quite easy to create, I assume it will just need an
> older version of debhelper. That is, specifying the version in
> debian/control and recreating the debian/compat file is probably sufficient?

You won’t be able to upload the new version to buster-backports; the only
version that could go there is a backport of 1.8.6~rc2-1 (the version
currently in bullseye). 1.9.2-1 could only be backported to
buster-backports-sloppy, but that shouldn’t be necessary – 1.8.6~rc2-1 should
be good enough for buster.

You shouldn’t need any change for that version. Debhelper compatibility level
13 is available in buster-backports too (although that’s not a concern  for
1.8.6~rc2-1). BTW debhelper compatibility levels should be specified using
debhelper-compat now, not debian/compat; see "man debhelper" for details.

See https://backports.debian.org/Contribute/ for detailed backporting
instructions, including how to prepare the changelog.

As mentioned previously, if you need further help don’t hesitate to ask! I
can also check your package for unstable if you don’t already have a mentor.

Regards,

Stephen


pgpJ73bh9QIcc.pgp
Description: OpenPGP digital signature

Bug#998780: caml-crush: bashism in configure script

[Andrej Shadura]

Source: caml-crush
Version: 1.0.10-4
Severity: normal
Tags: ftbfs
User: d...@packages.debian.org
Usertags: lineno-bashism

Hi,

Your package uses configure script with bash features not present in
POSIX without explicitly declaring the need to bash shell; this
currently works as configure scripts select bash, but when dash enables
LINENO support, your configure script will start failing:

 ../configure: 2616: test: make: unexpected operator
 checking for ocamlc... yes
 ../configure: 2682: test: yes: unexpected operator
 OCaml version is 4.11.1
 OCaml library path is /usr/lib/ocaml
 checking for ocamlopt... ocamlopt
 checking for ocamlc.opt... ocamlc.opt
 checking for ocamlopt.opt... ocamlopt.opt
 checking for ocamldep... ocamldep
 ...
 checking for dlfcn.h... yes
 checking for pthread.h... yes
 checking for camlp4... yes
 ../configure: 4083: test: yes: unexpected operator
 checking for ocamlfind... ocamlfind
 ../configure: 4181: test: yes: unexpected operator
 checking OCaml package camlidl... found
 checking for dlopen in -ldl... yes
 checking for pthread_mutex_init in -lpthread... yes
 checking for gawk... no
 checking for mawk... mawk
 ../configure: 4419: test: yes: unexpected operator
 checking for camlidl... yes
 ../configure: 4478: test: yes: unexpected operator
 checking for spatch... yes
 ../configure: 4525: test: yes: unexpected operator
 Detected coccinelle version 1.1.0
 ../configure: 4568: test: yes: unexpected operator
 ../configure: 4605: test: yes: unexpected operator
 configure: Compiling OCaml bindings only
 configure: creating ./config.status
 ...
 configure.ac:1458: warning: AC_OUTPUT should be used without arguments.
 configure.ac:1458: You should run autoupdate.
   |-> Run ./configure with the desired options, and then make
 dh_auto_configure -Bbuild-UNIX_CLIENT -- --srcdir=.. 
--with-client-socket="unix,/var/run/pkcs11proxyd.socket"
install -d build-UNIX_CLIENT
cd build-UNIX_CLIENT && ../configure --build=x86_64-linux-gnu 
--prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking --srcdir=.. 
--with-client-socket=unix,/var/run/pkcs11proxyd.socket
 checking for make... make
 ../configure: 2616: test: make: unexpected operator
 checking for ocamlc... yes
 ../configure: 2682: test: yes: unexpected operator
 OCaml version is 4.11.1
 OCaml library path is /usr/lib/ocaml
 checking for ocamlopt... ocamlopt
 checking for ocamlc.opt... ocamlc.opt
 ...
 checking for caml/camlidlruntime.h... yes
 checking for dlfcn.h... yes
 checking for pthread.h... yes
 checking for camlp4... yes
 ../configure: 4083: test: yes: unexpected operator
 checking for ocamlfind... ocamlfind
 ../configure: 4181: test: yes: unexpected operator
 checking OCaml package camlidl... found
 checking for dlopen in -ldl... yes
 checking for pthread_mutex_init in -lpthread... yes
 checking for gawk... no
 checking for mawk... mawk
 ../configure: 4419: test: yes: unexpected operator
 ../configure: 4605: test: yes: unexpected operator
 configure: Compiling OCaml bindings only
 configure: creating ./config.status
 config.status: creating src/bindings-pkcs11/Makefile
 config.status: creating src/bindings-pkcs11/Makefile.standalone
 config.status: creating src/rpc-pkcs11/Makefile
 config.status: creating src/pkcs11proxyd/Makefile
 ...

To test this, you can install dash from experimental and re-run the
configure script.

Please replace non-POSIX features with their equivalents to make sure
the script runs with dash. Most common ones are usage of == instead of =
and for with arrays (not lists).

-- 
Cheers,
  Andrej


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

Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
[0s] Memory limit set to 46776712KB
[0s] Using BUILD_ROOT=/srv/obs/worker/root_3
[0s] Using BUILD_ARCH=x86_64:i686:i586:i486:i386
[0s] 
[0s] 
[0s] potassium started "build caml-crush_1.0.10-4.dsc" at Thu Nov  4 
22:35:25 UTC 2021.
[0s] build version: 20180831-2co3debian9.1
[0s] 
[0s]

Bug#998776: apertium-pt-gl: bashism in configure script

[Andrej Shadura]

Source: apertium-pt-gl
Version: 0.9.2~r57551-4
Severity: normal
Tags: ftbfs
User: d...@packages.debian.org
Usertags: lineno-bashism

Hi,

Your package uses configure script with bash features not present in
POSIX without explicitly declaring the need to bash shell; this
currently works as configure scripts select bash, but when dash enables
LINENO support, your configure script will start failing:

 ./configure: 2946: test: =: unexpected operator
 checking that generated files are newer than configure... done
 configure: creating ./config.status
 config.status: creating Makefile
 config.status: creating config

To test this, you can install dash from experimental and re-run the
configure script.

Please replace non-POSIX features with their equivalents to make sure
the script runs with dash. Most common ones are usage of == instead of =
and for with arrays (not lists).

-- 
Cheers,
  Andrej


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

Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
[0s] Memory limit set to 46776712KB
[0s] Using BUILD_ROOT=/srv/obs/worker/root_3
[0s] Using BUILD_ARCH=x86_64:i686:i586:i486:i386
[0s] 
[0s] 
[0s] potassium started "build apertium-pt-gl_0.9.2~r57551-4.dsc" at Thu Nov 
 4 17:16:19 UTC 2021.
[0s] build version: 20180831-2co3debian9.1
[0s] 
[0s] Building apertium-pt-gl for project 'home:andrewsh:sid' repository 
'main' arch 'x86_64' srcmd5 '7baffa2d7fcd8376b700a9e6da0871a0'
[0s] 
[0s] processing recipe 
/srv/obs/worker/root_3/.build-srcdir/apertium-pt-gl_0.9.2~r57551-4.dsc ...
[0s] running changelog2spec --target debian --file 
/srv/obs/worker/root_3/.build-srcdir/apertium-pt-gl_0.9.2~r57551-4.dsc
[0s] init_buildsystem --configdir 
/srv/obs/worker/run/worker/3/build/configs --cachedir /var/cache/obs-build 
--clean --create-build-binaries --rpmlist /srv/obs/worker/root_3/.build.rpmlist 
/srv/obs/worker/root_3/.build-srcdir/apertium-pt-gl_0.9.2~r57551-4.dsc build 
rpmlint-Factory ...
[0s] init_buildsystem version: 20180831-2co3debian9.1
[4s] cycle: libc6 -> libgcc-s1
[4s]   breaking dependency libgcc-s1 -> libc6
[4s] [1/45] preinstalling libgcc-s1...
[4s] Version: 11.2.0-10
[4s] [2/45] preinstalling libc6...
[4s] Version: 2.32-4
[4s] [3/45] preinstalling debianutils...
[4s] Version: 5.5-1
[4s] [4/45] preinstalling diffutils...
[4s] Version: 1:3.7-5
[5s] [5/45] preinstalling insserv...
[5s] Version: 1.23.0-1
[5s] [6/45] preinstalling libacl1...
[5s] Version: 2.3.1-11.1
[5s] [7/45] preinstalling libattr1...
[5s] Version: 1:2.5.1-11.1
[5s] [8/45] preinstalling libbz2-1.0...
[5s] Version: 1.0.8-4
[5s] [9/45] preinstalling libc-bin...
[5s] Version: 2.32-4
[5s] [10/45] preinstalling libcrypt1...
[5s] Version: 1:4.4.25-2
[5s] [11/45] preinstalling libdbus-1-3...
[5s] Version: 1.12.20-3
[5s] [12/45] preinstalling libdebconfclient0...
[5s] Version: 0.2601.1
[5s] [13/45] preinstalling libgmp10...
[5s] Version: 2:6.2.1+dfsg-2
[5s] [14/45] preinstalling liblzma5...
[5s] Version: 5.2.5-2
[5s] [15/45] preinstalling libpcre2-8-0...
[5s] Version: 10.36-2
[5s] [16/45] preinstalling libpcre3...
[5s] Version: 2:8.39-13
[5s] [17/45] preinstalling libsepol1...
[5s] Version: 3.1-1
[5s] [18/45] preinstalling libsigsegv2...
[5s] Version: 2.13-1
[5s] [19/45] preinstalling libtinfo5...
[5s] Version: 6.2+20210905-1
[5s] [20/45] preinstalling mawk...
[5s] Version: 1.3.4.20200120-2
[5s] [21/45] preinstalling zlib1g...
[5s] Version: 1:1.2.11.dfsg-2
[6s] [22/45] preinstalling libstdc++6...
[6s] Version: 11.2.0-10
[6s] [23/45] preinstalling base-passwd...
[6s] Version: 3.5.52
[6s] [24/45] preinstalling libncurses5...
[6s] Version: 6.2+20210905-1
[6s] [25/45] preinstalling libselinux1...
[6s] Version: 3.1-3+b1
[6s] [26/45] preinstalling login...
[6s] Version: 1:4.8.1-1.1
[6s] [27/45] preinstalling xz-utils...
[6s] Version: 5.2.5-2
[6s] [28/45] preinstalling base-files...
[6s] Version: 12
[6s] [29/45] preinstalling findutils...
[6s] Version: 4.8.0-1
[6s] [30/45] preinstalling passwd...
[6s] Version: 1:4.8.1-1.1
[6s] [31/45] preinstalling sed...
[6s] Version: 4.8-1
[6s] [32/45] preinstalling tar...
[6s] Version: 1.34+dfsg-1
[7s] [33/45] preinstalling util-linux...
[7s] Version: 2.37.2-4
[   

Bug#998775: src:licensecheck: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: licensecheck
Version: 3.2.11-1
Severity: serious
Control: close -1 3.2.13-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 997882

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:licensecheck has been trying to migrate
for 63 days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bookworm, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=licensecheck




OpenPGP_signature
Description: OpenPGP digital signature

Bug#998774: apertium-oc-es: bashism in configure script

[Andrej Shadura]

Source: apertium-oc-es
Version: 1.0.6~r57551-4
Severity: normal
Tags: ftbfs
User: d...@packages.debian.org
Usertags: lineno-bashism

Hi,

Your package uses configure script with bash features not present in
POSIX without explicitly declaring the need to bash shell; this
currently works as configure scripts select bash, but when dash enables
LINENO support, your configure script will start failing:

 ./configure: 2946: test: =: unexpected operator
 checking that generated files are newer than configure... done
 configure: creating ./config.status
 config.status: creating Makefile
 config.status: creating config

To test this, you can install dash from experimental and re-run the
configure script.

Please replace non-POSIX features with their equivalents to make sure
the script runs with dash. Most common ones are usage of == instead of =
and for with arrays (not lists).

-- 
Cheers,
  Andrej


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

Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
[0s] Memory limit set to 46776712KB
[0s] Using BUILD_ROOT=/srv/obs/worker/root_1
[0s] Using BUILD_ARCH=x86_64:i686:i586:i486:i386
[0s] 
[0s] 
[0s] potassium started "build apertium-oc-es_1.0.6~r57551-4.dsc" at Thu Nov 
 4 17:12:34 UTC 2021.
[0s] build version: 20180831-2co3debian9.1
[0s] 
[0s] Building apertium-oc-es for project 'home:andrewsh:sid' repository 
'main' arch 'x86_64' srcmd5 'c71a6e23578e370b3616c52ed8c90406'
[0s] 
[0s] processing recipe 
/srv/obs/worker/root_1/.build-srcdir/apertium-oc-es_1.0.6~r57551-4.dsc ...
[0s] running changelog2spec --target debian --file 
/srv/obs/worker/root_1/.build-srcdir/apertium-oc-es_1.0.6~r57551-4.dsc
[0s] init_buildsystem --configdir 
/srv/obs/worker/run/worker/1/build/configs --cachedir /var/cache/obs-build 
--clean --create-build-binaries --rpmlist /srv/obs/worker/root_1/.build.rpmlist 
/srv/obs/worker/root_1/.build-srcdir/apertium-oc-es_1.0.6~r57551-4.dsc build 
rpmlint-Factory ...
[0s] init_buildsystem version: 20180831-2co3debian9.1
[4s] cycle: libc6 -> libgcc-s1
[4s]   breaking dependency libgcc-s1 -> libc6
[4s] [1/45] preinstalling libgcc-s1...
[4s] Version: 11.2.0-10
[4s] [2/45] preinstalling libc6...
[4s] Version: 2.32-4
[5s] [3/45] preinstalling debianutils...
[5s] Version: 5.5-1
[5s] [4/45] preinstalling diffutils...
[5s] Version: 1:3.7-5
[5s] [5/45] preinstalling insserv...
[5s] Version: 1.23.0-1
[5s] [6/45] preinstalling libacl1...
[5s] Version: 2.3.1-11.1
[5s] [7/45] preinstalling libattr1...
[5s] Version: 1:2.5.1-11.1
[5s] [8/45] preinstalling libbz2-1.0...
[5s] Version: 1.0.8-4
[5s] [9/45] preinstalling libc-bin...
[5s] Version: 2.32-4
[5s] [10/45] preinstalling libcrypt1...
[5s] Version: 1:4.4.25-2
[5s] [11/45] preinstalling libdbus-1-3...
[5s] Version: 1.12.20-3
[5s] [12/45] preinstalling libdebconfclient0...
[5s] Version: 0.2601.1
[6s] [13/45] preinstalling libgmp10...
[6s] Version: 2:6.2.1+dfsg-2
[6s] [14/45] preinstalling liblzma5...
[6s] Version: 5.2.5-2
[6s] [15/45] preinstalling libpcre2-8-0...
[6s] Version: 10.36-2
[6s] [16/45] preinstalling libpcre3...
[6s] Version: 2:8.39-13
[6s] [17/45] preinstalling libsepol1...
[6s] Version: 3.1-1
[6s] [18/45] preinstalling libsigsegv2...
[6s] Version: 2.13-1
[6s] [19/45] preinstalling libtinfo5...
[6s] Version: 6.2+20210905-1
[6s] [20/45] preinstalling mawk...
[6s] Version: 1.3.4.20200120-2
[6s] [21/45] preinstalling zlib1g...
[6s] Version: 1:1.2.11.dfsg-2
[6s] [22/45] preinstalling libstdc++6...
[6s] Version: 11.2.0-10
[6s] [23/45] preinstalling base-passwd...
[6s] Version: 3.5.52
[6s] [24/45] preinstalling libncurses5...
[6s] Version: 6.2+20210905-1
[6s] [25/45] preinstalling libselinux1...
[6s] Version: 3.1-3+b1
[6s] [26/45] preinstalling login...
[6s] Version: 1:4.8.1-1.1
[7s] [27/45] preinstalling xz-utils...
[7s] Version: 5.2.5-2
[7s] [28/45] preinstalling base-files...
[7s] Version: 12
[7s] [29/45] preinstalling findutils...
[7s] Version: 4.8.0-1
[7s] [30/45] preinstalling passwd...
[7s] Version: 1:4.8.1-1.1
[7s] [31/45] preinstalling sed...
[7s] Version: 4.8-1
[7s] [32/45] preinstalling tar...
[7s] Version: 1.34+dfsg-1
[7s] [33/45] preinstalling util-linux...
[7s] Version: 2.37.2-4
[   

Bug#998773: apertium-oc-ca: bashism in configure script

[Andrej Shadura]

Source: apertium-oc-ca
Version: 1.0.6~r57551-4
Severity: normal
Tags: ftbfs
User: d...@packages.debian.org
Usertags: lineno-bashism

Hi,

Your package uses configure script with bash features not present in
POSIX without explicitly declaring the need to bash shell; this
currently works as configure scripts select bash, but when dash enables
LINENO support, your configure script will start failing:

 ./configure: 2946: test: =: unexpected operator
 checking that generated files are newer than configure... done
 configure: creating ./config.status
 config.status: creating Makefile
 config.status: creating config

To test this, you can install dash from experimental and re-run the
configure script.

Please replace non-POSIX features with their equivalents to make sure
the script runs with dash. Most common ones are usage of == instead of =
and for with arrays (not lists).

-- 
Cheers,
  Andrej


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

Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
[0s] Memory limit set to 46776712KB
[0s] Using BUILD_ROOT=/srv/obs/worker/root_3
[0s] Using BUILD_ARCH=x86_64:i686:i586:i486:i386
[0s] 
[1s] 
[1s] potassium started "build apertium-oc-ca_1.0.6~r57551-4.dsc" at Thu Nov 
 4 17:11:38 UTC 2021.
[1s] build version: 20180831-2co3debian9.1
[1s] 
[1s] Building apertium-oc-ca for project 'home:andrewsh:sid' repository 
'main' arch 'x86_64' srcmd5 '49eb9d6734ccc67de89b893de52fd09f'
[1s] 
[1s] processing recipe 
/srv/obs/worker/root_3/.build-srcdir/apertium-oc-ca_1.0.6~r57551-4.dsc ...
[1s] running changelog2spec --target debian --file 
/srv/obs/worker/root_3/.build-srcdir/apertium-oc-ca_1.0.6~r57551-4.dsc
[1s] init_buildsystem --configdir 
/srv/obs/worker/run/worker/3/build/configs --cachedir /var/cache/obs-build 
--clean --create-build-binaries --rpmlist /srv/obs/worker/root_3/.build.rpmlist 
/srv/obs/worker/root_3/.build-srcdir/apertium-oc-ca_1.0.6~r57551-4.dsc build 
rpmlint-Factory ...
[1s] init_buildsystem version: 20180831-2co3debian9.1
[5s] cycle: libc6 -> libgcc-s1
[5s]   breaking dependency libgcc-s1 -> libc6
[5s] [1/45] preinstalling libgcc-s1...
[5s] Version: 11.2.0-10
[5s] [2/45] preinstalling libc6...
[5s] Version: 2.32-4
[6s] [3/45] preinstalling debianutils...
[6s] Version: 5.5-1
[6s] [4/45] preinstalling diffutils...
[6s] Version: 1:3.7-5
[6s] [5/45] preinstalling insserv...
[6s] Version: 1.23.0-1
[6s] [6/45] preinstalling libacl1...
[6s] Version: 2.3.1-11.1
[6s] [7/45] preinstalling libattr1...
[6s] Version: 1:2.5.1-11.1
[6s] [8/45] preinstalling libbz2-1.0...
[6s] Version: 1.0.8-4
[6s] [9/45] preinstalling libc-bin...
[6s] Version: 2.32-4
[6s] [10/45] preinstalling libcrypt1...
[6s] Version: 1:4.4.25-2
[6s] [11/45] preinstalling libdbus-1-3...
[6s] Version: 1.12.20-3
[6s] [12/45] preinstalling libdebconfclient0...
[6s] Version: 0.2601.1
[6s] [13/45] preinstalling libgmp10...
[6s] Version: 2:6.2.1+dfsg-2
[6s] [14/45] preinstalling liblzma5...
[7s] Version: 5.2.5-2
[7s] [15/45] preinstalling libpcre2-8-0...
[7s] Version: 10.36-2
[7s] [16/45] preinstalling libpcre3...
[7s] Version: 2:8.39-13
[7s] [17/45] preinstalling libsepol1...
[7s] Version: 3.1-1
[7s] [18/45] preinstalling libsigsegv2...
[7s] Version: 2.13-1
[7s] [19/45] preinstalling libtinfo5...
[7s] Version: 6.2+20210905-1
[7s] [20/45] preinstalling mawk...
[7s] Version: 1.3.4.20200120-2
[7s] [21/45] preinstalling zlib1g...
[7s] Version: 1:1.2.11.dfsg-2
[7s] [22/45] preinstalling libstdc++6...
[7s] Version: 11.2.0-10
[7s] [23/45] preinstalling base-passwd...
[7s] Version: 3.5.52
[7s] [24/45] preinstalling libncurses5...
[7s] Version: 6.2+20210905-1
[7s] [25/45] preinstalling libselinux1...
[7s] Version: 3.1-3+b1
[7s] [26/45] preinstalling login...
[7s] Version: 1:4.8.1-1.1
[7s] [27/45] preinstalling xz-utils...
[7s] Version: 5.2.5-2
[8s] [28/45] preinstalling base-files...
[8s] Version: 12
[8s] [29/45] preinstalling findutils...
[8s] Version: 4.8.0-1
[8s] [30/45] preinstalling passwd...
[8s] Version: 1:4.8.1-1.1
[8s] [31/45] preinstalling sed...
[8s] Version: 4.8-1
[8s] [32/45] preinstalling tar...
[8s] Version: 1.34+dfsg-1
[8s] [33/45] preinstalling util-linux...
[8s] Version: 2.37.2-4
[   

Bug#998771: apertium-mk-bg: bashism in configure script

[Andrej Shadura]

Source: apertium-mk-bg
Version: 0.2.0~r49489-3
Severity: normal
Tags: ftbfs
User: d...@packages.debian.org
Usertags: lineno-bashism

Hi,

Your package uses configure script with bash features not present in
POSIX without explicitly declaring the need to bash shell; this
currently works as configure scripts select bash, but when dash enables
LINENO support, your configure script will start failing:

 ./configure: 3057: test: =: unexpected operator
 checking that generated files are newer than configure... done
 configure: creating ./config.status
 config.status: creating Makefile

To test this, you can install dash from experimental and re-run the
configure script.

Please replace non-POSIX features with their equivalents to make sure
the script runs with dash. Most common ones are usage of == instead of =
and for with arrays (not lists).

-- 
Cheers,
  Andrej


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

Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
[0s] Memory limit set to 46776712KB
[0s] Using BUILD_ROOT=/srv/obs/worker/root_6
[0s] Using BUILD_ARCH=x86_64:i686:i586:i486:i386
[0s] 
[0s] 
[0s] potassium started "build apertium-mk-bg_0.2.0~r49489-3.dsc" at Thu Nov 
 4 17:10:40 UTC 2021.
[0s] build version: 20180831-2co3debian9.1
[0s] 
[0s] Building apertium-mk-bg for project 'home:andrewsh:sid' repository 
'main' arch 'x86_64' srcmd5 '69d8e328bfe3f811accb0be4050fd3de'
[0s] 
[0s] processing recipe 
/srv/obs/worker/root_6/.build-srcdir/apertium-mk-bg_0.2.0~r49489-3.dsc ...
[0s] running changelog2spec --target debian --file 
/srv/obs/worker/root_6/.build-srcdir/apertium-mk-bg_0.2.0~r49489-3.dsc
[0s] init_buildsystem --configdir 
/srv/obs/worker/run/worker/6/build/configs --cachedir /var/cache/obs-build 
--clean --create-build-binaries --rpmlist /srv/obs/worker/root_6/.build.rpmlist 
/srv/obs/worker/root_6/.build-srcdir/apertium-mk-bg_0.2.0~r49489-3.dsc build 
rpmlint-Factory ...
[0s] init_buildsystem version: 20180831-2co3debian9.1
[5s] cycle: libc6 -> libgcc-s1
[5s]   breaking dependency libgcc-s1 -> libc6
[5s] [1/45] preinstalling libgcc-s1...
[5s] Version: 11.2.0-10
[5s] [2/45] preinstalling libc6...
[5s] Version: 2.32-4
[5s] [3/45] preinstalling debianutils...
[5s] Version: 5.5-1
[5s] [4/45] preinstalling diffutils...
[5s] Version: 1:3.7-5
[6s] [5/45] preinstalling insserv...
[6s] Version: 1.23.0-1
[6s] [6/45] preinstalling libacl1...
[6s] Version: 2.3.1-11.1
[6s] [7/45] preinstalling libattr1...
[6s] Version: 1:2.5.1-11.1
[6s] [8/45] preinstalling libbz2-1.0...
[6s] Version: 1.0.8-4
[6s] [9/45] preinstalling libc-bin...
[6s] Version: 2.32-4
[6s] [10/45] preinstalling libcrypt1...
[6s] Version: 1:4.4.25-2
[6s] [11/45] preinstalling libdbus-1-3...
[6s] Version: 1.12.20-3
[6s] [12/45] preinstalling libdebconfclient0...
[6s] Version: 0.2601.1
[6s] [13/45] preinstalling libgmp10...
[6s] Version: 2:6.2.1+dfsg-2
[6s] [14/45] preinstalling liblzma5...
[6s] Version: 5.2.5-2
[6s] [15/45] preinstalling libpcre2-8-0...
[6s] Version: 10.36-2
[6s] [16/45] preinstalling libpcre3...
[6s] Version: 2:8.39-13
[6s] [17/45] preinstalling libsepol1...
[6s] Version: 3.1-1
[6s] [18/45] preinstalling libsigsegv2...
[6s] Version: 2.13-1
[6s] [19/45] preinstalling libtinfo5...
[6s] Version: 6.2+20210905-1
[6s] [20/45] preinstalling mawk...
[6s] Version: 1.3.4.20200120-2
[6s] [21/45] preinstalling zlib1g...
[7s] Version: 1:1.2.11.dfsg-2
[7s] [22/45] preinstalling libstdc++6...
[7s] Version: 11.2.0-10
[7s] [23/45] preinstalling base-passwd...
[7s] Version: 3.5.52
[7s] [24/45] preinstalling libncurses5...
[7s] Version: 6.2+20210905-1
[7s] [25/45] preinstalling libselinux1...
[7s] Version: 3.1-3+b1
[7s] [26/45] preinstalling login...
[7s] Version: 1:4.8.1-1.1
[7s] [27/45] preinstalling xz-utils...
[7s] Version: 5.2.5-2
[7s] [28/45] preinstalling base-files...
[7s] Version: 12
[7s] [29/45] preinstalling findutils...
[7s] Version: 4.8.0-1
[7s] [30/45] preinstalling passwd...
[7s] Version: 1:4.8.1-1.1
[7s] [31/45] preinstalling sed...
[7s] Version: 4.8-1
[7s] [32/45] preinstalling tar...
[7s] Version: 1.34+dfsg-1
[8s] [33/45] preinstalling util-linux...
[8s] Version: 2.37.2-4
[8s] [34/45] preinstalling coreutils

Bug#998772: src:ruby-omniauth-openid-connect: fails to migrate to testing for too long: unresolved RC bug

[Paul Gevers]

Source: ruby-omniauth-openid-connect
Version: 0.3.5-1
Severity: serious
Control: close -1 0.4.0-2
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 996342

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:ruby-omniauth-openid-connect has been
trying to migrate for 63 days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bookworm, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=ruby-omniauth-openid-connect




OpenPGP_signature
Description: OpenPGP digital signature

Bug#998770: apertium-eu-en: bashism in configure script

[Andrej Shadura]

Source: apertium-eu-en
Version: 0.3.1~r56205-3
Severity: normal
Tags: ftbfs
User: d...@packages.debian.org
Usertags: lineno-bashism

Hi,

Your package uses configure script with bash features not present in
POSIX without explicitly declaring the need to bash shell; this
currently works as configure scripts select bash, but when dash enables
LINENO support, your configure script will start failing:

 ./configure: 2947: test: =: unexpected operator
 checking that generated files are newer than configure... done
 configure: creating ./config.status
 config.status: creating Makefile
 config.status: creating config

To test this, you can install dash from experimental and re-run the
configure script.

Please replace non-POSIX features with their equivalents to make sure
the script runs with dash. Most common ones are usage of == instead of =
and for with arrays (not lists).

-- 
Cheers,
  Andrej


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

Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
[0s] Memory limit set to 46776712KB
[0s] Using BUILD_ROOT=/srv/obs/worker/root_2
[0s] Using BUILD_ARCH=x86_64:i686:i586:i486:i386
[0s] 
[0s] 
[0s] potassium started "build apertium-eu-en_0.3.1~r56205-3.dsc" at Thu Nov 
 4 14:47:15 UTC 2021.
[0s] build version: 20180831-2co3debian9.1
[0s] 
[0s] Building apertium-eu-en for project 'home:andrewsh:sid' repository 
'main' arch 'x86_64' srcmd5 '376ec537fcac46ee6ad26f1ff5accc67'
[0s] 
[0s] processing recipe 
/srv/obs/worker/root_2/.build-srcdir/apertium-eu-en_0.3.1~r56205-3.dsc ...
[0s] running changelog2spec --target debian --file 
/srv/obs/worker/root_2/.build-srcdir/apertium-eu-en_0.3.1~r56205-3.dsc
[0s] init_buildsystem --configdir 
/srv/obs/worker/run/worker/2/build/configs --cachedir /var/cache/obs-build 
--clean --create-build-binaries --rpmlist /srv/obs/worker/root_2/.build.rpmlist 
/srv/obs/worker/root_2/.build-srcdir/apertium-eu-en_0.3.1~r56205-3.dsc build 
rpmlint-Factory ...
[0s] init_buildsystem version: 20180831-2co3debian9.1
[4s] cycle: libc6 -> libgcc-s1
[4s]   breaking dependency libgcc-s1 -> libc6
[4s] [1/45] preinstalling libgcc-s1...
[4s] Version: 11.2.0-10
[4s] [2/45] preinstalling libc6...
[4s] Version: 2.32-4
[4s] [3/45] preinstalling debianutils...
[4s] Version: 5.5-1
[4s] [4/45] preinstalling diffutils...
[4s] Version: 1:3.7-5
[5s] [5/45] preinstalling insserv...
[5s] Version: 1.23.0-1
[5s] [6/45] preinstalling libacl1...
[5s] Version: 2.3.1-11.1
[5s] [7/45] preinstalling libattr1...
[5s] Version: 1:2.5.1-11.1
[5s] [8/45] preinstalling libbz2-1.0...
[5s] Version: 1.0.8-4
[5s] [9/45] preinstalling libc-bin...
[5s] Version: 2.32-4
[5s] [10/45] preinstalling libcrypt1...
[5s] Version: 1:4.4.25-2
[5s] [11/45] preinstalling libdbus-1-3...
[5s] Version: 1.12.20-3
[5s] [12/45] preinstalling libdebconfclient0...
[5s] Version: 0.2601.1
[5s] [13/45] preinstalling libgmp10...
[5s] Version: 2:6.2.1+dfsg-2
[5s] [14/45] preinstalling liblzma5...
[5s] Version: 5.2.5-2
[5s] [15/45] preinstalling libpcre2-8-0...
[5s] Version: 10.36-2
[5s] [16/45] preinstalling libpcre3...
[5s] Version: 2:8.39-13
[5s] [17/45] preinstalling libsepol1...
[5s] Version: 3.1-1
[5s] [18/45] preinstalling libsigsegv2...
[5s] Version: 2.13-1
[5s] [19/45] preinstalling libtinfo5...
[5s] Version: 6.2+20210905-1
[5s] [20/45] preinstalling mawk...
[5s] Version: 1.3.4.20200120-2
[6s] [21/45] preinstalling zlib1g...
[6s] Version: 1:1.2.11.dfsg-2
[6s] [22/45] preinstalling libstdc++6...
[6s] Version: 11.2.0-10
[6s] [23/45] preinstalling base-passwd...
[6s] Version: 3.5.52
[6s] [24/45] preinstalling libncurses5...
[6s] Version: 6.2+20210905-1
[6s] [25/45] preinstalling libselinux1...
[6s] Version: 3.1-3+b1
[6s] [26/45] preinstalling login...
[6s] Version: 1:4.8.1-1.1
[6s] [27/45] preinstalling xz-utils...
[6s] Version: 5.2.5-2
[6s] [28/45] preinstalling base-files...
[6s] Version: 12
[6s] [29/45] preinstalling findutils...
[6s] Version: 4.8.0-1
[6s] [30/45] preinstalling passwd...
[6s] Version: 1:4.8.1-1.1
[6s] [31/45] preinstalling sed...
[6s] Version: 4.8-1
[6s] [32/45] preinstalling tar...
[6s] Version: 1.34+dfsg-1
[7s] [33/45] preinstalling util-linux...
[7s] Version: 2.37.2-4
[   

Bug#998769: apertium-eo-en: bashism in configure script

[Andrej Shadura]

Source: apertium-eo-en
Version: 1.0.0~r63833-3
Severity: normal
Tags: ftbfs
User: d...@packages.debian.org
Usertags: lineno-bashism

Hi,

Your package uses configure script with bash features not present in
POSIX without explicitly declaring the need to bash shell; this
currently works as configure scripts select bash, but when dash enables
LINENO support, your configure script will start failing:

 /bin/sh: 1: [: unexpected operator
 apertium-preprocess-transfer-bytecode-j apertium-eo-en.eo-en.t1x 
eo-en.t1x.class
 make[2]: apertium-preprocess-transfer-bytecode-j: No such file or directory
 make[2]: [Makefile:804: eo-en.t1x.bin] Error 127 (ignored)
 apertium-validate-interchunk apertium-eo-en.eo-en.t2x
 apertium-preprocess-transfer apertium-eo-en.eo-en.t2x eo-en.t2x.bin
 apertium-validate-interchunk apertium-eo-en.eo-en.antaux_t2x
 apertium-preprocess-transfer apertium-eo-en.eo-en.antaux_t2x 
eo-en.antaux_t2x.bin
 apertium-validate-postchunk apertium-eo-en.eo-en.t3x
 apertium-preprocess-transfer apertium-eo-en.eo-en.t3x eo-en.t3x.bin
 apertium-validate-transfer apertium-eo-en.en-eo.t1x
 apertium-preprocess-transfer apertium-eo-en.en-eo.t1x en-eo.t1x.bin
 Warning (3360): Paths to rule 57 blocked by rule 55.
 Warning (4670): Paths to rule 82 blocked by rule 81.
 /usr/bin/which: this version of `which' is deprecated; use `command -v' in 
scripts instead.
 /bin/sh: 1: [: unexpected operator
 apertium-preprocess-transfer-bytecode-j apertium-eo-en.en-eo.t1x 
en-eo.t1x.class
 make[2]: apertium-preprocess-transfer-bytecode-j: No such file or directory
 make[2]: [Makefile:818: en-eo.t1x.bin] Error 127 (ignored)

To test this, you can install dash from experimental and re-run the
configure script.

Please replace non-POSIX features with their equivalents to make sure
the script runs with dash. Most common ones are usage of == instead of =
and for with arrays (not lists).

-- 
Cheers,
  Andrej


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

Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
[0s] Memory limit set to 46776712KB
[0s] Using BUILD_ROOT=/srv/obs/worker/root_2
[0s] Using BUILD_ARCH=x86_64:i686:i586:i486:i386
[0s] 
[0s] 
[0s] potassium started "build apertium-eo-en_1.0.0~r63833-3.dsc" at Thu Nov 
 4 14:43:02 UTC 2021.
[0s] build version: 20180831-2co3debian9.1
[0s] 
[0s] Building apertium-eo-en for project 'home:andrewsh:sid' repository 
'main' arch 'x86_64' srcmd5 '7fb9de51dc51324be53e26d678d3d42f'
[0s] 
[0s] processing recipe 
/srv/obs/worker/root_2/.build-srcdir/apertium-eo-en_1.0.0~r63833-3.dsc ...
[0s] running changelog2spec --target debian --file 
/srv/obs/worker/root_2/.build-srcdir/apertium-eo-en_1.0.0~r63833-3.dsc
[0s] init_buildsystem --configdir 
/srv/obs/worker/run/worker/2/build/configs --cachedir /var/cache/obs-build 
--clean --create-build-binaries --rpmlist /srv/obs/worker/root_2/.build.rpmlist 
/srv/obs/worker/root_2/.build-srcdir/apertium-eo-en_1.0.0~r63833-3.dsc build 
rpmlint-Factory ...
[0s] init_buildsystem version: 20180831-2co3debian9.1
[5s] cycle: libc6 -> libgcc-s1
[5s]   breaking dependency libgcc-s1 -> libc6
[5s] [1/45] preinstalling libgcc-s1...
[5s] Version: 11.2.0-10
[5s] [2/45] preinstalling libc6...
[5s] Version: 2.32-4
[5s] [3/45] preinstalling debianutils...
[5s] Version: 5.5-1
[5s] [4/45] preinstalling diffutils...
[5s] Version: 1:3.7-5
[5s] [5/45] preinstalling insserv...
[5s] Version: 1.23.0-1
[5s] [6/45] preinstalling libacl1...
[5s] Version: 2.3.1-11.1
[6s] [7/45] preinstalling libattr1...
[6s] Version: 1:2.5.1-11.1
[6s] [8/45] preinstalling libbz2-1.0...
[6s] Version: 1.0.8-4
[6s] [9/45] preinstalling libc-bin...
[6s] Version: 2.32-4
[6s] [10/45] preinstalling libcrypt1...
[6s] Version: 1:4.4.25-2
[6s] [11/45] preinstalling libdbus-1-3...
[6s] Version: 1.12.20-3
[6s] [12/45] preinstalling libdebconfclient0...
[6s] Version: 0.2601.1
[6s] [13/45] preinstalling libgmp10...
[6s] Version: 2:6.2.1+dfsg-2
[6s] [14/45] preinstalling liblzma5...
[6s] Version: 5.2.5-2
[6s] [15/45] preinstalling libpcre2-8-0...
[6s] Version: 10.36-2
[6s] [16/45] preinstalling libpcre3...
[6s] Version: 2:8.39-13
[6s] [17/45] preinstalling libsepol1...
[6s] Version: 3.1-1
[6s] [18/45] preinstalling libsigsegv2...
[6s] Version: 2.13-1
[

Bug#998767: mkdocs: readthedocs theme is not self contained

[Salvo 'LtWorf' Tomaselli]

Package: mkdocs
Version: 1.1.2+dfsg-2
Severity: normal
Tags: upstream
X-Debbugs-Cc: tipos...@tiscali.it

Hello,

I use mkdocs for typedload (python3-typedload) and to generate the website from
markdown text files.

However I realised that my adblock in the browser complains, because the 
"readthedocs"
theme included with mkdocs uses css and js files from cloudflare and is not self
contained.


The js file in question is highlight.js, which seems to be present in copious 
copies in the
debian archive, mostly in documentation packages.

For me the ideal would be to align mkdocs with the other packages and vendor 
the file rather
than link it to an external domain I have no control over.

The even better solution would probably be to have a package with it, which can 
be symlinked by
all the packages which use the file.

Best

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

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

Versions of packages mkdocs depends on:
ii  fonts-font-awesome   5.0.10+really4.7.0~dfsg-4.1
ii  libjs-bootstrap4 4.5.2+dfsg1-8
ii  libjs-jquery 3.5.1+dfsg+~3.5.5-7
ii  libjs-lunr   2.3.8~dfsg-3
ii  libjs-modernizr  2.6.2+ds1-4
ii  python3  3.9.7-1
ii  python3-click8.0.2-1
ii  python3-jinja2   3.0.1-2
ii  python3-livereload   2.6.3-2
ii  python3-markdown 3.3.4-1
ii  python3-pkg-resources58.2.0-1
ii  python3-tornado  6.1.0-1+b1
ii  python3-yaml 5.4.1-1
ii  sphinx-rtd-theme-common  1.0.0+dfsg-1

mkdocs recommends no packages.

Versions of packages mkdocs suggests:
pn  ghp-import  
pn  mkdocs-doc  
pn  nodejs  

-- no debconf information

Bug#998754: praat: libasound2-plugins package needed to record in praat

[Castedo Ellerman]

On 11/7/21 13:12, Rafael Laboissière wrote:
Praat in Debian can perfectly record sounds from the microphone 
without the libasound2-plugins package installed. Of course, a sound 
card is needed for that.


At any rate, it would be convenient to be able to do recordings in the 
corner case that you describe (i.e. without sound card but with a 
PulseAudio domain socket available).


However, I dislike the idea of forcing the dependency on 
libasound2-plugins. Do you think that Suggests would be enough?


Putting libasound2-plugins only in Suggests sounds reasonable to me. I 
think the right choice depends on whether one thinks PulseAudio is the 
ideal universal interface for application to access audio and 
applications should avoid directly accessing lower level interfaces like 
ALSA and /dev/snd. I have not been following the progress of sound 
interfaces in Linux very much, but I suspect it's not clear PulseAudio 
is the audio interface that everybody will adopt and should start using. 
I see there is also JACK, GStreamer and PipeWire which also sound like 
high level audio interfaces for applications.

Bug#997794: xscreensaver: systemd integration leads to spurious deactivations (unblank) on desktop

[Lionel Élie Mamane]

I reproduced the issue with 6.02 and more patience, too, but it
doesn't log anything. I locked the screen, and at 20:01 it
spontaneously turned on again, and the XScreenSaver login screen
appeared. At 20:15 I moved the mouse and unlocked (entering my
password), and ran "xscreensaver-command -exit". Here's the full
log file. It doesn't show any of the above described events.


##
xscreensaver: 19:30:12: logging to "logfile4"
##

XScreenSaver 6.02, released Oct 2021
Copyright © 1991-2021 by Jamie Zawinski 

xscreensaver-gfx: 19:49:43: screens in use: 2
xscreensaver-gfx: 19:49:43:0/0: 1440x2560+0+0 (DP-1)
xscreensaver-gfx: 19:49:43:1/0: 1440x2560+1440+0 (DP-2)

Bug#993350: [sane-devel] Epson Perfection1640: Operation not supported

[Wolfram Sang]

> It is better in that it no longer crashes, but is still a 
> regression: I suspect that I can no longer scan films.
> 
> So it seems that commit 580c278dcafe4159213406b4307ee8598fe08fe7
> was too simplistic?

It is true that the option is not a boolean anymore but an integer. But
still, if you selet the TPU the old default value for 2.5mm above glass
(89) should be automatically selected. Without TPU, it should use the
default of on glass (64).

I tested this on an Epson 12000XL and Perfection1640.

Please check if that works on your system as well.



signature.asc
Description: PGP signature

Bug#998763: openjdk-17-doc: Java 17 documentation wrong jquery symlink

[Maurizio Sartori]

Package: openjdk-17-doc
Version: 17.0.1+12-1
Severity: normal

Dear Maintainer,
I just installed the Java 17 documentation and opening it in a browser the
search is not working.
Looking at the file, I found that there is a wrong symlink
   /usr/share/doc/openjdk-17-jre/api/script-dir/jquery-3.5.1.min.js
  -> ../../../../javascript/jquery-ui/jquery-ui.min.js
It points to jquery-ui instead of jquery

Changing it with:
   /usr/share/doc/openjdk-17-jre/api/script-dir/jquery-3.5.1.min.js
  -> ../../../../javascript/jquery/jquery.min.js
the search works as expected

Regards


-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'testing'), (500, 'stable'), (10, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_DK.utf8, LC_CTYPE=en_DK.utf8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openjdk-17-doc depends on:
ii  libjs-jquery3.5.1+dfsg+~3.5.5-8
ii  libjs-jquery-ui 1.12.1+dfsg-8
ii  libjs-jquery-ui-theme-base  1.12.1+dfsg-1

openjdk-17-doc recommends no packages.

Versions of packages openjdk-17-doc suggests:
ii  openjdk-17-jdk  17.0.1+12-1

-- no debconf information

Bug#993505: netgen-lvs: diff for NMU version 1.5.133-1.1

[Adrian Bunk]

Control: tags 993505 + patch
Control: tags 993505 + pending

Dear maintainer,

I've prepared an NMU for netgen-lvs (versioned as 1.5.133-1.1) and 
uploaded it to DELAYED/15. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru netgen-lvs-1.5.133/debian/changelog netgen-lvs-1.5.133/debian/changelog
--- netgen-lvs-1.5.133/debian/changelog	2019-10-19 12:35:31.0 +0300
+++ netgen-lvs-1.5.133/debian/changelog	2021-11-07 20:50:30.0 +0200
@@ -1,3 +1,10 @@
+netgen-lvs (1.5.133-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with autoconf 2.71. (Closes: #993505)
+
+ -- Adrian Bunk   Sun, 07 Nov 2021 20:50:30 +0200
+
 netgen-lvs (1.5.133-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru netgen-lvs-1.5.133/debian/patches/autoconf2.71.patch netgen-lvs-1.5.133/debian/patches/autoconf2.71.patch
--- netgen-lvs-1.5.133/debian/patches/autoconf2.71.patch	1970-01-01 02:00:00.0 +0200
+++ netgen-lvs-1.5.133/debian/patches/autoconf2.71.patch	2021-11-07 20:50:30.0 +0200
@@ -0,0 +1,15 @@
+Description: Fix FTBFS with autoconf 2.71
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/993505
+
+--- netgen-lvs-1.5.133.orig/scripts/configure.in
 netgen-lvs-1.5.133/scripts/configure.in
+@@ -4,7 +4,7 @@ dnl Use autoconf 2.52 or newer.
+ AC_INIT(netgen, 1.3, eda-...@opencircuitdesign.com)
+ AC_PREREQ(2.52)
+ AC_CONFIG_SRCDIR(rules.mak)
+-AC_CONFIG_AUX_DIR(.)
++AC_CONFIG_AUX_DIR(scripts)
+ 
+ AC_CANONICAL_SYSTEM
+ 
diff -Nru netgen-lvs-1.5.133/debian/patches/series netgen-lvs-1.5.133/debian/patches/series
--- netgen-lvs-1.5.133/debian/patches/series	2019-10-19 12:35:31.0 +0300
+++ netgen-lvs-1.5.133/debian/patches/series	2021-11-07 20:50:30.0 +0200
@@ -1,2 +1,3 @@
 0002-Make-sure-hardening-flags-are-passed-down.patch
 0002-Fix-some-sprintf-calls.patch
+autoconf2.71.patch

Bug#998762: RM: golang-gopkg-flosch-pongo2.v3 -- ROM; Orphaned; superseded by golang-gopkg-flosch-pongo2.v4

[Aloïs Micard]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: creekor...@debian.org, math...@calenhad.com

Please remove golang-gopkg-flosch-pongo2.v3 from unstable, it
is not used anymore and will be superseded by golang-gopkg-flosch-pongo2.v4
(currently in NEW).

```
creekorful@coccia:~$ dak rm -Rn golang-gopkg-flosch-pongo2.v3
Will remove the following packages from unstable:

golang-gopkg-flosch-pongo2.v3 |  3.0-4 | source
golang-gopkg-flosch-pongo2.v3-dev |  3.0-4 | all

Maintainer: Debian Go Packaging Team 


--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.
```

Thanks!

Cheers,

--
Aloïs Micard 

GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2







OpenPGP_signature
Description: OpenPGP digital signature

Bug#998761: ITP: golang-github-x448-float16 -- IEEE 754 half-precision format with correct conversions to/from float32

[Mathias Gibbens]

Package: wnpp
Severity: wishlist
Owner: Mathias Gibbens 
X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org

* Package name: golang-github-x448-float16
  Version : 0.8.4-1
  Upstream Author : Montgomery Edwards and Faye Amacker
* URL : https://github.com/x448/float16
* License : Expat
  Programming Lang: Go
  Description : IEEE 754 half-precision format with correct conversions 
to/from float32

 x448/float16 package provides IEEE 754 half-precision
 floating-point format (binary16) with IEEE 754 default
 rounding for conversions. IEEE 754-2008 refers to this
 16-bit floating-point format as binary16.
 .
 IEEE 754 default rounding ("Round-to-Nearest
 RoundTiesToEven") is considered the most accurate and
 statistically unbiased estimate of the true result.

This package is a dependency of golang-github-fxamacker-cbor (ITP
#998760), which is needed by golang-github-duo-labs-webauthn (ITP
#998759).

This package will be team-maintained within the Debian Go Packaging
Team.


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

Bug#998760: ITP: golang-github-fxamacker-cbor -- CBOR codec implementing RFCs 7049 & 8949

[Mathias Gibbens]

Package: wnpp
Severity: wishlist
Owner: Mathias Gibbens 
X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org

* Package name: golang-github-fxamacker-cbor
  Version : 2.3.0-1
  Upstream Author : Faye Amacker
* URL : https://github.com/fxamacker/cbor
* License : Expat
  Programming Lang: Go
  Description : CBOR codec implementing RFCs 7049 & 8949

 CBOR is a concise binary data format inspired by JSON and MessagePack.
 CBOR is defined in RFC 8949 (December 2020) which obsoletes RFC 7049
 (October 2013).
 .
 CBOR is an Internet Standard by IETF. It's used in other standards
 like WebAuthn by W3C, COSE (RFC 8152), CWT (RFC 8392), CDDL (RFC 8610)
 and more.

This package is a dependency of golang-github-duo-labs-webauthn (ITP
#998759), which is needed for packaging LXD (ITP #768073).

This package will be team-maintained within the Debian Go Packaging
Team.


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

Bug#950271: netperfmeter: can't start netperfmeter (passive) without DCCP

[Thomas Dreibholz]

Hi,

I created an updated package for "unstable" on the mentors server:
https://mentors.debian.net/package/netperfmeter/ .

How is the procedure for submitting a backport package for buster? The
backport is probably quite easy to create, I assume it will just need an
older version of debhelper. That is, specifying the version in
debian/control and recreating the debian/compat file is probably sufficient?

Den 21.04.2020 19:00, skrev Stephen Kitt:
> Control: retitle -1 Please provide a backported netperfmeter for Buster
>
> Hi Zac,
>
> On Thu, Jan 30, 2020 at 03:07:08PM -0500, Zachary Wolff wrote:
>> I've had some contact with the maintainer.
>> He advised netperfmeter 1.2.3 is quite old.
>> Debian testing and unstable have much newer versions and shouldn't have
>> this problem.
>>
>> netperfmeter is not in buster-backports at the moment.
>>
>> Can we get a newer version of netperfmeter added to buster or
>> buster-backports?
> Thanks for filing this; as you say, the bug is already fixed in
> Bullseye, but rather than closing it, I’ve changed it to a request for
> a backport to Buster.
>
> I can help backport this if necessary.
>
> Regards,
>
> Stephen

-- 
Best regards / Mit freundlichen Grüßen / Med vennlig hilsen

===
 Thomas Dreibholz

 SimulaMet -- Simula Metropolitan Centre for Digital Engineering
 Centre for Resilient Networks and Applications
 Pilestredet 52
 0167 Oslo, Norway
---
 E-Mail: dre...@simula.no
 Homepage:   http://simula.no/people/dreibh
===




OpenPGP_signature
Description: OpenPGP digital signature

Bug#998686: [pkg-apparmor] Bug#998686: apparmor: b-d on python3-all-dev, but not built for all supported Python3 versions

[intrigeri]

Hi,

Graham Inggs (2021-11-06):
> This package build-depends on python3-all-dev, but does not build
> extensions/libraries for all supported python3 versions.

Thanks for this report :)

debian/rules tries to build for every Python 3 version
output by "py3versions -s".

On my sid system, this command currently outputs only "python3.9".

I understand that somehow, debian/rules should figure out that Python
3.10 is supported too. Correct?
If so: where can it find this information?

Thanks in advance,
cheers!

Bug#998759: ITP: golang-github-duo-labs-webauthn -- WebAuthn (FIDO2) server library

[Mathias Gibbens]

Package: wnpp
Severity: wishlist
Owner: Mathias Gibbens 
X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org

* Package name: golang-github-duo-labs-webauthn
  Version : 0.0~git20210727.9f1b88e-1
  Upstream Author : Duo Security, Inc
* URL : https://github.com/duo-labs/webauthn
* License : BSD-3-clause
  Programming Lang: Go
  Description : WebAuthn (FIDO2) server library

 This library is meant to handle Web Authentication for Go apps
 that wish to implement a passwordless solution for users. While
 the specification is currently in Candidate Recommendation, this
 library conforms as much as possible to the guidelines and
 implementation procedures outlined by the document.

This package is a dependency for packaging LXD (ITP #768073).

This package will be team-maintained within the Debian Go Packaging
Team.


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

Bug#998318: cups-client: lpoptions ignores and deletes settings of printer instances in ~/.cups/lpoptions

[mtemp001]

* any attempt to modify printer instance settings using "lpoptions -p
laserjet5si/konzept -o InputSlot=Upper" results in deletion of all
"Dest" lines previously present within lpoptions file and modification
of the single line that was considered to be affected

Not quite my observation. I cannot set up more than one instance. Adding
a second one witj lpoptions deletes the existing one. You show five
lines in your example. Was ~/.cups/lpoptions edited by hand?



For clarification:
The  ~/.cups/lpoptions file cited above has been extracted from a backup 
taken before upgrade towards debian bullseye (minus potential but in 
case present unintentional modifications while copy-pasting from the 
backup).
It is being rewirtten in the same way you reproduced above upon any 
attempt to issue an "lpoptions -p" command with the new CUPS installation.


Thanks for keeping tracks of this issue.

Regards,
Martin

Bug#997794: xscreensaver: systemd integration leads to spurious deactivations (unblank) on desktop

[Jamie Zawinski]

On Nov 7, 2021, at 10:31 AM, Lionel Élie Mamane  wrote:
> 
>> I couldn't immediately reproduce the behaviour I as complaining
>> about within a few minutes, also not with 5.45. (...) I will make
>> longer (e.g. overnight) tests.
> 
> I reproduced the issue with 5.45 and more patience, on the scale of
> ten minutes. The attached log file is from 5.45 and contains at least
> two occurrences, about 10 minutes apart. The screen spontaneously
> turns back on, and back off after about 3 minutes, the configured idle
> time to DPMS off.

I don't know what "about ten minutes apart" means without you saying actual 
timestamps, but that log file shows the screen powering on due to user activity:

> xscreensaver: 18:48:06: user is active (keyboard activity)
> ...
> xscreensaver: 19:25:42: user is active (mouse motion)


--
Jamie Zawinski  https://www.jwz.org/  https://www.dnalounge.com/

Bug#998718: Brasero fails (on Testing) burning an ISO image on a CD-RW

[Thomas Schmitt]

Hi,

i am upstream programmer of libburn, which might be in charge of
burning underneath Brasero. Regrettably i cannot interpret Brasero's
messages unless they come from libburn or libisofs. So i am not sure
whether i can help with fixing Brasero.

The statement by other software that no medium is found in /dev/sr0
surprises me. Such a status assessment is usually done by the drive
and i am not aware of any regular means to let a drive ignore or deny
its loaded medium.

Do you see anything in dmesg that occured when Brasero failed and looks
related to "sr" or "cdrom" ?

Can i talk you into inquring the drive by xorriso and logging its
SCSI transactions when the drive has gone mad from Brasero and a medium
is still inserted ?

  xorriso -scsi_log on -outdev /dev/sr0 -toc 2>&1 | tee -i /tmp/xorriso.log

This would give insight into what the drive tells about its status
without the programs-in-the-middle. The log is quite verbose and will
have several hundred lines. Please post /tmp/xorriso.log as attachment
or send it to me by private mail.

(I wonder why udevadm monitor of Testing is so eager to insert blanks
everywhere. But that would be a different bug, if it is not a copy+paste
artefact.)


Have a nice day :)

Thomas

Bug#934297: RFS: bibtexconv

[Thomas Dreibholz]

Hi,

version 1.3.1~test4 closes bug #975076 now. I added the Closes: to the
change that actually fixed the bug (update of the debian/watch file).

If there are no other problems, I could create release 1.3.1.

Den 06.11.2021 23:31, skrev Bastian Germann:
> On 06.11.21 21:30, Thomas Dreibholz wrote:
>> Hi,
>>
>> version test3 makes the following updates:
>>
>>   * changelog is merged, i.e. new entry + all old entries from
>> unstable. In the new entry, all items
>>     from the changes after the latest "unstable" version are merged.
>>   * Installation of examples with dh_installexamples.
>>   * Installation of manpages with dh_installman.
>>   * Updated standards version
>>   * Removed empty test/control
>>   * Removed OpenSSL exception from debian/copyright. BibTeXConv uses
>> LibSSL's MD5 computation
>>     function (from shared library). In addition, it uses (by default)
>> libcurl with OpenSSL (from
>>     shared library).
>>
>> If the changes are okay, I would create an upstream release 1.3.1
>> (i.e. without ~testX), and a new package.
>>
>> Den 04.11.2021 22:54, skrev Bastian Germann:
>>> Control: tags -1 moreinfo
>>>
>>> On Thu, 02 Jan 2020 12:18:40 +0100 Tobias Frost 
>>> wrote:
 - Can you please merge the d/changelog entries for (in Debian)
 unreleased versions?
 - The Debian changelog seems incomplete, I see (packaing) changes
 which
 are not documented. Please also try to expand a bit on the changes,
 e.g
 did the SV update require you add changes? (documenting "why has this
 changed" is important as additional information to the "what")
>>>
>>> These were fixed.
>>>
 - You do not need to specify the standards versions 4th digit, this
 digit is for editorial changes only. So it is sufficient to declare
 compatiblitliy with e.g 4.4.1 (which has been released since you put
 this package to mentors)
 - d/test/control is a empty file. I don't think that is right.

 nitpicks:
 d/compat can be obsoleted. (
 https://nthykier.wordpress.com/2019/01/04/debhelper-compat-12-is-now-released/

 )
>>>
>>> Please correct these.
>>>
>>> - Where do you get the OpenSSL exception from? I know you are the
>>> upstream but this exception should be present in the source as well
>>> or should be removed from d/copyright. Debian does not require it
>>> any longer.
>>>
>>> - Please change the version and the origtarxz to actually match the
>>> released version/file. No ~test0
>>>
>>> - Add "(Closes: #975076)" to d/changelog's "New upstream release."
>>> line.
>>>
>>> With these changes I am going to sponsor the package. Please untag
>>> moreinfo when you are done.
>
> Still I cannot see the changelog closing the bug.

-- 
Best regards / Mit freundlichen Grüßen / Med vennlig hilsen

===
 Thomas Dreibholz

 SimulaMet -- Simula Metropolitan Centre for Digital Engineering
 Centre for Resilient Networks and Applications
 Pilestredet 52
 0167 Oslo, Norway
---
 E-Mail: dre...@simula.no
 Homepage:   http://simula.no/people/dreibh
===




OpenPGP_signature
Description: OpenPGP digital signature