[gentoo-user] Changed behavior of portage when using FEATURES="getbinpkg"

[gentoo-user] Changed behavior of portage when using FEATURES="getbinpkg"

[Dan Johansson]

I have a setup where I have one "development" host and one "production" host. 
On the dev-host I have FEATURES="buildpkg" and on the prod-host I have 
FEATURES="getbinpkg" and PORTAGE_BINHOST="http://192.168.4.4/portage-i686/" 
(this is my dev-host) set. 

A few days ago, after the two hosts has been down for an extended time (since 
Nov last year) I can no longer install/update an packages on the prod-host.

Here is an example of how it looks like :
-----------------------------------8<---------------------------------
# emerge --update --deep --verbose --reinstall changed-use --with-bdeps y 
world

These are the packages that would be merged, in order:

Calculating dependencies
Fetching bininfo from http://192.168.4.4/portage-i686/
Loaded metadata pickle.
cache miss: '0' --- cache hit: '470'
... done!
[binary     U ] sys-apps/portage-2.1.7.17 [2.1.7.16] USE="-build -doc -epydoc 
(-python3) (-selinux)" LINGUAS="-pl"

Total: 1 package (1 upgrade, 1 binary), Size of downloads: 0 kB


>>> Emerging binary (1 of 1) sys-apps/portage-2.1.7.17
--2010-03-05 17:54:15--  http://192.168.4.4/portage-i686/portage-2.1.7.17.tbz2
Connecting to 192.168.4.4:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 568929 (556K) [text/plain]
Saving to: `/usr/portage/packages/sys-apps/portage-2.1.7.17.tbz2'

     0K .......... .......... .......... .......... ..........  8% 1.75M 0s
    50K .......... .......... .......... .......... .......... 17% 4.30M 0s
   100K .......... .......... .......... .......... .......... 26% 20.8M 0s
   150K .......... .......... .......... .......... .......... 35% 6.12M 0s
   200K .......... .......... .......... .......... .......... 44% 2.16M 0s
   250K .......... .......... .......... .......... .......... 53% 1.84M 0s
   300K .......... .......... .......... .......... .......... 62% 2.60M 0s
   350K .......... .......... .......... .......... .......... 71% 84.4M 0s
   400K .......... .......... .......... .......... .......... 80% 72.0M 0s
   450K .......... .......... .......... .......... .......... 89% 12.5M 0s
   500K .......... .......... .......... .......... .......... 98%  135M 0s
   550K .....                                                 100% 2.73M=0.1s

2010-03-05 17:54:15 (4.42 MB/s) - `/usr/portage/packages/sys-
apps/portage-2.1.7.17.tbz2' saved [568929/568929]


!!! Digest verification failed:
!!! /usr/portage/packages/sys-apps/portage-2.1.7.17.tbz2
!!! Reason: Filesize does not match recorded size
!!! Got: 568929
!!! Expected: 2224676
File renamed to '/usr/portage/packages/sys-
apps/portage-2.1.7.17.tbz2._checksum_failure_.IJVYZY'

>>> Failed to emerge sys-apps/portage-2.1.7.17, Log file:

>>>  '/var/log/portage/sys-apps:portage-2.1.7.17:20100305-165414.log'
-----------------------------------8<---------------------------------

The size 568929 matches the size on dev and prod:
dev:
# ll /usr/portage/packages/sys-apps/portage-2.1.7.17.tbz2  
/usr/portage/packages/All/portage-2.1.7.17.tbz2
-rw-r--r-- 1 root root 568929 Mar  5 17:53 
/usr/portage/packages/All/portage-2.1.7.17.tbz2
lrwxrwxrwx 1 root root     28 Mar  5 17:53 /usr/portage/packages/sys-
apps/portage-2.1.7.17.tbz2 -> ../All/portage-2.1.7.17.tbz2

prod:
# ll /usr/portage/packages/sys-
apps/portage-2.1.7.17.tbz2._checksum_failure_.IJVYZY
-rw-r--r-- 1 root root 568929 Mar  5 17:53 /usr/portage/packages/sys-
apps/portage-2.1.7.17.tbz2._checksum_failure_.IJVYZY

What has happened and how to solve it?

-- 
Dan Johansson, <http://www.dmj.nu>
***************************************************
This message is printed on 100% recycled electrons!
***************************************************

[gentoo-user] Re: Changed behavior of portage when using FEATURES="getbinpkg"

[Nicolas Sebrecht]

On Fri, Mar 05, 2010 at 06:14:39PM +0100, Dan Johansson wrote:
> 
> I have a setup where I have one "development" host and one "production" host. 
> On the dev-host I have FEATURES="buildpkg" and on the prod-host I have 
> FEATURES="getbinpkg" and PORTAGE_BINHOST="http://192.168.4.4/portage-i686/" 
> (this is my dev-host) set. 
> 
> A few days ago, after the two hosts has been down for an extended time (since 
> Nov last year) I can no longer install/update an packages on the prod-host.

<...>

> !!! Digest verification failed:
> !!! /usr/portage/packages/sys-apps/portage-2.1.7.17.tbz2
> !!! Reason: Filesize does not match recorded size
> !!! Got: 568929
> !!! Expected: 2224676
> File renamed to '/usr/portage/packages/sys-
> apps/portage-2.1.7.17.tbz2._checksum_failure_.IJVYZY'
> 
> >>> Failed to emerge sys-apps/portage-2.1.7.17, Log file:
> 
> >>>  '/var/log/portage/sys-apps:portage-2.1.7.17:20100305-165414.log'
> -----------------------------------8<---------------------------------
> 
> The size 568929 matches the size on dev and prod:
> dev:
> # ll /usr/portage/packages/sys-apps/portage-2.1.7.17.tbz2  
> /usr/portage/packages/All/portage-2.1.7.17.tbz2
> -rw-r--r-- 1 root root 568929 Mar  5 17:53 
> /usr/portage/packages/All/portage-2.1.7.17.tbz2
> lrwxrwxrwx 1 root root     28 Mar  5 17:53 /usr/portage/packages/sys-
> apps/portage-2.1.7.17.tbz2 -> ../All/portage-2.1.7.17.tbz2
> 
> prod:
> # ll /usr/portage/packages/sys-
> apps/portage-2.1.7.17.tbz2._checksum_failure_.IJVYZY
> -rw-r--r-- 1 root root 568929 Mar  5 17:53 /usr/portage/packages/sys-
> apps/portage-2.1.7.17.tbz2._checksum_failure_.IJVYZY
> 
> What has happened and how to solve it?

I'd say the prod portage tree is not synced against the same
version of the dev one since it's expecting for a 2224676 file size.

Do you sync the prod tree against the dev tree?

-- 
Nicolas Sebrecht