On Fri, Apr 13, 2012 at 4:24 PM, Michael Schroeder wrote:

On Fri, Apr 13, 2012 at 04:19:34PM +0200, Robert Schiele wrote:

...

I observed the following behavior which seems inconsistent to me but maybe there is a reason behind that that I currently don't see:

- When deleting all architecture from a repository, the corresponding /srv/obs/build/$PRJ/$REPO/$ARCH directory is not wiped, nor is /src/obs/repos/$PRJ/$REPO/*.

That's the "published" area, which is a mix-in of all architectures for this repo.

I understand that but still when removing all architectures it should publish an empty repository. This is not triggered though. If I trigger repository publishing manually with the obs_admin tool it does exactly that but a manual trigger is needed. My guess for this case is that since I deleted all architectures in the repository no scheduler feels responsible for triggering the publishing.

...

- When deleting a repository from a project, the corresponding directories are neither deleted in those places.

- When deleting the whole project, the corresponding directories _do_ get deleted (which is what I would have expected in all three cases).

Is there a reason that in the first two cases the directories don't get removed or is this a bug?

The scheduler is supposed to delete the directories, please consult the log to see what's going on. (Maybe it's just busy...)

Even if it is busy it should still do that after it has calmed down, right? But I will investigate further... Again the question: If I made sure that the scheduler has processed its work queue, is it safe to delete the directories that refer to non-existing architectures or repositories in the mentioned places or do you see a problem with that? Robert -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Fri, Apr 13, 2012 at 4:54 PM, Robert Schiele wrote:

Even if it is busy it should still do that after it has calmed down, right? But I will investigate further...

Did that now. So, what I found is that when you delete an architecture or a repository the only thing that happens in the scheduler is something like: updating meta for project 'home:rschiele:foobar' from http://obs-srcsrv.mydomain.com:5352 getting data for project 'home:rschiele:foobar' from http://obs-srcsrv.mydomain.com:5352 calculating project dependencies... sorting projects and repositories... The result is that in these cases apparently never something in the build directory gets deleted, even after _Only_ when I delete the whole project the scheduler finally seems to remove stuff from the backend. Robert -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Mon, Apr 16, 2012 at 1:06 PM, Michael Schroeder wrote:

On Mon, Apr 16, 2012 at 12:43:42PM +0200, Robert Schiele wrote:

...

updating meta for project 'home:rschiele:foobar' from http://obs-srcsrv.mydomain.com:5352 getting data for project 'home:rschiele:foobar' from http://obs-srcsrv.mydomain.com:5352 calculating project dependencies... sorting projects and repositories...

What are the next lines? There should be a "looking at..." line with just the project and no repo.

No, it is just followed with the usual... 2012-04-16 08:15:34: waiting for an event... ... actually don't have anything more to do line. Robert -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Mon, Apr 16, 2012 at 1:20 PM, Michael Schroeder wrote:

Hmm, WORKSFORME(tm). Just tested it on my local OBS instance. I've no clue what's different on your site.

Ok, maybe there was a change within the recent weeks. I might try an update to the current git version... Robert -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

-----Original Message----- From: "Robert Schiele" Sent: Monday, April 16, 2012 6:43am To: "Michael Schroeder" Cc: opensuse-buildservice@opensuse.org Subject: Re: [opensuse-buildservice] inconsistent behavior on architecture, repository, and project deletion On Fri, Apr 13, 2012 at 4:54 PM, Robert Schiele wrote:

Even if it is busy it should still do that after it has calmed down, right? But I will investigate further...

Did that now. So, what I found is that when you delete an architecture or a repository the only thing that happens in the scheduler is something like: updating meta for project 'home:rschiele:foobar' from http://obs-srcsrv.mydomain.com:5352 getting data for project 'home:rschiele:foobar' from http://obs-srcsrv.mydomain.com:5352 calculating project dependencies... sorting projects and repositories... The result is that in these cases apparently never something in the build directory gets deleted, even after _Only_ when I delete the whole project the scheduler finally seems to remove stuff from the backend. ------------ (Sorry for the unmarked quoting, rackspace webmail.) Could this be the cause of my false unresolvable problem? I had dependency-borking versions of autoconf and m4 in a project briefly, they caused a lot of packages in some repos in that project to either fail building or become unresolvable because of the way the various specs are written. I removed the offending autoconf & m4 packages, but one package, in two repos, just one arch in each repo, keeps saying unresolvable for a couple days now. I can't see how to clear it. There shouldn't be any such problem any more. Outwardly, the state of the project for those packages is the same as it was a few days ago when it built just fine. It's saying nothing provides m4 1.4.4 in one repo and nothing provides m4 1.4.3 in the other. Those are the native m4 versions in those repos and they ARE there because other packages that need the same things build fine, and even those same pacckages build fine in the same repos in a new subproject. So I'm guessing the problem is that it's seeing a newer m4 that's not supposed to be there anymore and not seeing the repo's own native m4 which IS there in build service DISCONTINUED:<version> repos, and IS the requested version in each case. Is there any osc commands I can use to clear this? or at least find out why it's doing that so I can ask an obs admin to fix something that can't be fixed from my end as a user? Stuck false unresolvables: https://build.opensuse.org/package/show?package=jbigkit&project=home%3Aaljex Proof it's a false unresolvable: https://build.opensuse.org/package/show?package=jbigkit&project=home%3Aaljex%3Abranches%3Agraphics -- bkw -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org