9front - general discussion about 9front
 help / color / mirror / Atom feed
* Re: [9front] bug: hg pull fails on a bitbucket repo
@ 2018-11-28 20:40 cinap_lenrek
  2018-11-28 21:05 ` Nick Owens
  0 siblings, 1 reply; 11+ messages in thread
From: cinap_lenrek @ 2018-11-28 20:40 UTC (permalink / raw)
  To: 9front

noted.

on very low priority for me as i dont have much time and like
working on plan9 problems rather than python ones.

this would mostly consist of doing tons of testing to see
if there are any operational issues with the new python code.
not just cloning bitbucket repos but actually do commits, merge,
remove, add, diff ect... also wonder if our repo format is
still fully supported. as people will not manually nuke ther
/dist/.hg.

see if hg serve still works...

maybe add support for new repo formats to hgfs...

also, how big are the differences? have you diffed the python
code and can say how big the changes in mercurial are?

--
cinap


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [9front] bug: hg pull fails on a bitbucket repo
  2018-11-28 20:40 [9front] bug: hg pull fails on a bitbucket repo cinap_lenrek
@ 2018-11-28 21:05 ` Nick Owens
  2018-11-28 21:40   ` hiro
  0 siblings, 1 reply; 11+ messages in thread
From: Nick Owens @ 2018-11-28 21:05 UTC (permalink / raw)
  To: 9front

executing diffstat on linux against plan9front's copy and mercurial 3.4.1:

 114 files changed, 34938 insertions(+), 12458 deletions(-)

it is nice that mercurial 3.4.1 already works, but it would indeed be
quite some work to replace the system hg with it.

i suppose for now i can simply encourage people to install mercurial
3.4.1 and use it instead of the system hg.
On Wed, Nov 28, 2018 at 12:41 PM <cinap_lenrek@felloff.net> wrote:
>
> noted.
>
> on very low priority for me as i dont have much time and like
> working on plan9 problems rather than python ones.
>
> this would mostly consist of doing tons of testing to see
> if there are any operational issues with the new python code.
> not just cloning bitbucket repos but actually do commits, merge,
> remove, add, diff ect... also wonder if our repo format is
> still fully supported. as people will not manually nuke ther
> /dist/.hg.
>
> see if hg serve still works...
>
> maybe add support for new repo formats to hgfs...
>
> also, how big are the differences? have you diffed the python
> code and can say how big the changes in mercurial are?
>
> --
> cinap


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [9front] bug: hg pull fails on a bitbucket repo
  2018-11-28 21:05 ` Nick Owens
@ 2018-11-28 21:40   ` hiro
  2018-11-28 21:42     ` hiro
  0 siblings, 1 reply; 11+ messages in thread
From: hiro @ 2018-11-28 21:40 UTC (permalink / raw)
  To: 9front

why didn't you do diff between the mercurial 9front is BASED on and
mercurial 3.4.1 ?!
we already know there were tons of changes in 9front's copy. this is
thus worthless information.


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [9front] bug: hg pull fails on a bitbucket repo
  2018-11-28 21:40   ` hiro
@ 2018-11-28 21:42     ` hiro
  0 siblings, 0 replies; 11+ messages in thread
From: hiro @ 2018-11-28 21:42 UTC (permalink / raw)
  To: 9front

also, why should do you want to encourage people to install mercurial
3.4.1 ?


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [9front] bug: hg pull fails on a bitbucket repo
  2018-11-29  5:35           ` Kurt H Maier
@ 2018-11-29  9:49             ` hiro
  0 siblings, 0 replies; 11+ messages in thread
From: hiro @ 2018-11-29  9:49 UTC (permalink / raw)
  To: 9front

