From: loreb <loreb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: mnemosyne-2.10.1
Date: Mon, 04 Sep 2023 17:20:49 +0200 [thread overview]
Message-ID: <20230904152049.Nx0TdARJPNBL4Fc1fuTKp7frACIicxvRWrAH62zOuq4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40063@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2055 bytes --]
New comment by loreb on void-packages repository
https://github.com/void-linux/void-packages/pull/40063#issuecomment-1705439664
Comment:
It used to work... applying
```
diff --git a/srcpkgs/python3-gtts/template b/srcpkgs/python3-gtts/template
index c46e4335..a959073c 100644
--- a/srcpkgs/python3-gtts/template
+++ b/srcpkgs/python3-gtts/template
@@ -17,7 +17,7 @@ pre_install() {
#dist/gTTS-2.3.2-py3-none-any.whl
for i in dist/gTTS-*.whl ; do
test -e "$i" || continue
- cp -f "$i" "${i,,}" # lowercase
+ mv -f "$i" "${i,,}" # lowercase
done
}
post_install() {
```
fixed the issue for me, but then at the end I get
```
=> mnemosyne-2.9_1: running post_build ...
make: 'build' is up to date.
./pyuic5 main_wdgt.ui > ui_main_wdgt.py
env: ‘python\r’: No such file or directory
env: use -[v]S to pass options in shebang lines
make: *** [makefile:28: ui_main_wdgt.py] Error 127
=> ERROR: mnemosyne-2.9_1: post_build: 'make default' exited with 2
=> ERROR: in post_build() at srcpkgs/mnemosyne/template:22
=> ERROR: mnemosyne-2.9_1: post_build: '( cd mnemosyne/pyqt_ui && make default )' exited with 1
=> ERROR: in post_build() at srcpkgs/mnemosyne/template:22
```
Apparently masterdir/builddir/mnemosyne-2.9/mnemosyne/pyqt_ui/pyuic5 has a carriage return in its shabang (fixed upstream, but there's also a new release, it's now pyuic6)
Fix that and it now complains (it used to work I swear!!!) that
```
./pyuic5 add_cards_dlg.ui > ui_add_cards_dlg.py
Traceback (most recent call last):
File "/builddir/mnemosyne-2.9/mnemosyne/pyqt_ui/./pyuic5", line 15, in <module>
from PyQt5 import QtCore
ModuleNotFoundError: No module named 'PyQt5'
```
The newer release uses PyQt6, so anything we do to fix that (nothing difficult, every time I try to build a new tiny patch/dependency is needed) will have to be discarded when we upgrade - it says above you tried 2.10, did anything go wrong? I still have hostdir/binpkgs/mnemosyne/mnemosyne-2.10.1_1.x86_64-musl.xbps, why downgrading to 2.9?
next prev parent reply other threads:[~2023-09-04 15:20 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 21:44 [PR PATCH] [WIP] New package: mnemosyne-2.9 Eloitor
2022-10-20 21:46 ` [PR PATCH] [Updated] " Eloitor
2022-10-20 22:13 ` Eloitor
2022-10-20 22:24 ` Eloitor
2022-10-20 23:31 ` classabbyamp
2022-10-20 23:32 ` classabbyamp
2022-10-21 13:02 ` [PR PATCH] [Updated] " Eloitor
2023-03-30 1:56 ` github-actions
2023-03-30 10:25 ` Eloitor
2023-05-26 11:10 ` [PR PATCH] [Updated] " Eloitor
2023-05-26 12:35 ` [PR PATCH] [Updated] [WIP] New package: mnemosyne-2.10.1 Eloitor
2023-05-26 12:50 ` Eloitor
2023-05-26 12:53 ` Eloitor
2023-05-26 12:55 ` Eloitor
2023-05-26 12:58 ` Eloitor
2023-06-14 16:21 ` loreb
2023-06-15 15:27 ` loreb
2023-08-29 13:02 ` loreb
2023-09-02 17:33 ` [PR PATCH] [Updated] " Eloitor
2023-09-02 18:06 ` Eloitor
2023-09-02 18:32 ` Eloitor
2023-09-02 18:33 ` Eloitor
2023-09-02 18:37 ` [PR PATCH] [Updated] " Eloitor
2023-09-04 15:20 ` loreb [this message]
2023-09-04 22:27 ` Eloitor
2023-09-05 13:57 ` [PR REVIEW] " loreb
2023-09-05 13:59 ` loreb
2023-09-05 14:33 ` [PR PATCH] [Updated] " Eloitor
2023-09-05 14:41 ` Eloitor
2023-09-05 14:41 ` Eloitor
2023-09-05 15:25 ` loreb
2023-09-05 16:55 ` Eloitor
2023-09-06 5:35 ` Eloitor
2023-09-06 5:51 ` Eloitor
2023-09-06 9:02 ` [PR PATCH] [Updated] " Eloitor
2023-09-06 9:05 ` Eloitor
2023-09-06 13:10 ` loreb
2023-09-06 17:04 ` [PR PATCH] [Updated] " Eloitor
2023-09-06 17:28 ` Eloitor
2023-09-06 17:41 ` Eloitor
2023-09-06 17:47 ` Eloitor
2023-09-06 18:02 ` Eloitor
2023-09-06 18:07 ` Eloitor
2023-09-07 12:32 ` loreb
2023-09-07 15:26 ` [PR PATCH] [Updated] " Eloitor
2023-09-07 15:28 ` Eloitor
2023-09-07 15:45 ` Eloitor
2023-09-07 15:51 ` Eloitor
2023-09-07 16:04 ` [PR PATCH] [Updated] " Eloitor
2023-09-07 16:08 ` Eloitor
2023-09-07 16:12 ` Eloitor
2023-09-07 16:19 ` Eloitor
2023-09-08 14:25 ` loreb
2023-09-08 15:56 ` [PR PATCH] [Updated] " Eloitor
2023-09-08 15:56 ` Eloitor
2023-12-08 1:46 ` github-actions
2023-12-09 16:12 ` loreb
2024-02-14 7:47 ` [PR PATCH] [Updated] " Eloitor
2024-02-14 8:02 ` [PR PATCH] [Updated] New package: mnemosyne-2.11 Eloitor
2024-02-14 8:03 ` Eloitor
2024-05-15 1:48 ` github-actions
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230904152049.Nx0TdARJPNBL4Fc1fuTKp7frACIicxvRWrAH62zOuq4@z \
--to=loreb@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).