19. jan. 2012 19.01 skrev Carsten Munk <[email protected]>: > 19. jan. 2012 18.56 skrev letters.random13 <[email protected]>: >> hello, >> >> i'm trying to debug a rejected patch for Change I984779d5. i'm not too >> surprised it was rejected, just don't know how to decipher the rejection & >> proceed. >> [the contrib wiki pages don't seem to have any details like this in the >> 'responding to reviews' section] >> >> Patch Set 2: >> >> DBC results in Core_i586 can be read at >> http://qtl.merproject.org/13cf4e56-41a9-11e1-9caf-00163e6e0038.html >> >> the build log links for pkgs that succeeded and that failed both give: >> >> <status code="400"> >> <summary>i586: no logfile</summary> >> </status> > Hi, > > this is a bug (logs not showing) I've been meaning to get around to > tomorrow/during the weekend - you should be able to replicate the > error message by: > > osc linkpac Mer:fake:Core:i586 the-package-that-breaks home:you:yourproject > > The DBC report is basically saying that when your change is admitted, > packages that depend on your changed package, is failing to build > after the change was admitted >> >> >> >> where can i find the actual logs? (the pkg builds for me on obs against >> mer:core:fake i586 & armv7l/hl). >>
This should be fixed now, For future reference, /build/%s/%s/%s/%s/_log?nostream&start=0" % (wi.params.obsprojectname, wi.params.reponame, wi.params.repoarch, pkg) is the right format, not (obsprojectname, pkg, reponame, repoarch) :) BR Carsten Munk
