PDA

View Full Version : Package Support Levels



mikewillis
12-Sep-2011, 14:06
Whilst many packages have support levels (described at 'SUSE Linux
Enterprise Desktop Supported Packages'
(http://support.novell.com/products/desktop/supported_packages/) )
listed for them, many packages have no support level listed. For
example

Code:
--------------------
$ zypper info pidgin | grep '^Support Level'
Support Level: unknown
--------------------

Can anyone enlighten me as to what this means in practice?

I'm also curious as to how it is decided what Support Level a package
is given. What's the logic in the pidgin package having a no support
level whilst pidgin-sipe is Level 3 and pidgin-otr is Level 2? What is
about kmines ("...the classical Minesweeper game where you have to find
mines by logical deduction") that merits Level 3 support?


What got me wondering about this is someone in my organisation pointing
at Secunia advisories from late August relating to pidgin which say you
should update to 2.10.0 and asking me how this affects our Linux
machines. Given that pidgin is included in SLED my initial reaction was
that any updates Novell deem necessary will appear in the Updates
channel. However the version of pidgin included in SLED 11 SP1 is 2.6.6
and last updated in December. Which suggests that maybe Novell aren't
hugely interested in keeping it up to date. I'm wondering if 'Support
Level: unknown' is intended to reflect this.


I would ask Novell directly about this but for reasons unknown that one
of my colleagues is trying to figure out, we haven't been able to raise
Service Requests for the last week or so.


--
mikewillis
------------------------------------------------------------------------
mikewillis's Profile: http://forums.novell.com/member.php?userid=7510
View this thread: http://forums.novell.com/showthread.php?t=444559

Automatic Reply
16-Sep-2011, 17:38
mikewillis,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team
http://forums.novell.com/

malcolmlewis
16-Sep-2011, 18:04
On Mon, 12 Sep 2011 13:06:04 GMT
mikewillis <mikewillis@no-mx.forums.novell.com> wrote:

>
> Whilst many packages have support levels (described at 'SUSE Linux
> Enterprise Desktop Supported Packages'
> (http://support.novell.com/products/desktop/supported_packages/) )
> listed for them, many packages have no support level listed. For
> example
>
> Code:
> --------------------
> $ zypper info pidgin | grep '^Support Level'
> Support Level: unknown
> --------------------
>
> Can anyone enlighten me as to what this means in practice?
>
> I'm also curious as to how it is decided what Support Level a package
> is given. What's the logic in the pidgin package having a no support
> level whilst pidgin-sipe is Level 3 and pidgin-otr is Level 2? What is
> about kmines ("...the classical Minesweeper game where you have to
> find mines by logical deduction") that merits Level 3 support?
>
>
> What got me wondering about this is someone in my organisation
> pointing at Secunia advisories from late August relating to pidgin
> which say you should update to 2.10.0 and asking me how this affects
> our Linux machines. Given that pidgin is included in SLED my initial
> reaction was that any updates Novell deem necessary will appear in
> the Updates channel. However the version of pidgin included in SLED
> 11 SP1 is 2.6.6 and last updated in December. Which suggests that
> maybe Novell aren't hugely interested in keeping it up to date. I'm
> wondering if 'Support Level: unknown' is intended to reflect this.
>
>
> I would ask Novell directly about this but for reasons unknown that
> one of my colleagues is trying to figure out, we haven't been able to
> raise Service Requests for the last week or so.
>
>
Hi Mike
Do you still need info on this?

--
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.4 (x86_64) Kernel 2.6.37.6-0.7-desktop
up 3 days 20:05, 4 users, load average: 0.24, 0.15, 0.21
GPU GeForce 8600 GTS Silent - Driver Version: 280.13

mikewillis
16-Sep-2011, 19:16
Yeah, I guess. As of late today it looks like I can raise Service
Requests again, but the info might be of interest to others too.


--
mikewillis
------------------------------------------------------------------------
mikewillis's Profile: http://forums.novell.com/member.php?userid=7510
View this thread: http://forums.novell.com/showthread.php?t=444559

malcolmlewis
17-Sep-2011, 02:02
On Fri, 16 Sep 2011 18:16:02 GMT
mikewillis <mikewillis@no-mx.forums.novell.com> wrote:

>
> Yeah, I guess. As of late today it looks like I can raise Service
> Requests again, but the info might be of interest to others too.
>
>
Hi
It looks like repository priorities and repository numbers...

If you change the SLE SDK priorities to 100 and re-check.

--
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.4 (x86_64) Kernel 2.6.37.6-0.7-desktop
up 4 days 4:00, 4 users, load average: 0.18, 0.13, 0.14
GPU GeForce 8600 GTS Silent - Driver Version: 280.13

paulparker
18-Sep-2011, 08:06
Code:
--------------------

localhost:/home/paulparker # zypper se pidgin
Refreshing service 'nu_novell_com'.
Loading repository data...
Reading installed packages...

S | Name | Summary | Type
--+-------------------------------+---------------------------------+-----------
i | nautilus-sendto-plugin-pidgin | Pidgin plugin for nautilus-se-> | package
i | pidgin | GTK+-Based Multiprotocol Inst-> | package
| pidgin | GTK+-Based Multiprotocol Inst-> | srcpackage
i | pidgin-otr | "Off The Record" end-to-end e-> | package
| pidgin-otr | "Off The Record" end-to-end e-> | srcpackage
i | pidgin-sipe | Pidgin plugin for connecting -> | package
| pidgin-sipe | Pidgin plugin for connecting -> | srcpackage
i | sledsp1-pidgin-sipe | Recommended update for pidgin-> | patch
localhost:/home/paulparker # zypper info nautilus-sendto-plugin-pidgin | grep '^Support Level'
Support Level: Level 3
localhost:/home/paulparker # zypper info pidgin | grep '^Support Level'Support Level: Level 3
localhost:/home/paulparker # zypper info pidgin-otr | grep '^Support Level'
Support Level: Level 2
localhost:/home/paulparker # zypper info pidgin-sipe | grep '^Support Level'Support Level: Level 3
localhost:/home/paulparker # zypper info sledsp1-pidgin-sipe | grep '^Support Level'
localhost:/home/paulparker #

--------------------

mikewillis
19-Sep-2011, 13:36
malcolmlewis;2138254 Wrote:
>
> It looks like repository priorities and repository numbers...
>
> If you change the SLE SDK priorities to 100 and re-check.
>


Code:
--------------------
$ zypper info pidgin | grep '^Support Level'
Support Level: unknown
$ zypper info pidgin | grep '^Repository'
Repository: sle11sdksp1
--------------------

On my machine that repo apparently takes precedence over all others.

Code:
--------------------
$ # zypper lr -P
# | Alias | Name | Enabled | Refresh | Priority
---+-----------------------------+-----------------------------+---------+---------+---------
1 | sle11sdksp1 | sle11sdksp1 | Yes | No | 50
2 | sle11sdksp1_updates | sle11sdksp1_updates | Yes | No | 50
3 | sle11sdksp1_updates_testing | sle11sdksp1_updates_testing | Yes | No | 50
4 | sled11_extras | sled11_extras | Yes | No | 50
5 | sled11_extras_testing | sled11_extras_testing | Yes | No | 50
6 | sled11sp1 | sled11sp1 | Yes | No | 50
7 | sled11sp1_updates | sled11sp1_updates | Yes | No
(and so on)

--------------------

It looks like the priority of repos with the same Priority number is
decided by an alphanumeric sort of their name.

I changed the Priority number of the sled11sp1 repo to something lower
than 50 and now I get

Code:
--------------------

$ zypper info pidgin | grep '^Support Level'
Support Level: Level 3
$ zypper info pidgin | grep '^Repository'
Repository: sled11sp1

--------------------

I find this interesting. Firstly it's made me realise that the
Repository line in the output of 'zypper info' does not indicate which
repository the packages was installed from. I thought it did, though I
can't recall how I came to believe that.

Secondly, it doesn't even necessarily tell you about the package you
have installed. The pidgin package I actually have installed isn't in
the sled11sp1, it's in sled11sp1_updates.

Thirdly, I had assumed that the Support Level was information contained
in the package somehow, though I'd been unable to work out how. That it
is determined by which ever repo 'zypper info' happens to find a package
by that name in would seem to make it somewhat less useful that perhaps
it ought be. I haven't changed which pidgin package I have installed,
but by altering a number in a .repo I can make alter what level of
support 'zypper info' says applies to it. The pidgin package in the SLED
updates repo and the SLE SDK updates repo are identical (same md5sum) so
that zypper can report than as having different support levels is rather
unhelpful.


--
mikewillis
------------------------------------------------------------------------
mikewillis's Profile: http://forums.novell.com/member.php?userid=7510
View this thread: http://forums.novell.com/showthread.php?t=444559