Re: sources.list and locally generated debs
On Tuesday 10 April 2001 00:38, Rick Macdonald wrote: > On Mon, 9 Apr 2001, Chris Gray wrote: > > On Mon, 09 Apr 2001, Colin Watson wrote: > > > Mario Vukelic <[EMAIL PROTECTED]> wrote: > > >>My locally generated debs, e.g. from kernel compiles, show up > > >> as obsolete in dselect. Is there an easy way to tell their > > >> locations to the package manager or do I have to mess with > > >> Packages.gz files and the like? > > > > > > You pretty much have to mess with Packages.gz, I'm afraid (at > > > least, that's the easiest way I can think of). apt-ftparchive > > > in the apt-utils package in testing/unstable may help. > > I used to put my local debs (kernels etc) into a directory > (/usr/local/src/debian-local/dists/local/local/binary-i386) > and then run this script: > > #!/bin/sh > cd /usr/local/src/debian-local > dpkg-scanpackages dists/local/local/binary-i386 /dev/null > > dists/local/local/binary-i386/Packages > gzip dists/local/local/binary-i386/Packages > > Then I would add this to sources.list: > > deb file:/usr/local/src/debian-local local/ > > I was never quite sure about the proper directory paths to set up, > and in fact the names above might not be consistant and correct. > Perhaps somebody can comment on, fix or improve this idea? > > ...RickM... No need to be consistent, really. My sources.list reads deb file:/ephemeroot/pool ./ That's slashdot in reverse. My Packages (no need to gzip it!) file is filed at /ephemeroot/pool/Packages It appears that dpkg-scanpackages creates a Filename: line [Filename: ./nautilus/nautilus_1.0-1_i386.deb] that's appended to the deb line in sources.list [deb file:/ephemeroot/pool ./]. /ephemeroot/pool + ./nautilus/nautilus_1.0-1_i386.deb = /ephemeroot/pool/nautilus/nautilus_1.0-1_i386.deb Giving us the path to the deb in question. Maybe it's time somebody wrote a FAQ/tutor on this.
Re: sources.list and locally generated debs
On Mon, Apr 09, 2001, Chris Gray wrote: > On Mon, 09 Apr 2001, Colin Watson wrote: > > Mario Vukelic <[EMAIL PROTECTED]> wrote: > >>My locally generated debs, e.g. from kernel compiles, show up as > >>obsolete in dselect. Is there an easy way to tell their locations to > >>the package manager or do I have to mess with Packages.gz files and > >>the like? > > > > You pretty much have to mess with Packages.gz, I'm afraid (at least, > > that's the easiest way I can think of). apt-ftparchive in the > > apt-utils package in testing/unstable may help. > > If I understand the question correctly, it seems the canonical answer > is to raise the version number of the locally created package. This > should keep dselect or apt from thinking that the local package is > obsolete. You can change the version of the package by adding to the > debian/changelog file. There is a nice mode in emacs to help you do this. Hi, At the risk of talking about something I don't really understand fully myself, I believe there's some functionality called 'epochs' built into dpkg, and denoted by 'make-kpkg --revision=2:myrevision' (note the ':' syntax), which has some benefits in this area. I looked into it last time I used kernel-package, but I remember conflicting messages/descriptions from different sources, so I don't recall the full system or the true benefits of epochs. Just wanted to mention it to possibly point you in the right direction. Hope this helps and take care, Daniel > > Cheers, > Chris > > -- > Got jag? http://www.tribsoft.com -- Daniel A. Freedman Laboratory for Atomic and Solid State Physics Department of Physics Cornell University
Re: sources.list and locally generated debs
> My locally generated debs, e.g. from kernel compiles, show up as > obsolete in dselect. Is there an easy way to tell their locations to the > package manager or do I have to mess with Packages.gz files and the Generate local Packages.gz of your debs, eg, in my mirror I use: dpkg-scanpackages dists/potato/local/binary-i386 \ dists/potato/local/binary-i386/override.local.gz | \ gzip -c > dists/potato/local/binary-i386/Packages.gz -Igor Mozetic
Re: sources.list and locally generated debs
On 09 Apr 2001 10:38:36 -0600, Rick Macdonald wrote: > Then I would add this to sources.list: > > deb file:/usr/local/src/debian-local local/ It works now, except that the line needs to be deb file:/usr/local/src/debian-local local local with the given directory setup. Thanks again and sorry for being a nuisance :o) -- I did not vote for the Austrian government
Re: sources.list and locally generated debs
On 09 Apr 2001 20:08:26 +0200, Mario Vukelic wrote: > Uuhm, I did this now and it generates a nice Packages.gz, but the debs > still show up as obsolete ? (Yes, I did update) I'm a moron, the deb line in sources.list was commented out. Sorry -- I did not vote for the Austrian government
Re: sources.list and locally generated debs
On 09 Apr 2001 10:38:36 -0600, Rick Macdonald wrote: (...) > Then I would add this to sources.list: > > deb file:/usr/local/src/debian-local local/ Uuhm, I did this now and it generates a nice Packages.gz, but the debs still show up as obsolete ? (Yes, I did update) -- I did not vote for the Austrian government
Re: sources.list and locally generated debs
On 09 Apr 2001 10:38:36 -0600, Rick Macdonald wrote: > I used to put my local debs (kernels etc) into a directory > (/usr/local/src/debian-local/dists/local/local/binary-i386) > and then run this script: > > #!/bin/sh > cd /usr/local/src/debian-local > dpkg-scanpackages dists/local/local/binary-i386 /dev/null > > dists/local/local/binary-i386/Packages > gzip dists/local/local/binary-i386/Packages > > Then I would add this to sources.list: > > deb file:/usr/local/src/debian-local local/ Thanks, this is it! -- I did not vote for the Austrian government
Re: sources.list and locally generated debs
Chris Gray <[EMAIL PROTECTED]> wrote: >On Mon, 09 Apr 2001, Colin Watson wrote: >> Mario Vukelic <[EMAIL PROTECTED]> wrote: >>>My locally generated debs, e.g. from kernel compiles, show up as >>>obsolete in dselect. Is there an easy way to tell their locations to >>>the package manager or do I have to mess with Packages.gz files and >>>the like? >> >> You pretty much have to mess with Packages.gz, I'm afraid (at least, >> that's the easiest way I can think of). apt-ftparchive in the >> apt-utils package in testing/unstable may help. > >If I understand the question correctly, it seems the canonical answer >is to raise the version number of the locally created package. This >should keep dselect or apt from thinking that the local package is >obsolete. That stops packages you've taken from the Debian archive and modified locally from being overwritten on the next upgrade, certainly (you normally increase by 0.1). Packages you've created yourself and which don't exist at all in the archive will still appear in the "Obsolete/Local" section unless you create a pseudo-archive for yourself. >You can change the version of the package by adding to the >debian/changelog file. There is a nice mode in emacs to help you do >this. Also debchange (or dch) in the devscripts package. Cheers, -- Colin Watson [EMAIL PROTECTED]
Re: sources.list and locally generated debs
On Mon, 9 Apr 2001, Chris Gray wrote: > On Mon, 09 Apr 2001, Colin Watson wrote: > > Mario Vukelic <[EMAIL PROTECTED]> wrote: > >>My locally generated debs, e.g. from kernel compiles, show up as > >>obsolete in dselect. Is there an easy way to tell their locations to > >>the package manager or do I have to mess with Packages.gz files and > >>the like? > > > > You pretty much have to mess with Packages.gz, I'm afraid (at least, > > that's the easiest way I can think of). apt-ftparchive in the > > apt-utils package in testing/unstable may help. I used to put my local debs (kernels etc) into a directory (/usr/local/src/debian-local/dists/local/local/binary-i386) and then run this script: #!/bin/sh cd /usr/local/src/debian-local dpkg-scanpackages dists/local/local/binary-i386 /dev/null > dists/local/local/binary-i386/Packages gzip dists/local/local/binary-i386/Packages Then I would add this to sources.list: deb file:/usr/local/src/debian-local local/ I was never quite sure about the proper directory paths to set up, and in fact the names above might not be consistant and correct. Perhaps somebody can comment on, fix or improve this idea? ...RickM...
Re: sources.list and locally generated debs
On 09 Apr 2001 12:17:09 -0400, Chris Gray wrote: > If I understand the question correctly, it seems the canonical answer > is to raise the version number of the locally created package. This > should keep dselect or apt from thinking that the local package is > obsolete. You can change the version of the package by adding to the > debian/changelog file. There is a nice mode in emacs to help you do this. First, thanks to everyone who replied. To make it more concrete here's an example: I compile the kernel with 'make-kpkg --revision=Custom.2 kernel_image' and dpkg -i the resulting deb, as recommended in the debian FAQ. Now, when i start dselect, kernel-image-2.4 with installed version Custom.2 has no available version (since dselect doesn't know about the directory it lives in) and is therefore in section Obsolete/local. This is what I don't like. Thanks for comments, M. -- I did not vote for the Austrian government
Re: sources.list and locally generated debs
On Mon, 09 Apr 2001, Colin Watson wrote: > Mario Vukelic <[EMAIL PROTECTED]> wrote: >>My locally generated debs, e.g. from kernel compiles, show up as >>obsolete in dselect. Is there an easy way to tell their locations to >>the package manager or do I have to mess with Packages.gz files and >>the like? > > You pretty much have to mess with Packages.gz, I'm afraid (at least, > that's the easiest way I can think of). apt-ftparchive in the > apt-utils package in testing/unstable may help. If I understand the question correctly, it seems the canonical answer is to raise the version number of the locally created package. This should keep dselect or apt from thinking that the local package is obsolete. You can change the version of the package by adding to the debian/changelog file. There is a nice mode in emacs to help you do this. Cheers, Chris -- Got jag? http://www.tribsoft.com
Re: sources.list and locally generated debs
Mario Vukelic <[EMAIL PROTECTED]> wrote: >My locally generated debs, e.g. from kernel compiles, show up as >obsolete in dselect. Is there an easy way to tell their locations to the >package manager or do I have to mess with Packages.gz files and the >like? You pretty much have to mess with Packages.gz, I'm afraid (at least, that's the easiest way I can think of). apt-ftparchive in the apt-utils package in testing/unstable may help. -- Colin Watson [EMAIL PROTECTED]
sources.list and locally generated debs
Hi, My locally generated debs, e.g. from kernel compiles, show up as obsolete in dselect. Is there an easy way to tell their locations to the package manager or do I have to mess with Packages.gz files and the like? Thanks for comments, M. -- I did not vote for the Austrian government
