Where to raise an issue for the stm library

Can someone tell me where to raise an issue for the stm library? The hackage link sends me here http://git.haskell.org/packages/stm.git. But this page provides no clue on raising issues. I wondered if GHC trac itself is used for this library. I saw some other libraries in the drop down list but not this one in the GHC trac ticket creation page. It is frustrating that figuring out how to raise an issue is not easy for such an important library. -harendra

Hi Harendra,
I think STM issues are fine to report to GHC's trac (please someone else
chime in if this isn't the case):
https://ghc.haskell.org/trac/ghc/wiki/ReportABug
If that isn't the appropriate place it can get sorted out from there.
Ryan
On Fri, Aug 25, 2017 at 3:06 PM, Harendra Kumar
Can someone tell me where to raise an issue for the stm library? The hackage link sends me here http://git.haskell.org/packages/stm.git. But this page provides no clue on raising issues. I wondered if GHC trac itself is used for this library. I saw some other libraries in the drop down list but not this one in the GHC trac ticket creation page. It is frustrating that figuring out how to raise an issue is not easy for such an important library.
-harendra
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Ok. So I got the bug tracker link from the hackage page which I missed
earlier. It will be great if the source repo page as well has a link to the
bug tracker. I have never used the bug tracker link on hackage before
because I usually go to the package source page and it usually has the
issue tracker as well (e.g. for github repos). Also, it may be good to have
it as libraries/stm instead of libraries/other in the ghc trac ticket page.
-harendra
On 26 August 2017 at 00:36, Harendra Kumar
Can someone tell me where to raise an issue for the stm library? The hackage link sends me here http://git.haskell.org/packages/stm.git. But this page provides no clue on raising issues. I wondered if GHC trac itself is used for this library. I saw some other libraries in the drop down list but not this one in the GHC trac ticket creation page. It is frustrating that figuring out how to raise an issue is not easy for such an important library.
-harendra

BTW, this is the bug tracker link I got from the hackage
https://ghc.haskell.org/trac/ghc/newticket?component=libraries%20%28other%29&keywords=stm
.
On 26 August 2017 at 00:45, Harendra Kumar
Ok. So I got the bug tracker link from the hackage page which I missed earlier. It will be great if the source repo page as well has a link to the bug tracker. I have never used the bug tracker link on hackage before because I usually go to the package source page and it usually has the issue tracker as well (e.g. for github repos). Also, it may be good to have it as libraries/stm instead of libraries/other in the ghc trac ticket page.
-harendra
On 26 August 2017 at 00:36, Harendra Kumar
wrote: Can someone tell me where to raise an issue for the stm library? The hackage link sends me here http://git.haskell.org/packages/stm.git. But this page provides no clue on raising issues. I wondered if GHC trac itself is used for this library. I saw some other libraries in the drop down list but not this one in the GHC trac ticket creation page. It is frustrating that figuring out how to raise an issue is not easy for such an important library.
-harendra

Harendra Kumar
Ok. So I got the bug tracker link from the hackage page which I missed earlier. It will be great if the source repo page as well has a link to the bug tracker. I have never used the bug tracker link on hackage before because I usually go to the package source page and it usually has the issue tracker as well (e.g. for github repos). Also, it may be good to have it as libraries/stm instead of libraries/other in the ghc trac ticket page.
I've created a libraries/stm component; I'll update the stm library's cabal file accordingly. Cheers, - Ben

Thanks Ben! You rock!
On 26 August 2017 at 09:15, Ben Gamari
Harendra Kumar
writes: Ok. So I got the bug tracker link from the hackage page which I missed earlier. It will be great if the source repo page as well has a link to the bug tracker. I have never used the bug tracker link on hackage before because I usually go to the package source page and it usually has the issue tracker as well (e.g. for github repos). Also, it may be good to have it as libraries/stm instead of libraries/other in the ghc trac ticket page.
I've created a libraries/stm component; I'll update the stm library's cabal file accordingly.
Cheers,
- Ben
participants (3)
-
Ben Gamari
-
Harendra Kumar
-
Ryan Yates