Bug#1033462: KMail: Sending emails fails via Gmail due to OAuth 2.0 Scopes

[Sedat Dilek]

Hi,

Unfortunately, I had no big success with playing with Google's OAuth Scopes.

But I found another solution ...

Gmail-Account > Data & Privacy > Apps and services > Third party apps
and services > Akonadi Service For Google Services

... I was able to send emails again via KMail.

[ INFO ]
Akonadi Resources for Google Services has some access to your Google Account

To use some Akonadi Resources for Google Services features, you gave
Akonadi Resources for Google Services some access to your Google
Account.
This access might include sensitive info

[ See your profile info ]
See your primary Google Account email address
Associate you with your personal info on Google

[ Read, compose, send, and permanently delete all your email from
Gmail ] <--- so-called "Scopes"
This app wants permission to do anything you can do in your Gmail, including:
Read your emails
Compose new emails
Add new emails meant for a different email address into your inbox
Send emails for you
Delete your email
Create, change or delete your email labels
Get notified when certain kinds of emails appear in your Gmail inbox,
like a travel confirmation

Your email may contain sensitive info, like names of your contacts,
your private communications, or financial or medical information

[ CONCLUSION ]
Unsure, if this was a clever/smart decision?

BR,
-Sedat-

Bug#1033462: kmail: Kmail fails to send emails via Google mail with "Failed to authenticate additional scopes"

[Sedat Dilek]

OAuth 2.0 Scopes for Google APIs:

https://developers.google.com/identity/protocols/oauth2/scopes

Bug#1033462: kmail: Kmail fails to send emails via Google mail with "Failed to authenticate additional scopes"

[Sedat Dilek]

Hi,

I upgraded yesterday my machine from bookworm/stable to trixie/testing.

KMail was used to check if I can send emails - this seems no more to work.

Seeing the same issue like Ariel Garcia in #1033462 (sorry partly in German):

We have an error during reading password  "Entry not found"
We have an error during reading password  "Entry not found"
[SASL-XOAUTH2] - Requesting authID!
[SASL-XOAUTH2] - Requesting token!
[SASL-XOAUTH2] - filling prompts!
[SASL-XOAUTH2] - Requesting authID!
[SASL-XOAUTH2] - Requesting token!
org.kde.kgapi: Bad request, Google replied ' "{\n  \"error\":
\"invalid_grant\",\n  \"error_description\": \"Bad Request\"\n}" '
org.kde.pim.mailtransport.smtpplugin: Error obtaining XOAUTH2 token:
"Authentifizierung zusätzlicher Bereiche ist fehlgeschlagen"
org.kde.pim.ksmtp: SMTP Socket error:
QAbstractSocket::RemoteHostClosedError "Der entfernte Rechner hat die
Verbindung geschlossen"

English:

org.kde.pim.mailtransport.smtpplugin: Error obtaining XOAUTH2 token: "Failed to
authenticate additional scopes"
org.kde.pim.ksmtp: SMTP Socket error: QAbstractSocket::RemoteHostClosedError
"The remote host closed the connection"

When NO password (token) is set I see:
We have an error during reading password  "Entry not found"

Tryouts:

[ kmail - SMTP ]

User: sedat.di...@gmail.com
Pass:MYTOKEN

Encryption-1: STARTTLS
Port-1: 587
Authentication-1: XOAUTH2

Alternatively:

Encryption-2: SSL/TLS
Port-2: 465
Authentication-2: XOAUTH2

NOTE: On Gmail side nothing was changed - I can send patches via git
send-email but not KMail.

I use postgresql backend and can connect to the database and its tables.

[ ~/.config/akonadi/akonadiserverrc ]

[Debug]
Tracer=null

[%General]
Driver=QPSQL

[QPSQL]
Host=
InitDbPath=
Name=akonadi-dileks
Options=
ServerPath=
StartServer=false
- EOF -

Deleting all files in ~/.config/akonadi/ but keeping akonadiserverrc
plus deleting directory ~/.local/share/akonadi after stopping akonadi
did not help.

In May 2023 was my last working sent-email - I kept all test-emails
and are stored in sent-mail:

[ 
~/.local/share/local-mail/sent-mail/new/1683526703181.R196.iniza26703181.R196.iniza
]

From: dileks 
To: sedat.di...@gmail.com
Subject: KMail - Test 08-May-2023
Date: Mon, 08 May 2023 08:18:22 +0200
Message-ID: <2687898.mvXUDI8C0e@iniza>
X-KMail-Identity: 1886993645
X-KMail-Transport: 1190029663
X-KMail-Fcc: 20
X-KMail-Identity-Name: dileks
X-KMail-Transport-Name: dileks@gmail
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

KMail - Test 08-May-2023
- EOF -

Not sure where to dig into the woods.

Any help is much appreciated.

Thanks.

Best regards,
-Sedat-

Bug#1029079: akonadi-backend-mysql: Build against default-mysql-{client,server}-core 1.1.0

[Sedat Dilek]

Package: akonadi-backend-mysql
Version: 4:22.12.0-2
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

I removed akonadi-backend-mysql from my Debian/unstable AMD64 box as I need a 
higher version of mariadb.

These changes were done on my latest upgrade:

-ii  mariadb-client-core-10.61:10.6.11-2
+ii  mariadb-client-core 1:10.11.1-1
-ii  mariadb-server-core-10.61:10.6.11-2
+ii  mariadb-server-core 1:10.11.1-1

-ii  default-mysql-client-core   1.0.8
-ii  default-mysql-server-core   1.0.8
+ii  default-mysql-client-core   1.1.0
+ii  default-mysql-server-core   1.1.0
-ii  mysql-common5.8+1.0.8
+ii  mysql-common5.8+1.1.0

Can you please build against latest default-mysql-{client,server}-core v1.1.0 
aka mariadb 10.11?

Thanks.

Best regards,
-Sedat-

P.S.: From my upgrade log:

...
Unpacking default-mysql-server-core (1.1.0) over (1.0.8) ...
dpkg: mariadb-server-core-10.6: dependency problems, but removing anyway as you 
requested:
 akonadi-backend-mysql depends on default-mysql-server-core | 
virtual-mysql-server-core; however:
  Package default-mysql-server-core is not configured yet.
  Package virtual-mysql-server-core is not installed.
  Package mariadb-server-core-10.6 which provides virtual-mysql-server-core is 
to be removed.
...
dpkg: mariadb-client-core-10.6: dependency problems, but removing anyway as you 
requested:
 akonadi-backend-mysql depends on default-mysql-client-core | 
virtual-mysql-client-core; however:
  Package default-mysql-client-core is not configured yet.
  Package virtual-mysql-client-core is not installed.
  Package mariadb-client-core-10.6 which provides virtual-mysql-client-core is 
to be removed.
...

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

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

Versions of packages akonadi-backend-mysql depends on:
ii  default-mysql-client-core1.1.0
ii  default-mysql-server-core1.1.0
ii  libqt5sql5-mysql 5.15.8+dfsg-2
ii  mariadb-client-core [virtual-mysql-client-core]  1:10.11.1-1
ii  mariadb-server-core [virtual-mysql-server-core]  1:10.11.1-1

Versions of packages akonadi-backend-mysql recommends:
ii  akonadi-server  4:22.12.0-2+b1

akonadi-backend-mysql suggests no packages.

-- no debconf information

Bug#1024873: cvlc shows wrong revision 3.0.13-8-g41878ff4f2

[Sedat Dilek]

Hi Debian MM team,

looks like I have reported the bug against cvlc not vlc.

Feel free to correct.

Thanks.

Regards,
-Sedat-

Bug#1024873: cvlc shows wrong revision 3.0.13-8-g41878ff4f2

[Sedat Dilek]

Package: cvlc
Version: vlc
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

cvlc shows a wrong revision:

$ LC_ALL=C cvlc --version
VLC media player 3.0.18 Vetinari (revision 3.0.13-8-g41878ff4f2)
VLC version 3.0.18 Vetinari (3.0.13-8-g41878ff4f2)
Compiled by Debian buildd for unstable on Debian amd64 buildd (Nov 23 2022 
18:50:35)
Compiler: gcc version 12.2.0 (Debian 12.2.0-9)
This program comes with NO WARRANTY, to the extent permitted by law.
You may redistribute it under the terms of the GNU General Public License;
see the file named COPYING for details.
Written by the VideoLAN team; see the AUTHORS file.

VLC GUI version says 3.0.18 Vetinari.

So, is this revison hardcoded or a leftover?

Please ckeck yourself.

Thanks.

Regards,
-Sedat-

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

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

Bug#1023455: clang-15: Bump version to 15.0.4

[Sedat Dilek]

Package: clang-15
Version: 1:15.0.3-2
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

LLVM version 15.0.4 is a bugfix release (see below links).

Please, update to it.

Thanks.

Regards,
-Sedat-

[1] https://github.com/llvm/llvm-project/releases/tag/llvmorg-15.0.4
[2] https://discourse.llvm.org/t/llvm-15-0-4-released/66337

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

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

Versions of packages clang-15 depends on:
ii  binutils2.39-8
ii  libc6   2.36-4
ii  libc6-dev   2.36-4
ii  libclang-common-15-dev  1:15.0.3-2
ii  libclang-cpp15  1:15.0.3-2
ii  libclang1-151:15.0.3-2
ii  libgcc-12-dev   12.2.0-9
ii  libgcc-s1   12.2.0-9
ii  libllvm15   1:15.0.3-2
ii  libobjc-12-dev  12.2.0-9
ii  libstdc++-12-dev12.2.0-9
ii  libstdc++6  12.2.0-9
ii  llvm-15-linker-tools1:15.0.3-2

Versions of packages clang-15 recommends:
pn  llvm-15-dev  
ii  python3  3.10.6-1

Versions of packages clang-15 suggests:
pn  clang-15-doc  
pn  wasi-libc 

-- no debconf information

Bug#1022267: mpv: No sound played from TV live-stream or music file

[Sedat Dilek]

On Sun, Oct 23, 2022 at 12:20 PM Sebastian Ramacher
 wrote:
>
> On 2022-10-23 12:15:48 +0200, Sedat Dilek wrote:
> > On Sun, Oct 23, 2022 at 12:05 PM Sebastian Ramacher
> >  wrote:
> > >
> > > Control: tags -1 moreinfo
> > >
> > > On 2022-10-23 10:43:57 +0200, Sedat Dilek wrote:
> > > > Package: mpv
> > > > Version: 0.34.1-1+b5
> > > > Severity: normal
> > > > X-Debbugs-Cc: sedat.di...@gmail.com
> > > >
> > > > Dear Maintainer,
> > > >
> > > > after my daily upgrade yesterday I cannot hear any sound when using mpv.
> > > >
> > > > Like playing MP4 audio-files or TV live-stream...
> > > >
> > > > $ mpv https://www.zdf.de/sender/zdf/zdf-live-beitrag-100.html
> > > > EDL: source file 
> > > > 'https://zdf-hls-15.akamaized.net/hls/live/2016498-b/de/1b5fb462ae0547adb9b368a4363428a9/4/4.m3u8'
> > > >  has unknown duration.
> > > > EDL: source file 
> > > > 'https://zdf-hls-15.akamaized.net/hls/live/2016498/de/1b5fb462ae0547adb9b368a4363428a9/5/5.m3u8'
> > > >  has unknown duration.
> > > >  (+) Video --vid=1 (h264 1280x720 50.000fps)
> > > >  (+) Audio --aid=1 (aac 2ch 48000Hz)
> > > > AO: [pulse] 48000Hz stereo 2ch float
> > > > VO: [gpu] 1280x720 yuv420p
> > >
> > > This stream is not available, but others from ZDF which are accessible
> > > from outside of Germany work just fine. Please provide a verbose mpv log
> > > (run it with -v) when this issue occurs.
> > >
> >
> > Hi Sebastian,
> >
> > Hmmm, I tried a youtou.be link with mpv after several starts with -v and 
> > w/o.
> > Now, I have sound with all 3 - youtu.be and ZDF live-stream.
> >
> > $ mpv https://www.youtube.com/watch?v=Tp0j7pqFat4
> > $ mpv --vid=1 --aid=2
> > https://www.zdf.de/serien/death-in-paradise/die-smaragdinsel-100.html
> > $ mpv 
> > https://www.zdf.de/serien/father-brown/der-hochmut-der-familie-pryde-102.html
>
> Okay, then let's close this issue for now.
>

Yes, please.

-sed@-

Bug#1022267: mpv: No sound played from TV live-stream or music file

[Sedat Dilek]

On Sun, Oct 23, 2022 at 12:05 PM Sebastian Ramacher
 wrote:
>
> Control: tags -1 moreinfo
>
> On 2022-10-23 10:43:57 +0200, Sedat Dilek wrote:
> > Package: mpv
> > Version: 0.34.1-1+b5
> > Severity: normal
> > X-Debbugs-Cc: sedat.di...@gmail.com
> >
> > Dear Maintainer,
> >
> > after my daily upgrade yesterday I cannot hear any sound when using mpv.
> >
> > Like playing MP4 audio-files or TV live-stream...
> >
> > $ mpv https://www.zdf.de/sender/zdf/zdf-live-beitrag-100.html
> > EDL: source file 
> > 'https://zdf-hls-15.akamaized.net/hls/live/2016498-b/de/1b5fb462ae0547adb9b368a4363428a9/4/4.m3u8'
> >  has unknown duration.
> > EDL: source file 
> > 'https://zdf-hls-15.akamaized.net/hls/live/2016498/de/1b5fb462ae0547adb9b368a4363428a9/5/5.m3u8'
> >  has unknown duration.
> >  (+) Video --vid=1 (h264 1280x720 50.000fps)
> >  (+) Audio --aid=1 (aac 2ch 48000Hz)
> > AO: [pulse] 48000Hz stereo 2ch float
> > VO: [gpu] 1280x720 yuv420p
>
> This stream is not available, but others from ZDF which are accessible
> from outside of Germany work just fine. Please provide a verbose mpv log
> (run it with -v) when this issue occurs.
>

Hi Sebastian,

Hmmm, I tried a youtou.be link with mpv after several starts with -v and w/o.
Now, I have sound with all 3 - youtu.be and ZDF live-stream.

$ mpv https://www.youtube.com/watch?v=Tp0j7pqFat4
$ mpv --vid=1 --aid=2
https://www.zdf.de/serien/death-in-paradise/die-smaragdinsel-100.html
$ mpv 
https://www.zdf.de/serien/father-brown/der-hochmut-der-familie-pryde-102.html

Thanks for the hint with `mpv -v $link`.

Have a nice tea,
-Sedat-

> Cheers
>
> >
> >
> > Here the list of upgraded packages:
> >
> > # git diff packages_2669.txt packages.txt | egrep '^[+|-]ii' | column -t
> > -ii  bpftool  7.0.0+6.0.2-1+b1
> > +ii  bpftool  7.0.0+6.0.3-1
> > -ii  fuse33.11.0-1
> > +ii  fuse33.12.0-1
> > -ii  gstreamer1.0-gtk3:amd64  1.20.3-1
> > +ii  gstreamer1.0-gtk3:amd64  1.20.3-1+b1
> > -ii  gstreamer1.0-plugins-good:amd64  1.20.3-1
> > +ii  gstreamer1.0-plugins-good:amd64  1.20.3-1+b1
> > -ii  gstreamer1.0-pulseaudio:amd641.20.3-1
> > +ii  gstreamer1.0-pulseaudio:amd641.20.3-1+b1
> > -ii  libextutils-depends-perl 0.8001-1
> > +ii  libextutils-depends-perl 0.8001-2
> > +ii  libflac12:amd64  1.4.1-2
> > -ii  libfuse3-3:amd64 3.11.0-1
> > +ii  libfuse3-3:amd64 3.12.0-1
> > -ii  libmath-base85-perl  0.5+dfsg-1
> > +ii  libmath-base85-perl  0.5+dfsg-2
> > -ii  libqca-qt5-2:amd64   2.3.4-1+b1
> > -ii  libqca-qt5-2-dev 2.3.4-1+b1
> > -ii  libqca-qt5-2-plugins:amd64   2.3.4-1+b1
> > +ii  libqca-qt5-2:amd64   2.3.5-1
> > +ii  libqca-qt5-2-dev 2.3.5-1
> > +ii  libqca-qt5-2-plugins:amd64   2.3.5-1
> > -ii  libsndfile1:amd641.1.0-3
> > +ii  libsndfile1:amd641.1.0-3+b1
> > -ii  libstring-shellquote-perl1.04-2
> > +ii  libstring-shellquote-perl1.04-3
> > -ii  libzmq5:amd644.3.4-3
> > +ii  libzmq5:amd644.3.4-4
> > -ii  linux-compiler-gcc-12-x866.0.2-1+b1
> > -ii  linux-headers-6.0.0-1-amd64  6.0.2-1+b1
> > -ii  linux-headers-6.0.0-1-common 6.0.2-1
> > -ii  linux-headers-amd64  6.0.2-1+b1
> > -ii  linux-image-6.0.0-1-amd646.0.2-1+b1
> > +ii  linux-compiler-gcc-12-x866.0.3-1
> > +ii  linux-headers-6.0.0-2-amd64  6.0.3-1
> > +ii  linux-headers-6.0.0-2-common 6.0.3-1
> > +ii  linux-headers-amd64  6.0.3-1
> > +ii  linux-image-6.0.0-2-amd646.0.3-1
> > -ii  linux-image-amd646.0.2-1+b1
> > -ii  linux-kbuild-6.0 6.0.2-1+b1
> > -ii  linux-libc-dev:amd64 6.0.2-1+b1
> > -ii  linux-perf   6.0.2-1+b1
> > +ii  linux-image-amd646.0.3-1
> > +ii  linux-kbuild-6.0 6.0.3-1
> > +ii  linux-libc-dev:amd64 6.0.3-1
> > +ii  linux-perf   6.0.3-1
> > -ii  login1:4.12.3+dfsg1-1
> > +ii  login1:4.12.3+dfsg1-2
> > -ii  openjdk-8-jre:amd64  8u342-b07-1
> > -ii  openjdk-8-jre-headless:amd64 8u342-b07-1
> > +ii  openjdk-8-jre:amd64  8u352-ga-1
> > +ii  openjdk-8-jre-headless:am

Bug#1022267: mpv: No sound played from TV live-stream or music file

[Sedat Dilek]

Package: mpv
Version: 0.34.1-1+b5
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

after my daily upgrade yesterday I cannot hear any sound when using mpv.

Like playing MP4 audio-files or TV live-stream...

$ mpv https://www.zdf.de/sender/zdf/zdf-live-beitrag-100.html
EDL: source file 
'https://zdf-hls-15.akamaized.net/hls/live/2016498-b/de/1b5fb462ae0547adb9b368a4363428a9/4/4.m3u8'
 has unknown duration.
EDL: source file 
'https://zdf-hls-15.akamaized.net/hls/live/2016498/de/1b5fb462ae0547adb9b368a4363428a9/5/5.m3u8'
 has unknown duration.
 (+) Video --vid=1 (h264 1280x720 50.000fps)
 (+) Audio --aid=1 (aac 2ch 48000Hz)
AO: [pulse] 48000Hz stereo 2ch float
VO: [gpu] 1280x720 yuv420p


Here the list of upgraded packages:

# git diff packages_2669.txt packages.txt | egrep '^[+|-]ii' | column -t
-ii  bpftool  7.0.0+6.0.2-1+b1
+ii  bpftool  7.0.0+6.0.3-1
-ii  fuse33.11.0-1
+ii  fuse33.12.0-1
-ii  gstreamer1.0-gtk3:amd64  1.20.3-1
+ii  gstreamer1.0-gtk3:amd64  1.20.3-1+b1
-ii  gstreamer1.0-plugins-good:amd64  1.20.3-1
+ii  gstreamer1.0-plugins-good:amd64  1.20.3-1+b1
-ii  gstreamer1.0-pulseaudio:amd641.20.3-1
+ii  gstreamer1.0-pulseaudio:amd641.20.3-1+b1
-ii  libextutils-depends-perl 0.8001-1
+ii  libextutils-depends-perl 0.8001-2
+ii  libflac12:amd64  1.4.1-2
-ii  libfuse3-3:amd64 3.11.0-1
+ii  libfuse3-3:amd64 3.12.0-1
-ii  libmath-base85-perl  0.5+dfsg-1
+ii  libmath-base85-perl  0.5+dfsg-2
-ii  libqca-qt5-2:amd64   2.3.4-1+b1
-ii  libqca-qt5-2-dev 2.3.4-1+b1
-ii  libqca-qt5-2-plugins:amd64   2.3.4-1+b1
+ii  libqca-qt5-2:amd64   2.3.5-1
+ii  libqca-qt5-2-dev 2.3.5-1
+ii  libqca-qt5-2-plugins:amd64   2.3.5-1
-ii  libsndfile1:amd641.1.0-3
+ii  libsndfile1:amd641.1.0-3+b1
-ii  libstring-shellquote-perl1.04-2
+ii  libstring-shellquote-perl1.04-3
-ii  libzmq5:amd644.3.4-3
+ii  libzmq5:amd644.3.4-4
-ii  linux-compiler-gcc-12-x866.0.2-1+b1
-ii  linux-headers-6.0.0-1-amd64  6.0.2-1+b1
-ii  linux-headers-6.0.0-1-common 6.0.2-1
-ii  linux-headers-amd64  6.0.2-1+b1
-ii  linux-image-6.0.0-1-amd646.0.2-1+b1
+ii  linux-compiler-gcc-12-x866.0.3-1
+ii  linux-headers-6.0.0-2-amd64  6.0.3-1
+ii  linux-headers-6.0.0-2-common 6.0.3-1
+ii  linux-headers-amd64  6.0.3-1
+ii  linux-image-6.0.0-2-amd646.0.3-1
-ii  linux-image-amd646.0.2-1+b1
-ii  linux-kbuild-6.0 6.0.2-1+b1
-ii  linux-libc-dev:amd64 6.0.2-1+b1
-ii  linux-perf   6.0.2-1+b1
+ii  linux-image-amd646.0.3-1
+ii  linux-kbuild-6.0 6.0.3-1
+ii  linux-libc-dev:amd64 6.0.3-1
+ii  linux-perf   6.0.3-1
-ii  login1:4.12.3+dfsg1-1
+ii  login1:4.12.3+dfsg1-2
-ii  openjdk-8-jre:amd64  8u342-b07-1
-ii  openjdk-8-jre-headless:amd64 8u342-b07-1
+ii  openjdk-8-jre:amd64  8u352-ga-1
+ii  openjdk-8-jre-headless:amd64 8u352-ga-1
-ii  passwd   1:4.12.3+dfsg1-1
+ii  passwd   1:4.12.3+dfsg1-2
-ii  postgresql   15+244+nmu1
+ii  postgresql   15+245
-ii  postgresql-1414.5-2
+ii  postgresql-1414.5-3
-ii  postgresql-client-14 14.5-2
+ii  postgresql-client-14 14.5-3
-ii  postgresql-client-common 244+nmu1
-ii  postgresql-common244+nmu1
+ii  postgresql-client-common 245
+ii  postgresql-common245
-ii  python3-sip  4.19.25+dfsg-3+b2
+ii  python3-sip  4.19.25+dfsg-4
-ii  python3-tz   2022.4-1
+ii  python3-tz   2022.4-2
-ii  vnstat   2.9-1+b1
-ii  vnstati  2.9-1+b1
+ii  vnstat   2.10-1
+ii  vnstati  2.10-1

Might help to know.

Output of pactl:

$ pactl info 
Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 238
Tile Size: 65472
User Name: dileks
Host Name: iniza
Server Name: PulseAudio (on PipeWire 0.3.59)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-_00_1b.0.analog-stereo
Default Source: alsa_input.pci-_00_1b.0.analog-stereo
Cookie: ee25:0423

If you have any hint to check why there is no audio(-stream) or need further 
information, please let me know.

Thanks.

Best regards,

Bug#1008735: base-files: /etc/os-release should contain VERSION variables for testing and unstable

[Sedat Dilek]

On Thu, Oct 13, 2022 at 4:03 PM Masahiro Yamada  wrote:
>
> Hi Sedat,
>
> Sorry for my late replay.
>
>
> On Mon, Oct 3, 2022 at 6:56 PM Sedat Dilek  wrote:
> >
> > [ CC linux-kbuild folks (see [0] ]
>
>
>
> Can you give me more context of this email?
>
>
>
>
> > Hi,
> >
> > I am using Debian/unstable AMD64 and doing Linux-kernel upstream
> > development and testing.
> >
> > People using bindeb-pkg (mkdebian) from Linux-kernel sources
> > (scripts/packages) to build and test their selfmade Debian kernels get
> > a now a "n/a" for distribution.
>
>
>
> Right, if I try the latest sid,
> "lsb_release -cs" returns "n/a".
> It returned "sid" before IIRC.
>
>
> What was changed in Debian?
> Any change in the lsb_release program?
>

Hi Masahiro San,

The Debian maintainer(s) changed the co-working of these packages:

root# dpkg -l | egrep 'base-files|lsb-release' | awk '/^ii/ {print $1
" " $2 " " $3}' | column -t
ii  base-files   12.3
ii  lsb-release  12.0-1
ii  lsb-release-minimal  12.0-1

My findings:
First, /usr/bin/lsb_release-11.4 (python) VS.
/usr/bin/lsb_release-12.0 (shell) - both files attached.
Second, version 12.0 checks now explicitly for values in /etc/os-release.
As a side note: All these changes were not mentioned in lsb-release
debian/changelog.

The easiest way to fix this is to add...

VERSION_ID=sid (or unstable)

...to /etc/os-release file.

Just for the sake of technical correctness:
"sid" or "unstable" is not a numerical value - it's a string.

In version 12.3 of base-files "VERSION_CODENAME=bookworm" was added on
users' request.

Last checks:

Original (base-files version 12.0):

[ /etc/os-release ]
PRETTY_NAME="Debian GNU/Linux bookworm/sid"
NAME="Debian GNU/Linux"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/;
SUPPORT_URL="https://www.debian.org/support;
BUG_REPORT_URL="https://bugs.debian.org/;

root# lsb_release --all
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux bookworm/sid
Release:n/a
Codename:   bookworm

