[arch-haskell] Signed repos
On Fri, Dec 28, 2012 at 12:03:48PM +0100, Magnus Therning wrote: > On Fri, Dec 28, 2012 at 1:25 AM, Xyne wrote: >> Hi Magnus, >> >> Everything seems to be working as expected. Have you overcome the >> problems of ensuring a secure custody chain? > > I'm not quite satisfied with it, but just keeping a subkey for > signing on kiwilight (where I build), will have to do. > >> Also, could you send me a copy of the ArchHaskell key signed with >> your other key (0xAB4DFBA4)? > > Will do, as soon as I've signed the "real" repos. I've now signed the official repos, both x86_64 and i686. The signing will work whether you access it as [haskell] or [haskell-core]. I've also signed the database, which means the following kind of entry will now work: [haskell-core] SigLevel = Required TrustedOnly Server = http://www.kiwilight.com/haskell/core/$arch The key has been uploaded to the server hkp://pgp.mit.edu: 4209170B Oh, by the way, I've been putting up deltas for a while too, even though every delta seems to be larger than the original :) /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: mag...@therning.org jabber: mag...@therning.org twitter: magthe http://therning.org/magnus Perl is another example of filling a tiny, short-term need, and then being a real problem in the longer term. -- Alan Kay pgpgNNEGnkjIi.pgp Description: PGP signature ___ arch-haskell mailing list arch-hask...@haskell.org http://www.haskell.org/mailman/listinfo/arch-haskell
Re: [arch-haskell] [arch-general] Haskell Support Was: Xmonad version?
On Wed, Dec 21, 2011 at 06:00:02PM +0100, Fabio Riga wrote: > 2011/12/20 Magnus Therning > >> Den 20 dec 2011 04:58 skrev "Bernardo Barros" : >> >>> Arch is not a testing distro... And it's not even up to date with >>> Haskell Platform. If you want to "go faster them haskell platform" >>> you will need to work hard with packaging testing and this seems >>> NOT the case with Arch at the moment... >> >> I don't think it's quite that easy. AFAIU we'll soon have a choice >> to make, either stick to HP with an old version of GHC, or move to >> the latest stable GHC (7.4) and drop HP proper. >> >> Personally, I'm in favour of the latter. >> >> /M >> > *From Arch Linux About page:* > Arch strives to stay bleeding edge, and typically offers the latest stable > versions of most software. [...] > Arch Linux uses a "rolling release" system which allows one-time > installation and perpetual software upgrades. > ... and many other interesting feautres that made me love this distribution. > > Haskell Platform is not bleeding edge, it seems to follow a "old > versions are more stable" approach, more in the way of Debian. This > approach has is merits, but I prefer the "Arch way", so I vote for > dropping HP. > > Actually Ghc is not the problem. Most packages in hackage are > already builded with ghc-7.2, but 7.2 is testing, so we should use > 7.04. The problem are the other packages: for example every update > that depends upon * text* failed because in HP (until some days ago) > the version was too old. In a couple of months this package will be > too old again and will break other packages, unless we update > haskell packages twice a year. I think we all agree that GHC isn't the problem per se, it just created a very awkward situation when upstream decided that 7.2 (which based on the version number is stable) was a "tech preview". Lots of people just grabbed the latest release with a even version number and started using it. This is probably a good thing for upstream (lots of testing), but it isn't very good for packagers. It does mean that a lot of packages have recent releases that haven't been tested on 7.0, which does affect us. This situation is temporary though and I hope upstream realises what effects their decision had. I was in favour of switching to 7.2 despite it being a "tech preview". > IMHO, if cabal installs the latest available hackage, we sholud > simply do the same. As far as possible yes, there will always be dependencies that will make us lag at times, but without HP we won't have any upstream for libraries that are on a fixed release schedule. That will increase our chances of sticking close to the edge AFAICS. Dropping HP might have a big impact on [haskell] though. At the moment [extra]/[community] offers a stable base to build on, this will go away in the future. Every upgrade to [extra]/[community] has the potential to render [haskell] un-buildable. It will be interesting to see how well we can communicate to avoid that :-) It's still a net-win in my book though! /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: mag...@therning.org jabber: mag...@therning.org twitter: magthe http://therning.org/magnus Perl is another example of filling a tiny, short-term need, and then being a real problem in the longer term. -- Alan Kay pgp3lL8XPq39h.pgp Description: PGP signature ___ arch-haskell mailing list arch-hask...@haskell.org http://www.haskell.org/mailman/listinfo/arch-haskell
Re: [arch-haskell] Updating
On Fri, Nov 11, 2011 at 10:52:02PM +0100, Magnus Therning wrote:
> I'm currently removing a few gtk-related packages from [haskell] since
> these packages already exist in [community].
>
> Please hold off any modifications to the repo until I've finished
> doing this.
Done.
The following package were updated:
AttoJson
json-tools
gio
gconf
gtksourceview2
glade
Chart
timeplot
splot
sifflet-lib
sifflet
Due to the nature of this update you might have to re-install a few
packages just to make sure you get the ones from [community]. The
packages in question are
gtk2hs-buildtools
haskell-bytestring-show
haskell-cairo
haskell-glib
haskell-gtk
haskell-pango
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: mag...@therning.org jabber: mag...@therning.org
twitter: magthe http://therning.org/magnus
Perl is another example of filling a tiny, short-term need, and then
being a real problem in the longer term.
-- Alan Kay
pgpmr3zRtgxOA.pgp
Description: PGP signature
___
arch-haskell mailing list
arch-hask...@haskell.org
http://www.haskell.org/mailman/listinfo/arch-haskell
Re: [arch-haskell] Leksah depends on haddock which isn't listed in ghc-pkg
On Tue, May 10, 2011 at 13:30, Peter Simons wrote: > Hi Leif, > > > I was trying to add the IDE Leksah, and some of the parts have > > dependencies on specific versions of haddock. Haddock is provided by > > the ghc package, but it's not listed in ghc-pkg list. > > why would it be necessary for Haddock to be listed by ghc-pkg? The way I > see it, "cabal configure" should simply find Haddock in $PATH, no? Haddock (on Hackage) is both a program and a library. GHC doesn't include the library (only the program), and I'm guessing that's what is required. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: mag...@therning.org jabber: mag...@therning.org twitter: magthe http://therning.org/magnus ___ arch-haskell mailing list arch-hask...@haskell.org http://www.haskell.org/mailman/listinfo/arch-haskell
Re: [arch-haskell] What version of cabal2arch should be used to build HABS?
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: mag...@therning.org jabber: mag...@therning.org twitter: magthe http://therning.org/magnus signature.asc Description: OpenPGP digital signature ___ arch-haskell mailing list arch-hask...@haskell.org http://www.haskell.org/mailman/listinfo/arch-haskell
Re: [arch-haskell] State of Affairs: Summarizing 83 days worth of experience
On 11/01/11 11:27, Peter Simons wrote: >> Here's my "process" for updating packages on AUR: >> >> 1. Pull down any changes to my local copy of the HABS tree. >> 2. Open a clean chroot and bind-mount HABS and some personal tools into it. >> 3. Get the URL for the package that needs updating. >> 4. Run `cabal2arch ` in the HABS top-level. >> 5. Switch to the chroot and build the updated package and it's >>dependencies (I have a simple shell script that does this) >> 6. If the build fails, then revert the changes to the package in HABS. >> 7. Go back to 2 and update another package. >> 8. When no more packages need updating, build the source packages for >>all modified packages. >> 9. Use aurploader to upload the source packages to AUR. >> >> The problem with this is that step 5 can take a VERY long time, and >> sometimes I end up doing unnecessary work because there's no easy way of >> ordering the packages I'm updating such that the number of builds are >> minimised. > > In <http://github.com/peti/arch-haskell>, I have automated that entire > procedure so that boils down to running "make world". There is also a target > "make updates" that will identify and print out all available updates from > Hackage. Then I use "make publish" to upload the newly generated binary > repository to the kiwilight.com server. The target "make src" will generate > a whole bunch of taurballs that can be published on AUR using the aurupload > utility. The set of packages that is being built is determined by this file: > > http://github.com/peti/arch-haskell/blob/master/PKGLIST > > I hope this helps! Thanks, there are absolutely some stuff in there that I will find useful. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: mag...@therning.org jabber: mag...@therning.org twitter: magthe http://therning.org/magnus signature.asc Description: OpenPGP digital signature ___ arch-haskell mailing list arch-hask...@haskell.org http://www.haskell.org/mailman/listinfo/arch-haskell
Re: [arch-haskell] Destination folder of Haskell modules
On 13/12/10 16:57, Rémy Oudompheng wrote: > While playing with Haskell modules currently in [community], I > discovered that several of them, like haskell-x11, get installed to > /usr/lib/ghc-$(GHC_VERSION)/site-local/$(PACKAGE_NAME)-$(PACKAGE_VERSION) > whereas cabal2arch PKGBUILDs use the default directory > /usr/lib/$(PACKAGE_NAME)-$(PACKAGE_VERSION)/ghc-$(GHC_VERSION) > > The latter hierarchy looks highly confusing to me, as for example > gtk2hs-glib gets installed in /usr/lib/glib-0.12.0, not to be confused > with the glib2 package which installs files in /usr/lib/glib-2.0. > > So the first directory hierarchy looks much more logical to me. It is > obtained by using the option > --libsubdir=\$compiler/site-local/\$pkgid > in the "runhaskell Setup configure" command. That looks like a worthwhile change to make to cabal2arch. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: mag...@therning.org jabber: mag...@therning.org twitter: magthe http://therning.org/magnus signature.asc Description: OpenPGP digital signature ___ arch-haskell mailing list arch-hask...@haskell.org http://www.haskell.org/mailman/listinfo/arch-haskell
