[04:59] <Mirv> dobey: cjwatson: kenvandine: yeah so it was not just because train packages don't tend to have debian/source, but the train refused to build a source tarball (for some reason) when it was kept, so it was not able to upload the package to PPA. that was the problem before getting to the build/install problems.
[05:00] <Mirv> dobey: cjwatson: kenvandine: the first problem might easily be caused by changes in train, and then finally with your finding we'd have the explanation for the second problem..
[06:24] <Mirv> the sick leave part was technically correct yesterday but it seems unfortunately that it will hold true today again
[07:15] <morphis> Mirv: ping
[07:22] <morphis> robru: ping
[08:46] <cjwatson> Mirv: the "for some reason" really needs to be investigated in more detail IMO; having debian/source/format should be considered standard practice nowadays
[08:47] <Saviq> jibel, I forgot today is a holiday here and in the UK, probably makes sense to move our meeting to tomorrow
[08:51] <seb128> Saviq, are you off by one day? yesterday was an uk holiday afaik but not today
[08:51] <Saviq> seb128, I might be, there is a holiday here, though ;)
[08:51] <Saviq> jibel, ↑
[08:53] <jibel> Saviq, np, next week then
[08:53] <jibel> Saviq, I'll be off Thursday and Friday and I cannot do it tomorrow
[08:53] <Saviq> jibel, ack
[08:53] <jibel> rhuddie, ^
[08:53] <Saviq> sry
[09:23] <Mirv> cjwatson: it's probably the creation of the orig tarball that has changed that doesn't anymore like .bzrignore/.gitignore files that are lower than / of the source tree: https://ci-train.ubuntu.com/job/ubuntu-landing-058-1-build/54/console
[09:23] <Mirv> so it's mostly ubuntu-push specific special case
[09:23] <Mirv> it first excludes them and then notices they are "local changes"
[09:23] <Mirv> I'll ping robert when I'm both back and robert is also available
[09:23] <cjwatson> Mirv: Ah, yeah, that does seem like a plausible kind of ci-train bug
[09:33] <jgdx> Mirv, hey, what's the latest? :) I see the quilt 3.0 patch didn't fix it?
[09:39] <Mirv> jgdx: sorry I'm on sick leave today and have about 1h now in which I need to clean stuff and eat, I can't work on that. check with morphis he did some build(s). from what I've quickly viewed if the quilt still gives problems to train (like yesterday), the solution is to keep the removal of it, .install files as unchanged and add chmod +x debian/*.install in debian/rules
[09:40] <morphis> Mirv: thanks, I think we're close to get this fixed
[09:40] <morphis> will work with jgdx to finish this thign :-)
[09:50] <mzanetti> jibel, hey, on silo 69. it failed the auto signoff because of this: https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-069/excuses.html
[09:51] <mzanetti> jibel, it's the same tests that pass on ubuntu-ui-toolkit but not on ubuntu-ui-toolkit-gles. bzoltan said this happens frequently for uitk.
[09:51] <mzanetti> jibel, however, in order to rerun this, we'd need pitti to trigger it because of some bug in the system and I can't reach him atm
[09:51] <mzanetti> jibel, tl;dr: IMO you could start with QA-ing this
[09:52] <mzanetti> I'll try to get autopkgtests retriggered asap
[09:54] <jibel> mzanetti, okay
[09:57] <cjwatson> Mirv: FWIW I believe the ci-train bug is in tools/buildpackage.sh, which does --exclude='.bzr*' --exclude='.git*' when building the orig.tar
[09:58] <cjwatson> it'll need to do that only at the top level somehow
[09:59] <cjwatson> or if that's too fiddly (I'm not quite sure how to do it ...), switch to just --exclude=.bzr --exclude=.git and accept that ignore files will end up in the tarball, which wouldn't be terrible
[10:20] <jgdx> morphis, ^ my bad, kicked off another
[10:21] <morphis> jgdx: ok
[10:23] <morphis> jgdx: updated https://requests.ci-train.ubuntu.com/#/ticket/1361
[10:23] <morphis> so it has test plan etc.
[10:23] <jgdx> thx
[10:40] <jgdx> morphis, argh, that one flaky test failed ^ we have a patch for it, but it's a rather impactful change
[10:40] <morphis> jgdx: hm, can we just disable it?
[10:41] <jgdx> morphis, maybe, but let's try another build first?
[10:41] <jgdx> whatever you want, really, your silo :p
[10:41] <morphis> jgdx: hahaha :-)
[10:42] <jgdx> I'm going to prepare a branch disabling it while we try again, ok?
[11:18] <jgdx> morphis, https://code.launchpad.net/~jonas-drange/ubuntu-push/lp1577723-skiptest/+merge/293606
[11:18] <morphis> ok
[11:20] <jgdx> though seems the http13 tests have started failing
[11:24] <morphis> wonderful
[11:33] <morphis> jgdx: sounds like all those tests are not very stable
[11:33] <jgdx> morphis, those tests are just copy pasted from the golang go-http repo
[11:34] <morphis> why that?
[11:34] <jgdx> morphis, wish I knew
[11:34] <morphis> :-)
[11:35] <morphis> jgdx: who developed ubuntu-push intially?
[11:36] <jgdx> I think it just always existed
[11:38] <cjwatson> It was John Lenton and Samuele Pedroni
[11:38] <cjwatson> AIUI
[11:38] <cjwatson> Only goes back to 2014!  Not that old :)
[11:41] <morphis> :-)
[11:41] <morphis> jgdx: I would say for the current situation we can disable them and bring them back afterwards
[11:41] <morphis> otherwise we just loose more and more time
[11:42] <morphis> jibel: ^^
[11:42] <jibel> morphis, what do they test?
[11:42] <morphis> jgdx: ^^
[11:42] <jgdx> pedronis | Chipaca ^^
[11:43] <jibel> hopefully it only goes back to 2014 so they won't have anyone else to ping :)
[11:44] <jgdx> jibel, they prob test the go http client library because they use it heavily. And it did uncover a bug in go itself some time back
[11:45] <jgdx> why idk
[11:45] <jibel> jgdx, I don't know the details but it should be tested in go itself, push seesm like the wrong place. But there is probably a good reason
[11:46] <jibel> jgdx, anyway the change is still just state -> State?
[11:46] <jgdx> ++
[11:46] <jgdx> jibel, some packaging fixes and disabling a test which will require a fix that we cannot include for OTA11
[11:46] <jgdx> jibel,  see bug 1577723
[11:47] <jibel> jgdx, can you skip this test and move on
[11:48] <morphis> jibel: afaik the http tests are now failing
[11:49] <jibel> morphis, all of them?
[11:49] <morphis> jgdx can comment on that
[11:55] <jgdx> well, this run was very green, one failure on armhf, not related to http
[11:56] <jgdx> all green on vivid, one singular test failure on xenial armhf
[11:57]  * ogra_ glares at the last ubuntu-pd image build failure mail ...
[11:57] <ogra_> why the heck is it installing ltsp-server by default ?!?
[11:59] <ogra_> oh, thats even in the builder chroot before it calls live-build
[11:59] <rvr> ChrisTownsend: ping
[11:59] <ChrisTownsend> rvr: Hi
[12:00] <rvr> ChrisTownsend: Hi. I'm testing silo 31
[12:00] <rvr> ChrisTownsend: It crashes when the german layout is selected
[12:01] <rvr> ChrisTownsend: At least, the app opens and closes
[12:01] <ChrisTownsend> rvr: What crashes?  The X app?  And strange since that is one of keyboard layouts I tried:)
[12:02] <rvr> ChrisTownsend: I first tested Spanish and it worked fine. Then added German, and didn't work.
[12:02] <rvr> ChrisTownsend: I thought it was because two layouts were selected, but I removed Spanish. And then German.
[12:02] <rvr> ChrisTownsend: If no layout is selected, apps open again fine.
[12:02] <ChrisTownsend> rvr: Are all X apps affected by this?
[12:03] <rvr> ChrisTownsend: gedit and LibreOffice
[12:03] <rvr> Those are the ones I'm using to check
[12:03] <ChrisTownsend> rvr: So you select the keyboard first in System Settings, put German layout on top, and then try to start the X app, right?
[12:05] <rvr> ChrisTownsend: Yes
[12:05] <ChrisTownsend> rvr: Ok, I'll try to reproduce when I get to my office where my test phone is.  Thanks for letting me know.
[12:06] <rvr> ChrisTownsend: Apps closes when I select another layout and go back to it
[12:07] <ChrisTownsend> rvr: You are using the Puritine click too, right?
[12:07] <ChrisTownsend> rvr: Could you also look in ~/.cache/upstart/application-legacy-puritine_gedit_0.0.log and see if anything of note is in it?
[12:08] <ChrisTownsend> rvr: If you have time.  I can try to look later.
[12:10] <jgdx> rvr, okay, we have testable vpn servers for almost all of the auth schemes
[12:11] <jgdx> rvr, pete-woods has instructions for testing cert+pass, and cert-only will be done against canonical's company vpn
[12:11] <rvr> jgdx: Wee!
[12:11] <rvr> ChrisTownsend: Hmmm
[12:11] <rvr> ChrisTownsend: I'm using latest rc-proposed image
[12:12] <jgdx> rvr, note there is no way of testing Static key auth right now, so we're hoping QA can be of help here (either compromising testing or help us find some server that let us test it)
[12:13] <ChrisTownsend> rvr: I guess I was meaning how are you getting the X apps on the device?  They are not in rc-proposed by default.
[12:13] <rvr> ChrisTownsend: They are in frieza
[12:13] <ChrisTownsend> rvr: Oh Frieza, nevermind
[12:15] <ChrisTownsend> rvr: I'm still in the N4 mindset:)
[12:15] <rvr> ChrisTownsend: http://paste.ubuntu.com/16200922/
[12:16] <ChrisTownsend> rvr: Ok, got it.  Definitely an Xmir crash.  I'll look into today.  Thanks!
[13:05] <jibel> jgdx, approved
[13:06] <jgdx> thx jibel
[13:21] <morphis> jibel, jgdx: awesome!
[13:21] <jibel> morphis, thanks for your help, that was a tough one
[13:24] <jibel> morphis, once it's published we'll rebuild an image
[13:24] <morphis> jibel: can't wait for that to happen :-)
[13:24] <morphis> jibel: indeed, but thankfully we got it solved :-)
[13:27] <jibel> morphis, jgdx you can publish or need a train guard?
[13:28] <jgdx> jibel, I don't know how.
[13:28] <morphis> jibel: its not a main package, right?
[13:29] <dobey> morphis: it doesn't matter because it's only going to the PPA
[13:29] <dobey> anyone can publish
[13:31] <morphis> ok
[13:32] <morphis> jibel, jgdx: https://ci-train.ubuntu.com/job/ubuntu-landing-055-2-publish/10/
[13:34] <jgdx> nice
[13:39] <ogra_> jibel, morphis, what about the livecd-rootfs bits (they are still sitting on my disk)
[13:39] <jibel> ogra_, can you upload the changes?
[13:40] <morphis> jibel: afaik ogra_ wanted a build with his previous password db changes first
[13:40] <ogra_> jibel, sure, i was just waiting for a "go" from someone
[13:40] <dobey> well, since there debian/ changes, you probably need kenvandine or someone to publish with an ack on the pkg changes
[13:40] <ogra_> morphis, well, the NM dropping wont cause any build issues so it can land ...
[13:41] <morphis> ogra_: OK
[13:41] <ogra_> (you will at most have runtime issues)
[13:42] <morphis> :-)
[13:42] <morphis> lets hope we don't get htem
[14:05] <charles> ondra, ToyKeeper, any news on that adb crash?
[14:07] <ondra> charles hi
[14:07] <ondra> sorry jus saw it
[14:07] <ondra> charles we had day off here
[14:07] <kenvandine> alesage_, i just replied to your comment on the trello card for silo 59
[14:07] <ondra> charles what devices is crashing on?
[14:07] <kenvandine> alesage_, i think your problem there was the same issue you had with my silo, but shouldn't be an issue now since we've had images built since then
[14:08] <kenvandine> alesage_, so should be unblocked
[14:08] <renatu> ubuntu-qa, Hey guys silo 9 is ready to review:  https://requests.ci-train.ubuntu.com/#/ticket/1362, and it is target to ota11
[14:09] <jgdx> rvr, hey, what's the status of https://trello.com/c/9ufZ0bTi/3124-1314-ubuntu-landing-008-ubuntu-settings-components-jgdx ?
[14:09] <charles> ondra, [04:05:37] <ToyKeeper> charles: It was krillin rc-proposed 321 and arale rc-proposed 313.
[14:09] <charles> ondra, [04:07:14] -*- ToyKeeper tries it again with 323+315.
[14:09] <charles> ondra, I got the crash only once, on krillin rc-proposed 323
[14:10] <rvr> jgdx: Still need the VPN instructions :)
[14:10] <jgdx> pete-woods, can you abide? ^ :)
[14:10] <jibel> ogra_, ubuntu-push is in the overlay. can you build an image?
[14:11] <jgdx> pete-woods, provide rather
[14:11] <ogra_> jibel, once livecd-rootfs is published
[14:11] <pete-woods> jgdx: okay, will start yanking the stuff out of the .ovpn file
[14:13] <jgdx> thx
[14:15] <ondra> charles and any steps to reproduce or just to plug cable?
[14:20] <alesage_> kenvandine, ack
[15:06] <pete-woods> jgdx: I've put the split files in here: http://people.canonical.com/~pete/vpn/vpn-credentials.tar.gz
[15:07] <pete-woods> user/pass = testuser/testpassword
[15:10] <ogra_> grmpf ...
[15:10] <ogra_> slangasek, did you change the crontab on nusakan ?
[15:10]  * ogra_ notes the vivid snappy builds are gone from it
[15:13] <ogra_> jibel, your image build is running
[15:16] <oSoMoN> jgdx, jibel pointed out that automated tests are failed for silo 8, do you know what’s up with that?
[15:16] <jgdx> pete-woods, is that also for rvr ?
[15:16] <jgdx> oSoMoN, checking
[15:17] <oSoMoN> renatu, what’s the status of the new calendar-app release you’re preparing?
[15:17] <pete-woods> jgdx whoever needs to test it
[15:17] <pete-woods> jgdx I haven't had to to check it works at this end
[15:17] <pete-woods> but this is the same thing I did last time
[15:17] <pete-woods> you have to poke through the config file and map the entries to settings in the UI
[15:18] <pete-woods> and obviously set the various certificates and user/pass
[15:21] <jibel> ogra_, thanks
[15:21] <jgdx> oSoMoN, jibel: failures are in unity8 tests that should be unrelated to my changes. Any way to re-run them?
[15:22] <jibel> jgdx, if you go to the excuses page there is an icon to re-run the tests
[15:23] <jgdx> jibel, i'm not allowed
[15:23] <jibel> jgdx, https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-008/excuses.html next to amd64
[15:23] <jgdx> cimi, could you rerun the failing autopkg tests in silo 8?
[15:23] <jibel> the recycle symbol
[15:24] <renatu> oSoMoN, is on silo, I am testing it today
[15:24] <jgdx> cimi, direct link:  https://autopkgtest.ubuntu.com/request.cgi?release=xenial&arch=amd64&package=unity8&trigger=ubuntu-settings-components%2F0.7%2B16.04.20160427-0ubuntu1&ppa=ci-train-ppa-service%2Fstable-phone-overlay&ppa=ci-train-ppa-service%2Flanding-008
[15:24] <renatu> I need to test if it is compatible with ota10, to launch it without framework bump
[15:25] <renatu> oSoMoN, https://requests.ci-train.ubuntu.com/#/ticket/1362
[15:41] <cimi> jgdx, I can't, I'll ask saviq tomorrow or dednick
[15:42] <dobey> jgdx: anyone who has upload rights to the package that failed, or the package that triggered the tests (or who is a coredev) can re-run the tests
[16:12] <slangasek> ogra_: I did, by request of jibel
[16:13] <rvr> bregma: ping
[16:16] <ogra_> slangasek, you mangled the snappy entries...
[16:45] <bregma> rvr, yo?
[16:46] <rvr> bregma: Hi
[16:47] <rvr> bregma: libertine-scope... it's not showin gedit icon. Also, it's not translated.
[16:48] <bregma> rvr, translation is not a surprise, but it should probably be showing an icon
[16:48] <bregma> rvr, are you testing with Puritine or with your own hand-made container?
[16:48] <rvr> bregma: Latest rc-proposed on frieza
[17:00] <robru> slangasek: https://code.launchpad.net/~robru/cupstream2distro/fix-ubuntu-push/+merge/293643
[17:21] <jgdx> cimi, okay, np
[17:22] <rvr> bregma: https://trello-attachments.s3.amazonaws.com/5726002b34077f16dbadb21b/1920x1200/025826ed80f3356796d3e1e1188dfce5/libertine-scope-gedit.png
[17:29] <bregma> rvr, https://bugs.launchpad.net/libertine-scope/+bug/1558741 is in progress, should hit OTA-12
[17:30] <bregma> maybe OTA-11 if things aren't too sluggish
[18:13] <charles> ondra, ToyKeeper, sorry my ISP went out for a couple of hours there. Either of you still around?
[18:16] <ondra> charles hi
[18:17] <charles> ondra, any news on the adb crash? Is there anything you need from me for that silo?
[18:29] <ondra> charles I need to know how to reproduce it, do you have some bug report?
[18:29] <ondra> steps
[18:29] <boiko> alesage: "sim services" can be grayed out if your sim card doesn't have service numbers, not related to the changes proposed though
[18:29] <ondra> charles and it it crashing only with your silo?
[18:29] <ondra> charles code handling those requests is from google, we might be up for some AOSP contribution :)
[18:36] <charles> ondra, I got it to crash by walking through the manual test indicator-display/adb-prompt-after-boot, and then following the steps ToyKeeper wrote in comment #1 at https://trello.com/c/gzf3hdwh/3111-1299-ubuntu-landing-035-indicator-display-charles-ondra
[18:37] <charles> according to ToyKeeper it is only crashing with the silo, but I didn't test w/o the silo
[18:38] <charles> let's see...
[18:38] <slangasek> ogra_: I commented out a single ubuntu-touch line, AFAIK; what was mangled?
[18:39] <ogra_> Snappy daily pointed to yakkety again and the vivid line was completely gone
[18:40] <ogra_> BTW,  is the importer off ? I built an image for jibel ages ago, seems cdimage has them sine a while
[18:44] <charles> ondra, getting a clean device to test with
[18:50] <jgdx> jibel, are we building rootfs yet? :)
[18:55] <ogra_> jgdx, long done
[18:56] <ogra_> but seems system-image didn't import it yet....
[18:57] <ogra_> http://cdimage.ubuntu.com/ubuntu-touch/vivid/daily-preinstalled/current/ has them
[18:57] <ogra_> slangasek, are there known importer issues ? ^^^
[19:04] <slangasek> ogra_: not that I'm aware of currently
[19:04] <slangasek> ogra_: and no, I did not touch those snappy lines
[19:04] <ogra_> Weird
[19:05] <ogra_> I changed them on Friday... must have been someone else who changed them then
[19:13] <ogra_> slangasek, hmmmhttp://paste.ubuntu.com/16207648/
[19:14] <ogra_> bah...http://paste.ubuntu.com/16207648/
[19:15] <ogra_> something is clearly broken
[19:21] <jibel> ogra_, do you know what is this empty custom tarball?
[19:21] <jibel> which channel/device?
[19:21] <jibel> ogra_, they changed to their own jenkaas instance maybe something broke there
[19:22] <ogra_> jibel, sorry, no idea... and it is ages since I have even seen the system-image code last
[19:23] <ogra_> the tarball seems to be empty though
[19:23] <ogra_> if I can belive the message
[19:24] <jibel> ogra_, yeah maybe the importer (or whatever copies images from the system that builds the tarballs) as not been reconfigured to point to the new location
[19:24] <jibel> has*
[19:24] <ogra_> and the file in the old location has been zeroed ?
[19:25] <ogra_> it should just pull in the old file if thats the case
[19:26] <jibel> just a blind guess, the way custom tarball are imported is pretty obscure to me. But this new jenkaas to build custom tarballs is one thing that changed recently
[20:24] <ToyKeeper> robru: I just realized this never landed...  is there any chance you might be able to help?  https://code.launchpad.net/~toykeeper/phablet-tools/phablet-network-no-nm/+merge/251564
[20:25] <robru> ToyKeeper: what do you need? is it not in a silo?
[20:25] <ToyKeeper> robru: The MP got approved but apparently never merged into trunk.
[20:25] <ToyKeeper> robru: ... and you're listed as top contributor to that project.  :)
[20:30] <robru> ToyKeeper: reviewed
[20:31] <robru> ToyKeeper: lol that's a year old
[20:32] <robru> ToyKeeper: wait, disregard my review
[20:33] <ToyKeeper> Yeah, I had forgotten about it; thought it landed because it kept working after I dist-upgraded.
[20:34] <robru> ToyKeeper: so anyway, this needs to go through a silo like anything else. you want to create one?
[20:35] <ToyKeeper> robru: Sure, though I'm not sure how that works from the dev side.
[20:35] <robru> ToyKeeper: log in at requests.ci-train.ubuntu.com and clicke 'create new ticket' and then fill it out as best you can
[20:36] <ToyKeeper> robru: Thanks, will do.  Wasn't sure if there was a documented process to follow or if I should just figure it out.  :)
[20:37] <robru> ToyKeeper: mountains of verbose and questionable recency documentation is at https://wiki.ubuntu.com/citrain/LandingProcess, but it should be pretty straightforward to just fill out the form.
[20:37] <ToyKeeper> :)
[20:58] <robru> ToyKeeper: click build
[20:58] <robru> ToyKeeper: also you might want to consider making this a yakkety silo, as it's probably aimed at desktop users?
[21:00] <dobey> does phablet-tools actually land via train?
[21:01] <dobey> ah i guess so. guess i'm just used to having it from the sdk team ppa
[21:01] <robru> dobey: yeah typically I do a train silo then copy it to that ppa.
[21:01] <robru> since I can't be bothered to build packages locally
[21:02] <ToyKeeper> robru: Yes, desktop users, mostly the ones in QA, so the distro QA is using (and everything after that).
[21:02] <robru> ToyKeeper: I dunno what QA is using ;-)
[21:03] <robru> ToyKeeper: I guess do a xenial+vivid build, I'll copy those to the sdk ppa, then do a yakkety build and that can go to archive.
[21:20] <dobey> aww phablet-tools isn't arch:all
[22:42] <slangasek> ogra_: did you look at /srv/system-image.ubuntu.com/www/full/pool/custom-51fb7bd3e49898416dd4d9ce47c71563743aefac760b034834a793fa19d2619a.tar.xz ? it's an html 'openid auth required' page
[22:42] <slangasek> ogra_: so do we know which import that came from, that we can disable it?
[22:54] <slangasek> ogra_: looks like this came from https://jenkins.canonical.com/ues-phone/job/custom-bq-aquaris.en-mako/lastSuccessfulBuild/artifact/out/here-international/build/custom.tar.xz


