Hi,
On Mon, 7 Mar 2022, at 10:17, intrigeri wrote:
> But regarding maintenance of src:apparmor itself, the bus factor of in Debian
> is
> 1, which is not great. I don't feel comfortable with this situation.
>
> src:apparmor includes:
>
> - system initialization bits
>
> - AppArmor parser,
condominio
Package: qa.debian.org
Severity: normal
Hi,
some parts of the pages generated by the (old) PTS no longer get
updated:
E.g. https://packages.qa.debian.org/s/spirv-llvm-translator-12.html
(a relatively new package)
* 'versions' box: only lists the version in unstable, not the one in
testing
*
Hello,
This should have been fixed upstream with the following patch:
https://github.com/cisco/libsrtp/commit/4f1d945fe3eb302fa2bab2aea63fdf6ea7485e95
Do you think you could do an upload with that includes it?
Thanks
Laurent Bigonville
Package: qa.debian.org
Severity: normal
Hi,
DDPO currently uses the "No Entry" sign with read background ⛔ (U+26D4)
for the "neutral" CI state. I find this more eye-catching than the "fail"
state (which uses the word "fail" in red).
The CI pages itself use the "No Entry" sign with a blue
Package: wnpp
Severity: normal
X-Debbugs-Cc: debian-de...@lists.debian.org,
pkg-apparmor-t...@alioth-lists.debian.net
Control: affects -1 src:apparmor
Hi,
I request assistance with maintaining the apparmor package.
AppArmor has been enabled by default on the Linux ports of Debian
since Buster.
Package: pmacct
X-Debbugs-Cc: deb...@seufer.de
Version: 1.7.6-2
Severity: important
Dear Maintainer,
The pmacct version (1.7.6) segfaults in Debian Bullseye, when you use the
'flows' feature.
I already reported this problem upstream:
https://github.com/pmacct/pmacct/issues/586
And Paolo
AFAIK there are two possible reasons for this behaviour:
1) In Preferences->Download the option 'Pre-allocate disk space for all
files' is checked (but that's not the default).
2) The option above is not checked but the download folder is within a
filesystem that doesn't support sparse files (at
There are several reports in upstream bug tracker ( [1], [2] ) that show
the same stacktrace.
They both point to a bug in libtorrent-rasterbar 1.1.0 in ip-filtering
code, fixed in 1.1.1. so chances are this bug is solved now.
Regards
BZ
[1] https://github.com/qbittorrent/qBittorrent/issues/5730
Source: sdl12-compat
Version: 1.2.52-3
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: environment
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi Simon,
Whilst working on the Reproducible Builds effort [0] we noticed that
sdl12-compat could
101 - 110 of 110 matches
Mail list logo
