Hi
I don't know if somebody tested how would react urpmi in those cases , when
the same package is doubled in main with the only diff distepoch and
sometimes bumped rel, I've done some tests
on my own , ( so nothing official, just in order to know if I'll can
build on 2014.1) , and it seems that
in 10 cases out of 28 ( almost a third) the new distepoched package had
to be republished
to avoid wget 8 error, this should fix it until main media is still open
in writing, ( I've informed Collin about one of my tests),
but when will be closed we'll have again that plf situation as we had it
on 2014.0.
I don't have a fix for this, since never-ever, saw something like this ,
meaning to use same main for 2 distepoched packages
i don't want to discuss if is a good or bad idea, just want to warn you
all before the 2014.0&&2014.1 main repo freeze.
This situation is not ABF related I'm pretty sure about it, so can we
just try to find the guilty in "our home" before
start accusing somebody else? Right mister Bero, sir?
I don't really know if urpmi is to be blamed, or genhdlist2 or other but
i's a matter of fact that
the root of the problem is two distepoch packages in the same hdlist.
And Is also hard to reproduce since the
wget error is observed randomly ... , same build with no changes,( not
even a bumped rel), sometimes went
just nice sometimes I've got wget 8 error -missing package
Consider yourselves warned.
Thank you for your attention.
--
Greetings
___________________
MRB ain't no shit
Rosalinux.Ro
Mandrivausers.Ro
________________
Talk is cheap, show me the code.