Hi Olivier, On Fri, 2008-08-08 at 11:42 +0200, Olivier Berger wrote: > Sh*t. > > Was looking at > http://michele.pupazzo.org/files/debian/mod-auth-cas/1.0.7/ :( > > I guess you should update http://michele.pupazzo.org/diary/?p=277 and > maybe remove the files from /files/debian/mod-auth-cas/1.0.7/ then ? Heh and I was wondering were you got the -2 release.. Sorry for the confusion, I forgot about that leftover. > > > Here's details of the changes I made (changelog obviously needs updating > > > more than I did) : > > > > > > * Now use apxs2's -i option to install the libs in the right place at > > > package contruction > > > > This gives me an error because axps tries to write in /usr/lib/... Is > > there a specific version that understands AXPS_OPTIONS? A quick grep and > > google didn't turn up anything interesting. > > > > AXPS_OPTIONS is just my own invention for the Makefile.in. Ah ok, didn't see you changed Makefile.in. I've uploaded a new -7 package w/ changes. I only kept the change to Makefile.in as a separate patch (via dpatch). > I updated your latest package (in attachment) to incorporate that. > > > > * moved chown on cookies dir into a postinst (safer for package > > > construction) > > > > Thanks, embarassing leftover of mine ;) > > > > Well, after some responses received on the -mentors Debian list, I > changed the rules file to do the chown again, but after the dh_fixperms. > > Now, the postinst is probably needed to manage upgrades (also suggested > on debian-mentors). > > Updated the package sources in this respect too. Just read that thread on #d-m, didn't know that both approaches together make sense. /me notes. > > I uploaded -6 on my repo on my homepage. > > > > Excellent. Thanks alot. I removed mine from mentors.debian.net, then. > > I send you in attachment an updated version. Thanks. Integrated and uploaded a new version. <snip> > Seen your mail on the cas-dev list ;) Thanks. 2 people asking is better, > I guess. > > Maybe that problem should be mentioned in the copyright file of the > package ? Let's wait for an answer and then we'll see what to do. > > The other point, is that I think it makes sense to push this in Debian > > only if the CAS server is also present as a package. > > Well... that is not a requisite I guess... one may imagine that CAS > server would be setup manually since it requires much more tuning than > clients, which should in principle be more simple and then have less > need to evolve, be patched, tweaked, etc. So clients are in a greater > need of packaging, I guess. At least, for one CAS server deployed there > will be many CAS clients, so the burden of deployment justifies a > priority on the client. Makes sense. > > If you feel like landing in a hand, we can set up something on alioth to > > get this in shape. > I cannot commit a long-time interest into it, but for the time being, > count me in. I'm no DD, but already a maintainer of phpgroupware (and > soon more packages to come, like twiki-ldapcontrib). > I'd probably try and push CAS-ification bits into Debian for a couple > apps we use in PicoForge (www.picoforge.org). Like TWiki, phpGroupware, > Sympa (already included, I guess) and others. Looks like an interesting project ;) I'll ping you when (sic) I get around to set something up to do some collaborative work for CAS. thanks, Michele
Attachment:
signature.asc
Description: This is a digitally signed message part