Summary: | emerge-webrsync thinks tarsync supports lzma | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Brian Harring (RETIRED) <ferringb> |
Component: | Core - External Interaction | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alon.barlev, doron.fediuck, esigra |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=702970 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 335925 |
Description
Brian Harring (RETIRED)
2010-08-15 04:58:35 UTC
This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=df3921f0ea835a62ea417c9074f3c9ab87c59b64 The problem is people may get stuck (as I did), without the possibility to sync again. Thus they won't get the fix. A possible workaround is to unmerge tarsync, run emerge-webrsync, and the emerge tarsync again. It would be wise to publish this issue somewhere in Gentoo (forums ?), so people become aware of if. This is in 2.2_rc68, but I'll leave this bug open until it's in an unmasked version. This is fixed in 2.1.9. |