[00:06] <marcoceppi> do I just include setup/gui/fceux.desktop in the tree?
[00:25] <wililupy> When building a kernel snap, I now have to create a symbolic link named kernel.img to vmlinuz in my parts/kernel/install directory before I ran snapcraft stage/prime/snap. Is this something new or should I just rename vmlinuz to kernel.img?
[01:55] <sergiusens> marcoceppi gpsd uses scons (which that plugin was built for)
[01:55] <sergiusens> doesn't have many miles/km on it yet
[01:56] <marcoceppi> sergiusens: I didn't see anything in snappy playpen, which is where I searched for scons usage
[01:57] <marcoceppi> sergiusens: where's the snapcraft yaml for gpsd?
[01:58] <sergiusens> marcoceppi here's the part definition https://bugs.launchpad.net/snapcraft/+bug/1587289
[01:58] <mup> Bug #1587289: Bad includes generated by snapcraft scons plugin <Snapcraft:Invalid by sergiusens> <https://launchpad.net/bugs/1587289>
[02:02] <marcoceppi> sergiusens: well I got it working eventually, this is what the yaml looks like now
[02:02] <marcoceppi> sergiusens: http://paste.ubuntu.com/23066003/
[02:03] <marcoceppi> sergiusens: this line just feels weird to me
[02:03] <marcoceppi>     scons-options:
[02:03] <marcoceppi>       - --prefix=../install/usr
[02:03] <sergiusens> marcoceppi so your SConstruct does not support using DESTDIR?
[02:03] <marcoceppi> sergiusens: not mine, not sure
[02:04] <sergiusens> does using that --prefix make any assumtions about runtime?
[02:04] <sergiusens> you probably want --prefix=$SNAPCRAFT_PART_INSTALLDIR (not implemented yet)
[02:04] <marcoceppi> sergiusens: so far, does not appear so
[02:04] <marcoceppi> since it works
[02:04] <marcoceppi> sergiusens: I'd love to use a variable like that ;)
[02:05] <marcoceppi> sergiusens: here is there SConstruct file http://paste.ubuntu.com/23066005/
[02:05] <mup> PR snapcraft#737 opened: Release changelog for 2.15 <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/737>
[02:06] <marcoceppi> prefix seems to be used only during the installation phase
[02:06] <marcoceppi> (thankfully)
[02:12] <sergiusens> marcoceppi usually code that builds on Windows has location independent code... usually
[02:12] <sergiusens> good luck with that
[02:13] <marcoceppi> sergiusens: well, that must be from when the win32 and SDL code was in the same repo, that's split a while ago but still seems to hold true
[02:13] <marcoceppi> my only problem now is audio with strict confinement, but that seems to be a snappy isue
[02:53] <sergiusens> robert_ancell hey, thanks for updating the PR, there is one minor issue in there still if you don't mind fixing (whitespace between method/function and ())
[02:54] <robert_ancell> sergiusens, fixed, thanks
[07:06] <mup> PR snapd#1693 opened: tests: add qemu to our spread.yaml and update README <Created by mvo5> <https://github.com/snapcore/snapd/pull/1693>
[08:21] <zyga> o/
[08:35] <zyga> Son_Goku: hey, didn't you menition that FHS standard is at 3.0 now
[08:35] <Son_Goku> yes
[08:36] <zyga> Son_Goku: I'm looking at http://www.pathname.com/fhs/ and I see 2.3 released in 2004
[08:36] <Son_Goku> https://wiki.linuxfoundation.org/lsb/fhs-30
[08:36] <Son_Goku> it moved to LF
[08:36] <zyga> aha
[08:36] <zyga> thanks
[08:36]  * zyga hates dead pages like that
[08:53] <Son_Goku> zyga: don't we all?
[09:30] <ogra_> sigh
[09:30] <ogra_> so my daily upgrade on 16.04 gets completely stuck in the apparmor postinst
[09:30] <zyga> ogra_: what's up?
[09:30] <zyga> ogra_: anything in syslog?
[09:30] <ogra_> well, it looks for upstart
[09:31] <Son_Goku> :/
[09:31] <Son_Goku> there's so much sad right there
[09:31] <zyga> ogra_: what do you mean specifically?
[09:31] <ogra_> http://paste.ubuntu.com/23066846/
[09:32] <zyga> well, there you have it update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
[09:32] <ogra_> sure
[09:32] <zyga> all postinst scripts are evil
[09:32] <zyga> because they are never perfect
[09:32] <ogra_> zyga, tell that to a million or two of our users who can not upgrade their LTS installs anymore
[09:33] <ogra_> this is a normal 16.04 ... no PPAs or fancy hacks ... just using the daily update-manager run
[09:33] <zyga> ogra_: aha, that's more severe then
[09:33] <seb128> does it hang or just take time?
[09:33] <ogra_> seb128, well, i killed update-manager after 20min the first run ...
[09:33] <Son_Goku> ogra_ this must be what my colleague at work was grumbling about
[09:34] <Son_Goku> it somehow magically worked after apt upgrade twice, the apt-get install -f, then install -f again
[09:34] <seb128> no report of that issue so far, doesn't look like it impact everyone or we would have read more about it
[09:34] <Son_Goku> which makes zero sense
[09:35] <ogra_> (admittedly this machine was upgraded 12.04->14.04->16.04 ... so perhaps something on the way hasnt been cleaned up properly, ut this is my desktop, i dont do any os level changes or hackery on it )
[09:36] <seb128> the box I'm using was upgraded all the way every cycle since 2011
[09:36] <seb128> no such issue
[09:36] <ogra_> every cycle != LTS->LTS
[09:36] <seb128> right
[09:36] <ogra_> so this might be related
[09:36] <seb128> but it's usually enough to stack cruft as well
[09:37] <ogra_> it gets more developer attention :)
[09:37] <seb128> did you get a bt or details about the hanging process?
[09:37] <seb128> seems worth a bug report in any case
[09:37] <ogra_> yeah
[09:42]  * ogra_ filed bug 1614459
[09:42] <mup> Bug #1614459: daily upgrade on 16.04 hangs <apparmor (Ubuntu):New> <https://launchpad.net/bugs/1614459>
[09:42] <ogra_> funnily i cant ctrl-C out of the hanging process
[09:48]  * ogra_ comments the update-rc.d call in the postinst
[09:50] <ogra_> hrm ... loooks like the upstart thing isnt actually the issue ... it still hangs ... just without any error now
[10:02] <zyga> Son_Goku: https://bugzilla.redhat.com/show_bug.cgi?id=1367825#c11
[10:02] <Son_Goku> zyga, did you run spectool -g on the specfile first?
[10:03] <Son_Goku> it does work, but you have to download the tarball with the right name
[10:03] <Son_Goku> spectool -g snapd.spec
[10:04] <zyga> yes
[10:04] <zyga> it doesn't work because that url is 404
[10:04] <zyga> ther'es no such thing on github apparently
[10:04] <zyga> Son_Goku: look at https://github.com/snapcore/snapd/releases/tag/2.11
[10:05] <zyga> the tarball URL is https://github.com/snapcore/snapd/archive/2.11.tar.gz
[10:05] <Son_Goku> I tried this: https://github.com/snapcore/snapd/archive/2.11/snapd-2.11.tar.gz
[10:05] <Son_Goku> that worked
[10:07] <zyga> odd, I just ran spectool
[10:07] <zyga> let me check again
[10:07] <zyga> Son_Goku: btw, about directory ownership, did you have something like this on your mind? http://paste.ubuntu.com/23066917/
[10:07] <Son_Goku> yeah
[10:08] <Son_Goku> it essentially mimics how libvirt is set up in /var/lib/libvirt
[10:08] <Son_Goku> in this case, /var/lib/snapd/snaps is where the snaps go
[10:08] <Son_Goku> as opposed to /snap
[10:09] <zyga> Son_Goku: odd, now spectool downloads the file, ...., anyway, let me commit that
[10:09] <zyga> Son_Goku: as for /snap that's a separate issue :-) I'm working on that
[10:10] <zyga> Son_Goku: ok pushed again, have a look
[10:12] <zyga> Son_Goku: essentially right now as of 2.11 that won't work without several major patches, I'm open to the conversation but you already know that :)
[10:14] <zyga> Son_Goku: the %dir entries make rpmbuild choke, those things are only made at runtime, should I just mkdir them in install?
[10:15] <Son_Goku> mkdir and install them
[10:15] <Son_Goku> err, mkdir in %install
[10:15] <zyga> right, tring
[10:15] <zyga> trying*
[10:16] <Son_Goku> as for the directories not working right now without patches, I'm not worried about that at the moment, as you *can* patch it
[10:17] <zyga> Son_Goku: well, the patch'd better be something that upstream can support over time, it's a major change that has to be architected correctly
[10:17] <Son_Goku> yes
[10:17] <zyga> Son_Goku: I don't want to break existing snaps
[10:17] <Son_Goku> but you're upstream :)
[10:17] <Son_Goku> you can also make the legacy packaging migrate the data around as needed
[10:17] <Son_Goku> s/legacy/debian/
[10:17] <zyga> Son_Goku: yes but has to be planned and executed, I'm not a one-man team
[10:18] <Son_Goku> yes
[10:18] <Son_Goku> this was an issue that was brought up at the sprint
[10:18] <zyga> Son_Goku: heh, github just broke
[10:18] <zyga> remote: ruby-jemalloc: symbol lookup error: /data/github/current/vendor/gems/2.1.7/ruby/2.1.0/gems/json-1.8.3/lib/json/ext/generator.so: undefined symbol: rb_data_typed_object_alloc
[10:19] <zyga> I get this on each push
[10:19] <Son_Goku> O.o
[10:19] <Son_Goku> that's...
[10:19] <zyga> I'll just commit and scp to fedorapeople
[10:19] <Son_Goku> yeah
[10:20] <zyga> I guess github is not using snaps ;)
[10:21] <zyga> and they pushed some partial updates
[10:21] <Son_Goku> github does jenkins deploys
[10:21] <Son_Goku> it's very ugly stuff
[10:21] <Son_Goku> I've heard rumors that people describe the codebase as duct tape and silly string
[10:21] <zyga> are they public about about the deploy process?
[10:22] <zyga> I read some cool and nice things about them on their blog
[10:22] <zyga> (~100 deploys a day)
[10:23] <Son_Goku> not really
[10:23] <Son_Goku> they've talked about it at a high level
[10:23] <Son_Goku> but never in detail
[10:37] <zyga> Son_Goku: I've updated snapd to 2.12, no change on /snap yet but I'll do all the things I can today
[10:37] <zyga> (exception request and patches)
[10:38] <Son_Goku> okay
[10:50] <mup> Bug #1614212 changed: Invalid character in ubuntu-core mount name breaks etckeeper <Snappy:New> <https://launchpad.net/bugs/1614212>
[10:57] <mup> PR snapcraft#738 opened: nodjs, gulp plugins: use http_proxy to connect npm registry <Created by m-shibata> <https://github.com/snapcore/snapcraft/pull/738>
[11:08] <mrCyborg> hey! I am heaving a strange issue, when I run `snapcraft snap` I get the following error while it is at the building part: "[Errno 39] Directory not empty: '/home/cyborg/Code/webtorrent-desktop-snap/parts/webtorrent-desktop/install'". content of snapcraft.yaml: https://gist.github.com/nloomans/5d87feb430901a0d1130be9d32bffd9f
[11:20] <mup> PR snapd#1694 opened: tests: adapt to new spread version <Created by fgimenez> <https://github.com/snapcore/snapd/pull/1694>
[11:27] <mup> PR snapd#1695 opened: tests: first iteration on all-snap image tests <Blocked> <Created by mvo5> <https://github.com/snapcore/snapd/pull/1695>
[11:30] <cjwatson> I'm struggling to build my local version of snapd.  Can somebody help?  The instructions in README.md appear to build the code downloaded from GitHub, not my local tree.
[11:31] <cjwatson> Oh, never mind, symlink in the right place under $GOPATH seems to do the trick.
[11:32] <mup> PR snapd#1696 opened: interfaces: add hidraw-device interface <Created by jocave> <https://github.com/snapcore/snapd/pull/1696>
[11:44] <mrCyborg> I've figured out that the problem only exist when I use a stage-package... can anyone help?
[11:53] <ogra_> GAH !
[11:53] <ogra_> so my laptop hangs the same way when updating apparmor
[12:03] <niemeyer> mrCyborg: sergiusens will be online in a short while and should be able to give you a hand
[12:05] <mrCyborg> nieweyer: tnx, I will wait
[12:26] <sergiusens> niemeyer mrCyborg I am online now :-)
[12:26] <ogra_> sergiusens, hmm, how would the macaroon affect logging in ?
[12:26] <sergiusens> oh, you have been hit by a bug
[12:27] <ogra_> do we hack around in pam ?
[12:27] <sergiusens> mrCyborg 2.15 should solve that
[12:27] <sergiusens> ogra_ I totally missed the ubuntu:ubuntu thing!
[12:27] <ogra_> :)
[12:27] <ogra_> smells like image corruption or some such
[12:28] <sergiusens> ogra_ there
[12:28] <ogra_> (though i'm waiting for the version answer ... if thats 16.04 all-snaps it might simply be an experimental image )
[12:28] <sergiusens> ogra_ what about the first user setup that is being put in place?
[12:29] <ogra_> well, we put it in place at image build time ... then cloud-init mangles it on first boot
[12:29] <sergiusens> mrCyborg it is currently making its way into the archives
 good to know it's a bug, is there a beta I can test, or is the patch not jet written?
[12:31] <sergiusens> mrCyborg it is being released; do you know how to run from sources?
[12:32] <mrCyborg> yes
[12:32] <sergiusens> mrCyborg or alternatively install the snapcraft deb from https://launchpad.net/~snappy-dev/+archive/ubuntu/snapcraft-daily/+build/10630457
[12:33] <sergiusens> mrCyborg if sources is your cup of tee, just make sure master is up to date and run snapcraft from /<path to source>/bin/snapcraft
[12:34] <mrCyborg> sergiusens: I will install the daily form launchpad
[12:35] <jcastro> niemeyer: is the snapcraft list moderated? I fear my message might be stuck in a queue somewhere.
[12:37] <sergiusens> jcastro when I posted with my wrong email I got a reply for it
[12:45] <mrCyborg> sergiusens: It solved that issue, but now I'm getting a bunch of "unable to chown" errors... "unable to chown /home/cyborg/Code/webtorrent-desktop-snap.bak/prime/usr/lib/x86_64-linux-gnu/libXtst.so.6: [Errno 1] Operation not permitted: '/home/cyborg/Code/webtorrent-desktop-snap.bak/prime/usr/lib/x86_64-linux-gnu/libXtst.so.6'", any idea?
[12:46] <sergiusens> mrCyborg does it fail the build or is it just printed out?
[12:47] <mrCyborg> just a warn, the build doesn't fail
[12:47] <sergiusens> mrCyborg great then; those are system imported libs but we do some _link_or_copy smarts to make things go faster
[12:47] <sergiusens> I need to filter out those errors
[12:50] <sergiusens> josepht mind taking care of what mrCyborg mentions?
[12:50] <sergiusens> mrCyborg mind logging a bug against snapcraft against the launchpad project?
[12:52] <mrCyborg> serguisens: About what? I thought this one was fixed? Still heaving some issues tho but I beleve the problem is on my side.
[12:54] <sergiusens> mrCyborg about the messages :-)
[12:55] <mrCyborg> serguisens: oh, sure
[12:58] <mrCyborg> serguisens I think I just found another but tho, dumping an (online) zip doesn't seem to respect file permissions.
[12:58] <josepht> sergiusens: sure, it's just a warning and is expected to fail unless snapcraft is run as root (i.e. for an os snap)
[13:04] <jdstrand> ratliff, tyhicks: fyi, bug #1614459 (ogra saw an oops on two machines)
[13:04] <mup> Bug #1614459: daily upgrade on 16.04 hangs <regression-update> <apparmor (Ubuntu):New> <https://launchpad.net/bugs/1614459>
[13:05] <ogra_> jdstrand, i still have  the update-manager sitting here in hanging state in case anyone needs more info
[13:06] <ratliff> ack jdstrand, thanks
[13:10] <mrCyborg> serguisens: issue submitted!
[13:11] <josepht> mrCyborg: thank you
[13:25] <cwayne> sergiusens: how do i tell the dump plugin where to put the files?
[13:25] <stokachu> cwayne: https://github.com/conjure-up/conjure-up/blob/master/snapcraft/snapcraft.yaml#L59
[13:27] <cwayne> stokachu: thanks
[13:28] <stokachu> np
[13:28] <cwayne> stokachu: do you know if it accepts globs
[13:28] <cwayne> like can i copy everything from launchers/ to bin/
[13:29] <stokachu> cwayne: yea it should
[13:29] <stokachu> filesets do accept globs so it should apply the same here as well
[13:31] <mup> PR snapd#1557 closed: many: introduce an assertstate task handler to fetch snap assertions <Critical> <Reviewed> <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/1557>
[13:50] <marcoceppi> so, USB inputs and stuff, what's the TL;DR on that?
[13:57] <mup> PR snapcraft#737 closed: Release changelog for 2.15 <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/737>
[14:17] <tyhicks> jdstrand, ratliff: see #ubuntu-devel for my response
[14:17] <jdstrand> yep, thanks
[14:17] <jdstrand> tyhicks: I didn't realize you were pinged there. I only saw the reference here
[14:17] <tyhicks> no problem
[14:22] <mup> PR snapd#1697 opened: allow bind() in the network client interface <Created by tych0> <https://github.com/snapcore/snapd/pull/1697>
[14:29] <mup> PR snapd#1695 closed: tests: first iteration on all-snap image tests <Blocked> <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/1695>
[14:30] <mup> PR snapcraft#670 closed: Remove .la files generated by autotools <Created by robert-ancell> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/670>
[14:39] <mup> PR snapcraft#739 opened: Only show chown warnings with --debug <Created by josepht> <https://github.com/snapcore/snapcraft/pull/739>
[14:45] <mup> PR snapd#1698 opened: tests: add all-snap spread image tests <Blocked> <Created by mvo5> <https://github.com/snapcore/snapd/pull/1698>
[14:46] <mrCyborg> hey! I was wondering why ~/snap is used for user data, instead of ~/.snap.
[14:52] <mup> PR snapd#1690 closed: partition: ensure that snap_{kernel,core} is not overriden with an empty value <Created by mvo5> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/1690>
[14:54] <Pharaoh_Atem> mrCyborg: dot folders are evil
[14:54] <Pharaoh_Atem> :P
[14:55] <Pharaoh_Atem> zyga: golang(gopkg.in/macaroon.v1) will sync out to the repos as soon as the latest updates mash runs
[14:55] <Pharaoh_Atem> as will snap-confine
[14:56] <zyga> Pharaoh_Atem: I saw
[14:56] <zyga> Pharaoh_Atem: I need to update the golang something mux package, it's slightly out of date it seems
[14:57] <Pharaoh_Atem> gorilla/mux?
[14:59] <Pharaoh_Atem> zyga: like most golang packages that are docker deps, it's maintained by jchaloup
[14:59] <Pharaoh_Atem> you can ask him to update it and to become a comaintainer
[14:59] <Pharaoh_Atem> it might even be a good idea to just ask to become a comaintainer for all snapd deps
[15:15] <jdstrand> niemeyer: hey, would now be an ok time to discuss bug 1611444? I think it can be covered in a short hangout (probably less than 10 minutes)
[15:15] <mup> Bug #1611444: Cannot share a namespace between apps in a SNAP <Snappy:Confirmed> <https://launchpad.net/bugs/1611444>
[15:16] <jdstrand> niemeyer: if not, I can schedule something for later today
[15:16] <zyga> Pharaoh_Atem: yep, that's my plan
[15:16] <niemeyer> jdstrand: It's lunch time, so probably best to schedule it for the afternoon
[15:16] <jdstrand> ah, sorry, sure thing
[15:27] <popey> https://github.com/PowerShell/PowerShell who's up for snapping that :)
[15:32] <marcoceppi> so, USB inputs and stuff, what's the TL;DR on that? does it work is there a plug for it?
[15:33] <popey> marcoceppi: we discussed this here yesterday. it's not fully designed yet, so no, not implemented AIUI
[15:33] <marcoceppi> ta, must have missed it
[15:33] <mup> Bug #1614587 opened: unable to run snap on ubuntu 14.04 (ZOE error) <Snappy:New> <snapd (Ubuntu):New> <https://launchpad.net/bugs/1614587>
[15:34] <arges> sergiusens: hi. When I type snapcraft. why does it not rebuild sources if any of the source files have been modified?
[15:35] <arges> i've been working around this by snapcraft clean && snapcraft, but seems like it should detect changes in source (timestamps changed for local source, git commits for remote source)
[15:36] <sergiusens> arges because we have not implemented those smarts yet
[15:36] <sergiusens> it is in the queue
[15:36] <sergiusens> but there are just too many things to do
[15:37] <arges> sergiusens: ok that's cool. Yup understand! it was mostly a question if I should file a bug, or if you had already thought about it
[15:37] <sergiusens> arges already in queue, so no need ;-)
[15:37] <arges> awesome
[15:50] <mup> PR snapd#1699 opened: introduce the "lxd" interface <Created by tych0> <https://github.com/snapcore/snapd/pull/1699>
[16:00] <mup> PR snapd#1700 opened: add mir to implicit for running gui snaps on unity8 classic desktop <Created by kgunnfront> <https://github.com/snapcore/snapd/pull/1700>
[16:01] <popey> mhall119: meeting time?
[16:06] <elopio> kyrofa: do we have a desktop client snap for next cloud?
[16:06] <kyrofa> elopio, only the owncloud one right now: https://software.opensuse.org/download/package?project=isv:ownCloud:desktop&package=owncloud-client
[16:33] <sergiusens> kyrofa but you were working on a client, right?
[16:33] <kyrofa> sergiusens, ohh, wow I need to read the complete question
[16:34] <kyrofa> sergiusens, yeah I was working on it, but I put it on hold due to the indicator stuff
[16:37] <mup> PR snapd#1697 opened: allow bind() in the network client interface <Created by tych0> <https://github.com/snapcore/snapd/pull/1697>
[16:38] <mhall119> zyga: if you have a brain-dump for the content-sharing interface you can share with popey and I, we can get started with just that
[16:42] <zyga> mhall119: I'll write my blog post today, just let me get off the call :)
[16:52] <sergiusens> elopio 2.15 is in xenial-proposed; get your chain saw ready ;-)
[16:58] <popey> zyga: thanks
[16:58] <mhall119> thanks zyga
[17:21] <qengho> On all-snaps images, how does that /writable partition work for things in "/etc" ?
[17:36] <mrCyborg> hey! I'm trying to snap a gtk package, but I get the error `Gtk-Message: Failed to load module "overlay-scrollbar"` when trying to run it, to resolve the issue I tried adding `overlay-scrollbar` to `stage-packages`, but that didn't seem to help... any ideas?
[17:42] <qengho> mrCyborg: I do not think that is fatal. Is it working anyway?
[17:46] <mrCyborg> qengho: It is fatal, that wasn't the only package missing, it was just an example
[17:48] <mrCyborg> qengho: It fails to load overlay-scrollbar, gail, atk-bridge, unity-gtk-module, and canberra-gtk-module.
[17:49] <qengho> mrCyborg: what is your "command" in YAML?
[17:51] <mrCyborg> qengho: gist: https://gist.github.com/nloomans/5d87feb430901a0d1130be9d32bffd9f
[17:55] <mup> PR snapcraft#739 closed: Only show chown warnings with --debug <Created by josepht> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/739>
[17:57] <qengho> mrCyborg: Ah, thx. I think you should use the wrapper that sets up the environment for gtk2 apps. In parts, webtorrent-desktop, add  after: [ desktop/gtk2 ]  and change your command to  command: desktop-launcher $SNAP/WebTorrent
[18:03] <mrCyborg> qengho: tnx for the help, but now I get the flowing error: "The specified command 'desktop-launcher' defined in the app 'webtorrent-desktop' does not exist or is not executable"
[18:04] <qengho> Sorry. `desktop-launch`
[18:08] <mvo> ogra_: hey, the fix for the upgrade problem has landed, let me create new images for you so that we can verify it
[18:09] <qengho> Who's in charge of the parts yaml on the web?
[18:15] <mrCyborg> qengho: Thanks a lot, that works now! I really should have asked for help earlier...
[18:25] <qengho> mrCyborg: welcome!
[18:37] <elopio> sergiusens: ack. I'll test after lunch.
[18:37] <mup> PR snapcraft#740 opened: Allow debugging cleanbuild runs <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/740>
[19:05] <ahoneybun> mm
[19:05] <ahoneybun> 'no mobule 'gi'
[19:08] <qengho> There's a lot wrong there.
[19:11] <ahoneybun> XD
[19:28] <om26er> Hi! I am not able to apt-get anything on all-snaps latest in classic mode, it gives me: cat: standard output: Permission denied
[19:33] <om26er> actually sudo classic.create gives me:
[19:33] <om26er> chroot: failed to run command ‘/var/lib/classic/enable.sh’: No such file or directory
[19:34] <om26er> ogra_, ^
[19:38] <qengho> The images are the big bad ignored part of snappy. There's no build system. There's no bug tracker. It's untethered to any kind of quality control.
[19:39] <qengho> We should be saying "We have no images", instead of hoping these ad-hoc ones are good enough.
[20:03] <mup> PR snapd#1681 closed: tests: test `snap run --hook` using in-tree snap-exec <Created by kyrofa> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/1681>
[20:04] <kyrofa> qengho, we aren't hoping that. The all-snap images aren't done yet, these are pre-releases
[20:06] <kyrofa> qengho, also, they are indeed tethered to a QA process, but perhaps that could be more transparent
[20:06] <qengho> kyrofa: I'm not saying they should be good enough for release. I'm saying they're not good enough for testing. I emailed my own "bug report" yesterday, into the void.
[20:07] <kyrofa> Which void?
[20:07] <qengho> I
[20:08] <qengho> I'm not picking on him, but the owner of the personal file I used to flash.
[20:08] <qengho> http://people.canonical.com/~mvo/all-snaps/16/all-snaps-pi2.img.xz
[20:09] <kyrofa> Where was that announced as being available?
[20:10] <qengho> I asked here, "What should I be installing on my rpi3"?
[20:13] <qengho> kyrofa: if you know of daily builds and a bug tracker, I would be happy to know of it.
[20:16] <mup> PR snapcraft#741 opened: Make it easy to setup a pre-commit hook <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/741>
[20:16] <qengho> kyrofa: In any case, I'm not new to this. It's om2`6er of 45 minutes ago who has a new bug to report.
[20:17] <qengho> I don't know where to send himher.
[20:18] <kyrofa> qengho, mvo has made those just for testing purposes. They are unofficial. Until they are, all you can really do is talk to mvo (and maybe ogra_)
[20:31] <mup> PR snapcraft#742 opened: Handle missing source type packages in the parser <Created by josepht> <https://github.com/snapcore/snapcraft/pull/742>
[21:27] <mup> Bug #1614730 opened: dpkg: dependency problems prevent configuration of snapd -  snapd depends on ubuntu-core-launcher (>= 1.0.23) <oil> <Snappy:New> <https://launchpad.net/bugs/1614730>


[12:37] <infinity> Is the kernel planning on liking gcc4 well enough to be stable for 5 years?
[12:37] <infinity> And is it going to do so in the next month?
[12:37] <infinity> If not, I think we're stuck with gcc3.4 :)
[01:40] <zul> everninng
[02:37] <zul__> everybody still on holiday?
[02:37] <fabbione> hey zul
[02:39] <BenC> hey
[02:39] <fabbione> hey Ben
[02:40] <fabbione> BenC: i finally got the git export properly
[02:40] <BenC> fabbione: cool
[02:40] <fabbione> but i can't manage to push it to my server
[02:40] <fabbione> David was talking about gitd or rsync
[02:40] <fabbione> but git push rsync:// farts on me
[02:40] <BenC> why doesn't git push ssh:// work?
[02:41] <fabbione> Cannot push to rsync://
[02:41] <fabbione> there is a specific exception in git-push script
[02:41] <fabbione> no idea why
[02:41] <BenC> what does it say when you do "git push ssh://people.ubuntu.com/..." ?
[02:42] <fabbione> i can try that.. gimme a sec
[02:42] <BenC> make sure you supply ubuntu-2.6.14 after the url, so it pushes the right branch
[02:42] <fabbione> ssh: ssh: Name or service not known
[02:42] <BenC> show me your command line?
[02:43] <BenC> git-send-pack people.ubuntu.com:/home/bcollins/public_html/repos/ubuntu-2.6.git ubuntu-2.6.14
[02:43] <fabbione> AHHH
[02:43] <BenC> give that a try aswell
[02:43] <fabbione> git push ssh://rookery.warthogs.hbd.com/
[02:43] <fabbione> fatal: / doesn't appear to be a git directory
[02:43] <fabbione> Killed by signal 1.
[02:43] <fabbione> fatal: unexpected EOF
[02:43] <BenC> git push ssh://people.ubuntu.com//home/bcollins/public_html/repos/ubuntu-2.6.git ubuntu-2.6.14
[02:44] <BenC> that is the right push line
[02:44] <fabbione> that's if i want to push into your archive... right?
[02:44] <fabbione> what if i want to branch...
[02:44] <fabbione> and expose my archive for you to pull from
[02:44] <BenC> then use your branch name at the end
[02:45] <BenC> git branch fabbione-2.6.14
[02:45] <fabbione> ok..
[02:45] <BenC> git checkout fabbione-2.6.14
[02:45] <BenC> (do work)
[02:45] <BenC> then push
[02:45] <fabbione> so we need to land into the same repo
[02:45] <fabbione> i cannot publish it let say in my home dir on people
[02:45] <BenC> yeah, you can do that aswell
[02:46] <BenC> hold a sec...
[02:46] <fabbione> sure
[02:47] <BenC> git clone -n -l -s /home/bcollins/public_html/repos/ubuntu-2.6.git fabbione-2.6.14
[02:47] <BenC> mv fabbione-2.6.14 fabbione-2.6.14.git
[02:47] <BenC> do that on rookery
[02:47] <BenC> and it will create a git repo for you with shared objects with mine (reduces space usage)
[02:47] <BenC> then you can push your stuff there
[02:48] <BenC> mv fabbione-2.6.14/.git fabbione-2.6.14.git
[02:48] <BenC> use that line second
[02:51] <fabbione> ok it seems to work
[02:51] <fabbione> i don't need a real branch
[02:51] <fabbione> just the option to work on the same tree
[02:51] <fabbione> but push to you async for crack
[02:52] <fabbione> error: remote 'refs/heads/ubuntu-2.6.14' object 180a764cccdd44c16050c25716a9f814c1955a47 does not exist on local
[02:52] <fabbione> crap
[02:53] <fabbione> git push ssh://rookery.warthogs.hbd.com/home/fabbione/public_html/archives/fabbione-2.6.14.git ubuntu-2.6.14
[02:53] <fabbione> so i didn't change branch.. just pushing like you said
[02:55] <BenC> hold a sec
[02:55] <fabbione> sure
[02:55] <BenC> ah
[02:55] <BenC> do a pull
[02:56] <fabbione> done i am already in sync
[02:56] <BenC> still getting the message?
[02:56] <fabbione> trying again
[02:56] <fabbione> take into account that i did this in my tree
[02:56] <BenC> it's saying that a revision on the remote doesn't exist in your local copy
[02:56] <fabbione> pull from you
[02:57] <fabbione> ok.. let me explain what i did first
[02:57] <fabbione> pull from you
[02:57] <fabbione> pull from linus
[02:57] <BenC> where did you clone from?
[02:57] <fabbione> pull from davem
[02:57] <fabbione> you
[02:57] <fabbione> i did clone from you
[02:57] <BenC> why the pull from linus and davem?
[02:58] <fabbione> BenC: for fun? i need to stretch my wings on git
[02:58] <fabbione> and then i want to publish this tree somewhere else other than your
[02:58] <fabbione> since i don't want to mess it up
[02:59] <BenC> ok, you're going to need to take your local .git/ directory and copy it to rookery
[02:59] <BenC> make that your initial repo and push to it
[02:59] <fabbione> oook..
[02:59] <fabbione> that's crack :)
[03:00] <BenC> it's weird that your missing an object that the remote has :)
[03:01] <fabbione> $ cd linux-2.6
[03:01] <fabbione> $ rsync -a --verbose --stats --progress \
[03:01] <fabbione>    rsync://rsync.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git/ \
[03:01] <fabbione>    .git/
[03:01] <fabbione> this is according to the guide.. could it make sense that we need to do it from you too?
[03:02] <fabbione> actually.. no i want to get this right in the right way
[03:02] <fabbione> not with hacks
[03:02] <BenC> yeah, that guide is for ancient git bins
[03:03] <BenC> me personally, I did "git clone ssh://people.ubuntu.com/home/bcollins/public_html/repos/ubuntu-2.6.14"
[03:03] <fabbione> git clone ssh://rookery.warthogs.hbd.com/home/bcollins/public_html/repos/ubuntu-2.6.git ubuntu-2.6.14
[03:04] <fabbione> starting from here now
[03:04] <BenC> then I did some work, and periodically I do "git push"
[03:04] <fabbione> yes, but you push in your own archive :)
[03:04] <fabbione> that's already there
[03:04] <BenC> actually, what you want first is to do the local clone on rookery
[03:04] <BenC> then on your desktop do the clone from your personal git repo
[03:05] <fabbione> right
[03:05] <fabbione> BenC: we also need to think one second how do we want to keep pathes in git
[03:05] <fabbione> i don't think .dpatch is efficent anymore
[03:05] <fabbione> not if we want to push changes upstream
[03:06] <BenC> as of this moment, everything is going to be in the repo
[03:06] <BenC> no patches, directly applied
[03:06] <fabbione> BenC: exactly what i was thinking...
[03:06] <BenC> so far I have merged almost all the external drivers
[03:06] <BenC> read "git log" and you'll see the format for the log messages
[03:06] <fabbione> in the newest versions? or just from .12?
[03:06] <BenC> newest versions
[03:06] <fabbione> cool
[03:07] <fabbione> i need to push you the new redhat and ocfs2 crack
[03:07] <BenC> 2 or 3 of them have been merged in 2.6.14-rc, so they just got left alone
[03:07] <fabbione> BenC: yes.. some of them were there already in .13 like sc
[03:07] <fabbione> and idiotify
[03:07] <BenC> where is the latest cluster patch? I couldn't find anything as new as what was listed in external-drivers?
[03:08] <fabbione> BenC: sources.redhat.com
[03:08] <doko> fabbione: found the biarch sparc thing
[03:08] <fabbione> but let me deal with it
[03:08] <BenC> doko: sweet
[03:08] <fabbione> BenC: because their upstream is really really messy
[03:08] <BenC> fabbione: sure
[03:08] <fabbione> doko: cool, send it here
[03:08] <fabbione> BenC: they have like a few branches and they manage to get confused by themselves
[03:08] <BenC> doko: is gcc4.1 expected to compile the kernel?
[03:09] <fabbione> BenC: like fixes that goes in STABLE branch are not propagated and viceversa
[03:09] <BenC> fabbione: hehe
[03:09] <infinity> BenC : Probably, but are we willing to risk a "supported for 5 years on servers" release on a compiler that may produce panicking kernels?
[03:09] <fabbione> BenC: it took me a month or 2 of fights with them to get that right
[03:10] <fabbione> BenC: and they still manage to miss the STABLE branch
[03:10] <infinity> BenC : I'd push for 3.4 in dapper, and 4.x as the kernel compiler in dapper+1, even if it's not ready (cause dapper+1 is good place to be testing shit that might break hideously)
[03:10] <BenC> infinity: servers are going to be 2.6.12 based anyway
[03:10] <fabbione> BenC: no no no
[03:10] <infinity> BenC : Ugh, we're not going with jdub's crackful suggestion on that, are we?
[03:10] <fabbione> who said .12?
[03:10] <infinity> That's nuts.
[03:11] <BenC> where is this all being discussed?
[03:11] <fabbione> BenC: i just had a big fight with jdub about that crack
[03:11] <fabbione> ubuntu-devel mailing list
[03:11] <infinity> Maintaining two kernel branches is confusing to users, and a pain for us.
[03:11] <fabbione> infinity: that's my Copyright :P
[03:11] <BenC> only thing I've read about it so far is what mark emailed to ask me
[03:11] <infinity> Anyhow, jdub's just spouting opinions, not policy, we'll all get to yell about this at UBZ in person.
[03:11] <BenC> I'm not sure supporting a kernel for 5 years is sane in any case
[03:12] <fabbione> eheh exactly
[03:12] <BenC> 5 years ago, 2.2.7 was released
[03:12] <BenC> try supporting that now
[03:12] <infinity> Hey, 2.2.7 was solid, dude.
[03:12] <infinity> :)
[03:12] <fabbione> still better than 2.2.11
[03:12] <BenC> yeah, on your grandma's hardware :)
[03:12] <fabbione> after that the 2.2 serie was crack
[03:13] <infinity> I suspect we may need to come up with a point-release plan to update stuff like kernels (for server/desktop) and X drivers (for desktop) occasionally, while not compromising overall stability.
[03:13] <infinity> Thankfully, modular X is making the latter job easier.
[03:13] <infinity> Hopefully rolling kernel driver updating shouldn't be too much hell either.
[03:14] <infinity> RHEL manages to get away with point releases for hardware updates and such, so I'm sure we can manage.
[03:15] <fabbione> infinity: well we get back to the same point...
[03:15] <BenC> I'm hoping that a revamped development model for our kernel will make it easier for us to move from one version to the next
[03:15] <fabbione> developing release foo + preparing service pack X for bar
[03:15] <fabbione> we don't have the resources :)
[03:16] <infinity> Well, we shouldn't be changing much of anything in dapper except for installability support.
[03:16] <infinity> IMO.
[03:16] <infinity> So, hardware support, and nothing else (other than the usual security and critical -updates)
[03:16] <infinity> So, assuming we can get our act in gear enough for that, we're okay.
[03:16] <BenC> personally, I think the kernel should have two branches, one that is targeted for next release, and if there needs to be, a second that is following the latest upstream release
[03:17] <fabbione> BenC: we did try that in hoary
[03:17] <BenC> e.g., when 2.6.14 becomes final, we keep that branch for dapper, and immediately start on 2.6.15-rc1 just to follow the code
[03:17] <fabbione> it was horribly confusing
[03:17] <BenC> but 2.6.15-rc branch doesn't have to be uploaded
[03:17] <infinity> And it can be parallelized a bit.  Say, a month after dapper+1 releases, we decide dapper+1's kernel looks pretty stable and well-tested, we push it back into Dapper-revision1
[03:17] <fabbione> BenC: that will help to release .15
[03:17] <BenC> just kept up-to-date
[03:18] <BenC> just thinking that moving to the next kernel will be a lot easier if we don't wait so long for the code to diverge from our working setup
[03:19] <BenC> we're at 2.6.12, and starting this whole 2.6.14 thing is a real pain (but a good experience, since I have an excuse to scrap as much as I want :)
[03:20] <fabbione> BenC: we did the "following code very close game"  when we did open hoary
[03:20] <fabbione> with a 2.6.12-rc2 i think
[03:20] <fabbione> and started with that
[03:20] <BenC> so breezy's kernel was being worked on during hoary?
[03:20] <fabbione> the main issue is that when we approach release, there is really not so much time to play around in syncing
[03:20] <fabbione> BenC: immediatly after hoary was released
[03:20] <BenC> ah
[03:21] <BenC> well, for 2.6.15, it will be mostly just doing "git pull"
[03:22] <BenC> you can even be in the 2.6.15 branch, and do a pull from the 2.6.14 branch to make sure we have all the little security fixes merged
[03:23] <BenC> it's not that I expect that the branch will build, just keeping the code in sync so it isn't so hard to merge stuff later (easier to merge from day one, than jump from 2.6.14 -> 2.6.16-rc3)
[03:23] <fabbione> yup
[03:24] <makx> fabbione: will you use the debian unified packaging?
[03:24] <makx> i mean you were the first to introduce that model..
[03:24] <fabbione> makx: probably..
[03:25] <fabbione> we are changing sort of RCS and way of handling patches and so on
[03:25] <fabbione> makx: so perhaps yes, perhaps no
[03:25] <makx> i read the git part. :)
[03:25] <fabbione> it depends how it fits :)
[03:26] <BenC> what is debian unified packaging?
[03:26] <makx> well before you had the separeted source and images debs xu build stuff
[03:26] <infinity> Building all the arch-specific kernels from one source package, I assume.
[03:26] <infinity> And scrapping that would be dumb.
[03:27] <fabbione> BenC: the old DEbian system was -> upload source -> wait -> upload pkg that b-D on source to create -image- -> wait -> upload d-i stuff to update .udebs
[03:27] <fabbione> BenC: we do all from the same pkgs
[03:27] <makx> it works quite good for anyone beside the mips/mipsel maintainer.
[03:27] <fabbione> and that's what debian did adopt except for the .udeb side
[03:27] <BenC> ah
[03:28] <BenC> yeah, I don't think we'll change the way the build works :)
[03:28] <fabbione> BenC: we will stick to that model of building everything, but we might want to look at the Debian way of building
[03:28] <fabbione> last time i checked it was more polished than ours
[03:29] <fabbione> dunno right now, given the amount of people hacking in it
[03:29] <infinity> That's not surprising.  Debian's "arguing about stuff for 12 months before, during, and after implementation" method may be slow, but it produces polish eventually.
[03:29] <makx> fabbione: do you build uml?
[03:29] <fabbione> makx: no
[03:29] <jbailey> What's the value in uploading a binary "source" deb?
[03:30] <makx> isn't that a dpkg limitation.
[03:30] <infinity> Has nothing to do with dpkg.
[03:30] <BenC> jbailey: back when ports were way out of sync, and had wildly different "upstream" kernel versions, it was the only way to do things
[03:30] <jbailey> BenC: Ah, okay.
[03:30] <jbailey> I had always assumed it was something to do with making custom kernels easier.
[03:30] <infinity> It has to do with people wanting our source to build custom kernels, without having to "apt-get source" and figure out how to build with the maintainer scripts.
[03:30] <infinity> Which is scary and weird for most people.
[03:31] <BenC> that's true too
[03:31] <jbailey> I'd love to see all hacks that make custom kernels easier go away.
[03:31] <jbailey> But that's my hatred of custom kernels and the bugs they cause. =)
[03:32] <infinity> I run custom kernels built from upstream source.

[03:32] <infinity> But I can see why people may prefer to use our source.
[03:32] <fabbione> infinity: that's becuse you are australian
[03:32] <infinity> (close tracking of security issues, for instance)
[03:32] <infinity> fabbione : I'm Canadian, dude.
[03:32] <fabbione> EVEN WORST
[03:32] <fabbione> and you live in .au
[03:32] <fabbione> tsk tsk :P
[03:32] <jbailey> Right, but if people do their own kernels, we can make no promises about things running.
[03:32] <infinity> My granmother was Sicilian, does that help?
[03:32] <fabbione> infinity: no
[03:33] <fabbione> ;)
[03:33] <jbailey> Our bits are all tested as one piece together.
[03:33] <infinity> jbailey : Yes, and?
[03:33] <infinity> jbailey : You can't stop them from making custom kernels, so making it pointlessly hard is silly.
[03:33] <makx> we had scary questions about allowing the user to nitpick the applied patches.
[03:34] <fabbione> that won't happen with git :)
[03:34] <jbailey> infinity: I think it actually makes it harder for hacking on our kernels to do it this way.  For any other package, apt-get source, hack, debuild, is enough.
[03:34] <fabbione> one tree with all patches applied :)
[03:34] <infinity> jbailey : apt-get source, hack, debuild works for the kernel.
[03:34] <makx> btw a scary tree yours.   And is nonintuitive for people to make one custom image out of.
[03:36] <makx> fabbione: nice than you wont need the patch apply business of the current targets.
[03:37] <makx> it should cope with empy debian-patches dirs.
[03:38] <jbailey> If someone can't figure out which .deb to install, they're probably not clueful enough about their system to spend time building their own kernel.
[03:38] <infinity> It's not about which deb.
[03:38] <infinity> It's about the build taking 8 hours.
[03:38] <jbailey> Although a hack to debi to only install packages that are already installed might be nice. =)
[03:38] <fabbione> i am off
[03:38] <fabbione> later guys
[03:39] <fabbione> BenC: i will come back as soon as the git clone is done
[03:39] <fabbione> connection to the DC sucks
[03:39] <infinity> And I still prefer "make menuconfig && fiddle around && make-kpkg foo" to mucking around in the linux-source-2.6.12 source package for the sake of one image build.
[03:40] <infinity> We should fix our copy of make-kpkg to use '--stem linux' as the default, though, instead of '--stem kernel'
[03:40] <infinity> But, y'know.  That's cosmetic.
[03:41] <infinity> I'm all about discouraging users from building custom kernels if they don't have to (I'm running the breezy kernel on my laptop, and the freedom to not care is a bit nice), but poeple have reasons to do so at times.  Such is life.
[03:42] <infinity> Discouraging people from doing out-of-band kernel builds is good thing (ie: make bzImage && make install), but we can't PREVENT that, only educate people about the joys of make-kpkg.
[03:56] <jbailey> Mmm.
[03:57] <jbailey> I guess I'd like to eventually see us move the kernel to being part of ubuntu-standard
[03:57] <jbailey> That way if we add an inotify patch or whatnot, there's always that promise that these patches are there on a running system.
[03:57] <jbailey> And to be able to commit to that sort of tight integration.
[03:59] <infinity> Still doesn't stop me from booting another kenrel if I so choose.
[03:59] <infinity> The insaller does install the linux-$(arch) metapackage that pulls in automatic upgrades, we can't do much better than that.
[04:31] <BenC> we could force a signature in the kernel that grub verifies :)
[04:31] <BenC> then people would have to replace grub in order to boot a custom kernel
[04:32] <BenC> for "supported" systems, I almost think it would be vital to have such a feature
[04:32] <BenC> especially something in dmesg or ksymoops output (like tainted does now for unsupported modules)
[04:48] <infinity> And now I'm rebuilding the kernel and the bootloader, pushing me from one unsupported package to two.  Yay.
[04:49] <BenC> the grub thing isn't so much to keep them from booting a custom kernel, just to make it easier for us to know about it
[04:51] <BenC> get grub to spit out a message that says "YOU ARE BOOTING AN UNSUPPORTED KERNEL. YOU DO SO AT YOUR OWN RISK"
[04:51] <infinity>  /proc/version is all you need to know it's a custom kernel.
[04:51] <infinity> Not sure how grub will help you, since you're not watching them boot.
[04:51] <BenC> not if they use our source and add stuff to it
[04:51] <infinity> (Also, every system I build custom kernels on doesn't have a head, so I'd never notice the bootloader anyway) :)
[04:51] <infinity> I run supported kernels on desktops.
[04:52] <infinity> BenC : Erm, even if they use our sources, /proc/version will tell you it's custom.
[04:52] <infinity> it won't be tagged as being built on our buildds, for one.
[04:52] <infinity> And the build date won't be one of ourss, etc.
[04:53] <BenC> that's true
[04:53] <Yagisan> infinity: can't I just manually patch that in :)
[04:54] <infinity> If you manually patch your kernel to look just like one of ours, you're probably not going to be blaming us if it doesn't work either.
[04:54] <BenC> would be nice if we could have the buildd's so that when it built an ubuntu kernel, it would force the build date and builder to that of the changelog entry for the version
[04:54] <infinity> Seriously.  These sorts of countermeasures are to prevent idiots from begging for support on unsupported configs, not to prevent EVERYONE from using their computers effectively.
[04:55] <infinity> BenC : That would have to be done in debian/rules, and then it would also apply for people rebulding from apt-get source.
[04:55] <BenC> wouldn't have to be
[04:56] <infinity> Well, we do already do DC-specific things by way of really broken hacks (like checking that /CurrentlyBuilding exists), but we shouldn't.
[04:56] <infinity> CurrentlyBuilding may not be around forever, as it is also a hideous hack.
[04:56] <jbailey> Especially since you know you'll see in the forums about 2 days after "I don't know why, but if I mkdir /CurrentlyBuilding it works MUCH BETTER"
[04:57] <BenC> lol
[04:57] <infinity> Every once in a while, I consider a DDoS on the forums.
[04:57] <infinity> But then I think better of it.
[04:57] <infinity> What with the whole "I could get fired" thing and all.
[04:58] <jbailey> Well.  It would be your fault for using all of the DC machines to do the DDoS. =)
[04:58] <infinity> *cough*
[04:58] <infinity> I wouldn't JUST use DC machines.  I'd jeopardize my Debian account by using every Debian host I have access to as well, sheesh.
[04:58] <infinity> THINK, MAN, THINK.
[04:58] <Yagisan> What's the most common reason that people build their own kernels ? I build mine for sec patches that will never go mainstream
[04:59] <jbailey> Yagisan: My opinion?  I think themost common reason is that people assume that a new kernel will fix all of their troules.
[04:59] <infinity> I build for stability on server systems.
[04:59] <jbailey> So they grab a new one and just build it.
[04:59] <jbailey> Basically insufficient shinyness.
[04:59] <infinity> On the desktop, I only build new kernels when playing with new features (testing new DRI, etc)
[05:00] <infinity> So, yeah, on the desktop it's all about either development work or bling.
[05:00] <infinity> On the server side, I feel I have real justification to build new kernels.
[05:01] <Yagisan> I had a proposal for universe kernels based on the main kernel + sec patches up for discussion for MOTU
[05:01] <infinity> Like PaX and grsec and such?
[05:01] <Yagisan> exactly
[05:02] <jbailey> Is it possible to work those patches in a way to allow them to be runtime selectable?
[05:02] <infinity> If you could maintain the forked flavours in complete lockstep with the main sources, including building lrm packages for multiverse, I'd not have too many issues with it.
[05:02] <infinity> But I'd want to see a commitment to maintaining lockstep source reuse.
[05:02] <Yagisan> jbailey: for many of them - no
[05:02] <jbailey> Ah, too bad.
[05:02] <Yagisan> infinity: I'm only interested in doing it - if the patches apply to mains kernel
[05:03] <infinity> Yeh, they'd have to apply cleanly, obviously.  But more than that, MOTU would have to commit to doing releases to -security each time we do a release of the main kernel to -security, either.
[05:03] <Yagisan> infinity - for myself I need pax, and possibly rsbac (to provide an alternative for selinux)
[05:03] <makx> Yagisan: irc grsec doesn't cope with the 2.6 release speed.
[05:03] <infinity> In practice, people are horrible at separating supported from unsupported, and the kernel is not a good place to test that.
[05:04] <jbailey> Reminds me that ajmitch is supposed to send me selinux bits for initramfs-tools this week
[05:04] <Yagisan> makx: I know, but they do have cvs releases
[05:05] <makx> Yagisan: and that's against latest stable?
[05:05] <Yagisan> makx: they have a cvs against .12
[05:05] <makx> bleeh that's old.
[05:05] <Yagisan> makx: but I don't use it - I use pax
[05:06] <Yagisan> makx: well - I said I don't use it - I see a pax against .14rc
[05:06] <makx> Yagisan: i thougt the main dev of pax quited..
[05:06] <makx> # blah to many typos sorry.
[05:06] <Yagisan> makx: nope - he discovered he is human
[05:08] <Yagisan> infinity: when the first dapper kernels appear in the archive - I'll see if I can do up a proof of concept
[05:08] <Yagisan> that can pull it in, and create hardened kernels - so only a kernel-patch-foo package is needed in universe
[05:19] <johnm> Yagisan: makx: I just pushed out a release (not ubuntu related) which is grsec against <IP_ADDRESS>, the only reason it skipped .12 was because of a massive internals rewrite. mostly related to rbac.
[05:24] <makx> johnm: not that i would thouch that piece.
[05:27] <Yagisan> johnm: I'm interested, but unless I can patch it against the main kernel, and pass the motu revu - I can't submit it
[05:40] <johnm> Yagisan: that shouldn't be any problem at all imo.
[06:48] <BenC> fabbione:?
[06:53] <zul_> gday
[06:56] <BenC> hey
[06:56] <hkais> hello
[06:58] <hkais> anyone here who works with xen in ubuntu/debian?
[06:58] <hkais> I'm looking to support if necessary, but I do not know how and what to do for the XEN
[07:07] <hkais> hmm really nobody here?
[07:09] <BenC> probably just no one could answer you :)
[07:18] <zul_> BenC: i finally have git going
[07:19] <zul_> and i have made a change last night yay...but how do we push stuff to you?
[07:22] <BenC> are you able to put a git repo where I can pull from it?
[07:22] <BenC> if not, you'll have to send me git pushes via email
[07:36] <zul_> ok..
[07:36] <zul_> so i can mailbomb you ;)
[07:51] <BenC> git-mailsplit will help a lot :)
[07:52] <zul_> heh...actually i can place the patches on my homepage if you want and you can get them from there
[08:09] <BenC> fabbione: ping
[08:16] <BenC> zul_: emailing me a legit git push object would be best
[08:16] <BenC> that way when you merge it and you pull, it will reflect properly
[08:16] <BenC> when I merge it, and you pull, that is
[08:33] <zul_> ok...not a problem
[08:49] <spiekey> hiho
[08:50] <hkais> hi
[08:53] <hkais> next try...
[08:53] <hkais> I am searching for someone who is currently working with/on XEN in combination with ubuntu or debian unstable, anyone here?
[08:53] <hkais> I want to support if necessary for a port XEN3
[08:58] <hkais> hmm okay i will try it in the debian kernel channel
[09:14] <fabbione> BenC: pong?
[09:15] <fabbione> Unpacking 101726 objects
[09:15] <fabbione> fatal: unable to read e9066604fd66fe0be7600f74d295b95e8fac474c
[09:15] <fabbione> Killed by signal 1.) done
[09:15] <fabbione> fatal: early EOF726) done
[09:15] <fabbione> fatal: git-unpack-objects died with error code 128
[09:15] <fabbione> BenC: that's the result of several hours of pulling :/
[09:21] <fabbione> BenC: that's weird.. doing a fresh pull now
[09:22] <fabbione> there are like 4000 objs less?
[11:33] <lamont__> why doesn't the breezy kernel find my sound card??? huh???
[11:33] <lamont__> ew
[11:33] <lamont__> Neomagic Corporation NM2200
[11:37] <crimsun> well, there's snd-nm256, but I don't think that's yours


[14:51] <janskyview> hi everyone, my machine doesn't  have a serial port and i'm trying to write a java application that reads and writes to a serial port, do you know any emulators please?
[15:31] <mythos> janskyview_, java?
[15:32] <mythos> does java even support rs232?
[15:33] <mythos> oh, it does
[15:35] <mythos> janskyview_, you need a device on the rs232-port, so a virtual one won't help you
[15:43] <janskyview_> mythos: yeah
[15:44] <janskyview_> mythos: do you think socat could overcome that problem?
[15:46] <mythos> ttySx is character-device, so i don't think, this will work
[15:47] <mythos> so, you want to use a com-port on another machine?
[15:47] <mythos> *on a
[15:50] <janskyview_> mythos: no, I have to write a java app that reads/writes to a serial port, but the pc where i am working at does not have any serial port so I thought I could try to emulate it with socat
[15:52] <mythos> i think, the easiest way is to buy a usb2rs232-adapter
[15:52] <mythos> else you are going to write a rs232-dummy and a client for that dummy


[07:18] <tsdgeos> mzanetti: hi ho
[08:20] <mzanetti> tsdgeos, hey
[08:21] <tsdgeos> mzanetti: so that new silo landed, now the vivid only silos don't build anymore
[08:21] <mzanetti> tsdgeos, why do we have vivid-only silos?
[08:22] <tsdgeos> i do not know :D
[08:22] <tsdgeos> because it's what we did until it stopped working ?
[08:22] <tsdgeos> :D
[08:23] <tsdgeos> what are we supposed to have now?
[08:23] <mzanetti> ah. you mean the old ones, like in-card music
[08:23] <tsdgeos> yes
[08:23] <mzanetti> we're back to dual landing
[08:23] <tsdgeos> off the overlay branch?
[08:23] <mzanetti> yes
[08:24] <tsdgeos> funnies
[08:24] <mzanetti> doesn't really matter as trunk & overlay are the same now
[08:24] <mzanetti> except the changelog
[08:24] <tsdgeos> no, they're not the same at all
[08:24] <mzanetti> they should be :D
[08:25] <tsdgeos> hmmm, really?
[08:25]  * tsdgeos checks
[08:25] <mzanetti> could be that we need to do a manual sync
[08:26] <tsdgeos> mzanetti: http://paste.ubuntu.com/12416173/
[08:27] <mzanetti> yes that last landing needs to be pushed to trunk
[08:30] <tsdgeos> ok
[08:33] <pstolowski> mzanetti, hey, some of the projects we have in silo 4 cannot be dual-landed, i need to land them separately in V and W
[08:33] <mzanetti> and there we go again
[08:34] <mzanetti> :D
[08:34] <pstolowski> mzanetti, e.g. mediascanner2
[08:34] <mzanetti> so we need to split the silo I guess
[08:34] <pstolowski> mzanetti, yes
[08:34] <mzanetti> and land mediascanner before this one
[08:34] <mzanetti> to both
[08:35] <pstolowski> mzanetti, also, Saviq had a branch of unity-api which merges V+W back into single tree, but i cannot find it..
[08:35] <mzanetti> i landed
[08:35] <mzanetti> it
[08:35] <greyback> pstolowski: why can't you dual land?
[08:35] <pstolowski> greyback, symbols
[08:38] <pstolowski> mzanetti, ah, it landed in trunk15.04 branch, ok
[08:39] <mzanetti> tsdgeos, ok. trunk and overlay are the same now. for now we still oser overlay tho, because that's where CI we want runs on
[08:39] <mzanetti> s/oser/user/
[08:39] <mzanetti> gees
[08:39] <mzanetti> use
[08:39] <mzanetti> :D
[08:40] <tsdgeos> makes sense
[08:40]  * mzanetti gets some coffee
[08:42] <greyback> pstolowski: is it the package name that is different between the v+o & w, or the actual symbols themselves are different (because gcc4.9/5)?
[08:48] <pstolowski> greyback, symbols are different
[08:48] <greyback> pstolowski: yeah. Annoying
[08:51] <ltinkl> tsdgeos, mzanetti: silo 33 is vivid only, and we managed to get it build yesterday, after much changelog+version torturing :)
[08:51] <mzanetti> :D
[08:51] <mzanetti> well, should be dual landing now
[08:51] <ltinkl> I know
[08:51] <ltinkl> design desperately wanted it
[09:53] <greyback> tsdgeos: https://bugs.launchpad.net/ubuntu/+source/ubuntu-app-launch/+bug/1495871/comments/6
[09:53] <tsdgeos> yes
[09:53] <tsdgeos> you have the same thing i have :)
[09:53] <greyback> great :D
[09:54] <greyback> my glib-fu ain't the best, not seeing any obvious leak anywy
[09:56] <greyback> tsdgeos: http://pastebin.ubuntu.com/12416538/ <- maybe  "creationcontext != NULL" ?
[09:57] <greyback> hmm no
[09:57] <tsdgeos> nah
[09:59]  * guest42315 aw-food
[09:59] <tsdgeos> or maybe
[09:59] <tsdgeos> does g_dbus_connection_close_sync(cgmanager, NULL, &error); need to be moved up that if?
[10:00]  * tsdgeos gives it a quick try
[11:22] <tsdgeos> dednick: what do you mean in your last comment to https://code.launchpad.net/~nick-dedekind/unity8/lp1378821.time-translation/+merge/265006 ?
[11:24] <dednick> tsdgeos: if we have a absolute time. ie "7th September 2015" and we change the system timezone, it will not update.
[11:24] <tsdgeos> tedg: am i supposed to be able to dpkg-buildpackage ubuntu-app-launch in the desktop? tests don't seem to pass
[11:25] <dednick> but i dont think it'll actually be used. i was thinking about ltinkl using it, but he was just looking for a place to put a method.
[11:25] <tsdgeos> dednick: so you're saying that we can't remove it?
[11:25] <tsdgeos> or?
[11:25] <dednick> for formatting time with a specified timezone
[11:25] <tsdgeos> food! bbl
[11:25] <dednick> tsdgeos: well, i think we'll need it at some point, but not right now. since we only use relative times.
[11:26] <dednick> can bring it back in uitk if we ever need it.
[11:26] <dednick> using the new stuff i put in there.
[12:26] <tsdgeos> dednick: makes sense, anyhow, retarget to the overlay branch?
[13:11] <dednick> tsdgeos: should not be going into trunk as well?
[13:12] <tsdgeos> dednick: we target overlay that is what we care and then do a "sync push" to trunk
[13:12] <dednick> tsdgeos: ok
[13:12] <tsdgeos> or that's what i understood is our current strategy
[13:12] <tsdgeos> mzanetti: ↑↑↑↑
[13:13] <mzanetti> yes... for now
[13:13] <mzanetti> the plan is is to move back to trunk. but we don't have a vivid ci running on that yet
[13:13] <mzanetti> only wily which is secondary choice atm...
[13:14] <mzanetti> but we're talking to CI to run both, wily and vivid in one go on trunk
[13:21] <tedg> tsdgeos: I would think so. Usually I do "bzr bd" but I think both should work.
[13:22] <tsdgeos> tedg: on vivid? could you try?
[13:22] <tedg> tsdgeos: Sure, building now.
[13:23] <tsdgeos> tedg: and more importantly have a look at the fd leaking bug
[13:23] <tsdgeos> https://bugs.launchpad.net/ubuntu/+source/ubuntu-app-launch/+bug/1495871/
[13:23] <tsdgeos> both gerry and me seem to have reached the conclusion something happens in ubuntu-app-launch that causes it
[13:24] <tedg> tsdgeos: Heh, you both are biased ;-)
[13:24] <tsdgeos> tedg: but we're also both right ;)
[13:24] <tedg> tsdgeos: It built for me.
[13:24] <tsdgeos> tedg: vivd? wily?
[13:24] <tedg> tsdgeos: vivid
[13:24]  * tsdgeos scratches head
[13:25] <tsdgeos> let me try bzr bd
[13:32] <tsdgeos> tedg: so bzr bd works and dpkg-buildpage no :S
[13:33] <tedg> Huh, I wonder why that is.
[13:34] <tedg> Is it the Upstart job tests that fail?
[13:34] <tsdgeos> dednick: qml/Panel/Indicators/MessageMenuItemFactory.qml conflict
[13:34] <tsdgeos> tedg: http://paste.ubuntu.com/12417570/
[13:34] <dednick> tsdgeos: ya, fixing it now.
[13:35] <tsdgeos> tedg: anyway, not jokin on the ubuntu-app-launch leaking the fds, there's a eventfd() call leaking and ubuntu-app-launch is responsible for the only 3 calls to eventfd() (via glib) when launching an app
[13:35] <tedg> tsdgeos: Hmm, yeah. It is testing the Upstart jobs.
[13:36] <tedg> tsdgeos: K
[13:48] <tedg> tsdgeos: gerry: Do you guys have a system set up where you can easily test it?
[13:48] <tsdgeos> tedg: yes
[13:48] <tsdgeos> the phone :D
[13:48] <tedg> I think this is likely the fix: lp:~ted/ubuntu-app-launch/lp1495871-unref-context
[13:49] <tedg> Sure, but I don't have one with a current image and writeable and all that.
[13:50] <tsdgeos> ah, would have never ever realized that what's needed
[13:50] <tsdgeos> the g*refing is too hard :D
[13:50]  * tsdgeos tries
[13:50] <tedg> Heh, yeah. It can be trickey.
[13:51] <davmor2> tedg: https://www.youtube.com/watch?v=l-O5IHVhWj0
[13:52] <tedg> tsdgeos: I'm not 100%, but I think that should be it. Not sure how I can count FDs in a unit test.
[13:52] <tedg> Does valgrind do that?
[13:52] <tsdgeos> don't know
[13:53] <tsdgeos> i straced and counted the eventfd() + close
[13:53] <tsdgeos> but of course that's very manual
[13:54] <tsdgeos> tedg: valgrind can
[13:54] <tsdgeos>  –track-fds=yes
[13:54] <tsdgeos> --
[13:56] <tedg> tsdgeos: Don't think that fixed it.
[13:56] <tedg> tsdgeos: Valgrind has some errors for it.
[13:57] <larsu> tedg: g_autoptr() !
[13:58] <tsdgeos> tedg: ok, so no need for me to try for now? or still want me to try?
[14:00] <tedg> tsdgeos: Don't try right now, seems dbus-test-runner is causing a lot of noise here :-(
[14:01] <tedg> larsu: More complex here as we're tracking out of the stack.
[14:02] <larsu> just a random drive by comment :)
[14:02] <tsdgeos> ok
[14:06] <seb128> hum
[14:07] <seb128> my wily laptop test machine fails to start applications under unity8
[14:07] <seb128> it was working 10 days ago
[14:07] <seb128> just dist upgraded
[14:07] <seb128> is there a known issue?
[14:16] <seb128> ChrisTownsend, ^ do you know?
[14:18] <ChrisTownsend> seb128: It was working yesterday, but I haven't tried today.  I'll try it right now.
[14:18] <seb128> k, I upgraded yesterday and again today, so likely something local
[14:18] <seb128> though my dash only list webbrowser and settings, I might want to try to install other apps
[14:21] <ChrisTownsend> seb128: It's working fine for me.  Anything in unity8.log?
[14:24] <seb128> ChrisTownsend, http://paste.ubuntu.com/12417795/
[14:24] <seb128> "ApplicationManager::onProcessStopped reports stop of appId= "ubuntu-system-settings" which AppMan is not managing, ignoring the event"
[14:24] <seb128> unsure if that's the issue
[14:25] <ChrisTownsend> seb128: How about the application log?
[14:25] <larsu> AppMan sounds like a super hero
[14:25] <seb128> cgmanager's job is failing to start
[14:25]  * larsu should stop spamming this channel with useless comments
[14:26] <ChrisTownsend> larsu: Humor is always appreciated:)
[14:26] <seb128> failing to delete staled socket
[14:27] <ChrisTownsend> seb128: Hmm, weird.  Sounds like a bug.
[14:27] <tedg> tsdgeos: Okay, I have a good trace now. I can confirm that didn't fix it.
[14:28] <tedg> Not the results I wanted to report, but eh, focusing :-)
[14:29] <tsdgeos> tedg: :)
[14:41] <seb128> ChrisTownsend, works after a reboot, something was wrong with the cgmanager, unsure what ... thanks anyway for looking!
[14:41] <ChrisTownsend> seb128: Ok, sure thing!
[20:13] <slangasek> mzanetti: so bug #1278780 is assigned to qtmir now; did you see my question about needing changes up and down the stack, to avoid libraries installing signal handlers?
[20:32] <mzanetti> slangasek, ok, so iiuc what we want is to intercept SIGSEGV in apps, release the connection to mir and then raise the signal again to get apparmor etc going, correct?
[20:41] <slangasek> mzanetti: no, this isn't about sigsegv handling in apps; I'm assuming that an app which is hung because it's stuck in the kernel crash handler is not going to lock up the ui
[20:41] <slangasek> mzanetti: this is about sigsegv handling in the compositor itself
[20:44] <mzanetti> slangasek, ah ok. so for when the shell crashes
[20:45] <mzanetti> so atm mir is handling some signals
[20:45] <mzanetti> also qtmir IIRC
[20:45] <mzanetti> anyhow, will discuss what the proper thing to do is.
[20:47] <slangasek> mzanetti: am I correct in supposing that a lot of the memory mir has mapped consists of video buffers?
[20:47] <greyback> slangasek: darn, I misunderstood you too
[20:48] <slangasek> maybe it would be helpful to free up video buffers from a sigsegv handler for apps also, but that's not the case that's of concern
[20:49] <slangasek> the problem we have right now is that if the shell crashes, the ui is locked for a long time while the kernel dumps all the memory across to apport, and it's probably dumping a lot that it shouldn't
[20:50] <mzanetti> right
[20:51] <greyback> AlbertA: is that correct^^? If a mir server crashes, the contents of the video buffers would be dumped too?
[21:00] <AlbertA> greyback: I don't think so...
[21:02] <AlbertA> greyback: but I've never paid attention.... I guess the argument is they are mmap'ed they would?
[21:11] <greyback> AlbertA: I'm similarly clueless :) Will ask in my a.m.
[23:46] <slangasek> AlbertA: yes, if they are mmapped they're going to get dumped along with everything else


[01:02] <smee> Hi, is it possible to apt update an img that is not the one loaded?
[01:04] <cartdrige> an img?
[01:04] <leftyfb> smee: if you can properly chroot to it, yes
[01:04] <smee> I might be using the wrong term here, when Linux starts, press ESC and you get a list to choose from.
[01:04] <NickH> kernel
[01:05] <NickH> In grub?
[01:05] <NickH> Before linux starts?
[01:05] <leftyfb> those are kernels, nothing to do with the rest of the packages on your system
[01:05] <leftyfb> smee: your machine will update to the latest kernel as needed
[01:06] <NickH> Need to reboot to actually use the new kernel though.
[01:06] <smee> Within GRUB, the list of Kernels, NickH has mentioned kernels.
[01:07] <leftyfb> smee: and those will get updated and removed as necessary
[01:07] <smee> The issue is I updated to the latest nvidia driver and now the kernel won't start completely. Just stops after displays some text.
[01:08] <leftyfb> smee: what version of ubuntu?
[01:08] <smee> 22.04
[01:09] <leftyfb> smee: which kernel?
[01:10] <smee> I've got 5.15.0-48-generic and <IP_ADDRESS>.56. 56 wont start but 48 does in recovery mode.
[01:10] <leftyfb> smee: you should instal linux-generic-hwe-22.04. That should bring the necessary modules package you need
[01:11] <smee> I'm hoping to update 56 and see if I can get that started, I dont wont 48 to be placed in a bad state like 56
[01:11] <leftyfb> smee: boot to your working kernel and install linux-generic-hwe-22.04
[01:21] <smee> leftyfb: Can  linux-generic-hwe-22.04 be install as a new kernel ?
[01:22] <leftyfb> smee: it's a meta package that will just make sure you have the latest kernel installed. But it should do a better job of also making sure you have the proper modules package installed as well
[02:18] <leftyfb> smee: did you install linux-generic-hwe-22.04 and reboot?
[02:19] <smee> leftyfb: No, I haven't worked out how to start the dud kernel.
[02:20] <smee> I want to make sure that the one that I can get into via recovery is not touched.
[02:20] <leftyfb> smee: I told you to just start ANY kernel that you can get into
[02:20] <leftyfb> smee: that's not how this works
[02:20] <leftyfb> smee: your working kernel won't get removed yet
[02:21] <leftyfb> smee: boot into a working kernel and run: sudo apt install linux-image-generic-hwe-22.04
[02:22] <smee> leftyfb: so will this create a new kernel?
[02:23] <leftyfb> smee: I told you exactly what it is and what it will do
[02:23] <leftyfb> smee: it's a meta package that will just make sure you have the latest kernel installed. But it should do a better job of also making sure you have the proper modules package installed as well
[02:23] <leftyfb> from 1 hour ago
[02:23] <leftyfb> it should take you less than a minute to boot into a kernel that'll let you login to a terminal and install the package
[02:26] <cartdrige> if you can't boot with grub, you can boot with a live USB stick and chroot to the filesystem of the hard drive (chroot tutorial to mount /dev etc. few terminal commands)
[02:27] <leftyfb> they can boot just fine into 48 which will work
[02:28] <smee> leftyfb: I'm wanting to make sure that the outcome was going to be a NEW kernel to select  from via GRUB? And no, the only kernel I cant start is the previous one but only in recovery mode.
[02:28] <leftyfb> smee: you don't need a NEW kernel. You're probably just missing the modules package for the latest kernel.
[02:28] <leftyfb> smee: please just take the advice
[02:29] <leftyfb> smee: it's been over an hour and you probably could have had this fixed in a couple minutes but you refuse
[02:32] <smee> leftyfb: Not refuse, just time poor.
[02:33] <leftyfb> smee: boot into a working kernel and run: sudo apt install linux-image-generic-hwe-22.04
[02:33] <smee> leftyfb: ok
[02:34] <sarnold> .. wouldn't "time poor" have been "thanks for the advice let me run that and report back"? :)
[02:35] <leftyfb> horse to water
[03:02] <quazimodo> 20.04 has wireguard built into the kernel right?
[03:02] <quazimodo> or do i need to install kernel modules for it via apt?
[03:04] <leftyfb> quazimodo: pretty sure it's already there
[03:07] <sarnold> quazimodo: it depends on which kernel package you have installed if the module comes along easily or if you need a new linux-modules-extra-* package https://termbin.com/3oss
[03:07] <sarnold> quazimodo: most people won't need to do anything
[03:14] <quazimodo> goti it
[05:07] <casada> hola
[09:22] <tozzi> anyone knows hopw to access mongodb with preinstalled wekan on 22.04.1 server ?
[09:22] <tozzi> trying to change my user as admin in wekan.
[11:11] <screenboi> Hey all, I have a weird problem. I have been using a dock for my laptop(screens go through dock) for a few months now, but since rebooting it doesn't work anymore. I tried a different dock, same problem. I can confirm the dock working at another computer. I am not sure what I should do now
[11:13] <murmel> screenboi: does your journal say anything, when you connect the dock?
[11:16] <screenboi> murmel: What should I be looking for? I disconnected it and connected, there is a lot of messaging. BTW, I currently use a keyboard + mouse succesfully through the dock. But let me upload the journal, a sec
[11:20] <screenboi> murmel: This is the pasty: https://pastebin.ubuntu.com/p/jgmJGpdTW8/
[11:20] <screenboi> That is the disconnecting + connecting log
[11:28] <murmel> screenboi: is the other system also ubuntu?
[11:29] <screenboi> murmel: No, a windows system.
[11:34] <murmel> screenboi: what dock are we talking about? as from skimming through the logs, I assume something from ASIX?
[11:34] <murmel> sadly docks are quite annoying on linux :S
[11:39] <screenboi> murmel: The dock says Baseus. But it is strange since it worked for the last few months. Just after booting up this morning it doesn't anymore.
[11:39] <murmel> screenboi: did you update anything last time you booted?
[11:39] <murmel> or did anything else which could interfere?
[11:42] <daily> i have this text string: "./gameconfigurations/initialinstallpackage/cas_02.cas" and i want to replace everything between slashes with double dots, how can i do that, using sed (or equivalent)? so i want the output to be "./../../cas_02.cas"
[11:44] <otisolsen70> On my Ubuntu servers, I seem to have an endless stream of these type of audit messages in auth.log: https://paste.yt/p24403.html Does Ubuntu Server by default log every program executed on a system? Is there a way to disable this?
[11:47] <murmel> screenboi: hey, sadly I have to go offline, so hope you can find somebody else who can help you :)
[11:54] <Maik> otisolsen70: please don't cross post
[11:54] <otisolsen70> Sorry, it was because I thought #ubuntu-server was dead and the topic mentioned this channel.
[11:56] <Maik> it's not dead :-) people aren't 24/7 at their pc and most of us are just volunteers. Just try to be patient and if no answer try asking again at a later point of the day or try askubuntu.com or the forums
[11:57] <otisolsen70> alright
[12:50] <davegarath> Hi all, I´ve Ubuntu 20.04 with root encrypted file system. I've run apt-get upgrade and it was installed new 5.15.53-generic linix image. At boot it still stuck and don't ask me in graphical form for the passphrase to unlock the FS. Booting with my old 5.15.0-48 I have not any problem. Also booting in safety mode with 5.15.0-53. Any idea how to fix this ?
[13:00] <_merlin_> I have this keyboard shortcut I need to copy to 30 other machines. Is there any shell command I can make to deploy keyboard ou any file do edit, so I can automate this task?
[13:13] <Apachez> rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL
[13:13] <Apachez> rehash: warning: skipping dhparam.pem,it does not contain exactly one certificate or CRL
[13:13] <Apachez> now what?
[13:26] <BluesKaj> Hi all
[14:35] <GrImz> Hi all! Ubuntu server noob here, i'm installing a Ubuntu Server with Graylog&ElasticSearch&MongoDB on it and i'd like to update everything except the Kernel since I don't want any compatibility with Ubuntu version and my apps.
[14:35] <GrImz> Any apt-get command that update/upgrade all except the kernel?
[14:36] <leftyfb> GrImz: there shouldn't be any compatibility with the kernel and your apps
[14:36] <leftyfb> compatibility issues*
[14:37] <leftyfb> GrImz: you can always remove the newer kernel if needed
[14:38] <GrImz> https://go2docs.graylog.org/5-0/downloading_and_installing_graylog/installing_graylog.html#:~:text=The%20Graylog%20server%20application%20is,%2FCentOS%206%2C%207%2C%208
[14:39] <GrImz> System requirement says Ubuntu 22.04
[14:39] <leftyfb> GrImz: ok, so install Ubuntu 22.04
[14:40] <GrImz> but if I install 22.04 and do apt-get update/upgrade it will upgrade to 22.10 right?
[14:40] <leftyfb> negative
[14:40] <GrImz> oh
[14:40] <InZane> yeah that's not sane behavior for a LTS release to upgrade to a non-lts....
[14:41] <GrImz> ok cool!
[14:41] <leftyfb> apt-get upgrades packages, it will not upgrade your release without first purposely making changes to system elsewhere
[14:42] <GrImz> and thanks all! my install can now resume :)
[15:10] <davegarath> Hi all, I´ve Ubuntu 20.04 with root encrypted file system. I've run apt-get upgrade and it was installed new 5.15.53-generic linix image. At boot it still stuck and don't ask me in graphical form for the passphrase to unlock the FS. Booting with my old 5.15.0-48 I have not any problem. Also booting in safety mode with 5.15.0-53. Any idea how to fix this ?
[15:49] <KBar> hi all. what's the command to install all binary packages that some specific source package provides?
[15:49] <leftyfb> KBar: sudo apt install <package name>
[15:50] <KBar> sorry but that's not what i asked
[15:50] <InZane> 0.o
[15:50] <leftyfb> KBar: source packages in the ubuntu repositories are directly related to the binary packages which they are the source for
[15:51] <KBar> leftyfb: try that with gtk+3.0 for example
[15:51] <KBar> it wont work
[15:51] <KBar> there are many source packages that are named differently and that come with multiple binary packages
[15:52] <ashafq> KBar, like dev package?
[15:52] <ashafq> sudo apt install libsomething-dev?
[15:52] <KBar> nope
[15:52] <ioria> apt-cache  showsrc  gtk+3.0 | sed -n "/Binary:/,/Architecture:/p"
[15:52] <ashafq> there you go
[15:54] <KBar> ioria: nice! i imagine there isn't a single command/option for this kind of operation?
[15:55] <ioria> you mean a one-liner install command or such ?
[15:55] <KBar> yeah kinda like a flag to `apt` itself, e.g. `apt instal -S gtk+3.0`
[15:56] <KBar> -S meaning 'install all binaries provided by this source'
[15:57] <ioria> i don't know that, sy
[15:57] <blomberg> should i do-release-upgrade -d #or without -d and should i update&upgrade my os first before release-upgrade?
[15:57] <leftyfb> blomberg: you should run before you upgrade your release: sudo apt update ; sudo apt full-upgrade
[15:58] <KBar> ioria: thanks for the tip!
[15:58] <blomberg> why not just upgrade ? why full-upgrade leftyfb
[15:58] <ioria> no prob
[16:00] <blomberg> should i -d?
[16:00] <leftyfb> blomberg: what release of ubuntu are you currently running and what release are you trying to get to?
[16:00] <blomberg> 20.04
[16:00] <blomberg> latest 22
[16:01] <leftyfb> blomberg: -d is for the latest development release which is currently 23.04
[16:01] <blomberg> what's the difference
[16:01] <blomberg> and what's the non-dev release latest
[16:02] <leftyfb> blomberg: as for full-upgrade, it will remove any packages or dependencies that aren't needed anymore. No sense in trying to re-install those on your new release
[16:02] <leftyfb> blomberg: the latest LTS release is 22.04. I recommend continuing your pursuit to upgrade to that
[16:03] <blomberg> ok then i can just use the non-LTS version and keep running -d after expiry of 23.04
[16:03] <blomberg> I prefer LTS for installs, but seems do-release-upgrade is awesome as it's so easy and comfy
[16:03] <leftyfb> 23.04 is not released yet and unless you plan on installing for the purposes of discovering, reporting and/or fixing bugs, I do not recommend upgrading to it
[16:04] <blomberg> ahh i see
[16:04] <leftyfb> blomberg: I suggest upgrading to 22.04 and not worrying about 23.04 or even 22.10 unless you know you need either of those
[16:05] <blomberg> i can get 23.04 after the ... release, since non-LTS too seems fine from this comfy cool do-release-upgrade
[16:05] <leftyfb> blomberg: 22.10 and 23.04 are not LTS releases.
[16:06] <blomberg> next LTS is 24.04 yes
[16:07] <blomberg> you have LTS ? and prefer it?
[16:07] <blomberg> well i prefer the latest
[16:07] <blomberg> non-dev
[16:08] <blomberg> is LTS more secure,?
[16:08] <leftyfb> blomberg: LTS's tend to be more stable
[16:09] <leftyfb> and continue to get security patches for 5 years
[16:15] <davegarath> Hi all, I´ve Ubuntu 20.04 with root encrypted file system. I've run apt-get upgrade and it was installed new 5.15.53-generic linix image. At boot it still stuck and don't ask me in graphical form for the passphrase to unlock the FS. Booting with my old 5.15.0-48 I have not any problem. Also booting in safety mode with 5.15.0-53. Any idea how to fix this ?
[16:15] <davegarath> I'm searching it in google since 7 days without success
[16:16] <WaV> davegarath: uname -a
[16:16] <WaV> davegarath: Does it say Oracle at the end?
[16:16] <davegarath> nope
[16:16] <davegarath> Linux dave-desktop 5.15.0-48-generic #54~20.04.1-Ubuntu SMP Thu Sep 1 16:17:26 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
[16:17] <davegarath> This version are working correctly
[16:17] <leftyfb> davegarath: sudo apt install linux-image-generic-hwe-20.04
[16:17] <davegarath> The kernel with the problem is 5.15.0-53 generic
[16:19] <davegarath> leftyfb, why hwe-20.04 ?
[16:19] <leftyfb> davegarath: it will do a better job at keeping you with the latest kernel and the associated modules packages
[16:20] <davegarath> I'll try
[16:23] <davegarath> leftyfb, I'm thinking to do-release-upgrade in the next future to ubuntu 22.04. Do you think I'll do some problem ?
[16:23] <leftyfb> davegarath: depends on what the problem is. You have yet to determine that
[16:30] <davegarath> doh! leftyfb is left
[16:31] <leftyfb> davegarath: ?
[16:31] <davegarath> leftyfb, tab completion confused me
[16:32] <davegarath> leftyfb, I've installaed linux-generic-hwe-20.04 that as insalled initrd.img-5.15.0-56-generic But I've the same problem
[16:32] <davegarath> just initrd.img-5.15.0-48-generic seems works
[16:33] <leftyfb> davegarath: sudo apt install linux-modules-5.15.0-56-generic linux-modules-extra-5.15.0-56-generic
[16:34] <leftyfb> davegarath: after that, try booting to 5.15.0-56-generic which should be the default
[16:34] <davegarath> But the strange thing is that if I choice safe mode of the kernel he ask me the passphrase and I can boot normally after that
[16:35] <WaV> davegarath: Try what leftyfb suggested. Sounds like your hardware isn't supported without some additional kernel modules.
[16:35] <davegarath> leftyfb, linux-modules and extra are already installed
[16:36] <leftyfb> davegarath: apt list --installed |grep oracle    # do you have any oracle kernel installed?
[16:36] <leftyfb> (not sure if this was just an issue on 22.04)
[16:37] <davegarath> I'm on 20.04.5 now
[16:41] <knmae> Hey, I needed to log in from tty, how to change localization of keyboard?
[16:42] <leftyfb> knmae: sudo dpkg-reconfigure locales
[16:43] <leftyfb> sudo update-locale LANG=fi_FI.UTF-8
[16:51] <knmae> Great, thanks! Do I need to reboot or something?
[16:54] <leftyfb> knmae: I don't think so. Though I've never actually done it
[16:54] <leftyfb> knmae: maybe a lot out and back in might help
[17:31] <oerheks> leftyfb, seen this before, how does this oracle kernel get installed?
[18:17] <leftyfb> oerheks: not sure, though it was a bug that seemed to happen recently to multiple people
[18:53] <noord> does 22.04 force to use snap or flatpak?
[18:59] <leftyfb> noord: flatpak is not officially supported in ubuntu
[18:59] <leftyfb> noord: there are a few packages in ubuntu 22.04 that are only available via snap, like firefox
[19:03] <cartdrige> Actually weither it is snaps or normal .deb is not visible at all for a normal user. But the snap version mounts virtual FS etc which makes things even more obscure, like when looking at mount output or process going on.
[19:06] <leftyfb> cartdrige: you're assuming all users only use the GUI software app to install applications. When using the CLI, it's very apparent if an app is a snap or .deb
[19:07] <noord> cartdrige: which messes df output, and bundles its dependencies, no thanks
[19:08] <leftyfb> noord: snaps do not "mess with" "bundles" or dependencies
[19:08] <leftyfb> noord: for df you can run: df -h -x squashfs
[19:11] <cartdrige> leftyfb, all snaps are squashfs blobs mounted on the real FS?
[19:11] <leftyfb> yes
[19:11] <cartdrige> ok.
[19:12] <leftyfb> catalase: to be clear, sqashfs is a "real FS"
[19:14] <cartdrige> leftyfb, i mean the FS on the hardware, cause squashfs is like an ISO, on top of the FS of the hardware.
[19:27] <neoweb> MAN
[19:27] <neoweb> https://askubuntu.com/questions/1337649/how-to-disable-suspend-in-20-minutes-from-the-lightdm-login-screen
[19:27] <neoweb> That worked.
[19:27] <neoweb> It is the only way.
[19:27] <neoweb> Bad ubuntu.
[19:27] <neoweb> BAD!!!
[19:28] <leftyfb> !bug | neoweb
[19:30] <leftyfb> neoweb: though, you must be running an outdated and unsupported version of ubuntu. What you say works is changing configs for lightdm, which isn't used anymore
[19:30] <arraybolt3> Neither is Unity.
[19:30] <arraybolt3> Ubuntu uses GNOME currently (though there is Ubuntu Unity, if you like Unity, and it's now an official flavor).
[19:46] <girafe3> what are official ubuntu flavors ?
[19:47] <leftyfb> !flavors | girafe3
[19:59] <snakes2112> i eat kids
[20:04] <rjwiii> I seem to have 2 instances of Ubuntu Core mounted on my Ubuntu 22.04. One if for Core 20, the other is for Core 16 ... I don't have any USB drives  connected. There are in /media/<user>. Are these supposed to be there?
[20:05] <leftyfb> rjwiii: a reboot should resolve that
[20:06] <rjwiii> leftyfb: Thanks ... I'll reboot after work ...
[20:06] <tomreyn> i'm guessing that rjwiii is probably referring to the compatibility snaps
[20:06] <tomreyn> if so, those wont go away with a reboot
[20:07] <leftyfb> tomreyn: I've seen this before. It does. After upgrading the snap it gets into a weird state where the old mounts get orphaned
[20:07] <tomreyn> hmm, okay, better not research this too much. ;)
[20:08] <leftyfb> and by seen it before, I mean on my own machine. It's happened several times
[20:08] <leftyfb> I THINK a bug was filed for it. Can't remember. It was several months ago that I ran into it
[20:14] <knmae> Yeah, now it wörks, thänks
[21:17] <kiet> whats this channel about
[21:18] <leftyfb> kiet: Ubuntu support


[02:38] <alkisg> Hi, in https://code.launchpad.net/sch-scripts it mentions:        You can push the branch directly to Launchpad with the command:  bzr push lp:~alkisg/sch-scripts/sch-scripts
[02:38] <alkisg> Why does it say "~alkisg" instead of "~ts.sch.gr", the team, there?
[02:39] <lifeless> alkisg: looks like a bug to me
[02:40] <alkisg> Ah, ok, thank you :)
[02:40] <lifeless> its like an amalgamation of
[02:40] <lifeless> you can push a new branch with <...>
[02:40] <lifeless> and you can push to trunk with <...>
[02:40] <lifeless> please file a bug, its definitely horribly confusing UI
[02:40] <alkisg> Will do, thanks again
[02:42] <wgrant> It possibly means "push a branch" rather than "push the branch"
[02:42] <wgrant> How odd
[02:43] <lifeless> its definitely not what it should be
[02:43] <lifeless> I don't know what it should be, but it isn't it.
[02:44] <wgrant> Indeed
[02:45] <wgrant> Ah
[02:46] <wgrant> It was semi-copied from another page in March when the "Register a branch" link was removed
[02:46] <wgrant> But not reworded to fit its new location
[02:48] <alkisg> When I push a branch under lp:~ts.sch.gr/sch-scripts/branch-name, that branch can be just "related" to sch-scripts, it doesn't have to be a fork of the sch-scripts code, right?
[02:49] <alkisg> We have many little projects like e.g. "mahara-el", greek packaging for mahara, while sch-scripts is an "umbrella" project for greek schools, and I'm looking to better organize things...
[02:50] <lifeless> alkisg: nothing mechanical forces it to be part of the same project, but its generally better not to mix things up like that
[02:50] <lifeless> new projects are pretty low overhead
[02:50] <alkisg> lifeless: so, I should make another project for each of those small projects?
[02:50] <lifeless> alkisg: the general rule of thumb is one code base per project
[02:50] <alkisg> Another example, "libnatspec, support for greek in unzip". Gotcha, thanks!
[04:46] <mark06> what's the procedure when a code import from external VCS fails? file a bug?
[11:39] <mlankhorst> can I get a bump on https://launchpad.net/~mlankhorst/+archive/x-1.13/+packages ?
[11:40] <czajkowski> mlankhorst: wgrant I can't bump an individual package....
[11:41] <mlankhorst> ..?
[11:41] <czajkowski> mlankhorst: just a moment
[11:42] <czajkowski> mlankhorst: you;ll have to ask in -ops as I can't do it for you
[11:42]  * wgrant does it
[11:42] <czajkowski> ah
[11:42] <czajkowski> wgrant: so how can we fix this for me in future :)
[11:42] <czajkowski> it's weekly this occurs
[11:42] <wgrant> I'm going to ask IS when we get the rest of our builders back
[11:42] <wgrant> Then it won't be weekly
[11:43] <mlankhorst> well, could the daily builds get a lower priority instead of 2505?
[11:43] <mlankhorst> usually I get clogged behind firefox, libreoffice and thunderbird daily builds
[11:43] <czajkowski> wgrant: will it be daily ;)
[11:44] <wgrant> They should all be building in a few seconds, anyway
[11:45] <mlankhorst> yeah thanks :)
[17:17] <cnd> I seem to be locked out of my launchpad.net account
[17:17] <cnd> when I try to log in, I get: "Your login was unsuccessful"
[17:17] <cnd> "User cancelled"
[17:18] <cnd> would anyone here be able to help?
[17:18] <czajkowski> cnd: https://launchpad.net/~chasedouglas <-- you
[17:18] <cnd> czajkowski: yes
[17:18] <czajkowski> ot's active and hasn't been suspended
[17:19] <czajkowski> are you having a SSO issue
[17:19] <cnd> czajkowski: I don't know where the issue is
[17:19] <czajkowski> cnd: well I can tell you it's not LP for sure as your ac is there and not suspended
[17:19] <cnd> czajkowski: what do you suggest I try?
[17:20] <dobey> cnd: go to login.ubuntu.com directly and see if you can log in or have any issues on there
[17:21] <cnd> dobey, it asks me to choose a password
[17:21] <cnd> when I do that, it says my acct details have been updated
[17:21] <czajkowski> cnd: I think SSO and your email address could be the issue
[17:21] <cnd> but launchpadnet doesn't work
[17:22] <czajkowski> I wish the branding was different it's rather confusing
[17:22] <cnd> czajkowski: how do I fix SSO?
[17:23] <czajkowski> cnd: let me see if I can find someone for you as I am EOD and just heading out
[17:23] <cnd> czajkowski: ok, thanks
[17:24] <czajkowski> jcsackett: hiya if you're about could you look into this isue for cnd I'm heading out to collect some dinner
[17:25] <czajkowski> cnd: also asking toykeeper she might be able to help https://launchpad.net/~toykeeper
[17:25] <cnd> ok
[17:46] <jcsackett> cnd: i'm back from my lunch, looking at backtrace now.
[17:46] <jcsackett> er, log, not bactkrace.
[17:46] <cnd> jcsackett: thanks :)
[17:47] <jcsackett> cnd, ah, okay, SSO issues. fun times.
[17:48] <jcsackett> cnd: have you tried logging into launchpad with the email/password you have just set on SSO?
[17:48] <cnd> yes
[17:48] <cnd> I've tried in incognito windows just to be sure there are no cookie issues
[17:48] <jcsackett> and it still fails with the "user canceled"?
[17:49] <cnd> yeah
[17:50] <cnd> every time I login, though, it asks me to change my password
[17:50] <jcsackett> cnd: that's every time you login to login.ubuntu.com?
[17:50] <cnd> yeah, from a clean session
[17:50] <cnd> if I've already logged in, then I get the error message
[17:59] <jcsackett> cnd: so, it does look like it's SSO. i'm hunting down help for you specific to that.
[17:59] <jcsackett> sadly it's not something i can directly address.
[18:01] <jcsackett> cnd: so, SSO has a support form at https://forms.canonical.com/sso-support/
[18:01] <cnd> jcsackett: ok
[18:02] <jcsackett> cnd: sorry i can't directly fix it for you.
[18:02] <cnd> jcsackett: uhhh… I choose "login issue" and then clicked "submit", but it took me to a page that generically says "someone will be contacting you shortly"
[18:02] <cnd> I have no idea how they are going to contact me
[18:03] <cnd> or how they know who I am, even
[18:03] <jcsackett> hrm.
[20:46] <joey> lifeless: api question for you
[20:46] <joey> lifeless: how do I state t.team_owner_link.name     I can get to t.team_owner_link  but can't seem to get the .name out of it
[20:46] <joey> abstract it maybe?
[20:47] <joey> I need the name of the owning team
[20:47] <dobey> t.team_owner.name ?
[20:47] <joey> get an error
[20:48] <dobey> joey: t.team_owner.display_name
[20:48] <joey> oh but it's a key error
[20:48] <joey> ah, thanks dobey
[20:48] <joey> I'm good.  unping lifeless
[20:48] <dobey> though, name should work too
[21:03] <lifeless> joey: :P
[22:09] <mark06> hi, what to do on failed branch imports?


[00:27] <silverarrow> is anyone good with bug reporting for quantal testing?
[00:28] <histo> silverarrow: people in #ubuntu+1
[00:29] <silverarrow> yeah,
[00:29] <silverarrow> thanks
[00:39] <silverarrow> my head is more like fogg
[01:43] <phillw> how do you interrupt grub so as to put in nomodeset?
[08:23] <Blazemore> phillw: hold shift
[18:19] <Widgete> glad i am not the only one in here
[18:19] <bioterror> can we help you?
[18:20] <Widgete> maybe, i am just kinda trying to learn my way around... learning both ubuntu and irc
[18:20] <Widgete> i am currently running this off a sd card, is it still possible to run cloud storage?
[18:24] <bioterror> okay
[18:24] <bioterror> you can still quit this irc
[18:25] <bioterror> it's just waste of time :D
[18:25] <Widgete> lol i have plenty of time to waste
[18:27] <bioterror> there you go! ;D


[23:56] <mr-day> guys is that possible create custom launcher on start menu
[23:57] <mr-day> on side with accessoris, internet, office, games, etc
[23:59] <wxl> mr-day: yep. just make sure there's a desktop file in /usr/share/applications


[16:23] <poutsi> hey, i just tried out mer 0.15 on my n810 and thought i'd try changing the apt sources and installing ubuntu on top of that.. would it work?
[16:23] <poutsi> I see no reason why not
[16:30] <poutsi> what I can't seem to figure out is what the apt sources are, surely there are arm repos?
[16:31] <jmc93739653> poutsi: You'll have to ensure mer-0.15 and whichever version of Ubuntu you are wanting to install
[16:31] <jmc93739653> poutsi: use the same toolchain (gcc, g++, binutils, bison, m4, gdb, GNU Autotools, et cetera.
[16:33] <poutsi> hmm
[16:33] <jmc93739653> poutsi: By "apt sources" are you asking about obtaining source (un-compiled) DEB-file components
[16:33] <jmc93739653> poutsi: Or are you asking about where to find the sources.list apt-get _binary_ URLs/entries?
[16:33] <poutsi> installing directly on top would've saved me the trouble of flashing an image, since mer had an installer...
[16:33] <poutsi> I'm asking about binaries
[16:34] <jmc93739653> poutsi You can run binaries that are not toolchain compatible, as long as they are compiled statically, but that's a whole other debate.
[16:36] <jmc93739653> poutsi: if you want binaries, then you'll have to get the .dsc, .orig.tar.gz, and diff.gz files and build them yourself on top of mer.
[16:37] <poutsi> alright
[16:37] <jmc93739653> poutsi: http://packages.debian.org/source/lenny/qemu has examples of the compilation dependencies and source files you'd have to grab for compilation.
[16:39] <jmc93739653> poutsi: http://www.debian.org/doc/FAQ/ch-pkg_basics.en.html all sections are relevant, but 7.13 and 7.14 seem to be the most relevant to your question.  (Sorry, I just skimmed the doc)
[16:40] <jmc93739653> poutsi: I'd have used ax example from packages.ubuntu.com, but my browser is telling me it's unreachable.  (I blame my ISP.)
[16:40] <poutsi> thanks a bunch, I'll take a look
[16:41] <poutsi> I guess my ultimate goal would be to get the netbook remix running on this n810
[16:41] <poutsi> it was pretty nice on an intel laptop
[16:41] <jmc93739653> poutsi: You're welcome :) If you have questions, and I'm on, either drop back in, or PM me.
[16:59] <jmc93739653> poutsi:  There are also different build-targets for ARM which Ubuntu is is using.
[16:59] <jmc93739653> poutsi:  ARMv7 (the μarch to be used in Nokia's next-gen "RX-51" tablet is a given.
[16:59] <jmc93739653> poutsi:  Ubuntu is also targeting ARMv6 (which is in the N800 and N810), and ARMv5t.
[16:59] <jmc93739653> poutsi:  ARMv5t includes Xscale chips and "ARM9" series CPUs. (e.g. the Atmel SAM9G45, based on
[16:59] <jmc93739653> poutsi: an ARM926. 'ARMv<number>' indicates the instruction-set version,
[16:59] <jmc93739653> poutsi: 'ARM<number>' indicates a particular _μarch_ compliant with a specific ISA version.
[19:26] <poutsi> yeah, I know
[19:27] <poutsi> I guess I misinterpreted some of this ubuntu on arm hype as meaning that they'd have had packages in the repos built for the n810, and that someone somewhere had made it easy to install too :)
[19:27] <poutsi> meaning as easy as it was with mer
[19:28] <poutsi> and I've seen ubuntu running on some arm hardware last week, and the impression that I got was that the guy just downloaded and image and presto
[19:29] <poutsi> anyway, there seems to have been a jaunty rootstrap for n810 floating around but the site that hosted it went away
[19:29] <poutsi> 'cause that would've been enough for me, I'd have just put it on the internal mmc of the n810
[19:43] <jmc93739653> poutsi: There are armel packages here: http://ports.ubuntu.com/dists/karmic/main/installer-armel/alpha-2/images/
[19:43] <jmc93739653> poutsi: well images at least
[19:47] <jmc93739653> There are some ARMv5t packages here http://ports.ubuntu.com/pool/main/l/linux/
[19:47] <jmc93739653> But the current (daily) installer images are for Freescale's i.MX51 series,
[19:47] <jmc93739653> so ARMv7A build targets appear to be slated too.
[19:47] <jmc93739653> (I'd do just about anything to get my hands on a development Freescale i.MX515 "Babbage Board".)