[18:47] <BinarySavior> will I be able to update to 24.04 without wiping sdd and installing with usb drive?
[21:08] <OvenWerks> BinarySavior: where are you starting from?
[21:08] <OvenWerks> BinarySavior: you should be able to. I just up graded from 23.04 to 23.10


[06:59] <tjaalton> oh
[07:31] <ibilalkayy> I sent a PR to adsys on GitHub and they were requiring to sign the CLA. I filled the form but they are asking me to add the Canonical Project Manager or contact. I don't know what it is and where to find
[07:34] <ibilalkayy55> I sent a PR to adsys repository on GitHub and they were requiring me to sign the CLA. I filled out the form but they are asking me to add the Canonical Project Manager or contact. I don't know what it is and where to find
[07:40] <ibilalkayy55> any response
[07:40] <ibilalkayy55> I sent a PR to adsys repository on GitHub and they were requiring me to sign the CLA. I filled out the form but they are asking me to add the Canonical Project Manager or contact. I don't know what it is and where to find
[07:41] <ibilalkayy> I sent a PR to adsys repository on GitHub and they were requiring me to sign the CLA. I filled out the form but they are asking me to add the Canonical Project Manager or contact. I don't know what it is and where to find.
[09:05] <ibilalkayy> I sent a PR to adsys repository on GitHub and they were requiring me to sign the CLA. I filled out the form but they are asking me to add the Canonical Project Manager or contact. I don't know what it is and where to find.
[16:07] <hallyn> hm, so i notice that both debian/libsystemd-dev.install and debian/libsystemd0.install list libsystemd.so .  Is that intentional?
[16:09] <cjwatson> libsystemd0.install lists libsystemd.so.*, not bare libsystemd.so
[16:58] <hallyn> Ah, yes, thank you.
[19:17] <UnivrslSuprBox> I think I found an odd dependency relationship in libreoffice: libreoffice-nogui depends libreoffice-base-nogui and recommends libreoffice-sdbc-postgresql. libreoffice-sdbc-postgresql depends libreoffice-base, which conflicts libreoffice-base-nogui. Trying to install libreoffice-nogui only results in Apt's problem resolver coming up occasionally, though, and I haven't figured out what decides that.
[19:20] <UnivrslSuprBox> Those parts of the control file seem taken directly from Debian, so I suppose I have a couple questions. Is this a bug? If it is, would it be better for -nogui to stop Recommending the postgres driver or for the driver to specify an or-relation with -core-nogui?
[19:22] <UnivrslSuprBox> And as an aside, why does apt only follow this Recommends relationship, leading to a broken package count, if the dpkg status file is empty? That's the only way I've been able to get it to reliably call `libreoffice-nogui` not installable (other than specifying `libreoffice-nogui libreoffice-sdbc-postgresql` of course)
[20:31] <rbasak> UnivrslSuprBox: without looking into any details, it sounds like maybe libreoffice-sdbc-postgresql should depend on libreoffice-base | libreoffice-base-nogui
[20:31] <rbasak> Or something like that.
[20:31] <UnivrslSuprBox> I agree, but also wonder if there's a reason it depends on base exclusively
[20:31] <rbasak> As you've checked that this affects Debian already, it might be best to report it as a bug to them.
[20:31] <UnivrslSuprBox> When I eventually figure out how the Debian BTS works, I'll ask them
[20:32] <rbasak> Or maybe they should have a virtual package that is provided both by libreoffice-base and libreoffice-base-nogui
[20:32] <rbasak> (going off the names only, to be clear - this is just speculation)