[01:26] <jayjo> is there a way to tell what device file is represented by an `lsusb` entry?
[01:27] <jayjo> In my case, I'm trying to figure out what usb serial connection I can use with `avrdude`, but this comes up for me other times when I'm connecting smartcard readers or other usb converters
[01:29] <sarnold> jayjo: this feels like something to tie together with udev's persistant device naming support
[01:47] <jayjo> I think that's what I need, thanks!
[01:48] <jayjo> I'm trying to test a few rules, because using "-P usb" as a port wasn't working https://manpages.ubuntu.com/manpages/focal/man1/avrdude.1.html
[01:48] <jayjo> not sure if it assumes a /dev file for the port
[02:38] <jayjo> in "avrdude", could "port" be a DOS or Windows term? Does it just mean device file? I have a serial device connected over USB that I'm trying to access, and using "-P /dev/serial/by-id/usb-...." gives me "avrdude: Error: Invalid port specification for USB device"
[02:38] <jayjo> I can connect to that serial device with screen
[02:58] <jayjo> looks like /dev/port is an option sometimes: https://tldp.org/HOWTO/IO-Port-Programming-2.html
[10:20] <hwpplayer1> hi people!
[10:22] <hwpplayer1> do you have any suggestions for a server infrastructure design ?
[10:23] <hwpplayer1> As i understand, one playground livepatch server and clones, one LDAP and clones, it goes like that
[10:23] <hwpplayer1> like dominoes i install more applications
[13:06] <RoyK> hwpplayer1: building a server is like building a house - there are different types depending on needs, so please specify
[13:07] <hwpplayer1> RoyK: Thanks for answering
[13:08] <hwpplayer1> RoyK: One playground for kernel patch service, development machines with or without GPU, LDAP, File servers, Git, Media(live stream) and goes on
[19:19] <Minall> Hello Ubuntu Community!... Where can I find a list of installable snaps for my server environments?
[19:19] <oerheks> snap list
[19:20] <oerheks> if you could not find that, you did not try
[19:20] <Minall> oerheks: I search for 'Ubuntu server snap list' and similar terms like 'Ubuntu Server 20.04 package list, server list, installable packages' etc. But I couldn't find results that show me what packages can be installed in the installation process
[19:21] <oerheks> i think snaps are not part of the install process on server. one could install them after 1st boot.
[19:23] <oerheks> cloud-init and core are installed standard, AFIK
[19:25] <tomreyn> yes, there's a snap install screen at the end of the server (live) installation
[19:25] <oerheks> oh? is this in 20 ?
[19:25] <oerheks> c/20.04
[19:25] <tomreyn> in 20.04 LTS, yes. maybe 18.04 LTS, too, not sure.
[19:27] <tomreyn> https://ubuntucommunity.s3.dualstack.us-east-2.amazonaws.com/original/2X/3/3bd814edad81fbdfd8a13d3c8b5e79eb2a55293c.png
[19:28] <tomreyn> https://ubuntu.com/server/docs/install/step-by-step#Snaps
[19:29] <oerheks> there you go, Minall
[19:40] <tomreyn> https://github.com/CanonicalLtd/subiquity/ is the source code if you'd like to work out how the installer filters 'popular snaps in server environments' off the list retrieved from snapcraft.io
[20:29] <hwpplayer1> tomreyn: It says Issues while validating snapcraft.yaml: could not find expected ':' on line 45, column 11
[20:30] <hwpplayer1> But there is : char
[20:41] <hwpplayer1> i'll be back in 10 minutes
[20:43] <hwpplayer1> i'm back
[23:33] <grendal-prime> anyone here ever use pfsense or opensense
[23:46] <tomreyn> there are better platforms for online polls than IRC
[23:47] <tomreyn> (maybe you meant to ask a different question)


