Package Base Details: util-linux-aes

Git Clone URL: (read-only, click to copy)
Submitter: None
Maintainer: TrialnError
Last Packager: TrialnError
Votes: 6
Popularity: 0.000002
First Submitted: 2011-03-02 21:16 (UTC)
Last Updated: 2023-03-12 13:56 (UTC)

Pinned Comments

TrialnError commented on 2020-06-12 15:49 (UTC)

This package should only be flagged out of date if there is a release of loop-aes which offers a new diff.

Latest Comments

1 2 3 4 5 Next › Last »

vaygr commented on 2022-10-15 19:43 (UTC)

I wonder if we could make asciidoctor optional since it's required only for manual pages. On my system it requires a zoo of ruby dependencies which I'd like to avoid.

TrialnError commented on 2022-07-01 17:23 (UTC)

Hello vaygr.
Fair point you're mentioning. Didn't thought of those lines in loop-aes.
So let's remove it from this and maybe change loop-aes such that the modules handling is moved to a separate file and more visible as such.
Thanks for the heads up

vaygr commented on 2022-06-20 00:03 (UTC)

TrialInError am I missing something or "util-linux-aes.modules" file should be dropped from here?

I think both loop-aes and loop-aes-dkms set up module loading properly and this one just duplicates what's already there + leaves some old cruft that's not relevant anymore:

systemd-modules-load[262]: Failed to find module 'aes-i586'

TrialnError commented on 2021-06-21 16:13 (UTC)

Not the first to mention this :D
Yes, I indeed overlooked this detail. I was under the impression the loop-aes files come with a sig. Well, apparantly not..

vaygr commented on 2021-06-21 15:17 (UTC)

TrialInError seems Jari's key needs to be added to validpgpkeys for successful build.

Which is '12D64C3ADCDA0AA427BDACDFF0733C808132F189'.

TrialnError commented on 2021-06-20 18:39 (UTC)

Sure thing, vaygr.
And thanks for getting into contact with upstream.

vaygr commented on 2021-06-20 16:50 (UTC)

TrialnError I reached out to Jari, and now the patch is there:

Could you please bump the package once again?

vaygr commented on 2021-06-17 13:39 (UTC)

Ah I see, yes, green highlight confused me :) I think it should be safe.

TrialnError commented on 2021-06-17 06:45 (UTC)

You mean the changes in libmount/src/context_umount.c?
As those lines get removed I suppose the added lines after this are at the place where they should be.

vaygr commented on 2021-06-16 21:59 (UTC)

No worries.

One change in the patch that I noticed was a move of "return loopdev_is_used(devname, src, offset, 0, flags);" down the block. Was it a typo?