debian-haskell October 2008

debian-haskell@lists.urchin.earth.li

11 participants
14 discussions

debian-haskell@lists.debian.org now live!
by John Goerzen 04 Nov '08

04 Nov '08

Hi folks, The debian-haskell(a)lists.debian.org list is now live! WOOHOO! You can subscribe by sending an email to debian-haskell-request(a)lists.debian.org. Put SUBSCRIBE in the subject. Ian (or whoever maintains this list) -- are you interested in moving subscriber lists and archives over? Whoever maintains http://urchin.earth.li/~ian/haskell-policy/haskell-policy.html/index.html#c… (ian?) should also update the mailing list info there. Thanks! -- John ----- Forwarded message from Debian Bug Tracking System <owner(a)bugs.debian.org> ----- From: Debian Bug Tracking System <owner(a)bugs.debian.org> Date: Sat, 04 Oct 2008 20:33:03 +0000 Reply-To: 488418(a)bugs.debian.org To: John Goerzen <jgoerzen(a)complete.org> Subject: Bug#488418 closed by "David Moreno" <david(a)axiombox.com> (debian-haskell mailing list created) This is an automatic notification regarding your Bug report which was filed against the lists.debian.org package: #488418: Request debian-haskell(a)lists.debian.org list It has been closed by "David Moreno" <david(a)axiombox.com>. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact "David Moreno" <david(a)axiombox.com> by replying to this email. -- 488418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=488418 Debian Bug Tracking System Contact owner(a)bugs.debian.org with problems From: David Moreno <david(a)axiombox.com> Date: Sat, 4 Oct 2008 16:29:57 -0400 To: 488418-done(a)bugs.debian.org, debian-haskell(a)lists.debian.org Subject: debian-haskell mailing list created Hello, the debian-haskell mailing list has been created now. -- Big D. * http://damog.net/ * http://axiombox.com/ From: John Goerzen <jgoerzen(a)complete.org> Date: Sat, 28 Jun 2008 13:36:25 -0500 To: Debian Bug Tracking System <submit(a)bugs.debian.org> Subject: Request debian-haskell(a)lists.debian.org list Package: lists.debian.org Severity: normal Hi, I would like to request the creation of a debian-haskell(a)lists.debian.org mailing list, for the purposes of coordinating Haskell-related development activities. The Debian Haskell community has been using an unofficial mailing list [1] since 2004 already, and we would like to move to an official list at this time. [1] http://urchin.earth.li/~ian/haskell-policy/haskell-policy.html/ch-introduct… -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (99, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash ----- End forwarded message -----

4 6

Version problems
by Magnus Therning 30 Oct '08

30 Oct '08

Am I right in believing that missingh requires a recompilation against the version of hslogger currently in sid will solve this? Sample code: import Data.ConfigFile import Control.Monad import Data.Either.Utils test = do conf <- liftM forceEither $ readfile emptyCP "./text.conf" return $ sections conf GHCi: Prelude> :load Test.hs [1 of 1] Compiling Test ( Test.hs, interpreted ) Ok, modules loaded: Test. *Test> test Loading package array-0.1.0.0 ... linking ... done. Loading package containers-0.1.0.1 ... linking ... done. Loading package bytestring-0.9.0.1 ... linking ... done. Loading package mtl-1.1.0.0 ... linking ... done. Loading package regex-base-0.93.1 ... linking ... done. Loading package regex-posix-0.93.1 ... linking ... done. Loading package regex-compat-0.91 ... linking ... done. Loading package parsec-2.1.0.0 ... linking ... done. Loading package old-locale-1.0.0.0 ... linking ... done. Loading package old-time-1.0.0.0 ... linking ... done. Loading package filepath-1.1.0.0 ... linking ... done. Loading package directory-1.0.0.0 ... linking ... done. Loading package random-1.0.0.0 ... linking ... done. Loading package unix-2.3.0.0 ... linking ... done. Loading package process-1.0.0.0 ... linking ... done. Loading package network-2.1.0.0 ... linking ... done. Loading package haskell98 ... linking ... done. Loading package HUnit-1.2.0.0 ... linking ... done. Loading package QuickCheck-1.1.0.0 ... linking ... done. unknown package: hslogger-1.0.5 % dpkg -l \*hslogger\* ii libghc6-hslogger-dev 1.0.6.1 The Haskell Logging Framework, GHC package /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus＠therning．org http://therning.org/magnus identi.ca|twitter: magthe

