3:54 a.m.
Under http://alt.fedoraproject.org/pub/alt/nightly-composes/ are
supposed to be the nightly-builds of the "latest" code. However, a
quick look at the logs shows that those are build once in a week or
even not that "often".
Can someone explain why? It's just a signle script to be run. I really
cannot understand where the problem is to build every night the isos?
1:12 p.m.
On Tue, 1 Jun 2010 01:17:09 +0200
"Joshua C." <joshuacov(a)googlemail.com> wrote:
Great!
Well after booting - no KDE, 2 kernel oops. This is fine when we
consider the switch to the beta-kde and the very early stage of the
2.6.34 kernel.
Yep. It's early days for rawhide. ;)
The idea is good but I don't think that it's worthy. If I
compose my
own isos then I won't depend on the nightly composes. And the fedora
infrastructure is a way better than my pc :-)
Sure, but you probibly only want the kde one in one arch. ;)
You can do that faster than I can make all the isos.
Why is this syncing done manually. If the isos are automatically
build
(which I think is the case here), why cannot they be automatically
synced to the server?
I have been meaning to set that up, just haven't gotten to it. The
composes are hosted on another machine, so I have to rsync them with my
credentials. I'm sure something can be worked out to script it, I will
try and do so this cycle.
kevin
6:17 p.m.
2010/5/31 Kevin Fenzi <kevin(a)scrye.com>:
On Sun, 30 May 2010 22:01:12 +0200
"Joshua C." <joshuacov(a)googlemail.com> wrote:
>
> I expected this but without seeing the failed logs one can only guess.
Sorry, perhaps a 'state' file or something would be good to have.
I don't know. If the iso is successfully build then this state file
won't help. But any indication that the files are build is a sign in
the right direction.
> > Out of curiosity, what do you use them for, and which spins? :)
>
> I'm interested in the kde spin. I know that the "latest" kde code
> reaches this spin not that fast but the main reason for using the
> nightly composes is the ati/xserver stack. The maintainers have done a
> great job in improving this video driver but it's still away from its
> win**** counter part. The only way to test this and/or apply the
> latest mesa patches is to have the latest rawhide code. The versions
> that go with the serial distributions are outdated.
I am syncing over the new images now. Most everything composed
yesterday. ;)
Great!
Well after booting - no KDE, 2 kernel oops. This is fine when we
consider the switch to the beta-kde and the very early stage of the
2.6.34 kernel.
> Here's a suggestion:
>
> I know that those builds are based on the build tags e.g. dist-f14
> etc. Sometimes some builds are made without being tagged and therefore
> cannot be caught by the build script. (the kernel package in
> particular). Is it possible to have a "rawhide" spin e.g. a spin that
> has the "very latest" packages build in rawhide _not_ based on tags?
> This will mean that if a package is in koji the script will take it
> without looking if it is tagged as update-testing or dist-XX. This is
> what I mean with the "very latest" packages. That will be a reall
> rawhide spin.
You are welcome to do so... there is a koji static repo that has the
contents of everything built currently in the tag. I don't think I want
to switch the nightlys to that, because one of the reasons for them is
for maintainers to see what packages are currently composed and would
be in a final spin if it happend then, and also with rawhide, all the
packages built push out the next day, so a 1 day change isn't that
worthwhile.
Anyhow, enjoy the composes. I hope they are helpfull.
The idea is good but I don't think that it's worthy. If I compose my
own isos then I won't depend on the nightly composes. And the fedora
infrastructure is a way better than my pc :-)
Why is this syncing done manually. If the isos are automatically build
(which I think is the case here), why cannot they be automatically
synced to the server?
4 a.m.
On 30/05/10 09:54, Joshua C. wrote:
--snip--
Can someone explain why? It's just a signle script to be run. I really
cannot understand where the problem is to build every night the isos?
More than likely the Release of F13, has brought the person (singular)
attention elsewhere.
They will probably start again, once Rawhide settles a bit.
--
Regards,
Frank Murphy
UTF_8 Encoded
Friend of Fedora
11:59 a.m.
On Sun, 30 May 2010 22:01:12 +0200
"Joshua C." <joshuacov(a)googlemail.com> wrote:
I expected this but without seeing the failed logs one can only guess.
Sorry, perhaps a 'state' file or something would be good to have.
> Out of curiosity, what do you use them for, and which spins? :)
I'm interested in the kde spin. I know that the "latest" kde code
reaches this spin not that fast but the main reason for using the
nightly composes is the ati/xserver stack. The maintainers have done a
great job in improving this video driver but it's still away from its
win**** counter part. The only way to test this and/or apply the
latest mesa patches is to have the latest rawhide code. The versions
that go with the serial distributions are outdated.
I am syncing over the new images now. Most everything composed
yesterday. ;)
Here's a suggestion:
I know that those builds are based on the build tags e.g. dist-f14
etc. Sometimes some builds are made without being tagged and therefore
cannot be caught by the build script. (the kernel package in
particular). Is it possible to have a "rawhide" spin e.g. a spin that
has the "very latest" packages build in rawhide _not_ based on tags?
This will mean that if a package is in koji the script will take it
without looking if it is tagged as update-testing or dist-XX. This is
what I mean with the "very latest" packages. That will be a reall
rawhide spin.
You are welcome to do so... there is a koji static repo that has the
contents of everything built currently in the tag. I don't think I want
to switch the nightlys to that, because one of the reasons for them is
for maintainers to see what packages are currently composed and would
be in a final spin if it happend then, and also with rawhide, all the
packages built push out the next day, so a 1 day change isn't that
worthwhile.
Anyhow, enjoy the composes. I hope they are helpfull.
kevin
3:04 p.m.
2010/5/30 Frank Murphy <frankly3d(a)gmail.com>:
On 30/05/10 15:08, Joshua C. wrote:
--snip--
>
> This is not exactly correct. It foo+1 isn't in the build system then
> the automatic script will throw out an error.
No because how will an auto script know to expect foo+1.
It will accept fooX (the borked one)
An error will only be thrown iirc, if there is no foo.
Without eyes watching.
The yum-dependences will resolve those issues.
3:01 p.m.
2010/5/30 Kevin Fenzi <kevin(a)scrye.com>:
On Sun, 30 May 2010 10:54:37 +0200
"Joshua C." <joshuacov(a)googlemail.com> wrote:
> Under http://alt.fedoraproject.org/pub/alt/nightly-composes/ are
> supposed to be the nightly-builds of the "latest" code. However, a
> quick look at the logs shows that those are build once in a week or
> even not that "often".
>
> Can someone explain why? It's just a signle script to be run. I really
> cannot understand where the problem is to build every night the isos?
I have been building them, but I haven't synced out the new images yet,
for the following reasons:
- With the release of F13, we have switched the nightly composes to use
rawhide. Most of the spins currently don't compose due to various
rawhide issues.
I expected this but without seeing the failed logs one can only guess.
- I wanted to announce that we have switched them to rawhide, but
haven't had the chance yet.
- I wanted to give maintainers of spins some time to fix issues so
there are images that compose again.
I'll probibly send out an announcement to devel-announce later today
and see what state they are in after todays compose.
Thanks
Out of curiosity, what do you use them for, and which spins? :)
I'm interested in the kde spin. I know that the "latest" kde code
reaches this spin not that fast but the main reason for using the
nightly composes is the ati/xserver stack. The maintainers have done a
great job in improving this video driver but it's still away from its
win**** counter part. The only way to test this and/or apply the
latest mesa patches is to have the latest rawhide code. The versions
that go with the serial distributions are outdated.
Here's a suggestion:
I know that those builds are based on the build tags e.g. dist-f14
etc. Sometimes some builds are made without being tagged and therefore
cannot be caught by the build script. (the kernel package in
particular). Is it possible to have a "rawhide" spin e.g. a spin that
has the "very latest" packages build in rawhide _not_ based on tags?
This will mean that if a package is in koji the script will take it
without looking if it is tagged as update-testing or dist-XX. This is
what I mean with the "very latest" packages. That will be a reall
rawhide spin.
11:33 a.m.
On Sun, 30 May 2010 10:54:37 +0200
"Joshua C." <joshuacov(a)googlemail.com> wrote:
Under http://alt.fedoraproject.org/pub/alt/nightly-composes/ are
supposed to be the nightly-builds of the "latest" code. However, a
quick look at the logs shows that those are build once in a week or
even not that "often".
Can someone explain why? It's just a signle script to be run. I really
cannot understand where the problem is to build every night the isos?
I have been building them, but I haven't synced out the new images yet,
for the following reasons:
- With the release of F13, we have switched the nightly composes to use
rawhide. Most of the spins currently don't compose due to various
rawhide issues.
- I wanted to announce that we have switched them to rawhide, but
haven't had the chance yet.
- I wanted to give maintainers of spins some time to fix issues so
there are images that compose again.
I'll probibly send out an announcement to devel-announce later today
and see what state they are in after todays compose.
Out of curiosity, what do you use them for, and which spins? :)
kevin
10:04 a.m.
On 30/05/10 15:08, Joshua C. wrote:
--snip--
This is not exactly correct. It foo+1 isn't in the build system then
the automatic script will throw out an error.
No because how will an auto script know to expect foo+1.
It will accept fooX (the borked one)
An error will only be thrown iirc, if there is no foo.
Without eyes watching.
At the end we'll see at
least a try to build the isos but this is not the case accorinding
to
the logs.
At the moment Rawhide is no longer directly installable.
Which means the only way to get it is FedoraN + updateToRawhide.
I will hazard a guess that nightlies will resume when
Rawhide gets to F14-Branched (3mths?)
--
Regards,
Frank Murphy
UTF_8 Encoded
Friend of Fedora
9:08 a.m.
2010/5/30 Frank Murphy <frankly3d(a)gmail.com>:
It's also based on tester feedback.
Package foo doesn't work.
If Package foo+1 doesn't make it into the build system for a week,
there's a weeks builds down the swanee.
That's why eyes rather than automation is used.
--
Regards,
Frank Murphy
This is not exactly correct. It foo+1 isn't in the build system then
the automatic script will throw out an error. At the end we'll see at
least a try to build the isos but this is not the case accorinding to
the logs.
4:08 a.m.
On 30/05/10 10:04, Joshua C. wrote:
--snip--
> --
I thought this is an automated process?!? I really cannot understand
why this cannot be done automatically. They've got the space, the
script and just need to re-compose the isos - which can be done with a
cron job. It's not that difficult, isn't it?
It's also based on tester feedback.
Package foo doesn't work.
If Package foo+1 doesn't make it into the build system for a week,
there's a weeks builds down the swanee.
That's why eyes rather than automation is used.
--
Regards,
Frank Murphy
UTF_8 Encoded
Friend of Fedora
4:04 a.m.
2010/5/30 Frank Murphy <frankly3d(a)gmail.com>:
On 30/05/10 09:54, Joshua C. wrote:
--snip--
>
> Can someone explain why? It's just a signle script to be run. I really
> cannot understand where the problem is to build every night the isos?
More than likely the Release of F13, has brought the person (singular)
attention elsewhere.
They will probably start again, once Rawhide settles a bit.
--
Regards,
Frank Murphy
UTF_8 Encoded
Friend of Fedora
--
I thought this is an automated process?!? I really cannot understand
why this cannot be done automatically. They've got the space, the
script and just need to re-compose the isos - which can be done with a
cron job. It's not that difficult, isn't it?
5085
days inactive
5087
days old
11 comments
3 participants
participants (3)
-
Frank Murphy -
Joshua C. -
Kevin Fenzi