#7655 Please improve the way how to show orphaned packages
Closed: Upstream 5 years ago by kevin. Opened 5 years ago by jskarvad.

  • Describe the issue
    According to the [1] the list of orphaned packages is on the [2]. Currently there are over 4600 packages. Unfortunately it seems:
  • there is no search dialog, so you have to go page by page (97 pages!) to see whether the package is orphaned
  • there are no quick-links e.g. according to the first letter of the package name
  • fortunately, the page number is in the URL, so you can guess the page number and find the right page by an trial and error
  • unfortunately, it's ultra slow, the page load can take over 10 seconds, so even if crawling it script it could take over 20 minutes! (I will not do it to not kill the server :)

In case it's not possible to improve the page [2] could be just the up-to-date plain text of the orphaned packages hosted somewhere?

[1] https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Lists_of_Orphan_and_Retired_Packages
[2] https://src.fedoraproject.org/user/orphan/projects

  • When do you need this? (YYYY/MM/DD)

  • When is this no longer needed or useful? (YYYY/MM/DD)

  • If we cannot complete your request, what is the impact?
    Low comfort when referencing orphaned packages.


I'm not sure this is the best place to discuss this, but we can leave it here until we figure out a better place.

@pingou is this something for the upstream pagure tracker? Or parts of it anyhow?

Metadata Update from @kevin:
- Issue tagged with: src.fp.o

5 years ago

Some of these are definitely for upstream (the slowness part and the filtering of projects for examples), other may be downstream, we'll have to see what we can do :)

Hm looking further at this, I think they are all upstream issues.

Note to @jskarvad there is an API which would help scripting if you still wanted to :)
https://src.fedoraproject.org/api/0/

Thanks for info. I opened this, because I wanted to quickly check list of orphaned packages and wasn't able to do it (without scripting). So I am OK if you bring it upstream.

Great. Can one of you file these issues upstream?

Thanks!

Metadata Update from @kevin:
- Issue close_status updated to: Upstream
- Issue status updated to: Closed (was: Open)

5 years ago

Since then, things have got worse
the orphan page does not open at all anymore,
instead a 504 Gateway Timeout is returned.

Since I could not find a Pagure issue
about the slowness problem
I now reported pagure/issue/5209.
Most probably the usabiity issues are still also there
but I cannot say,
because I have never seen that page opened,
so I will wait until it is actually possible to open it
before filing tickets about the other issues.

Login to comment on this ticket.

Metadata