Bug#1006744: open-vm-tools core dump on debian 10

[Chilukuri, Girish - Dell Team]

Hi Bernd,
Below is the full backtrace from all threads from the core file.

gdb /usr/bin/vmtoolsd rp_core.417

GNU gdb (Debian 8.2.1-2+b3) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/vmtoolsd...(no debugging symbols found)...done.
[New LWP 417]
[New LWP 1105]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/vmtoolsd'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:120
120 ../sysdeps/x86_64/multiarch/../strlen.S: No such file or directory.
[Current thread is 1 (Thread 0x7f321f095780 (LWP 417))]
(gdb) where
#0  0x7f321f589206 in __strlen_sse2 () at 
../sysdeps/x86_64/multiarch/../strlen.S:120
#1  0x7f321f56b475 in __GI___fputs_unlocked
(str=0x7f321e2f7ac8 , fp=fp@entry=0x55d222325690)
at iofputs_u.c:34
#2  0x7f321f5e4868 in __GI___vsyslog_chk (pri=, flag=1, 
fmt=0x7f321edc083c "%s.", ap=0x7ffd36e1eda0)
at ../misc/syslog.c:205
#3  0x7f321f5e4dff in __syslog_chk (pri=, flag=, fmt=)
at ../misc/syslog.c:129
#4  0x7f321edbb1db in Audit_EventV () at /lib/libvgauth.so.0
#5  0x7f321edbb2a4 in Audit_Event () at /lib/libvgauth.so.0
#6  0x7f321edb7f95 in VGAuth_AuditEvent () at /lib/libvgauth.so.0
#7  0x7f321edb6d05 in VGAuth_ValidateUsernamePassword () at 
/lib/libvgauth.so.0
#8  0x7f321edd1cf1 in  () at /usr/lib/open-vm-tools/plugins/common/libvix.so
#9  0x7f321edd22e3 in  () at /usr/lib/open-vm-tools/plugins/common/libvix.so
#10 0x7f321edd25d9 in  () at /usr/lib/open-vm-tools/plugins/common/libvix.so
#11 0x7f321edd81f6 in  () at /usr/lib/open-vm-tools/plugins/common/libvix.so
#12 0x7f321edcf2cb in  () at /usr/lib/open-vm-tools/plugins/common/libvix.so
#13 0x7f3221a5f664 in RpcChannel_Dispatch () at /lib/libvmtools.so.0
#14 0x7f3221a611de in  () at /lib/libvmtools.so.0
#15 0x7f3221a61aa4 in  () at /lib/libvmtools.so.0
#16 0x7f32218dfe98 in g_main_context_dispatch () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x7f32218e0288 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x7f32218e0582 in g_main_loop_run () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x55d221850bb6 in  ()
#20 0x55d22184fcc7 in main ()
(gdb) thread apply all bt

Thread 2 (Thread 0x7f321ed23700 (LWP 1105)):
#0  0x7f321f5df819 in __GI___poll (fds=0x55d22231b050, nfds=1, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f32218e01f6 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f32218e031c in g_main_context_iteration () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f32218e0361 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f32219084d5 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f321f6bbfa3 in start_thread (arg=) at 
pthread_create.c:486
#6  0x7f321f5ea4cf in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f321f095780 (LWP 417)):
#0  0x7f321f589206 in __strlen_sse2 () at 
../sysdeps/x86_64/multiarch/../strlen.S:120
#1  0x7f321f56b475 in __GI___fputs_unlocked
(str=0x7f321e2f7ac8 , fp=fp@entry=0x55d222325690)
at iofputs_u.c:34
#2  0x7f321f5e4868 in __GI___vsyslog_chk (pri=, flag=1, 
fmt=0x7f321edc083c "%s.", ap=0x7ffd36e1eda0)
at ../misc/syslog.c:205
#3  0x7f321f5e4dff in __syslog_chk (pri=, flag=, fmt=)
at ../misc/syslog.c:129
#4  0x7f321edbb1db in Audit_EventV () at /lib/libvgauth.so.0
#5  0x7f321edbb2a4 in Audit_Event () at /lib/libvgauth.so.0
#6  0x7f321edb7f95 in VGAuth_AuditEvent () at /lib/libvgauth.so.0
#7  0x7f321edb6d05 in VGAuth_ValidateUsernamePassword () at 
/lib/libvgauth.so.0
#8  0x7f321edd1cf1 in  () at /usr/lib/open-vm-tools/plugins/common/libvix.so
#9  0x7f321edd22e3 in  () at /usr/lib/open-vm-tools/plugins/common/libvix.so
#10 0x7f321edd25d9 in  () at /usr/lib/open-vm-tools/plugins/common/libvix.so
#11 0x7f321edd81f6 in  () at /usr/lib/open-vm-tools/plugins/common/libvix.so
#12 0x7f321edcf2cb in  () at /usr/lib/open-vm-tools/plugins/common/libvix.so
#13 0x7f3221a5f664 in RpcChannel_Dispatch () at /lib/libvmtools.so.0
#14 0x7f3221a611de in  () at /lib/libvmtools.so.0
#15 

Bug#1006870: sdl12-compat: please make the build reproducible

[Chris Lamb]

Hi Simon,

>> Instead of not calling dh_fixperms at all, a patch is attached that
>> lets it run as usual but then removes the executable bits.
>
> I don't think this is correct either: the executables need to be
> executable, and the test data needs to be non-executable.

Ah, whoops, looks like I screwed up in two ways here. I meant to write
"then removes the *group* executable bits" and the patch should match:

  -override_dh_fixperms:
  -dh_fixperms -Xusr/libexec/installed-tests
  +execute_after_dh_fixperms:
  +find debian -path "*/usr/libexec/installed-tests/*" -type f print0 | 
xargs -0r chmod g-x

> I'll do that next time I look at this package.

Sure thing; you will probably find a cleaner solution anyway. :)


Regards,

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

Bug#1006914: fonts-noto-color-emoji: Most emojis not displayed at all in Plasma

[Max Görner]

Package: fonts-noto-color-emoji
Version: 2.034-1
Severity: normal

Dear Maintainer,

I use KDE on Debian Bullseye and Bookworm. For several years most emojis did
not work, neither in the Konsole terminal nor in the title bar of
windows nor in notifications. However, recently I learned that emojis
work when using Xfce on Debian and even inside the Xfce terminal under
KDE.

I reported bug #1006685 [1] against kde-plasma-desktop. There it was
found that the required font configuration file is not provided.

I would assume that a font package should provide the required
configuration for all desktop environments of the distribution.
Therefore I am opening a bug for fonts-noto-color-emoji. If I am
mistaken I would be glad to learn which package I should file a bug
against.

Thank you very much.


Best Regards
Max Görner


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

Kernel: Linux 5.16.0-3-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=C.UTF-8 (charmap=UTF-8), LANGUAGE=de:en_GB
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

Bug#1005733: g++-11 internal compiler error when building onetbb on riscv64

[Matthias Klose]

Control: reassign -1 src:onetbb
Control: retitle -1 onetbb ftbfs on riscv64

this isn't reproducible at the moment. The build now fails with:

In file included from /<>/src/tbb/tools_api/ittnotify_static.c:17,

 from /<>/src/tbb/itt_notify.cpp:43:

/<>/src/tbb/tools_api/ittnotify_config.h: In function ‘long int 
__itt_interlocked_increment(volatile long int*)’:


/<>/src/tbb/tools_api/ittnotify_config.h:360:12: error: 
‘__TBB_machine_fetchadd4’ was not declared in this scope


  360 | return __TBB_machine_fetchadd4(ptr, 1) + 1L;

  |^~~

compilation terminated due to -Wfatal-errors.

Bug#808230: deluser --system should lock the account

[Marc Haber]

On Thu, Dec 17, 2015 at 01:56:50PM +0100, Marc Haber wrote:
> how to handle an account on package purge is a discussion going on for
> more than a decade now. After the umpteenth re-hash of the issue on
> #debian-devel, I have gotten the impression that there is rough
> consensus for not deleting system accounts on package purge. The most
> prominent argument for this situation is that the local admin might
> have given file ownership to the account while the package was
> installed, and when the account is deleted and its uid re-used later,
> those files may become accessible to an unintended entity.

I have filed #1006912 against policy to solicit the policy editor's
opinion.

adduser might probably go ahead prematurely by implementing deluser
--lock --system, locking an account if it's a system account.

Greetings
Marc

Bug#863751: Add --btrfs-subvolume-home option to adduser

[Marc Haber]

Control: retitle -1 use useradd's --btrfs-subvolume-home option
thanks

On Sun, Feb 21, 2021 at 08:52:39PM +0900, Osamu Aoki wrote:
> The current useradd since 2019 has --btrfs-subvolume-home option.

How does this option behave if the parent of the new home directory is
not on btrfs? adduser could add this option to all useradd calls but
this would only be possible if useradd will _silently_ ignore the option
if the parent directory is not btrfs and of course create a normal
directory in that case. If the operation is not silent, package
maintainers are going to redirect adduser's output to /dev/null which is
not desired from adduser's pov.

Greetings
Marc

Bug#1006912: is it time to have account deletion in policy?

[Marc Haber]

Package: debian-policy
Version: 4.6.0.1
Severity: wishlist

Hi!

Currently, Policy does contain guidelines about system accounts being
created on package installation. It is, however, more reluctant to give
advice about accout deletion on package uninstall and/or purge. In
Addition, the existing advice is somewhat hidden in chapter 9.2.2
documetning UID and GID classes.

There is the requirement that a purged package vanishes completly. There
seems to be consensus about this being not a good idea regarding account
deletion since noone knows whether the local admin has given some files
to the package account which would be left around unowned (and could
even suddenly belong to a new account that was creatd with the same
UID).

There are way over 514 packages matching "adduser.*--system" on
codesearch.debian.net, but just 125 packages containing
"deluser.*--system". I didn't check in all details whether all of those
matches are in maintainer scripts, but I think that this gives a rough
overview how many packages do not delete their account at the current
time.

How about putting advice like this in policy:

Suggestion 1:
Create a dedicated chapter (which would ideally be placed between the
current chapters 9.2.1. Introduction and 9.2.2. UID and GID classes)
named "dynamically allocated system users or groups for packages" with
the following contents:
- packages can create users and groups on installation
- usernames should be chosen wisely, allowing to deduce the related
  package from the name, and prefixed with an underscore
- adduser --system is the preferred method to create package account, it
  takes responsibility of being policy compliant. Other packages doing
  this job might exist (dh-sysuser, for example).

Suggestion 2a:
Document that a package should not delete its user on uninstallation
and/or purge. This reflects current practice of most packages but might
need changes in some packages that currently delete their user. Those
packages are the reason that this policy item should not be introduced
as a MUST.

Suggestion 2b:
Document that a package may lock its user on uninstall, but leave it on
the system on purge. That way, a leftover account could not be used as
an attack vector and just blocks the uid/gid and the name. On
reinstallation of a package, the existing, locked account would just be
unlocked.

This would be a new behavior that could be worth documenting in Policy.
Should the policy editors indicate that this might be an option, adduser
would be willing to implement a deluser --lock --system option that
would lock a named account if its uid is in the appropriate range for
system accounts, and adduser --system would not error out if the account
already exists and would just remove the lock. Thus implementing this
option in a package would just mean to add the appropriat deluser call
to postrm uninstall while postinst can remain unchanged.

transparency advice: I am on the adduser maintainer team and have the
longest track history of caring for adduser of all active team members.

I am willing to suggest wording, but I am not a policy expert and
wording would probably be better if an experienced policy editor would
write the appropriate language. How would a new chapter be inserted in
Policy without destroying existing references to chapter numbers?

I would like to hear your opinion on that. Thanks for considering.

Greetings
Marc

Bug#1000155: sorry for the noise / Re: #1006908 ITA: daemontools -- collection of tools for managing UNIX services

[Joost van Baal-Ilić]

Oops, this message belonged somewhere else, sorry for the noise!

Joost

On Tue, Mar 08, 2022 at 06:13:52AM +0100, Joost van Baal-Ilić wrote:
> retitle 1006908 ITA: daemontools -- collection of tools for managing UNIX 
> services

Bug#925511: adduser: [INTL:pt] Update on Portuguese translation of manpage

[Marc Haber]

Control: tags -1 moreinfo
thanks

Hi,

thanks for your work. Please reconsider assigning copyright to the FSF,
they don't have any stakes in Debian and in adduser. Feel free to add
yourself as the copyright owner, and please add a license statement. I
would prefer if you could put the tranlation "under the same license as
adduser itself", which would be the GPL 2 or any later version.

You might also want to review the program and debconf template
translation.

Greetings
Marc

On Mon, Mar 25, 2019 at 11:45:02PM +, Américo Monteiro wrote:
> Package: adduser
> Version: 3.118
> 3ags: l10n, patch-
> Severity: wishlist
> 
> Updated Portuguese translation for  adduser's manpage
> Translator: Américo Monteiro 
> Feel free to use it.
> 
> For translation updates please contact 'Last Translator' 
> 
> -- 
> Melhores cumprimentos/Best regards,
> 
> Américo Monteiro
> 
> 

Bug#801067: nfs-common: Remove or updated README.Debian.nfsv4

[Salvatore Bonaccorso]

Source: nfs-utils
Source-Version: 1:2.6.1-1

On Mon, Oct 05, 2015 at 09:32:39PM +0100, Reuben Thomas wrote:
> Package: nfs-common
> Version: 1:1.2.8-6ubuntu1.1
> Severity: normal
> 
> The README.Debian.nfsv4 file is now rather old; is NFSv4 really still
> considered experimental?
> 
> Parts of this file may be worth keeping (I???m not an expert!), but at least
> that claim should be removed, and mention of kernel versions and patch sets.

We have removed the outdated README.Debian.nfsv4 in the 1:2.6.1-1
upload.

Regards,
Salvatore

Bug#1000155: #1006908 ITA: daemontools -- collection of tools for managing UNIX services

[Joost van Baal-Ilić]

retitle 1006908 ITA: daemontools -- collection of tools for managing UNIX 
services
owner 1006908 !
thanks

I intend to adopt the daemontools package, and upload it with myself as Mainter
in debian/control.

