For dealing with 'lp:' repos which are pretty common for bzr ebuilds, bzr can use two protocols: either anonymous https (by default) or ssh (when logged in). Sadly, the https protocol is awfully ineffective. For the games-strategy/s25rttr ebuild (Sunrise overlay), with anonymous https download bzr fetched ~740M of data while with ssh... ~140M. So, using https resulted in circa ~600M of overhead which is practically insane. After asking on #bzr, I was informed that they're aware of the uneffictivity and they plan to fix it someday. I was suggested that we should consider creating a global launchpad account for our users, and using that in the eclass. What do you think?
Created attachment 312321 [details] .bzr.log for s25rttr I can't reproduce the problem. The downloaded data volume for initial branchning of the s25rttr repo doesn't look excessive to me: >>> Unpacking source... * bzr branch start --> * repository: lp:s25rttr => /var/portage/distfiles/bzr-src/s25rttr You have not informed bzr of your Launchpad ID, and you must do this to write to Launchpad or access private data. See "bzr help launchpad-login". 6kB 8kB/s \ Finding revisions 6kB 8kB/s | Fetching revisions:Get stream source [...] 148253kB 365kB/s - Fetching revisions:Inserting stream:Done 90117/90117 148367kB 10kB/s | Fetching revisions:Finishing stream Branched 7975 revisions. * exporting ... * revision 7975 is now in /var/tmp/portage/games-strategy/s25rttr-9999/work/s25rttr-9999 >>> Source unpacked in /var/tmp/portage/games-strategy/s25rttr-9999/work $ du -s /usr/portage/distfiles/bzr-src/s25rttr 145688 /usr/portage/distfiles/bzr-src/s25rttr BZR log is attached.
Ok, it seems to work fine now...