[16:22] <PaoloRotolo> Hi all!
[16:49] <highvoltage> hi PaoloRotolo
[16:54] <PaoloRotolo> Ehm, sorry, why "https://apps.ubuntu.com/cat/applications/gamedevelop/" isn't in Precise Pangoline?
[16:54] <PaoloRotolo> It's a very good app ;)
[17:00] <stgraber> looks like it's a commercial app, so not something the ARB can help with
[17:14] <PaoloRotolo> stgraber, but was it submitted on http://developer.ubuntu.com/
[17:14] <PaoloRotolo> ?
[17:15] <highvoltage> PaoloRotolo: hey there. there are two groups who vet apps for inclusion in software center for post-release apps. one deals with non-fre apps, and one deals with free apps. the ARB deals with the free apps.
[17:15] <highvoltage> PaoloRotolo: what I suggest you do is check the myapps web interface and see if there's perhaps a feedback request. perhaps they need some more information from you
[17:16] <highvoltage> PaoloRotolo: otherwise it might be best to ask on the web interface to request the status of your application
[17:17] <highvoltage> PaoloRotolo: ah, according to https://apps.ubuntu.com/cat/applications/gamedevelop/ it's already available in Ubuntu 11.10 (Oneiric)
[17:17] <highvoltage> PaoloRotolo: I guess you checked in Precise? You have to submit myapp apps seperately for each Ubuntu release.
[17:17] <PaoloRotolo> highvoltage, Hi, thanks for the help. But "gamedevelop" isn't a my application :) I saw it on this post http://developer.ubuntu.com/2012/05/top-10-ubuntu-app-downloads-for-april-2012/
[17:18] <PaoloRotolo> because I'm using Precise, it's possible to install it in precise too?
[17:20] <highvoltage> PaoloRotolo: I think it's possible to manually add the right software source for that and install it manually, but I don't think there's anyway to do it from software centre
[17:20] <highvoltage> (not sure if SC sets up auth for no-cost non-free apps, if it does then I guess you can't)
[17:22] <stgraber> you can trick software center into thinking you're on 11.10
[17:22] <stgraber> SOFTWARE_CENTER_DISTRO_CODENAME=oneiric software-center
[17:22] <stgraber> I can then see gamedevelop in the UI
[17:23] <PaoloRotolo> highvoltage stgraber , ok, thanks a lot :)
[17:24] <PaoloRotolo> and sorry for my bad english: I'm italian :)
[17:24] <highvoltage> PaoloRotolo: try what stgraber said, it should work
[17:26] <PaoloRotolo> highvoltage, stgraber, it works :D Thanks again!
[17:26] <highvoltage> great
[17:29] <PaoloRotolo> BTW, I have already uploaded some apps for the ARB. Now they are in Oneiric and Precise. Why gamedevelop was uploaded only for Oneiric? (it's a free app too)
[17:30] <highvoltage> PaoloRotolo: you don't have to pay for it, but it's a non-free license
[17:33] <highvoltage> PaoloRotolo: see http://en.wikipedia.org/wiki/Debian_Free_Software_Guidelines for what we mean when we talk about free software
[17:34] <PaoloRotolo> highvoltage, oh, yes, I know. So only the open-source apps are uploaded from the ARB for all the Ubuntu versions?
[17:35] <highvoltage> PaoloRotolo: usually for the current stable ubuntu version. we try to encourage people to get them into the ubuntu archives as well so that they can be available for future releases
[17:36] <PaoloRotolo> highvoltage, ok I understand, thanks :)
[17:37] <highvoltage> PaoloRotolo: you're welcome
[23:20] <malin> is this app approved soon? https://myapps.developer.ubuntu.com/dev/apps/782/


[12:09] <cmaloney> Good morning
[12:28] <rick_h> party
[12:33] <cmaloney> \m/
[12:36] <_stink_> hi
[12:37] <jrwren> what is new in ubuntu land?
[12:38] <cmaloney> I turn another year older today.
[12:41] <_stink_> https://www.youtube.com/watch?v=tUxnBs86iUA&feature=youtu.be&t=16
[13:00] <jrwren> happy birthday cmaloney
[13:00] <cmaloney> Thank you!
[13:01] <cmaloney> I <3 that Garfield animation
[13:01] <cmaloney> show
[13:01] <cmaloney> thing
[13:02] <jrwren> you're one year older, one year wiser, Rock n' Roll star king dzar and a kaiser.  Every present is for you and it feels pretty great.
[13:06] <cmaloney> <3 Thank you.
[13:06] <cmaloney> I'm just happy to be here.
[13:22] <cmaloney> Eoan Ermine is 19.10
[13:22] <cmaloney> https://ubuntu.social/@ubuntu/102785251361304988
[13:24] <jrwren> lol
[13:25] <jrwren> does sabdfl still write his biannual naming blog post?
[13:26] <cmaloney> probably.
[13:32] <jrwren> hrm... https://www.markshuttleworth.com  not since cosmic
[13:32] <jrwren> takes over as CEO... starts to care less :(
[13:33] <cmaloney> Probably has someone else take over naming responsibilities
[13:33] <jrwren> end of an era
[13:34] <jrwren> what point is there in running a  multi million dollar linux company if you don't get to name stuff? :)
[13:41] <_stink_> that's a lot of vowels
[15:58] <jrwren> this is cool. http://zynthian.org
[16:00] <cmaloney> That's cool, but the interface for ZynAdSubFX is anything but easy to use. :)
[16:01] <cmaloney> https://www.youtube.com/watch?v=-q9gPyQ8IJE
[16:42] <greg-g> jrwren arbor is emailing a bunch of us at work:)
[16:43] <jrwren> greg-g: ha! I'm not surprised.
[16:46] <cmaloney> ?
[18:58] <jrwren> MSFT releasing CC-SA licensed icons. https://github.com/microsoft/vscode-icons
[19:12] <cmaloney> CC-BY
[19:12] <cmaloney> which is even more relaxed
[19:13] <cmaloney> Though this is fun: The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653.
[19:13] <cmaloney> so if they wanted to be pedantic I couldn't use their trademark for their attribution. ;)
[19:16] <jrwren> oh right!


