Re: Extras not enabled on koji?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Sun, 5 Apr 2020 at 19:37, Richard Shaw <hobbes1069@xxxxxxxxx> wrote:
On Sun, Apr 5, 2020 at 5:21 PM Kevin Fenzi <kevin@xxxxxxxxx> wrote:
On Sun, Apr 05, 2020 at 03:37:29PM -0500, Richard Shaw wrote:
> On Sun, Apr 5, 2020 at 9:52 AM Stephen John Smoogen <smooge@xxxxxxxxx>
> wrote:
>
> > OK so swig3 seems to just be in CentOS extras and not in RHEL extras.
> >
>

> This doesn't make for a good packager experience :)

Well, not sure how to make it better. We could move to building against
CentOS, but that would be a big undertaking and some folks would like
that and some would not.

We could perhaps advertise the developer rhel subscription more for
testing?

Open to other ideas...

Well I should have been more specific. What I mean by a "poort packager experience" is about consistency. When I build the package in mock, it built. When I built it in COPR, it built. But when I tried to build the real package, it failed.

This may be a corner case where things are "different" but consistency *IS* important.


Yes I agree.. but we have built against RHEL for years and they do not have this package in their extras. CentOS does have it in their Extras which is the inconsistency. The problem is that CentOS EL5/EL6 had an Extras channel which had updated swig and other packages in it, but RHEL-7 named one of their channels Extras which was to have non-supported packages in it. So both groups did something inconsistent with each other and you and us got stuck with it.

I can't fix either CentOS or RHEL package sets or channel names. I can't tell either of them what should be in these channels especially for channels which are older than a year old. I can't create a consistent package experience. I can commiserate with you and say I understand what a frustration it is... but that is cold comfort.


--
Stephen J Smoogen.

_______________________________________________
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

[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux