date:20220505

David Bremner  writes:

> Nicholas D Steeves  writes:
>
>> I suspect the failing test in markdown-mode 2.5
>> (test-markdown-ext/wiki-link-search-under-project) is failing for a
>> similar reasons …
[snip]
>> … My hypothesis is
>> that upstream makes a normally-valid assumption about path handling that
>> breaks on sbuild and buildds.
>
> Sounds like we should just disable this test for now?

Sounds good to me.  Can I leave this bug to you?  I'm juggling one too
many things at the moment.  If not, please ping me in a few weeks :)

Thanks,
Nicholas


signature.asc
Description: PGP signature

Bug#1010648: RFP: golang-github-pierrec-lz4.v4 -- LZ4 compression and decompression in pure Go (v4)

Hi Shengjing Zhu and Go Packaging Team,

>
> * Package name: golang-github-pierrec-lz4.v4
>   Version : 4.1.14
>   Upstream Author : Pierre Curto
> * URL : https://github.com/pierrec/lz4
> * License : BSD-3-clause
>   Programming Lang: Go
>   Description : LZ4 compression and decompression in pure Go (v4)
>

[snip]

> This RFP is for v4 of the package referred to as "github.com/pierrec/lz4/v4". 
>  It is a dependency of newer versions of Syncthing, and will presumably 
> become a dependency of all packages that migrate away from 
> golang-github-pierrec-lz4.
>

