Re: Beancount issues

On Fri, May 22, 2020 at 5:27 AM Kirill Goncharov wrote: > Thanks! I successfuly transferred the repo: > https://github.com/beancount/docs > Documentation site is at https://beancount.github.io/docs/ > > Now we need to change site url in repo description ( > https://github.com/beancount/docs). I g

Re: Beancount issues

Thanks! I successfuly transferred the repo: https://github.com/beancount/docs Documentation site is at https://beancount.github.io/docs/ Now we need to change site url in repo description (https://github.com/beancount/docs). I guess it requires admin privileges. Contributions page also needs an

Re: Beancount issues

On Wed, May 20, 2020 at 3:45 PM Kirill Goncharov wrote: > If you'd prefer to move it (I didn't know it was possible to move a repo >> across users) you can wait, if I have Owner ACLs I'd be happy to make that >> happen. >> > > Yes, I would prefer transfer as it preserves issues, watchers and star

Re: Beancount issues

Hi Martin, thanks for the direct CC. I'm happy that the migration is happening :) On Thu, May 21, 2020 at 12:41:22AM -0400, Martin Blais wrote: - Dominik Aumayr created the github.com/beancount/beancount repository originally and gave me admin rights. While I'm able to pull the output of a fre

Re: Beancount issues

On Wed, May 20, 2020 at 6:04 PM Martin Blais wrote: > On Tue, May 19, 2020 at 9:56 AM Martin Blais wrote: > >> On Tue, May 19, 2020 at 5:28 AM Martin Michlmayr wrote: >> >>> * Martin Blais [2020-05-18 04:24]: >>> > Martin: Did you want to go beyond this and create a mapping? >>> >>> I have a m

Re: Beancount issues

On Tue, May 19, 2020 at 9:56 AM Martin Blais wrote: > On Tue, May 19, 2020 at 5:28 AM Martin Michlmayr wrote: > >> * Martin Blais [2020-05-18 04:24]: >> > Martin: Did you want to go beyond this and create a mapping? >> >> I have a mapping now for some users. For quite a few people I cannot >>

Re: Beancount issues

> > If you'd prefer to move it (I didn't know it was possible to move a repo > across users) you can wait, if I have Owner ACLs I'd be happy to make that > happen. > Yes, I would prefer transfer as it preserves issues, watchers and stars. Let's wait for Dominik's response. Strange. Maybe ther

Re: Beancount issues

On Wed, May 20, 2020 at 2:35 PM Kirill Goncharov wrote: > I'd love for you to move that repo under "http://github.com/beancount/docs"; >> if you don't mind, that would be ideal. >> > > Sure, I'll rename it. > > According to the GitHub documentation >

Re: Beancount issues

> > I'd love for you to move that repo under "http://github.com/beancount/docs"; > if you don't mind, that would be ideal. > Sure, I'll rename it. According to the GitHub documentation , I need a permissi

Re: Beancount issues

On Wed, May 20, 2020 at 6:34 AM Kirill Goncharov wrote: > >After I refresh the code and migrate the tickets, I'd love to integrate > Kirill's .md docs > > How would you like to do that? > > I think it's better to keep the parser and resulting markdown files in a > separate repo unless there's a c

Re: Beancount issues

