Bug#1022969: [EXTERNAL] Bug#1022969: isc-dhcp-client: dhcp6 client failing to renew the IPv6 address upon T1 expiry.

2022-11-21 Thread Bastian Blank
Hi Souradeep

On Tue, Nov 22, 2022 at 07:44:11AM +, Souradeep Chakrabarti wrote:
> Is there any work around for the time being?

Yes, you replace /sbin/dhclient-script with the file
client/scripts/linux out of the isc-dhcp source.

Bastian

-- 
Bastian Blank
Berater
Telefon: +49 2166 9901-194
E-Mail: bastian.bl...@credativ.de
credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, James Mark McGowan
Unser Umgang mit personenbezogenen Daten unterliegt
folgenden Bestimmungen: https://www.credativ.de/datenschutz



Bug#1022969: [EXTERNAL] Bug#1022969: isc-dhcp-client: dhcp6 client failing to renew the IPv6 address upon T1 expiry.

2022-11-21 Thread Jack Aboutboul
Thanks Bastian for the efforts on this.

Should this be the default behavior?

If so, can we get a package update and image refresh?

Thanks,
Jack

-Original Message-
From: Bastian Blank  
Sent: Tuesday, November 22, 2022 2:52 AM
To: Souradeep Chakrabarti 
Cc: 1022969-qu...@bugs.debian.org; 1022...@bugs.debian.org; 
1022969-submit...@bugs.debian.org; Jack Aboutboul ; 
Anirudh Rayabharam ; Jinank Jain 

Subject: Re: Bug#1022969: [EXTERNAL] Bug#1022969: isc-dhcp-client: dhcp6 client 
failing to renew the IPv6 address upon T1 expiry.

