You are not logged in.

#1 2010-03-18 20:22:17

moimael
Member
Registered: 2009-10-04
Posts: 4

Boost is older in testing repo !

Hi, i just wanted to test some new stuff with the testing repo but it appears that the version of boost is older in testing than in extra (1.41 vs 1.42) avoiding me to upgrade my arch ! (because of super maryo chronicle who depend on boost >= 1.42), is there any reason to do that ?

Thanks !

Offline

#2 2010-03-18 20:24:30

wonder
Developer
From: Bucharest, Romania
Registered: 2006-07-05
Posts: 5,941
Website

Re: Boost is older in testing repo !

if you use testing, you should know already from arch-dev-public why is that.

http://mailman.archlinux.org/pipermail/ … 16194.html

basically, the rebuild is not finished and you should wait a bit more.


Give what you have. To someone, it may be better than you dare to think.

Offline

#3 2010-03-18 20:59:31

Daenyth
Forum Fellow
From: Boston, MA
Registered: 2008-02-24
Posts: 1,244

Re: Boost is older in testing repo !

If you use the testing repo, you really should pay attention to the dev list.

Offline

#4 2010-03-18 22:08:05

moimael
Member
Registered: 2009-10-04
Posts: 4

Re: Boost is older in testing repo !

Thanks for your answer, i just use occasionnaly the testing repo, and only for specific things , so i dont follow arch-dev-public wink

Offline

#5 2010-03-29 21:56:30

pyther
Member
Registered: 2008-01-21
Posts: 1,395
Website

Re: Boost is older in testing repo !

*facepalm*
/me waits for the speech


Website - Blog - arch-home
Arch User since March 2005

Offline

#6 2010-03-29 22:09:00

Ghost1227
Forum Fellow
From: Omaha, NE, USA
Registered: 2008-04-21
Posts: 1,422
Website

Re: Boost is older in testing repo !

moimael wrote:

Thanks for your answer, i just use occasionnaly the testing repo, and only for specific things , so i dont follow arch-dev-public wink

Short version: Fail
Short version for those who are reading impaired:
epic-fail-breakdance-fail.jpg
Long version: We kinda figure if you're using the testing repo, you're smart enough to either follow what's going on with it, or fix it yourself. Hence, not a bug. I suggest this "bug report" be closed as such tongue
Longer version: I'm too lazy to write it... NEXT!


.:[My Blog] || [My GitHub]:.

Offline

Board footer

Powered by FluxBB