Clean up spec file to enable building on leap #1
Reference in New Issue
Block a user
No description provided.
Delete Branch "(deleted):factory"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes buildfailure on Leap, patches were dropped, but the conditional was left in the spec file.
@sfalken This is either empty PR or at least needs to be rebased on the top of
pool/factory
.I have no idea what that means. There's a commit and 2 files changed, based on what I'm looking at.
What do you mean "empty PR" ?
You need to rebase your changes on top of
pool/python-pygit2
factory branch. The diff is against your older version and there are conflicts in the .changes file.I think I did that right.
That seems a rather optimistic statement:
Then it can just stay broken. I don't have time to wade through this half broken mess of a workflow.
It's not the workflow here... It's simply git. Look
https://src.opensuse.org/sfalken/python-pygit2/src/branch/factory
says "This branch is 6 commits behind pool/python-pygit2:factory"
git rebase
is not cherry picking other stuff that was missing, which is what you've appeared to have done.git rebase
puts your changes on top of Factory.So, I've looked at this trying to merge this change .... and there's nothing to apply because
8f774c3b9f (diff-b2e7f83b7484cae11bfecf6a91f99c0051fa57c3)
@mcepl has already fixed this 4 months ago in this changeset.
This PR was not empty when @sfalken created it on Oct 19.
8f774c3b9f
was committed on Nov 5.You are correct... I guess this highlights the need to have devel projects and not just one giant
/pool
with direct submissions, where PR can get lost much more easily. (we still plan on having /pool for factory and SLE and other official stuff, but that is going to be managed via projects, so these PRs should not get lost like this one did)Auch, I have missed how old this PR was! I am sorry for that.
Pull request closed