Re: [Denemo-devel] Ubuntu PPA & Debian Packaging

[Pietro Battiston]

Il giorno mar, 01/06/2010 alle 00.14 +0200, Till Hartmann ha scritto:
> On 31.05.2010 18:07, Pietro Battiston wrote:
> > Il giorno lun, 31/05/2010 alle 17.44 +0200, Till Hartmann ha scritto:
> >> Hi all,
> >>
> >> I'm currently planning to create a PPA for recent Ubuntu versions
> >> (karmic and lucid, that is) (for those who do not know what a PPA is:
> >> Personal Package Archive, where launchpad users can upload source
> >> packages and let Canonical's servers build the packages for you. These
> >> PPA can be added as a software repository to the apt sources).
> >> To prevent redundant work and learn more about debian packaging, I would
> >> like to know who is the deb maintainer for denemo (I've seen mails on
> >> the list some time ago, but the denemo version packaged is already quite
> >> old, especially as denemo's development process keeps getting faster)
> >> and if you could help me a little bit.
> >>
> > 
> > - formally, there is no debian maintainer - the last packages were
> > uploaded as "quality assurance" uploads, which is what happens with
> > orphaned packages
> > 
> > - more pragmatically, I'm the one behind those last uploads
> > 
> > - even more pragmatically, Josue Abarca is the one who already packaged
> > the last denemo version and is currently trying to get it into Debian,
> > and also to become its (official) maintainer.
> > 
> > 
> > I guess he's the right person to answer more in depth to your questions,
> > but since I did use several times some PPAs, I just add that the
> > following:
> > 
> > git clone git://git.debian.org/collab-maint/denemo.git
> > git-buildpackage -S -sa
> > 
> > should produce something almost ready for a PPA, though you will
> > probably want to add a changelog entry in order to target the right
> > Ubuntu release (and obviously give a clean "git-buildpackage" to verify
> > it builds fine).
> > 
> > 
> > One more step would be to patch the default settings in order to use
> > pulseaudio (present by default in Ubuntu but not in Debian).
> > 
> > The Right Thing (TM) may then be, if that's fine for Josue, that you
> > register on Alioth and create a separate branch for (the few,
> > presumably) Ubuntu-specific patches.
> > 
> > Pietro
> > 
> > 
> > _______________________________________________
> > Denemo-devel mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/denemo-devel
> Thanks for both your answers.
> 
> I actually already sent libsmf to launchpad which built it for me
> (libsmf is already available via my ppa [at
> https://launchpad.net/~tillux/+archive/t-audio]). However, denemo makes
> some problems; the funny part is: building denemo *locally* on my
> machine did succeed, after I had removed the "autopoint" (debian
> specific?)

for the moment, yes, I guess

> dependency from the control file, the launchpad build will
> fail with though. See
> http://launchpadlibrarian.net/49465059/buildlog_ubuntu-lucid-i386.denemo_0.8.16-3_FAILEDTOBUILD.txt.gz
> for the complete buildlog.
> 

How about just adding "cvs" to build-depends?

In general: the best and easiest (in my experience) system to locally
check missing dependencies (by building a package like it gets built in
repositories) is cowbuilder:
http://wiki.debian.org/cowbuilder

Pietro