Re: Problem with mercurial 2.1
2012/3/28 Stefan Bodewig : > On 2012-03-18, Konstantin Kolinko wrote: > >> 2012/3/16 Stefan Bodewig : >>> Hi, > >>> maybe somebody with more experience with hg than myself can help. > >>> With the upgrade of the the FreeBSD jail gump is now using Mercurial 2.1 >>> there. Since them most if not all hg updates are failing. The reason >>> is (quoting "hg help pull") > >>> , >>> | Returns 0 on success, 1 if no changes found or an update had >>> unresolved >>> | files. >>> ` > >>> so Gump can no longer tell a "pull" that didn't change anything from one >>> that failed (I'm sure there is an explanation why mixing "nothing to do" >>> with "things have failed" is not silly). > >> Searching about this issue, I see that people say that the old >> behaviour was restored in Mercurial 2.1.1 (released 2012-03-01). > > Thanks, I didn't search myself. > >>> (...) > I don't have any idea if/when FreeBSD may update hg. > Just searching Ports catalog at freebsd.org, http://www.freebsd.org/cgi/ports.cgi?query=^mercurial-2.1.1&stype=name shows that 2.1.1 does exist and apparently was released just today (March 28). (Well, I do not know much about FreeBSD, so no clue whether this can be used as is, or how long you'd have to wait. Just some good news). Best regards, Konstantin Kolinko - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Problem with mercurial 2.1
On 2012-03-18, Konstantin Kolinko wrote: > 2012/3/16 Stefan Bodewig : >> Hi, >> maybe somebody with more experience with hg than myself can help. >> With the upgrade of the the FreeBSD jail gump is now using Mercurial 2.1 >> there. Since them most if not all hg updates are failing. The reason >> is (quoting "hg help pull") >> , >> | Returns 0 on success, 1 if no changes found or an update had unresolved >> | files. >> ` >> so Gump can no longer tell a "pull" that didn't change anything from one >> that failed (I'm sure there is an explanation why mixing "nothing to do" >> with "things have failed" is not silly). > Searching about this issue, I see that people say that the old > behaviour was restored in Mercurial 2.1.1 (released 2012-03-01). Thanks, I didn't search myself. >> Does anybody see any way to make hg support work without making it a >> two-step process of running "hg incoming" first and only run "pull" if >> that returned 0? > Maybe wrap "hg pull" with some script and examine what last line of > its output says. People say that it is localized, but you can know > what language your FreeBSD instance uses. Or just ignore the return > code for now - until you can install 2.1.1. Current trunk now runs "hg incoming" and only runs "hg pull" if there are any changes. This isn't ideal as "hg incoming" doesn't really differentiate between "no updates" and "error" either, but parsing the message didn't look like a clean solution either. I don't have any idea if/when FreeBSD may update hg. Thanks Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Problem with mercurial 2.1
2012/3/16 Stefan Bodewig : > Hi, > > maybe somebody with more experience with hg than myself can help. > > With the upgrade of the the FreeBSD jail gump is now using Mercurial 2.1 > there. Since them most if not all hg updates are failing. The reason > is (quoting "hg help pull") > > , > | Returns 0 on success, 1 if no changes found or an update had unresolved > | files. > ` > > so Gump can no longer tell a "pull" that didn't change anything from one > that failed (I'm sure there is an explanation why mixing "nothing to do" > with "things have failed" is not silly). Searching about this issue, I see that people say that the old behaviour was restored in Mercurial 2.1.1 (released 2012-03-01). [1] http://stackoverflow.com/questions/9410140/mercurial-2-1-how-can-i-use-pull-incoming-without-getting-return-code-1-when-th [2] http://mercurial.selenic.com/wiki/UpgradeNotes [3] http://selenic.com/pipermail/mercurial-devel/2012-February/037986.html > > Does anybody see any way to make hg support work without making it a > two-step process of running "hg incoming" first and only run "pull" if > that returned 0? > Maybe wrap "hg pull" with some script and examine what last line of its output says. People say that it is localized, but you can know what language your FreeBSD instance uses. Or just ignore the return code for now - until you can install 2.1.1. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Problem with mercurial 2.1
Hi, maybe somebody with more experience with hg than myself can help. With the upgrade of the the FreeBSD jail gump is now using Mercurial 2.1 there. Since them most if not all hg updates are failing. The reason is (quoting "hg help pull") , | Returns 0 on success, 1 if no changes found or an update had unresolved | files. ` so Gump can no longer tell a "pull" that didn't change anything from one that failed (I'm sure there is an explanation why mixing "nothing to do" with "things have failed" is not silly). Does anybody see any way to make hg support work without making it a two-step process of running "hg incoming" first and only run "pull" if that returned 0? Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
