Summary: | sys-apps/portage-2.1.8.3 dies with stacktrace on binhost FTP errors | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Christian Kauhaus <kc> |
Component: | Binary packages support | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 335925 |
Description
Christian Kauhaus
2010-09-20 13:06:23 UTC
The exception indicates that you're triggering the old protocol, which happens whenever $PORTAGE_BINHOST/Packages can't be fetched. Make sure that you have $PORTAGE_BINHOST set correctly so that the Packages file can be fetched. You can run `emaint --fix binhost` on the server in order to generate or update the Packages file. This file is updated automatically with new packages when they are built, but you need to call `emaint --fix binhost` if it is out of sync with the packages in $PKGDIR for any reason. For example, eclean-pkg calls `emaint --fix binhost` after it removes old binary packages. (In reply to comment #1) > The exception indicates that you're triggering the old protocol. I'm trying to clarify. The bug is triggered when a defective FTP server gives *no* sensible answers at all. I think that emerge should not die in such cases. Instead, it should either try to compile the package or proceed with the next one. Thanks, there's a fix in git now: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=bf5877484cbca0b59c1b9d3688d338465083bcf9 This is fixed in 2.1.9.10 and 2.2_rc86. |