On Date: Tue, 8 Mar 2022 05:50:26 +0100, Jan Mojzis  
wrote:
> I planned to manage the daemontools package (new repo is here
> https://salsa.debian.org/debian/daemontools), but I didn't get a sponsor.  I
> leave the packaging to someone else.  The package is orphaned.

Jan: Would you like to be recorded as co-maintainer?  (Listed in Uploaders: in
debian/control .)

Anyway, thanks a lot for setting up the salsa repo, that's very helpful.  And
thanks a lot for your work on the packaging, of course!  At a first glance, it
looks ready for uploading: very nice work.

Bye,

Joost



signature.asc
Description: PGP signature

Bug#1006910: pdal: Should not be included in bookworm

[Bas Couwenberg]

Source: pdal
Version: 2.3.0+ds-2
Severity: serious
Tags: upstream
Justification: in the maintainer's opinion, makes the package unsuitable for 
release

PDAL upstream has exhausted my tolerance of his combative attitude. I am
no longer willing to spend time on maintaining this package.

The package should be removed from Debian, as others should not be
subjected to his attitude either.

At time of writing cloudcompare and facet-analyser have pdal as a build
dependency, and paraview also has it in its binary package dependencies.

These packages will need to remove their pdal support. Once that's done
pdal can be removed from Debian.

If anyone wants to take over maintenance of the pdal package despite a
combative upstream, that will need to happen outside the GIS team.

Bug#1006909: impressive: Fails to find any pages in the presentation

[Gunnar Wolf]

Package: impressive
Version: 0.13.0~beta2-2
Severity: important
Tags: patch

Whenever I try to open a PDF presentation with impressive, I get the
following error message:

Welcome to Impressive version 0.13.0-beta2 (SVN r298)
pygame 1.9.6
Hello from the pygame community. https://www.pygame.org/contribute.html
Detected screen size: 1920x1080 pixels
PDF renderer: Xpdf/Poppler
pdftkParse() FAILED
WARNING: The input file `/tmp/testfile.pdf' could not be analyzed.
The presentation doesn't have any pages, quitting.

Do note that I am running this on ARM64, and using Wayland.

And... Oh! This seems to be due to a missing dependency! I was
checking through the list of versions of depends/recommends/suggests
(am not running reportbug from the affected system), and turns out
that installing pdftk (or rather, pdftk-java, as pdftk is now just a
transitional package) fixes the issue. Just for completeness sake, the
PDF renderer is still marked to be Xpdf/Poppler, but now it reports
"OpenGL renderer: FD630" and... works! :-D

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

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

Versions of packages impressive depends on:
ii  poppler-utils   20.09.0-3.1
ii  python3 3.9.8-1
ii  python3-pil 9.0.1-1
pn  python3-pygame  1.9.6+dfsg-5

Versions of packages impressive recommends:
ii  ffmpeg 7:4.3.1-3+b2
ii  mplayer2:1.4+ds1-1+b1
ii  perl   5.34.0-3
ii  xdg-utils  1.1.3-4.1

Versions of packages impressive suggests:
ii  ghostscript   9.55.0~dfsg-3
pn  latex-beamer  
pn  pdftk 
diff --git a/debian/control b/debian/control
index 12a1a9d..981c495 100644
--- a/debian/control
+++ b/debian/control
@@ -28,13 +28,13 @@ Depends: python3,
  python3-pygame,
  python3-pil,
  mupdf-tools (>= 1.5) | poppler-utils,
+pdftk-java,
 Recommends: mplayer,
 ffmpeg,
 perl,
 xdg-utils
 Suggests: ghostscript,
   latex-beamer,
-  pdftk,
 Conflicts: keyjnote (<< 0.10.2r-0)
 Provides: keyjnote
 Replaces: keyjnote (<< 0.10.2r-0)

Bug#1006908: O: daemontools -- collection of tools for managing UNIX services

[Jan Mojzis]

Package: wnpp
Severity: normal
Control: affects -1 src:daemontools

I planned to manage the daemontools package 
(new repo is here https://salsa.debian.org/debian/daemontools),
but I didn't get a sponsor.
I leave the packaging to someone else.

The package is orphaned.

Bug#960927: gerbera: Version 1.1.0 is very old, please update it

[Nicholas D Steeves]

Hi Hamish, James, and Francesco,

Hamish Moffatt  writes:

Subject: Bug#960927: version 1.10
> The current version is now 1.10. Could you please update the package?

In the future, please don't rewrite the subject header, because this
makes it hard to tell what package the bug refers to...which I hope
you'll see is disadvantageous to getting the bug fixed ;-)

Hi James!

I've CCed you because you're the maintainer of this package and wonder
if you might not have received emails about this bug.  If you're too
busy to take care of this longstanding new version bug, would you please
consider reaching out to the team to find a new maintainer, and/or
filing and RFA or Orphaning bug?  As it stands, gerbera meets the
criteria for salvaging, so there's that too.  An RFA or O bug (or RFH
bug) will make it easier for prospective DMs to find a package they can
contribute to :-)

Kind regards,
Nicholas


signature.asc
Description: PGP signature

Bug#1006907: Xorg - blackscreen (no output?) from output connectors on #2 PCIe graphics card

[Felix Miata]

Package: xserver-xorg-core
Version: 2:21.1.3-2+b1

SUMMARY:
Xorg - blackscreen (no output?) from output connectors on #2 PCIe graphics card

APPLIES TO:
Bookworm
Bullseye
Buster
Stretch

NOT TESTED:
Sid

Not used:
kernel command line options affecting Xorg graphics
/etc/X11/xorg.con*
xrandr
desktop display configuration applets

IOW, what follows is purely Xorg's automatic configuration output results.

TO REPRODUCE:
Start a DM (SDDM or TDM) and login to an Xorg (TDE, IceWM or Plasma) session,
or start an Xorg session with startx.

ACTUAL BEHAVIOR (output_only_on_2_displays_connected_to_first_gfxcard):
# xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x43 cap: 0xf, Source Output, Sink Output, Source Offload, Sink 
Offload crtcs: 2 outputs: 3 associated providers: 1 name:modesetting
Provider 1: id: 0xff cap: 0xf, Source Output, Sink Output, Source Offload, Sink 
Offload crtcs: 2 outputs: 2 associated providers: 1 name:modesetting
# xrandr | egrep 'onnect|creen|\*' | grep -v disconn | sort -r
VGA-1 connected 1680x1050+1920+0 (normal left inverted right x axis y axis) 
474mm x 296mm
Screen 0: minimum 320 x 200, current 3600 x 1200, maximum 16384 x 16384
DVI-I-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y 
axis) 519mm x 324mm
DVI-I-1-3 connected (normal left inverted right x axis y axis)
DVI-I-1-2 connected (normal left inverted right x axis y axis)
   1920x1200 59.95*+
   1680x1050 59.97*+  74.8959.9559.88
# inxi -Sy
System:
  Host: gb970 Kernel: 5.16.0-3-amd64 x86_64 bits: 64 Desktop: Trinity R14.0.12
Distro: Debian GNU/Linux bookworm/sid
# inxi -Gayz
Graphics:
  Device-1: NVIDIA GF108 [GeForce GT 630] vendor: Gigabyte driver: nouveau
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16 ports:
active: DVI-I-1,VGA-1 empty: HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:0f00
class-ID: 0300
  Device-2: NVIDIA G84 [GeForce 8600 GT] vendor: XFX Pine driver: nouveau
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 4 link-max: lanes: 16 ports:
active: none off: DVI-I-2,DVI-I-3 empty: none bus-ID: 05:00.0
chip-ID: 10de:0402 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting
gpu: nouveau display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3600x1200 s-dpi: 120 s-size: 762x254mm (30.0x10.0")
s-diag: 803mm (31.6")
  Monitor-1: DVI-I-1 pos: primary,left model: NEC EA243WM serial: 1Z101367NA
built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
size: 519x324mm (20.4x12.8") diag: 612mm (24.1") ratio: 16:10 modes:
max: 1920x1200 min: 640x480
  Monitor-2: VGA-1 pos: right model: Lenovo L2251x Wide serial: 6V647310
built: 2011 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
size: 474x296mm (18.7x11.7") diag: 559mm (22") ratio: 16:10 modes:
max: 1680x1050 min: 720x400
  OpenGL: renderer: NVC1 v: 4.3 Mesa 21.2.6 direct render: Yes
#

EXPECTED BEHAVIOR (output_on_all_4_connected_displays):
# xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x43; cap: 0xf (Source Output, Sink Output, Source Offload, 
Sink Offload); crtcs: 2; outputs: 3; associated providers: 1; name: modesetting
output DVI-I-1
output HDMI-1
output VGA-1
Provider 1: id: 0xee; cap: 0xf (Source Output, Sink Output, Source Offload, 
Sink Offload); crtcs: 2; outputs: 2; associated providers: 1; name: modesetting
output DVI-I-1-2
output DVI-I-1-3
# xrandr | egrep 'onnect|creen|\*' | grep -v disconn | sort -r
VGA-1 connected 1680x1050+1920+0 (normal left inverted right x axis y axis) 
474mm x 296mm
Screen 0: minimum 320 x 200, current 7760 x 1440, maximum 16384 x 16384
DVI-I-1-3 connected 1600x900+6160+0 (normal left inverted right x axis y axis) 
443mm x 249mm
DVI-I-1-2 connected 2560x1440+3600+0 (normal left inverted right x axis y axis) 
598mm x 336mm
DVI-I-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y 
axis) 519mm x 324mm
   2560x1440 59.95*+
   1920x1200 59.95*+
   1680x1050 59.97*+  74.8959.9559.88
   1600x900  59.98*+  59.9559.82
# inxi -Syz
System:
  Kernel: 5.15.12-1-default x86_64 bits: 64 Desktop: KDE Plasma 5.24.2
Distro: openSUSE Tumbleweed 20220302
# inxi -Gayz
Graphics:
  Device-1: NVIDIA GF108 [GeForce GT 630] vendor: Gigabyte driver: nouveau
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16 ports:
active: DVI-I-1,VGA-1 empty: HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:0f00
class-ID: 0300
  Device-2: NVIDIA G84 [GeForce 8600 GT] vendor: XFX Pine driver: nouveau
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 4 link-max: lanes: 16 ports:
active: DVI-I-2,DVI-I-3 empty: none bus-ID: 05:00.0 chip-ID: 10de:0402
class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.3 compositor: kwin_x11 driver: X:
loaded: modesetting unloaded: fbdev,vesa alternate: nouveau,nv,nvidia
gpu: nouveau display-ID: :0 screens: 1
  Screen-1: 0 s-res: 7760x1440 s-dpi: 120 s-size: 1642x304mm (64.6x12.0")
s-diag: 1670mm (65.7")
  Monitor-1: DVI-I-1 

Bug#1006842: ovmf 2022.02-1 makes TPM unusable in Windows guests

[dann frazier]

On Sun, Mar 06, 2022 at 04:47:58PM +, Etienne Dechamps wrote:
> Package: ovmf
> Version: 2022.02-1
> Severity: important
> Control: fixed -1 2021.11-1
> 
> An ovmf regression somewhere between 2021.11-1 and 2022.02-1 makes it
> impossible to use a TPM in Windows guest VMs (tested with various
> Windows 11 builds). The Windows Device Manager shows the TPM as
> defective, with the error "This device cannot start. (Code 10) A
> protocol error was detected between the driver and the device".
> tpm.msc shows no TPM is available.
> 
> One consequence is that Windows 11 refuses to install with ovmf
> 2022.02-1, since the Windows 11 installer demands a functional TPM.
> 
> Steps to reproduce using qemu-system-x86 1:6.2+dfsg-2 and swtpm 0.7.1-1:
> 
> # mkdir /tmp/tpm
> # swtpm socket --tpm2 --tpmstate dir=/tmp/tpm --ctrl
> type=unixio,path=/tmp/tpm/sock &
> # qemu-system-x86_64 -enable-kvm -drive
> if=pflash,format=raw,readonly=on,file=/usr/share/OVMF/OVMF_CODE.fd
> -chardev socket,id=tpm,path=/tmp/tpm/sock -tpmdev
> emulator,id=tpm,chardev=tpm -device tpm-tis,tpmdev=tpm …
> 
> With ovmf 2021.11-1, the TPM is functional in Windows using the above
> parameters; with 2022.02-1, it is not. Switching to "tpm-crb" doesn't
> seem to make any difference.
> 
> In Linux guests the TPM appears to be functional, although the guest
> kernel outputs the following messages with 2022.02-1:
> 
> tpm_tis MSFT0101:00: 2.0 TPM (device-id 0x1, rev-id 1)
> tpm tpm0: A TPM error (256) occurred attempting the self test
> tpm tpm0: starting up the TPM manually
> 
> With 2021.11-1, the kernel only outputs the first line - no errors.

Thanks for the bug report. Apparently upstream renamed the flag to
enable the TPM, so we need to adjust the build:
  
https://github.com/tianocore/edk2/commit/4de8d61bcec02a13ceed84f92b0cf3ea58adf9c5

  -dann

Bug#1006906: plocate: cifs file system not being indexed by plocate or mlocate

[Ed Biow]

Package: plocate
Version: 1.1.13-1~bpo11+1
Severity: normal
X-Debbugs-Cc: edmundb...@gmail.com

Dear Maintainer,

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

   * What led up to the situation?

I noticed that the locate command is not indexing files on my local samba
server, which is where the vast majority of my files exist. My server mounts
from the fstab automatically, the entry in /proc/mounts is something like this:
//server/share /mnt/server cifs
rw,relatime,vers=3.1.1,cache=strict,username=USERNAMe,uid=1000,forceuid,gid=1000,forcegid,addr=192.168.223.169,file_mode=0777,dir_mode=0777,soft,nounix,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1
0 0
I always change the /etc/updatedb.conf file to remove cifs from PRUNEFS. The
command works as expected on my Ubuntu systems, mostly 20.04 using the
0.26-3ubuntu3 of mlocate. In the past mlocate worked on Debian.
The locate command is pretty useless to me without indexing my cifs directory.


   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I repeatedly purged mlocate & plocate and tried different versions of mlocate
and plocate, both the standard bullseye stable version and the bullseye-
backports versions. I updated my updatedb.conf file and ran updatedb, but the
programs failed to index my server. The mlocate versions I tried were
1.1.13-1~bpo11+1 100 & 0.26-5. The plocate version I currently have installed
is the backports 1.1.13-1~bpo11+1, but I also tried the main repository
1.1.8-2+deb11u1 version. I also tried setting a new temporary 'updatedb' with
the command "updatedb -o /tmp/plocate.db" and searched it with 'locate -d
/tmp/plocate.db' but still couldn't see files on my server.


   * What was the outcome of this action?

No joy. locate only dredges up files stored on my local computer.

   * What outcome did you expect instead?

I expected updatedb to index my cifs share on my server as it has in the past.

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


-- System Information:
Debian Release: 11.2
  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-11-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plocate depends on:
ii  libc6   2.31-13+deb11u2
ii  libgcc-s1   10.2.1-6
ii  libstdc++6  10.2.1-6
ii  liburing1   0.7-3
ii  libzstd11.4.8+dfsg-2.1

plocate recommends no packages.

Versions of packages plocate suggests:
ii  systemd-sysv  247.3-6

-- Configuration Files:
/etc/updatedb.conf changed:
PRUNE_BIND_MOUNTS="yes"
PRUNEPATHS="/tmp /var/spool /media /var/lib/os-prober /var/lib/ceph"
PRUNEFS="NFS afs autofs binfmt_misc ceph cgroup cgroup2  coda configfs
curlftpfs debugfs devfs devpts devtmpfs ecryptfs ftpfs fuse.ceph fuse.glusterfs
fuse.gvfsd-fuse fuse.mfs fuse.rclone fuse.rozofs fuse.sshfs fusectl  hugetlbfs
iso9660 lustre lustre_lite mfs mqueue ncpfs nfs nfs4 ocfs ocfs2 proc pstore
rpc_pipefs securityfs shfs  sysfs tmpfs tracefs udev udf usbfs"

Bug#1006905: bullseye-pu: package ostree/2020.8-2+deb11u1

[Simon McVittie]

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

This update isn't finalized yet, but does it look like something of a
scale that you would be likely to accept in a point release?

[ Reason ]
Backport several bug fixes from testing/unstable, prompted by a user
request in #1004467 and various issues reported to Flatpak upstream

[ Impact ]
In descending priority order:

If d/p/Fall-back-if-copy_file_range-fails-with-EINVAL.patch is not applied,
users with an eCryptFS encrypted home directory cannot use `flatpak --user`.
If they had already configured all necessary remotes before encrypting the
home directory, the symptom is that `flatpak build-bundle` crashes; if not,
from my tests on unstable, it appears that the symptom is that
`flatpak remote-add` fails. (#1004467)
There are indications from upstream bug reports that this patch might
also fix similar issues for ZFS users, although this is not yet confirmed.

If d/p/Fix-marking-static-delta-commits-as-partial.patch is not applied,
interrupted downloads can result in a corrupted local repository, requiring
manual cleanup via `flatpak repair` or `ostree fsck`.

If d/p/libotutil-Avoid-infinite-recursion-during-error-unwinding.patch is
not applied, some failure modes (in particular the symptom of #1004467)
lead to a crash instead of a graceful failure.

If d/p/Fix-translation-of-file-URIs-into-paths.patch is not applied,
users will be unable to install Flatpak apps from paths on the local
filesystem that contain a backslash or non-ASCII, most commonly during
"sideloading" from a USB stick created by `flatpak create-usb`.

If d/p/lib-Fix-a-bad-call-to-g_file_get_child.patch is not applied,
checking out only a subset of a commit (most frequently seen in Flatpak
when installing locale data) can fail with an assertion failure if a
backport or local build of GLib 2.71 is in use. I'm a little unsure about
this one for bullseye, since I would generally not recommend backporting
something as foundational as GLib, but it's a one-line fix. With my
GNOME team hat on, we need to get GLib >= 2.72 into bookworm within the
next few weeks, so if someone does a backport of bookworm's GLib into
bullseye-backports, then the priority of this change will suddenly go up.

[ Tests ]
Automated tests are run at build-time and via autopkgtest, and pass.
Build-time and ci.debian.net coverage are limited by the buildd and
debci testbed using schroot/lxc, which prevents some of the more exotic
scenarios from being tested, but I run tests on an amd64 qemu VM before
each upload and those also pass.

I will give this some real-world testing via Flatpak on bullseye
before upload (in particular to confirm that the eCryptFS fix has been
successful), but so far it has only had automated tests.

[ Risks ]
I would say this is low-risk. They're narrowly-targeted patches, and
all are straightforward backports, either from upstream release 2022.2
(in unstable, not in testing yet) or from older releases that are already
in testing.

If one of these changes does cause a regression, then it's most likely to
be something similar to the bugs I'm fixing: a crash in a very specific
scenario that most Flatpak users don't exercise.

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

[ Changes ]
See d/changelog, the Impact description above, and the individual patches
for details.

[ Other info ]
I'm open to suggestions for additional patches with a similar risk/impact
ratio. I've cc'd Dan Nicholson, who maintains the fork of our Flatpak and
libostree packages in Endless, a Debian derivative that makes very heavy use
of both Flatpak and libostree.
diff --git a/debian/changelog b/debian/changelog
index 3e4cd1b0..0bd98941 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,30 @@
+ostree (2020.8-2+deb11u1) UNRELEASED; urgency=medium
+
+  * d/gbp.conf, d/control: Branch for Debian 11 updates
+  * Backport various bug fixes from newer libostree releases.
+Each of these fixes an issue that was reported against Flatpak when
+using the libostree from Debian 11, either via bullseye or
+buster-backports.
+- d/p/Fall-back-if-copy_file_range-fails-with-EINVAL.patch:
+  Add patch to fall back if copy_file_range fails with EINVAL.
+  This fixes an incompatibility with eCryptFS, in particular when
+  using Flatpak in an eCryptFS home directory. (Closes: #1004467)
+- d/p/libotutil-Avoid-infinite-recursion-during-error-unwinding.patch:
+  Avoid infinite recursion when recovering from certain errors, in
+  particular the one that was a symptom of #1004467.
+- d/p/Fix-marking-static-delta-commits-as-partial.patch:
+  Mark commits as partial before downloading, to avoid Flatpak and other
+  ostree 

Bug#910028: [Freedombox-pkg-team] Bug#910028: marked as done (pagekite: Stopped logging to /var/log/pagekite/ when using systemd)

[Sunil Mohan Adapa]

On 3/7/22 15:30, Petter Reinholdtsen wrote:

[Sunil Mohan Adapa]

Yes, we can create a README file in /var/log/pagekite to avoid the
confusion it creates. Alternatively, could the confusion have been
avoided if /var/log/pagekite directory was not created at all? I would
guess that people will start looking at centralized logging such as
/var/log/syslog when they don't find service specific logging.


My idea was more to replace the file content in /var/log/pagekite/ with
instructions to look elsewhere, but a README could work too.

I was looking in /var/log/pagekite/ because it was the place to look the
last time I debugged pagekite.  I assume new installations do not have
this directory at all.


We have /var/log/pagekite listed in debian/dirs. New installations might 
be creating this directory unnecessarily.


--
Sunil


OpenPGP_0x36C361440C9BC971.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1006904: debsnap: Add a -l option as the short version of --list

[David (Plasma) Paul]

Source: devscripts
Version: 2.22.1
Severity: wishlist
Tags: patch

Dear Maintainer,

Please accept the attached patch which adds a -l short option to debsnap
that serves the same function as the existing --list long option.

I believe this patch should be directly `git am`-able as I created it
with `git format-patch`. This is my first time using `git format-patch`
to submit a patch, so if there's anything wrong with the patch, please
let me know. (Then I'll have a reason to use the `-v` option of `git
format-patch` for the first time as well.)

Thanks,

-- 
Plasma
>From 6c04b315752a3a8ba9ca24367355d790dabcd80f Mon Sep 17 00:00:00 2001
From: "David (Plasma) Paul" 
Date: Mon, 7 Mar 2022 16:41:09 -0600
Subject: [PATCH] debsnap: Add a -l option as the short version of --list.

---
 debian/changelog   | 4 
 scripts/debsnap.1  | 2 +-
 scripts/debsnap.pl | 4 ++--
 3 files changed, 7 insertions(+), 3 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 713b9085..b220c546 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -4,6 +4,10 @@ devscripts (2.22.2) UNRELEASED; urgency=medium
   * who-permits-upload:
 + Fix fingerprint lookup, so it actually finds the user id
 
+  [ David Paul ]
+  * debsnap:
++ Add a -l option as the short version of --list.
+
  -- Mattia Rizzolo   Sun, 23 Jan 2022 18:04:17 +0100
 
 devscripts (2.22.1) unstable; urgency=medium
diff --git a/scripts/debsnap.1 b/scripts/debsnap.1
index 11fae5b9..7958e9e9 100644
--- a/scripts/debsnap.1
+++ b/scripts/debsnap.1
@@ -45,7 +45,7 @@ Report on the \fBdebsnap\fP configuration being used and progress during the
 download operation.  Please always use this option when reporting bugs.
 
 .TP
-.BR \-\-list
+.BR \-l ", " \-\-list
 Don't download but just list versions.
 
 .TP
diff --git a/scripts/debsnap.pl b/scripts/debsnap.pl
index f687259c..09be5355 100755
--- a/scripts/debsnap.pl
+++ b/scripts/debsnap.pl
@@ -85,7 +85,7 @@ The following options are supported:
 Default is ./source-
 -f, --force Force overwriting an existing
 destdir
---list  Don't download but just list versions
+-l, --list  Don't download but just list versions
 --binaryDownload binary packages instead of
 source packages
 -a ,
@@ -215,7 +215,7 @@ Getopt::Long::Configure('no_ignore_case');
 GetOptions(
 \%opt,'verbose|v', 'destdir|d=s', 'force|f',
 'help|h', 'version',   'first=s', 'last=s',
-'list',   'binary','architecture|a=s@'
+'list|l', 'binary','architecture|a=s@'
 ) || usage(1);
 
 usage(0)  if $opt{help};
-- 
2.28.0

Bug#910028: [Freedombox-pkg-team] Bug#910028: marked as done (pagekite: Stopped logging to /var/log/pagekite/ when using systemd)

[Petter Reinholdtsen]

[Sunil Mohan Adapa]
> Yes, we can create a README file in /var/log/pagekite to avoid the
> confusion it creates. Alternatively, could the confusion have been
> avoided if /var/log/pagekite directory was not created at all? I would
> guess that people will start looking at centralized logging such as
> /var/log/syslog when they don't find service specific logging.

My idea was more to replace the file content in /var/log/pagekite/ with
instructions to look elsewhere, but a README could work too.

I was looking in /var/log/pagekite/ because it was the place to look the
last time I debugged pagekite.  I assume new installations do not have
this directory at all.
--
Happy hacking
Petter Reinholdtsen

Bug#910028: [Freedombox-pkg-team] Bug#910028: marked as done (pagekite: Stopped logging to /var/log/pagekite/ when using systemd)

[Sunil Mohan Adapa]

On 3/3/22 21:13, Petter Reinholdtsen wrote:

[Sunil Mohan Adapa]

I believe that we should not re-enable logging to /var/log/pagekite.


What about adding a message into /var/log/pagekite/ , if the old log
files exist during package upgrade, stating that the logging now is done
via journald?  It would have saved me some time when I had to debug
pagekite last time.



Yes, we can create a README file in /var/log/pagekite to avoid the 
confusion it creates. Alternatively, could the confusion have been 
avoided if /var/log/pagekite directory was not created at all? I would 
guess that people will start looking at centralized logging such as 
/var/log/syslog when they don't find service specific logging.


--
Sunil


OpenPGP_0x36C361440C9BC971.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

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

[Felix Lechner]

Hi,

On Sun, Nov 7, 2021 at 11:37 PM intrigeri  wrote:
>
> The bug lies in the interaction between these 2 tools.

Yay, the problem was solved! [1] Will you please deploy the fix with a
little bit of urgency? Lintian's pipeline has been malfunctioning for
a little while. Thanks!

Kind regards,
Felix Lechner

[1] 
https://github.com/Perl-Critic/Perl-Critic/issues/925#issuecomment-1048340859

Bug#960927: version 1.10

[Hamish Moffatt]

The current version is now 1.10. Could you please update the package?

Bug#1004915: transition: ruby2.7-rm

[Lucas Kanashiro]

Hi Paul,

Em 06/03/2022 17:58, Paul Gevers escreveu:

Hi

On 27-02-2022 14:07, Antonio Terceiro wrote:

The fix for that is probably non-trivial, so IMO we should remove
diaspora-installer from testing to let the transition complete.


diaspora-installer was removed, and ruby-defaults migrated to testing. 
Under the assumption that you haven't seen any fall-out that needs 
fixing first (please let me know), you can proceed with the upload of 
ruby-defaults where ruby2.7 support is dropped.


I uploaded ruby-defaults/1:3.0+1 removing ruby2.7 support.

--
Lucas Kanashiro

Bug#1006903: please split reformail in a separate binary package

[Antoine Beaupre]

Package: maildrop
Severity: wishlist

reformail(1) is a useful program on its own, and it would be nice to
be able to install it without installing all of maildrop. This would
be particularly because maildrop ships with a SUID root binary that
could be incompatible with certain security policy deployments.


-- System Information:
Debian Release: 11.2
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable'), 
(1, 'unstable'), (1, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-11-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.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 maildrop depends on:
pn  courier-authlib  
ii  libc62.31-13+deb11u2
pn  libcourier-unicode4  
ii  libgcc-s1 [libgcc1]  10.2.1-6
ii  libgdbm6 1.19-2
ii  libpcre3 2:8.39-13
ii  libstdc++6   10.2.1-6

Versions of packages maildrop recommends:
ii  postfix [mail-transport-agent]  3.5.6-1+b1

maildrop suggests no packages.

Bug#521883: adduser: Please accept underscore prefixed system names

[Marc Haber]

Control: severity -1 important 
thanks

On Fri, Nov 25, 2016 at 09:38:12PM -0800, Afif Elghraoui wrote:
> Since considering underscore-prefixed names as a valid format for system
> user accounts does not necessarily mandate its use, I have no problem
> accepting this. The campaign for making it the resolution of #248809 is
> another matter.

Since we discussed this for the last time, Debian policy was amended to
recommend _username for newly created system accounts. This clearly
means that adduser should accept prefixed underscores for system
accounts.

In my opinion, this automatically means that normal user accounts should
not have an underscore prefix, this is especially valid for accounts
created from d-i. The local admin is of course free to ask for trouble
with adduser --force-badname, but the installer should not allow this.

The original intent of this bug report was to allow the installer to
create underscore-prefixed user accounts. For this case, my resolution
is "wontfix", but we should change the behavior for adduser --system.

I am also willing to have this bug report closed with the adduser
--system modification after so many years. If the original submitter
does still care they're invited to file a new bug.

Greetings
Marc

Bug#432562: adduser: Please accept underscore prefixed system names

[Marc Haber]

Control: severity -1 wishlist
thanks

On Fri, Nov 25, 2016 at 01:30:36AM +0100, Guillem Jover wrote:
> I also think allowing Debian-style names by default would be a bad
> idea, and I'm glad that bug is marked as wontfix. ;)

For the time being, it is going to stay wontfix, especially since
Debian's policy has been amended to recommend the underscore notation
for package-related system accounts. I am adjusting the severity
accordingly.

To allow upper case names for normal user accounts, I am still opposed
to doing this in Debian. I will consider advice from the TC should
somebody want to ask them.

Greetings
Marc

Bug#782001: access granted to /home files of another user

[Marc Haber]

Control: severity -1 important
thanks

On Sun, Sep 29, 2019 at 10:46:03AM +0200, Salvatore Bonaccorso wrote:
> Was there any progress or objections towards changing this default?

Not yet. I dont feel that this should be a local decision of adduser.
This needs consensus on debian-devel. Feel free to start that
discussion. I will try doing this myself in due time, but I would
appreciate if somebody else would do it (time limiting factors...)

Greetings
Marc

Bug#625758: 'adduser --disabled-login' does not behave as documented.

[Marc Haber]

Control: tags -1 - patch
thanks

Thanks for your work. I am removing the tag "patch" since I do not think
that this problem can be fixed as easily.

Greetings
Marc

Bug#625758: 'adduser --disabled-login' does not behave as documented.

[Marc Haber]

Control: tags -1 confirmed
thanks

On Thu, May 05, 2011 at 06:56:37PM +0100, Matthew Woodcraft wrote:
> The adduser manpage in squeeze contains the following:
> 
>--disabled-login
>   Do  not  run passwd to set the password.  The user won't be able
>   to use her account until the password is set.

This is used in 73 packages in Debian

>--disabled-password
>   Like --disabled-login, but logins are still possible (for  exam‐
>   ple using SSH RSA keys) but not using password authentication.

150 Packages in Debian use this.

We therefore must not break things for packages.

Discussion of historical UNIX behavior does not help us too much.

I would suggest making both options do the same, just not setting a
password for the newly created account, document this, and emit in the
--disabled-login case a warning that logins might still be possible for
the account. A NEWS.Debian entry is probably in order.

In the future, we might have a new option, for example
--no-set-password, and deprecate both old versions of the options.

afaics, the code path selected by adduser --system does not honor either
option anyway and just does not set a password. If this is true, this
should be documented as well. I a not sure whether we should issue a
warning if adduser --system --disabled-(password|login) is called.

Greetings
Marc

Bug#1006902: expeyes not fully ported to Python 3

[Balbir Thomas]

Package: expeyes
Version: 4.8.8+repack-2
Severity: normal

Dear Maintainer,

On running expeyes from the command line I see the following error
message

$ expeyes
Traceback (most recent call last):
  File "/usr/share/expeyes/eyes/explore.py", line 12, in 
from Tkinter import *
ModuleNotFoundError: No module named 'Tkinter'

As I understand this is because the packaged expeyes version is not
ported to Python version 3.

I am attaching patches to 
- /usr/share/expeyes/eyes/explore.py (explore.patch)
- /usr/lib/python3/dist-packages/expeyes/eyes.py (eyes.patch)

With these two patches expeyes launches successfully for me. I have not
tested all of its functionality though.

regards

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

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

Versions of packages expeyes depends on:
ii  python3  3.9.2-3
ii  python3-expeyes  4.8.8+repack-2
ii  python3-pil.imagetk  8.1.2+dfsg-0.3+deb11u1
ii  python3-tk   3.9.2-1
ii  tix  8.4.3-10+b1
ii  udev 247.3-6

Versions of packages expeyes recommends:
ii  expeyes-doc-en [expeyes-doc]  4.3-3
pn  expeyes-web   
ii  python3-numpy 1:1.19.5-1
ii  python3-pygrace   0.6-2
ii  python3-scipy 1.6.0-2
pn  qtiplot   

Versions of packages expeyes suggests:
pn  firm-phoenix-ware  

-- no debconf information
12,13c12,15
< from Tkinter import *
< import Image, ImageTk, tkFont, os, sys, commands, math
---
> from tkinter import *
> from tkinter import font
> from PIL import Image, ImageTk
> import os, sys, subprocess, math
497c499
< 	stat,out = commands.getstatusoutput('python '+ eyeplot.abs_path() + 'hwtest.py')
---
> 	stat,out = subprocess.getstatusoutput('python '+ eyeplot.abs_path() + 'hwtest.py')
563c565
< font = tkFont.Font(family = 'helvetica', size = 12)
---
> font = font.Font(family = 'helvetica', size = 12)
610c612
< 		stat,out = commands.getstatusoutput('python '+ eyeplot.abs_path() + expt+'.py')
---
> 		stat,out = subprocess.getstatusoutput('python '+ eyeplot.abs_path() + expt+'.py')
30c30
< import serial, struct, math, time, command, sys, os, glob, fnmatch
---
> import serial, struct, math, time, subprocess, sys, os, glob, fnmatch
154c154
< res = command.getoutput('lsof -t '+ str(dev))
---
> res = subprocess.getoutput('lsof -t '+ str(dev))

Bug#1006885: ITP: lumin -- pattern match highlighter

[Jonas Smedegaard]

Quoting Stephen Kitt (2022-03-07 21:44:55)
> On Mon, 07 Mar 2022 18:01:47 +0100, Jonas Smedegaard  wrote:
> > Quoting Stephen Kitt (2022-03-07 17:50:43)
> > > Package: wnpp
> > > Severity: wishlist
> > > Owner: Stephen Kitt 
> > > X-Debbugs-Cc: debian-de...@lists.debian.org
> > > 
> > > * Package name: lumin
> > >   Version : 1.0.0
> > >   Upstream Author : John Kerl
> > > * URL : https://github.com/johnkerl/lumin
> > > * License : BSD-2-clause
> > >   Programming Lang: Go
> > >   Description : pattern match highlighter
> > > 
> > > lumin highlights matches to a specified pattern (string or regular
> > > expression) in files, using color. This is similar to grep with
> > > colorized output, but it outputs all lines in the given files, not
> > > only matching lines.  
> > 
> > Is this a command-line tool or only a Go library?
> > 
> > If the latter, then please use a source package name starting with 
> > "golang-" to not needlessly occupy a short global name.
> 
> It’s both, a command-line tool and a Go library.

Ah, ok.  Makes sense, then :-)


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1006747: SIGSEGV: Click 'Update All' then 'Next Unread Item'

[Paul Gevers]

Hi Roland,

On 04-03-2022 10:23, Roland Clobus wrote:

Occasionally I'm experiencing SIGSEGV in liferea.


Thank you for this high quality bug report. I sent it upstream and there 
is already a pull request supposedly fixing the issue.


If you don't mind, I'll just wait until upstream releases a new version.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads

[Axel Beckert]

Hi Damien,

one of the affected users here.

Damien Le Moal wrote:
> In the bug report, I did not see a dmesg output for a failed boot. But I
> guess it is because the user cannot capture it.

Correct.

> Could you have a look at this bug report for Fedora:
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=215519
> 
> This Debian case does sound similar. The problem is fixed with commit:
> 
> fda17afc6166 ("ata: libata-core: Fix ata_dev_config_cpr()")
> 
> which is included in kernel 5.16.9.

Then it didn't help.

> Could the users try that kernel version to see if that fixes the
> issue ?

Both affected users already tried 5.16.11 and the issue is still
there.

Nevertheless thanks for your prompt reply and all the details so far!

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#1006901: /usr/bin/dglob: grep-dctrl: not found

[xiscu]

Package: debian-goodies
Version: 0.87
Severity: important

Dear Maintainer,

   * What led up to the situation?
Triying to use dglob

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
> dglob debian-goodies

   * What was the outcome of this action?
> dglob debian-goodies
/usr/bin/dglob: 80: grep-dctrl: not found
/usr/bin/dglob: 87: grep-dctrl: not found

   * What outcome did you expect instead?
search on installed packages names after the pattern

Notice that Iḿ able to see that the package 'dctrl-tools' exists,
but shouldn't be installed as dependecy? otherwise some of the
commands on debian-goodies just fail to work

Thanks in advance,
xiscu

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

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

debian-goodies depends on no packages.

Versions of packages debian-goodies recommends:
ii  apt2.4.0
ii  curl   7.81.0-1
pn  dctrl-tools
pn  elfutils   
pn  equivs 
pn  libfile-slurper-perl   
pn  libfile-which-perl 
pn  libipc-system-simple-perl  
ii  man-db 2.10.1-1
ii  perl   5.34.0-3
pn  popularity-contest 
ii  procps 2:3.3.17-6
ii  python33.9.8-1
ii  sensible-utils 0.0.17
ii  whiptail   0.52.21-5+b1
ii  zenity 3.41.0-2

Versions of packages debian-goodies suggests:
pn  apt-file   
ii  chromium [www-browser] 98.0.4758.102-1
ii  firefox [www-browser]  95.0.1-1
ii  firefox-esr [www-browser]  91.5.0esr-1
pn  konqueror  
ii  lsb-release11.1.0
ii  lsof   4.93.2+dfsg-1.1
ii  lynx [www-browser] 2.9.0dev.10-1
ii  openssh-client 1:8.8p1-1
ii  sudo   1.9.9-1
ii  surf [www-browser] 2.1+git20210719-1
ii  xdg-utils  1.1.3-4.1

-- no debconf information

Bug#983405: adduser: race conditions in adduser

[Marc Haber]

Control: tags -1 confirmed
Control: severity -1 normal
thanks

On Tue, Feb 23, 2021 at 12:21:56PM -0500, Brent Baccala wrote:
> Then I modified the custom service to protect the call to adduser with
> a POSIX semaphore.

Yes, adduser should lock itself against concurrent invocation.

This is probably hard to write a test-case for without having a testing
option that makes adduser sleep while the other instance is invoked.

Severity normal since this does not happen during package installations,
but only in concurrent settings.

Greetings
Marc

Bug#1006885: ITP: lumin -- pattern match highlighter

[Stephen Kitt]

Hi Jonas,

On Mon, 07 Mar 2022 18:01:47 +0100, Jonas Smedegaard  wrote:
> Quoting Stephen Kitt (2022-03-07 17:50:43)
> > Package: wnpp
> > Severity: wishlist
> > Owner: Stephen Kitt 
> > X-Debbugs-Cc: debian-de...@lists.debian.org
> > 
> > * Package name: lumin
> >   Version : 1.0.0
> >   Upstream Author : John Kerl
> > * URL : https://github.com/johnkerl/lumin
> > * License : BSD-2-clause
> >   Programming Lang: Go
> >   Description : pattern match highlighter
> > 
> > lumin highlights matches to a specified pattern (string or regular
> > expression) in files, using color. This is similar to grep with
> > colorized output, but it outputs all lines in the given files, not
> > only matching lines.  
> 
> Is this a command-line tool or only a Go library?
> 
> If the latter, then please use a source package name starting with 
> "golang-" to not needlessly occupy a short global name.

It’s both, a command-line tool and a Go library.

Regards,

Stephen


pgpFLWvDeFiqw.pgp
Description: OpenPGP digital signature

Bug#1006900: nuspell: New upstream version 5.1.0

[Dimitrij Mijoski]

Package: nuspell
Severity: wishlist
X-Debbugs-Cc: dm...@hotmail.com

Dear Maintainer,

New upstream version 5.1.0 is available for download. Please update when
you can.

Bug#1006899: crontab calls syntactically incorrect

[Marc Haber]

Package: adduser
Version: 3.118
Severity: normal
File: /usr/sbin/deluser

deluser calls crontab as "crontab -l $user". This is synctactially
incorrect and no longer accepted by current crontab. Correct would be
crontab -u $user -l.

Same goes for other operations than -l.

There should also be a test case that creates a user, installs a user
crontab, deletes the user and verifies that the crontab is actually
gone.

Greetings
Marc

Bug#1006895: should give error message if no crontab binary

[Marc Haber]

On Mon, Mar 07, 2022 at 08:35:08PM +0100, Marc Haber wrote:
> currently, an absent crontab binary is silently ignored. I think that
> deluser should give a helpful warning in that case (cf: deluser
> lines 350~).

In fact, an absent crontab binary leads to an error, crontab's presence
is not even checked. It should.

Greetings
Marc

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

Bug#940577: adduser: [SECURITY] command injection in deluser program when invoking crontab with malicious username

[Marc Haber]

Control: outlook -1 write test case, fix issue
thanks

On Tue, Sep 17, 2019 at 01:22:46PM +, Haoxi Tan wrote:
> A command injection vulnerability has been found in the deluser
> program in the adduser package.

Embarrassing. My own bug. system() should never be used with a string,
just with an array, to avoid a shell being used to execute the code. The
culprit is

if (system("crontab -l $user >/dev/null 2>&1") == 0) {

which should be rewritten to use systemcall(). Probably it would be wise
to adapt systemcall() to allow redirections.

Greetings
Marc

Bug#1006853: cups-browsed: HTTP Forbidden when adding printer with cups-browsed

[Mark Brandis]

Works! Thank you!

Bug#1006898: RFP: handlr -- application default handler

[Antoine Beaupre]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-r...@lists.debian.org

* Package name: handlr
  Version : 0.6.4
  Upstream Author : Gregory
* URL : https://github.com/chmln/handlr
* License : MIT
  Programming Lang: Rust
  Description : application default handler

Manage your default applications with ease using handlr!

Features

 * Set default handler by extension or mime-type
 * Intelligent mime type detection from files based on extension and
   content
 * Open multiple files at once
 * Set multiple handlers for mime/extension and use rofi/dmenu to pick
   one
 * Wildcard support like text/*
 * Automatically removes invalid/wrong .desktop entries from
   mimeapps.list
 * Helper commands like launch, get --json for your scripting needs
 * Unnecessarily fast (written in Rust)
 * Single compiled binary with no dependencies



As the description mentions, this overlaps with the already packages
xdg-utils, but does have interesting improvements, to quote the
upstream README:

Compared to xdg-utils

 * Can open multiple files/URLs at once
 * Can have multiple handlers and use rofi/dmenu to pick one at runtime
 * Far easier to use with simple commands like get, set, list
 * Can operate on extensions, no need to look up or remember mime types
 * useful for common tasks like setting a handler for png/docx/etc files
 * Superb autocomplete (currently fish, zsh and bash), including mimes, 
extensions, and .desktop files
 * Optional json output for scripting
 * Properly supports Terminal=true entries

Bug#1006897: deluser does not support VERBOSE

[Marc Haber]

Package: adduser
Version: 3.118
Severity: minor
File: /usr/sbin/deluser

Hi,

adduser sets the environment variable VERBOSE according to --quite and
--debug. deluser doesn't. Should it?

Greetings
Marc

Bug#1006896: RFP: firedm -- internet download manager GUI

[Antoine Beaupre]

Package: wnpp
Severity: wishlist

* Package name: firedm
  Version : 2022.2.5
  Upstream Author : https://github.com/firedm
* URL : https://github.com/firedm/FireDM
* License : LGPLv3
  Programming Lang: Python
  Description : internet download manager GUI

FireDM is a python open source (Internet Download Manager) with
multi-connections, high speed engine, it downloads general files and
videos from youtube and tons of other streaming websites .  Developed
in Python, based on "LibCurl", and "youtube_dl".

Features:

 * High download speeds "based on LibCurl"
 * Multi-connection downloading "Multithreading"
 * Automatic file segmentation.
 * Automatic refresh for dead links.
 * Resume uncompleted downloads.
 * Support for Youtube, and a lot of stream websites "using youtube-dl
   to fetch info and libcurl to download media".
 * download entire video playlist or selected videos.
 * download fragmented video streams, and encrypted/nonencrypted HLS
   media streams.
 * watch videos while downloading* "some videos will have no audio
   until finish downloading".
 * download video subtitles.
 * write video metadata to downloaded files.
 * check for application updates.
 * Scheduling downloads
 * Re-using existing connection to remote server.
 * Clipboard Monitor.
 * proxy support (http, https, socks4, and socks5).
 * user/pass authentication, referee link, use cookies, video
   thumbnail, subtitles.
 * use custom cookies files.
 * MD5 and SHA256 checksums.
 * Custom gui themes.
 * Set download Speed limit
 * User can run shell commands or shutdown computer on download
  completion.
 * Control number of Concurrent downloads and Max. connections per
   each download.



This relies on ffmpeg and youtube-dl, and seems like a nice GUI. Not
sure if we already have something like this in Debian.

Bug#1006895: should give error message if no crontab binary

[Marc Haber]

Package: adduser
Version: 3.118
Severity: minor

currently, an absent crontab binary is silently ignored. I think that
deluser should give a helpful warning in that case (cf: deluser
lines 350~).

Greetings
Marc

Bug#1004714: (no subject)

[ziegler]

Same problem here.
Thanks for the workarounds!
Martin

Bug#701110: adduser removes cloned-uid usernames, during gpasswd -M ... (get_group_members() bug)

[Marc Haber]

Control: severity -1 normal
Control: outlook -1 write test case, then apply patch
thanks

Readjusting priority since this is kind of a corner case. I am not even
convinced that having multiple user names with the same uid is a
supported or recommended configuration.

For the patch to be applied, we'd need to have a test case first.

Greetings
Marc

On Thu, Feb 21, 2013 at 06:49:33PM +0100, Daniel Heimann wrote:
> From: Daniel Heimann 
> Subject: Bug#701110: adduser removes cloned-uid usernames, during gpasswd
>  -M ... (get_group_members() bug)
> To: Debian Bug Tracking System 
> Reply-To: Daniel Heimann ,
>  701...@bugs.debian.org
> Date: Thu, 21 Feb 2013 18:49:33 +0100
> X-Mailer: reportbug 4.12.6
> 
> Package: adduser
> Version: 3.112+nmu2
> Severity: important
> Tags: patch
> 
> if adduser needs to call gpasswd -M (e.g. when adding the new user to groups,
> because of EXTRA_GROUPS in adduser.conf) it uses get_group_members() to first
> retrieve other users that have been added to the group before. It then adds
> the new user to the list and calls gpasswd with all users alltogether.
> 
> When uid-cloned systemusers (two usernames, same userid) are members of such
> a group, all but the first (as listed in passwd) get removed, due to adduser's
> wrong call to gpasswd. The reason is get_group_members() returns wrong
> @members, because getpwuid(getpwnam($_)) eq $_ does not match for cloned 
> uid's.
> Instead the first matching username (as listed in passwd) is returned by
> getpwuid which is not $_ in this case, so the uid-cloned users do not get
> pushed to @members.
> 
> get_group_members() (contained in /usr/share/perl5/Debian/AdduserCommon.pm)
> is defined as
> 
> sub get_group_members
>   {
>   my $group = shift;
>   my @members;
>   foreach (split(/ /, (getgrnam($group))[3])) {
>   if (getpwuid(getpwnam($_)) eq $_ ) {
>   push @members, $_;
>   }
>   }
>   return @members;
>   }
> 
> While searching for the reason why this is broken in Squeeze and Wheezy, but
> not Etch, I found 
> http://anonscm.debian.org/viewvc/adduser/trunk/AdduserCommon.pm?r1=646=732
> 
> It seems the getpwuid(getpwnam($_)) part was made, to prevent root from being 
> removed
> from groups (because UID 0 "failed" the if), which is nice. In order to have 
> this still
> fixed (allow root to be and stay part of groups), not break cloned-uids 
> usernames and
> still validate that processed users actually exist I'd propose the use of 
> defined, like:
> 
> sub get_group_members
>   {
>   my $group = shift;
>   my @members;
>   foreach (split(/ /, (getgrnam($group))[3])) {
>   if (defined getpwnam($_)) {
>   push @members, $_;
>   }
>   }
>   return @members;
>   }
> 
> Works for me (in all described cases).
> 
> 
> -- System Information:
> Debian Release: 6.0.6
>   APT prefers stable
>   APT policy: (500, 'stable')
> Architecture: i386 (i686)
> 
> Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
> Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15) (ignored: 
> LC_ALL set to de_DE@euro)
> Shell: /bin/sh linked to /bin/bash
> 
> Versions of packages adduser depends on:
> ii  debconf [de 1.5.36.1 Debian configuration management 
> sy
> ii  passwd  1:4.1.4.2+svn3283-2+squeeze1 change and administer password 
> and
> ii  perl-base   5.10.1-17squeeze4minimal Perl system
> 
> adduser recommends no packages.
> 
> Versions of packages adduser suggests:
> ii  liblocale-gettext-perl 1.05-6Using libc functions for 
> internati
> ii  perl-modules   5.10.1-17squeeze4 Core Perl modules
> 
> -- debconf information excluded

Bug#1006892: cups-browsed: Local queues are not created for discovered printers

[Brian Potkin]

tags 1006892 moreinfo
tags 1006892 normal
thanks.


On Mon 07 Mar 2022 at 18:32:10 +0100, Grzesiek11 wrote:

> Package: cups-browsed
> Version: 1.28.12-1
> Severity: important

[...]

> `cups-browsed` can no longer create local queues for discovered
> printers, because root (which the daemon runs as) now has no implicit
> permission in `cupsd` to do so. It is now required for root to be in
> the `lpadmin` group or to be otherwise explicitly allowed.
> 
> See https://github.com/OpenPrinting/cups/issues/306 for details

Thank you for your report, Grzesiek11.

Please look at #1006727:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006727

Does that answer your needs?

Regards,

Brian.

Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads

[Diederik de Haas]

Hi Damien,

On Sunday, 6 March 2022 23:26:03 CET Diederik de Haas wrote:
> Upstream commit 68dbbe7d5b4fde736d104cbbc9a2fce875562012 [1]
> seems potentially relevant (included in 5.16-rc1), but given ...
> 
> On Saturday, 5 March 2022 17:59:50 CET Petra R.-P. wrote:
> > The "Read log 0x00 page 0x00 failed" line has disappeared,
> 
> ... I don't know if building a new kernel with that commit reverted
> would be enough.
> 
> From the above mentioned commit message it very much seems the logic
> wrt slow drives was changed, but how exactly is 'above my pay grade'.
> The new timeout (15s) seems to work for SATA 6.0 Gbps links, but it appears
> the T41 uses PATA which I think is (quite a bit?) slower then that.

In https://bugs.debian.org/1006149 we have 2 users where the 5.16 kernel fails 
to boot, while the 5.15 kernel succeeded.
In the bug report there are a number of dmesg outputs posted which contain 
time gaps of ~ 20, 100 and even 160 seconds; i.e. more then 15 seconds.
The commit message mentions 'SATA link up 6.0 Gbps', but these users hava PATA 
links for their HDD. IIUC that means a max speed of ~600MB/s vs ~133MB/s.

As the author of the above mentioned commit, could you tell us whether it 
*could* be that your commit is causing the boot failures? Or is it completely 
irrelevant for this problem?

Cheers,
  Diederik


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

Bug#1006892: cups-browsed: Local queues are not created for discovered printers

[Till Kamppeter]

Probably cause by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006853

   Till

Bug#1006894: ganglia-webfrontend: incorrect file permissions in /var/lib/ganglia-web/conf/

[Jochen Kellner]

Package: ganglia-webfrontend
Version: 3.7.5+debian-3
Severity: normal

Dear Maintainer,

There are two errors in setting up ganglia due to incorrect
file permissions.  I've removed the package, checked that
the files were gone. After new installation the permissions
were again wrong.

1. In a host view click on the "+" above one of the graphs.
   Select "default" as the view to add the graph to.
   I get the following message:
   Alert: Can't write to file: "/var/lib/ganglia-web/conf/view_default.json". 
Perhaps permissions are wrong.
   The file is not updated.

2. In the "Events" tab press "Add event". Fill in the fields and
   after pressing "Add" I get the message:
   {"status":"error","message":"Can't write to 
\/var\/lib\/ganglia-web\/conf\/events.json. Please check permissions."}

Ganglia-webfrontend runs as www-data, but there are files owned by root
in /var/lib/ganglia-web/conf.

root@example:/usr/share/ganglia-webfrontend# ls -l /var/lib/ganglia-web/conf/
insgesamt 52
-rw-r--r-- 1 root root84 21. Mär 2019  default.json
-rw-r--r-- 1 root root 3 21. Mär 2019  event_color.json
-rw-r--r-- 1 root root 3 21. Mär 2019  events.json
-rw-r--r-- 1 www-data www-data 14869  6. Mär 23:09 ganglia_metrics.cache
-rw-r--r-- 1 www-data www-data   442  6. Mär 23:09 
ganglia_metrics.cache_cluster_data
-rw-r--r-- 1 www-data www-data   250  6. Mär 23:09 
ganglia_metrics.cache_host_list
-rw-r--r-- 1 www-data www-data  3247  6. Mär 23:09 
ganglia_metrics.cache_metric_list
drwxr-xr-x 2 root root  4096  7. Mär 18:28 sql
-rw-r--r-- 1 www-data www-data   442 30. Dez 2016  view_Bacula_Volumes.json
-rw-r--r-- 1 root root58 21. Mär 2019  view_default.json

Changing the file owner/group to www-data:www-data fixes the errors for me.


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

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

Versions of packages ganglia-webfrontend depends on:
ii  apache2 [httpd-cgi] 2.4.52-1~deb11u2
ii  debconf [debconf-2.0]   1.5.77
ii  libapache2-mod-php  2:8.1+92+0~20220117.43+debian11~1.gbpe0d14e
ii  libapache2-mod-php7.4 [libapac  7.4.28-1+deb11u1
ii  libapache2-mod-php8.1 [libapac  8.1.3-1+0~20220223.13+debian11~1.gbp7757b9
ii  libjs-chosen1.8.7+dfsg-2
ii  libjs-d33.5.17-4
ii  libjs-jquery3.5.1+dfsg+~3.5.5-7
ii  libjs-jquery-cookie 12-3
ii  libjs-jquery-flot   4.2.1+dfsg-5
ii  libjs-jquery-jstree 3.3.11+dfsg1-1
ii  libjs-jquery-mobile 1.4.5+dfsg-1
ii  libjs-jquery-scrollto   2.1.2+dfsg-6
ii  libjs-jquery-ui 1.12.1+dfsg-8+deb11u1
ii  libjs-jstimezonedetect  1.0.6-5
ii  libjs-moment2.29.1+ds-2
ii  libjs-moment-timezone   0.5.32+dfsg1-2+2021a
ii  libjs-rickshaw  1.5.1.dfsg-4
ii  libjs-select2.js4.0.13+dfsg1-4
ii  php 2:8.1+92+0~20220117.43+debian11~1.gbpe0d14e
ii  php-xml 2:8.1+92+0~20220117.43+debian11~1.gbpe0d14e
ii  php7.4 [php]7.4.28-1+deb11u1
ii  php7.4-xml [php-xml]7.4.28-1+deb11u1
ii  php8.1 [php]8.1.3-1+0~20220223.13+debian11~1.gbp7757b9
ii  php8.1-xml [php-xml]8.1.3-1+0~20220223.13+debian11~1.gbp7757b9
ii  rrdtool 1.7.2-3+b7

Versions of packages ganglia-webfrontend recommends:
ii  gmetad  3.7.2-4
ii  php-gd  2:8.1+92+0~20220117.43+debian11~1.gbpe0d14e
ii  php7.4-gd [php-gd]  7.4.28-1+deb11u1
ii  php8.1-gd [php-gd]  8.1.3-1+0~20220223.13+debian11~1.gbp7757b9

ganglia-webfrontend suggests no packages.

-- debconf information excluded

Bug#1000788:

[Damon Lynch]

This bug does not appear to be fixed.

To enable CR3 support, the library should be built with an additional
build option:
-DEXIV2_ENABLE_BMFF=0

See: https://github.com/Exiv2/exiv2/issues/1679#issuecomment-846389046

Bug#1006893: src:golang-github-komkom-toml: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: golang-github-komkom-toml
Version: 0.0~git20210303.132fb38-2
Severity: serious
Control: close -1 0.0~git20211215.3c8ee9d-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1004048

Dear maintainer(s),

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


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1006892: cups-browsed: Local queues are not created for discovered printers

[Grzesiek11]

Package: cups-browsed
Version: 1.28.12-1
Severity: important

Dear Maintainer,

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

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

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

`cups-browsed` can no longer create local queues for discovered printers, 
because root (which the daemon runs as)
now has no implicit permission in `cupsd` to do so. It is now required for root 
to be in the `lpadmin` group or
to be otherwise explicitly allowed.

See https://github.com/OpenPrinting/cups/issues/306 for details.

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

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

Versions of packages cups-browsed depends on:
ii  cups-daemon  2.4.1op1-1
ii  init-system-helpers  1.62
ii  libavahi-client3 0.8-5
ii  libavahi-common3 0.8-5
ii  libavahi-glib1   0.8-5
ii  libc62.33-7
ii  libcups2 2.4.1op1-1
ii  libcupsfilters1  1.28.12-1
ii  libglib2.0-0 2.70.4-1
ii  libldap-2.4-22.4.59+dfsg-1+b1
ii  lsb-base 11.1.0

Versions of packages cups-browsed recommends:
ii  avahi-daemon  0.8-5

cups-browsed suggests no packages.

-- no debconf information

Bug#549655: ganglia-webfrontend: The script pie.php creates wrong pie charts.

[Jochen Kellner]

Package: ganglia-webfrontend
Followup-For: Bug #549655

Dear Maintainer,

I still can't reproduce the bug. I agree that the bug should be closed.

Jochen

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

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

Versions of packages ganglia-webfrontend depends on:
ii  apache2 [httpd-cgi] 2.4.52-1~deb11u2
ii  debconf [debconf-2.0]   1.5.77
ii  libapache2-mod-php  2:8.1+92+0~20220117.43+debian11~1.gbpe0d14e
ii  libapache2-mod-php7.4 [libapac  7.4.28-1+deb11u1
ii  libapache2-mod-php8.1 [libapac  8.1.3-1+0~20220223.13+debian11~1.gbp7757b9
ii  libjs-chosen1.8.7+dfsg-2
ii  libjs-d33.5.17-4
ii  libjs-jquery3.5.1+dfsg+~3.5.5-7
ii  libjs-jquery-cookie 12-3
ii  libjs-jquery-flot   4.2.1+dfsg-5
ii  libjs-jquery-jstree 3.3.11+dfsg1-1
ii  libjs-jquery-mobile 1.4.5+dfsg-1
ii  libjs-jquery-scrollto   2.1.2+dfsg-6
ii  libjs-jquery-ui 1.12.1+dfsg-8+deb11u1
ii  libjs-jstimezonedetect  1.0.6-5
ii  libjs-moment2.29.1+ds-2
ii  libjs-moment-timezone   0.5.32+dfsg1-2+2021a
ii  libjs-rickshaw  1.5.1.dfsg-4
ii  libjs-select2.js4.0.13+dfsg1-4
ii  php 2:8.1+92+0~20220117.43+debian11~1.gbpe0d14e
ii  php-xml 2:8.1+92+0~20220117.43+debian11~1.gbpe0d14e
ii  php7.4 [php]7.4.28-1+deb11u1
ii  php7.4-xml [php-xml]7.4.28-1+deb11u1
ii  php8.1 [php]8.1.3-1+0~20220223.13+debian11~1.gbp7757b9
ii  php8.1-xml [php-xml]8.1.3-1+0~20220223.13+debian11~1.gbp7757b9
ii  rrdtool 1.7.2-3+b7

Versions of packages ganglia-webfrontend recommends:
ii  gmetad  3.7.2-4
ii  php-gd  2:8.1+92+0~20220117.43+debian11~1.gbpe0d14e
ii  php7.4-gd [php-gd]  7.4.28-1+deb11u1
ii  php8.1-gd [php-gd]  8.1.3-1+0~20220223.13+debian11~1.gbp7757b9

ganglia-webfrontend suggests no packages.

-- debconf information excluded

Bug#1006846: [Pkg-matrix-maintainers] Bug#1006846: matrix-mirage: Upstream unmaintained ? Switch to fork ?

[Jonas Smedegaard]

Hi Karl,

Quoting Karl Kashofer (2022-03-06 20:02:36)
> Dear Maintainer,
> 
> I use matrix-mirage on Pinephone Mobian. 
> It seems matrix-mirage upstream is unmaintained.
> 
> Apparently there is a maintained fork at
> https://mx-moment.xyz/
> with sources at
> https://gitlab.com/mx-moment/moment
> 
> Could you maybe provide a Moment package for debian ?
> Or switch upstream ?

Thanks for raising concern.

I am aware that matrix-mirage is far from a firehose of changes, and 
also that it is not perfect.  I am not aware that it is unmaintained, 
though.  Are you aware of any other indicators for that than simply the 
timestamp of newest upstream git commit?

Nice that someone has invested time in a fork of matrix-mirage.  Looking 
closely at it, most of the changes are so far tied to the very forking 
process, however - I don't see any substantial improvements.

I suggest to file an RFP bugreport and post news about upstream progress 
to that other bugreport, to encourage me and others to have a renewed 
look at its packaging for Debian.

Unless I receive substantial information that matrix-mirage should be 
dropped from Debian, I will close this bugreport.


Thanks,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#878066: ganglia-webfrontend: not compatible with PHP 7

[Jochen Kellner]

Package: ganglia-webfrontend
Followup-For: Bug #878066

Dear Maintainer,

the bug report talks about two needed changes:
1. 
https://github.com/ganglia/ganglia-web/commit/c5e5831d23c6db0b04a868578680b32cb03ee952#diff-6e9d3d41e5bc04968be8f28e0b6f7a1a
   -  list( $_cluster, $_host ) = split( '/', $v );
   +  list( $_cluster, $_host ) = str_split( '/', $v );
2. 
https://github.com/ganglia/ganglia-web/commit/13d426bcf66fb0f27d44847154ba2180884edcd6
   -  $context_metrics = "";
   +  $context_metrics = array();

Both changes are in 3.7.5+debian-3, so I suggest to finally close the bug.

Thanks,
Jochen

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

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

Versions of packages ganglia-webfrontend depends on:
ii  apache2 [httpd-cgi] 2.4.52-1~deb11u2
ii  debconf [debconf-2.0]   1.5.77
ii  libapache2-mod-php  2:8.1+92+0~20220117.43+debian11~1.gbpe0d14e
ii  libapache2-mod-php7.4 [libapac  7.4.28-1+deb11u1
ii  libapache2-mod-php8.1 [libapac  8.1.3-1+0~20220223.13+debian11~1.gbp7757b9
ii  libjs-chosen1.8.7+dfsg-2
ii  libjs-d33.5.17-4
ii  libjs-jquery3.5.1+dfsg+~3.5.5-7
ii  libjs-jquery-cookie 12-3
ii  libjs-jquery-flot   4.2.1+dfsg-5
ii  libjs-jquery-jstree 3.3.11+dfsg1-1
ii  libjs-jquery-mobile 1.4.5+dfsg-1
ii  libjs-jquery-scrollto   2.1.2+dfsg-6
ii  libjs-jquery-ui 1.12.1+dfsg-8+deb11u1
ii  libjs-jstimezonedetect  1.0.6-5
ii  libjs-moment2.29.1+ds-2
ii  libjs-moment-timezone   0.5.32+dfsg1-2+2021a
ii  libjs-rickshaw  1.5.1.dfsg-4
ii  libjs-select2.js4.0.13+dfsg1-4
ii  php 2:8.1+92+0~20220117.43+debian11~1.gbpe0d14e
ii  php-xml 2:8.1+92+0~20220117.43+debian11~1.gbpe0d14e
ii  php7.4 [php]7.4.28-1+deb11u1
ii  php7.4-xml [php-xml]7.4.28-1+deb11u1
ii  php8.1 [php]8.1.3-1+0~20220223.13+debian11~1.gbp7757b9
ii  php8.1-xml [php-xml]8.1.3-1+0~20220223.13+debian11~1.gbp7757b9
ii  rrdtool 1.7.2-3+b7

Versions of packages ganglia-webfrontend recommends:
ii  gmetad  3.7.2-4
ii  php-gd  2:8.1+92+0~20220117.43+debian11~1.gbpe0d14e
ii  php7.4-gd [php-gd]  7.4.28-1+deb11u1
ii  php8.1-gd [php-gd]  8.1.3-1+0~20220223.13+debian11~1.gbp7757b9

ganglia-webfrontend suggests no packages.

-- debconf information excluded

Bug#893879: "Inspect" graph broken

[Jochen Kellner]

Package: ganglia-webfrontend
Followup-For: Bug #893879

Dear Maintainer,

inspect works for me too. I agree that the bug should be closed.

Jochen

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

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

Versions of packages ganglia-webfrontend depends on:
ii  apache2 [httpd-cgi] 2.4.52-1~deb11u2
ii  debconf [debconf-2.0]   1.5.77
ii  libapache2-mod-php  2:8.1+92+0~20220117.43+debian11~1.gbpe0d14e
ii  libapache2-mod-php7.4 [libapac  7.4.28-1+deb11u1
ii  libapache2-mod-php8.1 [libapac  8.1.3-1+0~20220223.13+debian11~1.gbp7757b9
ii  libjs-chosen1.8.7+dfsg-2
ii  libjs-d33.5.17-4
ii  libjs-jquery3.5.1+dfsg+~3.5.5-7
ii  libjs-jquery-cookie 12-3
ii  libjs-jquery-flot   4.2.1+dfsg-5
ii  libjs-jquery-jstree 3.3.11+dfsg1-1
ii  libjs-jquery-mobile 1.4.5+dfsg-1
ii  libjs-jquery-scrollto   2.1.2+dfsg-6
ii  libjs-jquery-ui 1.12.1+dfsg-8+deb11u1
ii  libjs-jstimezonedetect  1.0.6-5
ii  libjs-moment2.29.1+ds-2
ii  libjs-moment-timezone   0.5.32+dfsg1-2+2021a
ii  libjs-rickshaw  1.5.1.dfsg-4
ii  libjs-select2.js4.0.13+dfsg1-4
ii  php 2:8.1+92+0~20220117.43+debian11~1.gbpe0d14e
ii  php-xml 2:8.1+92+0~20220117.43+debian11~1.gbpe0d14e
ii  php7.4 [php]7.4.28-1+deb11u1
ii  php7.4-xml [php-xml]7.4.28-1+deb11u1
ii  php8.1 [php]8.1.3-1+0~20220223.13+debian11~1.gbp7757b9
ii  php8.1-xml [php-xml]8.1.3-1+0~20220223.13+debian11~1.gbp7757b9
ii  rrdtool 1.7.2-3+b7

Versions of packages ganglia-webfrontend recommends:
ii  gmetad  3.7.2-4
ii  php-gd  2:8.1+92+0~20220117.43+debian11~1.gbpe0d14e
ii  php7.4-gd [php-gd]  7.4.28-1+deb11u1
ii  php8.1-gd [php-gd]  8.1.3-1+0~20220223.13+debian11~1.gbp7757b9

ganglia-webfrontend suggests no packages.

-- debconf information excluded

Bug#1006891: src:nuitka: fails to migrate to testing for too long: unresolved RC bug

[Paul Gevers]

Source: nuitka
Version: 0.6.17.2+ds-1.1
Severity: serious
Control: close -1 0.6.19.1+ds-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1006051

Dear maintainer(s),

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


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1006616: firefox: new upstream version

[Christoph Anton Mitterer]

On Wed, 2022-03-02 at 03:13 -0300, Leandro Cunha wrote:
> Firefox in bookworm/testing is ESR version only.

Well sure... but I guess not few people (probably including DDs/DMs)
are using FF non-ESR on their systems.

The recent minor release contains further critical issues, which are
apparently already actively attacked.


> It's having a problem and logs can be accessed through the link
> below.
> https://buildd.debian.org/status/package.php?p=firefox=sid

Isn't it "just" the current rust version that's missing?

Would it be feasible to backport the fixes for the most grave holes?


Thanks,
Chris.

Bug#1006890: missing libio-string-perl dependency

[Matus UHLAR - fantomas]

Package: spamassassin
Version: 3.4.6-1

Hello,

package spamassassin plugin OLEVBMacro requires debian package libio-string-perl
otherwise checks fail with message:

Mar  7 19:17:05.217 [25340] dbg: OLEVBMacro: Found zip attachment with name 
attachments 1635049.zip
Mar  7 19:17:05.217 [25340] dbg: message: decoding base64
Mar  7 19:17:05.218 [25340] warn: rules: failed to run L_OLEMACRO_ZIP_PW test, 
skipping:
Mar  7 19:17:05.218 [25340] warn:  (Can't locate object method "new" via package 
"IO: [...]:String" at /usr/share/perl5/Mail/SpamAssassin/Plugin/OLEVBMacro.pm line 758.
Mar  7 19:17:05.218 [25340] warn: )

thanks

--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
"One World. One Web. One Program." - Microsoft promotional advertisement
"Ein Volk, ein Reich, ein Fuhrer!" - Adolf Hitler

Bug#1006887: cinnamon: Missing dependency on psmisc (cinnamon-launcher uses killall)

[Martin Simmons]

Package: cinnamon
Version: 4.8.6-2
Severity: normal

Dear Maintainer,

/usr/bin/cinnamon-launcher tries to run killall, but this is only available
when the psmisc package is installed.

Normally psmisc is installed by other dependencies, but I noticed this while
testing a minimal live CD.

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

Kernel: Linux 5.10.0-11-686 (SMP w/1 CPU thread)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cinnamon depends on:
ii  cinnamon-common  4.8.6-2
ii  cinnamon-control-center  4.8.2-1
ii  cinnamon-desktop-data4.8.1-2
ii  cinnamon-screensaver 4.8.1-3
ii  cinnamon-session 4.8.0-3
ii  cinnamon-settings-daemon 4.8.5-1
ii  cjs  4.8.2-1
ii  cups-pk-helper   0.2.6-1+b1
ii  dbus 1.12.20-2
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-2
ii  gir1.2-accountsservice-1.0   0.6.55-3
ii  gir1.2-caribou-1.0   0.4.21-7.1
ii  gir1.2-clutter-1.0   1.26.4+dfsg-2
ii  gir1.2-cmenu-3.0 4.8.3-1
ii  gir1.2-cogl-1.0  1.22.8-2
ii  gir1.2-cvc-1.0   4.8.1-2
ii  gir1.2-gdkpixbuf-2.0 2.42.2+dfsg-1
ii  gir1.2-gkbd-3.0  3.26.1-1
ii  gir1.2-glib-2.0  1.66.1-1+b1
ii  gir1.2-gnomedesktop-3.0  3.38.5-3
ii  gir1.2-gtk-3.0   3.24.24-4
ii  gir1.2-gtkclutter-1.01.8.4-4
ii  gir1.2-keybinder-3.0 0.3.2-1.1
ii  gir1.2-nemo-3.0  4.8.6-2
ii  gir1.2-nm-1.01.30.0-2
ii  gir1.2-nma-1.0   1.8.30-1
ii  gir1.2-notify-0.70.7.9-3
ii  gir1.2-pango-1.0 1.46.2-3
ii  gir1.2-polkit-1.00.105-31+deb11u1
ii  gir1.2-soup-2.4  2.72.0-2
ii  gir1.2-timezonemap-1.0   0.4.6-2
ii  gir1.2-upowerglib-1.00.99.11-2
ii  gir1.2-xapp-1.0  2.0.7-1
ii  gkbd-capplet 3.26.1-1
ii  gnome-backgrounds3.38.0-1
ii  gnome-themes-extra   3.28-1
ii  gsettings-desktop-schemas3.38.0-2
ii  iso-flags-png-320x2401.0.2-1.1
ii  libatk-bridge2.0-0   2.38.0-1
ii  libatk1.0-0  2.36.0-2
ii  libc62.31-13+deb11u2
ii  libcairo21.16.0-5
ii  libcinnamon-desktop4 4.8.1-2
ii  libcinnamon-menu-3-0 4.8.3-1
ii  libcjs0  4.8.2-1
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libgirepository-1.0-11.66.1-1+b1
ii  libgl1   1.3.2-1
ii  libglib2.0-0 2.66.8-1
ii  libglib2.0-bin   2.66.8-1
ii  libgstreamer1.0-01.18.4-2.1
ii  libgtk-3-0   3.24.24-4
ii  libmuffin0   4.8.1-1
ii  libpango-1.0-0   1.46.2-3
ii  libpangocairo-1.0-0  1.46.2-3
ii  libstartup-notification0 0.12-6+b1
ii  libx11-6 2:1.7.2-1
ii  libxfixes3   1:5.0.3-2
ii  libxml2  2.9.10+dfsg-6.7
ii  mesa-utils   8.4.0-1+b1
ii  muffin   4.8.1-1
ii  nemo 4.8.6-2
ii  network-manager-gnome1.20.0-3
ii  policykit-1-gnome0.105-7
ii  python3  3.9.2-3
ii  python3-dbus 1.2.16-5
ii  python3-distro   1.5.0-1
ii  python3-gi   3.38.0-2
ii  python3-gi-cairo 3.38.0-2
ii  python3-pampy1.8.4-2
ii  python3-pexpect  4.8.0-2
ii  python3-pil  8.1.2+dfsg-0.3+deb11u1
ii  python3-pyinotify   

Bug#1006870: sdl12-compat: please make the build reproducible

[Simon McVittie]

Control: tags -1 - patch

On Mon, 07 Mar 2022 at 08:11:51 +, Chris Lamb wrote:
> Instead of not calling dh_fixperms at all, a patch is attached that
> lets it run as usual but then removes the executable bits.

I don't think this is correct either: the executables need to be
executable, and the test data needs to be non-executable. I'll do that
next time I look at this package.

smcv

Bug#1006886: ITP: gocc -- Go lexer and parser generator

[Stephen Kitt]

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

* Package name: gocc
  Version : 0.0~git20211213.7ea6993
  Upstream Author : Marius Ackerman 
* URL : https://github.com/goccmack/gocc
* License : ASL-2.0
  Programming Lang: Go
  Description : Go lexer and parser generator

Gocc generates lexer-parser pairs or stand-alone DFAs or parsers from
a Backus-Naur form (BNF). The generated lexers are deterministic
finite automata (DFAs), recognising regular languages. The generated
parsers are pushdown automata (PDAs), recognising LR(1) languages.
Optional LR(1) conflict handling automatically resolves shift/reduce
and reduce/reduce conflicts.



This is a new dependency of Miller 6.1.0.

Bug#1006553: btrfs-progs: integration with util-linux fsck

[Adam Borowski]

On Thu, Mar 03, 2022 at 07:47:37AM +0200, Martin-Éric Racine wrote:
> On Thu, Mar 3, 2022 at 5:49 AM Adam Borowski  wrote:
> >
> > On Sun, Feb 27, 2022 at 08:32:17PM +0200, Martin-Éric Racine wrote:
> > > As per the enclosed screenshot, btrfs-progs splatters its filesystem
> > > checking message all over the place.  It would be desirable to integrate
> > > it with the util-linux fsck run that follows.

> > btrfs, like all modern filesystems except for ext4, doesn't run fsck at
> > mount time at all. [...]

> It would be a good idea to actually read the bug report before replying.
> 
> Your reply doesn't address the issue AT ALL. It addresses an entirely
> different matter.

... but there's no filesystem checking here.  So what do you suggest
integrating with?

The only message related to btrfs on your screenshot is "Scanning for Btrfs
filesystems", which does nothing fsck related.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁'Russkiy voyennyi korabl, idi nakhuy'
⢿⡄⠘⠷⠚⠋⠀
⠈⠳⣄

Bug#1006885: ITP: lumin -- pattern match highlighter

[Jonas Smedegaard]

Quoting Stephen Kitt (2022-03-07 17:50:43)
> Package: wnpp
> Severity: wishlist
> Owner: Stephen Kitt 
> X-Debbugs-Cc: debian-de...@lists.debian.org
> 
> * Package name: lumin
>   Version : 1.0.0
>   Upstream Author : John Kerl
> * URL : https://github.com/johnkerl/lumin
> * License : BSD-2-clause
>   Programming Lang: Go
>   Description : pattern match highlighter
> 
> lumin highlights matches to a specified pattern (string or regular
> expression) in files, using color. This is similar to grep with
> colorized output, but it outputs all lines in the given files, not
> only matching lines.

Is this a command-line tool or only a Go library?

If the latter, then please use a source package name starting with 
"golang-" to not needlessly occupy a short global name.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1006885: ITP: lumin -- pattern match highlighter

[Stephen Kitt]

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

* Package name: lumin
  Version : 1.0.0
  Upstream Author : John Kerl
* URL : https://github.com/johnkerl/lumin
* License : BSD-2-clause
  Programming Lang: Go
  Description : pattern match highlighter

lumin highlights matches to a specified pattern (string or regular
expression) in files, using color. This is similar to grep with
colorized output, but it outputs all lines in the given files, not
only matching lines.



This is a new dependency of Miller 6.1.0.

Bug#1006744: open-vm-tools core dump on debian 10

[Bernd Zeimetz]

Hi,


Core file was generated and below is the segmentation fault
information from core dump file:

Using host libthread_db library
"/usr/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/vmtoolsd'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65
65 ../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or
directory.


is that the full backtrace? Please install the debug packages and get 
the backtrace from all threads from the core file.


(gdb) where
(gdb) thread apply all bt

Thanks,

Bernd

--
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Bug#1006384: closed by Debian FTP Masters (reply to Olivier Sallou ) (Bug#1006384: fixed in logol 1.7.9+dfsg-2)

[dogsleg]

Hi,

Paul Gevers писал 2022-03-06 21:36:
> Hi Lev,
> 
> On 06-03-2022 11:30, dogs...@riseup.net wrote:
>> As I can see, there is only one reverse build-dependency on swi-prolog
>> apart from eye and logol, that is ppl. It is a C++ library providing
>> SWI-Prolog interface. I tried to build it against swi-prolog from
>> unstable on amd64 porterbox and the build was successful (including
>> tests, which are unfortunately not autopkgtest-ready).
> 
> Is this enough to say the ABI change doesn't effect ppl?

I'm not sure whether ppl depends and/or somehow uses some particular
swi-prolog ABI, I tried to run tests from ppl source package with
ppl and swi-prolog binary packages installed (from unstable), but
with no success. I just don't know right now how to run them
correctly (these are C++ source code, as far as I can tell). So,
CCing uploaders of ppl.

Tobias, Michael, is it possible that ABI changes in swi-prolog may
break binaries of ppl in unstable? How can we test it? As quoted
above, I already tried to build ppl against the newest swi-prolog
in unstable, and ppl was built successfully.

Regards,
Lev

Bug#955479: InspIRCd package AppArmor issues

[Sadie Powell]

It seems like Debian are not shipping the AppArmor file that the InspIRCd build 
system generates and instead are shipping an incomplete custom one.

This problem can be fixed by using the AppArmor file that InspIRCd generates 
and installs to the script directory (named "apparmor").

Bug#1006884: libseccomp-dev: Cannot install libseccomp-dev using apt

[Guillaume Bouvier]

Package: libseccomp-dev
Version: 2.5.1-1
Severity: important
Tags: a11y
X-Debbugs-Cc: bougui...@gmail.com

Dear Maintainer,

I tried to install libseccomp-dev using apt with the following command:

sudo apt install libseccomp-dev

The output is the following:

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Suggested packages:
  seccomp
The following NEW packages will be installed:
  libseccomp-dev
0 upgraded, 1 newly installed, 0 to remove and 84 not upgraded.
Need to get 92.1 kB of archives.
After this operation, 439 kB of additional disk space will be used.
Err:1 http://ftp.fr.debian.org/debian bullseye/main amd64 libseccomp-dev 
amd64 2.5.1-1
  404  Not Found [IP: 212.27.32.66 80]
E: Failed to fetch 
http://ftp.fr.debian.org/debian/pool/main/libs/libseccomp/libseccomp-dev_2.5.1-1_amd64.deb
  404  Not Found [IP: 212.27.32.66 80]
E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

I ran apt-get update before without and with the --fix-missing option,
but it didn't solve the problem.
Looking at http://ftp.fr.debian.org/debian/pool/main/libs/libseccomp/,
it seems that libseccomp-dev_2.5.1-1_amd64.deb is not present.

Thanks for the help,

Best regards,
Guillaume


-- System Information:
Debian Release: 11.0
  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-8-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libseccomp-dev depends on:
ii  libseccomp2  2.5.1-1

libseccomp-dev recommends no packages.

Versions of packages libseccomp-dev suggests:
pn  seccomp  

Bug#958427: libsrtp2: FTBFS on x32: bogus printf with time_t, then segfaults [regression]

[Laurent Bigonville]

found 958427 2.4.2-3
thanks

So apparently the patch proposed here was not enough and the test is 
crashing :/


Thorsten do you think you could have a look?

Bug#988333: [Pkg-xen-devel] Bug#988333: libxenmisc4.16: libxl fails to grant necessary I/O memory access for gfx_passthru of Intel IGD

[Marek Marczykowski-Górecki]

On Mon, Mar 07, 2022 at 10:11:29AM -0500, Chuck Zmudzinski wrote:
> Detailed description of how I discovered the patch that fixes the bug and
> enables Intel IGD passthrough to Bullseye when using the traditional Qemu
> device model:
> 
> A long time ago, during the development of Xen 4.5 in 2014, two patches
> implemented a change to the way permission is granted for an unprivileged
> domain to access PCI/VGA-related I/O memory. Prior to this, AFAICT,
> permission was implicitly granted to access the memory the domain requested
> when a PCI device being passed to the domain was being configured. After the
> change, permission to access such memory is not granted without prior
> explicit permission being configured, and this is still the current
> behavior.
> 
> The relevant patches are:
> 
> 1. 
> https://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=abfb006f1ff4af1424e5b0d0589f0226377fda36
> 
> and
> 
> 2. 
> https://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=0561e1f01e87b777bcc47971e4ae1f420314f4a0
> 
> The first of these patches intended to implement explicit granting of
> permission to access the I/O memory that is needed to support the
> gfx_passthru feature in libxl_pci.c, in the
> libxl__grant_vga_iomem_permission function. The second patch implements the
> removal of implicit permission to access the PCI/VGA-related I/O memory and
> causes requests to access such memory by a domain to be denied unless prior
> explicit permission has been configured.
> 
> Specifically, the first patch adds 32 (0x20) units (I presume bytes) of data

That's in pages.

> starting at memory address 0xa >> XC_PAGE_SHIFT to the memory the domain
> is permitted to access. XC_PAGE_SHIFT is 12, so this memory range shows up
> in the logs when running Xen 4.5 as:
> 
> memory_map:add: dom1 gfn=a0 mfn=a0 nr=20
> 
> But my testing of these old patches with added custom logging shows that
> another two units (bytes?) are needed:
> 
> memory_map:access not permitted: dom1 gfn=fdffc mfn=cc490 nr=2

You may be interested in this patch:
https://github.com/QubesOS/qubes-vmm-xen/blob/xen-4.14/patch-fix-igd-passthrough-with-linux-stubdomain.patch

Qubes OS uses qemu-upstream in a Linux-based stubdomain, and with the
above patch applied, IGD passthrough works, at least to a Linux HVM.

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab


signature.asc
Description: PGP signature

Bug#1006883: bullseye-pu: package python2-pip/20.3.4-4+deb11u1

[Stefano Rivera]

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

[ Reason ]
There is a race-condition in pip querying metadata from PyPI in
parallel, e.g. for "pip list --outdated". I suspect upstream never saw
it because we were using zipimports for pip's dependencies, where they
vendor them.

The race-condition seems to be specific to their home-grown parallel
map() implementation, that has later been replaced by Python's native
map().

[ Impact ]
pip list --outdated can fail with a very obscure traceback. See
#1006150.

[ Tests ]
Manually reproduced the race, fairly frequently.
With this patch I haven't seen the race again.

[ Risks ]
Trivial change, following something upstream did in a later version,
when dropping support for older Python releases.

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

[ Changes ]
Use Python's native map() instead of pip's home-grown map_multithread().

[ Other info ]
N/A
diff -Nru python-pip-20.3.4/debian/changelog python-pip-20.3.4/debian/changelog
--- python-pip-20.3.4/debian/changelog  2021-07-01 16:44:29.0 -0400
+++ python-pip-20.3.4/debian/changelog  2022-03-07 11:19:24.0 -0400
@@ -1,3 +1,10 @@
+python-pip (20.3.4-4+deb11u1) bullseye; urgency=medium
+
+  * Use native map() to avoid a zipimport race in pip list --outdated.
+(Closes: #1006150)
+
+ -- Stefano Rivera   Mon, 07 Mar 2022 11:19:24 -0400
+
 python-pip (20.3.4-4) unstable; urgency=medium
 
   * No-change upload against distlib 0.3.2+really+0.3.1-0.1.
diff -Nru python-pip-20.3.4/debian/patches/native-map.patch 
python-pip-20.3.4/debian/patches/native-map.patch
--- python-pip-20.3.4/debian/patches/native-map.patch   1969-12-31 
20:00:00.0 -0400
+++ python-pip-20.3.4/debian/patches/native-map.patch   2022-03-07 
11:19:24.0 -0400
@@ -0,0 +1,33 @@
+From: Stefano Rivera 
+Date: Mon, 7 Mar 2022 11:17:31 -0400
+Subject: Use native map() instead of map_multithread()
+
+Avoids a race-condition when using zip-imported dependencies.
+
+Origin: upstream, 
https://github.com/pypa/pip/commit/0252c04a16cd93fe422cebf0b48453b559a2e404
+Bug-Debian: https://bugs.debian.org/1006150
+---
+ src/pip/_internal/commands/list.py | 3 +--
+ 1 file changed, 1 insertion(+), 2 deletions(-)
+
+diff --git a/src/pip/_internal/commands/list.py 
b/src/pip/_internal/commands/list.py
+index 10720b2..8e63eea 100644
+--- a/src/pip/_internal/commands/list.py
 b/src/pip/_internal/commands/list.py
+@@ -20,7 +20,6 @@ from pip._internal.utils.misc import (
+ write_output,
+ )
+ from pip._internal.utils.packaging import get_installer
+-from pip._internal.utils.parallel import map_multithread
+ from pip._internal.utils.typing import MYPY_CHECK_RUNNING
+ 
+ if MYPY_CHECK_RUNNING:
+@@ -234,7 +233,7 @@ class ListCommand(IndexGroupCommand):
+ dist.latest_filetype = typ
+ return dist
+ 
+-for dist in map_multithread(latest_info, packages):
++for dist in map(latest_info, packages):
+ if dist is not None:
+ yield dist
+ 
diff -Nru python-pip-20.3.4/debian/patches/series 
python-pip-20.3.4/debian/patches/series
--- python-pip-20.3.4/debian/patches/series 2021-07-01 16:44:29.0 
-0400
+++ python-pip-20.3.4/debian/patches/series 2022-03-07 11:19:24.0 
-0400
@@ -10,3 +10,4 @@
 debug-command-for-unbundled.patch
 str-version.patch
 git-split-ascii.patch
+native-map.patch

Bug#1006882: podman fails to install - unable to open podman.socket.dpkg-new

[Martin Hradil]

Package: podman
Version: 4.0.1+ds1-3
Severity: normal
X-Debbugs-Cc: him...@gmail.com

Dear Maintainer,

when upgrading podman from 4.0.1+ds1-1 to 4.0.1+ds1-3, install failed.
Purging podman and trying to install again gives me the same error:

Unpacking podman (4.0.1+ds1-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/podman_4.0.1+ds1-3_amd64.deb (--unpack):
 unable to open '/usr/lib/systemd/user/podman.socket.dpkg-new': No such 
file or directory
Errors were encountered while processing:
 /var/cache/apt/archives/podman_4.0.1+ds1-3_amd64.deb

Notes:
the file indeed doesn't exist, and if I create it before install, it gets 
deleted.


Installing podman bookworm version (3.4.4+ds1-1) works,
upgrading from that to 4.0.1+ds1-3 still fails with the same error, except for 
extra lines...

Unpacking podman (4.0.1+ds1-3) over (3.4.4+ds1-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/podman_4.0.1+ds1-3_amd64.deb (--unpack):
 unable to open '/usr/lib/systemd/user/podman.socket.dpkg-new': No such 
file or directory
/usr/bin/deb-systemd-helper: error: unable to read podman.socket
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.
Errors were encountered while processing:
 /var/cache/apt/archives/podman_4.0.1+ds1-3_amd64.deb


Not sure what the cause is, this seems to be coming from dpkg-deb and not the 
postrm/prerm/postinstall scripts.


Hope it helps,
Regards,
Martin Hradil


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

Kernel: Linux 5.16.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, 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)

Versions of packages podman depends on:
ii  conmon   2.0.25+ds1-1.1
ii  containernetworking-plugins  1.1.0+ds1-1
ii  golang-github-containers-common  0.47.2+ds1-1
ii  init-system-helpers  1.62
ii  iptables 1.8.7-1
ii  libc62.33-7
ii  libdevmapper1.02.1   2:1.02.175-2.1
ii  libgpgme11   1.16.0-1.2
ii  libseccomp2  2.5.3-2
ii  runc 1.1.0+ds1-1

Versions of packages podman recommends:
ii  buildah   1.24.1+ds1-1
ii  fuse-overlayfs1.7.1-1
ii  golang-github-containernetworking-plugin-dnsname  1.3.1+ds1-2
ii  slirp4netns   1.0.1-2
ii  tini  0.19.0-1
ii  uidmap1:4.11.1+dfsg1-1

Versions of packages podman suggests:
ii  containers-storage  1.36.0+ds1-3
ii  docker-compose  1.29.2-1
ii  iptables1.8.7-1

Bug#450787: postfix: Smarthost set up

[Michael Prokop]

Hi,

* LaMont Jones [Fri Jan 04, 2008 at 07:06:49AM -0700]:

> The bug here is quite possibly that postfix's install doesn't make
> dealing with a machine that needs to tweak myorigin (usually because
> it's not in the DNS for the rest of the internet) easier.

I recently stumbled upon a related issue, where a system had a
static IP configuration, but its search path wasn't configured.
systemd-resolved uses "search ." then, and installation of postfix
fails with such a setup.

Steps to reproduce:

| root@grml ~ # hostname
| grml
| root@grml ~ # hostname --fqdn
| grml
| root@grml ~ # grep '^search' /etc/resolv.conf
| search .
| root@grml ~ # apt install postfix
| [...]
| Creating /etc/postfix/dynamicmaps.cf
| Adding group `postdrop' (GID 125) ...
| Done.
| setting myhostname: grml..
| setting alias maps
| setting alias database
| mailname is not a fully qualified domain name.  Not changing /etc/mailname.
| setting destinations: $myhostname, grml, localhost.localdomain, , localhost
| setting relayhost: 
| setting mynetworks: 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
| setting mailbox_size_limit: 0
| setting recipient_delimiter: +
| setting inet_interfaces: all
| setting inet_protocols: all
| /etc/aliases does not exist, creating it.
| WARNING: /etc/aliases exists, but does not have a root alias.
|
| Postfix (main.cf) is now set up with a default configuration.  If you need to 
| make changes, edit /etc/postfix/main.cf (and others) as needed.  To view 
| Postfix configuration values, see postconf(1).
|
| After modifying main.cf, be sure to run 'systemctl reload postfix'.
|
| Running newaliases
| newaliases: warning: valid_hostname: misplaced delimiter: grml..
| newaliases: fatal: file /etc/postfix/main.cf: parameter myhostname: bad 
parameter value: grml..
| dpkg: error processing package postfix (--configure):
|  installed postfix package post-installation script subprocess returned error 
exit status 75
| [...]

The generated "grml.." setting for postfix's myhostname
configuration is invalid and rejected by e.g. postfix's newaliases.

This is caused by postfix's postinst script, which includes this:

| myfqdn() {
| myhostname=$(hostname --fqdn 2>/dev/null || echo "")
| # If we don't have a name with a dot (which includes ""), then we have 
work.
| if [ $myhostname = ${myhostname%.*} ]; then
| # If it's empty, and we have /etc/hostname, try that.
| if [ -z $myhostname ] && [ -r /etc/hostname ]; then
| myhostname=$(cat /etc/hostname)
| fi
| # If we are still lacking a domain component, then try resolv.conf.
| if [ $myhostname = ${myhostname%.*} ]; then
| if [ -f /etc/resolv.conf ]; then
| # The resolver uses the last one found, and ignores the rest
| mydom=$(sed -n 
's/^search[[:space:]]*\.*\([^[:space:]]*\).*/\1/p;s/^domain[[:space:]]*\.*\([^[:space:]]*\).*/\1/p'
 /etc/resolv.conf | tail -1)
| myhostname="$myhostname${mydom:+.${mydom%.}}"
| else
| myhostname="$myhostname.UNKNOWN"
| fi
| fi
| fi
| echo $myhostname
| }

regards
-mika-


signature.asc
Description: PGP signature

Bug#899167: qbittorrent: ppc64el architecture bugged

[Christian Marillat]

Hi,

Couls you tell us is this bug still exist in version 4.4.1 ?

Christian

Bug#1006150: python3-pip: Error when trying to list packages that need to be updated (local and system-wide)

[Stefano Rivera]

Hi Christian (2022.02.19_17:52:34_-0400)

This feels related to de-vendoring pip's dependencies, because it's
happening inside a zip import, but it's not *just* that.

I think it's a race importing html5lib.treebuilders.etree as multiple
threads try to parse HTML at the same time. Before one thread has
evaluated the line to set the getETreeModule local variable, another
thread sees that html5lib.treebuilders.etree is in sys.modules and tries
to access getETreeModule.

Maybe there's a potential race while zipimporting modules, that one
doesn't see with regular imports? Or I'd assume upstream would have run
into this bug by now. I marked the fixed version based on the zipimport
hunch.

Upstream replaced their homegrown map_multithread with Python 3.7+ map()
in https://github.com/pypa/pip/commit/0252c04a16cd93fe422cebf0b48453b559a2e404
(in 22.0) and if I apply that patch I can't reproduce the race any more.

So, let's apply that.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#997969: Failure with latest upstream

[Frédéric Bonnard]

Control: tags -1 + patch

Upstream 0.9.3 has patches.

F.


signature.asc
Description: PGP signature

Bug#1006881: webcamoid: VirtualCamera support does not work due to pkexec calls not working

[Achim Schaefer]

Package: webcamoid
Version: 9.0.0-2
Severity: normal
X-Debbugs-Cc: bts.debian@schaefer-home.eu

Dear MAintainer,

when trying the new pluging "virtualCameral" I always get the following error:
Webcamoid, 0x7fee2d1ae7c0,  (0)] debug: pkexec --version |
   --help |
   --disable-internal-agent |
   [--user username] PROGRAM [ARGUMENTS...]

