Mailinglist Archive: opensuse-buildservice (269 mails)

< Previous Next >
Re: [opensuse-buildservice] how to verify and fix broken links?
  • From: Adrian Schröter <adrian@xxxxxxx>
  • Date: Thu, 25 Sep 2008 16:52:45 +0200
  • Message-id: <200809251652.45846.adrian@xxxxxxx>
On Thursday 25 September 2008 16:47:38 wrote Peter Poeml:
On Thu, Sep 25, 2008 at 10:59:23AM +0200, Ludwig Nussel wrote:

Suppose I have a package linked from another project with patches
(project*.diff) on top of it. Now the other package is updated and
the patches no longer apply. osc rdiff doesn't work because it can't
apply the patches either. How do I verify how and which of my
changes got applied to the linked package?

I had the same at least two times, and it was a bug mess and manual work
to sort it out.

Especially, it seems it can happen with applying submit requests - which
is the following bug, I assume?

sure, if an intermediate state gets submitted, this can happen.
We can improve this maybe in the server side clean up, but we need in any case
a better handling of not matching patches in our frontends.

osc could for example checkout unexpanded, and check which changes have been
merged. And keep conflicting changes like svn does with the conflicting
changes in the files.

I dunno if there are standard tools around which can get utelized for this.



Adrian Schroeter
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
email: adrian@xxxxxxx

To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups