Salix Forums

In gslapt:

When in mark outdated packages i get a big list of packages like gthumb, thunar, perl, gtk-engines-* etc. etc. When, on the other hand i mark upgradeables packages there are none. How this?

jsfarinet wrote:In gslapt:

When in mark outdated packages i get a big list of packages like gthumb, thunar, perl, gtk-engines-* etc. etc. When, on the other hand i mark upgradeables packages there are none. How this?

What do you mean by "Outdated"? I don't see that.

When you "Update", your local cache is updated and checked from repositories. There may or may not be anything "Upgradeable".

I wonder if knome's confusion might be a translation problem?

On my machine (US English) I have, in the gslapt File menu, an item called "Mark Obsolete" (CTRL-O). (When I select it and "execute", it appears that everything that I added through Sourcery is listed to be removed. Not sure what this is doing or why they are listed, as it doesn't make sense to me to say that items added through Sourcery are "obsolete", but then I've never bothered to find out either.)

Anyway, jsfarinet, could this be the menu item/action you are talking about.

And knome, what I think jsfarinet is asking is: If there are outdated/obsolete packages, how come there are no updates/upgrades for them? Is this correct jsfarinet ?

ElderDryas wrote:. . .
And knome, what I think jsfarinet is asking is: If there are outdated/obsolete packages, how come there are no updates/upgrades for them? Is this correct jsfarinet ?

Exactly. I use ge as default language, sorry for being unprecise ...

I'm wondering why i'm told thunar e.g. is obsolete as well as all gtk-engines etc. etc. Thunar i use (and need) as well as libmurrine or alsa and i'd pretty much break my system when i'd delete them. Upgrade would be different, obviously ...

slapt-get man page wrote: --remove-obsolete
Remove installed packages that are no longer available. This
works for --dist-upgrade and --remove only. This removes pack‐
ages that are no longer available from any current package
sources, but are currently installed. Be careful as this will
also remove custom built packages.

If the package is no longer or never was available in the official Salix/Salckware repository gslapt / slapt-get will mark as obsolete,

"Be careful as this will also remove custom built packages."

This means by default all packages installed by sourcery and slapt-src will be marked for removal. Bottom line is that the "mark obsolete" option should never be used unless you want to break your system.

jsfarinet wrote:I'm wondering why i'm told thunar e.g. is obsolete as well as all gtk-engines

Not sure why Thunar would be mark as obsolete on your system. Are you sure it is the Thunar package or is it another package with Thunar in the name?

laprjns wrote:

slapt-get man page wrote: --remove-obsolete
Remove installed packages that are no longer available. This
works for --dist-upgrade and --remove only. This removes pack‐
ages that are no longer available from any current package
sources, but are currently installed. Be careful as this will
also remove custom built packages.

If the package is no longer or never was available in the official Salix/Salckware repository gslapt / slapt-get will mark as obsolete,

"Be careful as this will also remove custom built packages."

This means by default all packages installed by sourcery and slapt-src will be marked for removal. Bottom line is that the "mark obsolete" option should never be used unless you want to break your system.

jsfarinet wrote:I'm wondering why i'm told thunar e.g. is obsolete as well as all gtk-engines

Not sure why Thunar would be mark as obsolete on your system. Are you sure it is the Thunar package or is it another package with Thunar in the name?

Ok, that's a very reasonable answer. It's exactly what you said re the custom built (or installed by sourcery) packages.

As for thunar, i guess that's why i installed the thunar extensions from sourcery. Ok then, i'll forget about the remove obsolete option and never think of it anymore

Unless you messed with the repositories, there's no way Thunar is in that list. Obsolete packages include anything that is not present in the binary package repositories that gslapt sees. That includes everything you can find in sourcery.

No, i did not touch the ressources. And you're right, on the list there is not thunar itself, i didn't look enough precisely in it, but "only" the thunar extensions from sourcery (those with a _SBO extension).

ElderDryas wrote:I wonder if knome's confusion might be a translation problem?

That's very kind. Any confusion is probably due to my near obsolete and outdated brain.