unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: iyzsong@outlook.com
To: Roman Riabenko <roman@riabenko.com>
Cc: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>,
	54283@debbugs.gnu.org
Subject: bug#54283: eog-plugins don't shop up
Date: Sat, 12 Mar 2022 12:22:25 +0800	[thread overview]
Message-ID: <TYCP286MB1897152EB4EBD734AFBB3137A30D9@TYCP286MB1897.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <ff70ad5a3f6f2a58f7c56867b8de30ea9e3b57ac.camel@riabenko.com> (Roman Riabenko's message of "Mon, 07 Mar 2022 13:27:05 +0200")

Roman Riabenko <roman@riabenko.com> writes:

> Hello, Liliana. Thank you for looking into this.
> [...]
>
> Roman
>
> У пн, 2022-03-07 у 08:30 +0100, Liliana Marie Prikler пише:
>> Hi Roman,
>> 
>> Am Montag, dem 07.03.2022 um 07:34 +0200 schrieb Roman Riabenko:
>> > I installed eog-plugins, but they do not show up in EOG Preferences
>> > >
>> > Plugins.
>> Note that eog-plugins have the version 3.26.8, while EOG itself has
>> version 40.3 -- in other words, a mismatch.  There is to my knowledge
>> no eog-plugins release for 40.3, but there are release candidates for
>> 42.  Apart from that, it would appear that the plugin installation
>> path
>> changed from lib/ to share/, but we could add our own lib-respecting
>> plugin path to eog with a patch or snippet once we have corresponding
>> eog-plugins again.
>> [...]

Hello, Roman and Liliana, thanks for the report and explain.

I have fixed this issue in commit b769fe7f756 by symlink the plugins
directory in eog-plugins from lib/ to share/.




      reply	other threads:[~2022-03-12  4:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07  5:34 bug#54283: eog-plugins don't shop up Roman Riabenko
2022-03-07  7:30 ` Liliana Marie Prikler
2022-03-07 11:27   ` Roman Riabenko
2022-03-12  4:22     ` iyzsong [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=TYCP286MB1897152EB4EBD734AFBB3137A30D9@TYCP286MB1897.JPNP286.PROD.OUTLOOK.COM \
    --to=iyzsong@outlook.com \
    --cc=54283@debbugs.gnu.org \
    --cc=liliana.prikler@ist.tugraz.at \
    --cc=roman@riabenko.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).