Why Are Some Packaged Red and Blue?

I use OpenSUSE 12.1 64-bit with KDE and I noticed that in the Install/Remove Software GUI there are software versions which
appear in red, some in blue, while the majority are black.

What does each color mean? Sorry while I am not new to OpenSUSE, I am new to KDE and this was very different with Gnome.

Thanks in advance,

From my YaST Archive of information I find this:

  • Blue
    : There is a newer version of your installed package available. - Red
    : The package that you have installed is newer than the available version. - Black
    : The package that is installed is the same as the available version.

Thank You,

**Red **may also mean the package is orphaned, that is it has no provider in your current list of repos.

That can happen if you install a package and disable the repo
If you manually install a .rpm
If a package becomes obsolete

So James,

Is it advised to downgrade red packages to the (lower) version now available? One would assume the reason the package is now red means that at some point a newer version was available in the repo*, which got installed, and has now been rolled back in the repo because… why? Security? Bug introduced?

Or should we just ignore red packages & leave them be?

*I am assuming here that the currently installed (red) package came from the same repo that now only contains an older version, not that you installed a newer package from another repo (containing updated packages) which was subsequently removed.

I tend to roll them back - where that is appropriate

But I like to think I know what I’m doing.

What you suggest can be true, but changing repos might do it if you pull a repository from which the red displayed package was installed. Unless I have a problem I know of, I may just leave the newer or orphan application alone.

Thank You,

On 2012-03-23 07:06, weighty foe wrote:
>
> So James,
>
> Is it advised to downgrade red packages to the (lower) version now
> available? One would assume the reason the package is now red means
> that at some point a newer version was available in the repo*, which got
> installed, and has now been rolled back in the repo because… why?
> Security? Bug introduced?

You have to decide on each case.

For example, it is typical to add the vlc repo, install decss, then remove
the repo. You need decss, but it will be in red. No problem.

Some times, for unknown reasons, a package is modified, but the number goes
back, it will not be automatically updated - but you must.

Sometimes a package disappears from the repo, because it has been
superseded by another package with another name. This can be handled
automatically, but they forgot to add the necessary clauses to the rpms. So
you see it, think, decide, and remove it if appropriate.

Or you may have upgraded the distro, an operation that disables all old
repos. Maybe you do not re-add certain repo because you think you do not
need them. Later you see a red package that came from one of those removed
repos. The proper action would be to decide if the package is needed,
remove if not, or add the repo and update the package if it is needed. Or
do nothing if you feel lazy. :-p

In short: you are the administrator, you decide. >:-)


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

For example, it is typical to add the vlc repo, install decss, then remove
the repo. You need decss, but it will be in red. No problem.

Actually no. We don’t recommend the VLC (VideoLan) repo and that’s why we removed it from the Community list.
You now see the libdvdcss repo, which can remain enabled and avoid the old issues when VideoLan was used.

In short: you are the administrator, you decide. >:-)
That may be true. But the forum is here to assist those who may be unsure and we can Help them Decide

On 2012-03-23 16:26, caf4926 wrote:
>
>> For example, it is typical to add the vlc repo, install decss, then
>> remove the repo. You need decss, but it will be in red. No problem.
> Actually no. We don’t recommend the VLC (VideoLan) repo and that’s why
> we removed it from the Community list.
> You now see the libdvdcss repo, which can remain enabled and avoid the
> old issues when VideoLan was used.

I know that.

But I’m explaining a situation in which a package shows in red, and it is a
valid, although obsolete, method to do it. I’m not recommending to add the
vlc repo.

>> In short: you are the administrator, you decide. >:-)

> That may be true. But the forum is here to assist those who may be
> unsure and we can Help them Decide

Yes, we do :slight_smile:


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

It must be a language fart then.

Because you did say:

it is typical to add the vlc repo

To me that suggests we should add it.

For example: If I said

‘It’s typical for openSUSE users to hit their machines with a hammer before switching them on’

It sounds like we recommend hitting our computer with a hammer…

Hyperbole I know, to the extreme. Because anyone with common sense would ignore that advice.

On 2012-03-24 04:46, caf4926 wrote:

> Hyperbole I know, to the extreme. Because anyone with common sense
> would ignore that advice.

If you wish…


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

On 2012-03-24 04:46, caf4926 wrote:
> Because you did say: > it is typical to add the vlc repo
> To me that suggests we should add it.

You may interpret it as you wish.

If you wish, you can add the vlc repo, install only decss from it, then
remove the repo. It is (still) a perfectly valid method, like it or not.
There is a safer, easier method? Indeed, of course there is.

I was giving samples about how can a package be in red. I’m not explaining
what repos to add. That’s a different issue.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

Thanks to all the replies. That clears up the mystery!

  • Itai

Yes, thanks.

It became less enlightening but more fun in later posts :slight_smile:

I for one always start my mornings by hitting my laptop with a hammer. I find that it encourages better performance.