Try again :-)
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva(a){redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva(a){lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
Well, I haven't gotten anything since Sep 19th.
----
[root@ip68-12-228-23 up2date]# up2date --show-channel
redhat-linux-severn-i386-9.0.93
redhat-linux-severn-i386-9.0.93-updates
[root@ip68-12-228-23 up2date]# up2date --nosig -u
Fetching package list for channel: redhat-linux-severn-i386-9.0.93...
########################################
Fetching package list for channel:
redhat-linux-severn-i386-9.0.93-updates...
########################################
Fetching Obsoletes list for channel: redhat-linux-severn-i386-9.0.93...
Fetching Obsoletes list for channel:
redhat-linux-severn-i386-9.0.93-updates...
Fetching rpm headers...
All packages are currently up to date
----
Output of rpm -qa attached.
The base channel has been populated (try updating to the
fedora-release package from the second test release and
then running up2date.)
There's no updates channel for the second test release yet.
Bill
Why up2date is not updating beta packages from rawhide, like on severn1
beta channel?
Regards,
Thiago
Em Ter, 2003-09-30 às 12:11, Bill Nottingham escreveu:
Louis Garcia (louisg00(a)bellsouth.net) said:
> Rawhide has not synced since the 23.
Yup, fixed.
> Also, since the fedora name change is rawhide still being called
> rawhide?
For now, yes.
Bill
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
http://www.redhat.com/mailman/listinfo/fedora-test-list
I don't understand why you have a severn-beta2 channel (with just what is on
the cdroms) and plan a separate updates channel (with cdroms plus updates as
they appear) ... or did I misunderstand your statement?
--
Gene
On Tuesday 30 September 2003 16:13, Elliot Lee wrote:
>The updates channel is in the works.
I don't understand why you have a severn-beta2 channel (with just what is on
the cdroms) and plan a separate updates channel (with cdroms plus updates as
they appear) ... or did I misunderstand your statement?
perhaps for the --update-to-release feature of up2date. Although why you
would want to update to the base release and then go get the updates is
still a question. Just a thought though.