Bug#1023379: git-buildpackage: FTBFS with Git 2.38.1

[Arnaud Rebillout]

Package: git-buildpackage
Version: 0.9.29
Severity: normal
User: de...@kali.org
Usertags: origin-kali

Dear Maintainer,

I tried to rebuild git-buildpackage locally and the submodule tests
fail:


==
ERROR: Add a submodule
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/git-buildpackage-JtfSq8/git-buildpackage-0.9.29/tests/04_test_submodules.py",
 line 99, in test_add_submodule
REPO.add_submodule(SUBMODULES[0].dir)
  File 
"/build/git-buildpackage-JtfSq8/git-buildpackage-0.9.29/gbp/git/repository.py", 
line 1938, in add_submodule
self._git_command("submodule", ["add", repo_path])
  File 
"/build/git-buildpackage-JtfSq8/git-buildpackage-0.9.29/gbp/git/repository.py", 
line 245, in _git_command
raise GitRepositoryError("Error running git %s: %s" % (command, 
detail.decode().strip()))
gbp.git.repository.GitRepositoryError: Error running git submodule: Cloning 
into '/tmp/tmp7tjw_zrzgbp_tests.04_test_submodules_/test_repo/test_submodule'...
fatal: transport 'file' not allowed
fatal: clone of '/tmp/tmp7tjw_zrzgbp_tests.04_test_submodules_/test_submodule' 
into submodule path 
'/tmp/tmp7tjw_zrzgbp_tests.04_test_submodules_/test_repo/test_submodule' failed
 >> begin captured logging << 
gbp: debug: ['git', 'submodule', 'add', 
'/tmp/tmp7tjw_zrzgbp_tests.04_test_submodules_/test_submodule']
- >> end captured logging << -


This is due to a recent change in Git, and it's documented at:
* 
https://vielmetti.typepad.com/logbook/2022/10/git-security-fixes-lead-to-fatal-transport-file-not-allowed-error-in-ci-systems-cve-2022-39253.html
* https://bugs.launchpad.net/ubuntu/+source/git/+bug/1993586

Please find a tentative fix at:
https://salsa.debian.org/arnaudr/git-buildpackage/-/commit/5a73cf0e

I tried using REPO.set_config() but it didn't work, so I used the
environment instead.

Best,

Arnaud



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

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

Versions of packages git-buildpackage depends on:
ii  devscripts 2.22.2
ii  git1:2.37.2-1
ii  man-db 2.11.0-1+b1
ii  python33.10.6-1
ii  python3-dateutil   2.8.2-1
ii  python3-pkg-resources  65.5.0-1
ii  python3-yaml   5.4.1-1+b2
ii  sensible-utils 0.0.17

Versions of packages git-buildpackage recommends:
ii  pristine-tar  1.49
ii  python3-requests  2.27.1+dfsg-1
ii  sbuild0.83.2

Versions of packages git-buildpackage suggests:
pn  python3-notify2  
ii  sudo 1.9.11p3-2
ii  unzip6.0-27

-- no debconf information

Bug#966573: progress packaging awscli v2

[Noah Meyerhans]

On Wed, Nov 02, 2022 at 07:55:51PM -0700, Ross Vandegrift wrote:
> > > - the aws-cli2-temp repo is based on upstream, not our awscli repo.  I was
> > >   intentionally being sloppy to quickly get through a test.
> > 
> > Same.  I essentially Debianized the upstream v2 repo from scratch,
> > pulling in some of your packaging metadata as it made sense.  Given that
> > v2 is developed on a different branch and by now differs quite
> > significantly from v1, a case could be made for introducing a new
> > awscli2 package as a new source package and retiring the original awscli
> > package.  However, the debian package metadata isn't really all that
> > complex, so it may not actually be necessary.
> 
> Is there any reason to have both versions available to install at once?

No, there isn't.  And both should be installed as /usr/bin/aws anyway.

At this point my v2 package builds as awscli_2.8.7-1_all.deb and should
be a direct upgrade from the current 1.x packages.

> > Fortunately, aws-lc isn't an issue. But s2n-tls remains one.  Not sure
> > we're going to be able to do anything about that.  The difficult thing
> > is that it's typically expected to be used as a statically linked
> > library, which means updates end up being tedious.
> 
> Agreed, there's nothing we can do about it.  But I think it's good news to be
> able to use OpenSSL and just have one highly security sensitive package.

I just uploaded s2n, so it should be in the NEW queue momentarily.
Sources are at https://salsa.debian.org/cloud-team/s2n-tls.  So we'll
see how this goes.

> > I haven't pushed my changes anywhere, yet.  Once I do, the remaining
> > tasks will be to any lintian issues or other obvious problems and get
> > these packages into NEW.  I think they're in reasonably good shape, but
> > we don't have a lot of time before bookworm starts freezing, so I'd love
> > any help with these steps.
> 
> I might have some time to help.  Would it be useful to transfer my original
> repos to the cloud-team group?

I don't think so.  There were a couple repos where you had made a commit
on the upstream branch, which I blew away in order to stay in sync with
upstream commits.  So I'd need to force push.  Either way, I think the
repos I have locally can be pushed to empty salsa repos.

Honestly, filing some of the ITPs would be quite helpful at this point.
We'll need to get the following projects packaged:

aws-c-auth
aws-c-cal
aws-c-common
aws-c-compression
aws-c-event-stream
aws-c-http
aws-c-io
aws-c-mqtt
aws-c-s3
aws-c-sdkutils
aws-checksums
aws-crt-python

Bug#1009998: gvfs-backends: Unable to access smb://host/sharing on any file manager after upgrade

[Michael Tokarev]

