bug#36084: ghc-tasty/ghc-clock circular dependency breaking is broken

Hi, Robert Vollmert writes: >> On 16. Jul 2019, at 17:08, Timothy Sample wrote: >> >> Hi Robert, >> >> After looking at this and your patch at , >> I’m wondering if it works as long as we make sure the versions match. >> Can we just inherit the current

bug#36084: ghc-tasty/ghc-clock circular dependency breaking is broken

> On 16. Jul 2019, at 17:08, Timothy Sample wrote: > > Hi Robert, > > After looking at this and your patch at , > I’m wondering if it works as long as we make sure the versions match. > Can we just inherit the current “ghc-clock”, disable its tests, and call > it

bug#36084: ghc-tasty/ghc-clock circular dependency breaking is broken

Hi Robert, Robert Vollmert writes: > ghc-tasty depends via “inputs” on ghc-clock-bootstrap (v0.5) which is built > without tests, > while ghc-clock (v0.7) depends via “native-inputs” on ghc-tasty for tests. > > This means that any package which depends on ghc-tasty and ghc-clock is >

bug#36084: ghc-tasty/ghc-clock circular dependency breaking is broken

ghc-tasty depends via “inputs” on ghc-clock-bootstrap (v0.5) which is built without tests, while ghc-clock (v0.7) depends via “native-inputs” on ghc-tasty for tests. This means that any package which depends on ghc-tasty and ghc-clock is potentially broken, e.g.: Warning: This package