Updating igraph to 0.5.4. Success for devel and f14. Then for f13 I get:
> fedpkg switch-branch f13
Branch f13 set up to track remote branch f13/master from origin.
> git merge master
CONFLICT (rename/delete): Rename .cvsignore->.gitignore in HEAD and deleted
in master
Automatic merge failed; fix conflicts and then commit the result.
Strange, that seems to be the same thing I did for f14. How do I fix?
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
09-16-2010, 02:44 PM
Todd Zullinger
yet another git problem
Neal Becker wrote:
> Updating igraph to 0.5.4. Success for devel and f14. Then for f13 I get:
>
>> fedpkg switch-branch f13
> Branch f13 set up to track remote branch f13/master from origin.
>
>> git merge master
> CONFLICT (rename/delete): Rename .cvsignore->.gitignore in HEAD and deleted
> in master
> Automatic merge failed; fix conflicts and then commit the result.
>
> Strange, that seems to be the same thing I did for f14. How do I fix?
The merge works well for f14 because it was branched from master after
the conversion to git. Prior release were "branched" in cvs and the
git conversion imported those branches with different histories. So
the first merge you do into an older branch usually needs some
massassing. There's an open fedpkg ticket to improve this.
On a few of my packages where I wanted to sync f13 from master, I used
this:
git merge -s recursive -X theirs master
This tells git that when there are conflicts in the merge, resolve
them automatically by preferring the content from the master branch
('theirs').
--
Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~
Never attribute to malice that which can be adequately explained by
stupidity.
-- Hanlon's Razor
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
09-16-2010, 03:05 PM
Neal Becker
yet another git problem
Todd Zullinger wrote:
> Neal Becker wrote:
>> Updating igraph to 0.5.4. Success for devel and f14. Then for f13 I
>> get:
>>
>>> fedpkg switch-branch f13
>> Branch f13 set up to track remote branch f13/master from origin.
>>
>>> git merge master
>> CONFLICT (rename/delete): Rename .cvsignore->.gitignore in HEAD and
>> deleted in master
>> Automatic merge failed; fix conflicts and then commit the result.
>>
>> Strange, that seems to be the same thing I did for f14. How do I fix?
>
> The merge works well for f14 because it was branched from master after
> the conversion to git. Prior release were "branched" in cvs and the
> git conversion imported those branches with different histories. So
> the first merge you do into an older branch usually needs some
> massassing. There's an open fedpkg ticket to improve this.
>
> On a few of my packages where I wanted to sync f13 from master, I used
> this:
>
> git merge -s recursive -X theirs master
>
> This tells git that when there are conflicts in the merge, resolve
> them automatically by preferring the content from the master branch
> ('theirs').
>
Let's try:
$cd igraph
$fedpkg switch-branch f13
Branch f13 set up to track remote branch f13/master from origin.
$ git merge -s recursive -X theirs master
CONFLICT (rename/delete): Rename .cvsignore->.gitignore in HEAD and deleted
in master
Automatic merge failed; fix conflicts and then commit the result.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
09-16-2010, 03:14 PM
Roman Rakus
yet another git problem
On 09/16/2010 04:21 PM, Neal Becker wrote:
> Updating igraph to 0.5.4. Success for devel and f14. Then for f13 I get:
>
>> fedpkg switch-branch f13
> Branch f13 set up to track remote branch f13/master from origin.
>
>> git merge master
> CONFLICT (rename/delete): Rename .cvsignore->.gitignore in HEAD and deleted
> in master
> Automatic merge failed; fix conflicts and then commit the result.
>
> Strange, that seems to be the same thing I did for f14. How do I fix?
>
What are you trying to do? I guess `git cherry-pick' will work for you.
RR
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
09-16-2010, 03:23 PM
Andreas Schwab
yet another git problem
Neal Becker <ndbecker2@gmail.com> writes:
> Let's try:
>
> $rm -rf igraph
Btw., you can undo a failed merge with "git reset --merge".
Andreas.
--
Andreas Schwab, schwab@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84 5EC7 45C6 250E 6F00 984E
"And now for something completely different."
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
09-16-2010, 03:23 PM
Garrett Holmstrom
yet another git problem
Roman Rakus wrote:
> On 09/16/2010 04:21 PM, Neal Becker wrote:
>> Updating igraph to 0.5.4. Success for devel and f14. Then for f13 I get:
>>
>>> fedpkg switch-branch f13
>> Branch f13 set up to track remote branch f13/master from origin.
>>
>>> git merge master
>> CONFLICT (rename/delete): Rename .cvsignore->.gitignore in HEAD and deleted
>> in master
>> Automatic merge failed; fix conflicts and then commit the result.
>>
>> Strange, that seems to be the same thing I did for f14. How do I fix?
>>
> What are you trying to do? I guess `git cherry-pick' will work for you.
Or you can just resolve the merge conflict yourself. You only have to
merge the disparate branches once. :-
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
09-17-2010, 10:45 AM
Neal Becker
yet another git problem
Any help here? I'm still stuck.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
09-17-2010, 02:41 PM
Michel Alexandre Salim
yet another git problem
On Thu, 16 Sep 2010 10:21:02 -0400, Neal Becker wrote:
> Updating igraph to 0.5.4. Success for devel and f14. Then for f13 I
> get:
>
>> fedpkg switch-branch f13
> Branch f13 set up to track remote branch f13/master from origin.
>
>> git merge master
> CONFLICT (rename/delete): Rename .cvsignore->.gitignore in HEAD and
> deleted in master
> Automatic merge failed; fix conflicts and then commit the result.
>
> Strange, that seems to be the same thing I did for f14. How do I fix?
Sometimes the merge can be resolved without conflict if you first merge
an older commit; try finding the commit ID for the dist-git conversion on
the master branch, and on the F-13 branch, git merge COMMITID followed by
git merge master
--
Michel Alexandre Salim
Fedora Project Contributor: http://fedoraproject.org/
() ascii ribbon campaign - against html e-mail
/ www.asciiribbon.org - against proprietary attachments
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
09-17-2010, 07:58 PM
Jesse Keating
yet another git problem
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09/16/2010 07:21 AM, Neal Becker wrote:
> Updating igraph to 0.5.4. Success for devel and f14. Then for f13 I get:
>
>> fedpkg switch-branch f13
> Branch f13 set up to track remote branch f13/master from origin.
>
>> git merge master
> CONFLICT (rename/delete): Rename .cvsignore->.gitignore in HEAD and deleted
> in master
> Automatic merge failed; fix conflicts and then commit the result.
>
> Strange, that seems to be the same thing I did for f14. How do I fix?
>
- From testing here, I think you can just do:
git add .gitignore
git commit
then your merge will complete.
- --
Jesse Keating RHCE (http://jkeating.livejournal.com)
Fedora Project (http://fedoraproject.org/wiki/JesseKeating)
GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub)
identi.ca (http://identi.ca/jkeating)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
yet another git problem
