[gentoo-user] question about binhost's

[gentoo-user] question about binhost's

[Michael Mair-Keimberger]

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

Hi list,

I was setting up an binhost recently and i couldn't found any
information how to keep old builds.
Usually, for example a newer version of tcpdump gets build, the old
build will be deleted. Only different slots were keeped. However, I 
want to keep these old builds but I haven't found an option for that. 

Is it even possible to keep these? If not, anyone know why? if it's not
possible there must be a reason and i couldn't think of anyone...

-- 
greetings
Michael Mair-Keimberger

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: [gentoo-user] question about binhost's

[Alan McKinnon]

On 17/11/2014 23:01, Michael Mair-Keimberger wrote:
> Hi list,
> 
> I was setting up an binhost recently and i couldn't found any
> information how to keep old builds.
> Usually, for example a newer version of tcpdump gets build, the old
> build will be deleted. Only different slots were keeped. However, I 
> want to keep these old builds but I haven't found an option for that. 
> 
> Is it even possible to keep these? If not, anyone know why? if it's not
> possible there must be a reason and i couldn't think of anyone...
> 

short answer:
emerge -b

long answer:
read "man emerge". All of it. Gotchas await.

-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] question about binhost's

[Michael Mair-Keimberger]

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

On Mon, Nov 17, 2014 at 11:27:08PM +0200, Alan McKinnon wrote:
> On 17/11/2014 23:01, Michael Mair-Keimberger wrote:
> > Hi list,
> > 
> > I was setting up an binhost recently and i couldn't found any
> > information how to keep old builds.
> > Usually, for example a newer version of tcpdump gets build, the old
> > build will be deleted. Only different slots were keeped. However, I 
> > want to keep these old builds but I haven't found an option for that. 
> > 
> > Is it even possible to keep these? If not, anyone know why? if it's not
> > possible there must be a reason and i couldn't think of anyone...
> > 
> 
> short answer:
> emerge -b
> 
> long answer:
> read "man emerge". All of it. Gotchas await.

Well, the man page doesn't describe why it can't keep old builds...
(don't know what you referring too)

I do know `emerge -b` creates binary packages, but i orginally asked for
a way to keep older versions of binary packages.

Example:

emerge -b =net-analyzer/tcpdump-4.5.1-r1 
 - binary package for tcpdump-4.5.1-r1 gets created
emerge -b =net-analyzer/tcpdump-4.6.2
 - binary package for tcpdump-4.6.2 gets created AND tcpdump-4.5.1-r1
   gets deleted

However, I want to keep tcpdump-4.5.1-r1 if possible.

Is there a way? Simply emerge -b isn't sufficiency.

> 
> -- 
> Alan McKinnon
> alan.mckinnon@gmail.com
> 
> 

-- 
greetings
Michael Mair-Keimberger

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: [gentoo-user] question about binhost's

[Alan McKinnon]

On 17/11/2014 23:46, Michael Mair-Keimberger wrote:
> On Mon, Nov 17, 2014 at 11:27:08PM +0200, Alan McKinnon wrote:
>> On 17/11/2014 23:01, Michael Mair-Keimberger wrote:
>>> Hi list,
>>>
>>> I was setting up an binhost recently and i couldn't found any
>>> information how to keep old builds.
>>> Usually, for example a newer version of tcpdump gets build, the old
>>> build will be deleted. Only different slots were keeped. However, I 
>>> want to keep these old builds but I haven't found an option for that. 
>>>
>>> Is it even possible to keep these? If not, anyone know why? if it's not
>>> possible there must be a reason and i couldn't think of anyone...
>>>
>>
>> short answer:
>> emerge -b
>>
>> long answer:
>> read "man emerge". All of it. Gotchas await.
> 
> Well, the man page doesn't describe why it can't keep old builds...
> (don't know what you referring too)
> 
> I do know `emerge -b` creates binary packages, but i orginally asked for
> a way to keep older versions of binary packages.



You can't because emerge does not work that way[1].

If you want to keep the contents of an installed package:

a. use binpkgs to create an archive of the package at the time it is
built (not at the time is is about to be replaced)

b. Manually run quickpkg on packages you are interested in before
emerging them



[1] Unless Zac added this feature since the last time I read the man
pages. Won't be the first time a new feature sneaked in without a user
noticing :-)



> 
> Example:
> 
> emerge -b =net-analyzer/tcpdump-4.5.1-r1 
>  - binary package for tcpdump-4.5.1-r1 gets created
> emerge -b =net-analyzer/tcpdump-4.6.2
>  - binary package for tcpdump-4.6.2 gets created AND tcpdump-4.5.1-r1
>    gets deleted
> 
> However, I want to keep tcpdump-4.5.1-r1 if possible.
> 
> Is there a way? Simply emerge -b isn't sufficiency.
> 
>>
>> -- 
>> Alan McKinnon
>> alan.mckinnon@gmail.com
>>
>>
> 


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] question about binhost's