1 3

Best way to package Haskell package for Debian?
by Magnus Therning 07 Oct '08

07 Oct '08

Has a best way for packaging Haskell packages (modules, not binaries) for Debian crystallised yet? I'd like to make sure I'm following all the rules to better my chances of actually getting the package into Sid in the end. What's available that will help me in this regard? /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus＠therning．org http://therning.org/magnus Haskell is an even 'redder' pill than Lisp or Scheme. -- PaulPotts

2 3

Re: [Debian-haskell] Debian support for Haskell
by Ian Lynagh 06 Oct '08

06 Oct '08

Hi Norman, On Mon, Sep 29, 2008 at 11:16:56PM -0400, Norman Ramsey wrote: > > Have you any suggestions who I could try to recruit as a Debian maintainer > who could put up a package that would have a /usr/bin/cabal binary > in it, so as to make it a little easier for Debian and Ubuntu to > get started with hackage.haskell.org? I'm CCing the Debian/Haskell list; anyone up for this? Debian will need it pretty soon anyway to qualify for the "Haskell Platform" seal of approval :-) (I think you have to be subscribed to the list in order to post, incidentally) Thanks Ian

3 5

How to get haddock 2 into Debian
by Joachim Breitner 05 Oct '08

05 Oct '08

Hi, I’d like to bring up http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464364 again, because haddock 2 has some features I’d really like to see. From what I’m reading in http://www.haskell.org/pipermail/cvs-ghc/2008-June/042779.html haddock 2 can only work on files that were compiled with the version of ghc that haddock was compiled with itself. Is that right? The problem is then that during the build of a new ghc6 source (which includes building the docs for that), the old haddock used to build documentation, which then fails. Is that right as well? What solutions are possible? I can think of: 1. Including haddock in the ghc6 source. 2. Not building the ghc6 docs during the ghc6 build, but from a separate source file, so that ghc6 can be built, then a new haddock version, and then the docs for everything. 3. Ignoring haddock errors in the ghc6 build process, and re-building the ghc6 packages after haddock has built against the new ghc6 (assuming that the internal GHC version does not change just by re-building ghc). 4. Finding a way for haddock to work independent of the ghc6 that has built the files. Anything that we can rule out? Anything that sounds reasonable? I’m no expert in this matter, so I’d like to hear your opinion. Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nomeata(a)debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nomeata(a)joachim-breitner.de | http://people.debian.org/~nomeata

3 4

cabal-1.4 and terminfo
by Marco Túlio Gontijo e Silva 04 Oct '08

04 Oct '08

Hi. I've made a package for cabal-1.4[0] and another[1] version for terminfo. The old one wasn't registering itself. Sorry about that. Joachim, could you upload them please? Greetings. 0: http://marcot.iaaeee.org/cabal-1.4/ 1: http://marcot.iaaeee.org/terminfo/ -- marcot Página: http://marcotmarcot.iaaeee.org/ Blog: http://marcotmarcot.blogspot.com/ Correio: marcot(a)riseup.net XMPP: marcot(a)jabber.org IRC: marcot(a)irc.freenode.net Telefone: 25151920 Celular: 98116720 Endereço: Rua Turfa, 639/701 Prado 30410-370 Belo Horizonte/MG Brasil

2 1

Bug#501031: ITP: haskell-cabal-1.4 -- A framework for packaging Haskell software
by Marco Túlio Gontijo e Silva 04 Oct '08

04 Oct '08

