On 11/01/11 20:41, Peter Simons wrote:

Hi Magnus,

...

Are [cabal2arch and archlinux] in a state where new versions can be released right now?

only recently, Remy has added the "platform-provides.txt" feature to these tools, which constitutes a major change in behavior. It's best illustrated by looking at the diff that results from re-generating the hasktags package with the new tools: [...] Personally, I am a little scared by this feature, because the generated files are really quite different from what we used to distribute before. On the other hand, I can't think of a reason why these of ultra-explicit dependencies might cause trouble, so I tend to defer to Remy's expertise in this matter, who clearly though that this is a good idea.

It's always an option to put the release tag on a previous changeset if we don't want this in our HABS tree yet. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus

On Wed, Jan 12, 2011 at 14:46, Peter Simons wrote:

Hi guys,

I've re-generated all our PKGBUILDs using the latest version of the tool-chain. The Git repository for HABS is visible here:

                http://github.com/archhaskell/habs

One major change is that our PKGBUILDs now require very specific versions of those packages provided by Haskell Platform and GHC. It's likely that some people have obsolete packages installed in their system that will conflict with our required versions, so I'd expect some reports of broken builds to come in when the new versions go on-line.

I'm re-building the i686 binary repository as we speak, and so far things look good. I guess, the new binary packages are going to be available within the next 24 hours.

Are you uploading the source packages to AUR as well, or do you want me to do it?

As far as I'm concerned, this means that we can (and should) publish new releases of the ArchLinux library and of cabal2arch. I could probably do that tomorrow or so, but if anyone else would like to do the honors of tagging, assembling, and uploading those packages to Hackage, then please do!

I'll tag them up as follows: 0.7.7 - https://github.com/archhaskell/cabal2arch/commit/02f5bec78dfd415db8bca5215b7... 0.3.6 - https://github.com/archhaskell/archlinux/commit/b27f8e880fa884d03f2b26f79f3b... No changes to the CABAL files are necessary, only tagging in git. Is that all right? /M -- Magnus Therning                      OpenPGP: 0xAB4DFBA4 email: magnus@therning.org   jabber: magnus@therning.org twitter: magthe               http://therning.org/magnus

On Wed, Jan 12, 2011 at 16:08, Peter Simons wrote:

Hi Magnus,

 > Are you uploading the source packages to AUR as well, or do you want  > me to do it?

it would help me a lot if you could do it.

I'll upload a little later today.

 > I'll tag them up as follows:  >  > 0.7.7 - https://github.com/archhaskell/cabal2arch/commit/02f5bec78dfd415db8bca5215b7...  > 0.3.6 - https://github.com/archhaskell/archlinux/commit/b27f8e880fa884d03f2b26f79f3b...  >  > No changes to the CABAL files are necessary, only tagging in git.

Great, thank you very much!

Sure, the tags have been pushed. /M -- Magnus Therning                      OpenPGP: 0xAB4DFBA4 email: magnus@therning.org   jabber: magnus@therning.org twitter: magthe               http://therning.org/magnus

Hi Magnus,

They've all been uploaded to AUR.

I saw it. Thanks a lot!

Peter, I'm guessing you've already upgraded the i686 repo, right?

The build process took a while, but I've uploaded the new binaries to the server a few minutes ago. As far as I can tell, the Git repository, the binary repository, AUR, and the latest releases of the tool-chain are now in sync. :-) Take care, Peter