My main priority is that we get packages built. I don't mind if the original rootfs is
used or a new one but I would not want to prioritize getting bootable kernels over e.g.
chrooting onto either of the original rootfs or whatever candidates exist to replace it.
So my $0.02 is let's get the VM and build process working using something folks can
chroot into and let the building continue (with results feeding back into the new repo)
while other efforts at images take place in parallel.
My suggestion is that a new area on Scotland regularly sync with your VM, and both ends
are setup via cron to sync and run createrepo. Either should be useable as a repo source
for mock though I don't mind if in practice Scotland is a backup mirror and we all
share keys that allow us to push builds to your VM as primary.
Ideally, before Friday anyone who wants to contribute can use whatever rootfs we want to
standardize on, run mock with the repo hosted inside your throwaway VM as a source
(alongside noarch and group reps from primary) and then push the results back to your VM.
That would then be backed up to Scotland. If we could automate the pushing to your VM then
so much the better but the main thing is that folks can easily contribute builds. That way
we can run another VFAD very soon.
Hopefully not much longer to get to Koji. I will followup on e.g. RPM patches later -
currently on the way to the Isle of Wight with my gf and being reminded I said I would try
not being online...
Jon.
--
Sent from my phone - message formatted and/or shortened accordingly.
-----Original Message-----
From: Dennis Gilmore [dennis(a)ausil.us]
Received: Monday, 15 Aug 2011, 17:14
To: Jonathan Masters [jcm(a)redhat.com]; jkc(a)redhat.com, ctyler(a)seneca.ca,
arm(a)lists.fedoraproject.org, blc(a)redhat.com, jcm(a)redhat.com
Subject: RE: Rootfs and mock
I spent some time on the weekend working on a rootfs that has working mock out of the box.
The cm is up. Ill put a SSH key in the rootfs people will be able to use to rsync builds
up. Right now I need to get a good set of kernels for it. At the least tegra and omap imx
if dans work pays off as well. Anything else people think we will need? I have it booted
on my trimslice.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Jonathan Masters <jcm(a)redhat.com> wrote:
Also. I pulled Ken's bits earlier so mock in the rootfs should work as long as the fs
(eg NFS) you use has the right fs cap support (eg v4 nfs). We should keep the rootfs
around and not archive it until at te earliest the point where we have a bootable F15
image. I will handle the archiving in co-operation with Dennis at that time.
I am not on IRC until Thu but I will try to sneak online when my gf doesn't notice
while on the Isle of Wight :)
--
Sent from my phone - message formatted and/or shortened accordingly.
-----Original Message-----
From: Jonathan Masters [jcm(a)redhat.com]
Received: Monday, 15 Aug 2011, 15:22
To: jkc(a)redhat.com, dennis(a)ausil.us, ctyler(a)seneca.ca, arm(a)lists.fedoraproject.org,
blc(a)redhat.com
CC: jcm(a)redhat.com
Subject: Rootfs and mock
Ken, Dennis, Chris,
Forgive the bad formatted phone email. I am on the way for three days of vacation and have
a bad cold or worse...so this will have to do :)
The rootfs in git has served its purpose. We can run mock now. The best thing going
forward is to build one set of RPMs, either using mock running in the rootfs or using
native builds from Dennis' semi-bootable F15 image. What we don't need to do is
update the rootfs. Just use it to run mock if you need to and then we will stash the RPMs
we build in a common repo we keep synced.
I spoke with Dennis last week. He is setting up a VM on his server we can use to host a
set of common RPMs. I hope Ken can work with Chris on #fedora-arm to perhaps get Ken a
login on Scotland and then work with Dennis to setup a means to replace the current set of
armb7hl repo bits on Scotland with an rsync of Dennis' new VM. Dennis will supply a
login for pushing to his VM which will also host the RPMs. Then, people building with mock
can stash to either place, they will sync with cron, and serve as the source repo for
building more.
Hope this makes sense. Please co-ordinate to make this happen so our VFADs can start up
again :)
Jon.
--
Sent from my phone - message formatted and/or shortened accordingly.
Show replies by date