Bug#404346: vino-server segmentation fault

Loïc Minier lool at dooz.org
Sun Dec 24 18:00:38 UTC 2006


On Sun, Dec 24, 2006, Guy Roussin  wrote:
> I have time but i don't know the process to build upstream CVS of vino.
> Perhaps you can give some hints. Then i give it a try ?

 It's a process very close to building a version with debugging symbols,
 but you don't need to pass any build options (so it's simpler).
 Additionally, you'll need to do two things:
 1) create a tarball with a CVS snapshot:
   1) use cvs export from the upstream CVS to export a copy into a
      temporary directory (without any "CVS/" directories)
   2) run ./autogen.sh
   3) add any missing tools requested by autogen.sh and repeat 2) until
      it doesn't fail ;)
   4) rm -rf autom4te.cache
   5) create a tarball of the resulting bootstrapped directory
 2) update the debian/changelog file to have a new entry saying that
    this is a CVS snapshot and with a different version than Debian, for
    example cvs20061224-1; you can use dch to edit the changelog
 3) try to build and rename the tarball you created to match
    <someversion>.orig.tar.gz

 You might also try upstream build tools such as "jhbuild", or simply
 building from a CVS checkout, without installing the result.

   Cheers,
-- 
Loïc Minier <lool at dooz.org>
 "Forget your stupid theme park! I'm gonna make my own! With hookers!
  And blackjack! In fact, forget the theme park!"          -- Bender





More information about the pkg-gnome-maintainers mailing list