On Fri, 2013-05-24 at 10:17 +0300, Alexander Bokovoy wrote:
> On Thu, 23 May 2013, Dean Hunter wrote:
> >On Thu, 2013-05-23 at 13:22 -0400, Rob Crittenden wrote:
> >> Dean Hunter wrote:
> >> > On Thu, 2013-05-23 at 17:58 +0200, Martin Kosek wrote:
> >> >>
> >> >> # koji download-build freeipa-3.2.0-2.fc19 --arch x86_64
> >> >>
> >> >> HTH,
> >> >> Martin
> >> >
> >> > Do these messages mean that there are addition RPMs that are missing
> >> > from the Fedora 19 repositories?
> >> You need samba-4.0.6-2. See
> >> https://bugzilla.redhat.com/show_bug.cgi?id=966130
> >1) Could someone explain why samba-4.0.6-2 is now (as in since the
> >previous response about 8 hours ago) available in Fedora 19
> >updates-testing but freeipa-3.2.0-2 still is not? I would like to
> >understand why freeipa is frozen, but samba is not.
> It is a question to Fedora release management. We stuck with 3.2.0-2 at
> the point when decision to freeze updates machinery was made for F19
> beta release. I think it was later raised but some issues were still in
> place in bodhi which prevented push of packages stuck in flight.
> >2) Creating a local repository populated by koji downloads from bodhi
> >has me considering a local repository as the source for updates to all
> >my machines and updating the local repository at a time of my choosing.
> >Is this a common practice? Are there problems with this approach? Should
> >I use NFS or HTTP to serve the updates?
> You need to wait until F19 machinery properly works. As far as I can
> see, we experienced similar freezes every release cycle of Fedora; it is
> just F19 beta when we were hit hard.
> Remember that F19 is still at alpha stage; F19 beta is slated for May
Thank you for the explanation. The freeze caught me in the middle of
rebuilding my Fedora 19 test VMs. I can not go forward and I do not want
to go back. I will try to be more patient. Thank you.
Freeipa-users mailing list