See the pkexec manual page for more details.

v4l2loopback is installaed and even the recommended download of akv does not 
help.

Thanks


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

Kernel: Linux 5.16.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de:en_GB:en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages webcamoid depends on:
ii  libavkys9   9.0.0-2
ii  libc6   2.33-7
ii  libgcc-s1   12-20220302-1
ii  libqt5core5a5.15.2+dfsg-15
ii  libqt5gui5  5.15.2+dfsg-15
ii  libqt5network5  5.15.2+dfsg-15
ii  libqt5qml5  5.15.2+dfsg-10
ii  libqt5quick55.15.2+dfsg-10
ii  libqt5quickcontrols2-5  5.15.2+dfsg-4
ii  libqt5widgets5  5.15.2+dfsg-15
ii  libstdc++6  12-20220302-1
ii  qml-module-qt-labs-folderlistmodel  5.15.2+dfsg-10
ii  qml-module-qt-labs-settings 5.15.2+dfsg-10
ii  qml-module-qtgraphicaleffects   5.15.2-2
ii  qml-module-qtqml-models25.15.2+dfsg-10
ii  qml-module-qtquick-controls 5.15.2-2
ii  qml-module-qtquick-controls25.15.2+dfsg-4
ii  qml-module-qtquick-dialogs  5.15.2-2
ii  qml-module-qtquick-extras   5.15.2-2
ii  qml-module-qtquick-privatewidgets   5.15.2-2
ii  qml-module-qtquick-templates2   5.15.2+dfsg-4
ii  webcamoid-data  9.0.0-2
ii  webcamoid-plugins   9.0.0-2