It looks like reportbug can no longer X-Debbugs-CC wnpp bugs, so I'm
manually posting this follow-up.  As far as I can tell, the existing
golang-github-pierrec-lz4 debian/* can be copied into this package, the
copyright file updated, the watch file updated to scrape v4 tags, and
the changelog reset, which should be pretty quick! :-)

I'm not sure why uscan in the existing 2.x package isn't finding v4
versions.

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#1010648: RFP: golang-github-pierrec-lz4.v4 -- LZ4 compression and decompression in pure Go (v4)

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: s...@debian.org
Control: block 1004648 by -1

* Package name: golang-github-pierrec-lz4.v4
  Version : 4.1.14
  Upstream Author : Pierre Curto
* URL : https://github.com/pierrec/lz4
* License : BSD-3-clause
  Programming Lang: Go
  Description : LZ4 compression and decompression in pure Go (v4)

(copied from golang-github-pierrec-lz4)

 This library implements reading and writing lz4 compressed data (a frame),
 as specified in
 http://fastcompression.blogspot.fr/2013/04/lz4-streaming-format-final.html,
 using an io.Reader (decompression) and io.Writer (compression).  It is
 designed to minimize memory usage while maximizing throughput by being
 able to [de]compress data concurrently.

This RFP is for v4 of the package referred to as "github.com/pierrec/lz4/v4".  
It is a dependency of newer versions of Syncthing, and will presumably become a 
dependency of all packages that migrate away from golang-github-pierrec-lz4.

Thank you for you consideration,
Nicholas

Bug#1010490:

2022-05-05 Thread Mario Limonciello

It was validated  to be fixed in 1.8.0, but the fix is present in 1.5.8 and
later.  Debian testing has 1.7.7, which picks up this fix.

-- 
Mario Limonciello
supe...@gmail.com

Bug#1008354: fossil: FTBFS: ./conftest__.c:3: undefined reference to `sqlite3_open'

2022-05-05 Thread Nobuhiro Ban

Thank you for your reply.
Understood.  I will wait for the next release.

2022年5月5日(木) 17:14 Barak A. Pearlmutter :
>
> Yes.
>
> I patched over the issue for now by just using the internal sqlite3
> library, so I think it can wait until the next official release to
> pick up the proper bug fix and go back to using the system sqlite3
> library.

Bug#745763: license-problem-non-free-RFC: False positive when describing license conditions

2022-05-05 Thread Ben Finney

Control: retitle -1 license-problem-non-free-RFC: False positive when 
describing license conditions

On 26-Apr-2014, Lisandro Damián Nicanor Pérez Meyer wrote:
> On Sunday 27 April 2014 02:13:04 Bastien ROUCARIES wrote:
> > Moreover in this case lintian is right because this file describe
> > the license used by some of qt4-x11 code. For instance how can I
> > programatically check if README license text apply to whole
> > project or to only the README file* ?
> 
> No, lintian is not right because it is pointing to the wrong file.

Here's another example:

https://salsa.debian.org/bignose/pkg-python-irc/-/blob/main/debian/README.source#L102>

The mention of the RFC includes the copyright notice from that RFC,
for the purpose of explaining why the RFC is *not* part of the Debian
package.

So Lintian should not raise a tag for that; it is a false positive.

Please refine the Lintian check so that it does not catch documents
which *describe* license conditions and do not *claim* those
conditions on the package.

-- 
 \   “Know what I hate most? Rhetorical questions.” —Henry N. Camp |
  `\   |
_o__)  |
Ben Finney 

signature.asc
Description: PGP signature

Bug#1010628: libsm6: Missing symbolic link libSM.so (to libSM.so.6.0.1)

2022-05-05 Thread Thomas Dickey

On Thu, May 05, 2022 at 01:43:00PM -0400, Kevin Cole wrote:
> Package: libsm6

The symbolic link is provided by the development package,
and doesn't belong in the runtime.

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


signature.asc
Description: PGP signature

Bug#1010630: libice6: Missing symbolic link libICE.so (to libICE.so.6.3.0)

2022-05-05 Thread Thomas Dickey

On Thu, May 05, 2022 at 01:45:53PM -0400, Kevin Cole wrote:
> Package: libice6

The symbolic link is provided in the development package (libice-dev)

/.
/usr
/usr/include
/usr/include/X11
/usr/include/X11/ICE
/usr/include/X11/ICE/ICE.h
/usr/include/X11/ICE/ICEconn.h
/usr/include/X11/ICE/ICElib.h
/usr/include/X11/ICE/ICEmsg.h
/usr/include/X11/ICE/ICEproto.h
/usr/include/X11/ICE/ICEutil.h
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libICE.a
/usr/lib/x86_64-linux-gnu/pkgconfig
/usr/lib/x86_64-linux-gnu/pkgconfig/ice.pc
/usr/share
/usr/share/doc
/usr/share/doc/libice-dev
/usr/share/doc/libice-dev/changelog.Debian.gz
/usr/share/doc/libice-dev/changelog.gz
/usr/share/doc/libice-dev/copyright
/usr/lib/x86_64-linux-gnu/libICE.so

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


signature.asc
Description: PGP signature

Bug#999544: Package new upstream version

2022-05-05 Thread Shelikhoo

The aim of the first patch is to remove VSign signature verification, 
which requires additional dependency. It is designed to verify 
upstream's binary release and is useless on distributions since 
distributions neither creates the same binary(requires replicating 
upstream's reproducible build and applying no patching) nor generate its 
own signature. The original opengpg signature verification is no longer 
useful as we no longer create gpg signatures of our binary(gpg 
signatures do not include and verify filename or other context 
information in our old signature formats, this would allow an attacker 
to swap binaries of different versions).


This file can be simply deleted to remove verify command. (patch 1)


In addition to this, to remove dependency on VSign, executable resource 
integrity protection is also removed(patch 3). (This is not only 
designed to prevent someone from running that in an unsandboxed 
electron, but make sure we won't have merge conflict with the user's own 
version of these scripts when we update it. So removing it shouldn't 
create too many issues in Debian's case.)



To remove dependency on github.com/jhump/protoreflect, an engineering 
feature dynamic protojson loading is removed(not very useful for 
end-users)(patch 2). It is used to help users with a customized build of 
V2Ray that have configuration elements that cannot be represented by 
jsonv4 format, not distribution users.



On 5/5/2022 9:48 pm, Antoine Beaupré wrote:

On 2021-11-12 00:16:38, Alois Micard wrote:

Since Go 1.17 is now the defaults on the archive this package
fails to build.

It could be great to update to upstream 4.43.0 and backport the
following commit [1] in order to make the package build again.

I have tried to upgrade to the latest upstream (4.45) today, and failed
at the first patch because it doesn't apply. I refreshed the other two
patches and I'm waiting to hear from upstream (in CC) how to deal with
the first. I pushed my work to the debian/experimental branch on salsa:

https://salsa.debian.org/go-team/packages/golang-v2ray-core/-/merge_requests/new?merge_request%5Bsource_branch%5D=debian%2Fexperimental

a.
From 6f2fa9d9310a5d4371da7a527dd629c0c052982b Mon Sep 17 00:00:00 2001
From: Shelikhoo 
Date: Thu, 5 May 2022 22:31:40 +0100
Subject: [PATCH 1/3] Remove upstream signature verification system

---
 infra/control/verify.go | 64 -
 1 file changed, 64 deletions(-)
 delete mode 100644 infra/control/verify.go

diff --git a/infra/control/verify.go b/infra/control/verify.go
deleted file mode 100644
index 48bed7f3..
--- a/infra/control/verify.go
+++ /dev/null
@@ -1,64 +0,0 @@
-package control
-
-import (
-	"flag"
-	"os"
-
-	"github.com/v2fly/VSign/signerVerify"
-
-	"github.com/v2fly/v2ray-core/v4/common"
-)
-
-type VerifyCommand struct{}
-
-func (c *VerifyCommand) Name() string {
-	return "verify"
-}
-
-func (c *VerifyCommand) Description() Description {
-	return Description{
-		Short: "Verify if a binary is officially signed.",
-		Usage: []string{
-			"v2ctl verify --sig= file...",
-			"Verify the file officially signed by V2Ray.",
-		},
-	}
-}
-
-func (c *VerifyCommand) Execute(args []string) error {
-	fs := flag.NewFlagSet(c.Name(), flag.ContinueOnError)
-
-	sigFile := fs.String("sig", "", "Path to the signature file")
-
-	if err := fs.Parse(args); err != nil {
-		return err
-	}
-
-	target := fs.Arg(0)
-	if target == "" {
-		return newError("empty file path.")
-	}
-
-	if *sigFile == "" {
-		return newError("empty signature path.")
-	}
-
-	sigReader, err := os.Open(os.ExpandEnv(*sigFile))
-	if err != nil {
-		return newError("failed to open file ", *sigFile).Base(err)
-	}
-
-	files := fs.Args()
-
-	err = signerVerify.OutputAndJudge(signerVerify.CheckSignaturesV2Fly(sigReader, files))
-
-	if err == nil {
-		return nil
-	}
-
-	return newError("file is not officially signed by V2Ray").Base(err)
-}
-
-func init() {
-	common.Must(RegisterCommand({}))
-}
-- 
2.34.1

From 431fe1de7e15afd50cffe8c70ed7b0a93e0d03fb Mon Sep 17 00:00:00 2001
From: Shelikhoo 
Date: Thu, 5 May 2022 22:38:52 +0100
Subject: [PATCH 2/3] Remove engineering dynamic jsonpb loading function

this functionality provided with stock protobuf library in jsonv5
---
 go.mod |  1 -
 infra/conf/api.go  | 12 
 infra/conf/services.go | 30 --
 infra/conf/v2ray.go| 13 -
 4 files changed, 56 deletions(-)
 delete mode 100644 infra/conf/services.go

diff --git a/go.mod b/go.mod
index ff684538..97a3366e 100644
--- a/go.mod
+++ b/go.mod
@@ -7,7 +7,6 @@ require (
 	github.com/golang/protobuf v1.5.2
 	github.com/google/go-cmp v0.5.6
 	github.com/gorilla/websocket v1.4.2
-	github.com/jhump/protoreflect v1.9.0
 	github.com/lucas-clemente/quic-go v0.27.0
 	github.com/miekg/dns v1.1.43
 	github.com/pires/go-proxyproto v0.6.1
diff --git a/infra/conf/api.go b/infra/conf/api.go
index 0749e3db..c6ed685c 100644
---

Bug#1010646: php-nrk-predis: After install php-nrk-predis, Predis seems to be unavailable for applications e.g. Horde

2022-05-05 Thread Leonardo Lopes

Package: php-nrk-predis
Version: 1.0.0-1+b1
Severity: important

Dear Maintainer,


The php-nrk-predis package put the Predis library files under 
/usr/share/php/php-nrk-predis. The directory /usr/share/php/Predis is created 
but left empty.

However, it seems that /usr/share/php/Predis is the location where the Predis 
library is system-wide available. When setting Horde Groupware to use a Redis 
server for caching, one gets the followinf message: "A fatal error has 
occurredClass 'Predis\Client' not found".

Making /usr/share/php/Predis a symlink to /usr/share/php/php-nrk-predis solved 
the problem (at least for Horde). So I suppose that post-0install script could 
be adjusted to make this automatically.

I also cofirmed that the php-nrk-predis package on 'testing' install the Predis 
files under /usr/share/php/Predis ans makes /usr/share/php/php-nrk-predis a 
symlink to /usr/share/php/Predis.

Regards,
Leonardo Lopes


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

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

-- no debconf information

Bug#1010607: transition: libpodofo

Control: tags -1 confirmed

On 2022-05-05 13:29:43 +0200, Mattia Rizzolo wrote:
> Package: release.debian.org
> User: release.debian@packages.debian.org
> Usertags: transition
> Forwarded: https://release.debian.org/transitions/html/auto-libpodofo.html
> 
> Please schedule a transition for libpodofo.
> 
> I test-built all of the reverse deps (calibre, gimagereader,
> horizon-eda, krename, scribus) and they all build.

Please go ahead

Cheers

> 
> -- 
> 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  `-



-- 
Sebastian Ramacher

Bug#1010553: transition: dlib

Control: tags -1 confirmed
Control: forwarded -1 https://release.debian.org/transitions/html/auto-dlib.html

On 2022-05-04 10:08:04 +0200, Pierre Gruet wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Dear Release team,
> 
> I would like to request a transition slot for dlib, which has been accepted in
> experimental and builds well inside. I changed the name of the binary lib
> package after an ABI breakage.
> The automatic ben file at
> https://release.debian.org/transitions/html/auto-dlib.html
> looks good.
> 
> Three reverse dependencies:
> - seer
> - plastimatch
> - openturns
> All of them build fine against the new package, so binNMU will be enough for
> the three of them.

Please go ahead

Cheers

> 
> Best regards,
> 
> -- 
> Pierre
> 

-- 
Sebastian Ramacher

Bug#1010590: transition: proftpd-dfsg

Control: forwarded -1 
https://release.debian.org/transitions/html/proftpd-abi-1.3.7d.html

On 2022-05-05 08:16:18 +0200, Hilmar Preusse wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> This transition was already started by the recent proftpd upload, but is
> not caught caught automatically since it is a virtual package name that
> has changed.

binNMUs scheduled

Cheers

> 
> Ben file:
> 
> title = "proftpd-dfsg";
> is_affected = .depends ~ "proftpd-abi-1.3.7c" | .depends ~ 
> "proftpd-abi-1.3.7d";
> is_good = .depends ~ "proftpd-abi-1.3.7d";
> is_bad = .depends ~ "proftpd-abi-1.3.7c";
> 
> Thanks,
>   Hilmar
> 

-- 
Sebastian Ramacher

Bug#1010468: transition: gnat-11

Control: tags -1 confirmed
Control: forwarded -1 https://release.debian.org/transitions/html/gnat-11.html

On 2022-05-01 22:29:06 +0200, Nicolas Boulenguez wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Hello.
> 
> The gcc-V source package builds the Ada compiler (gnat-V) and
> companion library (libgnat-V).
> The default Ada compiler is selected by the gnat package.
> In unstable and testing, gnat Depends: gnat-10.
> In experimental, gnat Depends: gnat-11.
> 
> Ada libraries have specific requirements.
> * They must Build-Depend: gnat-V (in addition to gnat).
> * Each -dev package name carries a version, similar to the shared
>   object version for lib packages.  Most changes in the source require
>   a renaming of the -dev package, and a source upload of all reverse
>   dependencies.
>   In order to reduce the number of such transitions, many unrelated
>   changes, like new upstream releases, are introduced with a libgnat
>   transition and tested in experimental.
> * Each -dev package depends on both gnat and gnat-V.
> 
> GCC builds no libgnat-V-dev package. The sources for the Ada standard
> library are distributed with the compiler in the gnat-V package.  So
> it is convenient to track the transition with the libgnat-V package
> instead (even when the ABI is unchanged).

Please go ahead

Cheers

> 
> Ben file:
> 
> title = "gnat-11";
> is_affected = .depends ~ "libgnat-8" | .depends ~ "libgnat-9" | .depends ~ 
> "libgnat-10" | .depends ~ "libgnat-11";
> is_good = .depends ~ "libgnat-11";
> is_bad = .depends ~ "libgnat-8" | .depends ~ "libgnat-9" | .depends ~ 
> "libgnat-10";
> 
> During last transition, Sebastian Ramacher has requested that the -dev
> packages replace
>   Depends: gnat, gnat-V
> with
>   Depends: gnat (>= V), gnat (<< V+1)
> in order to help the migration from unstable to testing.
> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975589#24)
> Only a few key packages have been updated and tested in experimental,
> but it seems safe to update the remaining packages during the reupload
> to unstable.
> 
> dh-ada-library libxmlada gprbuild
>   are ready in experimental (including a correct gnat dependency)
> 
> gprconfig-kb
>   is tightly connected with gprbuild and must migrate with the other
>   packages despite not depending on libgnat.
>   It is ready in experimental too.
> 
> adasockets plplot
>   are almost ready in experimental,
>   but must manually change the -dev dependency when reuploaded to unstable
> gnat, gnat-V  ->  gnat (>= V), gnat (<< V+1)
> 
> adacgi ahven anet dbusada gprbuild libalog libaunit libflorist
> libgmpada libgnatcoll libgnatcoll-bindings libgnatcoll-db libgtkada
> liblog4ada libncursesada libtemplates-parser libtexttools libxmlada
> libxmlezout pcscada
>   are almost ready in experimental, but must
>   Build-Depend: dh-ada-library (>= 7.5)
>   when reuploaded to unstable so that the gnat dependency is correctly
>   generated during the rebuild.
> 
> These source packages produce no library and should only need a
> bin-NMU in due time:
> nmumusic123_16.6-2   . ANY . -m 'Rebuild with gnat-11'
> nmu   topal_81-1 . ANY . -m 'Rebuild with gnat-11 for 
> unstable'
> nmu whitakers-words_0.2020.10.27-1.1 . ANY . -m 'Rebuild with gnat-11'
> 
> adabrowse adacontrol asis gnat-gps libaws
>   are RC-buggy and have been removed from testing.
>   They should not prevent the transition.
>   Once the dust has settled, we will see if and when they can be
>   reintroduced into Debian.
> 
> libgnatcoll-python
>   was a temporary package only intended for python2 support in the
>   unstable distribution.
>   It should be removed after this transition.
> 
> ghdl
>   should not be affected.
>   It requires an explicit gnat-V, independently of the default gnat.
> 
> ada-reference-manual
>   should not be affected.
>   It needs gnat at build time only.
> 

-- 
Sebastian Ramacher

Bug#980566: Crashes with python traceback if parsing ubuntu.csv

2022-05-05 Thread Steve McIntyre

Hi Mark,

On Thu, May 05, 2022 at 09:10:23PM +0100, Mark Hindley wrote:
>Just a small update. I think the following is better.
>
>Mark
>
>diff --git a/lsb_release.py b/lsb_release.py
>index 3e19519..472d96b 100644
>--- a/lsb_release.py
>+++ b/lsb_release.py
>@@ -45,7 +45,7 @@ def get_distro_info(origin='Debian'):
> global RELEASE_CODENAME_LOOKUP, RELEASES_ORDER, TESTING_CODENAME
> RELEASE_CODENAME_LOOKUP = { r['version']: r['series'] for r in reader if 
> r['version']}
> RELEASES_ORDER = list(RELEASE_CODENAME_LOOKUP.items())
>-RELEASES_ORDER.sort(key=lambda n: [int(v) for v in 
>re.split('([[:space:].])+', n[0]) if v.isdigit()])
>+RELEASES_ORDER.sort(key=lambda n: [int(v) for v in re.split('\D+', n[0]) 
>if v.isdigit()])
> RELEASES_ORDER = list(list(zip(*RELEASES_ORDER))[1])
> 
> if origin.lower() == 'debian':

Both of these DTRT for me, I think. Up to you which you prefer... :-)

Thanks!

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Who needs computer imagery when you've got Brian Blessed?

Bug#1004258: modem-manager-gui: segfaults on launch

2022-05-05 Thread Matteo F. Vescovi

Hi Graham!

On 2022-05-04 at 10:42 (+02), Graham Inggs wrote:
> Hi Matteo, Mykola
>
> What make/model modem do you have?  I am unable to reproduce this with
> a Huawei E3276.

Attached, you'll find the gdb backtrace for modem-manager-gui and the
output for mmcli about my LTE modem (Sierra EM7345, ftr).

Hope this info could help you find a fix.
Feel free to ping me for whatever more info you'd need to solve the
problem.

Cheers.

mfv

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x75791640 (LWP 4627)]
[New Thread 0x74f90640 (LWP 4628)]
[New Thread 0x7fffe640 (LWP 4629)]
[New Thread 0x7fffef7fe640 (LWP 4630)]
[New Thread 0x7fffeeffd640 (LWP 4631)]
[Thread 0x7fffeeffd640 (LWP 4631) exited]
[New Thread 0x7fffeeffd640 (LWP 4632)]
[New Thread 0x7fffee7fc640 (LWP 4633)]
[Thread 0x7fffeeffd640 (LWP 4632) exited]
[Thread 0x7fffee7fc640 (LWP 4633) exited]
[New Thread 0x7fffee7fc640 (LWP 4634)]
[Thread 0x74f90640 (LWP 4628) exited]
[New Thread 0x74f90640 (LWP 4635)]

Thread 1 "modem-manager-g" received signal SIGSEGV, Segmentation fault.
g_bit_lock (address=address@entry=0x20, lock_bit=lock_bit@entry=0) at 
../../../glib/gbitlock.c:218
218 ../../../glib/gbitlock.c: No such file or directory.
#0  g_bit_lock (address=address@entry=0x20, lock_bit=lock_bit@entry=0) at 
../../../glib/gbitlock.c:218
#1  0x77f09699 in g_variant_lock (value=value@entry=0x0) at 
../../../glib/gvariant-core.c:229
#2  g_variant_n_children (value=value@entry=0x0) at 
../../../glib/gvariant-core.c:1007
#3  0x744f3a60 in mmgui_module_connection_get_params 
(connpath=, mmguicore=0x55d46f90) at 
../src/modules/nm09.c:633
#4  mmgui_module_connection_enum (mmguicore=0x55d46f90, 
connlist=0x55d47138) at ../src/modules/nm09.c:732
#5  0x5557e859 in mmguicore_connections_enum (mmguicore=0x55d46f90) 
at ../src/mmguicore.c:1567
#6  0x5559e4c5 in mmgui_main_event_callback 
(event=MMGUI_EVENT_DEVICE_OPENED, mmguicore=, 
data=0x55d6c730, userdata=0x555c4680) at ../src/main.c:197
#7  0x5557ee50 in mmguicore_devices_open (mmguicore=0x55d46f90, 
deviceid=1, openfirst=openfirst@entry=1) at ../src/mmguicore.c:1900
#8  0x5558ffb6 in mmgui_main_device_select_from_list 
(mmguiapp=mmguiapp@entry=0x555c4680, 
identifier=identifier@entry=0x55dc50e0 '0' ) at 
../src/devices-page.c:338
#9  0x5559012a in mmgui_main_device_select_from_list 
(mmguiapp=mmguiapp@entry=0x555c4680, 
identifier=identifier@entry=0x55dc50e0 '0' ) at 
../src/devices-page.c:307
#10 0x5559e072 in mmgui_main_settings_ui_load (mmguiapp=0x555c4680) 
at ../src/main.c:2157
#11 mmgui_main_continue_initialization (mmguicore=, 
mmguiapp=0x555c4680) at ../src/main.c:2780
#12 mmgui_main_event_callback (event=, mmguicore=, data=0x0, userdata=0x555c4680) at ../src/main.c:402
#13 0x5557b1dc in mmgui_svcmanager_start_services_activation 
(svcmanager=0x55d48540) at ../src/svcmanager.c:890
#14 0x55580b58 in mmguicore_modules_prepare (mmguicore=0x55d46f90) 
at ../src/mmguicore.c:1079
#15 mmguicore_start (mmguicore=0x55d46f90) at ../src/mmguicore.c:2889
#16 0x77e2671f in g_closure_invoke (closure=0x556b56c0, 
return_value=return_value@entry=0x0, n_param_values=1, 
param_values=param_values@entry=0x7fffd9d0, 
invocation_hint=invocation_hint@entry=0x7fffd950) at 
../../../gobject/gclosure.c:830
#17 0x77e38cf6 in signal_emit_unlocked_R 
(node=node@entry=0x5569de00, detail=detail@entry=0, 
instance=instance@entry=0x556870f0, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffd9d0) at 
../../../gobject/gsignal.c:3743
#18 0x77e3f111 in g_signal_emit_valist (instance=, 
signal_id=, detail=, 
var_args=var_args@entry=0x7fffdb50) at ../../../gobject/gsignal.c:3496
#19 0x77e3f6bf in g_signal_emit 
(instance=instance@entry=0x556870f0, signal_id=, 
detail=detail@entry=0) at ../../../gobject/gsignal.c:3553
#20 0x77d092b3 in g_application_activate 
(application=application@entry=0x556870f0) at 
../../../gio/gapplication.c:2308
#21 0x77d09648 in g_application_real_local_command_line 
(application=0x556870f0, arguments=0x7fffdc98, 
exit_status=0x7fffdc94) at ../../../gio/gapplication.c:1144
#22 0x77d097be in g_application_run (application=0x556870f0, 
argc=argc@entry=1, argv=argv@entry=0x7fffe0a8) at 
../../../gio/gapplication.c:2538
#23 0x5556a5f0 in main (argc=, argv=) at 
../src/main.c:3090
#0  g_bit_lock (address=address@entry=0x20, lock_bit=lock_bit@entry=0) at 
../../../glib/gbitlock.c:218
address_nonvolatile = 0x20
#1  0x77f09699 in g_variant_lock (value=value@entry=0x0) at 
../../../glib/gvariant-core.c:229
No locals.
#2  g_variant_n_children (value=value@entry=0x0) at

Bug#881910: ITA: libcdio-paranoia -- library to read and control digital audio CDs (was: Bug#881910: O: libcdio and libcdio-paranoia)

2022-05-05 Thread Gabriel F. T. Gomes


Oh, I'm deeply sorry for not replying to this and for sitting on the ITA.

Please feel free to take the ITA. I'm very slow at Debian stuff these days.

Cheers,
Gabriel

On 2022-04-16 03:40, Florian Ernst wrote:

Hello Gabriel,

On Mon, Oct 18, 2021 at 08:37:10PM +0200, Bastian Germann wrote:

On Tue, 4 Feb 2020 23:10:06 -0300 "Gabriel F. T. Gomes" wrote:

I maintain pragha, which depends on this package, so I'll adopt it.

It is now 1.5 years since you filed the ITA. There is a new upstream version
that is unpackaged. Do you still want to take over maintainership?


Could you please comment on this, thanks.

Cheers,
Flo

Bug#1010643: dpkg-reconfigure -f noninteractive unattended-upgrades reverts to installed state

2022-05-05 Thread E.S. Rosenberg

Package: unattended-upgrades
Version: 2.8
Version: 2.3ubuntu0.1

Hi,
While trying to create an ansible playbook to enable/disable
unattended-upgrades I ran into a strange behavior, it seems that
dpkg-reconfigure is reverting the package to the installed state instead of
applying the change made through debconf, running the postinst script
manually (extracted from the deb to /tmp) does result in the expected
outcome.

Example:
root@debian:~# debconf-show unattended-upgrades
* unattended-upgrades/enable_auto_updates: true
*** run playbook that changes state *
root@debian:~# debconf-show unattended-upgrades
* unattended-upgrades/enable_auto_updates: false
root@debian:~# dpkg-reconfigure -f noninteractive unattended-upgrades
root@debian:~# debconf-show unattended-upgrades
* unattended-upgrades/enable_auto_updates: true

The same seems to apply in the other direction (false > true).
It is unclear to me if dpkg-reconfigur is triggering the postinst script or
not.

Thanks for the great work,
Eli

Bug#1010642: RFS: streamlink/4.0.1-1 -- CLI for extracting video streams from various websites to a video player

2022-05-05 Thread Alexis Murzeau

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "streamlink" for a new
upstream version 4.0.1.

 * Package name: streamlink
   Version : 4.0.1-1
   Upstream Author : Streamlink Team
 * URL : https://streamlink.github.io/
 * License : BSD-2-clause, Apache-2.0, MIT/Expat, SIL-OFL-1.1
   Section : python

It builds those binary packages:

  python3-streamlink - Python module for extracting video streams from
various websites
  python3-streamlink-doc - CLI for extracting video streams from various
websites (documentation)
  streamlink - CLI for extracting video streams from various websites to
a video player

To access further information about this package, please visit the
following URL:
  https://mentors.debian.net/package/streamlink


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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/streamlink/streamlink_4.0.1-1.dsc

Changes since the last upload to unstable:
streamlink (4.0.1-1) unstable; urgency=medium

  * New upstream version 4.0.1
  * d/patches: update patches
  * switch to pyproject build
  * d/patches: remove dependency on versioningit

 -- Alexis Murzeau   Thu, 05 May 2022 23:02:52 +0200

Regards,
-- 
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F



















signature.asc
Description: OpenPGP digital signature

Bug#1010641: dpdk: CVE-2021-3839 and CVE-2022-0669

2022-05-05 Thread Luca Boccassi

Source: dpdk
Version: 20.11-1
Severity: serious
Tags: security upstream

DPDK from version 19.11 onward is affected by CVE-2021-3839 and
CVE-2022-0669 in the vhost driver:

https://bugzilla.redhat.com/show_bug.cgi?id=2025882
https://bugzilla.redhat.com/show_bug.cgi?id=2055793

Fixed in upstream version 20.11.5.

Bug#1010640: RFS: arbtt/0.11.1-1 [ITA] -- Automatic Rule-Based Time Tracker


On Thu, 05 May 2022 21:26:34 +0100 Robert Greener  wrote:

Changes since the last upload:

 arbtt (0.11.1-1) unstable; urgency=medium
 .
   * New upstream release


On a first glance, there are the following problems:

d/changelog has to close the ITA with a Closes: tag.
d/control's Vcs-* have to point to the place where the package is maintained, 
not upstream.

Bug#986590: Patch

2022-05-05 Thread Anton Gladky

As I mentioned before the patch does not solve the problem.
Increasing the "Session time" sometimes causes very long
test-times. So we have here definitely the deadlock.

If somebody has more experience in glib, it would be really
helpful to investigate an issue.

Best regards

Anton

Bug#955832: Help needed

2022-05-05 Thread Anton Gladky

tags 955832 +moreinfo
thanks

Hi Simon,

Unfortunately, I failed to drop the dependency on libdbus-glib-1-dev.
Simple removal and updating configure.ac causes tons of other
errors.

Would it be possible for you to have a short look and provide
a patch for that? I would then gladly apply it.

Thanks and regards.

Anton

Bug#999544: Package new upstream version

2022-05-05 Thread Antoine Beaupré

On 2021-11-12 00:16:38, Alois Micard wrote:
> Since Go 1.17 is now the defaults on the archive this package
> fails to build.
>
> It could be great to update to upstream 4.43.0 and backport the
> following commit [1] in order to make the package build again.

I have tried to upgrade to the latest upstream (4.45) today, and failed
at the first patch because it doesn't apply. I refreshed the other two
patches and I'm waiting to hear from upstream (in CC) how to deal with
the first. I pushed my work to the debian/experimental branch on salsa:

https://salsa.debian.org/go-team/packages/golang-v2ray-core/-/merge_requests/new?merge_request%5Bsource_branch%5D=debian%2Fexperimental

a.

-- 
From the age of uniformity, from the age of solitude, from the age of
Big Brother, from the age of doublethink - greetings!
- Winston Smith, 1984

signature.asc
Description: PGP signature

Bug#884575: ITP: syncthingtray -- a tray applet, plasmoid, and Dolphin integration for Syncthing

Hi Hannah, and anyone else reading this,

Update: qtforkawesome is currently waiting in NEW, and I'm currently
testing the latest upstream syncthingtray.  I haven't moved the project
to the Salsa (old collab-maint) group yet, but you can find it with the
fork relationship on salsa between your work and mine.

Sorry for the delay, the questions in this email were also discussed at
various other sites towards the end of 2021, and I didn't see the need
to send this draft until now.

Hannah Rittich  writes:
> On 21/11/2021 22:13, Nicholas D Steeves wrote:
>
> Currently, the Syncthing sources are neither included in the upstream
> tarballs nor in the upstream git repo. They can be pulled into the
> source tree by using the git submodule, but this does not happen unless
> you do this explicitly.
>
> Nevertheless, to be sure I have added the `submodules = False` to the
> `gbp.conf` file. This ensures that the submodules will never be included
> in a tarball built by gbp.
>
> If this situation changes, we might need to change the git repository to
> the gbp import-orig workflow, but for now we should be able to keep it
> as it is.
>
>> 2) Use a build-system config key to explicitly disable this functionality.
>
> Done.
>

Thanks much appreciated!  The principle here is thus: should the
maintainers disappear, it should be easy for someone else to take up the
baton and resume work with minimal pitfalls.

[snip]

>>> - in the syncthingtray package the "package-name-doesnt-match-sonames
>>>libsyncthingconnector1.1.10 libsyncthingmodel1.1.10
>>>libsyncthingwidgets1.1.10". Since these are quite specific libraries
>>>that are only used for Syncthing Tray, I do not see a point in
>>>making separate binary packages for each of them. Hence, I would
>>>suggest to ignore these warnings for now.
>>>
>> 
>> At this time I'm not thinking about this issue; Let's return to this
>> question after the two dependencies have been uploaded.  Policy will
>> need to be consulted
>> 
>>   https://www.debian.org/doc/debian-policy/ch-sharedlibs.html
>> 
>> Be it resolved that the current state is indeed the correct direction, a
>> minimum solution is a lintian override.
>
> Okay.
>

The salient questions here are "are they private libraries?" and "do they
have any kind of stable ABI?"  For the former, yes, for practical
purposes, and to the latter, no they don't have any kind of stable ABI.
Thus I've chosen to go with a lintian override.  Various colleagues have
also expressed that it may be necessary to cut these libs from the
system library path...if ftpmasters don't see an issue, no further work
will be required at this time.  It is possible that Policy may one day
prohibit this, but that's a worry for later!

>> Additionally, no Debian package should bundle fonts (or font-icons).
>
> Why? Which part of the policy manual are you referring to? What are your
> concerns regarding pre-rendered icons?
>

This is mostly a question related to martchus-qtforkawesome packaging if
I remember correctly.

Policy § 11.8.5.1 "Fonts of any type supported by the X Window System
must be in a separate binary package from any executables, libraries, or
documentation".  The font-icons hack is an interesting case because
while they're a font they intuitively seem to be icons.  The
'fonts-font-awesome' is the package that fulfills this requirement, and
I remain hopeful that ftpmasters will approve martchus-qtforkawesome
with Syncthing as prior art, even though both packages embed what are
technically fonts.

There's a dialectic between the work people publish, and Policy, and
this case definitely affects Policy.  As for pre-rendering, I'm sure
you've noticed that the majority of documentation overwhelmingly
supports regeneration of everything from the most sourceful form...  For
example, for fonts: TTF, OTF, BDF, PFB, FNT, and WOFF are output
formats, and not source (https://wiki.debian.org/Fonts).  To answer what
you may be thinking, yes, font-icons may only be fonts due the output
format of their build system.

Thus, I suspect that the following loophole exists: If a font-icon
source has a DFSG-free license, this means that another project has the
right to to export the font source into another format, such as SVG.
SVG can be losslessly modified, and thus I believe it could be argued
that SVG may be considered high-quality source, and that the font source
to SVG format conversion is a non-issue.  On the other hand, I don't
think that rasterised icons (lossy) qualify for this loophole when
lossless source is available.  There have been many discussions about
the freeness of lossy graphics on the mailing lists over the years, if
you're interested.

'hope this answers your questions!
Thank you once again for all of your work on this and related
dependencies.

Regards,
Nicholas

signature.asc
Description: PGP signature

Bug#775049: poppler-utils: "pdftohtml -s .pdf" produces multiple files.

2022-05-05 Thread peter

Resolved upstream with addition of the option -dataurls.  The name of 
the option is rather obscure but means that an entity such as an image 
is included as a Base64 encoded src attribute of an img tag.  

In Debian 11 the command
pdftohtml -dataurls -c -s MyPhDthesis.pdf
produces MyPhDthesis.html as a complete document, including images, in 
one file.

Regards,  ... P.

-- 
mobile: +1 778 951 5147
  VoIP: +1 604 670 0140
   48.7693 N 123.3053 W

Bug#1010639: beep: Doesn't beep - could not open any device

2022-05-05 Thread Richard Z

Package: beep
Version: 1.4.9-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: r...@linux-m68k.org

Dear Maintainer,

installed the beep package and tried beep without any arguments and it does not
work.

$ BEEP_LOG_LEVEL=999 beep
beep-log: Verbose: log_constructor
beep-log: Verbose: beep_driver_console_constructor
beep-log: Verbose: beep_drivers_register 0x5658c6a0 (console)
beep-log: Verbose: beep_driver_evdev_constructor
beep-log: Verbose: beep_drivers_register 0x5658c6e0 (evdev)
beep: Verbose: evdev driver_detect 0x5658c6e0 (nil)
beep: Verbose: b-lib: could not open(2) /dev/input/by-path/platform-pcspkr-
event-spkr: Permission denied
beep: Verbose: console driver_detect 0x5658c6a0 (nil)
beep: Verbose: b-lib: could not open(2) /dev/tty0: Permission denied
beep: Verbose: b-lib: could not stat(2) /dev/vc/0: No such file or directory
beep: Error: Could not open any device


Regards
Richard


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

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

Versions of packages beep depends on:
ii  libc6  2.31-13+deb11u3

beep recommends no packages.

beep suggests no packages.

Bug#1010638: ITP: gnome-shell-extension-proxy-switcher -- Gnome Shell Extension to switch the proxy mode

2022-05-05 Thread Stephan Lachnit

Package: wnpp
Severity: wishlist
Owner: Stephan Lachnit 
X-Debbugs-Cc: debian-de...@lists.debian.org, stephanlach...@debian.org, 
pkg-gnome-maintain...@lists.alioth.debian.org

* Package name: gnome-shell-extension-proxy-switcher
  Version : 1.5.1
  Upstream Author : Tom Flannaghan 
* URL : https://github.com/tomflannaghan/proxy-switcher
* License : GPL-2.0
  Programming Lang: JavaScript
  Description : Gnome Shell Extension to switch the proxy mode

The title pretty much says it all. If wanted I would maintain it the Debian
GNOME Maintainers team.

Cheers,
Stephan

Bug#1010619: rsyslog: CVE-2022-24903: Potential heap buffer overflow in TCP syslog server (receiver) components

2022-05-05 Thread Michael Biebl


Am 05.05.22 um 17:10 schrieb Salvatore Bonaccorso:

Source: rsyslog
Version: 8.2204.0-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for rsyslog. Filling for now
as grave, but we might downgrade. Probably affected configurations are
not that common if I understood correctly, the advisory has some
comments about it as well[1].


Yeah, I think this feature is obscure enough (and not enabled by 
default) that non-RC severity is fine.






OpenPGP_signature
Description: OpenPGP digital signature

Bug#1010570: binaries in source without related source

2022-05-05 Thread Antoine Beaupré

On 2022-05-05 21:51:16, Tino Mettler wrote:
> Hi Antoine,
>
> I'm currently thinking about missing bits for a 0.9.33 release.  I
> didn't switch a package to dfsg source before, so I'm new to that.
>
> It looks like it should be documented in debian/copyright, e.g. why the
> source tarball was repacked and what is the reason.
>
> There should be a changelog entry, which also refers to this bug.

That all sounds about right to me!

> Furthermore, I guess that the procedure to create the upstream tarball
> should be described, by providing the script that I used. This could be
> done in a README.Packaging.

Typically, the script lives in debian/rules, as a target
("get-orig-source"). This has actually been deprecated by Debian policy
4.1.4, interestingly:

https://www.debian.org/doc/debian-policy/upgrading-checklist.html#version-4-1-4

... but is still mentioned in the developer's reference:

https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.en.html#repackaged-upstream-source

In general, I think that means *maybe* we could try harder to get uscan
to do the right thing here, but I understand if it seems impossible. :)

The documentation about that stuff can also live in README.source:

https://www.debian.org/doc/debian-policy/ch-source.html#source-package-handling-debian-readme-source

> Please let me know if I am missing something.

I think that's about right, thanks for the hard work!

-- 
We will create a civilization of the Mind in Cyberspace. May it be more
humane and fair than the world your governments have made before.
- John Perry Barlow, 1996
A Declaration of Independence of Cyberspace

Bug#980566: Crashes with python traceback if parsing ubuntu.csv

2022-05-05 Thread Mark Hindley

Just a small update. I think the following is better.

Mark

diff --git a/lsb_release.py b/lsb_release.py
index 3e19519..472d96b 100644
--- a/lsb_release.py
+++ b/lsb_release.py
@@ -45,7 +45,7 @@ def get_distro_info(origin='Debian'):
 global RELEASE_CODENAME_LOOKUP, RELEASES_ORDER, TESTING_CODENAME
 RELEASE_CODENAME_LOOKUP = { r['version']: r['series'] for r in reader if 
r['version']}
 RELEASES_ORDER = list(RELEASE_CODENAME_LOOKUP.items())
-RELEASES_ORDER.sort(key=lambda n: [int(v) for v in 
re.split('([[:space:].])+', n[0]) if v.isdigit()])
+RELEASES_ORDER.sort(key=lambda n: [int(v) for v in re.split('\D+', n[0]) 
if v.isdigit()])
 RELEASES_ORDER = list(list(zip(*RELEASES_ORDER))[1])
 
 if origin.lower() == 'debian':

Bug#1010637: ITP: mathcomp-multinomials -- Multivariate polynomials for Mathematical Components

2022-05-05 Thread Julien Puydt

Package: wnpp
Severity: wishlist
Owner: Julien Puydt 
X-Debbugs-Cc: debian-ocaml-ma...@lists.debian.org, jpu...@debian.org

* Package name: mathcomp-multinomials
  Version : 1.5.5
  Upstream Author : Pierre-Yves Strub
* URL : https://www.github.com/mathcomp/multinomials
* License : CeCILL-B
  Programming Lang: Coq/OCaml
  Description : Multivariate polynomials for Mathematical Components
 This package provides an extension to Mathematical Components
 for monomial algebra, multivariate polynomials over ring
 structures and an extended theory for polynomials whose
 coefficients live in abelian rings and integral domains.
 .
 The Mathematical Components library is a coherent repository of
 general-purpose formalized mathematical theories for the
 Coq proof assistant.

I plan to maintain it within the Debian OCaml Maintainers team, along the rest
of the Coq-related packages.

Cheers,

J.Puydt

Bug#1010570: binaries in source without related source

2022-05-05 Thread Tino Mettler

Hi Antoine,

I'm currently thinking about missing bits for a 0.9.33 release.  I
didn't switch a package to dfsg source before, so I'm new to that.

It looks like it should be documented in debian/copyright, e.g. why the
source tarball was repacked and what is the reason.

There should be a changelog entry, which also refers to this bug.

Furthermore, I guess that the procedure to create the upstream tarball
should be described, by providing the script that I used. This could be
done in a README.Packaging.

Please let me know if I am missing something.

Regards,
Tino

Bug#903374: tracker : flaky autopkgtest: ERROR: tracker-monitor-test - Bail out!


Control: tags -1 patch

On 22-09-2021 22:30, Paul Gevers wrote:

Since the beginning of September 2021, the autopkgtest of tracker
started to fail consistently.

Can you please look into this?


I prepared a fix
https://salsa.debian.org/elbrus/tracker/-/commit/2dffe8c7dd19ea263c7d951b8234fb659b1d9d3a

I'm not sure if the --no-parallel is really needed, but I found that in 
debian/rules, so at least that's not unheard off.


As the git tree has moved on with the work for experimental, I wasn't 
sure how to propose an MR.


Paul

diff --git a/debian/tests/unit-tests b/debian/tests/unit-tests
index e1191fef1..3d7ac668f 100644
--- a/debian/tests/unit-tests
+++ b/debian/tests/unit-tests
@@ -16,4 +16,4 @@ LOCPATH=${AUTOPKGTEST_TMP}/locale \
 HOME=${AUTOPKGTEST_TMP} \
 LANG=en_US.utf8 \
 LC_ALL=en_US.utf8 \
-dbus-run-session -- dh_auto_test 2> >(grep -vE 
'^(Activating|Successfully activated)')>&2
+dbus-run-session -- dh_auto_test --no-parallel 2> >(grep -vE 
'^(Activating|Successfully activated)')>&2

diff --git a/tests/functional-tests/cli.py b/tests/functional-tests/cli.py
index 1318e754e..6e4475d56 100644
--- a/tests/functional-tests/cli.py
+++ b/tests/functional-tests/cli.py
@@ -37,6 +37,7 @@ class TestCli(fixtures.TrackerCommandLineTestCase):
 expected_version_line = 'Tracker %s' % 
configuration.tracker_version()

 self.assertEqual(version_line, expected_version_line)

+@unittest.skipIf (1, "It errors on ci.d.n")
 def test_create_local_database(self):
 """Create a database using `tracker3 endpoint` for local 
testing"""


@@ -53,6 +54,7 @@ class TestCli(fixtures.TrackerCommandLineTestCase):
 ['tracker3', 'sparql', '--database', tmpdir,
  '--query', 'ASK { ?u a rdfs:Resource }'])

+@unittest.skipIf (1, "It errors on ci.d.n")
 def test_export(self):
 """Export contents of a Tracker database."""

@@ -69,6 +71,7 @@ class TestCli(fixtures.TrackerCommandLineTestCase):
 self.run_cli(
 ['tracker3', 'export', '--database', tmpdir, 
'--show-graphs']);


+@unittest.skipIf (1, "It errors on ci.d.n")
 def test_import(self):
 """Import a Turtle file into a Tracker database."""

@@ -83,6 +86,7 @@ class TestCli(fixtures.TrackerCommandLineTestCase):
 self.run_cli(
 ['tracker3', 'import', '--database', tmpdir, testdata]);

+@unittest.skipIf (1, "It errors on ci.d.n")
 def test_http_endpoint(self):
 """Create a HTTP endpoint for local testing"""

diff --git a/tests/functional-tests/portal.py 
b/tests/functional-tests/portal.py

index 2dbbd66c8..b52352e53 100644
--- a/tests/functional-tests/portal.py
+++ b/tests/functional-tests/portal.py
@@ -32,6 +32,7 @@ import configuration
 import fixtures

 class TestPortal(fixtures.TrackerPortalTest):
+@unittest.skipIf (1, "It errors on ci.d.n")
 def test_01_forbidden(self):
 self.start_service('org.freedesktop.Inaccessible')
 self.assertRaises(
@@ -39,6 +40,7 @@ class TestPortal(fixtures.TrackerPortalTest):
 'org.freedesktop.Inaccessible',
 'select ?u { BIND (1 AS ?u) }')

+@unittest.skipIf (1, "It errors on ci.d.n")
 def test_02_allowed(self):
 self.start_service('org.freedesktop.PortalTest')
 res = self.query(
@@ -47,6 +49,7 @@ class TestPortal(fixtures.TrackerPortalTest):
 self.assertEqual(len(res), 1)
 self.assertEqual(res[0][0], '1')

+@unittest.skipIf (1, "It errors on ci.d.n")
 def test_03_graph_access(self):
 self.start_service('org.freedesktop.PortalTest')
 self.update(
@@ -61,6 +64,7 @@ class TestPortal(fixtures.TrackerPortalTest):
 self.assertEqual(len(res), 1)
 self.assertEqual(res[0][0], 'b')

+@unittest.skipIf (1, "It errors on ci.d.n")
 def test_04_rows_cols(self):
 self.start_service('org.freedesktop.PortalTest')
 res = self.query(
@@ -95,6 +99,7 @@ class TestPortal(fixtures.TrackerPortalTest):
 self.timeout_id = 0
 self.loop.quit()

+@unittest.skipIf (1, "It errors on ci.d.n")
 def test_05_local_connection_notifier(self):
 self.start_service('org.freedesktop.PortalTest')



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1010568: busco: missing dependencies on hmmer and prodigal

2022-05-05 Thread Andreas Tille

Hi Andrius,

Am Thu, May 05, 2022 at 04:14:16PM +0300 schrieb Andrius Merkys:
> > Adding these is easy.  Would you mind adding either this fna file (or
> > some similar example) to the test suite enabling us to test that package
> > properly in autopkgtest?
> 
> Adding these surely are easy - thanks for doing so. Some maintainers
> prefer keeping nonessential dependencies as Recommends or Suggests and
> since this is my first encounter with busco I cannot say much about it.

I think in the field of bioinformatics there is no real point in beeing
sparse with dependencies.  I think a failure due to a missing program is
a pretty good reason to add a Depends.
 
> As for autopkgtest, busco has fna files under test_data/. Bit more
> problematic is that busco needs some data from BUSCO database [1] to
> calculate genome coverage. These could be downloaded and stored
> somewhere under debian/ for autopkgtest purpose, but I cannot find the
> licensing information.
> 
> > (And feel free to do a team upload if you are in that mood.)
> 
> Sure, I can upload if we decide that autopkgtest could wait.

I'm a big fan of fixing bugs quickly - so feel free to upload.
May be some wishlist bug that describes the problem of the
autopkgtest keeps a record about this issue.

Kind regards

  Andreas.

> [1] https://busco-data.ezlab.org/v5/data/lineages/
> 
> Best,
> Andrius
> 

-- 
http://fam-tille.de

Bug#1010636: dogtag-pki: please reduce unused Build-Depends

2022-05-05 Thread Helmut Grohne

Source: dogtag-pki
Version: 11.0.3-4
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability

dogtag-pki cannot be cross built from source, because its Build-Depends
are not satisfiable. The problems are numerous, so instead of looking
into them in detail, I looked for low hanging fruit: unused
Build-Depends. Since dogtag-pki is mostly reproducible (except for the
build path), there is a relatively easy technique for identifying unused
Build-Depends:
 * Build dogtag-pki
 * Build dogtag-pki with as many Build-Depends moved to Build-Conflicts
   as possible while also passing DEB_BUILD_OPTIONS=nocheck. Use the
   same build path.
 * Verify that both builds produce bit-identical results.

So that's what I did and the following dependencies could be moved to
Build-Conflicts:
 * libjaxp1.3-java
 * libxalan2-java
 * policycoreutils
 * python3-dev
 * python3-nss

Of course, Build-Conflicts is not the aim, but it ensures that the
packages are really gone and not pulled by some other dependency for the
purpose of testing. Then, disabling tests via DEB_BUILD_OPTIONS=nocheck
of course may have found test dependencies. And finally, packages may
contain pre-build artifacts that are only rebuilt when the relevant
build tools are available, so we cannot just delete these packages from
Build-Depends. Some will have to stay. Some may be annotated 
and some can be dropped.

Can I ask you to review each of the mentioned 5 dependencies? I'd hope
that all of them can be annotated  or dropped entirely.

Thanks in advance

Helmut

Bug#1004107: meson: flaky autopkgtest on armhf: dictionary changed size during iteration -> timeout


Hi Jussi,

On 21-01-2022 19:17, Paul Gevers wrote:

Running tests with 160 workers


It just occurred to me that it may be useful to try and reduce the 
number of concurrent running tests to something you would expect on a 
more normal computer (under conditions where the framework is better 
tested). Our armel host has 160 cores, similar, our amd64 ci-worker13 
host has 56.


Paul

https://sources.debian.org/src/meson/0.62.1-1/run_project_tests.py/#L1542

https://sources.debian.org/src/meson/0.62.1-1/run_project_tests.py/#L1552


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1010635: denemo: Help | Browse Manual opens the wrong directory

2022-05-05 Thread Nate Bargmann

Package: denemo
Version: 2.5.0-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Maintainer,

In attempting to open the manual using Help | Browse Manual from the
main menu, The browser is given the following file path to open:

file:///usr/share/doc/denemo-doc/denemo-manual.html

However, that file does not exist.

I then manually opened the file from:

file:///usr/share/doc/denemo/denemo-manual.html

and can read the manual.

It's possible that the following patch should be corrected so that the
"denemo" directory is in the path rather than "denemo-doc":

https://sources.debian.org/patches/denemo/2.5.0-1/0001-Change-path-of-manual.patch/

- - Nate



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

Kernel: Linux 5.16.0-0.bpo.4-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_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 denemo depends on:
ii  denemo-data 2.5.0-1
ii  fonts-denemo2.5.0-1
ii  guile-2.2-libs  2.2.7+1-6
ii  libaubio5   0.4.9-4+b4
ii  libc6   2.31-13+deb11u3
ii  libcairo2   1.16.0-5
ii  libevdocument3-43.38.2-1
ii  libevview3-33.38.2-1
ii  libfluidsynth2  2.1.7-1.1
ii  libfontconfig1  2.13.1-4.2
ii  libgdk-pixbuf-2.0-0 2.42.2+dfsg-1
ii  libglib2.0-02.66.8-1
ii  libgtk-3-0  3.24.24-4+deb11u2
ii  libgtksourceview-3.0-1  3.24.11-2
ii  libpango-1.0-0  1.46.2-3
ii  libpangocairo-1.0-0 1.46.2-3
ii  libportaudio2   19.6.0-1.1
ii  libportmidi01:217-6
ii  librsvg2-2  2.50.3+dfsg-1
ii  librubberband2  1.9.0-1
ii  libsmf0 1.3-4
ii  libsndfile1 1.0.31-2
ii  libxml2 2.9.10+dfsg-6.7+deb11u1

Versions of packages denemo recommends:
ii  denemo-doc  2.5.0-1
ii  lilypond2.22.0-10

denemo suggests no packages.

- -- debconf-show failed

-BEGIN PGP SIGNATURE-

iGsEARECACsWIQSC1k9rDmfNQfaJu6b7LFEw1VqIGQUCYnQdcg0cbjBuYkBuMG5i
LnVzAAoJEPssUTDVWogZNhgAnivjTLMR07J1SVRP+p/rsFqHARW8AJ9tb12x3dwv
R/sqVGKmX42a38lfVg==
=tJnI
-END PGP SIGNATURE-

Bug#1007884: bullseye-pu: package glewlwyd/2.5.2-2+deb11u2

Hi,

On Thu, May 05, 2022 at 08:37:51PM +0200, Salvatore Bonaccorso wrote:
> Control: tags -1 - moreinfo
> 
> Hi Nicolas,
> 
> On Sat, Apr 30, 2022 at 12:54:31PM -0400, Nicolas Mora wrote:
> > Hello,
> > 
> > Is it possible to review the patch, so the package in bullseye can be in
> > p-u?
> 
> I guess it did not appear again on the radar of the SRM, because it
> had still the addeded moreinfo tag. Given you provided an answer to
> Julien's question, you can remove the tag, which puts it back for
> review for SRM. Doing so now with this message.

Btw, can you add as well the fix for the second open CVE?
CVE-2022-29967.

Regards,
Salvatore

Bug#1010634: slurm-wlm: CVE-2022-29500

Source: slurm-wlm
Version: 21.08.7-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 20.11.7+really20.11.4-2

Hi,

The following vulnerability was published for slurm-wlm.

CVE-2022-29500[0]:
| SchedMD Slurm 21.08.x through 20.11.x has Incorrect Access Control
| that leads to Information Disclosure.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-29500
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29500
[1] https://lists.schedmd.com/pipermail/slurm-announce/2022/72.html
[2] 
https://github.com/SchedMD/slurm/commit/500787548cf3da22cc69ca2111ce51f77543849b
 

Regards,
Salvatore

Bug#1010633: slurm-wlm: CVE-2022-29501

Source: slurm-wlm
Version: 21.08.7-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 20.11.7+really20.11.4-2

Hi,

The following vulnerability was published for slurm-wlm.

CVE-2022-29501[0]:
| SchedMD Slurm 21.08.x through 20.11.x has Incorrect Access Control
| that leads to Escalation of Privileges and code execution.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-29501
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29501
[1] https://lists.schedmd.com/pipermail/slurm-announce/2022/72.html
[2] 
https://github.com/SchedMD/slurm/commit/863c763c241db46039c27c4b7438ef5d33defb12

Regards,
Salvatore

Bug#1010632: slurm-wlm: CVE-2022-29502

Source: slurm-wlm
Version: 21.08.7-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for slurm-wlm.

CVE-2022-29502[0]:
| SchedMD Slurm 21.08.x through 20.11.x has Incorrect Access Control
| that leads to Escalation of Privileges.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-29502
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29502
[1] https://lists.schedmd.com/pipermail/slurm-announce/2022/72.html
[2] 
https://github.com/SchedMD/slurm/commit/351669e7db3b5bc84b5791dc3626d683b8abe18e

Regards,
Salvatore

Bug#1007884: bullseye-pu: package glewlwyd/2.5.2-2+deb11u2

Control: tags -1 - moreinfo

Hi Nicolas,

On Sat, Apr 30, 2022 at 12:54:31PM -0400, Nicolas Mora wrote:
> Hello,
> 
> Is it possible to review the patch, so the package in bullseye can be in
> p-u?

I guess it did not appear again on the radar of the SRM, because it
had still the addeded moreinfo tag. Given you provided an answer to
Julien's question, you can remove the tag, which puts it back for
review for SRM. Doing so now with this message.

Regards,
Salvatore

Bug#1010631: crypttab: Please cope with cipher-spec containing a comma

2022-05-05 Thread mtths

Package: cryptsetup
Version: 2:2.4.3-1
Severity: minor

Dear Maintainer,

since cryptsetup accepts a cipher specification like "xchacha12,aes-adiantum"
crypttab should cope with a forth field (= options) like:
cipher=xchacha12,aes-adiantum,size=256,hash=sha256,swap

[Currently the function crypttab_parse_options() in /lib/cryptsetup/functions
interprets every comma [,] as a separator of the different options so that
a comma as part of an option value is misinterpreted.]

-- Package-specific info:

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

Kernel: Linux 5.17.3 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE
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)

Versions of packages cryptsetup depends on:
ii  cryptsetup-bin 2:2.4.3-1
ii  debconf [debconf-2.0]  1.5.79
ii  dmsetup2:1.02.175-2.1
ii  libc6  2.33-7
ii  libcryptsetup122:2.4.3-1
ii  libjson-c5 0.16-1
ii  libssh-4   0.9.6-2

cryptsetup recommends no packages.

Versions of packages cryptsetup suggests:
pn  cryptsetup-initramfs
ii  dosfstools  4.2-1
ii  keyutils1.6.1-3
ii  liblocale-gettext-perl  1.07-4+b2

-- debconf information:
  cryptsetup/prerm_active_mappings: true

Bug#980566: Crashes with python traceback if parsing ubuntu.csv

2022-05-05 Thread Mark Hindley

Steve,

Thanks for this.

I am just looking at some lsb updates and have picked your report up.

My proposed fix is attached.

Does it look sane to you? Are you able to verify?

Thanks

Mark
>From 77c66f523138fddd433096d0c411aebd75de29a5 Mon Sep 17 00:00:00 2001
From: Mark Hindley 
Date: Thu, 5 May 2022 17:26:13 +0100
Subject: [PATCH] Naturally sort release versions and ignore strings.

Closes: #980566
---
 lsb_release.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lsb_release.py b/lsb_release.py
index c03d036..3e19519 100644
--- a/lsb_release.py
+++ b/lsb_release.py
@@ -45,7 +45,7 @@ def get_distro_info(origin='Debian'):
 global RELEASE_CODENAME_LOOKUP, RELEASES_ORDER, TESTING_CODENAME
 RELEASE_CODENAME_LOOKUP = { r['version']: r['series'] for r in reader if r['version']}
 RELEASES_ORDER = list(RELEASE_CODENAME_LOOKUP.items())
-RELEASES_ORDER.sort(key=lambda n: float(n[0]))
+RELEASES_ORDER.sort(key=lambda n: [int(v) for v in re.split('([[:space:].])+', n[0]) if v.isdigit()])
 RELEASES_ORDER = list(list(zip(*RELEASES_ORDER))[1])
 
 if origin.lower() == 'debian':
-- 
2.35.1

Bug#1010630: libice6: Missing symbolic link libICE.so (to libICE.so.6.3.0)

2022-05-05 Thread Kevin Cole

Package: libice6
Version: 2:1.0.10-1
Severity: normal
Tags: patch
X-Debbugs-Cc: dc.l...@gmail.com

Dear Maintainer,

I was attempting to build the Strawberry Music Player for a Raspberry Pi 4
with a fresh install of Raspberry Pi OS (Bullseye).   
  
The `$ make -j$(nproc)` command chugged along for a while and the eventually  
died with:
  
...   
make[2]: *** No rule to make target \ 
 '/usr/lib/arm-linux-gnueabihf/libICE.so', \  
 needed by 'strawberry'.  Stop.   
```   
  
Adding symbolic links fixed the problem:  

```   
$ sudo -i 
$ cd /usr/lib/arm-linux-gnueabihf/
$ ln -s libICE.so.6.3.0 libICE.so 
```   

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 11 (bullseye)
Release:11
Codename:   bullseye
Architecture: armv7l

Kernel: Linux 5.15.32-v7l+ (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libice6 depends on:
ii  libbsd0 0.11.3-1
ii  libc6   2.31-13+rpt2+rpi1+deb11u2
ii  x11-common  1:7.7+22

libice6 recommends no packages.

libice6 suggests no packages.

-- no debconf information

Bug#1010629: libc++-14-dev: provide memorysanitizer enabled variants of libc++ and libc++-abi

2022-05-05 Thread Norbert Lange

Package: libc++-14-dev
Version: 1:14.0.0-2
Severity: wishlist
X-Debbugs-Cc: nolang...@gmail.com

Dear Maintainer,

the MemorySanitizer basically requires all used libraries (outside of libc)
to be recompiled.
Given that a C++ library is needed for any C++ Application, providing
libc++ and libc++-abi would be very welcome.

Unfortunatly the llvm-toolchain package is rather complex, so it
is too much for me to figure out a solution.

The idea is that a separate package would install the instrumented
libraries into a subdirectory like
/usr/lib/x86_64-linux-gnu/msan/libc++{.so,.a}
/usr/lib/x86_64-linux-gnu/msan/libc++abi{.so,.a}

[1] - https://github.com/google/sanitizers/wiki/MemorySanitizerLibcxxHowTo


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

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

Versions of packages libc++-14-dev depends on:
ii  libc++1-141:14.0.0-2
ii  libunwind-14-dev  1:14.0.0-2

libc++-14-dev recommends no packages.

libc++-14-dev suggests no packages.

-- no debconf information

Bug#1010628: libsm6: Missing symbolic link libSM.so (to libSM.so.6.0.1)

2022-05-05 Thread Kevin Cole

Package: libsm6
Version: 2:1.2.3-1
Severity: normal
Tags: patch
X-Debbugs-Cc: dc.l...@gmail.com

Dear Maintainer,


I was attempting to build the Strawberry Music Player for a Raspberry Pi 4
with a fresh install of Raspberry Pi OS (Bullseye).   
  
The `$ make -j$(nproc)` command chugged along for a while and the eventually  
died with:
  
...   
make[2]: *** No rule to make target \ 
 '/usr/lib/arm-linux-gnueabihf/libSM.so', \  
 needed by 'strawberry'.  Stop.   
```   
  
Adding symbolic links fixed the problem:  

```   
$ sudo -i 
$ cd /usr/lib/arm-linux-gnueabihf/
$ ln -s libSM.so.6.0.1 libSM.so   

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 11 (bullseye)
Release:11
Codename:   bullseye
Architecture: armv7l

Kernel: Linux 5.15.32-v7l+ (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libsm6 depends on:
ii  libc6 2.31-13+rpt2+rpi1+deb11u2
ii  libice6   2:1.0.10-1
ii  libuuid1  2.36.1-8+deb11u1

libsm6 recommends no packages.

libsm6 suggests no packages.

-- no debconf information

Bug#1008792: Should vmtk be removed?

severity 1008792 normal
reassign 1008792 ftp.debian.org
retitle 1008792 RM: vmtk -- RoM; Depends on Python 2, unmaintained
thanks

Reassigning for removal

Bug#1008700: Should geda-gaf be removed?

severity 1008700 normal
reassign 1008700 ftp.debian.org
retitle 1008700 RM: geda-gaf -- RoM; Depends on Python 2, replacement exists
thanks

Reassigning for removal.

Bug#1008534: devhelp: No page open

2022-05-05 Thread Tor Slettnes

Shouldn't this be a higher priority than "normal"?  It basically makes 
"devhelp" unusable.

Bug#1008703: Should sortsmill-tools be removed?

severity 1008703 normal
reassign 1008703 ftp.debian.org
retitle 1008703 RM: sortsmill-tools -- RoM; Depends on Python 2, unmaintained
thanks

Reassigning for removal

Bug#1008704: Sould astk be removed?

severity 1008704 normal
reassign 1008704 ftp.debian.org
retitle 1008704 RM: astk -- RoM; depends on Python 2, unmaintained
thanks

Reassigning for removal.

Bug#1010627: molly-guard: check cryptsetup passwords on shutdown

2022-05-05 Thread Thorsten Glaser

Package: molly-guard
Version: 0.7.2
Severity: wishlist
X-Debbugs-Cc: t...@mirbsd.de

For all active cryptsetup/luks/whatever discs
whose key is not random (such as in

# 
cswap   /dev/vg-tglase/lv-swap  /dev/random 
cipher=aes-xts-plain64,size=256,discard,plain,swap

in /etc/crypttab), check on shutdown that the admin knows the password.

Do this independent on whether logged in via SSH or not, do it always.

Aus Gründen™. (For Reasons™.)


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

Kernel: Linux 5.10.0-10-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages molly-guard depends on:
ii  procps  2:3.3.17-5

molly-guard recommends no packages.

molly-guard suggests no packages.

-- Configuration Files:
/etc/molly-guard/rc changed:
ALWAYS_QUERY_HOSTNAME=true


-- no debconf information

Bug#1010626: RM: dpatch -- RoQA; obsolete

2022-05-05 Thread Moritz Muehlenhoff

Package: ftp.debian.org
Severity: normal

Please remove dpatch. It has been obsoleted by source format 3.0/quilt

Please force the removal, there are still 10 remaining build deps, but
they are all dropped from testing, have RC bugs and are generally
unmaintained (no maintainer uploads since at least 10 years, in some
cases dating back to 2003...).

If anyone cases, these are easy to fix, the rest will be removed if
not fixed by the bookworm freeze.

Cheers,
Moritz

Bug#1010579: RFS: shotwell/0.30.15-2 -- digital photo organizer

2022-05-05 Thread Jörg Frings-Fürst

Hello Bastian,


many thanks for your review.


Am Donnerstag, dem 05.05.2022 um 17:15 +0200 schrieb Bastian Germann:
> Please fix the patch metadata:
> 
> Author: 

Changed to 

Author: Jens Georg 


and uploaded into git and to montors.

CU
Jörg

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

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

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


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

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


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



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

Bug#1010624: neuron-dev: Compilation/linking problems with nrnivmodl

2022-05-05 Thread Pavel Sanda

Package: neuron-dev
Version: 7.6.3-1+b3
Severity: normal
X-Debbugs-Cc: sa...@lyx.org

Dear Maintainer,

I encountered several problems while trying to compile with nrnivmodl.
When running it nrnivmodl expects that
1) for compilation openmpi (mpicc et al.) is present
2) for linking -lmeschach is expected to work

1. is solved by installing libopenmpi-dev
2. is solved by installing libmeschach-dev (libmeschach.so.1.2 was present, 
but for -lmeschach to work libmeschach.so link needs to be present and
that is provided by libmeschach-dev)

I wonder whether these should be dependencies (or at least suggested ones)
for neuron-dev.

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

Kernel: Linux 5.10.0-13-amd64 (SMP w/8 CPU threads)
Locale: LANG=C, LC_CTYPE=cs_CZ (charmap=ISO-8859-2), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages neuron-dev depends on:
ii  libc6   2.31-13+deb11u3
ii  libstdc++6  10.2.1-6
ii  neuron  7.6.3-1+b3

neuron-dev recommends no packages.

neuron-dev suggests no packages.

-- no debconf information

Bug#1010376: RFS: rinetd/0.73-0.1 [NMU] [ITA] -- Internet TCP/UDP redirection server


Control: retitle -1 RFS: rinetd/0.73-0.1 [NMU] -- Internet TCP/UDP redirection 
server

This does not close an ITA. The package is not even orphaned.

Bug#1009915: sysvinit: Please align with manpages-l10n and afterwards activate man page translations

2022-05-05 Thread Helge Kreutzmann

Hello Mark,
On Thu, May 05, 2022 at 04:27:26PM +0100, Mark Hindley wrote:
> On Sun, May 01, 2022 at 04:16:33PM -0300, Jesse Smith wrote:
> > > The attached Makefile for man/ does not yet work, but I think it's just my
> > > limited man page knowledge.
> > 
> > Thank you for putting this together. I'm applying upstream to our 3.05
> > branch.
> 
> I was still having difficulties with the Makefile you committed. There are 
> some
> patches attached which resolve them for me.
> 
> Helge, I am unclear what the po4a option '--msgid-bugs-address "Your Bugmail
> "' is for. Is it required or should it be set to something
> @upstream sysvinit?

Yes. It should be set to some e-mail address wich actually handles bug
reports on strings. This is put into the header of each message file
(pot and po file).

> Jesse, I have suggested making po4a optional. I wonder if some users might not
> want to install and build the translated pages?

Ideally it should be opt out, e.g. for space constraints. Otherwise
uptake may be very slow.

> Any successfully translated manpages are now installed.

Great.

> What do you both think?

> Subject: [PATCH 3/5] Use single rule and make po4a optional (with warning).
> 
> This ensures the version in set in the master copy before being translated.

Looks fine.

> Subject: [PATCH 1/5] Fix parsing LANGUAGES: $ needs escaping in Makefile.

Yes, this was my intent, I just had some trouble with the quoting and
hence my hack. Please use.

> Subject: [PATCH 5/5] Use po4a --stamp option to avoid rebuild every time, also
>  requires --destdir=./

I did not implement stamp file yet, my status was just to get the work
going, which I achieved, so yes, the stamp part I agree.

For 

> -PO4A_OPTS = --previous --srcdir po/ --destdir po/ --no-backups \
> +PO4A_OPTS = --previous --srcdir po/ --destdir ./ --no-backups --stamp \

We have a (larger) problem, not yet adressed. If the original man
pages get updated, how (and when) are man/po/* updated? My intention
was to do this latest at build time (to avoid outdated translations).

Jesse, how do you want this to be done?

Version a) 
- You update man page
- You update man/po/*
  This could happen by hand or you could have a makefile target which
  you call and then commit the results to the git repository
- Whenever translators see the outdated xx.po (e.g. de.po), they pick
  it up, translate it and you integrate it (all at theier own pace).

Version b)
- During release, you update man/po/* (and commit the result!)
- Whenever translators see the outdated xx.po (e.g. de.po), they pick
  it up, translate it and you integrate it (all at theier own pace).
  However, if you decide to release seldom (e.g. once a year) than
  translations are at least outdated this time.

> Subject: [PATCH 4/5] Install i10n manpages, if available.

Did not check this in detail, best to try out. I hadn't coded this
part yet.

> Subject: [PATCH 2/5] Remove dummy VERSION.

Yes, this was part of my testing only, not meant for production.

Greetings

Helge


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


signature.asc
Description: PGP signature

Bug#1010623: linux-image-amd64: Missing Crypto Modules

2022-05-05 Thread Dick Middleton

Package: linux-image-amd64
Version: 5.10.106-1
Severity: serious
Justification: 4

Dear Maintainer,

Upgrading Stable to Bullseye no longer can access encrypted root file system. 
Prevents booting. 

Needed to add crypto modules ecb and ccm (although I'm not sure which or both 
were needed) to initrd as both were missing.

Was using dracut to build initrd.

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

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

Versions of packages linux-image-amd64 depends on:
ii  linux-image-5.10.0-13-amd64  5.10.106-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- debconf-show failed

Bug#1009915: sysvinit: Please align with manpages-l10n and afterwards activate man page translations

2022-05-05 Thread Mark Hindley

Jesse, Helge,

Thanks.

On Sun, May 01, 2022 at 04:16:33PM -0300, Jesse Smith wrote:
> > The attached Makefile for man/ does not yet work, but I think it's just my
> > limited man page knowledge.
> 
> Thank you for putting this together. I'm applying upstream to our 3.05
> branch.

I was still having difficulties with the Makefile you committed. There are some
patches attached which resolve them for me.

Helge, I am unclear what the po4a option '--msgid-bugs-address "Your Bugmail
"' is for. Is it required or should it be set to something
@upstream sysvinit?

Jesse, I have suggested making po4a optional. I wonder if some users might not
want to install and build the translated pages?

Any successfully translated manpages are now installed.

What do you both think?

Thanks

Mark
>From 3c37edc7386ba86b259d51c0204916e8ed7d254e Mon Sep 17 00:00:00 2001
From: Mark Hindley 
Date: Wed, 4 May 2022 18:35:41 +0100
Subject: [PATCH 3/5] Use single rule and make po4a optional (with warning).

This ensures the version in set in the master copy before being translated.
---
 man/Makefile | 11 +++
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/man/Makefile b/man/Makefile
index 38fc9015..53fe2d11 100644
--- a/man/Makefile
+++ b/man/Makefile
@@ -5,16 +5,19 @@ wall.1
 
 LANGUAGES=$(shell sed -ne 's/^.*\[po4a_langs\] \(.*\)$$/\1/p' po/po4a.cfg)
 
+PO4A := $(shell command -v po4a 2> /dev/null)
 
 PO4A_OPTS = --previous --srcdir po/ --destdir po/ --no-backups \
 --package-name sysvinit --package-version $(VERSION) \
 --msgid-bugs-address "Your Bugmail "
 
-translated:
-	po4a $(PO4A_OPTS) po/po4a.cfg
-
-all install: translated
+all install:
 	sed --in-place=.orig --separate 's/\@VERSION\@/$(VERSION)/g' $(MANPAGES)
+ifdef PO4A
+	po4a $(PO4A_OPTS) po/po4a.cfg
+else
+	@echo 'Install po4a to build translated manpages'
+endif
 
 clean distclean:
 	for man in $(MANPAGES) ; do \
-- 
2.35.1

>From ec8bab0151bad7c2c90601e2c2cda2fbecb3661b Mon Sep 17 00:00:00 2001
From: Mark Hindley 
Date: Wed, 4 May 2022 18:33:15 +0100
Subject: [PATCH 1/5] Fix parsing LANGUAGES: $ needs escaping in Makefile.

---
 man/Makefile | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/man/Makefile b/man/Makefile
index 5817b961..d0ae39d9 100644
--- a/man/Makefile
+++ b/man/Makefile
@@ -3,9 +3,7 @@ killall5.8 last.1 lastb.1 logsave.8 mesg.1 mountpoint.1 pidof.8 poweroff.8 \
 readbootlog.1 reboot.8 runlevel.8 shutdown.8 sulogin.8 telinit.8 utmpdump.1 \
 wall.1
 
-LANGUAGES_DIST =`sed -ne 's/^.*\[po4a_langs\] \(.*\)$/\1/p' po/po4a.cfg`
-LANGUAGES=$(LANGUAGES_DIST)
-LANGUAGES=de es fi fr hu id pl
+LANGUAGES=$(shell sed -ne 's/^.*\[po4a_langs\] \(.*\)$$/\1/p' po/po4a.cfg)
 
 VERSION?=1.2.3
 
-- 
2.35.1

>From 430320674a1e0f716a5c6798e977ddc2a6c903d4 Mon Sep 17 00:00:00 2001
From: Mark Hindley 
Date: Wed, 4 May 2022 18:38:49 +0100
Subject: [PATCH 5/5] Use po4a --stamp option to avoid rebuild every time, also
 requires --destdir=./

---
 man/Makefile | 6 +++---
 src/Makefile | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/man/Makefile b/man/Makefile
index ed3edc77..3b06f561 100644
--- a/man/Makefile
+++ b/man/Makefile
@@ -7,7 +7,7 @@ LANGUAGES=$(shell sed -ne 's/^.*\[po4a_langs\] \(.*\)$$/\1/p' po/po4a.cfg)
 
 PO4A := $(shell command -v po4a 2> /dev/null)
 
-PO4A_OPTS = --previous --srcdir po/ --destdir po/ --no-backups \
+PO4A_OPTS = --previous --srcdir po/ --destdir ./ --no-backups --stamp \
 --package-name sysvinit --package-version $(VERSION) \
 --msgid-bugs-address "Your Bugmail "
 
@@ -25,6 +25,6 @@ install: all
 clean distclean:
 	for man in $(MANPAGES) ; do \
 	   if [ -f "$$man.orig" ] ; then mv "$$man.orig" "$$man" ; fi \
-	done  
-	for lang in $(LANGUAGES) ; do rm -rf "po/$$lang" ; done
+	done
+	for lang in $(LANGUAGES) ; do rm -rf "$$lang" "$$lang.po" ; done
 
diff --git a/src/Makefile b/src/Makefile
index afbeaac2..865af488 100644
--- a/src/Makefile
+++ b/src/Makefile
@@ -219,15 +219,15 @@ install:	all
 			$(INSTALL_DIR) $(ROOT)$(MANDIR)/man5/$$lang; \
 			$(INSTALL_DIR) $(ROOT)$(MANDIR)/man8/$$lang; \
 		done
-		for man in $(MAN1) $(subst ../man/,,$(foreach man,$(MAN1),$(wildcard ../man/po/??/$(man; do \
+		for man in $(MAN1) $(subst ../man/,,$(foreach man,$(MAN1),$(wildcard ../man/??/$(man; do \
 			$(INSTALL_DATA) ../man/$$man $(ROOT)$(MANDIR)/man1/$$man; \
 			sed -i "1{ $(MANDB); }" $(ROOT)$(MANDIR)/man1/$$man ; \
 		done
-		for man in $(MAN5) $(subst ../man/,,$(foreach man,$(MAN5),$(wildcard ../man/po/??/$(man; do \
+		for man in $(MAN5) $(subst ../man/,,$(foreach man,$(MAN5),$(wildcard ../man/??/$(man; do \
 			$(INSTALL_DATA) ../man/$$man $(ROOT)$(MANDIR)/man5/$$man; \
 			sed -i "1{ $(MANDB); }" $(ROOT)$(MANDIR)/man5/$$man ; \
 		done
-		for man in $(MAN8) $(subst ../man/,,$(foreach man,$(MAN8),$(wildcard ../man/po/??/$(man; do \
+		for man in $(MAN8) $(subst ../man/,,$(foreach man,$(MAN8),$(wildcard

Bug#1010621: Missing dependency on fdisk

2022-05-05 Thread Robie Basak

Package: cloud-guest-utils
Version: 0.31-2
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic

Hi,

cloud-guest-utils is missing a dependency on whatever supplies sfdisk or
sgdisk (eg. fdisk and gdisk), so growpart fails by default. gdisk
is a Recommends. Should this be a Depends, given that growpart is a
headline item in the package description?

Thanks,

Robie


signature.asc
Description: PGP signature

Bug#1010579: RFS: shotwell/0.30.15-2 -- digital photo organizer


Please fix the patch metadata:

Author:

Bug#1010619: rsyslog: CVE-2022-24903: Potential heap buffer overflow in TCP syslog server (receiver) components

Source: rsyslog
Version: 8.2204.0-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for rsyslog. Filling for now
as grave, but we might downgrade. Probably affected configurations are
not that common if I understood correctly, the advisory has some
comments about it as well[1].

CVE-2022-24903[0]:
| Potential heap buffer overflow in TCP syslog server (receiver)
| components

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-24903
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24903
[1] 
https://github.com/rsyslog/rsyslog/security/advisories/GHSA-ggw7-xr6h-mmr8#advisory-comment-72243

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1010618: Package new upstream release and java-fast library

2022-05-05 Thread Jochen Sprickerhof

Source: qr-code-generator
Version: 1.7.0-2
Severity: wishlist
Tags: patch

Hi,

the new version of src:jameica depends on the java-fast implementation
of qr-code-generator which is part of version 1.8. I have imported the
new version locally and added the attached patch on top to build the
java package. Note that it needs some patching to compile with maven
which I send upstream here:

https://github.com/nayuki/QR-Code-generator/pull/143

Could you update the version in Salsa and apply the attached patch?
I could also push my version if you give me write access to the repo.
Also I would be happy to sponsor the new package to get through new.

Cheers Jochen


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

Kernel: Linux 5.17.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
>From 11fda9ed89d3196c27822db7679f10df322fb2ef Mon Sep 17 00:00:00 2001
From: Jochen Sprickerhof 
Date: Thu, 5 May 2022 10:06:58 +0200
Subject: [PATCH] Add libfastqrcodegen-java package

---
 debian/control|  28 
 debian/libfastqrcodegen-java.poms |   1 +
 debian/maven.ignoreRules  |   4 +
 debian/maven.rules|   1 +
 .../patches/0003-Add-java-fast-pom.xml.patch  | 151 ++
 debian/patches/series |   1 +
 debian/rules  |  19 +++
 7 files changed, 205 insertions(+)
 create mode 100644 debian/libfastqrcodegen-java.poms
 create mode 100644 debian/maven.ignoreRules
 create mode 100644 debian/maven.rules
 create mode 100644 debian/patches/0003-Add-java-fast-pom.xml.patch

diff --git a/debian/control b/debian/control
index c2c180f..1650984 100644
--- a/debian/control
+++ b/debian/control
@@ -4,9 +4,12 @@ Priority: optional
 Maintainer: Yangfl 
 Build-Depends:
  debhelper-compat (= 13),
+ default-jdk,
+ maven-debian-helper,
 Build-Depends-Indep:
  dh-python,
  python3,
+ libmaven-compiler-plugin-java,
  python3-setuptools,
 Rules-Requires-Root: no
 Standards-Version: 4.6.0
@@ -138,3 +141,28 @@ Description: QR Code generator library in multiple 
languages - Python3 version
   * Open source code under the permissive MIT License
  .
  This package contains the module in Python3.
+
+Package: libfastqrcodegen-java
+Section: java
+Architecture: all
+Multi-Arch: foreign
+Depends: ${misc:Depends}, ${maven:Depends}, ${maven:CompileDepends}
+Description: QR Code generator library in multiple languages - fast Java 
version
+ This project aims to be the best, clearest QR Code generator library in
+ multiple languages. The primary goals are flexible options and absolute
+ correctness. Secondary goals are compact implementation size and good
+ documentation comments. Core features:
+  * Available in 7 programming languages, all with nearly equal functionality:
+Java, JavaScript, TypeScript, Python, C++, C, Rust
+  * Significantly shorter code but more documentation comments compared to
+competing libraries
+  * Supports encoding all 40 versions (sizes) and all 4 error correction 
levels,
+as per the QR Code Model 2 standard
+  * Output formats: Raw modules/pixels of the QR symbol (all languages), SVG 
XML
+string (all languages except C), BufferedImage raster bitmap (Java only),
+HTML5 canvas (JavaScript and TypeScript only)
+  * Encodes numeric and special-alphanumeric text in less space than general
+text
+  * Open source code under the permissive MIT License
+ .
+ This package contains the fast libarary for Java.
diff --git a/debian/libfastqrcodegen-java.poms 
b/debian/libfastqrcodegen-java.poms
new file mode 100644
index 000..e613562
--- /dev/null
+++ b/debian/libfastqrcodegen-java.poms
@@ -0,0 +1 @@
+java-fast/pom.xml --has-package-version
diff --git a/debian/maven.ignoreRules b/debian/maven.ignoreRules
new file mode 100644
index 000..a7175a8
--- /dev/null
+++ b/debian/maven.ignoreRules
@@ -0,0 +1,4 @@
+org.apache.maven.plugins maven-gpg-plugin * * * *
+org.apache.maven.plugins maven-javadoc-plugin * * * *
+org.apache.maven.plugins maven-release-plugin * * * *
+org.apache.maven.plugins maven-source-plugin * * * *
diff --git a/debian/maven.rules b/debian/maven.rules
new file mode 100644
index 000..038c2cd
--- /dev/null
+++ b/debian/maven.rules
@@ -0,0 +1 @@
+io.nayuki fastqrcodegen jar s/.*/debian/ * *
diff --git a/debian/patches/0003-Add-java-fast-pom.xml.patch 
b/debian/patches/0003-Add-java-fast-pom.xml.patch
new file mode 100644
index 000..534056c
--- /dev/null
+++ b/debian/patches/0003-Add-java-fast-pom.xml.patch
@@ -0,0 +1,151 @@
+From: Jochen Sprickerhof 
+Date: Thu, 5 May 2022 16:33:09 +0200
+Subject: Add java-fast/pom.xml
+
+https://github.com/nayuki/QR-Code-generator/pull/143
+---
+

