From: Gottfried <gottfried@posteo.de>
To: Wojtek Kosior <koszko@koszko.org>
Cc: Gary Johnson <lambdatronic@disroot.org>, help-guix@gnu.org
Subject: Re: update-profiles.sh
Date: Tue, 25 Apr 2023 15:51:30 +0000 [thread overview]
Message-ID: <02c0fd23-fb74-8815-e554-8a659e48ebad@posteo.de> (raw)
In-Reply-To: <20230424201155.35dcfbc0.koszko@koszko.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 4645 bytes --]
Hi,
thanks for help
no problem, I make constantly mistakes...
> Also, the script I prepared previously probably created some extraneous
>> profiles at the paths it was trying to use. Again, sorry if this
>> happened. You might want to remove the extra profiles you'll find.
>>
I have e.g. in the directory /home/gfp/Projekte/Emacs/
the directories:
1. emacs (8 elements: bin, etc, include, lib, libexec, sbin, share,
manifest),
2. emacs-1-link (8 elements),
3. guix-profil (8 elements: bin, etc, include, lib, libexec, sbin share,
manifest),
4. guix-profil-2-link (8 elements),
5. guix-profil-3-link (8 elements)
and 6. emacs.scm
Do you mean the directories "emacs" and "guix-profil" because they have
the same subdirectories/8 elements
are now created, like double
and I have to remove the directory "emacs",
because the directory "guix-profil" should stay?
All the different profiles (I put them in the directory "Projekte
(engl. projects)
have now always like the example above "emacs"
subdirectories: like their "different package names" and also "guix-profil".
I understood you, that now the subdirectories (with the names of the
profiles) are now according to the update script additionally created.
and I should delete those directories with the name of the profile
I hope I could express myself clearly.
....................................................................
Kind regards
Gottfried
Am 24.04.23 um 20:11 schrieb Wojtek Kosior:
>> Hi,
>> thanks for help
>>
>> I tried this script in the terminal.
>>
>> 1.
>> gfp@Tuxedo ~$ ./update-profiles.sh
>>
>> it said
>> guix package: Error: Profile /home/gfp/Projects/Calibre/calibre is
>> locked by another process
>>
>> I didn’t open calibre, so what could be the problem?
>
> Oooops, there's probably been a mistake.
>
> Looking at your emails from an older thread, it seems your profile
> paths were like "/home/gfp/Projects/Calibre/guix-profil" and
> "/home/gfp/Projects/Musik/guix-profil". Is that correct, is there
> "guix-profil" at the end of every profile path? And here, with this
> script, I erroneously assumed profile paths like
> "/home/gfp/Projects/Calibre/calibre" and
> "/home/gfp/Projects/Musik/musik". I apologize :(
>
> We need to adapt the script to use the correct profile paths. I think
> you could use something like
>
> ```
> #!/bin/sh
>
> GUIX_PROFILES=$HOME/Projekte
>
> for dir in $GUIX_PROFILES/*
> do
> name="$(basename "$dir" | tr '[:upper:]' '[:lower:]')"
> manifest="$dir"/"$name".scm
> profile="$dir"/guix-profil
> if [ -r $manifest ]
> then
> guix package --manifest="$manifest" --profile="$profile"
> fi
> done
> ```
>
> Also, the script I prepared previously probably created some extraneous
> profiles at the paths it was trying to use. Again, sorry if this
> happened. You might want to remove the extra profiles you'll find.
>
> Good luck,
> Wojtek
>
> -- (sig_start)
> website: https://koszko.org/koszko.html
> PGP: https://koszko.org/key.gpg
> fingerprint: E972 7060 E3C5 637C 8A4F 4B42 4BC5 221C 5A79 FD1A
>
> ♥ R29kIGlzIHRoZXJlIGFuZCBsb3ZlcyBtZQ== | ÷ c2luIHNlcGFyYXRlZCBtZSBmcm9tIEhpbQ==
> ✝ YnV0IEplc3VzIGRpZWQgdG8gc2F2ZSBtZQ== | ? U2hhbGwgSSBiZWNvbWUgSGlzIGZyaWVuZD8=
> -- (sig_end)
>
>
> On Mon, 24 Apr 2023 15:42:38 +0000
> Gottfried <gottfried@posteo.de> wrote:
>
>> Hi,
>> thanks for help
>>
>> I tried this script in the terminal.
>>
>> 1.
>> gfp@Tuxedo ~$ ./update-profiles.sh
>>
>> it said
>> guix package: Error: Profile /home/gfp/Projects/Calibre/calibre is
>> locked by another process
>>
>> I didn’t open calibre, so what could be the problem?
>>
>>
>> 2. it installed almost all packages from all profiles
>> without icecat, probably because I had it opened.
>>
>> 3. It did not install my "Musik" profile with several packages.
>> is locked by another process
>>
>> I am not sure about that, because I haven't opened any of those packages.
>>
>>
>> So we have success.
>> Thank you very much.
>> You saved me a lot of time and headache.
>>
>>
>> Kind regards
>>
>> Gottfried
>>
>>
>>> #!/bin/sh
>>>>
>>>> GUIX_PROFILES=$HOME/Projekte
>>>>
>>>> for dir in $GUIX_PROFILES/*
>>>> do
>>>> name=$(basename "$dir" | tr '[:upper:]' '[:lower:]')
>>>> manifest="$dir"/$name.scm
>>>> profile=$dir/$name
>>>> if [ -r $manifest ]
>>>> then
>>>> guix package --manifest="$manifest" --profile="$profile"
>>>> fi
>>>> done
>>
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3191 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2023-04-25 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 11:22 update-profiles.sh Gottfried
2023-04-24 12:05 ` update-profiles.sh Wojtek Kosior via
2023-04-24 15:42 ` update-profiles.sh Gottfried
2023-04-24 18:11 ` update-profiles.sh Wojtek Kosior via
2023-04-25 15:51 ` Gottfried [this message]
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=02c0fd23-fb74-8815-e554-8a659e48ebad@posteo.de \
--to=gottfried@posteo.de \
--cc=help-guix@gnu.org \
--cc=koszko@koszko.org \
--cc=lambdatronic@disroot.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).