On June 4, 2015 8:45:19 PM EDT, Jimmy Berry
Based on that explanation I am confused how this situation could have arose. As I understand it the following would have had to occur for boost to be updated in tumblweed.
- factory snapshot created - automated tests run against factory snapshot - tests passed and tumbleweed snapshot released
As such how could the network repository be compiling against factory snapshot that does not contain updated boost like tumbleweed?
<path project="openSUSE:Factory" repository="snapshot"/>
Either way, just looking to get this resolved. Also would it not make more sense for the tumbleweed repository in network to actually build against tumbleweed as seems to be the default configuration if creating a new project.
<repository name="openSUSE_Tumbleweed"> <path project="openSUSE:Tumbleweed" repository="standard"/> ... </repository>
Changing the "tumbleweed" repo in network to actually be the tumbleweed repo is the right thing to do. The tumbleweed repo only came to exist 6 or 7 months ago and not everything has been redirected to the relatively new tumbleweed repo yet. I don't have the credentials to do that. I suggest you open a new thread asking for that to be done. If you're subscribed to -buildservice that might be a more productive list for that request than -factory. Greg -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org