Hello. After recent [nonsystemd]base (I'll omit nonsystemd prefix below) update, I am unable to upgrade my Parabola properly. The base package depends on your-init-freedom, which was before your-initfreedom (without dash).
While the abslibre git repo contains your-init-freedom PKGBUILD and does not contain your-initfreedom one, the actual Parabola repositories seem to only have your-initfreedom and not your-init-freedom: see search results https://www.parabola.nu/packages/?q=your-init . Manual installation of your-init-freedom also fails: the PKGBUILD contains the following _gitver daf9eebc77cc719c818165e256efd5e0d5dee7aa for https://git.parabola.nu/blacklist.git repo, while it does actually exist. I've changed the hash to master in order to get the latest your-init-freedom blacklist version. With such change, the package installs properly, and the base package installation stops complaining about missing dependency. Unfortunately, there are further issues which prevent Parabola upgrade process. The new version of base tries to create /usr/bin/init, while it's already owned by openrc-init. The latter is a required dependency for openrc and for the previous version of base. There are several possible options to solve that, I consider all of them non-trivial and I do not know which one is preferrable. To sum up: - Actual Parabola repositories still contain your-initfreedom instead of your-init-freedom. - The previous issue might be a result of nonexistent gitver mentioned in your-init-freedom PKGBUILD which prevents its proper build. - The new version of base creates /usr/bin/init, which conflicts with openrc-init which already owns the file. The first two issues might be resolved quickly as they are trivial. Would be glad if at least they are addressed shortly. Thanks! -- Daniil Kovalev _______________________________________________ Dev mailing list [email protected] https://lists.parabola.nu/mailman/listinfo/dev
