Permanent URL for EPEL configuration

[Remi Collet]

Why doesn't this exists yet ?

Most third party repository have some permanent URL.

Each time epel-release is updated to a new version, so much stuff is
broken (doc, scripts, ...)

Is it so hard to simply create a link ?

So:
https://fedorahosted.org/fedora-infrastructure/ticket/3605

Regards,
Remi.

[Kevin Fenzi]

On Fri, 21 Dec 2012 14:59:14 +0100
Remi Collet  wrote:
> Why doesn't this exists yet ?

Because there's not an automated way to create it?

And having it be "when someone with access notices an epel-release
update and happens to update it" is fragile. ;(
> Most third party repository have some permanent URL.
>
> Each time epel-release is updated to a new version, so much stuff is
> broken (doc, scripts, ...)

Where are these? In the wiki?

Perhaps we could use a template file there? (then we still have the
manual problem, but at least anyone with a wiki account could update
it).
> Is it so hard to simply create a link ?
>
> So:
> https://fedorahosted.org/fedora-infrastructure/ticket/3605

No, but it's hard to keep maintaining that manually.

kevin

[Remi Collet]

Le 21/12/2012 19:17, Kevin Fenzi a écrit :
> On Fri, 21 Dec 2012 14:59:14 +0100
> Remi Collet  wrote:
> > Why doesn't this exists yet ?
>
> Because there's not an automated way to create it?

A simple one:

ln -f 6/i386/epel-release-* epel-release-6.rpm
> And having it be "when someone with access notices an epel-release
> update and happens to update it" is fragile. ;(
> > Most third party repository have some permanent URL.
> >
> > Each time epel-release is updated to a new version, so much stuff is
> > broken (doc, scripts, ...)
>
> Where are these? In the wiki?

The wiki give a link to the repoview page.
This will allow to also use a permanent link

There is a lot of tuto using something like:
yum install
http://dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm

Search epel-release on google
You will find entry with 6-3, 6-4, 6-5, ...

Remi
> Perhaps we could use a template file there? (then we still have the
> manual problem, but at least anyone with a wiki account could update
> it).
> > Is it so hard to simply create a link ?
> >
> > So:
> > https://fedorahosted.org/fedora-infrastructure/ticket/3605
>
> No, but it's hard to keep maintaining that manually.
>
> kevin
>
> epel-devel-list mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/epel-devel-list

[Kevin Fenzi]

On Sat, 22 Dec 2012 07:35:51 +0100
Remi Collet  wrote:
> Le 21/12/2012 19:17, Kevin Fenzi a écrit :
> > On Fri, 21 Dec 2012 14:59:14 +0100
> > Remi Collet  wrote:
> > > Why doesn't this exists yet ?
> >
> > Because there's not an automated way to create it?
>
> A simple one:
>
> ln -f 6/i386/epel-release-* epel-release-6.rpm

How is that automated? :)

Sure, I can do that manually right now, but what makes you think I
would notice when there's a new update? Manually putting it on a
person is something I want to avoid. ;)

Perhaps we could use something from the fedmsg bus to detect when this
package is pushed to stable. Or run a cron job that lists the most
current one in the repo...
> The wiki give a link to the repoview page.
> This will allow to also use a permanent link
>
> There is a lot of tuto using something like:
> yum install
> http://dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
>
> Search epel-release on google
> You will find entry with 6-3, 6-4, 6-5, ...

kevin

[Ken Dreyer]

On Thu, Dec 27, 2012 at 10:58 AM, Kevin Fenzi  wrote:
> Sure, I can do that manually right now, but what makes you think I
> would notice when there's a new update? Manually putting it on a
> person is something I want to avoid. ;)
>
> Perhaps we could use something from the fedmsg bus to detect when this
> package is pushed to stable. Or run a cron job that lists the most
> current one in the repo...

I too was wondering where the right tool is for this. Would it be
appropriate to build this functionality into mash?

- Ken

[Michael Stahnke]

On Thu, Dec 27, 2012 at 9:58 AM, Kevin Fenzi  wrote:
> On Sat, 22 Dec 2012 07:35:51 +0100
> Remi Collet  wrote:
> > Le 21/12/2012 19:17, Kevin Fenzi a écrit :
> > > On Fri, 21 Dec 2012 14:59:14 +0100
> > > Remi Collet  wrote:
> > > > Why doesn't this exists yet ?
> > >
> > > Because there's not an automated way to create it?
> >
> > A simple one:
> >
> > ln -f 6/i386/epel-release-* epel-release-6.rpm
>
> How is that automated? :)
>
> Sure, I can do that manually right now, but what makes you think I
> would notice when there's a new update? Manually putting it on a
> person is something I want to avoid. ;)
>
> Perhaps we could use something from the fedmsg bus to detect when this
> package is pushed to stable. Or run a cron job that lists the most
> current one in the repo...

Another option, how do we just get epel-release into RHEL? Scientific ships
with it in their core. It makes things so much nicer. I realize Red Hat
doesn't want to support everything from EPEL, but having it easily
available might be nice. I haven't used a RHEL system since 2007 without
EPEL anyway ;)
> > The wiki give a link to the repoview page.
> > This will allow to also use a permanent link
> >
> > There is a lot of tuto using something like:
> > yum install
> > http://dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
> >
> > Search epel-release on google
> > You will find entry with 6-3, 6-4, 6-5, ...
>
> kevin
>
> epel-devel-list mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/epel-devel-list

[Stephen John Smoogen]

