Project

General

Profile

Freedom Issue #3550

All? nonfree packages from Arch Linux slipped to Parabola repos

grizzlyuser - 4 months ago - . Updated 8 days ago.

Status:
fixed
Priority:
freedom issue
Assignee:
% Done:

0%


Description

  • expected result:
    No packages found on steps 1) and 3).
  • actual result:
    Step 1) cuda package is found, which is currently blocklisted by Parabola blacklist.txt.
    Step 2) linux package is found, which is currently blocklisted by Parabola blacklist.txt. And yes, I still have 'your-freedom' installed. It looks like 'your-freedom' doesn't prevent installation of nonfree packages. For example, I could install 'firefox' this way.

History

#1

Updated by wael 4 months ago

  • Priority changed from bug to freedom issue
  • Status changed from unconfirmed to confirmed
  • Tracker changed from Bug to Freedom Issue
#2

Updated by bill-auger 4 months ago

as with #3437 last year, this is almost certainly due to resource exhaustion on the repo server (also #3053 #3343 #3351 and others) - #3437 fixed itself the next time the importer ran; and it probably will this time also

this is not a freedom concern for users; but a distribution problem for parabola - as long as 'your-freedom' is installed, it is not possible to install any of those packages - 'your-freedom' is required by 'base', which is considered to be mandatory for a fully-supported parabola system

i havent verified this theory yet; but cgit was not responding for some time yesterday - i suspect that the importer does not halt if it fails to download the blacklist file - the result is that it makes the resources problem worse for the next day; because the repo server is so low on disk space - i disabled imports for i686 and arm yesterday for that reason; but not x86_64

i think all of these strange intermittent problems will be avoided when the web services are moved to the new server, which will take most of the load off the repo server, and to ensure that the importer halts if it fails to download the blacklist file

#3

Updated by bill-auger 4 months ago

  • Status changed from confirmed to in progress

ok it fixed itself again - i will leave this ticket open though; and try to find a way to prevent it from happening again

#4

Updated by grizzlyuser 4 months ago

It happened again:

$ pacman -Ss linux-firmware | grep 'core/linux-firmware '
core/linux-firmware 20230804.7be2766d-2

#5

Updated by grizzlyuser 4 months ago

It's interesting that 'your-freedom' package does not conflict with 'linux', 'linux-firmware', 'firefox'. Was this done intentionally, like for technical reasons?

#6

Updated by bill-auger 4 months ago

it is probably because some packages in libre must provides=() an arch
dependency - it would be good to constrain that mechanism per-repo

the unwanted packages have been purged again - im still not sure which code is
responsible for the quirk; but it may have been a bug in some code i injected -
if that is the source of problem, i just fixed it - if not, i could add a new
explicit safeguard to force the import to fail

#7

Updated by bill-auger 8 days ago

  • Assignee set to bill-auger
  • Status changed from in progress to fixed

ok its been a few months - looks like i fixed it for good this time

Also available in: Atom PDF