[thegeezer]

On 17/11/14 21:01, Michael Mair-Keimberger wrote:
> Hi list,
>
> I was setting up an binhost recently and i couldn't found any
> information how to keep old builds.
> Usually, for example a newer version of tcpdump gets build, the old
> build will be deleted. Only different slots were keeped. However, I 
> want to keep these old builds but I haven't found an option for that. 
>
> Is it even possible to keep these? If not, anyone know why? if it's not
> possible there must be a reason and i couldn't think of anyone...
>

um, these _are_ kept until you run
# eclean packages
unless i'm missing something ? 

so you can still emerge -K old-apps/package

for an example, in my /usr/portage/packages/app-shells on my laptop i have
# ls -lah
total 6.8M
drwx------  2 root root 4.0K Oct 14 21:02 .
drwx------ 76 root root 4.0K Nov 17 10:51 ..
-rw-------  1 root root 1.2M Sep  5 10:43 bash-4.2_p45.tbz2
-rw-r--r--  1 root root 1.2M Sep 26 20:52 bash-4.2_p48-r1.tbz2
-rw-r--r--  1 root root 1.2M Oct  1 14:33 bash-4.2_p50.tbz2
-rw-r--r--  1 root root 1.2M Oct  2 22:22 bash-4.2_p51.tbz2
-rw-r--r--  1 root root 1.2M Oct  6 10:09 bash-4.2_p52.tbz2
-rw-r--r--  1 root root 1.2M Oct  9 23:50 bash-4.2_p53.tbz2
-rw-r--r--  1 root root 8.4K Oct 14 21:02 push-1.6.tbz2

Re: [gentoo-user] question about binhost's

[Alan McKinnon]

On 17/11/2014 23:32, thegeezer wrote:
> On 17/11/14 21:01, Michael Mair-Keimberger wrote:
>> Hi list,
>>
>> I was setting up an binhost recently and i couldn't found any
>> information how to keep old builds.
>> Usually, for example a newer version of tcpdump gets build, the old
>> build will be deleted. Only different slots were keeped. However, I 
>> want to keep these old builds but I haven't found an option for that. 
>>
>> Is it even possible to keep these? If not, anyone know why? if it's not
>> possible there must be a reason and i couldn't think of anyone...
>>
> 
> um, these _are_ kept until you run
> # eclean packages
> unless i'm missing something ? 


No, you're not missing something. The OP seems to be non-English-first-
language and the question is poorly worded to a native speaker.

He's saying that emerge overwrites the previous installed version when
it rebuilds a package and he wants to keep it. The solution to that is
binpkgs.

You are talking about what happens to binpkg you already have, he is
asking how to get binpkgs in the first place




> 
> so you can still emerge -K old-apps/package
> 
> for an example, in my /usr/portage/packages/app-shells on my laptop i have
> # ls -lah
> total 6.8M
> drwx------  2 root root 4.0K Oct 14 21:02 .
> drwx------ 76 root root 4.0K Nov 17 10:51 ..
> -rw-------  1 root root 1.2M Sep  5 10:43 bash-4.2_p45.tbz2
> -rw-r--r--  1 root root 1.2M Sep 26 20:52 bash-4.2_p48-r1.tbz2
> -rw-r--r--  1 root root 1.2M Oct  1 14:33 bash-4.2_p50.tbz2
> -rw-r--r--  1 root root 1.2M Oct  2 22:22 bash-4.2_p51.tbz2
> -rw-r--r--  1 root root 1.2M Oct  6 10:09 bash-4.2_p52.tbz2
> -rw-r--r--  1 root root 1.2M Oct  9 23:50 bash-4.2_p53.tbz2
> -rw-r--r--  1 root root 8.4K Oct 14 21:02 push-1.6.tbz2
> 
> 
> 
> 


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] question about binhost's

[Matti Nykyri]

> On Nov 17, 2014, at 23:46, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> 
>> On 17/11/2014 23:32, thegeezer wrote:
>>> On 17/11/14 21:01, Michael Mair-Keimberger wrote:
>>> Hi list,
>>> 
>>> I was setting up an binhost recently and i couldn't found any
>>> information how to keep old builds.
>>> Usually, for example a newer version of tcpdump gets build, the old
>>> build will be deleted. Only different slots were keeped. However, I 
>>> want to keep these old builds but I haven't found an option for that. 
>>> 
>>> Is it even possible to keep these? If not, anyone know why? if it's not
>>> possible there must be a reason and i couldn't think of anyone...
>> 
>> um, these _are_ kept until you run
>> # eclean packages
>> unless i'm missing something ?
> 
> 
> No, you're not missing something. The OP seems to be non-English-first-
> language and the question is poorly worded to a native speaker.
> 
> He's saying that emerge overwrites the previous installed version when
> it rebuilds a package and he wants to keep it. The solution to that is
> binpkgs.
> 
> You are talking about what happens to binpkg you already have, he is
> asking how to get binpkgs in the first place