[05:18] <lfitz> is there a guide to install ubuntu onto an SD card?
[05:18] <lfitz> for the sheevaplug
[07:01] <lfitz> is there a default password for root on ubuntu-arm i followed this guide: http://plugcomputer.org/plugwiki/index.php/Ubuntu_9.0.4_Plug_Computer_Distribution#Building_a_rootfs_to_install_Ubuntu_on_an_SD_Card_or_USB_Drive
[07:02] <lfitz> also, i can login to the user account i created, but i cant login as root
[07:02] <lfitz> or sudo
[07:02] <lfitz> sudo outputs: must be setuid root
[07:13] <lfitz> ugh, i chown'd everything so i could move it before putting it on the sd card and forgot...thats why that happened ^^^
[07:36] <DanaG> yeah, next time sudo tar. =þ
[07:38] <lfitz> DanaG actually im still stuck
[07:38] <lfitz> do i have to build the rootfs again?
[07:38] <lfitz> because i basically have no root, correct?
[08:06] <sechrist> are there prebuilt armv6 images?
[08:07] <sechrist> heh perhaps I should read further down the page next time. Found one
[08:08] <sechrist> woah
[08:08] <sechrist> http://w3.impa.br/~gabrield/data/click.php?id=4 shows php source hehe
[11:16] <dcordes> hi
[11:19] <dcordes> somebody has a secret deb to fix rootstock ?
[11:22] <dcordes> so far it only worked with karmic in karmic for me
[11:24] <dcordes> creating lucid rootfs from lucid it hangs building iso locales or so (that's in bugzilla for 3 months or so)
[11:25] <dcordes> not exactly specific to roostcok: getting lucid minimal rootfs and installing the desktop task results in dependency problems
[11:25] <dcordes> worked around it and got non working usb keyboard in gdm
[11:26] <dcordes> building maverick image from lucid results in segfault
[11:29] <dcordes> alternatively, somebody has a clue where to get finished lucid or maverick desktop tarballs ?
[12:00] <armin76> sechrist: ubuntu doesn't support armv6 anymore, 9.10 is the last release supporting armv6+vfp(so no qualcomm)
[12:00] <sechrist> armin76: thanks, I figured this out a few hours ago
[12:00] <armin76> someone from ubuntu should answer those questions instead of me :)
[12:01] <armin76> dcordes: ogra is the one you should poke about it
[12:02] <dcordes> armin76: it's armv7 only now ?
[12:02] <dcordes> ogra: poke
[12:02] <dcordes> on a side note I considered reporting on bugzilla instead of here
[12:02] <dcordes> but everything is present already
[12:03] <dcordes> I am just wondering if somebody is working on this
[12:03] <armin76> dcordes: yes
[12:03] <dcordes> sechrist: which device do you have ?
[12:04] <sechrist> dcordes: kindle
[12:04] <dcordes> isn't ubuntu a bit 'big' for it ?
[12:04] <dcordes> did you consider something openembedded based ?
[12:04] <sechrist> nfs dawg
[12:04] <sechrist> nah I haven't, I can't replace the kernel either
[12:04] <sechrist> I just wanted something to chroot into
[12:04] <lfitz> hi, my sheevaplug stops booting at uncompressing the kernel...booting the kernel.
[12:04] <dcordes> oh that sucks
[12:05] <sechrist> well I probably could replace the kernel
[12:05] <sechrist> but I don't have a serial cable. I don't want to risk a brick.
[12:05] <dcordes> lfitz: what build do you use?
[12:05] <dcordes> sechrist: lol then don't :)
[12:06] <lfitz> do you mean the kernel number?
[12:06] <lfitz> 2.6.34
[12:06] <dcordes> lfitz: I mean your entire setup
[12:07] <lfitz> uboot 3.4.19
[12:07] <dcordes> you built this yourself ?
[12:07] <lfitz> yeah
[12:07] <lfitz> it was working
[12:07] <lfitz> until i tried to go and install ubuntu :P
[12:07] <lfitz> i ran debian, now both sd cards stop at the same place
[12:07] <dcordes> on first look it seems unrealted to ubuntu
[12:07] <lfitz> yeah
[12:07] <dcordes> maybe file corruption?
[12:08] <lfitz> well...not on the sd cards
[12:08] <armin76> haha
[12:08] <lfitz> cause i have two
[12:08] <lfitz> possibly on nand cause theres a crc error
[12:08] <dcordes> aha
[12:08] <dcordes> there you go
[12:08] <lfitz> but i think its unrelated
[12:08] <dcordes> rebuild the kernel
[12:08] <lfitz> cause it was booting debian from sd today
[12:08] <dcordes> copy it again
[12:08] <dcordes> check md5
[12:09] <lfitz> rebuild the kernel on sd card?
[12:09] <lfitz> i just downloaded it from sheeva.with-linux.com/sheeva
[12:09] <dcordes> I don't know how you build your kernel
[12:09] <dcordes> you said you were building yourself.
[12:09] <lfitz> well, heres what i have done...
[12:10] <lfitz> used rootstock to build a....?filesystem?....then downloaded the kernel headers, extracted them to the filesystem, and the modules
[12:11] <dcordes> armin76: any clue where to get prebuilt arm tarballs ? I can only find some minimal builds.
[12:11] <lfitz> along with uimage
[12:11] <tmzt_> does qemu-debootstrap work?
[12:11] <lfitz> preferably i would like to default the plug, but i dont know if its possible...
[12:11] <dcordes> this all irrelevant if your kernel fails uncompressing
[12:11] <lfitz> yeah
[12:11] <dcordes> you flash the kernal image to nand ?
[12:11] <lfitz> is there an easier way to restore the factory install
[12:11] <armin76> dcordes: sorry i don't, i don't even use ubuntu myself
[12:12] <dcordes> ok
[12:12] <dcordes> hi tmzt_
[12:12] <tmzt_> sechrist: isn't kindle arm11?
[12:12] <tmzt_> hey
[12:12] <dcordes> tmzt_: big rootstock disappointment here
[12:12] <dcordes> tmzt_: did you ever use it ?
[12:13] <tmzt_> no, I'm just reading the changelogs on my maverick update
[12:13] <tmzt_> I hadn't heard of qemu-debootstrap before
[12:13] <dcordes> tmzt_: it is installed on my lucid host
[12:16] <tmzt_> cp $(which "qemu-$qemu_arch-static") "$target/usr/bin"
[12:16] <tmzt_> run chroot "$target" /debootstrap/debootstrap --second-stage
[12:16] <lfitz> dcordes:  would it be wise to set the username in rootstock to root
[12:16] <sechrist> tmzt_: you reading wikipedia?
[12:16] <tmzt_> that's from the script, okay
[12:16] <tmzt_> sechrist: no, why?
[12:16] <sechrist> tmzt_: because it's armv6
[12:16] <tmzt_> yep, armv6==arm11
[12:16] <tmzt_> neither is supported in lucid or maverick to my knowledge
[12:16] <sechrist> I'm running 9
[12:18] <lfitz> dcordes:  http://plugcomputer.org/plugwiki/index.php/Ubuntu_9.0.4_Plug_Computer_Distribution#Building_a_rootfs_to_install_Ubuntu_on_an_SD_Card_or_USB_Drive
[12:19] <lfitz> thats the guide i followed...
[12:20] <sechrist> so is cross compiling even worth trying
[12:20] <sechrist> or is there like architecture-sound emulators (I'm thinking qemu but I haven't ever used it)
[12:21] <dcordes> lfitz: You should download the kernel place the uImage in the boot directory of the filesystem
[12:21] <sechrist> like a full running arm nix system inside an emu on x86
[12:21] <dcordes> lfitz: make sure nothing goes wrong during that step
[12:21] <dcordes> lfitz: check md5sum of kernel inside your SD /boot/ vs kernel image from the download source
[12:21] <lfitz> well sheeva.with-linux.com has kernel-headers...
[12:21] <lfitz> is that the kernel...
[12:21] <lfitz> ?
[12:22] <dcordes> no
[12:22] <dcordes> http://sheeva.with-linux.com/sheeva/2.6.34/sheeva-2.6.34-uImage
[12:22] <dcordes> this is the kernel
[12:22] <lfitz> okay
[12:22] <dcordes> get this along with the modules http://sheeva.with-linux.com/sheeva/2.6.34/sheeva-2.6.34-Modules.tar.gz
[12:23] <lfitz> what about kernel headers, no need for it?
[12:23] <dcordes> this is the device specific part you need
[12:23] <dcordes> no
[12:23] <dcordes> unless you want to compile some modules
[12:23] <dcordes> later on
[12:23] <lfitz> okay
[12:24] <lfitz> so im running rootstock again to build the rootfs, and then ill add sheeva-2.6.34-uImage to \\boot and sheeva-2.6.34-Modules (extracted) to rootfs
[12:24] <lfitz> err //boot
[12:24] <lfitz> / boot
[12:25] <dcordes> if you still have the .tar.gz from your previous roostcok build, you do not need to build it again
[12:25] <tmzt_> sheeva only has one ethernet?
[12:25] <lfitz> dump it to sd card, modify the environment settings to boot from sd and hopefully boot sucessfully...
[12:25] <lfitz> tmzt_:  yes only one
[12:26] <dcordes> tmzt_: uboot able to mount rootfs ?
[12:26] <dcordes> tmzt_: just wondering if he needs to flash uimage
[12:26] <tmzt_> too bad, I might need a voip proxy for a project
[12:26] <tmzt_> dcordes: what do you mean?
[12:26] <tmzt_> if I understand rootfs is just a kernel parameter
[12:27] <dcordes> lfitz: he's told to put uImage in /boot
[12:27] <dcordes> and I'm wondering if the bootloader can access it
[12:27] <dcordes> or if he needs to flash
[12:28] <lfitz> yeah, it can access uImage, its offset at 0x80000000
[12:28] <lfitz> 0x8000000*
[12:28] <lfitz> and it reads all the bytes
[12:29] <lfitz> i mean, the total number of bytes of the uImage
[12:29] <dcordes> fine
[12:30] <lfitz> ?
[14:06] <dcordes> lfitz: so you got anywhere with the clean reinstall ?
[14:26] <sechrist> dcordes: I'm having weird issues where I can't access the internet inside my chroot, but I can outside
[14:27] <sechrist> I mounted the various system endpoints and stuff too.. no idea
[14:27] <tmzt_> probably dns
[14:27] <sechrist> no
[14:27] <sechrist> pinging <IP_ADDRESS> fails
[14:27] <tmzt_> copy /etc/resolv.conf
[14:27] <tmzt_> hmm
[14:27] <sechrist> "operation not permitted"
[14:27] <sechrist> not dns
[14:27] <tmzt_> ah
[14:27] <tmzt_> you don't have root?
[14:27] <sechrist> of course I have root
[14:27] <tmzt_> weird
[14:27] <sechrist> https://gist.github.com/0df5ac2f27bf0c7cfb30
[14:28] <tmzt_> strace
[14:28] <sechrist> I don't have strace in the chroot but i'll try and copy the one I have over
[14:28] <dcordes> sechrist: I have hada similar problem in karmic where I could not user network interfaces as non privileged user. this was native rather than chroot
[14:28] <dcordes> s/user/use/
[14:29] <sechrist> straced
[14:29] <sechrist> added as comment to gist above
[14:29] <sechrist> O.o @ that
[14:30] <sechrist> umoven input/output error
[14:30] <sechrist> hm
[14:31] <sechrist> so it's a ptrace problem?
[14:36] <sechrist> oooh it's not that
[14:36] <sechrist> it's getuid32 failing
[14:36] <sechrist> wt
[14:38] <sechrist> oh, no, meh
[14:39] <dcordes> sechrist: did you do lucid lynx tarball with rootstock ?
[14:39] <sechrist> nah this is armv6
[14:39] <sechrist> it's 9.10.2
[14:40] <sechrist> ubuntu-9.10.2-minimal-armel to be exact I guess
[14:40] <sechrist> I extracted the rootfs tarball and just mounted it
[14:40] <dcordes> aight
[14:40] <sechrist> I didn't need to provision it or anything right?
[14:40] <sechrist> it's not like I was booting off of it
[14:41] <dcordes> just wondering cause I have severe problems creating tarballs with roostock with anything > karmic
[14:41] <sechrist> v6 device running v7 code?
[14:41] <sechrist> oh
[14:41] <sechrist> creating
[14:41] <sechrist> nv,
[14:57] <sechrist> mystery solved
[14:57] <sechrist> permissions error
[14:57] <sechrist> some critical shit was owned by my macbook user
[14:57] <sechrist> doh
[14:58] <tmzt_> did you post an strace?
[14:58] <tmzt_> I think I know the issue but I'd like to confirm
[14:58] <sechrist> https://gist.github.com/0df5ac2f27bf0c7cfb30
[14:58] <sechrist> several
[15:00] <sechrist> dude I am totally apt-get installing on a kindle. huuah
[15:00] <tmzt_> I think it wasn't able to read either /etc/resolv.conf or other /etc/ file or a required lib because of the permissions issue
[15:00] <sechrist> most likely a lib
[15:01] <sechrist> I did a few stats and went doh when I saw the userid owning the files was 503, so I did a find/exec loop
[15:44] <Jameswstubbs> ogra, Is this http://people.canonical.com/~ogra/mobile/ possible on armv6?
[15:53] <Jameswstubbs> I'd like to use it for iPhone port
[16:14] <GrueMaster> Jameswstubbs: The image you are referring to at ~ogra/mobile is specific to an Intel project over two years ago.  It is not arm based, it is lpia (Intel Atom/Poulsbo).
[16:16] <Jameswstubbs> Hm, Is there a list of the software/configs so I can check ports.ubuntu.com
[16:16] <Jameswstubbs> Maybe piece bits together
[16:18] <GrueMaster> Esentially, Jaunty is Armv5, Karmic is Armv6+vfp, and Lucid+ is Armv7+thumb2.
[16:18] <GrueMaster> I don'tknow what is in the original iPhone.  You might want to stick with debian.
[16:19] <GrueMaster> At least that way you can have access to the latest software but built for older hardware.
[16:19] <Jameswstubbs> I've just finished booting Karmic on the iPhone 3g, I'm wanting to choose a more appropriate wm before release,
[16:19] <Jameswstubbs> Considering matchbox
[16:19] <Jameswstubbs> But this is more attractive
[16:23] <gsnedders> The 3G is a Cortex A8, AFAIK
[16:23] <Jameswstubbs> armv6
[16:23] <gsnedders> Oh, it's only the 3GS that's Cortex A8
[16:24] <Jameswstubbs> Yep, i think iphone 4 is a4 or whatever it's called. Im only working on 2G and 3G atm
[16:24] <gsnedders> A4 is just a Cortex A8 impl
[16:25] <Jameswstubbs> I havn't looked into, I can't afford one
[17:35] <lfitz> hi, i can boot ubuntu on my sheevaplug from an sd card now...however i can not login, i followed this guide...
[17:36] <lfitz> http://plugcomputer.org/plugwiki/index.php/Ubuntu_9.0.4_Plug_Computer_Distribution#Building_a_rootfs_to_install_Ubuntu_on_an_SD_Card_or_USB_Drive
[17:36] <lfitz> at this section: '  sudo ./rootstock -f sheevaplug -l [username] -p nosoup4u -d jaunty --serial ttyS0 --seed ssh' i set my username to root
[17:37] <lfitz> with a temp password
[17:37] <lfitz> and i tried to login as root with the temp passwd and even the default password in that line and it says login incorrect...
[17:37] <lfitz> since the fs is on sd can i edit a text file such as /etc/passwd to add a new user/pass?
[17:37] <lfitz> or does it need to be done, once logged in...
[17:39] <lfitz> hi orga: the README in rootstock fs says to contact you here... or by email, are you around?
[19:53] <dcordes> lfitz: can you share how you came over the can't extract kernel Image problem ? was the reason you did not have a kernel image in /boot ?
[19:54] <dcordes> lfitz: ogra is busy fixing rootstock I guess :P
[19:54] <dcordes> lfitz: are you 100% sure you usin the same password you specified with the rootstock command ?
[20:34] <lfitz> dcordes:  100% sure
[20:35] <lfitz> it worked initially, on the first attempt...but when i tried to switch to root i got an error 'setuid root'
[20:35] <lfitz> or whenever i tried to sudo i got that error
[20:36] <lfitz> dcordes:  i switched from ext3 to ext2 because i only had one partition
[20:36] <lfitz> the command to boot is ext2load
[20:36] <lfitz> so i figured ext2 fs would be best
[20:36] <lfitz> basically /boot needs to be ext2
[20:37] <dcordes> I see
[20:37] <dcordes> so that was the source of the unable to uncompress image erorr ?
[20:37] <lfitz> im not sure....but i think thats the only thing i changed...
[20:38] <lfitz> i would rewrite the section in the plugwiki about using rootstockfs, its missing a few words (not meaning to insult anyone) but its a little hard to follow
[20:39] <dcordes> go for it that's why it's a wiki
[20:39] <lfitz> but thats not ubuntu-arm... its at plugwiki / ubuntu 9.04
[20:39] <lfitz> oh
[20:39] <lfitz> alright :)
[20:40] <dcordes> I've been asking you so that others can contribute when they read the logs of this channel
[20:40] <dcordes> foss we are doomed to work toegether
[20:40] <lfitz> okay, thats a good idea :)
[20:41] <dcordes> so to get back to your login problem
[20:41] <lfitz> i will try to write the rootfs from scratch for sheevaplug entirely :)
[20:41] <dcordes> I've had the exact same problem
[20:41] <dcordes> with lucid lynx rootstock
[20:41] <lfitz> no way! :P
[20:41] <dcordes> it is specific to rootstock
[20:42] <dcordes> and seems to exist across different versions
[20:42] <lfitz> i switched the sd card into my laptop and tried chrooting to it so i could add users
[20:42] <lfitz> but that didnt work either
[20:42] <dcordes> yxou don't need to  chroot
[20:42] <lfitz> no exec error
[20:42] <dcordes> you can spare the chroot part
[20:42] <dcordes> just mount he rootfs
[20:42] <dcordes> and copy the passwd and groups etc from your known work ubuntu rootfs.
[20:43] <dcordes> shadow
[20:44] <lfitz> /etc/passwd, /etc/group, /etc/shadow?
[20:46] <dcordes> yeap
[20:48] <lfitz> okay that works, however it only works for one user the primary user and not the root account
[20:48] <lfitz> and it logins then quickly logs out
[20:48] <lfitz> could it be because i dont have a /home/dir
[20:51] <dcordes> lfitz: what is it ?
[20:51] <lfitz> um, i copied the /etc files you mentioned
[20:51] <lfitz> but the /home/username directory on the sd cards dont exist..yet
[20:52] <dcordes> I mean, you logging in on the text terminal or graphical ?
[20:52] <lfitz> text...screen
[20:53] <dcordes> ok it worked for me w/o /home/username
[20:53] <dcordes> just got warning
[20:53] <lfitz> i get the default log in message
[20:53] <lfitz> but then im asked for my password again
[20:53] <lfitz> username and password*
[20:56] <lfitz> dcordes:  ^^
[20:57] <dcordes> I hate roostock
[20:57] <dcordes> I mean it's not a bad concept
[20:57] <dcordes> but needs much love
[20:57] <dcordes> spent way too much time wit it this week
[20:58] <lfitz> any idea how to get the default ubuntu image back?
[20:58] <dcordes> lfitz: ask #ubuntu
[20:58] <lfitz> okay, thanks
[20:58] <lfitz> thank you for the help
[20:58] <lfitz> !
[20:58] <dcordes> the cause of the problem is specific to rootstock
[20:58] <dcordes> or the arm repos...
[20:59] <dcordes> but way to solve it is generic so you can go ask anywhere
[20:59] <dcordes> no problem
[20:59] <dcordes> you welcome
[20:59] <dcordes> what do you mean get default ubuntu image back ?
[21:08] <lfitz> dcordes:  the plug ships with ubuntu installed
[21:08] <lfitz> but i think i bricked it just now
[21:08] <lfitz> :X
[21:09] <dcordes> put your cheepoplug in the trashcan and get something decent like new gumstix
[21:15] <zumbi> armin76: remember where i used to work? right by us are developing a new product based on igepv2 :)
[21:32] <Jameswstubbs> How do use apt-cache with rootstock?
[21:40] <michaelh1>  Jameswstubbs: I've used rootstock with apt-cacher-ng quite happily...
[21:40] <michaelh1> (oh, sorry, wrong tool)
[21:40] <Jameswstubbs> Do you just install apt-cache on host machine?
[21:40] <Jameswstubbs> Anything else need to be done?
[21:41] <Jameswstubbs> I spent 6 hours making a ubuntu-rootfs only to accidently format my image :p
[21:42] <michaelh1> What would you like to achieve?
[21:43] <Jameswstubbs> To not need to download all the dpkg's over and over again
[21:43] <Jameswstubbs> I might just make a backup of the tarball this time
[21:44] <michaelh1> Ah.  A couple of options - use --copy-package-cache/--save-package-cache, or use a APT proxy like apt-cacher-ng
[21:45] <michaelh1> I use the latter and am quite happy with it.  Set http_proxy and /etc/apt/apt.conf.d/proxy to point to the cache and the rest just flows...
[21:48] <Jameswstubbs> Ah thank you :) I think i'll use --copy-package-cache