Bug#1010602: [Pkg-javascript-devel] Bug#1010602: Bug#1010602: pkg-js-tools should run require test when node#exports#require is specified in package.json

2022-05-05 Thread Jérémy Lal

Le jeu. 5 mai 2022 à 15:57, Yadd  a écrit :

> On 05/05/2022 15:49, Pirate Praveen wrote:
> >
> >
> > On വ്യാ, മേയ് 5 2022 at 03:46:30 വൈകു +0200 +0200, Yadd 
>
> > wrote:
> >> On 05/05/2022 11:53, Pirate Praveen wrote:
> >>> Package: pkg-js-tools
> >>> Version: 0.14.19
> >>>
> >>> An example is istextorbinary module it has both esm and cjs
> >>> versions and  so require test should not be skipped even though type:
> >>> module is present.
> >>>
> >>>   "type": "module",
> >>>   "main": "edition-es2019/index.js",
> >>>   "exports": {
> >>> "node": {
> >>>   "import": "./edition-es2019-esm/index.js",
> >>>   "require": "./edition-es2019/index.js"
> >>> },
> >>
> >> Hi,
> >>
> >> could you give me the repository link ?
> >
> > This is a new package and I need some more work before I can push it.
> > For now you can just try with npm2deb create istextorbinary I think.
>
> Could you give me the link to a complete "exports" syntax ? It seems
> there are many ways to declare CJS files
>

I may have skipped that part when I explained this to you :)
See
file:///usr/share/doc/nodejs/api/packages.html#conditional-exports