Modified:

[ /etc/os-release ]
PRETTY_NAME="Debian GNU/Linux bookworm/sid"
NAME="Debian GNU/Linux"
VERSION_CODENAME=bookworm
VERSION_ID=sid
ID=debian
HOME_URL="https://www.debian.org/;
SUPPORT_URL="https://www.debian.org/support;
BUG_REPORT_URL="https://bugs.debian.org/;

root# lsb_release --all
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux bookworm/sid
Release:sid
Codename:   bookworm

More comments see https://bugs.debian.org/1008735.

-Sedat-

>
>
>
>
>
> >
> > Background (see [1]):
> >
> > [ scripts/package/mkdebian ]
> >
> > # Try to determine distribution
> > if [ -n "$KDEB_CHANGELOG_DIST" ]; then
> > distribution=$KDEB_CHANGELOG_DIST
> > # In some cases lsb_release returns the codename as n/a, which breaks
> > dpkg-parsechangelog
> > elif distribution=$(lsb_release -cs 2>/dev/null) && [ -n
> > "$distribution" ] && [ "$distribution" != "n/a" ]; then
> > : # nothing to do in this case
> > else
> > distribution="unstable"
> > echo >&2 "Using default distribution of 'unstable' in the changelog"
> > echo >&2 "Install lsb-release or set \$KDEB_CHANGELOG_DIST 
> > explicitly"
> > fi
> >
> > Personally, I set hardcoded in my kernel build-script as a workaround:
> >
> > distribution="bookworm"
> >
> > Gioele suggested me to enrich /etc/os-release with:
> >
> > VERSION_ID=unstable <--- XXX: I prefer sid because of PRETTY_NAME and
> > it's shorter
> > VERSION_CODENAME=bookworm
> >
> > In the end the file looks like:
> >
> > PRETTY_NAME="Debian GNU/Linux bookworm/sid"
> > NAME="Debian GNU/Linux"
> > ID=debian
> > VERSION_ID=sid
> > VERSION_CODENAME=bookworm
> > HOME_URL="https://www.debian.org/;
> > SUPPORT_URL="https://www.debian.org/support;
> > BUG_REPORT_URL="https://bugs.debian.org/;
> >
> > ...and this seems to work:
> >
> > # lsb_release -cs
> > No LSB modules are available.
> > bookworm
> >
> > Please, provide a solution not to break workflows that were successful
> > for years.
> >
> > Thanks.
> >
> > Best regards,
> > -Sedat-
> >
> > [0] 
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS#n11005
> > [1] 
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/scripts/package/mkdebian#n123
>
>
>
> --
> Best Regards
> Masahiro Yamada


lsb_release-11.4
Description: Unix manual page


lsb_release-12.0
Description: Binary data

Bug#1008735: base-files: /etc/os-release should contain VERSION variables for testing and unstable

[Sedat Dilek]

