Update problems

For awhile now I’ve had problems with the following:

openSUSE-2012-565- kdeenlive: align mlt dependencies with packman
openSUSE-2012-588- KDE: 4.8.5 stable update
openSUSE-2012-751- update for libqt4

Any attempt to ‘Apply’ in Apper yields:

patch:openSUSE-2012-588-1.noarch conflicts with kdeartwork4-
wallpapers.noarch < 4.8.5-2.4.1 provided by kdeartwork4-
wallpapers-4.8.4-186.1.noarch<br>patch:openSUSE-2012-565-1.noarch conflicts
with libmlt4.i586 < 0.7.8-2.4.1 provided by
libmlt4-0.7.6-1.8.i586<br>patch:openSUSE-2012-751-1.noarch conflicts with
libqt4-devel-doc-data.noarch < 4.8.1-2.4.2 provided by libqt4-devel-doc-
data-4.8.0-247.2.noarch

zypper lr -d below:

1 | nvidia | nvidia | Yes
| Yes | 99 | rpm-md | ftp://download.nvidia.com/opensuse/12.2/
|
2 | openSUSE-12.2-1.6 | openSUSE-12.2-1.6 | No
| No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ata-
TSSTcorpCD_DVDW_SH-W162L |
3 | packman-essentials | packman-essentials | Yes
| Yes | 99 | rpm-md |
http://packman.inode.at/suse/openSUSE_12.2/Essentials/ |
4 | packman-multimedia | packman-multimedia | Yes
| Yes | 99 | rpm-md |
http://packman.inode.at/suse/openSUSE_12.2/Multimedia/ |
5 | repo-debug | openSUSE-12.2-Debug | No
| Yes | 99 | NONE |
http://download.opensuse.org/debug/distribution/12.2/repo/oss/ |
6 | repo-debug-update | openSUSE-12.2-Update-Debug | No
| Yes | 99 | NONE |
http://download.opensuse.org/debug/update/12.2/ |
7 | repo-debug-update-non-oss | openSUSE-12.2-Update-Debug-Non-Oss | No
| Yes | 99 | NONE |
http://download.opensuse.org/debug/update/12.2-non-oss/ |
8 | repo-non-oss | openSUSE-12.2-Non-Oss | Yes
| Yes | 99 | yast2 |
http://download.opensuse.org/distribution/12.2/repo/non-oss/ |
9 | repo-oss | openSUSE-12.2-Oss | Yes
| Yes | 99 | yast2 |
http://download.opensuse.org/distribution/12.2/repo/oss/ |
10 | repo-source | openSUSE-12.2-Source | No
| Yes | 99 | NONE |
http://download.opensuse.org/source/distribution/12.2/repo/oss/ |
11 | repo-update | openSUSE-12.2-Update | Yes
| Yes | 99 | rpm-md | http://download.opensuse.org/update/12.2/
|
12 | repo-update-non-oss | openSUSE-12.2-Update-Non-Oss | Yes
| Yes | 99 | rpm-md | http://download.opensuse.org/update/12.2-
non-oss/

On 2012-11-16 19:38, GofBorg wrote:
> zypper lr -d below:

Unreadable.
Please use code tags. Advanced editor, ‘#’ button.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))

> Advanced editor, ‘#’ button.

I don’t know what this means. I am posting via NNTP.
Here is my best effort at cleaning it up.