webcamoid recommends no packages.

webcamoid suggests no packages.

-- no debconf information

Bug#1006647: libeclipse-jdt-core-java 4.21 breaks Java 8 compatibility for Tomcat

[Per Lundberg]

Hi,

On 2022-03-02 17:24, Markus Koschany wrote:


(Speaking about tomcat10, I noted the package in experimental is really
old - doesn't seem to have been updated for a few years. Do you know if
anyone is working on updating the package to e.g. Tomcat 10.0.17 or will
it perhaps happen later in the Bookworm release cycle?)


I intend to update it in the near future. I believe the initial goal was to
make it co-installable with Tomcat 9. Currently there are still some file
conflicts which have to be resolved before we can upload Tomcat 10 to unstable.


Aha, I see. Good to know.


We still need OpenJDK 8 to bootstrap Kotlin. Please don't ask for its removal.
It would be great if we could use OpenJDK 11 instead but we are not there yet.


Alright, I will definitely not suggest it in that case. :D


As for the actual libeclipse-jdt-core-java package, is there any
particular reason for going with the 4.21 version in Debian unstable &
bookworm? I am just curious. It feels like a somewhat odd decision to go
with a more recent version than the 4.20 version which Apache bundles in
their distribution. But perhaps there are other Debian packages which
can find use of the newer package, or has it perhaps just been done to
be able to ship the "latest and greatest" version of this package with
Bookworm? (I mean: to not ship something which is "old" already at the
time of release.)