[06:46] <ara> morning all :)
[09:04]  * ara reboots
[09:53]  * ara takes a break
[13:03] <ara> happy weekend everybody!
[13:03] <ara> cheers!
[15:58] <ogasawara> cr3: sconklin posted a link to a test kernel for bug 293372 (dell optiplex 330 reboot issue)
[15:58] <ogasawara> cr3: care to test and confirm it fixes it
[15:58] <cr3> ogasawara: sure thing
[15:59] <ogasawara> cr3: thanks
[16:14] <cr3> ogasawara: the package seems to contain a menu.lst, install package maintainers or keep?
[16:15] <ogasawara> cr3: hrm, dunno.  I guess keep?
[16:16] <ogasawara> cr3: which .deb was it?
[16:16] <ogasawara> cr3: I think you only need to install the linux-image-2.6.27-8-generic_2.6.27-8.17_i386.deb
[16:25] <cr3> ogasawara: that's the package I'm installing
[16:26] <cr3> ogasawara: I'll install the package maintainer's version so that I can claim it works
[16:26] <ogasawara> cr3: ok thanks
[16:32] <ogasawara> cr3: I'd never seen that pop up before, how odd.  I selected to "show the differences between the versions", it just shows is adding the 2.6.27-8 kernel to menu.lst.  so probably good you picked the maintainer's version.
[16:32] <cr3> ogasawara: the package worked, I updated the bug
[16:33] <ogasawara> cr3: sweet, thanks for testing.
[16:33] <persia> Umm, is this /boot/grub/menu.lst?
[16:33] <cr3> persia: yep
[16:33] <cr3> ogasawara: probably just mispackaged, no biggie
[16:33] <persia> That *really* shouldn't be shipped in a package.  It's modified by running update-grub.
[16:33] <persia> If the kernel package is shipping it, that's different, and should be stopped.
[16:34] <persia> Does it show in dpkg --contents on the .deb ?
[16:34] <james_w> persia: I think it's a side effect of having a ucf managed menu.lst
[16:34] <cr3> persia: it's not in the package, dpkg --contents linux-image-2.6.27-8-generic_2.6.27-8.17_i386.deb | grep menu.lst returns nothing
[16:35] <persia> cr3, OK.  Ignore me then.
[16:35] <ogasawara> cr3: it is sconklin's first patch/SRU for the kernel-team and I'm not quite sure of the steps he used to create the package
[16:36] <persia> james_w, That makes sense, but regardless of how it's managed, the bootloader update hook is the right way to update it most of the time, and shipping it in a package would be a much more significant change than might be sane for an SRU.
[16:36] <james_w> persia: I agree, but in this case the message that the package includes a new version is misleading, as it doesn't include it at all
[16:37] <persia> james_w, Yep.  It certainly confused me.  On the other hand, that's probably a relatively minor update-grub bug.
[16:37] <persia> I'm also a little curious how cr3's system was changed in a way that raised the flag, but that's probably just a documentation gap.
[16:40] <ogasawara> persia: it I happened just now on my system as well when I tried.  I'd never seen it before.
[16:40] <ogasawara> persia:  http://people.ubuntu.com/~sconklin/293372/
[16:44] <persia> ogasawara, Do you know if source packages for that are available anywhere?
[16:45] <ogasawara> persia: unfortunately I don't, but let me get sconklin to join here
[16:45]  * persia doesn't have an i386 system handy anyway, but would prefer to avoid asking users a misleading and probably incorrect question if possible.
[16:46] <ogasawara> hi sconklin
[16:46] <sconklin> hi, what's up?
[16:47] <persia> sconklin, We're just looking at http://people.ubuntu.com/~sconklin/293372/ and it seems to prompt for a change in menu.lst, which is unexpected.
[16:47] <persia> I was curious if there was a source package available that produced those .debs for comparison with the current version in the repos.
[16:49] <persia> Mind you, I don't understand why a change to the vesa drivers would affect menu.lst that way.  Maybe it's because the version number isn't different?
[16:49] <sconklin> persia: I only built the ones that are there, but I can build the source package. It's quite possible I did something wrong, as I'm new to the process.
[16:49] <persia> How did you build binary packages without first building the source package?
[16:50] <sconklin> Prompting for the same version case makes sense, so you have a recovery path, but I don't know whether that's the case.
[16:52] <sconklin> maybe I'm not understanding. I just built binary-generic from the git checkout.
[16:52] <persia> Oh, maybe I'm looking at the wrong thing then.
[16:52]  * persia compares against 2.6.7-7.16
[16:53] <sconklin> I checked out Ubuntu-2.6.27-8.17
[16:54] <persia> Right, which is why I'm comparing to 2.6.27-7-16 as opposed to 2.6.27-8.17 (repo version).  It might be that the change isn't your latest change, but something else.
[16:54] <persia> cr3, ogasawara Can you reproduce the menu.lst issue with the current version in -proposed?
[16:55] <ogasawara> persia: I'll test, just a sec
[16:56] <persia> Looks to me like -8.17 (both sconklin's and -proposed) have some extra stuff that doesn't belong.
[16:58] <persia> http://pastebin.com/f255fc809 is the output of debdiff between 7.16 and the 8.17 in -proposed.  I think most of that belongs in linux-firmware, and the /boot stuff doesn't belong at all.
[17:00] <persia> Hmm.  Seems to contain a bunch of modules stuff as well.  Explains why *-modules-2.6.27-8-* have such small filesizes from http://archive.ubuntu.com/ubuntu/pool/main/l/linux/
[17:01] <ogasawara> persia: installed normally, not prompt
[17:01]  * persia is confused.
[17:02] <sconklin> not as confused as me.
[17:02] <persia> binary debdiffs tend to be opaque, but the only thing different between the 8.17 in the pool and sconklin's 8.17 appears to be the vesa drivers.
[17:03] <persia> Whereas the difference between the contents of 7.16 and 8.17 are *huge*
[17:04] <sconklin> oh, pgraner said something about a bunch of firmware being put in at some point, but I didn't follow all of it. That was a couple of weeks ago. He might have some insight.
[17:04] <persia> And I don't understand why changes to the contents of the vesa drivers would trigger a menu.lst warning.
[17:05] <persia> ogasawara, Just to double-check (although I'm confident the answer is "yes"), the same procedure was used for each upgrade, from the same base state, right?
[17:05] <ogasawara> persia: yes
[17:06] <persia> james_w, Any other ideas?  This sounds like more than a ucf issue.
[17:06] <james_w> ogasawara: have you manually modified your menu.lst?
[17:07] <ogasawara> james_w: just small tweaks like removing 'quiet'
[17:07] <james_w> I assume you did it the "correct" way?
[17:08] <ogasawara> james_w: what's the "correct" way?  I just manually edited
[17:09] <james_w> ogasawara: did you change the "# defoptions=quiet splash" line?
[17:10] <persia> (the correct way is to change that, and run `update-grub`)
[17:10] <ogasawara> james_w: ah, I didn't do that
[17:10] <james_w> cr3: hey, did you edit your menu.lst at all?
[17:12] <persia> ogasawara, But when you upgraded to sconklin's kernel with your manually edited menu.lst you got the warning, and when you upgraded to the proposed kernel with your manually edited menu.lst you didn't get a warning?
[17:12] <ogasawara> persia: correct
[17:14] <persia> See, that's the confusing part, which makes me suspect that either the manual edits aren't the culprit, or that something else odd is happening.
[17:16] <ogasawara> sconklin: when you built the kernel you used the magic kernel scripts right? eg CONCURRENCY_LEVEL=2 AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules binary-generic
[17:17] <persia> hunh?
[17:17] <persia> Shouldn't it just be "debuild -b"?
[17:17] <persia> (or build a source package, and feed it to pbuilder or sbuild)
[17:17] <sconklin> maybe not. I used:
[17:17] <sconklin> fakeroot debian/rules binary-generic
[17:18] <ogasawara> persia: the kernel builds straight from the git repository
[17:18] <persia> ogasawara, Not on the buildds it doesn't.
[17:18] <persia> And testing anything built differently than it will be built on the buildds invites unexpected differences.
[17:20] <ogasawara> persia: right, which might explain this oddity
[17:21] <persia> Yeah.  That makes a lot more sense than the other stuff, and it could well not show in a binary debdiff.
[17:26] <sconklin> if I need to do things differently, please explain it in small words :)
[17:30] <ogasawara> sconklin: for test kernels I usually just build it with the kernel scripts like you did but I've never ran into this prompt issue about changing grub's menu.lst
[17:31] <ogasawara> sconklin: let's maybe raise it next week in PDX
[17:32] <sconklin> yes please.
[17:36] <persia> sconklin, I'd recommend running `apt-get build-dep linux-image-2.6.27-8-generic` on your system once, and then running `debuild -b` from the source directory as a quick hack until then, but I don't tend to do much on the kernels, so this might not be the best advice.
[17:42] <sconklin> persia: thanks, I'll ask some other kernel folks, too. I did what I found on the wiki, so perhaps that page needs some love.
[17:43] <sconklin> biab, emergency delivery of socks to my son's school.
[18:00] <sconklin> back
[19:08] <nagappan> cr3, with Ubuntu 8.10, for all message I receive in XChat, it highlights as I have received private message, is this known issue ? I have upgraded from 8.04 to 8.10
[19:09] <cr3> nagappan: sorry, I wouldn't know, I don't use XChat :)
[19:16] <nagappan> cr3, ok
[19:17] <nagappan> cr3, can you point some one, I want it to be fixed
[19:17] <persia> nagappan, You'd do better to file a bug about it, no?
[19:18] <nagappan> persia, sure
[19:22] <cr3> persia: nice going, you scared him away ;)
[19:27] <nagappan> cr3, persia, removed existing XChat conf and restarting the XChat, fixed the issue for me, thanks :)
[19:28] <persia> nagappan, Oh, so it's a config issue, rather than a source issue?  That's excellent to hear.
[19:28] <nagappan> persia, :)