i want my money back, mischief. nontrivial myass


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [9front] bug: hg pull fails on a bitbucket repo
  2018-11-29  1:02         ` hiro
@ 2018-11-29  5:35           ` Kurt H Maier
  2018-11-29  9:49             ` hiro
  0 siblings, 1 reply; 11+ messages in thread
From: Kurt H Maier @ 2018-11-29  5:35 UTC (permalink / raw)
  To: 9front

On Thu, Nov 29, 2018 at 02:02:03AM +0100, hiro wrote:
> let's just wait 9 more years, perhaps bitbucket will stop supporting hg then.

there are three editions of bitbucket, and only one supports hg any
more. I'd say 9 years from now we'll definitely be on our own.  

khm


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [9front] bug: hg pull fails on a bitbucket repo
  2018-11-29  0:42       ` Nick Owens
@ 2018-11-29  1:02         ` hiro
  2018-11-29  5:35           ` Kurt H Maier
  0 siblings, 1 reply; 11+ messages in thread
From: hiro @ 2018-11-29  1:02 UTC (permalink / raw)
  To: 9front

let's just wait 9 more years, perhaps bitbucket will stop supporting hg then.


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [9front] bug: hg pull fails on a bitbucket repo
  2018-11-28 23:44     ` hiro
@ 2018-11-29  0:42       ` Nick Owens
  2018-11-29  1:02         ` hiro
  0 siblings, 1 reply; 11+ messages in thread
From: Nick Owens @ 2018-11-29  0:42 UTC (permalink / raw)
  To: 9front

our hg is approximately 9 years old. 3.4.1 is about 4 years old.

perhaps within another 5 years, more stuff will break. i and a
nontrivial amount of other people use bitbucket for mercurial hosting
and interact with it from 9front, so having it work reliably is pretty
desirable.
On Wed, Nov 28, 2018 at 3:44 PM hiro <23hiro@gmail.com> wrote:
>
> fucking hell, so 3.4.1 is also already multiple years old?!
>
> i doubt anybody would like to waste a week updating both python and hg.
> also: how often will this game need to be repeated in the future if we
> start with this now?


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [9front] bug: hg pull fails on a bitbucket repo
  2018-11-28 23:36   ` Nick Owens
@ 2018-11-28 23:44     ` hiro
  2018-11-29  0:42       ` Nick Owens
  0 siblings, 1 reply; 11+ messages in thread
From: hiro @ 2018-11-28 23:44 UTC (permalink / raw)
  To: 9front

fucking hell, so 3.4.1 is also already multiple years old?!

i doubt anybody would like to waste a week updating both python and hg.
also: how often will this game need to be repeated in the future if we
start with this now?


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [9front] bug: hg pull fails on a bitbucket repo
  2018-11-28 21:45 ` [9front] " hiro
@ 2018-11-28 23:36   ` Nick Owens
  2018-11-28 23:44     ` hiro
  0 siblings, 1 reply; 11+ messages in thread
From: Nick Owens @ 2018-11-28 23:36 UTC (permalink / raw)
  To: 9front

you'd want 3.4.1 if you want newer mercurial features, or want to
avoid this bug.

mercurial 3.4.1 was release before they axed python 2.5 support.


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [9front] bug: hg pull fails on a bitbucket repo
  2018-11-28 20:25 Nick Owens
@ 2018-11-28 21:45 ` hiro
  2018-11-28 23:36   ` Nick Owens
  0 siblings, 1 reply; 11+ messages in thread
From: hiro @ 2018-11-28 21:45 UTC (permalink / raw)
  To: 9front

> one caveat of updating to newer mercurial is that upstream dropped
> python 2.5 support some years ago.

so then how does your port work then?!


^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2018-11-29  9:49 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-11-28 20:40 [9front] bug: hg pull fails on a bitbucket repo cinap_lenrek
2018-11-28 21:05 ` Nick Owens
2018-11-28 21:40   ` hiro
2018-11-28 21:42     ` hiro
  -- strict thread matches above, loose matches on Subject: below --
2018-11-28 20:25 Nick Owens
2018-11-28 21:45 ` [9front] " hiro
2018-11-28 23:36   ` Nick Owens
2018-11-28 23:44     ` hiro
2018-11-29  0:42       ` Nick Owens
2018-11-29  1:02         ` hiro
2018-11-29  5:35           ` Kurt H Maier
2018-11-29  9:49             ` hiro

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).