I guess there was no particular reason other than upgrading to the latest
available version back then. I have not investigated yet if another Debian
package requires 4.21 specifically but since we don't really support Java 8
anymore I think we can just move forward. Tomcat 9 will be gone next year and
since we rather have to invest time into fixing OpenJDK 17 bugs than making
packages Java 8 compatible, I would say let's keep it as is.


Thanks, I'm fine with this. I suggest we keep this bug open until we 
have the Dependencies line for tomcat9 fixed, as discussed.



For our own internal needs, we'll have to find another approach (either 
creating our own tomcat9 package as you suggested, or spending the time 
getting our software to be ready for Java 11 (and eventually Java 17) - 
or both. :-)


Given that we will likely have to spend quite an effort moving from 
tomcat9 to tomcat10 (because of the javax.* to jakarta.* package 
change), providing this as a package of our own might not be such a bad 
idea anyway, since it gives us total control of when to roll it our to 
our customers. (We have built an in-house product which is deployed 
using Tomcat at a number of on-premise & cloud-based installations, so 
being too dependent on the Tomcat version which happens to be in Debian 
unstable => Ubuntu LTS at any given time is perhaps not ideal for us.)


Best regards,
Per

Bug#1006880: RFP: httpolice -- validator for HTTP requests and responses

[Jakub Wilk]