On 27 December 2012 11:15, Michael Stahnke  wrote:
> On Thu, Dec 27, 2012 at 9:58 AM, Kevin Fenzi  wrote:
> > On Sat, 22 Dec 2012 07:35:51 +0100
> > Remi Collet  wrote:
> > > Le 21/12/2012 19:17, Kevin Fenzi a écrit :
> > > > On Fri, 21 Dec 2012 14:59:14 +0100
> > > > Remi Collet  wrote:
> > > > > Why doesn't this exists yet ?
> > > >
> > > > Because there's not an automated way to create it?
> > >
> > > A simple one:
> > >
> > > ln -f 6/i386/epel-release-* epel-release-6.rpm
> >
> > How is that automated? :)
> >
> > Sure, I can do that manually right now, but what makes you think I
> > would notice when there's a new update? Manually putting it on a
> > person is something I want to avoid. ;)
> >
> > Perhaps we could use something from the fedmsg bus to detect when this
> > package is pushed to stable. Or run a cron job that lists the most
> > current one in the repo...
>
> Another option, how do we just get epel-release into RHEL? Scientific ships
> with it in their core. It makes things so much nicer. I realize Red Hat
> doesn't want to support everything from EPEL, but having it easily available
> might be nice. I haven't used a RHEL system since 2007 without EPEL anyway
> ;)

I don't believe it will ever happen. Too many customers take it to
mean that what is shipped on Red Hat means it is Red Hat built and
supported. From dealing as a customer the number of times I had to
"report" flash because my boss told me to means that even shipping
EPEL installation instructions means a lot of pain and suffering.

[Mikael Fridh]

On Fri, Dec 21, 2012 at 2:59 PM, Remi Collet  wrote:
> Why doesn't this exists yet ?
>
> Most third party repository have some permanent URL.
>
> Each time epel-release is updated to a new version, so much stuff is
> broken (doc, scripts, ...)
>
> Is it so hard to simply create a link ?
>
> So:
> https://fedorahosted.org/fedora-infrastructure/ticket/3605

I agree it's been annoying on a few occassions ... but I always have a
version of epel-release in my own internal repo and just add my
internal repo with the repo command in the kickstart config and
include epel-release in the %packages section. Then I follow that up
with a yum upgrade (which pulls down newest from upstream epel), so I
rarely have to worry about this, if ever anymore ...

Anyway, I did this for fun just to show how it can be done
_externally_ by someone not in the Fedora org:
https://github.com/frimik/epel-latest#readme

Demo:

rpm -qip http://warm-scrubland-1864.herokuapp.com/epel-latest/6/x86_64/epel-release
rpm -qip http://warm-scrubland-1864.herokuapp.com/epel-latest/6/x86_64/fail2ban

--
Mikael

[Russell Golden]

I have a question that may better address the problem. At least to me.

Why does epel-release need to change so much in the first place?

Russell Golden
Fedora Project Contributor
[e-mail]
[phone]
--
"We are the Borg. Lower your shields and surrender your ships. We will
add your biological and technological distinctiveness to our own. Your
culture will adapt to service us. Resistance is futile."

[Stephen John Smoogen]

On 21 January 2013 12:11, Russell Golden  wrote:
> I have a question that may better address the problem. At least to me.
>
> Why does epel-release need to change so much in the first place?

I believe it is due to key signing. The key is signed against the
other Fedora Keys. So when the F18 key or some other key comes out,
the EPEL key gets signed with it.
> Russell Golden
> Fedora Project Contributor
> [e-mail]
> [phone]
> --
> "We are the Borg. Lower your shields and surrender your ships. We will
> add your biological and technological distinctiveness to our own. Your
> culture will adapt to service us. Resistance is futile."
>
> epel-devel-list mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/epel-devel-list

[Kevin Fenzi]

On Tue, 22 Jan 2013 08:05:42 -0700
Stephen John Smoogen  wrote:
> On 21 January 2013 12:11, Russell Golden
>  wrote:
> > I have a question that may better address the problem. At least to
> > me.
> >
> > Why does epel-release need to change so much in the first place?
>
> I believe it is due to key signing. The key is signed against the
> other Fedora Keys. So when the F18 key or some other key comes out,
> the EPEL key gets signed with it.

It doesn't change very often at all. From the changelog:

* Sun Nov 04 2012  - 6-8
- Fix URL bz #870686

* Wed May 09 2012 Jens Petersen  - 6-7
- add ppc64 to ghc_arches

* Tue Jan 10 2012 Jens Petersen  - 6-6
- add /etc/rpm/macros.ghc-srpm from fedora redhat-rpm-macros

* Tue Oct 12 2010 Michael Stahnke  - 6-5
- Fix bug #627611

* Wed Aug 11 2010 Seth Vidal <skvidal at fedoraproject.org> - 6-4
- conflict fedora-release
...

so 2 or 3 times a year due to macros or other adjustments and sometimes
0 times a year (2010).

kevin

[Stephen John Smoogen]

On 22 January 2013 08:22, Kevin Fenzi  wrote:
> On Tue, 22 Jan 2013 08:05:42 -0700
> Stephen John Smoogen  wrote:
> > On 21 January 2013 12:11, Russell Golden
> >  wrote:
> > > I have a question that may better address the problem. At least to
> > > me.
> > >
> > > Why does epel-release need to change so much in the first place?
> >
> > I believe it is due to key signing. The key is signed against the
> > other Fedora Keys. So when the F18 key or some other key comes out,
> > the EPEL key gets signed with it.
>
> It doesn't change very often at all. From the changelog:
> Sun Nov 04 2012  - 6-8
> Fix URL bz #870686
> Wed May 09 2012 Jens Petersen  - 6-7
> add ppc64 to ghc_arches

Dude.. what have we told you about bringing real facts into an EPEL
argument? Now we have to come up with a new conspiracy.

PS thanks. I should have checked the rpm and not the memory.