From: Ken Heard on
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John A. Sullivan III wrote:

> Yes, indeed it breaks. We learned that the hard way. We repackaged it
> using the newer source. I do not know how we submit such repacking for
> backports but here are the steps we took to make it happen (edited to
> protect internal information:

> As root, install the needed packages for building
> apt-get -t lenny-backports install devscripts build-essential
> Edit /etc/apt/sources.list by adding a Lenny Backports source repository such as the following:
> deb-src http://www.backports.org/debian/ lenny-backports main contrib non-free
> Make apt aware of the repository:
> apt-get update

Your instructions amended.

> We will need the 2.2.6 source deb to have all the various settings and options used by debian.
> These will be in the debian directory and is really all we need from the source deb. We will store this in gnucash-2.2.6
> We will also need the 2.2.9 source tarball. We will store this in gnucash which will become the deb build directory
> mkdir /download/gnucash
> mkdir /download/gnucash-2.2.6
> change the permissions of these two directories to drwxrwxrwx.
> cd /download/gnucash-2.2.6
> The following step MUST not be done by root so open a user console and
> in it run:
> apt-get -t lenny-backports source gnucash gnucash-common
> We need to install dependencies and this must be done as root so return to the root console and do:
> cd /download/gnucash-2.2.6
> apt-get -t lenny-backports build-dep gnucash gnucash-common

> Return to the user console
> cd /download/gnucash
> wget http://www.gnucash.org/pub/gnucash/sources/stable/gnucash-2.2.9.tar.bz2
> tar jfvx gnucash-2.2.9.tar.bz2
> mv gnucash{-,_}2.2.9.tar.bz2
> mv gnucash_2.2.9{,.orig}.tar.bz2 - This is the name format debuild will expect

With your amended instructions I got as far as here, but the following
command confuses me.

> cd gnucash-2.2.9

As this directory does not exist it is impossible to change to it. Do
you mean cd ../gnucash-2.2.6, since the directory I am in at this point
is /download/gnucash, or do you want a new directory guncash-2.2.9 to be
created somewhere? If the former, it seems to me that there is an
extra ../ and an extra gnucash-2.2.6 -- two of each rather than one. If
the object of the exercise is to create gnucash-2.2.6, shouldn't the
directories now be so named?

> cp -r ../../gnucash-2.2.6/gnucash-2.2.6/debian ./
> cd debian
> The changelog is more than information; it is critical for debuild processing.
> Add something similar to the following at the top (the syntax is very fussy)
> gnucash (2.2.9-0) stable; urgency=high
> * 2.2.6 segfaults with libglib from lenny-backports
> -- John Sullivan <myname(a)mycompany.com> Sat, 27 Mar 2010 19:18:00 -0500
> Edit the control file and edit the two Replaces lines so they read:
> Replaces: gnucash-common (<< 2.2.6-3)
> Replaces: gnucash (<< 2.2.6-3)
> Edit the files file so it reads:
> gnucash-common_2.2.9-0_all.deb gnome optional
> gnucash_2.2.9-0_amd64.deb gnome optional
> debuild will complain about the -0 but I do not want to give it -1 in case the real 2.2.9 package is -1 when it is released.
> cd ..
> debuild -us -uc
> cd ..
> The two .deb files should be in this directory and can be installed where needed

> Any corrections to the process are welcome as I am by no means an
> expert. Hope this helps - John

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEUEARECAAYFAkw2kScACgkQlNlJzOkJmTc7owCfXC6jQ2FAk7I3DNK1Ypy0OGnC
pHsAmNk2zboiozoH5q4ftiz27Yp0iwE=
=fz4B
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4C369128.5000602(a)heard.name
From: John A. Sullivan III on
On Thu, 2010-07-08 at 23:02 -0400, Ken Heard wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> John A. Sullivan III wrote:
>
> > Yes, indeed it breaks. We learned that the hard way. We repackaged it
> > using the newer source. I do not know how we submit such repacking for
> > backports but here are the steps we took to make it happen (edited to
> > protect internal information:
<snip>
> > Return to the user console
> > cd /download/gnucash
> > wget http://www.gnucash.org/pub/gnucash/sources/stable/gnucash-2.2.9.tar.bz2
> > tar jfvx gnucash-2.2.9.tar.bz2
> > mv gnucash{-,_}2.2.9.tar.bz2
> > mv gnucash_2.2.9{,.orig}.tar.bz2 - This is the name format debuild will expect
>
> With your amended instructions I got as far as here, but the following
> command confuses me.
>
> > cd gnucash-2.2.9
>
> As this directory does not exist it is impossible to change to it.
It has been a while since I've done this but, after you untar the
gnucash-2.2.9.tar.bz2, don't you have a gnucash-2.2.9 directory into
which we are now going to copy the debian folder from 2.2.6 so we can
build it into a Debian package?
> Do
> you mean cd ../gnucash-2.2.6, since the directory I am in at this point
> is /download/gnucash, or do you want a new directory guncash-2.2.9 to be
> created somewhere? If the former, it seems to me that there is an
> extra ../ and an extra gnucash-2.2.6 -- two of each rather than one. If
> the object of the exercise is to create gnucash-2.2.6, shouldn't the
> directories now be so named?
>
> > cp -r ../../gnucash-2.2.6/gnucash-2.2.6/debian ./
> > cd debian
> > The changelog is more than information; it is critical for debuild processing.
> > Add something similar to the following at the top (the syntax is very fussy)
> > gnucash (2.2.9-0) stable; urgency=high
> > * 2.2.6 segfaults with libglib from lenny-backports
> > -- John Sullivan <myname(a)mycompany.com> Sat, 27 Mar 2010 19:18:00 -0500
> > Edit the control file and edit the two Replaces lines so they read:
> > Replaces: gnucash-common (<< 2.2.6-3)
> > Replaces: gnucash (<< 2.2.6-3)
> > Edit the files file so it reads:
> > gnucash-common_2.2.9-0_all.deb gnome optional
> > gnucash_2.2.9-0_amd64.deb gnome optional
> > debuild will complain about the -0 but I do not want to give it -1 in case the real 2.2.9 package is -1 when it is released.
> > cd ..
> > debuild -us -uc
> > cd ..
> > The two .deb files should be in this directory and can be installed where needed
>
> > Any corrections to the process are welcome as I am by no means an
> > expert. Hope this helps - John
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEUEARECAAYFAkw2kScACgkQlNlJzOkJmTc7owCfXC6jQ2FAk7I3DNK1Ypy0OGnC
> pHsAmNk2zboiozoH5q4ftiz27Yp0iwE=
> =fz4B
> -----END PGP SIGNATURE-----
>
>



--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/1278649183.9929.6.camel(a)denise.theartistscloset.com
From: Ken Heard on
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John A. Sullivan III wrote:
> On Thu, 2010-07-08 at 23:02 -0400, Ken Heard wrote:
> John A. Sullivan III wrote:

> With your amended instructions I got as far as here, but the following
> command confuses me.
>
>>>> cd gnucash-2.2.9
> As this directory does not exist it is impossible to change to it.


>> It has been a while since I've done this but, after you untar the
>> gnucash-2.2.9.tar.bz2, don't you have a gnucash-2.2.9 directory into
>> which we are now going to copy the debian folder from 2.2.6 so we can
>> build it into a Debian package?

Yes, it did create directory /download/gnucash/gnucash-2.2.9. I should
have known enough to look before asking the question.

>>>> cp -r ../../gnucash-2.2.6/gnucash-2.2.6/debian ./
>>>> cd debian
>>>> The changelog is more than information; it is critical for debuild processing.
>>>> Add something similar to the following at the top (the syntax is very fussy)
>>>> gnucash (2.2.9-0) stable; urgency=high
>>>> * 2.2.6 segfaults with libglib from lenny-backports
>>>> -- John Sullivan <myname(a)mycompany.com> Sat, 27 Mar 2010 19:18:00 -0500

Done.

>>>> Edit the control file and edit the two Replaces lines so they read:
>>>> Replaces: gnucash-common (<< 2.2.6-3)
>>>> Replaces: gnucash (<< 2.2.6-3)

Done, but with 2.2.6-2, as it is the -2 versions which are in my box.

>>>> Edit the files file so it reads:
>>>> gnucash-common_2.2.9-0_all.deb gnome optional
>>>> gnucash_2.2.9-0_amd64.deb gnome optional

In directory /download/gnucash/guncash-2.2.9/debian there is no files
file. Should I create it with only those two lines, before running the
final steps?

>>>> debuild will complain about the -0 but I do not want to give it -1 in case the real 2.2.9 package is -1 when it is released.
>>>> cd ..
>>>> debuild -us -uc
>>>> cd ..
>>>> The two .deb files should be in this directory and can be installed where needed
>>>> Any corrections to the process are welcome as I am by no means an
>>>> expert. Hope this helps - John

Regards, Ken Heard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkw3LYAACgkQlNlJzOkJmTcYzgCeNDUwyaowQlB2kU1bA8ZfjRjF
GZYAn3iWb+xHEG7HpMcLLgh/Sy97hDUf
=r7/m
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4C372D81.4040400(a)heard.name
From: John A. Sullivan III on
On Fri, 2010-07-09 at 10:09 -0400, Ken Heard wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> John A. Sullivan III wrote:
> > On Thu, 2010-07-08 at 23:02 -0400, Ken Heard wrote:
<snip>
> >>>> Edit the control file and edit the two Replaces lines so they read:
> >>>> Replaces: gnucash-common (<< 2.2.6-3)
> >>>> Replaces: gnucash (<< 2.2.6-3)
>
> Done, but with 2.2.6-2, as it is the -2 versions which are in my box.
>
> >>>> Edit the files file so it reads:
> >>>> gnucash-common_2.2.9-0_all.deb gnome optional
> >>>> gnucash_2.2.9-0_amd64.deb gnome optional
>
> In directory /download/gnucash/guncash-2.2.9/debian there is no files
> file. Should I create it with only those two lines, before running the
> final steps?
<snip>
It looks like that is indeed the case in my installation - just those
two lines. If I recall correctly, though, your architecture is not
amd64 so you will need to use whatever is appropriate for you. Good
luck - John


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/1278694731.20386.2.camel(a)denise.theartistscloset.com