A few questions about packages

A few questions about packages

[Jone]

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

Hello. Can I remove old package versions and other builds? On the example
of Icecat:

    252.1 MiB [          ]
/5ym67s5vp1vmnc3y4ds4r3687vc3nl25-icecat-52.6.0-gnu1
    252.0 MiB [          ]
/360i9ca4gnm3rsjj8v43ih0j3mfrp40n-icecat-52.6.0-gnu1
    246.8 MiB [          ]
/kd0nnq3i0qarx4vqxcampxfj3igxn84h-icecat-52.3.0-gnu1

(Or is it possible to remove a specific package, in "package-version"
format?)

And the next question, is also about Icecat: version 52.6.0 was compiled
from source. This is too long. Can I create binary package from this local
installation?

If possible, please give a couple of examples.

[-- Attachment #2: Type: text/html, Size: 752 bytes --]

Re: A few questions about packages

[Ricardo Wurmus]

Jone <yeger9@gmail.com> writes:

> Hello. Can I remove old package versions and other builds? On the example
> of Icecat:
>
>     252.1 MiB [          ]
> /5ym67s5vp1vmnc3y4ds4r3687vc3nl25-icecat-52.6.0-gnu1
>     252.0 MiB [          ]
> /360i9ca4gnm3rsjj8v43ih0j3mfrp40n-icecat-52.6.0-gnu1
>     246.8 MiB [          ]
> /kd0nnq3i0qarx4vqxcampxfj3igxn84h-icecat-52.3.0-gnu1
>
> (Or is it possible to remove a specific package, in "package-version"
> format?)

You can remove all unused packages with “guix gc”.  Individual store
items can be removed with “guix gc -d /gnu/store/…”.

“Unused” means that no profile generation refers to the item, so you may
want to delete old profile generations with “guix package -d” first.

> And the next question, is also about Icecat: version 52.6.0 was compiled
> from source. This is too long. Can I create binary package from this local
> installation?

After building it once from source you won’t have to build it again
until the dependencies to Icecat are modified.

Building Icecat does indeed take a long time.  The current version is
52.6.0-gnu1 and should be built by our build farms.  When you’re using
the latest version of Guix then you should be able to get a binary as
soon as the build farms have compiled that package.   Only if no binary
is available you will have to build it from source.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

Re: A few questions about packages

[Konrad Hinsen]

On 07/03/2018 17:09, Jone wrote:

> Hello. Can I remove old package versions and other builds? On the 
> example of Icecat:
> 
>      252.1 MiB [          ] 
> /5ym67s5vp1vmnc3y4ds4r3687vc3nl25-icecat-52.6.0-gnu1
>      252.0 MiB [          ] 
> /360i9ca4gnm3rsjj8v43ih0j3mfrp40n-icecat-52.6.0-gnu1
>      246.8 MiB [          ] 
> /kd0nnq3i0qarx4vqxcampxfj3igxn84h-icecat-52.3.0-gnu1

"guix gc" will delete all packages that are no longer required. Most 
probably that includes all Icecat installs except for the latest. 
However, if two users on the system have different versions of Icecat 
installed, both will be kept.

> And the next question, is also about Icecat: version 52.6.0 was compiled 
> from source. This is too long. Can I create binary package from this 
> local installation?

In a sense you already have one, stored on your computer. So I guess 
your question is how you can use this binary package on a different 
machine, right? There are two answers to this question:

  1) If the other machine also runs Guix, the answer is "guix archive":
 
https://www.gnu.org/software/guix/manual/guix.html#Invoking-guix-archive

  2) If the other machine does not use Guix, have look at "guix pack":
     https://www.gnu.org/software/guix/manual/guix.html#Invoking-guix-pack

Konrad.

Re: A few questions about packages

[Jone]

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

Thanks to all respondents, I thumbed through manual. All my questions
relate exclusively to 'reconfigure' and old grub menu entries, and old
system configurations.
guix gc Ok, next:

