Re: package-plan is failing (was: Request to Join Project pkg-haskell from Ilias Tsitsimpis (iliastsi-guest))
On Mon, May 09, 2016 at 11:46PM, Joachim Breitner wrote:
> Am Montag, den 09.05.2016, 23:01 +0300 schrieb Ilias Tsitsimpis:
> >
> > On Sun, May 08, 2016 at 11:53PM, Joachim Breitner wrote:
> > >
> > > welcome! Anything in particular you are interested in?
> > Thanks! I was thinking of starting with updating some existing packages,
> > in order to get myself familiar with the procedures and practices of the
> > team. I believe the haskell-language-python package (an update for which
> > was requests a few days ago in the irc channel) is a good candidate. I
> > have already tested it with package-plan and there doesn't seem to be
> > any integration errors. What do you think?
>
> If the package-plan is happy, then it is usually ok. There once was the
> plan to follow Stackage closely, but since the aeson issue, where
> Stackage downgraded, this has not be strictly followed. We should
> decide what do there.
I didn't know that, thanks for sharing. Following the Stackage closely
sounds good to me. That said, Stackage currently doesn't provide
language-python[1], so I will go ahead and update it.
When I tried to rerun the package-plan today, it failed. At first, I
thought it was me doing something wrong, but then package-plan also
broke in Jenkins[2]. I couldn't understand why as there were no new
commits on package-plan. It turns out that the propellor[3] package was
updated yesterday and it now uses the haskell-devscripts in order to
be built. This means that package-plan now recognizes the propellor
package as missing from the packages.txt file. As far as I can tell,
this is the first package maintained outside of DHG that uses the
haskell-devscripts. Do we add it to the packages.txt file?
Cheers,
Ilias
[1] https://www.stackage.org/package/language-python
[2] https://jenkins.debian.net/job/haskell-package-plan/1251/console
[3] https://packages.qa.debian.org/p/propellor/news/20160509T230020Z.html
Reply to: