unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Martin Castillo <castilma@uni-bremen.de>
To: Gottfried <gottfried@posteo.de>, help-guix@gnu.org
Subject: Re: creating a manifest
Date: Sun, 26 Mar 2023 13:36:28 +0200	[thread overview]
Message-ID: <49204610-60ec-62fb-6603-ec807ce3e34d@uni-bremen.de> (raw)
In-Reply-To: <23f6065e-7b7b-e509-3598-5a72decabf67@posteo.de>

Hi,

Am 26.03.23 um 10:16 schrieb Gottfried:

>>> please send the command you used to update the profile and the 
>>> manifest file inside the profile, i.e. 
>>> home/gfp/Projekte/Musik/guix-profil/manifest.scm
>>>
>>> Martin
> 
> This was the command I used to upgrade the profile
> (because I deleted one package: ardour
> in my main profile, so I wanted to install it in this profile)
> 
> ~$ guix package --upgrade --profile=/home/gfp/Projekte/Musik/guix-profil

Like you, I would expect that to work, but I read the info page again. 
It says about --upgrade:

   Note that this upgrades package to the latest version of packages
      found in the distribution currently installed.

And the latest version of musescore is 4.0.2, so it tries to install that.

So I guess the right command would be:

guix package -m /home/gfp/Projekte/Musik/musik.scm --profile 
/home/gfp/Projekte/Musik/guix-profil


> 
> -----------------------------------------------------------------------------
> 
> here the musik.scm:
> 

I actually meant /home/gfp/Projekte/Musik/guix-profil/manifest and not 
/home/gfp/Projekte/Musik/musik.scm, but now I don't need it anymore.

Martin


  reply	other threads:[~2023-03-26 11:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-18 10:50 creating a manifest Gottfried
2023-03-18 11:48 ` Martin Castillo
2023-03-18 12:44   ` Martin Castillo
2023-03-18 18:58   ` Gottfried
     [not found]     ` <DFF79ED1-D430-4DE9-81C9-C1B146E1B84D@uni-bremen.de>
     [not found]       ` <ddb1213e-3864-bbdc-381d-aed8f9f4ace2@posteo.de>
     [not found]         ` <400c34f4-61e4-fc2e-f826-8b6d2c37f62b@uni-bremen.de>
     [not found]           ` <726a7642-df0b-495b-4b24-ce956533cba7@posteo.de>
     [not found]             ` <81AEB7B8-17C7-4484-90B6-BFEF5163B670@uni-bremen.de>
2023-03-25 12:49               ` Gottfried
2023-03-25 22:07                 ` Martin Castillo
2023-03-26  8:16                   ` Gottfried
2023-03-26 11:36                     ` Martin Castillo [this message]
2023-03-26 13:07                       ` Gottfried
2023-03-26 18:36                         ` Martin Castillo
2023-03-27 11:52                           ` Gottfried
2023-03-27 18:06                             ` Wojtek Kosior via

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=49204610-60ec-62fb-6603-ec807ce3e34d@uni-bremen.de \
    --to=castilma@uni-bremen.de \
    --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).