Build control-center in mock fail

Adam Williamson awilliam at redhat.com
Fri May 17 03:38:12 UTC 2013


On Thu, 2013-05-16 at 22:48 -0400, Nico Kadel-Garcia wrote:
> On Thu, May 9, 2013 at 12:12 AM, Rahul Sundaram <metherid at gmail.com> wrote:
> > Hi
> >
> >
> > On Thu, May 9, 2013 at 12:04 AM, Adam Williamson wrote:
> >>
> >>
> >>
> >> Yes, I know that, thanks. I didn't ask for a lecture, but whether this
> >> was actually written down in the guidelines somewhere.
> >
> >
> > It is not written down as policy and since the tools themselves enforce
> > this, I don't think it has been needed
> >
> > Rahul
> 
> Which tool enforces this? Unless the toolkit for the build
> environments is completely isolated from the Internet and uses only
> disk access or local VLAN for it's access to source file repositories,
> this can be very difficult to enforce.

It is, as mentioned elsewhere in the thread. The build hosts do not have
outside network access.

> But I continue to
> run across Java based SRPM's that use "maven" and wind up with broken
> URL's or insufficiently specific URL's that just grab the latest
> modules from their relevant upstream repo.

In Fedora's build system the source tarballs aren't ever 'automagically'
pulled from the URL specified in the spec file, so it can be utterly and
complete incorrect without any obvious consequences. Though by policy,
it's supposed to be valid and correct.

> It would make my life easier to have a stated policy I can point
> packagers to in the wide world. Please?

Fedora's policies only apply to packages that are part of Fedora in any
case, so I'm not sure why you think people who are packaging outside of
the Fedora repositories would pay attention to a Fedora policy, and we
can't really set policies for anyone else...:)
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net



More information about the devel mailing list