Bug#1010616: libmnl-dev: The libmnl.a is missing in libmnl-dev. Static build fails.

2022-05-05 Thread Lars Ekman

Package: libmnl-dev
Version: 1.0.4-3build2
Severity: normal
X-Debbugs-Cc: lars.g.ek...@est.tech

Dear Maintainer,

 # gcc -o /tmp/hello /tmp/hello.c -lmnl
(dynamic libs work)
# gcc -static -o /tmp/hello /tmp/hello.c -lmnl
/usr/bin/ld: cannot find -lmnl: No such file or directory

Since this is on Ubuntu 22.04 I reported the bug here:

https://bugs.launchpad.net/ubuntu/+source/libmnl/+bug/1971523

but was told that this is a Debian bug and asked to report it to you
to improve the quality of the original package.


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

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

Versions of packages libmnl-dev depends on:
ii  libmnl0  1.0.4-3build2

libmnl-dev recommends no packages.

libmnl-dev suggests no packages.

-- no debconf information

Bug#1010614: elpa-f: circular dependency between Emacs extensions during byte-compilation

2022-05-05 Thread David Bremner

l.bonn...@laposte.net writes:

> Setting up elpa-f (0.20.0-3) ...
> tsort: -: input contains a loop:
> tsort: elpa-dash
> tsort: emacsen-common
> tsort: -: input contains a loop:
> tsort: emacsen-common
> tsort: elpa-s