>After I refresh the code and migrate the tickets, I'd love to integrate Kirill's .md docs How would you like to do that? I think it's better to keep the parser and resulting markdown files in a separate repo unless there's a compelling reason to do otherwise, as this allows frequent updates (

Re: Beancount issues

On Tue, May 19, 2020 at 5:28 AM Martin Michlmayr wrote: > * Martin Blais [2020-05-18 04:24]: > > Martin: Did you want to go beyond this and create a mapping? > > I have a mapping now for some users. For quite a few people I cannot > find a mapping. I think once we've done the migration, we can

Re: Beancount issues

* Martin Blais [2020-05-18 04:24]: > Martin: Did you want to go beyond this and create a mapping? I have a mapping now for some users. For quite a few people I cannot find a mapping. I think once we've done the migration, we can update the BitBucket issues and let them know about the move to Gi

Re: Beancount issues

* Martin Blais [2020-05-18 04:24]: > It's a bummer the author of all tickets ends up being who runs the script, Unfortunately the GitHub API doesn't allow setting the submitter. I ran into the same issue with the ledger migration from Bugzilla. > but we can live with that and manually Cc the git

Re: Beancount issues

* Kirill Goncharov [2020-05-18 01:43]: > But then Martin Michlmayr suggested to create a mapping manually, I > think it's a good approach too. I can take a look tomorrow. -- Martin Michlmayr https://www.cyrius.com/ -- You received this message because you are subscribed to the Google Groups

Re: Beancount issues

>I see you have your own fork. In some cases the script creates invalid markup, for example here: https://github.com/xuhcc/beancount/issues/428 I looked into the code and found that it all comes down to account matching procedure and it's hard to do it right automatically, so I re

Re: Beancount issues

Sorry I lost that thread. I just pulled it up now and looked at the tickets, looks very nice indeed, thanks for this test run Kirill. Did you do anything beyond running https://github.com/jeffwidman/bitbucket-issue-migration? I see you have your own fork. It's a bummer the author of all tickets en

Re: Beancount issues

Hello, As everybody I'm ready to help with anything for the migration. And I would like to vote (I know that is not a voting decision but anyway) for Github first and Gitlab second. I think is going to be easier to work all together later even if we loss some information in the migration. Re

Re: Beancount issues

As anticipated a couple of weeks ago, the folks at Heptapod ran a test migration of beancount from Bitbucket to their Gitlab-like platform with Mercurial support. It looks good at a first glance. Currently the bitbucket project on Heptapod is in private mode, but we can switch it to public any tim

Re: Beancount issues

* Kirill Goncharov [2020-04-26 07:02]: > I think we can simply remove profile links and keep only a reference to > original issue with a display name: I kinda like the original links. > This kind of username matching is not reliable anyway I can work on a mapping of user names. -- Martin Mich

Re: Beancount issues

> > Kirill: in some tickets the Markdown or something seems broken, e.g. > https://github.com/xuhcc/beancount/issues/428 > I think we can simply remove profile links and keep only a reference to original issue with a display name: https://github.com/xuhcc/bitbucket-issue-migr

Re: Beancount issues

* Kirill Goncharov [2020-04-26 05:49]: > Just tried this issue migration tool: > https://github.com/jeffwidman/bitbucket-issue-migration > > Here's the result: https://github.com/xuhcc/beancount/issues Thanks so much for doing this! I was going to do a test migration but I&#

Re: Beancount issues

Just tried this issue migration tool: https://github.com/jeffwidman/bitbucket-issue-migration Here's the result: https://github.com/xuhcc/beancount/issues And Gitlab apparently has a pretty good built-in importer: https://docs.gitlab.com/ee/user/project/import/bitbucket.html (Regardin

Re: Beancount issues

On Sat, Apr 25, 2020 at 7:22 PM Red S wrote: > Hi Martin, > Okay, good to know, and no rush. > > As others suggested, please do feel free to lean on this community for > anything we can assist you with. If you want help with testing the handful > of bitbucket-to-github solutions that exist, for i

Re: Beancount issues

Hi Martin, Okay, good to know, and no rush. As others suggested, please do feel free to lean on this community for anything we can assist you with. If you want help with testing the handful of bitbucket-to-github solutions that exist, for instance, do let us know. I'm sure several of us would b

Re: Beancount issues

Nothing changed. I'm too busy to deal with it, a few weeks ago I was set to move the whole thing to github manually but now it looks like there's a bunch of easier solutions are coming around (converters to github that will also import issues, heptapod to stick with mercurial, etc.). Atlassian also

Re: Beancount issues

On Sat, Mar 28, 2020 at 03:10:52PM -0400, Martin Blais wrote: > I had ruled out Heptapod as it seemed to have only a few projects it > itself owned just even last week (and now I see the list growing, so it's > morphing into a hosting solution). Looks like this has been made official now: https

Re: Beancount issues

Just curious: is https://bitbucket.org/blais/beancount/src/default/ still the official repo? I can still seem to check out from it. Is mercurial on bitbucket going to remain alive? -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe fr

Re: Beancount issues

Hi Martin, Sure. I didn't want to force your hand one way or the other (although, if you decide to move to git, I would prefer Gitlab over GitHub). I was just investigating what it would take to migrate to Heptapod. I didn't expect things to move so quickly. Cheers, Dan On 28/03/2020 13:10, Mar

Re: Beancount issues

Thank you Daniele. Just as I had pretty much decided to give in to the Github... I had ruled out Heptapod as it seemed to have only a few projects it itself owned just even last week (and now I see the list growing, so it's morphing into a hosting solution). Let me think about this a bit more. O

Re: Beancount issues

On 27/03/2020 12:11, Daniele Nicolodi wrote: > To further explore this possibility, I went ahead and filled a hosting > request ticket on https://foss.heptapod.net > > https://foss.heptapod.net/heptapod/foss.heptapod.net/issues/49 > > The only requirement on the project, other than being released

Re: Beancount issues

On 23/03/2020 02:30, Stefano Zacchiroli wrote: > On Sun, Mar 22, 2020 at 10:06:01PM -0400, Martin Blais wrote: >> Ahh yes, now I know why. It's just the software, it's not hosting. >> I need a hosted solution. > > They do hosting too. The only restriction is that the project should be > under a FO

Re: Beancount issues

On Sun, Mar 22, 2020 at 10:06:01PM -0400, Martin Blais wrote: > Ahh yes, now I know why. It's just the software, it's not hosting. > I need a hosted solution. They do hosting too. The only restriction is that the project should be under a FOSS license, which is the case for Beancount. I think you

Re: Beancount issues

On Sun, Mar 22, 2020 at 8:48 PM Martin Blais wrote: > Kirill: Thanks, I managed to re-export from scratch using git-remote-log. > Despite this being a completely separate export, it did manage to update > the github.com/beancount/beancount repo, so it must be using stable > hashes or some other w

Re: Beancount issues

Kirill: Thanks, I managed to re-export from scratch using git-remote-log. Despite this being a completely separate export, it did manage to update the github.com/beancount/beancount repo, so it must be using stable hashes or some other way to avoid allocating new hashes when exporting (which is gre

Re: Beancount issues

On Sun, Mar 22, 2020 at 01:58:53PM -0400, Martin Blais wrote: > So either I find another Hg hosting (doesn't seem to be anything foss > friendly with issue tracking out there I feel confident about), or try > a move to github. It's known™ that I'd personally favor a move to a git-based hosting. Bu

Re: Beancount issues

On Sun, Mar 22, 2020 at 1:20 PM Stefano Zacchiroli wrote: > On Sun, Mar 22, 2020 at 01:05:20PM -0400, Martin Blais wrote: > > I just attempted to update the github mirror now and it fails again. > > I'm spending more time fixing this up than I have, I just can't, have to > > figure out trades for

Re: Beancount issues

I just updated my github mirror with your latest commit: https://github.com/xuhcc/beancount/commits/master The tool that I'm using is git-remote-hg (https://github.com/mnauw/git-remote-hg). It allows both pull and push operations to remote mercurial repos, but local repo needs to be in git form

Re: Beancount issues

On Sun, Mar 22, 2020 at 01:05:20PM -0400, Martin Blais wrote: > I just attempted to update the github mirror now and it fails again. > I'm spending more time fixing this up than I have, I just can't, have to > figure out trades for tomorrow's session > I'd contemplate switching over if I knew it wa

Re: Beancount issues

I just attempted to update the github mirror now and it fails again. I'm spending more time fixing this up than I have, I just can't, have to figure out trades for tomorrow's session I'd contemplate switching over if I knew it was possible to switch back (demonstrated) without losing any data On

Re: Beancount issues

We already hvae a github repo here: https://github.com/beancount/beancount It's just not up-to-date because I don't use it, and sync'ing fails regularly (and I don't have time to fix it) On Sun, Mar 22, 2020 at 12:04 PM Martin Michlmayr wrote: > * Uwe Ziegenhagen [2020-03-22 16:26]: > > If you

Re: Beancount issues

* Uwe Ziegenhagen [2020-03-22 16:26]: > If you have the issues in a readable format ask us, your followers, to > import them. I am sure some of us have plenty of time now. :-( https://github.com/jeffwidman/bitbucket-issue-migration And someone already said he created a Git repo. -- Martin Mich

Re: Beancount issues

; I've quickly archived all the Beancount issues and the repo in prevision > of the Mercurial shutdown next week. > New changes will be lost. > It's possible to reimport them into another Mercurial project I think, > that's the easiest avenue. > I still need to figure out

Re: Beancount issues

. :-( Uwe Am So., 22. März 2020 um 16:21 Uhr schrieb Martin Blais : > I've quickly archived all the Beancount issues and the repo in prevision > of the Mercurial shutdown next week. > New changes will be lost. > It's possible to reimport them into another Mercurial project I think

Beancount issues

I've quickly archived all the Beancount issues and the repo in prevision of the Mercurial shutdown next week. New changes will be lost. It's possible to reimport them into another Mercurial project I think, that's the easiest avenue. I still need to figure out where this is all goin