[Some people who received this message don't often get email from 
bastian.bl...@credativ.de. Learn why this is important at 
https://aka.ms/LearnAboutSenderIdentification ]

Hi Souradeep

On Tue, Nov 22, 2022 at 07:44:11AM +, Souradeep Chakrabarti wrote:
> Is there any work around for the time being?

Yes, you replace /sbin/dhclient-script with the file client/scripts/linux out 
of the isc-dhcp source.

Bastian

--
Bastian Blank
Berater
Telefon: +49 2166 9901-194
E-Mail: bastian.bl...@credativ.de
credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209 
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, James Mark McGowan Unser Umgang mit 
personenbezogenen Daten unterliegt folgenden Bestimmungen: 
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.credativ.de%2Fdatenschutz=05%7C01%7Cjaboutboul%40microsoft.com%7C51820d3fe8e94b397db408dacc5e79eb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638047003427902103%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=IMK67PgesfkjoLPVAYqs9Q9S4yAUfrJEB4VYgoVV5O8%3D=0



Bug#365454: lintian: Please check for man pages referring to non-existent info documentation.

2022-11-21 Thread Andrius Merkys

Hello,

On Sun, 30 Apr 2006 09:31:51 +0200 "Piotr Engelking" 
 wrote:

Some man pages contain the following snippet:

This manual page was written for the Debian distribution because the
original program does not have a manual page. Instead, it has
documentation in the GNU Info format; see below.


Only a few packages carry this snippet nowadays [1], but I would like to 
extend this issue a bit and suggest a catch-all solution.


Manpages sometimes contain references to info documentation, especially 
the ones generated by help2man which includes such reference by default. 
Thus it would be nice to detect info documentation references at least 
in help2man-generated manpages and check if they exist. Particularly, 
lintian could search for /^\.B info (\S+)/ and then check for existence 
of /usr/share/info/$1.info.gz among all the binary packages produced 
from the same source.


The same code could as well be reused to locate nonexistent info 
documentation as requested in the original post.


[1] 
https://codesearch.debian.net/search?q=This+manual+page+was+written+for+the+Debian+distribution+because=1


Andrius



Bug#1022969: [EXTERNAL] Bug#1022969: isc-dhcp-client: dhcp6 client failing to renew the IPv6 address upon T1 expiry.

2022-11-21 Thread Souradeep Chakrabarti




> -Original Message-
> From: Bastian Blank 
> Sent: Monday, November 21, 2022 9:23 PM
> To: Souradeep Chakrabarti 
> Cc: 1022969-qu...@bugs.debian.org; 1022...@bugs.debian.org; 1022969-
> submit...@bugs.debian.org; Jack Aboutboul ;
> Anirudh Rayabharam ; Jinank Jain
> 
> Subject: Re: Bug#1022969: [EXTERNAL] Bug#1022969: isc-dhcp-client: dhcp6 
> client
> failing to renew the IPv6 address upon T1 expiry.
> 
> [You don't often get email from bastian.bl...@credativ.de. Learn why this is
> important at https://aka.ms/LearnAboutSenderIdentification ]
> 
> Hi Souradeep
> 
> Thanks.  I found the problem.  It's burried in the unrelated copy of the 
> dhclient-
> script.
> 
> It never set's a lifetime for a renewed address.  So as soon as one expired 
> it will
> never reset the lifetime.
> 
> The upstream script just replaces the complete address entry.
[Souradeep] 
Is there any work around for the time being?

> 
> Bastian
> 
> --
> Bastian Blank
> Berater
> Telefon: +49 2166 9901-194
> E-Mail: bastian.bl...@credativ.de
> credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209
> Trompeterallee 108, 41189 Mönchengladbach
> Geschäftsführung: Dr. Michael Meskes, James Mark McGowan Unser Umgang
> mit personenbezogenen Daten unterliegt folgenden Bestimmungen:
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cr
> edativ.de%2Fdatenschutzdata=05%7C01%7Cschakrabarti%40microsoft.co
> m%7Cb4e026b3a44f4dc38f2c08dacbd88807%7C72f988bf86f141af91ab2d7cd011db
> 47%7C1%7C0%7C638046428185323465%7CUnknown%7CTWFpbGZsb3d8eyJWIjoi
> MC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7
> C%7C%7Csdata=5qrl24QzqX0YHBH%2FnDM1rKVfK6G7rKQaHzTUsteIkFE%3
> Dreserved=0



Bug#1024516: mariadb-10.6: FTBFS on ia64: ha_archive.so: version node not found for symbol lzma_get_progress@@XZ_5.2

2022-11-21 Thread Sebastian Andrzej Siewior
On 2022-11-21 21:39:21 [+0100], John Paul Adrian Glaubitz wrote:
> Hi!
Hi,

> On 11/21/22 00:07, John Paul Adrian Glaubitz wrote:
> > This issue has shown in other packages such as glibc on ia64 [1]:
> > 
> > /usr/bin/ld: 
> > /<>/build-tree/ia64-libc/dlfcn/bug-atexit3-lib.so: version 
> > node not found for symbol lzma_get_progress@@XZ_5.2
> > /usr/bin/ld: failed to set dynamic section sizes: bad value
> > collect2: error: ld returned 1 exit status
> > 
> > So, I don't think it's a regression in mariadb-10.6 itself but rather
> > the toolchain on ia64.
> 
> FWIW, there have been changes to the symbols file of src:xz-utils by 
> Sebastian (CC'ed) which
> might be responsible for this regression on ia64 with liblzma [1].
> 
> I will build a test package on the porterbox yttrium with the changes 
> reverted and see if that
> fixes the problem.

Interesting. So only ia64 is failing here? Everyone else is fine?

> Adrian

Sebastian



Bug#960278: fixed in python-debian 0.1.49

2022-11-21 Thread Niels Thykier

Control: reopen -1

On Sun, 20 Nov 2022 01:06:19 + Debian FTP Masters 
 wrote:

[...]
Changes:
 python-debian (0.1.49) unstable; urgency=medium
 .
   [ Niels Thykier ]
   * Fix whitespace handling of Copyright files (Closes: #960278)
 .

Hi,

I do not see a fix to Copyright files in my name in the 0.1.49 release 
(checking the git log).  I did a draft MR but it was never merged.


Therefore, I am reopening this.

Thanks,
~Niels



Bug#1024613: gcstar: Please upgrade to 1.7.3

2022-11-21 Thread Matthias Urlichs
Package: gcstar
Version: 1.7.1
Severity: normal
X-Debbugs-Cc: sm...@smurf.noris.de

1.7.1 needs a couple of bug fixes.

Also, it still uses perl-gtk2 instead of -gtk3.


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

Kernel: Linux 6.0.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
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 gcstar depends on:
ii  fonts-liberation1:1.07.4-11
ii  libarchive-zip-perl 1.68-1
pn  libgtk2-perl
pn  libmp3-tag-perl 
pn  libogg-vorbis-header-pureperl-perl  
ii  libwww-perl 6.67-1
ii  libxml-parser-perl  2.46-3+b2
pn  libxml-simple-perl  
ii  perl [libarchive-tar-perl]  5.36.0-4

Versions of packages gcstar recommends:
ii  libdatetime-format-strptime-perl  1.7900-1
pn  libgtk2-spell-perl
pn  libmp3-info-perl  
pn  libnet-freedb-perl

gcstar suggests no packages.



Bug#1024547: ITP: sparrow -- Bitcoin wallet with a focus on privacy and usability

2022-11-21 Thread Craig Raw
21 Nov 2022, 19:44 by hartm...@debian.org:

> In the past we've had a bit of trouble with bitcoin wallets in Debian
> when security issues emerged.  If this package makes it into Debian
> stable, will you be able to provide security support for the version in
> stable without upgrading to new upstream versions for the release
> lifetime of stable?
>
Yes - apart from the listed email address in the package, there is also a 
community managed Telegram group at https://t.me/SparrowWallet and of course 
the Github issues page, both linked from the application Help menu. All are 
actively monitored. 

It's worth noting as well that Sparrow hasn't had a security issue in the now 
2+ years since it was first released. It had been the subject of external code 
review and build reproducibility is regularly checked by external parties. 

Craig

Bug#1024612: pastebinit: default level -P seems to be broken: Invalid arguments: option -P requires argument!

2022-11-21 Thread Paul Wise
Package: pastebinit
Version: 1.6.2-1
Severity: normal

The pastebinit -P option seems to now require an argument even though
the option didn't require one before and the docs mention a default.

This seems to be a regression from the version in Debian bullseye.

More details of the error and documentation:

   $ pastebinit -P |& grep -- -P
   Invalid arguments: option -P requires argument!
-P  (default is '1')
   
   $ man pastebinit  | grep -- -P
  -P [private level] (default: 1)
   
   $ pastebinit -P 
   Invalid arguments: option -P requires argument!
   
   pastebinit v1.6.2
   
   Reads on stdin for input or takes a list of files as parameters
   
   Usage:   pastebinit [OPTION...] [FILE...]
   
   General arguments:
   
-b  (default is 'paste.debian.net')
-i 
-l List all supported pastebins
-E Print the content to stdout too
-h Print this help screen
-v Print the version number
-V Print verbose output to stderr
   
   Optional arguments (not supported by all pastebins):
   
-a  (default is 'pabs')
-t  (default is none)
-f  (default is 'text')
-j  (default is '')
-m  (default is none)
-P  (default is '1')
-u  -p 
   
-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
merged-usr: no
Architecture: amd64 (x86_64)

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

Versions of packages pastebinit depends on:
ii  python3 3.10.6-1
ii  python3-distro  1.8.0-1

pastebinit recommends no packages.

pastebinit suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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


Bug#1024611: rocminfo FTCBFS: confused architecture terminology

2022-11-21 Thread Helmut Grohne
Source: rocminfo
Version: 5.2.3-1
Tags: patch upstream
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

rocminfo fails to cross build from source, because it passes invalid
compiler flags. The detection is broken due to confusing architecture
terminologies. The system we are building on is called "build" in Debian
and GNU, but for cmake it is called "host". The system we are building
for is called "host" in Debian and GNU, but for cmake it is empty (it
doesn't have a name). I'm attaching a patch for your convenience and
hope to not leave too much confusion.

Helmut
--- rocminfo-5.2.3.orig/CMakeLists.txt
+++ rocminfo-5.2.3/CMakeLists.txt
@@ -143,7 +143,7 @@
 #
 # Extend the compiler flags for 64-bit builds
 #
-if((${CMAKE_HOST_SYSTEM_PROCESSOR} STREQUAL "x86_64") OR (${CMAKE_HOST_SYSTEM_PROCESSOR} STREQUAL "AMD64"))
+if((${CMAKE_SYSTEM_PROCESSOR} STREQUAL "x86_64") OR (${CMAKE_SYSTEM_PROCESSOR} STREQUAL "AMD64"))
   set(ROCMINFO_CXX_FLAGS ${ROCMINFO_CXX_FLAGS} -msse -msse2)
 endif()
 


Bug#1024610: lintian: fpos runtime-test-file-uses-supported-python-versions-without-test-depends

2022-11-21 Thread Mattia Rizzolo
Package: lintian
Version: 2.115.1

Running on limnoria/2022.11.10, I'm getting:

W: limnoria source: 
runtime-test-file-uses-supported-python-versions-without-test-depends 
py3versions --supported [debian/tests/upstream-tests:14]

d/tests/control looks like this:
|Tests: upstream-tests
|Depends:
| @,
| @builddeps@,
|Restrictions: allow-stderr

And python3-all is part of @builddeps@.

I reckon that lintian is perhaps not expanding @builddeps@ correctly for
this check?

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature


Bug#963025: fixed in firmware-nonfree 20210315-1~exp1

2022-11-21 Thread Salvatore Bonaccorso
Source: firmware-nonfree
Source-Version: 20221012-1
Hi

On Mon, Nov 21, 2022 at 09:43:48PM +, Stefan Pietsch wrote:
> On 08.04.21 11:50, Stefan Pietsch wrote:
> > On 30.03.21 13:35, maximilian attems wrote:
> > > reopen 963025
> > > found -1 20210315-2
> > > tags -1 moreinfo
> > > stop
> > > 
> > > > [18661.586025] CPU: 0 PID: 8408 Comm: hostapd Tainted: G    W   
> > > >   5.10.0-5-amd64 #1 Debian 5.10.24-1
> > > > [18661.586029] Hardware name: LENOVO 20N2007GGE/20N2007GGE, BIOS 
> > > > N2IET81W (1.59 ) 11/29/2019
> > > 
> > > 
> > > Please could you upgrade the BIOS to latest for T490, 1.72 2021/03/17
> > > to exclude this guy fault.
> > 
> > 
> > I upgraded the Lenovo T490 BIOS from 1.59 to 1.72.
> > That did not make any difference.
> 
> 
> I cannot reproduce this with firmware version 46.9d0122c0.0
> 9000-pu-b0-jf-b0-46.ucode from firmware-iwlwifi 20221012-1.  This
> seems to be fixed.

Thanks for testing! The update which includes that firmware verison
was AFAICS 20210716-1~exp1, but will still mark it with the above.

There is as well 20221109-2 in unstable right now, which would migrate
to testing in 2 days (including another update for the
9000-pu-b0-jf-b0-46.ucode to version 46.50fdb42f.0).

Regards,
Salvatore



Bug#1024357: dhcpcd-base: segmentation fault in manager process

2022-11-21 Thread Alexander Inyukhin
I found that the option 51 (lease time) was specified twice inside server reply.



Bug#1023046: zabbix: FTBFS: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)

2022-11-21 Thread Shengjing Zhu
Control: tags -1 + patch

Hi,

On Tue, Nov 22, 2022 at 02:39:34PM +1100, Dmitry Smirnov wrote:
> On Sunday, 20 November 2022 6:22:10 PM AEDT Adrian Bunk wrote:
> > > > golang.org/x/text/unicode/norm
> > > > # golang.org/x/sys/unix
> > > > vendor/golang.org/x/sys/unix/syscall.go:83:16: unsafe.Slice requires
> > > > go1.17 or later (-lang was set to go1.16; check go.mod)
> > > > vendor/golang.org/x/sys/unix/syscall_linux.go:2255:9: unsafe.Slice
> > > > requires go1.17 or later (-lang was set to go1.16; check go.mod)
> > > > vendor/golang.org/x/sys/unix/syscall_unix.go:118:7: unsafe.Slice
> > > > requires go1.17 or later (-lang was set to go1.16; check go.mod)
> > > > vendor/golang.org/x/sys/unix/sysvshm_unix.go:33:7: unsafe.Slice
> > > > requires go1.17 or later (-lang was set to go1.16; check go.mod)
> > > > zabbix.com/pkg/procfs
> > > > # golang.org/x/sys/unix
> > > > vendor/golang.org/x/sys/unix/syscall.go:83:16: unsafe.Slice requires
> > > > go1.17 or later (-lang was set to go1.16; check go.mod)
> > > > vendor/golang.org/x/sys/unix/syscall_linux.go:2255:9: unsafe.Slice
> > > > requires go1.17 or later (-lang was set to go1.16; check go.mod)
> > > > vendor/golang.org/x/sys/unix/syscall_unix.go:118:7: unsafe.Slice
> > > > requires go1.17 or later (-lang was set to go1.16; check go.mod)
> > > > vendor/golang.org/x/sys/unix/sysvshm_unix.go:33:7: unsafe.Slice
> > > > requires go1.17 or later (-lang was set to go1.16; check go.mod)
> > This comes from the new version of golang-golang-x-sys, see also [1].
> > 
> > [1]
> > https://tracker.debian.org/news/1384566/accepted-golang-golang-x-sys-010-1
> > bpo111-source-into-bullseye-backports/
> 
> Unfortunately "golang-golang-x-sys/0.1.0-1" did not fix this FTBFS.
> Maybe it is because it ships "go.mod" ?

I though golang-x-* upstream has a good track of api stablity when I update that
package. But it turns out hmm ...

Please see the attached patch.
>From ff8af531f1493f8e5717f76ccdd26d68e58c527a Mon Sep 17 00:00:00 2001
From: Shengjing Zhu 
Date: Tue, 22 Nov 2022 12:42:11 +0800
Subject: [PATCH] bump go version to 1.17

By running `go mod tidy -go=1.17`

And `go mod vendor`, then sync vendor/modules.txt to topdir.

golang.org/x/sys 0.1.0 uses unsafe.Slice, and this requires go1.17.
See https://github.com/golang/go/issues/46525
---
 src/go/go.mod  | 27 ++---
 src/go/go.sum  | 12 ---
 vendor/modules.txt | 50 +++---
 3 files changed, 58 insertions(+), 31 deletions(-)

diff --git a/src/go/go.mod b/src/go/go.mod
index a49e83b..4b1899a 100644
--- a/src/go/go.mod
+++ b/src/go/go.mod
@@ -1,6 +1,6 @@
 module zabbix.com
 
-go 1.16
+go 1.17
 
 require (
 	git.zabbix.com/ap/plugin-support v0.0.0-20220608100211-35b8bffd7ad0
@@ -15,7 +15,6 @@ require (
 	github.com/go-ole/go-ole v1.2.4
 	github.com/go-sql-driver/mysql v1.5.0
 	github.com/goburrow/modbus v0.1.0
-	github.com/goburrow/serial v0.1.0 // indirect
 	github.com/godbus/dbus v4.1.0+incompatible
 	github.com/godror/godror v0.20.1
 	github.com/jackc/pgx/v4 v4.8.2-0.20200910143026-040df1ccef85
@@ -25,8 +24,30 @@ require (
 	github.com/miekg/dns v1.1.43
 	github.com/natefinch/npipe v0.0.0-20160621034901-c1b8fa8bdcce
 	github.com/omeid/go-yarn v0.0.1
-	github.com/pkg/errors v0.9.1 // indirect
 	golang.org/x/sys v0.0.0-20220310020820-b874c991c1a5
+)
+
+require (
+	github.com/chromedp/sysutil v1.0.0 // indirect
+	github.com/go-logfmt/logfmt v0.5.0 // indirect
+	github.com/goburrow/serial v0.1.0 // indirect
+	github.com/gobwas/httphead v0.1.0 // indirect
+	github.com/gobwas/pool v0.2.1 // indirect
+	github.com/gobwas/ws v1.0.4 // indirect
+	github.com/jackc/chunkreader/v2 v2.0.1 // indirect
+	github.com/jackc/pgconn v1.6.5-0.20200905181414-0d4f029683fc // indirect
+	github.com/jackc/pgio v1.0.0 // indirect
+	github.com/jackc/pgpassfile v1.0.0 // indirect
+	github.com/jackc/pgproto3/v2 v2.0.4 // indirect
+	github.com/jackc/pgservicefile v0.0.0-20200714003250-2b9c44734f2b // indirect
+	github.com/jackc/pgtype v1.4.3-0.20200905161353-e7d2b057a716 // indirect
+	github.com/jackc/puddle v1.1.2-0.20200821025810-91d0159cc97a // indirect
+	github.com/josharian/intern v1.0.0 // indirect
+	github.com/mailru/easyjson v0.7.6 // indirect
+	github.com/pkg/errors v0.9.1 // indirect
+	golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 // indirect
+	golang.org/x/net v0.0.0-20210226172049-e18ecbb05110 // indirect
+	golang.org/x/text v0.3.3 // indirect
 	golang.org/x/xerrors v0.0.0-20200804184101-5ec99f83aff1 // indirect
 	gopkg.in/asn1-ber.v1 v1.0.0-20181015200546-f715ec2f112d // indirect
 	gopkg.in/yaml.v2 v2.2.8 // indirect
diff --git a/src/go/go.sum b/src/go/go.sum
index 52f1940..717a47f 100644
--- a/src/go/go.sum
+++ b/src/go/go.sum
@@ -1,17 +1,5 @@
-git.zabbix.com/ap/plugin-support v0.0.0-20220524072909-7233a93fe116 h1:IGbQPDh/U7UHSM0M4h2k/wdRjyO3zG8uq4Dx+gej4y8=
-git.zabbix.com/ap/plugin-support v0.0.0-20220524072909-7233a93fe116/go.mod 

Bug#1024609: ITS: n2n

2022-11-21 Thread Tianyu Chen
Package: n2n
Source: n2n
Severity: important
X-Debbugs-Cc: billchenchina2...@gmail.com, m...@qa.debian.org, 
f...@rolf.leggewie.biz, f...@leggewie.org

Hi,

It seems that n2n is still lagging behind upstream, and there're several bugs
that didn't got well-responded. #914321 reported upstream version 2.4 and
#1024139 reported upstream version 3.1.1. I also discussed with folks on
#debian-devel, #debian-qa, and mia team, due to current n2n maintainer stopped
working on Debian several years ago, I'm here willing to take over n2n's
maintenance according to developers-reference.

https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-
salvaging

I'd like to upload n2n 3.1.1, and continue maintaining n2n with its future
versions. I've started a nmu several days ago, the current work is available at
salsa and mentors.d.n.

Current working repo: https://salsa.debian.org/billchenchina/n2n.git
mentors.d.n link: https://mentors.debian.net/package/n2n/

Thanks!

Tianyu Chen


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

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



Bug#874207: geckodriver: please enable

2022-11-21 Thread Mike Hommey
tag 874207 + wontfix
tag 989455 + wontfix
thanks

On Mon, Sep 04, 2017 at 11:02:06AM +0200, Matthias Urlichs wrote:
> Package: firefox
> Version: 54.0-2
> Severity: normal
> 
> Firefox does not work with python{,3}-selenium because you don't build the
> "geckodriver" executable.
> 
> The end of testing/geckodriver/README.md states:
> 
> geckodriver is built in the Firefox CI by default but not if you build
> Firefox locally. To enable building of geckodriver locally, ensure you
> put this in your mozconfig:
> 
> ac_add_options --enable-geckodriver
> 
> The geckodriver binary will appear in ${objdir}/dist/bin/geckodriver 
> alongside firefox-bin.
> 
> Please enable and install it so that Firefox may be used with Selenium.

It would be better to package it standalone. Nowadays, it is available
on crates.io.

Mike



Bug#1024607: Passing audio from virtual machine to host via PulseAudio

2022-11-21 Thread Michael Tokarev

22.11.2022 07:24, yin...@tutanota.com wrote:

Package: qemu-system-x86
Version: 1:5.2+dfsg-11+deb11u2

===Error message===
Error changing VM configuration: unsupported configuration: unknown audio type 
'pulseaudio'

===Steps to reproduce===
1) Create a VM.
2) Remove the default sound card.
3) Edit VM config to use the following anywhere in :


  
  



I thought setting it to 'pa' would work but it didn't. I tried 'pulseaudio', 
'pulse', and 'pa'. Neither worked.


I was about to help you but decided to let you deal with this one.
Instead of trying various stuff which is not documented to work
(hint: there's just one name for the pulseaudio driver in qemu).


RHEL(I  used AlmaLinux 9) has a separate package named "qemu-kvm-audio-pa". I 
installed it and tried to make a VM and it works there but not under Debian. This problem 
seems to be Debian specific.


Here's a hint for you.

/mjt



Bug#1024608: RFS: n2n/3.1.1-0.1 [NMU] -- Peer-to-Peer VPN network daemon

2022-11-21 Thread Tianyu Chen
Package: sponsorship-requests
Severity: normal
X-Debbugs-Cc: billchenchina2...@gmail.com

Dear mentors,

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

 * Package name : n2n
   Version  : 3.1.1-0.1
   Upstream contact : Luca Deri 
 * URL  : http://www.ntop.org/products/n2n/
 * License  : Expat, __AUTO_PERMISSIVE__, GPL-3.0+
 * Vcs  : https://github.com/leggewie-DM/n2n
   Section  : net

Though "n2n" is already in debian, but it's already behind upstream(See #914321
and #1024139). I'm uploading a NMU for that.

The source builds the following binary packages:

  n2n - Peer-to-Peer VPN network daemon

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

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

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

  dget -x https://mentors.debian.net/debian/pool/main/n/n2n/n2n_3.1.1-0.1.dsc

Changes since the last upload:

 n2n (3.1.1-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version 3.1.1. (Closes: #914321, #1024139)

Regards,
--
  Tianyu Chen



Bug#1024607: Passing audio from virtual machine to host via PulseAudio

2022-11-21 Thread yin846
Package: qemu-system-x86
Version: 1:5.2+dfsg-11+deb11u2

===Error message===
Error changing VM configuration: unsupported configuration: unknown audio type 
'pulseaudio'

===Steps to reproduce===
1) Create a VM.
2) Remove the default sound card.
3) Edit VM config to use the following anywhere in :


 
 



I thought setting it to 'pa' would work but it didn't. I tried 'pulseaudio', 
'pulse', and 'pa'. Neither worked.

I was using this article as a general guide. (Section 8.2: Passing audio from 
virtual machine to host via PulseAudio)

https://wiki.archlinux.org/title/PCI_passthrough_via_OVMF#Passing_audio_from_virtual_machine_to_host_via_PulseAudio

==Additional information==

$ qemu-system-x86_64 -audio-help
Environment variable based configuration deprecated.
Please use the new -audiodev option.

Equivalent -audiodev to your current environment variables:
(Since you didn't specify QEMU_AUDIO_DRV, I'll list all possibilities)
-audiodev id=pa,driver=pa
-audiodev id=alsa,driver=alsa
-audiodev id=oss,driver=oss
-audiodev id=none,driver=none

$ ls /usr/lib/x86_64-linux-gnu/qemu/audio-pa.so
/usr/lib/x86_64-linux-gnu/qemu/audio-pa.so

$ neofetch --stdout
user@desktop
-
OS: Debian GNU/Linux 11 (bullseye) x86_64
Host: Z390 UD
Kernel: 5.10.0-19-amd64
Uptime: 2 hours, 36 mins
Packages: 2519 (dpkg)
Shell: bash 5.1.4
Resolution: 1920x1080
DE: Xfce 4.16
WM: Xfwm4
WM Theme: Default
Theme: Adwaita-dark [GTK2/3]
Icons: Tango [GTK2/3]
Terminal: xfce4-terminal
Terminal Font: Monospace Semi-Condensed 12
CPU: Intel i3-9100 (4) @ 4.200GHz
GPU: Intel CoffeeLake-S GT2 [UHD Graphics 630]
GPU: AMD ATI Radeon R9 285/380
Memory: 2171MiB / 15748MiB

RHEL(I  used AlmaLinux 9) has a separate package named "qemu-kvm-audio-pa". I 
installed it and tried to make a VM and it works there but not under Debian. 
This problem seems to be Debian specific.



Bug#1024606: ognibuild: New upstream version 0.0.15

2022-11-21 Thread Tianyu Chen
Package: ognibuild
Version: 0.0.13-1
Severity: wishlist
Tags: patch
X-Debbugs-Cc: billchenchina2...@gmail.com

Hi,

ognibuild has new upstream version 0.0.15. debianize reports
`ModuleNotFoundError: No module named 'ognibuild.upstream'` with current
0.0.13-1.

I've opened a MR on salsa.

https://salsa.debian.org/jelmer/ognibuild/-/merge_requests/3


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

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

Versions of packages ognibuild depends on:
ii  python3  3.10.6-3
ii  python3-apt  2.3.0+nmu1+b1
ii  python3-breezy   3.3.0+bzr7661-5
ii  python3-buildlog-consultant  0.0.21-1
ii  python3-lz4  4.0.2+dfsg-1+b1
ii  python3-requirement-parser   0.2.0-1.1
ii  python3-toml 0.10.2-1

Versions of packages ognibuild recommends:
ii  brz-debian 2.8.74
ii  python3-debmutate  0.62

ognibuild suggests no packages.

-- no debconf information



Bug#1020595: Tests FTBFS on arm64

2022-11-21 Thread Ben Westover
Hello,

All of the tests fail when building on arm64. Here is an example:

In file included from ../tests/conformance_burntsushi_invalid.cpp:8:
../tests/tests.h:15:2: error: #error TOML_FP16 was not deduced correctly
15 | #error TOML_FP16 was not deduced correctly
   |  ^

A full log is attached. Build with nocheck profile is fine.

Thanks,
--
Ben Westover
sbuild (Debian sbuild) 0.84.1 (15 November 2022) on debian

+==+
| tomlplusplus 3.2.0+ds-1 (arm64)  Tue, 22 Nov 2022 04:00:13 + |
+==+

Package: tomlplusplus
Version: 3.2.0+ds-1
Source Version: 3.2.0+ds-1
Distribution: unstable
Machine Architecture: arm64
Host Architecture: arm64
Build Architecture: arm64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-arm64-sbuild-8411e09e-0601-4c26-a03f-a7fc09a641fb'
 with '<>'
I: NOTICE: Log filtering will replace 
'build/tomlplusplus-gUfSxV/resolver-mI45Yl' with '<>'

+--+
| Update chroot|
+--+

Hit:1 http://localhost:3142/deb.debian.org/debian unstable InRelease
Get:2 http://localhost:3142/deb.debian.org/debian unstable/main Sources [10.0 
MB]
Fetched 10.0 MB in 3s (3038 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

+--+
| Fetch source files   |
+--+


Local sources
-

/home/ben/tomlplusplus_3.2.0+ds-1.dsc exists in /home/ben; copying to chroot
I: NOTICE: Log filtering will replace 
'build/tomlplusplus-gUfSxV/tomlplusplus-3.2.0+ds' with '<>'
I: NOTICE: Log filtering will replace 'build/tomlplusplus-gUfSxV' with 
'<>'

+--+
| Install package build dependencies   |
+--+


Setup apt archive
-

Merged Build-Depends: debhelper-compat (= 13), build-essential, fakeroot, 
catch2, cmake, cmark-gfm, locales-all, meson (>= 0.54.0), nlohmann-json3-dev, 
pkg-config
Filtered Build-Depends: debhelper-compat (= 13), build-essential, fakeroot, 
catch2, cmake, cmark-gfm, locales-all, meson (>= 0.54.0), nlohmann-json3-dev, 
pkg-config
dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
'/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
Ign:1 copy:/<>/apt_archive ./ InRelease
Get:2 copy:/<>/apt_archive ./ Release [580 B]
Ign:3 copy:/<>/apt_archive ./ Release.gpg
Get:4 copy:/<>/apt_archive ./ Sources [775 B]
Get:5 copy:/<>/apt_archive ./ Packages [739 B]
Fetched 2094 B in 0s (0 B/s)
Reading package lists...
Reading package lists...

Install main build dependencies (apt-based resolver)


Installing build dependencies
Reading package lists...
Building dependency tree...
The following additional packages will be installed:
  autoconf automake autopoint autotools-dev bsdextrautils catch2 cmake
  cmake-data cmark-gfm debhelper dh-autoreconf dh-elpa-helper
  dh-strip-nondeterminism dwz emacsen-common file gettext gettext-base
  groff-base intltool-debian libarchive-zip-perl libarchive13 libbrotli1
  libc-l10n libcmark-gfm-extensions0.29.0.gfm.6 libcmark-gfm0.29.0.gfm.6
  libcurl4 libdebhelper-perl libelf1 libexpat1
  libfile-stripnondeterminism-perl libicu72 libjsoncpp25 libldap-2.5-0
  libmagic-mgc libmagic1 libmpdec3 libncurses6 libncursesw6 libnghttp2-14
  libpipeline1 libpkgconf3 libprocps8 libpsl5 libpython3-stdlib
  libpython3.10-minimal libpython3.10-stdlib libreadline8 librhash0 librtmp1
  libsasl2-2 libsasl2-modules-db libsqlite3-0 libssh2-1 libsub-override-perl
  libtool libuchardet0 libuv1 libxml2 locales-all m4 man-db media-types meson
  ninja-build nlohmann-json3-dev pkg-config pkgconf pkgconf-bin po-debconf
  procps python3 python3-distutils python3-lib2to3 python3-minimal
  python3-pkg-resources python3-setuptools python3.10 python3.10-minimal
  readline-common sensible-utils
Suggested packages:
  autoconf-archive gnu-standards autoconf-doc cmake-doc cmake-format dh-make
  gettext-doc libasprintf-dev libgettextpo-dev groff lrzip libtool-doc
  gfortran | fortran95-compiler gcj-jdk m4-doc apparmor less www-browser
  libmail-box-perl python3-doc python3-tk python3-venv python-setuptools-doc
  python3.10-venv python3.10-doc binfmt-support readline-doc
Recommended packages:
  curl | wget | 

Bug#1023046: zabbix: FTBFS: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)

2022-11-21 Thread Dmitry Smirnov
On Sunday, 20 November 2022 6:22:10 PM AEDT Adrian Bunk wrote:
> > > golang.org/x/text/unicode/norm
> > > # golang.org/x/sys/unix
> > > vendor/golang.org/x/sys/unix/syscall.go:83:16: unsafe.Slice requires
> > > go1.17 or later (-lang was set to go1.16; check go.mod)
> > > vendor/golang.org/x/sys/unix/syscall_linux.go:2255:9: unsafe.Slice
> > > requires go1.17 or later (-lang was set to go1.16; check go.mod)
> > > vendor/golang.org/x/sys/unix/syscall_unix.go:118:7: unsafe.Slice
> > > requires go1.17 or later (-lang was set to go1.16; check go.mod)
> > > vendor/golang.org/x/sys/unix/sysvshm_unix.go:33:7: unsafe.Slice
> > > requires go1.17 or later (-lang was set to go1.16; check go.mod)
> > > zabbix.com/pkg/procfs
> > > # golang.org/x/sys/unix
> > > vendor/golang.org/x/sys/unix/syscall.go:83:16: unsafe.Slice requires
> > > go1.17 or later (-lang was set to go1.16; check go.mod)
> > > vendor/golang.org/x/sys/unix/syscall_linux.go:2255:9: unsafe.Slice
> > > requires go1.17 or later (-lang was set to go1.16; check go.mod)
> > > vendor/golang.org/x/sys/unix/syscall_unix.go:118:7: unsafe.Slice
> > > requires go1.17 or later (-lang was set to go1.16; check go.mod)
> > > vendor/golang.org/x/sys/unix/sysvshm_unix.go:33:7: unsafe.Slice
> > > requires go1.17 or later (-lang was set to go1.16; check go.mod)
> This comes from the new version of golang-golang-x-sys, see also [1].
> 
> [1]
> https://tracker.debian.org/news/1384566/accepted-golang-golang-x-sys-010-1
> bpo111-source-into-bullseye-backports/

Unfortunately "golang-golang-x-sys/0.1.0-1" did not fix this FTBFS.
Maybe it is because it ships "go.mod" ?

-- 
Best wishes,
 Dmitry Smirnov
 GPG key : 4096R/52B6BBD953968D1B

---

Without doubt you are not sane.
 -- Tage Danielsson

---

COVID-19: The Trouble With PCR Tests
https://swprs.org/the-trouble-with-pcr-tests/


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


Bug#1024535: 'GtkSettings' has no property named 'gtk-overlay-scrolling'

2022-11-21 Thread Ángel
On 2022-11-21 at 09:29 +, Alberto Garcia wrote:
> On Mon, Nov 21, 2022 at 03:38:37AM +0100, Ángel wrote:
> 
> > After the recent update of webkit2gtk in buster-security, running
> > evolution, geary, devhelp (or any other program using wbkit2gtk, i
> > guess) from a console it is continuously filled by lines like
> > 
> > (WebKitWebProcess:): GLib-GObject-WARNING **: :
> > g_object_get_is_valid_property: object class 'GtkSettings' has no
> > property named 'gtk-overlay-scrolling'
> 
> Does 'export GTK_OVERLAY_SCROLLING=0' solve the problem?
> 
> Berto

Hello Alberto

Yes, it does! It actually doesn't completely remove them, but are now
only a few (one warning per webkit2gtk object, I think), which is
something I can live with. I thought I would need to end up recompiling
webkit2gtk.

Thanks so much



Bug#1024605: nginx: NULL deref in HTTP SSI module cause worker crash SEGV

2022-11-21 Thread Ciel Zhao
Package: nginx
Version: 1.22.1-1
Severity: normal
Tags: patch upstream
X-Debbugs-Cc: deb...@ciel.dev

When a subrequest has SSI enabled but its main request does not, the SSI module
may crash the worker due to NULL-pointer dereference.

This bug has been reported since 2017 to NGINX, and a patch is just accepted by
the upstream.

See:

Patch: https://hg.nginx.org/nginx/rev/49e7db44b57c
Issue Trac: https://trac.nginx.org/nginx/ticket/1263
Maillist: 
https://mailman.nginx.org/archives/list/nginx-de...@nginx.org/thread/E2HSRDHFSDWXVJ464B2GQD7PEDQ5AVMI/


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

Kernel: Linux 5.15.64-1-pve (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nginx depends on:
ii  nginx-core  1.22.1-1

nginx recommends no packages.

nginx suggests no packages.

-- no debconf information



Bug#1024450: ITP: setuptools-gettext -- Compile .po files into .mo files

2022-11-21 Thread Jelmer Vernooij
Hi Roland,

On Mon, Nov 21, 2022 at 09:19:41PM +0100, Roland Clobus wrote:
> On 19/11/2022 18:20, Jelmer Vernooij wrote:
> > Package: wnpp
> > Severity: wishlist
> > Owner: Jelmer Vernooij 
> > X-Debbugs-Cc: debian-de...@lists.debian.org
> > 
> > * Package name: setuptools-gettext
> >Version : 0.0.1
> >Upstream Author : Breezy Team 
> > * URL : https://github.com/jelmer/setuptools-gettext
> > * License : GPL
> >Programming Lang: Python
> >Description : Compile .po files into .mo files
> > 
> > This extension for setuptools compiles gettext .po files
> > found in the source directory into .mo files and installs them.
> 
> How does this tool differ from 'msgfmt' from 'gettext'?

It's a wrapper around msgfmt, but making it convenient to run from setuptools.
I'll clarify that in the final description.

Jelmer



Bug#1024604: konsole: dose not show combining characters right

2022-11-21 Thread Mr. T

On 22.11.22 02:27, Mr. T wrote:

see attatched screenshots and text file


here are those missing screenshots, attaching files on the terminal is 
not so easy when send is the default thing to do instead


PS: see also Bug No. 1024603


Bug#1024444: spamd: systemd hardening flags prevents bayes access to per-user dirs

2022-11-21 Thread Michael Welsh Duggan
Noah Meyerhans  writes:

> Control: tags -1 + moreinfo
>
> On Sat, Nov 19, 2022 at 10:23:12AM -0500, Michael Welsh Duggan wrote:
>> The addition of the
>> 
>>   ProtectSystem=full
>> 
>> clause to the spamd service module prevents spamd from writing to user
>> bayes files.  Here is a log from spamd:
>
> Hi Michael.  Per the systemd documentation on the ProtectSystem setting:
>
> Takes a boolean argument or the special values "full" or
> "strict". If true, mounts the /usr/ and the boot loader
> directories (/boot and /efi) read-only for processes invoked by
> this unit. If set to "full", the /etc/ directory is mounted
> read-only, too.
>
> Access to /home is not restricted by this setting.  Is /home on your
> system a symlink or otherwise not actually located at /home?

Ah, all becomes clear.  The system that I eventually converted over to
my mail server (over 12 years old) symlinked /home to /usr/local/home.
This is because / was on a fairly small SSD and /usr was on spinning
disk.  I had managed to forget that and overlook what it meant in the
context of the ProtectSystem setting.  As such, I now think that my
system deviates enough from the norm that the fact that I have to make
manual adjustments to the systemd unit is only fair.  Thanks for looking
into this.

-- 
Michael Welsh Duggan
(m...@md5i.com)



Bug#1024604: konsole: dose not show combining characters right

2022-11-21 Thread Mr. T
Package: konsole
Version: 4:20.12.3-1
Severity: important
X-Debbugs-Cc: t...@treaki.tk

Dear Maintainer,


   * What led up to the situation?
trying about whith german Umlauten encoded with combining characters
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
i created a textfile that displays right in firefox, libreoffice and
xterm, but wrong in gnome-terminal, gedit and konsole
   * What was the outcome of this action?
i was confused on what software implements it right which wrong
(guessing firefox, soffice and xterm doing it right but your modern
open source stuff wrong, but am not sure)
   * What outcome did you expect instead?
that all software would display it the same

see attatched screenshots and text file

thanks for looking in to this and hopefully fixing it

PS: see also bug regarding gome-terminal with same issue

-- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages konsole depends on:
ii  kio5.78.0-5
ii  konsole-kpart  4:20.12.3-1
ii  libc6  2.31-13+deb11u5
ii  libkf5configcore5  5.78.0-4
ii  libkf5configwidgets5   5.78.0-2
ii  libkf5coreaddons5  5.78.0-4
ii  libkf5crash5   5.78.0-3
ii  libkf5dbusaddons5  5.78.0-2
ii  libkf5globalaccel-bin  5.78.0-3
ii  libkf5globalaccel5 5.78.0-3
ii  libkf5i18n55.78.0-2
ii  libkf5iconthemes5  5.78.0-2
ii  libkf5kiowidgets5  5.78.0-5
ii  libkf5notifyconfig55.78.0-2
ii  libkf5widgetsaddons5   5.78.0-2
ii  libkf5windowsystem55.78.0-2
ii  libkf5xmlgui5  5.78.0-2
ii  libqt5core5a   5.15.2+dfsg-9
ii  libqt5gui5 5.15.2+dfsg-9
ii  libqt5widgets5 5.15.2+dfsg-9
ii  libstdc++6 10.2.1-6

konsole recommends no packages.

Versions of packages konsole suggests:
pn  lrzsz  

-- no debconf information
das hält mich nicht auf
doch das hier hält mich immer auf


Bug#1024603: gnome-terminal: dose not show combining characters right

2022-11-21 Thread Mr. T
Package: gnome-terminal
Version: 3.38.3-1
Severity: important
X-Debbugs-Cc: t...@treaki.tk

Dear Maintainer,


   * What led up to the situation?
trying about whith german Umlauten encoded with combining characters
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
i created a textfile that displays right in firefox, libreoffice and
xterm, but wrong in gnome-terminal, gedit and konsole
   * What was the outcome of this action?
i was confused on what software implements it right which wrong
(guessing firefox, soffice and xterm doing it right but your modern
open source stuff wrong, but am not sure)
   * What outcome did you expect instead?
that all software would display it the same

see attatched screenshots and text file

thanks for looking in to this and hopefully fixing it

-- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages gnome-terminal depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.24-0+deb11u1
ii  dbus-x11 [dbus-session-bus]   1.12.24-0+deb11u1
ii  dconf-gsettings-backend [gsettings-backend]   0.38.0-2
ii  gnome-terminal-data   3.38.3-1
ii  gsettings-desktop-schemas 3.38.0-2
ii  libatk1.0-0   2.36.0-2
ii  libc6 2.31-13+deb11u5
ii  libdconf1 0.38.0-2
ii  libglib2.0-0  2.66.8-1
ii  libgtk-3-03.24.24-4+deb11u2
ii  libpango-1.0-01.46.2-3
ii  libuuid1  2.36.1-8+deb11u1
ii  libvte-2.91-0 0.62.3-1
ii  libx11-6  2:1.7.2-1

Versions of packages gnome-terminal recommends:
ii  gvfs   1.46.2-1
ii  nautilus-extension-gnome-terminal  3.38.3-1
ii  yelp   3.38.3-1

gnome-terminal suggests no packages.

-- no debconf information
das hält mich nicht auf
doch das hier hält mich immer auf


Bug#616604: ONLINE NOTIFICATION

2022-11-21 Thread Barouat Saida
https://bit.ly/3tL9bZv



Bug#21941: ONLINE NOTIFICATION

2022-11-21 Thread PLS Tech
https://bit.ly/3tO993c



Bug#989874: (no subject)

2022-11-21 Thread Mr. T
any idea of which package i have to install in addition so that i get 
some nice icons instead of this bulky text?




Bug#1024602: bash: inaccurate copyright file

2022-11-21 Thread Bastian Germann

Source: bash
Version: 5.2-2
Severity: serious
Tags: patch

The bash package's copyright file is inaccurate.

It includes the Bash exemption that refers to GPL-2 while Bash was relicensed 
to GPL-3 and lost that exemption.

bashref.texi does not have the following as part of its license (anymore?):
"Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice
are preserved on all copies."

The Bison exception is missing.

GPL-2+ is missing.

I have attached a machine-readable copyright file that solves these issues.

More features of the attached copyright file:
Files-Excluded for automatic repacking with #1024598 taken into account.
BSD-4-clause's advertisement clause is removed per allowance of the University 
of Berkeley.
doc/FAQ's non-free license is removed.
You should also remove the file debian/FAQ because the FAQ is not maintained 
anymore upstream.

The copyright and licenses of the embedded fonts of the non-source files in the 
doc directory are not included.
You should instead get rid of them and build them from source if needed.Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Contact: c...@po.cwru.edu
Comment:
 This is Debian GNU/Linux's prepackaged version of the FSF's GNU Bash,
 the Bourne Again SHell.
 .
 This package was put together by Matthias Klose .
Source:
 ftp.gnu.org:/pub/gnu/bash
Files-Excluded:
 doc/FAQ
 doc/aosa-bash*.pdf
 doc/article.*
 doc/rose94.*

Files: *
Copyright: (C) 1987-2022 Free Software Foundation, Inc.
License: GPL-3+

Files: examples/shellmath/*
Copyright: (c) 2020 by Michael Wood. All rights reserved.
License: GPL-3+

Files: support/bash.xbm
Copyright: (C) 1992 Simon Marshall
License: GPL-3+

Files: support/checkbashisms
Copyright:
 Copyright (C) 1998 Richard Braakman
 Copyright (C) 2002 Josip Rodin
 Copyright (C) 2003 Julian Gilbey
License: GPL-3+

Files:
 tests/ifs-posix.tests
 tests/posix2.tests
Copyright: (C) 2005 Glen Fowler
 Copyright (c) 1995 Stephen Gildea
License: GPL-3+

License: GPL-3+
 Bash is free software; you can redistribute it and/or modify it under
 the terms of the GNU General Public License as published by the Free
 Software Foundation; either version 3, or (at your option) any later
 version.
 .
 Bash is distributed in the hope that it will be useful, but WITHOUT
 ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
 FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
 for more details.
 .
 You should have received a copy of the GNU General Public License
 along with Bash.  If not, see .
Comment:
 On Debian systems, the complete text of the GNU General Public License
 version 3 can be found in `/usr/share/common-licenses/GPL-3'.

Files: y.tab.*
Copyright: (C) 1984, 1989-1990, 2000-2015, 2018-2021 Free Software Foundation,
   Inc.
License: GPL-3+ with Bison exception
   This program is free software: you can redistribute it and/or modify
   it under the terms of the GNU General Public License as published by
   the Free Software Foundation, either version 3 of the License, or
   (at your option) any later version.
 .
   This program is distributed in the hope that it will be useful,
   but WITHOUT ANY WARRANTY; without even the implied warranty of
   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
   GNU General Public License for more details.
 .
   You should have received a copy of the GNU General Public License
   along with this program.  If not, see .
 .
   As a special exception, you may create a larger work that contains
   part or all of the Bison parser skeleton and distribute that work
   under terms of your choice, so long as that work isn't itself a
   parser generator using the skeleton or a modified version thereof
   as a parser skeleton.  Alternatively, if you modify or redistribute
   the parser skeleton itself, you may (at your option) remove this
   special exception, which will cause the skeleton and the resulting
   Bison output files to be licensed under the GNU General Public
   License without this special exception.
 .
   This special exception was added by the Free Software Foundation in
   version 2.2 of Bison.
Comment:
 On Debian systems, the complete text of the GNU General Public License
 version 3 can be found in `/usr/share/common-licenses/GPL-3'.

Files:
 examples/functions/array-stuff
 examples/functions/fstty
 examples/functions/func
 examples/functions/inetaddr
 examples/functions/isnum2
 examples/functions/ksh*
 examples/functions/notify.bash
 examples/functions/seq*
 examples/functions/sort-pos-params
 examples/functions/substr*
 examples/functions/substr2
 examples/functions/w*
 tests/complete.tests
Copyright: 1992-2020 Chester Ramey
License: GPL-2+

Files:
 debian/clear_console.c
 examples/complete/bash_completion
Copyright:
 Copyright (C) 2006-2019 Canonical Ltd.
 Copyright (C) Ian Macdonald 

Bug#1023767: neomutt: unable to find gpgme-config

2022-11-21 Thread Daniel Kahn Gillmor
Control: tags 1023767 + patch

On Wed 2022-11-09 22:04:00 +0100, Timo Röhling wrote:
> neomutt fails to build with the recent libgpgme-dev update that dropped
> the gpgme-config executable.
>
> https://github.com/neomutt/neomutt/pull/3555 fixes the problem, but does
> not apply cleanly to the neomutt release in Debian, unfortunately.

The attached patch appears to fix things for me so that neomutt builds
successfully against libgpgme-dev 1.18.0-3, though i don't know enough
about how to adequately test neomutt to be confident in the results (i
don't use neomutt myself).

It's also on salsa at
https://salsa.debian.org/mutt-team/neomutt/-/merge_requests/8 if that's
useful.

Please let me know if you'd like me to NMU it.

   --dkg

From a9d3c0fe8c8e678311ad7a4810df6db519abc798 Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor 
Date: Mon, 21 Nov 2022 19:10:20 -0500
Subject: [PATCH] find modern versions of gpgme (Closes: #1023767)

---
 debian/patches/series |   1 +
 .../upstream/Use-pkgconf-to-find-GPGMe.patch  | 121 ++
 2 files changed, 122 insertions(+)
 create mode 100644 debian/patches/upstream/Use-pkgconf-to-find-GPGMe.patch

diff --git a/debian/patches/series b/debian/patches/series
index 8c37cf1cc..b0cb4f4fc 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -6,3 +6,4 @@ upstream/964416-manpages-fixes.patch
 upstream/1020414-gsasl-support-prereq.patch
 upstream/1020414-gsasl-support.patch
 upstream/use-pkgconfig-for-libgpg-error.patch
+upstream/Use-pkgconf-to-find-GPGMe.patch
diff --git a/debian/patches/upstream/Use-pkgconf-to-find-GPGMe.patch b/debian/patches/upstream/Use-pkgconf-to-find-GPGMe.patch
new file mode 100644
index 0..f4c583cdb
--- /dev/null
+++ b/debian/patches/upstream/Use-pkgconf-to-find-GPGMe.patch
@@ -0,0 +1,121 @@
+From: Pietro Cerutti 
+Date: Mon, 7 Nov 2022 08:41:07 +
+Subject: Use pkgconf to find GPGMe
+
+(cherry-picked from upstream 516568f3f0769fad1c006a6b3a70884e97092a2a)
+---
+ Makefile.autosetup |  2 +-
+ auto.def   | 85 --
+ 2 files changed, 6 insertions(+), 81 deletions(-)
+
+diff --git a/Makefile.autosetup b/Makefile.autosetup
+index 3884704..24a2f17 100644
+--- a/Makefile.autosetup
 b/Makefile.autosetup
+@@ -572,7 +572,7 @@ $(PWD)/mutt:
+ LIBNCRYPT=	libncrypt.a
+ LIBNCRYPTOBJS=	ncrypt/config.o ncrypt/crypt.o ncrypt/cryptglue.o \
+ 		ncrypt/crypt_mod.o
+-@if HAVE_GPGME
++@if HAVE_PKG_GPGME
+ LIBNCRYPTOBJS+=	ncrypt/crypt_gpgme.o ncrypt/dlg_gpgme.o \
+ 		ncrypt/crypt_mod_pgp_gpgme.o ncrypt/crypt_mod_smime_gpgme.o
+ @endif
+diff --git a/auto.def b/auto.def
+index 12dc5d3..e0dcbb5 100644
+--- a/auto.def
 b/auto.def
+@@ -480,88 +480,13 @@ if {[get-define want-gpgme]} {
+ define-append CFLAGS -D_FILE_OFFSET_BITS=[get-define _FILE_OFFSET_BITS]
+   }
+ 
+-  msg-checking "Checking for GPGME..."
+-  if {1} {
+-# Locate gpgme-config
+-set gpgme_prefix [opt-val with-gpgme $prefix]
+-set gpgme_config_guess [file join $gpgme_prefix bin gpgme-config]
+-if {[file-isexec $gpgme_config_guess]} {
+-  define GPGME-CONFIG $gpgme_config_guess
+-} else {
+-  if {![cc-check-progs gpgme-config]} {
+-user-error "Unable to find gpgme-config"
+-  }
+-}
+-set gpgme_config [get-define GPGME-CONFIG]
+-
+-# Version
+-if {[catch {exec-with-stderr $gpgme_config --version} gpgme_version err]} {
+-  user-error "Could not derive --version from $gpgme_config"
+-}
+-if {[scan $gpgme_version "%d.%d.%d" gpgme_maj gpgme_min gpgme_patch] != 3} {
+-  user-error "Could not parse GPGME version $gpgme_version"
+-}
+-msg-result $gpgme_version
+-if {[get-define want-autocrypt]} {
+-  if {$gpgme_maj < 1 || $gpgme_min < 8} {
+-user-error "Found GPGME version $gpgme_version, need 1.8.0 for AutoCrypt"
+-  }
+-} else {
+-  if {$gpgme_maj < 1 || $gpgme_min < 4} {
+-user-error "Found GPGME version $gpgme_version, need 1.4.0"
+-  }
+-}
+-define GPGME_VERSION_NUMBER [format "0x%02x%02x%02x" $gpgme_maj $gpgme_min $gpgme_patch]
+-
+-# RHEL6 doesn't have this function yet
+-cc-check-function-in-lib gpgme_op_export_keys gpgme
+-
+-# CFLAGS
+-if {[catch {exec-with-stderr $gpgme_config --cflags} res err]} {
+-  user-error "Could not derive --cflags from $gpgme_config"
+-}
+-define-append CFLAGS $res
+-
+-# LIBS
+-if {[catch {exec-with-stderr $gpgme_config --libs} res err]} {
+-  user-error "Could not derive --libs from $gpgme_config"
+-}
+-define-append LIBS $res
+-  }
+-  define-feature gpgme
+-
+-  if {![get-define want-pkgconf] || ![pkgconf false gpg-error]} {
+-# Locate gpg-error-config
+-msg-checking "Checking for gpg-error..."
+-set gpg_error_config_guess [file join $gpgme_prefix bin gpg-error-config]
+-if {[file-isexec $gpg_error_config_guess]} {
+-  define GPG-ERROR-CONFIG 

Bug#1024599: Acknowledgement (mpv: [ffmpeg/demuxer] ogg: Header processing failed: Invalid data found when processing input)

2022-11-21 Thread Mr. T
sry, lookes like my try to paste in the terminal output closed the text 
editor and send the bugreport, please close that report in favor for 
00:51 Bug#1024600


thanks



Bug#1024599: Acknowledgement (mpv: [ffmpeg/demuxer] ogg: Header processing failed: Invalid data found when processing input)

2022-11-21 Thread Mr. T
sry, lookes like my try to paste in the terminal output closed the text 
editor and send the bugreport, please close that report in favor for 
00:51 Bug#1024600


thanks

On 22.11.22 00:45, Debian Bug Tracking System wrote:

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 1024599: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024599.

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
   t...@treaki.tk
(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 Multimedia Maintainers 

If you wish to submit further information on this problem, please
send it to 1024...@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.





Bug#1024599: mpv: [ffmpeg/demuxer] ogg: Header processing failed: Invalid data found when processing input

2022-11-21 Thread Mr. T
Package: mpv
Version: 0.32.0-3
Severity: important
X-Debbugs-Cc: t...@treaki.tk

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
wanted to play some music with mpv
* What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages mpv depends on:
ii  libarchive13  3.4.3-2+deb11u1
ii  libasound21.2.4-1.1
ii  libass9   1:0.15.0-2
ii  libavcodec58  7:4.3.5-0+deb11u1
ii  libavdevice58 7:4.3.5-0+deb11u1
ii  libavfilter7  7:4.3.5-0+deb11u1
ii  libavformat58 7:4.3.5-0+deb11u1
ii  libavutil56   7:4.3.5-0+deb11u1
ii  libbluray21:1.2.1-4+deb11u1
ii  libc6 2.31-13+deb11u5
ii  libcaca0  0.99.beta19-2.2
ii  libcdio-cdda2 10.2+2.0.0-1+b2
ii  libcdio-paranoia2 10.2+2.0.0-1+b2
ii  libcdio19 2.1.0-2
ii  libdrm2   2.4.104-1
ii  libdvdnav46.1.0-1+b1
ii  libegl1   1.3.2-1
ii  libgbm1   20.3.5-1
ii  libgl11.3.2-1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.17~dfsg-1
ii  libjpeg62-turbo   1:2.0.6-4
ii  liblcms2-22.12~rc1-2
ii  liblua5.2-0   5.2.4-1.1+b3
ii  libpulse0 14.2-2
ii  librubberband21.9.0-1
ii  libsdl2-2.0-0 2.0.14+dfsg2-3+deb11u1
ii  libsmbclient  2:4.13.13+dfsg-1~deb11u5
ii  libsndio7.0   1.5.0-3
ii  libswresample37:4.3.5-0+deb11u1
ii  libswscale5   7:4.3.5-0+deb11u1
ii  libuchardet0  0.0.7-1
ii  libva-drm22.10.0-1
ii  libva-wayland22.10.0-1
ii  libva-x11-2   2.10.0-1
ii  libva22.10.0-1
ii  libvdpau1 1.4-3
ii  libwayland-client01.18.0-2~exp1.1
ii  libwayland-cursor01.18.0-2~exp1.1
ii  libwayland-egl1   1.18.0-2~exp1.1
ii  libx11-6  2:1.7.2-1
ii  libxext6  2:1.3.3-1.1
ii  libxinerama1  2:1.1.4-2
ii  libxkbcommon0 1.0.3-2
ii  libxrandr22:1.5.1-1
ii  libxss1   1:1.2.3-1
ii  libxv12:1.0.11-1
ii  zlib1g1:1.2.11.dfsg-2+deb11u2

Versions of packages mpv recommends:
ii  xdg-utils   1.1.3-4.1
ii  youtube-dl  2021.06.06-1

mpv suggests no packages.

-- no debconf information



Bug#1024532: gjs allocates 237 GB of RAM during build (!)

2022-11-21 Thread Jeremy Bicha
On Mon, Nov 21, 2022 at 7:54 AM Santiago Vila  wrote:
> El 21/11/22 a las 11:20, Simon McVittie escribió:
> > I think you might accidentally be measuring how much it *can* allocate
> > if given the opportunity, as opposed to how much it strictly *needs*
> > to allocate?
>
> Not exactly. As explained, I am intentionally measuring the allocated
> memory as a completely safe upper bound for the required memory, and I
> am aware that they are not the same. Nevertheless, I try to report
> anomalies like this one when I find them.

Another example is webkitgtk. It uses overcommit as a security feature
codenamed Gigacage. The webkitgtk maintainers would close this kind of
bug as NOTABUG. Perhaps, gjs is doing something similar.

https://blogs.gnome.org/mcatanzaro/2018/11/02/on-webkit-build-options-also-how-to-accidentally-disable-important-security-features/

Thank you,
Jeremy Bicha



Bug#1024226: git-annex: please replace youtube-dl suggests with yt-dlp

2022-11-21 Thread Sean Whitton
Hello,

On Mon 21 Nov 2022 at 03:05PM -04, Joey Hess wrote:

> Sean Whitton wrote:
>> Do you happen to know whether git-annex currently works with youtube-dl
>> replaced with yt-dlp?  Thanks.
>
> Yes, it does, with this git config:
>
>   git config annex.youtube-dl-command yt-dlp
>
> If youtube-dl becomes a wrapper script calling yt-dlp, it would also work
> without that config.
>
> I've also changed git-annex to fall back to yt-dlp when youtube-dl is
> not in path; see attached patch. Also there was a small problem with
> parsing yt-dlp's output that prevented git-annex from displaying
> progress; see second attached patch.

Many thanks.  Just building now, will upload closing this bug shortly.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#1024598: bash: non-source file

2022-11-21 Thread Bastian Germann

Source: bash
Version: 5.2-2
Severity: serious

The bash source includes doc/aosa-bash-full.pdf which is a non-source file 
without corresponding source.
Please remove it additionally to doc/aosa-bash.pdf (already excluded).
You should also add a repack suffix to the upstream version.



Bug#1024597: r-bioc-demixt FTBFS: dependency ‘DSS’ is not available for package ‘DeMixT’

2022-11-21 Thread Adrian Bunk
Source: r-bioc-demixt
Version: 1.14.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=r-bioc-demixt=1.14.0-1

...
I: Using built-time from d/changelog: Mon, 21 Nov 2022 13:38:58 +0100
mkdir -p /<>/debian/r-bioc-demixt/usr/lib/R/site-library
R CMD INSTALL -l 
/<>/debian/r-bioc-demixt/usr/lib/R/site-library --clean . 
"--built-timestamp='Mon, 21 Nov 2022 13:38:58 +0100'"
ERROR: dependency ‘DSS’ is not available for package ‘DeMixT’
* removing ‘/<>/debian/r-bioc-demixt/usr/lib/R/site-library/DeMixT’
dh_auto_install: error: R CMD INSTALL -l 
/<>/debian/r-bioc-demixt/usr/lib/R/site-library --clean . 
"--built-timestamp='Mon, 21 Nov 2022 13:38:58 +0100'" returned exit code 1
make: *** [debian/rules:4: binary-arch] Error 25


Bug#1024540: transition: libpinyin

2022-11-21 Thread Gunnar Hjalmarsson

On 2022-11-21 20:46, Sebastian Ramacher wrote:

Please go ahead after filing the bug against malitt-keyboard.


Ok.

* maliit-keyboard bug: https://bugs.debian.org/1024593

* libpinyin 2.7.92-2 uploaded to unstable



Bug#1024596: usrmerge: remove hard-coded list of bi-arch directories

2022-11-21 Thread Luca Boccassi
Package: usrmerge
Version: 33
X-Debbugs-CC: a...@debian.org

Hi,

Andreas says:

> now that glibc is fixed and creates appropriate /lib{23,64,x32}
> symlinks, can we update usrmerge and debootstrap (how many variants?) to
> not leave unused (and unowned) /lib{23,64,x32} symlinks and empty
> /usr/lib{23,64,x32} directories that may disappear during piuparts tests?
> I'd prefer to fix that properly and not work around it in piuparts.
>
> For usrmerge it should be rather easy: there is no need to "convert" not
> existing paths.
>
> We could add a versioned Depends on libc6 (and the equivalent libcX on
> !linux)) to usrmerge (and usr-is-merged) to ensure a "fixed" libc is
> already installed (and only "fixed" libc-foo packages can be installed
> afterwards). That Depends should be sufficient to also keep out older
> libc-foo since iirc libc6 and libc6-foo are (transitively) version-locked).

Kind regards,
Luca Boccassi



Bug#1024595: python3-gevent 22.10.2 must depend on python3-greenlet >= 2.0.1

2022-11-21 Thread Adrian Bunk
Package: python3-gevent
Version: 22.10.2-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Jelmer Vernooij 
Control: affects -1 src:derpconf
Control: block -1 by 1024433

https://buildd.debian.org/status/fetch.php?pkg=derpconf=all=0.8.3-3=1669044556=0

...
/usr/bin/make test
make[2]: Entering directory '/<>'
:241: RuntimeWarning: greenlet.greenlet size 
changed, may indicate binary incompatibility. Expected 40 from C header, got 
160 from PyObject
:241: RuntimeWarning: greenlet.greenlet size 
changed, may indicate binary incompatibility. Expected 40 from C header, got 
160 from PyObject
:241: RuntimeWarning: greenlet.greenlet size 
changed, may indicate binary incompatibility. Expected 40 from C header, got 
160 from PyObject
:241: RuntimeWarning: greenlet.greenlet size 
changed, may indicate binary incompatibility. Expected 40 from C header, got 
160 from PyObject
:241: RuntimeWarning: greenlet.greenlet size 
changed, may indicate binary incompatibility. Expected 40 from C header, got 
160 from PyObject
:241: RuntimeWarning: greenlet.greenlet size 
changed, may indicate binary incompatibility. Expected 40 from C header, got 
160 from PyObject
:241: RuntimeWarning: greenlet.greenlet size 
changed, may indicate binary incompatibility. Expected 40 from C header, got 
160 from PyObject
:241: RuntimeWarning: greenlet.greenlet size 
changed, may indicate binary incompatibility. Expected 40 from C header, got 
160 from PyObject
Segmentation fault
make[2]: *** [Makefile:2: test] Error 139


This is due to:

https://sources.debian.org/src/python-gevent/22.10.2-1/CHANGES.rst/

...
22.10.2 (2022-10-31)



Bugfixes


- Update to greenlet 2.0. This fixes a deallocation issue that required
  a change in greenlet's ABI. The design of greenlet 2.0 is intended to
  prevent future fixes and enhancements from requiring an ABI change,
  making it easier to update gevent and greenlet independently.
...


Bug#1023872: [Pkg-mpd-maintainers] Bug#1023872: mpd: 0.23.9-1+b3 fails to start with 'io_uring_get_sqe() failed'

2022-11-21 Thread Florian Schlichting
On Tue, Nov 15, 2022 at 05:40:13PM +0300, Michael Tokarev wrote:
> This is #1023654 , fwiw.

which is now fixed, but mpd will need a rebuild to pick up the tightened
dependency. I'll look into uploading 0.23.10 over the next few days.

Florian



Bug#1002855: mpd: Installation fails: invoke-rc.d: initscript mpd, action "restart" failed

2022-11-21 Thread Florian Schlichting
Hi,

On Thu, Dec 30, 2021 at 06:04:30AM -0300, Eppur Si Muove wrote:
> I'm with this new installation of a virtual machine of Debian Testing, using 
> runit as init,
> and I wanted to install mpd, but that process returned this:
> ...
> Configurando mpd (0.23.5-1+b1) ...
> /etc/mpd.conf must have pid_file set; cannot stop daemon. ... failed!
> invoke-rc.d: initscript mpd, action "restart" failed.
> dpkg: erro ao processar o pacote mpd (--configure):
>  o subprocesso instalado, do pacote mpd, o script post-installation retornou 
> erro do status de saída 1
> Erros foram encontrados durante o processamento de:
>  mpd
> E: Sub-process /usr/bin/dpkg returned an error code (1)

it becomes difficult to support systemd and alternative init systems at
the same time. The /etc/mpd.conf file that comes with the package is
configured to be used with systemd, and thus doesn't set pid_file or
log_file any more. However the init script expects it to be there and
won't run if it isn't.

I might accept a patch to the initscript to not fail with the mpd.conf
shipped by the package, but I won't have time to develop one myself.

> I tried the following workaround:
>  - # reboot
>  - uncommented the line aboud PID file in /etc/mpd.conf
>  - # mkdir /run/mpd
>  - # touch /run/mpd/pid
>  - # chown mpd /run/mpd/pid
>  - # apt upgrade

I would expect it to be enough to uncomment the pid_file line and run

sudo dpkg --configure -a

However if you weren't going to use and configure mpd just yet, I would
expect leaving mpd.conf as-is and just disabling mpd should also do the
trick:

sudo update-rc.d disable mpd

Florian



Bug#1024594: RFP: nginx-unit -- polyglot app server, a reverse proxy, and a static file server

2022-11-21 Thread Georg Faerber
Package: wnpp
Owner: Georg Faerber 
Severity: wishlist
X-Debbugs-Cc: debian-de...@lists.debian.org

Package name: nginx-unit
Version : 1.28.0
Upstream Author : Nginx team members and contributors
URL : https://github.com/nginx/unit
License : Apache Software License (ASL) 2.0
Programming Lang: C
Description : polyglot app server, reverse proxy, and static file server

nginx-unit is a lightweight and versatile open-source server that has three
core capabilities:

* it is an HTTP reverse proxy,
* a web server for static media assets,
* and an application server that runs code in seven languages.

Key Features

Flexibility

* The entire configuration is managed dynamically over HTTP via a RESTful JSON 
API
* Updates to the configuration are performed granularly at runtime with zero 
interruption
* Requests are routed between static content, upstream servers, and local apps
* Request filtering and dispatching uses elaborate matching rules that allow 
regular expressions
* Apps in multiple languages and language versions run side by side
* Common language-specific APIs for all supported languages run seamlessly
* Upstream server groups provide dynamic load balancing using a weighted 
round-robin method
* Originating IP identification supports X-Forwarded-For and similar header 
fields

Performance

* Requests are asynchronously processed in threads with efficient event loops 
(epoll, kqueue)
* Syscalls and data copy operations are kept to a necessary minimum
* 10,000 inactive HTTP keep-alive connections take up only a few MBs of memory
* Router and app processes rely on low-latency IPC built with lock-free queues 
over shared memory
* Built-in statistics provide insights into Unit’s performance
* The number of per-app processes is defined statically or scales preemptively 
within given limits
* App and instance usage statistics are collected and exposed via the API
* Multithreaded request processing is supported for Java, Perl, Python, and 
Ruby apps

Security & Robustness

* Client connections are handled by a separate non-privileged router process
* Low-resource conditions (out of memory or descriptors) and app crashes are 
handled gracefully
* SSL/TLS with SNI, session cache and tickets is integrated (OpenSSL 1.0.1 and 
later)
* Different apps are isolated in separate processes
* Apps can be additionally containerized with namespace and file system 
isolation
* Static file serving benefits from chrooting, symlink and mount point 
traversal restrictions

Supported App Languages

* Binary-compiled languages in general: using the embedded libunit library
* Go: by overriding the http module
* JavaScript (Node.js): by automatically overloading the http and websocket 
modules
* Java: using the Servlet Specification 3.1 and WebSocket APIs
* Perl: using PSGI
* PHP: using a custom SAPI module
* Python: using WSGI or ASGI with WebSocket support
* Ruby: using the Rack API

Upstream docs available via https://unit.nginx.org/.



Bug#1024070: linux-image-6.0.0-3-amd64: IPv6 ProxyNDP stops responding to ND solicitation some time after startup

2022-11-21 Thread Kevin P. Fleming
On Sun, Nov 20, 2022, at 12:56, Kevin P. Fleming wrote:
> On Sun, Nov 20, 2022, at 08:38, Salvatore Bonaccorso wrote:
>
>> If that would be helpful, we have some instructions on "simple
>> patching and building" the kernel with a additional patches on top
>> here:
>>
>> https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2
>
> I found those via another path, and used them :-) Had a few little 
> issues along the way: failing to set DEBFULLNAME produces a broken 
> changelog entry so then the build won't run (and leaves the tree in a 
> broken state as well). Once I solved that problem I was able to make 
> packages, but the linux-headers-common package didn't get produced, so 
> I had to use --force-depends-version when installing the packages 
> (which I knew was safe since the headers had not changed).
>
> I now have the patched kernel in operation and should know whether the 
> problem is solved in 24-48 hours.

It's been more than 24 hours and connectivity is still in place, and it never 
lasted this long without the patch. I'm comfortable saying that this patch 
resolved the problem.



Bug#963025: fixed in firmware-nonfree 20210315-1~exp1

2022-11-21 Thread Stefan Pietsch

On 08.04.21 11:50, Stefan Pietsch wrote:

On 30.03.21 13:35, maximilian attems wrote:

reopen 963025
found -1 20210315-2
tags -1 moreinfo
stop


[18661.586025] CPU: 0 PID: 8408 Comm: hostapd Tainted: G    W 
5.10.0-5-amd64 #1 Debian 5.10.24-1
[18661.586029] Hardware name: LENOVO 20N2007GGE/20N2007GGE, BIOS N2IET81W (1.59 
) 11/29/2019



Please could you upgrade the BIOS to latest for T490, 1.72 2021/03/17
to exclude this guy fault.



I upgraded the Lenovo T490 BIOS from 1.59 to 1.72.
That did not make any difference.



I cannot reproduce this with firmware version 46.9d0122c0.0 
9000-pu-b0-jf-b0-46.ucode from firmware-iwlwifi 20221012-1.
This seems to be fixed.

Regards,
Stefan



Bug#1022052: whiptail 0.52.21-6: fails with output: "free(): invalid pointer"

2022-11-21 Thread Håvard F . Aasen
Control: tags -1 + fixed-upstream
Control: forwarded -1 https://pagure.io/newt/issue/22

Dear Maintainer,

This bug was fixed upstream a few hours ago. They also
released a new version containing the fix.

Regards,
Håvard



Bug#1023495: transition: ruby3.1

2022-11-21 Thread Lucas Kanashiro

Hi,

We have been performing the rebuilds and fixing packages for a while, 
you can see the results of our last test rebuild (from the beginning of 
this month) here:


https://people.debian.org/~kanashiro/ruby3.1

Some package listed as build failures were actually fixed already. From 
the list we have in the transition tracker:


https://release.debian.org/transitions/html/ruby3.1-default.html

Apart from the packages not in testing, only 2 packages are failing to 
build in the first dependency level:


- dislocker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024589 . 
This one seems unrelated to this transition.


- uwsgi: this needs a trivial patch in d/control to replace 3.0 with 3.1 
in the uwsgi-plugin-rack-ruby3.0 binary name. This will be done once 
ruby3.1 becomes the default in unstable.


All the others seem good to go.

With that in mind, we would like to ask the Release Team if we can start 
the transition in unstable and change the default to 3.1.


TIA!

--
Lucas Kanashiro



Bug#1024593: libpinyin transition: build-dep on libpinyin15-dev needed

2022-11-21 Thread Gunnar Hjalmarsson

Package: src:maliit-keyboard
Version: 2.3.1-3
Severity: important

Hi!

libpinyin upstream made a SOVERSION bump from 13 to 15, and I'm about to 
upload libpinyin 2.7.92-2 to unstable with altered package names.


https://bugs.debian.org/1024540

As a result there will be a need to upload maliit-keyboard with 
libpinyin15-dev in Build-Depends instead of libpinyin13-dev. Please do 
so soon once libpinyin 2.7.92-2 has been built in unstable.


--
Cheers,

Gunnar Hjalmarsson



Bug#1024592: systemd configuration for inetd mode is broken in 1:9.1p1-1

2022-11-21 Thread Eugene Berdnikov
Package: openssh-server
Version: 1:9.1p1-1
Severity: minor

 After upgrade from 1:9.0p1-1+b1 to 1:9.1p1-1 sshd starts under systemd
 as standalone daemon only.

 1. File /lib/systemd/system/ssh@.service is missing in 1:9.1p1-1,
while /lib/systemd/system/ssh.socket is present.
So sshd can not be run as inetd-style service, because ".socket"
requires apropriate "@.service" unit.

 2. Unit file /lib/systemd/system/ssh.socket has considerable changes
in comparison with old 1:9.0p1-1+b1. First, it's [Unit] section
has "Before=sockets.target", and [Install] section has
"WantedBy=sockets.target", it seems contradictionry to me.
Then, old version 1:9.0p1-1+b1 has two options in this section:
"Before=ssh.service" and "Conflicts=ssh.service". It prevents
from concurent access to listening socket. New package 1:9.1p1-1
has no such options.

 Result: with ssh.service=disabled and ssh.socket=enabled port 22 is
 listened by two process: by systemd and by sshd daemon. All incoming
 connections are handled by standalone sshd daemon, probably because
 systemd can't handle them due to absence of @.service unit file.

 If unit files ssh.socket and ssh@.service are taken from old package,
 all works right as expected.
-- 
 Eugene Berdnikov



Bug#1024591: Building with libcamera?

2022-11-21 Thread Dylan Aïssi
Hi Sebastien

Le lun. 21 nov. 2022 à 21:39, Sebastien Bacher  a écrit :
>
> would it make sense to turn the option on?
>

Sure, it's on the top of my todo list.

Best,
Dylan



Bug#1023731: BioC Transition blocked by new dependencies

2022-11-21 Thread Dylan Aïssi
Hi Nilesh,

Le lun. 21 nov. 2022 à 18:29, Nilesh Patra  a écrit :
>
> Lastly I also want to higlight that: while bioc transition is in theory a 
> transition (I agree)
> but to my understanding, there is no _real_ API change. It is just the tool 
> taking the
> API field from DESCRIPTION file into consideration, and causing FTBFS if it 
> does not match.
>
> In principle, building a package that has an older API value in DESCRIPTION 
> file with the newer
> one does not break anything, it rather looks as updates of various packages 
> disguised as an API
> change, and at least in debian land, to me it just appears as a broken tool 
> config and not a real
> transition (like library transition, for example the recent onetbb one).
>

Before having this r-api-bioc virtual package, transitions were even
worse. We had a lot of autopkgtest
issues only because a mix of r-bioc pkgs installed from the old and
from the new bioconductor releases.
Issues which solved by themselves when the transition is over and of
course, users were complaining
about broken packages during the transition. We were losing a lot of
time to investigate these issues.
With this r-api-bioc mechanism, we don't allow this mixture of r-bioc
pkgs and thus we limit these
temporary issues.

Adding this r-api-bioc virtual package has another consequence, now we
can take advantage of the
transition tracker and upload packages following levels. Before the
order of the uploads were a bit
random and again we lose of lot of time to figure out in which order
we have to update them.

Best,
Dylan



Bug#1024524: Thunderbird: mail.compose.other.header side effects

2022-11-21 Thread Pascal Hambourg

Hello Carsten,

On 21/11/2022 at 08:53, Carsten Schoenert wrote:


Could you please report your problem to the Bugzilla bugtracker and give 
us a linking to the bug report afterwards?


Thank you for the quick reply.
Bugzilla found an existing bug report which seems to be related:

I added my observations and will report.



Bug#1024516: mariadb-10.6: FTBFS on ia64: ha_archive.so: version node not found for symbol lzma_get_progress@@XZ_5.2

2022-11-21 Thread John Paul Adrian Glaubitz

Hi!

On 11/21/22 00:07, John Paul Adrian Glaubitz wrote:

This issue has shown in other packages such as glibc on ia64 [1]:

/usr/bin/ld: /<>/build-tree/ia64-libc/dlfcn/bug-atexit3-lib.so: 
version node not found for symbol lzma_get_progress@@XZ_5.2
/usr/bin/ld: failed to set dynamic section sizes: bad value
collect2: error: ld returned 1 exit status

So, I don't think it's a regression in mariadb-10.6 itself but rather
the toolchain on ia64.


FWIW, there have been changes to the symbols file of src:xz-utils by Sebastian 
(CC'ed) which
might be responsible for this regression on ia64 with liblzma [1].

I will build a test package on the porterbox yttrium with the changes reverted 
and see if that
fixes the problem.

Adrian


[1] 
https://tracker.debian.org/news/1376000/accepted-xz-utils-527-00-source-into-unstable/


--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Bug#953630: [Debichem-devel] Bug#953630: openbabel autopkg tests fail on non-amd64 architectures

2022-11-21 Thread Paul Gevers

Hi,

On 21-11-2022 16:01, Andrius Merkys wrote:

On 2022-11-20 18:18, Paul Gevers wrote:
 From the BSP in Tilburg, I uploaded the attached NMU to DELAYED/5. 
Please let me know if I should delay more or cancel.


Thanks, IMO this NMU is fine. Similar logic should be applied to the 
build time tests in future, since now their failures are plainly ignored.


Rescheduled to DELAYED/0.

Thanks.

Paul


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1024524: Thunderbird: mail.compose.other.header side effects

2022-11-21 Thread Carsten Schoenert

Control: forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1800759

Hello Pascal,

I've added that upstream bug report so the BTS will inform if something 
is happen within the upstream report.

Thanks!

Am 21.11.22 um 21:31 schrieb Pascal Hambourg:

Hello Carsten,

On 21/11/2022 at 08:53, Carsten Schoenert wrote:


Could you please report your problem to the Bugzilla bugtracker and give
us a linking to the bug report afterwards?


Thank you for the quick reply.
Bugzilla found an existing bug report which seems to be related:

I added my observations and will report.


--
Regards
Carsten



Bug#1024591: Building with libcamera?

2022-11-21 Thread Sebastien Bacher

Package: pipewire
Version: 0.3.60-2

The Debian package is currently built without libcamera. Since libcamera 
seems to be the preferred option for camera support on linux going 
forward 
(https://blogs.gnome.org/uraeus/2021/10/01/pipewire-and-fixing-the-linux-video-capture-stack/) 
and upstream libcamera properly set its soname now 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962650) would it make 
sense to turn the option on?


Thanks,



Bug#1024590: libsearch-xapian-perl FTCBFS: uses the build architecture C++ compiler

2022-11-21 Thread Helmut Grohne
Source: libsearch-xapian-perl
Version: 1.2.25.5-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

libsearch-xapian-perl fails to cross build from source, because it ends
up using the build architecture C++ compiler. The easiest way to
correctly initialize the CXX variable is using dpkg's buildtools.mk. I'm
attaching a patch for your convenience.

Helmut
diff --minimal -Nru libsearch-xapian-perl-1.2.25.5/debian/changelog 
libsearch-xapian-perl-1.2.25.5/debian/changelog
--- libsearch-xapian-perl-1.2.25.5/debian/changelog 2022-03-04 
17:33:49.0 +0100
+++ libsearch-xapian-perl-1.2.25.5/debian/changelog 2022-11-21 
08:11:53.0 +0100
@@ -1,3 +1,10 @@
+libsearch-xapian-perl (1.2.25.5-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dpkg's buildtools.mk initialize CXX. (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 21 Nov 2022 08:11:53 +0100
+
 libsearch-xapian-perl (1.2.25.5-1) unstable; urgency=medium
 
   [ Debian Janitor ]
diff --minimal -Nru libsearch-xapian-perl-1.2.25.5/debian/rules 
libsearch-xapian-perl-1.2.25.5/debian/rules
--- libsearch-xapian-perl-1.2.25.5/debian/rules 2022-03-04 17:33:49.0 
+0100
+++ libsearch-xapian-perl-1.2.25.5/debian/rules 2022-11-21 08:11:51.0 
+0100
@@ -2,6 +2,8 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 export TEST_POD=1
+DPKG_EXPORT_BUILDTOOLS=1
+include /usr/share/dpkg/buildtools.mk
 
 %:
dh $@


Bug#972315: sysvinit still misses B-D: libcrypt-dev

2022-11-21 Thread Helmut Grohne
reopen -1
thanks

sysvinit lost its libcrypt-dev dependency. Please add it back.

Helmut



Bug#983912: grub2: consider renaming signed source packages to grub2-signed-*

2022-11-21 Thread J.A. Bezemer



On Sun, 20 Nov 2022, Salvatore Bonaccorso wrote:

On Wed, Mar 03, 2021 at 10:52:39AM +0100, Ansgar wrote:

Source: grub2
Version: 2.04-16
Severity: normal
X-Debbugs-Cc: ftpmas...@debian.org, debian-rele...@lists.debian.org

grub2 currently uses grub-efi-signed-* as source package names for the
Secure Boot signed packages.  While releasing the last security update
we found a small issue with these names:

dak processes source packages in lexiographic order, so it would
process grub-efi-signed-* before grub2 when accepting all packages at
once from the "embargoed" policy queue.  But the grub-efi-signed-*
binary packages have Built-Using: grub2; as grub2 is not accepted from
embargoed at this point in time, the /binary/ uploads will be rejected
in this case.  (This problem exists in principle with all Built-Using
relations.)


How hard would it be to enhance dak to not require any specific ordering?

One way could be to process the same list repeatedly, until no additional 
packages have been accepted for an entire pass.


Regards,
Anne Bezemer



Bug#1024450: ITP: setuptools-gettext -- Compile .po files into .mo files

2022-11-21 Thread Roland Clobus

Hello Jelmer,

On 19/11/2022 18:20, Jelmer Vernooij wrote:

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

* Package name: setuptools-gettext
   Version : 0.0.1
   Upstream Author : Breezy Team 
* URL : https://github.com/jelmer/setuptools-gettext
* License : GPL
   Programming Lang: Python
   Description : Compile .po files into .mo files

This extension for setuptools compiles gettext .po files
found in the source directory into .mo files and installs them.


How does this tool differ from 'msgfmt' from 'gettext'?

With kind regards,
Roland Clobus

PS: The URL is https://github.com/breezy-team/setuptools-gettext


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1024589: dislocker: FTBFS with ruby3.1: mv: cannot stat '/<>/debian/tmp/usr/lib/libdislocker*': No such file or directory

2022-11-21 Thread Lucas Kanashiro

Source: dislocker
Version: 0.7.3-2.1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User:debian-r...@lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild dislocker with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):

   debian/rules override_dh_install-arch
make[1]: Entering directory '/<>'
dh_install
mv /<>/debian/tmp/usr/lib/libdislocker* \
   /<>/debian/libdislocker0.7/usr/lib/
mv: cannot stat '/<>/debian/tmp/usr/lib/libdislocker*': No such 
file or directory
make[1]: *** [debian/rules:16: override_dh_install-arch] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:12: binary] Error 2

The full build log is available from:

https://people.debian.org/~kanashiro/ruby3.1/20/dislocker/dislocker_0.7.3-2.1+rebuild1667925374_amd64-2022-11-08T16:36:15Z.build

To reproduce this, you need ruby-all-dev >= 1:3.1~0.  Depending on when you
read this, this might mean installing ruby-all-dev from experimental, or if the
transition has already started in unstable, a normal build on unstable should
do it.  If you fail to reproduce, please provide a build log and diff it with
mine so that we can identify if something relevant changed in the meantime.

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS  . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. Seehttps://www.debian.org/Bugs/server-control#affects

--
Lucas Kanashiro


Bug#1024588: genomicsdb needs hinting into testing

2022-11-21 Thread Adrian Bunk
Package: release.debian.org
Severity: normal

binary-any + binary-all, but binary-any does not build on most
architectures.

This results in autopkgtest failure due to missing binaries on
the architectures without binaries where autopkgtest is anyway
run due to the binary-all.



Bug#1024519: ITP: golang-github-keybase-go-ps -- find, list, and inspect processes from Go

2022-11-21 Thread Ryan Kavanagh
On Mon, Nov 21, 2022 at 11:11:07AM +0800, Shengjing Zhu wrote:
> Besides, which package needs it? I checked #1012721, which is for
> chezmoi. But I can't any use of the go-ps.

chezmoi imports from golang-github-google-gops (NEW), which depends on
golang-github-keybase-go-ps.

Ryan

-- 
|)|/  Ryan Kavanagh  | 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac | BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature


Bug#1024561: Unmaintained, keep out of stable

2022-11-21 Thread Sam Trenholme
Upstream here. I should probably summarize the security issues post
2.0.13; MaraDNS is the authoritative server and Deadwood is the
recursive server:

- A theoretical issue with the cryptographic code which doesn’t affect
gcc and clang compiles of Deadwood.
- An issue where a clever attacker could had kept a record in the
cache longer than desired in a fully recursive instance of Deadwood.
- An issue where a clever attack could make Deadwood perform around
500 queries to resolve a given name, if they can control the query and
responses Deadwood gets. In the fix, that number was reduced to 83.

None of these are serious security issues; I would be comfortable
using a non-Recursive instance of MaraDNS 2.0.13 on a public network,
but they are “it’s probably worth updating” security issues. I should
point out that MaraDNS 3 is fully compatible with MaraDNS 2
configuration files and the number jump was done to keep Deadwood’s
and MaraDNS’s version numbers in sync.

In terms of the upgrade, there are two branches to consider:

- The very stable 3.4 branch, where the fixes are by and large
security and other serious fixes. This branch, which was dormant for
about three years, recently had a flurry of updates for minor security
and Y2038 fixes. [1] The majority of the updates are made as patches
which can be applied to older versions, if Debian wants to take the
“patch older software” route. My plan is to keep this branch dormant
again unless another security issue comes up. In particular, this
branch is generally *not* updated to fix resolution issues with the
Deadwood recursive resolver, unless it’s something huge like
amazon.com not resolving.
- The less stable 3.5 branch. This is the continuous integration
version of MaraDNS; features are added and there’s no “frozen” branch.
Automated testing is done once a day whenever the Git tree changes and
I frequently make new releases when a given Git checkout passes
automated tests. Effort is made to keep older configuration files
compatible, so we don’t get the situation where configuration files
need to be revised to apply a security update.

[1] Other stuff was changed too. I changed a bunch Makefiles and
filenames in MaraDNS 3.4 so that it will compile with a mostly-POSIX
compliant implementation of `make`; POSIX actually didn’t mandate `-`
in make targets (it will in the next 202X POSIX release); I added
min_ttl to Deadwood so it remains semi usable as a fully recursive DNS
server on the modern Internet.

On Mon, Nov 21, 2022 at 5:03 AM Moritz Muehlenhoff  wrote:
>
> Source: maradns
> Version: 2.0.13-1.4
> Severity: serious
>
> The last maintainer upload was in 2015 and the version currently in the
> archive is way behind current upstream releases (which is at 3.4.07),
> we have plenty of maintained DNS servers, keep it out of testing (
> and if noone picks it up, remove it from the archive).
>



Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries

2022-11-21 Thread Soren Stoutner
No current changes are needed to QT WebEngine as it currently exists in 
Debian.  It works just fine as long as the dictionaries are in the canonical 
location (or that canonical location is a symlink to the actual location).

I have written some descriptions of my testing of this in earlier posts to 
this bug report, but if there are any questions I would be happy to provide 
more documentation about how I did my testing and how anyone can reproduce it 
and verify that the existing QT WebEngine already has all the .bdic plumbing 
built into it.

On Monday, November 21, 2022 11:29:28 AM MST Lisandro Damián Nicanor Pérez 
Meyer wrote:
> Hi,
> 
> On Wed, 9 Nov 2022 at 15:13, Soren Stoutner  wrote:
> [snip]
> 
> > This would also require the the Debain Qt/KDE Maintainers add a symlink
> > from / usr/share/qt5/qtwebengine_dictionaries and /usr/share/qt6/
> > qtwebengine_dictionaries to /usr/share/hunspell-bdic.  They can do this in
> > whatever package makes the most sense to them, but possibly in
> > libqt5webengine-data and libqt6webengine6-data.
> 
> The problem is not a symlink, but building and testing qt[5 6]webkit
> with this change. Maybe building is not an issue as we could just
> remove the bdic files and add the symlink... but someone who really
> understands what's going on under the hood should do a very careful
> test to see things are working.


-- 
Soren Stoutner
so...@stoutner.com

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


Bug#1010648: marked as pending in golang-github-pierrec-lz4.v4

2022-11-21 Thread Nicholas D Steeves
Control: retitle -1 RFP: golang-github-pierrec-lz4.v4 -- LZ4 compression and 
decompression in pure Go (v4)
Control: noowner -1

TLDR: this missing package is blocking updates for syncthing as well as
golang-github-gocql-gocql.  It will be more challenging to maintain
syncthing (backported fixes for CVEs) in bookworm if we get stuck with
1.19.2, from 05 April 2022 rather than 1.22.x or 1.23.x.

Hi Eric, Aloïs, Alexandre, and Go Team,

There is no longer a package waiting for review in NEW.

I missed a few Gutenberg headers in my review; however, strictly
speaking, this might be what FTP Masters are objecting to (without
saying so), because there is less precedent for implicit Gutenberg
license to 3-clause-BSD has than public domain to 3-clause-BSD.
Upstream would need to exercise his public domain right to remove the
Gutenberg headers, and some FTP Masters appear to also be angling for an
explicit upstream public_domain to 3-clause-BSD record, even though this
isn't required.

Yet there is precedent in the GCC package (and golang package) for how
this isn't a real problem...In these two places, the copyright
information appears to have been strategically omitted from the
copyright file.  This is 100% valid in places that recognise public
domain works (eg: works that have no copyright, not even moral rights),
but I fail to see how it's acceptable for world-wide scope for some
packages but not others.

It's fastest to just remove all the tests.  If the newest src:syncthing
1.19.2 tests for correct operation of lz4.v4 compression on buildds and
DebCI than this may not be as horrifying at it seems.

It may also be sufficient to remove the fuzz and testdata from the
single binary package, but I feel like that depends on which FTP Master
reviews the package.

We're running out of time to fix this for bookworm, so I leave this to
someone else.  Here's the remote:

  g...@salsa.debian.org:go-team/packages/golang-github-pierrec-lz4.v4.git

Regards,
Nicholas


signature.asc
Description: PGP signature


Bug#1024540: transition: libpinyin

2022-11-21 Thread Sebastian Ramacher
Control: tags -1 confirmed

On 2022-11-21 08:03:26 +0100, Gunnar Hjalmarsson wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-Cc: debian-input-met...@lists.debian.org
> 
> Hello Release Team,
> 
> libpinyin upstream made a SOVERSION bump from 13 to 15, and the Debian
> packaging has been changed accordingly in libpinyin 2.7.92-1 in
> experimental. These are the packages affected by the transition:
> 
>  fcitx-libpinyin
>  fcitx5-zhuyin
>  ibus-libpinyin
>  ibus-libzhuyin
>  maliit-keyboard
> 
> I have changed the sources as appropriate and successfully test built the
> packages against the new libpinyin.
> 
> As regards maliit-keyboard I plan to ping the maintainer (aka submit a bug)
> and possibly do an NMU. The other affected packages are maintained by
> Debian's IME team, and as a team member I plan to upload them myself.
> 
> The autogenerated ben tracker looks as expected:
> 
> https://release.debian.org/transitions/html/auto-libpinyin.html
> 
> Please consider libpinyin for transition.

Please go ahead after filing the bug against malitt-keyboard.

Cheers
-- 
Sebastian Ramacher



Bug#1023535: transition: protobuf

2022-11-21 Thread Sebastian Ramacher
Control: tags -1 = confirmed

On 2022-11-10 23:10:29 +0100, Sebastian Ramacher wrote:
> Control: block -1 by 1022248 1018945
> 
> On 2022-11-06 09:08:57 +0100, László Böszörményi wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > 
> > Hi RMs,
> > 
> > There's a long awaited transition of Protobuf. It clashes with the
> > ruby3.1-default transition, but as I know its rebuilds are just
> > starting[1].
> > On the other hand I'm done with the rebuilds and patched all issues,
> > this transition may start immediately at your decision. The only
> > downside is that the Sid version of cura-engine is FTBFS and to fix
> > it, the libarcus transition (only affecting this package) will need to
> > be done.
> > 
> > Failing packages and fixes in detail.
> > Level 2:
> > android-platform-frameworks-base has my patch already applied [2] for
> > experimental (not Sid!).
> > libarcus builds in Sid, but not the version in experimental for which
> > I provided a fix [3].
> > target-factory changed library symbols [4], maintainer will need to update 
> > that.
> > 
> > Level 3:
> > cura-engine fails with the Sid version [5], with the libarcus
> > transition done it compiles fine.
> > grpc-java for which I provided the fix [6], the maintainer noted he
> > will be ready to update the package.
> > llvm-toolchain-13 for which I provided the fix [7], other problems
> > seem to be fixed with the upload just happened.
> > llvm-toolchain-14 for which I also provided the fix [8], its other
> > problem [9] might be wrongly closed by cross referenced
> > llvm-toolchain-15 package - but Sylvestre Ledru seems to be aware of
> > issues anyway.
> 
> Let's wait until icu and libbpf are done.

Please go ahead

Cheers

> 
> Cheers
> 
> > 
> > Thanks for considering,
> > Laszlo/GCS
> > [1] https://bugs.debian.org/1023495#5
> > [2] https://bugs.debian.org/1012572
> > [3] https://bugs.debian.org/1023497
> > [4] https://bugs.debian.org/1023496
> > [5] https://bugs.debian.org/1023498
> > [6] https://bugs.debian.org/1023500
> > [7] https://bugs.debian.org/1023532
> > [8] https://bugs.debian.org/1023532
> > [9] https://bugs.debian.org/1023444
> > 
> 
> -- 
> Sebastian Ramacher
> 

-- 
Sebastian Ramacher



Bug#1023846: transition: gdal

2022-11-21 Thread Sebastiaan Couwenberg

On 11/20/22 20:19, Sebastiaan Couwenberg wrote:

On 11/19/22 20:18, Sebastian Ramacher wrote:

On 2022-11-11 11:55:45 +0100, Bas Couwenberg wrote:

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: pkg-grass-de...@lists.alioth.debian.org
Control: forwarded -1 
https://release.debian.org/transitions/html/auto-gdal.html
Control: block -1 by 1023480 1023506 1004795 998833 984398 1023520 
1012950


For the Debian GIS team I'd like to transition to GDAL 3.6.0.


Please go ahead

>
Thanks. gdal (3.6.0+dfsg-2) has been uploaded to unstable and took a 
while to get built on s390x, but is not built & installed on all release 
architectures.


grass is built & installed on all release architectures, libgdal-grass 
can be binNMUed.


qgis had a source upload to fix the FTBFS with python3.11 and cmake 3.25.

Kind Regards,

Bas

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



Bug#1024587: alkimia: BD-Uninstallable on s390x

2022-11-21 Thread Sebastian Ramacher
Source: alkimia
Version: 8.1.1-2
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/package.php?p=alkimia

Dependency installability problem for alkimia on s390x:

alkimia build-depends on:
- libkf5kio-dev:s390x
libkf5kio-dev depends on:
- libkf5xmlgui-dev:s390x (>= 5.98.0~)
libkf5xmlgui-dev depends on:
- libkf5xmlgui5:s390x (= 5.98.0-1+b1)
libkf5xmlgui5 depends on missing:
- libkf5xmlgui-data:s390x (= 5.98.0-1)

Cheers
-- 
Sebastian Ramacher



Bug#1024580: r-bioc-affxparser: FTBFS on hppa - cannot handle R_PARISC_PCREL17F

2022-11-21 Thread Andreas Tille
Hi John,

Am Mon, Nov 21, 2022 at 06:27:59PM + schrieb John David Anglin:
> Source: r-bioc-affxparser
> Version: 1.70.0-1
> Severity: normal
> Tags: ftbfs patch
> ...
> Index: r-bioc-affxparser-1.68.1/src/Makevars
> ===
> --- r-bioc-affxparser-1.68.1.orig/src/Makevars
> +++ r-bioc-affxparser-1.68.1/src/Makevars
> @@ -1,5 +1,5 @@
>  ## -Wno-unused-private-field gives notes/errors with some compiler
> -MYCXXFLAGS = -Wno-sign-compare -O0
> +MYCXXFLAGS = -Wno-sign-compare
>  
>  %.o: %.cpp
>   $(CXX) $(ALL_CPPFLAGS) $(ALL_CXXFLAGS) $(MYCXXFLAGS) -c $< -o $@

Thanks a lot for the patch.  I admit I think this is only half of the
solution.  It deactivated optimisation for all architectures which means
a diversion from -O2 default.  If there is no better solution this patch
(which I added in Git) should be applied only for hppa.

Kind regards
Andreas.

-- 
http://fam-tille.de



Bug#1024585: ITP: golang-github-performancecopilot-speed -- Implementation of the PCP instrumentation API

2022-11-21 Thread 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-performancecopilot-speed
  Version : 4.0.0-1
  Upstream Author : Performance Co-Pilot
* URL : https://github.com/performancecopilot/speed
* License : Expat
  Programming Lang: Go
  Description : Implementation of the PCP instrumentation API
 Golang implementation of the Performance Co-Pilot (PCP)
 instrumentation API.
 .
 There are 3 main components defined in the library, a Client, a
 Registry and a Metric. A client is created using an application name,
 and the same name is used to create a memory mapped file in
 PCP_TMP_DIR. Each client contains a registry of metrics that it
 holds, and will publish on being activated.

This is a dependency of updating golang-github-go-kit-kit and will be
team-maintained within the Go Packaging Team.


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


Bug#1024586: ITP: golang-github-knetic-govaluate -- Arbitrary expression evaluation for golang

2022-11-21 Thread 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-knetic-govaluate
  Version : 3.0.0-1
  Upstream Author : George Lester
* URL : https://github.com/Knetic/govaluate
* License : Expat
  Programming Lang: Go
  Description : Arbitrary expression evaluation for golang
 Provides support for evaluating arbitrary C-like artithmetic/string
 expressions.
 .
 Sometimes, you can't know ahead-of-time what an expression will look
 like, or you want those expressions to be configurable. Perhaps
 you've got a set of data running through your application, and you
 want to allow your users to specify some validations to run on it
 before committing it to a database. Or maybe you've written a
 monitoring framework which is capable of gathering a bunch of
 metrics, when evaluating a few expressions to see if any metrics
 should be alerted upon, but the conditions for alerting are different
 for each monitor.
 .
 A lot of people wind up writing their own half-baked style of
 evaluation language that fits their needs, but isn't complete. Or they
 wind up baking the expression into the actual executable, even if
 they know it's subject to change. These strategies may work, but they
 take time to implement, time for users to learn, and induce technical
 debt as requirements change. This library is meant to cover all the
 normal C-like expressions, so that you don't have to reinvent one of
 the oldest wheels on a computer.

This is a dependency of golang-github-casbin-casbin (ITP#1024583) and
will be team-maintained within the Go Packaging Team.


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


Bug#1024584: ITP: golang-github-vividcortex-gohistogram -- Streaming approximate histograms in Go

2022-11-21 Thread 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-vividcortex-gohistogram
  Version : 1.0.0-1
  Upstream Author : VividCortex
* URL : https://github.com/VividCortex/gohistogram
* License : Expat
  Programming Lang: Go
  Description : Streaming approximate histograms in Go
 This package provides Streaming Approximate Histograms for efficient
 quantile approximations.
 .
 The histograms in this package are based on the algorithms found in
 Ben-Haim & Yom-Tov's "A Streaming Parallel Decision Tree Algorithm".
 Histogram bins do not have a preset size. As values stream into the
 histogram, bins are dynamically added and merged.

This is a dependency of updating golang-github-go-kit-kit and will be
team-maintained within the Go Packaging Team.


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


Bug#1024583: ITP: golang-github-casbin-casbin -- Authorization library that supports access control models like ACL, RBAC, ABAC

2022-11-21 Thread 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-casbin-casbin
  Version : 2.57.0-1
  Upstream Author : Casbin
* URL : https://github.com/casbin/casbin
* License : Apache-2.0
  Programming Lang: Go
  Description : Authorization library that supports access control models 
like ACL, RBAC, ABAC
 Casbin is a powerful and efficient open-source access control library
 for Golang projects. It provides support for enforcing authorization
 based on various access control models.

This is a dependency of updating golang-github-go-kit-kit and will be
team-maintained within the Go Packaging Team.


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


Bug#1024226: git-annex: please replace youtube-dl suggests with yt-dlp

2022-11-21 Thread Joey Hess
Sean Whitton wrote:
> Do you happen to know whether git-annex currently works with youtube-dl
> replaced with yt-dlp?  Thanks.

Yes, it does, with this git config:

git config annex.youtube-dl-command yt-dlp

If youtube-dl becomes a wrapper script calling yt-dlp, it would also work
without that config.

I've also changed git-annex to fall back to yt-dlp when youtube-dl is
not in path; see attached patch. Also there was a small problem with
parsing yt-dlp's output that prevented git-annex from displaying
progress; see second attached patch.

-- 
see shy jo
From 5256be61c12fb030fe2eebe2751ee1601a5e7514 Mon Sep 17 00:00:00 2001
From: Joey Hess 
Date: Mon, 21 Nov 2022 14:39:26 -0400
Subject: [PATCH] When youtube-dl is not available in PATH, use yt-dlp instead

Debian is going to drop youtube-dl which is not active upstream, and yt-dlp
is the replacement. This will make it be used if youtube-dl gets removed.

If an old version of youtube-dl remains installed, git-annex will still use
it. That might not be desirable, but changing git-annex to use yt-dlp in
preference to youtube-dl when both are installed risks breaking when
the user has annex.youtube-dl-options set to something that is supported
by youtube-dl, but not by yt-dlp.

Sponsored-by: Boyd Stephen Smith Jr. on Patreon
---
 Annex/YoutubeDl.hs | 5 +++--
 CHANGELOG  | 1 +
 debian/control | 2 +-
 doc/git-annex.mdwn | 7 ---
 4 files changed, 9 insertions(+), 6 deletions(-)

diff --git a/Annex/YoutubeDl.hs b/Annex/YoutubeDl.hs
index e466f01eba..ba050d4024 100644
--- a/Annex/YoutubeDl.hs
+++ b/Annex/YoutubeDl.hs
@@ -249,8 +249,9 @@ youtubeDlOpts addopts = do
 	return (opts ++ addopts)
 
 youtubeDlCommand :: Annex String
-youtubeDlCommand = fromMaybe "youtube-dl" . annexYoutubeDlCommand 
-	<$> Annex.getGitConfig
+youtubeDlCommand = annexYoutubeDlCommand <$> Annex.getGitConfig >>= \case
+	Just c -> pure c
+	Nothing -> fromMaybe "yt-dlp" <$> liftIO (searchPath "youtube-dl")
 
 supportedScheme :: UrlOptions -> URLString -> Bool
 supportedScheme uo url = case parseURIRelaxed url of
diff --git a/CHANGELOG b/CHANGELOG
index d193ceca85..78fa628e4f 100644
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -4,6 +4,7 @@ git-annex (10.20221105) UNRELEASED; urgency=medium
   * Sped up the initial scan for annexed files by 21%.
   * init: Avoid scanning for annexed files, which can be lengthy in a
 large repository. Instead that scan is done on demand.
+  * When youtube-dl is not available in PATH, use yt-dlp instead.
 
  -- Joey Hess   Fri, 18 Nov 2022 12:58:06 -0400
 
diff --git a/debian/control b/debian/control
index 762052186a..ac28ca029c 100644
--- a/debian/control
+++ b/debian/control
@@ -111,7 +111,7 @@ Recommends:
 	lsof,
 	gnupg,
 	bind9-host,
-	youtube-dl,
+	yt-dlp,
 	git-remote-gcrypt (>= 0.20130908-6),
 	nocache,
 	aria2,
diff --git a/doc/git-annex.mdwn b/doc/git-annex.mdwn
index 5eca6600c8..60811dce06 100644
--- a/doc/git-annex.mdwn
+++ b/doc/git-annex.mdwn
@@ -1719,8 +1719,8 @@ Remotes are configured using these settings in `.git/config`.
 
 * `annex.youtube-dl-options`
 
-  Options to pass to youtube-dl when using it to find the url to download
-  for a video.
+  Options to pass to youtube-dl (or yt-dlp) when using it to find the url
+  to download for a video.
 
   Some options may break git-annex's integration with youtube-dl. For
   example, the --output option could cause it to store files somewhere
@@ -1730,7 +1730,8 @@ Remotes are configured using these settings in `.git/config`.
 
 * `annex.youtube-dl-command`
 
-  Command to run for youtube-dl. Default is "youtube-dl".
+  Command to run for youtube-dl. Default is to use "youtube-dl" or 
+  if that is not available in the PATH, to use "yt-dlp".
 
 * `annex.aria-torrent-options`
 
-- 
2.38.1

From 43f681d4c15221096975250c0809ded40bf8a5fd Mon Sep 17 00:00:00 2001
From: Joey Hess 
Date: Mon, 21 Nov 2022 15:04:36 -0400
Subject: [PATCH 2/2] Support parsing yt-dpl output to display download
 progress

Before this fix, no progress was displayed when yt-dpl was used.

Sponsored-by: Graham Spencer on Patreon
---
 Annex/YoutubeDl.hs | 11 ---
 CHANGELOG  |  1 +
 2 files changed, 9 insertions(+), 3 deletions(-)

diff --git a/Annex/YoutubeDl.hs b/Annex/YoutubeDl.hs
index ba050d4024..c6d0f2253e 100644
--- a/Annex/YoutubeDl.hs
+++ b/Annex/YoutubeDl.hs
@@ -265,8 +265,10 @@ supportedScheme uo url = case parseURIRelaxed url of
 		_ -> allowedScheme uo u
 
 {- Strategy: Look for chunks prefixed with \r, which look approximately
- - like this:
+ - like this for youtube-dl:
  - "ESC[K[download]  26.6% of 60.22MiB at 254.69MiB/s ETA 00:00"
+ - or for yt-dlp, like this:
+ - "\r[download]   1.8% of1.14GiB at1.04MiB/s ETA 18:23"
  - Look at the number before "% of " and the number and unit after,
  - to determine the number of bytes.
  -}
@@ -292,8 +294,11 @@ parseYoutubeDlProgress = go [] . reverse . progresschunks
 	calc percent total = round (percent * fromIntegral total / 100)
 
 	

Bug#1024582: ITP: r-cran-ggrastr -- Bioconductor rasterize layers for 'ggplot2'

2022-11-21 Thread Andreas Tille
Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-ggrastr -- Bioconductor rasterize layers for 'ggplot2'
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: r-cran-ggrastr
  Version : 1.0.1
  Upstream Author : Viktor Petukhov,
* URL : https://cran.r-project.org/package=ggrastr
* License : MIT
  Programming Lang: GNU R
  Description : Bioconductor rasterize layers for 'ggplot2'
 Rasterize only specific layers of a 'ggplot2' plot while simultaneously
 keeping all labels and text in vector format. This allows users to keep
 plots within the reasonable size limit without loosing vector properties
 of the scale-sensitive information.

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



Bug#1022114: RFH: highlight -- Universal source code to formatted text converter

2022-11-21 Thread Daniel Echeverri
Hello David!

El lun, 7 nov 2022 a la(s) 21:14, Daniel Echeverri (epsi...@debian.org)
escribió:

> Hello Again!
>
> El lun, 7 nov 2022 a la(s) 13:57, Daniel Echeverri (epsi...@debian.org)
> escribió:
>
>> Hello!
>>
>> El jue, 20 oct 2022 a la(s) 05:33, David Bremner (brem...@debian.org)
>> escribió:
>>
>>> Package: wnpp
>>> Severity: normal
>>> X-Debbugs-Cc: debian-de...@lists.debian.org
>>> Control: affects -1 src:highlight
>>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA256
>>>
>>> I request assistance with maintaining the highlight package.
>>>
>>> I have not really been keeping up with new upstream releases and could
>>> use a co-maintainer.
>>>
>>> The package description is:
>>>  A utility that converts sourcecode to HTML, XHTML, RTF, LaTeX, TeX,
>>>  SVG, XML or terminal escape sequences with syntax highlighting.  It
>>>  supports several programming and markup languages.  Language
>>>  descriptions are configurable and support regular expressions.  The
>>>  utility offers indentation and reformatting capabilities.  It is
>>>  easily possible to create new language definitions and colour themes.
>>>
>>>
>>> -BEGIN PGP SIGNATURE-
>>>
>>> iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmNRIyoACgkQA0U5G1Wq
>>> FSGyjQ/8CbUEHtTj0Rad0xZAdVULj9B3EqJN9H35YyUatq85rbdJ69p1cMLgWiu0
>>> hQbypoCRyn+swf30+Slc7X8tIlmKoqxkDJOiqGl5uLdgEUmMB5Ael89ZUCQU+yh5
>>> m2BPAYWb6AuU0uJPPXBGIfIcw54ZtzzGMarvgd7PTlxEOYBaSZo+mkzO4YB/AoXc
>>> xLSSXUp8mW3kqQoQEtyJ5NlwfFVoaERUIJcJXHurtd3wWk8NCbqau+10/m/oyem8
>>> AzRHzEzu8FsIadYlK6jyvCtcuHY6WwEVnA++qsWd92CjBza2nmb2bjS8bgRRC/JS
>>> K/gcK2bf2zA2J4o6BKJgfSmTO9rzp0hb4CwYv/91ecM/rNB8mBvUIYzZn1caKbGZ
>>> N758k9HcyMDywEdZ8Ue2fl0hmYg0/skO7FJEB2TIfnAhqJlQ6n+MexRLIVTAJ8zW
>>> 1omcULUhnW3c6IdK8WmM6DuX76iO1QGkrslMU3opsKvy8G4jOyp8l3qh3oqd6uWj
>>> hXknT5lPaE936qd6xDn2dy4niB07W0FhSWBpb9jb3nb5G1pkoWbx/iRjmRT+v0KU
>>> QB50EoNYZDVWw9AyI0wTkU3NwanWWIggG6lpripCoirxaqlDkkJxe5VH0N9fZncZ
>>> irLYONNifkBHonshPaDgIYGTN5U55NlaVPs58p95GGvNw+61dmg=
>>> =GkDM
>>> -END PGP SIGNATURE-
>>>
>>>
>> My perl skills maybe aren't the highest but my desire to help is yes :)
>> so  if you agree I could co-maintain highlight with you,
>>
>> I am working in a new revision, I will push the changes to Salsa soon.
>>
>> Regards.
>>
>>
>
>  Could you give me access to salsa repo? or Do you agree if we move this
> repo to Debian Group?
>
> Regards.
>
> --
> Daniel Echeverri
> Debian Developer
> Linux user: #477840
> GPG Fingerprint:
> D0D0 85B1 69C3 BFD9 4048 58FA 21FC 2950 4B52 30DB
>

Could I move the repo to the Debian Group?

Regards

-- 
Daniel Echeverri
Debian Developer
Linux user: #477840
GPG Fingerprint:
D0D0 85B1 69C3 BFD9 4048 58FA 21FC 2950 4B52 30DB


Bug#1024581: Acknowledgement (linux-image-6.0.0-0.deb11.2-amd64: System freeze)

2022-11-21 Thread Felicia P
Sorry the initial report was terse because I tried to get the bug sent 
out while running the buggy kernel before it froze.


Here is some more information:

In syslog there are messages like the following:

Message from syslogd@compute2 at Nov 21 08:38:58 ...
 kernel:[  256.407191] watchdog: BUG: soft lockup - CPU#10 stuck for 
44s! [kwor

ker/u48:0:9]

Message from syslogd@compute2 at Nov 21 08:39:18 ...
 kernel:[  276.291100] watchdog: BUG: soft lockup - CPU#1 stuck for 
23s! [migration/1:21]


Message from syslogd@compute2 at Nov 21 08:39:26 ...
 kernel:[  284.407071] watchdog: BUG: soft lockup - CPU#10 stuck for 
70s! [kworker/u48:0:9]


Message from syslogd@compute2 at Nov 21 08:39:46 ...
 kernel:[  304.291026] watchdog: BUG: soft lockup - CPU#1 stuck for 
49s! [migration/1:21]



The machine is a SuperMicro SYS-1028R-WTNR server

Please let me know if I can provide any more info.

--
Felicia



Bug#1024581: linux-image-6.0.0-0.deb11.2-amd64: System freeze

2022-11-21 Thread Felicia
Package: src:linux
Version: 6.0.3-1~bpo11+1
Severity: normal

Dear Maintainer,

System freezes


-- Package-specific info:
** Version:
Linux version 6.0.0-0.deb11.2-amd64 (debian-ker...@lists.debian.org) (gcc-10 
(Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 
SMP PREEMPT_DYNAMIC Debian 6.0.3-1~bpo11+1 (2022-10-29)

** Command line:
BOOT_IMAGE=/@rootfs/boot/vmlinuz-6.0.0-0.deb11.2-amd64 
root=UUID=40ced9ef-9c89-48b6-8818-289ad6db5ec9 ro rootflags=subvol=@rootfs quiet

** Not tainted

** Kernel log:
[4.350874] ast :07:00.0: [drm] AST 2400 detected
[4.350885] ast :07:00.0: [drm] Using analog VGA
[4.350886] ast :07:00.0: [drm] dram MCLK=396 Mhz type=1 bus_width=16
[4.354961] [drm] Initialized ast 0.1.0 20120228 for :07:00.0 on minor 0
[4.364655] fbcon: astdrmfb (fb0) is primary device
[4.392176] Console: switching to colour frame buffer device 128x48
[4.392944] ast :07:00.0: [drm] fb0: astdrmfb frame buffer device
[4.421776] RAPL PMU: API unit is 2^-32 Joules, 2 fixed counters, 655360 ms 
ovfl timer
[4.421781] RAPL PMU: hw unit of domain package 2^-14 Joules
[4.421783] RAPL PMU: hw unit of domain dram 2^-16 Joules
[4.424989] cryptd: max_cpu_qlen set to 1000
[4.436392] AVX2 version of gcm_enc/dec engaged.
[4.436457] AES CTR mode by8 optimization enabled
[4.796186] ipmi_si IPI0001:00: The BMC does not support clearing the recv 
irq bit, compensating, but the BMC needs to be fixed.
[4.895862] ipmi_si IPI0001:00: IPMI message handler: Found new BMC (man_id: 
0x002a7c, prod_id: 0x0864, dev_id: 0x20)
[4.932277] EDAC sbridge: Seeking for: PCI ID 8086:2fa0
[4.932294] EDAC sbridge: Seeking for: PCI ID 8086:2fa0
[4.932324] EDAC sbridge: Seeking for: PCI ID 8086:2fa0
[4.932356] EDAC sbridge: Seeking for: PCI ID 8086:2f60
[4.932373] EDAC sbridge: Seeking for: PCI ID 8086:2fa8
[4.932379] EDAC sbridge: Seeking for: PCI ID 8086:2fa8
[4.932389] EDAC sbridge: Seeking for: PCI ID 8086:2fa8
[4.932397] EDAC sbridge: Seeking for: PCI ID 8086:2f71
[4.932403] EDAC sbridge: Seeking for: PCI ID 8086:2f71
[4.932412] EDAC sbridge: Seeking for: PCI ID 8086:2f71
[4.932419] EDAC sbridge: Seeking for: PCI ID 8086:2faa
[4.932424] EDAC sbridge: Seeking for: PCI ID 8086:2faa
[4.932432] EDAC sbridge: Seeking for: PCI ID 8086:2faa
[4.932439] EDAC sbridge: Seeking for: PCI ID 8086:2fab
[4.932444] EDAC sbridge: Seeking for: PCI ID 8086:2fab
[4.932452] EDAC sbridge: Seeking for: PCI ID 8086:2fab
[4.932459] EDAC sbridge: Seeking for: PCI ID 8086:2fac
[4.932464] EDAC sbridge: Seeking for: PCI ID 8086:2fac
[4.932472] EDAC sbridge: Seeking for: PCI ID 8086:2fac
[4.932480] EDAC sbridge: Seeking for: PCI ID 8086:2fad
[4.932485] EDAC sbridge: Seeking for: PCI ID 8086:2fad
[4.932493] EDAC sbridge: Seeking for: PCI ID 8086:2fad
[4.932500] EDAC sbridge: Seeking for: PCI ID 8086:2f68
[4.932505] EDAC sbridge: Seeking for: PCI ID 8086:2f79
[4.932520] EDAC sbridge: Seeking for: PCI ID 8086:2f6a
[4.932533] EDAC sbridge: Seeking for: PCI ID 8086:2f6b
[4.932547] EDAC sbridge: Seeking for: PCI ID 8086:2f6c
[4.932561] EDAC sbridge: Seeking for: PCI ID 8086:2f6d
[4.932574] EDAC sbridge: Seeking for: PCI ID 8086:2ffc
[4.932578] EDAC sbridge: Seeking for: PCI ID 8086:2ffc
[4.932586] EDAC sbridge: Seeking for: PCI ID 8086:2ffc
[4.932594] EDAC sbridge: Seeking for: PCI ID 8086:2ffd
[4.932599] EDAC sbridge: Seeking for: PCI ID 8086:2ffd
[4.932608] EDAC sbridge: Seeking for: PCI ID 8086:2ffd
[4.932618] EDAC sbridge: Seeking for: PCI ID 8086:2fbd
[4.932624] EDAC sbridge: Seeking for: PCI ID 8086:2fbd
[4.932633] EDAC sbridge: Seeking for: PCI ID 8086:2fbd
[4.932640] EDAC sbridge: Seeking for: PCI ID 8086:2fbf
[4.932647] EDAC sbridge: Seeking for: PCI ID 8086:2fbf
[4.932656] EDAC sbridge: Seeking for: PCI ID 8086:2fbf
[4.932665] EDAC sbridge: Seeking for: PCI ID 8086:2fb9
[4.932672] EDAC sbridge: Seeking for: PCI ID 8086:2fb9
[4.932680] EDAC sbridge: Seeking for: PCI ID 8086:2fb9
[4.932686] EDAC sbridge: Seeking for: PCI ID 8086:2fbb
[4.932693] EDAC sbridge: Seeking for: PCI ID 8086:2fbb
[4.932700] EDAC sbridge: Seeking for: PCI ID 8086:2fbb
[4.932832] EDAC MC0: Giving out device to module sb_edac controller Haswell 
SrcID#1_Ha#0: DEV :ff:12.0 (INTERRUPT)
[4.932978] EDAC MC1: Giving out device to module sb_edac controller Haswell 
SrcID#0_Ha#0: DEV :7f:12.0 (INTERRUPT)
[4.932981] EDAC sbridge:  Ver: 1.1.2 
[4.997520] ipmi_si IPI0001:00: IPMI kcs interface initialized
[5.014898] ipmi_ssif: IPMI SSIF Interface driver
[5.094960] intel_rapl_common: Found RAPL domain package
[5.094970] intel_rapl_common: Found RAPL domain dram
[5.094976] intel_rapl_common: DRAM domain energy unit 15300pj
[5.095185] intel_rapl_common: Found RAPL domain package
[   

Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries

2022-11-21 Thread Lisandro Damián Nicanor Pérez Meyer
Hi,

On Wed, 9 Nov 2022 at 15:13, Soren Stoutner  wrote:
[snip]
> This would also require the the Debain Qt/KDE Maintainers add a symlink from /
> usr/share/qt5/qtwebengine_dictionaries and /usr/share/qt6/
> qtwebengine_dictionaries to /usr/share/hunspell-bdic.  They can do this in
> whatever package makes the most sense to them, but possibly in
> libqt5webengine-data and libqt6webengine6-data.

The problem is not a symlink, but building and testing qt[5 6]webkit
with this change. Maybe building is not an issue as we could just
remove the bdic files and add the symlink... but someone who really
understands what's going on under the hood should do a very careful
test to see things are working.



Bug#1024580: r-bioc-affxparser: FTBFS on hppa - cannot handle R_PARISC_PCREL17F

2022-11-21 Thread John David Anglin
Source: r-bioc-affxparser
Version: 1.70.0-1
Severity: normal
Tags: ftbfs patch

Dear Maintainer,

Build fails here:
g++ -std=gnu++14 -shared -L/usr/lib/R/lib -o affxparser.so 
fusion/calvin_files/data/src/CDFData.o 
fusion/calvin_files/data/src/CDFProbeGroupInformation.o 
fusion/calvin_files/data/src/CDFProbeInformation.o 
fusion/calvin_files/data/src/CDFProbeSetInformation.o 
fusion/calvin_files/data/src/CDFQCProbeInformation.o 
fusion/calvin_files/data/src/CDFQCProbeSetInformation.o 
fusion/calvin_files/data/src/CELData.o 
fusion/calvin_files/data/src/CHPBackgroundZone.o 
fusion/calvin_files/data/src/CHPData.o 
fusion/calvin_files/data/src/CHPExpressionEntry.o 
fusion/calvin_files/data/src/CHPMultiDataData.o 
fusion/calvin_files/data/src/CHPTilingData.o 
fusion/calvin_files/data/src/CHPQuantificationData.o 
fusion/calvin_files/data/src/CHPQuantificationDetectionData.o 
fusion/calvin_files/data/src/CHPGenotypeEntry.o 
fusion/calvin_files/data/src/CHPUniversalEntry.o 
fusion/calvin_files/data/src/ColumnInfo.o 
fusion/calvin_files/data/src/DataGroup.o 
fusion/calvin_files/data/src/DataGroupHeader.o 
fusion/calvin_files/data/src/DataSet.o 
fusion/calvin_files/data/src/DataSetHeader.o 
fusion/calvin_files/data/src/FileHeader.o 
fusion/calvin_files/data/src/GenericData.o 
fusion/calvin_files/data/src/GenericDataHeader.o 
fusion/calvin_files/exception/src/ExceptionBase.o 
fusion/calvin_files/fusion/src/CalvinAdapter/CalvinCELDataAdapter.o 
fusion/calvin_files/fusion/src/CalvinAdapter/CalvinCHPDataAdapter.o 
fusion/calvin_files/fusion/src/FusionBPMAPData.o 
fusion/calvin_files/fusion/src/FusionCDFData.o 
fusion/calvin_files/fusion/src/FusionCDFQCProbeSetNames.o 
fusion/calvin_files/fusion/src/FusionCELData.o 
fusion/calvin_files/fusion/src/FusionCHPData.o 
fusion/calvin_files/fusion/src/FusionProbeSetResults.o 
fusion/calvin_files/fusion/src/GCOSAdapter/GCOSCELDataAdapter.o 
fusion/calvin_files/fusion/src/GCOSAdapter/GCOSCHPDataAdapter.o 
fusion/calvin_files/fusion/src/FusionCHPLegacyData.o 
fusion/calvin_files/fusion/src/FusionCHPMultiDataAccessor.o 
fusion/calvin_files/fusion/src/FusionCHPMultiDataData.o 
fusion/calvin_files/fusion/src/FusionCHPTilingData.o 
fusion/calvin_files/fusion/src/FusionCHPGenericData.o 
fusion/calvin_files/fusion/src/FusionCHPQuantificationData.o 
fusion/calvin_files/fusion/src/FusionCHPQuantificationDetectionData.o 
fusion/calvin_files/parameter/src/ParameterNameValueType.o 
fusion/calvin_files/parsers/src/CDFFileReader.o 
fusion/calvin_files/parsers/src/CelFileReader.o 
fusion/calvin_files/parsers/src/CHPFileReader.o 
fusion/calvin_files/parsers/src/CHPMultiDataFileReader.o 
fusion/calvin_files/parsers/src/CHPTilingFileReader.o 
fusion/calvin_files/parsers/src/CHPQuantificationFileReader.o 
fusion/calvin_files/parsers/src/CHPQuantificationDetectionFileReader.o 
fusion/calvin_files/parsers/src/DataGroupHeaderReader.o 
fusion/calvin_files/parsers/src/DataGroupReader.o 
fusion/calvin_files/parsers/src/DataSetHeaderReader.o 
fusion/calvin_files/parsers/src/DataSetReader.o 
fusion/calvin_files/parsers/src/FileHeaderReader.o 
fusion/calvin_files/parsers/src/FileInput.o 
fusion/calvin_files/parsers/src/GenericDataHeaderReader.o 
fusion/calvin_files/parsers/src/GenericFileReader.o 
fusion/calvin_files/utils/src/AffymetrixGuid.o 
fusion/calvin_files/utils/src/DateTime.o 
fusion/calvin_files/utils/src/FileUtils.o 
fusion/calvin_files/utils/src/StringUtils.o 
fusion/calvin_files/utils/src/checksum.o fusion/file/BPMAPFileData.o 
fusion/file/BPMAPFileWriter.o fusion/file/CDFFileData.o 
fusion/file/CELFileData.o fusion/file/CHPFileData.o fusion/file/FileIO.o 
fusion/file/FileWriter.o fusion/file/TsvFile/ClfFile.o 
fusion/file/TsvFile/PgfFile.o fusion/file/TsvFile/TsvFile.o 
fusion/util/AffxByteArray.o fusion/util/AffxConv.o fusion/util/MsgStream.o 
fusion/util/Util.o fusion/util/Err.o fusion/util/Fs.o fusion/util/Verbose.o 
fusion/util/RowFile.o fusion/util/TableFile.o fusion/util/Convert.o 
R_affx_cel_parser.o R_affx_cdf_parser.o R_affx_cdf_extras.o 
R_affx_bpmap_parser.o R_affx_clf_pgf_parser.o R_affx_chp_parser.o 000.init.o 
-L/usr/lib/R/lib -lR
/usr/bin/ld: 
fusion/calvin_files/data/src/CHPQuantificationData.o(.text._ZN20affymetrix_calvin_io21CHPQuantificationData10AddColumnsERNS_13DataSetHeaderEb+0x6c):
 cannot reach 
231f__ZN20affymetrix_calvin_io13DataSetHeader14AddAsciiColumnERKNSt7__cxx1112basic_stringIwSt11char_traitsIwESaIwEEEi+0,
 recompile with -ffunction-sections
/usr/bin/ld: 
fusion/calvin_files/data/src/CHPQuantificationData.o(.text._ZN20affymetrix_calvin_io21CHPQuantificationData10AddColumnsERNS_13DataSetHeaderEb+0x6c):
 cannot handle R_PARISC_PCREL17F for 
_ZN20affymetrix_calvin_io13DataSetHeader14AddAsciiColumnERKNSt7__cxx1112basic_stringIwSt11char_traitsIwESaIwEEEi
/usr/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit status
make[2]: *** [/usr/share/R/share/make/shlib.mk:10: affxparser.so] Error 1

Full log is here:

Bug#1022248: transition: icu

2022-11-21 Thread GCS
On Tue, Nov 8, 2022 at 2:00 AM Sebastian Ramacher  wrote:
> On 2022-10-30 14:08:55 +0100, László Böszörményi wrote:
> > Package 0ad and gnucash fail to build [1][2] with ICU 72.1 and bugs are 
> > filed.
> > Package supercollider failed to build due to another issue [3]. Its
> > packaging Git has a working fix and after applying that it was built
> > with ICU 72.1 as well.
>
> Alright, please go ahead.
 Friendly ping on what needs to be done for this transition? ICU
itself migrated to testing more than a week ago. Thunderbird, the last
reverse dependency needed  for this transition, just migrated. Other
reverse dependencies are already Sid only. How can I check what's
still missing?

Thanks,
Laszlo/GCS



Bug#1010544: victoriametrics: FTBFS on armel

2022-11-21 Thread Antoine Beaupré
Seems to me we could just kick armel out of the supported architectures
for this package for now... I think we'd need to downgrade the severity
of this bug report, and remove the armel package from testing.

What do people think here?
-- 
Never believe that a few caring people can't change the world. For,
indeed, that's all who ever have.
- Margaret Mead



Bug#1023731: BioC Transition blocked by new dependencies

2022-11-21 Thread Sebastian Ramacher
On 2022-11-21 16:39:26 +0100, Andreas Tille wrote:
> Hi Sebastian,
> 
> Am Mon, Nov 21, 2022 at 03:05:26PM +0100 schrieb Sebastian Ramacher:
> > On 2022-11-21 15:02:16 +0100, Andreas Tille wrote:
> > > Control: block -1 by 1024563
> > > Control: block -1 by 1024565
> > > Control: block -1 by 1024567
> > > 
> > > Some of the BioConductor packages need new dependencies.
> > > I have pushed these to new queue and set the ITP bugs as
> > > blocker.
> > 
> > As this is happening every r-bioc transition, could this be handled
> > before starting the transition the next time?
> 
> This is really hard to do, thought.  The new packages are needing those
> packages from the transition.  I actually injected two packages from
> higher levels manually to be able to build one of the new packages.  So
> we really need to upload the start of the transition and I do not see
> any sense in not documenting what we are doing without the transition
> tracker.

Others have already answered this part.

> However, to make us understand your suggestion better:  Is there any
> drawback on your side if the transition of a closed set of packages if
> the transition is delayed by new processing?

Some packages are also involved in other transitions. For example,
currently a hdf5 transition is prepared in experimental. While we could
now also start the hdf5 transition, completing hdf5 would not be
possible until this one is done.

Now replace the hdf5 transition with another lock-step transition such
as this one. Then we suddenly have two set of packages that can only
migrate together. Especially for lock-step transition a quick turn
around is thus greatly appreciated.

I will remember for the next time that I'll ask you to stage everything
in experimental or to give me a list of packages that require NEW
dependencies so that we can get those removed early in the transition to
not hold of the transition by NEW delay.

Cheers
-- 
Sebastian Ramacher



Bug#1023550: transition: qcustomplot

2022-11-21 Thread Sebastian Ramacher
Hi Filippo

On 2022-11-21 09:58:08 +0100, Filippo Rusconi wrote:
> > > > > For the libs under my control, the transition is already prepared and 
> > > > > these
> > > > > projects are going to be linking against the Qt6-built library, 
> > > > > contrary to all
> > > > > the other packages detailed below.
> > > > >
> > > > > For the other libs listed above, I have already checked that they 
> > > > > would build if
> > > > > some modifications were performed. I have already git branches ready 
> > > > > for the
> > > > > packages under git VCS. For the others (source deb), I have patches 
> > > > > available.
> > > > >
> > > > > The modifications are lean: change -lqcustomplot to -lQCustomPlot for 
> > > > > many and
> > > > > also sometimes use the CMake-based configuration involving first
> > > > > find_package(QCustomPlot) and second the QCustomPlot::QCustomPlot 
> > > > > formalism for
> > > > > the linker.
> > > > >
> > > > > That is: almost one- or two-liner patches.
> > > >
> > > > Could you please file bugs for those so that maintainers are aware?
> > > 
> > > Yes, I'll do that. I have already informed them individually of the 
> > > process and
> > > provided them with the relevant patch.
> > 
> > Thanks! Please go ahead with the transition.
> 
> I'm sorry, what should I do? Shall I upload the package to unstable?

Yes, please upload the package to unstable to start the transition.

Cheers
-- 
Sebastian Ramacher



Bug#1023678: clasp: diff for NMU version 3.3.5-4.2

2022-11-21 Thread Nilesh Patra
On Sat, 19 Nov 2022 12:14:16 +0200 Adrian Bunk  wrote:
> Control: tags 1023678 + patch
> Control: tags 1023678 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for clasp (versioned as 3.3.5-4.2) and uploaded
> it to DELAYED/15. Please feel free to tell me if I should cancel it.

This is a science team package, and I am not quite sure if the uploader
is gonna respond. I have granted you push access to the corresponding repo
of this package.
Will you please commit your NMU (after it is accepted) to the salsa repo?

Thanks!

-- 
Best,
Nilesh


signature.asc
Description: PGP signature


Bug#1006457: closed by Willem Mulder (Re: Bug#1006457: Chromium fails to start on aarch64 systems)

2022-11-21 Thread MichaIng

Great, also solved here, many thanks!

Best regards,

Micha



Bug#1024579: mcabber: Loses gpgme integration when rebuilt against gpgme 1.18.0-2

2022-11-21 Thread Andreas Metzler
Source: mcabber
Version: 1.1.2-2
Severity: important
Tags: patch
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gpgme-config-transition

The packages ships an outdated version of gpgme.m4 in macros/gpgme.m4
which cannot handle the transition from gpgme-config to gpgrt-config.
Deleting the outdated copy fixes the issue.

cu Andreas



Bug#1024578: mandos: FTBFS against libgpgme-dev >= 1.18.0-2

2022-11-21 Thread Andreas Metzler
Source: mandos
Version: 1.8.15-1.1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gpgme-config-transition

The package relies on gpgme-config to detect gpgme. gpgme-config has been
dropped and replaced by pkg-config pc files.

cu Andreas
--- mandos-1.8.15.orig/Makefile
+++ mandos-1.8.15/Makefile
@@ -96,8 +96,8 @@ GNUTLS_CFLAGS:=$(shell $(PKG_CONFIG) --c
 GNUTLS_LIBS:=$(shell $(PKG_CONFIG) --libs gnutls)
 AVAHI_CFLAGS:=$(shell $(PKG_CONFIG) --cflags-only-I avahi-core)
 AVAHI_LIBS:=$(shell $(PKG_CONFIG) --libs avahi-core)
-GPGME_CFLAGS:=$(shell gpgme-config --cflags; getconf LFS_CFLAGS)
-GPGME_LIBS:=$(shell gpgme-config --libs; getconf LFS_LIBS; \
+GPGME_CFLAGS:=$(shell $(PKG_CONFIG) --cflags-only-I gpgme; getconf LFS_CFLAGS)
+GPGME_LIBS:=$(shell $(PKG_CONFIG) --libs gpgme; getconf LFS_LIBS; \
 	getconf LFS_LDFLAGS)
 LIBNL3_CFLAGS:=$(shell $(PKG_CONFIG) --cflags-only-I libnl-route-3.0)
 LIBNL3_LIBS:=$(shell $(PKG_CONFIG) --libs libnl-route-3.0)


Bug#924685: RFP: cumin -- An automation and orchestration framework

2022-11-21 Thread Moritz Mühlenhoff
Antoine wrote:

Thanks! I would put that in the Python team, is that okay? Probably next
> week too.
>

Sure, Python team sounds good to me as well.

Cheers,
Moritz


Bug#1024547: ITP: sparrow -- Bitcoin wallet with a focus on privacy and usability

2022-11-21 Thread Sam Hartman
> "craig" == craig   writes:

craig> Inclusion into the Debian repository is a precursor to
craig> inclusion into Tails, which has been broadly requested in the
craig> Bitcoin community.  Sparrow is already released as a .deb
craig> package (see https://sparrowwallet.com/downloads/) as part of
craig> the standard release process.  I intend to maintain this
craig> package going forward.

In the past we've had a bit of trouble with bitcoin wallets in Debian
when security issues emerged.  If this package makes it into Debian
stable, will you be able to provide security support for the version in
stable without upgrading to new upstream versions for the release
lifetime of stable?


signature.asc
Description: PGP signature


Bug#1023889: libimage-exiftool-perl: exiftool ignores GPSLongitudeRef option

2022-11-21 Thread Andreas Tille
Hi Gregor,

Am Mon, Nov 21, 2022 at 06:26:39PM +0100 schrieb gregor herrmann:
> On Wed, 16 Nov 2022 11:14:11 -0500, Phil Harvey wrote:
> 
> > Yes, I considered your suggestions.  Adding a warning wasn't feasible.  I 
> > actually did update the documentation (the only place this is really 
> > documented is in FAQ 14):
> > https://exiftool.org/faq.html#Q14
> 
> Thanks Andreas for the bug report and your input, and thanks Phil for
> your quick replies and all the considerations you gave and give to
> this issue.
> 
> I guess there's not much I can do from the packaging side; and I
> assume I'll close the bug once the updated html/faq.html is in a
> released tarball.

Fully ACK.

Kind regards
   Andreas.

-- 
http://fam-tille.de



Bug#1024577: libzypp: FTBFS against libgpgme-dev >= 1.18.0-2

2022-11-21 Thread Andreas Metzler
Source: libzypp
Version: 17.25.7-2.2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gpgme-config-transition

The package relies on gpgme-config to detect gpgme. gpgme-config has been
dropped and replaced by pkg-config pc files.

I would suggest following #1024417 where the same cmake module seems to
be used.

cu Andreas



Bug#990828: mutt can not delete mails due to access rights

2022-11-21 Thread Kevin J. McCarthy

On Mon, Nov 21, 2022 at 02:53:14PM +0100, Juan Pedro Vallejo wrote:

Yes, you were right.

Architecture: i386 (i686)


Thank you Juan.  So you are running the i386 mutt package on an i386 
architecture.  I believe this means something is wrong the package 
building environment.


I've just looked again at the Mutt configure/makefile related to 
mutt_dotlock, and it turns out Mutt always installs as group 'mail' when 
setting sgid:


configure.ac:
=
if test x$mutt_cv_setgid = xyes; then
DOTLOCK_GROUP='mail'
DOTLOCK_PERMISSION=2755
else
DOTLOCK_GROUP=''
DOTLOCK_PERMISSION=755
fi
AC_SUBST(DOTLOCK_GROUP)
AC_SUBST(DOTLOCK_PERMISSION)

Makefile.am:

if test -f $(DESTDIR)$(bindir)/mutt_dotlock && test x$(DOTLOCK_GROUP) 
!= x ; then \
chgrp $(DOTLOCK_GROUP) $(DESTDIR)$(bindir)/mutt_dotlock && \
chmod $(DOTLOCK_PERMISSION) $(DESTDIR)$(bindir)/mutt_dotlock || 
\
{ echo "Can't fix mutt_dotlock's permissions!  This is required to lock 
mailboxes in the mail spool directory." >&2 ; exit 1 ; } \
fi


The content of the various mutt deb files:
==
% for deb in *; do echo $deb; dpkg -c $deb | grep bin/mutt_dotlock; echo; done
mutt_2.2.9-1_amd64.deb
-rwxr-sr-x root/mail 14584 2022-11-13 09:01 ./usr/bin/mutt_dotlock

mutt_2.2.9-1_arm64.deb
-rwxr-sr-x root/mail 67680 2022-11-13 09:01 ./usr/bin/mutt_dotlock

mutt_2.2.9-1_armel.deb
-rwxr-sr-x root/root 67108 2022-11-13 09:01 ./usr/bin/mutt_dotlock

mutt_2.2.9-1_armhf.deb
-rwxr-sr-x root/root 67120 2022-11-13 09:01 ./usr/bin/mutt_dotlock

mutt_2.2.9-1_i386.deb
-rwxr-sr-x root/root 13804 2022-11-13 09:01 ./usr/bin/mutt_dotlock

mutt_2.2.9-1_mips64el.deb
-rwxr-sr-x root/mail 68648 2022-11-13 09:01 ./usr/bin/mutt_dotlock

mutt_2.2.9-1_mipsel.deb
-rwxr-sr-x root/root 67732 2022-11-13 09:01 ./usr/bin/mutt_dotlock

mutt_2.2.9-1_ppc64el.deb
-rwxr-sr-x root/mail 67760 2022-11-13 09:01 ./usr/bin/mutt_dotlock

mutt_2.2.9-1_s390x.deb
-rwxr-sr-x root/mail 14432 2022-11-13 09:01 ./usr/bin/mutt_dotlock


I'm not sure what is going wrong, but armel, armhf, i386, and mipsel are 
failing to chgrp to mail during the package building.


Antonio I'll need your help to figure out what is going on in this case. 
Since this renders the program unusable for working with spoolfile mail, 
I think this ought to be bumped to 'serious'.


-Kevin



signature.asc
Description: PGP signature


Bug#1023731: BioC Transition blocked by new dependencies

2022-11-21 Thread Nilesh Patra
On Mon, Nov 21, 2022 at 06:11:41PM +0100, Andreas Tille wrote:
> Hi Adrian and others,
> 
> Am Mon, Nov 21, 2022 at 06:33:52PM +0200 schrieb Adrian Bunk:
> > > This is really hard to do, thought.  The new packages are needing those
> > > packages from the transition.  I actually injected two packages from
> > > higher levels manually to be able to build one of the new packages.  So
> > > we really need to upload the start of the transition and I do not see
> > > any sense in not documenting what we are doing without the transition
> > > tracker.
> > >...
> > 
> > Your transition is special because you are manually uploading every 
> > single package involved in the transition.
> > 
> > You could upload everything to experimental, run a local ben tracker 
> > against experimental, and when the transition is complete in 
> > experimental contact the release team for the transition in unstable.
> > 
> > The actual transition is then a batch of "Upload to unstable".
> 
> Thanks for all helpful hints.  I understand that with some effort over
> the current workflow it is possible to do the transition differently.
> The only thing which I did not yet understood is the actual drawback of
> the current workflow.  I do not think that it takes specifically longer
> than other transition - we just have a different set of showstoppers to
> get it done in 24 hours. 

Personal experience+opinion: I have been involved with quite a few bioc 
transitions
and often times you and me were the _only_ people who did the entire transition.

I have noticed several times that the NEW processing takes quite sometime, and 
the way
forward (for me) has been to manually patch the DESCRIPTION file to patch it to 
be
compatible with new r-bioc api until the dependency from new is accepted.

The new processing time tends to create delay with respect to bioc packages 
migrating
to testing and this creats a terrible amount of noise. And then what comes next 
is
a bunch of workarounds to get things moving, and this takes a quite a lot of 
energy
at my end which I'd like to spend somewhere else. I have not been entirely 
happy with the
way it happens, and would like if we can do the transition differently with 
less friction,
less days of wide-uninstallability.

The advantage with a reprepo thing that Sebastian suggests is that everything 
(possibly)
will migrate as soon as it is uploaded. Once you have stored the sources into a 
reprepo,
all you need to do is run a script to do all the uploads.

> In the past we got support by ftpmaster when
> pinging them and explaining the transition issue.

Which takes time as well, and at least my experience regarding transition new 
processing
has not been quite same as you.

Lastly I also want to higlight that: while bioc transition is in theory a 
transition (I agree)
but to my understanding, there is no _real_ API change. It is just the tool 
taking the
API field from DESCRIPTION file into consideration, and causing FTBFS if it 
does not match.

In principle, building a package that has an older API value in DESCRIPTION 
file with the newer
one does not break anything, it rather looks as updates of various packages 
disguised as an API
change, and at least in debian land, to me it just appears as a broken tool 
config and not a real
transition (like library transition, for example the recent onetbb one).

-- 
Best,
Nilesh


signature.asc
Description: PGP signature


  1   2   >