AuthorTopic: updates to 5.9 (Read 8113 times)

OK. now I understand all the errors. You CANNOT have just patches. There are always dependencies into packages and extra. What you tried cannot and will not work. I'm putting it in rather strong terms not to be harsh to you but for the benefit of other users who may read this thread. To do upgrades you MUST have packages and extra enabled. There is no reason to ever disable those repositories.

Oh...I see...but.. all that I originally updated with just patches...browsers, abi & plugins seemed to be fine I thought it was done. just the ones I listed cased an issue...which made me wonder.. why..so why is there a patches in the first place...why not just put them in packages and extras with the rest.. it is impossible to see the patches list with packages and extras loaded so what is the point? just curious

AS MENTIONED ALWAYS LOAD PACKAGES, EXTRAS AND PATCHES

edit...2 steps forward 15 steps back...this install is totalled...I will have to reinstall...someday

You asked why the repositories work the way they do. Here is the logic (and it does make sense):

Packages -- contents of the original Standard iso only, nothing else ever Maintaining this is critical to allow you to go back to a known, good build.

Extra -- anything made available not in packages. This includes original builds of extra packages. If an extra package is updated it replaces the prior version, which goes into extra/old.

Patches -- upgrades to items in packages -only-

The other issue is that a patched or upgraded version of a program may have new dependencies that the original version did not have. Those dependencies can include a library from packages, an updated version of the same found in patches, or an entirely new package found in extra.

You most certainly can see all of the above at once in gslapt. All of those should be enabled by default. The fact that patches wasn''t enabled by default in 5.9 was a bug. It's fixed in 6.0.

yes...that does make sence and yes you can see all in gslapt...the error was not reloading packages and extras before clicking install...looking at the patches only list allowed me to see what patches were tested and available..

the system is not a total loss the browsers seem to work fine ...abiword seems to have taken over as default for text..gimp about posts the new version number..

I just get a packagetool error if I attempt to install now...not that I need to do any more of that..haha..for example I added packages and extras and patches and attempted to install abiword extras..it downloaded and then gave the packagetool error. this issue occured when I added one of the patches likely that required a dependency. I do not know which one..perhaps a reinstall is best and a LONG way back to this blissfull customization...dang....what a maroon...what an ignoranamus...

the error is "packagetools returned an error"...I can uninstall at will...abiword was bugging me as text files open with it so I uninstalled it but when I chose to reinstall it downloads then a message pops up..packagetools returned an error...I uninstalled pkgtools thinking it was corrupted and..ya I know..

I've had to resort to manually fixing packagetools in the past, but had no guidance. Needless to say, it took a lot of extracting, searching, and copying/moving to get it to finally work. I think that uelsk8s post should make it into the HOWTO section (HOWTO: Easily fix broken packagetools). It would have saved me lots of time and been more complete than my manual method

If this button were enabled and clicked would it check all the patches?

If clicked a second time would it UNcheck all the patches?

If patches were checked, with ONLY packages, extras, patches loaded would clicking "execute" update the system?

could a pop up be added to mark all updates?when clicked a pop up with OK button would appear

WARNING: marking all updates: DO NOT execute unless ONLY packages, extras, patches are loaded as source via edit/ preferances/sources.

DAMAGE WILL OCCUR otherwise.

To unmark all updates click OK then click the markall updates button again.

CHECK YOU SOURCES.

OK

If packages,extras and patches were checked by default then the only mishap would be for those with added sources and the warning would be a good reminder...if this is possible even if patches were not loaded by default it would warn one to do so. and make updates much simplier for novice users like myself

I agree that we need the "mark all updates" button back. It was the easiest way to check what was new. Currently, you cannot tell obsolete (updated) packages from new ones (which makes for a veeeery long list to read).

« Last Edit: October 29, 2008, 01:27:42 pm by Joe1962 »

Logged

O'Neill (RE the Asgard): "Usually they ask nicely before they ignore us and do what they damn well please."http://joe1962.bigbox.infoRunning: VL 7 Std 64 + self-cooked XFCE-4.10

I had no idea Mark All Updates was back in VL6. I can't wait to try it!

I'm one of those who *really* wanted it back. As others have said, it's very difficult to tell what's new without Mark All Updates. I'm not into wholesale updating "just because it's there," but I do want security updates at the very least.--GrannyGeek