From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 39717@debbugs.gnu.org
Subject: [bug#39717] [PATCH 1/3] gnu: delft-icon-theme: Use the copy-build-system.
Date: Thu, 27 Feb 2020 14:44:45 +0100 [thread overview]
Message-ID: <b50a5c21c5db04d0b9160db2b6ebdbcba50a4114.camel@student.tugraz.at> (raw)
In-Reply-To: <875zfs6ubq.fsf@ambrevar.xyz>
Am Donnerstag, den 27.02.2020, 14:19 +0100 schrieb Pierre Neidhardt:
> Can you detail what does not work? Which file, what error message?
$ find `guix build --source delft-icon-theme` -xtype l
This returns a list of broken symlinks. On any of them, install-file
fails with "file not found".
> In my opinion, the install-plan should be able to install any file,
> symlink or not. Failing to do so seems like a bug to me.
I think I agree with you. Instead of simply doing (copy-file file
dest), we'd have to check for symlinks as is done in copy-recursively.
Now that I have a more complete understanding of this bug, I'll try to
come up with a patch.
Regards,
Leo
next prev parent reply other threads:[~2020-02-27 13:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 16:32 [bug#39717] [PATCH 1/3] gnu: delft-icon-theme: Use the copy-build-system Leo Prikler
2020-02-21 16:32 ` [bug#39716] [PATCH 2/3] gnu: gnome-shell-extension-appindicator: " Leo Prikler
2020-02-27 10:31 ` Pierre Neidhardt
2020-02-21 16:32 ` [bug#39715] [PATCH 3/3] gnu: gnome-shell-extension-noannoyance: " Leo Prikler
2020-02-27 10:34 ` Pierre Neidhardt
2020-02-27 10:27 ` [bug#39717] [PATCH 1/3] gnu: delft-icon-theme: " Pierre Neidhardt
2020-02-27 10:52 ` Leo Prikler
2020-02-27 13:19 ` Pierre Neidhardt
2020-02-27 13:44 ` Leo Prikler [this message]
2020-02-27 14:02 ` Pierre Neidhardt
2020-02-27 14:49 ` Leo Prikler
2020-02-28 8:40 ` Pierre Neidhardt
2020-02-27 10:52 ` Leo Prikler
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=b50a5c21c5db04d0b9160db2b6ebdbcba50a4114.camel@student.tugraz.at \
--to=leo.prikler@student.tugraz.at \
--cc=39717@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
/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).