On 2015/05/21 17:32, Francisco de Borja Lopez Rio wrote: > On Tue, May 19, 2015 at 07:47:43PM +0100, Stuart Henderson wrote: > > On 2015/05/19 17:37, Francisco de Borja Lopez Rio wrote: > > > Hi guys. > > > > > > I'm maintaining a buildslave box for python.org [1], running on (more or > > > less) > > > up-to-date snapshots and I've realized that something started to go wrong > > > after my latest upgrade, it seems mercurial is not able to clone the > > > cpython > > > repository anymore: > > > > "More or less" might not be good enough. If you have libpthread.so.19.0 then > > make *sure* your packages were updated after that, especially any > > python-related > > ones. > > > > Thanks for the hint on that one. With "more or less" I meant the snapshot + > packages. I usually wait for the .es mirror to be in sync (snapshot+packages) > and then I do a "full upgrade". Afterwards I don't upgrade packages unless I > upgrade the snapshot too (I guess installing packages built after a snapshot > has been released should be safe enough).
That isn't very safe, if you are tracking snapshots and there is a newer package snapshot out, you should really do a full pkg_add -u before installing new packages. Sometimes you can get away without it, but not always.
