Github messages for voidlinux
 help / color / mirror / Atom feed
From: chili-b <chili-b@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: frescobaldi-3.1.3
Date: Tue, 12 Oct 2021 02:23:27 +0200	[thread overview]
Message-ID: <20211012002327.jMoMPGrY0lD9_sgJl-8Zr4jsRruOGr_x8dpGFRvzlns@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33279@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 583 bytes --]

New comment by chili-b on void-packages repository

https://github.com/void-linux/void-packages/pull/33279#issuecomment-940555184

Comment:
I just tried installing frescobaldi again and it fails with:
```
error: can't copy 'linux/org.frescobaldi.Frescobaldi.desktop': doesn't exist or not a regular file
```
At the `do_install()` step. I don't think I changed anything significant in the template that would cause this. Is there anything I can do to investigate? I saw a new issue on the upstream repository which mentioned that there were issues when running under python 3.10.

  parent reply	other threads:[~2021-10-12  0:23 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-03  1:16 [PR PATCH] " chili-b
2021-10-03  5:18 ` chili-b
2021-10-03  7:24 ` [PR PATCH] [Updated] " chili-b
2021-10-03  7:29 ` chili-b
2021-10-03  7:30 ` chili-b
2021-10-03 17:45 ` [PR PATCH] [Updated] " chili-b
2021-10-03 17:50 ` chili-b
2021-10-03 17:57 ` chili-b
2021-10-03 18:02 ` chili-b
2021-10-03 18:05 ` chili-b
2021-10-03 18:08 ` chili-b
2021-10-03 18:22 ` chili-b
2021-10-04 21:38 ` chili-b
2021-10-09 15:44 ` [PR REVIEW] " NeelChotai
2021-10-09 15:44 ` NeelChotai
2021-10-09 15:44 ` NeelChotai
2021-10-09 15:44 ` NeelChotai
2021-10-10 19:26 ` [PR PATCH] [Updated] " chili-b
2021-10-10 19:27 ` chili-b
2021-10-10 19:30 ` chili-b
2021-10-10 19:34 ` chili-b
2021-10-10 19:35 ` chili-b
2021-10-10 19:36 ` [PR PATCH] [Updated] " chili-b
2021-10-10 19:37 ` chili-b
2021-10-10 19:38 ` chili-b
2021-10-10 21:57 ` chili-b
2021-10-10 22:05 ` chili-b
2021-10-10 22:28 ` chili-b
2021-10-11  9:32 ` NeelChotai
2021-10-11 15:02 ` [PR PATCH] [Updated] " chili-b
2021-10-11 22:15 ` [PR REVIEW] " paper42
2021-10-11 22:15 ` paper42
2021-10-11 22:15 ` paper42
2021-10-11 23:31 ` [PR PATCH] [Updated] " chili-b
2021-10-11 23:32 ` chili-b
2021-10-11 23:34 ` chili-b
2021-10-11 23:35 ` chili-b
2021-10-11 23:37 ` chili-b
2021-10-11 23:38 ` chili-b
2021-10-11 23:39 ` chili-b
2021-10-11 23:43 ` [PR PATCH] [Updated] " chili-b
2021-10-11 23:47 ` chili-b
2021-10-12  0:23 ` chili-b [this message]
2021-10-12  9:28 ` NeelChotai
2021-10-12  9:31 ` NeelChotai
2021-10-12 13:39 ` [PR PATCH] [Updated] " chili-b
2021-10-12 13:40 ` chili-b
2021-10-12 13:46 ` chili-b
2021-10-12 15:02 ` chili-b
2021-10-12 17:19 ` paper42
2021-11-09  1:24 ` chili-b
2021-11-09  2:15 ` [PR PATCH] [Updated] " chili-b
2021-11-09  2:23 ` chili-b
2021-11-09  2:35 ` chili-b
2021-11-09  2:46 ` chili-b
2021-11-09  2:55 ` chili-b
2021-11-09  3:02 ` chili-b
2021-11-09  3:13 ` chili-b
2021-11-09  3:39 ` chili-b
2021-11-10 18:31 ` [PR PATCH] [Updated] " chili-b
2021-11-10 19:10 ` chili-b
2021-11-10 19:24 ` chili-b
2021-11-10 22:20 ` chili-b
2022-01-17  1:06 ` chili-b
2022-01-19 22:10 ` chili-b
2022-01-20  5:11 ` chili-b
2022-02-02  9:55 ` [PR REVIEW] " ericonr
2022-02-02  9:55 ` ericonr
2022-02-02  9:55 ` ericonr
2022-02-02  9:55 ` ericonr
2022-02-03 16:03 ` chili-b
2022-02-03 16:04 ` chili-b
2022-02-03 16:21 ` chili-b
2022-02-03 16:24 ` [PR PATCH] [Updated] " chili-b
2022-02-03 19:50 ` chili-b
2022-02-03 19:50 ` chili-b
2022-03-09  5:46 ` chili-b
2022-05-22 15:13 ` [PR PATCH] [Updated] " chili-b
2022-05-22 15:18 ` [PR PATCH] [Updated] New package: frescobaldi-3.2 chili-b
2022-05-22 15:27 ` chili-b
2022-05-22 19:17 ` chili-b
2022-05-22 19:54 ` chili-b
2022-05-22 20:10 ` chili-b
2022-05-29 18:23 ` chili-b
2022-08-28  2:14 ` github-actions
2022-08-31 16:43 ` [PR PATCH] [Closed]: " cratesiosomething

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=20211012002327.jMoMPGrY0lD9_sgJl-8Zr4jsRruOGr_x8dpGFRvzlns@z \
    --to=chili-b@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).