You also have a tool called 'quickpkg'. With that you can make binpkgs out of packages already installed on your system without recompiling. This might be a good tool for you if you have not made them in the first place.

>> 
>> so you can still emerge -K old-apps/package
>> 
>> for an example, in my /usr/portage/packages/app-shells on my laptop i have
>> # ls -lah
>> total 6.8M
>> drwx------  2 root root 4.0K Oct 14 21:02 .
>> drwx------ 76 root root 4.0K Nov 17 10:51 ..
>> -rw-------  1 root root 1.2M Sep  5 10:43 bash-4.2_p45.tbz2
>> -rw-r--r--  1 root root 1.2M Sep 26 20:52 bash-4.2_p48-r1.tbz2
>> -rw-r--r--  1 root root 1.2M Oct  1 14:33 bash-4.2_p50.tbz2
>> -rw-r--r--  1 root root 1.2M Oct  2 22:22 bash-4.2_p51.tbz2
>> -rw-r--r--  1 root root 1.2M Oct  6 10:09 bash-4.2_p52.tbz2
>> -rw-r--r--  1 root root 1.2M Oct  9 23:50 bash-4.2_p53.tbz2
>> -rw-r--r--  1 root root 8.4K Oct 14 21:02 push-1.6.tbz2

-- 
-Matti

Re: [gentoo-user] question about binhost's

[Michael Mair-Keimberger]

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

On Mon, Nov 17, 2014 at 09:32:45PM +0000, thegeezer wrote:
> On 17/11/14 21:01, Michael Mair-Keimberger wrote:
> > Hi list,
> >
> > I was setting up an binhost recently and i couldn't found any
> > information how to keep old builds.
> > Usually, for example a newer version of tcpdump gets build, the old
> > build will be deleted. Only different slots were keeped. However, I 
> > want to keep these old builds but I haven't found an option for that. 
> >
> > Is it even possible to keep these? If not, anyone know why? if it's not
> > possible there must be a reason and i couldn't think of anyone...
> >
> 
> um, these _are_ kept until you run
> # eclean packages
> unless i'm missing something ? 
> 
> so you can still emerge -K old-apps/package
> 
> for an example, in my /usr/portage/packages/app-shells on my laptop i have
> # ls -lah
> total 6.8M
> drwx------  2 root root 4.0K Oct 14 21:02 .
> drwx------ 76 root root 4.0K Nov 17 10:51 ..
> -rw-------  1 root root 1.2M Sep  5 10:43 bash-4.2_p45.tbz2
> -rw-r--r--  1 root root 1.2M Sep 26 20:52 bash-4.2_p48-r1.tbz2
> -rw-r--r--  1 root root 1.2M Oct  1 14:33 bash-4.2_p50.tbz2
> -rw-r--r--  1 root root 1.2M Oct  2 22:22 bash-4.2_p51.tbz2
> -rw-r--r--  1 root root 1.2M Oct  6 10:09 bash-4.2_p52.tbz2
> -rw-r--r--  1 root root 1.2M Oct  9 23:50 bash-4.2_p53.tbz2
> -rw-r--r--  1 root root 8.4K Oct 14 21:02 push-1.6.tbz2
> 
> 

Hmm, that's interesting.
I just checked another binhost and they clearly were kept. I don't
know why it doesn't work with mine but it's definitely a problem with my system.

Gonna check what's configured wrong.

Anyway, thanks for the hint.

-- 
greetings
Michael Mair-Keimberger

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: [gentoo-user] question about binhost's

[Neil Bothwick]

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

On Mon, 17 Nov 2014 22:55:05 +0100, Michael Mair-Keimberger wrote:

> Hmm, that's interesting.
> I just checked another binhost and they clearly were kept. I don't
> know why it doesn't work with mine but it's definitely a problem with
> my system.

They should be kept, it defeats one of the main reasons for using -b if
the old package is deleted - the ability to quickly roll back if a
package update causes problems. Are you running eclean from a cron job or
a portage env script?


-- 
Neil Bothwick

I typed Format SER: and accidentally killed a telephone operator!

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

Re: [gentoo-user] question about binhost's

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 721 bytes --]

On Monday 17 Nov 2014 22:14:47 Neil Bothwick wrote:
> On Mon, 17 Nov 2014 22:55:05 +0100, Michael Mair-Keimberger wrote:
> > Hmm, that's interesting.
> > I just checked another binhost and they clearly were kept. I don't
> > know why it doesn't work with mine but it's definitely a problem with
> > my system.
> 
> They should be kept, it defeats one of the main reasons for using -b if
> the old package is deleted - the ability to quickly roll back if a
> package update causes problems. Are you running eclean from a cron job or
> a portage env script?

