Hi, I was reported a weird behavior of packages in GNOME:Apps, specifically gnucash. osc buildhist GNOME:Apps gnucash openSUSE_12.1 x86_64 for example has this in the list 2012-08-03 08:24:11 28f8033d394dffaeae755db983f58b2f 35 2.4.10-38.3 2012-08-05 18:48:51 d2dd40f1c261c65516bdf1d04be6ca58 36 2.4.11-39.1 2012-08-07 04:30:46 d2dd40f1c261c65516bdf1d04be6ca58 36 2.4.11-39.2 2012-08-09 10:15:53 b66a20f770f53a7be1459c03824a0cab 37 2.4.11-37.1 2012-08-10 02:26:01 b66a20f770f53a7be1459c03824a0cab 37 2.4.11-37.2 => So around Aug 9, the release dropped down by 2.. Also interesting: Release 37 (which is normally between 36 and 38) was skipped: 2012-07-21 16:43:53 de907016bad800b089c3b8d8cde63047 34 2.4.10-36.1 2012-07-24 13:11:43 28f8033d394dffaeae755db983f58b2f 35 2.4.10-38.1 (ok, maybe there were two checkins shortly). osc log shows r37 as the current release (which explains why the current package is at 37). So, any explanation where r38 and r39 are coming from in the build hist and on users systems? This is not limited to gnucash, as can be seen here: osc buildhist GNOME:Apps transmission openSUSE_12.1 x86_64 2012-07-04 16:43:41 db55e49bd1d121526cda936d0c5706fa 71 2.52-73.2 2012-07-09 13:57:21 7921fb7db5cf542d4a2be57993b3953e 72 2.60-74.1 2012-07-24 12:28:00 d980394c3fce783f389274a38983dac8 73 2.60-73.1 Looking forward to hear from the masters on that one... would be great to find a way to avoid such cases, as it asks users to either downgrade (if they dup) or they might not get the next update (considering current being 37, the user having 39, he will likely not get '38'). (Actually, also something that disappeared somewhen: didn't we reset CI count when the version increased?) Best regards, Dominique -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org