On Wed, 2021-08-18 at 08:56 -0700, Kevin Fenzi wrote: > On Wed, Aug 18, 2021 at 08:15:36PM +0700, Didik Supriadi wrote: > > I think ppl now can go to > > https://packager-dashboard.fedoraproject.org/user/orphan to see > > orphaned > > packages. > > IMHO, we should not point people to this list.y Then I messed it up by editing the Wiki. Should I revert the Wiki to the non-working orphans page ? > I think it might be better to > suggest pacakging something the user users thats not packaged, or > looking for more simple requests on the wishlist? I checked out the wishlist and the first entry is the orphans page, that leads to the link I edited to the packager dashboard orphans. So I am now a bit confused on what should be the path to look for a new package. It seems there is no consensus on this issue. Right now, I was aiming for rarian. It was orphaned a week ago, but the packager dashboard shows many dependencies that will be in trouble in a month: - dia - etherape - gconf-editor - glade2 - gnome-search-tool - gnome-translate - grhino - gtk-v4l - mail-notification - pioneers - qalculate-gtk - stardict - ucview - viking - xiphos - xiphos There is an email by Mukundan Ragavan on the list stating it was going to be orphaned because notning depends on it on rawhide. https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/MLIT6EJ4RIWJKW34E7BVGUQMC2AP4QFK/ He used this repoquery to check it out: # dnf repoquery --releasever rawhide --whatrequires librarian\* Last metadata expiration check: 0:02:50 ago on Wed 11 Aug 2021 06:03:30 PM EDT. rarian-compat-0:0.8.1-27.fc34.x86_64 rarian-devel-0:0.8.1-27.fc34.i686 rarian-devel-0:0.8.1-27.fc34.x86_64 But my results for the "rairian" package differ: [iago@rawhide]$ dnf repoquery --releasever rawhide --whatrequires "rarian*" Last metadata expiration check: 0:00:26 ago on Thu 19 Aug 2021 10:34:56 PM CEST. alleyoop-0:0.9.8-18.fc35.x86_64 etherape-0:0.9.18-8.fc35.x86_64 gnome-translate-0:0.99-39.fc35.x86_64 grhino-0:0.16.1-13.fc35.x86_64 mail-notification-0:5.4-100.git.9ae8768.fc35.x86_64 pioneers-0:15.6-3.fc35.x86_64 rarian-compat-0:0.8.1-27.fc34.x86_64 rarian-devel-0:0.8.1-27.fc34.i686 rarian-devel-0:0.8.1-27.fc34.x86_64 ucview-0:0.33-21.fc35.i686 ucview-0:0.33-21.fc35.x86_64 It seems most packages requires rarian-compat as - I guess - most used it as a replacement for scrollkeeper. alleyoop -> rarian-compat -> rarian etherape -> rarian-compat -> rarian gnome-translate -> rarian-compat -> rarian grhino -> rarian-compat -> rarian mail-notification -> rarian-compat -> rarian pioneers -> rarian-compat -> rarian ucview -> rarian-compat -> rarian The other problem stated by Mukundan was: "Last upstream release was in 2008 and this is currently FTBFS on rawhide/F35". Indeed the package doesn't build, but it's a combination of ancient autotools & libtool and rpath rpm checks failing. I got it building on rawhide by fiddling with the sources and now I can get a working rpm. I have to put all the commands and patches on the spec file, but it don't looks like it's going to be a huge problem. Most Makefile.am files need to be touch, but the changes are minimal. Should I go fot it or I'd rather search for other package on the wish list ? Thanks in advance. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
