
You can now find open issues here: https://github.com/haskell/cabal/issues?state=open Duncan or Andres, could one of you please chmod -w the files owned by Trac, and add a note pointing people to github for filing bugs?

Hi Bryan.
First of all, thanks. It looks great.
On Thu, May 24, 2012 at 8:14 AM, Bryan O'Sullivan
You can now find open issues here: https://github.com/haskell/cabal/issues?state=open
Duncan or Andres, could one of you please chmod -w the files owned by Trac, and add a note pointing people to github for filing bugs?
Sorry for noting this only once I go through the Wiki page. The difficulty level has not been converted? It's not terribly important, but we've used it in the past to point interested newcomers to supposedly "easy" tasks. If it's a lot of work to change now, then don't. But perhaps it could be done by just modifying the already converted tickets in one batch process and adding new tags? I have tried to delete ticket modification permissions for authenticated users in the trac. I'm hesitating to change the file permissions, as we'll probably still want to use the Wiki for now. I changed the pointers on the Trac main page and on haskell.org/cabal -- there are probably other references elsewhere. If you know of anything important that should be changed, please let me know. Cheers, Andres -- Andres Löh, Haskell Consultant Well-Typed LLP, http://www.well-typed.com

On Wed, May 23, 2012 at 11:43 PM, Andres Löh
Sorry for noting this only once I go through the Wiki page. The difficulty level has not been converted? It's not terribly important, but we've used it in the past to point interested newcomers to supposedly "easy" tasks.
I could do that, but it might be as fast to do it by hand as to write a script for the job.

On Thu, May 24, 2012 at 7:14 AM, Bryan O'Sullivan
You can now find open issues here: https://github.com/haskell/cabal/issues?state=open
Duncan or Andres, could one of you please chmod -w the files owned by Trac, and add a note pointing people to github for filing bugs?
_______________________________________________ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel
At least one of the ticket cross-references has gone wrong: https://github.com/haskell/cabal/issues/653 I refer to #719 in this ticket, which links to github issue #719, but that's Trac ticket #729. I wanted the ticket imported from Trac #719, i.e. this one https://github.com/haskell/cabal/issues/710

Hi Ben and Bryan.
At least one of the ticket cross-references has gone wrong:
https://github.com/haskell/cabal/issues/653
I refer to #719 in this ticket, which links to github issue #719, but that's Trac ticket #729. I wanted the ticket imported from Trac #719, i.e. this one https://github.com/haskell/cabal/issues/710
I can confirm that. I've checked a number of cross-references in cabal-install bugs, and afaics, they're all(?) wrong. Cheers, Andres -- Andres Löh, Haskell Consultant Well-Typed LLP, http://www.well-typed.com

On Fri, May 25, 2012 at 6:56 PM, Johan Tibell
On Fri, May 25, 2012 at 9:49 AM, Bryan O'Sullivan
wrote: Ugh. I'll see if I can find time to write a script to fix up the cross references.
Is the problem due to there already being some issue reports in the repo and thus all the Trac tickets got offset by some number?
My speculation would be that some Trac tickets don't exist because they have been deleted, and then these don't get converted, and this introduces an offset. Cheers, Andres -- Andres Löh, Haskell Consultant Well-Typed LLP, http://www.well-typed.com

On Fri, May 25, 2012 at 5:59 PM, Andres Löh
On Fri, May 25, 2012 at 6:56 PM, Johan Tibell
wrote: On Fri, May 25, 2012 at 9:49 AM, Bryan O'Sullivan
wrote: Ugh. I'll see if I can find time to write a script to fix up the cross references.
Is the problem due to there already being some issue reports in the repo and thus all the Trac tickets got offset by some number?
My speculation would be that some Trac tickets don't exist because they have been deleted, and then these don't get converted, and this introduces an offset.
Yeah, I think this is more likely, since it seems like not all of the cross-references are off by the same amount. github issue #719 is trac #729, but github issue #410 is trac #417.

On Sat, May 26, 2012 at 2:28 AM, Ben Millwood
Yeah, I think this is more likely, since it seems like not all of the cross-references are off by the same amount. github issue #719 is trac #729, but github issue #410 is trac #417.
I'll get around to fixing this at some point, but this is the second bug tracker migration I've done in the past few weeks, and I need a break :-)

On Fri, May 25, 2012 at 9:56 AM, Johan Tibell
Is the problem due to there already being some issue reports in the repo and thus all the Trac tickets got offset by some number?
Possibly. I thought I had some code in there to fix that up, but I guess it didn't do its thing.

On 23 May 2012 23:14, Bryan O'Sullivan
You can now find open issues here: https://github.com/haskell/cabal/issues?state=open
Haven't had time to look at it yet (on the road atm) but I just wanted to say a big thank you Bryan for all the hard work!
Duncan or Andres, could one of you please chmod -w the files owned by Trac, and add a note pointing people to github for filing bugs?
Will do when I get back (unless Andres beats me to it) Duncan
participants (5)
-
Andres Löh
-
Ben Millwood
-
Bryan O'Sullivan
-
Duncan Coutts
-
Johan Tibell