FS#70398 - [ruby-bundler] file conflict with ruby package

Attached to Project: Community Packages
Opened by M. Greyson Christoforo (greyltc) - Saturday, 10 April 2021, 14:55 GMT
Last edited by Anatol Pomozov (anatolik) - Tuesday, 13 April 2021, 19:16 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Anatol Pomozov (anatolik)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 34
Private No

Details

ruby-bundler: /usr/share/man/man5/gemfile.5.gz exists in filesystem (owned by ruby)
This task depends upon

Closed by  Anatol Pomozov (anatolik)
Tuesday, 13 April 2021, 19:16 GMT
Reason for closing:  Fixed
Additional comments about closing:  2.2.16-3
Comment by Kr1ss X (Kr1ss) - Saturday, 10 April 2021, 16:58 GMT
Note that this bug applies to `ruby-bundler-2.2.16-1`.

Looks that it will be resolved once `ruby-3.0.1-1` which currently is in [testing]) hits [extra].

Ref: https://github.com/archlinux/svntogit-packages/commit/bacd85913db1edd442716f90e18736ee0fc31da1#diff-37538beb61ff63edebbf735dfcf39e5d732f49183d6beb097169d971875ca422L60
Comment by Dirk Möbius (dmoebius) - Sunday, 11 April 2021, 08:45 GMT
Workaround: sudo rm /usr/share/man/man5/gemfile.5.gz
Comment by Peter Himmelman (arch-arch-arch) - Monday, 12 April 2021, 16:37 GMT
Just did the basic workaround suggested by Dirk. It updated just fine. Not exactly certain as to the ramifications from removing said gemfile though.
Comment by Kr1ss X (Kr1ss) - Monday, 12 April 2021, 16:40 GMT
> Not exactly certain as to the ramifications from removing said gemfile though.

The workaround removes a manual page (i.e. documentation), not some gemfile.
Comment by BrLi (brli) - Monday, 12 April 2021, 16:42 GMT
even if 3.0.1 fix this issue, IIRC you should still push a quick pkgrel+1 package of the 2.2.16 to fix this in stable repos, or current broken status has hit people.

BTW, rm isn't quick solution, you should probably using --overwrite argument from pacman -S
Comment by Peter Himmelman (arch-arch-arch) - Monday, 12 April 2021, 16:48 GMT
Makes sense Kr1ss. That's what I figured as the file is nested in a man directory.

And good point BrLi, I didn't realize there was even an overwrite flag for pacman. Good to know.
Comment by Doug Newgard (Scimmia) - Monday, 12 April 2021, 16:54 GMT
Do NOT use --overwrite or rm the file! You end up with pacman thinking that two packages own the same file and will end up removing the file completely when it gets fixed.
Comment by Bryan L. Gay (linuxninja) - Tuesday, 13 April 2021, 08:38 GMT
One or the other package, either ruby or ruby-bundler, is broken. They both currently claim to own the same file.
I opened a bug on the extra repo, before I found this one. I think ruby-bundler is to blame since it is the package that just updated to cause this issue.
Comment by Anatol Pomozov (anatolik) - Tuesday, 13 April 2021, 17:02 GMT
@felixonmars I would like to move forward with this bug, are you ok if I take care of fixing it?
Comment by Anatol Pomozov (anatolik) - Tuesday, 13 April 2021, 17:42 GMT
the original issue happened when ruby-bundler was bumped while a large ruby rebuild was going on in testing.

ruby-bundler 2.2.16-3 has worked around it and there should not be any file conflict now.
Comment by Kr1ss X (Kr1ss) - Tuesday, 13 April 2021, 17:48 GMT
Yep. Thanks Anatol !
Comment by Felix Yan (felixonmars) - Tuesday, 13 April 2021, 18:00 GMT
@anatolik Sure. Thanks for taking care of it and sorry for the slow response.

Loading...