Is there a user-visible problem other than these messages?

Bug#1008951: openldap FTBFS on musl-linux-any: conflicting declaration of calloc

2022-05-05 Thread Helmut Grohne

Control: forwarded -1 https://bugs.openldap.org/show_bug.cgi?id=9841
Control: tags - moreinfo

Hi Ryan,

On Wed, May 04, 2022 at 05:47:12PM -0700, Ryan Tandy wrote:
> Has this been reported upstream yet? I searched and didn't find this
> specific issue, but it looks like upstream have fixed at least two other
> musl-specific issues recently [ITS#9648, ITS#9650].

Both are unrelated to the issue I reported.

> Before applying a patch for this in Debian, I'd at least like to know
> whether and how upstream intend to address the issue. I'd rather not take a
> patch if it has no future upstream.

The more I see about this issue, the more I am convinced that this is
actually two bugs, not just one.

1. musl should not declare a calloc in . Beyond breaking
   openldap, this also causes issues with libgccjit[citation needed].

2. openldap should not #define calloc before #including system headers.

Fixing either of these fixes the issue I reported. At this point, I
recommend fixing both.

I've just created a matching report at
https://bugs.openldap.org/show_bug.cgi?id=9841.

Hope this works out.

Helmut

Bug#1010571: shotwell: No pubishing plugins available


Control: reopen -1
Control: notfixed -1 openlp/2.9.4-2

Sorry, I have probably got the wrong copy buffer on inserting the bug number 
(had this one open in a browser tab as well).

Bug#965454: chise-base: diff for NMU version 0.3.0-2.2

2022-05-05 Thread Guilherme de Paula Xavier Segundo

Control: tags 965454 + patch
Control: tags 965454 + pending


Dear maintainer,

I've prepared an NMU for chise-base (versioned as 0.3.0-2.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

diff -u chise-base-0.3.0/debian/changelog chise-base-0.3.0/debian/changelog
--- chise-base-0.3.0/debian/changelog
+++ chise-base-0.3.0/debian/changelog
@@ -1,3 +1,14 @@
+chise-base (0.3.0-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Using new DH level format. Consequently:
+  - debian/compat: removed.
+  - debian/control: changed from 'debhelper' to 'debhelper-compat' in
+Build-Depends field and bumped level to 13.
+  - Closes: #965454
+
+ -- Guilherme de Paula Xavier Segundo   Fri, 22 Apr 2022 13:29:50 -0300
+
 chise-base (0.3.0-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
reverted:
--- chise-base-0.3.0/debian/compat
+++ chise-base-0.3.0.orig/debian/compat
@@ -1 +0,0 @@
-5
diff -u chise-base-0.3.0/debian/control chise-base-0.3.0/debian/control
--- chise-base-0.3.0/debian/control
+++ chise-base-0.3.0/debian/control
@@ -2,7 +2,7 @@
 Priority: optional
 Section: devel
 Maintainer: NIIBE Yutaka 
-Build-Depends: debhelper (>= 5.0.0), libdb-dev (>= 4.8)
+Build-Depends: debhelper-compat (= 13), libdb-dev (>= 4.8)
 Standards-Version: 3.8.4
 
 Package: chise-db
diff -u chise-base-0.3.0/libchise/config.guess chise-base-0.3.0/libchise/config.guess
--- chise-base-0.3.0/libchise/config.guess
+++ chise-base-0.3.0/libchise/config.guess
@@ -1,14 +1,14 @@
 #! /bin/sh
 # Attempt to guess a canonical system name.
-#   Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
-#   2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009
-#   Free Software Foundation, Inc.
+#   Copyright 1992-2022 Free Software Foundation, Inc.
 
-timestamp='2009-06-10'
+# shellcheck disable=SC2006,SC2268 # see below for rationale
+
+timestamp='2022-01-09'
 
 # This file 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 2 of the License, or
+# 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
@@ -17,26 +17,30 @@
 # General Public License for more details.
 #
 # You should have received a copy of the GNU General Public License
-# along with this program; if not, write to the Free Software
-# Foundation, Inc., 51 Franklin Street - Fifth Floor, Boston, MA
-# 02110-1301, USA.
+# along with this program; if not, see .
 #
 # As a special exception to the GNU General Public License, if you
 # distribute this file as part of a program that contains a
 # configuration script generated by Autoconf, you may include it under
-# the same distribution terms that you use for the rest of that program.
-
-
-# Originally written by Per Bothner .
-# Please send patches to .  Submit a context
-# diff and a properly formatted ChangeLog entry.
+# the same distribution terms that you use for the rest of that
+# program.  This Exception is an additional permission under section 7
+# of the GNU General Public License, version 3 ("GPLv3").
 #
-# This script attempts to guess a canonical system name similar to
-# config.sub.  If it succeeds, it prints the system name on stdout, and
-# exits with 0.  Otherwise, it exits with 1.
+# Originally written by Per Bothner; maintained since 2000 by Ben Elliston.
 #
-# The plan is that this can be called by configure scripts if you
-# don't specify an explicit build system type.
+# You can get the latest version of this script from:
+# https://git.savannah.gnu.org/cgit/config.git/plain/config.guess
+#
+# Please send patches to .
+
+
+# The "shellcheck disable" line above the timestamp inhibits complaints
+# about features and limitations of the classic Bourne shell that were
+# superseded or lifted in POSIX.  However, this script identifies a wide
+# variety of pre-POSIX systems that do not have POSIX shells at all, and
+# even some reasonably current systems (Solaris 10 as case-in-point) still
+# have a pre-POSIX /bin/sh.
+
 
 me=`echo "$0" | sed -e 's,.*/,,'`
 
@@ -45,7 +49,7 @@
 
 Output the configuration name of the system \`$me' is run on.
 
-Operation modes:
+Options:
   -h, --help print this help, then exit
   -t, --time-stamp   print date of last modification, then exit
   -v, --version  print version number, then exit
@@ -56,8 +60,7 @@
 GNU config.guess ($timestamp)
 
 Originally written by Per Bothner.
-Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001,
-2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
+Copyright 1992-2022 Free Software Foundation, Inc.
 
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A

Bug#952692: xcffib test timeout on s390x.

Control: severity -1 important

Hi,

On Sat, 23 May 2020 15:11:52 +0300 Adrian Bunk  wrote:

> A new try succeeded. It seems something in the testsuite is flaky, and it
> doesn't seem to be specific to this version. Adjusting to version info to
> allow this version to migrate.

With version 0.11.1-2, this package is now arch:all and normally isn't 
built on s390x, so lowering the severity to non-RC level.

On ci.debian.net we haven't seen the timeout yet (but the package hasn't 
been tested a lot yet on that arch). If we're seeing the timeout there 
regularly, I'll raise the severity again, as we consider flaky tests RC.

Paul

OpenPGP_signature
Description: OpenPGP digital signature

Bug#1010613: bullseye-pu: package twisted/20.3.0-7+deb11u1

2022-05-05 Thread Stefano Rivera

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: d...@debian.org

[ Reason ]
Catching up on outstanding security issues.
Security team deemed them no-dsa.

[ Impact ]
Outstanding security issues remain unresolved.

[ Tests ]
Twisted has a comprehensive test-suite, the relevant updates come with
tests, and no regressions were noticed.

[ Risks ]
The same patches are carried in Ubuntu, and in Debian LTS * ELTS.
They did need some backporting to older releases, but nothing too risky.

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

[ Changes ]
* CVE-2022-21712: Information disclosure results in leaking of HTTP cookie
  and authorization headers when following cross origin redirects
  - debian/patches/CVE-2022-21712-*.patch: Ensure sensitive HTTP headers are
removed when forming requests, in src/twisted/web/client.py,
src/twisted/web/test/test_agent.py and src/twisted/web/iweb.py.
  - Thanks Canonical for backporting the patches.
* CVE-2022-21716: Parsing of SSH version identifier field during an SSH
  handshake can result in a denial of service when excessively large packets
  are received
  - debian/patches/CVE-2022-21716-*.patch: Ensure that length of received
handshake buffer is checked, prior to processing version string in
src/twisted/conch/ssh/transport.py and
src/twisted/conch/test/test_transport.py
  - Thanks Canonical for backporting the patches.
* CVE-2022-24801: Correct several defects in HTTP request parsing that could
  permit HTTP request smuggling: disallow signed Content-Length headers,
  forbid illegal characters in chunked extensions, forbid 0x prefix to chunk
  lengths, and only strip space and horizontal tab from header values.
  - debian/patches/CVE-2022-24801-*.patch
* Patch: remove spurious test for illegal whitespace in xmlns, to allow
  tests to pass, again.
  This was a regression introduced by the patch to expat for CVE-2022-25236.
  The resolution upstream was to just delete the test.

[ Other info ]
(Anything else the release team should know.)
diff -Nru twisted-20.3.0/debian/changelog twisted-20.3.0/debian/changelog
--- twisted-20.3.0/debian/changelog 2021-04-24 12:36:24.0 -0400
+++ twisted-20.3.0/debian/changelog 2022-05-05 09:59:26.0 -0400
@@ -1,3 +1,30 @@
+twisted (20.3.0-7+deb11u1) bullseye; urgency=medium
+
+  * Team upload.
+  * CVE-2022-21712: Information disclosure results in leaking of HTTP cookie
+and authorization headers when following cross origin redirects
+- debian/patches/CVE-2022-21712-*.patch: Ensure sensitive HTTP headers are
+  removed when forming requests, in src/twisted/web/client.py,
+  src/twisted/web/test/test_agent.py and src/twisted/web/iweb.py.
+- Thanks Canonical for backporting the patches.
+  * CVE-2022-21716: Parsing of SSH version identifier field during an SSH
+handshake can result in a denial of service when excessively large packets
+are received
+- debian/patches/CVE-2022-21716-*.patch: Ensure that length of received
+  handshake buffer is checked, prior to processing version string in
+  src/twisted/conch/ssh/transport.py and
+  src/twisted/conch/test/test_transport.py
+- Thanks Canonical for backporting the patches.
+  * CVE-2022-24801: Correct several defects in HTTP request parsing that could
+permit HTTP request smuggling: disallow signed Content-Length headers,
+forbid illegal characters in chunked extensions, forbid 0x prefix to chunk
+lengths, and only strip space and horizontal tab from header values.
+- debian/patches/CVE-2022-24801-*.patch
+  * Patch: remove spurious test for illegal whitespace in xmlns, to allow
+tests to pass, again.
+
+ -- Stefano Rivera   Thu, 05 May 2022 09:59:26 -0400
+
 twisted (20.3.0-7) unstable; urgency=medium
 
   * Team upload.
diff -Nru twisted-20.3.0/debian/patches/CVE-2022-21712-10.patch 
twisted-20.3.0/debian/patches/CVE-2022-21712-10.patch
--- twisted-20.3.0/debian/patches/CVE-2022-21712-10.patch   1969-12-31 
20:00:00.0 -0400
+++ twisted-20.3.0/debian/patches/CVE-2022-21712-10.patch   2022-05-05 
09:59:26.0 -0400
@@ -0,0 +1,29 @@
+From 0c44b4806a27d258baf13d6f714f06eddb28da5a Mon Sep 17 00:00:00 2001
+From: Glyph 
+Date: Sun, 23 Jan 2022 15:31:51 -0800
+Subject: [PATCH] correct docstring to suggest the right order
+
+---
+ src/twisted/web/iweb.py | 10 +-
+ 1 file changed, 5 insertions(+), 5 deletions(-)
+
+--- a/src/twisted/web/iweb.py
 b/src/twisted/web/iweb.py
+@@ -716,12 +716,12 @@ class IAgent(Interface):
+ obtained by combining a number of (hypothetical) implementations::
+ 
+ baseAgent = Agent(reactor)
+-redirect = BrowserLikeRedirectAgent(baseAgent, limit=10)
++

Bug#1009219: Please import upstream version 2.5

2022-05-05 Thread David Bremner

Nicholas D Steeves  writes:

> Hi David,
>
> I suspect the failing test in markdown-mode 2.5
> (test-markdown-ext/wiki-link-search-under-project) is failing for a
> similar reasons to why 'ffip-test-relative-path-commands' was failing in
> find-file-in-project from 6.0.7 to a minimum of 1d2f0b3.  The nature of
> the problem appears to be an upstream bug, and in find-file-in-project's
> case, the bug was fixed between 1d2f0b3 and 6.2.0.  My hypothesis is
> that upstream makes a normally-valid assumption about path handling that
> breaks on sbuild and buildds.

Sounds like we should just disable this test for now?

d

Bug#1010608: openldap: Flaky test test063-delta-multiprovider

2022-05-05 Thread Quanah Gibson-Mount





--On Thursday, May 5, 2022 3:54 PM +0300 Adrian Bunk  
wrote:



Source: openldap
Version: 2.5.11+dfsg-1
Severity: seriou
Tags: ftbfs
X-Debbugs-Cc: Philipp Kern 

https://buildd.debian.org/status/fetch.php?pkg=openldap=amd64=2.
5.12%2Bdfsg-1=1651720566=0
https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/openlda
p_2.5.11+dfsg-1.rbuild.log.gz

...

Starting test063-delta-multiprovider for mdb...

running defines.sh
Initializing server configurations...
Starting server 1 on TCP/IP port 9011...
Using ldapsearch to check that server 1 is running...
Using ldapadd for context on server 1...
Starting server 2 on TCP/IP port 9012...
Using ldapsearch to check that server 2 is running...
Starting server 3 on TCP/IP port 9013...
Using ldapsearch to check that server 3 is running...
Starting server 4 on TCP/IP port 9014...
Using ldapsearch to check that server 4 is running...
Using ldapadd to populate server 1...
Waiting 7 seconds for syncrepl to receive changes...
Using ldapsearch to read all the entries from server 1...
Using ldapsearch to read all the entries from server 2...
Using ldapsearch to read all the entries from server 3...
Using ldapsearch to read all the entries from server 4...
Comparing retrieved entries from server 1 and server 2...
Comparing retrieved entries from server 1 and server 3...
Comparing retrieved entries from server 1 and server 4...
Using ldapadd to populate server 2...
Using ldapsearch to read all the entries from server 1...
Using ldapsearch to read all the entries from server 2...
Using ldapsearch to read all the entries from server 3...
Using ldapsearch to read all the entries from server 4...
Comparing retrieved entries from server 1 and server 2...
Comparing retrieved entries from server 1 and server 3...
test failed - server 1 and server 3 databases differ

test063-delta-multiprovider failed for mdb after 28 seconds



The test suite is heavily timing dependent.  If you're building in a 
resource constrainted environment, you'll need to adjust the timers 
accordingly.


--Quanah

Bug#1010602: [Pkg-javascript-devel] Bug#1010602: pkg-js-tools should run require test when node#exports#require is specified in package.json

2022-05-05 Thread Yadd


On 05/05/2022 15:49, Pirate Praveen wrote:



On വ്യാ, മേയ് 5 2022 at 03:46:30 വൈകു +0200 +0200, Yadd  
wrote:

On 05/05/2022 11:53, Pirate Praveen wrote:

Package: pkg-js-tools
Version: 0.14.19

An example is istextorbinary module it has both esm and cjs 
versions and so require test should not be skipped even though type: 
module is present.


  "type": "module",
  "main": "edition-es2019/index.js",
  "exports": {
    "node": {
  "import": "./edition-es2019-esm/index.js",
  "require": "./edition-es2019/index.js"
    },


Hi,

could you give me the repository link ?


This is a new package and I need some more work before I can push it. 
For now you can just try with npm2deb create istextorbinary I think.


Could you give me the link to a complete "exports" syntax ? It seems 
there are many ways to declare CJS files

Bug#1010612: ITP: coq-bignums -- Coq library for big numbers

2022-05-05 Thread Julien Puydt

Package: wnpp
Severity: wishlist
Owner: Julien Puydt 
X-Debbugs-Cc: debian-ocaml-ma...@lists.debian.org, jpu...@debian.org

* Package name: coq-bignums
  Version : 8.15.0
  Upstream Author : Laurent Théry, Benjamin Grégoire, Arnaud Spiwack, Evgeny
Makarov and Pierre Letouzey
* URL : https://www.github.com/coq-community/bignums/
* License : LGPL-2.1
  Programming Lang: Ocaml/Coq
  Description : Coq library for big numbers
 This package provides big numbers (natural numbers,
 integers and rationals) in Coq, as BigN, BigZ and BigQ,
 which used to be part of the standard library.

I plan to maintain the package within the Debian Ocaml Maintainers team, along
with the rest of the Coq packages.

Cheers,

J.Puydt

Bug#1010602: [Pkg-javascript-devel] Bug#1010602: pkg-js-tools should run require test when node#exports#require is specified in package.json

2022-05-05 Thread Yadd


On 05/05/2022 11:53, Pirate Praveen wrote:

Package: pkg-js-tools
Version: 0.14.19

An example is istextorbinary module it has both esm and cjs versions and 
so require test should not be skipped even though type: module is present.


  "type": "module",
  "main": "edition-es2019/index.js",
  "exports": {
    "node": {
  "import": "./edition-es2019-esm/index.js",
  "require": "./edition-es2019/index.js"
    },


Hi,

could you give me the repository link ?

Bug#1009452: libgit2-glib: FTBFS: gir1.2-ggit-1.0 missing files: usr/lib/python3/-packages/gi/overrides

2022-05-05 Thread Peter Green


This issue is related to https://bugs.debian.org/1009097


Bug 1009097 has been marked as fixed in meson 0.62.1-1, but according to
"reproducible builds" libgit2-glib still FTBFS with the same error.

https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/libgit2-glib.html

Bug#1005757: python-jsonschema: Please provide latest upstream release 4.4.0

2022-05-05 Thread Thomas Goirand


On 2/14/22 14:50, Agathe Porte wrote:

Source: python-jsonschema
Version: 3.2.0-5
Severity: wishlist
X-Debbugs-Cc: deb...@microjoe.org

Dear Maintainer,

I am currently packaging dtschema (see ITP #1005301 [0]). This package
seems to use a validator introduced in 2019 but not available in the
current 3.2 release.

Here is the test failing during package build:


==
ERROR: dtschema (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: dtschema
Traceback (most recent call last):
   File "/usr/lib/python3.9/unittest/loader.py", line 470, in _find_test_path
 package = self._get_module_from_name(name)
   File "/usr/lib/python3.9/unittest/loader.py", line 377, in 
_get_module_from_name
 __import__(name)
   File 
"/home/microjoe/dev/debian/result/dt-schema/.pybuild/cpython3_3.9_dt-schema/build/dtschema/__init__.py",
 line 1, in 
 from dtschema.lib import (
   File 
"/home/microjoe/dev/debian/result/dt-schema/.pybuild/cpython3_3.9_dt-schema/build/dtschema/lib.py",
 line 766, in 
 DTVal = jsonschema.validators.extend(jsonschema.Draft201909Validator, 
{'typeSize': typeSize, 'phandle': phandle})
AttributeError: module 'jsonschema' has no attribute 'Draft201909Validator'


--
Ran 1 test in 0.000s

FAILED (errors=1)



It seems to be that providing the latest 4.4.0 release should solve this
issue, and allow me to finish the packaging of the dtschema package. The
`Draft201909Validator` was introduced a commit 6 months ago in upstream
[1].

Bests regards,

Agathe.


Hi,

python-jsonschema is packaged as part of the OpenStack components. Until 
OpenStack upgrades to that version, I wont be upgrading the package. 
Thanks for your understanding.


Cheers,

Thomas Goirand (zigo)

Bug#1010570: binaries in source without related source

2022-05-05 Thread Antoine Beaupré

On 2022-05-05 10:37:41, Tino Mettler wrote:
> Hi,
>
> regarding the comments in the code, the binary blob in install.py and
> upgrade.py can be generated during build time using tasks/generate.py. 
> However, both files are not part of the binary package so I see no
> point in doing that. So I think replacing them with empty files in
> the dfsg source tarball is okay.

Agreed.

-- 
Music gives a soul to the universe, wings to the mind, flight to the
imagination and life to everything
 - Plato

Bug#1010568: busco: missing dependencies on hmmer and prodigal

2022-05-05 Thread Andrius Merkys

Hi Andreas,

Thanks for prompt action.

On 2022-05-04 18:25, Andreas Tille wrote:
>> I propose adding
>> hmmer and prodigal as dependencies of busco.
> Adding these is easy.  Would you mind adding either this fna file (or
> some similar example) to the test suite enabling us to test that package
> properly in autopkgtest?

Adding these surely are easy - thanks for doing so. Some maintainers
prefer keeping nonessential dependencies as Recommends or Suggests and
since this is my first encounter with busco I cannot say much about it.

As for autopkgtest, busco has fna files under test_data/. Bit more
problematic is that busco needs some data from BUSCO database [1] to
calculate genome coverage. These could be downloaded and stored
somewhere under debian/ for autopkgtest purpose, but I cannot find the
licensing information.

> (And feel free to do a team upload if you are in that mood.)

Sure, I can upload if we decide that autopkgtest could wait.

[1] https://busco-data.ezlab.org/v5/data/lineages/

Best,
Andrius

Bug#1010610: Babeld is an old, buggy version

2022-05-05 Thread Juliusz Chroboczek

Package: babeld
Vesion: 1.9.1-1+b1

The version of babeld in Debian is almost three years old, and has
a number of bugs that have been fixed in more recent versions.  Please
upgrade to a more recent version.

Bug#1010526: [xml/sgml-pkgs] Bug#1010526: libxml2: CVE-2022-29824: integer overflows in xmlBuf and xmlBuffer

2022-05-05 Thread Mattia Rizzolo

On Tue, May 03, 2022 at 05:43:50PM +0200, Salvatore Bonaccorso wrote:
> CVE-2022-29824[0]:
> | In libxml2 before 2.9.14,

I'm uploading 2.9.14 in a few minutes, taking care of this for unstable
and bookworm, but if you believe this bug deserves to be fixed through
-security, I'd ask if you can take care of that yourselves.

Otherwise I'll submit a pu next week.

-- 
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#929983: bug 929983: ipxe-qemu: virtio booting no longer works after upgrade to buster

2022-05-05 Thread Michael Tokarev


05.05.2022 13:47, Paul Gevers wrote:

Hi all,

[CC-ing src:debian-edu and src:qemu as they pull in src:ipxe-qemu into the key 
package set, so I consider them stakeholders in this RC bug.]

On Fri, 12 Mar 2021 19:29:55 +0100 (CET) Thorsten Glaser  
wrote:

So we now know without fail that there’s a change in the ipxe-qemu
binary package, introduced between jessie and stretch, that breaks
netbooting on virtio NICs for at least some qemu machine models in
use by libvirt guests.


Is there any progress on this front? It would be a shame if we have to 
-ignore the bug again for bookworm.


Well, there's no progress in there, -
I weren't aware of this issue is still occurs on bookworm.

I don't have a netboot environment handy to test it, either.

Help?

/mjt

Bug#1010609: chromium: Missing suggested package chromium-l10n on 101.0.4951.54-1 upgrade

2022-05-05 Thread Ernesto Domato

Package: chromium
Version: 101.0.4951.41-2
Severity: normal
X-Debbugs-Cc: edo...@gmail.com

Hi,

The package chromium-l10n is missing when trying to upgrade to 101.0.4951.54-1

Greets,
Ernesto


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

Kernel: Linux 5.17.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common  101.0.4951.41-2
ii  libasound2   1.2.6.1-2+b1
ii  libatk-bridge2.0-0   2.38.0-4
ii  libatk1.0-0  2.38.0-1
ii  libatomic1   12-20220428-1
ii  libatspi2.0-02.44.1-1
ii  libc62.33-7
ii  libcairo21.16.0-5
ii  libcups2 2.4.1op1-2
ii  libdbus-1-3  1.14.0-1
ii  libdrm2  2.4.110-1
ii  libevent-2.1-7   2.1.12-stable-5
ii  libexpat12.4.8-1
ii  libflac8 1.3.4-1
ii  libfontconfig1   2.13.1-4.4
ii  libfreetype6 2.11.1+dfsg-2
ii  libgbm1  22.0.2-1
ii  libgcc-s112-20220428-1
ii  libglib2.0-0 2.72.1-1
ii  libgtk-3-0   3.24.33-1
ii  libjpeg62-turbo  1:2.1.2-1
ii  libjsoncpp25 1.9.5-4
ii  liblcms2-2   2.12~rc1-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.33-1
ii  libnss3  2:3.77-1
ii  libopenjp2-7 2.4.0-6
ii  libopus0 1.3.1-0.1
ii  libpango-1.0-0   1.50.7+ds-1
ii  libpng16-16  1.6.37-5
ii  libpulse015.0+dfsg1-4
ii  libre2-9 20220401+dfsg-1
ii  libsnappy1v5 1.1.8-1
ii  libstdc++6   12-20220428-1
ii  libwayland-client0   1.20.0-1
ii  libwebp7 1.2.2-2+b1
ii  libwebpdemux21.2.2-2+b1
ii  libwebpmux3  1.2.2-2+b1
ii  libx11-6 2:1.7.5-1
ii  libxcb1  1.14-3
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.4-1
ii  libxfixes3   1:6.0.0-1
ii  libxkbcommon01.4.0-1
ii  libxml2  2.9.13+dfsg-1+b1
ii  libxrandr2   2:1.5.2-2+b1
ii  libxslt1.1   1.1.34-4
ii  xdg-desktop-portal-gtk [xdg-desktop-portal-backend]  1.14.0-1
ii  zlib1g   1:1.2.11.dfsg-4

Versions of packages chromium recommends:
ii  chromium-sandbox  101.0.4951.41-2

Versions of packages chromium suggests:
pn  chromium-driver  
ii  chromium-l10n101.0.4951.41-2
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  libc6   2.33-7
ii  libstdc++6  12-20220428-1
ii  libx11-62:1.7.5-1
ii  libxext62:1.3.4-1
ii  x11-utils   7.7+5
ii  xdg-utils   1.1.3-4.1
ii  zlib1g  1:1.2.11.dfsg-4

Versions of packages chromium-common recommends:
ii  chromium-sandbox101.0.4951.41-2
ii  dunst [notification-daemon] 1.5.0-1+b1
ii  fonts-liberation1:1.07.4-11
ii  libgl1-mesa-dri 22.0.2-1
ii  libu2f-udev 1.1.10-3
ii  mate-notification-daemon [notification-daemon]  1.26.0-1
ii  notification-daemon

Bug#1010608: openldap: Flaky test test063-delta-multiprovider

2022-05-05 Thread Adrian Bunk

Source: openldap
Version: 2.5.11+dfsg-1
Severity: seriou
Tags: ftbfs
X-Debbugs-Cc: Philipp Kern

https://buildd.debian.org/status/fetch.php?pkg=openldap=amd64=2.5.12%2Bdfsg-1=1651720566=0
https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/openldap_2.5.11+dfsg-1.rbuild.log.gz

...
> Starting test063-delta-multiprovider for mdb...
running defines.sh
Initializing server configurations...
Starting server 1 on TCP/IP port 9011...
Using ldapsearch to check that server 1 is running...
Using ldapadd for context on server 1...
Starting server 2 on TCP/IP port 9012...
Using ldapsearch to check that server 2 is running...
Starting server 3 on TCP/IP port 9013...
Using ldapsearch to check that server 3 is running...
Starting server 4 on TCP/IP port 9014...
Using ldapsearch to check that server 4 is running...
Using ldapadd to populate server 1...
Waiting 7 seconds for syncrepl to receive changes...
Using ldapsearch to read all the entries from server 1...
Using ldapsearch to read all the entries from server 2...
Using ldapsearch to read all the entries from server 3...
Using ldapsearch to read all the entries from server 4...
Comparing retrieved entries from server 1 and server 2...
Comparing retrieved entries from server 1 and server 3...
Comparing retrieved entries from server 1 and server 4...
Using ldapadd to populate server 2...
Using ldapsearch to read all the entries from server 1...
Using ldapsearch to read all the entries from server 2...
Using ldapsearch to read all the entries from server 3...
Using ldapsearch to read all the entries from server 4...
Comparing retrieved entries from server 1 and server 2...
Comparing retrieved entries from server 1 and server 3...
test failed - server 1 and server 3 databases differ
> test063-delta-multiprovider failed for mdb after 28 seconds
(exit 1)
make[4]: *** [Makefile:303: mdb-mod] Error 1

Bug#1010607: transition: libpodofo

2022-05-05 Thread Mattia Rizzolo

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: transition
Forwarded: https://release.debian.org/transitions/html/auto-libpodofo.html

Please schedule a transition for libpodofo.

I test-built all of the reverse deps (calibre, gimagereader,
horizon-eda, krename, scribus) and they all build.

-- 
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#974833: iw: output of 'mpath dump' is wrongly formatted

2022-05-05 Thread Diederik de Haas

Control: tag -1 fixed-upstream

On Saturday, 23 April 2022 18:15:11 CEST Diederik de Haas wrote:
> Control: tag -1 patch upstream
> Control: forwarded -1
> https://lore.kernel.org/linux-wireless/20220423160922.14952-1-didi.deb...@cknow.org/T/#u
> 
> I've made an attempt, hope that's alright. And hopefully I did it correctly.

My patch has been accepted upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/jberg/iw.git/commit/?id=ff67fb2c8860cbf868dc0faa1fbbc97d0f4d9a42

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

Bug#1010606: openssh-server: Include directive not present in sshd_config despite claimed version

2022-05-05 Thread Yann Salmon

Package: openssh-server
Version: 1:7.9p1-10+deb10u2
Severity: normal

Dear Maintainer,


I included an Include directive in my /etc/sshd_config and sshd said it was not
recognised. Indeed, the manual of the installed version does not mention it.
However, ssh -V says that version is 7.9p1 (consistent with apt list openssh-
server), and the release notes for version 7.3 of OpenSSH mention the addition
of the Include directive.

I would have expected version 7.9 to have it as well. Was it advertently
removed by Debian ?



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

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

Versions of packages openssh-server depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.71+deb10u1
ii  dpkg   1.19.7
ii  libaudit1  1:2.8.4-3
ii  libc6  2.28-10+deb10u1
ii  libcom-err21.44.5-1+deb10u3
ii  libgssapi-krb5-2   1.17-3+deb10u3
ii  libkrb5-3  1.17-3+deb10u3
ii  libpam-modules 1.3.1-5
ii  libpam-runtime 1.3.1-5
ii  libpam0g   1.3.1-5
ii  libselinux12.8-1+b1
ii  libssl1.1  1.1.1n-0+deb10u1
ii  libsystemd0241-7~deb10u8
ii  libwrap0   7.6.q-28
ii  lsb-base   10.2019051400
ii  openssh-client 1:7.9p1-10+deb10u2
ii  openssh-sftp-server1:7.9p1-10+deb10u2
ii  procps 2:3.3.15-2
ii  ucf3.0038+nmu1
ii  zlib1g 1:1.2.11.dfsg-1+deb10u1

Versions of packages openssh-server recommends:
ii  libpam-systemd [logind]  241-7~deb10u8
ii  ncurses-term 6.1+20181013-2+deb10u2
ii  xauth1:1.0.10-1

Versions of packages openssh-server suggests:
pn  molly-guard   
pn  monkeysphere  
pn  rssh  
pn  ssh-askpass   
pn  ufw   

-- debconf information excluded

Bug#1010605: pytest: please package pytest 7.1.x

2022-05-05 Thread Sascha Silbe

Source: pytest
Version: 6.0.2-2
Severity: wishlist
X-Debbugs-Cc: sascha-debian-bugs-pytest-2022-05...@silbe.org

Dear Maintainer,

pytest 7.0.0 introduced a couple useful new features. It would be
great to have the latest upstream version (7.1.2 at the time of
writing) in Debian.

Thanks in advance!

Sascha

-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (500, 'stable-debug'), (100, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-13-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_GB, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en:en_US:C:de_DE:de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#929983: bug 929983: ipxe-qemu: virtio booting no longer works after upgrade to buster