[00:07] <saivann> asac : I'm trying to build to see if my patch apply correctly and the patch system here is dpatch. While building, I get this error : applying patch 04_xulrunner1.9_glue to ./ ...patch: **** malformed patch at line 80: @@ -96,29 +72,28 @@
[00:08] <saivann> asac : current patch : http://paste.ubuntu.com/24562/
[00:08] <saivann> asac : At this point in the patch, no tricky modifications has been made
[00:08] <saivann> asac : I wonder if dpatch needs a space before each hunks
[00:09] <asac> saivann: no ... malformed usually means that you have the numbers wrong
[00:09] <asac> could be that you miss a space somewhere ;)
[00:09] <saivann> asac : Oh! That makes sense! I forgot to add 11.. thanks
[00:09] <asac> but you should never remove anything else than complete lines
[00:25] <saivann> asac : I switched back to the patch without modifications in the first lines and I still get the same error for line 280
[00:25] <saivann> asac : default-prefs-libxul.js does not exist, it is suposed to be created by that patch
[00:26] <saivann> asac : but dpatch does not seem to share that point of view
[00:26] <saivann> asac : Is there something missing, like @only_in_patch2
[00:29] <asac> saivann: how did you add the default-*js file to the patch?
[00:31] <saivann> asac : I just copied the hunk from the complete diff
[00:32] <saivann> asac : default-*js exist in 1.0.1 so it was in the original diff
[00:34] <asac> saivann: not sure without looking. try to remove hunk by hunk until you find the intruder
[00:34] <asac> double check that you dont miss a line break at the end of some patch
[00:35] <asac> the original filterdiff patch should work
[00:40] <saivann> Ah right.. missing break lines, that seems to work now
[00:41] <asac> hehe
[00:49] <saivann> asac : Bad new.. using the same rules file as 1.0.1 (with correct FLAGS), I still get a lot of /usr/lib/xulrunner-devel-1.9b5/lib/libxul.so: undefined reference to `JS_RemoveRoot'
[00:49] <saivann>  when I try to build in hardy
[00:49] <saivann> The package build-depends on xulrunner-1.9-dev
[00:50] <asac> saivann: right. we are not there yet
[00:50] <asac> saivann: now you have a minimal xulrunner-1.9 patch
[00:50] <asac> what you dont have is a patch that applies all the autoconf/make changes
[00:51] <saivann> asac : Oh, right
[00:51] <asac> so thats the next step
[00:51] <asac> saivann: is there a 99_autoXXX patch already?
[00:51] <saivann> asac : Actual patch still contains not necessary stuff
[00:51] <saivann> asac : no
[00:51] <asac> saivann: yeah. you can clean this afterwards.
[00:51] <asac> lets get through the process
[00:52] <saivann> asac : The patch applies correctly from now :)
[00:52] <saivann> asac : Great! I'm ready to continue
[00:52] <asac> you use dpatch-edit-patch to create a new patch that gets applied at the end of the patchset
[00:52] <asac> saivann: its dpatch right?
[00:52] <asac> read manpatch of that tool ;)
[00:52] <saivann> asac : yes, the build system use dpatch
[00:53] <asac> so when you are in "edit" mode you run the required autotools
[00:53] <saivann> asac : Ok
[00:53] <asac> not sure what that is
[00:53] <asac> in worst case you just run autoreconf -i -f
[00:53] <asac> when in edit mode and exit the mode to produce a full update
[00:54] <saivann> asac : Do you mean man dpatch?
[00:55] <asac> saivann: no dpatch-edit-patch ;)
[00:59] <saivann> asac : I'm not sure but it seems to works like the cdbs patch edit tool
[01:00] <asac> yes
[01:00] <asac> saivann: you can use that two most likely ;)
[01:00] <asac> i found that cdbs-edit-tools has more bugs though ;)
[01:00] <asac> -patch
[01:00] <saivann> asac : Oh I get it, I will use kind of sed command on all makefiles?
[01:00] <saivann> asac : And then save the patch
[01:01] <saivann> hehe :)
[01:01] <asac> saivann: no, you just run the autotools
[01:01] <saivann> asac : I just type "autotools" and then "exit" ?
[01:01] <asac> like the autoreconf i suggested above
[01:03] <saivann> asac : autoreconf and autotools are still unknown to me, where can I find more information?
[01:03] <asac> saivann: autotools is just a word for a bunch of autoXXXX commands
[01:04] <asac> autoreconf is quite simple helper that runs the autoXXX commands in right order for you
[01:04] <asac> maybe you just need to run autoconf, but autoreconf should be safe ;) ... though a bit brute force-like
[01:04] <asac> name the patch 99_autoreconf if you use autoreconf ;)
[01:04] <saivann> asac : Ok I will try "autoconf" first :)
[01:05] <asac> yeah
[01:05] <asac> saivann: well at best try autoreconf first as this will most likely work
[01:05] <asac> then you can try autoconf later and i can bail out :-D
[01:06] <asac> good excercise
[01:06] <asac> :)
[01:08] <saivann> asac : Ok :P
[01:10] <saivann> asac : autoreconf fails with error code 1 : http://paste.ubuntu.com/24570/
[01:14] <asac> saivann: does the source ship a autogen.sh ?
[01:14] <saivann> looking..
[01:14] <saivann> asac : Yes
[01:14] <asac> can you run that? sh autogen.sh ?
[01:14] <asac> or does it give you problems too
[01:15] <asac> in case it auto starts configure, abort
[01:15] <saivann> asac : Strangely, same errors : http://paste.ubuntu.com/24573/
[01:16] <asac> saivann: is libtool package installed?
[01:16] <saivann> asac : The source is un-touched, changes has been made in debian folder only
[01:16] <saivann> asac : on my computer?
[01:16] <asac> yes
[01:17] <asac> aclocal must succeed
[01:17] <asac> otherwise you miss a package
[01:18] <saivann> asac : It was not, however, I installed it and tried again without success
[01:18] <saivann> asac : Mmh, is there any way to have some clues about which package is missing?
[01:18] <asac> saivann: whats the error now?
[01:19] <asac> aclocal should not print AM_PROG_LIBTOOL error if you have libtool installed
[01:19] <saivann> asac : http://paste.ubuntu.com/24574/
[01:20] <asac> saivann: do you have all build dependencies of that package installed?
[01:20] <asac> that would be a good start i guess ;)
[01:20] <saivann> asac : Ok then I should install glib, gtk, chmlib, etc.
[01:20] <asac> chmlib wont exist
[01:20] <asac> but run sh autogen.sh
[01:20] <asac> then it should work
[01:20] <asac> saivann: install build-dependencies ;)
[01:20] <asac> sudo apt-get build-dep PACKAGENAME
[01:21] <saivann> asac : Sorry
[01:21] <saivann> asac : I did remember that command, it's installing now
[01:21] <saivann> :)
[01:21] <asac> hehe
[01:21] <asac> welcome
[01:23] <saivann> asac : since build-deps are installed, only AM_PATH_CHMLIB gives a error
[01:23] <asac> saivann: right. use sh autogen.sh
[01:23] <asac> did you use that?
[01:24] <saivann> asac : No I was still using autoreconf
[01:24] <asac> look at the output ... it uses aclocal -I m4 ... which means it looks for its _own_ m4 files
[01:24] <asac> so that will give you that macro ;)
[01:24] <asac> done
[01:24] <saivann> asac : autogen.sh seems to have executed successfully
[01:24] <asac> AM_PATH_CHMLIB == macro ;)
[01:24] <asac> saivann: congrats :)
[01:24] <saivann> asac : Thanks :D
[01:25] <asac> saivann: the definition for that  macro is in the m4/ directory if you care
[01:25] <asac> saivann: ok if you have created a 99_autogen_sh.dpatch .. chances are high that things work ... if not completely at least somehow
[01:25] <asac> it will break if you have forgotten to remove some GLADE rename things for sure
[01:26] <asac> saivann: oh. i think you have to add that patch manually to 00list
[01:26] <asac> but not sure
[01:26] <saivann> asac : Yeah I'm looking at it
[01:26] <asac> i have a bad opinion about dpatch and avoid to use it ;)
[01:26] <saivann> asac : There is still GLADE renaming things in my patch which I did not succed to remove..
[01:27] <saivann> asac : ..Well I'm not an expert, but I prefer other patch systems too at this point
[01:27] <asac> saivann: for now you can fix it by just making
[01:27] <asac> + CHMSE
[01:27] <asac> - CHMSE
[01:27] <asac> :)
[01:27] <asac> as a trick;)
[01:27] <asac> just make the patch do nothing so you dont have to care about the hunk bounds ;)
[01:28] <saivann> asac : Haha, yeah that's simple, but ugly :P
[01:28] <asac> saivann: you can clean up later
[01:28] <asac> but certainly before upload ;)
[01:28] <asac> hehe
[01:28] <saivann> asac : I agree :)
[01:28] <saivann> asac : Ok let's try this
[01:29] <asac> ha ... i already have almost 30 posts in the forums ;)
[01:29] <asac> http://ubuntuforums.org/showthread.php?t=797059&page=9
[01:36] <saivann> asac : :)
[01:36] <saivann> asac : Unfortunately.. still the same /usr/lib/xulrunner-devel-1.9b5/lib/libxul.so: undefined reference to `JS_RemoveRoot'
[01:37] <asac> saivann: check that the linker flags are there
[01:37] <asac> e.g. see if you see XPCOM_GLUE in the compile line
[01:37] <asac> and -lxpcomglue
[01:37] <saivann> asac : I confirm : DEB_CONFIGURE_EXTRA_FLAGS += --with-gecko=libxul
[01:37] <asac> saivann: if thats the new --with-gecko?
[01:38] <saivann> asac : No and it's not in the 1.0.1 either
[01:38] <asac> saivann: use the --with-gecko from 1.0.1
[01:38] <saivann> asac : I used the same rules file as 1.0.1, which use DEB_CONFIGURE_EXTRA_FLAGS += --with-gecko=libxul
[01:39] <asac> saivann: yeah. look at what the compiler spit out and if it had the xpcomglue linker flags
[01:40] <saivann> asac : you speak about the configure.ac or Makefile.am??
[01:40] <saivann> asac : Or about the build logs?
[01:41] <asac> saivann: about what you see on the command line right before it fails
[01:41] <asac> thtas basically the compile command used
[01:41] <saivann> asac : Ok, I'm looking to save build logs
[01:44] <asac> saivann: if you see something like -DXPCOMGLUE and -lxpcomglue in there then its probably right
[01:44] <asac> and we are likely missing some other hunk which i might have missed
[01:48] <saivann> asac : cd . && CC="cc" CXX="g++" CFLAGS="-g -O2 -g -Wall -O2" CXXFLAGS="-g -O2 -g -Wall -O2" CPPFLAGS="" LDFLAGS="-Wl,-Bsymbolic-functions" LDFLAGS=" -Wl,--as-needed" /tmp/buildd/chmsee-1.0.0/./configure --build=x86_64-linux-gnu --prefix=/usr --includedir="\${prefix}/include" --mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" --sysconfdir=/etc --localstatedir=/var --libexecdir="\${prefix}/lib/chmsee" --di
[01:48] <saivann> sable-maintainer-mode --disable-dependency-tracking --srcdir=.   --with-gecko=libxul
[01:49] <saivann> asac : I found the word lxpcomglue 2 times in the build logs, but not DXPCOMGLUE
[01:49] <saivann> I come back in 2 seconds
[01:50] <asac> saivann: sorry ... XPCOM_GLUE
[01:51] <asac> most likely -DXPCOM_GLUE :)
[01:51] <asac> like what you get with pkg-config --cflags libxul-embedding
[01:51] <asac> and pkg-config --libs libxul-embedding
[01:53] <saivann> back
[01:54] <saivann> asac : DXPCOM_GLUE, XPCOM_GLUE, pkg-config --libs libxul-embedding, none of them are in build logs
[01:54] <asac> saivann: thats bad
[01:54] <asac> that means that the configure.ac changes are not applied
[01:54] <saivann> asac : Not really?..
[01:55] <asac> nope
[01:55] <asac> saivann: double check that the 99_autogen patch is in 00list
[01:55] <saivann> asac : I looked at the build logs and the patches are reported to be applied
[01:55] <asac> autogen too?
[01:55] <saivann> asac : Yes it is, and build logs says that it was applied during build process
[01:56] <saivann> asac : 99_autogen contains a huge amount of changes, made by autogen in dpatch edit
[01:56] <asac> saivann: ok check that GECKO_CFLAGS and GECKO_LIBS are properly set in config.status
[01:57] <saivann> asac : config.status, I can't find that file in sources
[01:58] <asac> saivann: nothats in the build directory
[01:58] <asac> not sources
[01:58] <saivann> config.guess, config.h.in, config.sub
[01:58] <asac> thats the result of configure basically
[01:59] <saivann> asac : Oh, then that file appears after configure is executed?
[01:59] <asac> yes
[01:59] <asac> in the build tree
[01:59] <asac> keep that tree
[01:59] <asac> work in there ;)
[02:00] <saivann> asac : s,@GECKO_CFLAGS@,|#_!!_#|-fshort-wchar -I/usr/include/xulrunner-1.9/unstable -I/usr/include/nspr   -I/usr/include/xulrunner-1.9 -I/usr/include/xulrunner-1.9/commandhandler -I/usr/include/xulrunner-1.9/content -I/usr/include/xulrunner-1.9/dom -I/usr/include/xulrunner-1.9/find -I/usr/include/xulrunner-1.9/gfx -I/usr/include/xulrunner-1.9/gtkembedmoz -I/usr/include/xulrunner-1.9/locale -I/usr/include/xulrunner-1.9/p
[02:00] <saivann> ref -I/usr/include/xulrunner-1.9/string -I/usr/include/xulrunner-1.9/webbrwsr -I/usr/include/xulrunner-1.9/xpcom -I/usr/include/xulrunner-1.9/xpconnect,g
[02:00] <asac> that looks wrong
[02:00] <asac> thats still mozilla-gtkmozembed
[02:00] <asac> not libxul
[02:01] <saivann> asac : s,@GECKO_LIBS@,|#_!!_#|-L/usr/lib/xulrunner-devel-1.9/lib -lxpcomglue_s -lxul -lxpcom -lplds4 -lplc4 -lnspr4 -lpthread -ldl  ,g
[02:01] <asac> saivann: yeah thats wrong too
[02:01] <asac> thats the dependent glue
[02:01] <saivann> asac : Wait, I will try to update my pbuilder environment. After all, xulrunner has been updated
[02:01] <asac> so most likely the configure.ac patch is not properly applied in our 99_auto patch
[02:02] <asac> or the configure flags we pass from rules are wrong
[02:02] <asac> saivann: no that shouldnt be the problem here
[02:02] <asac> (e.g. outdated xulrunner ) :)
[02:02] <saivann> asac : No, that's my error, I'm was not working on the patched tree, wait, I will give you the right values
[02:03] <asac> k
[02:08] <saivann> asac : s,@GECKO_CFLAGS@,|#_!!_#|-fshort-wchar -I/usr/include/xulrunner-1.9/unstable -I/usr/include/nspr   -I/usr/include/xulrunner-1.9 -I/usr/include/xulrunner-1.9/commandhandler -I/usr/include/xulrunner-1.9/content -I/usr/include/xulrunner-1.9/dom -I/usr/include/xulrunner-1.9/find -I/usr/include/xulrunner-1.9/gfx -I/usr/include/xulrunner-1.9/gtkembedmoz -I/usr/include/xulrunner-1.9/locale -I/usr/include/xulrunner-1.9/p
[02:08] <saivann> ref -I/usr/include/xulrunner-1.9/string -I/usr/include/xulrunner-1.9/webbrwsr -I/usr/include/xulrunner-1.9/xpcom -I/usr/include/xulrunner-1.9/xpconnect,g
[02:08] <saivann> s,@GECKO_LIBS@,|#_!!_#|-L/usr/lib/xulrunner-devel-1.9/lib -lxpcomglue_s -lxul -lxpcom -lplds4 -lplc4 -lnspr4 -lpthread -ldl  ,g
[02:08] <asac> still the same
[02:08] <asac> check config.log
[02:08] <saivann> asac : I see, and now that's with patches applied
[02:09] <asac> yeah. so either configure doesnt have our changes
[02:09] <saivann> asac : Right!! We did not patch configure!
[02:09] <asac> well, there is no or ;)
[02:09] <asac> saivann: 99_autogen patch should
[02:09] <saivann> asac : ah.
[02:09] <asac> try lsdiff debian/patches/99_*
[02:10] <saivann> asac : I have config.log, what do you want to search in this file?
[02:10] <asac> saivann: for GECKO_CFLAGS
[02:10] <asac> :)
[02:11] <saivann> asac : pkg_cv_GECKO_CFLAGS='-fshort-wchar -I/usr/include/xulrunner-1.9/unstable -I/usr/include/nspr  '
[02:11] <saivann> pkg_cv_GECKO_LIBS='-L/usr/lib/xulrunner-devel-1.9/lib -lxpcomglue_s -lxul -lxpcom -lplds4 -lplc4 -lnspr4 -lpthread -ldl  '
[02:11] <asac> thats wrong
[02:11] <asac> maybe ther eis --with-gecko ?
[02:11] <asac> in the log?
[02:13] <saivann> asac : Is lsdiff suposed to find if patches has been applied?
[02:13] <asac> list the files affected by a patch
[02:13] <asac> so configure should be in there ;)
[02:15] <saivann> asac : It is
[02:16] <saivann> asac : In build logs, --with-gecko is at the end of the LDFLAGS :
[02:16] <saivann> LDFLAGS=" -Wl,--as-needed" /tmp/buildd/chmsee-1.0.0/./configure --build=x86_64-linux-gnu --prefix=/usr --includedir="\${prefix}/include" --mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" --sysconfdir=/etc --localstatedir=/var --libexecdir="\${prefix}/lib/chmsee" --disable-maintainer-mode --disable-dependency-tracking --srcdir=.   --with-gecko=libxul
[02:16] <asac> that looks ok
[02:16] <asac> in config.log you have to hunt why libxul-embedding-unstable is not used
[02:16] <asac> even though --with-gecko=libxul is set
[02:17] <saivann> ...
[02:18] <saivann> I really don't understand why if we use the same files as 1.0.1
[02:19] <saivann> Except of course... is it possible that autogen.sh does not update files correctly?
[02:20] <saivann> asac : would that be possible?
[02:21] <asac> i doubt that
[02:21] <saivann> oh.. autogen.sh is pretty short
[02:22] <asac> however, the patch is most likely broken. you can try to look in configure file and asee if the changes we did for configure.ac are there
[02:23] <asac> in any case night has to come here
[02:26] <asac> sorry that it ended up harder than expected
[02:26] <asac> but the procedure is good for other stuff for sure
[02:26]  * asac off
[02:26] <asac> not saying that you should stop now ;)
[02:26] <saivann> asac : Oh you go? Good night ;) Thanks for the time to spent with me, I will continue to search
[02:27] <saivann> asac : And well this is not your fault if this package is frustrating ;)
[04:36] <saivann> asac : I don't want to give false hopes, but I think that I found the problem! Working..
[04:56] <saivann> asac : I successfully applied the standalone glue! I'm still stuck with FTBFS problems with libltool and working around this.
[06:36] <saivann> asac : When you have time for it, I still have a FTBFS but standalone glue works, here's the current package : http://upload.leservicetechnique.com/bugs/chmsee_1.0.0-1ubuntu1~hardy1.tar.gz
[06:36] <saivann> asac : build logs : http://paste.ubuntu.com/24635/
[06:37]  * saivann off
[07:05] <gnomefreak> asac: you up yet?
[07:16]  * gnomefreak wonders if we get redirected to new wiki
[07:55] <gnomefreak> I have finished with the roadmap wiki for now. Let me know if you want something added or have ideas for it. https://wiki.ubuntu.com/MozillaTeam/Roadmap
[07:57] <gnomefreak> or maybe i should use mozillateam/roadmap/todolist but its fine for now
[08:35] <gnomefreak> also i cant get sound now :( volume control everything is enabled(not muted) :(
[09:15] <asac> gnomefreak: yes?
[09:15] <gnomefreak> yes?
[09:15] <asac> saivann: yeah. that look quite good
[09:16] <asac> saivann: what was the problem?
[09:18] <gnomefreak> that email about the dates is hardewr than it was needed adn why did the dates in each section not match any other dates on attachment
[09:18] <gnomefreak> are these the dates? 20-07-2008
[09:18] <gnomefreak> 31-08-2008
[09:18] <gnomefreak> 19-10-2008
[09:18] <gnomefreak> 23-11-2008
[09:18] <gnomefreak> 04-01-2008
[09:30] <asac> reconnect
[09:30] <asac> well more a disconnect ;)
[09:34] <asac_> bad thing
[09:34] <asac_> shaky connection
[09:34] <asac_> gnomefreak: i think at the bottom of the mail there are the actual release dates
[09:34] <asac_> err, meeting dates
[09:35] <gnomefreak> asac_: not sure but i will ask volan(spelling) or wait for him to reply. if the last ones are it what the hell do the other ones hav eto do?
[09:39] <asac__> argh
[09:39] <asac__> reconnected again
[09:39] <asac__> gnomefreak: those are the mails we send out
[09:39] <asac__> with the dates _when_ they are send
[09:39] <asac__> (e.g. the preannonucements)
[09:49] <gnomefreak> ah ok
[09:49]  * gnomefreak needs a smoke. i havent fallen asleep yet and its not 4:49am
[09:52] <asac> gnomefreak: i doubt that you fall asleep if sit infront of the computer ;)
[09:52] <asac> or smoke a cigarette
[09:58] <gnomefreak> asac: almost fell asleep while smoking my eyes kept closing and i thought they were open :(
[09:58] <asac> gnomefreak: then lay down and sleep ;)
[09:58] <asac> thats simple
[09:58] <gnomefreak> asac: i will soon
[09:58] <asac> i mean if the eyes keep closing you will just fade a away
[09:58] <gnomefreak> i would like to get sound working first
[09:58] <asac> haha
[09:59] <asac> thats your problem then ;)... dont complain about a lack of sleep
[09:59] <gnomefreak> something changed maybe alsa or default card/driver or something adn the one person that knew didnt answer me
[10:02] <gnomefreak> persia > gnomefreak: cat /proc/asound/cards  Notice the new  device.  Change your default.  Ask Hobbsee for  details :)
[10:02] <gnomefreak> me doesnt understand since you cant edit that file
[10:03] <gnomefreak> hobbsee had left right before that comment
[10:03] <gnomefreak> asac: so you know anything about this new device?
[10:06] <asac> sound issues are not in my field of expertise
[10:06] <asac> i'd love to get rid of all sound ;)
[10:08] <gnomefreak> i kind oif like music while working more so working on wikis
[10:10] <gnomefreak> asac: feel free to take a look at our roadmap wiki and add so other topics (or giv eme a list and i will. so far there is = TO DO = and == assigned tasks == and == unassigned tasks ==
[10:16] <gnomefreak> ok im off to bed ill ask crimsun if we see eachother in one of the channels
[10:16]  * gnomefreak cant keep eyes open
[12:30] <saivann> asac : I'll probabl be there in ~4 hours, during the current day
[12:30] <asac> kk
[15:39] <saivann> asac : ping
[15:39] <asac> saivann: yeah .. more or less here
[15:39] <saivann> asac : I'm here for 5 hours
[15:40] <asac> saivann: whats up? i read that you managed to get it done mostly
[15:41] <saivann> asac : Yes! I found the problem which was in autoreconf patch, which is now correct. Now I still have FTBFS for another reason, see build logs here : http://paste.ubuntu.com/24635/
[15:41] <saivann> asac : I don't know if you can help me at this point..
[15:42] <asac> saivann: i think you have to run intltoolize -f -c and include the changes in the autogen patch
[15:42] <asac> not sure why its not in the autgen.sh
[15:43] <saivann> asac : autogen.sh contains this : libtoolize -c --automake
[15:43] <saivann> ho. ok
[15:43] <asac> found something?
[15:43] <saivann> asac : No, not yet, but I will try what you suggest right now
[15:44] <asac> saivann: maybe -f is just missing in autogen.sh
[15:44] <asac> i think it omits the update if it thinks that all files are in place
[15:45] <saivann> asac : autoget.sh use libtoolize -c --automake but not intltoolize -f -c
[15:46] <asac> saivann: add an -f
[15:47] <saivann> asac : Ok
[15:47] <asac> bug 245184
[15:53] <armin76> bumb
[15:54]  * armin76 blames asac
[15:57] <asac> armin76: there is nothing left to bumb
[15:58] <armin76> asac: xulrunner :P
[16:00] <saivann> asac : Does not FTBFS anymore, you're a genius
[16:01] <asac> saivann: you are quite smart too
[16:01] <asac> saivann: others dont get that far ... no matter what i do ;)
[16:02] <saivann> asac : Really, it's not kind of encouraging words? :P
[16:02] <asac> armin76: xulrunner is fresh and great ... we are far ahead of everyone
[16:02] <armin76> thank you thank you :D
[16:02] <armin76> asac: 1.8?
[16:02] <asac> saivann: its encouraging that you fixed it ;)
[16:02] <asac> armin76: oh :) ... its not in ubuntu, but universe
[16:03] <saivann> asac : Thanks :) I'm glad to have worked until the end. I'm going to test the package now
[16:03] <asac> saivann: yeah. enjoy ;)
[16:03] <saivann> :)
[16:06]  * asac has no idea what chmsee does ;(
[16:22] <asac> saivann: let me know when you attache a) the minimal patch + b) the complete debdiff to the bug
[16:22] <asac> so i can test and sponsor
[16:28] <saivann> asac : Ok, it should not be too long, I'm looking to be sure that I don't forget anything
[16:29] <saivann> asac : chmsee is a good tool to open .chm files (it's a common help file format used by many programs, and opened by the help center in Windows XP)
[16:35] <asac> saivann: take your time ;)
[16:35] <saivann> asac : I want to build it in my PPA before, just a precaution
[16:35] <asac> sure
[16:35] <asac> its good to have for SRUs anyway
[16:36] <asac> saivann: remember to lower the version by appending ~saivann1
[16:36] <asac> or something to the package revision
[16:36] <saivann> asac : Yes, I added ~ppa1 :) As I do normally
[16:36] <asac> good
[16:36] <saivann> asac : And I will create the patch with hardy-proposed in the changelog
[16:37] <asac> top
[16:39] <saivann> asac : For the patch, chmsee_1.0.0-1ubuntu1~hardy1 is the good version name I guess?
[16:40] <asac> usually we dont use codenames, but versions
[16:40] <asac> e.g. 8.04.1
[16:40] <asac> (for 1 revision of 8.04 backports
[16:40] <asac> )
[16:41] <saivann> So : chmsee_1.0.0-1ubuntu1~8.04.1 ?
[16:41] <saivann> asac
[16:41] <asac> bug 245184
[16:43] <saivann> asac : So is chmsee_1.0.0-1ubuntu1~8.04.1 correct?
[16:44] <asac> looks good
[16:44] <asac> or ubuntu<IP_ADDRESS> :)
[16:44] <asac> whatever you prefer
[16:45] <saivann> ubuntu0.* ? Shouldn't we keep the existing *1ubuntu1* ?
[16:45] <asac> saivann: where does 1ubuntu1 exist?
[16:45] <asac> in intrepid we hvae 1.0.1 iirc
[16:45] <saivann> asac : Current hardy version is : chmsee_1.0.0-1ubuntu1
[16:46] <asac> saivann: oh. then its wrong
[16:46] <asac> it has to be _higher_
[16:46] <asac> ~ == lower ;)
[16:46] <saivann> asac : Oh!
[16:47] <saivann> asac : That's right :P I did not think about that
[16:51] <saivann> asac  Ok then chmsee_1.0.0-1ubuntu<IP_ADDRESS> would be correct?
[16:51] <asac> i think so
[17:08] <saivann> asac : Thanks, and sorry I got a phone so I was not very active on the channel
[17:21] <saivann> asac : Before I open the SRU bug, can you review the patch? http://upload.leservicetechnique.com/bugs/chmsee_1.0.0-1ubuntu<IP_ADDRESS>.debdiff
[17:29] <asac> saivann: is there a bug for the desktop thing?
[17:29] <asac> if not either open one, or be more verbose so archive admin can understand whats going on and why this is suitable for a SRU
[17:30] <saivann> asac : Ok
[17:30] <asac> saivann: and maybe tell more about what you did in rules: e.g. drop -rpath in favour of standalone glue + use --with-gecko=libuxl... to use standalone glue
[17:30] <asac> + whatever you did
[17:30] <asac> the patch itself looks great
[17:31] <saivann> asac : If I give more details in the SRU bug report instead of the changelog, would it be ok?
[17:31] <asac> if the .desttop files are not required just drop the changes
[17:31] <asac> saivann: well. you currently have two of four entries linked to bugs
[17:31] <saivann> asac : I believe that I will drop the .desktop file since it does not cause issues in up-to-date hardy, and since it's already fixed in intrepid
[17:32] <asac> saivann: right
[17:32] <asac> drop that
[17:32] <asac> and wrap the debian/rules changes in a changelog entry for xulrunner 1.9 support
[17:32] <asac> which is most likely bug 2044..
[17:33] <saivann> asac : Ok, I do this
[17:33] <asac> actually i would use only one bug: "xulrunner 1.9 support" and dupe the others into that
[17:33] <asac> then just make changelog read: + xulrunner 1.9 support
[17:34] <asac>  - debian/rules: use --with-gecko=libxul... and drop -rpath LDFLAGS
[17:34] <asac>  - debian/patches/....: do this
[17:34] <asac>  - debian/patches/....: do that ;)
[17:34] <asac> first line with (LP: #XXXX)
[17:55] <saivann> asac : What about this : http://upload.leservicetechnique.com/bugs/chmsee_1.0.0-1ubuntu<IP_ADDRESS>.debdiff
[18:07] <fta> SEAMONKEY_1_1_11_RELEASE
[22:25] <asac> saivann: thats ok
[22:26] <saivann> asac : Oh thanks, I uploaded the patch to the bug report
[22:26] <asac> bug #232402
[22:27] <asac> saivann: attach a debdiff with filtered out autogen
[22:27] <asac> too
[22:27] <asac> i will ack it then
[22:27] <saivann> asac : But the patch doesn't work without autogen, are sure that you want this?
[22:27] <asac> yes
[22:27] <asac> for review
[22:28] <saivann> asac : Ok, I do it right now
[22:28] <asac> just say that its filtered out for brevity
[22:28] <asac> nobody really wants to read the autofiles changes ;)
[22:28] <saivann> asac : thanks for showing me filterdiff ;)
[22:32] <saivann> asac : Attached
[23:56] <marcus_> quick question: can I get at this: http://bazaar.launchpad.net/~mozillateam/flock/flock.head/files/fta%40sofaraway.org-20080608215313-8sy67d8oualhhh3h?file_id=debian-20080603204533-7sw9230101gige8g-1
[23:56] <marcus_> via svn or cvs?
[23:56] <marcus_> thanks.


 I think that's the time for superfan 3 valorie
 @DarinMiller, i cant see plasma wayland option in gdm3 :(
 your using sddm ?
[12:07] <BluesKaj> Hi folks
[19:26] <genii> Is i386 dropped now? I don't see an iso at http://cdimages.ubuntu.com/kubuntu/daily-live/current/ for it
[21:45] <mparillo> It has been a while
[21:52] <mparillo> https://lists.ubuntu.com/archives/kubuntu-devel/2018-May/011657.html


[17:33] <x-fak> hi
[17:33] <x-fak> i'm running ubuntu on Odroid
[17:33] <x-fak> Arm64 architecture
[17:34] <x-fak> i want to install kodi, but with apt-get install kodi, i have only Kodi 15.2+dfsg1-3ubuntu1
[17:34] <x-fak> why there is not 16.1 Jarvis?
[17:39] <x-fak> anyone?
[17:41] <k1l_> !info kodi
[17:41] <k1l_> ah, no bot in here. 15.2+dfsg1-3ubuntu1 is the release that is included in 16.04
[17:42] <x-fak> k1l_ ?
[17:44] <k1l_> kodi 16.1 was released 2 days ago? well. you will need a ppa or another 3rd party repo then.
[17:46] <k1l_> but look out if that repo includes arm64 packages. which is not that common so far
[17:51] <x-fak> k1l_ , kodi jarvis was release 2 month ago
[18:06] <x-fak> k1l_ , i now have this issue: http://kodi.wiki/view/HOW-TO:Install_Kodi_for_Linux


[07:24]  * nlsthzn waves
[15:44] <nlsthzn-work> finally my working day draws to a close... weeeeee!!! ~cheers till later then, kthxbai


[07:27] <dholbach> brb, relocating
[13:46] <dholbach> all rightie... relocating - brb
[16:12] <dholbach> all right my friends - have a great weekend everyone! :)
[17:01] <jose> jcastro: just got my tshirt on the mail, thanks a bunch! :)
[17:03] <jcastro> \o/ yeah!
[17:53] <czajkowski> evening
[17:53] <popey> yo
[17:55] <czajkowski> looking forward to tomorrow
[17:55] <czajkowski> you on the evening tickets also ?
[17:58] <popey> ya
[17:58] <czajkowski> excellent
[17:58] <czajkowski> curry afterwards perhaps :)
[18:06] <popey> oooh yes.
[18:07] <popey> not seen you for ages
[18:07] <popey> be good to catch up
[18:10] <czajkowski> yup :) \o/
[18:10] <czajkowski> last time I'm in the UK till June that I'm free
[18:10] <czajkowski> :D
[18:10] <czajkowski> will need beer and curry
[18:10] <czajkowski> yummy yummy ciders!


