[00:11] <postg> could someone help me look at the error: http://paste.uni.cc/17831
[00:11] <postg> I try to upgrade from 7.04 - > 7.10
[00:12] <postg>  I do upgrade 7.04 first, before upgrading
[00:13] <postg> from these error message, most likely , it is  eieio/emacs error
[00:13] <postg> config error
[00:13] <postg> h eieioow can I fix it?
[00:13] <postg> how can I fix it?
[00:13] <Flare183> might have more luck in #ubuntu-server
[00:14] <postg> someone on #ubuntu sugguest me doing a freash install, that's thing I cannot afford to
[00:14] <postg> yes, Flare183
[00:14] <postg> me?
[00:14] <Flare183> yeah
[00:14] <Flare183> not alot of people in here
[00:14] <postg> but it's installer problem
[00:14] <postg> yes
[00:14] <Flare183> yeah but it's also a server problme
[00:14] <Flare183> problem
[00:14] <postg> twb is here
[00:15] <postg> he is the person who help me when I was upgrading to 7.04
[00:15] <Flare183> twb:> dude lend a hand please
[00:33] <Flare183> nothing
[00:54] <postg> hello, should  Iremove these error package first?
[00:54] <postg> http://paste.uni.cc/17832
[01:05] <postg> thanks Flare183
[01:06] <postg> I fixed it
[01:06] <Flare183> yeah!
[01:06] <Flare183> great
[01:06] <Flare183> how?
[01:06] <Flare183> lol
[01:06] <postg> yeah!
[01:06] <postg> force remove eieio
[01:07] <postg> so simple
[01:07] <postg> just try it
[01:07] <Flare183> oh wow
[01:07] <postg> remove/eieio: purging byte-compiled files for emacs22
[01:08] <Flare183> i should of thought of that a long time ago but oh well now
[01:08] <Flare183> 6 years since that error
[01:08] <postg> great result!
[01:08] <postg> dont need to reinstall, haha
[02:17] <twb> d-i uses the wrong driver in xorg.conf (via instead of vesa).  What is the most elegant way to force it to use a particular video driver?
[02:18] <twb> Aha, found it: xserver-xorg    xserver-xorg/config/device/driver       select  ati
[05:58] <twb> cjwatson: ping?
[05:58] <twb> That didn't work, it's still using the via driver :-(
[08:09] <cjwatson> twb: you need to ask the X people
[08:14] <twb> Surely not the xorg people -- I'm pretty sure this is related the debconf code for xserver-xorg
[08:29] <cjwatson> which is maintained by the Debian/Ubuntu X maintainers
[08:29] <cjwatson> it's not part of the installer
[08:29] <cjwatson> (it happens to be fairly closely related, but we don't deal with it)
[09:03] <tjaalton> twb: which pci-id?
[09:03] <tjaalton> twb: do you have multiple video adapters installed?
[09:06] <superm1> cjwatson, i didn't see an ack on the branch to merge.  Would you like me to file a bug against user-setup so it doesn't get forgotten?
[09:16] <cjwatson> superm1: oh, yes, please do file a bug, I haven't looked at the branch yet
[09:16] <CIA-4> ubiquity: cjwatson * r2389 ubiquity/ (d-i/Makefile d-i/update-control debian/changelog):
[09:16] <CIA-4> ubiquity: * Update d-i/update-control to work with the new Dpkg::Deps module in
[09:16] <CIA-4> ubiquity:  dpkg-dev 1.14.8.
[09:16] <cjwatson> superm1: I'll probably actually just commit it upstream
[09:17] <superm1> cjwatson, okay cool.  it's a small patch too.
[09:17] <cjwatson> superm1: I think it would be best to add an entry for it to the templates file too
[09:17] <cjwatson> even though it isn't strictly required if it's only going to be used by preseeding
[09:19] <superm1> yeah that's why i wasn't sure it was necessary
[09:19] <superm1> i'll add that, push, and then file a bug
[09:19] <cjwatson> superm1: I don't think the code you added for useradd will work, not that I hugely care
[09:19] <cjwatson> useradd -g requires an existing group
[09:19] <superm1> according to the man page the syntax looked right
[09:19] <cjwatson> probably needs to do groupadd separately
[09:19] <superm1> oh you're right
[09:19] <cjwatson> syntax is fine but semantics are wrong
[09:19] <cjwatson> :-)
[09:21] <superm1> the case that /usr/sbin/adduser isn't around, when does that come up for installations?
[09:26] <twb> 19:29 <cjwatson> (it happens to be fairly closely related, but we don't deal with it)
[09:26] <twb> cjwatson: OK.
[09:26] <twb> 20:03 <tjaalton> twb: which pci-id?
[09:27] <twb> tjaalton: I don't have the number offhand, but I spoke to the #unichrome people and they added it to their list of IDs
[09:27] <twb> tjaalton: the default "via" driver works, but only on the external head
[09:27] <twb> (It's a laptop, only one video card.)
[09:27] <twb> Er, and "their" means openchrome.org, not unichrome.sf.net
[09:28] <twb> tjaalton: here we go 17:49 <gabriel> twb: the ID is missing: (EE) VIA(0): Unknown Card-IDs (1071|8650); please report to <openchrome-users@openchrome.org>
[09:29] <tjaalton> we probably should follow fedora and default to unichrome..
[09:29] <twb> ...so vesa works on both heads on gutsy, and svn openchrome works on gutsy+1, but via/gutsy only works on the external head.
[09:30] <superm1> twb, openchrome 0.3 is available in hardy
[09:30] <twb> superm1: yeah, I didn't end up trying that.
[09:30] <cjwatson> superm1: it doesn't, in Ubuntu
[09:31] <cjwatson> superm1: it might do if you were producing a stripped-down Debian variant
[09:31] <superm1> cjwatson, all i was saying is that I packaged up openchrome for hardy a few weeks ago
[09:32] <twb> cjwatson: should I be hassling the Debian X Strike Force, or some Ubuntu derivate thereof?  Either way, do you know if they have a dedicated channel (maybe on OFTC)?
[09:32] <tjaalton> twb: #ubuntu-x
[09:32] <twb> Thanks.
[09:33] <cjwatson> superm1: I was replying to your question about adduser
[09:33] <superm1> cjwatson, oh :)
[10:23] <CIA-4> debian-installer: cjwatson * r862 ubuntu/ (build/util/help-to-gfxboot.py debian/changelog):
[10:23] <CIA-4> debian-installer: * Encapsulate UTF-8 encoding pain differently in
[10:23] <CIA-4> debian-installer:  build/util/help-to-gfxboot.py. (The resulting code is longer but I think
[10:23] <CIA-4> debian-installer:  the horribleness is better-positioned.)
[10:24] <cjwatson> excellent, my CIA bot cunning worked
[10:24] <cjwatson> debian-installer svn commits -> #debian-boot, bzr commits -> #ubuntu-installer
[10:24] <cjwatson> logic not perfect but it'll do for now
[10:25] <cjwatson> not sure I feel like manually writing out all the d-i subprojects though ... maybe some other day
[10:26] <CIA-4> oem-config: cjwatson * r389 oem-config/ (d-i/Makefile d-i/update-control debian/changelog):
[10:26] <CIA-4> oem-config: * Update d-i/update-control to work with the new Dpkg::Deps module in
[10:26] <CIA-4> oem-config:  dpkg-dev 1.14.8.
[10:34] <cjwatson> ok, automation works wonders, I think I have all the d-i components set up for CIA notifications now
[10:35] <cjwatson> at least all the ones with bzr imports that I know about
[12:11] <CIA-4> ubiquity: cjwatson * r2390 ubiquity/ (d-i/manifest debian/changelog):
[12:11] <CIA-4> ubiquity: * Automatic update of included source packages: apt-setup 1:0.31ubuntu2,
[12:11] <CIA-4> ubiquity:  base-installer 1.86ubuntu1, debian-installer-utils 1.50ubuntu1,
[12:11] <CIA-4> ubiquity:  partman-auto 73ubuntu1, partman-base 114ubuntu1, partman-basicmethods
[12:11] <CIA-4> ubiquity:  36, partman-efi 14ubuntu1, partman-partitioning 54ubuntu1.
[12:19] <CIA-4> ubiquity: cjwatson * r2391 ubiquity/debian/po/ (79 files): debconf-updatepo
[12:59] <CIA-4> ubiquity: cjwatson * r2392 ubiquity/ (4 files in 3 dirs):
[12:59] <CIA-4> ubiquity: * Update partman extensions to cope with changes in partman-base 114
[12:59] <CIA-4> ubiquity:  (/lib/partman/definitions.sh -> /lib/partman/lib/base.sh).
[13:02] <CIA-4> ubiquity: cjwatson * r2393 ubiquity/debian/ (80 files in 2 dirs): mark ${PARTITIONS} untranslatable
[13:04] <CIA-4> ubiquity: cjwatson * r2394 ubiquity/debian/ (80 files in 2 dirs): sync templates with migration-assistant changes
[13:11] <CIA-4> ubiquity: cjwatson * r2395 ubiquity/debian/changelog: releasing version 1.7.2
[13:24] <soren> Sheesh. Calm down.
[13:26] <soren> cjwatson: I'm supposed to be implementing some form of iscsi support in the installer. Can you think of any other installer components doing something like that that I could look at for inspiration? AFAIK (I'm a complete iscsi n00b), it's mostly a matter of passing some information to the iscsi initiator thing which (AFAIK) creates some block devices for the installer to use..
[13:27] <cjwatson> err, sounds a little like how dmraid works, though that's a freaky hard
[13:27] <cjwatson> er, a freaky hack
[13:28] <cjwatson> or maybe the other lvm/raid stuff
[13:28] <soren> Hmm..
[13:28] <soren> I was thinking that it should preceed all of that.
[13:28] <soren> All of the lvm/raid stuff needs to happen at the same time, because it can be layered like crazy.
[13:29] <soren> that's not the case for iscsi. It just makes some block devices available for the rest of the partitioning magic to use.
[13:32] <cjwatson> you could use an init.d script then
[13:32] <cjwatson> /lib/partman/init.d that is
[13:33] <soren> Sounds like a sensible place for it. I can interact with the user there?
[13:33] <soren> debconf style, of course.
[13:33] <cjwatson> in principle yes, though I don't think anything else in init.d does
[13:34] <cjwatson> hmm
[13:34] <cjwatson> from the sound of it, a better place would actually be disk-detect (in the hw-detect source package)
[13:35] <cjwatson> since it's fundamentally just a weird case of disk block device detection
[13:35] <soren> It is.
[13:36] <soren> And yes, that does sound more sensible.
[13:36] <soren> I'm stilling trying to get an overview of all the components and how they fit together, so I'll probably be bouncing this sort of thing off of you for a bit. Hope that's ok.
[13:36] <cjwatson> no problem at all
[13:37] <cjwatson> I know it's a bit of a maze at first
[13:37] <soren> Think of it as an investment :)
[13:37] <cjwatson> I do :)
[14:07] <soren> cjwatson: What's this doing at the top of disk-detect.sh?
[14:07] <soren> if [ "$(uname)" != Linux ]; then exit 0
[14:07] <soren> fi
[14:07] <soren> Seems a bit superfluous :)
[14:07] <soren> Ah, hurd?
[14:09] <cjwatson> I imagine so
[14:09] <cjwatson> or freebsd
[14:10] <cjwatson> d-i doesn't actually work completely on either of those yet, but has been partially ported in places
[14:10] <cjwatson> might as well leave the stuff in since it's generally cheap and saves doing it again when the time comes
[14:11] <soren> Sure. I didn't think of the freebsd or hurd use cases and then it seemed a bit odd.
[14:38] <soren> cjwatson: I'm trying to work out why disk-detect get installed and called.. Any hints?
[14:41] <soren> cjwatson: I can't find it anywhere in any dependency chain.. d-i itself only mentions it in documention, afaics..
[14:42] <cjwatson> it's got an Installer-Menu-Item control field, so main-menu calls it
[14:43] <cjwatson> it goes roughly in menu-item number order, modified by requirements imposed by dependencies
[14:51] <soren> Ah, so it does.
[14:51] <soren> What makes sure that it get installed at all, though?
[15:04] <soren> Ah, think I got it.
[15:05] <soren> grep is hard..
[15:07] <cjwatson> soren: partman-base is Priority: standard, depends on harddrive-detection, provided by disk-detect
[15:07] <cjwatson> anything Priority: standard gets installed by default
[15:08] <soren> cjwatson: Oh. disk-detect is also mentioned in the pkg-list of debian-installer.
[15:08] <soren> Ah, but that just includes it in the installer, that doesn't actually install it.
[15:09] <cjwatson> right
[15:09] <soren> Ok.. Got it.
[15:09] <cjwatson> s/installer/initrd/
[15:09] <soren> Er, yes.
[15:10] <soren> Ok, so all the ordering stuff mentioned here http://d-i.alioth.debian.org/doc/talks/debconf6/paper/  is generally dictated by Installer-Menu-Item.
[15:39] <soren> cjwatson: I'm just looking at the code to support dmraid.. It seems to me that the only way to enable it is by preseeding.. Is that a general approach to these more exotic kinds of things, or is it merely because its considered experimental?
[15:42] <cjwatson> probably best not to use dmraid as an example
[15:45] <soren> cjwatson: Oh?
[15:45] <cjwatson> it's a nasty hack in a bunch of ways, one of which is the UI issue you mention
[15:46] <cjwatson> if you can detect whether it's sane to enable iscsi, that's a lot better
[15:46] <cjwatson> but if you can't detect it, then yeah, you're probably going to have to either (a) use preseeding (b) make it an optional installer components
[15:46] <cjwatson> s/s$//
[15:47] <soren> cjwatson: If I go with (b) I need to create a separate udeb, I suppose.. How would I then get access to that in the installer?
[15:47] <soren> Is there a way to get a list of the available udebs and the choose to install one?
[15:48] <cjwatson> in expert mode it'll ask
[15:48] <cjwatson> or you can preseed anna/choose_modules=some_extra_thing
[15:48] <soren> Oh, I see.
[15:49] <cjwatson> if it's not very much code, it would probably be easier to put it in disk-detect and have a preseed for that
[15:49] <cjwatson> we could even alias it ... iscsi => hw-detect/enable_iscsi or whatever
[15:50] <soren> I don't think it's going to be a lot of code, no, but I need to create a udeb anyway to have the userspace tools available in the installer.
[15:50] <soren> I didn't think of that until just now.
[15:50] <cjwatson> right, but that's a udeb built out of the main iscsi source package or whatever; installer integration is often separate
[15:50] <cjwatson> though, hmm, it would have to depend on the tools, that does suggest a separate udeb
[15:51] <soren> Well, the dmraid code just anna-install's the dmraid-udeb if it gets activated.
[15:53] <soren> I can't really decide which approach makes more sense.
[15:53] <soren> Doing the configuration after partman is kind of useless, I suppose, and the only way to make sure it's done prior to that is to hook it into disk-detect (or something simiar).
[15:54] <soren> Or?
[15:55] <soren> And from there conditionally install the userspace utilities using anna if the user needs iscsi.
, sorry
[16:38] <soren> I'm in a meeting myself, so no worries.
[16:50] <cjwatson> ok, off
[16:50] <cjwatson> you definitely want to do it before partman
[16:51] <cjwatson> using anna-install would be OK
[16:51] <cjwatson> that way you wouldn't need a separate udeb for the installer integration, and could just use anna-install instead of a hard dependency
[17:00] <soren> Exactly.
[20:06] <Goosemoose> Can I get my server running apt-cache to handle the security updates too? Right now the clients are looking out to the internet to download security updates and the firewall is blocking them
[20:07] <Goosemoose> Right now I'm using: d-i mirror/http/directory string /us.archive.ubuntu.com/ubuntu and d-i apt-setup/security_host us.archive.ubuntu.com because install wasn't working without it. Now I opened the firewall just for that client and it goes through
[20:07] <Goosemoose> I'd rather it get it all from the server though
[20:31] <soren> Goosemoose: Why not just point it at your apt-cacher?
[20:36] <Goosemoose> for the directory string?
[20:36] <Goosemoose> i had tried that a few days ago and got an error, maybe it was just a fluke, i can try it again
[20:36] <Goosemoose> right now i have d-i mirror/http/hostname string 10.0.2.131:3142
[20:37] <soren> Goosemoose: No, for the security_host.
[20:38] <Goosemoose> so you're saying add d-i mirror/http/directory string 10.0.2.131:3142
[20:38] <soren> No.
[20:38] <soren> Leave mirror/blah as is.
[20:38] <soren> Do:
[20:39] <soren> di apt-setup/security_host string 10.0.2.131:3142
[20:39] <soren> Er..
[20:39] <soren> d-i apt-setup/security_host string 10.0.2.131:3142
[20:39] <soren> Hm.. Hang on.
[20:40] <soren> Oh, I see the problem now!
[20:40] <soren> Hah..
[20:41] <Goosemoose> I'm listening :D
[20:42] <soren> I said I saw the problem. Not the solution :)
[20:42] <soren> It seems that /security is hardcoded.
[20:42] <Goosemoose> haha
[20:42] <soren> Er..
[20:42] <Goosemoose> doh
[20:42] <soren> I mean /ubuntu
[20:42] <Goosemoose> ok, that would explain why i couldn't get it to work
[20:43] <Goosemoose> soooo, should i create a symlink called ubuntu or something to trick it?
[20:43] <soren> That won't work.
[20:43] <soren> apt-cacher doesn't look at file system paths, it just uses the first bit of the URI to know which host to actually ask for the files.
[20:44] <soren> Hm... I belive apt-cacher has some sort of aliasing system..
[20:44] <soren> It does.
[20:44] <soren> You could add something like:
[20:44] <Goosemoose> so even if i type in d-i apt-setup/security_host string 10.0.2.131:3142 its still looking at the /ubuntu location
[20:45] <Goosemoose> ok, listening
[20:45] <soren> path_map = ubuntu security.ubuntu.com/ubuntu
[20:45] <soren> to apt-cacher.conf
[20:45] <Goosemoose> ok
[20:45] <Goosemoose> you said to leave d-i mirror/http/directory string /us.archive.ubuntu.com/ubuntu alone?
[20:45] <Goosemoose> just change the security host
[20:45] <soren> As long as you make sure you always remember to use "/nn.archive.ubuntu.com/ubuntu" when you're not trying to get to the security stuff.
[20:46] <soren> Goosemoose: Yes.
[20:46] <Goosemoose> ok, but then wouldn't the client need access to that site?
[20:46] <soren> Ok, from the top:
[20:46] <soren> d-i mirror/http/directory string /us.archive.ubuntu.com/ubuntu
[20:47] <soren> d-i mirror/http/hostname string 10.0.2.131:3142
[20:47] <soren> d-i apt-setup/security_host string 10.0.2.131:3142
[20:47] <soren> Those three lines will result in the following in /etc/apt/sources.list:
[20:48] <soren> deb http://10.0.2.131:3142/us.archive.ubuntu.com/ubuntu gutsy main restricted blahblahbhal  # This is the regular (non-security) archive
[20:48] <soren> deb http://10.0.2.131:3142/ubuntu gutsy main restricted blahblahbhal  # This is the security archive
[20:48] <soren> The reason the latter works is due to the mapping we defined in apt-cacher.conf
[20:48] <soren> i.e. path_map = ubuntu security.ubuntu.com/ubuntu
[20:48] <Goosemoose> ok i see
[20:48] <Goosemoose> thanks, ill try that now
[20:49] <soren> What I was just pointing out was that it's an easy mistake to just put "deb http://10.0.2.131:3142/ubuntu gutsy main restricted blahblahbhal" in your sources.list if you're writing it by hand, but that will only get you the security updates, not the regular (non-security) archive.
[20:50] <Goosemoose> gotcha
[20:50] <soren> ...so you just need to keep that in mind.. Now that I've mentioned it, it might spring to mind if you start seeing a lot of stuff missing from your archive :)
[20:50] <Goosemoose> lol
[21:08] <cjwatson> there's a bug about the hardcoding of /ubuntu, it just needs to be cleaned up in a couple of places, and ideally the preseed template should go to Debian so that we don't end up diverging on its name
[21:10] <soren> cjwatson: You mentioned something about debconf aliases..
[21:10] <soren> cjwatson: Does that just provide a means for defining short-hands for keys or is it for key *and* value?
[21:11] <soren> cjwatson: I.e. can we make "iscsi" on the kernel command line mean "disk-setup/iscsi/enable=true"?
[21:11] <cjwatson> preseed_aliases in the preseed package
[21:11] <cjwatson> no, I think it would have to be iscsi=true
[21:11] <cjwatson> but I think that would be clearer anyway
[21:11] <soren> Oh, definitely.
[21:12] <soren> The other thing would just be a bonus.
[21:12] <soren> Ah..
[21:12] <soren> No.
[21:12] <soren> :)
[21:12] <soren> Never mind.
[21:14] <CIA-4> debian-installer: cjwatson * r863 ubuntu/debian/changelog: releasing version 20070308ubuntu23
[21:14] <cjwatson> xivulon: yes, that bug list is fine
[21:15] <xivulon> m,kkkkkkkkkkkkkkkkkkk[-0-;plkl-;[,0m
[21:16] <cjwatson> same to you
[21:16] <xivulon> kids at the keyboard,
[21:16] <cjwatson> heh
[21:16] <xivulon> sorry
[21:16] <cjwatson> evand: well done on -core-dev!
[21:17] <soren> cjwatson: The code that grabs the stuff from the kernel commandline and turns it into preseed stuff... Where's that? greping through the preseed code for /proc/commandline doesn't give me anything.
[21:17] <cjwatson> it's spelled /proc/cmdline ...
[21:17] <cjwatson> but in any case, it actually shows up as environment variables
[21:18] <soren> *headdesk*
[21:18] <cjwatson> /bin/env2debconf, called from /lib/debian-installer-startup.d/S30env-preseed
[21:18] <soren> Er... say what?
[21:18] <soren> How does it end up as environment variables?
[21:19] <cjwatson> I believe the kernel puts stuff from the kernel command line in the environment by default
[21:20] <soren> I've never noticed that. How odd.
[21:20] <cjwatson> it's possible that other init implementations clear it out
[21:20] <cjwatson> but busybox init doesn;t
[21:20] <cjwatson> doesn't
[21:21] <soren> That doesn't add up...
[21:21] <soren> The init in our initramfs goes through the contents of /proc/cmdline to fish them out..
[21:22] <soren> Why would it do that if they're already there?  Hmm..
[21:22] <cjwatson> don't recall, I just know it works. :)
[21:23] <soren> I'm just trying to work out if there was any simple way to magically turn "iscsi"  on the kernel command line into something useful. That would really be optimal.
[21:24] <soren> Even if it just set it to an empty string would be usable.
[21:24] <cjwatson> I don't think that's a good idea; it's too likely to clash with future options parsed by the kernel itself
[21:24] <cjwatson> even iscsi=true is skating on thin ice there
[21:25] <cjwatson> all the foo/bar=blah things are safe because the kernel never uses keys containing /
[21:25] <soren> Hm... point.
[21:30] <evand> thanks cjwatson !
[21:31] <evand> \o/
[22:19] <Goosemoose> damnit, still getting installation step failed and select and install software
[22:19] <Goosemoose> if i go back to the menu and click install it goes fine
[22:22] <Goosemoose> soren, the client still tried to access the internet via http://91.189.88.31/ubuntu/dists/gusty/Release
[22:27] <soren> I can't imagine why.. cjwatson is likely to have better guesses than me.
[22:36] <Goosemoose> cj, you still around?
[22:36] <Goosemoose> as soon as the install finishes here i can get the install log
[22:39] <soren> Goosemoose:  That would be lovely.
[22:42] <Goosemoose> almost there
[23:21] <Goosemoose> ok, got the file
[23:21] <Goosemoose> posting it to pastebin now
[23:27] <Goosemoose> wow its 6 megs
[23:27] <Goosemoose> guess ill need to post it to my site
[23:30] <Goosemoose> oops only 600k
[23:30] <Goosemoose> was gonna say!
[23:32] <Goosemoose> ok its up http://www.damien-hs.edu/syslog
[23:33] <Goosemoose> soren or cjwatson, if you guys see the problem ,please let me know
[23:33] <cjwatson> Dec 18 22:18:48 in-target: E: Method http has died unexpectedly!
[23:33] <soren> Goosemoose: How are you running your apt-cacher?
[23:34] <cjwatson> looks like random network interruption, hard to say for sure
[23:34] <cjwatson> at any rate that's internal to apt
[23:34] <Goosemoose> hmm, the server and client are hooked up to the same switch
[23:34] <cjwatson> could be a bug in the server, sure
[23:34] <Goosemoose> soren, followed that apt-cacher ubuntu install guide
[23:34] <cjwatson> mvo would be the best person to debug that
[23:34] <cjwatson> if it's possible to give him a reasonably compact reproduction recipe
[23:35] <Goosemoose> funny thing is if i go back when i get the software install errror to the menu, then click install software it goes through
[23:35] <cjwatson> right, hence my "random" comment
[23:35] <cjwatson> it might well work fine if you ran it through again
[23:35] <Goosemoose> happens every time though
[23:35] <Goosemoose> no, ran it 5 times
[23:35] <cjwatson> odd
[23:35] <Goosemoose> i still see it attempting to go through the firewall too, though I think it's sucessfull, but I want to avoid that for the other clients. This one I gave all access to
[23:36] <soren> It's apt-cacher that's messing up.
[23:36] <Goosemoose> interesting
[23:36] <soren> Sorry, I lost my network for a little bit.
[23:36] <Goosemoose> hmm
[23:36] <soren> Dec 18 22:11:58 base-installer:   500 Can't connect to ubuntu:80 (Bad hostname 'ubuntu')
[23:36] <Goosemoose> no problem soren
[23:36] <Goosemoose> ok, there is no machine called ubuntu:80
[23:36] <soren> Did you set those mappings as I said?
[23:36] <Goosemoose> so why would it be connecting to that?
[23:36] <Goosemoose> yes
[23:36] <cjwatson> it dies twice, so it may just not be reliable enough to last for a full install ...
[23:36] <soren> Goosemoose: It's apt-cacher that's trying to connect to at host called ubuntu.
[23:37] <Goosemoose> strange
[23:37] <soren> Goosemoose: because those mappings aren't taking effect.
[23:37] <Goosemoose> path_map = ubuntu security.ubuntu.com/ubuntu
[23:37] <Goosemoose> i have that
[23:37] <Goosemoose> let me pastebin my apt config
[23:37] <soren> Where's that guide you mentioned?
[23:37] <cjwatson> oh yes, I misread that as a client-side error, good catch soren
[23:37] <Goosemoose> i have it printed, let me find it online
[23:37] <soren> I don't remember if it runs as a mod_perl thing..
[23:38] <Goosemoose> http://www.google.com/url?sa=t&ct=res&cd=1&url=http%3A%2F%2Fubuntu-tutorials.com%2F2007%2F01%2F08%2Fsave-bandwidth-during-updates-with-apt-cacher-ubuntu-610%2F&ei=0VloR7-WOaXqpATM9-nWBA&usg=AFQjCNEK1wayl7Xg7LchBYrDNfOg910M9Q&sig2=Y0hR-ArQXrHEw20kO12sIQ
[23:38] <soren> If it does, you might need to restart apache for those changes to take effect.
[23:38]  * cjwatson knows nothing about apt-cacher and will go to bed
[23:38] <Goosemoose> hmm, good point, it does run off of apache, let me try restarting apache
[23:38] <Goosemoose> good night cjwatson, thanks for the help
[23:38] <cjwatson> Goosemoose: BTW, if you want my attention, you need to say "cjwatson" for it to effectively highlight; I don't highlight just on "cj" because it would be a bit crazy
[23:38] <Goosemoose> sure thing
[23:38] <soren> cjwatson: When you've done that see what happens if you go to: http://10.0.2.131:3142/ubuntu
[23:38] <cjwatson> I'm on enough channels that I need mechanical assistance to keep up ;)
[23:39] <cjwatson> soren: not me :)
[23:39] <Goosemoose> let me see if i can go to that before i reboot
[23:39] <soren> cjwatson: Gah..
[23:39] <Goosemoose> yeah i have mine on my mirc at home
[23:39] <soren> Goosemoose: When you've done that see what happens if you go to: http://10.0.2.131:3142/ubuntu
[23:39] <Goosemoose> i can see it now before i reboot apache soren
[23:39] <soren> What can you see?
[23:39] <Goosemoose> looks like a php info type page
[23:40] <Goosemoose> Apt-cacher version 0.1
[23:40] <Goosemoose> has the config settings
[23:40] <Goosemoose> Usage: edit your /etc/apt/sources.list so all your HTTP sources are prepended with the address of your apt-cacher machine and the port, like this:
[23:40] <Goosemoose> deb http://ftp.au.debian.org/debian unstable main contrib non-free
[23:40] <Goosemoose> becomes
[23:40] <Goosemoose> deb http://yourcache.example.com:3142/ftp.au.debian.org/debian unstable main contrib non-free
[23:40] <soren> Does it show the mapping?
[23:40] <Goosemoose> no
[23:40] <Goosemoose> so let me reboot and then see if it does
[23:42] <soren> Try this: http://10.0.2.131:3142/ubuntu/dists/gutsy/Release
[23:43] <Goosemoose> ok restarted
[23:44] <Goosemoose> still dont see the mapping
[23:44] <Goosemoose> and that url never loads
[23:44] <soren> Odd. It works for me. I've just set the same mapping.
[23:44] <soren> Is your apt-cacher machine allowed to access security.ubuntu.com?
[23:44] <Goosemoose> hmm
[23:44] <soren> Firewallwise?
[23:44] <Goosemoose> yes, it has full access
[23:45] <Goosemoose> yup, looks like it's in new zealand when i ping it
[23:45] <soren> Did you stop and start apache? Or just reload?
[23:46] <Goosemoose> restart
[23:46] <soren> Goosemoose: That's very odd.
[23:46] <Goosemoose> ill try stop/start, should be the same
[23:46] <soren> Goosemoose: Mine shows it just fine on that page.
[23:47] <Goosemoose> http://pastebin.com/d7a66ab5
[23:47] <Goosemoose> there's my apt conf file
[23:48] <soren> Looks about right.
[23:48] <Goosemoose> hmm
[23:48] <Goosemoose> i dont have to restart apt right?
[23:48] <Goosemoose> it restarts with apache?
[23:51] <Goosemoose> hmm
[23:53] <Goosemoose> oh you can restart apt-cacher direclty, just a sec
[23:54] <Goosemoose> im running sudo aptitude update && sudo aptitiude upgrade and it seems to be d/l a lot of security files
[23:54] <Goosemoose> by the way, running sudo all the time is a huge PIA!