On 20/10/2005 Ales Kozumplik wrote: > Sure, I could give it a try. > I've never done this before - should I rather do that from debian sources or > from the sources on websites of the projects?
best is to do it from the debian sources: add a deb-src line to /etc/apt/sources.list. for example: deb-src ftp://ftp2.de.debian.org/debian/ sid main now you have to update the apt database and install all build-depends for python-mysqldb, this needs to be done as root: [ update the apt database ] # apt-get update [ install general build packages, needed to build almost every package ] # apt-get install fakeroot build-essential [ install the build-depends for python-mysqldb ] # apt-get build-dep python-mysqldb the package building can be done as normal system user: [ get the sources ] $ apt-get source python-mysqldb [ change to the build directory ] $ cd python-mysqldb-1.2.1c3/ [ actually build the package ] $ dpkg-buildpackage -rfakeroot -us -uc if everything went right, you should see the following files in ../ afterwards: python-mysqldb_1.2.1c3-2.diff.gz python-mysqldb_1.2.1c3-2.dsc python-mysqldb_1.2.1c3-2_all.deb python-mysqldb_1.2.1c3-2_i386.changes python-mysqldb_1.2.1c3.orig.tar.gz python2.2-mysqldb_1.2.1c3-2_i386.deb python2.3-mysqldb_1.2.1c3-2_i386.deb python2.4-mysqldb_1.2.1c3-2_i386.deb install the appropriative .deb files, and see whether the bug has been fixed. ... jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
