[00:02] <hyperair> does anyone know how i can get plymouth to give me at least some level of detail of what's going on during boot?
[00:02] <hyperair> i can't even figure out why my machine isn't resuming because plymouth refuses to tell me anything!
[00:03] <RAOF> hyperair: You can't just drop “quiet splash”?
[00:03] <hyperair> RAOF: er weird things happen
[00:04] <hyperair> i can't remember exactly what happened, as i've tried all sorts of things >_>
[00:04] <RAOF> Weird in what way?
[00:04] <hyperair> er i can't remember
[00:05] <hyperair> let me try again
[00:05] <RAOF> Works For Me™
[00:07] <Technoviking> Is there a file that I can set GdmXserverTimeout, want to try increse GdmXserverTimeout to fix a problem?
[00:38] <hyperair> okay, i've figured it out.
[00:38] <hyperair> initramfs-tools between karmic and lucid got this thing called "wait-for-root"
[00:38] <hyperair> and eventhough the "resume" local-premount script appears to attempt to detect tuxonice signatures, it doesn't.
[00:38] <hyperair> or rather, this wait-for-root does not detect tuxonice signatures
[00:45] <hyperair> hmm, it seems that the previous resume hook didn't detect tuxonice signatures either, but unconditionally attempted to resume anyway.
[00:48] <hyperair> hmmm so it turns out this value comes from udev.
[05:31] <pitti> Good morning
[05:56] <ravibn> Hi!
[05:57] <ravibn> Hi, I ran an update few minutes back and it asked me to restart in the boot menu I select kernel 2.6.31-21-genric to boot. I got an error msg "1.185157 Kernal Panic - not syncing VFS: unable to mount root fs on unknown block (8,17)" However I rebooted again with older version kernal 2.6.31-20 it works fine. How to fix this problem ?
[07:55] <baptistemm> hello
[07:55] <baptistemm> the build servers are down ?
[08:02] <pitti> baptistemm: they shouldn't, why?
[08:02] <pitti> there's just nothing to build ATM
[08:03] <baptistemm> Hi pitti, this is I sumitted a build yesterday night and the build time is planned for 1st May :)
[08:05] <pitti> baptistemm: ah, PPA?
[08:05] <baptistemm> yep
[08:05] <baptistemm> sorry I forgot to mention
[08:05] <pitti> you can check on https://edge.launchpad.net/builders
[08:06] <baptistemm_> oups
[08:07] <baptistemm_> the build queue for ppa is full
[08:20] <nigelbabu> kenvandine: normal for gwibber not to display identi.ca conversations?
[08:21] <nigelbabu> (and only the @ conversations)
[08:39] <rickspencer3> hi all
[08:39] <pitti> hey rickspencer3, good morning! Landed safely?
[08:39] <rickspencer3> pitti, yes!
[08:39] <rickspencer3> everything went quite smoothly
[08:40] <rickspencer3> I'm hoping this is a sign for good things come for next week and UDS :)
[08:40] <rickspencer3> pitti, so, no kitten killing or world melting bugs reported since release yesterday?
[08:41] <pitti> not that I heard of
[08:41] <rickspencer3> pitti, you were gone yesterday when I was singing your praises before I took off yesterday
[08:41] <pitti> I read it in scrollback; thanks :) *blush*
[08:41] <rickspencer3> (well deservedly gone, I should add ;) )
[08:42] <pitti> this cycle was great team work indeed
[08:42] <rickspencer3> yup
[08:42] <rickspencer3> It won't diminish the contributions to the rest of the team to acknowledge your awesome contributions as tech lead
[08:42] <rickspencer3> you've really taken it to a new level
[08:45] <pitti> thank you!
[08:45] <rickspencer3> on to maverick!
[08:57] <pitti> can we upload yet? can we upload yet?
[08:57]  * pitti wants to get rid of some 20 "fix committed" tasks
[09:01] <baptistemm> I have a SRU as well for obexd lying in a branch
[09:04] <seb128> hello there
[09:05] <seb128> over half an hour fsck and I stopped it because it was at 91% for 10 minutes, wondering if plymouth is buggy there, cpu was working at lot during this time too
[09:05] <pitti> hey seb128
[09:05] <pitti> urgh
[09:05] <seb128> hey pitti!
[09:05] <seb128> how are you?
[09:07] <pitti> seb128: quite well, thanks! how about you?
[09:07] <seb128> I'm good thanks, happy to have lucid being there ;-)
[09:09] <rickspencer3> hi seb128
[09:11] <mvo> seb128: good news, I think we can drop one of the vte patch (the repear object thing). the api is now ritch enough for this. I look at the other one next
[09:12] <seb128> hey rickspencer3, did you have a nice travel?
[09:12] <seb128> mvo, oh, nice ;-)
[09:12] <rickspencer3> seb128, yes, everything is going quite smoothly
[09:13] <seb128> rickspencer3, where are you there? still travelling?
[09:13] <rickspencer3> I'm waiting for the celebrations to start, then will head out
[09:13] <rickspencer3> seb128, I'm in the hotel
[09:13] <seb128> ok, nice ;-)
[09:13] <rickspencer3> will be heading to Vondelpark soon
[09:14] <rickspencer3> seb128, seems the release went fairly well
[09:15] <rickspencer3> you must be well satisfied
[09:16] <seb128> rickspencer3, indeed, great work from everybody ;-)
[09:16] <rickspencer3> seb128, on to Mavrick
[09:16] <rickspencer3> (and 10.04.1 ;) )
[09:17] <seb128> right, still on lucid bug fixing mode for a while
[09:17] <rickspencer3> seb128, next week I'll be all about Maverick UDS
[09:17] <seb128> while lucid is good there is still some bugs that should get fixed there
[09:17]  * rickspencer3 has lots of work to do on this next week
[09:17] <rickspencer3> seb128, yup
[09:17] <rickspencer3> perhaps we should split our attention a bit
[09:17] <seb128> I'm fine talking about maverick, I will just keep running lucid until after uds at least on this box ;-)
[09:18] <rickspencer3> I get us through UDS, and you get us through 10.04.1?
[09:18] <rickspencer3> (of course I'll need lots of help from you to get through UDS :) )
[09:18] <rickspencer3> ^typical manager move
[09:18] <seb128> yeah, don't worry, I think we can focus our attention on next cycle now
[09:18] <seb128> I will just delay technical work and keep my laptop stable and do sru updates for now
[09:20] <rickspencer3> I *really* need to get my blueprints written up
[09:20]  * rickspencer3 already feels behind for Maverick
[09:20] <seb128> only one week for this now, right ;-)
[09:21] <seb128> btw not sure what to do about next week IRC meeting since some of us will be sprinting or travelling
[09:21] <seb128> hey didrocks
[09:21] <seb128> got electricity back?
[09:21] <rickspencer3> seb128, meh
[09:21] <rickspencer3> let's cancel it
[09:21] <seb128> works for me
[09:22] <seb128> just send a reminder saying to everybody to have their blueprints ready
[09:22] <rickspencer3> yeah
[09:22] <seb128> and congrats everybody about lucid
[09:22] <seb128> ;-)
[09:22] <rickspencer3> and we can start scheduling
[09:22] <seb128> right
[09:22] <rickspencer3> lucid is dead to me now
[09:22] <rickspencer3> j/k
[09:22] <seb128> who is wanting to run this old cruft? ;-)
[09:22] <rickspencer3> seb128, btw, sounds like Telepathy folks will be there Thur/Fri
[09:22] <rickspencer3> lol
[09:23]  * baptistemm has already a todo list for maverick :)
[09:23] <rickspencer3> baptistemm, interesting, what's on it?
[09:24] <baptistemm> rickspencer3, bluez thinks, like getting back services scripts for rfcomm and whatno services were threw away when bluetoothd switched to udev starting method
[09:24] <seb128> ok, candidate updates installed on this box, let's restart my session
[09:24] <rickspencer3> baptistemm, nice
[09:25] <rickspencer3> you can probably guess the kinds of things on my personal todo list
[09:25] <rickspencer3> *cough* quidgets *cough*
[09:25]  * pitti wants to beat hal to death
[09:27] <baptistemm> seb128, I'll need to check a patch fix a small regression in obexd / bluetooth-sendto
[09:27] <baptistemm> +you
[09:27] <seb128> which one?
[09:30] <baptistemm> seb128, bug 559412 (sorry lp was slow)
[09:31] <baptistemm> new upstream release fixed the issue, but the patch is too intrusive
[09:32] <seb128> the changes in the new version you mean rather?
[09:33] <seb128> baptistemm, I've approved the lucid tasks, do you want to work on the SRU for it?
[09:33] <seb128> I can sponsor the change for you once it's ready
[09:33] <baptistemm> yeah, I backported the patch, which worked fine, but I found, just revert the change they done in 0.22 less intrusive
[09:33] <baptistemm> and fedora did the same than me :)
[09:33] <seb128> could you add pointers to the change and the fix to the bug?
[09:33] <seb128> ok good
[09:33] <seb128> do you want to work on the sru?
[09:34] <baptistemm> seb128, the branch is already linked to the bug
[09:34] <seb128> ok, I will review that
[09:57] <huats> morning
[10:09] <didrocks> bah, my laptop is a world of pain this morning…
[10:10] <didrocks> seb128: got the electricity back at 10:30 (starting my server again, hence the fact you saw me ;)). Then fscking for 30 minutes on my laptop and then, no wifi, can't have a descent fresh rate in Xorg…
[10:11] <didrocks> seb128: the good news is that I've fixed evince lately, when I was offline and on battery :)
[10:11] <seb128> didrocks, nice ;-)
[10:11] <seb128> lut huats
[10:11] <seb128> didrocks, I got an endless fsck today
[10:12] <didrocks> seb128: oh, I'm not alone so? ;)
[10:12] <seb128> I stopped it after half an hour, laptop fan was blowing a lot
[10:12] <didrocks> same here
[10:12] <seb128> and it moved from 88% to 91% in like 15 minutes
[10:12] <didrocks> I stopped it too after half an hour. It was stuck at 91% :/
[10:12] <seb128> where usually it takes 10 minutes for full check
[10:12] <didrocks> ok, that's not an isolated case so
[10:12] <didrocks> got exactly the same with the same numbers
[10:13] <seb128> pitti, ^ do you have any clue what is to bug there? plymouth I guess?
[10:13] <pitti> seb128: I'm not sure; you can try tune2fs -C 50 /dev/... to force a re-check on next boot, and try purging plymouth
[10:13] <pitti> to see whether it happens in text mode as well
[10:14] <pitti> and first do that again with plymouth to see whether it's reproducible
[10:14] <didrocks> I can do that and run my netbook meanwhile
[10:15] <didrocks> pushing the evince change first and do that after
[10:15] <didrocks> seb128: pitti: how are you apart from that?
[10:15] <pitti> quite well, thanks! did some cleanup this morning, and now working on new postgresql beta, yaya
[10:16] <didrocks> :)
[10:28] <kklimonda> when has f-spot been added to the default installation? in hardy?
[10:29] <seb128> not sure, wjhy?
[10:30] <kklimonda> heh, "someone is wrong on the internet!" ;)
[10:30] <kklimonda> I've just stumbled about a comment how "Canonical has done nothing other than changing a theme, creating a dropbox clone and dumping gimp in favour of f-spot in 10.04"..
[10:32] <seb128> we use f-spot for image editing now...
[10:32] <kklimonda> ach, 6.10
[10:34] <Laney> I wouldn't even bother replying :(
[10:42] <pitti> so in the beginning people complained that we did too many patches; now we get them upstream and people complain that we don't have any changes from upstream
[10:43] <pitti> (yes, I know about the indicator stuff, etc.)
[10:43] <didrocks> pitti: really? WTH :)
[10:43] <pitti> didrocks: what kklimonda said above
[10:44] <didrocks> pitti: well, as the power breakage shutdown my bip server, I have to grab the logs on it, one sec :)
[10:44] <pitti> didrocks: don't worry; it was just a snide remark, don't take me too seriously today :)
[10:45]  * didrocks wants to deserve some time to implement some kind of "progressive log" like the KDE irc client/proxy :)
[12:53] <kenvandine> good morning everyone
[12:54]  * kenvandine is heading out, on vacation today
[13:27] <duanedesign> didrocks: last night i reworked Stipple to get package information just like the SC instead of dpkg selections.
[13:27]  * hyperair lies in wait for keybuk
[13:28] <didrocks> duanedesign: sweet, I'll have a look next week, is it in the trunk?
[13:28] <duanedesign> didrocks: yes
[13:28] <didrocks> duanedesign: I think, I'll see with mvo if we can have that as a service somewhere (maybe s-c or something) to just ask "what apps do I have install"
[13:28] <didrocks> duanedesign: I'll have a look, great ;)
[13:31] <duanedesign> didrocks: i am enjoying the project. Thanks again for the input/ideas. :)
[13:31] <mvo> duanedesign: nice! I just had a quick look and if you just need the pakcage names you can use "for pkg in apt.Cache(): if pkg.is_installed"
[13:31] <didrocks> duanedesign: heh, I hope we can work as a team with a lot of contributors on that initiative. Thanks for your inputs too ;)
[13:32] <mvo> duanedesign: the xapian and db.postlist() stuff is not needed for that, but if you want iocns etc, then its useful (and needed)
[13:32] <duanedesign> mvo: yeah it is writting more than necessary to the DB right now.
[13:33] <duanedesign> mvo: ahh. Thank you.
[13:34] <mvo> duanedesign: np, I'm happy to help more, its a cool project
[13:34] <didrocks> mvo: I still think we should be more clever to get only "apps" installed and not the libraries and other pieces. Do you have an idea of how to get that? (that's more or less how you filtered in gnome-app-install ?) having a .desktop file in the package, some kind of debtag?
[14:09] <mvo> didrocks:  sorry for the delay, yeah, something more clever is called for
[14:10] <didrocks> mvo: no pb ;) something like is_installed and not is_auto_install, looking for a desktop file in "/usr/share/applications" in pkg.installed_files?
[14:16] <mvo> yeah
[14:16] <mvo> and maybe not part of ubuntu-desktop, but that will prob not mateer
[14:18] <didrocks> right, for defaults
[14:18] <didrocks> let me try something was that ;)
[14:18] <didrocks> s/was/with
[14:32] <duanedesign> didrocks: What is your idea? comparing contents of /usr/share/applications with "if (not pkg.is_auto_installed) and (pkg.is_installed):"?
[14:34] <didrocks> duanedesign: right, starting from that: http://paste.ubuntu.com/425259/
[14:34] <didrocks> duanedesign: I'm just trying to remove all deps of ubuntu-desktop now ("the default installed app"
[14:34] <didrocks> duanedesign: trying to do that in a efficient way in python (removing a subgroup of one group)
[15:00] <didrocks> mvo: should I really follow /usr/share/doc/python-apt/examples/all_deps.py to get the dep list (cache._depcache.GetCandidateVer(cache['ubuntu-desktop']._pkg) seems ugly to me) or use rather apt_pkg which seems to have a better api there? (not sure about the difference between the two)
[15:00] <duanedesign> didrocks: looks good. adding the if re.match trimmed the number of packages in the couchDB from 1411 to 192 :)
[15:01] <mvo> didrocks: that is a bit outdated
[15:01] <didrocks> duanedesign: right, I'm trying to exclude the default installed app (there are not installed on purpose and maybe people don't want it, or as an option) and we can push that in a library ;)
[15:01] <didrocks> mvo: do you have some examples somewhere about what you advise to use?
[15:01]  * duanedesign nods
[15:02] <mvo> didrocks: use the apt stuff, docs are here http://apt.alioth.debian.org/python-apt-doc/
[15:02] <mvo> didrocks: I can write you a example
[15:04] <didrocks> mvo: well, not sure how I can get the dependencies in http://apt.alioth.debian.org/python-apt-doc/library/apt.package.html (or do should use apt_pkg?). If you can just write an exemple for getting dependencies of one package, it will rock (I will then adapt for recommends) ;)
[15:04] <didrocks> mvo: thanks ;)
[15:04] <mvo> didrocks: http://paste.ubuntu.com/425269/
[15:05] <mvo> there is also candidate.recommends
[15:05] <didrocks> mvo: ok, candidate to get the version of the package… that was my missing piece :)
[15:05] <didrocks> mvo: thanks again ;)
[15:05] <mvo> didrocks: there is "candidate" and "installed" by default
[15:05] <mvo> didrocks: they may be "None" (if not installed or no candidate availalbe)
[15:06] <mvo> didrocks: cheers
[15:06] <didrocks> mvo: understood ;)
[15:17]  * pitti calls it a day, have a nice weekend everyone!
[15:20] <didrocks> enjoy the week-end pitti!
[15:20] <pitti> thanks, you too!
[15:20] <pitti> . o O { getting up at 6 _has_ to be good for something :) )
[15:22] <didrocks> heh :)
[16:10] <Nafai> Good morning #ubuntu-desktop!  Happy day-after-release day!
[16:12] <Nafai> So, for my French colleagues: my wife is taking French classes in school.  I tried sending her a text in French this morning, but used Google Translate.  Unfortunately, it picked the male form of the words I used so it didn't quite come out right. :)
[16:15] <didrocks> hey Nafai ;)
[16:16] <Nafai> :)
[16:16] <Nafai> I think I remember seeing this somewhere, but is there a place where we can see which binary packages were removed during Lucid?  (for failure to build, etc)
[16:17] <didrocks> Nafai: on the ubuntu-devel ML
[16:17] <Nafai> ah, that's where I saw it, thanks
[18:15] <sshaw> cj: you hiding out around here?
[18:29] <Nafai> heading out to lunch and a few quick errands
[18:33] <cj> sshaw: I'm evarware
[18:33] <sshaw> nice
[18:33]  * sshaw haves to run for a bit now
[18:34] <cj> sshaw: I've got more than 62 irssi windows open.  time to do some pruning
[18:34] <sshaw> I'd say :)
[19:26] <hyperair> qense: regarding banshee-extension-appindicator, how come next/prev don't have accelerators (the underlined letters), and how come pause is "a" rather than "p"?
[19:27] <qense> hyperair: I copied the menu from Banshee.NotificationArea and am using the default actions. Did I forget to do something?
[19:27] <hyperair> qense: hmmm maybe i was mistaken?
[19:27] <hyperair> let me check again
[19:27] <hyperair> qense: the playback menu in banshee has next=n, prev=v, play/pause=p
[19:28] <hyperair> qense: the notification area uses the same shortcuts as the playback menu.
[19:30] <qense> hyperair: I'll take a look at the code then.
[19:30] <hyperair> qense: thanks
[19:32] <hyperair> qense: another issue, but less minor, is that if appindicator is enabled, and notificationarea is enabled and disabled, banshee ends up quitting.
[19:33] <qense> hyperair: There is an action conflict, but we cannot do anything about it, unless you'd want me to write code in AppIndicator that disables another extension (yaargh), or do that in the packaging script.
[19:33] <qense> yuk
[19:33] <qense> You have to manually disable the plugin first.
[19:33] <qense> Or wait for Mono to implement conflicts support for Addins.
[19:33] <hyperair> heh okay
[19:34] <hyperair> qense: how does banshee's notificationarea icon prevent banshee from quitting on close anyway?
[19:34] <qense> I asked the Mono.Addin developer at #mono or #monodev about that and he said he'd add it to his very long ToDo list.
[19:34] <hyperair> lol
[19:34] <hyperair> very long eh
[19:34] <hyperair> it'll probably get lost in the list
[19:34] <qense> possibly
[19:35] <qense> But who knows!
[19:35] <hyperair> haha keep your fingers crossed, but don't hold your breath =p
[19:40] <Nafai> back
[20:24] <Nafai> boy sure quiet day
[20:44] <sshaw> cj: ping
[20:53] <cj> sshaw: ohai
[20:53] <sshaw> cj: should we get some at-spi2 hacking taken care of?
[20:53] <cj> sshaw: probably ;)
[20:53] <cj> sshaw: what point are you at?
[20:54] <sshaw> cj: I need to get autoreconf and intltool run during the build
[20:54] <cj> nah, do that once and produce the configure
[20:54] <cj> that's the point that things normally expect
[20:55] <cj> autoreconf happens on maintainer's machine.  you produce a configure, and the person who downloads it runs it
[20:55] <sshaw> cj: I'm so lost with some of this stuff though
[20:55] <cj> so.  upstream should deliver to you a mainter tarball produced from 'make dist'
[20:56] <sshaw> right, that's what I have
[20:56] <cj> great.  that should be uploaded to gnome's ftp server
[20:56] <cj> you should be downloading that
[20:56] <sshaw> yeah, it should be the one from gnome's ftp
[20:56] <cj> you should also be able to run ./configure from the unpacked tarball and then have a make; make install just work
[20:57] <cj> where did you get your debian/ directory?
[20:57] <sshaw> from a previous build of the package
[20:57] <sshaw> the tarball by itself is working just fine
[20:58] <cj> can I get the same version you have?
[20:58] <sshaw> its the patch that I'm applying that causes the issues
[20:58] <sshaw> cj: yeah, its 0.1.8
[20:59] <cj> I think this is the best place to grab the debian/ directory: git://git.debian.org/git/pkg-a11y/at-spi2-atk.git
[21:00] <cj> it's only at 0.1.1, though :(
[21:01] <sshaw> definitely dated
[21:01] <cj> woe.  looks like ubuntu has a newer one
[21:01] <sshaw> yeah, that's where I got mine
[21:01] <cj> oh, right.  mike said you haven't checked your debian directory into git yet
[21:02] <cj> sshaw: could you contact Mario Lang <mlang@debian.org> and request access to the alioth git repo?
[21:02] <cj> (write access that is)
[21:02] <cj> do you have an account on alioth?
[21:02] <sshaw> I don't know that I entirely trust my stuff
[21:02] <sshaw> no
[21:03] <sshaw> I'm not a debian/ubuntu packager... I'm a poke around the debian dir/ and hope not to break things packager :)
[21:03] <cj> ah.  well you've got newer stuff than debian has.  it would be nice to keep your stuff in the debian package repo
[21:03] <cj> okay, so let's work from the ubuntu 0.1.8 source package
[21:04] <cj> moment
[21:04] <sshaw> cj: I'm not opposed to that, but I didn't really do all the work.. Don't want to steal the credit
[21:04] <cj> from what I understand, you don't even have an RCS for your work, though ;)
[21:05] <sshaw> yup, its called different directories ;)
[21:05] <cj> runaway
[21:05] <cj> could I get your patches?
[21:05] <sshaw> cj: I could zip them for you ;)
[21:05] <sshaw> cj: the patch is in the mono svn... one sec
[21:05] <cj> sure!  cjac@colliertech.org
[21:06] <cj> I've pulled from mono svn recently.  the svn uri would work, too
[21:06] <sshaw> http://anonsvn.mono-project.com/viewvc/trunk/uia2atk/build/patches/at-spi2-atk.diff?view=log
[21:08] <cj> got it
[21:09] <sshaw> cj: ok, request sent
[21:09] <cj> what version of the tarball are you trying to apply the patches to?
[21:11] <sshaw> sorry, 0.1.8
[21:12] <cj> it doesn't apply cleanly for me
[21:12] <cj> or maybe I'm applying it after running debian/rules
[21:13] <sshaw> cj: it needs to be applied and then have autoreconf and intltools run against it
[21:13] <cj> makes sense
[21:13] <cj> so you need to add some more rules to debian/rules
[21:14] <sshaw> the patch adds a gnome schema file as well as translations
[21:14] <cj> add 'rm configure' to clean
[21:14] <cj> and add configure as a dep in build
[21:14] <sshaw> I don't see a clean section
[21:15] <cj> and make a target for 'configure' that runs automake -a and autoconf
[21:15] <cj> oh, and intltool
[21:17] <sshaw> what are the current versions for those tools
[21:17] <cj> I have...
[21:17] <cj> ii  automake                              1:1.11.1-1
[21:17] <cj> ii  autoconf                              2.65-3ubuntu1
[21:17] <cj> ii  intltool                              0.41.0-0ubuntu1
[21:18] <cj> but that patch doesn't apply when I dpkg-src -x at-spi2-atk_0.1.8-1~pre1.dsc
[21:18] <cj> is that the version of the .dsc you have?
[21:24] <sshaw> cj:  yeah
[21:24] <sshaw> ok, finally got those added.  Had to respond to an email
[21:24] <cj> http://paste2.org/p/802881
[21:25] <sshaw> it needs to be patch -p1
[21:25] <cj> add those to debian/control in the build-deps section
[21:25] <cj> k
[21:25] <sshaw> oh, forgot about the rules file
[21:25] <cj> cool
[21:25] <sshaw> do I need to create a clean: section?
[21:25] <cj> yeah
[21:26] <cj> I think there's something more debian-friendly
[21:26] <cj> but I don't know what it is
[21:26] <cj> ask #debian-cli review before uploading
[21:26] <cj> but it will work well enough for now
[21:26] <sshaw> override_dh_auto_clean: or something
[21:26] <cj> yeah, that
[21:27] <sshaw> cj: I probably won't upload anything until 0.1.9
[21:27] <sshaw> as this patch will completely disappear in couple weeks
[21:27] <cj> ok
[21:28] <sshaw> I don't want to upload something temporary
[21:28] <cj> have configure depend on patch
[21:29] <sshaw> I'm not sure I follow
[21:30] <cj> you don't want to generate the configure script until your Makefile.am files have been patched
[21:30] <sshaw> right, I'm just not sure how to translate that into debian/rules
[21:30] <cj> debian/rules is a Makefile
[21:31] <cj> so maybe configure: patch\n\t...
[21:34] <sshaw> cj: I think I might have it
[21:34]  * sshaw tests
[21:34] <cj> :)
[21:34] <sshaw> fingers crossed
[21:35] <sshaw> ... fail
[21:36] <cj> :)
[21:36] <sshaw> not sure why yet
[21:39] <sshaw> had a typo
[21:39] <sshaw> but now I'm getting a different error
[21:40] <sshaw> and the wrong version on a package
[21:41] <sshaw> I think I'm making progress here :)
[21:41] <cj> heh
[21:42] <sshaw> and the next error, not sure about is config.status: error: cannot find input file: `po/Makefile.in.in'
[21:42] <cj> it builds for me after patching ; autoreconf -i ; intltoolize ; ./configure make
[21:42] <sshaw> I think I might have seen that before, just not sure where
[21:42] <cj> that's intltoolize
[21:42] <sshaw> oh crap
[21:42] <sshaw> yup
[21:43] <sshaw> I know that ;)
[21:43] <sshaw> just testing you ;)
[21:43] <cj> do I pass?
[21:43] <sshaw> yup, better than me :)
[21:44] <sshaw> largely because I'm being extremely creative today when it comes to spelling
[21:45] <sshaw> looks promising
[21:46] <sshaw> cj: since I'm adding schema stuff and i18n, do I need to do anything special in the rules file to handle them?
[21:47] <cj> 'schema stuff'?
[21:47] <sshaw> gnome schema file
[21:47] <cj> I'd have to look at the diff
[21:47] <cj> moment
[21:49] <sshaw> cj: what command should I be using to check the build and then sign it?  I've been running debuild -S
[21:49] <cj> at-spi2.schemas.in is processed by configure and produces at-spi2.schemas
[21:50] <sshaw> something like that
[21:50] <cj> debuild is good
[21:50] <sshaw> it passed the first time, but now its blowing up on me with a bunch of errors
[21:50] <sshaw> is there a way to 'clean' it?
[21:51] <cj> fakeroot debian/rules clean
[21:51] <cj> are you applying the patch with quilt?
[21:52] <sshaw> yeah
[21:52] <cj> clean should remove the applied patches
[21:52] <cj> nwo is the timme where I would use git status to check what all has changed ;)
[21:52] <sshaw> debuild removed it
[21:53] <sshaw> show off :)
[21:55] <sshaw> dpkg-source: error: cannot represent change to at-spi2-atk-0.1.8/atk-adaptor/adaptor/.libs/libatk_bridge_adaptors_la-cache-adaptor.o: binary file contents changed
[21:56] <cj> sshaw: add that to your clean list
[21:56] <Laney> why is that in your source tarball?
[21:56] <sshaw> that's one of many
[21:56] <cj> what Laney said
[21:56] <sshaw> I doubt it is.  It seems like the build env is polluted
[21:56] <Laney> upstream's clean rule should sort that out
[21:57] <sshaw> this happened after it built successfully the first time
[21:58] <cj> sshaw: your patch added a new .c file, did you add the .c file to the Makefile's clean variable?
[21:58] <cj> or DISTCLEAN or something
[21:58] <sshaw> I would have assumed
[21:59] <sshaw> its not actually my patch
[22:01] <cj> sshaw: you don't have your .orig tarball in ..?
[22:01] <sshaw> I do
[22:01] <sshaw> at-spi2-atk_0.1.8.orig.tar.gz
[22:01] <cj> is at-spi2-atk-0.1.8/atk-adaptor/adaptor/.libs/libatk_bridge_adaptors_la-cache-adaptor.o in that tarball?
[22:02] <sshaw> no
[22:02] <cj> tar tfvz at-spi2-atk_0.1.8.orig.tar.gz | grep 'o$'
[22:03] <sshaw> nothing
[22:03] <cj> then I dunno ;)
[22:04] <cj> Laney: any idea what's going on?
[22:05] <sshaw> did I corrupt the jail?
[22:06] <sshaw> is my overriding the clean section causing problems?
[22:08] <cj> any chance you
[22:08] <cj> erhm...
[22:09] <cj> I was going to ask if you could keep revision logs using git
[22:09] <cj> it would be easier to debug that way
[22:09] <sshaw> git init .
[22:09] <sshaw> I suppose I could
[22:13] <cj> okay.  could you rewind and do the git init . on the package you're starting from
[22:13] <cj> ?
[22:14] <cj> and then make modifications to debian/rules, debian/control, debian/patches/*, etc?
[22:14] <sshaw> I ran a make clean and it seems to be running now
[22:17] <Laney> show me your rules file please
[22:17] <sshaw> sure, one sec
[22:18] <sshaw> http://paste2.org/p/803259
[22:19] <Laney> yeah
[22:19] <Laney> you probably need to put dh_auto_configure at the bottom of that override
[22:19] <Laney> erm, dh_auto_clean
[22:20] <sshaw> sorry, say that again
[22:20] <sshaw> dh_clean at the bottom of dh_auto_clean?
[22:20] <Laney> no no
[22:21] <Laney> dh_auto_clean is the debhelper script to take care of running make clean, basically (see the manpage)
[22:21] <Laney> but you've overriden the place where it would normally be called
[22:21] <Laney> and not put it back in
[22:21] <sshaw> oh
[22:22] <sshaw> where is it normally called?
[22:22] <Laney> when you insert an override target
[22:23] <Laney> it replaces debhelper's default behaviour with what you specify
[22:23] <Laney> but what you want here is "do this extra cleanup, then do what you would do normally", isn't it?
[22:23] <sshaw> right
[22:23] <Laney> so you need to tell it to run dh_auto_clean too
[22:24] <sshaw> oh oh, I think I'm starting to see
[22:24] <sshaw> so, the dh_clean is wrong and needs to be moved to the bottom and changed to dh_auto_clean
[22:25] <Laney> yeah sure
[22:25] <Laney> I guess dh_clean is run elsewhere anyway
[22:40] <sshaw> sorry, brb
[23:16] <sshaw>  wow, what craziness.  I'm really sorry about that
[23:16] <Laney> hmm?
[23:19] <sshaw> Laney: just some crazy things that I wasn't expecting just happened that pulled my attention from this
[23:28] <Laney> ha, such is life
[23:28] <sshaw> Laney: yeah
[23:28] <sshaw> its like a box of chocolates :)