[ https://bugs.debian.org/1009998 ]

Ok. This bug has been open for quite some time. And I'm confused now.
Is the reported issue still an issue?  If it is, what's the issue, exactly?
There are several problems here, and at least some of them has been resolved.

Thanks,

/mjt

Bug#1023337: nqp: Please add support for "riscv64" arch

[Paul Wise]

On Wed, 2022-11-02 at 15:47 +0100, Manuel A. Fernandez Montecelo wrote:

> Please enable this architecture, with the patch attached or an equivalent.

Since the Architecture field contains a lot of arches already, it might
be better to let nqp attempt to build on all arches instead. 

Presumably the tests are good enough to check if it works on an arch.

Please read this thread on debian-devel/debian-wb-team for more info
on this type of approach to Debian package architecture lists.

https://lists.debian.org/msgid-search/20220911150857.xedt2an2vye3qrc7@begin

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1023338: rakudo: Please add support for "riscv64" arch

[Paul Wise]

On Wed, 2022-11-02 at 16:12 +0100, Manuel A. Fernandez Montecelo wrote:

> Please enable this architecture, with the patch attached or an equivalent.

Since the Architecture field contains a lot of arches already, it might
be better to let rakudo attempt to build on all arches instead. 

Presumably the tests are good enough to check if it works on an arch.

Please read this thread on debian-devel/debian-wb-team for more info
on this type of approach to Debian package architecture lists.

https://lists.debian.org/msgid-search/20220911150857.xedt2an2vye3qrc7@begin

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1014936: weasyprint: manpage for weasyprint(1) is too much

[Scott Kitterman]

On Fri, 14 Oct 2022 11:09:54 -0400 Daniel Kahn Gillmor  
wrote:
> Control: forwarded 1014936 https://github.com/Kozea/WeasyPrint/issues/1741
> 
> On Wed 2022-10-12 16:57:29 -0400, Scott Kitterman wrote:
> > On Thu, 14 Jul 2022 16:19:58 -0400 Daniel Kahn Gillmor 
  wrote:
> >> Hi there!  I'm glad that there's a weasyprint(1) manpage, but the
> >> contents of the manual page contain way too much info.
> >> 
> >> The manpage in section 1 should make it clear how to use the command
> >> line utility.
> >
> > If you have suggestions on how to improve the situation without requiring 
> > manual editing every release, I would love to hear them.
> 
> Hm, i think you're saying that this is primarily an upstream problem,
> which seems plausible.  I've reported it upstream, maybe they'll have a
> suggestion.
> 
> Thanks for looking into it!  I agree that we want to keep the manpage
> up-to-date with upstream documentation.

This is fixed (or at least substantially better) in the upstream git now.  It 
should be included in version 57.1 when released.

Scott K

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

Bug#1006807: chromium: resolved

[bw]

Package: chromium
Followup-For: Bug #1006807

Dear Maintainer,

The latest upgrade resolved the issue for both yahoo mail and gmail.
Thanks for your attention.

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

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

Versions of packages chromium depends on:
ii  chromium-common 107.0.5304.87-1~deb11u1
ii  libasound2  1.2.4-1.1
ii  libatk-bridge2.0-0  2.38.0-1
ii  libatk1.0-0 2.36.0-2
ii  libatomic1  10.2.1-6
ii  libatspi2.0-0   2.38.0-4
ii  libbrotli1  1.0.9-2+b2
ii  libc6   2.31-13+deb11u5
ii  libcairo2   1.16.0-5
ii  libcups22.3.3op2-3+deb11u2
ii  libdbus-1-3 1.12.24-0+deb11u1
ii  libdouble-conversion3   3.1.5-6.1
ii  libdrm2 2.4.104-1
ii  libevent-2.1-7  2.1.12-stable-1
ii  libexpat1   2.2.10-2+deb11u5
ii  libflac81.3.3-2+deb11u1
ii  libfontconfig1  2.13.1-4.2
ii  libfreetype62.10.4+dfsg-1+deb11u1
ii  libgbm1 20.3.5-1
ii  libgcc-s1   10.2.1-6
ii  libglib2.0-02.66.8-1
ii  libgtk-3-0  3.24.24-4+deb11u2
ii  libjpeg62-turbo 1:2.0.6-4
ii  libjsoncpp241.9.4-4
ii  liblcms2-2  2.12~rc1-2
ii  libminizip1 1.1-8+b1
ii  libnspr42:4.29-1
ii  libnss3 2:3.61-1+deb11u2
ii  libopenjp2-72.4.0-3
ii  libopus01.3.1-0.1
ii  libpango-1.0-0  1.46.2-3
ii  libpng16-16 1.6.37-3
ii  libpulse0   14.2-2
ii  libre2-920210201+dfsg-1
ii  libsnappy1v51.1.8-1
ii  libstdc++6  10.2.1-6
ii  libwebp60.6.1-2.1
ii  libwebpdemux2   0.6.1-2.1
ii  libwebpmux3 0.6.1-2.1
ii  libwoff11.0.2-1+b1
ii  libx11-62:1.7.2-1
ii  libxcb1 1.14-3
ii  libxcomposite1  1:0.4.5-1
ii  libxdamage1 1:1.1.5-2
ii  libxext62:1.3.3-1.1
ii  libxfixes3  1:5.0.3-2
ii  libxkbcommon0   1.0.3-2
ii  libxml2 2.9.10+dfsg-6.7+deb11u2
ii  libxnvctrl0 470.141.03-1~deb11u1
ii  libxrandr2  2:1.5.1-1
ii  libxslt1.1  1.1.34-4+deb11u1
ii  xdg-desktop-portal-kde [xdg-desktop-portal-backend  5.20.5-1
ii  zlib1g  1:1.2.11.dfsg-2+deb11u2

Versions of packages chromium recommends:
ii  chromium-sandbox  107.0.5304.87-1~deb11u1

Versions of packages chromium suggests:
pn  chromium-driver  
pn  chromium-l10n
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  libc6  2.31-13+deb11u5
ii  libdouble-conversion3  3.1.5-6.1
ii  libstdc++6 10.2.1-6
ii  libx11-6   2:1.7.2-1
ii  libxnvctrl0470.141.03-1~deb11u1
ii  x11-utils  7.7+5
ii  xdg-utils  1.1.3-4.1
ii  zlib1g 1:1.2.11.dfsg-2+deb11u2

Versions of packages chromium-common recommends:
ii  chromium-sandbox107.0.5304.87-1~deb11u1
ii  fonts-liberation1:1.07.4-11
ii  

Bug#966573: progress packaging awscli v2

[Ross Vandegrift]

Hi Noah,

On Mon, Oct 31, 2022 at 10:50:19PM -0700, Noah Meyerhans wrote:
> On Tue, Oct 05, 2021 at 11:10:43PM -0600, Ross Vandegrift wrote:
> > > awscli v2 remains quite difficult to package, but it seems that upstream
> > > is looking to address this.  See
> > > https://github.com/aws/aws-cli/issues/6186 for details and tracking.
> > 
> > Using the source dist poc from https://github.com/aws/aws-cli/pull/6352 I've
> > made enough progress to get a packaged aws-cli v2 working.  There's a lot 
> > more
> > that needs to be done, but idea of the above linked PR could work for us.  
> > I'm
> > going to document my findings here.
> 
> So, only a year later, I've picked this up and made some additional
> progress:
> 
> I have no name!@b02f1db79f9e:/src$ aws --version
> aws-cli/2.8.7 Python/3.10.8 Linux/6.0.0-2-amd64 source/x86_64.debian 
> prompt/off
> I have no name!@b02f1db79f9e:/src$ dpkg -s awscli | grep Version
> Version: 2.8.7-1

Great news!

> > - some repos have tests disabled due to failing during builds.  So far, I 
> > don't
> >   know if these are real failures, or if upstream's build method.
> 
> I think I've got most of these fixed.

落

> > - copyright attribution for aws-lc is very hard.  It's a fork of Google's
> >   BoringSSL, which is a fork of pre-3.0 OpenSSL.
> > 
> > - That also means that aws-lc inherits the openssl gpl incompatibility.
> 
> Here's the good news: We don't actually need aws-lc at all.  awscli v2
> and its various dependencies (including s2n-tls) can build against
> OpenSSL 3.

落

> > - the aws-cli2-temp repo is based on upstream, not our awscli repo.  I was
> >   intentionally being sloppy to quickly get through a test.
> 
> Same.  I essentially Debianized the upstream v2 repo from scratch,
> pulling in some of your packaging metadata as it made sense.  Given that
> v2 is developed on a different branch and by now differs quite
> significantly from v1, a case could be made for introducing a new
> awscli2 package as a new source package and retiring the original awscli
> package.  However, the debian package metadata isn't really all that
> complex, so it may not actually be necessary.

Is there any reason to have both versions available to install at once?

> > - aws-lc and s2n-tls may be hard to maintain.  Both are complicated, 
> > security
> >   critical crypto libraries.
> 
> Fortunately, aws-lc isn't an issue. But s2n-tls remains one.  Not sure
> we're going to be able to do anything about that.  The difficult thing
> is that it's typically expected to be used as a statically linked
> library, which means updates end up being tedious.

Agreed, there's nothing we can do about it.  But I think it's good news to be
able to use OpenSSL and just have one highly security sensitive package.

> I haven't pushed my changes anywhere, yet.  Once I do, the remaining
> tasks will be to any lintian issues or other obvious problems and get
> these packages into NEW.  I think they're in reasonably good shape, but
> we don't have a lot of time before bookworm starts freezing, so I'd love
> any help with these steps.

I might have some time to help.  Would it be useful to transfer my original
repos to the cloud-team group?

Ross

Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

[Vincent Lefevre]

On 2022-11-02 14:24:51 +0200, Eli Zaretskii wrote:
> Signal 1 is SIGHUP, AFAIU.  Why should Emacs receive SIGHUP in the
> middle of GC, I have no idea.  Maybe ask the user what was he doing at
> that time.  E.g., could that be a remote Emacs session?

No, it is on my local machine.

On 2022-11-02 14:43:41 -0700, Sean Whitton wrote:
> Upstream says there isn't enough information in the backtrace to say
> anything helpful about this.  Could you take a look at
>  and consider supplying more information
> over there, please?
> 
> Also, are you able to reproduce this with 'emacs -q' (not -Q)?

This is not reproducible with "emacs -q".

I can reproduce it in a firejail private directory[*] (so that the
behavior doesn't depend on my own config files), where there is no
.emacs file. There is a .emacs.d directory with just a eln-cache
subdirectory:

zira% ls -la .emacs.d 
total 12
drwx-- 3 vinc17 vinc17 4096 2022-11-01 00:40:05 .
drwx-- 4 vinc17 vinc17 4096 2022-11-03 03:53:23 ..
drwxr-xr-x 3 vinc17 vinc17 4096 2022-11-01 00:40:05 eln-cache
zira% ls -la .emacs.d/eln-cache 
total 12
drwxr-xr-x 3 vinc17 vinc17 4096 2022-11-01 00:40:05 .
drwx-- 3 vinc17 vinc17 4096 2022-11-01 00:40:05 ..
drwxr-xr-x 2 vinc17 vinc17 4096 2022-11-01 00:40:05 28.2-43f520ab
zira% ls -la .emacs.d/eln-cache/28.2-43f520ab 
total 8
drwxr-xr-x 2 vinc17 vinc17 4096 2022-11-01 00:40:05 .
drwxr-xr-x 3 vinc17 vinc17 4096 2022-11-01 00:40:05 ..
zira% 

[*] firejail --ignore=read-only --ignore='noexec ${HOME}' 
--noblacklist='${HOME}/*' --private=fj-dir zsh

I run emacs, and quit it immediately. The generation of the core dump
is almost 100% reproducible. Ditto with "emacs -nw".

But note that the bug is also reproducible without firejail, but
harder to reproduce.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#999280: empire-lafe: diff for NMU version 1.1-1.1

[Drake Diedrich]

No need to delay.  Total possible impact one way or another would be really
low, and they can rebuild if they need to.  I haven't used it in a decade,
and am surprised my deadline hacks have survived all this time.  I don't
currently have a known working build system.
-Dtake



On Wed, Nov 2, 2022, 2:15 PM Marcos Talau  wrote:

> Control: tags 999280 + patch
> Control: tags 999280 + pending
>
>
> Dear maintainer,
>
> I've prepared an NMU for empire-lafe (versioned as 1.1-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
>
> Regards.
>

Bug#1021339: neovim: New upstream version (8.0.0) available

[James McCoy]

On Thu, Oct 06, 2022 at 09:23:59AM +0200, Bastian Venthur wrote:
> neovim 8.0.0 has been released a few days ago:
> 
> https://github.com/neovim/neovim/releases/tag/v0.8.0

It requires some tree-sitter projects to be packaged.  I've been working
on the infrastructure for a while, but then need to figure out the right
way to package the tree-sitter parsers.

This is going to take some time.  I may upload 0.8.0 to experimental
before this, just to get some testing on the parts that don't use
tree-sitter.  However, tree-sitter will be needed before uploading to
unstable.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#1023286: fakeroot doesn't wrap __stat64_time64 (and friends) introduced by glibc 2.34 on 32 bit arches

[Clint Adams]

On Tue, Nov 01, 2022 at 09:29:41PM +0100, Johannes Schauer Marin Rodrigues 
wrote:
> Do you have a patch for fakeroot that I can try?

You could try 
https://salsa.debian.org/clint/fakeroot/-/commit/4a946cdc5cba202f888deb4ad831b4a305df7978

Bug#1023378: RM: rust-glutin [i386 mips64el mipsel s390x] -- ROM; new dependency not available on all archs

[James McCoy]

Package: ftp.debian.org
Severity: normal

rust-glutin now transitively depends on rust-tiny-skia(-path) which is
targeting a limited set of architectures currently.

Bug#1023377: RM: rust-winit [i386 mips64el mipsel s390x] -- ROM; new dependency not available on all archs

[James McCoy]

Package: ftp.debian.org
Severity: normal

rust-winit now transitively depends on rust-tiny-skia(-path) which is
targeting a limited set of architectures currently.

Bug#1022939: linux-image-6.0.0-2-amd64: 6.0.0-2-amd64 regressions: Lenovo Carbon X1 gen7 can't suspend, sound card not instantiated

[Akkana Peck]

Diederik:

I haven't seen an updated kernel yet, but yesterday I noticed apt
had an update of firmware-intel-sound, along with a couple other
sound-related packages, so I tried booting into 6.0.0-2-amd64
and now both sound and suspend seem to be working.

I wonder if it was something like 6.0.0-2-amd64 changing something
in the way it deals with sound cards, but the corresponding firmware
update got delayed and didn't get uploaded at the same time.

Anyway, I think this is solved now (fingers crossed that it stays solved :-)

Bug#1023375: ITP: pafish -- Virtual machines detection tool

[Josenilson Ferreira da Silva]

Package: wnpp
Severity: wishlist
Owner: Josenilson Ferreira da Silva 
X-Debbugs-Cc: debian-de...@lists.debian.org, nilsonfsi...@hotmail.com

* Package name: pafish
  Version : 0.6
  Upstream Author : Alberto Ortega 
* URL : https://github.com/a0rtega/pafish
* License : (GPL3
  Programming Lang: C
  Description : Virtual machines detection tool

 As a test tool, Pafish aims to detect virtual machines.
 .
 Making use of various techniques, Pafish is widely used in
 malware analysis environments as well as malware families.

Bug#1023376: dpkg: /usr/share/locale/ja/LC_MESSAGES/dpkg.mo contains a typo

[Kisaragi Marine]

Package: dpkg
Version: 1.20.12
Severity: minor
Tags: l10n patch
X-Debbugs-Cc: kisaragi.effect...@gmail.com

I've found a typo in `/usr/share/locale/ja/LC_MESSAGES/dpkg.mo` which
was introduced by 69fe0265.
To fix this, I applied those commands in bash:

$ msgunfmt /usr/share/locale/ja/LC_MESSAGES/dpkg.mo > /tmp/dpkg-ja.po
$ vim /tmp/dpkg-ja.po # correct typo
$ msgunfmt /usr/share/locale/ja/LC_MESSAGES/dpkg.mo | git diff - /tmp/dpkg-ja.po
diff --git a/- b/tmp/dpkg-ja.po
index 000..0e648e8 100644
--- a/-
+++ b/tmp/dpkg-ja.po
@@ -3644,7 +3644,7 @@ msgstr "updates ディレクトリにあるファイル名の長さが異なり

 msgid "updating alternative %s because link group %s has changed slave links"
 msgstr ""
-"リンクグループ %2$s がスレーブッリンクを変更したため、alternative %1$s を更新"
+"リンクグループ %2$s がスレーブリンクを変更したため、alternative %1$s を更新"
 "しています"

 msgid "user '%s' does not exist"
$ sudo msgfmt /tmp/dpkg-ja.po -o /usr/share/locale/ja/LC_MESSAGES/dpkg.mo

I'd like to commit this patch if I could.

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

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

Kernel: Linux 5.10.0-19-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.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 dpkg depends on:
ii  libbz2-1.0   1.0.8-4
ii  libc62.31-13+deb11u5
ii  liblzma5 5.2.5-2.1~deb11u1
ii  libselinux1  3.1-3
ii  tar  1.34+dfsg-1
ii  zlib1g   1:1.2.11.dfsg-2+deb11u2

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt2.2.4
pn  debsig-verify  

-- no debconf information

Bug#1023374: kwin-x11: kwin_x11 --replace ... yields "symbol lookup error: /lib/x86_64-linux-gnu/libkwin.so.5: undefined symbol: drmModeFormatModifierBlobIterNext"

[Tom Gordon]

Package: kwin-x11
Version: 4:5.26.0-1
Severity: important

Dear Maintainer,

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

   * What led up to the situation? recent update
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
plasma did not have any borders or title bars on its windows, found kwin_x11
was not running ... so attempted to use kwin_x11 --replace
   * What was the outcome of this action?
symbol lookup error: /lib/x86_64-linux-gnu/libkwin.so.5: undefined symbol:
drmModeFormatModifierBlobIterNext
   * What outcome did you expect instead?
kill any existing kwin_x11 instances and start a new kwin_x11 instance.


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


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

Kernel: Linux 6.0.0-2-amd64 (SMP w/24 CPU threads; PREEMPT)
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 kwin-x11 depends on:
ii  kwin-common4:5.26.0-1
ii  libc6  2.35-4
ii  libepoxy0  1.5.10-1
ii  libgcc-s1  12.2.0-3
ii  libkdecorations2-5v5   4:5.26.0-1
ii  libkf5configcore5  5.98.0-1
ii  libkf5configgui5   5.98.0-1
ii  libkf5configwidgets5   5.98.0-1
ii  libkf5coreaddons5  5.98.0-1
ii  libkf5crash5   5.98.0-1
ii  libkf5globalaccel-bin  5.98.0-1
ii  libkf5globalaccel5 5.98.0-1
ii  libkf5i18n55.98.0-1+b1
ii  libkf5notifications5   5.98.0-1
ii  libkf5plasma5  5.98.0-1
ii  libkf5service-bin  5.98.0-1
ii  libkf5service5 5.98.0-1
ii  libkf5windowsystem55.98.0-1
ii  libkwineffects14   4:5.26.0-1
ii  libkwinglutils14   4:5.26.0-1
ii  libqaccessibilityclient-qt5-0  0.4.1-1+b1
ii  libqt5core5a   5.15.6+dfsg-2
ii  libqt5dbus55.15.6+dfsg-2
ii  libqt5gui5 5.15.6+dfsg-2
ii  libqt5qml5 5.15.6+dfsg-2
ii  libqt5quick5   5.15.6+dfsg-2
ii  libqt5widgets5 5.15.6+dfsg-2
ii  libqt5x11extras5   5.15.6-2
ii  libstdc++6 12.2.0-3
ii  libx11-6   2:1.8.1-2
ii  libxcb-composite0  1.15-1
ii  libxcb-keysyms10.4.0-1+b2
ii  libxcb-randr0  1.15-1
ii  libxcb-render0 1.15-1
ii  libxcb-shape0  1.15-1
ii  libxcb-xfixes0 1.15-1
ii  libxcb11.15-1
ii  libxi6 2:1.8-1+b1

kwin-x11 recommends no packages.

kwin-x11 suggests no packages.

-- no debconf information

Bug#1023284: libevent: FTBFS with glibc 2.36

[Samuel Thibault]

Nicolas Mora, le mer. 02 nov. 2022 19:14:51 -0400, a ecrit:
> If I understand correctly, removing the symbols evutil_secure_rng_add_bytes 
> from the symbols files is enough to fix this bug?

It will make the package build again. But possibly some binaries in
Debian are using that symbol, that'd have to be checked before accepting
that this symbol disappears, otherwise those binaries will break.

Samuel

Bug#992269: texlive-bibtex-extra: Missing beebe bst stiles like abstract.bst

[Hilmar Preuße]

Am 02.11.2022 um 17:04 teilte Simone Piccardi mit:

Hi Simone,

The issue is the missing file, abstract.bst it's a quite useful 
bibliography style, that was present from ages and now is not there 
anymore. Don't care too much about the fact is still listed, if it's 
absent in the package.


I had to copy the content of the dir 
/usr/share/texlive/texmf-dist/bibtex/bst/beebe/ from buster and execute 
mktexlsr, but I'd like to know why this directory has been removed 
(while /usr/share/texlive/texmf-dist/bibtex/bib/beebe/ is still there).




AFACT most of the bst files made by Nelson Beebe are gone, even from 
CTAN (at least I couldn't find them). I have no clue, what happened 
here. I'll have a look at that later on.


Hilmar
--
sigfault



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023317: Bug#1023318 / Bug#1023317: {screen,zsh}: re-adds /usr/bin/{screen,zsh} to /etc/shells on upgrade

[Axel Beckert]

Hi Helmut,

thanks for these bug reports and making us aware of this type of
issue.

Some more hints about how this all is meant to work and why it
actually works would have been appreciated, though:

Helmut Grohne wrote:
> When upgrading or reinstalling screen, it adds /usr/bin/screen to
> /etc/shells even if one locally removed it there. Such behaviour
> violates Debian policy section 10.7.3. I propose managing the entry
> declaratively using dpkg triggers and am attaching a patch for your
> convenience.
> + install -D -m644 debian/shells 
> $(ROOT)/usr/share/debianutils/shells.d/screen
[…]
> -  add-shell /usr/bin/screen || true
[…]
> -if [ "$1" = disappear ]; then
> -  remove-shell /usr/bin/screen || true
> -fi

It took me quite a while to where this
/usr/share/debianutils/shells.d/ comes from and where it is this
documented,

/usr/share/doc/debianutils/README.shells.gz clearly states that I
should use add-shell and remove-shell:

| So, if a package contains something that the maintainer thinks ought
| to be a valid login shell, it's postinst should, (on initial install
| only, to allow a sysadmin to take it out again), run:
|
| /usr/sbin/add-shell /path/to/shell
|
| In the postrm, probably on remove, the package should call
| 
| /usr/sbin/remove-shell /path/to/shell
| 
| As the various shells start to use it, the default shells list will
| shrink.

No mention of that directory. The man pages add-shell(8) and
remove-shell(8) don't mention this directory either.

Also can't find it mentioned in
/usr/share/doc/debianutils/changelog.Debian.gz.

I also found no mentioning of triggers inside the functional part of
the patches. So I assume you meant to refer to
/var/lib/dpkg/info/debianutils.triggers (which also seems not to be
mentioned in /usr/share/doc/debianutils/changelog.Debian.gz).

Finally when looking /var/lib/dpkg/info/debianutils.postinst, I found
a pointer to update-shells whose man-page explains that whole
mechanism and also why it actually track changes made by the
administrator. An early pointer to that or #990440 would have been
nice…

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#1023373: bibledit:

[Bastian Germann]

Source: bibledit
Version: 5.0.988-3
Severity: serious
Control: affects -1 bibledit-cloud

This is a follow-up on #1017083.

Aside from the embedded quill still not being built from source,
quill/source/docs/_includes/analytics.html is clearly a non-source
file that applies Google Analytics, which is not acceptable.

Bug#999158: icmpush: diff for NMU version 2.2-6.2

[Marcos Talau]

Control: tags 999158 + patch
Control: tags 999158 + pending


Dear maintainer,

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

Regards.
diff -u icmpush-2.2/debian/changelog icmpush-2.2/debian/changelog
--- icmpush-2.2/debian/changelog
+++ icmpush-2.2/debian/changelog
@@ -1,3 +1,10 @@
+icmpush (2.2-6.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999158).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 20:19:02 -0300
+
 icmpush (2.2-6.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u icmpush-2.2/debian/rules icmpush-2.2/debian/rules
--- icmpush-2.2/debian/rules
+++ icmpush-2.2/debian/rules
@@ -53,4 +53,8 @@
 	dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install

Bug#1023284: libevent: FTBFS with glibc 2.36

[Nicolas Mora]

Hello,

If I understand correctly, removing the symbols evutil_secure_rng_add_bytes 
from the symbols files is enough to fix this bug? If no objection, I'll upload 
the fixed package tomorrow.

Bug#1023372: kde-config-gtk-style: missing dependency on gsettings-desktop-schemas (causes kded5 to crash)

[Alexis Murzeau]

Package: kde-config-gtk-style
Version: 4:5.26.0-1
Severity: important

Dear Maintainer,


   * What led up to the situation?

In a KDE environment and plasma-nm installed, WiFi is not connecting
automatically with the NetworkMaanger error "No agents were available for this
request".
Normally, agent requests are served using the KDE Wallet.

The cause of this is that kded5 wasn't running, thus the service handling agent
requests was probably not running too.

kded5 was not running because it crashed with this error (I've run it with
gdb):

(process:4612): GLib-GIO-ERROR **: 23:53:37.684: Settings schema
'org.gnome.desktop.interface' is not installed

Thread 1 "kded5" received signal SIGTRAP, Trace/breakpoint trap.
0x759287c7 in g_log_structured_array () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
(gdb) bt
#0  0x759287c7 in g_log_structured_array () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#1  0x75928bee in g_log_default_handler () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#2  0x75928e57 in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x759290ef in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fffd8c94a37 in ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x7fffd8b516ed in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6  0x7fffd8b51f98 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x7fffd8b53b33 in g_object_new_valist () from /lib/x86_64-linux-
gnu/libgobject-2.0.so.0
#8  0x7fffd8b54189 in g_object_new () from /lib/x86_64-linux-
gnu/libgobject-2.0.so.0
#9  0x7fffd8ddf340 in ?? () from /usr/lib/x86_64-linux-
gnu/qt5/plugins/kf5/kded/gtkconfig.so
#10 0x7fffd8ddb475 in GtkConfig::setFont() const () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kded/gtkconfig.so
#11 0x7fffd8ddda59 in GtkConfig::applyAllSettings() const () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kded/gtkconfig.so
#12 0x7fffd8dddf99 in GtkConfig::GtkConfig(QObject*, QList
const&) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kded/gtkconfig.so
#13 0x7fffd8ddef69 in ?? () from /usr/lib/x86_64-linux-
gnu/qt5/plugins/kf5/kded/gtkconfig.so
#14 0x7773ead3 in KPluginFactory::create(char const*, QWidget*,
QObject*, QList const&, QString const&) () from /lib/x86_64-linux-
gnu/libKF5CoreAddons.so.5
#15 0xdeee in ?? ()
#16 0x555611a3 in ?? ()
#17 0x55561533 in ?? ()
#18 0xb15e in ?? ()
#19 0x7684618a in __libc_start_call_main
(main=main@entry=0xaa90, argc=argc@entry=1,
argv=argv@entry=0x7fffdfe8) at ../sysdeps/nptl/libc_start_call_main.h:58
#20 0x76846245 in __libc_start_main_impl (main=0xaa90, argc=1,
argv=0x7fffdfe8, init=, fini=,
rtld_fini=,
stack_end=0x7fffdfd8) at ../csu/libc-start.c:381
#21 0xb541 in ?? ()
(gdb)

The crash occurs in gtkconfig.so kded5 plugin (installed by kde-config-gtk-
style pacakge) because gsettings-desktop-schemas is not installed.

After having installed this package, everything is back working as expected
(and the wifi connects once I input the asked KWallet password on login).



Thus, I think that kde-config-gtk-style should depends on gsettings-desktop-
schemas.

This does not apply to kde-config-gtk-style-preview which won't cause any
crashes even if gsettings-desktop-schemas is not installed (as long as kde-
config-gtk-style is not installed).



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

Kernel: Linux 6.0.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr:en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kde-config-gtk-style depends on:
ii  libc6 2.35-3
ii  libglib2.0-0  2.74.0-3
ii  libgtk-3-03.24.34-3
ii  libkdecorations2-5v5  4:5.26.0-1
ii  libkdecorations2private9  4:5.26.0-1
ii  libkf5configcore5 5.98.0-1
ii  libkf5configwidgets5  5.98.0-1
ii  libkf5coreaddons5 5.98.0-1
ii  libkf5dbusaddons5 5.98.0-1
ii  libkf5guiaddons5  5.98.0-2
ii  libqt5core5a  5.15.6+dfsg-2
ii  libqt5dbus5   5.15.6+dfsg-2
ii  libqt5gui55.15.6+dfsg-2
ii  libqt5svg55.15.6-2
ii  libstdc++612.2.0-7

Versions of packages kde-config-gtk-style recommends:
pn  xsettingsd | xsettings-kde  

Versions of packages kde-config-gtk-style suggests:
pn  kde-config-gtk-style-preview  

-- no debconf information

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


OpenPGP_signature
Description: OpenPGP digital signature

Bug#999090: icheck: diff for NMU version 0.9.7-6.4

[Marcos Talau]

Control: tags 999090 + patch
Control: tags 999090 + pending


Dear maintainer,

I've prepared an NMU for icheck (versioned as 0.9.7-6.4) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u icheck-0.9.7/debian/changelog icheck-0.9.7/debian/changelog
--- icheck-0.9.7/debian/changelog
+++ icheck-0.9.7/debian/changelog
@@ -1,3 +1,10 @@
+icheck (0.9.7-6.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999090).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 20:15:09 -0300
+
 icheck (0.9.7-6.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u icheck-0.9.7/debian/rules icheck-0.9.7/debian/rules
--- icheck-0.9.7/debian/rules
+++ icheck-0.9.7/debian/rules
@@ -49,4 +49,8 @@
 	dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install 
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install 

Bug#1018004: qt6-tools: does not build and link with system litehtml

[Patrick Franz]

Hi again,

actually, screw the last message...I should've read and tried the 
entire(!!) patch and not just a part of it :-(.


-- 
Med vänliga hälsningar

Patrick Franz

Bug#999170: grpn: diff for NMU version 1.4.1-1.1

[Marcos Talau]

Control: tags 999170 + patch
Control: tags 999170 + pending


Dear maintainer,

I've prepared an NMU for grpn (versioned as 1.4.1-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru grpn-1.4.1/debian/changelog grpn-1.4.1/debian/changelog
--- grpn-1.4.1/debian/changelog	2017-11-12 06:53:32.0 -0200
+++ grpn-1.4.1/debian/changelog	2022-11-02 20:11:17.0 -0300
@@ -1,3 +1,10 @@
+grpn (1.4.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999170).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 20:11:17 -0300
+
 grpn (1.4.1-1) unstable; urgency=low
 
   [ Jens Getreu  ]
diff -Nru grpn-1.4.1/debian/rules grpn-1.4.1/debian/rules
--- grpn-1.4.1/debian/rules	2017-11-12 06:41:00.0 -0200
+++ grpn-1.4.1/debian/rules	2022-11-02 20:11:17.0 -0300
@@ -57,4 +57,7 @@
 
 binary: binary-indep binary-arch
 
-.PHONY: build clean binary-indep binary-arch binary
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary

Bug#999299: gpsim-doc: diff for NMU version 0.22.0-2.2

[Marcos Talau]

Control: tags 999299 + patch
Control: tags 999299 + pending


Dear maintainer,

I've prepared an NMU for gpsim-doc (versioned as 0.22.0-2.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u gpsim-doc-0.22.0/debian/changelog gpsim-doc-0.22.0/debian/changelog
--- gpsim-doc-0.22.0/debian/changelog
+++ gpsim-doc-0.22.0/debian/changelog
@@ -1,3 +1,10 @@
+gpsim-doc (0.22.0-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999299).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 20:08:20 -0300
+
 gpsim-doc (0.22.0-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u gpsim-doc-0.22.0/debian/rules gpsim-doc-0.22.0/debian/rules
--- gpsim-doc-0.22.0/debian/rules
+++ gpsim-doc-0.22.0/debian/rules
@@ -47,4 +47,8 @@
 	dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install configure

Bug#998967: gnuboy: diff for NMU version 1.0.3-7.2

[Marcos Talau]

Control: tags 998967 + patch
Control: tags 998967 + pending


Dear maintainer,

I've prepared an NMU for gnuboy (versioned as 1.0.3-7.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u gnuboy-1.0.3/debian/changelog gnuboy-1.0.3/debian/changelog
--- gnuboy-1.0.3/debian/changelog
+++ gnuboy-1.0.3/debian/changelog
@@ -1,3 +1,11 @@
+gnuboy (1.0.3-7.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Bump debhelper compat to 7.
+  * debian/rules: Add build-{arch,indep} (Closes: #998967).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 19:51:44 -0300
+
 gnuboy (1.0.3-7.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u gnuboy-1.0.3/debian/compat gnuboy-1.0.3/debian/compat
--- gnuboy-1.0.3/debian/compat
+++ gnuboy-1.0.3/debian/compat
@@ -1 +1 @@
-5
+7
diff -u gnuboy-1.0.3/debian/control gnuboy-1.0.3/debian/control
--- gnuboy-1.0.3/debian/control
+++ gnuboy-1.0.3/debian/control
@@ -2,7 +2,7 @@
 Section: contrib/games
 Priority: optional
 Maintainer: Davide Puricelli (evo) 
-Build-Depends: debhelper (>> 5), libx11-dev, libxext-dev, libxt-dev, x11proto-xext-dev, libsdl1.2-dev, libaa1-dev, libncurses5-dev  
+Build-Depends: debhelper (>= 7), libx11-dev, libxext-dev, libxt-dev, x11proto-xext-dev, libsdl1.2-dev, libaa1-dev, libncurses5-dev  
 Standards-Version: 3.8.3.0
 
 Package: gnuboy-sdl
diff -u gnuboy-1.0.3/debian/rules gnuboy-1.0.3/debian/rules
--- gnuboy-1.0.3/debian/rules
+++ gnuboy-1.0.3/debian/rules
@@ -48,4 +48,8 @@
 	dh_builddeb -a
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary 
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary 

Bug#1023371: plocate.postint requires a depedency on adduser

[Alexandre Detiste]

Package: plocate
Version: 1.1.16-1+b1
Severity: important

Hi,

"adduser" is priority 'important', not 'essential'.

The postinst script will fail if this tool
was not installed beforehand.


Installation failed in a piuparts chroot,
I'm not sur it's even possible in real life.

https://piuparts.debian.org/sid-strict/fail/cruft-ng_0.9.47.log

But as far as I understand this bug could
block the migration of my package "cruft-ng".

Easiest way to solve it on your
side would be to pre-depends on "adduser",
if I'm correct.

Greetings,

Alexandre


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

Kernel: Linux 6.0.0-2-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages plocate depends on:
ii  libc6   2.35-4
ii  libgcc-s1   12.2.0-3
ii  libstdc++6  12.2.0-3
ii  liburing2   2.2-2
ii  libzstd11.5.2+dfsg-1

plocate recommends no packages.

Versions of packages plocate suggests:
ii  powermgmt-base  1.37
ii  systemd-sysv251.6-1

-- no debconf information

Bug#1018004: qt6-tools: does not build and link with system litehtml

[Patrick Franz]

Hi,

I tried enabling system litehtml by adding liblitehtml-dev as a B-D
(version 0.6 of litehtml supposedly fixes the issue) and litehtml is indeed 
found by qttools.

However, the build fails because of

In file included from 
/<>/src/assistant/qlitehtml/src/container_qpainter.cpp:5:
/<>/src/assistant/qlitehtml/src/container_qpainter_p.h:8:10: fatal 
error: litehtml.h: No such file or directory
8 | #include 
  |  ^~~~
compilation terminated.

It seems that while system litehtml is now found, /usr/include/litehtml/ is not 
included by gcc/g++:

[327/632] /usr/lib/ccache/c++ -DQLITEHTML_STATIC_LIBRARY -DQT_CORE_LIB 
-DQT_GUI_LIB
-DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_JAVA_STYLE_ITERATORS 
-DQT_RESTRICTED_CAST_FROM_ASCII
-DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB 
-I/<>/obj-x86_64-linux-gnu/src/assistant/qlitehtml/src/qlitehtml_autogen/include
-I/<>/src/assistant/qlitehtml/src -isystem 
/usr/include/x86_64-linux-gnu/qt6/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt6
-isystem /usr/include/x86_64-linux-gnu/qt6/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt6/mkspecs/linux-g++
-isystem /usr/include/x86_64-linux-gnu/qt6/QtGui -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-fvisibility=hidden -fvisibility-inlines-hidden -w -fPIC -std=c++17
-MD -MT 
src/assistant/qlitehtml/src/CMakeFiles/qlitehtml.dir/container_qpainter.cpp.o
-MF 
src/assistant/qlitehtml/src/CMakeFiles/qlitehtml.dir/container_qpainter.cpp.o.d
-o src/assistant/qlitehtml/src/CMakeFiles/qlitehtml.dir/container_qpainter.cpp.o
-c /<>/src/assistant/qlitehtml/src/container_qpainter.cpp


-- 
Med vänliga hälsningar

Patrick Franz

Bug#999267: g3data: diff for NMU version 1:1.5.3-3.1

[Marcos Talau]

Control: tags 999267 + patch
Control: tags 999267 + pending


Dear maintainer,

I've prepared an NMU for g3data (versioned as 1:1.5.3-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u g3data-1.5.3/debian/changelog g3data-1.5.3/debian/changelog
--- g3data-1.5.3/debian/changelog
+++ g3data-1.5.3/debian/changelog
@@ -1,3 +1,10 @@
+g3data (1:1.5.3-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999267).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 19:47:41 -0300
+
 g3data (1:1.5.3-3) unstable; urgency=medium
 
   * Bug fix FTCBFS, thanks to Helmut Grohne  for the
diff -u g3data-1.5.3/debian/rules g3data-1.5.3/debian/rules
--- g3data-1.5.3/debian/rules
+++ g3data-1.5.3/debian/rules
@@ -79,4 +79,8 @@
 	dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install configure

Bug#1023370: [php-parser] Failing tests with PHP 8.2

[David Prévot]

Package: php-parser
Version: 4.15.1-1
Severity: important
Control: block 1014460 by -1

There are some tests failure under PHP 8.2 (rc5).

https://qa.debian.org/excuses.php?experimental=1=php-defaults


signature.asc
Description: PGP signature

Bug#999330: floatbg: diff for NMU version 1.0-28.1

[Marcos Talau]

Control: tags 999330 + patch
Control: tags 999330 + pending


Dear maintainer,

I've prepared an NMU for floatbg (versioned as 1.0-28.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u floatbg-1.0/debian/rules floatbg-1.0/debian/rules
--- floatbg-1.0/debian/rules
+++ floatbg-1.0/debian/rules
@@ -54,4 +54,8 @@
 	@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary
diff -u floatbg-1.0/debian/changelog floatbg-1.0/debian/changelog
--- floatbg-1.0/debian/changelog
+++ floatbg-1.0/debian/changelog
@@ -1,3 +1,10 @@
+floatbg (1.0-28.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999330).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 19:42:42 -0300
+
 floatbg (1.0-28) unstable; urgency=low
 
   * hacked in support for running under Xfce 4.6 or later (-xfce flag)

Bug#1023369: ITP: s2n-tls -- C99 implementation of the TLS/SSL protocols

[Noah Meyerhans]

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

* Package name: s2n-tls
  Version : 1.3.26
  Upstream Author : Amazon Web Services
* URL : https://github.com/aws/s2n-tls
* License : Apache 2.0
  Programming Lang: C
  Description : C99 implementation of the TLS/SSL protocols

 s2n-tls is a C99 implementation of the TLS/SSL protocols that is
 designed to be simple, small, fast, and with security as a
 priority. It is released and licensed under the Apache License 2.0.
 .
 The s2n-tls I/O APIs are designed to be intuitive to developers
 familiar with the widely-used POSIX I/O APIs, and s2n-tls supports
 blocking, non-blocking, and full-duplex I/O. Additionally there are
 no locks or mutexes within s2n-tls.
 .
 s2n-tls implements SSLv3, TLS1.0, TLS1.1, and TLS1.2. For encryption,
 s2n-tls supports 128-bit and 256-bit AES, in the CBC and GCM modes,
 ChaCha20, 3DES, and RC4. For forward secrecy, s2n-tls supports both
 DHE and ECDHE. s2n-tls also supports the Server Name Indicator (SNI),
 Application-Layer Protocol Negotiation (ALPN) and the Online
 Certificate Status Protocol (OCSP) TLS extensions. SSLv3, RC4, 3DES
 and DHE are each disabled by default for security reasons.
 .
 As it can be difficult to keep track of which encryption algorithms
 and protocols are best to use, s2n-tls features a simple API to use
 the latest "default" set of preferences. If you prefer to remain on a
 specific version for backwards compatibility, that is also supported.

This package will be maintained by the cloud team.  Initial packaging is
being driven by the awscli package, version 2 of which will depend on this
package.

Bug#998942: farpd: diff for NMU version 0.2-11.1

[Marcos Talau]

Control: tags 998942 + patch
Control: tags 998942 + pending


Dear maintainer,

I've prepared an NMU for farpd (versioned as 0.2-11.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u farpd-0.2/debian/rules farpd-0.2/debian/rules
--- farpd-0.2/debian/rules
+++ farpd-0.2/debian/rules
@@ -90,4 +90,8 @@
 	dh_builddeb -a
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install 
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install 
diff -u farpd-0.2/debian/changelog farpd-0.2/debian/changelog
--- farpd-0.2/debian/changelog
+++ farpd-0.2/debian/changelog
@@ -1,3 +1,10 @@
+farpd (0.2-11.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #998942).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 19:34:16 -0300
+
 farpd (0.2-11) unstable; urgency=low
 
   * configure.in: Fix FTBFS: configure: error: libevent not found with the

Bug#1023368: trousers: invalid test at line 32

[Lukasz Stelmach]

File: /etc/init.d/trousers
Package: trousers
Version: 0.3.14+fixed1-1.2
Severity: normal
X-Debbugs-Cc: none

Dear Maintainer,

The trousers startup script fails with the following messages in the
journal.

--8<---cut here---start->8---
Nov 02 17:37:12 darkstar trousers[179711]: Starting Trusted Computing daemon: 
tcsd/etc/init.d/trousers: 32: [: /dev/tpm0: unexpected operator
Nov 02 17:37:12 darkstar tcsd[179717]: TCSD TDDL[179717]: TrouSerS ioctl: (25) 
Inappropriate ioctl for device
Nov 02 17:37:12 darkstar tcsd[179717]: TCSD TDDL[179717]: TrouSerS Falling back 
to Read/Write device support.
Nov 02 17:37:12 darkstar tcsd[179717]: TCSD TCS[179717]: TrouSerS ERROR: TCS 
GetCapability failed with result = 0x1e
Nov 02 17:37:12 darkstar trousers[179718]:  failed!
Nov 02 17:37:12 darkstar systemd[1]: trousers.service: Control process exited, 
code=exited, status=30/n/a
Nov 02 17:37:12 darkstar systemd[1]: trousers.service: Failed with result 
'exit-code'.
Nov 02 17:37:12 darkstar systemd[1]: Failed to start LSB: starts tcsd.
--8<---cut here---end--->8---

The line 32 mentioned above is

  if [ ! -e /dev/tpm* ]
 
which fails because there are two files that match the pattern

--8<---cut here---start->8---
$ ls -l /dev/tpm*
crw-rw 1 tss root  10,   224 Nov  2 05:30 /dev/tpm0
crw-rw 1 tss tss  244, 65536 Nov  2 05:30 /dev/tpmrm0
--8<---cut here---end--->8---

One possible way to fix it is to change the test to

if ! ls /dev/tpm* >/dev/null 2>&1


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

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

Versions of packages trousers depends on:
ii  libc6  2.31-13+deb11u5
ii  libssl1.1  1.1.1n-0+deb11u3
ii  lsb-base   11.1.0
ii  tpm-udev   0.5

trousers recommends no packages.

trousers suggests no packages.

-- Configuration Files:
/etc/tcsd.conf [Errno 13] Brak dostępu: '/etc/tcsd.conf'

-- no debconf information

-- 
Łukasz Stelmach
Samsung R Institute Poland
Samsung Electronics


signature.asc
Description: PGP signature

Bug#1023367: ITP: plasma-phonebook -- Phone book for Plasma Mobile

[Marco Mattiolo]

Package: wnpp
Severity: wishlist
Owner: Marco Mattiolo 
X-Debbugs-Cc: debian-de...@lists.debian.org, marco.matti...@hotmail.it

* Package name    : plasma-phonebook
  Version : 22.09
  Upstream Author : 
* URL : https://invent.kde.org/plasma-mobile/plasma-phonebook
* License : GPL
  Programming Lang: QML, C++
  Description : Phone book for Plasma Mobile

Contacts application which allows adding, modifying and removing contacts.

Bug#1019417: Problem reproduced

[John Doe]

I observed the OOM problem again in my fresh Debian linux installation. The
steps to reproduce it are as follows

1. Install Debian
2. Connect to a wifi network
3. Wait for wpa_supplicant to use all the memory and observe the OOM killer
message

Bug#1017711: emacs-gtk: terminated with signal SIGABRT, 137 MB coredump

[Sean Whitton]

Hello Vincent,

Upstream says there isn't enough information in the backtrace to say
anything helpful about this.  Could you take a look at
 and consider supplying more information
over there, please?

Also, are you able to reproduce this with 'emacs -q' (not -Q)?

Currently we have no way to reproduce this, and you're the only person
who's seen anything like this, so we'll probably have to move the
severity back down to 'important'.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1023366: can appstream be marked Multi-Arch: foreign?

[Helmut Grohne]

Package: appstream

When cross building gthumb, appstreamcli fails to run with an Exec
format error. This is a clue that maybe appstream should be marked
Multi-Arch: foreign. Such a marking is only correct if appstream
provides an architcture-independent interface. It seems that the main
way to interact with the appstream package is invoking the appstreamcli
tool. This is a good start for Multi-Arch: foreign. What is not clear
from the manual page though is whether the architecture of the
appstreamcli binary plays a role in its operation or whether it behaves
the same way on all architectures. Would you be able to shed some light
on this?

If it cannot, gthumb should likely annotate its appstream dependency
with :native.

Helmut

Bug#1023365: prusa-slicer: Wrong wxWidgets Version linked during debian Build resulting in instant SIGSEGV on launch (due to lacking wxWidgets 3.2 support)

[vertuxt]

Package: prusa-slicer
Version: 2.5.0+dfsg-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: t...@beamnet.de, t...@debian.org, onit...@gmail.com

The wrong wxWidgets Version is linked during the build. Normally debian/rules
specifies WX_STABLE=1 which should result in the usage of wxWidgets 3.0 which
is in stable. However, wx-config always returns wx3.2 which is then used by
CMake even if CMakeLists.txt is changed to especially require wxWidgets 3.0
and wx-config options set to --version=3.0.


As already stated in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022234
and
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020702 upstream does not
have wxWidgets 3.2 support yet.

I verified, the package is usable if linked against wxWidgets 3.0 by setting my
wx-config alternative to 3.0 (update-alternatives).

BR Jan


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

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

Versions of packages prusa-slicer depends on:
ii  fonts-noto-hinted  20201225-1
ii  libboost-chrono1.74.0  1.74.0-17
ii  libboost-filesystem1.74.0  1.74.0-17
ii  libboost-iostreams1.74.0   1.74.0-17
ii  libboost-locale1.74.0  1.74.0-17
ii  libboost-log1.74.0 1.74.0-17
ii  libboost-regex1.74.0 [libboost-regex1.74.0-icu71]  1.74.0-17
ii  libboost-thread1.74.0  1.74.0-17
ii  libc6  2.35-4
ii  libcurl3-gnutls    7.85.0-1
ii  libdbus-1-3    1.14.4-1
ii  libexpat1  2.5.0-1
ii  libgcc-s1  12.2.0-3
ii  libgl1 1.5.0-1
ii  libglew2.2 2.2.0-4+b1
ii  libglib2.0-0   2.74.1-1
ii  libgmp10   2:6.2.1+dfsg1-1.1
ii  libgtk-3-0 3.24.34-3
ii  libimath-3-1-29    3.1.5-1+b1
ii  libjpeg62-turbo    1:2.1.2-1+b1
ii  libmpfr6   4.1.0-3
ii  libnlopt0  2.7.1-4+b2
ii  libocct-data-exchange-7.6  7.6.3+dfsg1-5
ii  libocct-foundation-7.6 7.6.3+dfsg1-5
ii  libocct-modeling-algorithms-7.6    7.6.3+dfsg1-5
ii  libocct-modeling-data-7.6  7.6.3+dfsg1-5
ii  libocct-ocaf-7.6   7.6.3+dfsg1-5
ii  libopenvdb9.1  9.1.0-7+b1
ii  libpng16-16    1.6.38-2
ii  libstdc++6 12.2.0-3
ii  libtbb12   2021.5.0-15
ii  libwxbase3.2-0 3.2.1+dfsg-1
ii  libwxgtk3.2-0  3.2.1+dfsg-1

prusa-slicer recommends no packages.

prusa-slicer suggests no packages.

-- no debconf information

Bug#1023364: yelp: info: can't handle "/" in node names

[Jakub Wilk]

Package: yelp
Version: 3.38.3-1

Yelp's info viewer doesn't seem to handle the "/" character in node 
names correctly. To reproduce, run


yelp info:'(coreutils)Traversing_symlinks'

then click the "Treating / specially" link at the top. You will get the 
following error message:


The URI ‘man:coreutils/Treating_’ does not point to a valid page.


-- System Information:
Debian Release: 11.5
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: i386 (i686)

Versions of packages yelp depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-2
ii  libc62.31-13+deb11u4
ii  libglib2.0-0 2.66.8-1
ii  libgtk-3-0   3.24.24-4+deb11u2
ii  libwebkit2gtk-4.0-37 2.38.0-1~deb11u1
ii  libyelp0 3.38.3-1
ii  man-db   2.9.4-2
ii  python3-distro   1.5.0-1
ii  yelp-xsl 3.38.3-1

--
Jakub Wilk

Bug#1023154: RFP: hypnotix -- IPTV player

[Fabio Fantoni]

Il 02/11/2022 20:22, Thomas Uhle ha scritto:

On Sun, 30 Oct 2022, Fabio Fantoni wrote:


Il 30/10/2022 20:20, Thomas Uhle ha scritto:
> [...]
> > Hypnotix is an application to watch TV by streaming from M3U 
sources.
> It is primarily developed for the Cinnamon desktop in Linux Mint 
but could > be used in any other desktop environment as well.
> I don't use an IPTV, I tried shortly kodi but I am not used enough 
about this type of program.


It should be seen which others are packaged in debian besides kodi (I 
know only it) and if hypnotix has anything better than these to 
determine if it is worth adding hypnotix in debian.


can you tell something about?


You are right, Kodi is a good program for watching IPTV. But it is 
also so much more: DVB, DLNA client as well as a client for 
video-on-demand or podcast services to name just a few more features. 
It is a full-grown media center solution and as such installs on disk 
with 100MB at least (not counting the various dependencies). Hypnotix 
has only one feature compared to Kodi that is being a simple-to-use 
and lean application for watching IPTV. It uses libmpv.so to 
seamlessly embed mpv as a player and so only needs about 1MB of extra 
space on disk. That means it is quite small compared to Kodi.
Hypnotix can consume the same M3U lists like Kodi, so you could use 
one of the links provided by kodinerds.net for instance to get an 
up-to-date list of TV stations. IMHO the usual suspects of media 
players like VLC and alike are not suited for these types of M3U lists 
because these lists contain the URLs for many TV stations in one file 
whereas those media players expect that each M3U file corresponds to 
exactly one TV station (and different URLs just refer to streams with 
different resolutions, bit rates, subtitles, etc., but all for the 
same TV station). Moreover, those media players would not 
automatically update the M3U lists (which is what Hypnotix does). You 
would need to manually synchronize the URLs of the TV stations.
In addition I think, sometimes it is just good to have an alternative, 
especially if there is a simple, small and ready-to-go solution for 
something that just works. Anyway, nobody would be asking why there 
are several reincarnations of GNOME's file manager Nautilus in Debian 
(like Caja, Nemo or Peony).



I don't see strong links with cinnamon from a quick look (the 
dependency with xapp is minor) so it could be maintained by another 
team or maintainer as well (if anyone will want maintain it)


That is right. Hypnotix is as much connected to Cinnamon as any other 
appliction from the XApps family (cf. xed or xviewer for instance with 
the corresponding RFP requests #830598 and #830616 respectively). Just 
because it is linked to (lib)xapp, does not mean it is needed for 
Cinnamon.


Thanks for the informations and from what you say it seems worth adding, 
but I have too few time and probably is better not maintain additional 
packages for me, mostly in that case that I'll not use it and where I'll 
need to do specific tests only for packaging/maintain it.


I specified the fact that it could be maintained by others to not block 
if anyone was interested but seeing the cinnamon team in the middle gave up.


About many filemanager forked by nautilus is because each is connected 
to a DE (also fork) and optimized for that DE.


I would prefer that there were fewer forks possible to have better 
supported software and not waste resources but unfortunately this is 
often difficult. One good example where forks was merged to join forces 
in one better project is memtest86+ (with pcmemtest)




OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023363: mark python3-pyparsing Multi-Arch: foreign

[Helmut Grohne]

Package: python3-pyparsing
Version: 3.0.7-2
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
Control: affects -1 + src:epigrass

Around 700 source packages cannot satisfy their cross Build-Depends,
because their transitive dependency on python3-pyparsing is not cross
satisfiable. src:epigrass is a random example. In general, Architecture:
all packages can never satisfy cross Build-Depends unless marked
Multi-Arch: foreign or annotated :native. In this case, I think that the
foreign marking is warranted, because pyparsing is a pure Python module
that does not depend on any other modules (and thus in particular does
not depend on extension modules outside the stdlib). Please consider
applying the attached patch.

Helmut
diff --minimal -Nru pyparsing-3.0.7/debian/changelog 
pyparsing-3.0.7/debian/changelog
--- pyparsing-3.0.7/debian/changelog2022-04-06 17:23:34.0 +0200
+++ pyparsing-3.0.7/debian/changelog2022-11-02 22:12:52.0 +0100
@@ -1,3 +1,10 @@
+pyparsing (3.0.7-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Mark python3-pyparsing Multi-Arch: foreign. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 02 Nov 2022 22:12:52 +0100
+
 pyparsing (3.0.7-2) unstable; urgency=medium
 
   * Team upload.
diff --minimal -Nru pyparsing-3.0.7/debian/control 
pyparsing-3.0.7/debian/control
--- pyparsing-3.0.7/debian/control  2022-04-06 17:23:34.0 +0200
+++ pyparsing-3.0.7/debian/control  2022-11-02 22:12:48.0 +0100
@@ -45,6 +45,7 @@
 
 Package: python3-pyparsing
 Architecture: all
+Multi-Arch: foreign
 Depends:
  ${misc:Depends},
  ${python3:Depends},

Bug#1023362: mark lowdown Multi-Arch: foreign

[Helmut Grohne]

Package: lowdown
Version: 0.10.0-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + src:libmaxminddb

libmaxminddb fails to cross build from source, because it fails to run
lowdown. This is due to lowdown being installed for the host
architecture. The usual fix for this is marking the affected package
(lowdown) Multi-Arch: foreign. In this case, I think that such a marking
is technically correct, because lowdown exclusively deals with textual
formats and thus does not exhibit any architecture-dependent aspects.
Please consider applying the attached patch.

Helmut
diff --minimal -Nru lowdown-0.10.0/debian/changelog 
lowdown-0.10.0/debian/changelog
--- lowdown-0.10.0/debian/changelog 2021-11-13 15:47:41.0 +0100
+++ lowdown-0.10.0/debian/changelog 2022-11-02 21:44:45.0 +0100
@@ -1,3 +1,10 @@
+lowdown (0.10.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Mark lowdown Multi-Arch: foreign. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 02 Nov 2022 21:44:45 +0100
+
 lowdown (0.10.0-1) unstable; urgency=medium
 
   * New upstream release.
diff --minimal -Nru lowdown-0.10.0/debian/control lowdown-0.10.0/debian/control
--- lowdown-0.10.0/debian/control   2021-11-13 15:47:14.0 +0100
+++ lowdown-0.10.0/debian/control   2022-11-02 21:39:00.0 +0100
@@ -15,6 +15,7 @@
 
 Package: lowdown
 Architecture: any
+Multi-Arch: foreign
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: Simple markdown translator
  Lowdown is a Markdown translator producing HTML5, roff documents in the ms and

Bug#999280: empire-lafe: diff for NMU version 1.1-1.1

[Marcos Talau]

Control: tags 999280 + patch
Control: tags 999280 + pending


Dear maintainer,

I've prepared an NMU for empire-lafe (versioned as 1.1-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u empire-lafe-1.1/debian/changelog empire-lafe-1.1/debian/changelog
--- empire-lafe-1.1/debian/changelog
+++ empire-lafe-1.1/debian/changelog
@@ -1,3 +1,10 @@
+empire-lafe (1.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999280).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 18:09:17 -0300
+
 empire-lafe (1.1-1) unstable; urgency=low
 
   * New upstream (Closes: #554326)
diff -u empire-lafe-1.1/debian/rules empire-lafe-1.1/debian/rules
--- empire-lafe-1.1/debian/rules
+++ empire-lafe-1.1/debian/rules
@@ -68,4 +68,8 @@
 	@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary

Bug#1023361: jupyter-core: CVE-2022-39286: Execution with Unnecessary Privileges in JupyterApp

[Salvatore Bonaccorso]

Source: jupyter-core
Version: 4.11.1-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for jupyter-core.

CVE-2022-39286[0]:
| Jupyter Core is a package for the core common functionality of Jupyter
| projects. Jupyter Core prior to version 4.11.2 contains an arbitrary
| code execution vulnerability in `jupyter_core` that stems from
| `jupyter_core` executing untrusted files in CWD. This vulnerability
| allows one user to run code as another. Version 4.11.2 contains a
| patch for this issue. There are no known workarounds.


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-39286
https://www.cve.org/CVERecord?id=CVE-2022-39286
[1] 
https://github.com/jupyter/jupyter_core/security/advisories/GHSA-m678-f26j-3hrp
[2] 
https://github.com/jupyter/jupyter_core/commit/1118c8ce01800cb689d51f655f5ccef19516e283

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1023360: singular-doc: info file in /usr/share/doc

[Jakub Wilk]

Package: singular-doc
Version: 1:4.2.1-p3+ds-2

singular-doc ships the info file in /usr/share/doc/singular/.
But per Policy §12.2, info files should be installed in 
/usr/share/info/.


--
Jakub Wilk

Bug#1023151: Recommends unneeded gist instead of netcat

[Fabio Fantoni]

Il 02/11/2022 18:00, Thomas Uhle ha scritto:


Ciao Fabio,

thanks for the immediate response!

I've had a quick look at your commits and so have one minor remark. 
/usr/bin/nc is handled by update-alternatives and both packages 
netcat-openbsd and netcat-traditional have "Provides: netcat", so you 
also could simply use netcat as dependency instead, similar to other 
packages in Debian like foomatic-db-engine, virt-viewer or playonlinux 
for instance.


Best regards,

Thomas Uhle


thanks for the information, I had quickly made that change and a test 
but not being sure and not having checked the different netcat before I 
wanted to be sure


I also added a patch in cinnamon to change the upload-system-info path 
(https://salsa.debian.org/cinnamon-team/cinnamon/-/commits/master)


I'll do other improvements and upload probably in the weekend if I'll 
have time





OpenPGP_signature
Description: OpenPGP digital signature

Bug#999207: dsh: diff for NMU version 0.25.10-1.5

[Marcos Talau]

Control: tags 999207 + patch
Control: tags 999207 + pending


Dear maintainer,

I've prepared an NMU for dsh (versioned as 0.25.10-1.5) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u dsh-0.25.10/debian/changelog dsh-0.25.10/debian/changelog
--- dsh-0.25.10/debian/changelog
+++ dsh-0.25.10/debian/changelog
@@ -1,3 +1,10 @@
+dsh (0.25.10-1.5) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999207).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 18:03:11 -0300
+
 dsh (0.25.10-1.4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u dsh-0.25.10/debian/rules dsh-0.25.10/debian/rules
--- dsh-0.25.10/debian/rules
+++ dsh-0.25.10/debian/rules
@@ -85,4 +85,8 @@
 	dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install configure

Bug#999031: dircproxy: diff for NMU version 1.0.5-6.1

[Marcos Talau]

Control: tags 999031 + patch
Control: tags 999031 + pending


Dear maintainer,

I've prepared an NMU for dircproxy (versioned as 1.0.5-6.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u dircproxy-1.0.5/debian/changelog dircproxy-1.0.5/debian/changelog
--- dircproxy-1.0.5/debian/changelog
+++ dircproxy-1.0.5/debian/changelog
@@ -1,3 +1,10 @@
+dircproxy (1.0.5-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999031).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 17:57:57 -0300
+
 dircproxy (1.0.5-6) unstable; urgency=medium
 
   * Upgrade to debhelper 9. (Closes: #817431)
diff -u dircproxy-1.0.5/debian/rules dircproxy-1.0.5/debian/rules
--- dircproxy-1.0.5/debian/rules
+++ dircproxy-1.0.5/debian/rules
@@ -80,4 +80,8 @@
 	dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install configure

Bug#999186: deps: diff for NMU version 0.13-4.2

[Marcos Talau]

Control: tags 999186 + patch
Control: tags 999186 + pending


Dear maintainer,

I've prepared an NMU for deps (versioned as 0.13-4.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u deps-0.13/debian/changelog deps-0.13/debian/changelog
--- deps-0.13/debian/changelog
+++ deps-0.13/debian/changelog
@@ -1,3 +1,10 @@
+deps (0.13-4.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999186).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 17:52:37 -0300
+
 deps (0.13-4.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -u deps-0.13/debian/rules deps-0.13/debian/rules
--- deps-0.13/debian/rules
+++ deps-0.13/debian/rules
@@ -76,4 +76,8 @@
 	@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary

Bug#1021668: [Pkg-xen-devel] Bug#1021668: xen: CVE-2022-33749 CVE-2022-33748 CVE-2022-33747 CVE-2022-33746

[Salvatore Bonaccorso]

Hi,

On Wed, Nov 02, 2022 at 08:02:26PM +0100, Hans van Kranenburg wrote:
> Hi,
> 
> On 10/19/22 21:55, Moritz Muehlenhoff wrote:
> >>> For the latest set of Xen issues my estimate is that we can postpone
> >>> them until the next batch, they seem all of moderate/limited impact.
> >>> But let me know if you think otherwise.
> >>
> >> I agree. Let's do them together with the new stuff that's planned for
> >> Nov 1st, https://xenbits.xen.org/xsa/
> > 
> > Ack, I've updated the Security Tracker.
> 
> I'm having a look at this now, and while writing the changelog entry, I
> run into the following thing:
> 
> XSA-403 has 4 CVE numbers. AFAIUI the first two are about the fixes done
> to Linux, and the other two are about changes to Xen. Shouldn't the
> Debian security tracker reflect that?
> 
> CVE-2022-26365 CVE-2022-33740 -> src:linux only ?
> CVE-2022-33741 CVE-2022-33742 -> src:xen only ?

Speaking for src:linux I do not think we need to change the tracking:

CVE-2022-26365: 2f446ffe9d73 ("xen/blkfront: fix leaking data in shared pages")
CVE-2022-33740: 307c8de2b023 ("xen/netfront: fix leaking data in shared pages")
CVE-2022-33741: 4491001c2e0f ("xen/netfront: force data bouncing when backend 
is untrusted")
CVE-2022-33742: 2400617da7ee ("xen/blkfront: force data bouncing when backend 
is untrusted")

Regards,
Salvatore

Bug#999145: cappuccino: diff for NMU version 0.5.1-10.1

[Marcos Talau]

Control: tags 999145 + patch
Control: tags 999145 + pending


Dear maintainer,

I've prepared an NMU for cappuccino (versioned as 0.5.1-10.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u cappuccino-0.5.1/debian/changelog cappuccino-0.5.1/debian/changelog
--- cappuccino-0.5.1/debian/changelog
+++ cappuccino-0.5.1/debian/changelog
@@ -1,3 +1,10 @@
+cappuccino (0.5.1-10.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999145).
+
+ -- Marcos Talau   Wed, 02 Nov 2022 17:41:30 -0300
+
 cappuccino (0.5.1-10) unstable; urgency=medium
 
   * Bumped the compat version to 7. Closes: #965446
diff -u cappuccino-0.5.1/debian/rules cappuccino-0.5.1/debian/rules
--- cappuccino-0.5.1/debian/rules
+++ cappuccino-0.5.1/debian/rules
@@ -82,4 +82,8 @@
 binary-arch: build install
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install 
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install 

Bug#1023359: twisted: CVE-2022-39348: NameVirtualHost Host header injection

[Salvatore Bonaccorso]

Source: twisted
Version: 22.4.0-3
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 20.3.0-7+deb11u1
Control: found -1 20.3.0-7

Hi,

The following vulnerability was published for twisted.

CVE-2022-39348[0]:
| Twisted is an event-based framework for internet applications. Started
| with version 0.9.4, when the host header does not match a configured
| host `twisted.web.vhost.NameVirtualHost` will return a `NoResource`
| resource which renders the Host header unescaped into the 404 response
| allowing HTML and script injection. In practice this should be very
| difficult to exploit as being able to modify the Host header of a
| normal HTTP request implies that one is already in a privileged
| position. This issue was fixed in version 22.10.0rc1. There are no
| known workarounds.


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-39348
https://www.cve.org/CVERecord?id=CVE-2022-39348
[1] https://github.com/twisted/twisted/security/advisories/GHSA-vg46-2rrj-3647
[2] 
https://github.com/twisted/twisted/commit/f2f5e81c03f14e253e85fe457e646130780db40b
 

Regards,
Salvatore

Bug#1023358: runit: Stage 1: boot script in rcS should never be skipped

[Lorenzo Puliti]

Package: runit
Version: 2.1.2-50
Severity: important

Partially related to #1022837.
run_sysv_scripts is invoked in stage 1 to run boot scripts (initscripts);
however it skip the sysv script when a runit service with the same name
exists. This is wrong for early boot tasks and it can break the boot
sequence. For example one can have a /etc/sv/udev longrun that will replace
the sysv instance in stage 2, but still need to run /etc/init.d/udev during
eraly boot.




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

Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
LSM: AppArmor: enabled

Versions of packages runit depends on:
ii  libc6   2.36-3
ii  runit-helper2.15.0
ii  sysuser-helper  1.3.7+really1.4.1

Versions of packages runit recommends:
ii  runit-init  2.1.2-50

Versions of packages runit suggests:
ii  socklog  2.1.0+repack-4+b1
pn  zsh  

-- Configuration Files:
/etc/default/runit changed [not included]
/etc/runit/ctrlaltdel changed [not included]
/etc/runit/runsvdir/single/sulogin/run [Errno 2] No such file or directory: 
'/etc/runit/runsvdir/single/sulogin/run'

-- no debconf information

Bug#1023348: Null dereference in dentry_unlink_inode / kswapd

[Nathan Ramsey]

On Nov 2, 2022, at 11:25 AM, Diederik de Haas  wrote:
> 
> Control: severity -1 normal
> 
> On Wednesday, 2 November 2022 18:16:12 CET nmr wrote:
>> Package: src:linux
>> Version: 5.10.4-1
> 
> This is one of the very first 5.10.x versions! ...

Whoops, sorry!

> Stable-security currently has 5.10.149-2 and Debian release 11.5 was released
> less then 2 months ago.
> Your system seems configured correctly and up-to-date, but that doesn't match
> your kernel version. Even the initial release of Bullseye was with a much 
> newer
> kernel version from the 5.10 series.
> 
> Lowering the severity until you can reproduce this issue with an up-to-date
> kernel version.

I must have pinned it to the wrong kernel ages ago, I remember having some
issues with OpenCL drivers. I'll reopen or update if the bug recurs.

Thanks for the help.

Bug#1023357: python3-morse-simulator: depends on non-existing python3 (< 3.9)

[Ralf Treinen]

Package: python3-morse-simulator
Version: 1.4-6+b1
Severity: serious

Hi,

python3-morse-simulator depends on python3 (< 3.9) which is only
satisfiable in oldstable or older.

-Ralf.

Bug#1023356: libdune-pdelab-dev: unsatisfiable dependency on libdune-common-2.7.0

[Ralf Treinen]

Package: libdune-pdelab-dev
Version: 2.7~20200605-2
Severity: serious

Hi,

this package depends on libdune-common-2.7.0 which does not exist in sid.

-Ralf.

Bug#1023355: limereg: depends on non-existing libboost-program-options1.67.0

[Ralf Treinen]

Package: limereg
Version: 1.4.1-4+b1
Severity: serious

Hi,

limereg depends on libboost-program-options1.67.0 which only exists in
oldstable.

-Ralf.

Bug#1023154: RFP: hypnotix -- IPTV player

[Thomas Uhle]

On Sun, 30 Oct 2022, Fabio Fantoni wrote:


Il 30/10/2022 20:20, Thomas Uhle ha scritto:
> [...]
> 
> Hypnotix is an application to watch TV by streaming from M3U sources.
> It is primarily developed for the Cinnamon desktop in Linux Mint but could 
> be used in any other desktop environment as well.
> 
I don't use an IPTV, I tried shortly kodi but I am not used enough about this 
type of program.


It should be seen which others are packaged in debian besides kodi (I know 
only it) and if hypnotix has anything better than these to determine if it is 
worth adding hypnotix in debian.


can you tell something about?


You are right, Kodi is a good program for watching IPTV. But it is also 
so much more: DVB, DLNA client as well as a client for video-on-demand or 
podcast services to name just a few more features. It is a full-grown 
media center solution and as such installs on disk with 100MB at least 
(not counting the various dependencies). Hypnotix has only one feature 
compared to Kodi that is being a simple-to-use and lean application for 
watching IPTV. It uses libmpv.so to seamlessly embed mpv as a player and 
so only needs about 1MB of extra space on disk. That means it is quite 
small compared to Kodi.
Hypnotix can consume the same M3U lists like Kodi, so you could use one of 
the links provided by kodinerds.net for instance to get an up-to-date list 
of TV stations. IMHO the usual suspects of media players like VLC and 
alike are not suited for these types of M3U lists because these lists 
contain the URLs for many TV stations in one file whereas those media 
players expect that each M3U file corresponds to exactly one TV station 
(and different URLs just refer to streams with different resolutions, bit 
rates, subtitles, etc., but all for the same TV station). Moreover, those 
media players would not automatically update the M3U lists (which is what 
Hypnotix does). You would need to manually synchronize the URLs of the TV 
stations.
In addition I think, sometimes it is just good to have an alternative, 
especially if there is a simple, small and ready-to-go solution for 
something that just works. Anyway, nobody would be asking why there are 
several reincarnations of GNOME's file manager Nautilus in Debian (like 
Caja, Nemo or Peony).



I don't see strong links with cinnamon from a quick look (the dependency with 
xapp is minor) so it could be maintained by another team or maintainer as 
well (if anyone will want maintain it)


That is right. Hypnotix is as much connected to Cinnamon as any other 
appliction from the XApps family (cf. xed or xviewer for instance with the 
corresponding RFP requests #830598 and #830616 respectively). Just because 
it is linked to (lib)xapp, does not mean it is needed for Cinnamon.

Bug#1023315: tmux: manage /etc/shells using dpkg triggers

[Romain Francoise]

Hi,

On Wed, Nov 2, 2022 at 10:51 AM Helmut Grohne  wrote:
> tmux manages its entry in /etc/shells using add-shell/remove-shell.
> Consider managing this entry declaratively instead. Since version 5.3-1,
> debianutils recognizes /usr/share/debianutils/shells.d/tmux and will add
> those shells to /etc/shells via dpkg triggers. I'm attaching a patch for
> your convenience.

Thank you for the patch. Indeed, that's a change I'm planning to make
in order to fix #939889, but it will have to wait for the new trigger
mechanism to be available in Debian stable because I maintain a
backport of tmux. So that's for after bookworm, but that's only a few
months away now.

Bug#1023291: gitlab-sidekiq spamming logs after upgrade to gitlab 15.4.2

[Jakob Haufe]

On Wed, 2 Nov 2022 06:52:41 +0100
Maximilian Stein  wrote:

> I can confirm this, the same is happening on my system, too.

I worked around this by setting

ForwardToSyslog=no

in /etc/systemd/journald.conf as I don't see any benefit in duplicated
logging.

-- 
ceterum censeo microsoftem esse delendam.


pgpS0U7CMVRjW.pgp
Description: OpenPGP digital signature

Bug#1023351: SOLVED: boot-info-script script fails if the root partition is a logical volume.

[Christian Andretzky]

The solution is very simple; in line 3576, the expression must be

LVM_Size=${LVM2_LV_SIZE%S};

instead of

LVM_Size=${LVM2_LV_SIZE%s};

Cheers, Christian
--
Name:  Christian Andretzky
mail:  christian.andret...@in-chemnitz.de
PGP:   public key available via public key server
Freedom is just another word for nothing left to lose (Janis Joplin)
Wer schweigt, stimmt nicht immer zu. Er hat nur manchmal keine Lust,
mit Idioten zu diskutieren. (Albert Einstein)

Bug#1021668: [Pkg-xen-devel] Bug#1021668: xen: CVE-2022-33749 CVE-2022-33748 CVE-2022-33747 CVE-2022-33746

[Hans van Kranenburg]

Hi,

On 10/19/22 21:55, Moritz Muehlenhoff wrote:
>>> For the latest set of Xen issues my estimate is that we can postpone
>>> them until the next batch, they seem all of moderate/limited impact.
>>> But let me know if you think otherwise.
>>
>> I agree. Let's do them together with the new stuff that's planned for
>> Nov 1st, https://xenbits.xen.org/xsa/
> 
> Ack, I've updated the Security Tracker.

I'm having a look at this now, and while writing the changelog entry, I
run into the following thing:

XSA-403 has 4 CVE numbers. AFAIUI the first two are about the fixes done
to Linux, and the other two are about changes to Xen. Shouldn't the
Debian security tracker reflect that?

CVE-2022-26365 CVE-2022-33740 -> src:linux only ?
CVE-2022-33741 CVE-2022-33742 -> src:xen only ?

And for XSA-403, at first upstream was unsure about what to do for older
Xen versions where the patches would be an ABI breaker. In the end, they
did apply the more coarse-grained patch to at least offer some kind of
mitigation in case a user wants to use it.

So, the changelog line I'm including now will just be:
  - Linux disk/nic frontends data leaks
XSA-403 CVE-2022-33741 CVE-2022-33742

HTH,
Hans

Bug#1023354: [icingaweb2] No php8.2 support

[David Prévot]

Package: icinga2
Version: 2.11.1-1
Severity: important
Control: block 1014460 by -1

Hi Bas,

As you noted recently [1], “icingaweb2 explicitly doesn't support php8.2
upstream yet, their php8.1”, so documenting it as a blocker to the
transition.

1: https://bugs.debian.org/1014460#33

Regards

David


signature.asc
Description: PGP signature

Bug#1023353: [php-faker] Failing tests with PHP 8.2

[David Prévot]

Package: php-faker
Version: 1.20.0+dfsg-1
Severity: important
Control: block 1014460 by -1

Hi Robin,

There are some tests failure under PHP 8.2 (rc5).

https://qa.debian.org/excuses.php?experimental=1=php-defaults

Even if there have been no updated version upstream since July, it
looks like the repository is still active, so hopefully “just”
cherry-picking the needed fixes will be enough.

Here are the current failures:

> There were 2 failures:
> 
> 1) Faker\Test\Core\DateTimeTest::testCentury
> Failed asserting that two strings are equal.
> --- Expected
> +++ Actual
> @@ @@
> -'XIX'
> +'XIII'
> 
> /tmp/autopkgtest-lxc.msk17iv_/downtmp/build.9oU/src/test/Faker/Core/DateTimeTest.php:222
> 
> 2) 
> Faker\Test\GeneratorTest::testUniqueReturnsUniqueGeneratorThatGeneratesUniqueValues
> Failed asserting that two arrays are equal.
> --- Expected
> +++ Actual
> @@ @@
>  Array (
> -0 => 'foo'
> -1 => 'bar'
> +0 => 'bar'
> +1 => 'foo'
>  2 => 'baz'
>  )
> 
> /tmp/autopkgtest-lxc.msk17iv_/downtmp/build.9oU/src/test/Faker/GeneratorTest.php:283
> 
> --

Regards

David


signature.asc
Description: PGP signature

Bug#1023352: transition: draco

[Timo Röhling]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Release Team,

I'd like to transition draco after the new release had a SONAME bump.
All reverse-dependencies build successfully on amd64.

The auto-generated Ben tracker is good:
https://release.debian.org/transitions/html/auto-draco.html

Cheers
Timo


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmNiu6IACgkQ+C8H+466
LVmGZQwAy2aK0AW9028jDsgsshbQbnDwJKLRp/D8cy+MFBXwEeOJg55gzUieJN5i
VUzFfZ2kdzu/4y2MSsxuizPbGYyKmQLQYWo0Pf81X+Co1PA1o7dI9D0sfD9xIXq/
ZtzHRmpxZPVLr+O+nI7blkssZVgd069SMViTZncv51miGtD6cJd7J4DHAqZZuy3k
lEt8UabTogWYxHkx9qOihJrDpqb2cA74a021J9jZAFwy0eetZWRTV7AxhtZfjTMw
C5ZQxNcKibwnX3xnjtUptay9h+LG0g0tQwRy4xBOog67OmSColI/0YAq45OTS6eA
Kq0bqR49v6LIaeg7GoDnXEuY/dPljrnFcJOhhceopmPY+S2Ob/2QvhL4jfmUk6mT
c58rDhq2zNeb6CLMyFhJuiTJowy/m7PQ/wHQb8a1pge00kjM2N0TxnOXamdbii+F
DPcLxIag6fxFA+6474dJOvH3lpYapGydMvMCsOKLk2xKPkdD1D2phJdG7okUDQwe
Pehe/JdK
=SuIz
-END PGP SIGNATURE-

Bug#1007984: netpbm-free ready to upload

[Andreas Tille]

Hi Andreas,

Am Thu, Oct 06, 2022 at 07:09:13PM +0200 schrieb Andreas Metzler:
> > I noticed you added some missing information to d/copyright
> > of netpbm-free.  Thanks a lot for doing so.  Do you think it
> > is time for another upload?
> 
> I invested a couple of hours but sadly it is not a finished effort.

Thanks a lot again for spending your time.  I would appreciate if we
could make it some team effort to finally get this package in good
shape.  I'm personally quite occupied by fixing a couple of RC bugs in
Debian Med team so netpbm-free (which I do not use personally) has low
priority for me.  So any help is welcome.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#1023236: Previous art

[Marco Mattiolo]

Hi Thomas,

I aligned within the "Mobian Development" Matrix room before starting 
the packaging, then I was aware of that repository in Salsa.


Having received some hints from Mobian devs, I think packaging is in 
pretty good shape already: plasma-mobile can be started as a system 
service, as Phosh does. I am testing the resulting packages on my PP: 
for the moment, the Plasma system is on an SD card, but I feel like it 
could become my daily system soon.


Feel free to take a look at my MR [1]. I am still waiting for some 
experienced dev to review it (a-wai should do it in some days), then 
comments are welcome!


Kind regards

Marco Mattiolo

[1] 
https://salsa.debian.org/DebianOnMobile-team/plasma-mobile/-/merge_requests/1



Il 02/11/22 12:00, Thomas Goirand ha scritto:

Just to make sure you noticed. I attempted such a packaging already at:
https://salsa.debian.org/DebianOnMobile-team/plasma-mobile

The package, last summer (during debconf) could:
- build
- be installed

1/ Remaining to do: review all non-useful build-depends from 
debian/control (I lazily took all the build-depends from the plasma 
non-mobile version because otherwise couldn't build...).


2/ Make sure you can actually run the package (by installing something 
like gdm and choosing plasma?)


Good luck with all of this, I'm looking forward seeing plasma-mobile 
on my pinephone running Debian.


Cheers,

Thomas Goirand (zigo)

Bug#1023348: Null dereference in dentry_unlink_inode / kswapd

[Diederik de Haas]

Control: severity -1 normal

On Wednesday, 2 November 2022 18:16:12 CET nmr wrote:
> Package: src:linux
> Version: 5.10.4-1

This is one of the very first 5.10.x versions! ...

> -- System Information:
> Debian Release: 11.5
>   APT prefers stable-security
>   APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable')

Stable-security currently has 5.10.149-2 and Debian release 11.5 was released
less then 2 months ago.
Your system seems configured correctly and up-to-date, but that doesn't match
your kernel version. Even the initial release of Bullseye was with a much newer
kernel version from the 5.10 series.

Lowering the severity until you can reproduce this issue with an up-to-date
kernel version.

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

Bug#1021952: libloc: FTBFS on hppa and alpha - test-network fails

[Michael Tremer]

Hello Dave,

Thank you for your bug report. I am Michael and I maintain libloc.

Your analysis is spot on. Unfortunately the function that seems to fail is kind 
of one of the most complex ones in the whole library. Debugging it without 
—-enable-debug is kind of impossible, so I don’t quite know where to start.

On x86_64 (which is my development platform) the build runs through no matter 
whether I enable the debugging code or not.

I manually searched the entire code base for some variable increment in a 
DEBUG() statement that is then compiled out. Nada.

Can you think of anything that makes hppa and alpha special? Especially 
together?

We have other 32 bit architectures which work fine, so it isn’t that. The 
compiler warnings in the log are mostly formatting issues which I need to 
resolve, but they don’t have any effect.

So, any pointers where I could look next?

Best,
-Michael

Bug#1023224: [Pkg-swan-devel] Bug#1023224: strongswan: autopkgtest regression: depends on no longer built strongswan-scepclient

[Paul Gevers]

Hi Yves-Alexis,

On 02-11-2022 17:27, Yves-Alexis Perez wrote:

I'm not sure why the test is failing then and what I should have done
differently. Could you give me some pointers here?


https://sources.debian.org/src/strongswan/5.9.8-1/debian/tests/control/

line 2 says that the *first* two tests Depends on strongswan-scepclient. 
That means that autopkgtests tries to install that binary package, which 
fails because it's no longer available. Either remove the tests (if they 
need that binary), or adapt the Depends line to what is required for the 
test.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023351: boot-info-script script fails if the root partition is a logical volume.

[Christian Andretzky]

Package: boot-info-script
Version: 0.78-3
Severity: important

Dear Maintainer,

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

if the root partition is located on a lvm volume boot info script fails to 
execute the function Get_Partition_Info because the calling parameters are 
wrong.
for a normal partition the call is

Get_Partition_Info /tmp/BootInfo-RKu7D0dK/Log /tmp/BootInfo-RKu7D0dK/Log1 
/dev/sda4 sda4 sda4 P 35670016 468860927 Logical Volume Manager (LVM) partition 
(Linux) 4

for a lvm volume the call is

Get_Partition_Info /tmp/BootInfo-RKu7D0dK/Log /tmp/BootInfo-RKu7D0dK/Log1 
/dev/mapper/system--kralle-rootfs system-kralle-rootfs LVM/system-kralle-rootfs 
LVM 0 83886080S

Get_Partition_Info fails because the value for 'end' in not a number '83886080S'


-- System Information:
Debian Release: 11.5
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 
'stable-security'), (100, 'bullseye-fasttrack'), (100, 
'bullseye-backports-staging')
Architecture: amd64 (x86_64)

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

Versions of packages boot-info-script depends on:
ii  bsdextrautils  2.36.1-8+deb11u1
ii  e2fsprogs  1.46.2-2
ii  fdisk  2.36.1-8+deb11u1
ii  gawk   1:5.1.0-1

boot-info-script recommends no packages.

boot-info-script suggests no packages.

-- no debconf information

Cheers, Christian

Bug#924664: ejabberd: node migration broken

[Philipp Huebner]

Hello Anton,

any news on this?

On Wed, 15 Sep 2021 16:21:27 +0100 Anton Ivanov 
 wrote:

OK.

I will retest when I upgrade to current stable which should happen in the next 
few days.

A.


OpenPGP_0xE5CA8C4925E4205F.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023350: cmark-gfm: please ship the spec

[Jakub Wilk]

Package: cmark-gfm
Version: 0.29.0.gfm.6-2
Severity: wishlist

The source package includes the format specification in tests/spec.txt. 
Please ship it in the binary package (ideally both in source and HTML 
formats).


--
Jakub Wilk

Bug#1023348: amended syslog snippet

[Nathan Ramsey]

I missed the first three lines of the syslog snippet
containing the BUG event, inlined here:

Oct 31 16:27:48 gonzo kernel: BUG: kernel NULL pointer dereference, address: 
0028
Oct 31 16:27:48 gonzo kernel: #PF: supervisor write access in kernel mode
Oct 31 16:27:48 gonzo kernel: #PF: error_code(0x0002) - not-present page
Oct 31 16:27:49 gonzo kernel: PGD 800121c24067 P4D 800121c24067 PUD 
1079bf067 PMD 0 
Oct 31 16:27:49 gonzo kernel: Oops: 0002 [#1] SMP PTI
Oct 31 16:27:49 gonzo kernel: CPU: 9 PID: 296 Comm: kswapd0 Tainted: G  
I   5.10.0-1-amd64 #1 Debian 5.10.4-1
Oct 31 16:27:49 gonzo kernel: Hardware name: System manufacturer System Product 
Name/ROG STRIX X299-E GAMING, BIOS 1503 08/03/2018
Oct 31 16:27:49 gonzo kernel: RIP: 0010:dentry_unlink_inode+0x51/0x100
Oct 31 16:27:49 gonzo kernel: Code: a9 00 00 08 00 74 08 65 48 ff 05 8a 45 75 
52 48 8b 85 b8 00 00 00 48 85 c0 74 29 48 8b 95 b0 00 00 00 48 89 10 48 85 d2 
74 04 <4>
Oct 31 16:27:49 gonzo kernel: RSP: 0018:b59d00a13b58 EFLAGS: 00010202
Oct 31 16:27:49 gonzo kernel: RAX: 9e2fbb8db9f8 RBX: 9e335a601740 RCX: 

Oct 31 16:27:49 gonzo kernel: RDX: 0020 RSI: 9e3466229350 RDI: 
9e34662292c0
Oct 31 16:27:49 gonzo kernel: RBP: 9e34662292c0 R08: 9e34662282d0 R09: 
9e2706d3e260
Oct 31 16:27:49 gonzo kernel: R10:  R11:  R12: 
9e2fbb8db8c0
Oct 31 16:27:49 gonzo kernel: R13: 9e3466229318 R14: 9e2760c01870 R15: 

Oct 31 16:27:49 gonzo kernel: FS:  () 
GS:9e365fa4() knlGS:
Oct 31 16:27:49 gonzo kernel: CS:  0010 DS:  ES:  CR0: 80050033
Oct 31 16:27:49 gonzo kernel: CR2: 0028 CR3: 000107aac004 CR4: 
003706e0
Oct 31 16:27:49 gonzo kernel: DR0:  DR1:  DR2: 

Oct 31 16:27:49 gonzo kernel: DR3:  DR6: fffe0ff0 DR7: 
0400
Oct 31 16:27:49 gonzo kernel: Call Trace:
Oct 31 16:27:49 gonzo kernel:  __dentry_kill+0xe4/0x180
Oct 31 16:27:49 gonzo kernel:  shrink_dentry_list+0x4e/0xc0
Oct 31 16:27:49 gonzo kernel:  prune_dcache_sb+0x54/0x80
Oct 31 16:27:49 gonzo kernel:  super_cache_scan+0x12c/0x1e0
Oct 31 16:27:49 gonzo kernel:  do_shrink_slab+0x145/0x240
Oct 31 16:27:49 gonzo kernel:  shrink_slab+0x188/0x2a0
Oct 31 16:27:49 gonzo kernel:  shrink_node+0x2c0/0x6e0
Oct 31 16:27:49 gonzo kernel:  balance_pgdat+0x2e5/0x600
Oct 31 16:27:49 gonzo kernel:  kswapd+0x1f6/0x380
Oct 31 16:27:49 gonzo kernel:  ? add_wait_queue_exclusive+0x70/0x70
Oct 31 16:27:49 gonzo kernel:  ? balance_pgdat+0x600/0x600
Oct 31 16:27:49 gonzo kernel:  kthread+0x11b/0x140
Oct 31 16:27:49 gonzo kernel:  ? __kthread_bind_mask+0x60/0x60
Oct 31 16:27:49 gonzo kernel:  ret_from_fork+0x22/0x30
Oct 31 16:27:49 gonzo kernel: Modules linked in: xt_MASQUERADE xt_mark 
nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
nft_counter nf_tab>
Oct 31 16:27:49 gonzo kernel:  mei_me sg watchdog mei ioatdma dca evdev drm 
fuse configfs efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 
raid10 raid456>
Oct 31 16:27:49 gonzo kernel: CR2: 0028
Oct 31 16:27:49 gonzo kernel: ---[ end trace 3c3f518d326d4df8 ]---
Oct 31 16:27:49 gonzo kernel: RIP: 0010:dentry_unlink_inode+0x51/0x100
Oct 31 16:27:49 gonzo kernel: Code: a9 00 00 08 00 74 08 65 48 ff 05 8a 45 75 
52 48 8b 85 b8 00 00 00 48 85 c0 74 29 48 8b 95 b0 00 00 00 48 89 10 48 85 d2 
74 04 <4>
Oct 31 16:27:49 gonzo kernel: RSP: 0018:b59d00a13b58 EFLAGS: 00010202
Oct 31 16:27:49 gonzo kernel: RAX: 9e2fbb8db9f8 RBX: 9e335a601740 RCX: 

Oct 31 16:27:49 gonzo kernel: RDX: 0020 RSI: 9e3466229350 RDI: 
9e34662292c0
Oct 31 16:27:49 gonzo kernel: RBP: 9e34662292c0 R08: 9e34662282d0 R09: 
9e2706d3e260
Oct 31 16:27:49 gonzo kernel: R10:  R11:  R12: 
9e2fbb8db8c0
Oct 31 16:27:49 gonzo kernel: R13: 9e3466229318 R14: 9e2760c01870 R15: 

Oct 31 16:27:49 gonzo kernel: FS:  () 
GS:9e365fa4() knlGS:
Oct 31 16:27:49 gonzo kernel: CS:  0010 DS:  ES:  CR0: 80050033
Oct 31 16:27:49 gonzo kernel: CR2: 0028 CR3: 000107aac004 CR4: 
003706e0
Oct 31 16:27:49 gonzo kernel: DR0:  DR1:  DR2: 

Oct 31 16:27:49 gonzo kernel: DR3:  DR6: fffe0ff0 DR7: 
0400

Bug#995961: libapache2-mpm-itk: Error "AH00052: child pid exit signal Segmentation fault" after update to apache 2.4.51-1~deb11u1

[Remon Moyede]

On Mon, 11 Oct 2021 17:28:51 +0200 Jean Weisbuch  wrote:
> I also have the issue on a custom compiled HTTPD and ITK, it's not a
> Debian specific bug ; it appeared between 2.4.48 and 2.4.49.
>
>
> Here is a basic patch for 2.4.51 that comments the line that provokes
> the segfaults but it might break other things :
>
> --- server/connection.c2021-09-26 16:11:22.0 +0200
> +++ server/connection.c2021-10-11 17:00:17.868463811 +0200
> @@ -156,7 +156,7 @@
>   apr_socket_t *csd = ap_get_conn_socket(c);
>
>   if (ap_start_lingering_close(c)) {
> -apr_socket_close(csd);
> +//apr_socket_close(csd);
>   return;
>   }
>
> A "cleaner" patch, also for 2.4.51, that reverts the changes between
> 2.4.48 and 2.4.49 on connection.c but keep the other changes ; i don't
> know what those changes could imply so i advise against using it on a
> production platform :
>
> --- ./server/connection.c2021-09-26 16:11:22.0 +0200
> +++ ./server/connection.c2021-10-11 17:15:04.232960328 +0200
> @@ -139,12 +139,18 @@
>   ap_flush_conn(c);
>
>   #ifdef NO_LINGCLOSE
> +apr_socket_close(csd);
>   return 1;
>   #else
>   /* Shut down the socket for write, which will send a FIN
>* to the peer.
>*/
> -return (c->aborted || apr_socket_shutdown(csd, APR_SHUTDOWN_WRITE));
> +if (c->aborted
> +|| apr_socket_shutdown(csd, APR_SHUTDOWN_WRITE) !=
> APR_SUCCESS) {
> +apr_socket_close(csd);
> +return 1;
> +}
> +return 0;
>   #endif
>   }
>
> @@ -156,7 +162,6 @@
>   apr_socket_t *csd = ap_get_conn_socket(c);
>
>   if (ap_start_lingering_close(c)) {
> -apr_socket_close(csd);
>   return;
>   }
>
>
>

Bug#1023151: Recommends unneeded gist instead of netcat

[Thomas Uhle]

On Tue, 1 Nov 2022, Fabio Fantoni wrote:


Control: tag -1 pending

Hello,

Bug #1023151 in xapp reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/cinnamon-team/xapp/-/commit/492569483b0b5042cdd32fcfd2c5e50431a2aafb


remove gist from xapps-common recommends and add netcat-openbsd

Closes: #1023151
Thanks: Thomas Uhle


(this message was generated automatically)
--
Greetings

https://bugs.debian.org/1023151




Ciao Fabio,

thanks for the immediate response!

I've had a quick look at your commits and so have one minor remark. 
/usr/bin/nc is handled by update-alternatives and both packages 
netcat-openbsd and netcat-traditional have "Provides: netcat", so you 
also could simply use netcat as dependency instead, similar to other 
packages in Debian like foomatic-db-engine, virt-viewer or playonlinux 
for instance.


Best regards,

Thomas Uhle

Bug#1023348: Null dereference in dentry_unlink_inode / kswapd

[nmr]

Package: src:linux
Version: 5.10.4-1
Severity: critical
Tags: upstream
X-Debbugs-Cc: nat...@acmeaom.com

Apologies if this isn't the right venue for this, doing
my best here.

Attachment descriptions

b1 - syslog from BUG event 
b2 - syslog from 12+ hours later preceding total system hang
b3 - hdparm -I /dev/sda
b4 - smartctl -a /dev/sda

As seen in /dev/sda appears to be running old firmware, and
it is hosting the swap volume.


-- Package-specific info:
** Version:
Linux version 5.10.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.2.1-3) 10.2.1 20201224, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP 
Debian 5.10.4-1 (2020-12-31)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.10.0-1-amd64 
root=UUID=25ffc6b2-d247-4531-8a8e-b6e8da5c6b36 ro quiet

** Tainted: I (2048)
 * workaround for bug in platform firmware applied

** Kernel log:
[5.389178] platform regulatory.0: firmware: failed to load regulatory.db 
(-2)
[5.389202] firmware_class: See https://wiki.debian.org/Firmware for 
information about missing firmware
[5.389226] platform regulatory.0: Direct firmware load for regulatory.db 
failed with error -2
[5.389228] cfg80211: failed to load regulatory.db
[5.411695] Adding 66771964k swap on /dev/sda5.  Priority:-2 extents:1 
across:66771964k SSFS
[5.457679] audit: type=1400 audit(1667325565.555:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-senddoc" 
pid=764 comm="apparmor_parser"
[5.457792] audit: type=1400 audit(1667325565.555:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="postgresql_akonadi" pid=762 
comm="apparmor_parser"
[5.457859] audit: type=1400 audit(1667325565.555:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" 
pid=763 comm="apparmor_parser"
[5.457885] audit: type=1400 audit(1667325565.555:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/sbin/haveged" pid=767 
comm="apparmor_parser"
[5.457940] audit: type=1400 audit(1667325565.555:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="lsb_release" pid=771 
comm="apparmor_parser"
[5.458475] audit: type=1400 audit(1667325565.555:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/libexec/ibus-engine-hangul" pid=758 comm="apparmor_parser"
[5.458545] audit: type=1400 audit(1667325565.555:8): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-oopslash" 
pid=765 comm="apparmor_parser"
[5.458708] audit: type=1400 audit(1667325565.555:9): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=769 
comm="apparmor_parser"
[5.458711] audit: type=1400 audit(1667325565.555:10): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_filter" pid=769 
comm="apparmor_parser"
[5.458713] audit: type=1400 audit(1667325565.555:11): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_groff" pid=769 
comm="apparmor_parser"
[5.577234] snd_hda_intel :65:00.1: Disabling MSI
[5.577274] snd_hda_intel :65:00.1: Handle vga_switcheroo audio client
[5.578996] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[5.631557] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:64/:64:00.0/:65:00.1/sound/card1/input9
[5.631597] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:64/:64:00.0/:65:00.1/sound/card1/input10
[5.631632] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:64/:64:00.0/:65:00.1/sound/card1/input11
[5.631663] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:64/:64:00.0/:65:00.1/sound/card1/input12
[5.631726] input: HDA NVidia HDMI/DP,pcm=10 as 
/devices/pci:64/:64:00.0/:65:00.1/sound/card1/input13
[5.631779] input: HDA NVidia HDMI/DP,pcm=11 as 
/devices/pci:64/:64:00.0/:65:00.1/sound/card1/input14
[5.631821] input: HDA NVidia HDMI/DP,pcm=12 as 
/devices/pci:64/:64:00.0/:65:00.1/sound/card1/input15
[5.641972] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC1220: 
line_outs=3 (0x14/0x15/0x16/0x0/0x0) type:line
[5.641974] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[5.641975] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x1b/0x0/0x0/0x0/0x0)
[5.641976] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[5.641977] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
[5.641977] snd_hda_codec_realtek hdaudioC0D0:inputs:
[5.641978] snd_hda_codec_realtek hdaudioC0D0:  Front Mic=0x19
[5.641979] snd_hda_codec_realtek hdaudioC0D0:  Rear Mic=0x18
[5.641980] snd_hda_codec_realtek hdaudioC0D0:  Line=0x1a
[5.649634] rtw_8822be :02:00.0: enabling device ( -> 0003)
[5.654652] rtw_8822be :02:00.0: firmware: direct-loading firmware 
rtw88/rtw8822b_fw.bin
[

Bug#998933: cgilib: diff for NMU version 0.6-1.2

[Marcos Talau]

Hi Andreas!

On Wed, Nov 02, 2022 at 02:50:12PM +0100, Andreas Beckmann wrote:
[...]
> cgilib is orphaned, so you should rather do a QA upload ;-)
> 

Heheh, sorry for that, and thanks for the info :D

The Maintainer field has not been changed, and I prepared a series of NMUs
against the same issue.

I will cancel the NMU and do a QA to fix the issue, and I'm going to take the
opportunity to update the Maintainer field to Debian QA Group.


Best Regards,
mt


signature.asc
Description: PGP signature

Bug#1022945: smbclient: ambiguous duplications in the smbclient(1) manpage

[Michael Tokarev]

28.10.2022 10:28, Patrice DUROUX wrote:

Package: smbclient
Version: 2:4.16.6+dfsg-5
Severity: wishlist

Dear Maintainer,

The smbclient(1) manpage contains some multiple entries in the OPTIONS
section regarding the SYNOPSIS list.

Here are the two detected cases:

71:   -m|--max-protocol protocol
72-   This allows the user to select the highest SMB protocol level 
that smbclient will use to connect to the server. By default this is set to 
highest available SMB3
and
259:   -m|--max-protocol=MAXPROTOCOL
260-   The value of the parameter (a string) is the highest protocol 
level that will be supported by the client.


samba manpages are generated. And this is interesting.

The first text above comes from docs-xml/manpages/smbclient.1.xml:

-m|--max-protocol protocol
This allows the user to select the
highest SMB protocol level that smbclient will use to
connect to the server. By default this is set to..

And the second text comes from 
docs-xml/smbdotconf/protocol/clientmaxprotocol.xml:

  http://www.samba.org/samba/DTD/samba-doc;>
  
The value of the parameter (a string) is the highest
protocol level that will be supported by the client.
...

So it looks like smbclient.1.xml manpage lists *all* options available,
and also includes other files which lists some options which are referenced
by smbclient.1.xml. And it looks like the same applies to other manpages too.

I'm Cc'ing samba-technical@ with this.

Thanks,

/mjt



76:   -P|--machine-pass
77-   Make queries to the external server using the machine account of 
the local server.
and
335:   -P|--machine-pass
336-   Use stored machine account password.

Moreover the entries in the OPTIONS section should be more consistent to the 
SYNOPSIS
syntax. For instance, SYNOPSIS is:

smbclient [-M|--message=HOST] [-I|--ip-address=IP] [-E|--stderr] 
[-L|--list=HOST] [-T|--tar=IXFvgbNan] [-D|--directory=DIR] 
[-b|--send-buffer=BYTES]
 [-t|--timeout=SECONDS] [-p|--port=PORT] [-g|--grepable] [-q|--quiet] 
[-B|--browse] [-?|--help] [--usage] [-d|--debuglevel=DEBUGLEVEL] 
[--debug-stdout]
 [-s|--configfile=CONFIGFILE] [--option=name=value] 
[-l|--log-basename=LOGFILEBASE] [--leak-report] [--leak-report-full] 
[-R|--name-resolve=NAME-RESOLVE-ORDER]
 [-O|--socket-options=SOCKETOPTIONS] [-m|--max-protocol=MAXPROTOCOL] 
[-n|--netbiosname=NETBIOSNAME] [--netbios-scope=SCOPE] 
[-W|--workgroup=WORKGROUP]
 [--realm=REALM] [-U|--user=[DOMAIN/]USERNAME%[PASSWORD]] 
[-N|--no-pass] [--password=STRING] [--pw-nt-hash] 
[-A|--authentication-file=FILE] [-P|--machine-pass]
 [--simple-bind-dn=DN] [--use-kerberos=desired|required|off] 
[--use-krb5-ccache=CCACHE] [--use-winbind-ccache] 
[--client-protection=sign|encrypt|off] [-V|--version]
 [-c|--command=STRING]

and the entries in OPTIONS are (with the duplicates):
-M|--message NetBIOS name  <- =HOST
-p|--port port <- =PORT
-g|--grepable
-m|--max-protocol protocol <- duplicated
-P|--machine-pass  <- duplicated
-I|--ip-address IP-address <- =IP
-E|--stderr
-L|--list  <- =HOST
-b|--send-buffer buffersize<- =BYTES
-B|--browse
-t|--timeout  <- =SECONDS
-T|--tar tar options   <- =IXFvgbNan
-D|--directory initial directory <- =DIR
-c|--command command string<- =STRING
-?|--help
-d|--debuglevel=DEBUGLEVEL
-l|--log-basename=logdirectory <- =LOGFILEBASE
-V|--version
-R|--name-resolve=NAME-RESOLVE-ORDER
-O|--socket-options=SOCKETOPTIONS
-m|--max-protocol=MAXPROTOCOL
-n|--netbiosname=NETBIOSNAME
-W|--workgroup=WORKGROUP
-r|--realm=REALM
-U|--user=[DOMAIN\]USERNAME[%PASSWORD] <- / or \ ?
-N|--no-pass
-A|--authentication-file=filename
-P|--machine-pass

And as we can see, the SYNOPSIS set is much larger than that of OPTIONS.

Regards,
Patrice

ps: I just used the following command to check: man smbclient | grep -n -A 1 
'\-.|'
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-samba-maint

Bug#1023347: tomopy: CUDA + MKL => FTBFS

[Andreas Beckmann]

Source: tomopy
Version: 1.10.4+ds1-4
Severity: important
Tags: ftbfs

Hi,

MKL detection currently does not work. I have a fix for that (pushed to
branch mkl-detection), but it causes an FTBFS on amd64 when nvcc
attempts to link against both libdl.a and -ldl. Unfortunately that does
not seem to be reproducible on salsa ci, cuda detection does not seem
to work there.
I'll try to debug the cuda detection issue on salsa, but no promises.

...
[41/44] Building CUDA object 
source/libtomo/accel/CMakeFiles/libtomopy-accel.dir/gpu/sirt.cu.o
nvcc warning : The 'compute_35', 'compute_37', 'sm_35', and 'sm_37' 
architectures are deprecated, and may be removed in a future release (Use 
-Wno-deprecated-gpu-targets to suppress warning).
[42/44] Linking CXX shared library 
CMakeFiles/libtomopy-accel.dir/cmake_device_link.o
FAILED: CMakeFiles/libtomopy-accel.dir/cmake_device_link.o
/usr/bin/nvcc -forward-unknown-to-host-compiler -ccbin=cuda-g++ -O3 -DNDEBUG  
-Xcompiler=-fPIC -Wno-deprecated-gpu-targets -shared -dlink 
source/libtomo/accel/CMakeFiles/libtomopy-accel.dir/cxx/common.cc.o 
source/libtomo/accel/CMakeFiles/libtomopy-accel.dir/cxx/mlem.cc.o 
source/libtomo/accel/CMakeFiles/libtomopy-accel.dir/cxx/sirt.cc.o 
source/libtomo/accel/CMakeFiles/libtomopy-accel.dir/gpu/common.cu.o 
source/libtomo/accel/CMakeFiles/libtomopy-accel.dir/gpu/mlem.cu.o 
source/libtomo/accel/CMakeFiles/libtomopy-accel.dir/gpu/sirt.cu.o 
source/libtomo/accel/CMakeFiles/libtomopy-accel.dir/gpu/utils.cu.o -o 
CMakeFiles/libtomopy-accel.dir/cmake_device_link.o 
-L/usr/lib/x86_64-linux-gnu/stubs  -L/usr/lib/gcc/x86_64-linux-gnu/11 -lm 
/usr/lib/x86_64-linux-gnu/libdl.a libptl.a 
/usr/lib/x86_64-linux-gnu/libnpps_static.a 
/usr/lib/x86_64-linux-gnu/libnppig_static.a 
/usr/lib/x86_64-linux-gnu/libnppisu_static.a 
/usr/lib/x86_64-linux-gnu/libnppc_static.a 
/usr/lib/x86_64-linux-gnu/libculibos.a -lcudadevrt -lcudart_static -lrt 
-lpthread -ldl
nvlink warning : Skipping incompatible '/usr/lib/x86_64-linux-gnu/librt.a' when 
searching for -lrt
nvlink warning : Skipping incompatible '/usr/lib/x86_64-linux-gnu/libpthread.a' 
when searching for -lpthread
nvlink warning : Skipping incompatible '/usr/lib/x86_64-linux-gnu/libdl.a' when 
searching for -ldl
nvlink fatal   : Could not open input file '/usr/lib/x86_64-linux-gnu/libdl.a'
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/skbuild/setuptools_wrap.py", line 645, 
in setup
cmkr.make(make_args, install_target=cmake_install_target, env=env)
  File "/usr/lib/python3/dist-packages/skbuild/cmaker.py", line 680, in make
self.make_impl(clargs=clargs, config=config, source_dir=source_dir, 
install_target=install_target, env=env)
  File "/usr/lib/python3/dist-packages/skbuild/cmaker.py", line 704, in 
make_impl
raise SKBuildError(

An error occurred while building with CMake.
  Command:
cmake --build . --target install --config Release --
  Install target:
install
  Source directory:
/build/tomopy-1.10.4+ds1
  Working directory:
/build/tomopy-1.10.4+ds1/_skbuild/linux-x86_64-3.10/cmake-build
Please check the install target is valid and see CMake's output for more 
information.
E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py build
dh_auto_build: error: pybuild --build -i python{version} -p 3.10 returned exit 
code 13
make: *** [debian/rules:6: build-arch] Error 13
...

The package uses some kind of non-verbose build that is a) not disabled
by the default measures to get a verbose build and b) not detected by
blhc. That makes debugging more difficult than neccessary.
https://salsa.debian.org/python-team/packages/tomopy/-/jobs/3463730#L3849

There are so many nested build systems involved ... I have no idea where
the bad linking command originates from.


Andreas

Bug#949654: no calculator in xfce4 is preinstalled

[Akbarkhon Variskhanov]

Hello.

As Karthik mentioned, there is xfce4-calculator-plugin, which I've
started to work on. The package has a couple of flaws. You can follow
the ITP progress here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850459

Bug#1023346: debianutils: NMU 5.7-0.4

[Bastian Germann]

Source: debianutils
Version: 5.7-0.3

I have just NMUed the debianutils package (DELAYED/3) with the
debian/copyright file converted to the machine-readable format.diff -Nru debianutils-5.7/debian/changelog debianutils-5.7/debian/changelog
--- debianutils-5.7/debian/changelog2022-07-27 08:20:06.0 +0200
+++ debianutils-5.7/debian/changelog2022-11-02 17:31:14.0 +0100
@@ -1,3 +1,10 @@
+debianutils (5.7-0.4) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * d/copyright: Convert to machine-readable format
+
+ -- Bastian Germann   Wed, 02 Nov 2022 17:31:14 +0100
+
 debianutils (5.7-0.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru debianutils-5.7/debian/copyright debianutils-5.7/debian/copyright
--- debianutils-5.7/debian/copyright2022-05-01 18:43:27.0 +0200
+++ debianutils-5.7/debian/copyright2022-11-02 17:31:05.0 +0100
@@ -1,161 +1,193 @@
-This is the Debian GNU/Linux package debianutils.
-
-It is an original Debian package.  Programs in it were maintained by
-Guy Maor , and are now maintained by Clint Adams
-.
-
-All its programs except savelog, and which may be
-redistributed under the terms of the GNU GPL, Version 2 or later,
-found on Debian systems in the file /usr/share/common-licenses/GPL-2.
-
-which is in the public domain.
-
-savelog may be redistributed under the following terms: (The rest of
-this file consists of savelog's distribution terms.)
-
-#ident "@(#)smail:RELEASE-3_2:COPYING,v 1.2 1996/06/14 18:59:10 woods Exp"
-
-SMAIL GENERAL PUBLIC LICENSE
-  (Clarified 11 Feb 1988)
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Comment: This is the Debian GNU/Linux package debianutils.
+ It is an original Debian package.  Programs in it were maintained by
+ Guy Maor , and are now maintained by Clint Adams
+ .
+
+Files: *
+Copyright: (see individual files)
+License: GPL-2+
+
+Files: installkernel
+Copyright:
+ Copyright (C) 1995 - 1998, Ian A. Murdock 
+ Copyright (C) 1998, 1999, Guy Maor
+ Copyright (C) 2002, Matthew Wilcox
+ Copyright (C) 2002, 2004, 2005, 2007, 2009  Clint Adams
+ Copyright (C) 2009  Manoj Srivasta
+License: GPL-2+
+
+Files: ischroot.c
+Copyright:
+ Copyright (C) 2011 Aurelien Jarno 
+ Copyright (C) 2015 Andreas Henriksson 
+License: GPL-2+
+
+Files: run-parts.*
+Copyright:
+ Copyright (C) 1994 Ian Jackson.
+ Copyright (C) 1996 Jeff Noxon 
+ Copyright (C) 1996-1999 Guy Maor 
+ Copyright (C) 2002-2020 Clint Adams
+License: GPL-2+
+
+Files: update-shells
+Copyright: 2021 Helmut Grohne 
+License: GPL-2+
+
+License: GPL-2+
+ All the package's programs except 'savelog', and 'which' may be
+ redistributed under the terms of the GNU GPL, Version 2 or later,
+ found on Debian systems in the file /usr/share/common-licenses/GPL-2.
+
+Files: which
+Copyright: public-domain
+License: public-domain
+ which is in the public domain.
 
+Files: savelog
+Copyright:
  Copyright (C)  1988 Landon Curt Noll & Ronald S. Karr
  Copyright (C)  1992 Ronald S. Karr
  Copyleft (GNU) 1988 Landon Curt Noll & Ronald S. Karr
-
+License: SMAIL-GPL
+ SMAIL GENERAL PUBLIC LICENSE
+   (Clarified 11 Feb 1988)
+ .
  Everyone is permitted to copy and distribute verbatim copies
  of this license, but changing it is not allowed.  You can also
  use this wording to make the terms for other programs.
-
-  The license agreements of most software companies keep you at the
-mercy of those companies.  By contrast, our general public license is
-intended to give everyone the right to share SMAIL.  To make sure that
-you get the rights we want you to have, we need to make restrictions
-that forbid anyone to deny you these rights or to ask you to surrender
-the rights.  Hence this license agreement.
-
-  Specifically, we want to make sure that you have the right to give
-away copies of SMAIL, that you receive source code or else can get it
-if you want it, that you can change SMAIL or use pieces of it in new
-free programs, and that you know you can do these things.
-
-  To make sure that everyone has such rights, we have to forbid you to
-deprive anyone else of these rights.  For example, if you distribute
-copies of SMAIL, you must give the recipients all the rights that you
-have.  You must make sure that they, too, receive or can get the
-source code.  And you must tell them their rights.
-
-  Also, for our own protection, we must make certain that everyone
-finds out that there is no warranty for SMAIL.  If SMAIL is modified by
-someone else and passed on, we want its recipients to know that what
-they have is not what we distributed, so that any problems introduced
-by others will not reflect on our reputation.
-
-  Therefore we (Landon Curt Noll and Ronald S. Karr) make the following 
-terms which say what you must do to be allowed to distribute or change 
-SMAIL.
-
-
-   COPYING POLICIES
-
-  1. You may copy and 

Bug#1022985: [Pkg-gtkpod-devel] Bug#1022985: libimobiledevice FTCBFS: python build dependencies not installable

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, 2022-11-02 at 17:08 +0100, Helmut Grohne wrote:
> On Wed, Nov 02, 2022 at 02:24:44PM +0100, Yves-Alexis Perez wrote:
> > Hi Helmut, thanks for the bug and the patch. Besides the add of :native
> > (and
> > :any) in various places, which make sense, I can see the drop of dh-
> > python. I
> > assume it's linked to this but could you explain a bit what is the reason?
> 
> I think this is a matter of taste and I tend to remove it due to DRY. In
> earlier times, you had to declare a debhelper addons in two places
> (Build-Depends and dh --with). Now you can enable it using Build-Depends
> alone. dh-python Provides dh-sequence-python3. Changing the dependency
> like that implicitly turns on --with python3. It doesn't hurt to keep
> dh-python in Build-Depends though. It just felt unnecessarily repetitive
> to me. Keep it or drop it. Both works for cross building.

Thanks for the explanation, it's definitely more clear for me. I might adapt
the patch a bit to add this information to the changelog and commits.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmNimvsACgkQ3rYcyPpX
RFtOOggArI1gI17JWQkx+D8SXrj4GiZdoBKgarf25AXcs1HYxC3pzMV8TMmGKFIt
crokNqRO66f4f+m0pEgicO+wSPGkpG3RNfIAhpsvbEDsLuCSFr4SNvAGoQ/m3x/s
OgAvsSUIA42sXl3i0n3K5FymVDcvQ3kTWU3ycbY1JH7quWTCsY4BPuSK+Owur1I6
Jt73XYR63R6RWMMHPFpTkiut93ljSGRLtrwYcizlT5++hUDUjrUoy/0vMX248FnR
7ERFJuHiNZEWJGjz7dMdhPsc0xuuR8vVrREi7rPIpu7C9blUFH8iq+T3T127UyB6
GsxXkRNGQTXghIZ/2Uern8AhPjhrAg==
=g7jl
-END PGP SIGNATURE-

Bug#1023345: spamassassin: plugin eval failed with unknown encoding 'MIME-Header'

[Francesco Potortì]

Package: spamassassin
Version: 4.0.0~rc3-3.1
Severity: normal
X-Debbugs-Cc: none, Francesco Potortì 
File: /usr/sbin/spamd

Starting few days ago, I get many of these in syslog:

plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 8342.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 248.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 2683.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 895.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 2194.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 2201.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 2181.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 135.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 220.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 161.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 243.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 292.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 309.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 220.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 212.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 225.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 191.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 1496.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 11184.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 1622.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 1924.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 253.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 184.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 243.
plugin: eval failed: Unknown encoding 'MIME-Header' at 
/usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090,  line 379.




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

Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=it_IT.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 spamassassin depends on:
ii  adduser 3.129
ii  curl7.85.0-1
ii  libhtml-parser-perl 3.79-1+b1
ii  libhttp-date-perl   6.05-2
ii  libio-string-perl   1.08-3.1
ii  libmail-dkim-perl   1.20220520-1
ii  libnet-dns-perl 1.35-1
ii  libnetaddr-ip-perl  4.079+dfsg-2+b1
ii  libsocket6-perl 0.29-2+b1
ii  libsys-hostname-long-perl   1.5-2
ii  libwww-perl 6.67-1
ii  lsb-base11.4
ii  perl [libarchive-tar-perl]  5.36.0-4
ii  sysvinit-utils [lsb-base]   3.05-6
ii  w3m 0.5.3+git20220429-1+b1

Versions of packages spamassassin recommends:
ii  gnupg  2.2.40-1
ii  libbsd-resource-perl   1.2911-2+b1
ii  libio-socket-inet6-perl2.73-1
ii  libmail-spf-perl   2.9.0-5
ii  perl [libsys-syslog-perl]  5.36.0-4
ii  sa-compile 4.0.0~rc3-3.1
ii  spamc  4.0.0~rc3-3.1

Versions of packages spamassassin suggests:
ii  libdbi-perl   1.643-3+b3
pn  libencode-detect-perl 
pn  libgeoip2-perl
ii  libio-socket-ssl-perl 

Bug#1022985: [Pkg-gtkpod-devel] Bug#1022985: libimobiledevice FTCBFS: python build dependencies not installable

[Helmut Grohne]

On Wed, Nov 02, 2022 at 02:24:44PM +0100, Yves-Alexis Perez wrote:
> Hi Helmut, thanks for the bug and the patch. Besides the add of :native (and
> :any) in various places, which make sense, I can see the drop of dh-python. I
> assume it's linked to this but could you explain a bit what is the reason?

I think this is a matter of taste and I tend to remove it due to DRY. In
earlier times, you had to declare a debhelper addons in two places
(Build-Depends and dh --with). Now you can enable it using Build-Depends
alone. dh-python Provides dh-sequence-python3. Changing the dependency
like that implicitly turns on --with python3. It doesn't hurt to keep
dh-python in Build-Depends though. It just felt unnecessarily repetitive
to me. Keep it or drop it. Both works for cross building.

Helmut

Bug#1023224: [Pkg-swan-devel] Bug#1023224: strongswan: autopkgtest regression: depends on no longer built strongswan-scepclient

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Mon, 2022-10-31 at 21:01 +0100, Paul Gevers wrote:
> With a recent upload of strongswan the autopkgtest of strongswan fails 
> in testing when that autopkgtest is run with the binary packages of 
> strongswan from unstable. It passes when run with only packages from 
> testing. In tabular form:
> 
>     pass    fail
> strongswan from testing    5.9.8-1
> all others from testing    from testing
> 
> I copied some of the output at the bottom of this report. The 
> autopkgtest d/t/control files says the first test depends on 
> strongswan-scepclient, but src:strongswan no long build it.

Hi Paul, thanks for the report but I'm not sure I totally understand it. The
strongswan-scepclient has indeed been removed in the 5.9.8 upload, so it's
definitely gone.

I'm not sure why the test is failing then and what I should have done
differently. Could you give me some pointers here?

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmNimmoACgkQ3rYcyPpX
RFtBzQf9H4dH0IMrBRuVBPPuYYm7l+61bvbp/+dtmqkw2dKGJFKTEKkH1+pEb8jl
0uWNXEONd1CjiwcNigt5/O+qhhsrX5t08RlQ3QdALuOyb8vpFmAX/mlI2peakRyF
daAuXvyyYRxa1827X894dsuKA/YZMe6UtlvraxyJsJTjZCTOI9LpeMDaMnXv5hwO
GXt/Dyg399FY9IZCgotIwY/8VbTLxPSCNE72vNyx9djJRBk5s+jtyMcc51jzwf+4
wm0TSpShtuw8odPWzkNYSMAPKAPn6wqYlx6D66YPLIAxNACTSBPz2iPRoYE5dRN4
IFOMmvN/z96Mz5rQPguANT4SURuaiA==
=6Bds
-END PGP SIGNATURE-

Bug#1022900: grub-install, efibootmgr etc. not working with new kernel

[Stephan Verbücheln]

Some updates.

linux-image-6.0.0-2-amd64 6.0.6-2 does not fix the bug.

In the upstream bug, a new set of new patches were mentioned which
should address this issue. I expect them to be merged into version
6.0.7.

New patches regarding EFI:
https://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git/log/?h=urgent

I will not apply any patches manually but just wait for the coming
releases instead. Anyone who has this issue right now can boot into
kernel 5.19 as a workaround.

Regards

Bug#1023329:

[Limonciello, Mario]

[Public]

FYI - the patch was originally targeted to ath-next (6.2), but because of the 
severity of this deadlock issue it's going to go to 6.1-rc with a CC to stable.
[v6.1] wifi: ath11k: avoid deadlock during regulatory update in 
ath11k_regd_update() - Patchwork 
(kernel.org)

Bug#1023343: iputils: machine-readable debian/copyright

[Bastian Germann]

Source: iputils
Version: 3:20211215-1
Severity: wishlist

Just for the record: I have pushed
https://salsa.debian.org/debian/iputils/-/commit/e83e27e32e3697c40cf3e44a5355d438b6c3aaed
that converts the debian/copyright file to the machine-readable format.

It would be nice if you could include this in the next (possibly bookworm?) 
upload.

Bug#1023344: eggdrop: Please upgrade debian package to Eggdrop Release v1.9.3 *STABLE*

[Bjoern Buerger]

Package: eggdrop
Version: 1.8.4+repack1-0.1
Severity: wishlist

Dear Maintainers,

Eggdrop v1.9.3 *STABLE* has been released on Aug 11, 2022

It would be awesome to have that version in Debian as well.


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

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

Versions of packages eggdrop depends on:
ii  eggdrop-data  1.8.4+repack1-0.1
ii  libc6 2.35-3
ii  libssl3   3.0.5-4
ii  libtcl8.6 8.6.12+dfsg-1+b1
ii  zlib1g1:1.2.11.dfsg-4.1

eggdrop recommends no packages.

eggdrop suggests no packages.

-- no debconf information

Bug#1023342: eggdrop dns module does not work on ipv6-only hosts

[Bjoern Buerger]

Package: eggdrop
Version: 1.8.4+repack1-0.1
Severity: important
Tags: ipv6

Dear maintainer,

using the eggdrop dns module on an ipv6-only host
fails with an "no valid dns servers found" error.

This happens, if
* /etc/resolv.conf contains only an IPv6 DNS Server
* and/or the system is ipv6-only
* the list of dns-servers, set with
  set dns-servers ""
  point to IPv6 Addresses.

Result: Long timeouts during operation

Workaround: Disable the module "dns" in your config


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

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

Versions of packages eggdrop depends on:
ii  eggdrop-data  1.8.4+repack1-0.1
ii  libc6 2.35-3
ii  libssl3   3.0.5-4
ii  libtcl8.6 8.6.12+dfsg-1+b1
ii  zlib1g1:1.2.11.dfsg-4.1

eggdrop recommends no packages.

eggdrop suggests no packages.

-- no debconf information

Bug#992269: texlive-bibtex-extra: Missing beebe bst stiles like abstract.bst

[Simone Piccardi]

Il 29/05/22 16:46, Hilmar Preuße ha scritto:
Not sure what your real issue is: the fact that the file is gone (I do 
not know yet, why it happened) or the fact that it is still listed on 
packages.debian.org? The latter should rather be reported to 
www.debian.org as the file is really gone.



The issue is the missing file, abstract.bst it's a quite useful 
bibliography style, that was present from ages and now is not there 
anymore. Don't care too much about the fact is still listed, if it's 
absent in the package.


I had to copy the content of the dir 
/usr/share/texlive/texmf-dist/bibtex/bst/beebe/ from buster and execute 
mktexlsr, but I'd like to know why this directory has been removed 
(while /usr/share/texlive/texmf-dist/bibtex/bib/beebe/ is still there).


Simone
--
Simone Piccardi Truelite Srl
picca...@truelite.it (email/jabber) Via Monferrato, 6
Tel. +39-347-103243350142 Firenze
http://www.truelite.it  Tel. +39-055-7879597

Bug#976707: O: kopanocore - Complete and feature rich groupware solution

[Andreas Beckmann]

On Mon, 07 Dec 2020 10:04:14 +0100 Carsten Schoenert 
 wrote:

I (as part of the pkg-giraffe team) intent to orphan src:kopanocore.



The pkg-giraffe-team is happy to offer help and guidance for interested
people which want to work on kopanocore (and also on related packages)
within Debian.


Can you move the git repository to the /debian space on salsa.d.o?
That would help anyone picking up the package.
I might do a QA upload applying the FTBFS patches sitting in the BTS, 
nothing more ;-)


Thanks.

Andreas

Bug#1023341: Fails to add any event due to too new python3-tzlocal

[Guido Günther]

Package: khal
Version: 1:0.10.4~ds-4
Severity: grave

Hi,
Adding a any new events on bookworm fails like (example is copied from
the manpage):

$ khal new 18:00 Awesome Event 
/usr/lib/python3/dist-packages/khal/icalendar.py:104: PytzUsageWarning: The 
localize method is no longer necessary, as this time zone supports the fold 
attribute (PEP 495). For more details on migrating to a PEP 495-compliant 
implementation, see 
https://pytz-deprecation-shim.readthedocs.io/en/latest/migration.html
  dtstart = timezone.localize(dtstart)
/usr/lib/python3/dist-packages/khal/icalendar.py:105: PytzUsageWarning: The 
localize method is no longer necessary, as this time zone supports the fold 
attribute (PEP 495). For more details on migrating to a PEP 495-compliant 
implementation, see 
https://pytz-deprecation-shim.readthedocs.io/en/latest/migration.html
  dtend = timezone.localize(dtend)
/usr/lib/python3/dist-packages/icalendar/parser.py:54: PytzUsageWarning: The 
zone attribute is specific to pytz's interface; please migrate to a new time 
zone provider. For more details on how to do so, see 
https://pytz-deprecation-shim.readthedocs.io/en/latest/migration.html
  if hasattr(dt.tzinfo, 'zone'):
/usr/lib/python3/dist-packages/icalendar/parser.py:55: PytzUsageWarning: The 
zone attribute is specific to pytz's interface; please migrate to a new time 
zone provider. For more details on how to do so, see 
https://pytz-deprecation-shim.readthedocs.io/en/latest/migration.html
  tzid = dt.tzinfo.zone  # pytz implementation
Traceback (most recent call last):
  File "/usr/bin/khal", line 5, in 
main_khal()
  File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
return self.main(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
rv = self.invoke(ctx)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/decorators.py", line 26, in 
new_func
return f(get_current_context(), *args, **kwargs)
  File "/usr/lib/python3/dist-packages/khal/cli.py", line 388, in new
new_func(
  File "/usr/lib/python3/dist-packages/khal/controllers.py", line 355, in 
new_from_string
new_from_args(
  File "/usr/lib/python3/dist-packages/khal/controllers.py", line 381, in 
new_from_args
collection.new(event)
  File "/usr/lib/python3/dist-packages/khal/khalendar/khalendar.py", line 208, 
in new
event.href, event.etag = self._storages[calendar].upload(event)
  File "/usr/lib/python3/dist-packages/khal/khalendar/vdir.py", line 212, in 
upload
if not isinstance(item.raw, str):
  File "/usr/lib/python3/dist-packages/khal/khalendar/event.py", line 382, in 
raw
timezone = create_timezone(tzinfo, self.start)
  File "/usr/lib/python3/dist-packages/khal/khalendar/event.py", line 858, in 
create_timezone
for one, two in iter(tz._tzinfos.items())
AttributeError: '_PytzShimTimezone' object has no attribute '_tzinfos'

This because khal can't cope with recent python3-tzlocal from bookworm (4.2-1),
downgrading python3-tzlocal (2.1-1) makes adding events work again (Got that
hint https://github.com/pimutils/khal/issues/1092)

As it fails to add any events I've picked grave severity. Please adjust
if you disagree.

Cheers,
  -- Guido


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

Kernel: Linux 6.0.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 khal depends on:
ii  python33.10.6-1
ii  python3-atomicwrites   1.4.1-1
ii  python3-click  8.0.3-1
ii  python3-click-log  0.3.2-1
ii  python3-configobj  5.0.6-5
ii  python3-dateutil   2.8.2-1
ii  python3-icalendar  4.0.3-5
ii  python3-packaging  21.3-1.1
ii  python3-pkg-resources  65.5.0-1
ii  python3-tz 2022.4-1
ii  python3-tzlocal4.2-1
ii  python3-urwid  2.1.2-2+b2
ii  python3-xdg0.27-3

Versions of packages khal recommends:
ii  python3-setproctitle  1.3.1-1

Versions of packages khal suggests:
pn  khal-doc  

-- no debconf information

Bug#792639: apt-listbugs: should use https to access bug tracking system

[marc]

Package: apt-listbugs
Version: 0.1.35
Followup-For: Bug #792639
X-Debbugs-Cc: marc.noto.5...@gmail.com




Hello, OpenSSL 3.0.5 is in bookworm. Are there other blockers to fix this issue?