Re: How to use dpkg -b ??
Hi!! Thanks again... Ok I tried the dpkg-source -x and here's the error I got: dpkg-source: error: tarfile `./mgetty_1.1.8.orig.tar.gz' contains object (mgetty-1.1.8/README.1st) not in expected directory (mgetty-1.1.8.orig) Help! ;) Ricardo On 18 Nov 1997, Ben Pfaff wrote: Debian List [EMAIL PROTECTED] writes: But given the 3 files (diff, dsc, tar), how do I use dpkg-buildpackage? I tried running it but it says it can't find debian/changelog and can't determine the source package... Oh, I'm sorry. Use `dpkg-source -x PACKAGE.dsc' to extract the source code, then use `dpkg-buildpackage' from the source directory. Also, what would be the procedure to customize/patch a package? Would I untar the original source, make mods to the source, tar it up again, and then build the package? I'm fuzzy as to what the procedure would be in order to customize a package. dpkg-buildpackage will automagically generate a diff from the original package source. If I make changes to the original source, wouldn't that invalidate the diff file? I don't understand the question. -- Ben Pfaff [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: How to use dpkg -b ??
Debian List [EMAIL PROTECTED] writes: Ok I tried the dpkg-source -x and here's the error I got: dpkg-source: error: tarfile `./mgetty_1.1.8.orig.tar.gz' contains object (mgetty-1.1.8/README.1st) not in expected directory (mgetty-1.1.8.orig) Reading the dpkg packaging manual: *3.4 Unpacking a Debian source package without dpkg-source* dpkg-source -x is the recommended way to unpack a Debian source package. However, if it is not available it is possible to unpack a Debian source archive as follows: 1. Untar the tarfile, which will create a .orig directory. 2. Rename the .orig directory to package-version. 3. Create the subdirectory debian at the top of the source tree. 4. Apply the diff using patch -p0. 5. Untar the tarfile again if you want a copy of the original source code alongside the Debianised version. It is probably necessary to do this by hand, as it looks like dpkg-source breaks on this particular package. This might be a bug in mgetty or in dpkg-source. -- Ben Pfaff [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: How to use dpkg -b ??
On Tue, 18 Nov 1997, Debian List wrote: Hi!! Thanks again... Ok I tried the dpkg-source -x and here's the error I got: dpkg-source: error: tarfile `./mgetty_1.1.8.orig.tar.gz' contains object (mgetty-1.1.8/README.1st) not in expected directory (mgetty-1.1.8.orig) Help! ;) Ricardo I had a similar problem with the xemacs20 source package - here's what I did, soup to nuts: Got the .tar.gz, .dsc, and .diff.gz files from ftp.debian.org. Since I have a bo system, I then had to make certain that I wasn't using the ldso from hamm. (the dpkg-dev in bo has problems with the ldd in ldso 1.9.x) Then, after experiencing the same problem with dpkg-source, I untarred the .tar.gz file into a temporary directory, and moved it about. That is, I did (something equivalent to) cd /tmp tar -xzf /usr/local/incoming/xemacs20_20.2.orig.tar.gz Now, this should have created a directory called xemacs20-20.2.orig; instead, however, it created xemacs-20.2.orig (I think; I know that the name was wrong, but can't remember exactly how it was wrong). So then I did: mv xemacs-20.2.orig xemacs20-20.2.orig tar -cf xemacs20_20.2.orig.tar xemacs20-20.2.orig gzip xemacs20_20.2.orig.tar This created a new xemacs20_20.2.orig.tar.gz - I then replaced the copy I'd downloaded with this one. This may be all that's needed; however, I also took the extra precaution of modifying the .dsc file; in the .dsc file there will be a line like: ece482d641199333788fb56bc6ea5e55 20651833 xemacs20_20.2.orig.tar.gz I changed this to match my new xemacs20_20.2.orig.tar.gz - this first long gobbledygook string was generated by 'md5sum xemacs20_20.2.orig.tar.gz' - the number after that is the size as shown by ls -l. As I said, this may be unnecessary, but I did it anyway. Then to compile the thing, I didn't use dpkg-buildpackage. Instead, after running the dpkg-source command to extract the package, I found that it (the source) had been put in /usr/local/incoming/xemacs20-20.2/ So then, I did: cd /usr/local/incoming/xemacs20-20.2/ vi debian/rules Now, the debian/rules file is just a makefile; I added the configuration options I needed; you may have to make other changes, (possibly in other files) depending on how mgetty is configured. I then did a debian/rules clean debian/rules build debian/rules binary This produced (after _much_ compiling and whatnot) the .deb packages (more than one since the xemacs source generates xemacs and xemacs-support, etc.) I wanted in /usr/local/incoming. I then could use dpkg to install them as I would any newly-downloaded .deb package. I think you can follow roughly this same procedure to compile your mgetty. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: How to use dpkg -b ??
Debian List wrote: Ok I tried the dpkg-source -x and here's the error I got: dpkg-source: error: tarfile `./mgetty_1.1.8.orig.tar.gz' contains object (mgetty-1.1.8/README.1st) not in expected directory (mgetty-1.1.8.orig) This version of mgetty is in hamm, which needs an upgraded dpkg to unpack correctly (it's in project/experimental, AFAIK). At this point you're anyway at half way; just do: cd mgetty-1.1.8 zcat ../mgetty_1.1.8*diff.gz | patch -p0 - and you're done (maybe with some old file as file.orig) dpkg-buildpackage will automagically generate a diff from the original package source. If I make changes to the original source, wouldn't that invalidate the diff file? Yes, it will overwrite the files with the old version number. You have to change the version number (first line in file debian/changelog). If you have debmake installed simply issue dch -n and you'll be editing that file _after_ the version change. Exit the editor saving the changes and issue dpkg-buildpackage or its wrapper build -rsudo (you need privileges to do build a package) pgp is needed only to sign the changes and dsc files. .deb will be OK even if you'll have an error for pgp. You'll see on the output: dpkg --build debian/tmp .. dpkg-deb: building package `mgetty' in `../mgetty_1.1.8-?_i386.deb'. fabrizio -- | [EMAIL PROTECTED][EMAIL PROTECTED][EMAIL PROTECTED] | Pluto Leader - Debian Developer Happy Debian 1.3.1 User - vi-holic | 6F7267F5 fingerprint 57 16 C4 ED C9 86 40 7B 1A 69 A1 66 EC FB D2 5E Just because Red Hat do it doesn't mean it's a good idea. [Ian J.] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
How to use dpkg -b ??
Hi guys, I've grabbed the source files for a package (.diff.gz, .dsc, .tar.gz) but now I don't know what to do ;) I thought the process was to use dpkg -b but that didn't work. How do I go about it? I need to customize some of the .h files, then I'd like to build the package... Can someone help? thanks Ricardo -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: How to use dpkg -b ??
Debian List [EMAIL PROTECTED] writes: I've grabbed the source files for a package (.diff.gz, .dsc, .tar.gz) but now I don't know what to do ;) I thought the process was to use dpkg -b but that didn't work. Install dpkg-dev, then run dpkg-buildpackage. -- Ben Pfaff [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: How to use dpkg -b ??
Thanks... But given the 3 files (diff, dsc, tar), how do I use dpkg-buildpackage? I tried running it but it says it can't find debian/changelog and can't determine the source package... Also, what would be the procedure to customize/patch a package? Would I untar the original source, make mods to the source, tar it up again, and then build the package? I'm fuzzy as to what the procedure would be in order to customize a package. If I make changes to the original source, wouldn't that invalidate the diff file? thanks Ricardo On 18 Nov 1997, Ben Pfaff wrote: Debian List [EMAIL PROTECTED] writes: I've grabbed the source files for a package (.diff.gz, .dsc, .tar.gz) but now I don't know what to do ;) I thought the process was to use dpkg -b but that didn't work. Install dpkg-dev, then run dpkg-buildpackage. -- Ben Pfaff [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: How to use dpkg -b ??
Debian List [EMAIL PROTECTED] writes: But given the 3 files (diff, dsc, tar), how do I use dpkg-buildpackage? I tried running it but it says it can't find debian/changelog and can't determine the source package... Oh, I'm sorry. Use `dpkg-source -x PACKAGE.dsc' to extract the source code, then use `dpkg-buildpackage' from the source directory. Also, what would be the procedure to customize/patch a package? Would I untar the original source, make mods to the source, tar it up again, and then build the package? I'm fuzzy as to what the procedure would be in order to customize a package. dpkg-buildpackage will automagically generate a diff from the original package source. If I make changes to the original source, wouldn't that invalidate the diff file? I don't understand the question. -- Ben Pfaff [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
