On Tue, Sep 3, 2024 at 1:16 PM Leon Fauster via epel-devel <epel-devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > Am 03.09.24 um 18:00 schrieb Troy Dawson: > > On Sun, Sep 1, 2024 at 3:03 PM Gary Buhrmaster > > <gary.buhrmaster@xxxxxxxxx <mailto:gary.buhrmaster@xxxxxxxxx>> wrote: > > > > On Sat, Aug 10, 2024 at 10:42 PM Carl George <carl@xxxxxxxxxx > > <mailto:carl@xxxxxxxxxx>> wrote: > > > > > > > > Happy packaging! > > > > > > > I have noted that some dependencies for some > > of my packages are (apparently) no longer > > going to be shipped in EL10 (they were in > > EL9). > > > > Before I request the branches and builds > > in EPEL10, I would like to make sure those > > packages are really removed from EL10, and > > are not some artifact of my misunderstandings. > > > > Is there a list somewhere of packages that > > are known to have been removed from EL10? > > > > > > Three things I do. > > 1 - Go to the CentOS Stream koji instance, look up the package, look at > > the latest el10 build of that package, and see if it's tags have been > > removed, or it has a trashcan tag. > > Examples: > > bash (still there) - > > https://kojihub.stream.centos.org/koji/buildinfo?buildID=62779 > > <https://kojihub.stream.centos.org/koji/buildinfo?buildID=62779> > > java-17-openjdk (removed) - > > https://kojihub.stream.centos.org/koji/buildinfo?buildID=66493 > > <https://kojihub.stream.centos.org/koji/buildinfo?buildID=66493> > > > > 2 - dnf list <package> > > This isn't the best. Sometimes a package is still in the process of > > being removed. Or it's been untagged, but we haven't had a successful > > compose pushed out. > > But, it's still a quick way to check. > > > > 3 - jira search > > The CentOS Stream 10 package removals are public in jira. We have a tag > > for centos-stream-10 package removals. > > This isn't 100% accurate, because sometimes the package has been > > re-added, but that is rare. > > https://issues.redhat.com/browse/CS-2504?jql=labels%20%3D%20rhel-10-beta-package-removal <https://issues.redhat.com/browse/CS-2504?jql=labels%20%3D%20rhel-10-beta-package-removal> > > > > > I wonder if RHEL10 will have a Workstation flavor? Or if CS10 will be > usable as Workstation OS. When I see all the missing/removed parts. > Can not imagine that EPEL can compensate this all (e.g. is firefox in > the compose?). > > > -- > Leon > > > > > > -- > _______________________________________________ > epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to epel-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/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue Why can't EPEL compensate for this? If RHEL doesn't ship it, then it's probably eligible to be shipped in EPEL. Several desktop apps such as firefox were dropped, but all it takes is someone willing to maintain them in EPEL 10. If there is a package you rely on that was dropped, then become a packager and file a bug asking the Fedora maintainer to add you as a co-maintainer. https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/ https://docs.fedoraproject.org/en-US/epel/epel-package-request/#fedora_packagers -- Carl George -- _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-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/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