Package: wnpp
Severity: wishlist

* Package name: httpolice
  Version : 0.9.0
  Upstream Author : Vasiliy Faronov 
* URL : https://github.com/vfaronov/httpolice
* License : Expat
  Programming Lang: Python
  Description : validator for HTTP requests and responses

HTTPolice is a validator or "linter" for HTTP requests and responses.
It can spot bad header syntax, inappropriate status codes, and other 
potential problems in your HTTP server or client.

-- 
Jakub Wilk

Bug#1006879: RM: playitslowly/1.5.0-1.1

[Tiago Bortoletto Vaz]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
X-Debbugs-Cc: ti...@debian.org

Hi, I'm requesting the removal of playitslowly package from stable and
oldstable due to an old RC bug as described in #1006017.

A RM for unstable has been requested as well in #1006761.

Thanks,

--
Tiago

Bug#1006017: playitslowly doesn't start (hasn't for awhile)

[Tiago Bortoletto Vaz]

On Sat, Mar 05, 2022 at 11:16:44AM +0100, Andreas Beckmann wrote:
> On 04/03/2022 13.15, Tiago Bortoletto Vaz wrote:
> > This package has indeed been broken for a long time already. Upstream is
> > inactive since 2015 and I'm not willing to do all the fixes it would
> > need. Therefore I requested its removal from Debian archive.
> 
> Then we should probably get it removed from stable and and oldstable as
> well, since it it not usable there either.
> Can you file the corresponding bugs, too?

