Bug #3437
Some blacklisted packages slipped into repos, like linux-rt-lts
Status:
fixed
Priority:
bug
Assignee:
% Done:
0%
Description
- steps to reproduce:
1) https://www.parabola.nu/packages/?sort=-last_update&q=linux-rt-lts&maintainer=&flagged=
2) https://git.parabola.nu/blacklist.git/tree/blacklist.txt#n461
- expected result:
No packages found on step #1 as they are blacklisted
- actual result:
Blacklisted packages are in the repos
History
Updated by bill-auger about 1 year ago
- Status changed from unconfirmed to confirmed
all blacklisted packages "slip in" in the same way - they can not be blacklisted until after that happens and someone notices - those were added to the blacklist though - im not sure yet, why they were not deleted automatically
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
Updated by bill-auger about 1 year ago
- Assignee set to bill-auger
- Status changed from confirmed to in progress
the repo importer was using a stale cached copy of the blacklist
in the future, this script can be used to identify them:
#!/bin/bash
readonly PACMANCONF_FILE=/etc/pacman-all.conf
readonly BLACKLIST_FILE=/usr/share/doc/your-freedom/blacklist.txt
pacman --config=${PACMANCONF_FILE} -Sy
for ea in $(cut -d: -f1 ${BLACKLIST_FILE})
do grep -q ^${ea}:: ${BLACKLIST_FILE} && pacman --config=${PACMANCONF_FILE} -Ssq ^${ea}$
done
Updated by bill-auger about 1 year ago
- Project changed from Packages to Servers
- Tracker changed from Freedom Issue to Bug