From: Csepp <raingloom@riseup.net>
To: Gottfried <gottfried@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: installing of two versions of package Musescore
Date: Mon, 19 Dec 2022 14:55:13 +0100 [thread overview]
Message-ID: <87v8m7o5qv.fsf@riseup.net> (raw)
In-Reply-To: <89e84b0b-0e63-01c7-9d44-2e6e3fd30641@posteo.de>
Gottfried <gottfried@posteo.de> writes:
> [[PGP Signed Part:Undecided]]
> Hi Guix,
>
> I tried to download the new version of Musescore, Version 4
> Even thought 100 % available, it wanted to build it locally, but
> failed. (takes 75 minutes)
> I tried it again, it failed.
> next day I tried it again, it failed.
>
> I checked the Musescore Forum etc
> and there are big problems with the new Musescore 4 in Linux.
> Several people complained.
>
> How can I now keep the Version 3.6.2
> and additionally install the new version 4.0 in future,
> so that my current version 3.6.2 does not get lost.
>
> The new version 4.0 needs improvements.
>
>
> Kind regards
>
> Gottfried
>
> [2. OpenPGP public key --- application/pgp-keys; OpenPGP_0x61FAF349C9FB7F94.asc]...
>
> [[End of PGP Signed Part]]
You could pass --do-not-upgrade=musescore if you want to keep it at the
same version in your main profile.
In general you do not need to install packages under development in your
main profile. It would be better to either put it in a separate profile
or use a temporary shell every time and put the package definition in a
manifest or script.
next prev parent reply other threads:[~2022-12-19 14:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 8:23 installing of two versions of package Musescore Gottfried
2022-12-19 13:55 ` Csepp [this message]
2022-12-19 14:19 ` Gottfried
2022-12-20 17:02 ` Csepp
2022-12-21 13:17 ` Gottfried
2022-12-21 18:06 ` Csepp
2022-12-22 13:21 ` Gottfried
2022-12-22 14:47 ` Csepp
2022-12-21 18:53 ` Wojtek Kosior via
2022-12-24 14:08 ` Gottfried
2022-12-26 18:33 ` Wojtek Kosior via
2022-12-27 11:30 ` Csepp
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=87v8m7o5qv.fsf@riseup.net \
--to=raingloom@riseup.net \
--cc=gottfried@posteo.de \
--cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).