guix gc -d /gnu/store/kd0nnq3i0qarx4vqxcampxfj3igxn84h-icecat-52.3.0-gnu1
finding garbage collector roots...
guix gc: error: build failed: cannot delete path
`/gnu/store/kd0nnq3i0qarx4vqxcampxfj3igxn84h-icecat-52.3.0-gnu1' since it
is still alive

 - icecat-52.3.0-gnu1 was installed in the first (or second) system
configuration, next 'reconfigure' and 'reconfigure' and 'reconfigure'.. Or
two version of linux-libre - too there is too much :)

[-- Attachment #2: Type: text/html, Size: 712 bytes --]

Re: A few questions about packages

[Jone]

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

Solved with emacs-guix (very cool tool!):
guix-system-generations -> select to delete (d) -> execute (x) -> guix gc

[-- Attachment #2: Type: text/html, Size: 153 bytes --]

Re: A few questions about packages

[Ricardo Wurmus]

Jone <yeger9@gmail.com> writes:

> Solved with emacs-guix (very cool tool!):
> guix-system-generations -> select to delete (d) -> execute (x) -> guix gc

Without emacs-guix you need to do this manually by deleting the links for
the old system generations under /var/guix/profiles/system-*-link.

Just don’t delete the latest system generation.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

Re: A few questions about packages

[Jone]

> On 07/03/2018, Jone wrote:

> Hello. Can I remove old package versions and other builds? On the 
> example of Icecat:
> 
>      252.1 MiB [          ] 
> /5ym67s5vp1vmnc3y4ds4r3687vc3nl25-icecat-52.6.0-gnu1
>      252.0 MiB [          ] 
> /360i9ca4gnm3rsjj8v43ih0j3mfrp40n-icecat-52.6.0-gnu1
>      246.8 MiB [          ] 
> /kd0nnq3i0qarx4vqxcampxfj3igxn84h-icecat-52.3.0-gnu1

Seems I has understood not until the end of..
After running 'guix package -d && guix gc':

ls -d /gnu/store/*gtk+*/

/gnu/store/9kv6d924wcii38zwd4jbkxzlaz8hsl4z-gtk+-3.22.26/
/gnu/store/baps67ax5wj5njl7mcpg825v7wvcd1g6-gtk+-3.22.21/
/gnu/store/blxcjvmcpm4h80wmzrjh8z8hxjp6a7cj-gtk+-2.24.31/
/gnu/store/gfz7znplsbgsw2npdbz5vgfl90q222hv-gtk+-3.22.26/
/gnu/store/j74pvcwvx93fnaq3j6jj1rxzhj80bk16-gtk+-2.24.31/
/gnu/store/jwaxdxsxfd220dx5a1crcbw3nh2nnpmy-gtk+-2.24.31/
/gnu/store/kx3p64ff6pnyj2wppj78s3d41a49d4lp-gtk+-3.22.26-bin/
/gnu/store/lf7379mdvch8y1i1ds4lqblm43sfzlbf-gtk+-2.24.31/
/gnu/store/mnxrb9zgbdglhsr98h7r2skn6wv7zvsp-gtk+-2.24.31/
/gnu/store/rbzlcg13vpabvj2sr6c67icd15wq0vhz-gtk+-2.24.31/
/gnu/store/wsdqwpm22l8dgqqibzbgx5zn4bnkz0ci-gtk+-3.22.26/Can be as something optimize?
/gnu/store/z23h6jgiyv180gxvmdc8xnpaqxd2bm7k-gtk+-2.24.31/
/gnu/store/zpvxja0ajxddyxjc1lsnhz53j0ysh822-gtk+-2.24.31/

How can I verify if these paths are needed and for what purpose? Can be
as something optimize (guix gc --optimize not do anything)?

Re: A few questions about packages

[Ricardo Wurmus]

Jone <yeger9@gmail.com> writes:

>> On 07/03/2018, Jone wrote:
>
>> Hello. Can I remove old package versions and other builds? On the
>> example of Icecat:
>>
>>   252.1 MiB [ ]
>> /5ym67s5vp1vmnc3y4ds4r3687vc3nl25-icecat-52.6.0-gnu1
>>   252.0 MiB [ ]
>> /360i9ca4gnm3rsjj8v43ih0j3mfrp40n-icecat-52.6.0-gnu1
>>   246.8 MiB [ ]
>> /kd0nnq3i0qarx4vqxcampxfj3igxn84h-icecat-52.3.0-gnu1
>
> Seems I has understood not until the end of..
> After running 'guix package -d && guix gc':
>
> ls -d /gnu/store/*gtk+*/ […]

Your user’s profiles are not the only ones that can keep packages alive.
You also have a system profile with potentially multiple generations.
They are stored under /var/guix/profiles/system*

> (guix gc --optimize not do anything)

As the manual says, this is for deduplicating files in the store.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

Re: A few questions about packages

[Jone]

>Your user’s profiles are not the only ones that can keep packages
>alive.
>You also have a system profile with potentially multiple generations.
>They are stored under /var/guix/profiles/system*

This we already figured out previously in this thread :) 
And:

"Label             : GNU with Linux-Libre 4.15.7 (beta)
Prev. generation  : 0  
Current           : Yes
Number of packages: 88  Packages
File name: 
  /var/guix/profiles/system-4-link"

The question remains.

Re: A few questions about packages

[Jone]

I wrote a simple script:

	TRGT="*-gtk+-2.2*"
	for i in $(ls -d /gnu/store/$TRGT/)
	do
		echo
		echo "----------> $i"
		echo "$(guix gc --referrers $i | grep -v \.drv)"
	done

Part of output:
----------> /gnu/store/595ydgdnkj9vdxr88dkscb0ws9rgjv0g-gtk+-2.24.31/
/gnu/store/595ydgdnkj9vdxr88dkscb0ws9rgjv0g-gtk+-2.24.31
/gnu/store/6h7w5z60zqx6802qxd98wcmx1yrhnzy5-xfce4-appfinder-4.12.0
/gnu/store/8vy4gnmb17xc3hiqjd1b5z28vfsn8jzq-gtk-im-modules
/gnu/store/fi77qxlq9ga6rgl9gg1xfxkfw7vps2l3-gtk-im-modules
/gnu/store/ggrwghpwyfwrmxb90aj846c3ydwprqvl-gtk-im-modules
/gnu/store/miiv6rnlrhbjk34l1ga7v6ys1x6983q4-libxfce4ui-4.12.0
/gnu/store/rki1c8z0v7crppym7qzqys894pikxljc-garcon-0.4.0

----------> /gnu/store/blxcjvmcpm4h80wmzrjh8z8hxjp6a7cj-gtk+-2.24.31/
/gnu/store/blxcjvmcpm4h80wmzrjh8z8hxjp6a7cj-gtk+-2.24.31
/gnu/store/sd4qn7ar9a7xyahv6ywvjwa3q0jqngbs-xfce4-taskmanager-1.1.0
/gnu/store/w5ybzdmixcji3ffngqvs8kcnysr265ww-libwnck-2.30.7
/gnu/store/wpy59cvw89rq607i2qsfagavllxc0ixf-murrine-0.98.2

----------> /gnu/store/jwaxdxsxfd220dx5a1crcbw3nh2nnpmy-gtk+-2.24.31/
/gnu/store/agfcmv3vyl6s5kwg74xw3hrp76xyc6g0-gnome-themes-standard-3.22.3
/gnu/store/jwaxdxsxfd220dx5a1crcbw3nh2nnpmy-gtk+-2.24.31

----------> /gnu/store/lf7379mdvch8y1i1ds4lqblm43sfzlbf-gtk+-2.24.31/
/gnu/store/360i9ca4gnm3rsjj8v43ih0j3mfrp40n-icecat-52.6.0-gnu1
/gnu/store/bnwiazvkqspg4nwg95hs4cj4dvshi0j4-gparted-0.30.0
/gnu/store/c6qmgjl5pv94yh9j5y1i2clcvxslgs68-gtkmm-2.24.5
/gnu/store/gd5kml4ci17nblgr05k38i4w2rpn5fap-webkitgtk-2.18.6
/gnu/store/lf7379mdvch8y1i1ds4lqblm43sfzlbf-gtk+-2.24.31
/gnu/store/mm5qhds0x1vxs37gwf9kxakilawcl8iw-claws-mail-3.16.0

----------> /gnu/store/mnxrb9zgbdglhsr98h7r2skn6wv7zvsp-gtk+-2.24.31/
/gnu/store/fmhaw615y43mjrijc0wm6s5ar4xnmy9w-leafpad-0.8.18.1
/gnu/store/gq6iw1d77rbndpz7niijp636rp6kcdyc-gtk-xfce-engine-2.10.1
/gnu/store/mnxrb9zgbdglhsr98h7r2skn6wv7zvsp-gtk+-2.24.31
/gnu/store/s1klb9q9aczcgzffvn7kq6azcdf5aw3g-gtk-engines-2.20.2

----------> /gnu/store/rbzlcg13vpabvj2sr6c67icd15wq0vhz-gtk+-2.24.31/
/gnu/store/16rwx833av4k48hk2diqj87mwsc457j3-gtk-im-modules
/gnu/store/rbzlcg13vpabvj2sr6c67icd15wq0vhz-gtk+-2.24.31


It is possible to draw a conclusion, that each application refers the
SEPARATE version of library. What??? Somebody can explain it?

Re: A few questions about packages

[Björn Höfling]

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

On Tue, 13 Mar 2018 22:15:35 +0300
Jone <yeger9@gmail.com> wrote:

> I wrote a simple script:
> 
> 	TRGT="*-gtk+-2.2*"
> 	for i in $(ls -d /gnu/store/$TRGT/)
> 	do
> 		echo
> 		echo "----------> $i"
> 		echo "$(guix gc --referrers $i | grep -v \.drv)"
> 	done
> 
> Part of output:
> ----------> /gnu/store/595ydgdnkj9vdxr88dkscb0ws9rgjv0g-gtk+-2.24.31/  
> /gnu/store/595ydgdnkj9vdxr88dkscb0ws9rgjv0g-gtk+-2.24.31
> /gnu/store/6h7w5z60zqx6802qxd98wcmx1yrhnzy5-xfce4-appfinder-4.12.0
> /gnu/store/8vy4gnmb17xc3hiqjd1b5z28vfsn8jzq-gtk-im-modules
> /gnu/store/fi77qxlq9ga6rgl9gg1xfxkfw7vps2l3-gtk-im-modules
> /gnu/store/ggrwghpwyfwrmxb90aj846c3ydwprqvl-gtk-im-modules
> /gnu/store/miiv6rnlrhbjk34l1ga7v6ys1x6983q4-libxfce4ui-4.12.0
> /gnu/store/rki1c8z0v7crppym7qzqys894pikxljc-garcon-0.4.0

[..]

> ----------> /gnu/store/rbzlcg13vpabvj2sr6c67icd15wq0vhz-gtk+-2.24.31/  
> /gnu/store/16rwx833av4k48hk2diqj87mwsc457j3-gtk-im-modules
> /gnu/store/rbzlcg13vpabvj2sr6c67icd15wq0vhz-gtk+-2.24.31
> 
> 
> It is possible to draw a conclusion, that each application refers the
> SEPARATE version of library. What??? Somebody can explain it?

I also have a lot of those in my store, although I rarely do a guix gc.

Suppose you don't change anything on a packages definition, i.e.
leave name, version, depencencies, build-system etc. completely as they
were. If you then change anything on the dependencies of that package
(or its sub-dependencies) it will get rebuild (or re-downloaded) with
the same package-name and package-version but under a different
hash-sum.

That's the reason why there is the branch of "core-updates" packages
(see point 7 in [1]): Basicly every package in the distribution depends
on a core-updates package. If you change one of the core-updates, the
whole distribution needs to be rebuilt. Because this would cause much
compilation-work on users computers, core-updates will be collected and
compiled by Hydra on a separate branch. If everything is compiled and
under a certain level of errors, it will be merged back into master and
will be available via guix pull.

In your case it could be that you have installed the different library
instances via different guix pulls.

Björn

[1]
https://www.gnu.org/software/guix/manual/guix.html#Submitting-Patches




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: A few questions about packages

[Jone]

And, I seem I begin to understand!
After deleting the previous profiles does not occur "relink" to current
version of library: what has already been established, that will also
remain. Correctly?

Re: A few questions about packages

[Ricardo Wurmus]

Jone <yeger9@gmail.com> writes:

> And, I seem I begin to understand!
> After deleting the previous profiles does not occur "relink" to current
> version of library: what has already been established, that will also
> remain. Correctly?

All profile generations are immutable and stateless.  They won’t change
when you install a new library.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

Re: A few questions about packages

[Jone]

Thanks, Ricardo.

Then still questions:
the difference in a hash is already enough to read two identical
libraries as two different versions? Whether are available dependences
of one package for another?

Need wiki, not only Manual! :)

Re: A few questions about packages

[Adonay Felipe Nogueira]

> Need wiki, not only Manual! :)

Awesome idea! Although I have been experiencing some bad moments with
wikis nowadays, specially since I don't have stable connection to the
Internet, that said, I must note that: manual is like a wiki, with added
benefit that:

a) manual is readable offline, while wiki needs internet;

b) wiki pages might *not* correspond to the version of your local copy
   of the software;

c) both wiki and manual allow contributions, but manual doesn't dictate
   that one has to do so through a web browser, you can even do so by
   sharing files through thumb drives, emails, forum posts,
   NNTP/netnews, whatever;

d) you don't have to have an account in any website to suggest
   contributions to current manual, you can send it to any member of
   project in any means of communication and transfer that the member has
   available.

In any case, both manuals and wikis allow contributions. If there is
something that needs change, then perhaps someone needs to send a patch
to improve the manual.

I hope this helps clarify things. :D

-- 
- https://libreplanet.org/wiki/User:Adfeno
- Palestrante e consultor sobre /software/ livre (não confundir com
  gratis).
- "WhatsApp"? Ele não é livre. Por favor, veja formas de se comunicar
  instantaneamente comigo no endereço abaixo.
- Contato: https://libreplanet.org/wiki/User:Adfeno#vCard
- Arquivos comuns aceitos (apenas sem DRM): Corel Draw, Microsoft
  Office, MP3, MP4, WMA, WMV.
- Arquivos comuns aceitos e enviados: CSV, GNU Dia, GNU Emacs Org, GNU
  GIMP, Inkscape SVG, JPG, LibreOffice (padrão ODF), OGG, OPUS, PDF
  (apenas sem DRM), PNG, TXT, WEBM.

Re: A few questions about packages

[Björn Höfling]

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

On Tue, 13 Mar 2018 22:36:37 +0300
Jone <yeger9@gmail.com> wrote:

> And, I seem I begin to understand!
> After deleting the previous profiles does not occur "relink" to
> current version of library: what has already been established, that
> will also remain. Correctly?

Store items are kept indefinitely. You can use guix gc to remove them.
But this of cause works only if they have zero references pointing to
them, i.e. there is no other dependency from the store or a profile
generation linking to it.

I'm not sure if I understood you fully, I hope my answer is the right
one to your question. Since a week or so we decided to invite people
also to write in their language and not only in English. If that helps
you, under "Mailing List" you will find the list of languages that are
understood by Guix developers (to be growing):

https://www.gnu.org/software/guix/contact/

Björn

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: A few questions about packages

[Jone]

Björn wrote:

> I'm not sure if I understood you fully, I hope my answer is the right
> one to your question.

But I understood you.

> Since a week or so we decided to invite people
> also to write in their language and not only in English.

Languages there is, but there is whether people..

Re: A few questions about packages

[Björn Höfling]

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

On Wed, 14 Mar 2018 01:48:15 +0300
Jone <yeger9@gmail.com> wrote:

> Björn wrote:
> 
> > I'm not sure if I understood you fully, I hope my answer is the
> > right one to your question.  
> 
> But I understood you.

OK, then it's fine :-)

 
> > Since a week or so we decided to invite people
> > also to write in their language and not only in English.  
> 
> Languages there is, but there is whether people..

Yes, for each language listed, there is one person within the
Guix group who speaks that language at a good level.

Björn


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: A few questions about packages

[Jone]

Another question.. Package zip refers to "compression" package source.
Can I not specify individual packages, but install all of this group?
Can I do this with a single command? (This is a general question, not
just about zip).

Re: A few questions about packages

[Ludovic Courtès]

Hello,

Jone <yeger9@gmail.com> skribis:

> Another question.. Package zip refers to "compression" package source.
> Can I not specify individual packages, but install all of this group?
> Can I do this with a single command? (This is a general question, not
> just about zip).

There’s no direct way to do that, but you could always do:

  guix package -i $(guix package -A | grep 'compression\.scm' | cut -f1)

HTH,
Ludo’.