[00:01] <bryce> \sh_away: inkscape 0.46 is already in hardy
[00:19] <dbmood1> oi we have bug with ubuntu gutsy and local time in australia in in nsw
[00:19] <dbmood1> we need the time to move forwards one hour -- ntp is not providing the proper time
[00:20] <dbmood1> this is a major problem for security etc. and needs to be worked on as soon as possible
[00:20] <ScottK> StevenK: ^^^ How's your time now?
[00:20] <dbmood1> 11:20 instead of 10:20
[00:21] <dbmood1> i will to go tzdata now and see if i can fix it
[00:21] <dbmood1> http://www.timeanddate.com/worldclock/city.html?n=240
[00:21] <Fujitsu> dbmood1: Timezones won't change for another week.
[00:21] <Fujitsu> It changed this year. It's the first week in April.
[00:21] <dbmood1> http://www.abc.net.au/news/stories/2008/03/30/2202804.htm
[00:22] <dbmood1> it needs to be moved -- forwards and then back
[00:22] <dbmood1> Fujitsu: yes you are normal correct it was changed
[00:22] <Fujitsu> We should still be +11.
[00:22] <Fujitsu> Is it not 0021 UTC at the moment?
[00:23] <sistpoty> well, UTC doesn't change, does it?
[00:23] <dbmood1> let me try apply utc
[00:23] <Fujitsu> It doesn't, but my system says it's 1123 local time.
[00:23] <dbmood1> its 00:23:31 according to my altered clock
[00:23] <dbmood1> as in put back for daylight savings
[00:24] <Fujitsu> All of my systems are correctly still +11.
[00:24] <Fujitsu> THey weren't meant to switch back, and didn't.
[00:24] <Fujitsu> I checked this some weeks ago.
[00:24] <dbmood1> what ?
[00:24] <sistpoty> dbmood1: I saw a new tzdata coming in recently (maybe today, not too sure). do you have that installed already?
[00:24] <sistpoty> (for gutsy)
[00:24] <dbmood1> i'm using ntpd to update too...
[00:25] <dbmood1> is that a problem ?
[00:25] <Fujitsu> We're not meant to switch from +11 to +10 for another week. My Dapper, Gutsy, Hardy systems haven't switched yet.
[00:25] <dbmood1> well i have just switched
[00:25] <Fujitsu> dbmood1: Which version of Ubuntu are you running?
[00:25] <sistpoty> Fujitsu: lucky you... I'm loosing an hour tonight already :(
[00:25] <dbmood1> 7.10 here i can check hardy
[00:25] <Fujitsu> dpkg -l tzdata
[00:26] <dbmood1> Desired=Unknown/Install/Remove/Purge/Hold
[00:26] <dbmood1> | Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
[00:26] <dbmood1> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
[00:26] <dbmood1> ||/ Name           Version        Description
[00:26] <dbmood1> +++-[00:26] <dbmood1> ii  tzdata         2007f-3ubuntu1 time zone and daylight-saving time data
[00:26] <dbmood1> i might have my updates screwy ?
[00:27] <Fujitsu> Ooh, damn.
[00:27] <Fujitsu> You're right.
[00:28] <dbmood1> is it just me ?
[00:28] <dbmood1> or ...
[00:28] <Fujitsu> 2007f-3ubuntu1 is too old, I think.
[00:28]  * Fujitsu looks harder.
[00:28] <dbmood1> rofl oh cool
[00:28] <Fujitsu> I'm thoroughly confused.
[00:28] <dbmood1> thank you
[00:28] <dbmood1> sorry
[00:28] <dbmood1> seems all is fine
[00:28] <dbmood1> but iinet my isp repos are slightly outdated
[00:28] <dbmood1> or something
[00:29] <dbmood1> oh wait .... was the tz.. thing a recommended update ? because i don't have those ticked
[00:29] <ion_> Let's just get rid of the stupid DST altogether. :-)
[00:29] <Fujitsu> Oh what.
[00:29] <Fujitsu> WHy the heck did this only go into -updates?
[00:29] <dbmood1> let me tick recommended and see what happens
[00:29] <Fujitsu> dbmood1: That's the problem.
[00:30] <dbmood1> its a security bug it should be in security too tho
[00:30] <Fujitsu> The update has been in *-updates since 2008/03/07.
[00:30] <dbmood1> i don't imagine many people to have recommended ticked
[00:30] <Fujitsu> But not in -security.
[00:30] <Fujitsu> Most people should.
[00:30] <Fujitsu> This sort of update should really go into -security, I think...
[00:30] <dbmood1> is it default ?
[00:30] <Fujitsu> As it's utterly critical.
[00:30] <Fujitsu> I believe it is on by default.
[00:30] <dbmood1> hopefully
[00:31] <dbmood1> -- what about for lts and the server releases -- yeah that fixed it
[00:35] <pwnguin> how is a tzdata bug a security bug?
[00:35] <dbmood1> well if you have encryption that is based on time etc. / you get time based attacks
[00:36] <pwnguin> because you're an hour off from everyone else?
[00:36] <dbmood1> ........a whole hour
[00:36] <dbmood1> yes
[00:40] <dbmood1> got an end user to confirm (hopefully didn't touch it) that she doesnt' have the correct time ....
[00:40] <dbmood1> no wait
[00:40] <dbmood1> she got the update
[00:40] <pwnguin> well, there's a hardy tz bug
[00:42] <dbmood1> well i will know the full answer when she returns...
[00:43] <keescook> doko: got any pointers for pycentral usage with a package that has SWIG python bindings?  I seem to be missing some critical step -- everything gets built and installed but python can't seem to find it...
[00:44] <dbmood1> but my debian box has the correct time it seems and this is an etch box... zdata         2007j-1etch1   Time Zone and Daylight Saving Time Data Australia/Sydney  Sat Apr  5 15:59:59 2008 UTC = Sun Apr  6 02:59:59 2008 EST isdst=1 gmtoff=39600
[00:44] <dbmood1> Australia/Sydney  Sat Apr  5 16:00:00 2008 UTC = Sun Apr  6 02:00:00 2008 EST isdst=0 gmtoff=36000
[00:44] <dbmood1> sorry to be so spamish i will be quiet except to tell you the out come of the lady's update
[00:46] <Fujitsu> The change was made in 2007g.
[00:46] <slangasek> pwnguin: hrm? what tz bugs are there in hardy?
[00:46] <slangasek> pwnguin: more precisely, why is there no bug report about this that's importance: high and milestoned for the release? :)
[00:46] <Fujitsu> So anybody who has updated from -updates since 2007/10/20 will have the changes.
[00:47] <Fujitsu> If tzdata updates are only pushed to -updates, it shouldn't be `Recommended updates', it should be `Critical (unless you don't care about even slight accuracy of time) updates'
[00:48] <pwnguin> slangasek: they're actually bugs in gnome-clock-applet
[00:48] <dbmood1> in this case it is an hour off and they - end users who might not have it ticked will have it off - some admins might not want to allow the recommended -- or know about the change yet -- they probably have them off
[00:49] <pwnguin> slangasek: apparently it doesn
[00:49] <slangasek> pwnguin: oh, I guess you mean the fact that gnome-panel guesses your timezone wrong
[00:50] <pwnguin> yes. just mentioning it in case the above "end user" was merely judging from hardy, etc
[00:53] <dbmoodb> apparently if you do not turn ntp on the time even with the correct tzdata will not fix the problem immediately (end user result) -- hope you guys can start looking into this --- seems easy to fix and blah (package seems to be fine -- waiting for sometime i guess)
[00:55] <mttr> i installed the beta,, everthing went well but grub doesn't like the partition
[00:55] <Fujitsu> mttr: #ubuntu+1.
[00:55] <mttr> np
[02:27] <_MMA_> gah.. After new updates GDM sound nor logout sounds work. :(
[02:28] <jdong> _MMA_: and you're sad?
[02:30] <_MMA_> Well a little more than sad because this has been something that has broke for one reason or another for 2 releases now. But I don't wanna be a di*k about it yet.
[02:32] <ion_> dirk?
[02:32] <_MMA_> dick
[02:32] <ion_> Ah, right. I thought you mean dink.
[02:32] <_MMA_> If ya wanna be a smart-ass. ;)
[02:35] <_MMA_> Oh well. I'll work on it Monday.
[03:04] <lifeless> there will be a short outage to the wiki and bazaar.launchpad.net, to hoepfully address the bazaar.launchpad.net performance problems
[06:05] <Oasys> hey
[08:15] <warp10> good morning
[11:17] <Hobbsee> ah yes, australian time confusion
[11:18] <ompaul> we got 11 hours gap or 9 now?
[11:18] <ompaul> you fell back and we went fortward
[11:18] <Seveas> @now sydney
[11:18] <ubotu> Current time in Australia/Sydney: March 30 2008, 20:18:58 - Next meeting: Server Team in 3 days
[11:18] <ompaul> so 9
[11:19] <ompaul> no
[11:19] <Seveas> 8 for me
[11:19] <Seveas> 9 for you
[11:19] <Hobbsee> Seveas: that's wrong.
[11:19] <Hobbsee> Seveas: it's currently 9.18pm
[11:19] <Seveas> ah
[11:19] <ompaul> Hobbsee, you don't change for two weeks iirc
[11:19] <Seveas> Hobbsee, hmm, odd
[11:19] <Hobbsee> ompaul: yeah.  something like that.  i only noticed when the pin clock for work was showing the wrong time.
[11:19] <ompaul> Seveas, they are auzzies  ;-)
[11:20]  * Hobbsee beats ompaul before he can run away
[11:20]  * ompaul buys Hobbsee a cup of tea and tells her to work on getting her country to change time in sync with the rest of the planet (or close enough that it don't matter)
[11:20] <Seveas> there's no python-tz update for dapper
[11:21] <Seveas> fun :/
[11:36] <slangasek> ompaul: so every time some government nutter up here decides to extend DST by another few weeks, Australia should get a few weeks less DST? :)
[11:38] <pwnguin> sounds great
[11:39]  * persia discourages synchronisation.  Conference calls are annoying when there is more than one time transition happening the same week
[11:40] <Hobbsee> persia: this is why we all deal in UTC.
[11:41] <Hobbsee> this must mean that the UK/AU time crossover gets significantly worse again, though
[11:41] <persia> Hobbsee: True, although I've recently discovered that some people confuse UTC and British Time
[11:41] <Hobbsee> yeah, true
[11:43] <Fujitsu> I find it most unfortunate that those without -updates enabled are doomed to have incorrect times.
[11:43] <persia> I think anyone living in a country that changes the clocks is doomed to have incorrect times once in a while.
[11:44] <Fujitsu> If you have -updates, you're safe.
[11:47] <persia> (excepting at least Argentina)
[11:50] <Fujitsu> Well, if we're *really* quick...
[11:51] <persia> heh
[12:38] <ompaul> slangasek, na there is normally a two week lag between .eu and .au
[12:38] <ompaul> slangasek, after that you factor in the nutters ;-)
[12:38] <Seveas> ompaul, that's not just with DST
[12:40] <StevenK> Actually, NSW comes first. Except they've changed it so that all of .au changes DST (the states that use it) at the same time
[12:41] <persia> StevenK: Not only the same day, but the same time?
[12:43] <StevenK> persia: Well, I mean the same day. It used to be NSW dropped DST today, and the rest followed a week later. Now we all have to wait until next week
[12:43] <StevenK> (And well done Telstra for having your time sources on the phone network jump back an hour today)
[12:44] <Nafallo> lol
[12:44] <persia> Ah.  That makes more sense.  I thought it was something like 4am in the east, 3am in the middle, and 1am in the west
[12:45] <StevenK> Actually, 4am in the east, 3:30am in the middle and 1am in the west
[12:45] <persia> Err.  Never mind the bit about the west
[12:45] <persia> Huh?  I thought there was a timezone between Melbourne and Adelaide.  Time to study the time map again
[12:46] <StevenK> There is.
[12:46] <StevenK> Melbourne is +1100, and Adelaide is +1030
[12:46] <StevenK> Perth is +0800
[12:47] <StevenK> (After next week, it's +1000, +0930, +0800)
[12:48] <persia> Ah.  And Victoria and NSW are the same.  Right.  And summer time expires in West Australia in 2009.
[12:50] <StevenK> persia: Yes, Victoria and NSW are the same in terms of DST. Queensland is not.
[12:51] <persia> Ah.  That was the source of confusion.  Thank you.
[13:38] <emgent> hello
[13:55] <pitti> lamont: look at what?
[13:56] <pitti> lamont: sorry, tab error; unping
[14:58] <emgent> hi dendrobates :)
[16:51] <Riddell> calc: KDE 4 uses shared-mime-info, KDE 3 not
[18:24] <keescook> why does glib2.0 have such an odd version number?  it's less than the unstable version it's based off of
[18:24] <keescook> it really should be named 2ubuntu1 not ~hardy1
[18:27] <jdong> I was wondering about that too
[18:38] <calc> Riddell: is there a way for me to query what kde 3 uses for particular files to see what i need
[18:46] <keescook> jdong: 209308
[18:46] <jdong> bug 209308
[18:46] <ubotu> Launchpad bug 209308 in glib2.0 "glib2.0 version is wrong" [Undecided,Confirmed] https://launchpad.net/bugs/209308
[18:47] <jdong> cool
[18:54] <calc> doko: how is the progress on the i18n stuff?
[18:54] <doko> looking ...
[18:55] <calc> doko: i'm testing my first full build right now, so it might be ready for upload tomorrow
[18:55] <doko> yes, second build finished, I'll let you know tonight
[18:55] <calc> doko: great :)
[19:11] <ffm> Does anyone here work on wubi?
[19:13] <calc> the cairo patch fixes OOo font display issues :)
[19:14] <protonchris> calc: which patch?
[19:14] <jdong> calc: so I have to scroll back 24hrs in my IRC logs to understand the context of that statement? :D
[19:15] <calc> jdong: no, if you notice OOo fonts have looked wrong for like forever, they will be fixed probably tomorrow (when i manage to upload)
[19:15] <calc> it was using cairo/libfreetype incorrectly :)
[19:15] <jdong> calc: awesome! and yes, I have noticed that
[19:16] <calc> i don't remember which bug report had the patch there were many related bug reports about OOo fonts looking bad
[19:18] <calc> it appears it doesn't do subpixel smoothing but works for the other settings
[19:21] <calc> jdong: yea i see you were one of the people commenting on the oldest of the fonts bugs
[19:22] <jdong> I vaguely recall filing a sarcastic bug or two on that when I felt in a particularly bad mood :D
[19:22] <calc> jdong: heh :)(
[19:22] <calc> er :)
[19:22]  * calc has fat fingers
[19:24] <tjaalton> calc: will impress support 3D effects too?
[19:25] <calc> tjaalton: not sure i haven't looked at that yet
[19:25] <calc> tjaalton: probably if it is listed as a 2.4 feature upstream
[19:26] <milli> calc: thank you!!  (font bugs with OO)
[19:26] <tjaalton> it's probably a config option or something, the current version in Hardy doesn't support it
[19:26]  * milli hates ugly fonts
[19:26] <calc> so far the font bugs look to be fixed EXCEPT for the subpixel stuff, but that is a lot better than it was
[19:26] <tjaalton> I mean build config option..
[19:26] <calc> tjaalton: hmm ok
[19:27] <calc> i'll need to dig to see if i can find a patch to fix the subpixel part also
[19:32] <calc> erm
[19:32] <calc> it looks like it is working now, wtf
[19:33] <calc> yea its definitely working, i thought it wasn't earlier, so now i am confuse
[19:33] <calc> confused
[19:34] <calc> ok yea its consistently working now, so i am not sure what happened earlier
[19:34] <calc> one minor issue is you have to restart OOo to get the font setting to change, you can't change it while running
[19:51] <tjaalton> calc: --enable-ogltrans
[19:51] <calc> tjaalton: ah
[19:51] <tjaalton> calc: don't know what it depends on
[19:51] <calc> let me see if it isn't getting enabled for some reason
[19:52] <tjaalton> calc: it was added after rc2 :)
[19:53] <calc> it appears to be attempted to be used via
[19:53] <calc> --enable-opengl
[19:53] <calc> so that might be a bug then
[19:53] <calc> ok
[19:54] <calc> well its still not there in the debian version as of 2.4 final
[19:54] <calc> i'll look into it and see if the arg needs to be changed or added in addition to the other one
[19:56] <tjaalton> cool, thanks
[20:02] <Riddell> calc: kde 3 uses /usr/share/mime
[20:03] <Riddell> calc: /usr/share/mimelnk/ rather
[20:18] <calc> Riddell: does it just do matches based off of file extension? or is there a way to determine what mimetype it would consider a particular given file to be?
[20:19] <calc> Riddell: i'm wanting to make sure that i list all the needed mimetypes for KDE in OOo to open the files correctly
[20:20] <calc> Riddell: i already have it for all the shared-mime-info using gvfs-info to verify
[20:20] <calc> Riddell: so i think that will probably already work correctly for KDE4 (haven't tested)
[20:20] <Riddell> calc: kde 3 also does some magic detection, using kdelibs-3.5.9/kio/magic
[20:21] <calc> Riddell: is there any kde util that i can use to have it spit out the mimetype?
[20:22] <emgent> calc :)
[20:25] <Riddell> calc: don't think so, probably not hard to write on in python
[20:38] <Riddell> calc: http://kubuntu.org/~jriddell/tmp/mimetype2.py
[21:19] <calc> Riddell: thanks!
[21:58] <calc> Riddell: still here?
[21:58] <calc> Riddell: i tried running that script and its bombing out
[21:58] <calc> Riddell: tells me list index out of range
[22:00] <calc> Riddell: i can paste it to pastebin if you are around, not sure why it is saying that
[22:01] <calc> http://pastebin.ubuntu.com/6234/
[22:01] <calc> i ran it as ./mimetype2.py filename
[22:02] <calc> ah it worked when i ran it as python mimetype2.py filename
[22:02] <calc> i'm not quite sure why but it worked
[22:15] <calc> i am confused, this script is telling me kde thinks a excel file is type application/msword
[22:15] <calc> but in dolphin it says its an excel file
[22:16] <calc> is dolphin using shared-mime-info or kde's mime stuff
[22:18] <calc> if this is working right then kde's mime support is crummy
[22:18] <calc> it claims xml file is text/plain
[22:19] <lifeless> is there a bug open on the AEST/AEDT tzdata error ?
[22:19]  * calc thinks he'll let a kde person determine if the files are opening correctly, since it seems kde mime support is very weird
[22:20] <calc> borderline broken it would seem
[22:25] <Riddell> calc: http://kubuntu.org/~jriddell/tmp/mimetype2.py updated
[22:27] <calc> Riddell: ok testing that
[22:29] <calc> Riddell: works much better! :)
[22:29] <calc> now it thinks excel files are... excel files ;-)
[22:30] <calc> yipee it looks like it is working much better all around :)
[22:30]  * calc can now make sure all these mimetypes are in the files as well
[22:31] <Fujitsu> lifeless: Which error? The updates have been in -updates since late October.
[22:31] <Fujitsu> But I'm not sure what you're expected to do if you only use -security.
[22:32] <lifeless> Fujitsu: I'm running hardy and its wrong
[22:32] <lifeless> Fujitsu: by which I mean, the NSW senate changed the daylight saving rules
[22:32] <Fujitsu> lifeless: Ermm.
[22:32] <Fujitsu> I'm in Vic, I know of the change.
[22:32] <Fujitsu> dpkg -l tzdata
[22:32] <calc> well its still a bit buggy but i wouldn't be surprised if it was actually real bugs at this point since most of the types are showing up right
[22:33] <lifeless> Fujitsu: 2008b-1ubuntu1 :P
[22:33] <Fujitsu> Ah, I'm only on 2008a...
[22:33] <Fujitsu> cat /etc/timezone
[22:33] <Fujitsu> I bet it's User defined.
[22:33] <lifeless> no such file
[22:34] <Fujitsu> Um.
[22:34] <Fujitsu> Anyway, I have to head off to uni now... but tzdata in all releases has been updated with the right dates.
[22:34] <lifeless> Another ubuntu user I know of has the same symptoms of an early change back
[22:35] <lifeless> bye
[22:35] <RAOF> lifeless: My (Hardy) clock is correctly showing DST.
[22:36] <lifeless> RAOF: thanks
[22:36] <jdong> my gutsy clock handles DST correctly too, although I use -proposed, -updates.
[22:37] <slangasek> lifeless: you're using the gnome clock applet?
[22:37] <lifeless> slangasek: well two things got it wrong: my server, and my gnome clock applet
[22:37] <lifeless> the server I can tell via irssi :>
[22:37] <slangasek> lifeless: click, Locations, Edit, verify that the timezone automatically populated for your city isn't wrong
[22:38] <lifeless> server is 7.04; probably just haven't updated in an age
[22:38] <jdong> I think this will be a great excuse for not turning in my paper on time tonight!
[22:38] <lifeless> slangasek: tiemzone "australia/sydney" with caps; looks right to me
[22:39] <lifeless> slangasek: and 'date' in a console has the same time
[22:39] <slangasek> hmm, ok
[22:39] <slangasek> so what time is it supposed to be there right now?
[22:39] <lifeless> did feisty get the tz updates?
[22:39] <lifeless> its supposed to be 0838
[22:40] <slangasek> lifeless: that's what I see on the console with current hardy when I type TZ=Australia/Sydney date
[22:40] <soren> Wow. A 1 minute offset?
[22:40] <soren> :p
[22:40] <lifeless> soren: race condition on the minute boundary :-}
[22:40] <slangasek> lifeless: so I don't think the problem lies with the tzdata package
[22:41] <lifeless> slangasek: well, thats quite bizaare then.
[22:41] <ion_> Since it was :39:58, the boundary was quite wide. :-)
[22:41] <lifeless> whats current utc ?
[22:41] <slangasek> lifeless: hwclock in UTC?  does it display the right time? :)
[22:41] <slangasek> 21:40
[22:41] <ion_> Sun Mar 30 21:41:59 UTC 2008
[22:42] <lifeless> TZ=utc hwclock --show --utc
[22:42] <lifeless> Sun 30 Mar 2008 21:43:07 UTC  -0.117192 seconds
[22:42] <lifeless> so, other than fucking around with kerberos, the hwclock seems ok.
[22:42]  * slangasek grumbles and adjusts his clock by hand, since repeatedly setting it via the clock panel causes it to drift backwards :P
[22:42] <slangasek> yet another bug I should file on that damn thing...
[22:43] <lifeless> TZ=Australia/Sydney date
[22:43] <lifeless> Mon Mar 31 08:43:39 EST 2008
[22:43] <lifeless> so my current time zone is apparently not Australia/Sydney
[22:44] <slangasek> score
[22:44] <slangasek> blame bug #185190
[22:44] <ubotu> Launchpad bug 185190 in gnome-panel "Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)" [Low,Triaged] https://launchpad.net/bugs/185190
[22:44] <slangasek> even if it's not the bug at issue ;)
[22:45] <lifeless> ~$ echo $TZ
[22:45] <lifeless>  
[22:45] <slangasek> ls -l /etc/localtime?
[22:45] <slangasek> (well, "readlink /etc/localtime")
[22:45] <lifeless> not a symlink !
[22:45] <lifeless> and I'll bet that my friends bug is the same
[22:45] <slangasek> and you said you don't have an /etc/timezone, so you get to try to guess which file under /usr/share/zoneinfo it corresponds to, enjoy
[22:46] <slangasek> welcome the world of precision timekeeping
[22:46] <slangasek> s/the/to &/
[22:46] <lifeless> running tzselect doesn't make it a symlink eithe
[22:46] <lifeless> well, I bet I know what file it is
[22:46] <lifeless> its the *old* Australia/Sydney file.
[22:46] <slangasek> oh, heh
[22:47] <lifeless> in fact, wtf is tzselect meant to do these days
[22:47] <slangasek> well, the reason it's not a symlink is that it screws things up if /usr is on a separate partition at boot
[22:47] <lifeless> cause it sure as hell ain't writing to /etc/localtime
[22:47] <slangasek> but /etc/timezone is supposed to be used to track this
[22:47] <lifeless> nor to /etc/localtime
[22:48] <lifeless> sorry, not to /etc/timezone
[22:48] <slangasek> and obviously we need to be updating /etc/localtime when the package updates
[22:48] <slangasek> lifeless: dpkg-reconfigure tzdata? :/
[22:48] <lifeless> yes just found via the tzselect man page
[22:48] <lifeless> :)
[22:49] <lifeless> and it too writes a static file
[22:49] <lifeless> yup
[22:49] <lifeless> you want to file the bug?
[22:52] <slangasek> no, I want you to file the bug and me to fix the bug ;)
[22:52] <lifeless> blah
[22:53] <lifeless> lp account name ?
[22:53] <slangasek> vorlon
[22:54] <lifeless> mailed
[22:54] <slangasek> we're going to have to get a gnome-panel task for this well, since the gnome panel is not interacting appropriately with the tzdata-controlled files
[22:54] <slangasek> thanks
[22:55] <lifeless> breakfast, then to see about unfucking the wiki & b.l.n
[22:57] <slangasek> lifeless: looking at the postinst, the failure here is because /etc/timezone didn't exist; I'm guessing you don't have any overt knowledge of removing this file yourself... :)
[22:57] <slangasek> (in which case I need to track down why it wasn't created on upgrade)
[22:58] <lifeless> I'm glad I poked around a bit first :)
[22:58] <lifeless> and no
[23:06] <Seveas> slangasek, which upgrade should have created it? I'm missing the file as well but my hardy is slightly outdated (a week or so). Might help tracking it down
[23:08] <slangasek> Seveas: an upgrade long ago, I think.  There's mention of a preinst having been added in Aug 2007, but that preinst doesn't exist now; I'm going to chase this with the Debian glibc maintainers
[23:17] <slangasek> lifeless: what was this machine originally installed as?
[23:18] <lifeless> -EDUNNO
[23:19] <lifeless> feisty or gutsy 64 bit; then I copied various things from my 32-bit laptop (like exim config files)
[23:19] <lifeless> probably the fister
[23:21] <calc> great i found all the mimetypes i needed for kde :)
[23:22] <slangasek> lifeless: do you happen to remember if it was liveCD or alternate?  It's conceivable that this was a ubiquity bug
[23:26] <Seveas> slangasek, mine (2 of them) were desktop installs
[23:27] <slangasek> Seveas: installed from which release?
[23:28]  * slangasek needs to know which CD to start downloading :)
[23:28] <Seveas> that's what I'm trying to find out, edgy or later for sure
[23:28] <Seveas> one of them ubiquity 1.2.5
[23:29] <slangasek> that's edgy
[23:29] <Seveas> another 1.4.11
[23:29] <slangasek> feisty
[23:29] <slangasek> fun fun
[23:30] <emgent> uhm cacti FTBFS, and patch is ready. If someone can please see bug #194687
[23:30] <ubotu> Launchpad bug 194687 in cacti "cacti web frontend fails with 'Invalid PHP_SELF Path' after upgrade" [Medium,In progress] https://launchpad.net/bugs/194687
[23:40] <emgent> ScottK: ping
[23:41] <ScottK> emgent: Pong
[23:42] <emgent> about bug #194190
[23:42] <ubotu> Launchpad bug 194190 in cacti "Please sync cacti 0.8.7b-1 (universe) from Debian unstable (main)" [Wishlist,Confirmed] https://launchpad.net/bugs/194190
[23:43] <emgent> i saw now that debian version bump fix all.
[23:43] <emgent> i go to remove ubuntu patch and i will attach debdiff.
[23:43] <lifeless> slangasek: no idea
[23:43] <slangasek> okie-day