http://bugzilla.opensuse.org/show_bug.cgi?id=1177175 Ismail Dönmez changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |idonmez@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177175 http://bugzilla.opensuse.org/show_bug.cgi?id=1177175#c3 Frank Schreiner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |FSchreiner@suse.com --- Comment #3 from Frank Schreiner --- As Fabian already explained - this is not a bug - its a feature. I would also not recommend to turn "--error-exit-val" on globally in OBS - this would put all the pressure to fix broken packages on the release managers. I already wrote some patches for the upstream rpmlint: https://github.com/rpm-software-management/rpmlint/pull/355 but it seems that these patches are not in the opensuse version. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177175 http://bugzilla.opensuse.org/show_bug.cgi?id=1177175#c5 --- Comment #5 from Adrian Schröter --- after some more investigation, the problem is not really new, just multiple bugreports reach us atm. Given the amount publisher errors in last hours we need to let publishing fail, but we need to transport this information also back to the user. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177175 http://bugzilla.opensuse.org/show_bug.cgi?id=1177175#c7 Frank Schreiner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #7 from Frank Schreiner --- (In reply to Neal Gompa from comment #6)

One thing you might want to consider for the future is having createrepo_c create the repodata per package, and use mergerepo_c to pull them together in the end for the repository. This is how Koji does it and that allows you to have "publish logs" on a per-package basis.

I think we could also achieve this with a log-file from createrepo_c's output - but we have no channel to display it to the user. The messages end up in a logfile on the server where only the admin see's it. The user gets no feedback what went wrong. But this is a different story that needs to be fixed on OBS side. Will close the bug as this is no bug in createrepo_c. -- You are receiving this mail because: You are on the CC list for the bug.