Re: Ongoing scanner setup, now need a bit of help with dpkg-buildpackage
Hello Craig, On 2/17/19, Craig Sanders via luv-main wrote: > On Sun, Feb 17, 2019 at 10:55:52AM +1100, Craig Sanders wrote: >> 2. run 'dch -i' to change the package version number. e.g. when dch starts >> up your text editor, change the first line to something like: >> >> sane-backends (1.0.27-3.1~backport) UNRELEASED; urgency=medium > > The version number (inside the parentheses) is the only thing that needs to > be > changed on this line. > > Note: i just tried this on my sid machine and dch aborted with some error > about not finding the original source archive, and didn't change the version > number for me. Don't know why, don't really care - it's a minor problem that > can be ignored(*), and we're not rebuilding the source packages anyway. About what I thought, dch worked, but would have preferred gedit or leafpad. That can be set up another time. > I just edited the changelog manually with 'vi debian/changelog' and changed > the version number, then ran dpkg-buildpackage. > > (*) OTOH, if it *had* prevented dpkg-buildpackage from successfully > compiling > the packages, it would have been a problem worth investigating and fixing. > but > it didn't and it wasn't, so i ignored it :) > >> 5. install the packages you just built with: >> >> dpkg -iBE *1.0.27-3.1~backport*.deb > > This last step has to be done as root (e.g. with sudo, or in a root shell). > everything else can be done as your normal, non-root user. Expected, but looking like will also have to backport debhelper, libtiff5 and libtiffxx5 first, and anything else it needs. I did find the changes that are due to ripple through with the update from 9.7 to 9.8, and none of those are listed. I notice that noscript will be dropped as no longer compatible with the new firefox esr. I do not like that. > BTW, the file glob pattern matches only the packages you just built, just in > case there are other .deb packages in the same dir. Thank you for the reminder, is as I would expect. > craig Regards, Mark Trickett ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
Re: Ongoing scanner setup, now need a bit of help with dpkg-buildpackage
Hello again Craig, On 2/17/19, Craig Sanders via luv-main wrote: > On Sun, Feb 17, 2019 at 10:16:37AM +1100, Mark Trickett wrote: >> I have managed to locate and download the source files, >> sane-backends_1.0.27.orig.tar.gz, sane-backends_1.0.27.debian.tar.gz and >> sane-backends_1.0.27.dsc and put them in a directory. I tried > > extract the debianised source with: > > dpkg-source -x sane-backends_1.0.27.dsc Aha, that is what that file is. >> Now I am looking at building my own backport, and looking at using >> dpkg-buildpackage. I would appreciate advice and comments about usage, >> what to do to prepare and the like. I will be looking at web searches, > > 0. Make sure all the essential compilation tools are installed with: > > apt-get install build-essential Is installed. > 1. cd sane-backends-1.0.27/ > > 2. run 'dch -i' to change the package version number. e.g. when dch starts > up > your text editor, change the first line to something like: > > sane-backends (1.0.27-3.1~backport) UNRELEASED; urgency=medium That makes sense, I think I can understand what is going on > 3. run "dpkg-buildpackage -b --no-sign". This tells dpkg-buildpackage to > build only the binary packages (-b), and not to bother signing anything (not > necessary for self-built packages, and avoids the need to create a gpg key > if > you don't have one) I was getting confused from the man page as to quite the switches and the like, thank you for the simple and concise command line and explanation. > The first time you run this, it will probably give you an error like this: > > dpkg-checkbuilddeps: error: Unmet build dependencies: chrpath libgphoto2-dev > libsnmp-dev libsystemd-dev libusb-1.0-0-dev > > install those build dep packages with apt-get, e.g.: > > apt-get install chrpath libgphoto2-dev libsnmp-dev libsystemd-dev > libusb-1.0-0-dev > > and then repeat this step until the packages compile successfully. Again simple when you put it that way, thank you. Just been doing, and wants a few later packages than I have installed, first up debhelper (>=11) when I have 10.2.5 installed. Then libtiff5 and libtiffxx5 (=4.0.10-4) but 4.0.8-2+deb9u4 is to be installed when run apt-get. Looks like will need to see what might be available in the later release (buster). I might have to do a dist upgrade. > 4. cd .. > > 5. install the packages you just built with: > > dpkg -iBE *1.0.27-3.1~backport*.deb Yes, I do like the packaging and the suitable manipulation, and that it handles dependencies and the like, mostly. System Administration, every computer needs it, and with a PC, you are your own System Administrator. The way Microsoft treats it and tries to hide and automate and makes so difficult to fix their errors, along with hiding file extensions by default, along with relying on the extension rather than actually looking at the contents is a very large measure of why I regard Windows and Windows software not even worth pirating, let alone paying for. > craig Again many thanks, expect will succeed shortly, but may need to do other aspects of life, being ready for work on Monday, too early. As an interim, a couple of documents photographed and needing cropping and balance adjusting if I do not complete today. Scanning will be so much better. Mark Trickett ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
Re: Ongoing scanner setup, now need a bit of help with dpkg-buildpackage
On Sun, Feb 17, 2019 at 10:55:52AM +1100, Craig Sanders wrote: > 2. run 'dch -i' to change the package version number. e.g. when dch starts > up your text editor, change the first line to something like: > > sane-backends (1.0.27-3.1~backport) UNRELEASED; urgency=medium The version number (inside the parentheses) is the only thing that needs to be changed on this line. Note: i just tried this on my sid machine and dch aborted with some error about not finding the original source archive, and didn't change the version number for me. Don't know why, don't really care - it's a minor problem that can be ignored(*), and we're not rebuilding the source packages anyway. I just edited the changelog manually with 'vi debian/changelog' and changed the version number, then ran dpkg-buildpackage. (*) OTOH, if it *had* prevented dpkg-buildpackage from successfully compiling the packages, it would have been a problem worth investigating and fixing. but it didn't and it wasn't, so i ignored it :) > 5. install the packages you just built with: > > dpkg -iBE *1.0.27-3.1~backport*.deb This last step has to be done as root (e.g. with sudo, or in a root shell). everything else can be done as your normal, non-root user. BTW, the file glob pattern matches only the packages you just built, just in case there are other .deb packages in the same dir. craig -- craig sanders ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
Re: Ongoing scanner setup, now need a bit of help with dpkg-buildpackage
On Sun, Feb 17, 2019 at 10:16:37AM +1100, Mark Trickett wrote: > I have managed to locate and download the source files, > sane-backends_1.0.27.orig.tar.gz, sane-backends_1.0.27.debian.tar.gz and > sane-backends_1.0.27.dsc and put them in a directory. I tried extract the debianised source with: dpkg-source -x sane-backends_1.0.27.dsc > Now I am looking at building my own backport, and looking at using > dpkg-buildpackage. I would appreciate advice and comments about usage, > what to do to prepare and the like. I will be looking at web searches, 0. Make sure all the essential compilation tools are installed with: apt-get install build-essential 1. cd sane-backends-1.0.27/ 2. run 'dch -i' to change the package version number. e.g. when dch starts up your text editor, change the first line to something like: sane-backends (1.0.27-3.1~backport) UNRELEASED; urgency=medium 3. run "dpkg-buildpackage -b --no-sign". This tells dpkg-buildpackage to build only the binary packages (-b), and not to bother signing anything (not necessary for self-built packages, and avoids the need to create a gpg key if you don't have one) The first time you run this, it will probably give you an error like this: dpkg-checkbuilddeps: error: Unmet build dependencies: chrpath libgphoto2-dev libsnmp-dev libsystemd-dev libusb-1.0-0-dev install those build dep packages with apt-get, e.g.: apt-get install chrpath libgphoto2-dev libsnmp-dev libsystemd-dev libusb-1.0-0-dev and then repeat this step until the packages compile successfully. 4. cd .. 5. install the packages you just built with: dpkg -iBE *1.0.27-3.1~backport*.deb craig -- craig sanders ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
Ongoing scanner setup, now need a bit of help with dpkg-buildpackage
hello All, Many thanks to Craig Sanders for help so far. I have found the binary sane-utils packages for sid, but too much conflicts to go that way. I have managed to locate and download the source files, sane-backends_1.0.27.orig.tar.gz, sane-backends_1.0.27.debian.tar.gz and sane-backends_1.0.27.dsc and put them in a directory. I tried using "apt-get src" to no effect, complained that could not find the source package, but finally understood the Debian site with Firefox, at least in that regard. Now I am looking at building my own backport, and looking at using dpkg-buildpackage. I would appreciate advice and comments about usage, what to do to prepare and the like. I will be looking at web searches, along with reading the manpage which I currently have up, but still not quite understanding, yet. All help is appreciated. Regards, Mark Trickett ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