Package: wnpp Severity: wishlist Owner: "Marco Túlio Gontijo e Silva" <marcot(a)riseup.net> * Package name : haskell-cabal-1.4 Version : 1.4.0.2 Upstream Author : Isaac Jones <ijones(a)syntaxpolice.org>, Duncan Coutts <duncan(a)haskell.org> * URL : http://www.haskell.org/cabal/ * License : BSD Programming Lang: Haskell Description : A framework for packaging Haskell software The Haskell Common Architecture for Building Applications and Libraries: a framework defining a common interface for authors to more easily build their Haskell applications in a portable way. The Haskell Cabal is meant to be a part of a larger infrastructure for distributing, organizing, and cataloging Haskell libraries and tools. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64)

2 1

haskell-zlib
by Marco Túlio Gontijo e Silva 03 Oct '08

03 Oct '08

Hello, I've packaged zlib. It's available at: http://mentors.debian.net/debian/pool/main/h/haskell-zlib/ . Joachim, could you upload it? Greetings. -- marcot Página: http://marcotmarcot.iaaeee.org/ Blog: http://marcotmarcot.blogspot.com/ Correio: marcot(a)riseup.net XMPP: marcot(a)jabber.org IRC: marcot(a)irc.freenode.net Telefone: 25151920 Celular: 98116720 Endereço: Rua Turfa, 639/701 Prado 30410-370 Belo Horizonte/MG Brasil

1 1

Package name in Haskell Utils
by Marco Túlio Gontijo e Silva 03 Oct '08

03 Oct '08

Hello, I noticed that haskell-utils looks in two places to get the package name. update-haskell-control uses the cabal package name and scripts/10/rules uses the information from changelog. I like the idea of querying the cabal name, but I think they should both get it from just one place, to avoid: dpkg-source -b Cabal-1.4.0.2 dpkg-source: error: source package has two conflicting values - haskell-cabal and haskell-cabal-1.4 dpkg-buildpackage: failure: dpkg-source -b Cabal-1.4.0.2 gave error exit status 255 I know this case is not standard and in cases like this I could edit the generated debian/control file, but still I don't see any reason for getting the package name from two different places. What do you think about it? Greetings. -- marcot Página: http://marcotmarcot.iaaeee.org/ Blog: http://marcotmarcot.blogspot.com/ Correio: marcot(a)riseup.net XMPP: marcot(a)jabber.org IRC: marcot(a)irc.freenode.net Telefone: 25151920 Celular: 98116720 Endereço: Rua Turfa, 639/701 Prado 30410-370 Belo Horizonte/MG Brasil

1 1

hashes as dependencies
by Joachim Breitner 03 Oct '08

03 Oct '08

Following up to the list, as it is of general interest. Am Donnerstag, den 02.10.2008, 18:15 -0300 schrieb Marco Túlio Gontijo e Silva: > Op donderdag 02-10-2008 om 21:43 uur [tijdzone +0200], schreef Joachim > Breitner: > > BTW, what do you think of my proposal about making haskell dependencies > > depend on virtual packages that contain a hash of the *.hi files? > > I confess at that time I couldn't understand very well what was being > discussed, so I didn't followed the thread, assuming that my Debian > knowledge was not enough for it. I read it again today, and I think > it's a good idea. The only thing I don't get is how the broken packages > are going to be rebuild automatically. By scheduling binNMUs in a semi-automatic fashion: We would a script that lists all packages that need to be re-build, and we pass that information to the guys on debian-release. > I think the main thing that > would change in this idea is the haskell-utils package, which I was > working on to maintain. I've done a version[0], but maybe it worth to > work on a version that already supports this, and apply the changes I've > made in this new version. > > Actually, this would be a big change in the Haskell package system, so > maybe it could be done with the creation of the haskell team, so that we > could maintain these packages together. What do you think? Yes, a packaging team would be useful, but it needs someone to take the lead (e.g. setting up the alioth group, choosing and setting up a VCS etc.) If we do such a big change, we should also use it to consolidate some of the packaging utilities around. For example, haskell-utils could use the dh scripts from haskell-devscripts where appropriate and drop some code, or maybe one of the two could be abandoned for the other completely. I still haven’t seen Arjan comment on the idea with the interface hashes: Would you support such a change in the Haskell Packaging Policy? Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nomeata(a)debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nomeata(a)joachim-breitner.de | http://people.debian.org/~nomeata

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

debian-haskell October 2008