Arch and Dracut version

[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).