Bug 787149 – media-gfx/flameshot-0.9.0 - file collision with app-shells/zsh-completions-0.32.0

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Toralf Förster 2021-04-30 13:27:47 UTC]

 * Press Ctrl-C to Stop
 * 
 * app-shells/zsh-completions-0.32.0:0::gentoo
 * 	/usr/share/zsh/site-functions/_flameshot
 * 
 * Package 'media-gfx/flameshot-0.9.0' NOT merged due to file collisions.

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

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.1_desktop_plasma-20210420-165442

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

gcc-config -l:
 [1] x86_64-pc-linux-gnu-7.3.1
 [2] x86_64-pc-linux-gnu-11.1.0 *
clang version 12.0.0
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/lib/llvm/12/bin
/usr/lib/llvm/12
12.0.0
Python 3.8.9
Available Ruby profiles:
  [1]   ruby26 (with Rubygems)
  [2]   ruby30 (with Rubygems) *
Available Rust versions:
  [1]   rust-bin-1.51.0
  [2]   rust-1.51.0 *
The Glorious Glasgow Haskell Compilation System, version 8.10.4

  timestamp(s) of HEAD at this tinderbox image:
/var/db/repos/gentoo	Fri Apr 30 11:35:14 UTC 2021

emerge -qpvO media-gfx/flameshot
[ebuild     U ] media-gfx/flameshot-0.9.0 [0.6.0]

[Comment 1 Toralf Förster 2021-04-30 13:27:48 UTC]

Created attachment 704514 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2021-04-30 13:27:50 UTC]

Created attachment 704517 [details]
CMakeCache.txt

[Comment 3 Toralf Förster 2021-04-30 13:27:51 UTC]

Created attachment 704520 [details]
emerge-history.txt

[Comment 4 Toralf Förster 2021-04-30 13:27:53 UTC]

Created attachment 704523 [details]
etc.portage.tar.bz2

[Comment 5 Toralf Förster 2021-04-30 13:27:54 UTC]

Created attachment 704526 [details]
logs.tar.bz2

[Comment 6 Toralf Förster 2021-04-30 13:27:56 UTC]

Created attachment 704529 [details]
media-gfx:flameshot-0.9.0:20210430-115654.log

[Comment 7 Pavel Kalugin 2021-05-03 09:47:03 UTC]

Probably an app-shells/zsh-completions problem, because in commit https://github.com/zsh-users/zsh-completions/commit/2e009c7ab8e9c7496ed86473ede0917a3cefee01 the completion was removed.
Unfortunately, latest zsh-completions release was Sep 20, 2020 i.e. 9 days before the fix. I've submitted the issue asking for a release (https://github.com/zsh-users/zsh-completions/issues/801). Should I do anything else?

[Comment 8 Pavel Kalugin 2021-05-03 09:48:53 UTC]

Is there a maintainer of zsh-completions? I didn't find one.

[Comment 9 Joonas Niilola 2021-05-03 13:03:09 UTC]

It is indeed maintainer-needed. I'd appreciate if you made a PR for zsh-completions fixing this, as it's maintainer-needed you can do that.

There are many ways to fix this:

1: revbump zsh-completions-0.32.0 to 0.32.0-r1 while keeping stable KEYWORDS, and then just rm the flameshot completion either in src_prepare or src_install (I'd do it in src_prepare).

Then we can drop the older version, 0.31.0 too, in a separate commit.

2: package a snapshot of zsh-completions per upstream, look here for an example:
https://gitweb.gentoo.org/repo/gentoo.git/tree/media-libs/rlottie/rlottie-0.2_p20210405.ebuild

3: Just define a blocker between flameshot and zsh-completion, however that seems a bit excessive and redundant.

Well here are the steps to fix, to whoever is willing. Let me know if you're not up for it, and I'll do it at some point.

[Comment 10 Pavel Kalugin 2021-05-03 17:41:32 UTC]

I was lucky and a new release of zsh-completions was published. I will try to update the ebuild now.

[Comment 11 Pavel Kalugin 2021-05-19 20:41:59 UTC]

zsh-completions was bumped to 0.33.0. The issue is fixed in the new version.