[ CC linux-kbuild folks (see [0] ]

Hi,

I am using Debian/unstable AMD64 and doing Linux-kernel upstream
development and testing.

People using bindeb-pkg (mkdebian) from Linux-kernel sources
(scripts/packages) to build and test their selfmade Debian kernels get
a now a "n/a" for distribution.

Background (see [1]):

[ scripts/package/mkdebian ]

# Try to determine distribution
if [ -n "$KDEB_CHANGELOG_DIST" ]; then
distribution=$KDEB_CHANGELOG_DIST
# In some cases lsb_release returns the codename as n/a, which breaks
dpkg-parsechangelog
elif distribution=$(lsb_release -cs 2>/dev/null) && [ -n
"$distribution" ] && [ "$distribution" != "n/a" ]; then
: # nothing to do in this case
else
distribution="unstable"
echo >&2 "Using default distribution of 'unstable' in the changelog"
echo >&2 "Install lsb-release or set \$KDEB_CHANGELOG_DIST explicitly"
fi

Personally, I set hardcoded in my kernel build-script as a workaround:

distribution="bookworm"

Gioele suggested me to enrich /etc/os-release with:

VERSION_ID=unstable <--- XXX: I prefer sid because of PRETTY_NAME and
it's shorter
VERSION_CODENAME=bookworm

In the end the file looks like:

PRETTY_NAME="Debian GNU/Linux bookworm/sid"
NAME="Debian GNU/Linux"
ID=debian
VERSION_ID=sid
VERSION_CODENAME=bookworm
HOME_URL="https://www.debian.org/;
SUPPORT_URL="https://www.debian.org/support;
BUG_REPORT_URL="https://bugs.debian.org/;

...and this seems to work:

# lsb_release -cs
No LSB modules are available.
bookworm

Please, provide a solution not to break workflows that were successful
for years.

Thanks.

Best regards,
-Sedat-

[0] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS#n11005
[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/scripts/package/mkdebian#n123

Bug#1019470: git: Bump version to 2.37.3

[Sedat Dilek]

Hi,

friendly ping.

Best regards,
-Sedat-

Bug#1013276: Alsa clients using the wrong plugin if pulseaudio is installed

[Sedat Dilek]

I removed this part from my custom /etc/pulse/default.pa file:

### Automatically move streams to the default sink if the sink they are
### connected to dies, similar for sources
load-module module-rescue-streams

Now, I have a microphone again!

-sed@-

Bug#1013276: Alsa clients using the wrong plugin if pulseaudio is installed

[Sedat Dilek]

I am awfully sorry - Webcam works!

user$ LANG=C wpctl status | grep -i webcam
│  32. WebCam SC-13HDL11431N   [v4l2]
│  38. WebCam SC-13HDL11431N   [v4l2]
│  *   40. WebCam SC-13HDL11431N (V4L2)

user$ LANG=C wpctl inspect 40
id 40, type PipeWire:Interface:Node
   api.v4l2.cap.bus_info = "usb-:00:1a.0-1.4"
   api.v4l2.cap.capabilities = "84a1"
   api.v4l2.cap.card = "WebCam SC-13HDL11431N: WebCam S"
   api.v4l2.cap.device-caps = "0421"
   api.v4l2.cap.driver = "uvcvideo"
   api.v4l2.cap.version = "5.19.7"
   api.v4l2.path = "/dev/video0"
 * client.id = "31"
   clock.quantum-limit = "8192"
   device.api = "v4l2"
 * device.id = "38"
   device.product.id = "0x101"
   device.vendor.id = "0x223"
 * factory.id = "10"
   factory.name = "api.v4l2.source"
 * media.class = "Video/Source"
 * media.role = "Camera"
 * node.description = "WebCam SC-13HDL11431N (V4L2)"
   node.driver = "true"
 * node.name = "v4l2_input.pci-_00_1a.0-usb-0_1.4_1.0"
 * node.nick = "WebCam SC-13HDL11431N"
   node.pause-on-idle = "false"
 * object.path = "v4l2:/dev/video0"
 * object.serial = "110"
 * priority.session = "1000"

user$ cvlc v4l2:///dev/video0
VLC media player 3.0.17.4 Vetinari (revision 3.0.13-8-g41878ff4f2)
[55c2fd415150] dummy interface: using the dummy interface module...
[7f25ec004fd0] gl gl: Initialized libplacebo v4.192.1 (API v192)
[7f25fc03d460] xcb_window window error: X server failure
...

I needed to turn on the lights in my living-room.

/me ashamed.

-Sedat-

Bug#1013276: Alsa clients using the wrong plugin if pulseaudio is installed

[Sedat Dilek]

Here on KDE/Plasma v5.25.4 (Wayland) it was sufficient just to remove
/etc/alsa/conf.d/99-pulse.conf only;

root# LC_ALL=C ll /etc/alsa/conf.d/99-pulse.conf
/etc/alsa/conf.d/50-pulseaudio.conf
ls: cannot access '/etc/alsa/conf.d/99-pulse.conf': No such file or directory
lrwxrwxrwx 1 root root 46 Jul  6 04:20
/etc/alsa/conf.d/50-pulseaudio.conf ->
/usr/share/alsa/alsa.conf.d/50-pulseaudio.conf

Looks like the config-files have different origin:

root# dpkg -S /etc/alsa/conf.d/50-pulseaudio.conf
/etc/alsa/conf.d/99-pulse.conf
libasound2-plugins:amd64: /etc/alsa/conf.d/50-pulseaudio.conf
pulseaudio: /etc/alsa/conf.d/99-pulse.conf

Maybe, talk with the Debian pulseaudio?

* Might be a different issue (after switching to pipewire/0.3.58-1):

BTW, in my KDE audio-settings I do NOT see a microphone.

Same with Webcam:

root# v4l2-ctl --list-devices

WebCam SC-13HDL11431N: WebCam S (usb-:00:1a.0-1.4):
   /dev/video0
   /dev/video1
   /dev/media0

$ cvlc v4l2:///dev/video0

^^ No picture.

$ LC_ALL=C systemctl --user stop wireplumber.service
$ LC_ALL=C systemctl --user start wireplumber.service

$ LC_ALL=C systemctl --user status wireplumber.service
* wireplumber.service - Multimedia Service Session Manager
Loaded: loaded (/usr/lib/systemd/user/wireplumber.service;
enabled; preset: enabled)
Active: active (running) since Sat 2022-09-17 22:02:42 CEST; 2s ago
  Main PID: 3633 (wireplumber)
 Tasks: 5 (limit: 9359)
Memory: 3.9M
   CPU: 140ms
CGroup: 
/user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
`-3633 /usr/bin/wireplumber

Sep 17 22:02:42 iniza systemd[1776]: Started Multimedia Service Session Manager.
Sep 17 22:02:42 iniza wireplumber[3633]: Failed to set scheduler
settings: Die Operation ist nicht erlaubt
Sep 17 22:02:42 iniza wireplumber[3633]: reserve-device plugin is not
connected to D-Bus, disabling device reservation
Sep 17 22:02:42 iniza wireplumber[3633]: SPA handle
'api.libcamera.enum.manager' could not be loaded; is it installed?
Sep 17 22:02:42 iniza wireplumber[3633]: PipeWire's libcamera SPA
missing or broken. libcamera not supported.

Just wanna let you know.

Regards,
-Sedat-

Bug#1013276: Alsa clients using the wrong plugin if pulseaudio is installed

[Sedat Dilek]

Hi,

I upgraded to pipewire/0.3.58-1 on my Debian/unstable AMD64 box.

This removed pipewire-pulse/0.3.57-1.

After this I was not able to listen to audio when doing
video-streaming in Firefox.

Please, point Debian/unstable folks to remove these files (as stated
in the Ubuntu BR):

root# rm -v /etc/alsa/conf.d/99-pulse.conf /etc/alsa/conf.d/50-pulseaudio.conf

This SOLVED the issue (unsure if 50-pulseaudio.conf needs to be
removed as well).

Some inspecting...

[ PACTL ]

user$ LANG=C pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 6
Tile Size: 65472
User Name: dileks
Host Name: iniza
Server Name: pulseaudio
Server Version: 15.0
Default Sample Specification: s16le 2ch 44100Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-_00_1b.0.analog-stereo
Default Source: alsa_input.pci-_00_1b.0.analog-stereo
Cookie: 10fd:1cb5

user$ LANG=C wpctl status
PipeWire 'pipewire-0' [0.3.58, dileks@iniza, cookie:479679219]
└─ Clients:
   31. WirePlumber [0.3.58, dileks@iniza, pid:1791]
   32. WirePlumber [export][0.3.58, dileks@iniza, pid:1791]
   43. xdg-desktop-portal  [0.3.58, dileks@iniza, pid:2165]
   44. wpctl   [0.3.58, dileks@iniza, pid:6084]

Audio
├─ Devices:
│  40. Internes Audio  [alsa]
│
├─ Sinks:
│
├─ Sink endpoints:
│
├─ Sources:
│
├─ Source endpoints:
│
└─ Streams:

Video
├─ Devices:
│  38. WebCam SC-13HDL11431N   [v4l2]
│  39. WebCam SC-13HDL11431N   [v4l2]
│
├─ Sinks:
│
├─ Sink endpoints:
│
├─ Sources:
│  *   41. WebCam SC-13HDL11431N (V4L2)
│
├─ Source endpoints:
│
└─ Streams:

Settings
└─ Default Configured Node Names:

user$ LANG=C wpctl inspect 40
id 40, type PipeWire:Interface:Device
   alsa.card = "0"
   alsa.card_name = "HDA Intel PCH"
   alsa.driver_name = "snd_hda_intel"
   alsa.long_card_name = "HDA Intel PCH at 0xf070 irq 34"
   api.acp.auto-port = "false"
   api.acp.auto-profile = "false"
   api.alsa.card = "0"
   api.alsa.card.longname = "HDA Intel PCH at 0xf070 irq 34"
   api.alsa.card.name = "HDA Intel PCH"
   api.alsa.path = "hw:0"
   api.alsa.use-acp = "true"
 * client.id = "32"
 * device.api = "alsa"
   device.bus = "pci"
   device.bus-path = "pci-:00:1b.0"
 * device.description = "Internes Audio"
   device.enum.api = "udev"
   device.form-factor = "internal"
   device.icon-name = "audio-card-analog-pci"
 * device.name = "alsa_card.pci-_00_1b.0"
 * device.nick = "HDA Intel PCH"
   device.plugged.usec = "36336190"
   device.product.id = "0x1c20"
   device.product.name = "6 Series/C200 Series Chipset Family High
Definition Audio Controller"
   device.string = "0"
   device.subsystem = "sound"
   device.sysfs.path = "/sys/devices/pci:00/:00:1b.0/sound/card0"
   device.vendor.id = "0x8086"
   device.vendor.name = "Intel Corporation"
 * factory.id = "14"
 * media.class = "Audio/Device"
   object.path = "alsa:pcm:0"
 * object.serial = "40"

[ ALSA ]

root# LC_ALL=C aplay --list-devices
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
 Subdevices: 1/1
 Subdevice #0: subdevice #0

root# aplay --list-pcms | egrep -A1 'default:'
default:CARD=PCH
   HDA Intel PCH, ALC269VC Analog
--
sysdefault:CARD=PCH
   HDA Intel PCH, ALC269VC Analog

root# aplay --list-pcms | egrep -A1 'plughw:'
plughw:CARD=PCH,DEV=0
   HDA Intel PCH, ALC269VC Analog
--
plughw:CARD=PCH,DEV=3
   HDA Intel PCH, HDMI 0

Thanks.

Regards,
-Sedat-

[1] https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1975823
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013276

Bug#1019470: git: Bump version to 2.37.3

[Sedat Dilek]

Package: git
Version: 1:2.37.2-1
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

please update git to version 2.37.3.
It's a maintenance release containing several bug-fixes.

Thanks.

Best regards,
-Sedat-

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

Kernel: Linux 5.19.7-1-amd64-clang15-kcfi (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 git depends on:
ii  git-man  1:2.37.2-1
ii  libc62.34-7
ii  libcurl3-gnutls  7.85.0-1
ii  liberror-perl0.17029-1
ii  libexpat12.4.8-1
ii  libpcre2-8-0 10.40-1
ii  perl 5.34.0-5
ii  zlib1g   1:1.2.11.dfsg-4.1

Versions of packages git recommends:
ii  ca-certificates  20211016
ii  less 590-1
ii  openssh-client [ssh-client]  1:9.0p1-1+b1
ii  patch2.7.6-7

Versions of packages git suggests:
ii  gettext-base  0.21-9
pn  git-cvs   
pn  git-daemon-run | git-daemon-sysvinit  
pn  git-doc   
ii  git-email 1:2.37.2-1
pn  git-gui   
pn  git-mediawiki 
pn  git-svn   
pn  gitk  
pn  gitweb

-- no debconf information

Bug#1016723: git: Bump version to 2.37.1

[Sedat Dilek]

Hi,

git version 2.37.2 was released.

Just wanna let you know.

Best regards,
-Sedat-

[1] https://git.kernel.org/pub/scm/git/git.git/tag/?h=v2.37.2

Bug#1016723: git: Bump version to 2.37.1

[Sedat Dilek]

Package: git
Version: 1:2.36.1-1
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

can you please upgrade git to version 2.37.1?

This includes several bug-fixes.

I am OK to wait for version 2.37.2 - looks like this maintenance-release will 
be done soon.

Thanks.

Regards,
-Sedat-

[1] https://git.kernel.org/pub/scm/git/git.git/tag/?h=v2.37.1
[2] https://git.kernel.org/pub/scm/git/git.git/log/?h=maint

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

Kernel: Linux 5.19.0-2-amd64-clang15-kcfi (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 git depends on:
ii  git-man  1:2.36.1-1
ii  libc62.33-8
ii  libcurl3-gnutls  7.84.0-2
ii  liberror-perl0.17029-1
ii  libexpat12.4.8-1
ii  libpcre2-8-0 10.40-1
ii  perl 5.34.0-5
ii  zlib1g   1:1.2.11.dfsg-4

Versions of packages git recommends:
ii  ca-certificates  20211016
ii  less 590-1
ii  openssh-client [ssh-client]  1:9.0p1-1+b1
ii  patch2.7.6-7

Versions of packages git suggests:
ii  gettext-base  0.21-6
pn  git-cvs   
pn  git-daemon-run | git-daemon-sysvinit  
pn  git-doc   
ii  git-email 1:2.36.1-1
pn  git-gui   
pn  git-mediawiki 
pn  git-svn   
pn  gitk  
pn  gitweb

-- no debconf information

Bug#1014319: depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or directory

[Sedat Dilek]

Hi,

with the fix from Sven Joachim applied to mkinitramfs I do not see the
warning of kmod-30.

Feel free to add my:

Tested-by: Sedat Dilek  # Debian/unstable AMD64

Thanks.

Regards,
-Sedat-

Bug#1011605: clang-14: Bump version to 14.0.4

[Sedat Dilek]

Here we go: Announcement and Git-tag.

-Sedat-

[1] https://discourse.llvm.org/t/llvm-14-0-4-release/62751
[2] https://github.com/llvm/llvm-project/releases/tag/llvmorg-14.0.4

Bug#1011605: clang-14: Bump version to 14.0.4

[Sedat Dilek]

Package: clang-14
Version: 1:14.0.4~++20220524063032+fecfc8394484-1~exp1~20220524183114.140
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

LLVM version 14.0.4 was released a few hours ago.

Please, bump the version.

Thanks.

Regards,
-Sedat-

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

Kernel: Linux 5.18.0-1-amd64-clang14-lto (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 clang-14 depends on:
ii  binutils   2.38-4
ii  libc6  2.33-7
ii  libc6-dev  2.33-7
ii  libclang-  1:14.0.4~++20220524063032+fecfc8394484-1~exp1~20220524183114.140
ii  libclang-  1:14.0.4~++20220524063032+fecfc8394484-1~exp1~20220524183114.140
ii  libclang1  1:14.0.4~++20220524063032+fecfc8394484-1~exp1~20220524183114.140
ii  libgcc-11  11.3.0-3
ii  libgcc-s1  12.1.0-2
ii  libllvm14  1:14.0.4~++20220524063032+fecfc8394484-1~exp1~20220524183114.140
ii  libobjc-1  11.3.0-3
ii  libstdc++  11.3.0-3
ii  libstdc++  12.1.0-2
ii  llvm-14-l  1:14.0.4~++20220524063032+fecfc8394484-1~exp1~20220524183114.140

Versions of packages clang-14 recommends:
ii  llvm-14-d  1:14.0.4~++20220524063032+fecfc8394484-1~exp1~20220524183114.140
ii  python33.10.4-1+b1

Versions of packages clang-14 suggests:
pn  clang-14-doc  

-- no debconf information

Bug#1010720: git: Bump version to 2.36.1

[Sedat Dilek]

Package: git
Version: 1:2.36.0-1
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

can you please bump git to version 2.36.1?
It contains several bug-fixes.

Thanks.

Regards,
-Sedat-

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

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

Versions of packages git depends on:
ii  git-man  1:2.36.0-1
ii  libc62.33-7
ii  libcurl3-gnutls  7.83.0-1
ii  liberror-perl0.17029-1
ii  libexpat12.4.8-1
ii  libpcre2-8-0 10.40-1
ii  perl 5.34.0-4
ii  zlib1g   1:1.2.11.dfsg-4

Versions of packages git recommends:
ii  ca-certificates  20211016
ii  less 590-1
ii  openssh-client [ssh-client]  1:9.0p1-1
ii  patch2.7.6-7

Versions of packages git suggests:
ii  gettext-base  0.21-6
pn  git-cvs   
pn  git-daemon-run | git-daemon-sysvinit  
pn  git-doc   
ii  git-email 1:2.36.0-1
pn  git-gui   
pn  git-mediawiki 
pn  git-svn   
pn  gitk  
pn  gitweb

-- no debconf information

Bug#1009170: perl: Bump version to 5.34.1

[Sedat Dilek]

Package: perl
Version: 5.34.0-3
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

perl version 5.34.1 was released 27 days ago (see [1]) and
includes several bug-fixes (see [2]).

Please bump version to 5.34.1.

Thanks.

Regards,
- Sedat -

P.S.: If possible integrate the diff from Debian bug #1009149.

[1] https://github.com/Perl/perl5/releases/tag/v5.34.1
[2] https://github.com/Perl/perl5/compare/v5.34.0...v5.34.1
[3] https://bugs.debian.org/1009149

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

Kernel: Linux 5.17.1-6-amd64-clang14-lto (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 perl depends on:
ii  dpkg   1.21.7
ii  libperl5.345.34.0-3
ii  perl-base  5.34.0-3
ii  perl-modules-5.34  5.34.0-3

Versions of packages perl recommends:
ii  netbase  6.3

Versions of packages perl suggests:
pn  libtap-harness-archive-perl 
pn  libterm-readline-gnu-perl | libterm-readline-perl-perl  
ii  make4.3-4.1
pn  perl-doc

-- no debconf information

Bug#1009149: libperl5.34: Upstream patches "skip using gcc brace groups for STMT_START/END"

[Sedat Dilek]

Package: libperl5.34
Version: 5.34.0-3
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

when building perf tool out of the Linux-kernel sources tree we see 
build-errors with Clang.

When using Debian's perl-5.34 we need to add -Wno-compound-token-split-by-macro 
as compiler-flag.
This is due to -Werror is set explicitly.

For details see [1] and [2].

I hit the issue in combination with Debian's LLVM/Clang v14.

There are two commits from upstream fixing the issue.

"skip using gcc brace groups for STMT_START/END"
https://github.com/Perl/perl5/commit/7169efc77525df70484a824bff4ceebd1fafc760

"Partially Revert "skip using gcc brace groups for STMT_START/END""
https://github.com/Perl/perl5/commit/e08ee3cb66f362c4901846a46014cfdfcd60326c

Latest perl v5.34.1 seems not to have these changes:
https://github.com/Perl/perl5/compare/v5.34.0...v5.34.1

To summarize the total diff of above 2 commits is related to perl.h header-file 
only:

# git diff /usr/lib/x86_64-linux-gnu/perl/5.34.0/CORE/perl.h.orig 
/usr/lib/x86_64-linux-gnu/perl/5.34.0/CORE/perl.h
diff --git a/usr/lib/x86_64-linux-gnu/perl/5.34.0/CORE/perl.h.orig 
b/usr/lib/x86_64-linux-gnu/perl/5.34.0/CORE/perl.h
index 17a21a1c4..bd575fe08 100644
--- a/usr/lib/x86_64-linux-gnu/perl/5.34.0/CORE/perl.h.orig
+++ b/usr/lib/x86_64-linux-gnu/perl/5.34.0/CORE/perl.h
@@ -733,13 +733,8 @@ Example usage:
  Trying to select a version that gives no warnings...
 */
 #if !(defined(STMT_START) && defined(STMT_END))
-# ifdef PERL_USE_GCC_BRACE_GROUPS
-#   define STMT_START  (void)( /* gcc supports "({ STATEMENTS; })" */
-#   define STMT_END)
-# else
 #   define STMT_START  do
 #   define STMT_ENDwhile (0)
-# endif
 #endif
 
 #ifndef BYTEORDER  /* Should never happen -- byteorder is in config.h */

With this diff applied and removing -Wno-compound-token-split-by-macro as 
compiler-flag
I am able to build perf tool successfully with LLVM-14.

For the records: These 2 patches against Linux-kernel from [2] are needed:

1. tools build: Use $(shell ) instead of `` to get embedded libperl's ccopts
2. tools build: Filter out options and warnings not supported by clang

Can you please apply the perl.h diff?

Thanks.

Regards,
- Sedat -

[1] https://marc.info/?t=16491117234=1=2
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/log/?h=tmp.perf/urgent

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

Kernel: Linux 5.17.1-6-amd64-clang14-lto (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 libperl5.34 depends on:
ii  libbz2-1.0 1.0.8-5
ii  libc6  2.33-7
ii  libcrypt1  1:4.4.27-1.1
ii  libdb5.3   5.3.28+dfsg1-0.8
ii  libgdbm-compat41.23-1
ii  libgdbm6   1.23-1
ii  perl-modules-5.34  5.34.0-3
ii  zlib1g 1:1.2.11.dfsg-4

libperl5.34 recommends no packages.

Versions of packages libperl5.34 suggests:
ii  sensible-utils  0.0.17

-- no debconf information

Bug#1008657: clang-14: Integrate post v14.0.0 upstream patches

[Sedat Dilek]

On Wed, Mar 30, 2022 at 6:19 PM Sedat Dilek  wrote:
>
> Hi Sylvestre,
>
> Unfortunately, I did NOT get your reply from the Debian-BR-system.
>
> Furthermore, I have no user (guest) account on , so
> a MR (Merge-Request) seems not possible for me.
>
> So, I cloned the latest debian "llvm-toolchain-14" from salsa-Git.
>
> git clone https://salsa.debian.org/pkg-llvm-team/llvm-toolchain.git debian
>
> cd debian/
> git checkout origin/14 -b llvm-toolchain-14
>
> [ EDIT debian/patches/series ]
>
> git add debian/patches/series
> debian/patches/0001-libc-Add-workaround-to-avoid-breaking-users-of-span-.patch
> debian/patches/0002-libc-Re-enable-workaround-for-pre-ranges-CTAD-in-std.patch
> git commit -m 'Add libc++ patches from upstream (post version 14.0.0)'
> git format-patch --signoff -1
>
> That patch is attached here.
>
> I have not modified debian/changelog and it does not look like it is the 
> latest:
>
> $ head -10 debian/changelog
> llvm-toolchain-14 (1:14.0.0~+rc4-1) unstable; urgency=medium
>
>  * New snapshot release (rc3 isn't a thing)
>  * Add an ugly workaround for Ubuntu jammy (some python files are
> installed in local/lib)
>
> -- Sylvestre Ledru   Fri, 11 Mar 2022 18:28:07 +0100
>
> llvm-toolchain-14 (1:14.0.0~+rc2-1~exp1) unstable; urgency=medium
>
>  * New snapshot release
>
> I have not tried or checked if my patch is applied when using the
> latest orig-tarball and latest debian-tarball.
>
> Normally, I would use dsc | orig-tarball | debian-tarball from [2], [3] and 
> [4].
>
> Is that attached patch helpful for you or not?
>
> Thanks.
>
> Regards,
> - Sedat -
>
> [1] https://packages.debian.org/sid/clang-14
> [2] 
> http://deb.debian.org/debian/pool/main/l/llvm-toolchain-14/llvm-toolchain-14_14.0.0-1.dsc
> [3] 
> http://deb.debian.org/debian/pool/main/l/llvm-toolchain-14/llvm-toolchain-14_14.0.0.orig.tar.xz
> [4] 
> http://deb.debian.org/debian/pool/main/l/llvm-toolchain-14/llvm-toolchain-14_14.0.0-1.debian.tar.xz

Attached is my debdiff against latest dsc | orig-tarball |
debian-tarball as of Debian version 14.0.0-1.

Hope this is helpful.

- sed@ -


llvm-toolchain-14_14-0-0-1_1_dileks.debdiff
Description: Binary data

Bug#1008657: clang-14: Integrate post v14.0.0 upstream patches

[Sedat Dilek]

Hi Sylvestre,

Unfortunately, I did NOT get your reply from the Debian-BR-system.

Furthermore, I have no user (guest) account on , so
a MR (Merge-Request) seems not possible for me.

So, I cloned the latest debian "llvm-toolchain-14" from salsa-Git.

git clone https://salsa.debian.org/pkg-llvm-team/llvm-toolchain.git debian

cd debian/
git checkout origin/14 -b llvm-toolchain-14

[ EDIT debian/patches/series ]

git add debian/patches/series
debian/patches/0001-libc-Add-workaround-to-avoid-breaking-users-of-span-.patch
debian/patches/0002-libc-Re-enable-workaround-for-pre-ranges-CTAD-in-std.patch
git commit -m 'Add libc++ patches from upstream (post version 14.0.0)'
git format-patch --signoff -1

That patch is attached here.

I have not modified debian/changelog and it does not look like it is the latest:

$ head -10 debian/changelog
llvm-toolchain-14 (1:14.0.0~+rc4-1) unstable; urgency=medium

 * New snapshot release (rc3 isn't a thing)
 * Add an ugly workaround for Ubuntu jammy (some python files are
installed in local/lib)

-- Sylvestre Ledru   Fri, 11 Mar 2022 18:28:07 +0100

llvm-toolchain-14 (1:14.0.0~+rc2-1~exp1) unstable; urgency=medium

 * New snapshot release

I have not tried or checked if my patch is applied when using the
latest orig-tarball and latest debian-tarball.

Normally, I would use dsc | orig-tarball | debian-tarball from [2], [3] and [4].

Is that attached patch helpful for you or not?

Thanks.

Regards,
- Sedat -

[1] https://packages.debian.org/sid/clang-14
[2] 
http://deb.debian.org/debian/pool/main/l/llvm-toolchain-14/llvm-toolchain-14_14.0.0-1.dsc
[3] 
http://deb.debian.org/debian/pool/main/l/llvm-toolchain-14/llvm-toolchain-14_14.0.0.orig.tar.xz
[4] 
http://deb.debian.org/debian/pool/main/l/llvm-toolchain-14/llvm-toolchain-14_14.0.0-1.debian.tar.xz
From 3f786648773a5ce334604d7a400505fc97196226 Mon Sep 17 00:00:00 2001
From: Sedat Dilek 
Date: Wed, 30 Mar 2022 18:03:22 +0200
Subject: [PATCH] Add libc++ patches from upstream (post version 14.0.0)

Details see Debian bug #1008657
("clang-14: Integrate post v14.0.0 upstream patches")

Link: https://bugs.debian.org/1008657
Signed-off-by: Sedat Dilek 
---
 ...und-to-avoid-breaking-users-of-span-.patch | 390 ++
 ...orkaround-for-pre-ranges-CTAD-in-std.patch |  78 
 debian/patches/series |   4 +
 3 files changed, 472 insertions(+)
 create mode 100644 debian/patches/0001-libc-Add-workaround-to-avoid-breaking-users-of-span-.patch
 create mode 100644 debian/patches/0002-libc-Re-enable-workaround-for-pre-ranges-CTAD-in-std.patch

diff --git a/debian/patches/0001-libc-Add-workaround-to-avoid-breaking-users-of-span-.patch b/debian/patches/0001-libc-Add-workaround-to-avoid-breaking-users-of-span-.patch
new file mode 100644
index ..e59a56057fb2
--- /dev/null
+++ b/debian/patches/0001-libc-Add-workaround-to-avoid-breaking-users-of-span-.patch
@@ -0,0 +1,390 @@
+From add3ab7f4c8a7f25c2940889d397cbdc9f267666 Mon Sep 17 00:00:00 2001
+From: Louis Dionne 
+Date: Mon, 14 Mar 2022 11:50:02 -0400
+Subject: [PATCH] [libc++] Add workaround to avoid breaking users of 
+ when  are disabled
+
+Back in 3a208c68942e, we implemented the range-based constructor for .
+However, in doing so, we removed a previous non-standard constructor that
+we provided before shipping . Unfortunately, that breaks code that
+was relying on a range-based constructor until we ship all of .
+
+This patch reintroduces the old non-conforming constructors and tests
+that were removed in 3a208c68942e and uses them whenever  is
+not provided (e.g. in LLVM 14). This is only a temporary workaround
+until we enable  by default in C++20, which should hopefully
+happen by LLVM 15.
+
+The goal is to cherry-pick this workaround back to the LLVM 14 release
+branch, since I suspect the constructor removal may otherwise cause
+breakage out there, like the breakage I saw internally.
+
+We could have avoided this situation by waiting for C++20 to be finalized
+before shipping std::span. For example, we could have guarded it with
+something like _LIBCPP_HAS_NO_INCOMPLETE_RANGES to prevent users from
+accidentally starting to depend on it before it is stable. We did not
+have these mechanisms when std::span was first implemented, though.
+
+NOTE: This is a pretty modified version of d4c39f1ab94 since that one
+didn't apply properly onto the release/14.x branch.
+
+(cherry picked from commit d4c39f1ab94abc1dd4fff1e82dd4fa97265940e1)
+
+Differential Revision: https://reviews.llvm.org/D121739
+---
+ libcxx/include/span   |  50 ++-
+ .../containers/views/span.cons/range.pass.cpp | 141 ++
+ .../views/span.cons/range.verify.cpp  | 118 +++
+ 3 files changed, 306 insertions(+), 3 deletions(-)
+ create mode 100644 libcxx/test/libcxx/containers/views/span.cons/range.pass.cpp
+ create mode 100644 libcxx/test/libcxx/containers/views/span.cons/range.verify.cpp
+
+diff --

Bug#1008658: virtualbox: Rebuild against python3 >= 3.10

[Sedat Dilek]

Hi,

Please close this BR.

I just updated to a new version of virtualbox packages:

+ii  virtualbox 6.1.32-dfsg-1+b3
+ii  virtualbox-qt  6.1.32-dfsg-1+b3

# zcat /usr/share/doc/virtualbox/changelog.Debian.amd64.gz
virtualbox (6.1.32-dfsg-1+b3) sid; urgency=low, binary-only=yes

 * Binary-only non-maintainer upload for amd64; no source changes.
 * Python 3.10 as default

-- amd64 / i386 Build Daemon (x86-csail-01)
  Wed, 30 Mar 2022
09:07:29 +

Thanks.

Regards,
- Sedat -

Bug#1008661: python3-samba: Rebuild against python >= 3.10

[Sedat Dilek]

Package: python3-samba
Version: 2:4.13.14+dfsg-1+b2
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

Debian/unstable now has python version 3.10.4-1 as default python / python3.

An update fails like that:

[ python3-samba ]
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 python3-samba : Depends: python3 (< 3.10) but 3.10.4-1 is to be installed
E: Unable to correct problems, you have held broken packages.

NOTE: The samba-common-bin package also gets removed - looks like there are 
dependencies to python3-samba?

Please, rebuild against python >= 3.10.

Thanks.

Regards,
- Sedat -

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

Kernel: Linux 5.17.0-3-amd64-clang14-lto (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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

Bug#1008660: rhythmbox-plugins: Rebuild against python >= 3.10

[Sedat Dilek]

Package: rhythmbox-plugins
Version: 3.4.4-5
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

Debian/unstable has updated python to version 3.10.4-1 and is now default for 
python and python3.

An upgrade fails like this:

[ rhythmbox-plugins ]
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 rhythmbox-plugins : Depends: python3 (< 3.10) but 3.10.4-1 is to be installed
E: Unable to correct problems, you have held broken packages.

NOTE: As rhythmbox-plugins is in the depends list of gnome meta-package, gnome 
package also gets removed.

Please, rebuild against python >= 3.10.

Thanks.

Regards,
- Sedat -


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

Kernel: Linux 5.17.0-3-amd64-clang14-lto (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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

Bug#1008078: zstd: Bump version to 1.4.10

[Sedat Dilek]

On Wed, Mar 30, 2022 at 11:21 AM Peter Pentchev  wrote:
>
> On Wed, Mar 30, 2022 at 10:50:09AM +0200, Sedat Dilek wrote:
> > Hi,
> >
> > Friendly ping...
> >
> > BTW, where is the packaging happening today?
> >
> > dsc file says:
> >
> > Vcs-Browser: https://salsa.debian.org/med-team/libzstd
> > Vcs-Git: https://salsa.debian.org/med-team/libzstd.git
> [snip]
> > Can you please update The Vcs-* fields with the new version?
>
> Oooof, good catch! I forgot to update that, thanks a lot!
>
> > Just for the records:
> >
> > zstd v1.4.10 has many bug-fixes :-).
>
> Right... sorry, I am slowly getting 'round to that.
>
> Actually, I was about to ask you, since there are other people who would
> like to see libzstd 1.5 in Debian: does your use case require 1.4, or
> can it work with 1.5, too? If you do require 1.4, then there will
> probably have to be a separate package for that and it will have to go
> through the NEW queue, since I'd like to update libzstd itself to 1.5
> some time soon. But anyway, the first step will certainly have to be to
> update the existing package to 1.4.10; I'll try to do that in the next
> couple of days, sorry for the delay.
>

Hi Peter,

Thanks for the fast response.

I prefer to see v1.4.10 in Debian first and later v1.5.x.

According to Nick Terell - maintainer of ZSTD in the Linux-kernel -
v1.5.x has a lot of benefits and speed improvements.
He wants to integrate that as an API update in a later Linux kernel version.
Unfortunately, I have no numbers for you but [3] has.

I can not imagine how much work it is to have a DSFG-free version of
any ZSTD version in Debian.

So, I am happy with version 1.4.10 :-).

Thanks for supporting ZSTD!

Regards and best wishes,
- Sedat -

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS#n21823
[2] https://marc.info/?l=linux-kernel=164616178411144=2
[3] https://github.com/facebook/zstd/blob/dev/README.md

> G'luck,
> Peter
>
> --
> Peter Pentchev  r...@ringlet.net r...@debian.org p...@storpool.com
> PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
> Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13

Bug#1008658: virtualbox: Rebuild against python3 >= 3.10

[Sedat Dilek]

Package: virtualbox-dkms
Version: 6.1.32-dfsg-1+b2
Severity: normal
File: virtualbox
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

Debian/unstable now has python version 3.10.4-1 as default python / python3.

An update fails like that:

[ virtualbox ]
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 virtualbox : Depends: python3 (< 3.10) but 3.10.4-1 is to be installed
  Recommends: virtualbox-qt (= 6.1.32-dfsg-1+b2) but it is not 
going to be installed
E: Unable to correct problems, you have held broken packages.

Please rebuild against python version >= 3.10.

Note: Please change Package: from virtualbox-dkms to  virtualbox.

root# dpkg -l | grep virtualbox | awk '{print $1 " " $2 " " $3}' | column -t
rc  virtualbox   6.1.32-dfsg-1+b2
ii  virtualbox-dkms  6.1.32-dfsg-1+b2

Thanks.

Regards,
- Sedat -

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

Kernel: Linux 5.17.0-3-amd64-clang14-lto (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 virtualbox-dkms depends on:
ii  dkms  2.8.7-2

Versions of packages virtualbox-dkms recommends:
pn  virtualbox  

virtualbox-dkms suggests no packages.

-- no debconf information

Bug#1008657: clang-14: Integrate post v14.0.0 upstream patches

[Sedat Dilek]

Package: clang-14
Version: 1:14.0.0-1
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Hi Sylvestre,

User ldionne requests in [1] to integrate some important libc++ fixes:

> We shipped LLVM 14 with an unfortunate regression in std::span which makes 
> adoption of LLVM 14 somewhat difficult in large code bases.
> Long story short, some valid code won’t compile anymore, and while 
> workarounds exist, it’s a bit painful and it really shouldn’t be necessary 
> since the code is 100% fine from a user’s perspective.
> This is my fault, I let that slip into the release, did not realize it was 
> going to have the impact it has, and my fixes missed the final RC by a couple 
> of days
> Had I known the impact, I would have made this a release blocker.

It's about these 2 commits:

$ cd /path/to/llvm-project/git

$ git log --oneline tags/llvmorg-14.0.0..release/14.x
3f43d803382d (HEAD -> release/14.x, origin/release/14.x) [libc++] Re-enable 
workaround for pre-ranges CTAD in std::span
add3ab7f4c8a [libc++] Add workaround to avoid breaking users of  when 
 are disabled

The changelog in [2] says nothing about an integration of these 2 commits.

Unfortunately, an updated LLVM/Clang version 14 from  is 
according to a lower Debian version only possible with some tricks.

[ major and debian versions ]
MVER="14" ; 
DVER="1:14.0.0~++20220329040533+3f43d803382d-1~exp1~20220329160543.107"

[ llvm packages ]
llvm_pkgs="clang-$MVER libclang-common-$MVER-dev libclang-cpp$MVER 
libclang1-$MVER libllvm$MVER lld-$MVER llvm-$MVER llvm-$MVER-linker-tools 
llvm-$MVER-runtime llvm-$MVER-tools"

echo $MVER $DVER $llvm_pkgs

[ simulate ]
for p in $llvm_pkgs ; do echo [ $p ] ; apt-get install $p=$DVER -t 
llvm-toolchain-$MVER --allow-downgrades --no-install-recommends -s ; done

[ install ]
for p in $llvm_pkgs ; do echo [ $p ] ; apt-get install $p=$DVER -t 
llvm-toolchain-$MVER --allow-downgrades --no-install-recommends -y ; done

Can you provide a new llvm-toolchain-14 packages in Debian/unstable with these 
upstream patches?

Thanks.

Regards,
- Sedat -

[1] https://discourse.llvm.org/t/llvm-14-0-1-schedule-and-release-updates/61227
[2] 
https://metadata.ftp-master.debian.org/changelogs//main/l/llvm-toolchain-14/llvm-toolchain-14_14.0.0-1_changelog

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

Kernel: Linux 5.17.0-3-amd64-clang14-lto (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 clang-14 depends on:
ii  binutils2.38-3
ii  libc6   2.33-7
ii  libc6-dev   2.33-7
ii  libclang-common-14-dev  1:14.0.0-1
ii  libclang-cpp14  1:14.0.0-1
ii  libclang1-141:14.0.0-1
ii  libgcc-11-dev   11.2.0-19
ii  libgcc-s1   12-20220319-1
ii  libllvm14   1:14.0.0-1
ii  libobjc-11-dev  11.2.0-19
ii  libstdc++-11-dev11.2.0-19
ii  libstdc++6  12-20220319-1
ii  llvm-14-linker-tools1:14.0.0-1

Versions of packages clang-14 recommends:
pn  llvm-14-dev  
ii  python3  3.10.4-1

Versions of packages clang-14 suggests:
pn  clang-14-doc  

-- no debconf information

Bug#1008078: zstd: Bump version to 1.4.10

[Sedat Dilek]

Hi,

Friendly ping...

BTW, where is the packaging happening today?

dsc file says:

Vcs-Browser: https://salsa.debian.org/med-team/libzstd
Vcs-Git: https://salsa.debian.org/med-team/libzstd.git

But I see the latest development in [1].

Ah OK latest debian/changelog says:

libzstd (1.4.9+dfsg-1) unstable; urgency=medium

  * New maintainer, bring libzstd under the RPM packaging team's umbrella.
Many thanks to the Debian Med Team and everyone else for their work!
...

Can you please update The Vcs-* fields with the new version?

Just for the records:

zstd v1.4.10 has many bug-fixes :-).

Thanks.

Regards,
- sed@ -

[1] https://salsa.debian.org/pkg-rpm-team/libzstd
[2] https://salsa.debian.org/roam

Bug#1008078: zstd: Bump version to 1.4.10

[Sedat Dilek]

Package: zstd
Version: 1.4.9+dfsg-1
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

I use where I can ZSTD to compress and decompress in things of file archiving.

The Linux kernel introduced a stable API on ZSTD v1.4.10 with Linux v5.16.
This version was tagged after my request on the LKML.
On the kernel-side I use it for ZSWAP, ZRAM and (de)compress my initrd.img as 
default. 

Last weekend, I saw you updated zstd package to version 1.4.9.
I am bit sorry with my late request.
Can you please bump the version to 1.4.10?

Thanks in advance.

Regards,
- Sedat -


[1] https://marc.info/?l=linux-kernel=164616178411144=2
[2] https://github.com/facebook/zstd/tags
[3] https://github.com/facebook/zstd/releases/tag/v1.4.10
[4] https://github.com/facebook/zstd/compare/v1.4.9...v1.4.10

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

Kernel: Linux 5.17.0-1-amd64-clang13-lto (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 zstd depends on:
ii  libc6   2.33-7
ii  libgcc-s1   12-20220319-1
ii  liblz4-11.9.3-2
ii  liblzma55.2.5-2
ii  libstdc++6  12-20220319-1
ii  zlib1g  1:1.2.11.dfsg-3

zstd recommends no packages.

zstd suggests no packages.

-- no debconf information

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

[Sedat Dilek]

Package: chromium
Version: 93.0.4577.82-1
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

I updated my google-chrome-stable package to version 94.0.4606.61-1 on my 
Debian/unstable AMD64 system.

Debian's security-tracker for chromium [1] package shows several CVE security 
issues not fixed.

Open issues:

Bug stretch buster  bullseyebookworm
sid Description
CVE-2021-37973  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37972  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37971  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37970  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37969  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37968  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37967  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37966  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37965  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37964  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37963  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37962  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37961  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37960  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37959  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37958  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37957  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable  
CVE-2021-37956  vulnerable  vulnerable  vulnerable  vulnerable  
vulnerable

For more details also see "Stable Channel Update for Desktop" at [2].

Please upgrade chromium from v93.x to v94.x.

Thanks.

Regards,
- Sedat -

[1] https://security-tracker.debian.org/tracker/source-package/chromium
[2] https://chromereleases.googleblog.com/search/label/Stable%20updates
[3] 
https://www.heise.de/news/Google-schliesst-19-Sicherheitsluecken-in-Chrome-6199412.html
 (German)

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

Kernel: Linux 5.14.0-1-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 chromium depends on:
ii  chromium-common 93.0.4577.82-1
ii  libasound2  1.2.5.1-1
ii  libatk-bridge2.0-0  2.38.0-2
ii  libatk1.0-0 2.36.0-2
ii  libatomic1  11.2.0-8
ii  libatspi2.0-0   2.42.0-1
ii  libavcodec587:4.4-6+b2
ii  libavformat58   7:4.4-6+b2
ii  libavutil56 7:4.4-6+b2
ii  libc6   2.32-4
ii  libcairo2   1.16.0-5
ii  libcups22.3.3op2-7
ii  libdbus-1-3 1.12.20-2
ii  libdrm2 2.4.107-8
ii  libevent-2.1-7  2.1.12-stable-1
ii  libexpat1   2.4.1-2+b1
ii  libflac81.3.3-2
ii  libfontconfig1  2.13.1-4.2
ii  libfreetype62.10.4+dfsg-1
ii  libgbm1 21.2.2-1
ii  libgcc-s1   11.2.0-8
ii  libglib2.0-02.70.0-1+b1
ii  libharfbuzz0b   2.7.4-1
ii  libicu6767.1-7
ii  libjpeg62-turbo 1:2.0.6-4
ii  libjsoncpp241.9.4-4
ii  liblcms2-2  2.12~rc1-2
ii  libminizip1 1.1-8+b1
ii  libnspr42:4.32-1
ii  libnss3 2:3.70-1
ii  libopenjp2-72.4.0-3
ii  libopus01.3.1-0.1
ii  libpango-1.0-0  1.48.10+ds1-1
ii  libpng16-16 1.6.37-3
ii  libpulse0   15.0+dfsg1-2
ii  libre2-920210901+dfsg-1
ii  libsnappy1v51.1.8-1
ii  libstdc++6  11.2.0-8
ii  libwebp60.6.1-2.1
ii  libwebpdemux2   0.6.1-2.1
ii  libwebpmux3 0.6.1-2.1
ii  libx11-62:1.7.2-2+b1
ii  libxcb1 1.14-3
ii  libxcomposite1  1:0.4.5-1
ii  libxdamage1 1:1.1.5-2
ii  libxext62:1.3.4-1
ii  libxfixes3  1:5.0.3-2
ii  libxml2 2.9.12+dfsg-5
ii  libxrandr2  2:1.5.1-1
ii  libxshmfence1   1.3-1
ii  libxslt1.1  1.1.34-4
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages chromium recommends:
ii  chromium-sandbox  

Bug#987715: chromium: Update to version 90.0.4430.93 (security-fixes)

[Sedat Dilek]

Package: chromium
Version: 90.0.4430.85-1
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

Google's chrome version 90.0.4430.93 ships several CVEs fixed (see [1] for 
details):

[1199345] High CVE-2021-21227: Insufficient data validation in V8. Reported by 
Gengming Liu of Singular Security Lab on 2021-04-15

[1175058] High CVE-2021-21232: Use after free in Dev Tools. Reported by 
Abdulrahman Alqabandi, Microsoft Browser Vulnerability Research on 2021-02-05

[1182937] High CVE-2021-21233: Heap buffer overflow in ANGLE. Reported by Omair 
on 2021-02-26

[1139156] Medium CVE-2021-21228: Insufficient policy enforcement in extensions. 
Reported by Rob Wu on 2020-10-16

[1198165] Medium CVE-2021-21229: Incorrect security UI in downloads. Reported 
by Mohit Raj (shadow2639) on 2021-04-12

[1198705] Medium CVE-2021-21230: Type Confusion in V8. Reported by Manfred Paul 
on 2021-04-13

[1198696] Low CVE-2021-21231: Insufficient data validation in V8. Reported by 
Sergei Glazunov of Google Project Zero on 2021-04-13

These CVEs are also listed in Debian's security-tracker (see [2]).

Can you please upgrade chromium to the same version?
Thanks.

Regards,
- Sedat -

[1] 
https://chromereleases.googleblog.com/2021/04/stable-channel-update-for-desktop_26.html
[2] https://security-tracker.debian.org/tracker/source-package/chromium
[3] 
https://www.heise.de/news/Sicherheitsluecken-in-Chrome-Aktuelles-Browser-Update-bessert-nach-6029565.htm
 (German)


-- System Information:
Debian Release: 11.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing'), (99, 
'buildd-unstable'), (99, 'buildd-experimental'), (99, 'experimental'), (99, 
'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.12.0-1-amd64-clang12-lto (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 chromium depends on:
ii  chromium-common 90.0.4430.85-1
ii  libasound2  1.2.4-1.1
ii  libatk-bridge2.0-0  2.38.0-1
ii  libatk1.0-0 2.36.0-2
ii  libatomic1  10.2.1-6
ii  libatspi2.0-0   2.38.0-4
ii  libavcodec587:4.3.2-0+deb11u1
ii  libavformat58   7:4.3.2-0+deb11u1
ii  libavutil56 7:4.3.2-0+deb11u1
ii  libc6   2.31-11
ii  libcairo2   1.16.0-5
ii  libcups22.3.3op2-3
ii  libdbus-1-3 1.12.20-2
ii  libdrm2 2.4.104-1
ii  libevent-2.1-7  2.1.12-stable-1
ii  libexpat1   2.2.10-2
ii  libflac81.3.3-2
ii  libfontconfig1  2.13.1-4.2
ii  libfreetype62.10.4+dfsg-1
ii  libgbm1 20.3.5-1
ii  libgcc-s1   10.2.1-6
ii  libglib2.0-02.66.8-1
ii  libgtk-3-0  3.24.24-3
ii  libharfbuzz0b   2.7.4-1
ii  libicu6767.1-6
ii  libjpeg62-turbo 1:2.0.6-4
ii  libjsoncpp241.9.4-4
ii  liblcms2-2  2.12~rc1-2
ii  libminizip1 1.1-8+b1
ii  libnspr42:4.29-1
ii  libnss3 2:3.63-1
ii  libopenjp2-72.4.0-3
ii  libopus01.3.1-0.1
ii  libpango-1.0-0  1.46.2-3
ii  libpng16-16 1.6.37-3
ii  libpulse0   14.2-2
ii  libre2-920210201+dfsg-1
ii  libsnappy1v51.1.8-1
ii  libstdc++6  10.2.1-6
ii  libvpx6 1.9.0-1
ii  libwebp60.6.1-2+b1
ii  libwebpdemux2   0.6.1-2+b1
ii  libwebpmux3 0.6.1-2+b1
ii  libx11-62:1.7.0-2
ii  libxcb1 1.14-3
ii  libxcomposite1  1:0.4.5-1
ii  libxdamage1 1:1.1.5-2
ii  libxext62:1.3.3-1.1
ii  libxfixes3  1:5.0.3-2
ii  libxml2 2.9.10+dfsg-6.3+b1
ii  libxrandr2  2:1.5.1-1
ii  libxshmfence1   1.3-1
ii  libxslt1.1  1.1.34-4
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages chromium recommends:
ii  chromium-sandbox  90.0.4430.85-1

Versions of packages chromium suggests:
pn  chromium-driver  
ii  chromium-l10n90.0.4430.85-1
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  libc6   2.31-11
ii  libstdc++6  10.2.1-6
ii  libx11-62:1.7.0-2
ii  libxext62:1.3.3-1.1
ii  x11-utils   7.7+5
ii  xdg-utils   1.1.3-4.1
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages chromium-common recommends:
ii  chromium-sandbox90.0.4430.85-1
ii  fonts-liberation1:1.07.4-11
ii  gnome-shell [notification-daemon]   3.38.4-1
ii  libgl1-mesa-dri 20.3.5-1
ii  libu2f-udev 1.1.10-3
ii  notification-daemon 3.20.0-4
ii  plasma-workspace [notification-daemon]  4:5.21.4-1
ii  system-config-printer   1.5.14-1
ii  upower  0.99.11-2

Versions of packages chromium-sandbox depends on:
ii  libc6  2.31-11

-- Configuration Files:

Bug#987358: chromium: Update to version 90.0.4430.85 (security-fixes)

[Sedat Dilek]

Package: chromium
Version: 90.0.4430.72-1
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

just today I upgraded Debian's chromium to version 90.0.4430.72-1.
Thanks.

With today's dist-upgrade I also see:

google-chrome-stable (90.0.4430.72-1 => 90.0.4430.85-1)

So, again a new google-chrome-stable with "open issues" according to Debian's 
security-tracker see [1].

The link in [2] lists the following 5 CVEs with "High" and a brief description:

[$TBD][1194046] High CVE-2021-21222: Heap buffer overflow in V8. Reported by 
Guang Gong of Alpha Lab, Qihoo 360 on 2021-03-30

[$TBD][1195308] High CVE-2021-21223: Integer overflow in Mojo. Reported by 
Guang Gong of Alpha Lab, Qihoo 360 on 2021-04-02

[$TBD][1195777] High CVE-2021-21224: Type Confusion in V8. Reported by Jose 
Martinez (tr0y4) from VerSprite Inc. on 2021-04-05

[$TBD][1195977] High CVE-2021-21225: Out of bounds memory access in V8. 
Reported by Brendon Tiszka (@btiszka) supporting the EFF on 2021-04-05

[$TBD][1197904] High CVE-2021-21226: Use after free in navigation. Reported by 
Brendon Tiszka (@btiszka) supporting the EFF on 2021-04-11

Please, upgrade Debian's chromium to version 90.0.4430.85.
Thanks.

Regards,
- Sedat -

[1] https://security-tracker.debian.org/tracker/source-package/chromium
[2] 
https://chromereleases.googleblog.com/2021/04/stable-channel-update-for-desktop_20.html
[3] 
https://www.heise.de/news/Webbrowser-Chrome-erneut-im-Visier-von-Angreifern-6024209.html
 (German)

-- System Information:
Debian Release: 11.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing'), (99, 
'buildd-unstable'), (99, 'buildd-experimental'), (99, 'experimental'), (99, 
'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.12.0-rc8-1-amd64-clang12-lto (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 chromium depends on:
ii  chromium-common 90.0.4430.72-1
ii  libasound2  1.2.4-1.1
ii  libatk-bridge2.0-0  2.38.0-1
ii  libatk1.0-0 2.36.0-2
ii  libatomic1  10.2.1-6
ii  libatspi2.0-0   2.38.0-2
ii  libavcodec587:4.3.2-0+deb11u1
ii  libavformat58   7:4.3.2-0+deb11u1
ii  libavutil56 7:4.3.2-0+deb11u1
ii  libc6   2.31-11
ii  libcairo2   1.16.0-5
ii  libcups22.3.3op2-3
ii  libdbus-1-3 1.12.20-2
ii  libdrm2 2.4.104-1
ii  libevent-2.1-7  2.1.12-stable-1
ii  libexpat1   2.2.10-2
ii  libflac81.3.3-2
ii  libfontconfig1  2.13.1-4.2
ii  libfreetype62.10.4+dfsg-1
ii  libgbm1 20.3.5-1
ii  libgcc-s1   10.2.1-6
ii  libglib2.0-02.66.8-1
ii  libgtk-3-0  3.24.24-3
ii  libharfbuzz0b   2.7.4-1
ii  libicu6767.1-6
ii  libjpeg62-turbo 1:2.0.6-4
ii  libjsoncpp241.9.4-4
ii  liblcms2-2  2.12~rc1-2
ii  libminizip1 1.1-8+b1
ii  libnspr42:4.29-1
ii  libnss3 2:3.63-1
ii  libopenjp2-72.4.0-3
ii  libopus01.3.1-0.1
ii  libpango-1.0-0  1.46.2-3
ii  libpng16-16 1.6.37-3
ii  libpulse0   14.2-2
ii  libre2-920210201+dfsg-1
ii  libsnappy1v51.1.8-1
ii  libstdc++6  10.2.1-6
ii  libvpx6 1.9.0-1
ii  libwebp60.6.1-2+b1
ii  libwebpdemux2   0.6.1-2+b1
ii  libwebpmux3 0.6.1-2+b1
ii  libx11-62:1.7.0-2
ii  libxcb1 1.14-3
ii  libxcomposite1  1:0.4.5-1
ii  libxdamage1 1:1.1.5-2
ii  libxext62:1.3.3-1.1
ii  libxfixes3  1:5.0.3-2
ii  libxml2 2.9.10+dfsg-6.3+b1
ii  libxrandr2  2:1.5.1-1
ii  libxshmfence1   1.3-1
ii  libxslt1.1  1.1.34-4
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages chromium recommends:
ii  chromium-sandbox  90.0.4430.72-1

Versions of packages chromium suggests:
pn  chromium-driver  
ii  chromium-l10n90.0.4430.72-1
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  libc6   2.31-11
ii  libstdc++6  10.2.1-6
ii  libx11-62:1.7.0-2
ii  libxext62:1.3.3-1.1
ii  x11-utils   7.7+5
ii  xdg-utils   1.1.3-4
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages chromium-common recommends:
ii  chromium-sandbox90.0.4430.72-1
ii  fonts-liberation1:1.07.4-11
ii  gnome-shell [notification-daemon]   3.38.4-1
ii  libgl1-mesa-dri 20.3.5-1
ii  libu2f-udev 1.1.10-3
ii  notification-daemon 3.20.0-4
ii  plasma-workspace [notification-daemon]  4:5.21.4-1
ii  system-config-printer   1.5.14-1
ii  upower  0.99.11-2

Versions of packages chromium-sandbox depends on:
ii  libc6  2.31-11

-- 

Bug#987053: chromium: Update to version 90.0.4430.72 (security-fixes)

[Sedat Dilek]

Package: chromium
Version: 89.0.4389.114-1
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

Google released chrome web-browser version 90.0.4430.72 with several CVE - some 
of them with "high" risk.
For details please see [1].

Debian's security tracker lists the following Open issues:

Bug stretch buster  bullseyesid 
Description
CVE-2021-21221  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21220  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21219  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21218  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21217  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21216  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21215  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21214  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21213  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21212  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21211  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21210  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21209  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21208  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21207  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21206  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21205  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21204  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21203  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21202  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21201  vulnerable  vulnerable  vulnerable  vulnerable

Please update chromium to the same version as Google chrome.

Thanks.

Regards,
- Sedat -


[1] 
https://chromereleases.googleblog.com/2021/04/stable-channel-update-for-desktop_14.html
[2] https://security-tracker.debian.org/tracker/source-package/chromium
[3] 
https://www.heise.de/news/Sicherheitsupdates-Mehrere-gefaehrliche-Luecken-in-Chrome-gestopft-6017779.html
 (German)

-- System Information:
Debian Release: 11.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing'), (99, 
'buildd-unstable'), (99, 'buildd-experimental'), (99, 'experimental'), (99, 
'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.12.0-rc7-3-amd64-clang12-lto (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE
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 chromium depends on:
ii  chromium-common  89.0.4389.114-1
ii  libasound2   1.2.4-1.1
ii  libatk-bridge2.0-0   2.38.0-1
ii  libatk1.0-0  2.36.0-2
ii  libatomic1   10.2.1-6
ii  libatspi2.0-02.38.0-2
ii  libavcodec58 7:4.3.2-0+deb11u1
ii  libavformat587:4.3.2-0+deb11u1
ii  libavutil56  7:4.3.2-0+deb11u1
ii  libc62.31-11
ii  libcairo21.16.0-5
ii  libcups2 2.3.3op2-3
ii  libdbus-1-3  1.12.20-2
ii  libdrm2  2.4.104-1
ii  libevent-2.1-7   2.1.12-stable-1
ii  libexpat12.2.10-2
ii  libflac8 1.3.3-2
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgbm1  20.3.5-1
ii  libgcc-s110.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.8-1
ii  libgtk-3-0   3.24.24-3
ii  libharfbuzz0b2.7.4-1
ii  libicu67 67.1-6
ii  libjpeg62-turbo  1:2.0.6-4
ii  libjsoncpp24 1.9.4-4
ii  liblcms2-2   2.12~rc1-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.29-1
ii  libnss3  2:3.63-1
ii  libopenjp2-7 2.4.0-3
ii  libopus0 1.3.1-0.1
ii  libpango-1.0-0   1.46.2-3
ii  libpng16-16  1.6.37-3
ii  libpulse014.2-2
ii  libre2-9 20210201+dfsg-1
ii  libsnappy1v5 1.1.8-1
ii  libstdc++6   10.2.1-6
ii  libvpx6  1.9.0-1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libx11-6 2:1.7.0-2
ii  libxcb1  1.14-3
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.3-1.1
ii  libxfixes3   1:5.0.3-2
ii  libxml2  2.9.10+dfsg-6.3+b1
ii  libxrandr2   2:1.5.1-1
ii  libxshmfence11.3-1
ii  libxslt1.1   1.1.34-4
ii  

Bug#986335: chromium: Update to version 89.0.4389.114 (security-fixes)

[Sedat Dilek]

Package: chromium
Version: 89.0.4389.90-1
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

several issues were fixed in Google's chrome version 89.0.4389.114 recently.

Debian's security-tracker lists these CVEs:

Bug stretch buster  bullseyesid 
Description
CVE-2021-21199  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21198  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21197  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21196  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21195  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21194  vulnerable  vulnerable  vulnerable  vulnerable

See also "Stable Channel Update for Desktop" in [2] (and [3] for German 
reading/speaking folks).

Please update Debian's chromium the version of Google's chrome.

Thanks.

Regards,
- Sedat -

[1] https://security-tracker.debian.org/tracker/source-package/chromium
[2] 
https://chromereleases.googleblog.com/2021/03/stable-channel-update-for-desktop_30.html
[3] 
https://www.heise.de/news/Chrome-Update-fuer-Desktop-Ausgabe-beseitigt-mehrere-Sicherheitsprobleme-6002712.html
 (German)


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing'), (99, 
'buildd-unstable'), (99, 'buildd-experimental'), (99, 'experimental'), (99, 
'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.12.0-rc5-11-amd64-clang12-lto (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE
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 chromium depends on:
ii  chromium-common  89.0.4389.90-1
ii  libasound2   1.2.4-1.1
ii  libatk-bridge2.0-0   2.38.0-1
ii  libatk1.0-0  2.36.0-2
ii  libatomic1   10.2.1-6
ii  libatspi2.0-02.38.0-2
ii  libavcodec58 7:4.3.2-0+deb11u1
ii  libavformat587:4.3.2-0+deb11u1
ii  libavutil56  7:4.3.2-0+deb11u1
ii  libc62.31-11
ii  libcairo21.16.0-5
ii  libcups2 2.3.3op2-3
ii  libdbus-1-3  1.12.20-2
ii  libdrm2  2.4.104-1
ii  libevent-2.1-7   2.1.12-stable-1
ii  libexpat12.2.10-2
ii  libflac8 1.3.3-2
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgbm1  20.3.5-1
ii  libgcc-s110.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.8-1
ii  libgtk-3-0   3.24.24-3
ii  libharfbuzz0b2.7.4-1
ii  libicu67 67.1-6
ii  libjpeg62-turbo  1:2.0.6-4
ii  libjsoncpp24 1.9.4-4
ii  liblcms2-2   2.12~rc1-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.29-1
ii  libnss3  2:3.63-1
ii  libopenjp2-7 2.4.0-3
ii  libopus0 1.3.1-0.1
ii  libpango-1.0-0   1.46.2-3
ii  libpng16-16  1.6.37-3
ii  libpulse014.2-2
ii  libre2-9 20210201+dfsg-1
ii  libsnappy1v5 1.1.8-1
ii  libstdc++6   10.2.1-6
ii  libvpx6  1.9.0-1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libx11-6 2:1.7.0-2
ii  libxcb1  1.14-3
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.3-1.1
ii  libxfixes3   1:5.0.3-2
ii  libxml2  2.9.10+dfsg-6.3+b1
ii  libxrandr2   2:1.5.1-1
ii  libxshmfence11.3-1
ii  libxslt1.1   1.1.34-4
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages chromium recommends:
ii  chromium-sandbox  89.0.4389.90-1

Versions of packages chromium suggests:
pn  chromium-driver  
ii  chromium-l10n89.0.4389.90-1
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  libc6   2.31-11
ii  libstdc++6  10.2.1-6
ii  libx11-62:1.7.0-2
ii  libxext62:1.3.3-1.1
ii  x11-utils   7.7+5
ii  xdg-utils   1.1.3-4
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages chromium-common recommends:
ii  chromium-sandbox89.0.4389.90-1
ii  fonts-liberation1:1.07.4-11
ii  gnome-shell [notification-daemon]   3.38.4-1
ii  libgl1-mesa-dri 20.3.5-1
ii  libu2f-udev 1.1.10-3
ii  notification-daemon 3.20.0-4
ii  plasma-workspace [notification-daemon]  4:5.21.3-1
ii  system-config-printer   1.5.14-1
ii  upower  0.99.11-2

Versions of packages chromium-sandbox depends on:
ii  libc6  2.31-11

-- Configuration Files:
/etc/chromium.d/default-flags changed [not included]

-- no debconf 

Bug#985271: chromium: Update to version 89.0.4389.90 (security-fixes)

[Sedat Dilek]

Package: chromium
Version: 89.0.4389.82-1
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

recently I got an update of google-chrome-stable to version 89.0.4389.90-1.

Debian's security-tracker lists the following CVEs:

Bug stretch buster  bullseyesid 
Description
---
CVE-2021-21193  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21192  vulnerable  vulnerable  vulnerable  vulnerable  
CVE-2021-21191  vulnerable  vulnerable  vulnerable  vulnerable

Especially CVE-2021-21193 is classified as "critical high".

Please update chromium to the same version as of google-chrome-stable.

Please see/check/read below links.

Thanks.

Regards,
- Sedat -


[1] https://security-tracker.debian.org/tracker/source-package/chromium
[2] https://chromereleases.googleblog.com/search/label/Stable%20updates
[3] 
https://www.heise.de/news/Sicherheitsupdate-Angreifer-nehmen-erneut-Google-Chrome-ins-Visier-5987831.html
 (German)

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing'), (99, 
'buildd-unstable'), (99, 'buildd-experimental'), (99, 'experimental'), (99, 
'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.12.0-rc3-1-amd64-clang12-cfi (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 chromium depends on:
ii  chromium-common  89.0.4389.82-1
ii  libasound2   1.2.4-1.1
ii  libatk-bridge2.0-0   2.38.0-1
ii  libatk1.0-0  2.36.0-2
ii  libatomic1   10.2.1-6
ii  libatspi2.0-02.38.0-2
ii  libavcodec58 7:4.3.2-0+deb11u1
ii  libavformat587:4.3.2-0+deb11u1
ii  libavutil56  7:4.3.2-0+deb11u1
ii  libc62.31-9
ii  libcairo21.16.0-5
ii  libcups2 2.3.3op2-3
ii  libdbus-1-3  1.12.20-2
ii  libdrm2  2.4.104-1
ii  libevent-2.1-7   2.1.12-stable-1
ii  libexpat12.2.10-2
ii  libflac8 1.3.3-2
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgbm1  20.3.4-1
ii  libgcc-s110.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.7-2
ii  libgtk-3-0   3.24.24-3
ii  libharfbuzz0b2.7.4-1
ii  libicu67 67.1-6
ii  libjpeg62-turbo  1:2.0.6-4
ii  libjsoncpp24 1.9.4-4
ii  liblcms2-2   2.12~rc1-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.29-1
ii  libnss3  2:3.61-1
ii  libopenjp2-7 2.4.0-3
ii  libopus0 1.3.1-0.1
ii  libpango-1.0-0   1.46.2-3
ii  libpng16-16  1.6.37-3
ii  libpulse014.2-2
ii  libre2-9 20210201+dfsg-1
ii  libsnappy1v5 1.1.8-1
ii  libstdc++6   10.2.1-6
ii  libvpx6  1.9.0-1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libx11-6 2:1.7.0-2
ii  libxcb1  1.14-3
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.3-1.1
ii  libxfixes3   1:5.0.3-2
ii  libxml2  2.9.10+dfsg-6.3+b1
ii  libxrandr2   2:1.5.1-1
ii  libxshmfence11.3-1
ii  libxslt1.1   1.1.34-4
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages chromium recommends:
ii  chromium-sandbox  89.0.4389.82-1

Versions of packages chromium suggests:
pn  chromium-driver  
ii  chromium-l10n89.0.4389.82-1
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  libc6   2.31-9
ii  libstdc++6  10.2.1-6
ii  libx11-62:1.7.0-2
ii  libxext62:1.3.3-1.1
ii  x11-utils   7.7+5
ii  xdg-utils   1.1.3-4
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages chromium-common recommends:
ii  chromium-sandbox89.0.4389.82-1
ii  fonts-liberation1:1.07.4-11
ii  gnome-shell [notification-daemon]   3.38.3-4
ii  libgl1-mesa-dri 20.3.4-1
ii  libu2f-udev 1.1.10-3
ii  notification-daemon 3.20.0-4
ii  plasma-workspace [notification-daemon]  4:5.21.2-1
ii  system-config-printer   1.5.14-1
ii  upower  0.99.11-2

Versions of packages chromium-sandbox depends on:
ii  libc6  2.31-9

-- Configuration Files:
/etc/chromium.d/default-flags changed [not included]

-- no debconf information

Bug#984532: chromium: Update to version 89.0.4389.72 (security-fixes)

[Sedat Dilek]

Package: chromium
Version: 88.0.4324.182-1
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

several CVE issues were fixed in Chrome version 89.0.4389.72.

For details and list of CVEs please see [1] and [2].
( [3] is in German. )

Please update to the new version.

Thanks.

Regards,
- Sedat -

[1] https://chromereleases.googleblog.com/search/label/Stable%20updates
[2] https://security-tracker.debian.org/tracker/source-package/chromium
[3] 
https://www.heise.de/news/Jetzt-patchen-Exploit-Code-fuer-Google-Chrome-in-Umlauf-5070743.html

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (99, 'buildd-unstable'), (99, 
'buildd-experimental'), (99, 'experimental'), (99, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.12.0-rc1-9-amd64-clang13-cfi (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 chromium depends on:
ii  chromium-common  88.0.4324.182-1
ii  libasound2   1.2.4-1.1
ii  libatk-bridge2.0-0   2.38.0-1
ii  libatk1.0-0  2.36.0-2
ii  libatomic1   10.2.1-6
ii  libatspi2.0-02.38.0-2
ii  libavcodec58 7:4.3.2-0+deb11u1
ii  libavformat587:4.3.2-0+deb11u1
ii  libavutil56  7:4.3.2-0+deb11u1
ii  libc62.31-9
ii  libcairo21.16.0-5
ii  libcups2 2.3.3op2-3
ii  libdbus-1-3  1.12.20-2
ii  libdrm2  2.4.104-1
ii  libevent-2.1-7   2.1.12-stable-1
ii  libexpat12.2.10-2
ii  libflac8 1.3.3-2
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgbm1  20.3.4-1
ii  libgcc-s110.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.7-1
ii  libgtk-3-0   3.24.24-3
ii  libharfbuzz0b2.7.4-1
ii  libicu67 67.1-6
ii  libjpeg62-turbo  1:2.0.6-2
ii  libjsoncpp24 1.9.4-4
ii  liblcms2-2   2.12~rc1-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.29-1
ii  libnss3  2:3.61-1
ii  libopenjp2-7 2.4.0-3
ii  libopus0 1.3.1-0.1
ii  libpango-1.0-0   1.46.2-3
ii  libpng16-16  1.6.37-3
ii  libpulse014.2-2
ii  libre2-9 20210201+dfsg-1
ii  libsnappy1v5 1.1.8-1
ii  libstdc++6   10.2.1-6
ii  libvpx6  1.9.0-1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libx11-6 2:1.7.0-2
ii  libxcb1  1.14-3
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.3-1.1
ii  libxfixes3   1:5.0.3-2
ii  libxml2  2.9.10+dfsg-6.3+b1
ii  libxrandr2   2:1.5.1-1
ii  libxslt1.1   1.1.34-4
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages chromium recommends:
ii  chromium-sandbox  88.0.4324.182-1

Versions of packages chromium suggests:
pn  chromium-driver  
ii  chromium-l10n88.0.4324.182-1
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  libc6   2.31-9
ii  libstdc++6  10.2.1-6
ii  libx11-62:1.7.0-2
ii  libxext62:1.3.3-1.1
ii  x11-utils   7.7+5
ii  xdg-utils   1.1.3-4
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages chromium-common recommends:
ii  chromium-sandbox88.0.4324.182-1
ii  fonts-liberation1:1.07.4-11
ii  gnome-shell [notification-daemon]   3.38.3-3
ii  libgl1-mesa-dri 20.3.4-1
ii  libu2f-udev 1.1.10-3
ii  notification-daemon 3.20.0-4
ii  plasma-workspace [notification-daemon]  4:5.21.2-1
ii  system-config-printer   1.5.14-1
ii  upower  0.99.11-2

Versions of packages chromium-sandbox depends on:
ii  libc6  2.31-9

-- Configuration Files:
/etc/chromium.d/default-flags changed [not included]

-- no debconf information

Bug#982301: virtualbox-dkms: Error! Your kernel headers for kernel 5.10.0-3 cannot be found.

[Sedat Dilek]

This bug-report can be closed.

See my comment in Debian Bug #982304 "linux-headers-5.10.0-3-amd64:
File include/generated/autoconf.h missed to compile virtualbox-dkms"
in [1].

- Sedat -

[1] https://bugs.debian.org/982304#15

Bug#982304: linux-headers-5.10.0-3-amd64: File include/generated/autoconf.h missed to compile virtualbox-dkms

[Sedat Dilek]

If you like you can close this bug-report.

linux-headers-5.10.0-4-amd64 version 5.10.19-1 ships the necessary
files and I was able to build virtualbox-dkms kernel-modules:

root# LC_ALL=C ll /lib/modules/5.10.0-4-amd64/updates/dkms/
total 852K
drwxr-xr-x 2 root root 4.0K Mar  3 04:00 .
drwxr-xr-x 3 root root 4.0K Mar  3 04:00 ..
-rw-r--r-- 1 root root 755K Mar  3 04:00 vboxdrv.ko
-rw-r--r-- 1 root root  21K Mar  3 04:00 vboxnetadp.ko
-rw-r--r-- 1 root root  61K Mar  3 04:00 vboxnetflt.ko

- Sedat -

Bug#983336: powertop: Update to version 2.13 and add a systemd service file

[Sedat Dilek]

Upstream announcement: "ANNOUNCING PowerTOP v2.13"

[1] 
https://lists.01.org/hyperkitty/list/power...@lists.01.org/thread/ZVKPXBGH5TZ2LYPQRTG74WMTRPU3NZPQ/

Bug#983336: powertop: Update to version 2.13 and add a systemd service file

[Sedat Dilek]

[ CC Joe ]

Hey Joe, finally here is the Debian bug-report :-).

Upstream mailing-list according to Joe:

1. MUA-friendly: power...@lists.01.org
2. Browser-friendly: https://lists.01.org/hyperkitty/list/power...@lists.01.org/

- Sedat -

Bug#983336: powertop: Update to version 2.13 and add a systemd service file

[Sedat Dilek]

Package: powertop
Version: 2.11-1
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

I promised the PowerTop upstream maintainer to write a Debian bug-report.
Sorry for the delay.

PowerTop v2.13 was released @ 11-Jun.2020.

I compiled PowerTop v2.13 out of Git and installed it in /opt/powertop.

Inspired by the Arch Linux wiki in [2] I wrote up a powertop.service file.

root# systemctl cat powertop.service
# /etc/systemd/system/powertop.service
[Unit]
Description=Powertop tunings

[Service]
Type=oneshot
ExecStart=/usr/sbin/powertop --auto-tune

[Install]
WantedBy=multi-user.target

Can you please update PowerTop in Debian to version 2.13?

And add a powertop.service file?
PowerTop upstream offers a powertop.service in "Add service file" (see [3]).
This commit is post v2.13.

Thanks.

Regards,
- Sedat -


[1] https://github.com/fenrus75/powertop/releases/tag/v2.13
[2] https://wiki.archlinux.org/index.php/Power_management
[3] 
https://github.com/fenrus75/powertop/commit/91ea2e7236bb77180aff4cb318af6a84573a8f75

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (99, 'buildd-unstable'), (99, 
'buildd-experimental'), (99, 'experimental'), (99, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.11.0-7-amd64-clang13-cfi (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 powertop depends on:
ii  libc62.31-9
ii  libgcc-s1 [libgcc1]  10.2.1-6
ii  libncursesw6 6.2+20201114-2
ii  libnl-3-200  3.4.0-1+b1
ii  libnl-genl-3-200 3.4.0-1+b1
ii  libpci3  1:3.7.0-5
ii  libstdc++6   10.2.1-6
ii  libtinfo66.2+20201114-2

powertop recommends no packages.

Versions of packages powertop suggests:
pn  cpufrequtils   
pn  laptop-mode-tools  

-- no debconf information

Bug#982980: closed by Michael Gilbert (Re: Bug#982980: chromium: Update to version 88.0.4324.182 (security-fixes))

[Sedat Dilek]

Hi Michael,

thanks for taking care.

Can you please add a "Closes:" tag in d/changelog - next time?
That will credit my time I invested to write a Debian bug-report.

Nice to see in the dsc file [0] that you moved the development back to
"chromium-team/chromium" on .

Is it possible to *first* build amd64 packages?
I always see the i386 Debian packages first, see [2].
Unsure, if you can influence the build-process.

Thanks again.

Regards,
- Sedat -

[0] 
https://incoming.debian.org/debian-buildd/pool/main/c/chromium/chromium_88.0.4324.182-1.dsc
[1] https://salsa.debian.org/chromium-team/chromium
[2] https://salsa.debian.org/mimi8/chromium
[3] https://incoming.debian.org/debian-buildd/pool/main/c/chromium/?C=M;O=D
[4] 
https://salsa.debian.org/chromium-team/chromium/-/commit/e1e12bccd22d6f8ecfa2c142820ed680e1d75967

On Thu, Feb 18, 2021 at 10:36 PM Debian Bug Tracking System
 wrote:
>
> This is an automatic notification regarding your Bug report
> which was filed against the chromium package:
>
> #982980: chromium: Update to version 88.0.4324.182 (security-fixes)
>
> It has been closed by Michael Gilbert .
>
> 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 Michael Gilbert 
>  by
> replying to this email.
>
>
> --
> 982980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982980
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Michael Gilbert 
> To: 982980-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Thu, 18 Feb 2021 16:32:26 -0500
> Subject: Re: Bug#982980: chromium: Update to version 88.0.4324.182 
> (security-fixes)
> version: 88.0.4324.182-1
>
> On Wed, Feb 17, 2021 at 1:12 PM Sedat Dilek  wrote:
> > please update to version 88.0.4324.182.
>
>
> -- Forwarded message --
> From: Sedat Dilek 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Wed, 17 Feb 2021 19:09:19 +0100
> Subject: chromium: Update to version 88.0.4324.182 (security-fixes)
> Package: chromium
> Version: 88.0.4324.150-1
> Severity: normal
> X-Debbugs-Cc: sedat.di...@gmail.com
>
> Dear Maintainer,
>
> please update to version 88.0.4324.182.
> [1] shows several CVEs Security Fixes labeled with "High".
>
> Thanks.
>
> Regards,
> - Sedat -
>
> [1] https://chromereleases.googleblog.com/search/label/Stable%20updates
> [2] https://security-tracker.debian.org/tracker/source-package/chromium
>
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (500, 'testing'), (99, 'buildd-unstable'), (99, 
> 'buildd-experimental'), (99, 'experimental'), (99, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.11.0-3-amd64-clang13-ias (SMP w/4 CPU threads)
> Kernel taint flags: TAINT_UNSIGNED_MODULE
> 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 chromium depends on:
> ii  chromium-common  88.0.4324.150-1
> ii  libasound2   1.2.4-1.1
> ii  libatk-bridge2.0-0   2.38.0-1
> ii  libatk1.0-0  2.36.0-2
> ii  libatomic1   10.2.1-6
> ii  libatspi2.0-02.38.0-2
> ii  libavcodec58 7:4.3.1-8
> ii  libavformat587:4.3.1-8
> ii  libavutil56  7:4.3.1-8
> ii  libc62.31-9
> ii  libcairo21.16.0-5
> ii  libcups2 2.3.3op2-3
> ii  libdbus-1-3  1.12.20-1
> ii  libdrm2  2.4.104-1
> ii  libevent-2.1-7   2.1.12-stable-1
> ii  libexpat12.2.10-1
> ii  libflac8 1.3.3-2
> ii  libfontconfig1   2.13.1-4.2
> ii  libfreetype6 2.10.4+dfsg-1
> ii  libgbm1  20.3.4-1
> ii  libgcc-s110.2.1-6
> ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
> ii  libglib2.0-0 2.66.7-1
> ii  libgtk-3-0   3.24.24-1
> ii  libharfbuzz0b2.7.4-1
> ii  libicu67 67.1-6
> ii  libjpeg62-turbo  1:2.0.6-1
> ii  libjsoncpp24 1.9.4-4
> ii  liblcms2-2   2.12~rc1-2
> ii  libminizip1  1.1-8+b1
> ii  libnspr4 2:4.29-1
> ii  libnss3  2:3.61-1
> ii  libopenjp2-7 2.4.0-3
> ii  libopus0 1.3.1-0.1
> ii  libpango-1.0-0   1.46.2-3
> ii  libpng16-16  1.6.37-3
> ii  libpulse014.2-1
> ii  libre2-9 20210201+dfsg-1
> ii  libsnappy1v5 1.1.8-1
> ii  libstdc++6   10.2.1-6

Bug#982980: chromium: Update to version 88.0.4324.182 (security-fixes)

[Sedat Dilek]

Package: chromium
Version: 88.0.4324.150-1
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

please update to version 88.0.4324.182.
[1] shows several CVEs Security Fixes labeled with "High".

Thanks.

Regards,
- Sedat -

[1] https://chromereleases.googleblog.com/search/label/Stable%20updates
[2] https://security-tracker.debian.org/tracker/source-package/chromium

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (99, 'buildd-unstable'), (99, 
'buildd-experimental'), (99, 'experimental'), (99, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.11.0-3-amd64-clang13-ias (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 chromium depends on:
ii  chromium-common  88.0.4324.150-1
ii  libasound2   1.2.4-1.1
ii  libatk-bridge2.0-0   2.38.0-1
ii  libatk1.0-0  2.36.0-2
ii  libatomic1   10.2.1-6
ii  libatspi2.0-02.38.0-2
ii  libavcodec58 7:4.3.1-8
ii  libavformat587:4.3.1-8
ii  libavutil56  7:4.3.1-8
ii  libc62.31-9
ii  libcairo21.16.0-5
ii  libcups2 2.3.3op2-3
ii  libdbus-1-3  1.12.20-1
ii  libdrm2  2.4.104-1
ii  libevent-2.1-7   2.1.12-stable-1
ii  libexpat12.2.10-1
ii  libflac8 1.3.3-2
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgbm1  20.3.4-1
ii  libgcc-s110.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.7-1
ii  libgtk-3-0   3.24.24-1
ii  libharfbuzz0b2.7.4-1
ii  libicu67 67.1-6
ii  libjpeg62-turbo  1:2.0.6-1
ii  libjsoncpp24 1.9.4-4
ii  liblcms2-2   2.12~rc1-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.29-1
ii  libnss3  2:3.61-1
ii  libopenjp2-7 2.4.0-3
ii  libopus0 1.3.1-0.1
ii  libpango-1.0-0   1.46.2-3
ii  libpng16-16  1.6.37-3
ii  libpulse014.2-1
ii  libre2-9 20210201+dfsg-1
ii  libsnappy1v5 1.1.8-1
ii  libstdc++6   10.2.1-6
ii  libvpx6  1.9.0-1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libx11-6 2:1.7.0-2
ii  libxcb1  1.14-3
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.3-1.1
ii  libxfixes3   1:5.0.3-2
ii  libxml2  2.9.10+dfsg-6.3+b1
ii  libxrandr2   2:1.5.1-1
ii  libxslt1.1   1.1.34-4
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages chromium recommends:
ii  chromium-sandbox  88.0.4324.150-1

Versions of packages chromium suggests:
pn  chromium-driver  
ii  chromium-l10n88.0.4324.150-1
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  libc6   2.31-9
ii  libstdc++6  10.2.1-6
ii  libx11-62:1.7.0-2
ii  libxext62:1.3.3-1.1
ii  x11-utils   7.7+5
ii  xdg-utils   1.1.3-4
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages chromium-common recommends:
ii  chromium-sandbox88.0.4324.150-1
ii  fonts-liberation1:1.07.4-11
ii  gnome-shell [notification-daemon]   3.38.3-2
ii  libgl1-mesa-dri 20.3.4-1
ii  libu2f-udev 1.1.10-3
ii  notification-daemon 3.20.0-4
ii  plasma-workspace [notification-daemon]  4:5.20.5-3
ii  system-config-printer   1.5.14-1
ii  upower  0.99.11-2

Versions of packages chromium-sandbox depends on:
ii  libc6  2.31-9

-- Configuration Files:
/etc/chromium.d/default-flags changed [not included]

-- no debconf information

Bug#982059: Bug#982372: Bug#982059: manpages-de: procps: File sconflict between procps and manpages-de

[Sedat Dilek]

With attached debdiff I was able to build and install:

manpages-de (4.9.2-1.1~dileks)

- Sedat -


manpages-l10n-4_9_2-1_dileks-v2.debdiff
Description: Binary data

Bug#982059: Bug#982372: Bug#982059: manpages-de: procps: File sconflict between procps and manpages-de

[Sedat Dilek]

On Wed, Feb 10, 2021 at 9:50 PM Craig Small  wrote:
>
>
>
> On Thu, 11 Feb 2021 at 07:39, Sedat Dilek  wrote:
>>
>> Small nit:
>> On a quick view on latest manpages-l10n I still see the duplicates in
>> debian/rules e.g. kill.1 (manpages-de).
>
> The criteria for removing a page out of manpages-* is actually more 
> complicated than that. It's not just "does the procps package have this 
> manpage" but "does the procps package have this translated manpage in *this 
> language*".
>
> And for each manpage the languages that are available are different, both in 
> the procps and manpages-l10n packages. It's also not good enough to see the 
> relevant .po file because po4a will only translate a file if it is at least 
> 80% translated.
>
> In short, its a massive pain, but I think its ok now; or at least its no 
> longer conflicting.
>
> I'm not sure what you mean by duplicates here.
>

In [1] I saw:

# Remove manpages from procps
rm -f debian/manpages-de/usr/share/man/de/man1/kill.1
rm -f debian/manpages-de/usr/share/man/de/man1/free.1
rm -f debian/manpages-de/usr/share/man/de/man1/kill.1

kill.1 double.

This is now history with manpages version 4.9.2 see [2].

[2] says:

  * New upstream version 4.9.2
  * This version no longer contains the procps manpages

No more need of above hacksz in d/r.

- Sedat -

[1] 
https://salsa.debian.org/debian/manpages-l10n/-/commit/d54f4eb1227af99607feab876fdd8927d5a16dc1
[2] 
https://salsa.debian.org/debian/manpages-l10n/-/commit/81eebd8536abfbb598cb0855a5f613b7204bb1c8

Bug#982059: manpages-de: procps: File sconflict between procps and manpages-de

[Sedat Dilek]

On Wed, Feb 10, 2021 at 9:38 PM Sedat Dilek  wrote:
>
> On Wed, Feb 10, 2021 at 8:59 PM Craig Small  wrote:
> >
> > For testing this I installed Procps and *all*of the generated man pages and 
> > that seemed to be fine.
> >
> > That's slightly different to the patch I put in the bug report but I 
> > emailed Helge the difference.
> >
>
> Thanks Craig.
>
> Small nit:
> On a quick view on latest manpages-l10n I still see the duplicates in
> debian/rules e.g. kill.1 (manpages-de).
>

Cool, you fixed that *.install files.

Checked the latest version d/r which is fine to me.

- Sedat -

[1] https://salsa.debian.org/debian/manpages-l10n/-/blob/master/debian/rules

Bug#982355: Bug#982059: manpages-de: procps: File sconflict between procps and manpages-de

[Sedat Dilek]

On Wed, Feb 10, 2021 at 8:59 PM Craig Small  wrote:
>
> For testing this I installed Procps and *all*of the generated man pages and 
> that seemed to be fine.
>
> That's slightly different to the patch I put in the bug report but I emailed 
> Helge the difference.
>

Thanks Craig.

Small nit:
On a quick view on latest manpages-l10n I still see the duplicates in
debian/rules e.g. kill.1 (manpages-de).

- Sedat -

Bug#982059: manpages-de: procps: File sconflict between procps and manpages-de

[Sedat Dilek]

user$ sudo LC_ALL=C dpkg -i manpages-de_4.9.1-2.1~dileks_all.deb
(Reading database ... 341292 files and directories currently installed.)
Preparing to unpack manpages-de_4.9.1-2.1~dileks_all.deb ...
Unpacking manpages-de (4.9.1-2.1~dileks) ...
Setting up manpages-de (4.9.1-2.1~dileks) ...
Processing triggers for man-db (2.9.4-1) ...

root# dpkg -l | egrep 'manpages-de|procps|psmisc' | awk '/^ii/ {print
$1 " " $2 " " $3}' | column -t
ii  libprocps8:amd64  2:3.3.17-2
ii  manpages-de   4.9.1-2.1~dileks
ii  manpages-dev  5.10-1
ii  procps2:3.3.17-2
ii  psmisc23.4-2

- Sedat -

Bug#982059: manpages-de: procps: File sconflict between procps and manpages-de

[Sedat Dilek]

On Wed, Feb 10, 2021 at 7:05 PM Sedat Dilek  wrote:
>
> Hi,
>
> I modified Craig's procps_manpage.diff as it still shows conflicts on
> manpages-de installation: e.g. man5/sysctl.conf.5.
>
> Attached is my manpages-de_procps_dileks.debdiff.
> The list of file-removal is alphabetically sorted.
> The debdiff is on top of (pending) manpages-l10n 4.9.1-2 solving
> issues for me with manpages-de (only).
>

Schei...benkleister - means in German politely sh*t.

I forgot... man8/vmstat.8 in the file-removal list.


$ git diff manpages-de_procps_dileks.debdiff
manpages-de_procps_dileks-v2.debdiff
diff --git a/manpages-de_procps_dileks.debdiff
b/manpages-de_procps_dileks-v2.debdiff
index ae2b07c4153a..f53f878e08ce 100644
--- a/manpages-de_procps_dileks.debdiff
+++ b/manpages-de_procps_dileks-v2.debdiff
@@ -30,7 +30,7 @@ diff -Nru manpages-l10n-4.9.1/debian/control
manpages-l10n-4.9.1/debian/control
diff -Nru manpages-l10n-4.9.1/debian/rules manpages-l10n-4.9.1/debian/rules
--- manpages-l10n-4.9.1/debian/rules   2021-01-24 12:19:47.0 +0100
+++ manpages-l10n-4.9.1/debian/rules   2021-02-10 17:20:06.0 +0100
-@@ -113,6 +113,17 @@
+@@ -113,6 +113,18 @@
   rm -f debian/manpages-pt-br-dev/usr/share/man/pt_BR/man3/intro.3
   rm -f debian/manpages-ro-dev/usr/share/man/ro/man2/intro.2
   rm -f debian/manpages-ro-dev/usr/share/man/ro/man3/intro.3
@@ -45,6 +45,7 @@ diff -Nru manpages-l10n-4.9.1/debian/rules
manpages-l10n-4.9.1/debian/rules
+  rm -f debian/manpages-de/usr/share/man/de/man1/w.1
+  rm -f debian/manpages-de/usr/share/man/de/man5/sysctl.conf.5
+  rm -f debian/manpages-de/usr/share/man/de/man8/sysctl.8
++  rm -f debian/manpages-de/usr/share/man/de/man8/vmstat.8

 # Use epoch for Polish packages
 override_dh_gencontrol:

Attached is v2 of my debdiff.

- Sedat -


manpages-de_procps_dileks-v2.debdiff
Description: Binary data

Bug#982059: manpages-de: procps: File sconflict between procps and manpages-de

[Sedat Dilek]

Hi,

I modified Craig's procps_manpage.diff as it still shows conflicts on
manpages-de installation: e.g. man5/sysctl.conf.5.

Attached is my manpages-de_procps_dileks.debdiff.
The list of file-removal is alphabetically sorted.
The debdiff is on top of (pending) manpages-l10n 4.9.1-2 solving
issues for me with manpages-de (only).

- Sedat -


manpages-de_procps_dileks.debdiff
Description: Binary data

Bug#982355: manpages-l10n: File conflict with procps and manpages-*

[Sedat Dilek]

Hi,

I applied Craig's procps_manpage.diff on top of latest manpages-10n
 Git.

I see double entries "kill.1" for manpages-de:

[ procps_manpage.diff ]

+ # Remove manpages from procps
+ rm -f debian/manpages-de/usr/share/man/de/man1/kill.1
+ rm -f debian/manpages-de/usr/share/man/de/man1/free.1
+ rm -f debian/manpages-de/usr/share/man/de/man1/kill.1
+ rm -f debian/manpages-de/usr/share/man/de/man1/pgrep.1
+ rm -f debian/manpages-de/usr/share/man/de/man1/pidof.1
+ rm -f debian/manpages-de/usr/share/man/de/man1/pmap.1
+ rm -f debian/manpages-de/usr/share/man/de/man1/ps.1
+ rm -f debian/manpages-de/usr/share/man/de/man1/pwdx.1
+ rm -f debian/manpages-de/usr/share/man/de/man1/slabtop.1
+ rm -f debian/manpages-de/usr/share/man/de/man8/sysctl.8
+ rm -f debian/manpages-de/usr/share/man/de/man1/tload.1
+ rm -f debian/manpages-de/usr/share/man/de/man1/uptime.1
+ rm -f debian/manpages-de/usr/share/man/de/man8/vmstat.8
+ rm -f debian/manpages-de/usr/share/man/de/man1/w.1
+ rm -f debian/manpages-de/usr/share/man/de/man1/watch.1

Still building a new manpages-10n...

Is there a simple way to just build manpages-de?
This package is of interest for me.

- Sedat -

Bug#982431: exfatprogs: Update to version 1.1.0

[Sedat Dilek]

Correct link to the announcement.

[1] 
https://lore.kernel.org/linux-fsdevel/001401d6ff68$5acaf360$1060da20$@samsung.com/T/#t

Bug#982059: manpages-de: procps: File sconflict between procps and manpages-de

[Sedat Dilek]

On Wed, Feb 10, 2021 at 8:25 AM Craig Small  wrote:
>
> The issue is you won't be able to install manpages-de afterwards (the fix is 
> one-way). See #982355 for the other half to this.
>

Yeah.

AFAICS for procps and manpages-de this file caused the conflict:
   de/man1/w.1.po

First, I wanted to simply remove the above file via debian/rules
(manpages-l10n).

So what is your suggestion?

- Sedat -


>  - Craig
>
>
> On Wed, 10 Feb 2021 at 03:39, Sedat Dilek  wrote:
>>
>> [ CC Helge & Craig ]
>>
>> With the attached debdiff on top of Helge's 4.9.1-1 tarball I was able
>> to co-install latest procps, psmisc and (pending) manpages-de.
>>
>> Check with dpkg:
>>
>> root# dpkg -l | egrep 'manpages-de|procps|psmisc' | awk '/^ii/ {print
>> $1 " " $2 " " $3}' | column -t
>> ii  libprocps8:amd64  2:3.3.17-1
>> ii  manpages-de   4.9.1-2
>> ii  manpages-dev  5.10-1
>> ii  procps2:3.3.17-1
>> ii  psmisc23.4-2
>>
>> - Sedat -

Bug#982431: exfatprogs: Update to version 1.1.0

[Sedat Dilek]

Package: exfatprogs
Version: 1.0.4-1
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

please, update exfatprogs to version 1.1.0.

See the announcement in [1] for more details.

Thanks.

Regards,
- Sedat -

[1] https://mail.google.com/mail/u/0/#inbox/FMfcgxwLsSXWrdHrXsGrjZpClGqxMChQ

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (99, 'buildd-unstable'), (99, 
'buildd-experimental'), (99, 'experimental'), (99, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.11.0-rc7-5-amd64-clang12-ias (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 exfatprogs depends on:
ii  libc6  2.31-9

exfatprogs recommends no packages.

exfatprogs suggests no packages.

-- no debconf information

Bug#982372: manpages-de: procps: File sconflict between procps and manpages-de

[Sedat Dilek]

[ CC Helge & Craig ]

With the attached debdiff on top of Helge's 4.9.1-1 tarball I was able
to co-install latest procps, psmisc and (pending) manpages-de.

Check with dpkg:

root# dpkg -l | egrep 'manpages-de|procps|psmisc' | awk '/^ii/ {print
$1 " " $2 " " $3}' | column -t
ii  libprocps8:amd64  2:3.3.17-1
ii  manpages-de   4.9.1-2
ii  manpages-dev  5.10-1
ii  procps2:3.3.17-1
ii  psmisc23.4-2

- Sedat -


helgefjell.debdiff
Description: Binary data

Bug#982059: manpages-de: procps: File sconflict between procps and manpages-de

[Sedat Dilek]

I filed Debian Bug #982372 "manpages-de: procps: File sconflict
between procps and manpages-de".

To quote from [0]:

On d-u I see:

root# RELEASE="buildd-unstable" ; LC_ALL=C apt-get dist-upgrade -V -t $RELEASE
...
The following packages will be REMOVED:
   manpages-de (4.9.1-1)
   task-german (3.63)
The following packages will be upgraded:
..
   libprocps8 (2:3.3.16-5 => 2:3.3.17-1)
..
   procps (2:3.3.16-5 => 2:3.3.17-1)
...
Do you want to continue? [Y/n] n
Abort

As you can see manpages-de and task-german packages will be REMOVED.

The manpages-l10n package will need some Breaks/Replaces like in [3].
...
- EndOfQuote -

Thanks.

Regards,
- Sedat -

[0] https://bugs.debian.org/982372
[1] https://bugs.debian.org/982059
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982059#49
[3] 
https://salsa.debian.org/debian/manpages-l10n/-/commit/50984aa59335b2821165e8c8ca1616f59c82e911

Bug#982372: manpages-de: procps: File sconflict between procps and manpages-de

[Sedat Dilek]

Package: procps
Version: 2:3.3.16-5
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

like in Debian Bug #982059 "manpages-de,psmisc: File conflict between psmisc 
and manpages-de: '/usr/share/man/de/man1/fuser.1.gz"
there exists file conflicts between manpages-de and procps package.

I have installed manpages-de package version 4.9.1-1 offered in tarball from 
Helge Kreutzmann (see [2]) who is preparing a version 4.9.1-2 on .

On d-u I see:

root# RELEASE="buildd-unstable" ; LC_ALL=C apt-get dist-upgrade -V -t $RELEASE

...
The following packages will be REMOVED:
   manpages-de (4.9.1-1)
   task-german (3.63)
The following packages will be upgraded:
   apt (2.1.18 => 2.1.19)
   apt-utils (2.1.18 => 2.1.19)
   firmware-amd-graphics (20201218-3 => 20210208-1)
   firmware-iwlwifi (20201218-3 => 20210208-1)
   firmware-linux (20201218-3 => 20210208-1)
   firmware-linux-nonfree (20201218-3 => 20210208-1)
   firmware-misc-nonfree (20201218-3 => 20210208-1)
   firmware-realtek (20201218-3 => 20210208-1)
   libapt-pkg6.0 (2.1.18 => 2.1.19)
   libmaven-resolver-java (1.4.2-1 => 1.4.2-2)
   libmaven3-core-java (3.6.3-3 => 3.6.3-4)
   libplexus-cipher-java (1.7-3 => 1.8-1)
   libprocps8 (2:3.3.16-5 => 2:3.3.17-1)
   libselinux1 (3.1-2+b2 => 3.1-3)
   libselinux1-dev (3.1-2+b2 => 3.1-3)
   procps (2:3.3.16-5 => 2:3.3.17-1)
16 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
Need to get 31.1 MB of archives.
After this operation, 1507 kB disk space will be freed.
Do you want to continue? [Y/n] n
Abort

As you can see manpages-de and task-german packages will be REMOVED.

The manpages-l10n package will need some Breaks/Replaces like in [3].

People will hit the problem when procps enters Debian/unstable (I have 
buildd-unstable in my APT sources.list).

I dunno how to CC: manpages maintainers via reportbug.
Please feel free to do so.
Increase the level of Severity if needed (the above mentioned BR has "serious).

As a temporary workaround I did:

root# packages="procps libprocps8" ; for p in $packages ; do echo "$p" "hold" | 
dpkg --set-selections ; done

root# dpkg --get-selections | grep hold | column -t
libprocps8:amd64  hold
procpshold

Thanks.

Regards,
- Sedat -


[1] https://bugs.debian.org/982059
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982059#49
[3] 
https://salsa.debian.org/debian/manpages-l10n/-/commit/50984aa59335b2821165e8c8ca1616f59c82e911

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (99, 'buildd-unstable'), (99, 
'buildd-experimental'), (99, 'experimental'), (99, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.11.0-rc7-4-amd64-clang12-ias (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 procps depends on:
ii  init-system-helpers  1.60
ii  libc62.31-9
ii  libncurses6  6.2+20201114-2
ii  libncursesw6 6.2+20201114-2
hi  libprocps8   2:3.3.16-5
ii  libtinfo66.2+20201114-2
ii  lsb-base 11.1.0

Versions of packages procps recommends:
ii  psmisc  23.4-2

procps suggests no packages.

-- no debconf information

Bug#982304: linux-headers-5.10.0-3-amd64: File include/generated/autoconf.h missed to compile virtualbox-dkms

[Sedat Dilek]

I checked the filelist from [1]:

# echo $files
/usr/src/linux-headers-5.10.0-3-amd64/include/generated/asm-offsets.h
/usr/src/linux-headers-5.10.0-3-amd64/include/generated/autoconf.h
/usr/src/linux-headers-5.10.0-
3-amd64/include/generated/bounds.h
/usr/src/linux-headers-5.10.0-3-amd64/include/generated/compile.h
/usr/src/linux-headers-5.10.0-3-amd64/include/generated/package.h
/usr/src/linux-headers-5.10.0-3-amd64/include/generated/timeconst.h
/usr/src/linux-headers-5.10.0-3-amd64/include/generated/uapi/linux/version.h
/usr/src/linux-headers
-5.10.0-3-amd64/include/generated/utsrelease.h

# LC_ALL=C ll $files
ls: cannot access
'/usr/src/linux-headers-5.10.0-3-amd64/include/generated/autoconf.h':
No such file or directory
-rw-r--r-- 1 root root 4.7K Feb  6 09:23
/usr/src/linux-headers-5.10.0-3-amd64/include/generated/asm-offsets.h
-rw-r--r-- 1 root root  318 Feb  6 09:23
/usr/src/linux-headers-5.10.0-3-amd64/include/generated/bounds.h
-rw-r--r-- 1 root root  337 Feb  6 09:23
/usr/src/linux-headers-5.10.0-3-amd64/include/generated/compile.h
-rw-r--r-- 1 root root   45 Feb  6 09:23
/usr/src/linux-headers-5.10.0-3-amd64/include/generated/package.h
-rw-r--r-- 1 root root 1.1K Feb  6 09:23
/usr/src/linux-headers-5.10.0-3-amd64/include/generated/timeconst.h
-rw-r--r-- 1 root root   97 Feb  6 09:23
/usr/src/linux-headers-5.10.0-3-amd64/include/generated/uapi/linux/version.h
-rw-r--r-- 1 root root   37 Feb  6 09:23
/usr/src/linux-headers-5.10.0-3-amd64/include/generated/utsrelease.h

- Sedat -

[1] https://packages.debian.org/sid/amd64/linux-headers-5.10.0-3-amd64/filelist

Bug#982301: virtualbox-dkms: Error! Your kernel headers for kernel 5.10.0-3 cannot be found.

[Sedat Dilek]

I filed Debian Bug #982304:
"linux-headers-5.10.0-3-amd64: File include/generated/autoconf.h
missed to compile virtualbox-dkms"

- Sedat -

[1] https://bugs.debian.org/982304

Bug#982304: linux-headers-5.10.0-3-amd64: File include/generated/autoconf.h missed to compile virtualbox-dkms

[Sedat Dilek]

Package: linux-headers-5.10.0-3-amd64
Version: 5.10.13-1
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

Today, I tried to build virtual-dkms from Debian/unstable against 
linux-headers-5.10.0-3-amd64.

This breaks here, thus I filed Debian Bug #982301:
"virtualbox-dkms: Error! Your kernel headers for kernel 5.10.0-3 cannot be 
found."

Please, see my detailed analysis there.

The important part is said in my comment #20:

- BeginOfQuote -
# dpkg -L linux-headers-5.10.0-3-amd64 | egrep 'auto.conf|autoconf.h'
/usr/src/linux-headers-5.10.0-3-amd64/include/config/auto.conf
/usr/src/linux-headers-5.10.0-3-amd64/include/generated/autoconf.h

# LC_ALL=C ll /usr/src/linux-headers-5.10.0-3-amd64/include/config/auto.conf
/usr/src/linux-headers-5.10.0-3-amd64/include/generated/autoconf.h
ls: cannot access
'/usr/src/linux-headers-5.10.0-3-amd64/include/generated/autoconf.h':
No such file or directory
-rw-r--r-- 1 root root 143K Feb  6 09:23
/usr/src/linux-headers-5.10.0-3-amd64/include/config/auto.conf

So, the package contents list "I ship a include/generated/autoconf.h"
but it does not exist :-).
- EndOfQuote -

Please, confirm that my analysis is correct.
If yes, please provide (really) an include/generated/autoconf.h file so that 
DKMS is happy.

Thanks.

Virtual Greetings from Moenchengladbach/Germnay,
- Sedat -

[1] https://bugs.debian.org/982301
[2] https://bugs.debian.org/982301#20

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (99, 'buildd-unstable'), (99, 
'buildd-experimental'), (99, 'experimental'), (99, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-3-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 linux-headers-5.10.0-3-amd64 depends on:
ii  linux-compiler-gcc-10-x86  5.10.13-1
ii  linux-headers-5.10.0-3-common  5.10.13-1
ii  linux-kbuild-5.10  5.10.13-1

linux-headers-5.10.0-3-amd64 recommends no packages.

linux-headers-5.10.0-3-amd64 suggests no packages.

-- no debconf information

Bug#982301: virtualbox-dkms: Error! Your kernel headers for kernel 5.10.0-3 cannot be found.

[Sedat Dilek]

LOL.

# dpkg -L linux-headers-5.10.0-3-amd64 | egrep 'auto.conf|autoconf.h'
/usr/src/linux-headers-5.10.0-3-amd64/include/config/auto.conf
/usr/src/linux-headers-5.10.0-3-amd64/include/generated/autoconf.h

# LC_ALL=C ll /usr/src/linux-headers-5.10.0-3-amd64/include/config/auto.conf
/usr/src/linux-headers-5.10.0-3-amd64/include/generated/autoconf.h
ls: cannot access
'/usr/src/linux-headers-5.10.0-3-amd64/include/generated/autoconf.h':
No such file or directory
-rw-r--r-- 1 root root 143K Feb  6 09:23
/usr/src/linux-headers-5.10.0-3-amd64/include/config/auto.conf

So, the package contents list "I ship a include/generated/autoconf.h"
but it does not exist :-).

- Sedat -

Bug#982301: virtualbox-dkms: Error! Your kernel headers for kernel 5.10.0-3 cannot be found.

[Sedat Dilek]

# LC_ALL=C ll /usr/src/linux-headers-5.10.0-3-amd64/.config
-rw-r--r-- 1 root root 231K Feb  8 15:40
/usr/src/linux-headers-5.10.0-3-amd64/.config

Passing --config=... and correct -k ...:

# LC_ALL=C dkms build -m virtualbox -v 6.1.18 -k 5.10.0-3-amd64
--kernelsourcedir=/usr/src/linux-headers-5.10.0-3-amd64
--config=/usr/src/linux-h
eaders-5.10.0-3-amd64

Preparing kernel 5.10.0-3-amd64 for module build:
(This is not compiling a kernel, just preparing kernel symbols)
Storing current .config to be restored when complete
Running Generic preparation routine
make mrproper...(bad exit status: 2)
using /usr/src/linux-headers-5.10.0-3-amd64
cp: -r not specified; omitting directory '/usr/src/linux-headers-5.10.0-3-amd64'
make oldconfig...(bad exit status: 2)
make prepare-all...(bad exit status: 2)

Building module:
cleaning build area...
make -j4 KERNELRELEASE=5.10.0-3-amd64 -C
/usr/src/linux-headers-5.10.0-3-amd64
M=/var/lib/dkms/virtualbox/6.1.18/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.10.0-3-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.18/build/make.log for more information.

# cat /var/lib/dkms/virtualbox/6.1.18/build/make.log
DKMS make.log for virtualbox-6.1.18 for kernel 5.10.0-3-amd64 (x86_64)
Mon Feb  8 15:40:26 CET 2021
make: Entering directory '/usr/src/linux-headers-5.10.0-3-amd64'

 ERROR: Kernel configuration is invalid.
include/generated/autoconf.h or include/config/auto.conf are missing.
Run 'make oldconfig && make prepare' on kernel src to fix it.

make[1]: *** [/usr/src/linux-headers-5.10.0-3-common/Makefile:717:
include/config/auto.conf] Fehler 1
make: *** [/usr/src/linux-headers-5.10.0-3-common/Makefile:185:
__sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-5.10.0-3-amd64'

[ EDIT: /usr/src/linux-headers-5.10.0-3-common/Makefile ]

711 # External modules and some install targets need
include/generated/autoconf.h
712 # and include/config/auto.conf but do not care if they are up-to-date.
713 # Use auto.conf to trigger the test
714 PHONY += include/config/auto.conf
715
716 include/config/auto.conf:
717 $(Q)test -e include/generated/autoconf.h -a -e $@ || (  \
718 echo >&2;   \
719 echo >&2 "  ERROR: Kernel configuration is invalid.";   \
720 echo >&2 " include/generated/autoconf.h or $@ are
missing.";\
721 echo >&2 " Run 'make oldconfig && make prepare' on
kernel src to fix it.";  \
722 echo >&2 ;  \
723 /bin/false)

Searching for include/generated/autoconf.h file:

# LC_ALL=C ll /usr/src/linux-headers-5.10.0-3-amd64/Makefile
/usr/src/linux-headers-5.10.0-3-amd64/include/generated/
-rw-r--r-- 1 root root   56 Feb  6 09:23
/usr/src/linux-headers-5.10.0-3-amd64/Makefile

/usr/src/linux-headers-5.10.0-3-amd64/include/generated/:
total 40K
drwxr-xr-x 3 root root 4.0K Feb  8 15:15 .
drwxr-xr-x 4 root root 4.0K Jan 31 17:36 ..
-rw-r--r-- 1 root root 4.7K Feb  6 09:23 asm-offsets.h
-rw-r--r-- 1 root root  318 Feb  6 09:23 bounds.h
-rw-r--r-- 1 root root  337 Feb  6 09:23 compile.h
-rw-r--r-- 1 root root   45 Feb  6 09:23 package.h
-rw-r--r-- 1 root root 1.1K Feb  6 09:23 timeconst.h
drwxr-xr-x 3 root root 4.0K Jan 31 17:36 uapi
-rw-r--r-- 1 root root   37 Feb  6 09:23 utsrelease.h

Such an include/generated/autoconf.h is missing in
linux-headers-5.10.0-3-amd64 package.

NOPE:

# find /usr/src/linux-headers-5.10.0-3-common -name autoconf.h
# find /usr/src/linux-headers-5.10.0-3-amd64 -name autoconf.h

- Sedat -

Bug#982301: virtualbox-dkms: Error! Your kernel headers for kernel 5.10.0-3 cannot be found.

[Sedat Dilek]

Passing --kernelsourcedir=... explicitly:

# LC_ALL=C dkms build -m virtualbox -v 6.1.18 -k 5.10.0-3
--kernelsourcedir=/usr/src/linux-headers-5.10.0-3-amd64

Preparing kernel 5.10.0-3 for module build:
(This is not compiling a kernel, just preparing kernel symbols)
Storing current .config to be restored when complete
Running Generic preparation routine
make mrproper...(bad exit status: 2)
Warning: using /usr/src/linux-headers-5.10.0-3-amd64/.config
(I hope this is the correct config for this kernel)
make oldconfig...(bad exit status: 2)
make prepare-all...(bad exit status: 2)

Building module:
cleaning build area...
make -j4 KERNELRELEASE=5.10.0-3 -C
/usr/src/linux-headers-5.10.0-3-amd64
M=/var/lib/dkms/virtualbox/6.1.18/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.10.0-3 (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.18/build/make.log for more information.

# cat /var/lib/dkms/virtualbox/6.1.18/build/make.log
DKMS make.log for virtualbox-6.1.18 for kernel 5.10.0-3 (x86_64)
Mon Feb  8 15:19:40 CET 2021
make: Entering directory '/usr/src/linux-headers-5.10.0-3-amd64'

 ERROR: Kernel configuration is invalid.
include/generated/autoconf.h or include/config/auto.conf are missing.
Run 'make oldconfig && make prepare' on kernel src to fix it.

make[1]: *** [/usr/src/linux-headers-5.10.0-3-common/Makefile:717:
include/config/auto.conf] Fehler 1
make: *** [/usr/src/linux-headers-5.10.0-3-common/Makefile:185:
__sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-5.10.0-3-amd64'

Why the hell is DKMS entering and searching in
/usr/src/linux-headers-5.10.0-3-common/ directory?

# find /usr/src/linux-headers-5.10.0-3-amd64 -name autoconf.h
[ empty ]

# find /usr/src/linux-headers-5.10.0-3-amd64 -name auto.conf
/usr/src/linux-headers-5.10.0-3-amd64/include/config/auto.conf

LOL, there exists an include/config/auto.conf file!

Confused,
- Sedat -

Bug#982301: virtualbox-dkms: Error! Your kernel headers for kernel 5.10.0-3 cannot be found.

[Sedat Dilek]

Package: virtualbox-dkms
Version: 6.1.18-dfsg-2
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

a build of virtualbox-dkms is not possible against latest Debian-kernel 
5.10.0-3-amd64:

root# dkms build -m virtualbox -v 6.1.18 -k 5.10.0-3
Error! Your kernel headers for kernel 5.10.0-3 cannot be found.
Please install the linux-headers-5.10.0-3 package,
or use the --kernelsourcedir option to tell DKMS where it's located

I have installed:

root# dpkg -l | egrep 'linux-headers|virtualbox|linux-image' | egrep 
'5.10.13|6.1.18' | awk '/^ii/ {print $1 " " $2 " " $3}' | column -t
ii  linux-headers-5.10.0-3-amd64   5.10.13-1
ii  linux-headers-5.10.0-3-common  5.10.13-1
ii  linux-headers-amd645.10.13-1
ii  linux-image-5.10.0-3-amd64 5.10.13-1
ii  linux-image-amd64  5.10.13-1
ii  virtualbox 6.1.18-dfsg-2
ii  virtualbox-dkms6.1.18-dfsg-2
ii  virtualbox-qt  6.1.18-dfsg-2

As you can see I have the required/corresponding linux-headers-5.10.0-3-amd64 
installed.

Can you tell me what is wrong?

Thanks.

Regards,
- Sedat -

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (99, 'buildd-unstable'), (99, 
'buildd-experimental'), (99, 'experimental'), (99, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-3-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 virtualbox-dkms depends on:
ii  dkms  2.8.4-1

Versions of packages virtualbox-dkms recommends:
ii  virtualbox  6.1.18-dfsg-2

virtualbox-dkms suggests no packages.

-- no debconf information

Bug#982059: manpages-de,psmisc: File conflict between psmisc and manpages-de: '/usr/share/man/de/man1/fuser.1.gz

[Sedat Dilek]

Hi,

installing manpages-de from Helge's tarball (see [1])...

dileks@iniza:~/src/manpages-l10n/current$ sudo dpkg -i
manpages-de_4.9.1-1_all.deb

..let's me coexist psmisc with manpages-de:

-ii manpages-de 4.2.0-1
+ii manpages-de 4.9.1-1
+ii psmisc 23.4-2

Thanks to all involved people.

Regards,
- Sedat -

[1] https://www.helgefjell.de/data/manpages-l10n_4.9.1-1.tar.xz
[2] https://www.helgefjell.de/data/manpages-l10n_4.9.1-1.tar.xz.sig

Bug#982059: manpages-de,psmisc: File conflict between psmisc and manpages-de: '/usr/share/man/de/man1/fuser.1.gz

[Sedat Dilek]

Hi,

I hit the same problem as Axel B. reported.

# RELEASE="buildd-unstable" ; LC_ALL=C apt-get dist-upgrade -V -t $RELEASE
...
The following packages will be REMOVED:
  manpages-de (4.2.0-1)
  task-german (3.63)
The following packages will be upgraded:
  psmisc (23.3-1 => 23.4-2)
1 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
Need to get 198 kB of archives.
After this operation, 3124 kB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.

So need to wait for new manpages-l10n (4.9.1-1)?

For now "hold" is your friend:

# echo "psmisc" "hold" | dpkg --set-selections

# dpkg --get-selections | grep hold
psmisc

After conflicts are solved:

# echo "psmisc" "install" | dpkg --set-selections

Just as a feedback.

Regards,
- Sedat -

Bug#982205: chromium: Update to version 88.0.4324.150 (security-fix)

[Sedat Dilek]

Package: chromium
Version: 88.0.4324.146-1
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

Chrome version 88.0.4324.150 contains CVE-2021-21148.
For details please see the link in [1].

Can you please provide a new version?

Thanks.

Regards,
- Sedat Dilek -

[1] 
https://chromereleases.googleblog.com/2021/02/stable-channel-update-for-desktop_4.html

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (99, 'buildd-unstable'), (99, 
'buildd-experimental'), (99, 'experimental'), (99, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 chromium depends on:
ii  chromium-common  88.0.4324.146-1
ii  libasound2   1.2.4-1.1
ii  libatk-bridge2.0-0   2.38.0-1
ii  libatk1.0-0  2.36.0-2
ii  libatomic1   10.2.1-6
ii  libatspi2.0-02.38.0-2
ii  libavcodec58 7:4.3.1-8
ii  libavformat587:4.3.1-8
ii  libavutil56  7:4.3.1-8
ii  libc62.31-9
ii  libcairo21.16.0-5
ii  libcups2 2.3.3op2-2
ii  libdbus-1-3  1.12.20-1
ii  libdrm2  2.4.104-1
ii  libevent-2.1-7   2.1.12-stable-1
ii  libexpat12.2.10-1
ii  libflac8 1.3.3-2
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgbm1  20.3.4-1
ii  libgcc-s110.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.6-1
ii  libgtk-3-0   3.24.24-1
ii  libharfbuzz0b2.7.4-1
ii  libicu67 67.1-6
ii  libjpeg62-turbo  1:2.0.5-2
ii  libjsoncpp24 1.9.4-4
ii  liblcms2-2   2.12~rc1-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.29-1
ii  libnss3  2:3.60-1
ii  libopenjp2-7 2.4.0-1
ii  libopus0 1.3.1-0.1
ii  libpango-1.0-0   1.46.2-3
ii  libpng16-16  1.6.37-3
ii  libpulse014.2-1
ii  libre2-9 20210201+dfsg-1
ii  libsnappy1v5 1.1.8-1
ii  libstdc++6   10.2.1-6
ii  libvpx6  1.9.0-1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libx11-6 2:1.7.0-2
ii  libxcb1  1.14-3
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.3-1.1
ii  libxfixes3   1:5.0.3-2
ii  libxml2  2.9.10+dfsg-6.3+b1
ii  libxrandr2   2:1.5.1-1
ii  libxslt1.1   1.1.34-4
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages chromium recommends:
ii  chromium-sandbox  88.0.4324.146-1

Versions of packages chromium suggests:
pn  chromium-driver  
ii  chromium-l10n88.0.4324.146-1
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  libc6   2.31-9
ii  libstdc++6  10.2.1-6
ii  libx11-62:1.7.0-2
ii  libxext62:1.3.3-1.1
ii  x11-utils   7.7+5
ii  xdg-utils   1.1.3-4
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages chromium-common recommends:
ii  chromium-sandbox88.0.4324.146-1
ii  fonts-liberation1:1.07.4-11
ii  gnome-shell [notification-daemon]   3.38.3-2
ii  libgl1-mesa-dri 20.3.4-1
ii  libu2f-udev 1.1.10-3
ii  notification-daemon 3.20.0-4
ii  plasma-workspace [notification-daemon]  4:5.20.5-3
ii  system-config-printer   1.5.14-1
ii  upower  0.99.11-2

Versions of packages chromium-sandbox depends on:
ii  libc6  2.31-9

-- Configuration Files:
/etc/chromium.d/default-flags changed [not included]

-- no debconf information

Bug#979135: chromium: GPU hw-accel: ANGLE libs cause a lot of errors and warnings

[Sedat Dilek]

With chromium version 87.0.4280.141-0.1 installed

I have commented now in /etc/chromium.d/default-flags...

##export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --use-gl=desktop"

...and desktop GL implementation is used as foreseen.

How can I switch back to ANGLE libs?
Just curious.

export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --use-gl= ??? "

Thanks.

- Sedat -

On Sat, Jan 9, 2021 at 10:15 AM Jan Luca Naumann  wrote:
>
> The reason I prefer at the moment the way to change the order in the
> code is that there it is checked if the desktop implementation is an
> allowed choice. I do not know what the behavior would be if this is not
> a valid choice for some case but we use the command line flag.
>
> The patch still allows to use "--use-gl=" in
> /etc/chromium.d/default-flags if people want to use something else for
> their installation.
>
> Best,
> Jan
>
> Am 09.01.21 um 08:03 schrieb Sedat Dilek:
> > Hi,
> >
> > Jan Luca is working on a patch "Use desktop gl implementation as default"...
> >
> > What about placing "--use-gl=desktop" in /etc/chromium.d/default-flags
> > as an alternative?
> >
> > # Default for GPU hardware-acceleration (Debian bug #979135)
> > export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --use-gl=desktop"
> >
> > Cannot say if this is wanted behaviour - to enable GPU hw-accel by default?
> > Looks like a safer methon when GPU hw-accel is wanted.
> >
> > In my logs I found references to Skia renderer...
> >
> > [ chrome://flags ]
> >
> > Skia API for compositing
> > If enabled, the display compositor will use Skia as the graphics API
> > instead of OpenGL ES. – Mac, Windows, Linux, Android
> > Here set to "Default"
> >
> > [ chrome://gpu ]
> > Graphics Feature Status > Skia Renderer: Enabled
> >
> > Cannot judge when not using ANGLE libs if there is a fallback to OpenGL ES.
> > Might be OpenGL ES renderer is the better choice?
> >
> > I have not looked for the parameters and cannot say I will play with them.
> >
> > ( BTW, I played with Vulkan support enabled - slow performance here
> > with Intel Sandy Bridge GPU. )
> >
> > Regards,
> > - Sedat -
> >
> > [1] https://salsa.debian.org/janluca-guest/chromium/-/commits/angle_fix
> > [2] https://wiki.archlinux.org/index.php/chromium#Force_GPU_acceleration
> > [3] 
> > https://wiki.archlinux.org/index.php/chromium#Hardware_video_acceleration
> >
>

Bug#979135: chromium: GPU hw-accel: ANGLE libs cause a lot of errors and warnings

[Sedat Dilek]

On Sat, Jan 9, 2021 at 10:15 AM Jan Luca Naumann  wrote:
>
> The reason I prefer at the moment the way to change the order in the
> code is that there it is checked if the desktop implementation is an
> allowed choice. I do not know what the behavior would be if this is not
> a valid choice for some case but we use the command line flag.
>
> The patch still allows to use "--use-gl=" in
> /etc/chromium.d/default-flags if people want to use something else for
> their installation.
>

Yesterday - with the help of karthek - I was able to play a bit with
ANGLE libs VS. --use-gl=desktop and GPU hardware-acceleration.

I was able to wath YouTube videos with GPU hardware-acceleration
enabled - also for video-decoding.
Here on my Intel SandyBridge GPU.
Fór the fruits see post-scriptum.

The strace log when running chromium showed me I can use
/etc/chromium.d/default-flags for custom settings.
I tried to put and activate my custom chromium settings in the user's
~/.config/chromium-flags.conf.
That did not work.
Did I miss something?

- Sedat -

[1] https://wiki.archlinux.org/index.php/chromium#Force_GPU_acceleration

P.S.: My custom default-flags for chromium (as an example, adapt with attention)

[ /etc/chromium.d/default-flags ]

# A set of command line flags that we want to set by default.

# Do not hide any extensions in the about:extensions dialog
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --show-component-extension-options"

# Enable GPU rasterization.
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --enable-gpu-rasterization"

# Don't display any warnings about not being the default browser
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --no-default-browser-check"

# Disable pinging
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --disable-pings"

# Disable the builtin media router (bug #833477)
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --media-router=0"

# XXX: Do NOT use ANGLE libs when GPU hardware-acceleration is enabled
# XXX: Comment below line to restore default usage of ANGLE libs
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --use-gl=desktop"

# XXX: Enable GPU hardware-accelerated video decoding
# Install: enhanced-h264ify chromium extension
# enhanced-h264ify:
#   Advanced settings: Block all codecs except h264
#   NOTE: Intel SandyBridge GPU does NOT support VP9 hw-accel but h264
# Link: 
https://chrome.google.com/webstore/detail/enhanced-h264ify/omkfmpieigblcllmkgbflkikinpkodlk
# YouTube:
#   Open chrome://media-internals/ > Players > Copy all to clipboard
#   Check clipboard for:
#   info: Selected for video decoding: "MojoVideoDecoder"
# config: codec: "h264"
#   NOTE: VpxVideoDecoder uses software-accelerated video decoding
# XXX: Comment below line when you see issues with video decoding
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --enable-accelerated-video-decode"

- EOT -

Bug#979135: chromium: GPU hw-accel: ANGLE libs cause a lot of errors and warnings

[Sedat Dilek]

On Sat, Jan 9, 2021 at 10:15 AM Jan Luca Naumann  wrote:
>
> The reason I prefer at the moment the way to change the order in the
> code is that there it is checked if the desktop implementation is an
> allowed choice. I do not know what the behavior would be if this is not
> a valid choice for some case but we use the command line flag.
>
> The patch still allows to use "--use-gl=" in
> /etc/chromium.d/default-flags if people want to use something else for
> their installation.
>

Hi Jan,

thanks for the feedback.

Your approach seems reasonable to me and wise.

Regards,
- Sedat -

Bug#979135: chromium: GPU hw-accel: ANGLE libs cause a lot of errors and warnings

[Sedat Dilek]

> I have not looked for the parameters and cannot say I will play with them.
>
> ( BTW, I played with Vulkan support enabled - slow performance here
> with Intel Sandy Bridge GPU. )
>

As common-line options...

Enable Vulkan support:

   --enable-features=Vulkan

Disable Skia renderer:

   --disable-features=UseSkiaRenderer

- Sedat -

[1] https://peter.sh/experiments/chromium-command-line-switches/

Bug#979135: chromium: GPU hw-accel: ANGLE libs cause a lot of errors and warnings

[Sedat Dilek]

Hi,

Jan Luca is working on a patch "Use desktop gl implementation as default"...

What about placing "--use-gl=desktop" in /etc/chromium.d/default-flags
as an alternative?

# Default for GPU hardware-acceleration (Debian bug #979135)
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --use-gl=desktop"

Cannot say if this is wanted behaviour - to enable GPU hw-accel by default?
Looks like a safer methon when GPU hw-accel is wanted.

In my logs I found references to Skia renderer...

[ chrome://flags ]

Skia API for compositing
If enabled, the display compositor will use Skia as the graphics API
instead of OpenGL ES. – Mac, Windows, Linux, Android
Here set to "Default"

[ chrome://gpu ]
Graphics Feature Status > Skia Renderer: Enabled

Cannot judge when not using ANGLE libs if there is a fallback to OpenGL ES.
Might be OpenGL ES renderer is the better choice?

I have not looked for the parameters and cannot say I will play with them.

( BTW, I played with Vulkan support enabled - slow performance here
with Intel Sandy Bridge GPU. )

Regards,
- Sedat -

[1] https://salsa.debian.org/janluca-guest/chromium/-/commits/angle_fix
[2] https://wiki.archlinux.org/index.php/chromium#Force_GPU_acceleration
[3] https://wiki.archlinux.org/index.php/chromium#Hardware_video_acceleration

Bug#979520: chromium: Security upgrade to version 87.0.4280.141

[Sedat Dilek]

Package: chromium
Version: 87.0.4280.88-0.4
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

there is a security fixed version 87.0.4280.141 of chrome available.

Can you please provide an adapted chromium package.

Thanks in advance.

Regards,
- Sedat -

[1] 
https://chromereleases.googleblog.com/2021/01/stable-channel-update-for-desktop.html


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (99, 'buildd-unstable'), (99, 
'buildd-experimental'), (99, 'experimental'), (99, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.11.0-rc2-5-amd64-clang11-cfi (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 chromium depends on:
ii  chromium-common  87.0.4280.88-0.4
ii  libasound2   1.2.4-1.1
ii  libatk-bridge2.0-0   2.38.0-1
ii  libatk1.0-0  2.36.0-2
ii  libatomic1   10.2.1-3
ii  libatspi2.0-02.38.0-2
ii  libavcodec58 7:4.3.1-5
ii  libavformat587:4.3.1-5
ii  libavutil56  7:4.3.1-5
ii  libc62.31-9
ii  libcairo21.16.0-5
ii  libcups2 2.3.3op1-4
ii  libdbus-1-3  1.12.20-1
ii  libdrm2  2.4.103-2
ii  libevent-2.1-7   2.1.12-stable-1
ii  libexpat12.2.10-1
ii  libflac8 1.3.3-2
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgbm1  20.3.2-1
ii  libgcc-s110.2.1-3
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.4-1
ii  libgtk-3-0   3.24.24-1
ii  libharfbuzz0b2.6.7-1
ii  libicu67 67.1-5
ii  libjpeg62-turbo  1:2.0.5-2
ii  libjsoncpp24 1.9.4-4
ii  liblcms2-2   2.9-4+b1
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.29-1
ii  libnss3  2:3.60-1
ii  libopenjp2-7 2.3.1-1
ii  libopus0 1.3.1-0.1
ii  libpango-1.0-0   1.46.2-3
ii  libpangocairo-1.0-0  1.46.2-3
ii  libpng16-16  1.6.37-3
ii  libpulse013.0-5
ii  libre2-9 20201101+dfsg-2
ii  libsnappy1v5 1.1.8-1
ii  libstdc++6   10.2.1-3
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libx11-6 2:1.7.0-1
ii  libx11-xcb1  2:1.7.0-1
ii  libxcb1  1.14-2.1
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.3-1.1
ii  libxfixes3   1:5.0.3-2
ii  libxml2  2.9.10+dfsg-6.3+b1
ii  libxrandr2   2:1.5.1-1
ii  libxslt1.1   1.1.34-4
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages chromium recommends:
ii  chromium-sandbox  87.0.4280.88-0.4

Versions of packages chromium suggests:
pn  chromium-driver  
ii  chromium-l10n87.0.4280.88-0.4
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  libc6   2.31-9
ii  libstdc++6  10.2.1-3
ii  libx11-62:1.7.0-1
ii  libxext62:1.3.3-1.1
ii  x11-utils   7.7+5
ii  xdg-utils   1.1.3-2
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages chromium-common recommends:
ii  chromium-sandbox87.0.4280.88-0.4
ii  fonts-liberation1:1.07.4-11
ii  gnome-shell [notification-daemon]   3.38.2-1
ii  libgl1-mesa-dri 20.3.2-1
ii  libu2f-udev 1.1.10-1.1
ii  notification-daemon 3.20.0-4
ii  plasma-workspace [notification-daemon]  4:5.20.5-1
ii  system-config-printer   1.5.13-1
ii  upower  0.99.11-2

Versions of packages chromium-sandbox depends on:
ii  libc6  2.31-9

-- no debconf information

Bug#979135: chromium: GPU hw-accel: ANGLE libs cause a lot of errors and warnings

[Sedat Dilek]

Attached are the promised full chrome://gpu/ logs.

- Sedat -

Graphics Feature Status
Canvas: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Out-of-process Rasterization: Disabled
OpenGL: Enabled
Hardware Protected Video Decode: Unavailable
Rasterization: Hardware accelerated on all pages
Skia Renderer: Enabled
Video Decode: Software only. Hardware acceleration disabled
Vulkan: Disabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated
Driver Bug Workarounds
adjust_src_dst_region_for_blitframebuffer
clear_uniforms_before_first_program_use
decode_encode_srgb_for_generatemipmap
exit_on_context_lost
msaa_is_slow
scalarize_vec_and_mat_constructor_args
disabled_extension_GL_KHR_blend_equation_advanced
disabled_extension_GL_KHR_blend_equation_advanced_coherent
Problems Detected
Protected video decoding with swap chain is for certain Intel and AMD GPUs on 
Windows: 1093625
Disabled Features: protected_video_decode
Clear uniforms before first program use on all platforms: 124764, 349137
Applied Workarounds: clear_uniforms_before_first_program_use
Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565
Applied Workarounds: msaa_is_slow
adjust src/dst region if blitting pixels outside framebuffer on Linux Intel: 
664740
Applied Workarounds: adjust_src_dst_region_for_blitframebuffer
Disable KHR_blend_equation_advanced until cc shaders are updated: 661715
Applied Workarounds: disable(GL_KHR_blend_equation_advanced), 
disable(GL_KHR_blend_equation_advanced_coherent)
Decode and Encode before generateMipmap for srgb format textures on Linux Mesa 
ANGLE path: 634519
Applied Workarounds: decode_encode_srgb_for_generatemipmap
Some drivers can't recover after OUT_OF_MEM and context lost: 893177
Applied Workarounds: exit_on_context_lost
Accelerated video decode has been disabled, either via blocklist, about:flags 
or the command line.
Disabled Features: video_decode
ANGLE Features
allow_compressed_formats (Frontend workarounds): Enabled: true
Allow compressed formats
disable_anisotropic_filtering (Frontend workarounds): Disabled
Disable support for anisotropic filtering
disable_program_binary (Frontend features) anglebug:5007: Disabled
Disable support for GL_OES_get_program_binary
disable_program_caching_for_transform_feedback (Frontend workarounds): 
Disabled: IsAndroid() && isQualcomm
On some GPUs, program binaries don't contain transform feedback varyings
lose_context_on_out_of_memory (Frontend workarounds): Enabled: true
Some users rely on a lost context notification if a GL_OUT_OF_MEMORY error 
occurs
scalarize_vec_and_mat_constructor_args (Frontend workarounds) 398694: Enabled: 
true
Always rewrite vec/mat constructors to be consistent
sync_framebuffer_bindings_on_tex_image (Frontend workarounds): Disabled: 
IsWindows() && isIntel
On some drivers TexImage sometimes seems to interact with the Framebuffer
add_and_true_to_loop_condition (OpenGL workarounds): Disabled: IsApple() && 
isIntel
Calculation of loop conditions in for and while loop has bug
adjust_src_dst_region_for_blitframebuffer (OpenGL workarounds) 830046: Enabled: 
IsLinux() || (IsAndroid() && isNvidia) || (IsWindows() && isNvidia)
Many platforms have issues with blitFramebuffer when the parameters are large.
allow_clear_for_robust_resource_init (OpenGL workarounds) 883276: Disabled: 
IsApple()
Using glClear for robust resource initialization is buggy on some drivers and 
leads to texture corruption. Default to data uploads except on MacOS where it 
is very slow.
always_call_use_program_after_link (OpenGL workarounds) 110263: Enabled: true
Always call useProgram after a successful link to avoid a driver bug
avoid_1_bit_alpha_texture_formats (OpenGL workarounds): Disabled: 
functions->standard == STANDARD_GL_DESKTOP && isAMD
Issue with 1-bit alpha framebuffer formats
avoid_dxt1_srgb_texture_format (OpenGL workarounds): Disabled: IsWindows() && 
isIntel
Replaces DXT1 sRGB with DXT1 sRGB Alpha as a driver bug workaround.
clamp_array_access (OpenGL workarounds) anglebug:2978: Enabled: IsAndroid() || 
isAMD || !functions->hasExtension("GL_KHR_robust_buffer_access_behavior")
Clamp uniform array access to avoid reading invalid memory.
clamp_frag_depth (OpenGL workarounds): Disabled: isNvidia
gl_FragDepth is not clamped correctly when rendering to a floating point depth 
buffer
clamp_msc_rate (OpenGL workarounds) 1042393: Disabled: IsLinux() && IsWayland()
Some drivers return bogus values for GetMscRate, so we clamp it to 30Hz
clamp_point_size (OpenGL workarounds): Disabled: IsAndroid() || isNvidia
The point size range reported from the API is inconsistent with the actual 
behavior
clear_to_zero_or_one_broken (OpenGL workarounds) 710443: Disabled: IsApple() && 
isIntel && GetMacOSVersion() < OSVersion(10, 12, 6)
Clears when the clear color is all zeros or ones do not work.

Bug#979135: chromium: GPU hw-accel: ANGLE libs cause a lot of errors and warnings

[Sedat Dilek]

Package: chromium
Version: 87.0.4280.88-0.4
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

Michel Le Bihan requested me to file a bug about this issue.

First some words to my environment:

1. Primarily, I am here on Debian/testing AMD64.
2. Selected packages like KDE/Plasma v5.20.4 are stolen from Debian/unstable.
3. With Linux v5.10.4 (LTS) available in Debian/unstable I jumped to
use it as my default Linux-kernel.
   ( I also do build my own Linux-kernels with LLVM/Clang version 11.0.1-rc2. )

In the chromium advanced settings I have enabled "GPU hardware-acceleration".

When I use libEGL.so and libGLESv2.so from version 0.4 I see dozens of
ERRORs and WARNINGs in the logs (see post-scriptum).

That does not happen when replacing the ANGLE libs from
google-chrome-stable version 87.0.4280.88-1 package.

Archive libEGL.so and libGLESv2.so from Debian:

root# cd /usr/lib/chromium/
root# cp -av libEGL.so libEGL.so.debian
root# cp -av libGLESv2.so libGLESv2.so.debian

Copy libEGL.so and libGLESv2.so from google-chrome-stable:

root# cp -av /opt/google/chrome/libEGL.so /usr/lib/chromium/
root# cp -av /opt/google/chrome/libGLESv2.so /usr/lib/chromium/

The file-sizes differ:

root# LC_ALL=C ll /usr/lib/chromium/lib*.so*
-rw-r--r-- 1 root root 229K Dec  2 02:58 /usr/lib/chromium/libEGL.so
-rw-r--r-- 1 root root  36K Dec 29 10:58 /usr/lib/chromium/libEGL.so.debian
-rw-r--r-- 1 root root 229K Dec  2 02:58 /usr/lib/chromium/libEGL.so.google
-rw-r--r-- 1 root root 6.7M Dec  2 02:58 /usr/lib/chromium/libGLESv2.so
-rw-r--r-- 1 root root 4.8M Dec 29 10:58 /usr/lib/chromium/libGLESv2.so.debian
-rw-r--r-- 1 root root 6.7M Dec  2 02:58 /usr/lib/chromium/libGLESv2.so.google

When I remove all the ANGLE libs from /usr/lib/chromium/ directory and
start from a terminal (see [2]):

user$ chromium --use-gl=desktop

I do NOT see any ERRORs and WARNINGs.

I will attach my full chrome://gpu logs in the next email.
( Dunno how to do that with reportbug run from shell. )

Thanks.

Regards,
- Sedat -

[1] https://bugs.debian.org/977870
[2] https://bugs.debian.org/977870/#32

P.S.: Warnings and errors with ANGLE libs shipped with version 0.4

Log Messages
[19666:19666:1231/194737.468589:ERROR:sandbox_linux.cc(374)] :
InitializeSandbox() called with multiple threads in process
gpu-process.
[19666:19666:1231/194737.773848:WARNING:angle_platform_impl.cc(48)] :
ProgramGL.cpp:990 (checkLinkStatus): Program link or binary loading
failed with no info log.
[19666:19666:1231/194737.773982:ERROR:shared_context_state.cc(74)] :
Skia shader compilation error  Errors: Invalid
program binary version.
[19666:19666:1231/194737.977867:WARNING:angle_platform_impl.cc(48)] :
ProgramGL.cpp:990 (checkLinkStatus): Program link or binary loading
failed with no info log.
[19666:19666:1231/194737.978016:ERROR:shared_context_state.cc(74)] :
Skia shader compilation error  Errors: Invalid
program binary version.
[19666:19666:1231/194738.014151:WARNING:angle_platform_impl.cc(48)] :
ProgramGL.cpp:990 (checkLinkStatus): Program link or binary loading
failed with no info log.
[19666:19666:1231/194738.014319:ERROR:shared_context_state.cc(74)] :
Skia shader compilation error  Errors: Invalid
program binary version.
[19666:19666:1231/194738.020256:ERROR:angle_platform_impl.cc(43)] :
renderergl_utils.cpp:2088 (ClearErrors): Preexisting GL error
0x0500 as of
../../third_party/angle/src/libANGLE/renderer/gl/TextureGL.cpp,
setStorage:987.
[19666:19666:1231/194738.333856:WARNING:angle_platform_impl.cc(48)] :
ProgramGL.cpp:990 (checkLinkStatus): Program link or binary loading
failed with no info log.
[...]

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (99, 'buildd-unstable'), (99,
'buildd-experimental'), (99, 'experimental'), (99, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.4-3-amd64-clang11-cfi (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 chromium depends on:
ii  chromium-common  87.0.4280.88-0.4
ii  libasound2   1.2.4-1
ii  libatk-bridge2.0-0   2.38.0-1
ii  libatk1.0-0  2.36.0-2
ii  libatomic1   10.2.1-3
ii  libatspi2.0-02.38.0-2
ii  libavcodec58 7:4.3.1-5
ii  libavformat587:4.3.1-5
ii  libavutil56  7:4.3.1-5
ii  libc62.31-6
ii  libcairo21.16.0-4
ii  libcups2 2.3.3op1-3
ii  libdbus-1-3  1.12.20-1
ii  libdrm2  2.4.103-2
ii  libevent-2.1-7   2.1.12-stable-1
ii  libexpat12.2.10-1
ii  libflac8 1.3.3-2
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgbm1  20.2.6-1
ii  libgcc-s110.2.1-3

Bug#977870: Failed to load /usr/lib/chromium/libGLESv2.so

[Sedat Dilek]

Inspired by commit "Install ANGLE EGL and GLESv2 libs" in Michel's
personal salsa Git repo (see [1]):

I have downloaded google-chrome-stable_current_amd64.deb version
87.0.4280.88 deb file.

Copied libEGL.so and libGLESv2.so files from /opt/google/chrome to
/usr/lib/chromium.

Hardware acceleration seems to work here:

URL: chrome://gpu/

Graphics Feature Status
Canvas: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Out-of-process Rasterization: Disabled
OpenGL: Enabled
Hardware Protected Video Decode: Unavailable
Rasterization: Hardware accelerated on all pages
Skia Renderer: Enabled
Video Decode: Software only. Hardware acceleration disabled
Vulkan: Disabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated

Full GPU report attached.

- sed@ -

[1] 
https://salsa.debian.org/mimi8/chromium/-/commit/c1265133b36931b3a8c4ffd8fc64b5e90fc02fe4

Graphics Feature Status
Canvas: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Out-of-process Rasterization: Disabled
OpenGL: Enabled
Hardware Protected Video Decode: Unavailable
Rasterization: Hardware accelerated on all pages
Skia Renderer: Enabled
Video Decode: Software only. Hardware acceleration disabled
Vulkan: Disabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated
Driver Bug Workarounds
adjust_src_dst_region_for_blitframebuffer
clear_uniforms_before_first_program_use
decode_encode_srgb_for_generatemipmap
exit_on_context_lost
msaa_is_slow
scalarize_vec_and_mat_constructor_args
disabled_extension_GL_KHR_blend_equation_advanced
disabled_extension_GL_KHR_blend_equation_advanced_coherent
Problems Detected
Protected video decoding with swap chain is for certain Intel and AMD GPUs on 
Windows: 1093625
Disabled Features: protected_video_decode
Clear uniforms before first program use on all platforms: 124764, 349137
Applied Workarounds: clear_uniforms_before_first_program_use
Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565
Applied Workarounds: msaa_is_slow
adjust src/dst region if blitting pixels outside framebuffer on Linux Intel: 
664740
Applied Workarounds: adjust_src_dst_region_for_blitframebuffer
Disable KHR_blend_equation_advanced until cc shaders are updated: 661715
Applied Workarounds: disable(GL_KHR_blend_equation_advanced), 
disable(GL_KHR_blend_equation_advanced_coherent)
Decode and Encode before generateMipmap for srgb format textures on Linux Mesa 
ANGLE path: 634519
Applied Workarounds: decode_encode_srgb_for_generatemipmap
Some drivers can't recover after OUT_OF_MEM and context lost: 893177
Applied Workarounds: exit_on_context_lost
Accelerated video decode has been disabled, either via blocklist, about:flags 
or the command line.
Disabled Features: video_decode
ANGLE Features
allow_compressed_formats (Frontend workarounds): Enabled: true
Allow compressed formats
disable_anisotropic_filtering (Frontend workarounds): Disabled
Disable support for anisotropic filtering
disable_program_binary (Frontend features) anglebug:5007: Disabled
Disable support for GL_OES_get_program_binary
disable_program_caching_for_transform_feedback (Frontend workarounds): 
Disabled: IsAndroid() && isQualcomm
On some GPUs, program binaries don't contain transform feedback varyings
lose_context_on_out_of_memory (Frontend workarounds): Enabled: true
Some users rely on a lost context notification if a GL_OUT_OF_MEMORY error 
occurs
scalarize_vec_and_mat_constructor_args (Frontend workarounds) 398694: Enabled: 
true
Always rewrite vec/mat constructors to be consistent
sync_framebuffer_bindings_on_tex_image (Frontend workarounds): Disabled: 
IsWindows() && isIntel
On some drivers TexImage sometimes seems to interact with the Framebuffer
add_and_true_to_loop_condition (OpenGL workarounds): Disabled: IsApple() && 
isIntel
Calculation of loop conditions in for and while loop has bug
adjust_src_dst_region_for_blitframebuffer (OpenGL workarounds) 830046: Enabled: 
IsLinux() || (IsAndroid() && isNvidia) || (IsWindows() && isNvidia)
Many platforms have issues with blitFramebuffer when the parameters are large.
allow_clear_for_robust_resource_init (OpenGL workarounds) 883276: Disabled: 
IsApple()
Using glClear for robust resource initialization is buggy on some drivers and 
leads to texture corruption. Default to data uploads except on MacOS where it 
is very slow.
always_call_use_program_after_link (OpenGL workarounds) 110263: Enabled: true
Always call useProgram after a successful link to avoid a driver bug
avoid_1_bit_alpha_texture_formats (OpenGL workarounds): Disabled: 
functions->standard == STANDARD_GL_DESKTOP && isAMD
Issue with 1-bit alpha framebuffer formats
avoid_dxt1_srgb_texture_format (OpenGL workarounds): Disabled: IsWindows() && 
isIntel
Replaces DXT1 sRGB with DXT1 sRGB Alpha as a driver bug workaround.
clamp_array_access 

Bug#977870: Failed to load /usr/lib/chromium/libGLESv2.so

[Sedat Dilek]

> No symlinks are needed in /usr/lib/chromium/ directory.
>

If you want GPU hardware-acceleration (hw-accel) the above is *not* true, sorry.

When I use the so-libs shipped by libgles2 and libegl1 packages and
activate hw-accel in chromium I see in the URL:  there
is hw-accel enabled but my CPU gets hot and its cooler gets loud.

The workaround is to not use GPU hw-accel in chromium for now.

- Sedat -

Bug#977870: Failed to load /usr/lib/chromium/libGLESv2.so

[Sedat Dilek]

Hi,

today, I upgraded to chromium version 87.0.4280.88-0.3 from Debian/unstable.

You need these (systemwide) symlinks:

cd /usr/lib/x86_64-linux-gnu

ln -sf libGLESv2.so.2 libGLESv2.so
ln -sf libEGL.so.1 libEGL.so

No symlinks are needed in /usr/lib/chromium/ directory.

So, this should be better reported to the maintainers of libegl1 and
libgles2 packages.

Checking for GPU hardware-acceleration ERRORs (which I see here too):

terminal$ LC_ALL=en chromium --disable-gpu

Alternatively:

Settings > Advanced > System > Use hardware acceleration if available
<--- Disable here

Solved the issues with GPU hardware-acceleration.

Thanks Michel and the bug-reporter.

Regards,
- Sedat -

Bug#953948: Fwd: libsnmp40: I do NOT want to have any MySQL/MariaDB dependencies on my Debian-system

[Sedat Dilek]

This is addressed in Debian Bug #953948 which will be hopefully fixed
with libsnmp40 (5.9+dfsg-2).
For the patch see [2].

- Sedat -

[1] https://bugs.debian.org/953948
[2] 
https://salsa.debian.org/debian/net-snmp/-/commit/926cb67414a70a501752d1b5c8b00db1c949463f

-- Forwarded message -
From: Sedat Dilek 
Date: Sun, Sep 6, 2020 at 11:24 AM
Subject: Re: libsnmp40: I do NOT want to have any MySQL/MariaDB
dependencies on my Debian-system
To: Craig Small ,



On Sun, Sep 6, 2020 at 10:54 AM Sedat Dilek  wrote:
>
> Hi Craig,
>
> I removed all *MySQL/MariaDB* dependencies by switching akonadi-server
> (KDE/Plasma) to PostgreSQL in my Debian/unstable system (see my howto
> attached in [1]).
>
> Please, please please if a database is now required offer alternative
> support for SQLite and/or PostgreSQL.
>
> Unsure if I will downgrade SNMP stuff for now.
>
> Shall I open a bug-report?
>
> Thanks.
>
> Regards,
> - Sedat -
>
> [1] https://lists.debian.org/debian-qt-kde/2020/09/msg00066.html

When I put "libsnmp-base" package on hold (independently of putting
libsnmp35 libsane sane-utils on hold):

root# dpkg --get-selections | grep hold
libsnmp-base

root# LC_ALL=C apt-get dist-upgrade -V -t unstable
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
...
  libsnmp35 (5.8+dfsg-5)
...
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
  libmariadb3 (1:10.3.24-2)
  libsnmp40 (5.9+dfsg-1)
  linux-perf-5.8 (5.8.7-1)
  mariadb-common (1:10.3.24-2)
  mysql-common (5.8+1.0.5)
The following packages have been kept back:
  libsnmp-base (5.8+dfsg-5 => 5.9+dfsg-1)
The following packages will be upgraded:
  at-spi2-core (2.36.0-3 => 2.36.1-1)
  gir1.2-atspi-2.0 (2.36.0-3 => 2.36.1-1)
  ifstat (1.1-8.1+b2 => 1.1-8.1+b3)
  libatspi2.0-0 (2.36.0-3 => 2.36.1-1)
  libfluidsynth2 (2.1.3-1 => 2.1.4-1)
  libsane (1.0.27-3.2+b1 => 1.0.27-3.2+b2)
  linux-libc-dev (5.7.17-1 => 5.8.7-1)
  linux-perf (5.7.17-1 => 5.8.7-1)
  sane-utils (1.0.27-3.2+b1 => 1.0.27-3.2+b2)
9 upgraded, 5 newly installed, 0 to remove and 1 not upgraded.
Need to get 8623 kB of archives.
After this operation, 15.1 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.

I expect when I hold "libsnmp-base" that a newer libsnmpXX will not be
installed on any upgrades.
Why is "libsnmp40" still upgrade-/install-able?

Can you enlighten me?

- Sedat -

Bug#955469: initramfs-tools-core: Enable zstandard support

[Sedat Dilek]

Now in Linus Git tree.

[1] says:

Merge tag 'x86-boot-2020-08-03' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

Pull x86 boot updates from Ingo Molnar:
"The main change in this cycle was to add support for ZSTD-compressed
kernel and initrd images. ZSTD has a very fast decompressor, yet it
compresses better than gzip"

- Sedat -

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c0dfadfed87489fa6126ece161a14c2d15dbdc79

Bug#955469: initramfs-tools-core: Enable zstandard support

[Sedat Dilek]

On Sat, Aug 1, 2020 at 12:27 AM Norbert Lange  wrote:
>
> Am Fr., 31. Juli 2020 um 16:48 Uhr schrieb Sedat Dilek 
> :
> >
> > Just FYI:
> >
> > Version 10 was now accepted in .
> >
> > Let's hope this will get into upcoming Linux v5.9.
> >
> > - Sedat -
> >
> > [1] https://github.com/terrelln/linux/commits/zstd-v10
> > [2] 
> > https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/?h=x86/boot
>
> Thanks,
>
> I updated the patch, and made a merge request there:
> https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests
>

Hi Norbert,

Thank you, too.

You mean [1]?

[ mkinitramfs ]

+zstd) compress="zstd -q -19 -T0" ;;

>From my kernel build-log:

{ cat arch/x86/boot/compressed/vmlinux.bin
arch/x86/boot/compressed/vmlinux.relocs | zstd -22 --ultra; printf
\014\015\315\001; } > arch/x86/boot/compressed/vmlinux.bin.zst

Thus I have analog here:

root# diff -uprN /usr/sbin/mkinitramfs.orig /usr/sbin/mkinitramfs
--- /usr/sbin/mkinitramfs.orig  2020-04-28 05:56:17.0 +0200
+++ /usr/sbin/mkinitramfs   2020-07-09 10:35:35.119280519 +0200
@@ -189,6 +189,7 @@ xz) compress="xz --check=crc32"
# If we're not doing a reproducible build, enable multithreading
test -z "${SOURCE_DATE_EPOCH}" && compress="$compress --threads=0"
;;
+zstd)  compress="zstd -22 --ultra -v" ;;
 bzip2|lzma|lzop)
# no parameters needed
;;

Regards,
- Sedat -


[1] 
https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/33/diffs?commit_id=e94f410c71e90598b4fabca3970c7f282b5bd0a0

Bug#955469: initramfs-tools-core: Enable zstandard support

[Sedat Dilek]

Just FYI:

Version 10 was now accepted in .

Let's hope this will get into upcoming Linux v5.9.

- Sedat -

[1] https://github.com/terrelln/linux/commits/zstd-v10
[2] https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/?h=x86/boot

Bug#965165: policykit-1: polkit.service broken after switch to /usr/libexec

[Sedat Dilek]

Addendum:

This is no more needed:
# rm -r /usr/lib/policykit-1

After applied the above diff run:

# systemctl daemon-reload
# systemctl restart polkit.service

# systemctl status polkit.service
● polkit.service - Authorization Manager
 Loaded: loaded (/lib/systemd/system/polkit.service; static;
vendor preset: enabled)
 Active: active (running) since Fri 2020-07-17 05:35:17 CEST; 9s ago
   Docs: man:polkit(8)
   Main PID: 2858 (polkitd)
  Tasks: 4 (limit: 9395)
 Memory: 5.3M
 CGroup: /system.slice/polkit.service
 └─2858 /usr/libexec/polkitd --no-debug

Jul 17 05:35:17 iniza systemd[1]: Starting Authorization Manager...
Jul 17 05:35:17 iniza polkitd[2858]: started daemon version 0.105
using authority implementation `local' version `0.105'
Jul 17 05:35:17 iniza systemd[1]: Started Authorization Manager.

- Sedat -

Bug#965165: policykit-1: polkit.service broken after switch to /usr/libexec

[Sedat Dilek]

Package: policykit-1
Version: 0.105-27
Severity: normal
Tags: patch
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

first the installation on upgrade fails like this:

Setting up policykit-1 (0.105-27) ...
chown: cannot access '/usr/lib/policykit-1/polkit-agent-helper-1': No
such file or directory
dpkg: error processing package policykit-1 (--configure):
 installed policykit-1 package post-installation script subprocess
returned error exit status 1

That fixed the installation:

# mkdir -p /usr/lib/policykit-1/polkit-agent-helper-1

But the polkit.service fails to start.

Checking the commits on  revealed there was a move/switch to 
/usr/libexec.

This fixes the issue for me (polkit.service):

--- /lib/systemd/system/polkit.service.orig 2020-07-17 00:50:43.0 
+0200
+++ /lib/systemd/system/polkit.service  2020-07-17 05:34:25.292147729 +0200
@@ -5,4 +5,4 @@ Documentation=man:polkit(8)
 [Service]
 Type=dbus
 BusName=org.freedesktop.PolicyKit1
-ExecStart=/usr/lib/policykit-1/polkitd --no-debug
+ExecStart=/usr/libexec/polkitd --no-debug

Thanks.

Regards,
- Sedat -

[1] 
https://salsa.debian.org/utopia-team/polkit/-/commit/90e87fe8887ee212fa05739f0b549546fea680ff

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (99, 'buildd-unstable'), (99, 
'buildd-experimental'), (99, 'experimental'), (99, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.8.0-rc5-9-amd64-llvm11-ias (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 policykit-1 depends on:
ii  dbus 1.12.20-1
ii  libc62.31-1
ii  libexpat12.2.9-1
ii  libglib2.0-0 2.64.4-1
ii  libpam-systemd [logind]  245.6-3
ii  libpam0g 1.3.1-5
ii  libpolkit-agent-1-0  0.105-27
ii  libpolkit-gobject-1-00.105-27
ii  libsystemd0  245.6-3

policykit-1 recommends no packages.

policykit-1 suggests no packages.

Versions of packages policykit-1 is related to:
pn  elogind 
pn  libpam-elogind  
ii  libpam-systemd  245.6-3
ii  systemd 245.6-3

-- no debconf information

Bug#964550: clang-10: Version handling/naming for RC releases

[Sedat Dilek]

On Thu, Jul 9, 2020 at 11:17 AM Sylvestre Ledru  wrote:
>
> Le 09/07/2020 à 11:01, Sedat Dilek a écrit :
> > On Wed, Jul 8, 2020 at 5:32 PM Sylvestre Ledru  wrote:
> >>
> >>> As pointed out by Sylvestre in [3] he is trying to keep packages in the 
> >>> Debian repositories
> >>> in balance with .
> >>>
> >>> As I am interested in having the best packages in Debian I am reporting 
> >>> here not upstream.
> >>
> >> As I said in the llvm bt, it is very unlikely to happen. This isn't a big 
> >> deal and it doesn't break any tool :)
> >>
> >
> > Can you enlighten me what you mean by "balance"?
> > And the correlation with the version naming/handling you have chosen?
>
> It is tricky because of the situation between:
> * apt.llvm.org with three branches
> * stable packages (ex: 10.0)
> * rc packages (ex: 10.0.1 rc4)
> * snapshot from the VCS (ex: 11~++20200701093119+ffee8040534-1~exp1)
>
> And you can have llvm-toolchain-9 from Debian official, -10 for apt.llvm.org 
> and -11 from Debian experimental.
>

Personally, I am to 99,9% that only experienced users try snapshot
packages (e.g. from ).

There should be no guarantee all packages from several branches and
repositories work together.
What counts are the packages in the official Debian repositories.

I like your offer - or to be more precise - from the Debian LLVM team
- and try to keep them working together.

> I need to make sure that the expected behavior is what users are getting
> and that the upgrade path still works (upgrading from version x-1 to x).
> Changing this is always a lot of work as it requires synchronized 
> uploads/updating scripts
> (not mentioning the potential regressions)
>

I like that to be able to have different (major) versions of
llvm-toolchains co-installable and switch via llvm-version-suffix.
Again, thanks for making this happen!

> Anyway, I am not sure to see what your point beside consistency in Debian 
> (note that, AFAIK? there isn't any policy).
> I have been using that patterns since the svn => git upstream migration (it 
> was similar with git).
> And at the end, Debian Stable only ships with clear versions like 10.0.1-12.
>

That's a pity - there does not exist clear rules for building from any VCS.
As demonstrated by my list of installed packages it differs.

I try to read between the lines (hocuspocus):

I check all available clang-10 packages:

root# LC_ALL=C apt-cache policy clang-10
clang-10:
  Installed: 1:10.0.1~+rc4-1
  Candidate: 1:10.0.1~+rc4-1
  Version table:
 1:10.0.1~++20200708124224+ef32c611aa2-1~exp1~20200707224820.197 99
 99 https://apt.llvm.org/unstable llvm-toolchain-10/main amd64 Packages
 *** 1:10.0.1~+rc4-1 100
 99 https://incoming.debian.org/debian-buildd
buildd-unstable/main amd64 Packages
 99 http://ftp.debian.org/debian unstable/main amd64 Packages
 99 https://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
 1:10.0.1~+rc2-1~exp1 99
 99 http://ftp.debian.org/debian experimental/main amd64 Packages
 99 https://deb.debian.org/debian experimental/main amd64 Packages
 1:10.0.0-4 500
500 http://ftp.debian.org/debian testing/main amd64 Packages
500 https://deb.debian.org/debian testing/main amd64 Packages

As you can see I - as an experienced Debian user - have set APT (pin)
priorities.

Packages from  are from my understanding from a "third
party" repository.
I respect this by setting appropriate APT prio.

As I want to have a "Debian/testing AMD64" system I treat packages
from Debian/unstable and Debian/experimental the same way.

I have to explicitly pass parameters like "-t $debian-branch" or "-t
llvm-toolchain-10" to install desired packages from repositories other
than Debian/testing AMD64.

Looking into my crystal-ball I guess you want by your "~+rc" and "~++"
prefixes trick to order the available installation-candidate(s)?

Again "~rcN" after an "upstream-version-string" is uncommon (but allowed).

BTW, I disagree with the VCS version-string handling:
Upstream-version-string should be "11.0.0" not "11" for snapshot
versions from Debian/experimental and /llvm-toolchain.

To clarify:
You are responsible for all the repositories - it is up to you.

Important for me:
The version-string should be exact telling me what was the (upstream)
base for the generated packages.

Just my €0,02.

- Sedat -

Bug#964550: clang-10: Version handling/naming for RC releases

[Sedat Dilek]

On Wed, Jul 8, 2020 at 5:32 PM Sylvestre Ledru  wrote:
>
> > As pointed out by Sylvestre in [3] he is trying to keep packages in the 
> > Debian repositories
> > in balance with .
> >
> > As I am interested in having the best packages in Debian I am reporting 
> > here not upstream.
>
> As I said in the llvm bt, it is very unlikely to happen. This isn't a big 
> deal and it doesn't break any tool :)
>

Can you enlighten me what you mean by "balance"?
And the correlation with the version naming/handling you have chosen?

Thanks.

- Sedat -

Bug#964553: clang-11: Version handling/naming for packages build-from-upstream-git

[Sedat Dilek]

Package: clang-11
Version: 1:11~++20200701093119+ffee8040534-1~exp1
Severity: wishlist

Dear Maintainer,

as reported in LLVM bug #38998 "llvm-toolchain: Include Debian version string 
like for gcc"
the version handling (naming) for packages build-from-upstream-git looks 
uncommon to me.

In comment #24 I have listed all packages having a "git" on my Debian/testing 
(sid) AMD64 system:

root# dpkg -l | grep '\~git' | awk '/^ii/ {print $1 " " $2 " " $3}' | column -t
[ EMPTY ]

root# dpkg -l | grep '\+git' | awk '/^ii/ {print $1 " " $2 " " $3}' | column -t
ii  crda4.14+git20191112.9856751-1
ii  libfakekey0:amd64   0.3+git20170516-2
ii  libmusicbrainz5-2:amd64 5.1.0+git20150707-9
ii  libmusicbrainz5cc2v5:amd64  5.1.0+git20150707-9
ii  libpfm4:amd64   4.10.1+git44-ga2909cd-1
ii  libsox-fmt-alsa:amd64   14.4.2+git20190427-2
ii  libsox-fmt-base:amd64   14.4.2+git20190427-2
ii  libsox3:amd64   14.4.2+git20190427-2
ii  libspatialaudio0:amd64  0.3.0+git20180730+dfsg1-2+b1
ii  libtiff5:amd64  4.1.0+git191117-2
ii  libx264-155:amd64   2:0.155.2917+git0a84d98-2
ii  lua-socket:amd643.0~rc1+git+ac3201d-4
ii  sox 14.4.2+git20190427-2
ii  xserver-xorg-video-intel2:2.99.917+git20200226-1
ii  xserver-xorg-video-qxl  0.1.5+git20200331-1

I remember when I build myself from git I used to:
'upstream-version' plus '+git' (prefered by Debian see above) or `~git` plus 
'posix-date' plus '.commit-hashid' (12 digits) plus 'debian-revision'

Transform for version-string "1:11~++20200701093119+ffee8040534-1~exp1" (latest 
in Debian/experimental):

11.0.0+git20200701.ffee8040534-1

To be read:
upstream-version:   11.0.0
"git" version-info: "git" + "posix-date" (here: "20200701" means 01-Jul-2020) + 
"commit-hashid" (here: "ffee8040534")
debian-revision:1

We do not need any informations concerning the hh:mm:ss of the commit.
Havin the (POSIX) date and the commit-hashid is clear and obvious enough.
I prefer a "." (dot) between POSIX-date and commit-hashid.

The suffix '~exp1' - if this common or a rule for packages in 
Debian/experimental - can be kept otherwise you can drop it, too.

Thanks.

Regards,
- Sedat -

[1] https://bugs.llvm.org/show_bug.cgi?id=38998
[2] https://bugs.llvm.org/show_bug.cgi?id=38998#c24

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (99, 'buildd-unstable'), (99, 
'buildd-experimental'), (99, 'experimental'), (99, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.8.0-rc4-4-amd64-llvm11-ias (SMP w/4 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages clang-11 depends on:
ii  binutils2.34.90.20200706-1
ii  libc6   2.30-8
ii  libc6-dev   2.30-8
ii  libclang-common-11-dev  1:11~++20200701093119+ffee8040534-1~exp1
ii  libclang-cpp11  1:11~++20200701093119+ffee8040534-1~exp1
ii  libclang1-111:11~++20200701093119+ffee8040534-1~exp1
ii  libgcc-9-dev9.3.0-14
ii  libgcc-s1   10.1.0-4
ii  libllvm11   1:11~++20200701093119+ffee8040534-1~exp1
ii  libobjc-9-dev   9.3.0-14
ii  libstdc++-9-dev 9.3.0-14
ii  libstdc++6  10.1.0-4

Versions of packages clang-11 recommends:
pn  libomp-11-dev  
pn  llvm-11-dev
ii  python33.8.2-3

Versions of packages clang-11 suggests:
pn  clang-11-doc  

-- no debconf information

Bug#964550: clang-10: Version handling/naming for RC releases

[Sedat Dilek]

Package: clang-10
Version: 1:10.0.1~+rc3-1
Severity: wishlist

Dear Maintainer,

as reported in LLVM bug #38998 "llvm-toolchain: Include Debian version string 
like for gcc"
the version handling (naming) looks uncommon to me.

In comment #23 I listed all "rc" packages I have installed on my Debian/testing 
(sid) AMD64 system:

root# dpkg -l | grep 'rc[0-9]' | grep -v dileks | awk '/^ii/ {print $1 " " $2 " 
" $3}' | column -t

ii  asciidoc-base   9.0.0~rc2-1
ii  asciidoc-common 9.0.0~rc2-1
ii  clang-101:10.0.1~+rc3-1
ii  libclang-common-10-dev  1:10.0.1~+rc3-1
ii  libclang-cpp10  1:10.0.1~+rc3-1
ii  libclang1-101:10.0.1~+rc3-1
ii  libllvm10:amd64 1:10.0.1~+rc3-1
ii  libpython3.8:amd64  3.8.4~rc1-1
ii  libpython3.8-minimal:amd64  3.8.4~rc1-1
ii  libpython3.8-stdlib:amd64   3.8.4~rc1-1
ii  libspeex1:amd64 1.2~rc1.2-1.1
ii  libspeexdsp1:amd64  1.2~rc1.2-1.1
ii  lld-10  1:10.0.1~+rc3-1
ii  llvm-10 1:10.0.1~+rc3-1
ii  llvm-10-runtime 1:10.0.1~+rc3-1
ii  lua-socket:amd643.0~rc1+git+ac3201d-4
ii  python3.8   3.8.4~rc1-1
ii  python3.8-minimal   3.8.4~rc1-1

So it looks like "common sense" to have "upstream-version" plus "~rcX" followed 
by "-debian-revision".

More correct to me looks a version-string (here: "1:10.0.1~+rc3-1"):

(1:)10.0.1~rc3-1 (dropping "+" after "~")

To be read:
upstream-version: 10.0.1
"rc" release-no:  rc3
debian-revision:  1

As pointed out by Sylvestre in [3] he is trying to keep packages in the Debian 
repositories
in balance with .

As I am interested in having the best packages in Debian I am reporting here 
not upstream.

Thanks.

Regards,
- Sedat -

[1] https://bugs.llvm.org/show_bug.cgi?id=38998
[2] https://bugs.llvm.org/show_bug.cgi?id=38998#c23
[3] https://bugs.llvm.org/show_bug.cgi?id=38998#c29

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (99, 'buildd-unstable'), (99, 
'buildd-experimental'), (99, 'experimental'), (99, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.8.0-rc4-4-amd64-llvm11-ias (SMP w/4 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages clang-10 depends on:
ii  binutils2.34.90.20200706-1
ii  libc6   2.30-8
ii  libc6-dev   2.30-8
ii  libclang-common-10-dev  1:10.0.1~+rc3-1
ii  libclang-cpp10  1:10.0.1~+rc3-1
ii  libclang1-101:10.0.1~+rc3-1
ii  libgcc-9-dev9.3.0-14
ii  libgcc-s1   10.1.0-4
ii  libllvm10   1:10.0.1~+rc3-1
ii  libobjc-9-dev   9.3.0-14
ii  libstdc++-9-dev 9.3.0-14
ii  libstdc++6  10.1.0-4

Versions of packages clang-10 recommends:
pn  libomp-10-dev  
pn  llvm-10-dev
ii  python33.8.2-3

Versions of packages clang-10 suggests:
pn  clang-10-doc  

-- no debconf information

Bug#956672: rtkit activation fails, because service unit is installed at the wrong place

[Sedat Dilek]

Attached is the patch I used.

- sed@ -
Fom: Sedat Dilek 
Date: Wed, 22 Apr 2020 10:51:32 +0200
Subject: Fix systemunitdir variable to handle systemd service file location

Suggested-by: Felipe Sateler 

--- rtkit-0.13.orig/meson.build
+++ rtkit-0.13/meson.build
@@ -58,7 +58,7 @@ if policydir == ''
 policydir = get_option('datadir') / 'polkit-1' / 'actions'
 endif
 
-systemunitdir = ''
+systemunitdir = get_option('systemd_systemunitdir')
 if systemunitdir == '' and systemd_dep.found()
 systemunitdir = systemd_dep.get_pkgconfig_variable(
 'systemdsystemunitdir',

Bug#956672: rtkit activation fails, because service unit is installed at the wrong place

[Sedat Dilek]

Hi,

with the suggested change from Felipe...

--- rtkit-0.13.orig/meson.build
+++ rtkit-0.13/meson.build
@@ -58,7 +58,7 @@ if policydir == ''
 policydir = get_option('datadir') / 'polkit-1' / 'actions'
 endif

-systemunitdir = ''
+systemunitdir = get_option('systemd_systemunitdir')
 if systemunitdir == '' and systemd_dep.found()
 systemunitdir = systemd_dep.get_pkgconfig_variable(
 'systemdsystemunitdir',

... the rtkit systemd service file is now at the correct place:

$ dpkg --contents rtkit_0.13-3.1~dileks_amd64.deb | grep rtkit-daemon.service
-rw-r--r-- root/root  1024 2020-04-22 10:51
./lib/systemd/system/rtkit-daemon.service

My d/c:

$ head -10 debian/changelog
rtkit (0.13-3.1~dileks) UNRELEASED; urgency=medium

  * Non-maintainer upload.
  * meson.build:
- Fix systemunitdir variable to handle systemd service file location
  * Build against libsystemd-dev (245.5-1).

 -- Sedat Dilek   Wed, 22 Apr 2020 10:51:32 +0200

rtkit (0.13-3) unstable; urgency=medium

Thanks.

Regards,
- Sedat -

Bug#956672: rtkit activation fails, because service unit is installed at the wrong place

[Sedat Dilek]

Hi,

rtkit (0.13-3) entered Debian/testing and the systemd unit file is
still at the wrong place.

testing: /usr/lib/x86_64-linux-gnu/systemd/system/rtkit-daemon.service
buster: /lib/systemd/system/rtkit-daemon.service

Sometimes it needs 3+1 attempts :-).

Bonne chance,
- Sedat -

[1] https://packages.debian.org/bullseye/amd64/rtkit/filelist
[2] https://packages.debian.org/buster/amd64/rtkit/filelist

Bug#956963: KDE/Plasma: gnome-keyring-daemon: couldn't access control socket: /run/user/1000/keyring/control

[Sedat Dilek]

Package: gnome-keyring
Version: 3.36.0-1
Severity: normal

Dear Maintainer,

I am here on Debian/testing AMD64.

While digging into a problem with Skype4Linux I fell over this in my logs:

gnome-keyring-daemon: couldn't access control socket: 
/run/user/1000/keyring/control

I have already reported this issue to pkg-gnome Maintainers.

As this annoying and can hit other people I decided to write this debian 
bug-report.

In [2] I found an inspiration to adapt this for KDE/Plasma.

I added "KDE" to the "OnlyShowIn" entry in these 3 desktop files:

[ gnome-keyring-pkcs11.desktop ]
[ gnome-keyring-secrets.desktop ]
[ gnome-keyring-ssh.desktop ]

-OnlyShowIn=GNOME;Unity;MATE;
+OnlyShowIn=GNOME;Unity;MATE;KDE;

After a logoff and re-login into SDDM I checked again my logs and the active 
gnome-keyring-daemon process:

root# journalctl -xe | grep gnome-keyring-daemon

Apr 16 23:01:03 iniza sddm-helper[7257]: gkr-pam: gnome-keyring-daemon started 
properly and unlocked keyring

dileks$ ps -ef | grep gn[o]me-keyring-daemon
dileks  7262   1  0 23:01 ?00:00:00 
/usr/bin/gnome-keyring-daemon --daemonize --login

This looks good to me.

Can you add these modifications to the *.desktop files?

Thanks in advance.

Regards,
- Sedat -

[1] 
https://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/2020-April/158216.html
[2] 
https://askubuntu.com/questions/243210/why-do-i-get-this-warning-from-gnome-keyring-in-xubuntu

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (99, 'buildd-unstable'), (99, 
'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.0-rc1-7-amd64-clang (SMP w/4 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-keyring depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.16-2
ii  dbus-x11 [dbus-session-bus]   1.12.16-2
ii  dconf-gsettings-backend [gsettings-backend]   0.36.0-1
ii  gcr   3.36.0-2
ii  libc6 2.30-4
ii  libcap-ng00.7.9-2.1+b2
ii  libcap2-bin   1:2.33-1
ii  libgck-1-03.36.0-2
ii  libgcr-base-3-1   3.36.0-2
ii  libgcrypt20   1.8.5-5
ii  libglib2.0-0  2.64.1-1
ii  p11-kit   0.23.20-1
ii  pinentry-gnome3   1.1.0-3+b1

Versions of packages gnome-keyring recommends:
ii  gnome-keyring-pkcs11  3.36.0-1
ii  libpam-gnome-keyring  3.36.0-1

gnome-keyring suggests no packages.

-- Configuration Files:
/etc/xdg/autostart/gnome-keyring-pkcs11.desktop changed:
[Desktop Entry]
Type=Application
Name[af]=Sertifikaat- en sleutelberging
Name[ar]=مخزن الشهادات والمفاتيح
Name[as]=প্ৰমাণপত্ৰ আৰু কি সংৰক্ষণ
Name[ast]=Certificaos y almacenamientu de claves
Name[be]=Сховішча сертыфікатаў і ключоў
Name[bg]=Съхранение на сертификати и ключове
Name[bn]=সার্টিফিকেট এবং কী স্টোরেজ
Name[bn_IN]=সার্টিফিকেট এবং কি সংগ্রহস্থল
Name[bs]=Skladište sertifikata i ključeva
Name[ca]=Magatzem de certificats i de claus
Name[ca@valencia]=Magatzem de certificats i de claus
Name[ckb]=کۆکەرەوەی بڕوانامە و کلیل
Name[cs]=Odemknout certifikáty a umístění klíčů
Name[da]=Certifikat- og nøglelager
Name[de]=Zertifikat-/Schlüsselverwahrung
Name[el]=Αποθήκη πιστοποιητικών και κλειδιών
Name[en_GB]=Certificate and Key Storage
Name[eo]=Memorejo de atestiloj kaj ŝlosiloj
Name[es]=Certificados y almacenamiento de claves
Name[et]=Sertifikaadi- ja võtmehoidla
Name[eu]=Ziurtagirien/gakoen biltegia
Name[fa]=مخزن کلید و گواهی‌نامه
Name[fi]=Varmenne- ja avainsäilö
Name[fr]=Stockage de certificats et de clés
Name[fur]=Archivi certificâts e clâfs
Name[gd]=Teisteanas agus stòras na h-iuchrach
Name[gl]=Almacenamento de chave ou certificado
Name[gu]=પ્રમાણપત્ર અને કી સંગ્રહ
Name[he]=אחסון תעודה ומפתח
Name[hi]=कुंजी भंडार प्रमाणित करें
Name[hr]=Vjerodajnice i spremište ključeva
Name[hu]=Tanúsítvány- és kulcstároló
Name[id]=Penyimpanan Kunci dan Sertifikat
Name[is]=Geymsla skilríkis og lykils
Name[it]=Archivio certificati e chiavi
Name[ja]=証明書および鍵を格納するストレージ
Name[kk]=Сертификаттар және кілттер қоймасы
Name[km]=វិញ្ញាបនបត្រ និងការ​ផ្ទុកសោ
Name[kn]=ಪ್ರಮಾಣಪತ್ರ ಮತ್ತು ಕೀಲಿಯ ಶೇಖರಣೆ
Name[ko]=인증서 및 키 저장소
Name[lt]=Liudijimų ir raktų saugykla
Name[lv]=Sertifikātu un atslēgu glabātava
Name[mjw]=Certificate pen Key Storage
Name[mk]=Склад на клучеви и сертификати
Name[ml]=സാക്ഷ്യപത്രവും കീ സംഭരണവും
Name[mr]=प्रमाणपत्र व कि स्टोरेज
Name[ms]=Sijil dan Storan Kunci
Name[nb]=Lager for sertifikat/nøkkel
Name[nl]=Certificaat- en sleutelopslag
Name[nn]=Serifikat- og nøkkellager
Name[oc]=Emmagazinatge de 

Bug#955469: initramfs-tools-core: Enable zstandard support

[Sedat Dilek]

Hi,

thanks Norbert for taking care.

I had a similar approach for Debian's userland tools when testing
version 3 of "Add support for ZSTD-compressed kernel and initramfs"
against Linux v5.6.

Norbert's patch seems to include what I have in [1] (includes my
README_zstd-v3.txt).

I am running both ZSTD support on the kernel and userland side using a
ZSTD compressed initramfs image.

As a side-note: zstd-v4 is out for testing see [2] and [3].

Thanks.

Regards,
- Sedat -

[1] LINK: 
https://lore.kernel.org/lkml/ca+iczuxcn2an9andrm+-enesaoygibz0w1xyhwka5k3b3u-...@mail.gmail.com/
[2] Message ID: <20200401053913.216783-1-nickrterr...@gmail.com>
[3] https://github.com/terrelln/linux/commits/zstd-v4