[11:27] <czajkowski> Morning
[14:53] <elky> AlanBell, http://browsershots.org/screenshots/154ef7c8af2a55841b72d57ced13f39c vs http://browsershots.org/screenshots/137dba994c781edf7b2cfd8522945970 \o/
[14:55] <AlanBell> gosh, how retro!
[14:56] <elky> heh. ie's less than 8 need to go find a volcano crater.
[14:57] <elky> i eventually remembered that i had something that resembles ie6 in the wince partition of the craptastic smartq tablet.
[15:00] <AlanBell> topic
[15:01] <elky> hm?
[15:01] <AlanBell> I will learn to type / one day
[15:01] <elky> heh
[15:01] <AlanBell> just looking for the meeting date
[15:02] <elky> yeah, i know, another one already
[15:02] <elky> at iirc, bus-o-clock for me
[15:05] <AlanBell> http://wiki.ubuntu-women.org/Meetings/September2010/Agenda put it on the agenda anyhow
[15:06] <elky> http://bazaar.launchpad.net/~ubuntu-women/ubuntu-women.org/mointheme/revision/12
[15:07] <elky> going to be a quick meeting at this rate
[15:09] <elky> ah, no, it's at 6am. even less likely than bus-o-clock.
[16:38] <nigelb> AlanBell: heh, retro indeed
[16:38] <nigelb> after using ubuntu for so long, IE looks ugly
[16:41] <Pendulum> nigelb: you did not need the modifying statement there
[16:41] <Pendulum> IE looks ugly would have been enough :P
[16:41] <nigelb> lol, true
[16:41] <Pendulum> erm... why is the next meeting on a wednesday rather than a thursday? did I miss something said at the last meeting?
[16:42] <nigelb> Lol, the meeting that was friendly to my tz I missed, but made it for the one that was at 3 am.  I'm awesome.
[16:42] <Pendulum> nigelb: that's because your sleep cycles is so messed up it impresses even me
[16:43] <nigelb> I'm not sure mine's a circle, more like a square :p
[17:16] <maco> i was once asked what timezone i'm in and what timezone my body thinks i'm in
[17:16] <maco> eastern us, hawaii  <-- my answer
[17:18] <nigelb> maco: hahaha
[17:28] <Pendulum> heh
[17:59] <pleia2> Pendulum: meetings these days are wednesday at 20:00 and thursday at 10:00 (announced in the beginning of august based on doodle results)
[18:00] <pleia2> "Ubuntu Women Project Meetings are held on the 2nd Wednesday of each month at 20:00 UTC and on the 4th Thursday of each month at 10:00 UTC."
[18:00] <pleia2> that's the blurb I was looking for :)
[18:23] <Pendulum> pleia2: ah, okay. I think I knew that, but then it was differeng on some page I looked at so I got confused


