Ticket #327 (closed enhancement: fixed)

Opened 6 years ago

Last modified 6 years ago

EL-updates from RHN should be in the buildroots for EPEL builds

Reported by: thl Owned by: ausil
Priority: minor Milestone:
Component: Buildsys Version:
Severity: Normal Keywords:
Cc: Blocked By:
Blocking: Sensitive:

Description

(this ticket is opened as discussed in this weeks EPEL-meeting https://www.redhat.com/archives/epel-devel-list/2008-January/msg00036.html )

The EPEL builders currently use the latest RHEL releases 4 and 5; but some packagers need to have the updates released by RH via RHN available in the buildroot as well for proper function.

Getting the updates from RHN into a repo (via reposync from yum-utils maybe?), running createrepo over them and adding that repo to the builders mock configs should do the trick.

Change History

comment:1 Changed 6 years ago by mmcgrath

Now I remember the problem. How are we going to do this with RHEL4? We can use reposync for RHEL5 (with a bit of voodoo) but I'm at a loss what to do for RHEL4.

comment:2 Changed 6 years ago by mmcgrath

I take that back, talking to seth he thinks it should be possible, going to test it to find out.

comment:3 Changed 6 years ago by skvidal

rhel4 i386 and x86_64 are synced down and will resync every day. ppc is going to be, umm, suffering until I figure out how to make the systemid work. I'll play some more and see what I can do.

comment:4 Changed 6 years ago by skvidal

ppc[64] is now synced down from rhn.

comment:5 Changed 6 years ago by thl

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.