On 1/15/26 12:04, Alexander Ploumistos wrote:
Hi Jiri,
On Thu, Jan 15, 2026 at 11:52 AM Jiri Vanek <[email protected]> wrote:
Hello!
Can please anybody remaind me how is this composed? How the package could end
as orhpan, even if it is maintianed (commit at least once per three monhts, but
usually more often (including upstream versions updates), and passing all mass
rebuilds ...), and working fine?
As far as I know, a package becomes an orphan the moment it loses its
Yah! And how it can happen? They did not FTBS.... Ihad not get rid of the... So
why? How?
This time it was https://src.fedoraproject.org/rpms/openjdk-asmtools/
and last time it was https://src.fedoraproject.org/rpms/jd-core and/or
https://src.fedoraproject.org/rpms/java-jd-decompiler
Some time ago, when I was less watchfull about this kind of emial (thanks for
it!), some of my packages even retired and I noticed oonly during push
(shameful:( )
I think I keep watching FTBFS quite enouugh...
main admin. Commits and rebuilds do not matter (unless of course it
FTBFS for some time), the important part is ownership.
You can claim any of these packages, e.g.
https://src.fedoraproject.org/rpms/cmake-fedora by logging in and
clicking on the "Take" button in the left-hand column.
Yout, that is known to me, and if I see my name in "Orphaned packages looking for new
maintainers" I moreover automatically click "take" again.
Just why.. :)
Thanx a lot for reply!!!! In fedora lists, one is never alone. Thanks again!
J.
--
Jiri Vanek <[email protected]>
Principal JDK QA engineer
IBM Middleware Czechia s.r.o.
+420 775 39 01 09
--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
