Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#75399 - [meld] meld doesn't start when started from within a virtural environment

Attached to Project: Arch Linux
Opened by stephanos (spapanik21) - Friday, 22 July 2022, 14:58 GMT
Last edited by Toolybird (Toolybird) - Sunday, 24 July 2022, 00:42 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

When trying to start meld from inside a venv, I get the following error:

```
venv:(undine)$ ~/programming/piper/undine
stephanos@sanji $ meld
Traceback (most recent call last):
File "/usr/bin/meld", line 97, in <module>
import meld.conf # noqa: E402
ModuleNotFoundError: No module named 'meld'
```

Outside the venv, it starts normally

Additional info:
* package version(s): extra/meld 3.21.2-1
* link to upstream bug report, if any: https://gitlab.gnome.org/GNOME/meld/-/issues/692

Steps to reproduce:
1. enter a venv
2. start meld
This task depends upon

Closed by  Toolybird (Toolybird)
Sunday, 24 July 2022, 00:42 GMT
Reason for closing:  Upstream
Comment by Doug Newgard (Scimmia) - Friday, 22 July 2022, 15:22 GMT
So you're overriding the system python, then are surprised when python things don't work?
Comment by stephanos (spapanik21) - Sunday, 24 July 2022, 00:36 GMT
  • Field changed: Percent Complete (100% → 0%)
The reason that I request a re-open is four-fold:
1. it used to work in all previous version since at least 2015 that I moved to arch
2. GNOME has marked as a bug indeed
3. for a python dev like me it's kind of important to diff on the same terminal
4. many other tools work like that, eg the black package
Comment by Toolybird (Toolybird) - Sunday, 24 July 2022, 00:41 GMT
Any way you look at this, it is clearly an upstream bug. This kind of scenario is pretty well covered here [1]. Please monitor the upstream issue and let us know if/when a fix becomes available. I'll add the PM to the notifications list (just in case).

[1] https://wiki.archlinux.org/title/Bug_reporting_guidelines#Upstream_or_Arch?

Loading...