Source: selinux-policy-default
Version: 2:2.20221101-9
Severity: normal
X-Debbugs-Cc: aeru...@aerusso.net
Dear Maintainer,
On a fresh bookworm installation, I have enabled selinux following [1]. I
enabled
enforcing mode, and tried to log in at the console tty (tty1, tty2, and tty6).
journalctl
I can confirm this version of systemd breaks my system's boot as well. I don't
have any
modified journald.conf settings.
I'm running dracut, and the image that is built fails to start
systemd-modules-load.service
Running systemd-modules-load (rd.shell=1 rd.break=cmdline) at the (dracut)
shell
that dpkg-dev version 1.22.5 (or later) allows you to use
Provides: ${t64:Provides}
to automatically generate the versioned Provides: line.
Best,
Antonio Russo
OpenPGP_0xB01C53D5DED4A4EE.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
nd trigger another build attempt.
So, I'm asking for someone to please "give back" the build to the buildds, so
that
we can spin the roulette wheel and hopefully get a buildd with an ipv4 address.
Best,
Antonio Russo
[1] https://tracker.debian.org/pkg/krb5
OpenPGP_0xB01C53D5DED4A4EE.asc
On 2023-12-08 09:01, Sven Joachim wrote:
>
> ,
> | @@ -8550,7 +8556,7 @@ tmux|tmux terminal multiplexer,
> | use=ecma+italics, use=ecma+strikeout, use=xterm+edit,
> | use=xterm+pcfkeys, use=xterm+sl, use=xterm+tmux,
> | use=screen, use=bracketed+paste, use=report+version,
> | -
-256color I get the same bad behavior in aptitude.
If I downgrade all ncurses packages to 6.4+20231016, I don't get this behavior.
Maybe this
bug should instead be assigned to ncurses?
Best,
Antonio Russo
OpenPGP_0xB01C53D5DED4A4EE.asc
Description: OpenPGP public key
OpenPGP_signature.asc
What semantics are you thinking for handling upgrades? This does not appear
to be a new zpool "feature", so we may want to support loading such a pool
on an earlier version of our zfs packaging. How does this sound?
- migrate the property if it exists (but do not remove the old, root
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "kcollectd":
* Package name : kcollectd
Version : 0.12.1-1
Upstream contact : Antonio Russo
* URL : https://www.antonioerusso.com/projects
31E98EED5
> gpgv: Can't check signature: No public key
> uscan die: OpenPGP signature did not verify. at
> /usr/share/perl5/Devscripts/Uscan/Output.pm line 77.
I assume that means it is actually verifying the signature.
Should I add a lintian override to capture this situation?
Bes
e; urgency=medium
.
* Initial release (Closes: #1041718)
Best,
Antonio Russo
OpenPGP_0xB01C53D5DED4A4EE.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
Most notably, upstream
has dropped support for
inkscape <1.3, and I am tracking that change here.
Best,
Antonio Russo
OpenPGP_0xB01C53D5DED4A4EE.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
.
* Initial release (Closes: #1041718)
Best,
Antonio Russo
OpenPGP_0xB01C53D5DED4A4EE.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
ebian/pool/main/k/keepassxc-proxy-client/keepassxc-proxy-client_0.1.6-1.dsc
Changes for the initial release:
keepassxc-proxy-client (0.1.6-1) unstable; urgency=medium
.
* Initial release (Closes: #1041718)
Best,
Antonio Russo
OpenPGP_0xB01C53D5DED4A4EE.asc
Description: OpenPGP
Package: wnpp
Severity: wishlist
Owner: Antonio Russo
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: keepassxc-proxy-client
Version : 0.1.6
Upstream Contact: Henrik Böving
* URL : https://github.com/hargoniX/keepassxc-proxy-client
* License : ISC
control: tag -1 patch
This breaks builds of many things including, e.g., kwin.
I'm attaching couc...@debian.org 's patch, which fixed 5.103.0-3, but
apparently never got into the git repository.
Best,
Antonio Russo
(hello other Antonio!)
--- ../kcmutils/debian/libkf5kcmutils-bin.install 2023-06
Hello,
This is the use case for the zfs-mount-generator(8).
The man page EXAMPLES section has a quick start guide.
Best,
Antonio
OpenPGP_0xB01C53D5DED4A4EE.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
retitle -1 dpkg continues to perform setup after usrmerge directory fails
thanks
This was a WSL1 install of Debian, which is buggy [1] (but I do no want to
be the focus of this bug report). (The /lib directory genuinely cannot
be renamed, or something. Who knows what/how exactly WSL1 butchered
Package: usrmerge
Version: 35
Severity: important
X-Debbugs-Cc: aeru...@aerusso.net
Dear Maintainer,
Under WSL, I installed Debian bullseye (months? a year? ago), and have now
decided to upgrade it to bookworm. My process was:
1. s/bullseye/bookworm/g for /etc/apt/sources.list
2. apt update
3.
some temporary files on ZFS with
Linux 6.1
will not work. (This should not be related to your compiling issue at all,
though).
Best,
Antonio Russo
this at important severity since it is a regression and could conceivable
lead to difficult to debug problems.
Briefly, the interface to tmpfile() interface in the kernel was adjusted to use
a struct file rather than a struct dentry. The adjustment is relatively
straightforward.
Best,
Antonio Russo
[1
On 1/8/23 09:22, Eduard Bloch wrote:
>
> Thanks. Regarding the second patch, I am not sure. Looks like my C++
> also has become rusty in the last months. It would be good to have an
> explicit description of the problem cases, since I don't know exactly
> what you mean with "streaming". I.e. it
the unavailable class.
Matthew Ahrens has fixed this with upstream commit b72efb751 [1].
Best,
Antonio Russo
[1]
https://github.com/openzfs/zfs/commit/b72efb751147ab57afd1588a15910f547cb22600
omain sockets.
Best,
Antonio Russocommit 3c8d91146b9acfa5ab42e4c2496038185b86f95d
Author: Antonio Russo
Date: Mon Dec 26 12:31:48 2022 -0700
Do not override disabled tcp listener
diff --git a/src/acfg.cc b/src/acfg.cc
index a137ac2..2a64348 100644
--- a/src/acfg.cc
+++ b/src/acfg.cc
@@ -
36b2e9fed01d5eb54e23
Author: Antonio Russo
Date: Thu Dec 22 04:41:14 2022 -0700
Streaming support for Sources
Signed-off-by: Antonio Russo
diff --git a/src/cacheman.cc b/src/cacheman.cc
index 940be40..52f3a38 100644
--- a/src/cacheman.cc
+++ b/src/cacheman.cc
@@ -1695,6 +169
I must have somehow managed to run an expiration task while there weren't
package files.
This presumably caused the files to be tagged for deletion. When they became
referenced
again, apt-cacher-ng still wants to delete them.
I'm leaving this bug open as a wishlist because it's trivial to work
Package: apt-cacher-ng
X-Debbugs-Cc: aeru...@aerusso.net
Version: 3.7.4-1~bpo11+1
Severity: normal
Dear Maintainer,
During a manual run of acng expiration scan, I'm finding acng wants to remove
basically all
the cached files. As a specific example, it's parsing
bullseye/main/binary-amd64:
er visible.
Best,
Antonio Russo
I've pushed packaging for 1.8.2 to salsa [1].
I don't presently have a testing/unstable system to test this with,
(and I wasn't able to trivially backport 1.2.1), so I can only
confirm it works on 1.0.2-4 and 1.1.2-3~bpo11+1.
If anyone confirms this works on unstable, I'll push it out.
Otherwise
Control: severity -1 wishlist
Control: retitle -1 Please backport support for 5.13
Hello,
ZFS 2.0.3 doesn't support 5.13. Neither does 2.0.5, (which is a
matter of some friction). You'll have to switch to 2.1 if you
can't wait -- and I haven't gotten around to packaging it yet.
- Antonio
Hello,
Those instructions don't quite work. It did, however, lead me how to figure
it out (thank you).
If you want to do this, you have to:
1. Open ANOTHER tab (try it if you don't believe me, you have to do this)
2. On that tab, a section called "top sites" will appear. Tab to the site
you
Package: firefox-esr
X-Debbugs-Cc: aeru...@aerusso.net
Version: 78.13.0esr-1~deb11u1
Severity: normal
Dear Maintainer,
* What led up to the situation?
Install firefox-esr, remove any old profiles, start the program,
and click in the URL bar. Advertisements for several non-free
online
With the release coming up, I don't think anyone has made getting
new versions of software into Debian a major priority. (So that's
the excuse this time!)
(Post-release) As for 2.1, I'd like to get this into experimental
-- and I'd like to keep unstable/bookworm on 2.0, since my
understanding is
Source: zfs-linux
Version: 2.0.1-1
Severity: grave
Tags: upstream
Justification: causes data loss
X-Debbugs-Cc: aeru...@aerusso.net
See Brian Behlendof's comment at [1], in the merge request for commit
3f81aba76, referencing the analysis of the bug report [2].
In summary: a kernel buffer
Package: chromium
Version: 89.0.4389.82-1
Severity: grave
Tags: upstream security
Justification: user security hole
X-Debbugs-Cc: aeru...@aerusso.net, Debian Security Team
Per [1] (or [2], and allegedly [3] which I cannot access):
> A use after free security issue was found in the Blink
Control: fixed -1 2.0.2-1
Hello,
Unfortunately, it took a while to get 2.0 into backports. This should
now be resolved. That said, if you look at the bug reports for ZFS,
there's a recurring theme---people often upgrade their kernel and find
that ZFS is not compatible. You point out:
> btw:
Control: found -1 0.8.6-1
Control: fixed -1 2.0.2-1
Thank you for reporting this. Are you running stable (0.7.12) and affected by
this?
Backports and bullseye should now have the fix you mention.
Best,
Antonio
OpenPGP_0xB01C53D5DED4A4EE.asc
Description: application/pgp-keys
Control: tag -1 patch
Hello Andreas,
Deleting these old symlinks from (presumably) another ZFS packaging is indeed
the correct fix. I do think we could handle this case slightly more nicely,
and I've opened an MR on salsa [1] that should fix this.
Best,
Antonio
[1]
Hello,
On 2/19/21 1:35 AM, Xavier wrote:
>
> The recently added cron "TRIM the first Sunday of every month" makes some SSD
> drives crash.
>
> The problem appears on reasonnably busy and otherwise stable servers:
>* with about 100 containers,
>* each on a separate zvol, ext4 mounted
Hello,
> Please change the email address on this bug report from
> send_only.aurin...@auroville.org.in to b...@charlesmatkinson.org
See controlling the Debian BTS [1].
> I tried hard to make a source .deb but did not manage to do so.
> Would you like me to share the system I use to create the
control: tag -1 patch
On 2/5/21 3:22 AM, Gianfranco Costamagna wrote:
> control: reopen -1
> control: notfixed -1 3.0.9+dfsg1-1.1
>
> Hello, I reuse this bug, to point out that now the package has an autopkgtest
> failure on armhf, probably due to an incomplete patch or a missing xvfb
>
Hello Wookey,
On 2/3/21 6:44 AM, Wookey wrote:
> On 2021-02-02 23:42 -0700, Antonio Russo wrote:
>
> I've tested the builds on arm64 and armhf. I'm short of non-headless
> boxes here to test the X functionality on.
>
> So I've uploaded to get the migration going and allow
* hardware to test this on, so, while I can
confirm that this builds (and works) on amd64, it would be nice if someone
could check that it works correctly on arm.
Best,
Antonio Russo
[1] https://tracker.debian.org/pkg/xpra
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956822
The patch I submitted builds and runs fine on amd64. It should
also trivially get past the assertion failure in the referenced
buildd log.
I can prepare an NMU---but I'd feel better if someone with an
actual arm* machine could test it.
Also, maybe
-if not
Control: severity -1 grave
Dear Maintainer,
Does this root-level access bug still affect the current
version of snapd in testing?
I do not think it befits Debian to ship a package in this
state---users expect security isolated snaps to not give
trivial root level access to their systems.
I
) there's no need to upstream this change.
Author: Simon Ruderich
Author: Antonio Russo
Bug-Debian: https://bugs.debian.org/863891
Forwarded: not-needed
Last-Update: 2020-12-18
Index: xpra-2.4.3+dfsg1/setup.py
===
--- xpra-2.4.3+dfsg1.orig
.
As for upstreaming the changes: I assume that they had some good reason not to
put it in a file by itself. I do not have any preexisting relationship with
them, so I don't feel like rocking the boat to change things up.
Best,
Antonio Russo
OpenPGP_0xB01C53D5DED4A4EE.asc
Description: application/pgp-keys
.
Per a conversation I've had on debian-devel [3], it appears I should
request a binNMU (as I believe I am, here). Please let me know if I
am doing anything incorrectly (e.g., should I be cc-ing the dovecot*
developers involved?)
Thank you,
Antonio Russo
[1] https://tracker.debian.org/pkg/dovecot
Yes, and this is partly my fault. I've prepared a version of this
patch [1] and forwarding it to upstream [2]. [1] Also includes
some other fixes that should get in, but weren't worth delaying
the upload for. (But this certainly is!)
/sbin is the correct place for this, right?
Antonio
[1]
to cherry-pick that commit?
Thanks,
Antonio Russo
[1] https://github.com/openzfs/zfs/issues/11448
[2]
https://github.com/karelzak/util-linux/commit/372ce5b74e79470b1bda1fc284c19a313a422361
OpenPGP_0xB01C53D5DED4A4EE.asc
Description: application/pgp-keys
OpenPGP_signature
Description: OpenPGP
dozen
machines.
>
> Kind regards,
>
> Laurent Bigonville
Thanks for getting back so quickly,
Antonio Russo
OpenPGP_0xB01C53D5DED4A4EE.asc
Description: application/pgp-keys
OpenPGP_signature
Description: OpenPGP digital signature
Hello,
I am interested in getting dma 0.13 into bullseye. I've been running it
on a fleet of machines after packaging it [1].
Would the dma packaging team be willing to sponsor an upload if I prepared
it?
Best,
Antonio Russo
[1] https://salsa.debian.org/debian/dma/-/merge_requests/2
Control: forcemerge 977656 -1
Hello,
0.8.6 does not support Linux 5.10---hence the failures. Right now, the only
released
version of ZFS that supports Linux 5.10 is 2.0.1, and that is currently
packaged in
experimental. The Debian ZFS team is still deciding between 0.8.x and 2.0.x
for
tag -1 upstream
thanks
Giving an update here, since many people may be interested in a status
report on this:
- There is *no released version* of ZoL/OpenZFS that supports 5.10.
- 5.10 appears to have been slightly more work for OpenZFS to adjust to.
- As of e1d9228b0 (on their 2.0.1-staging
Package: sponsorship-requests
Severity: normal
X-Debbugs-Cc: aeru...@aerusso.net
Dear mentors,
I am looking for a sponsor for my package "kcollectd"
* Package name: kcollectd
Version : 0.12.0-1
Upstream Author : Antonio Russo
* URL
he package builds, and after some customization behaves as I'd
like.
However, I'm not upgrading from a previous version, but I suspect there may be
significant friction for upgrades. I cannot be fully aware of how much trouble
this may cause for existing users.
Best,
Antonio Russo
Control: tag -1 patch
Dear maintainer,
Upstream 0.4.3 resolves this bug for me. It's unclear to me what package is "at
fault",
but I've built and installed ckb-next/0.4.3 (see [1]), and the problem goes
away.
Best,
Antonio Russo
[1] https://salsa.debian.org/debian/ckb-next/-/merg
ou decided not to include the rest
of that MR as a patch even after it is merged.
Best,
Antonio Russo
[1] https://bugs.kde.org/show_bug.cgi?id=430311
[2] https://invent.kde.org/utilities/konsole/-/merge_requests/299
OpenPGP_0xB01C53D5DED4A4EE.asc
Description: application/pgp-keys
OpenPGP_signature
D
Package: src:okular
Severity: wishlist
Tags: patch
X-Debbugs-Cc: aeru...@aerusso.net
Dear Maintainer,
I've taken a stab at updating the packaging for okular [1]. I'd
very much like to get okular 20.12.0 ASAP, since it fixes some
painful regressions for me.
Best,
Antonio Russo
[1] https
or package cleanup (bumped to the
new standards version 4.5.1 and aligning gbp.conf with my salsa layout).
Best,
Antonio Russo
OpenPGP_0xB01C53D5DED4A4EE.asc
Description: application/pgp-keys
OpenPGP_signature
Description: OpenPGP digital signature
exception of the warning about upstream
tarball signing and missing tests. I am still interacting with upstream to
get signed releases [1].
**My last upload is still in the NEW queue.** Should I wait for it to clear
before uploading my next revision?
Best,
Antonio Russo
[1] https://github.com/texte
he package is lintian clean, with the exception of the warning about upstream
tarball signing and missing tests. I am still interacting with upstream to
get signed releases [1].
Best,
Antonio Russo
[1] https://github.com/textext/textext/issues/231
to sharpen the
dependencies and update by email address.
The package is lintian clean, with the exception of the warning about upstream
tarball signing and missing tests. I am still interacting with upstream to
get signed releases [1].
Best,
Antonio Russo
[1] https://github.com/textext/textext/
-cache policy linux-headers-$(uname -r)
for the affected kernel version.
Antonio Russo
OpenPGP_0xB01C53D5DED4A4EE.asc
Description: application/pgp-keys
OpenPGP_signature
Description: OpenPGP digital signature
Hello,
On 10/25/20 4:03 AM, Thomas Lange wrote:
Thanks for the patch. But when I tried to apply it on my local machine
it failed. Can you please check this
[snip]
Hmm... it looks like 050+65-1 isn't on salsa, only 050+35-4 (and that's
what the patch is based on).
If you push 050+65-1 to
Package: dracut-core
Version: 050+65-1
Severity: normal
Tags: patch
X-Debbugs-Cc: aeru...@aerusso.net
By default, dracut --force acts on /boot/initramfs-$(uname -r).img, instead of
the debian default initramfs file,
/boot/initrd.img-$(uname -r).
The patch in salsa [1] addresses this.
Best,
Control: tag -1 patch
I have opened an MR on salsa [1] that addresses this by relaxing the version
constraints. I'd appreciate feedback if this is an appropriate way to solve
the problem.
Antonio
[1] https://salsa.debian.org/zfsonlinux-team/zfs/-/merge_requests/28
Hello Jordan,
Do you have the architecture-specific Linux headers installed?
I.e., please call
# uname -r
that should give you something like 5.8.0-2-amd64
Is the package linux-headers-5.8.0-2-amd64 installed (replaced for your
specific kernel version)?
Or, just run
# apt-cache policy
Control: tag -1 patch
I've gone ahead and taken a shot at the packaging [1]. I'm running
it locally on several machines (the new FINGERPRINT option is great).
If there's any more legwork to run on this, let me know. I'd love to
help out.
Antonio
[1]
Control: tag -1 patch
I've created an MR on salsa that should address this
https://salsa.debian.org/ahs3/rasdaemon/-/merge_requests/2
Best,
Antonio
Ugh, sorry. This is of course correct.
On 2020-07-30 17:50, Richard Laager wrote:
> On 7/30/20 1:58 PM, Antonio Russo wrote:
>> Changing this line to
>>
>> pools=$(zpool list -H -o name | true)
>
> This should be || true (two pipes, not one).
>
Package: zfsutils-linux
Version: 0.8.4-2
Severity: important
X-Debbugs-CC: rlaa...@wiktel.com
Tags: patch
The addition of the command
pools=$(zpool list -H -o name)
to /lib/systemd/system-generators/zfs-mount-generator means that zpool must
succeed at very early in the boot. This may not be the
Hello,
Could you confirm that you have linux-headers-5.6.0-0.bpo.2-amd64 installed,
and its exact version?
Additionally, to debug this we will need to
> Consult /var/lib/dkms/spl/0.7.12/build/make.log for more information.
Could you please attach that (and any other suspicious files in that
pt-library warning appears to be an issue with
dh_sphinxdoc (see [1], the last email dated Jul 13 from Alexis Murzeau).
I have not set up autopkgtests.
The packaging is maintained in Debian salsa [2], and builds in pbuilder.
Best,
Antonio Russo
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug
#964593 in the changelog, but should otherwise be
identical.
The mentors page often has trouble identifying a new version, but does appear
to be
showing up correctly now. Please be wary of this when downloading the package.
Best,
Antonio Russo
[1] https://salsa.debian.org/debian/pkg-collectd
Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: pkg-kde-t...@alioth-lists.debian.net
Dear mentors,
I am looking for a sponsor for my package "kcollectd":
* Package name: kcollectd
Version : 0.11.99.0-1
Upstream Author : Antonio Russo (myse
Hello again,
Is there anything I can do to help move this process along?
Are you still willing to sponsor an upload for this package?
Thank you,
Antonio Russo
Control: severity -1 wishlist
Control: tag -1 -moreinfo
On 2020-07-03 09:49, Wxcafé wrote:
> My problem is that canmount=noauto datasets should not be mounted
> automatically (I mean it’s in the name, isn’t it?) and right now they are
> being mounted automatically (through systemd)
systemd
Can you confirm that
zfs set org.openzfs.systemd:ignore=on rpool/backups
resolves your issue? Right now, you've got backup datasets that are
canmount=noauto, but presumably
should never be mounted at those mountpoints. Other options are
- change your mountpoint on your backup root, and have
Control: severity -1 wishlist
Control: tag -1 upstream
I haven't heard anything back about this, so I'm going to treat the bugreport
as exact fact.
> kcollectd starts, shows the inputs tree correctly but clicking any
> source shows only: "Drop sensors from list here" and the rest of the
> main
Control: tags -1 +moreinfo
Hello!
Is that attached file literally what is in /etc/zfs/zfs-list.cache ? How was
it generated, and how did it get there?
Because it's wrong---it's space separated, and must be tab separated. Use -H,
per man zfs-mount-generator, if it must be done by hand.
Just wanted to do a quick follow up:
Is there anything else you would like me to do to prepare this package
for submission?
Thanks,
Antonio
On 2020-06-10 18:30, Antonio Russo wrote:
> On 2020-06-10 08:53, Boyuan Yang wrote:
>> Signed tags/tarballs don't matter; they are totally optio
Control: tags -1 +moreinfo
Hello Eduard,
You say that the tree of sensors appears for you. Just to confirm: what
happens when you drag an item from
that list into the right-hand region, where it says "Drop sensors from list
here"?
Antonio
On 2020-06-10 08:53, Boyuan Yang wrote:
> Signed tags/tarballs don't matter; they are totally optional. Your
> debian/watch file is using mode=git, which is totally fine; however,
> you may also opt to monitor the github releases page like other Debian
> packages.
Understood. I've left it
regarding signed git tags [4].
Thank you very much for looking at this,
Antonio Russo
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961741
[2] https://mentors.debian.net/package/inkscape-textext
[3] https://salsa.debian.org/aerusso-guest/textext
[4] https://github.com/textext/textext/issues
ons I have found.
The package is lintian clean, with the exception of the warning about
upstream tarball signing (and tests) [1]. I'm currently interacting with
upstream to get signed releases [2].
The packaging is maintained in Debian salsa [3], and builds in pbuilder.
Best,
Antonio Russo
ning about
upstream tarball signing (and tests) [1]. I'm currently interacting with
upstream to get signed releases [2].
The packaging is maintained in Debian salsa [3], and builds in pbuilder.
Best,
Antonio Russo
[1] https://mentors.debian.net/package/inkscape-textext
[2] https://github.com/texte
eam to get signed releases [2].
The packaging is maintained in Debian salsa [3], and builds in pbuilder.
Best,
Antonio Russo
[1] https://mentors.debian.net/package/inkscape-textext
[2] https://github.com/textext/textext/issues/231
[3] https://salsa.debian.org/aerusso-guest/textext
Hello! I'm glad someone is finding use for this. I updated the
packaging in [1]. Notice the change in package name to
inkscape-textext, which more closely matches other inkscape extension
packages.
It "works" in the sense that it compiles, installs, and creates
basic objects in inkscape, but I
Source: zfs-linux
Severity: wishlist
Tags: patch
--- Please enter the report below this line. ---
Upstream has release 0.8.4 [1]. It adds official support for 5.5 and 5.6---a
dire need for Debian unstable
and testing users, since 5.4 is no longer supported.
Some packaging changes are required
Control: tag -1 patch
I've opened a merge request [1] addressing this.
[1] https://salsa.debian.org/debian/dracut/-/merge_requests/1
Package: dracut
Version: 050+35-2
Severity: serious
This newest version of dracut is not loading Intel microcode updates, and
reverting to 048+80-2 resolves the issue.
lsinitrd in 048 shows an early cpio archive with the microcode. that cpio is
missing in 050, so maybe that is related?
I've
Control: notfound -1 1.23.90-1
This was caused by the router's DHCP6 server (but not the dhcp4 server)
misbehaving.
While network manager could have more robustly handled the failure, it's at
most a wishlist
bug, and I've described mitigations in the upstream bugreport. There's no
reason to
The router firmware mentioned above is a red herring. A macbook on the same
network
is perfectly able to maintain ipv6 connectivity. Conversely, both wired and
wireless
connections are exhibiting this misbehavior on 3 separate Debian
testing/unstable
machines.
Antonio
Package: network-manager
Version: 1.23.90-1
Severity: important
Tags: ipv6
Symptom:
inet6 leases are acquired without (apparent) issue at connection start time,
but expire
without any attempt to renew (no log entry in journalctl containing "dhcp6").
inet4
addresses are properly acquired and
On 3/6/20 4:50 PM, Bernd Zeimetz wrote:
>
> I fail to understand the reason behind this: libiptc-dev still exists
> and collectd needs it to build successfully. Please convince me why
> there is a reason for this change.
>
My apologies: I for some reason thought I saw "pkg-config --exists
Sorry for the noise here. I understand that these are two separate issues, and
I believe
that upstream has addressed the libiptc -> libip4tc name change in their 5.10.0
release.
My MR has been updated to only pull in libip4tc-dev and libip6tc-dev, and not
libiptc-dev
in a third patch, so there
merged 946152 and 951088?) Or is the removal of the dependency on libiptc0 (by
rebuilding) sufficient to
address your original bug report?
Thanks,
Antonio Russo
[1] https://salsa.debian.org/debian/pkg-collectd/-/merge_requests/2
Control: forcemerge -1 946152
Control: tag -1 patch
Please see my MR on salsa [1]. With that patch, collectd builds locally
without the obsolete build-dep.
Antonio
[1] https://salsa.debian.org/debian/pkg-collectd/-/merge_requests/2
Package: zfs-zed
Version: 0.8.3-1
Severity: serious
Tags: patch
Justification: Policy 10.7.3
Please see my MR on salsa [1], which should address this policy violation. In
short: the symlinks shipped
by zfs-zed in /etc/zfs/zed.d are not tracked as conffiles by dpkg, so they
re-appear even after
please include your
NetworkManager.conf file? (Make sure there are no secrets in it!)
Best,
Antonio Russo
[1] https://www.debian.org/Bugs/server-control#found
1 - 100 of 263 matches
Mail list logo
