Bug#1056608: timeshift: Timeshift cant restore RSYNC snapshots if your system installed on BTRFS with wrong subvolume

2024-02-01 Thread theofficialgman
this bug being marked as "grave" prevents installation of timeshift
packages on some debian systems. please lower the severity of this bug
report. I am not even sure what causes apt-listbugs to block this

The following NEW packages will be installed:
  btrfs-progs libgee-0.8-2 libgnomekbd-common libgnomekbd8 libxapp1
pi-apps-9c59d247 timeshift xapps-common
0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded.
After this operation, 10.1 MB of additional disk space will be used.
Get:1 file:/tmp/pi-apps-local-packages ./ timeshift 23.07.1 [570 kB]
Get:2 /home/pi/pi-apps-9c59d247.deb pi-apps-9c59d247 all 1.0 [752 B]
Get:3 http://deb.debian.org/debian bullseye/main arm64 btrfs-progs arm64
5.10.1-2 [677 kB]
Get:4 http://deb.debian.org/debian bullseye/main arm64 libgee-0.8-2 arm64
0.20.4-1 [215 kB]
Get:5 http://deb.debian.org/debian bullseye/main arm64 libgnomekbd-common
all 3.26.1-1 [77.2 kB]
Get:6 http://deb.debian.org/debian bullseye/main arm64 libgnomekbd8 arm64
3.26.1-1 [45.4 kB]
Get:7 http://deb.debian.org/debian bullseye/main arm64 xapps-common all
2.0.7-1 [49.9 kB]
Get:8 http://deb.debian.org/debian bullseye/main arm64 libxapp1 arm64
2.0.7-1 [84.5 kB]
grave bugs of timeshift (→ 23.07.1) 
 b1 - #1056608 - timeshift: Timeshift cant restore RSYNC snapshots if your
system installed on BTRFS with wrong subvolume
Summary:
 timeshift(1 bug)
timeshift will be pinned. Restart APT session to enable
**
** Exiting with an error in order to stop the installation. **
**
Fetched 1,150 kB in 0s (2,332 kB/s)
E: Sub-process /usr/bin/apt-listbugs apt returned an error code (10)
E: Failure running script /usr/bin/apt-listbugs apt
Apt finished.
Failed to install the packages!
APT reported these errors:
E: Sub-process /usr/bin/apt-listbugs apt returned an error code (10)
E: Failure running script /usr/bin/apt-listbugs apt


Bug#1055312: adduser: "addgroup user group" is mentioned in man page but does not work anymore (ex bug 664869)

2023-12-27 Thread theofficialgman
This bug has been reported by multiple users across multiple bug reports.
It is functionality that has existed since 1995 and is well adopted and
expected in scripts and documentation (both the manpage and 3rd party). Fix
the manpage and revert the patch and accept that this is intended and
necessary functionality. Breaking something that has existed for 25 years
just because the documentation isn't as clear as you would like is not a
valid excuse.


Bug#1057013: Regression: addgroup user group no longer works and should have been documented instead of removed

2023-11-27 Thread theofficialgman
Package: adduser
Version: 3.122
Severity: major
File: /usr/sbin/addgroup

A regression was caused with the unnecessary commit
https://salsa.debian.org/debian/adduser/-/commit/8d42193438f6c1500fb36cd5c24bf682888a611c
to close https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664869

This undocumented syntax was known in use in scripting (such as nvidia
tegra debian based distros). Instead of disabling two argument syntax
this should instead be reverted and the manpage should be fixed to
advertise this syntax since it is functional and in use.

Thanks,
theofficialgman


Bug#1051276: xdg-desktop-portal-kde should include pipewire as a dep and enable it

2023-10-15 Thread theofficialgman
I have inspected the package build depends and it appears to all be correct
and the package seems to be getting built with these portals enabled,
however it does not function in practice.

I have spent multiple hours debugging this issue to no avail


Bug#1051276: xdg-desktop-portal-kde should include pipewire as a dep and enable it

2023-10-15 Thread theofficialgman
Hi,

I am also running into this. Please enable it on stable and oldstable!

Thanks,
theofficialgman


Bug#1052440: Request: enable widevine on all architectures if found (patch included)

2023-09-21 Thread theofficialgman
Package: chromium
Version: 117.0.5938.62-1

This is a request to include the patch that Ubuntu added to bionic/snap
back in March of this year. It is a simple patch to the
third_party/widevine/cdm/widevine.gni to no longer hardcode x64 as a
requirement for checking for widevine. This allows the user to supply a
widevine binary on any architecture if they have one. Right now it will not
load one even if the user supplies one on non-x64 architectures.

see:
https://bugs.launchpad.net/ubuntu/bionic/+source/chromium-browser/+bug/2008433
patch:
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/plain/build/chromium-patches/widevine-enable-version-string.patch?h=dev

I would appreciate it if this be backported/included in stable/oldstable as
well.

Thanks,
theofficialgman


Bug#1023237: openjdk-11: Keep out of testing and stable

2023-06-17 Thread theofficialgman
Is there a better reason this should be kept out of testing and stable?
Many users find this openjdk-11 helpful and necessary for
stability/continuity reasons over the current LTS. Security updates will
last for 3+ more years so I don't see any reason why this should be held
back from stable and testing.


Bug#1033961: dpkg: Please add support for zstd (Zstandard) compressed packages (for stable/oldstable)

2023-04-09 Thread theofficialgman
> That commit depends on several other refactors linked to the parallel

compression support for xz

Oh I see. In any case I don't see why these changes could not be made
in the -backports repositories for the requested distros. It seems
like only the 2-3 commits before you added this commit are dependent
on it.