Sure, I'll proceed with the requests.

Bests,

--
Tiago

Bug#1006832: RFS: minetest/5.5.0+dfsg+~1.9.0mt4+dfsg-1 -- Multiplayer infinite-world block sandbox

[Bastian Germann]

On Sat, 5 Mar 2022 21:59:31 -0500 Travis Wrightsman wrote:

Changes since the last upload:

 minetest (5.5.0+dfsg+~1.9.0mt4+dfsg-1) unstable; urgency=medium
 .
   * New upstream release.
   * Add git-buildpackage config file.
   * Migrate from repack.sh to Files-Excluded.
   * Refresh patches.
   * Add NEWS describing breaking/significant changes.
   * Add README.source for maintainer notes.



If this is a team upload, please say so in the changelog.

Bug#1006853: cups-browsed: HTTP Forbidden when adding printer with cups-browsed

[Brian Potkin]

On Mon 07 Mar 2022 at 11:15:26 +, Brian Potkin wrote:

> tags 1006853 moreinfo
> thanks
> 
> 
> 
> On Sun 06 Mar 2022 at 21:34:08 +0100, Mark Brandis wrote:
> 
> > Package: cups-browsed
> > Version: 1.28.12-1
> > Severity: normal
> > X-Debbugs-Cc: mark.bran...@posteo.de
> > 
> > I use a Epson XP 8600 printer, which cups found just fine and added
> > automatically as a printer queue, until recently. For a few days now, cups 
> > has
> > not added the printer as a queue, unless the printer was online during boot.
> > 
> > Searching in the logs I found the following:
> 
> [...]
> 
> > ==> error_log <==
> > E [06/Mar/2022:21:30:15 +0100] [Client 406] Returning HTTP Forbidden for 
> > CUPS-
> > Add-Modify-Printer (ipp://localhost/printers/EPSON_XP_8600_Series) from
> > localhost
> 
> Thank you for you report, Mark. Is the connection USB or network?

The connection type doesn't matter; I can now replicate your observation.

Edit /etc/cups/cups-files.conf to have

  SystemGroup lpadmin root

and restart cups.

Regards,

Brian.

Bug#1006853: cups-browsed: HTTP Forbidden when adding printer with cups-browsed

[Mark Brandis]

The printer is connected via network.

Regards,
Mark

Bug#1006808: RFS: jimtcl/0.79+dfsg0-4 [ITA] -- small-footprint implementation of Tcl - shared library

[Bastian Germann]

Am 07.03.22 um 13:17 schrieb vimer:

Hi,
On Mon, Mar 07, 2022 at 12:59:45PM +0100, Bastian Germann wrote:

On Sat, 5 Mar 2022 23:16:45 +0800 vimer wrote:

Changes since the last upload:

  jimtcl (0.79+dfsg0-4) unstable; urgency=medium
  .
 * Add myself as maintainer (Closes: #993599).


You should really accomplish something else on the package on adopting it.
I am closing this request.

Ok. But could you please tell me the "something else" on the package is
what really.
The lintian warnings? https://tracker.debian.org/pkg/jimtcl.
Thank you!


I do not know the package, so I do not know that. When you want to be the 
maintainer, please find that out yourself.
Just setting yourself as a maintainer without actually doing any work is just 
not feasible for a sponsorship request.
People want to sponsor package revisions that have an effect additionally to 
handing over maintainership.

Bug#1006878: libjs-of-ocaml-ocamlbuild-ocaml-dev: missing Breaks+Replaces: libjs-of-ocaml (<< 4), libjs-of-ocaml-dev (<< 4)

[Andreas Beckmann]

Package: libjs-of-ocaml-ocamlbuild-ocaml-dev
Version: 0.0.0+git20220118+852302c8-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack 
.../libjs-of-ocaml-ocamlbuild-ocaml-dev_0.0.0+git20220118+852302c8-1+b1_amd64.deb
 ...
  Unpacking libjs-of-ocaml-ocamlbuild-ocaml-dev 
(0.0.0+git20220118+852302c8-1+b1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libjs-of-ocaml-ocamlbuild-ocaml-dev_0.0.0+git20220118+852302c8-1+b1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/lib/ocaml/js_of_ocaml-ocamlbuild/META', which is 
also in package libjs-of-ocaml 3.11.0-1+b1
  Errors were encountered while processing:
   
/var/cache/apt/archives/libjs-of-ocaml-ocamlbuild-ocaml-dev_0.0.0+git20220118+852302c8-1+b1_amd64.deb

these files conflict with libjs-of-ocaml:

usr/lib/ocaml/js_of_ocaml-ocamlbuild/META
usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cma
usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cmxs

these files conflict with libjs-of-ocaml-dev

usr/lib/ocaml/js_of_ocaml-ocamlbuild/dune-package
usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.a
usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cmi
usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cmt
usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cmti
usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cmx
usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cmxa
usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.ml
usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.mli
usr/lib/ocaml/js_of_ocaml-ocamlbuild/opam

libjs-of-ocaml(-dev) 4.0.0-1+b1 in sid seems to no longer ship the
conflicting files.


cheers,

Andreas


libjs-of-ocaml-dev=3.11.0-1+b1_libjs-of-ocaml-ocamlbuild-ocaml-dev=0.0.0+git20220118+852302c8-1+b1.log.gz
Description: application/gzip

Bug#1006801: tinyssh: autopkgtests fail with OpenSSH 8.9

[Jan Mojzis]

Problem fixed in the release 20220305,
also update debian package https://salsa.debian.org/debian/tinyssh 

and debian package is ready to upload.

I need sponsor.

Jan.

> On 5. 3. 2022, at 16:24, Jan Mojzis  wrote:
> 
> Hello,
> 
> I can confirm that the autopkgtest does not pass the latest tinyssh version 
> (20220222).
> The problem is related to the openssh upgrade from 8.8 -> 8.9.
> 
> openssh-8.8p1# ./ssh test@127.0.0.1 "cat >/tmp/testfile2" < /tmp/testfile1 && 
> echo OK || echo BAD
> OK
> 
> openssh-8.9p1# ./ssh test@127.0.0.1 "cat >/tmp/testfile2" < /tmp/testfile1 && 
> echo OK || echo BAD
> client_loop: send disconnect: Broken pipe
> BAD
> 
> """
> tinysshd: VjEOjvCa: BUG:  (protocol error){sshcrypto_cipher_chachapoly.c:88}
> """
> Tinyssh receives too large packet (32784 bytes), instead of maxpacket ( 32768 
> bytes) and
> immediately closes the connection.
> 
> I have to look deeper where the bug is, if in tinyssh or in openssh client.
> 
> Jan
> 
> 
> 
> 
>> On 5. 3. 2022, at 13:04, Colin Watson  wrote:
>> 
>> Package: tinyssh
>> Version: 20190101-1
>> Severity: important
>> 
>> tinyssh's autopkgtests are failing with OpenSSH 8.9 in unstable.  See
>> e.g.:
>> 
>> https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/t/tinyssh/20220226_180547_e244f@/log.gz
>> 
>> autopkgtest [18:05:25]: test 06transfer: preparing testbed
>> Reading package lists...
>> Building dependency tree...
>> Reading state information...
>> Starting pkgProblemResolver with broken count: 0
>> Starting 2 pkgProblemResolver with broken count: 0
>> Done
>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>> 1 not fully installed or removed.
>> After this operation, 0 B of additional disk space will be used.
>> Setting up autopkgtest-satdep (0) ...
>> (Reading database ... 66551 files and directories currently installed.)
>> Removing autopkgtest-satdep (0) ...
>> autopkgtest [18:05:28]: test 06transfer: [---
>> 1048576+0 records in
>> 1048576+0 records out
>> 1048576 bytes (1.0 MB, 1.0 MiB) copied, 2.42825 s, 432 kB/s
>> Warning: Permanently added '[127.0.0.1]:1' (ED25519) to the list of 
>> known hosts.
>> tinysshd: VjEOjvCa: BUG:  (protocol error){sshcrypto_cipher_chachapoly.c:88}
>> client_loop: send disconnect: Broken pipe
>> ssh transfer failed
>> autopkgtest [18:05:31]: test 06transfer: ---]
>> autopkgtest [18:05:31]: test 06transfer:  - - - - - - - - - - results - - - 
>> - - - - - - -
>> 06transfer   FAIL non-zero exit status 1
>> 
>> I see that there's a new upstream release of tinyssh not yet in Debian,
>> though I haven't checked whether that fixes this problem.  Do you need
>> help with sponsorship?
>> 
>> -- 
>> Colin Watson (he/him)  [cjwat...@debian.org]

Bug#1006877: cubeb: please mark c++ symbol as optional

[Gianfranco Costamagna]

Source: cubeb
Version: 0.0~git20220110.9edd150+ds-1
severity: important
tags: patch

Hello, looks like in Ubuntu cubeb is FTBFS due to an extra symbol now removed.
I think this will become an issue in Debian too once new gcc defaults.

The best fix to me is to just mark the c++ vtable symbol as optional

--- debian/libcubeb0.symbols 
(libcubeb0_0.0~git20220110.9edd150+ds-1build1_amd64)
+++ dpkg-gensymbolsPCFvbW   2022-03-07 11:13:45.893845307 +
@@ -26,4 +26,4 @@
  cubeb_strings_destroy@Base 0.0~git20210801.6ce9596
  cubeb_strings_init@Base 0.0~git20210801.6ce9596
  cubeb_strings_intern@Base 0.0~git20210801.6ce9596
- (c++)"vtable for 
std::thread::_State_impl
 > >@Base" 0.0~git20210801.6ce9596
+#MISSING: 0.0~git20220110.9edd150+ds-1build1# (c++)"vtable for 
std::thread::_State_impl
 > >@Base" 0.0~git20210801.6ce9596
dh_makeshlibs: error: failing due to earlier errors
make: *** [debian/rules:7: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


see e.g.
https://launchpad.net/ubuntu/+source/cubeb/0.0~git20220110.9edd150+ds-1ubuntu1
and this patch:
--- cubeb-0.0~git20220110.9edd150+ds/debian/libcubeb0.symbols   2022-01-12 
18:16:20.0 +
+++ cubeb-0.0~git20220110.9edd150+ds/debian/libcubeb0.symbols   2022-03-07 
11:14:51.0 +
@@ -1,6 +1,6 @@
 libcubeb.so.0 libcubeb0 #MINVER#
 * Build-Depends-Package: libcubeb-dev
- (c++)"vtable for 
std::thread::_State_impl
 > >@Base" 0.0~git20210801.6ce9596
+ (c++|optional)"vtable for 
std::thread::_State_impl
 > >@Base" 0.0~git20210801.6ce9596
  cubeb_destroy@Base 0.0~git20210801.6ce9596
  cubeb_device_collection_destroy@Base 0.0~git20210801.6ce9596
  cubeb_enumerate_devices@Base 0.0~git20210801.6ce9596

Bug#956009: gvfs mounts via ssh but not when in GUI

[Lars Behrens]

Package: gvfs
Version: 1.46.2-1
Followup-For: Bug #956009




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

Kernel: Linux 5.10.0-11-amd64 (SMP w/4 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 gvfs depends on:
ii  gvfs-common   1.46.2-1
ii  gvfs-daemons  1.46.2-1
ii  gvfs-libs 1.46.2-1
ii  libc6 2.31-13+deb11u2
ii  libglib2.0-0  2.66.8-1

gvfs recommends no packages.

Versions of packages gvfs suggests:
ii  gvfs-backends  1.46.2-1

-- no debconf information

SMB-Mounts only appear in /var/run/$USER/gvfs when not logged in via GUI

Bug#1006853: cups-browsed: HTTP Forbidden when adding printer with cups-browsed

[Brian Potkin]

tags 1006853 moreinfo
thanks



On Sun 06 Mar 2022 at 21:34:08 +0100, Mark Brandis wrote:

> Package: cups-browsed
> Version: 1.28.12-1
> Severity: normal
> X-Debbugs-Cc: mark.bran...@posteo.de
> 
> I use a Epson XP 8600 printer, which cups found just fine and added
> automatically as a printer queue, until recently. For a few days now, cups has
> not added the printer as a queue, unless the printer was online during boot.
> 
> Searching in the logs I found the following:

[...]

> ==> error_log <==
> E [06/Mar/2022:21:30:15 +0100] [Client 406] Returning HTTP Forbidden for CUPS-
> Add-Modify-Printer (ipp://localhost/printers/EPSON_XP_8600_Series) from
> localhost

Thank you for you report, Mark. Is the connection USB or network?

Regards,

Brian.

Bug#1006876: python3-sunpy: tests fail with h5netcdf 0.14

[Drew Parsons]

Package: python3-sunpy
Version: 3.1.3-2
Severity: normal

sunpy is failing tests with python3-h5netcdf 0.14.1-1.

h5netcdf made some changes with respect to string types of attributes,
related to changes in h5py 3. Not sure if that explains the sunpy
errors.

There's a new release of sunpy available, hopefully it helps. Probably
it does help, it applies https://github.com/sunpy/sunpy/pull/5920
addressing h5netcdf problems

Bug#1006875: samba-libs: The dependency on python3-talloc breaks multiarch support

[Francois Gouget]

Package: samba-libs
Version: 2:4.13.13+dfsg-1~deb11u2
Severity: normal

Dear Maintainer,

samba-libs claims to support multiarch (Multiarch: same) but it depends
on python3-talloc which does not support multiarch.

python3-talloc seems to depend closely on the main python3 package so
I am not sure it would make sense to make it multiarch. So maybe it is
samba-libs that should not depend on it. Could the dependency be moved
to another package which would be, for instance, multiarch=foreign?

As is this prevents proper support for Samba NetAPI in 32-bit Windows
applications because of this dependency chain:
  32-bit Windows application -> 32-bit Wine -> 32-bit libnetapi.so ->
  samba-dev:i386 -> samba-libs:i386 -> python3-talloc:i386 which
  conflicts with python3-talloc:amd64


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

Kernel: Linux 5.10.0-10-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN, 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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages samba-libs depends on:
ii  libacl1   2.2.53-10
ii  libavahi-client3  0.8-5
ii  libavahi-common3  0.8-5
ii  libbsd0   0.11.3-1
ii  libc6 2.31-13+deb11u2
ii  libcap2   1:2.44-1
ii  libcups2  2.3.3op2-3+deb11u1
ii  libgnutls30   3.7.1-5
ii  libjansson4   2.13.1-1.1
ii  libldap-2.4-2 2.4.57+dfsg-3
ii  libldb2   2:2.2.3-2~deb11u1
ii  libnsl2   1.3.0-2
ii  libpam0g  1.4.0-9+deb11u1
ii  libpopt0  1.18-2
ii  libpython3.9  3.9.2-1
ii  libtalloc22.3.1-2+b1
ii  libtdb1   1.4.3-1+b1
ii  libtevent00.10.2-1
ii  libwbclient0  2:4.13.13+dfsg-1~deb11u2
ii  python3-ldb   2:2.2.3-2~deb11u1
ii  python3-talloc2.3.1-2+b1
ii  zlib1g1:1.2.11.dfsg-2

samba-libs recommends no packages.

samba-libs suggests no packages.

-- no debconf information

Bug#1000188: python3.10: testsuite gets stuck in a loop on buildds

[Julien Cristau]

Control: severity -1 serious

On Mon, Nov 29, 2021 at 09:56:39AM +0100, Matthias Klose wrote:
> Control: severity -1 imortant
> Control: tags -1 + moreinfo
> 
> tried to reproduce locally without success. having built the package
> continuously over the weekend ...

This happened again; if you can't easily fix the affected test then
please either disable it or add a timeout so it doesn't keep going for
days on end.

Cheers,
Julien

Bug#958427: libsrtp2: FTBFS on x32: bogus printf with time_t, then segfaults [regression]

[Jonas Smedegaard]

Quoting Laurent Bigonville (2022-03-07 11:10:41)
> This should have been fixed upstream with the following patch: 
> https://github.com/cisco/libsrtp/commit/4f1d945fe3eb302fa2bab2aea63fdf6ea7485e95
> 
> Do you think you could do an upload with that includes it?

Sure - I'll look into that right now...

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature