Re: Creating local package cache with apt-move
Lo, on Sunday, March 31, Simon Hepburn did write: > Richard Cobbe wrote: > > > On a related note, how come /var/lib/dpkg/available keeps getting hosed? > > It's happened to me twice now. The first time, I figured I was SOL and > > re-installed from scratch (fortunately I didn't lose much). It happened > > again about an hour ago, but I recovered by blowing away the existing > > copy (on the grounds that I didn't have anything to lose) and rerunning > > `dselect update', which recreated it correctly. What's going on here? > > Not sure. Did you originally create your local mirror with apt-move > 3.x (potato version) ? Are you now using 4.x (woody version) ? If so > you need to read /usr/share/doc/apt-move/README. There were major > changes between 3.x and 4.x. If you have not done apt-move fsck then > perhaps the Packages.gz apt-move creates are corrupted and this in > turn is affecting /var/lib/dpkg/available. No, I upgraded to woody from a brand-new, minimal potato install, so I only started creating the mirror with apt-move 4.1.20. I am running apt-move fsck as I type this, though, so we'll see if that fixes the problem. Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Creating local package cache with apt-move
Richard Cobbe wrote: > On a related note, how come /var/lib/dpkg/available keeps getting hosed? > It's happened to me twice now. The first time, I figured I was SOL and > re-installed from scratch (fortunately I didn't lose much). It happened > again about an hour ago, but I recovered by blowing away the existing > copy (on the grounds that I didn't have anything to lose) and rerunning > `dselect update', which recreated it correctly. What's going on here? Not sure. Did you originally create your local mirror with apt-move 3.x (potato version) ? Are you now using 4.x (woody version) ? If so you need to read /usr/share/doc/apt-move/README. There were major changes between 3.x and 4.x. If you have not done apt-move fsck then perhaps the Packages.gz apt-move creates are corrupted and this in turn is affecting /var/lib/dpkg/available. -- Simon Hepburn. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Creating local package cache with apt-move
Lo, on Saturday, March 30, Simon Hepburn did write: > Richard Cobbe wrote: > > > No, the three slashes are in fact correct. > > Hrmm.. just to add to the confusion. I just checked my sources.list > and saw I was using single slash. I did man sources.list to see if I > was going out of my mind. I'm not. No; it's apparently variable. Still, the apt-move manpage did say to use a file: URI, and every time I've seen those on a Unix system to date, they've started with three slashes. That, however, may be a netscape/mozilla peculiarity; I believe the kernel considers multiple consecutive slashes to be superfluous and throws away all but one. > > Turns out you have to write the Release files by hand. > > I have never had to do that. If I comment out all lines in sources.list > except my local mirror and do dselect|update I get to see everything in > there. > I'm not sure this is the problem. I just checked your apt-move.conf > again and noticed a couple of problems: > > ARCHS="alpha arm hurd-i386 i386 m68k powerpc sparc" > Do you really have all these installed ;-) Yeah, I realized that only *after* I did a `apt-move sync' and pulled down all sorts of random crud. This is now "i386" only. > DIST=potato > This should be testing. At least, that's what your sources.list points to. > They need to be the same. Yeah; saw that at the same time; it's now `woody'. > However... > > > Things are fine now; apt-get and dselect see the package files in my > > local mirror. (I found found this after a little bit more careful > > digging through the debian-user archives.) ...where `now' is defined to mean `after I fixed the above two settings.' > If it ain't broke don't fix it :-) In general, I agree, but I would like to understand exactly what's going on here. I may try moving the Release files outside the mirror, commenting everything out of sources.list, and trying again. > > > BTW when I reply to your message only part of it shows up in my > > > mailer. Not sure if that is my problem or yours. > > > > I doubt this is a problem; it's probably just the way KMail works. I > > included the sources.list and apt-move.conf files as MIME attachments > > (text/plain); a lot of mailers tend to display that MIME type inline but > > not include it in replies. I know VM works that way, ISTR that > > Netscape's mailer does also. > > I guessed they were attachments #1 and #2, what I was referring to was this: > > "Any advice would be very welcome. > > Thanks, > > Richard" Oh. More attachment stuff; this is just how VM handles attachments interposed into the body of the message. I'd attached the two config files, then kept typing; VM basically considers everything after the first attachment to be an attachment, possibly of type text/plain with inline content disposition. On a related note, how come /var/lib/dpkg/available keeps getting hosed? It's happened to me twice now. The first time, I figured I was SOL and re-installed from scratch (fortunately I didn't lose much). It happened again about an hour ago, but I recovered by blowing away the existing copy (on the grounds that I didn't have anything to lose) and rerunning `dselect update', which recreated it correctly. What's going on here? Thanks much for your advice, Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Creating local package cache with apt-move
Richard Cobbe wrote: > No, the three slashes are in fact correct. Hrmm.. just to add to the confusion. I just checked my sources.list and saw I was using single slash. I did man sources.list to see if I was going out of my mind. I'm not. > Turns out you have to write the Release files by hand. I have never had to do that. If I comment out all lines in sources.list except my local mirror and do dselect|update I get to see everything in there. I'm not sure this is the problem. I just checked your apt-move.conf again and noticed a couple of problems: ARCHS="alpha arm hurd-i386 i386 m68k powerpc sparc" Do you really have all these installed ;-) DIST=potato This should be testing. At least, that's what your sources.list points to. They need to be the same. However... > Things are fine now; apt-get and dselect see the package files in my > local mirror. (I found found this after a little bit more careful > digging through the debian-user archives.) If it ain't broke don't fix it :-) > > BTW when I reply to your message only part of it shows up in my > > mailer. Not sure if that is my problem or yours. > > I doubt this is a problem; it's probably just the way KMail works. I > included the sources.list and apt-move.conf files as MIME attachments > (text/plain); a lot of mailers tend to display that MIME type inline but > not include it in replies. I know VM works that way, ISTR that > Netscape's mailer does also. I guessed they were attachments #1 and #2, what I was referring to was this: "Any advice would be very welcome. Thanks, Richard" showing up as attachment #3 in your original post. -- Simon Hepburn. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Creating local package cache with apt-move
Lo, on Saturday, March 30, Simon Hepburn did write: > Richard Cobbe wrote: > > > I've added the local mirror to sources.list, but neither apt-get nor > > dselect appears to see these files. What step have I missed? > > It's a simple typo. Change deb file:///home... to deb file://home... No, the three slashes are in fact correct. Turns out you have to write the Release files by hand. (I have to say, I do wish this part of the process were documented better---if not necessarily in the apt-move manpage, then at least in /usr/share/doc/apt-move. It looks like there are already some bug reports which address this, though.) So, I created the following release files ./dists/woody/main/binary-i386/Release ./dists/woody/contrib/binary-i386/Release ./dists/woody/non-US/main/binary-i386/Release ./dists/woody/non-US/contrib/binary-i386/Release ./dists/woody/non-US/non-free/binary-i386/Release ./dists/woody/non-free/binary-i386/Release based on the following model (with different Component values as appropriate): Archive: testing Component: main Origin: Debian Label: Debian Architecture: i386 Things are fine now; apt-get and dselect see the package files in my local mirror. (I found found this after a little bit more careful digging through the debian-user archives.) > BTW when I reply to your message only part of it shows up in my > mailer. Not sure if that is my problem or yours. I doubt this is a problem; it's probably just the way KMail works. I included the sources.list and apt-move.conf files as MIME attachments (text/plain); a lot of mailers tend to display that MIME type inline but not include it in replies. I know VM works that way, ISTR that Netscape's mailer does also. Thanks, Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Creating local package cache with apt-move
Richard Cobbe wrote: > I've added the local mirror to sources.list, but neither apt-get nor > dselect appears to see these files. What step have I missed? It's a simple typo. Change deb file:///home... to deb file://home... BTW when I reply to your message only part of it shows up in my mailer. Not sure if that is my problem or yours. -- Simon Hepburn. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Creating local package cache with apt-move
Lo, on Friday, March 29, Richard Cobbe did write: > Greetings, all. > > I know this is a FAQ, but I can't find the answer anywhere. > > So, I'm in the process of upgrading from stable to testing (again---the > first time, somebody crapped on /var/lib/dpkg/available, and I couldn't > repair it. There was a large chunk missing out of the middle, so far as > I could tell). > > So, I dutifully saved all the .deb files I downloaded during the first > attempt, and I used apt-move to move them off to another directory. > I've added the local mirror to sources.list, but neither apt-get nor > dselect appears to see these files. What step have I missed? > > When I do a dselect update or an apt-get update, I see messages that > appear to indicate that it is ignoring the Release file in my local > mirror. I've rebooted into potato, so I don't have the error message > handy. In any case, when I install packages that I do have locally, > dselect still downloads them off the 'net. Sorry; I should have pointed out in my first post that cd /home/mirrors/debian find . -name Release\* -print doesn't find anything. Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Creating local package cache with apt-move
Greetings, all. I know this is a FAQ, but I can't find the answer anywhere. So, I'm in the process of upgrading from stable to testing (again---the first time, somebody crapped on /var/lib/dpkg/available, and I couldn't repair it. There was a large chunk missing out of the middle, so far as I could tell). So, I dutifully saved all the .deb files I downloaded during the first attempt, and I used apt-move to move them off to another directory. I've added the local mirror to sources.list, but neither apt-get nor dselect appears to see these files. What step have I missed? When I do a dselect update or an apt-get update, I see messages that appear to indicate that it is ignoring the Release file in my local mirror. I've rebooted into potato, so I don't have the error message handy. In any case, when I install packages that I do have locally, dselect still downloads them off the 'net. # See sources.list(5) for more information, especialy # Remember that you can only use http, ftp or file URIs # CDROMs are managed through the apt-cdrom tool. #deb http://http.us.debian.org/debian stable main contrib non-free #deb http://non-us.debian.org/debian-non-US stable/non-US main contrib non-free #deb http://security.debian.org stable/updates main contrib non-free # Uncomment if you want the apt-get source function to work #deb-src http://http.us.debian.org/debian stable main contrib non-free #deb-src http://non-us.debian.org/debian-non-US stable non-US deb file:///home/mirrors/debian/ testing main non-free contrib deb http://mirrors.kernel.org/debian/ testing main non-free contrib deb-src http://mirrors.kernel.org/debian/ testing main non-free contrib deb http://download.sourceforge.net/debian/ testing main non-free contrib deb-src http://download.sourceforge.net/debian/ testing main non-free contrib deb http://non-us.debian.org/debian-non-US testing/non-US main non-free contrib deb-src http://non-us.debian.org/debian-non-US testing/non-US main non-free contrib # Configuration file for the apt-move script. # # You should modify the following configuration to suit your system. # See the apt-move(8) manpage for information about these settings. # # The defaults for this file are simply the settings I currently use. # Configuration for apt-move script -- # The sites in ``/etc/apt/sources.list'' that you wish to mirror. #APTSITES="debian.midco.net non-us.debian.org" APTSITES="mirrors.kernel.org download.sourceforge.net non-us.debian.org" # The architectures that your site contain, separated with spaces. ARCHS="alpha arm hurd-i386 i386 m68k powerpc sparc" # The absolute path to your debian directory (top of your local mirror). # This MUST appear as the first entry of your sources.list if you use # sync or mirror. LOCALDIR=/home/mirrors/debian # The distribution you want to mirror (see the apt-move(8) manpage for # details) DIST=potato # The package types you want to mirror. # Possible values are: binary, source, and both (use only one). PKGTYPE=binary # The full (absolute) path to your local cache of package files. The default # will work for the apt-get packages, unless you've reconfigured apt. FILECACHE=/var/cache/apt/archives # The full (absolute) path to your local cache of Packages files. The # default will work for the apt-get Packages, unless you've reconfigured apt. LISTSTATE=/var/lib/apt/lists # Do you want apt-move to delete obsolete files from your mirror? (yes/no) DELETE=no # Maximum percentage of files to delete during a normal run. MAXDELETE=20 # Only move packages if its version matches "exactly" with the master files. # (yes/no) STRICTMOVE=no # End Configuration -- Any advice would be very welcome. Thanks, Richard
