On Sat, 26 Apr 2025 at 21:54, Arnout Vandecappelle wrote:
> On 12/04/2025 10:07, Russell Coker wrote:
> > Here are the results of running valgrind with a debugging build of every
> > relevant package installed:
> >
> > ==241689== Invalid read of size 8
> > ==241689==at 0x53A92E: UnknownInlined
sion of python3-alchemy currently in sid and
> testing is 2.0.40+ds1-1.
>From the last Debian changelog entry:
,
| gourmand (1.1.0+really1.1.0-1) unstable; urgency=medium
|
| * New upstream release.
| * Still not ready for testing.
|
| -- Christian Marillat Sun, 30 Mar 2025 03:38:29 +0200
`
Christian
Source: keyutils
Version: 1.6.3-5
Severity: serious
The patches for fixing a FBTFS in containerized environments uncovered
another latent bug, or possibly two separate bugs.
First, some tests involving an overlong description assume a page size
of 4K, which is not the case on at least some pcc64e
mporarily disable the tests on mips64el and powerpc to allow
libcap2 to migrate.
Best,
Christian
On 24 mars 2025 16:32, Jochen Sprickerhof wrote:
> Version: 1.9+b2
>
> Hi Christian,
>
> this should be fixed with the binNMU 1.9+b2 in unstable now.
Yes. Thanks.
Christian
oices are installable:
| [no choices]
`----
Christian
-- System Information:
Debian Release: trixie/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.13
Control: forwarded -1 https://bugzilla.kernel.org/show_bug.cgi?id=219880
This is a draft, as one of the tests enters a busy-loop when run within
a container or with unshare. It works fine on mips64el bare metal.
t you might be able to pass this on upstream.
Best,
Christian
[1]:
https://web.git.kernel.org/pub/scm/libs/libcap/libcap.git/tree/libcap/execable.c
Control: forwarded -1 https://bugzilla.kernel.org/show_bug.cgi?id=219880
I confirm the version 1.1.4 is fixing this bug
for both doxysphinx and sphinx-external-toc
Please upload to trixie/unstable
Cheers
Christian
Implement attribute
verification" as the reason for the endless loop.
https://savannah.gnu.org/bugs/index.php?66855
and this seems to be the patch that fixes it.
https://lists.gnu.org/archive/html/grub-devel/2025-02/msg00179.html
(I'll test this and report back)
Regards,
Christian
attr_cur after calling next_attribute()"
fixes the issue in my setup.
I can also confirm that reverting just the one patch:
fs-ntfs-Implement-attribute-verification.patch
also helped (as in grub booted again).
Best Regards,
Christian
Control: clone -1 -2
Control: severity -2 normal
On 2025-02-17 10:53, Christian Kastner wrote:
> thank you both for the report and the analysis so far. I managed to
> reproduce this on a porter box.
>
> Sadly, I haven't found the underlying issue yet, nor do I know why this
>
block 1080542 by 1100382
thanks
Thanks for the report, the issue is addressed in a 0.1.11-2 that is
uploaded to mentors at https://mentors.debian.net/package/arandr/ / RFS
in https://bugs.debian.org/1100382.
BR
chrysn
signature.asc
Description: PGP signature
/dl10n-check line 22.
Regards,
Christian Buhtz
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: arm64 (aarch64)
Kernel: Linux 6.12.12-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=de_DE.UTF-8, LC_CT
r" case (but not for performance checks).
The initial timeouts were based on "works for me/on my laptop", and
we've since increased the timeout for several tests in test-logprof.py
so that it has enough time to finish on all architectures.
So if another test needs an increas
the error reporting to make this error condition
> more clear and how to fix it. And I'm thinking about adding a NEWS
> entry, because I guess the implications of the changes are not obvious
> at all.
Probably a good idea.
Christian
al-py3_3.9.14-3_source.changes
`
Christian
-- System Information:
Debian Release: trixie/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.13.5-1-custom
roblem come from python3-bs4 4.13
https://github.com/hhursev/recipe-scrapers/issues/1497
Christian
Control: reopen -1
Apologies, I had a typo in my bug number.
Best,
Christian
date might help down the road.
Best,
Christian
On 2024-12-10 12:38, Chris Hofstaedtler wrote:
> Control: retitle -1 libcap2: FTBFS due to test suite failure on mips64el,
> powerpc
>
>> I observed the failure for this package to buildd with powerpc architecture.
>
> Wh
;, which
is also in package python3-tz (2024.2-1)
| Preparing to unpack .../python3-tz_2025.1-2_all.deb ...
| Unpacking python3-tz (2025.1-2) over (2024.2-1) ...
| Errors were encountered while processing:
| /var/cache/apt/archives/python3-pytz_2025.1-2_all.deb
`
Christian
-- System Information
in the list, got excited. Very
> exciting
> to see displaycal coming back to life. Ran apt dist-upgrade. Ran displaycal.
Fixed in displaycal 3.9.14-2
Christian
On 18 nov. 2024 10:11, Niels Thykier wrote:
> Control: tags -1 moreinfo
>
[...]
> Hi Christian
Hi Niels,
> The error from apt-file is correct in the sense that there are no
> `Contents` files in your apt-cache (it is possibly misleading in other
> ways).
I've found th
Package: apt
Version: 2.9.11
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I'm trying to package
root 439 15 nov. 04:07
incoming.debian.org_debian-buildd_dists_buildd-unstable_non-free-firmware_i18n_Translation-en
| -rw-r- 1 root root0 28 févr. 2020 lock
| drwx-- 2 _apt root20480 16 nov. 09:22 partial
`
Christian
-- System Information:
Debian Release: trix
t;>...
>
> That didn't work:
> https://buildd.debian.org/status/package.php?p=mbedtls&suite=sid
I'm sorry but I didn't test the proposed patch.
Christian
Package: tvnamer
Version: 3.0.4-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
When using tvnamer to rename files, I get an error:
$ python3 -m tvnamer.main --dry-run ~/Videos/download/file.mp4
Traceback (most recent call last):
File "", line 198, in _run_module_as_
.1.0-3_i386.deb
`
Christian
-- System Information:
Debian Release: trixie/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.11.0-1-custom (SMP w/24 CPU t
fully updating them, but I'd nevertheless feel
more comfortable spending a bit more time on this, to ensure this is
either gcc-14- and/or patch-related.
Best,
Christian
On 2024-08-26 19:10, Graham Inggs wrote:
> Control: tags -1 + patch
>
> This is already fixed upstream:
> h
Package: mdadm
Version: 4.3+20240723-2
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: c.h...@web.de
Dear Maintainer,
after upgrading to kernel 6.10.6 boot fails on mdadm not finding devices as
none are configured. Going back to 6.10.3 fixes the problem. mdadm package is
on
Hello,
> starting the program leads to an unrecoverable error, a backtrace is
> printed on the console and the error is:
>
> "ModuleNotFoundError: No module named 'blinker._saferef'"
I can confirm this problem.
--
Regards/Mit freundlichen Grüßen
Christian W
/f4dc2f2cfdb40e04022e4deb4aa67578deff5d23
(since v9.0.0)
Someone reported the problem to upstream and they told to use the
binaries they provide:
https://github.com/mitmproxy/mitmproxy/issues/6828
--
Regards/Mit freundlichen Grüßen
Christian Weiske
-=≡ Geeking around in the name of science since 1982 ≡=-
|
| * Non-maintainer upload.
| * Rename libraries for 64-bit time_t transition. Closes: #1061995
|
| -- Michael Hudson-Doyle Tue, 27 Feb 2024 23:25:09
+
`
Christian
-- System Information:
Debian Release: trixie/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-uns
.7_0.7.1-3+b1_amd64.deb
| E: Sub-process /usr/bin/dpkg returned an error code (1)
`
Christian
-- System Information:
Debian Release: trixie/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectu
On 09 juil. 2024 15:25, Michael Tokarev wrote:
> 09.07.2024 15:23, Christian Marillat wrote:
>> On 09 juil. 2024 13:18, Michael Tokarev wrote:
>> [...]
>>
>>>>> I don't know what "NIC support is missing" means. Qemu can't be built
&
emu-system-ppc64 -help display -nic and -net. Al
so the same from the online documentation.
https://www.qemu.org/docs/master/system/invocation.html#hxtool-5
Christian
el=help
| Available NIC models:
| e1000
| e1000-82544gc
| e1000-82545em
| e1000e
| i82550
| i82551
| i82557a
| i82557b
| i82557c
| i82558a
| i82558b
| i82559a
| i82559b
| i82559c
| i82559er
| i82562
| i82801
| igb
| ne2k_pci
| pcnet
| rtl8139
| sungem
| tulip
| virtio-net-pci
| virtio-net-pci-non-transitional
| virtio-net-pci-transitional
| vmxnet3
`
Christian
On 09 juil. 2024 12:53, Michael Tokarev wrote:
> Control: tag -1 + moreinfo unreproducible
>
> 09.07.2024 12:09, Christian Marillat wrote:
>> Package: qemu-system-ppc
>> Version: 1:9.0.1+ds-1
>> Severity: serious
>> Dear Maintainer,
>> My work
chine?)
`----
Christian
-- System Information:
Debian Release: trixie/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.9.8-1-custom (SMP w/24 CPU threads; PR
On 2024-06-16 15:10, Lucas Nussbaum wrote:
> Source: python-xmlschema
> Version: 3.3.1-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240615 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to
re `traitlets.warn` is called
```
warn(f"{klass} is not importable. Is it installed?", ImportWarning)
```
The call fails to provide the required keyword argument `stacklevel` as seen in
line 9 of
```
/usr/lib/python3/dist-packages/traitlets/utils/warnings.py
```
A solution could be
):
trying to overwrite '/usr/lib/arm-linux-gnueabihf/libpmix.so.2', which is also
in package libpmix2t64:armhf 5.0.1-4.1
Christian
-- System Information:
Debian Release: trixie/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable'
Control: tag -1 pending
Hello,
Bug #1067501 in hipsolver reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/rocm-team/hipsolver/-/commit/d51961aa5fc702bd5cf28c9524
doing all this renaming!)
I did not know.
> So I think this is not a bug, and certainly not a RC bug. The warnings are
> a bit annoying, but do not indicate a genuine problem.
Yes of course, you can close this bug.
Christian
Package: dpkg-dev
Version: 1.22.6
Severity: serious
Dear Maintainer,
Feel free to reassign.
I noticed this bug with the libopenshot-audio source and with
armel, armh and powerpc architectures from buildd logs and my rebuild.
I didn't pay attention for others sources, but I noticed that only
aft
unstable...
Christian
| ii libcom-err2:amd64 1.47.0-2.4
amd64common error description library
| ii libcom-err2:i386 1.47.0-2.4
i386 common error description library
`
Christian
2
| 0 upgraded, 2 newly installed, 1 to remove and 0 not upgraded.
`----
Christian
-- System Information:
Debian Release: trixie/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i3
Package: vlc-plugin-pipewire
Version: 3-3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: dvl...@gmail.com
vlc-plugin-pipewire depends on vlc-plugin-abi-3-0-0f. However, after the time_t
transition, the libvlccore9 package provides vlc-plugin-abi-3-0-0ft64.
Due to this, the p
Control: tag -1 pending
Hello,
Bug #1065353 in rocsparse reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/rocm-team/rocsparse/-/commit/328d612af51ece88548bbdd131
Control: tag -1 pending
Hello,
Bug #1065351 in rocblas reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/rocm-team/rocblas/-/commit/10bafdf7949eba57ae124741cba15e
self, but I'm
only 90% confident that I'm not missing something, so wanted to check
first.
If it's indeed missing from bin:hipcc, I guess it should be updated to
libamdhip64-dev (= ${binary:Version})
Discovered when building the newer rocFFT, which only build-depends on
hipcc.
B
ible useful to know.
Funny how I never realized that this was a thing.
Best,
Christian
ack.
This affects a key package of our stack, so it's not just about testing
this particular package, but the entire stack, and everything else in
the archive that depends on it.
A fix is in progress.
Best,
Christian
On 2024-01-20 21:59, Sylvestre Ledru wrote:
> Source: rocm-hipamd
>
27;m preparing an upload with this new fix.
Thanks.
Christian
available in Debian and packages
fail to build (ffmpeg).
Christian
-- System Information:
Debian Release: trixie/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.7.
On 02 févr. 2024 18:37, gregor herrmann wrote:
> On Tue, 30 Jan 2024 18:18:59 +0100, Christian Marillat wrote:
>
>> > @@ -96,9 +96,12 @@
>> > if ( $Net::HTTPS::SSL_SOCKET_CLASS->can('start_SSL')) {
>> > *_upgrade_sock = sub {
>> >
IP address.
> +# Details:
> https://github.com/libwww-perl/libwww-perl/issues/449#issuecomment-1896175509
I had the idea to read this github issue.
In my case I've a proxy and IPv6 isn't configured so this explain this
Debian bug and reverting upstream changes in 6.12 is maybe a bad idea.
Christian
On 29 janv. 2024 20:58, gregor herrmann wrote:
> On Mon, 29 Jan 2024 08:53:45 +0100, Christian Marillat wrote:
[...]
>> This diff fix this issue.
>
> Thanks for checking.
> Alright, so we know that
> 1) something is different between your and my environment, and
>
On 28 janv. 2024 19:03, gregor herrmann wrote:
> On Sun, 28 Jan 2024 18:44:02 +0100, Christian Marillat wrote:
>
>> > Does it work for you if you downgrade liblwp-protocol-https-perl to 6.11-1
>> > from testing? If yes, which of the two hunks from [0] is causing the
>
e errors from qa.debian.org go away if you run uscan as
> "PERL_LWP_SSL_VERIFY_HOSTNAME=1 uscan …"?
Still the same. I also this bug with gitlab.
Christian
:
hostname verification failed
`
Christian
-- System Information:
Debian Release: trixie/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.7.2-1-custom (
ykman : Depends: python3-cryptography (< 39) but 41.0.7-1 is to be
installed
| E: Unable to correct problems, you have held broken packages.
`
Christian
-- System Information:
Debian Release: trixie/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'
Thanks to Athos proposed fix that was easy to fix.
In the meantime it also has been upstream accepted and I ran a test build
with and without nocheck which both worked fine.
I updated git and I'm uploading debian/1.2.0-6
_1.12.1-dmo5.debian.tar.xz
| dpkg-source: info: using patch list from debian/patches/series
| dpkg-source: info: applying 01_debian-cutomization.patch
`
Christian
signature for
/srv/dak/ftp/pool/main/g/gerbera-dmo/gerbera-dmo_1.12.1-dmo5.dsc: no acceptable
signature found
| dpkg-source: info: extracting gerbera-dmo in gerbera-dmo-1.12.1
| dpkg-source: info: unpacking gerbera-dmo_1.12.1.orig.tar.gz
| dpkg-source: info: unpacking gerbera-dmo_1.12.1-dmo5.debian.tar.xz
| dpkg-source: info: using patch list from debian/patches/series
| dpkg-source: info: applying 01_debian-cutomization.patch
`
Christian
: no acceptable signature found
|
| dupload: error: Pre-upload '/usr/share/dupload/openpgp-check %1' failed for
../gerbera-dmo_1.12.1-dmo5_amd64.changes
`
Christian
-- System Information:
Debian Release: trixie/sid
APT prefers buildd-unstable
APT policy: (500, 'buil
and started with a torrent file.
The problem come libtorrent-rasterbar2.0 and the rebuild with boost 1.83
Downgrading libtorrent-rasterbar2.0 from 2.0.9-2+b1 to 2.0.9-2 fix this
issue.
Christian
Package: python3-apt
Version: 2.7.2
Severity: serious
Dear Maintainer,
This morning I see :
,
| dak@christian ~ % dak dominate
| Traceback (most recent call last):
| File "/usr/bin/dak", line 43, in
| import daklib.utils
| File "/usr/lib/python3/dist-packages/daklib/
error report didn't reach my mailbox:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050588
Could you possibly complete this as I'm (obviously) unfamiliar with the
Debian release process & policies.
Thanks,
Christian
smartmontools.org
relevant patch:
https://sources.debian.org/src/cron/3.0pl1-162/debian/patches/fixes/Check-privilege-drop-results-CVE-2006-2607.patch/
Are you perhaps looking at the unpatched source?
Best,
Christian
Version: 5.5.1-1
Closing this bug, as it is invalid. rocrand never failed, according to
the CI logs (even the linked one).
Control: severity -1 important
I'm downgrading this bug, as the suite successfully completed on another
Navi24 device [1]. No longer RC, this should allow migration to testing
again.
Best,
Christian
[1] https://lists.debian.org/debian-ai/2023/10/msg00044.html
correct so the file isn't corrupted
It is possible to see the complete awstats log ?
Are you sure that awstats is correctly configured ?
Christian
:
md5sum /usr/lib/cgi-bin/awstats.pl
Christian
f :
sha256sum /usr/lib/cgi-bin/awstats.pl
Christian
Control: tag -1 pending
Hello,
Bug #1052954 in rccl reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/rocm-team/rccl/-/commit/b936acd42edaa2c278c693477add9c7d2560
Control: tag -1 pending
Hello,
Bug #1052968 in hipcub reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/rocm-team/hipcub/-/commit/97247d25e7b4574622959e4d55a52b96
0.4+dfsg-3
is to be installed
E: Unable to correct problems, you have held broken packages.
Christian
-- System Information:
Debian Release: trixie/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable')
Arc
On 01 sept. 2023 13:55, Lourisvaldo Figueredo Junior
wrote:
> Hi Christian,
Hi,
> I saw now that you adopted the awstats package and that you closed this bug
> (1037213).
> But I believe the bug is not resolved yet. It happens on bookworm. I have two
> bugs open right now
d bookworm [2], as you said.
> If you agree, I can make an NMU and send it to you to upload, once the
> changes
> are approved.
Yes, please do it.
Christian
Source: rocfft
Version: 5.5.0-4
Severity: grave
Justification: Can crash the host
autopkgtests for rocfft triggered a soft lockup when run with an 6500 XT
(gfx1034, Navi24).
This is very probably a kernel issue, but I'm filing this bug here until
we have actually identified the root cause, after
o even if you have a
profile with abi/3.0, unix rules won't be enforced.
There's an exception: Ubuntu kernels carry some patches to enable unix
and some other rules even with older AppArmor versions.
Regards,
Christian Boltz
--
in my experience it's safe to assume developers never test
[Stephan Kulow in opensuse-factory]
signature.asc
Description: This is a digitally signed message part.
On 01 sept. 2023 13:55, Lourisvaldo Figueredo Junior
wrote:
> Hi Christian,
>
> I saw now that you adopted the awstats package and that you closed this bug
> (1037213).
> But I believe the bug is not resolved yet. It happens on bookworm. I have two
> bugs open right n
On 01 sept. 2023 13:55, Lourisvaldo Figueredo Junior
wrote:
> Hi Christian,
Hi,
> I saw now that you adopted the awstats package and that you closed this bug
> (1037213).
> But I believe the bug is not resolved yet. It happens on bookworm. I have two
> bugs open right now
Source: rocrand
Version: 5.5.1-1
Severity: serious
The tests from ci.rocm.debian.net failed on gfx1030 [1]. I'm filing this
RC bug to prevent migration to testing.
[1]
https://ci.rocm.debian.net/data/autopkgtest/unstable/amd64+gfx1030/r/rocrand/83/log.gz
A manual download of nsis{-common}-3.09-1 from debian testing and 'dpgk
--install --force-all' succeeded and makensis works then. With this
version, the problem does not occur.
A backport of this version to bookworm should fix the problem.
Severity of this bug promoted to 'grave' because further tests show that
generated installers may not work at all:
Testcase:
$ cat /etc/debian_version
12.1
$ makensis -VERSION
v3.08-3
$ cat test.nsi
RequestExecutionLevel user
Section "Test"
MessageBox MB_OK "Hello, World!"
SectionEnd
$ mak
Control: tag -1 pending
Hello,
Bug #1045688 in rocm-device-libs reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/rocm-team/rocm-device-libs/-/commit/a5eaa2718377
ffers-dev_2.0.8+dfsg1-5_amd64.deb
(--unpack) :
| tentative de remplacement de «
/usr/lib/x86_64-linux-gnu/pkgconfig/flatbuffers.pc », qui appartient aussi au
paquet libflatbuffers2:amd64 2.0.8+dfsg1-4
`----
Christian
-- System Information:
Debian Release: trixie/sid
APT prefers buildd-unstable
cause of dysfunct mkinitramfs
initramfs-tools .
i suspect dysfunct zstd 1.54 andor 0.142 initramfstools are the issue
n o t 1.48 +0.140 bullseye
greetings
Original Message
From: CHRISTIAN PETER KISS
Sent: Wednesday, 2 August 2023 14:49
To: car...@deian.org
Subject: Salvatore
systems are functional and longterm stable before these modifications.
Bookworm 0.142 and 1.54 are problem packages,
Bullseye -rt-22- and -rt-23- kernels are dysfunct now, while non-rt kernel -20-
work yet.
Thank you for your hard work, i hope this helps fix the issue.
All the best
Christian KISS
dysfunct now, while non-rt kernel -20-
work yet.
Thank you for your hard work, i hope this helps fix the issue.
All the best
Christian KISS
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do
Package: src:linux
Version: 6.4.4-1
Severity: serious
Dear Maintainer,
Kernel 6.4.4 is affected by a regression causing one core be report
high IO wait utilization.
See https://lore.kernel.org/lkml/12251678.o9o76zd...@natalenko.name/
just be
/etc/apparmor.d/abstractions/squid-deb-proxy
(assuming no other files get deployed to
/etc/apparmor.d/abstractions/squid-deb-proxy/ )
Bonus points if you add
include if exists
to the abstraction ;-)
For the records: include if exists needs AppArmor >= 3.0 userspace.
Re
On 07 juil. 2023 11:29, Helmut Grohne wrote:
> On Fri, Jul 07, 2023 at 11:10:51AM +0200, Christian Marillat wrote:
>> From Debian policy 7.2 :
>>
>> ,
>> | "Recommends"
>> |This declares a strong, but not absolute, dependency.
>> |
&g
On 07 juil. 2023 10:10, Helmut Grohne wrote:
> Hi,
>
> On Fri, Jul 07, 2023 at 09:46:39AM +0200, Christian Marillat wrote:
>> Severity: serious
>
> I believe that this is the wrong severity for this bug and it should be
> downgraded. As I am not otherwise involved with
for all plugins is really small 384K
The library itself is 648K
Please remove these plugins packages and restore as it was before in 1.15.1-1
Christian
-- System Information:
Debian Release: trixie/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500,
ill
transparent and flickery.
Maybe a Qt issue?
--
Christian Beier
what is, is; what is not is possible.
1 - 100 of 1041 matches
Mail list logo
