Bug #3125
File conflicts during upgrade caused by name change: webkit2gtk-4.1 (new) vs. webkit2gtk (old)
0%
Description
The above issue is breaking system upgrades due to identically-named files in the filesystem.
error: failed to commit transaction (conflicting files) webkit2gtk-4.1: /usr/share/gtk-doc/html/jsc-glib-4.0/JSCClass.html exists in filesystem (owned by webkit2gtk) webkit2gtk-4.1: /usr/share/gtk-doc/html/jsc-glib-4.0/JSCContext.html exists in filesystem (owned by webkit2gtk) webkit2gtk-4.1: /usr/share/gtk-doc/html/jsc-glib-4.0/JSCException.html exists in filesystem (owned by webkit2gtk) webkit2gtk-4.1: /usr/share/gtk-doc/html/jsc-glib-4.0/JSCValue.html exists in filesystem (owned by webkit2gtk) webkit2gtk-4.1: /usr/share/gtk-doc/html/jsc-glib-4.0/JSCVirtualMachine.html exists in filesystem (owned by webkit2gtk) webkit2gtk-4.1: /usr/share/gtk-doc/html/jsc-glib-4.0/JSCWeakValue.html exists in filesystem (owned by webkit2gtk) webkit2gtk-4.1: /usr/share/gtk-doc/html/jsc-glib-4.0/annotation-glossary.html exists in filesystem (owned by webkit2gtk) webkit2gtk-4.1: /usr/share/gtk-doc/html/jsc-glib-4.0/ch01.html exists in filesystem (owned by webkit2gtk) webkit2gtk-4.1: /usr/share/gtk-doc/html/jsc-glib-4.0/home.png exists in filesystem (owned by webkit2gtk) webkit2gtk-4.1: /usr/share/gtk-doc/html/jsc-glib-4.0/index-all.html exists in filesystem (owned by webkit2gtk) webkit2gtk-4.1: /usr/share/gtk-doc/html/jsc-glib-4.0/index.html exists in filesystem (owned by webkit2gtk) webkit2gtk-4.1: /usr/share/gtk-doc/html/jsc-glib-4.0/jsc-glib-4.0-JSCOptions.html exists in filesystem (owned by webkit2gtk) webkit2gtk-4.1: /usr/share/gtk-doc/html/jsc-glib-4.0/jsc-glib-4.0-JSCVersion.html exists in filesystem (owned by webkit2gtk) webkit2gtk-4.1: /usr/share/gtk-doc/html/jsc-glib-4.0/jsc-glib-4.0.devhelp2 exists in filesystem (owned by webkit2gtk) webkit2gtk-4.1: /usr/share/gtk-doc/html/jsc-glib-4.0/left-insensitive.png exists in filesystem (owned by webkit2gtk) webkit2gtk-4.1: /usr/share/gtk-doc/html/jsc-glib-4.0/left.png exists in filesystem (owned by webkit2gtk) [...]
The dependency tree goes back to the marco window-manager, for which there is no upgrade. But I have to ask; why introduce this naming change with a version-name in the package itself (similar to D*bian/*buntu), as a number of other packages would undoubtedly also be affected.
pacman -R webkit2gtk checking dependencies... error: failed to prepare transaction (could not satisfy dependencies) :: removing webkit2gtk breaks dependency 'webkit2gtk>=2.6.0' required by atril :: removing webkit2gtk breaks dependency 'webkit2gtk' required by midori :: removing webkit2gtk breaks dependency 'webkit2gtk' required by yelp :: removing webkit2gtk breaks dependency 'webkit2gtk' required by zenity
pacman -R webkit2gtk atril midori yelp zenity checking dependencies... error: failed to prepare transaction (could not satisfy dependencies) :: removing zenity breaks dependency 'zenity' required by marco :: removing yelp breaks dependency 'yelp' required by mate-user-guide
pacman -S marco warning: marco-1.26.0-1 is up to date -- reinstalling resolving dependencies... looking for conflicting packages... Packages (1) marco-1.26.0-1 Total Installed Size: 6.35 MiB Net Upgrade Size: 0.00 MiB :: Proceed with installation? [Y/n] ^C Interrupt signal received
History
Updated by Drag0nFly over 1 year ago
This is caused by the “yelp” package. So a fix is to simply remove this helpless victim, although a more permanent solution would be better...
Updated by bill-auger over 1 year ago
- Status changed from unconfirmed to confirmed
i suspect that the important factor is 'nonprism/webkit3gtk' - webkit3gtk was not renamed - webkit2gtk-4.1 is a new package, specifically to support the 'yelp' package - the reason for the conflict is that there is no nonprism/webkit2gtk-4.1 - that package would need to be created, along with upgrading 'nonprism/webkit3gtk' -
Updated by Drag0nFly over 1 year ago
Ack. All that introduced messyness just for one package – seems quite absurd, but thanks for the comment. :)
Updated by bill-auger over 1 year ago
that is normal practice - the alternatives are more intrusive (drop the dependent package (eg: yelp) or to hold back all other dependents
it is an inconvenience; but some packages are much worse - for example 'your-freedom' must conflict with multiple versions of electron, so your-freedom must be rebuilt routinely, to recognize the constantly rotating package names - they are currently: electron, electron10, electron11, electron12, electron13, electron14, electron15 - i just replaced electron9 with electron15 today