Hi,
I have seen this problem several times. conary updateall first applies
the critical updates then it quits.
Update group-gnome-dist
(gnome.rpath....@gnome:trunk/2.27.20090903-1-1[live,~!livecd] ->
gnome.rpath....@gnome:trunk/2.27.20090919-1-1[live,~!livecd])
** The update will restart itself after job 2 and continue updating
continue with update? [Y/n]
Performing critical system updates, will then restart update.
Applying update job 1 of 2:
Update conary-build:python
(foresight.rpath....@fl:2-devel/2.0.46-1-1 ->
foresight.rpath....@fl:2-devel/2.0.49-1-1)
Update conary-repository:python
(foresight.rpath....@fl:2-devel/2.0.46-1-1 ->
foresight.rpath....@fl:2-devel/2.0.49-1-1)
Update conary:config (foresight.rpath....@fl:2-devel/2.0.46-1-1 ->
foresight.rpath....@fl:2-devel/2.0.49-1-1)
Update conary:data (foresight.rpath....@fl:2-devel/2.0.46-1-1 ->
foresight.rpath....@fl:2-devel/2.0.49-1-1)
Update conary:doc (foresight.rpath....@fl:2-devel/2.0.46-1-1 ->
foresight.rpath....@fl:2-devel/2.0.49-1-1)
Update conary:runtime (foresight.rpath....@fl:2-devel/2.0.46-1-1 ->
foresight.rpath....@fl:2-devel/2.0.49-1-1)
[group-core preupdate]
[group-desktop-common preupdate]
[group-gnome-dist preupdate]
Applying update job 2 of 2:
Update conary:python (foresight.rpath....@fl:2-devel/2.0.46-1-1 ->
foresight.rpath....@fl:2-devel/2.0.49-1-1)
Critical update completed, rerunning command...
build count numbers must be allnumeric: 1[1#x86:i486:i586:i686:sse:sse2|
5#use:~!dom0:~!domU:live:~!livecd:~!vmware:~!xen]
[je...@gnome ~]$ conary q conary rmake group-gnome-dist
conary=foresight.rpath....@fl:2-devel/2.0.46-1-1
rmake=foresight.rpath....@fl:2-devel/1.0.30-1-1
group-gnome-dist=gnome.rpath....@gnome:trunk/2.27.20090903-1-1[live,~!
livecd]
-Zhang
_______________________________________________
Foresight-devel mailing list
Foresight-devel@lists.rpath.org
http://lists.rpath.org/mailman/listinfo/foresight-devel
