Tumbleweed -- zypper dup --> libwayland-egl error

Hello everyone

I did a zypper dup and I have an astonishing 4000 packages to be upgraded …

There is an error


Retrieving package libwayland-egl1-12.0.2-586.2.x86_64                                          (2004/4010), 102.5 KiB (  7.9 KiB unpacked)
Retrieving: libwayland-egl1-12.0.2-586.2.x86_64.rpm ................................................................................[error]
File './x86_64/libwayland-egl1-12.0.2-586.2.x86_64.rpm' not found on medium 'http://download.opensuse.org/repositories/home:boombatower:tum
bleweed++/openSUSE_Tumbleweed/'                                                                                                            

**Abort, retry, ignore? [a/r/i/? shows all options] (a): **a
Problem occured during or after installation or removal of packages:
Installation aborted by user 

Does anyone have the same error?

Thanks

I did try “ignore” and immediately showed up another error:


Retrieving: Mesa-libglapi0-12.0.2-586.2.x86_64.rpm .................................................................................[error]
File './x86_64/Mesa-libglapi0-12.0.2-586.2.x86_64.rpm' not found on medium 'http://download.opensuse.org/repositories/home:boombatower:tumb
leweed++/openSUSE_Tumbleweed/' 
                 
**Abort, retry, ignore? [a/r/i/? shows all options] (a): **a
Problem occured during or after installation or removal of packages:
Installation aborted by user                                                                                                                
Please see the above error message for a hint.

I will not update until error free …

Do you have a special reason for using this personal repository:

home:boombatower:tumbleweed++/openSUSE_Tumbleweed/

I think that you must expect to have problems with mixed repositories and Tumbleweed. You shoul probably use “zypper up” or perhaps “zypper dup --no-allow-vendor-change” if you need to mix repositories.

And I’m sure you need

zypper dup --no-allow-vendor-change

.

The main problem here though is that the repo metadata cache is outdated.
The packages in that repo have been updated meanwhile, the mentioned packages (that zypper tries to download) do not exist any more.

So run “zypper ref -f” to make sure the repos are refreshed.
And check that you have auto-refresh enabled for that particular repo.

zypper lr -d

Although, as has been suggested already, it may be a good idea to just remove that repo, if you have no particular reason to use it.

2000+ packages yesterday, but only using TW repo. No dup problems. Just a 30 second hang before x.org starts now.

There has been a gcc update, which means that basically all packages had to be rebuilt too.

Just a 30 second hang before x.org starts now.

May be a problem with ntp:
https://forums.opensuse.org/showthread.php/519844-ntp-problem-after-snapshot-20160905
And you replied in that thread anyway.
But what does anything of that have to do with the topic of this thread? :stuck_out_tongue:

Thanks everyone for your help

I tried to find which package uses boombatower repo and I am lost …

Nonetheless, I tried zypper dup and after 4157 packages upgraded, my system is awesome
Then I did the no-vendor-change


sudo zypper dup --no-allow-vendor-change
[sudo] password for root:  
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you c
ontinue. See 'man zypper' for more information about this command.
Loading repository data...
Reading installed packages...
Computing distribution upgrade...

The following 2 NEW packages are going to be installed:
  pam_kwallet socat

The following package is going to be upgraded:
  hardinfo

1 package to upgrade, 2 new.
Overall download size: 482.3 KiB. Already cached: 0 B. After the operation, additional 712.5 KiB will be used.
**Continue? [y/n/? shows all options] (y): ** 
Retrieving package hardinfo-0.5.1-13.134.x86_64                                                       (1/3), 242.8 KiB (456.1 KiB unpacked)
Retrieving: hardinfo-0.5.1-13.134.x86_64.rpm ..........................................................................[done (112.2 KiB/s)]
Retrieving package socat-1.7.3.1-2.5.x86_64                                                           (2/3), 214.2 KiB (637.4 KiB unpacked)
Retrieving: socat-1.7.3.1-2.5.x86_64.rpm ............................................................................................[done]
Retrieving package pam_kwallet-0.0.1git.1458558182.57d15b4-33.5.x86_64                                (3/3),  25.2 KiB ( 75.1 KiB unpacked)
Retrieving: pam_kwallet-0.0.1git.1458558182.57d15b4-33.5.x86_64.rpm .................................................................[done]
Checking for file conflicts: ........................................................................................................[done]
(1/3) Installing: hardinfo-0.5.1-13.134.x86_64 ......................................................................................[done]
(2/3) Installing: socat-1.7.3.1-2.5.x86_64 ..........................................................................................[done]
(3/3) Installing: pam_kwallet-0.0.1git.1458558182.57d15b4-33.5.x86_64 ...............................................................[done]
Additional rpm output:
Try `pam-config --help' or `pam-config --usage' for more information.


There are some running programs that might use files deleted by recent upgrade. You may wish to check and restart some of them. Run 'zypper
 ps -s' to list these programs.


I did have the nntp issue but I follow the recomendation to remove nntpd and problem solve!

We can consider this post close!

It’s not a package that uses it.

You added that repo to your system (probably without Auto-Refresh), and now zypper dup tries to install packages from there.
The reason is that zypper dup doesn’t normally care from which repo a package comes from, it only takes the highest version.
–no-allow-vendor change “fixed” that by preventing zypper dup to change packages to that repo.

You should still remove the repo though if you have no particular reason to use it.
And if you do want to use it, you should better turn on Auto-Refresh for it.

I did have the nntp issue but I follow the recomendation to remove nntpd and problem solve!

You mean ntp I suppose. nntp is something completely different, and you likely do not have an nntpd installed… :wink: