The update of lib64opensc4 should remove lib64opensc3. Probably an oversight.
1 Like
opensc-0.16.0-2 quick fix solved the issue.
Thanks.
1 Like
Apologies for not explaining this sooner, I’ve been on a forced sabbatical. This explanation is “as best as I understand the issue”. So errors are possible. Previously we had a QA procedure where new packages would go in the appropriate testing repo and also be listed in a utility called Kahinah. Kahinah is where QA and devs were supposed to vote packages up or down. To move a package to updates repo required 3 + votes whereas 3 - votes rejected a package. This worked well for a while or so it seemed to me. However over time problems developed. One is well known in that there is no good mechanism to vote up/down package groups like Plasam5, KApps, systemd, etc. And from experience I can say voting for each package individually is to much to ask. This never really got dealt with. Another issue is that over time the people who are supposed to vote started to take longer and longer no doubt leading to frustration on the part of those who built the packages. At some point devs started to just move packages to updates repos leading to a situation wherein we have no real QA on packages currently.
My purpose is not to cast blame just to point out a serious situation that in my opinion should become our first priority to get fixed. It seems to me at the very least odd that the Association/distro would be thinking of releasing an ISO for public consumption without first fixing this. On the other hand there may be question of can we fix this? Will people actually vote in a timely manner? Do we have enough people to do this effectively? And now that some time has elapsed since first bringing this up do other people in the disto and Association care as strongly about this as I do? If not then well that is an answer too.
I don’t know what if anything has been done on this issue in my absence. Just spent some time in Kahinah and just about every package I looked at is already in an updates repo so it doesn’t appear as if Kahinah is being used currently.
Edit: I have spoken with Colin about this and he is looking in to the matter.
If so that’s great but as of ISO 1077 the ISO’s are still using main-testing. I can assure everyone that it is a major pain trying to deal with this in the context of user testing so far - thinking about trying to deal with this after a public release scared the bejeezus out of me, it would be a nightmare for QA people.
Edit: I’m assured that this is fixed or being fixed. Thanks to TPG.
@ben79 main/testing repository has been cleaned by me. None rpm from this repository are pulled on ISO.
There is a pull-request waiting to be reviewed by me to allow to exclude testing repo when building iso with omdv-build-iso. I can not merge it now as i didn’t review it and i do not want to broke iso building now.
2 Likes
Kahiniah is not maintained and does not handle mass updates.
There were an approach to add QA features to ABF, but this task is not tracked at all by anyone.
It seems @robxu9 is back working on it.
1 Like
@raphael it seems 
Anyways we could get more benefits when QA tool will be integrated into ABF.
Thanks, much appreciated.
Colin and Robert are looking in to these issues and working on them. All is not lost…
1 Like