Interestingly, how do you remove an binary package using portage when you no 
longer need it?  Using 'rm -i <package>' manually?
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [gentoo-user] question about binhost's

[wraeth]

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

On Tue, Nov 18, 2014 at 06:45:51AM +0000, Mick wrote:
> Interestingly, how do you remove an binary package using portage when you no 
> longer need it?  Using 'rm -i <package>' manually?

The `eclean` utility from app-portage/gentoolkit can do this for you (as
well as maintaining your distfiles directory).

There's nothing overly special about it, though, so if you feel the need
you can just `rm` files (though eclean is better).

-- 
wraeth <wraeth@wraeth.id.au>
GnuPG Key: B2D9F759

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

Re: [gentoo-user] question about binhost's

[Neil Bothwick]

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

On Tue, 18 Nov 2014 18:46:45 +1100, wraeth wrote:

> > Interestingly, how do you remove an binary package using portage when
> > you no longer need it?  Using 'rm -i <package>' manually?  
> 
> The `eclean` utility from app-portage/gentoolkit can do this for you (as
> well as maintaining your distfiles directory).

I didn't think eclean could handle individual packages? They are just
files, so rm is fine.

> There's nothing overly special about it, though, so if you feel the need
> you can just `rm` files (though eclean is better).

Beware of eclean if you use a shared $DISTDIR (or a shared $PKGDIR) if
you have computers with the same architecture and settings). eclean run n
one computer may remove files wanted by others on the network.


-- 
Neil Bothwick

There is always one more imbecile than you counted on.

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

Re: [gentoo-user] question about binhost's

[Michael Mair-Keimberger]

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

On Tue, Nov 18, 2014 at 08:41:05AM +0000, Neil Bothwick wrote:
> On Tue, 18 Nov 2014 18:46:45 +1100, wraeth wrote:
> 
> > > Interestingly, how do you remove an binary package using portage when
> > > you no longer need it?  Using 'rm -i <package>' manually?  
> > 
> > The `eclean` utility from app-portage/gentoolkit can do this for you (as
> > well as maintaining your distfiles directory).
> 
> I didn't think eclean could handle individual packages? They are just
> files, so rm is fine.
> 
> > There's nothing overly special about it, though, so if you feel the need
> > you can just `rm` files (though eclean is better).
> 
> Beware of eclean if you use a shared $DISTDIR (or a shared $PKGDIR) if
> you have computers with the same architecture and settings). eclean run n
> one computer may remove files wanted by others on the network.
> 
> 
> -- 
> Neil Bothwick
> 
> There is always one more imbecile than you counted on.

Thanks for clarification!

So far I couldn't reproduce my "problem" anymore and I think I just made
a wrong observation.
Initially I asked because I was pretty sure I had a binary package of
traceroute-2.0.18 which I believe were deleted after I upgraded to
traceroute-2.0.21.
However, I did some tests and it seems traceroute was the only example I
could find were this happen and now I'm not even sure if I ever had an
binary package of traceroute-2.0.18.

Here is also a brief explanation of what I'm actually trying to achieve:
A few weeks ago I set up another gentoo system on a rather old system
(core2duo/4gb ram/1TB storage). Since this one should be just a computer
for toying and trying around I thought about to put rootfs on a lvm 
partition so that I can easily clone the whole system.
This works flawless. With a little nice script I've wrote myself I can
easily clone/delete/backup/restore complete system's in minutes, which is
why I already have 6 different systems.
	- gentoo_base
	- gentoo_cinnamon
	- gentoo_gnome (with systemd)
	- gentoo_kde
	- gentoo_kde_testing
	- gentoo_lxqt
I guess the names are self-explaining. 

Moreover, I also had the idea to share similar packages across these
systems. This would mean, if I already installed xorg on
gentoo_cinnamon, I don't have to build it again on gentoo_kde. In this
case binary packages are a big win. Only packages with different use
flags would be rebuild. It's especially handy on packages like firefox,
chromium or libreoffice. :)

After I though old binaries were deleted I was eagerly to find a
solution for that, since it would make my setup less practical.
After all I should have checked other packages more carefully before 
asking stupid questions, but laziness lead me to my initial mail...

Anyway:
Older packages are kept, so everything seems to work as expected. I've
also checked for rm/elcean in cron and other places were it could run
automatically but I couldn't find anything.
I also tested on different systems with different packages. No problems
so far.

I'll keep an eye on it, but I guess there wasn't really a problem.

-- 
greetings
Michael Mair-Keimberger

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]