[00:07] <geser> when you go on "See full publishing history" you can also see the dates when it happened
[02:01] <ScottK> zooko: Accepted.  You may get a reject mail, but that was me rejecting the previous one.
[02:01] <ScottK> jdong: ^^
[02:03] <jdong> ScottK: *nods* cool :)
[02:03] <jdong> zooko will be happy
[02:10] <Coolg1026> Does anyone else have issues with graphics in FF 3.5?
[02:10] <Coolg1026> Changing a gfx config in about:config in FF fixes this.
[02:10] <Coolg1026> All SIS comps seem to be affected by this color correction issue.
[02:11] <Coolg1026> *SIS video chip
[02:11] <Coolg1026> gfx.color_management.mode
[02:11] <Coolg1026> when set to 0 fixes this.
[02:12] <Coolg1026> Hello?
[02:25] <ScottK> Coolg1026: #ubuntu+1 for Karmic help.
[03:19] <zooko> Oh boy oh boy oh boy...
[03:19]  * zooko sees that tahoe-lafs is gone from the queue...
[03:19]  * zooko searches on packages.ubuntu.com...
[03:19] <zooko> Okay, it is not there yet, but I'll bet it will show up soon after a regularly scheduled job!
[03:19] <ScottK> zooko: I accepted the binary too, so once the current publisher run finishes, it should be installable.
[03:20] <ScottK> zooko: Probably another 25 minutes plus however long it takes for it to get to your mirror.
[03:21] <StevenK> zooko: https://launchpad.net/ubuntu/+source/tahoe-lafs
[03:21] <ScottK> zooko: I imagine it seems like we're unbelievably anal about the licensing stuff, but we really do have to be careful.
[03:22] <zooko> Whoo-hoo!  :-)
[03:22] <zooko> I really enjoyed seeing the intimate details of how picky you are about licensing.  Very interesting.
[03:22] <zooko> I have a deep interest in open source licensing already.
[03:23] <zooko> Whoo-hoo!  There is is!  I'm now going to announce it excitedly on tahoe-dev mailing list, my blog, etc.
[03:24] <lifeless> ScottK: well, we think we have to be :P
[03:25] <ScottK> lifeless: Certainly.
[03:26] <zooko> Hm, well I think this means it is time to upgrade my main development workstation from jaunty to karmic. :-)
[03:26]  * StevenK looks at the NBS queue and goes 'argh'
[03:28]  * ScottK figures then that StevenK would faint if he reviewed the archive rebuild test results.
[03:29] <StevenK> I doubt iut
[03:29] <StevenK> s/iut/it/
[03:29] <ScottK> The good news is that slightly over 7/8 of the packages in the archive can be built in the archive.
[03:30] <ajmitch> which still leaves 1/8 that don't?
[03:31] <zooko> Here goes the big apt-get dist-upgrade.  :-)
[03:31] <ScottK> Yep
[03:31] <ScottK> zooko: Use update-manaer
[03:31] <ScottK> zooko: do-release-upgrage -d
[03:32] <zooko> Hm.  Are you sure?  I've heard of that before, but I've been using apt-get dist-upgrade for, you know, almost a decade now, most recently two days ago to update some servers from feisty->gutsy->hardy.
[03:32] <zooko> I'm a traditionalist stick-in-the-mud and I hate new things.
[03:32] <ScottK> It will often work, but it's not the supported method.
[03:32] <zooko> But, if you say so...
[03:32] <wgrant> And it will break sometimes.
[03:32] <wgrant> Feisty->Gutsy was particularly bad for me.
[03:33] <ScottK> I do it sometimes too for testing, but it has work arounds for known problems so your upgrade is more likely to succeed.
[03:33] <zooko> Whoops, I accidentally installed upgrade-manager from karmic instead of jaunty.  Oh well.  :-)
[03:33] <ajmitch> last I recall, dist-upgrade is still supported but doesn't have the specific handling for corner cases
[03:34] <ScottK> Right, so if you hit those cases, you are suddenly unsupported....
[03:34] <zooko> By the way, is update-manager shared with debian?
[03:34] <ScottK> There was a Google SOC project to bring it to Debian.
[03:34]  * zooko reasd update-manager --help.  Cool, aufs.
[03:34] <ScottK> Not sure how it worked out.
[03:35] <zooko> by the way, it says "No new release found".
[03:36] <zooko> Ah, that's because it already thinks it as at Karmic.  Whoops.
[03:36] <zooko> Hm.  Might as well try out dist-upgrade just in case I can help out anyone else who tries this and hits a snag after Karmic is release.  ;-)
[03:37] <StevenK> zooko: -d to say "Look for development releases"
[03:40] <zooko> StevenK: I did.  The problem was I accidentally apt-get installed update-manager from karmic, and it brought in base files, so now it thinks it is already at Karmic.
[03:41] <lifeless> \o/
[03:41] <zooko> ScottK: I would like to rename the project page in launchpad from allmydata-tahoe to tahoe-lafs.  Ideally a vestigial "forwarding" page would be left at allmydata-tahoe pointing to tahoe-lafs for a while (a few years?).  Do you know how to accomplish such a thing?
[03:41] <lifeless> zooko: #launchpad
[03:41] <zooko> I guess I could g..
[03:41] <zooko> What lifeless just said.
[03:43] <sharms> yeah update-manager -d tells me no new release found also
[03:43] <sharms> must be broken right now
[03:46] <zooko> What URL should I give to people accompanying encouragement that they should upgrade to Karmic in order to help beta test?
[03:46] <sharms> http://www.ubuntu.com/testing/karmic/alpha6
[03:46] <zooko> Thanks.
[03:48] <zooko> ext4 default!  You crazy kids.
[03:49] <lifeless> crazy like a fox; and you know how that turns out
[03:57] <jdong> zooko: BTRFS! BTRFS!
[03:58] <jdong> *withholds output of mount on his present machine*
[03:58] <zooko> Yeah, btrfs is going to be great.
[03:58] <zooko> I messed around with reiser4 on my workstation at my day job last week.  :-)
[04:04] <ScottK> zooko: It's likely because you had the Karmic upgrade-manager that it didn't find a later release.
[04:04] <ScottK> Right, now I see you figured that out alread.
[04:04] <ScottK> y
[04:06] <zooko> Is ubuntu-bug a good way to report bugs?
[04:07] <zooko> I've been using launchpad web site, but I prefer not to use web ui if ubuntu-bug is good.
[04:07] <zooko> Hm, what is this thing that I'm talking about.  Ithought someone mentioned it on this channel recently, but now I don't see it.
[04:07] <zooko> Oh well, I'll use the web site.
[04:08] <ScottK> zooko: ubuntu-bug is the preferred method
[04:08] <RAOF> ubuntu-bug is the cannonical way to file bugs, yes.
[04:08] <ScottK> Ouch
[04:08] <zooko> Ouch what, the fact that "ubuntu-bug" doesn't appear in "apt-cache search ubuntu-bug"?
[04:08] <RAOF> Eh, spelling is for the weak.
[04:09] <zooko> Oh, it matches "reportbug".
[04:09] <ScottK> Don't use reportbug.
[04:09] <zooko> But at least in the bad old days, "reportbug" would send your bug reports to somewhere they weren't wanted.
[04:09] <ScottK> RAOF: The ouch was for the pun, not the spelling.
[04:10]  * RAOF wonders idly why a pulse callback that could obviously be called exactly once actually gets called exactly twice, with NULL the second time.
[04:12] <zooko> So, how do I get ubuntu-bug?
[04:13] <RAOF> It'll be in apport somewhere, right?
[04:13] <RAOF> dpkg -S says...
[04:13] <RAOF> apport :)
[04:17] <zooko> Thanks.
[04:22] <zooko> Yikes, apport won't work with my current system (not surprising), but the "yikes" is that launchpad takes me to a page telling me to use apport when I click "report a bug".
[04:22] <zooko> Hello launchpad.  I'm talkin to *you*...
[04:38] <ScottK> It's on purpose.  I did file a bug suggesting the redirection to require using apport to report bugs not be applied to apport itself.
[04:39] <zooko> Ah, well I wasn't going to report a bug in apport.
[04:39] <zooko> I guess if you guys are sufficiently serious about this, then I should just take notes and then once apport works I can go ahead and report the bugs.
[04:39] <zooko> There's a good chance I'll have forgotten/lost interest but then, but oh well.
[04:40] <lifeless> zooko: did you see the url?
[04:40] <lifeless> I pointed you at it in #launchpad
[04:43] <zooko> lifeless: that URL -- https://bugs.edge.launchpad.net/ubuntu/+filebug -- redirects to https://help.ubuntu.com/community/ReportingBugs .
[04:43] <lifeless> zooko: yes, and on that page
[04:43] <lifeless> zooko: -> #launchpad
[04:45] <zooko> lifeless: okay I finally see it.  Thanks!
[04:46] <zooko> lifeless: https://bugs.launchpad.net/ubuntu/+source/knode/+filebug?no-redirect  gives me a "no such page" error.
[04:47] <lifeless> the source package is kdepim I think
[04:47] <lifeless> yes
[04:47] <lifeless> change knode to kdepim
[04:48] <ScottK> zooko: apt-cache show knode will tell you for sure what the source package is.
[04:51] <zooko> ScottK thanks.
[04:51] <ScottK> You're welcome
[04:52] <zooko> I probably would have figured that out if it weren't past my bedtime.  Maybe I should stop reporting bugs and go to sleep.
[04:52] <zooko> Sadly, I have to go to $dayjob in the morning, so I have the feeling that I can prolong the weekend and hack on open source for fun if I stay up.
[04:55] <ScottK> zooko: Just remember that sleep is for the weak.
[04:55] <zooko> :-)
[04:56] <zooko> My wife was just reminding me that I've stayed up late for the last 5 days in a row and I'm getting really grumpy.
[04:56] <lifeless> s/ak/ekend/
[04:56] <zooko> I'm really happy about Tahoe-LAFS being in Karmic, though.
[05:38] <zooko> good night folks!
[06:28] <hyperair> who takes care of emacs-snapshot?
[06:38] <wrapster> how to use dh_link.. is it necessary to create debian/links file? coz i was going through a makefile which has something like this... dh_link -p <source> <dest>
[06:39] <persia> wrapster, Creation of debian/links or debian/${package}.links is optional, but it's often easier to read for others than embedding it in debian/rules.
[06:39] <wrapster> persia: so could you tell me how to use it.. the man page hardly has anything
[06:39] <persia> So, if you're creating from scratch, or adding links, best to use debian/links, but if you encounter a package that embeds it, best to follow that when adding more links.
[06:40] <persia> wrapster, What are you trying to accomplish?
[06:40] <wrapster> assume it this way.. im trying to repack gcc by creating a symlink to /usr/sfw/bin/gcc from /usr/bin/gcc
[06:40] <wrapster> how do i go about it.
[06:41] <wrapster> as an eg
[06:41] <wrapster> the similar was achieved through native commands but i want to use dh_link
[06:41] <wrapster> to learn...
[06:42] <persia> For that example, I'd not use dh_link, as I think you're seeking to use an alternate gcc, and would therefore recommend investigation of the alternatives system.
[06:42] <persia> That said, use of a debian/links file (in the format of source destination) is easiest.
[06:42] <persia> Otherwise, it's dh_link [debhelper options] [-A] [-Xitem] [source destination ...]
[06:43] <dholbach> good morning
[06:45] <wrapster> persia: thats what i did.. and in the rules file just add dh_link is it?
[06:45] <persia> Yes.
[06:45] <wrapster> under the proper rule ofcourse
[06:49] <wrapster> and when i do create the links.. how should the path be specified.. generally if its hardcoded in the rules file.. an i want a link at usr/sfw/bin/ then this is what i will do.. ln -s <source> debian/<pkg name/usr/sfw/bin/<file name> ... is that how i write the links files as well. or just /usr/sfw/bin/<file name>
[06:50] <persia> From the manpage: "Be sure you do specify the full filename to both the source and destination files (unlike you would do if you were using something like ln(1))"
[07:04] <wrapster> persia: ok cool.. thats what i've done lets see how it goes..
[07:12] <mase_wk_> Heya, tried asking this question in ubuntu-kernel but I guess no one knows or its not appropriate. i have just built a 2.6.31kernel with make-kpkg and I have used the --initrd switch however it still says ' please update the initramfs manually '. is there a way i can build an ubuntu package which will do this automagically on installation ?
[07:13] <mase_wk_> I would like to just install the images and have everything configured if that is possible?
[07:28] <wrapster> persia: http://pastie.org/633028
[07:28] <wrapster> i get this error..
[07:29] <wrapster> the links file has these....
[07:29] <wrapster> ### comments in the first line ;;;; <source path> <one whitespace> <dest path>
[07:31] <persia> paste your link file
[07:33] <wrapster> persia: (man)  A file named debian/package.links can list pairs of files.
[07:33] <wrapster> what i had created was debian/links
[07:33] <wrapster> let me see if this change works...
[07:33] <wrapster> then i'll do a pastie.
[08:09] <AnAnt> slangasek: Hello
[08:52] <wrapster> persia: i still get this http://pastie.org/633028 error
[08:52] <persia> And you still haven't pasted the call that gets the error :)
[08:52] <wrapster> http://pastie.org/633064
[08:53] <wrapster> and thats the links
[08:53] <persia> And the dh_links line in debian/rules ?
[08:53] <wrapster> one moment
[08:55] <wrapster> http://pastie.org/633066
[08:55] <persia> My, that's ugly.
[08:56] <wrapster> y
[08:56] <wrapster> i just started so could you tell me why?
[08:57] <persia> For this package, I'd probably skip dh_link, and use a construction like that used for libintl.so
[08:57] <wrapster> why
[08:57] <wrapster> what difference does it make?
[08:57] <wrapster> coz if you look at the rules thats exactly what i've done
[08:57] <lifeless>         rm debian/$@/usr/lib/charset.alias
[08:57] <lifeless>  rm debian/$@/usr/lib/libintl.so.8*
[08:58] <lifeless> note that the second line is broken
[08:58] <lifeless> its got a space, not a tab
[08:58] <lifeless> thats not valid Make syntax
[08:58] <persia> I think it's ugly because: 1) it uses cp rather than install, 2) it uses rm in build, rather than using it in clean or patching the build system, 3) It manually splits the package, rather than using dh_install, It forcibly strips the binaries, rather than using dh_strip (so there's no ddeb).
[08:59] <persia> I could probably go on, but the short form is: it does it the hard way, and it's long.
[08:59] <lifeless> however the breakage is the space-instead-of-tab
[08:59] <wrapster> so i cannot use dh_link
[08:59] <wrapster> in this case
[09:00] <persia> Well, you can, but I wouldn't.  That said, if you fix the issue that lifeless pointed out, it ought work a bit better.
[09:00] <wrapster> ok thanks
[09:01] <persia> The reason I'd use a construction like that for libintl.so is because I think it's best practice to try to match the style of a rules file when modifying it: this tends to cause less confusion than mixing styles for the next person.
[09:02] <wrapster> oh ok.
[09:03] <wrapster> secondly.. there is one more question... now that i'm making some changes to the actual pkg.. i would like to give it a different version no.. how do i do it?
[09:03] <wrapster> changelog?
[09:03] <persia> Yes.  You'll want to update the changelog with `dch -i`.  This tries to guess the right next version for you.
[09:05] <wrapster> just dch -i?
[09:05] <persia> yes.  From within the package directory.
[09:06] <wrapster> ok
[09:07] <wrapster> supposing i want to write something that i've changed for references then i do dch -i it opens up the log there beside the * i write what i want and save?
[09:08] <persia> wrapster, Yes.  Add more '*'s if youare doing more than one thing.  Try to stay within 70 characters.
[09:11] <wrapster> how do i save it .. no save option.. should i first ^x then save or writeout?
[09:12] <persia> Which editor launched?
[09:13] <wrapster> nano
[09:13] <wrapster> and the file is changelog.dch
[09:14] <persia> I think you need ^O and then ^X (but I'm not much of a nano user).
[09:15] <wrapster> ^o is writeout..
[09:16] <wrapster> ok so it says file name to write to and gives me changelog.dch . shall i remove the .dch or keep it ?
[09:17] <lifeless> wrapster: neither
[09:17] <lifeless> save and quite the editor
[09:19] <wrapster> lifeless:there is no save option so i will have to ^x it will save in the buffer but then again asks the same question to save in .dch file?
[09:22] <wrapster> instead of this cant i manually edit the chagnelog and add what i want ?
[09:23] <lifeless> wrapster: save and exit
[09:24] <\sh> moins
[09:24] <lifeless> wrapster: I don't know what forsaken editor you're using, so you'll have to figure that out yourself. I recommend you set EDITOR to whatever you normally use
[09:24] <wrapster> how do i set the editor?
[09:24] <lifeless> export EDITOR=vim
[09:24] <lifeless> or whatever
[09:26] <wrapster> lifeless: editor is not set at all dont know from where its picking up nano.... $EDITOR is null
[09:26] <wrapster> if ther is a env var like that :(
[09:29] <lifeless> wrapster: perhaps you should follow my recommendation then?
[09:29] <lifeless> I have to say it scares me that you are changing core toolchain packages while you're still learning standard Linux facilities.
[09:30] <wrapster> well... im learning ..
[09:30] <sebner> hihu \sh , nice post yesterday :)
[09:56] <\sh> sebner: depends...for me it was not nice to see brown scum on my ballot paper
[09:56] <sebner> \sh: heh, how much % got they?
[09:57] <sebner> *many
[11:02] <\sh> sebner, not so many...but read this: http://www.spiegel.de/politik/deutschland/0,1518,650151,00.html
[11:07] <sebner> \sh: yeah, it's pretty pretty stupid .. sick!
[11:11] <directhex> it's in germanese :/
[11:25] <sebner> directhex: google translator :P
[11:31] <hyperair> hmm emacs-snapshot's broken
[11:32] <hyperair> =(
[11:45] <sebner> huhu sistpoty|work
[11:46] <sistpoty|work> hi folks
[11:46] <sistpoty|work> hi sebner
[11:46] <sebner> sistpoty|work: I was bored so I already did the paperwork for xmoto, you just need to test *g* and ACK
[11:50] <sistpoty|work> sebner: hm... let's see if it still has the "too difficult for sistpoty" bug :P
[11:54] <sebner> sistpoty|work: heh, yep. I suggest a deep investigation *cough*
[11:54] <sistpoty|work> haha
[12:02] <sebner> sistpoty|work: gnahh, thx for the hint. changed
[12:03] <sistpoty|work> sebner: no problem
[12:08] <sebner> sistpoty|work: bah LP is soo buggy, I can't edit the bugreport
[12:09] <sistpoty|work> sebner: heh, happened to me this weekend as well
[12:23] <c_korn> this bug ? https://bugs.launchpad.net/malone/+bug/423924
[12:30] <wrapster> if i change the version number while installing i get an error saying it depends on some other software which is not of the same version..
[12:30] <wrapster> whats that suppose to mean?
[12:34] <mzz> wrapster: I can't parse your question (are you editing the .deb to change a version number in it while apt is reading it? that doesn't sound like a good idea :)
[12:35] <wrapster> hmmm.. im changing the version no in the changelog file :)
[12:35] <wrapster> not a good idea aye?
[12:36] <mzz> I still can't parse your question
[12:36] <mzz> the version number of the built source package is determined from the changelog, so adding a new version there is perfectly reasonable
[12:38] <wrapster> mzz: thats exactly what I'm doing
[12:38] <mzz> then perhaps it'd help if you gave specifics (what package, what version numbers, what error message)
[12:38] <wrapster> ok..
[12:38] <wrapster> one moment.
[12:57] <wrapster> mzz: the dpkg-buildpackage comes through but dpkg -i gives me this http://pastie.org/633066
[12:58] <mzz> wrapster: looks like gcc and cpp want to be kept in lockstep
[12:59] <directhex> yeah. the versions need to match, so both packages need to be installed at once
[12:59] <mzz> wrapster: so you need to build a matching version of cpp (if that's not built from the same source package) and install both at the same time
[13:00] <mzz> wrapster: also, I strongly agree with earlier comments about the toolchain not being the best place to start experimenting
[13:01] <mzz> wrapster: (not just because they're nontrivial packages, but mainly because you risk running into weird failure at a distance much later on because of changes you make now)
[13:10] <randomaction> looks like dependency versioning is wrong, 4:4.2.3-1-1nexenta4 has "-1" twice in it
[13:24] <wrapster> randomaction: yeah
[13:25] <wrapster> shucks!!
[13:52] <flithm1> hey all... is keyserver down?
[13:53] <jpds> flithm1: Known issue.
[13:53] <flithm1> thanks
[15:25] <bddebian> Heya gang
[15:27] <sebner> heya bddebian
[15:27] <bddebian> Hi sebner
[15:28] <fabrice_sp__> Hey bddebian
[15:33] <bddebian> Hello fabrice_sp__
[15:36] <sistpoty|work> hi bddebian
[15:37] <bddebian> Heya sistpoty|work
[16:04] <jtimberman> Not sure what else I need to do for LP bug 424576 - I posted a debdiff and diff.gz, do I need to upload to REVU? Also depends on libmixlib-config-ruby uupdate to 1.0.12, which can be synced from Debian Testing (LP bug 420674)
[16:14] <lamont> how does the freeze interact with new packages for universe?
[16:14] <Laney> lamont: you need to get a feature freeze exception
[16:15] <lamont> Laney: ok
[16:15] <lamont> from motu, or RM?
[16:15] <Laney> motu-release
[16:15] <Laney> !ffe
[16:19] <lamont> ta
[16:19] <lamont> and I'll worry about it for post-beta, if not karmic+1
[16:20] <irvingpop> MOTU team, quick packaging question:   I created a package under Jaunty,  it is compat level 7.    I cannot get it to build in Launchpad on Hardy,  because the compat level is too high.   Can I "downgrade" my compat level?
[16:21] <james_w> irvingpop: yes, but it may require changes beyond just changing the number
[16:21] <jpds> irvingpop: If the package doesn't use any debhelper 7 features, yes.
[16:21] <james_w> irvingpop: possibly extensive changes
[16:21] <irvingpop> Hardy is compat level 6, correct?
[16:21] <Laney> hardy-backports has dh7
[16:22] <irvingpop> Could that help me in a Launchpad PPA?
[16:22] <Laney> I'm not sure if PPAs build against -backports
[16:22] <irvingpop> When I required debhelper >= 7,  it wouldn't build on Hardy due to missing dependency
[16:23] <irvingpop> I changed that to 6,  and changed the compat file to 6,  but it still won't build on Hardy.
[16:23] <Laney> on a PPA?
[16:23] <irvingpop> (clarification)  on the Hardy PPA build box
[16:23] <Laney> you can either fix it to work on 6
[16:23] <Laney> or upload the dh7 backport to the ppa
[16:23] <cemc> Laney: you can select -backports as a dependency to ppa
[16:24] <Laney> yeah if that works :)
[16:24] <irvingpop> oh cool,  how can I do that?
[16:24] <Laney> I don't really use ppas that much
[16:24] <cemc> irvingpop: there should be a link 'Edit dependencies'
[16:24] <Laney> oh, how cool is that?
[16:24] <irvingpop> trying now
[16:25] <Laney> selecting backports will work
[16:25] <Laney> unless you use 7.0.50 features ;)
[16:36] <wrapster> guys im back with one last problem please help.. like i was saying i created a few symlinks under debian/<pkg name>/path and installed the result of dpkg-buildpackage.. but its not reflected on my machine..
[16:37] <wrapster> however if i open up debian/<pkg name>/path and see the files exist and a ls -l will display the source for that symlink as well
[16:37] <wrapster> what could be worng?
[16:46] <irvingpop> Laney and cemc,  thanks for the tip.   Resubmitting now
[16:47] <irvingpop> I'll submit for sponsorship after the Karmic crazyness is over :)
[17:41] <RoAkSoAx> kees, ping
[18:09] <moldy> hi
[18:09] <moldy> can i reply by e-mail to bug comments i receive from lp via e-mail? if so, is there anything i have to look out for?
[18:18] <moldy> e.g. what will happen with attachments/pgp signatures?
[18:32] <Elbrus> moldy: they are no problem
[18:33] <Elbrus> If I am right, they get stripped
[18:34] <RoAkSoAx> kees, i already have the security updates debdiff for nginx: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/430064, however I do not know which kind of tests are required for the patched code or to test the vulnerability
[18:44] <kees> RoAkSoAx: sounds like jdstand covered that pretty well on #ubuntu-hardened.  If you can get the service up and serving files, that's a reasonable test that it still works.  :)
[18:46] <RoAkSoAx> kees, cool :) I already brought the service up and it serves files, so I guess I'll just wait till someone of you reviews it :)
[18:46] <kees> RoAkSoAx: ok, cool
[21:49] <Darxus> "This bug was fixed in... mplayer (2:1.0~rc3+svn20090426-1ubuntu7) karmic; urgency=low"  That was just posted.  When is it likely to show up in the archives?
[21:53] <ajmitch> Darxus: normally within an hour or two, but it's possible that updates are being let through manually since it's beta freeze time
[21:54] <Darxus> ajmitch: Thanks.
[21:54] <ajmitch> dtchen: OK, I've grabbed the alsa-driver snapshot, I just need to find the proper way to build it :)
[21:55] <irvingpop> Quick devhelper question:   I want to convert my package from using init to Upstart.  What's the best way to do this AND remain compatible with Jaunty?
[21:56] <irvingpop> I see that Upstart is in /etc/init on Karmic,  but in /etc/event.d on Jaunty.    Plus,  Jaunty's dh_installinit has no idea about Upstart
[23:41] <zooko> Folks: I have a user asking why there aren't PowerPC .deb's of a few packages: http://allmydata.org/pipermail/tahoe-dev/2009-September/002930.html
[23:41] <zooko> What's the answer?
[23:42] <ChogyDan> zooko: I thought the powerpc support was ended
[23:43] <zooko> Aha.  I'll google for that.
[23:43] <RAOF> I'm pretty sure there are still some people who try to keep PPC up and running; TheMuso is one, from memory.
[23:43] <zooko> https://wiki.ubuntu.com/PowerPC
[23:44] <RAOF> But it's a port, no longer official, IIRC.
[23:45] <ajmitch> zooko: are you sre there are missing dependencies there?
[23:45] <ajmitch> packages.ubuntu.com may only be showing the official architectures
[23:46] <ajmitch> launchpad shows them all, eg https://edge.launchpad.net/ubuntu/+source/pycryptopp
[23:47] <zooko> b#da
[23:47] <zooko> oops
[23:47] <zooko> Well, it sounds like I need to ask Danny O'Brien to hop into #ubuntu-motu.  I don't know what's going on.
[23:47] <zooko> And I don't have an PPC machine to experiment with either.
[23:48] <james_w> zooko: yeah, it seems they should have no problems
[23:48] <james_w> zooko: if they are just looking at filenames they may be confused
[23:49] <zooko> james_w: he wrote "The powerpc builds don't seem to be available at that repository  "
[23:49] <zooko> > (yet?).
[23:49] <james_w> ports.ubuntu.com is what they want to actually install it on powerpc
[23:49] <james_w> (so they can get the architecture-specific dependencies)
[23:50] <zooko> So I can post to the tahoe-dev mailing list saying to make sure they have ports.ubuntu.com in addition to http://us.archive.ubuntu.com/ubuntu/ ?
[23:50] <james_w> instead of I think
[23:50] <james_w> "are running karmic" should cover it :-)
[23:51] <james_w> let update-manager figure it out
[23:58] <zooko> james_w: I didn't understand your last two sentences.