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>
--
Jimmy
On Thu, Jun 4, 2015 at 7:03 AM,
On June 4, 2015 6:05:15 AM EDT, "Carlos E. R."
wrote: On 2015-06-03 23:30, Jan Engelhardt wrote:
TW snapshots are not the same as the "snapshot" repository of openSUSE:Factory.
Basically, factory is untested. TW is tested (automated tests).
Agreed. Factory snapshots are made every day. If and only if a factory snapshot passes aotoqa it is promoted to a tumbleweed snapshot.
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
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org