<code>
1 |nvidia | nvidia Yes| Yes| 99|rpm-md | ftp://download.nvidia.com/opensuse/12.2/
2 | openSUSE-12.2-1.6| openSUSE-12.2-1.6 | No| No|99|yast2| cd:///?devices=/dev/disk/by-id/ata-TSSTcorpCD_DVDW_SH-W162L
3 | packman-essentials| packman-essentials | Yes| Yes|99| rpm-md | http://packman.inode.at/suse/openSUSE_12.2/Essentials/
4 | packman-multimedia| packman-multimedia| Yes| Yes|99| rpm-md | http://packman.inode.at/suse/openSUSE_12.2/Multimedia/
5 | repo-debug| openSUSE-12.2-Debug| No| Yes|99| NONE | http://download.opensuse.org/debug/distribution/12.2/repo/oss/
6 | repo-debug-update | openSUSE-12.2-Update-Debug| No | Yes |99 | NONE | http://download.opensuse.org/debug/update/12.2/
7 | repo-debug-update-non-oss|openSUSE-12.2-Update-Debug-Non-Oss|No|Yes|99|NONE|http://download.opensuse.org/debug/update/12.2-
non-oss/
8 | repo-non-oss| openSUSE-12.2-Non-Oss| Yes | Yes|99|yast2| http://download.opensuse.org/distribution/12.2/repo/non-oss/
9 | repo-oss| openSUSE-12.2-Oss| Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/12.2/repo/oss/
10 | repo-source| openSUSE-12.2-Source | No| Yes|99| NONE| http://download.opensuse.org/source/distribution/12.2/repo/oss/
11 | repo-update | openSUSE-12.2-Update | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/12.2/
12 | repo-update-non-oss | openSUSE-12.2-Update-Non-Oss| Yes| Yes |99 |rpm-md | http://download.opensuse.org/update/12.2-non-oss/
</code>

On 2012-11-16 20:09, GofBorg wrote:
>> Advanced editor, ‘#’ button.
>
> I don’t know what this means. I am posting via NNTP.

Me too.

Then use open square bracket, CODE, close bracket. At the end, same
thing with a ‘/’ before the code word. Like this:


code inside.

Here is my best effort at cleaning it up.

It is wrapped, difficult to read. Look how I do it:


> minas-tirith:~ # zypper lr --details
> #  | Alias                              | Name                                        | Enabled | Refresh | Priority | Type   | URI                                                                                                      | Service
> ---+------------------------------------+---------------------------------------------+---------+---------+----------+--------+----------------------------------------------------------------------------------------------------------+--------
>  1 | Ext_Packman                        | Packman Repository                          | Yes     | Yes     |  120     | rpm-md | http://packman.mirrors.skynet.be/pub/packman/suse/11.4/                                                  |
>  2 | Ext_google-talkplugin              | Google Talk Plugin                          | Yes     | Yes     |  110     | rpm-md | http://dl.google.com/linux/talkplugin/rpm/stable/x86_64                                                  |
>  3 | Ext_libdvdcss                      | libdvdcss repository                        | Yes     | Yes     |  120     | rpm-md | http://opensuse-guide.org/repo/11.4/
....

You have to use a fixed width font and make sure your editor does not wrap.

I’ll have to edit yours.



> 1 |nvidia                           | nvidia                               Yes| Yes|99| rpm-md | ftp://download.nvidia.com/opensuse/12.2/
> 2 | openSUSE-12.2-1.6               | openSUSE-12.2-1.6                  | No | No |99| yast2| cd:///?devices=/dev/disk/by-id/ata-TSSTcorpCD_DVDW_SH-W162L
> 3 | packman-essentials              | packman-essentials                 | Yes| Yes|99| rpm-md | http://packman.inode.at/suse/openSUSE_12.2/Essentials/
> 4 | packman-multimedia              | packman-multimedia                 | Yes| Yes|99| rpm-md | http://packman.inode.at/suse/openSUSE_12.2/Multimedia/
> 5 | repo-debug                      | openSUSE-12.2-Debug                | No | Yes|99| NONE   | http://download.opensuse.org/debug/distribution/12.2/repo/oss/
> 6 | repo-debug-update               | openSUSE-12.2-Update-Debug         | No | Yes|99| NONE   | http://download.opensuse.org/debug/update/12.2/
> 7 | repo-debug-update-non-oss       | openSUSE-12.2-Update-Debug-Non-Oss | No | Yes|99| NONE   |http://download.opensuse.org/debug/update/12.2- non-oss/
> 8 | repo-non-oss                    | openSUSE-12.2-Non-Oss              | Yes| Yes|99| yast2  | http://download.opensuse.org/distribution/12.2/repo/non-oss/
> 9 | repo-oss                        | openSUSE-12.2-Oss                  | Yes| Yes|99| yast2  | http://download.opensuse.org/distribution/12.2/repo/oss/
> 10 | repo-source                    | openSUSE-12.2-Source               | No | Yes|99| NONE   | http://download.opensuse.org/source/distribution/12.2/repo/oss/
> 11 | repo-update                    | openSUSE-12.2-Update               | Yes| Yes|99| rpm-md | http://download.opensuse.org/update/12.2/
> 12 | repo-update-non-oss            | openSUSE-12.2-Update-Non-Oss       | Yes| Yes|99|rpm-md  | http://download.opensuse.org/update/12.2-non-oss/