Bug#1033961: closed by Guillem Jover (Re: Bug#1033961: dpkg: Please add support for zstd (Zstandard) compressed packages (for stable/oldstable))

2023-04-09 Thread theofficialgman
The patch contents indicate that only libzstd1 >= 1.4.0 are a requirement
for the new parallel compression support. Bullseye has version 1.4.8 in the
repos and buster-backports has version 1.4.4 which are both compatible with
these changes.

Please reconsider in light of these corrections.

On Sat, Apr 8, 2023 at 7:00 AM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the dpkg package:
>
> #1033961: dpkg: Please add support for zstd (Zstandard) compressed
> packages (for stable/oldstable)
>
> It has been closed by Guillem Jover .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Guillem Jover <
> guil...@debian.org> by
> replying to this email.
>
>
> --
> 1033961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033961
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Guillem Jover 
> To: theofficialgman ,
> 1033961-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sat, 8 Apr 2023 12:57:58 +0200
> Subject: Re: Bug#1033961: dpkg: Please add support for zstd (Zstandard)
> compressed packages (for stable/oldstable)
> Control: tag -1 wontfix
>
> On Tue, 2023-04-04 at 22:34:20 -0400, theofficialgman wrote:
> > Package: dpkg
> > Severity: wishlist
>
> > Please backport these changes
> > (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892664
> > https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=2c2f7066b6b)
> <https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=2c2f7066b>) into
> > debian stable (bullseye) and debian oldstable (buster). The lack of
> > tar.zst support is critical for these releases as time goes on and
> > many popular CI systems only have Ubuntu builders. The lack of tar.zst
> > support means that for many projects providing packages for debian
> > distros is not possible or too difficult.
>
> That commit depends on several other refactors linked to the parallel
> compression support for xz. But in any case this is a significant
> change, that does not seem justifiable for a stable release update.
>
> (Also building for distribution X from distribution Y, even though
> unfortunately common, is in general frowned upon, and I'd strongly
> advise against doing that anyway.)
>
> So I'm afraid, I'll have to decline this request.
>
> Regards,
> Guillem
>
>
> -- Forwarded message --
> From: theofficialgman 
> To: sub...@bugs.debian.org
> Cc:
> Bcc:
> Date: Tue, 4 Apr 2023 22:34:20 -0400
> Subject: dpkg: Please add support for zstd (Zstandard) compressed packages
> (for stable/oldstable)
>
> Package: dpkg
> Severity: wishlist
>
> Dear debian developers,
>
> Please backport these changes 
> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892664 
> https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=2c2f7066b) into debian 
> stable (bullseye) and debian oldstable (buster). The lack of tar.zst support 
> is critical for these releases as time goes on and many popular CI systems 
> only have Ubuntu builders. The lack of tar.zst support means that for many 
> projects providing packages for debian distros is not possible or too 
> difficult.
>
> With the ease of which the backport is achievable I am politely requesting 
> that you include it in the mentioned distros at urnest.
>
> Thanks
>
>


Bug#1033961: dpkg: Please add support for zstd (Zstandard) compressed packages (for stable/oldstable)

2023-04-04 Thread theofficialgman
Package: dpkg
Severity: wishlist

Dear debian developers,

Please backport these changes
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892664
https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=2c2f7066b) into
debian stable (bullseye) and debian oldstable (buster). The lack of
tar.zst support is critical for these releases as time goes on and
many popular CI systems only have Ubuntu builders. The lack of tar.zst
support means that for many projects providing packages for debian
distros is not possible or too difficult.

With the ease of which the backport is achievable I am politely
requesting that you include it in the mentioned distros at urnest.

Thanks


Bug#1006182: buster-pu: package qtbase-opensource-src/5.11.3+dfsg1-1+deb10u5

2022-04-27 Thread theofficialgman
Hi I’m that original user that requested the patch.

Do you think you could just go ahead and release it and worry about the
CVEs later as necessary? This bug is quite crippling for some applications.


Bug#1001082: qtbase-opensource-src: segfault when closing one windows in a multi window QT application

2022-02-17 Thread theofficialgman
Thanks for pushing the fix to the buster git branch. Is this good to be
released or do we have to wait for some release timing before it is built
and published?


Bug#1001082: qtbase-opensource-src: segfault when closing one windows in a multi window QT application

2022-02-09 Thread theofficialgman
any updates on this? as referenced before, it should be fixable by picking
these two commits:
https://codereview.qt-project.org/c/qt/qtbase/+/264529
https://codereview.qt-project.org/c/qt/qtbase/+/237817
which were used to resolve this bug:
https://bugreports.qt.io/browse/QTBUG-68393


Bug#1001082: qtbase-opensource-src: segfault when closing one windows in a multi window QT application

2021-12-03 Thread theofficialgman
Package: qtbase-opensource-src
Severity: important
Tags: newcomer

Dear Maintainer,

In both debian buster and raspbian buster, closing an application window in a 
multi window QT application causes a segfault and the entire program to crash.
This might have been fixed upstream in one of these commits: 
https://github.com/qt/qtbase/commit/ca991ee22d3509f8f54ee26d4c30d45319428c8f or 
https://github.com/qt/qtbase/commit/e9e8d67e31b8b6a8348b5dae3225be2dbd87ffd2
QT 5.15 from debian bullseye does not have this issue, so it has been fixed 
upstream somewhere inbetween 5.12 and 5.15 release

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 10 (buster)
Release:10
Codename:   buster
Architecture: aarch64

Kernel: Linux 4.9.140+ (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C), 
LANGUAGE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect