Arch and Dracut version

[anon49550872]

I can see a Dracut version 059-1 in the Extra-Testing repo.

endeavouros/dracut 059-1 [installed]
    An event driven initramfs infrastructure

Few questions:

Will EnOS keep providing a dracut version in their repo or we will use the upstream version ?
Any actions required once this version releases ?

Thanks.

[firefly]

Apparently hell has frozen over - it had been out of date for more than a year.

@anon49550872

Will EnOS keep providing a dracut version in their repo or we will use the upstream version ?

If I recall it correctly, @dalto mentioned once that in case of an update it’ll be removed from EOS repo.

[anon49550872]

@firefly

it was outdated for more than year.

Indeed, I noticed that yesterday the version 0.56 was there in the testing repo, flagged out-of-date.

@firefly

If I recall it correctly, @dalto mentioned once that in case of an update, it’ll be removed from EOS repo.

Cool… I presume that this will happen transparently to the end user?

I mean, if a package is removed from the EnOS repo, the update process will find it in the Arch’s repo, same version in this case… Pacman won’t install Arch’s version, only if Arch update their version to a newer one other than the 0.59-1 ?

[BluishHumility]

@firefly

If I recall it correctly, @dalto mentioned once that in case of an update it’ll be removed from EOS repo.

That’s right, at least in this thread if not others:

Dracut overlayfs missing?

The current version of dracut has an overlayfs module. The version in the Arch repos is out of date due to packaging dispute between dracut and the Arch maintainers about signing. The result of that the repo version is 3 major versions out-of-date. When we last it looked into it it seemed like that was on-track to getting resolved. It seems that still hasn’t happened. We may need to look into packaging dracut ourselves.

It looks like the issue mentioned in the thread (something about a cross-signing key) was finally closed a few hours ago.

057 release without a signed tag and no signed assets

@anon49550872

I mean, if a package is removed from the EnOS repo, the update process will find it in the Arch’s repo, same version in this case… Pacman won’t install Arch’s version, only if Arch’s update their version to a newer one other than the 0.59-1 ?

If a package is available from more than one of the repos in /etc/pacman.conf, the one closest to the top of the list will be used for that package. The version of the package doesn’t matter, it’s the placement in the configuration file that decides.

In this case, if the package was removed from the EOS repo then EOS users would just get the version from the Arch repo (or whatever repo they have next that has the package).

[dalto]

@anon49550872

Will EnOS keep providing a dracut version in their repo or we will use the upstream version ?

We will remove our version once that happens.

Then once the next update hits it will automatically come from Arch.

[anon49550872]

Thanks everyone for the replies!