[pkg-synfig-devel] new upstream release, libetl-dev, synfig

[Paul Wise]

On Sat, 2006-03-04 at 16:35 +0200, Fabian Fagerholm wrote:

> >      2. Upload the new etl -2 as libetl-dev --> goes into NEW
> 
> What are the chances of optimizing away this binary package name change
> as part of upstream folding etl into synfig?

darco wants to fold it into synfig version 0.62. No idea of an ETA on
that.

> I'm proceeding to the new synfig package with the assumption that etl
> won't be folded in time (or at all) for our purposes.

This is the best course of action.

> However, I'm going to hold off a little on the name change for etl
> until I get your opinion on the above. We can always reverse the
> dependency changes, but NEW processing is expensive and should be
> avoided if possible.

Hmm, I think perhaps we should wait till after the amd64 archive
integration and mirror split work is done and then re-evaluate the speed
of NEW to see if we have time to do the name change, because I heard a
rumor on IRC that NEW isn't being processed during the mirror split and
amd64 integration process. I don't think the name change is all that
important anyway.

> libsynfig0-dev should probably depend on libetl-dev | etl-dev too,
> during the name transition. I made that change, ran ./bootstrap (and
> cleaned up the mess it produces :) and uploaded.

Hmm, I thought I did that too, mustn't have committed it.

> Btw, I think we should adopt the multi-person changelog format used by
> many other packages, when it makes sense.

Yeah, dch/debchange makes it very easy to do this.

> Personally, I like to prefix my changes with the filename(s) the
> change occurred in, unless it's some general thing like running
> the ./bootstrap script, updating to a new upstream version or it
> affects a large number of files.

Fair enough.

> >      7. Beer-o-clock!
> 
> Can't wait 'til we get to step 7! ;)

Heheh :)

> I ran bootstrap for synfigstudio, didn't have time to try building. I
> didn't check the result very carefully yet, so there might be some
> tweaking to do.

I'll check it out tomorrow.

> Do you know how to get a local package installed into the pbuilder
> chroot? In this case, the synfig debs would need to be installed
> somehow, since they're not in the archive yet. I ran out of time trying
> to figure this out.

~/.pbuilderrc:

HOOKDIR=/home/pabs/.pbuilder/hooks/

~/.pbuilder/hooks/D10shell

#!/bin/bash
/bin/bash < /dev/tty > /dev/tty

You then get a shell inside the chroot, but before build-dep
installation. During this phase, you can copy debs from outside the
chroot into it and run dpkg -i and apt-get -f install.

Also having a copy of the script as B10shell and C10shell gives you a
shell when it FTBFS, or when the debs are fully built. You can then fix
the FTBFS or run lintian/linda on the packages inside the chroot.

Also, if you have slow disks/cpu, you might want to try this pbuilder
cowdancer script:

http://bonedaddy.net/pabs3/files/bin/cowbuild

> > So, re-autotool and upload away! Please don't forget to use this when
> > building synfig: -v 0.61.04-1 (this will include all the changelog in
> > the upload so the ITP gets closed).
> 
> Good point, just a minor detail: it has to be -v 0.61.04-0 because the
> version comparison is >, not >=. Picky, I know ;)

Ahhh, I suppose this would work too: -v 0.61.04

> > Damn, wish svn+ssh could use my ssh agent instead of prompting for
> > passwords a thousand times on svn-upgrade. svn is passing the correct
> > env vars to ssh, but no joy. Plain ssh uses the key fine tho. Any ideas?
> 
> I had the same problem, too, until just now. Checked permissions on .ssh
> and .ssh/authorized_keys on svn.debian.org, nothing wrong there.
> However, it seems that uploading your key to svn.debian.org isn't
> enough; you need to upload it to alioth.debian.org. I guess it has
> something to do with the way the chroots are arranged, or something.
> Anyway, get your key into ~/.ssh/authorized_keys on alioth, permissions
> set right (700 for .ssh, 600 for authorized_keys) and you should be able
> to use the keys.

Thanks, that worked. I had the key on alioth.debian.org (haydn), but not
on svn.debian.org (costa). I didn't realise the difference, I thought
they were on the same host/chroot.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-synfig-devel/attachments/20060304/993be51f/attachment.pgp