[12:46] <crimsun> err, am I supposed to be getting error spew when attempting to checkout ubuntu-edgy-updates.git?
[12:47] <crimsun> (checking out ubuntu-2.6.git completes successfully)
[12:54] <crimsun> hmm, I guess so, since checking out ubuntu-edgy completes successfully, too. Probably the "shouldn't see" privilege. :)
[01:02] <qt> test
[01:02] <qt>  Hi all. How do I tell what kind of phy device my onboard 3Com 3C910 chip is attached to?
[02:32] <zul> morning
[02:40] <ChrisBradley> does anyone here work with the module assistant?
[04:53] <BenC> kylem: ping
[04:54] <kylem> yo dude
[04:54] <BenC> how's things?
[04:54] <kylem> good good
[04:54] <kylem> finally feeling a bit better
[04:54] <kylem> trying to take care of some administriva atm.
[04:55] <BenC> good deal
[04:55] <BenC> when you get back to kernel stuff, feel free to upload your -proposed stuff if you want
[04:56] <tepsipakki> does that include the tg3 backport for dapper, among other things?-)
[04:57] <kylem> okie doke
[04:57] <kylem> tepsipakki, yeppers
[04:58] <tepsipakki> kylem: sweet :)
[05:27] <zul> oh xensource how much i despise you sometimes
[06:00] <Mithrandir> BenC: any plans on fixing the resume/switch_console stuff that mjg59 asked you about a month ago?
[06:09] <BenC> Mithrandir: Yeah, working on it now
[06:09] <Mithrandir> great, thanks.
[06:12] <BenC> kylem: Am I remembering right that you had a patch for feisty for bug #36885?
[06:12] <BenC> https://bugs.launchpad.net/distros/ubuntu/+source/linux-source-2.6.20/+bug/36885
[06:12] <BenC> shit, wrong bug
[06:12] <BenC> https://bugs.launchpad.net/distros/ubuntu/+source/linux-source-2.6.20/+bug/33950
[06:12] <BenC> that one
[06:14] <kylem> yeppers.
[06:14] <BenC> kylem: Is it in your git, or is there a patch?
[06:14] <kylem> i think it's in git.
[06:14] <kylem> i'm not quite sure what do to with it, since you said that people were expecting different things.
[06:15] <BenC> it's an oddball bug, but I think we're stuck keeping things the same as dapper/edgy
[06:15] <kylem> k.
[06:15] <kylem> http://people.ubuntu.com/~kyle/hdaps_invert_no_smapi_feisty.diff
[06:16] <BenC> would be nice if the axis was configurable at runtime instead of this stupid table of hope-it-works-for-everyone crap
[06:16] <BenC> kylem: thanks
[06:16] <kylem> hmm, could fairly easily make it a sysfs attribute if you want
[06:17] <BenC> it's not possible to have more than one of these devices in a system is it?
[06:17] <kylem> i would doubt it.
[06:17] <kylem> unless the driver eventually becomes some kind of generic thing.
[06:17] <BenC> yeah, sysfs changeable axi configuration would be nice then
[06:18] <kylem> should be fairly easy.
[06:19] <BenC> basically add separate x/y axis inversion and make then both module_param's
[06:21] <BenC> kylem: I'm willing to drop the dmi table if we can configure it
[06:22] <kylem> hrm.
[06:23] <BenC> well, drop the dmi table changes we have in dapper/edgy in favor of this
[06:23] <BenC> leave what's there
[08:41] <BenC> Mithrandir: ping
[08:42] <Mithrandir> hi BenC
[08:42] <BenC> Mithrandir: Hey, can you let me know if ata_piix still doesn't work for you on 2.6.20-3?
[08:42] <BenC> re: bug #64433
[08:43] <Mithrandir> BenC: oh, I probably never had the problem, but it was marked as fixed by the kernel upload and it was a targetted bug, so I closed it (it shows up in my listings, which gets annoying)
[08:44] <BenC> It's re-targetted to 2.6.20 for some reason, probably because I removed the patch
[08:45] <BenC> Mithrandir: Sorry, I misread it as you having the same issue
[08:45] <BenC> I'll close it, I'm pretty sure ata_piix is the right driver, and works now
[08:45] <Mithrandir> it was added to 2.6.19 by Christian Kellner
[08:45] <mjg59> BenC: If both ata_piix and ahci can drive the chip (which they almost certainly can), ahci is preferable
[08:46] <BenC> mjg59: Just wondering why 0x268{1,2} are in ahci and 0x2680 is specifically in ata_piix
[08:46] <BenC> just seems like someone made a conscious decision
[08:47] <BenC> or maybe it's just been overlooked
[08:47] <mjg59> It's quite possible that > 0x2680 no longer have piix-compatibility
[08:47] <mjg59> But that doesn't explain why it isn't in ahci
[08:47] <mjg59> It's an utter mess.
[08:47] <mjg59> We probably ought to be keying off the device class - that ought to be different for ahci devices
[09:16] <BenC> mjg59: ping, bug #75305
[09:16] <BenC> does it work with 2.6.20-3?
[09:17] <mjg59> BenC: Haven't had a chance to try
[09:35] <BenC> Mithrandir: pm/console fix is in git now
[09:35] <Mithrandir> BenC: great, thanks.
[09:36] <BenC> Mithrandir: When's the latest I can upload a new kernel to not much with Herd 2 for you?
[09:36] <BenC> s/much/muck/
[09:36] <Mithrandir> BenC: preferably before next week.
[09:38] <BenC> can do
[10:56] <gnomefreak> BenC: are you around for a minute. i have a bad initramfs-tools bug and can use advice if you have any
[10:56] <BenC> is it the ide-generic bug?
[10:57] <gnomefreak> kernel no boot
[10:57] <BenC> probably
[10:57] <gnomefreak> i get a mdadm error
[10:57] <BenC> add ide0=noprobe ide1=noprobe to command line
[10:57] <gnomefreak> its only 2.6.20
[10:57] <BenC> see if that fixes it
[10:57] <gnomefreak> add that to boot options?
[10:58] <BenC> initramfs-tools wont update any initrd's except the newest one when updated
[10:58] <BenC> yeah
[10:58] <gnomefreak> ok gonna try this
[11:16] <gnomefreak> BenC: doesnt fix it it still wont boot