Your repo list looks fine to me. Maybe I would set packman priorities
different. I don’t see you have any extra repo, like for kde.

I would just use plain Yast Online Update module to apply patches, and
see what happens. I’m not familiar with apper to try solve its nuances.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))

Don’t use Apper is my recommend

Do this on repos 3 and 4
https://dl.dropbox.com/u/10573557/Switcher%20Pics/11.4_packman_switch.png

From here on only use

zypper up

On 11/16/2012 07:48 PM, Carlos E. R. wrote:
> Please use code tags.

he is using nntp.


dd

On 11/16/2012 07:38 PM, GofBorg wrote:
> Any attempt to ‘Apply’ in Apper yields:

what happens if you don’t use Apper and instead

  1. reset the update repo to a higher priority, like say 95 (you can do
    that easily in YaST Software Repositories…)

  2. then launch YaST Online Update

some of ‘they’ say apper works great in 12.2; other ‘they’ say to use
apper only as a signal that you should run either YaST or zypper (but
never actually use apper to install/uninstall anything); other ‘they’
say to disable or uninstall apper!

you be the judge or what is best for you!! if you disable or uninstall
it then it will be up to you to run YaST Online Update or ‘zypper patch’
occasionally (weekly, daily or ???)…

[note the developing ‘they’ are discussing if apper will be included in
12.3, or not…stay tuned]


dd

On 2012-11-17 09:15, dd wrote:
> On 11/16/2012 07:48 PM, Carlos E. R. wrote:
>> Please use code tags.
>
> he is using nntp.

So are we :slight_smile:
And I use code tags.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))

Done like this

[noparse]

 output text here

[/noparse]

On 11/17/2012 01:26 PM, Knurpht wrote:
> Done like this

looks like this: http://susepaste.org/76028734


dd

I didn’t have those conflicts. I haven’t installed “openSUSE-2012-565 - kdeenlive: align mlt dependencies with packman” and I don’t have kdenlive installed.

Re “openSUSE-2012-751 - update for libqt4”, note libqt4-devel-doc-data is not installed here. The patch installed without intervention.

Re “openSUSE-2012-588 - KDE: 4.8.5 stable update”, installed without intervention, and now have kdeartwork4-wallpapers-4.8.5-2.4.1.noarch.

Enabled repos: same as yours, except no nvidia repo and no cd: repo ; all still with default priorities, but normally I raise packman (i.e. lower its number).

> [note the developing ‘they’ are discussing if apper will be included in
> 12.3, or not…stay tuned]

Well, I hope they don’t give up on it just because it has teething problems.
I set the repo to 95, and the ran YaST OU. I got a load of red carnage about
packages that needed to be changed around. I wholesale accepted the changes
since it appeared the packages that were causing issues were out of date. It
is running now.

> zypper up

Well the issue I was having with zypper was it would give me a long list of
‘packages that will not be upgraded’ followed by ‘nothing to do’.

That happens, particualrly if you have switched on a repo. Eg Packman. Which is exactly the behaviour you want.

Thanks dd,

YOU has sorted out whatever was going on with the updates.

Or was it the repo priority change that sorted it out? Did you try with apper after the priority change? I guess not.

>> YOU has sorted out whatever was going on with the updates.
> Or was it the repo priority change that sorted it out? Did you try with
> apper after the priority change? I guess not.

No, sorry did not try that.