[opensuse-buildservice] A "sad" build history
Hi, somethings wrong here. My logdigest package hasn't been built for ~10 days, despite numerous check-ins. A known bug? Something's wrong with the new scheduler? Note the source md5 sums. Peter poeml@batavia510 ~/bs/server:monitoring/logdigest % osc buildhist SUSE_Linux_10.1 i586 time srcmd5 rev bcnt vers-rel 2007-11-21 21:56:47 c42ae0d112565a2ae3fb1432277dbc6d 12 1 0.1.6-1 2008-01-24 15:23:38 0f5da86481f9c0ea55029802b8da4518 13 1 0.1.6-2 2008-01-24 16:07:04 88172acfdfefe653ef867667b8920351 18 1 0.1.7-1 2008-01-24 18:33:36 dc70f624fb3a2300a46997b9c589fb98 19 1 0.1.7-2 2008-01-25 15:03:31 fb569bee91ba27647251a0ef31c06db4 20 1 0.1.7-3 poeml@batavia510 ~/bs/server:monitoring/logdigest % osc log ---------------------------------------------------------------------------- r24 | poeml | 2008-02-05 12:24:24 | 6c8f5b6a10dedfc8309a1e53cc17c781 | 0.1.7 more cyrus and named ignores (r77) ---------------------------------------------------------------------------- r23 | poeml | 2008-01-30 13:08:20 | 5ed92c07381ac20c4a4cf27fef96dfed | 0.1.7 update ignores ---------------------------------------------------------------------------- r22 | poeml | 2008-01-29 09:13:21 | 717d55d2f410cfc14251764bd43c9ca4 | 0.1.7 update ignores to r75 ---------------------------------------------------------------------------- r21 | poeml | 2008-01-28 11:54:18 | 4edd74ebb6df926fe703bff2626c6e04 | 0.1.7 update ignores to r74 ---------------------------------------------------------------------------- r20 | poeml | 2008-01-25 14:16:34 | fb569bee91ba27647251a0ef31c06db4 | 0.1.7 fix cron snippet [...]
On Tue, Feb 05, 2008 at 02:08:30PM +0100, Dr. Peter Poeml wrote:
Hi,
somethings wrong here. My logdigest package hasn't been built for ~10 days, despite numerous check-ins. A known bug? Something's wrong with the new scheduler?
I found things like this in the project meta: <repository name="SUSE_Linux_10.1"> <path project="deleted" repository="standard"/> ^^^^^^^^^^ <arch>i586</arch> <arch>x86_64</arch> </repository> So there might be something wrong with the project meta. So what happened to it, who changed it when, and what's "deleted"? Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
Dr. Peter Poeml wrote:
On Tue, Feb 05, 2008 at 02:08:30PM +0100, Dr. Peter Poeml wrote:
Hi,
somethings wrong here. My logdigest package hasn't been built for ~10 days, despite numerous check-ins. A known bug? Something's wrong with the new scheduler?
I found things like this in the project meta:
<repository name="SUSE_Linux_10.1"> <path project="deleted" repository="standard"/>
^^^^^^^^^^
<arch>i586</arch> <arch>x86_64</arch> </repository>
Were you using the Java:* repositories perhaps? These were deleted recently in favour of *:NonFree repos (osc ls | grep :NonFree). Probably the change was not announced loudly enough ;). Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, Feb 05, 2008 at 04:35:09PM +0100, Michal Marek wrote:
Dr. Peter Poeml wrote:
On Tue, Feb 05, 2008 at 02:08:30PM +0100, Dr. Peter Poeml wrote:
Hi,
somethings wrong here. My logdigest package hasn't been built for ~10 days, despite numerous check-ins. A known bug? Something's wrong with the new scheduler?
I found things like this in the project meta:
<repository name="SUSE_Linux_10.1"> <path project="deleted" repository="standard"/>
^^^^^^^^^^
<arch>i586</arch> <arch>x86_64</arch> </repository>
Were you using the Java:* repositories perhaps? These were deleted
I don't know. I just happen to build a package in that project.
recently in favour of *:NonFree repos (osc ls | grep :NonFree). Probably the change was not announced loudly enough ;).
loud or not loud. It is a bug that those projects are set to "deleted" silently, without replacing them with something useful. Especially if this concerns a large number of projects. The renaming should have involved a systematic change of all affected repositories, or at least notification of the maintainers. There was no indication of the rename and its consequences. See, all packages were in state "succeeded" (how could they?), and they simply were not rebuilt, even after source changes. Simply always "succeeded". Which is clearly a bug, isn't it? Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
participants (2)
-
Dr. Peter Poeml
-
Michal Marek