[04:43] <hk> where's the XMir code hosted?
[05:30] <mlankhorst> mirning
[05:31] <mlankhorst> support mir as a backend for plymouth is INPROGRESS, is there anyone actively working on it? sounds like a fun little item for me to get started in mir
[09:02] <mlankhorst> racarr_:         AC_DEFINE(XMIR, 1, [Support wayland mode])
[09:02] <mlankhorst> er RAOF_*
[13:07] <mlankhorst> ohey plymouth sort of works
[13:08] <mlankhorst> Mesa 9.2.0 implementation error: unhandled format!
[13:08] <mlankhorst> Please report at https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa
[13:14] <mlankhorst> http://testbot.winehq.org/~mlankhorst/plymouth-mir-wip-1.patch -- not complete yet, just a WIP
[15:51] <robert_ancell> thomi, is there a way to recompile unity-system-compositor every time mir changes?
[15:52] <robert_ancell> i.e. recompile the package in the PPA
[15:52] <thomi> robert_ancell: hmmmmm - you want to rebuild because of API/ABI changes?
[16:59] <robert_ancell> thomi, yes
[16:59] <robert_ancell> thomi, we just set the mirserver API to always require recompiling as it doesn't have any API/ABI stability at the moment
[17:09] <thomi> robert_ancell: I'll ask Francis, I don't think there's any easy way (although we could hack something up pretty easily).
[17:09] <robert_ancell> thomi, ta
[17:12] <thomi> robert_ancell: so the full story is that this is what the MBS is designed to solve (we use it for unity). It needs to be integrated with the new autolanding stuff
[17:12] <thomi> robert_ancell: but we can hack a jenkins job to do that. However, there are a few edge cases to think about, like what to do when the dependant package fails to build
[17:12] <thomi> so right now we'll just do the best we can - if anything fails to build it just won't get dput'd
[17:12] <bschaefer> robert_ancell, https://launchpad.net/~brandontschaefer/+archive/sdl-mir-support
[17:32] <RAOF> Dear GLX: I hate you.
[18:00] <robert_ancell> RAOF: From GLX. I apologize if I have offended you but I'm old and I just don't understand what you crazy kids are doing
[18:01] <mlankhorst> RAOF: oh btw could you peek at my plymouth mir wip patch?
[18:01] <robert_ancell> bschaefer, you should probably use version 2.0.0-0ubuntu1~mir1 so it's less than the official 2.0.0 release
[18:02] <robert_ancell> bschaefer, I mean 2.0.0-0ubuntu1+mir1
[18:02] <mlankhorst> I only tested on the mir demo server with input explicitly disabled, I still use raw console handling for input for now
[18:02] <robert_ancell> bschaefer, actually, disregard that. Now I understand
[18:03] <RAOF> mlankhorst: Sure. Where is it?
[18:04] <bschaefer> robert_ancell, alright, :)
[18:04] <mlankhorst> above^
[18:04] <mlankhorst> http://testbot.winehq.org/~mlankhorst/plymouth-mir-wip-1.patch
[18:04] <mlankhorst> it doesn't work correctly yet since it assumes that last buffer == current buffer
[18:05] <mlankhorst> so it doesn't do a full redraw, and mir_demo_server was complaining "Mesa 9.2.0 implementation error: unhandled format!"
[18:05] <robert_ancell> thomi, can we get u-s-c to rebuild now? Or shall I just do a trivial merge?
[18:05] <thomi> robert_ancell: sure, I'll trigger it manually
[18:06] <RAOF> mlankhorst: Got a patch that isn't full of automake droppingsz/
[18:06] <RAOF> ?
[18:06] <mlankhorst> RAOF: no sorry :(, plugins/renders/mir and configure.ac is the meat
[18:07] <robert_ancell> bschaefer, what branch are you working on libsdl?
[18:08] <thomi> robert_ancell: running now - http://<IP_ADDRESS>:8080/view/Generic%20jobs/job/generic-dput/1189/console
[18:08] <bschaefer> robert_ancell, I don't have the actual source pushed up but i moved over to using this version: http://hg.libsdl.org/SDL/
[18:09] <robert_ancell> bschaefer, just a local checkout?
[18:09] <bschaefer> yeah, I grabbed it changed it, made a patch, patched the libsdl2 from saucy then uploaded the ppa
[18:09] <bschaefer> soo I suppose Im using the libsdl in the ppa from saucy
[18:10] <bschaefer> robert_ancell, https://launchpad.net/ubuntu/saucy/+source/libsdl2
[18:11] <RAOF> mlankhorst: Is plymouth wedded to VTs? Because that would ideally go away.
[18:11] <mlankhorst> RAOF: no, I just didn't get around to fixing the input stack yet
[18:12] <RAOF> mlankhorst: Also, I think you're calling mir_surface_next_buffer_sync in the wrong place - you should call it *after* doing your drawing.
[18:12] <alan_g> robert_ancell: kdub is still testing android on https://code.launchpad.net/~afrantzis/mir/remove-in-tree-glm/+merge/162174
[18:12] <RAOF> mlankhorst: We're thinking of renaming it as mir_surface_swap_buffers to make it more obvious ☺
[18:12] <mlankhorst> RAOF: Yeah I thought so, but the unaccelerated demo did it like that
[18:12] <RAOF> mlankhorst: Hm, so it does. I'll fix that :)
[18:12] <mlankhorst> this is just the work of me poking half a day at the mir demos and plymouth
[18:13] <mlankhorst> how many buffers are there in the sw case?
[18:13] <RAOF> 2
[18:13] <RAOF> Well, or more.
[18:13] <RAOF> But 2 by default.
[18:13] <RAOF> And we don't currently expose any way to get anything but 2.
[18:14] <mlankhorst> is there any guarantee? I was thinking of just keeping track of the damage to last buffer and merge it with damage to current buffer
[18:14] <RAOF> You get buffer age :)
[18:14] <mlankhorst> ok
[18:15] <mlankhorst> I'll look at it monday then :)
[18:15] <RAOF> I'm not sure if we'll guarantee that the number of buffers will never exceed n, for a client-sent value of n.
[18:16] <mlankhorst> shrug buffer age is probably good enough
[18:16] <mlankhorst> if it's > 1 I'll just redraw the entire screen
[18:16] <RAOF> It'll always be > 1 (it'll almost always be 2).
[18:17] <mlankhorst> ok ok, I'll poke it a bit more before I shout random stuff again ;P
[18:17] <RAOF> Because the buffer you've just drawn to will have age = 1 right after you've called next_buffer (see the EGL_EXT_buffer_age spec for further details ☺)
[19:14] <thomi> robert_ancell: maybe you noticed already, but the u-s-c package is in the staging PPA now