Is up2date still getting any attention? This program was busted since the libssl versions went up to an .so.5 symlink to the libs. The problem is tht to get the GUI to work, I have to add a package to the exclusions list in order to be able to have the forward button highlighted for usage. I can even deselect the specific package added to the exclusion list and up2date will still work for installing packages.
Several different bugs have been opened regrding this issue. Getting the forward button to work when you select a program to be instaled from the exclusion list seems to indicate it would not be too hard to figure out why the button works when an excluded package is selected, but not if you never see the excluded package screen.
Jim
Jim Cornette wrote:
Is up2date still getting any attention?
I'd be happy if up2date just went away altogether.
I've always had problems with it not finding updates, even though it reports there are xx updates available and the little red ball is glowing nicely...
I know, I know, it's related to mirrors and who's in sync when etc.
But yum is so much more convenient... - easily added to daily/nightly cron so it's done automagically - automatically tries different mirrors as needed - simple command line entry "does it all": (as root) yum -y update
The ONLY thing up2date does that I like over yum, is up2date prompts me for the root password as needed. yum just chokes and dies, it's last words are "Help meeeeee, I'm not root..." :-)
So, su -c "yum -y up2date" and I'm back in business.
I like yum. It took me a while to start using it though... so thanks to up2date for being such a PITA, I learned a better way. :-)
The little ball is cute.... keep that. :-)
Don Russell
Don Russell wrote:
Jim Cornette wrote:
Is up2date still getting any attention?
I'd be happy if up2date just went away altogether.
I've always had problems with it not finding updates, even though it reports there are xx updates available and the little red ball is glowing nicely...
I know, I know, it's related to mirrors and who's in sync when etc.
But yum is so much more convenient... - easily added to daily/nightly cron so it's done automagically - automatically tries different mirrors as needed - simple command line entry "does it all": (as root) yum -y update
The ONLY thing up2date does that I like over yum, is up2date prompts me for the root password as needed. yum just chokes and dies, it's last words are "Help meeeeee, I'm not root..." :-)
So, su -c "yum -y up2date" and I'm back in business.
I like yum. It took me a while to start using it though... so thanks to up2date for being such a PITA, I learned a better way. :-)
The little ball is cute.... keep that. :-)
Don Russell
Not wanting to start a religious war, But though I think yum is excellent, I still prefer up2date. I find myself wanting to know "what the heck that package is" and with up2date I just highlight the package. With yum on the other hand, I do a check-update, followed by an info, followed by an update, each time I need to download .repo files look at dependencies etc. etc.
The 2 packages are about equal in finding mirrors that aren't ready :-)
Of course since either yum or up2date gets broken from time to time, I think it's nice to have both.
Scott
Scott wrote:
Don Russell wrote:
Jim Cornette wrote:
Is up2date still getting any attention?
I'd be happy if up2date just went away altogether.
I've always had problems with it not finding updates, even though it reports there are xx updates available and the little red ball is glowing nicely...
I know, I know, it's related to mirrors and who's in sync when etc.
But yum is so much more convenient... - easily added to daily/nightly cron so it's done automagically - automatically tries different mirrors as needed - simple command line entry "does it all": (as root) yum -y update
The ONLY thing up2date does that I like over yum, is up2date prompts me for the root password as needed. yum just chokes and dies, it's last words are "Help meeeeee, I'm not root..." :-)
So, su -c "yum -y up2date" and I'm back in business.
I like yum. It took me a while to start using it though... so thanks to up2date for being such a PITA, I learned a better way. :-)
The little ball is cute.... keep that. :-)
Don Russell
Not wanting to start a religious war, But though I think yum is excellent, I still prefer up2date. I find myself wanting to know "what the heck that package is" and with up2date I just highlight the package. With yum on the other hand, I do a check-update, followed by an info, followed by an update, each time I need to download .repo files look at dependencies etc. etc.
The 2 packages are about equal in finding mirrors that aren't ready :-)
Of course since either yum or up2date gets broken from time to time, I think it's nice to have both.
Scott
For yum, it would be nice if you could yum -y update and get the updates. The problem is that it had over 100 rpms that it could successfully update if it would do its best. Up2date does the same thing, so not really an up2date vs. yum issue. With a customized and manually edited script, I could get yum to do what I wanted by using the information related to what up2date was trying to install.
I use both up2date and yum for retrieving packages. Up2date is broken somewhere between displaying the excluded packages list and going onto regular rpms for selection. It has been this way with several bugs filed against it being broken. I was just wondering if it was left broken and concentration was being pushed onto pup or another update/dep resolver program.
Jim
For yum, it would be nice if you could yum -y update and get the updates. The problem is that it had over 100 rpms that it could successfully update if it would do its best. Up2date does the same thing, so not really an up2date vs. yum issue. With a customized and manually edited script, I could get yum to do what I wanted by using the information related to what up2date was trying to install.
I keep suggesting you use the yum shell and you don't seem to have tried it.
Try this, please:
yum shell
update transaction solve
<some error occurs here>
exclude package-that-causes-error update transaction solve
<no errors>
run quit
ta da!
-sv
seth vidal wrote:
For yum, it would be nice if you could yum -y update and get the updates. The problem is that it had over 100 rpms that it could successfully update if it would do its best. Up2date does the same thing, so not really an up2date vs. yum issue. With a customized and manually edited script, I could get yum to do what I wanted by using the information related to what up2date was trying to install.
I keep suggesting you use the yum shell and you don't seem to have tried it.
Try this, please:
yum shell
update transaction solve
<some error occurs here>
exclude package-that-causes-error update transaction solve
<no errors>
run quit
ta da!
-sv
I tried the shell and it did not show any conflicting programs. It installed all of the packages that were held up because of a multimedia program using an older flac library conflicted with the newer version.
The programs still works but I do not have any flac formatted files to see if they error. The DVDs still work.
Stumbling around in the shell, I got by with this transaction.
Thanks Seth. This should be a useful feature when it is further developed. The exclude package-that-causes-error below was added to a single > prompt that was returned. I figure that you would exclude k3b instead of the literal in your posting. Of coarse, I had to try the literal at the > prompt.
Jim
yum shell Setting up Yum Shell
transaction solve
--> Populating transaction set with selected packages. Please wait. --> Running transaction check
exclude package-that-causes-error
commands: clean, config, exit, groupinfo, groupinstall, grouplist, groupremove, groupupdate, info, install, list, localinstall, makecache, provides, quit, remove, repo, run, search, transaction, update
transaction
Transaction Summary ============================================================================= Install 0 Package(s) Update 0 Package(s) Remove 0 Package(s)
transaction update
transaction arg list: lists the contents of the transaction reset: reset (zero-out) the transaction solve: run the dependency solver on the transaction run: run the transaction
transaction list
Transaction Summary ============================================================================= Install 0 Package(s) Update 0 Package(s) Remove 0 Package(s)
transaction solve
--> Populating transaction set with selected packages. Please wait. --> Running transaction check
run transaction solve
--> Populating transaction set with selected packages. Please wait. --> Running transaction check
transaction
Transaction Summary ============================================================================= Install 0 Package(s) Update 0 Package(s) Remove 0 Package(s)
update
Setting up Update Process Setting up repositories development 100% |=========================| 1.1 kB 00:00 Reading repository metadata in from local files primary.xml.gz 100% |=========================| 955 kB 00:22 developmen: ################################################## 3491/3491 Added 3491 new packages, deleted 0 old in 61.94 seconds
run
============================================================================= Package Arch Version Repository Size ============================================================================= Installing: cryptsetup-luks i386 1.0-1 development 421 k replacing cryptsetup.i386 0.1-4
Updating: flac i386 1.1.2-24 development 291 k flac-devel i386 1.1.2-24 development 734 k gstreamer-plugins i386 0.8.8-5 development 1.4 M gstreamer-plugins-deve i386 0.8.8-5 development 35 k k3b i386 0.11.23-2 development 5.8 M kdemultimedia i386 6:3.4.0-2 development 6.8 M kdemultimedia-devel i386 6:3.4.0-2 development 143 k libmusicbrainz i386 2.1.1-1 development 195 k sound-juicer i386 2.10.1-1 development 346 k vorbis-tools i386 1:1.0.1-6 development 189 k
Transaction Summary ============================================================================= Install 1 Package(s) Update 10 Package(s) Remove 0 Package(s) Total download size: 16 M Is this ok [y/N]: y Downloading Packages: <snip> transaction test Finished Transaction Test Transaction Test Succeeded Running Transaction <snip> installing Removing : cryptsetup ####################### [20/22] Cleanup : libmusicbrainz ####################### [21/22] Cleanup : flac-devel ####################### [22/22]
Installed: cryptsetup-luks.i386 0:1.0-1 Updated: flac.i386 0:1.1.2-24 flac-devel.i386 0:1.1.2-24 gstreamer-plugins.i386 0:0.8.8-5 gstreamer-plugins-devel.i386 0:0.8.8-5 k3b.i386 0:0.11.23-2 kdemultimedia.i386 6:3.4.0-2 kdemultimedia-devel.i386 6:3.4.0-2 libmusicbrainz.i386 0:2.1.1-1 sound-juicer.i386 0:2.10.1-1 vorbis-tools.i386 1:1.0.1-6 Replaced: cryptsetup.i386 0:0.1-4 Finished Transaction
quit
Leaving Shell
<running yum again for test>
yum update Setting up Update Process Setting up repositories development 100% |=========================| 1.1 kB 00:00 Reading repository metadata in from local files primary.xml.gz 100% |=========================| 955 kB 00:03 developmen: ################################################## 3491/3491 Added 6 new packages, deleted 6 old in 17.10 seconds No Packages marked for Update/Obsoletion
On Thu, 2005-04-07 at 20:31 -0400, Jim Cornette wrote:
I tried the shell and it did not show any conflicting programs. It installed all of the packages that were held up because of a multimedia program using an older flac library conflicted with the newer version.
The programs still works but I do not have any flac formatted files to see if they error. The DVDs still work.
Stumbling around in the shell, I got by with this transaction.
Thanks Seth. This should be a useful feature when it is further developed. The exclude package-that-causes-error below was added to a single > prompt that was returned. I figure that you would exclude k3b instead of the literal in your posting. Of coarse, I had to try the literal at the > prompt.
My fault. the command is:
config exclude package-to-be-excluded
sorry about that.
-sv
seth vidal wrote:
On Thu, 2005-04-07 at 20:31 -0400, Jim Cornette wrote:
I tried the shell and it did not show any conflicting programs. It installed all of the packages that were held up because of a multimedia program using an older flac library conflicted with the newer version.
The programs still works but I do not have any flac formatted files to see if they error. The DVDs still work.
Stumbling around in the shell, I got by with this transaction.
Thanks Seth. This should be a useful feature when it is further developed. The exclude package-that-causes-error below was added to a single > prompt that was returned. I figure that you would exclude k3b instead of the literal in your posting. Of coarse, I had to try the literal at the > prompt.
My fault. the command is:
config exclude package-to-be-excluded
sorry about that.
-sv
No noticable damage to the system. I'll try out k3b and the other programs that were held back to see if they work as the media player does still. Thanks for lesson 1 in the usage of yum shell.
Jim
Not wanting to start a religious war, But though I think yum isexcellent, I still prefer up2date. I find myself wanting to know "what the heck that package is" and with up2date I just highlight the package. With yum on the other hand, I do a check-update, followed by an info, followed by an update, each time I need to download .repo files look at dependencies etc. etc.
yum shell
list updates info somepackage update run
all with only a single read of the repo information.
Of course since either yum or up2date gets broken from time to time,I think it's nice to have both.
broken how? The thing that most often "breaks" yum is mirrors being out of sync or the repositories being in unresolved states. Not exactly yum's fault.
-sv
Of course since either yum or up2date gets broken from time to time,I think it's nice to have both.
broken how? The thing that most often "breaks" yum is mirrors being out of sync or the repositories being in unresolved states. Not exactly yum's fault.
-sv
But it would be nice if the mirrors carried some kind of generation-number which yum checked.
But it would be nice if the mirrors carried some kind of generation-number which yum checked.
That would only tell you that the file with the generation-number had been synced. It wouldn't tell you that all of the rpms had been.
-sv
I see. So the rsyncing on the mirrors is done on the live files, there's no script trickery to only put the whole tree live when the mirror is synced?
Fair enough.
I see. So the rsyncing on the mirrors is done on the live files, there's no script trickery to only put the whole tree live when the mirror is synced?
Fair enough.
right-o. That's why the mirrors (especially rawhide) are so frequently out of sync - you try moving gigabytes of changes every night to hundreds of mirrors, see how well it does.
-sv
On Apr 6, 2005 8:54 PM, Jim Cornette fct-cornette@insight.rr.com wrote:
Is up2date still getting any attention? This program was busted since the libssl versions went up to an .so.5 symlink to the libs. The problem is tht to get the GUI to work, I have to add a package to the exclusions list in order to be able to have the forward button highlighted for usage. I can even deselect the specific package added to the exclusion list and up2date will still work for installing packages.
Several different bugs have been opened regrding this issue. Getting the forward button to work when you select a program to be instaled from the exclusion list seems to indicate it would not be too hard to figure out why the button works when an excluded package is selected, but not if you never see the excluded package screen.
Jim
-- Perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away. -- Antoine de Saint-Exupery
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-test-list
I'm having the same problem with up2date. When I tried updating packages after selecting them, I can't click the forward button because it is greyed out. Also all the packages show 0 kb and packages that are already updated still show up in the list. I tried ignoring some packages to see if it would allow me to use the forward button but it still doesn't work. Glad I'm not one of those squimsh people, I don't mind jumping into the command line to get things done. I just hope this is fixed :)
-
Don Russell -
Jim Cornette -
nodata -
Oldman -
Richard Ramson -
seth vidal