[06:18] <sub526> Hello all, when I tried to install a package via sudo apt install <pkg>, it prompted this message: "E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem". So I triggered 'sudo dpkg --configure -a' and the system went to reboot. Prior to reboot the kernel log has above two suspicious messages. I can
[06:18] <sub526> consistently reproduce the reboot on triggering 'sudo dpkg --configure -a', what could be the issue?
[09:28] <gokhani> Hello folks, ı am getting kernel error on syslog like > Feb  5 08:48:49 compute06 kernel: [49829.229272] xs_tcp_setup_socket: connect returned unhandled error -107. what does it mean can you help me please ? I am using ubuntu 18.04 and kernel version is 5.4.0-65 generic
[10:05] <TJ-> gokhani: #define ENOTCONN        107     /* Transport endpoint is not connected */
[10:11] <gokhani> TJ- does it mean there is a problem on my network cards ?
[10:18] <TJ-> gokhani: not entirely sure but would suggest the link isn't up (depending on how "transport" is interpreted)
[11:01] <gokhani> thanks TJ- . Is there anyway or debug mode to find which link isn't up ?
[17:00] <cascardo> are you using nfs?
[17:36] <gokhani> cascardo yes I am using nfs
[18:24] <cascardo> that is related to nfs, one possible reasons for cause would be the use of port 0, not sure how that happens
[18:24] <cascardo> it could just as well be totally unrelated to the reboot issue you are seeing
[18:25] <cascardo> what package is being configured at the time of the reboot? like, what are the last lines of dpkg right before it reboots?


[06:07] <oSoMoN> good morning desktoppers
[06:47] <luna> morning
[06:53] <jibel> Good morning folks
[06:58] <duflu> Hi oSoMoN, luna, jibel
[07:01] <didrocks> good morning
[07:02] <duflu> Hi didrocks
[07:03] <seb128> goood morning desktopers
[07:03] <seb128> lut didrocks, hey duflu, how are you?
[07:04] <didrocks> hey duflu, seb128. Good, and you?
[07:05] <luna> https://cdimage.ubuntu.com/daily-live/20220511.1/ Kinetic Daily images starts rolling
[07:05] <luna> gonna install and test later today
[07:10] <duflu> seb128, going OK. You?
[07:11] <seb128> duflu, I'm already thanks! went to tennis yesterday but had to stop after being rained on for an hour, which is frustrating because it was quite nice and sunny during the day, and we are back to blue sky this morning
[07:11] <seb128> already->alright
[07:12] <seb128> (and not awake yet it seems, I had to wake up earlier to prepare a bunch of fruit skewers for a kid's party)
[07:23] <luna> doing a test install in Virtualbox now
[08:09] <rastersoft_> hi again
[08:27] <duflu> Hi Rastersoft
[08:45] <bittin> hi
[08:51] <duflu> Hi bittin
[08:53] <bittin> my 22.10 daily install went well in Virtualbox, but not much changed from 22.04 yet :p
[10:28] <sil2100> Hey desktop-team! I saw the canary image FTBFS today, due to the fact that ppa:ubuntu-desktop/canary-image has no kinetic packages in it
[10:29] <sil2100> Could someone push a dummy package there to get a Release file generated for the archive?
[10:29] <sil2100> This should unblock the build
[10:36] <seb128> sil2100, hey, thanks for pointing that out, it should be fixed now ... can you trigger an ISO build to check?
[10:47] <KGB-2> gnome-remote-desktop Sebastien Bacher 308402 * commented merge request !2 * https://deb.li/HPyx
[11:04] <jbicha> good morning
[11:16] <nteodosio> jbicha, good morning
[11:17] <jbicha> nteodosio: hi, how is it going?
[11:18] <nteodosio> jbicha pretty well, thanks!, same with you?
[11:19] <jbicha> pretty good, gnome-remote-desktop has been frustrating me this week but I'm making progress 🙂
[11:20] <nteodosio> Good to hear that!
[11:20] <nteodosio> Well, the last part of that anyway :)
[14:24] <Trevinho> oSoMoN: reviewing that portal situation is quite bad all over the places... While one option is to make the shell, mutter and probably other places to handle the `.snap` prefix, we're still not handling well the snaps case with multiple apps, so I'm assuming that portals have many broken functionalities when it comes to cross-apps / shell interactions, as everyone is assuming to have a desktop-ID == applicationId
[14:28] <oSoMoN> Trevinho, so the proper solution is to modify all the portals to pass a desktop ID to the access requests they issue, right?
[14:28] <Trevinho> this is also an huge problem when it comes to GApplications because the application ID should also be used to figure out the application's `org.freedesktop.Application`'s path/iface, and so  lots of assumptions around simply don't work
[14:28] <Trevinho> yeah, I'm playing with something like that, but then we've still the GApplication case mentioned above, that won't never work.
[14:31] <Trevinho> I started from looking at GIO notifications some days ago, trying to figure out how to make them play nicely... And those are an easy case because we could just provide a different module implementation for the GNOME-sdk based snaps, but there may be other tons of places were we'll be just broken
[14:33] <Trevinho> so I basically opened a can of worms... We definitely need to find a way to make GApplication's play nicely in snaps without loosing their expected path, unless we want to be evil and change GLib implementation to use something like snap.snap_name.snap_instance as their well known name
[14:33] <Trevinho> this is relevant because a portal may want request to activate an  application Action... Now if we don't know how to reach it through dbus, we're screwed


[15:33] <SpecialK|Canon> https://code.launchpad.net/~doismellburning/launchpad/+git/launchpad/+merge/385644 - my og_title assert is failing and it's not yet clear to me if my template code is wrong or I should be poking makeTemplateView to inject more info - would appreciate feedback please
[15:33] <SpecialK|Canon> (both specific and general!)
[15:34] <cjwatson> SpecialK|Canon: What's the error message?
[15:35] <SpecialK|Canon> cjwatson: `testtools.matchers._impl.MismatchError: 'http' not in None`
[15:35] <SpecialK|Canon> presumably because `request/URL` is None
[15:35] <cjwatson> I normally write more like content.find('meta', property='og.title'), but your syntax should work too
[15:35] <cjwatson> request/URL is used in og:url rather than og:title though
[15:35] <SpecialK|Canon> cjwatson: property is a builtin in some modern Pythons though
[15:35] <SpecialK|Canon> cjwatson: hence I went for the dict
[15:36] <cjwatson> Ah yeah, fair point
[15:36] <SpecialK|Canon> (otherwise I would have)
[15:36] <cjwatson> "modern" :)
[15:36] <SpecialK|Canon> bah sorry, og_url not og_title
[15:37] <SpecialK|Canon> https://pastebin.canonical.com/p/y7S2VGN6YQ/ in full
[15:37] <SpecialK|Canon> https://pastebin.ubuntu.com/p/DFWsYspMcf/ even
[15:38] <SpecialK|Canon> very few things declare recommended_canonical_url, fine (I do mean to add tests for some of those later)
[15:38] <cjwatson> Mkay, having a look
[15:38] <cjwatson> I think soupmatchers would make this clearer FWIW
[15:39] <cjwatson> I always like composite tests to test as much as they can at once, because it means you get better error messages
[15:43] <SpecialK|Canon> Hm that does look interesting
[15:44] <cjwatson> request/URL should evaluate to http://launchpad.test here, since that's what makeTemplateView sets up ...
[15:45] <SpecialK|Canon> That's what I assumed; I'm struggling to find much in the way of docs about `request` though
[15:45]  * cjwatson sets a breakpoint on recommended_canonical_url
[15:45] <cjwatson> It's a LaunchpadTestRequest in this case
[15:46] <SpecialK|Canon> https://zope.readthedocs.io/en/latest/zopebook/AppendixC.html#tales-overview helpfully tells me it's a thing, but not much more
[15:46] <SpecialK|Canon> Ah
[15:46] <SpecialK|Canon> ...yes in hindsight it is, isn't it
[15:47] <cjwatson> Which is a thin layer over https://zopepublisher.readthedocs.io/en/latest/browser_api.html#zope.publisher.browser.TestRequest
[15:50] <cjwatson> As for template language docs, I generally point at https://pagetemplates.readthedocs.io/en/latest/ instead of that old Zope 2 doc
[15:51] <SpecialK|Canon> Digging a little more I suspect I may instead want view/url or context/url based on other usages, but I've not yet found anything definitive
[15:51] <SpecialK|Canon> Ah thanks
[15:52] <cjwatson> Ah
[15:53] <cjwatson> SpecialK|Canon: alternate expressions after | only get evaluated if the previous expressions *fail*, not just return None
[15:53] <SpecialK|Canon> Well, https://pagetemplates.readthedocs.io/en/latest/history/TutorialPart2.html?highlight=view%2Furl#inserting-text uses request/URL, but I'm still not clear on the exact different semantics
[15:53] <cjwatson> SpecialK|Canon: Try "python: view.recommended_canonical_url or request.URL" instead
[15:53] <SpecialK|Canon> cjwatson: ...that'll do it, thanks
[15:55] <SpecialK|Canon> hurrah, cheers :)
[16:13] <tomwardill> hopefully make css generation repeatable enough: https://code.launchpad.net/~twom/launchpad/+git/launchpad/+merge/385678
[16:13] <tomwardill> note, this disables compressed output for now, it makes the file ~80K bigger, but it's a single file that is then cached
[16:13] <tomwardill> but means SASS leaves the comments in, so I can work out which file is which!
[16:14] <tomwardill> I'll re-enable compressed output when this bug is confirmed fixed
[16:15] <cjwatson> Will you be able to compare between qastaging/staging/dogfood or something?
[16:15] <cjwatson> r=me anyway
[16:15] <tomwardill> that's the hope, yes
[16:16] <tomwardill> we have enough environments that build this that I can see if we get consistent results from it
[16:16] <tomwardill> I kind of dislike that we have rules that are dependant on the ordering of the filesystem
[16:16] <tomwardill> (apparently)
[16:19] <cjwatson> Yes, we clearly shouldn't
[16:21] <tomwardill> hopefully this will fix it for now, a better fix would probably be to create a SCSS _index file and use that rather than the jsbuild mechanisms
[16:23] <cjwatson> Yeah
[16:23] <cjwatson> Bah, another buildbot failure due to me
[16:33] <cjwatson> https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/385680 - quick testfix review?
[16:37] <tomwardill> looking
[16:38] <tomwardill> cjwatson: +1
[16:38] <cjwatson> cheers
[16:45] <cjwatson> I think that's about all the useful stuff I'm going to get done today.  Have a good weekend
[16:47] <SpecialK|Canon> cjwatson: you too!
[16:47] <SpecialK|Canon> https://code.launchpad.net/~doismellburning/launchpad/+git/launchpad/+merge/385644 if anyone's still around...?
[16:50] <tomwardill> mind blanked, what's the env var I need to use lp-shell with a local instance?
[16:50] <tomwardill> disables the SSL validation
[16:52] <tomwardill> LP_DISABLE_SSL_CERTIFICATE_VALIDATION=
[16:52] <tomwardill> that would do it
[16:56] <SpecialK|Canon> so https://dev.launchpad.net/Running - presumably "Point your usual web browser at https://launchpad.test, and accept the local self-signed certificate." predates "it is advisable to try Launchpad in an LXC/LXD container"
[16:57] <cjwatson> Probably, but I don't get the connection
[16:58] <SpecialK|Canon> is there anything more modern somewhere else?
[16:58] <cjwatson> What is your objection?
[16:58] <SpecialK|Canon> cjwatson: well the latter means that doing the former won't achieve much
[16:58] <cjwatson> Not so
[16:58] <SpecialK|Canon> cjwatson: because I'm running LP in a container
[16:58] <cjwatson> Works fine
[16:59] <cjwatson> You do have to follow the link to https://dev.launchpad.net/Running/RemoteAccess
[16:59] <SpecialK|Canon> and my host is not aware of launchpad.test
[16:59] <SpecialK|Canon> Right
[16:59] <cjwatson> It will be if you do the stuff in Running/RemoteAccess :)
[16:59] <cjwatson> Running may just need to be reordered a bit
[17:00] <SpecialK|Canon> "Works fine" *if* you have read some as-yet-unmentioned docs is...a stretch ;P
[17:00] <cjwatson> Yeah, I hadn't noticed that RemoteAccess is actually mentioned further down the page
[17:00] <SpecialK|Canon> But yes, thanks for the pointer, I'll rejig that a bit
[17:00] <cjwatson> A few people have been through the docs without mentioning that :)
[17:01]  * tomwardill always reads the entire paper before answering questions ;)
[17:01] <tomwardill> https://code.launchpad.net/~twom/launchpad/+git/launchpad/+merge/385683 add gitrepository.id to the API
[17:01] <cjwatson> Good catch that it's misordered though
[17:01] <tomwardill> (one of my previous statements is a complete lie)
[17:02] <tomwardill> I think at least myself and pappacena were given both links at the same time, so it's less obvious
[17:02] <cjwatson> Could be
[17:03] <cjwatson> https://dev.launchpad.net/Running/LXD also emphasises it a bit at the end
[17:03] <cjwatson> Anyway, not here :)
[17:03]  * tomwardill -> also not here, before dog eats anything else he's not meant to because I haven't fed him yet
[17:06] <SpecialK|Canon> Cheers :)
[17:06] <SpecialK|Canon> Have good weekends!


[09:44] <hydro-b> Hi there. I'm trying to install ubuntu with autoinstall in a IPv6 only environment. This used to work fine with d-i / preseed, but I'm trying to convert it to the newish autoinstall way of life. There is a ISC dhcpv6 server active (configured simlarly to https://wiki.ubuntu.com/UEFI/SecureBoot/PXE-IPv6). IPv6 RAs also working. I made a first attempt on a user-data cloud-init config
[09:44] <hydro-b> (https://pastebin.ubuntu.com/p/Vvx7HxGKgw/). I can see in the webserver logs that the file (and meta-data / vendor-data, both empty files) are downloaded. However, the autoinstall does not start. The installer stops with a prompt: "choose type of install". Note, I have added the kernel cmdline option "autoinstall": https://pastebin.ubuntu.com/p/TnJC4CvYf5/.
[09:46] <hydro-b> So I'm running into a few issues actually. 1) I would like to avoid "ip=dhcp" ... or hint that the live-server skips trying dhcpv4 ... and only uses dhcp6. However, dhcp6 i not recognized (ISC dhcp client will give an error about this)
[09:46] <hydro-b> currently it takes 5 minutes for the first round of DHCP timeouts
[09:48] <hydro-b> Then an attempt is made to actually load the iso ... which works fine (over IPv6) ... then another round of DHCPv4 timeouts ... and after that the installer is started and cloud-init config files are downloaded
[09:50] <hydro-b> So, one question I have, where can I check if the cloud-init config file that is downloaded is actually parsed / used?
[09:51] <hydro-b> I've learned that after a manual install, a "/var/log/installer/autoinstall-user-data" should be created. Hence I thought I would try a manual install. But then I run into some other issues ...
[09:57] <hydro-b> The first is network configuration. The installer lets me configure dhcpv6 (and disable dhcpv4), which is great. However, although it succesfully managed to get an IPv6 address, has working IPv6 internet connectivity, resolving does not work. So in the next step (Configure ubuntu archive mirror) it fails to resolve the mirrors. Sidenote: I found in the installer logs that a geoip check is tried, but
[09:57] <hydro-b> it is not working either, as geoip.ubuntu.com does not have a quad A record set. I know for sure the DHCPv6 server hands out a nameserver (it works fine with dhclient in an initramfs). So the systemd stub-resolver is not configured to try lookups via IPv6 (haven't checked the config, but that is what I suspect).
[09:57] <hydro-b> that's easy to configure by removing the symlink to the stub resolver and manually enter the nameserver entry in /etc/resolv.conf ... resolving works ... up to the next step
[09:57] <mwhudson> hydro-b: to check if the autoinstall / cloud-init config is found, looking in /var/lib/cloud-init.log would be a good start
[09:58] <hydro-b> mwhudson: ah, I will check right away
[09:58] <mwhudson> the name resolution stuff sounds like a bug, i don't have much experience in ipv6-only environments
[09:58] <hydro-b> mwhudson: I'm used to find IPv6 only bugs ;-)
[09:58] <mwhudson> hydro-b: we are going to try to make it more obvious when cloud-init has issues
[10:00] <hydro-b> that would be great. There has been a lot of advancements in this area (cloud-config, autoinstall, their interaction). It probably works awesome if you know all the moving parts work
[10:00] <hydro-b> /var/lib/cloud-init.log <- this file does not exist
[10:01] <hydro-b> I think I found it
[10:02] <mwhudson> sorry /var/log
[10:02] <hydro-b> /var/log/cloud-init.log does exist
[10:02] <mwhudson> it is late here :)
[10:02] <hydro-b> haha, appreciate your time
[10:05] <hydro-b> 023-10-19 09:24:29,167 - util.py[WARNING]: Failed loading yaml blob. Invalid format at line 34 column 16: "mapping values are not allowed here
[10:05] <hydro-b>   in "<unicode string>", line 34, column 16:
[10:05] <hydro-b>       late-commands:
[10:06] <hydro-b> I used the "autoinstall-generator" to convert from preseed ... but apparently it's inserting statements that are not allowed
[10:06] <hydro-b> I'll try to strip it down to bare minimum for now
[10:08] <hydro-b> and try again
[10:08] <hydro-b> And I'll file a bug for the nameserver resolving issue
[10:12] <mwhudson> hydro-b: yeah that kind of error is what we need to expose in the ui
[10:35] <hydro-b> mwhudson: is there a way with the intaller to configure UEFI partitions (vfat)? I seem to only be able to choose ext4, btrs, xfs, swap
[11:01] <bdrung> @pilot in
[13:17] <ahasenack> coreycb: hi, I'm about to release cinder into lunar, and was wondering about your test results in https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/2037319/comments/4
[13:17] -ubottu:#ubuntu-devel- Launchpad bug 2037319 in cinder (Ubuntu Lunar) "[SRU] antelope stable releases" [High, Fix Committed]
[13:17] <ahasenack> you say you used 2:22.1.1-0ubuntu1~cloud0, but that's from the cloud archive I suppose, not lunar-proposed
[13:18] <ahasenack> coreycb: could you please confirm in the bug if lunar-proposed is verified, or just cloud-archive?
[13:20] <coreycb> ahasenack: thanks for taking a look. it should have results for lunar above that (including package version from lunar-proposed). let me know if it needs clarification.
[13:20] <ahasenack> coreycb: ah, you are right, I skimmed to the end of the comment and only saw the UCA version
[13:20] <ahasenack> but in the middle of the comment you also mentioned the lunar version
[13:20] <ahasenack> my bad
[13:20] <ahasenack> all good
[16:35] <bdrung> @pilot out
[17:14] <amikhalitsyn> Dear friends, I need advice regarding fixing the LXC package in Ubuntu Jammy. I've filled a bug https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873 but as far as I understand I need someone from the SRU team to make that. And nobody in my team (LXD) do not have enough permissions to update packages.
[17:14] -ubottu:#ubuntu-devel- Launchpad bug 2039873 in lxc (Ubuntu) "liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic" [Undecided, New]
[17:57] <kanashiro> @pilot in
[21:59] <kanashiro> @pilot out


[15:46] <tos9> Hey, I'm sure it's been asked/reported before, but anyone planning on uploading bzr to PyPI?


[10:39] <hk_> guys do i need to have ubuntu to build apps for it?
[10:43] <hk_> do i need to have ubuntu to build apps for it?
[14:06] <asante002> h
[14:06] <asante002> j
[21:43] <ashams> Hey AhmedAbouZaid, best wishes
[21:46] <AhmedAbouZaid> Thanks ^^
[21:54] <hggdh> ~ô~
[21:58] <annod> السلام عليكم
[21:59] <asultan> and peace be with you
[21:59] <blablabla> w 3alekom Al salam w ra7mat Allah w barakato
[22:00] <Samar_> Peace be upon you
[22:00] <cjohnston> #startmeeting
[22:00] <meetingology> Meeting started Thu Jan  3 22:00:59 2013 UTC.  The chair is cjohnston. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[22:00] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[22:01] <cjohnston> #chair cjohnston
[22:01] <meetingology> Current chairs: cjohnston
[22:01] <cjohnston> #voters cjohnston hggdh cyphermox PabloRubianes
[22:01] <meetingology> Current voters: PabloRubianes cjohnston cyphermox hggdh
[22:01] <cjohnston> #topic Ubuntu  Membership Review Board - 3 January 2013
[22:01] <cjohnston> Hello and welcome to the Ubuntu Membership Review Board meeting for 3 January 2013. The wiki page for the Review Boards are available here: https://wiki.ubuntu.com/Membership/Boards
[22:01] <cjohnston> We will attempt to get through all of the applicants that have added themselves to that list before today's meeting. If we are unable to make it through the entire list due to time constraints, then at the next meeting we will pick up where we left off.
[22:01] <cjohnston> The format for the meeting is as follows: We will go through the list of applicants one by one, by date of application (FIFO).
[22:02] <cjohnston> Each applicant should introduce themselves (1-5 sentences) and provide links to their Ubuntu Wiki page. After the introduction the members of the Membership Review Board will review the pages and, if needed, ask the applicant further questions.
[22:02] <cjohnston> During this time it is encouraged for other members of the community to show their support for the applicant. Do not be alarmed if the members of the Membership Review Board are quiet during this time; they are most likely reading wiki/launchpad/forum/other pages and deciding how they are going to vote.
[22:02] <cjohnston> When the board is ready to vote, they will publicly vote in the channel with either +1, 0, or -1 (for membership, abstain, and against membership, respectively). If the sum of those numbers is positive, then the applicant is now an official Ubuntu member! (feel free congratulate them!)
[22:02] <cjohnston> Now, with any further ado, lets get started with the first applicant...
[22:03] <cjohnston> I don't see the first applicant in here.. so I will go on to the second
[22:03] <cjohnston> Would someone mind checking to see if the first is online please?
[22:03] <hggdh> Abdobonna: there?
[22:04] <cjohnston> #topic AhmedAbouZaid 's membership application
[22:04] <cjohnston> AhmedAbouZaid: please introduce yourself
[22:04] <AhmedAbouZaid> Thanks cjohnston : )
[22:05] <AhmedAbouZaid> My name is Ahmed, I'm 23 years old, I live in Cairo.
[22:05] <AhmedAbouZaid> fully Ubuntu user since 2008
[22:06] <AhmedAbouZaid> I love and believe in Free/Open source  and Ubuntu  :)
[22:06] <cjohnston> AhmedAbouZaid: I don't see anything documented on your wiki page for the last year. What happened?
[22:07] <cjohnston> #voters iulian
[22:07] <meetingology> Current voters: PabloRubianes cjohnston cyphermox hggdh iulian
[22:08] <ashams> may I support AhmedAbouZaid ?
[22:08] <AhmedAbouZaid> cjohnston: I was to perform compulsory military service in Egypt.
[22:08] <AhmedAbouZaid> cjohnston: It's about 12 months.
[22:08] <hggdh> ah
[22:09] <AhmedAbouZaid> cjohnston: So my activity was very limited this year : )
[22:09] <cjohnston> understandable in that case
[22:10] <PabloRubianes> AhmedAbouZaid, nice work with the book, are you already working on the updated version?
[22:10] <AhmedAbouZaid> My wiki page: https://wiki.ubuntu.com/AhmedAbouZaid
[22:11] <cyphermox> AhmedAbouZaid: I see you mention bugs reporting on your wiki page, but I can't see any on your launchpad page. Do you report your bugs elsewhere?
[22:11] <AhmedAbouZaid> PabloRubianes: Yes, I'm working now on a second version of it.
[22:12] <iulian> AhmedAbouZaid: How do I download the book?
[22:12] <iulian> Or rather, could you please give me the direct link?
[22:13] <AhmedAbouZaid> cyphermox: Unfortunately most of the reports were not through launchpad.
[22:13] <AhmedAbouZaid> iulian: One moment please.
[22:13] <iulian> I think I got it.
[22:13] <iulian> You could still paste the link here just for the record.
[22:14] <AhmedAbouZaid> Book site: http://www.simplyubuntu.com/
[22:14] <AhmedAbouZaid> Download link: http://download.simplyubuntu.com/getit.php
[22:14] <cyphermox> AhmedAbouZaid: that's what I thought. Is it due to reporting the bugs in English?
[22:15] <hggdh> AhmedAbouZaid: thank you for publishing the book with (at least) an option for free download. I/we appreciate it
[22:16] <AhmedAbouZaid> cyphermox: I made bug reports either in English and Arabic.
[22:16] <cyphermox> yeah it's really nice :)
[22:16] <cyphermox> ok
[22:16] <cjohnston> #subtopic Voting on AhmedAbouZaid 's membership application
[22:16] <cjohnston> #vote Voting on AhmedAbouZaid 's membership application
[22:16] <meetingology> Please vote on: Voting on AhmedAbouZaid 's membership application
[22:16] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me)
[22:16] <hggdh> +1
[22:16] <meetingology> +1 received from hggdh
[22:16] <PabloRubianes> +1
[22:16] <meetingology> +1 received from PabloRubianes
[22:16] <cyphermox> +1
[22:16] <meetingology> +1 received from cyphermox
[22:16] <cjohnston> +1
[22:16] <meetingology> +1 received from cjohnston
[22:17] <Samar_> +1
[22:17] <iulian> +0 - was still reviewing.
[22:17] <meetingology> +0 - was still reviewing. received from iulian
[22:17] <asultan> :)
[22:17] <AhmedAbouZaid> hggdh: Thanks : )
[22:17] <cjohnston> Samar_: voting is limited to those on the board only.
[22:17] <AhmedAbouZaid> hggdh: And it's also licensed under CC: By-Sa 3.0 license : )
[22:17] <hggdh> Samar_: heh, only members of the RMB can vote ;-)
[22:17] <Samar_> Got it! :)
[22:17] <hggdh> AhmedAbouZaid: ooohhh, even better! Thank you very much!
[22:18] <cjohnston> #endvote
[22:18] <meetingology> Voting ended on: Voting on AhmedAbouZaid 's membership application
[22:18] <meetingology> Votes for:4 Votes against:0 Abstentions:1
[22:18] <meetingology> Motion carried
[22:18] <cjohnston> Congrats AhmedAbouZaid
[22:18] <hggdh> AhmedAbouZaid: welcome in!
[22:18] <ashams> AhmedAbouZaid, Congrats :D
[22:19] <cyphermox> Congrats AhmedAbouZaid
[22:19] <PabloRubianes> congrats AhmedAbouZaid
[22:19] <cjohnston> With that being said, since the other applicant still hasn't arrived I'm going to end the meeting.
[22:19] <PabloRubianes> +1 cjohnston
[22:19] <hggdh> yep
[22:19] <cjohnston> #endmeeting
[22:19] <meetingology> Meeting ended Thu Jan  3 22:19:31 2013 UTC.
[22:19] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-01-03-22.00.moin.txt
[22:19] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-01-03-22.00.html
[22:19] <cjohnston> Thanks all
[22:19] <AhmedAbouZaid> Thank You very much. It's indeed a pleasure ^_^
[22:20] <hggdh> AhmedAbouZaid: the pleasure is ours
[22:20] <asultan> AhmedAbouZaid gratz mate :)
[22:20] <asultan> @AhmedAbouZaid gratz mate :)
[22:20] <meetingology> asultan: Error: "AhmedAbouZaid" is not a valid command.
[22:21] <Samar_> Congratulations Ahmed :)
[22:21] <blablabla> congratulations ^^
[22:22] <AhmedAbouZaid> Thank you all ^_^


[00:28] <vorlon> oh look, other random blockers for perl that britney could've reported on earlier but didn't
[00:30] <vorlon> rolling back libgit-raw-perl to break the link to rust via libgit2
[00:44] <vorlon> except that doesn't work because libgit-raw-perl had been ftbfs since kinetic; so, removing instead!
[01:10] -queuebot:#ubuntu-release- New binary: haskell-yesod-auth-oauth [ppc64el] (lunar-proposed/universe) [1.6.1-1] (no packageset)
[01:11] -queuebot:#ubuntu-release- New binary: haskell-yesod-auth-oauth [s390x] (lunar-proposed/universe) [1.6.1-1] (no packageset)
[01:13] -queuebot:#ubuntu-release- New binary: haskell-yesod-auth-oauth [arm64] (lunar-proposed/universe) [1.6.1-1] (no packageset)
[01:14] -queuebot:#ubuntu-release- New binary: haskell-yesod-auth-oauth [armhf] (lunar-proposed/universe) [1.6.1-1] (no packageset)
[01:16] -queuebot:#ubuntu-release- New binary: haskell-copilot-libraries [armhf] (lunar-proposed/universe) [3.12-1build2] (no packageset)
[03:18] -queuebot:#ubuntu-release- New: accepted haskell-yesod-auth-oauth [armhf] (lunar-proposed) [1.6.1-1]
[03:18] -queuebot:#ubuntu-release- New: accepted haskell-yesod-auth-oauth [amd64] (lunar-proposed) [1.6.1-1]
[03:18] -queuebot:#ubuntu-release- New: accepted haskell-yesod-auth-oauth [ppc64el] (lunar-proposed) [1.6.1-1]
[03:18] -queuebot:#ubuntu-release- New: accepted haskell-yesod-auth-oauth [arm64] (lunar-proposed) [1.6.1-1]
[03:18] -queuebot:#ubuntu-release- New: accepted haskell-yesod-auth-oauth [s390x] (lunar-proposed) [1.6.1-1]
[07:04] <vorlon> FINALLY, gah
[07:12] <vorlon> graphicsmagick and libsys-virt-perl rolled forward again; autosync reenabled
[07:31] <LocutusOfBorg> vorlon, how big will you slap me if I syncpackage -f perl?
[07:42] <vorlon> LocutusOfBorg: it won't cause a new transition, but it will queue a bunch of autopkgtests.... queues are empty so I don't feel strongly
[07:43] <vorlon> oh ick ubuntu-dev-tools still depends on python?
[07:43] <LocutusOfBorg> :/
[07:43] <vorlon> (noted because reverse-depends is failing, and the traceback is python2.7 :P)
[07:43] <LocutusOfBorg> loooooool
[07:43] <LocutusOfBorg> perl syncd
[07:43] <vorlon> oh wait I'm running it on the wrong machine
[07:43] <vorlon> THAT EXPLAINS
[07:43] <vorlon> (both the python and the failure)
[07:44]  * LocutusOfBorg cancels the amd64 perl build
[07:44] <LocutusOfBorg> so we have time to let it build elsewhere
[07:46] <LocutusOfBorg> it would be nice to recreate lunar chroots now that perl migrated... this can save some time during build
[07:53] <vorlon> yes, I thought the original plan for doing launchpad builder chroots in launchpad was that they would be updated more frequently; but this hasn't happened.
[08:22] <LocutusOfBorg> in Debian it happens twice a week if I remember correctly
[08:23] <LocutusOfBorg> for riscv64 it might save 5m of build time...
[09:06] -queuebot:#ubuntu-release- Packageset: Added qtxdg-tools to lubuntu in lunar
[09:43] -queuebot:#ubuntu-release- Unapproved: linux-firmware (jammy-proposed/main) [20220329.git681281e4-0ubuntu3.7 => 20220329.git681281e4-0ubuntu3.9] (core, kernel)
[09:46] -queuebot:#ubuntu-release- Unapproved: linux-firmware (kinetic-proposed/main) [20220923.gitf09bebf3-0ubuntu1.1 => 20220923.gitf09bebf3-0ubuntu1.3] (core, kernel)
[09:47] <RikMills> ubuntu-archive: could someone kindly clean up the kdevelop old binaries? thanks
[09:47] <RikMills> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#kdevelop
[09:49] <cjwatson> RikMills: kdevelop59-libs removed from lunar-proposed
[09:49] <RikMills> thanks!
[09:52] <cjwatson> LocutusOfBorg,vorlon: they're much easier to refresh, which of course is not quite the same as being automatically refreshed.  I've just refreshed them
[09:53] <LocutusOfBorg> thanks!
[09:54] <LocutusOfBorg> maybe a weekly cronjonb might be useful?
[09:56] <cjwatson> In theory but we're not in a place right now where that's practical
[09:56] <cjwatson> The upgrade is still a bit too shonky (in particular needing to keep records for reverts)
[09:57] <cjwatson> And actually the CPC buildd images haven't quite caught up with the perl transition yet, so I'll need to do this again a bit later
[10:01] -queuebot:#ubuntu-release- New binary: golang-github-mdlayher-ethtool [amd64] (lunar-proposed/universe) [0.0~git20221212.d43b2a7-1] (no packageset)
[10:04] <LocutusOfBorg> maybe its better to redo once perl 5.36.0-6 is fully installed in proposed pocket
[10:31] -queuebot:#ubuntu-release- New binary: opensubdiv [amd64] (lunar-proposed/universe) [3.5.0-2] (ubuntustudio)
[10:52] -queuebot:#ubuntu-release- New binary: opensubdiv [riscv64] (lunar-proposed/universe) [3.5.0-2] (ubuntustudio)
[11:28] -queuebot:#ubuntu-release- New binary: opensubdiv [arm64] (lunar-proposed/universe) [3.5.0-2] (ubuntustudio)
[11:29] -queuebot:#ubuntu-release- New binary: opensubdiv [armhf] (lunar-proposed/universe) [3.5.0-2] (ubuntustudio)
[11:29] -queuebot:#ubuntu-release- New binary: opensubdiv [s390x] (lunar-proposed/universe) [3.5.0-2] (ubuntustudio)
[11:29] -queuebot:#ubuntu-release- New binary: opensubdiv [ppc64el] (lunar-proposed/universe) [3.5.0-2] (ubuntustudio)
[11:53] -queuebot:#ubuntu-release- New binary: bootstrap-icons [amd64] (lunar-proposed/none) [1.10.2+dfsg-1] (no packageset)
[12:14] -queuebot:#ubuntu-release- New binary: golang-google-grpc [amd64] (lunar-proposed/universe) [1.32.0-3] (no packageset)
[12:15] -queuebot:#ubuntu-release- Unapproved: rejected linux-firmware [source] (jammy-proposed) [20220329.git681281e4-0ubuntu3.8]
[12:15] -queuebot:#ubuntu-release- Unapproved: rejected linux-firmware [source] (kinetic-proposed) [20220923.gitf09bebf3-0ubuntu1.2]
[12:15] -queuebot:#ubuntu-release- New binary: golang-google-grpc [armhf] (lunar-proposed/universe) [1.32.0-3] (no packageset)
[12:15] -queuebot:#ubuntu-release- New binary: golang-google-grpc [s390x] (lunar-proposed/universe) [1.32.0-3] (no packageset)
[12:15] -queuebot:#ubuntu-release- New binary: golang-google-grpc [ppc64el] (lunar-proposed/universe) [1.32.0-3] (no packageset)
[12:17] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (kinetic-proposed) [20220923.gitf09bebf3-0ubuntu1.3]
[12:19] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (jammy-proposed) [20220329.git681281e4-0ubuntu3.9]
[12:38] -queuebot:#ubuntu-release- Unapproved: libmbim (jammy-proposed/main) [1.26.2-1build1 => 1.28.0-1~ubuntu20.04.1] (desktop-core, i386-whitelist)
[12:39] -queuebot:#ubuntu-release- Unapproved: libqmi (jammy-proposed/main) [1.30.4-1 => 1.32.0-1ubuntu<IP_ADDRESS>] (desktop-core, i386-whitelist)
[12:40] -queuebot:#ubuntu-release- Unapproved: modemmanager (jammy-proposed/main) [1.18.6-1 => 1.20.0-1~ubuntu22.04.1] (desktop-core, i386-whitelist)
[12:43] -queuebot:#ubuntu-release- Unapproved: tzdata (focal-security/main) [2022g-0ubuntu<IP_ADDRESS> => 2022g-0ubuntu<IP_ADDRESS>] (core) (sync)
[12:50] -queuebot:#ubuntu-release- New binary: golang-google-grpc [riscv64] (lunar-proposed/universe) [1.32.0-3] (no packageset)
[13:02] -queuebot:#ubuntu-release- Unapproved: accepted tzdata [sync] (focal-security) [2022g-0ubuntu<IP_ADDRESS>]
[13:05] -queuebot:#ubuntu-release- Unapproved: rejected tzdata [sync] (focal-security) [2022g-0ubuntu<IP_ADDRESS>]
[13:07] -queuebot:#ubuntu-release- Unapproved: rejected tzdata [sync] (bionic-security) [2022g-0ubuntu0.18.04]
[13:11] -queuebot:#ubuntu-release- New binary: lambdabot [riscv64] (lunar-proposed/universe) [5.3.1-1build2] (no packageset)
[13:36] <RikMills> ubuntu-archive: please remove the neochat riscv64 binaries from lunar release pocket. it now FTBFS in proposed (as it does in debian) due the dropping of the last of our cmake delta
[13:56] <RikMills> sil2100: I guess publishing bileto tickets in lunar still broken?
[13:57] <RikMills> ^ mitya57:
[14:22] -queuebot:#ubuntu-release- Unapproved: rejected tzdata [sync] (jammy-security) [2022g-0ubuntu<IP_ADDRESS>]
[14:22] -queuebot:#ubuntu-release- Unapproved: rejected tzdata [sync] (kinetic-security) [2022g-0ubuntu<IP_ADDRESS>]
[14:28] <tjaalton> sil2100: I've added spirv-headers to the list of hwe backports, as spirv-llvm-translator build tests fail without the new version
[15:07] <sil2100> RikMills: eh, sadly, still no access and not enough cycles to do remote debugging :/
[15:08] <sil2100> tjaalton: thanks! Still need to look at those, they're high on my list but there's so much
[15:09] <RikMills> sil2100: thanks. I guess the Qt transition from mitya57 there will either wait or land another way
[15:09] <sil2100> RikMills: I can help with copying those out ;)
[15:10] <sil2100> Just point me in the right direction
[15:10] <RikMills> mitya57: ^
[15:20] <LocutusOfBorg> RikMills, what about fixing neochat?
[15:24] <mitya57> sil2100: I have rights to copy myself, will do in ~an hour. And thanks.
[15:26] <RikMills> LocutusOfBorg: had a bit of a look, and gave up. if debian/kde aren't bothered, then I have better things to use time on
[15:27] <LocutusOfBorg> RikMills,
[15:27] <LocutusOfBorg> export DEB_LDFLAGS_MAINT_APPEND = -latomic
[15:27] <LocutusOfBorg> easy and bad way to solve it ^^
[15:27] <RikMills> urgh
[15:28] <LocutusOfBorg> otherwise add this file
[15:28] <LocutusOfBorg> https://github.com/pothosware/SoapyRTLSDR/blob/master/CheckAtomic.cmake
[15:28] <LocutusOfBorg> # Test for Atomics
[15:28] <LocutusOfBorg> include(CheckAtomic)
[15:28] <LocutusOfBorg> if(NOT HAVE_CXX_ATOMICS_WITHOUT_LIB OR NOT HAVE_CXX_ATOMICS64_WITHOUT_LIB)
[15:28] <LocutusOfBorg>     set(ATOMIC_LIBS "atomic")
[15:28] <LocutusOfBorg> endif()
[15:28] <LocutusOfBorg> and then link it if needed
[15:28] <LocutusOfBorg> (however, I don't see any reference of "atomic" word in the code, strange)
[15:28] <RikMills> krita did a fix like that
[15:29] <RikMills> LocutusOfBorg: nope. I grep'd the code as well and found nothing
[15:29] <LocutusOfBorg> and also please open debian bugs
[15:29] <RikMills> The debian BTS is currently ignoring me
[15:29] <RikMills> my emails vanish into nothing
[15:44] <LocutusOfBorg> RikMills, I uploaded, lets see if it builds or not
[15:47] <RikMills> thanks.
[16:34] -queuebot:#ubuntu-release- New: accepted golang-github-mdlayher-ethtool [amd64] (lunar-proposed) [0.0~git20221212.d43b2a7-1]
[16:39] <sil2100> mitya57: if you'll be doing bin-copies, someone will have to accept the bin syncs I suppose?
[16:39] <sil2100> mitya57: since I don't think you'd be able to copy packages with their binaries into lunar-proposed as-is, right?
[16:55] <mitya57> sil2100: I copied and it looks like I _was_ able to do that: https://launchpad.net/ubuntu/+source/qtbase-opensource-src
[16:55] <sil2100> mitya57: oh, good to know!
[16:56] <sil2100> Maybe my memory was just busted
[17:01] <RikMills> sil2100: I think the limitation might be if any binaries need to go through NEW?
[17:02] <RikMills> Qt is a virtual ABI package bump, so avoids that
[18:10] <laney> There was (is?) a bug where binary copies skip queues
[18:25] <tjaalton> sil2100: yeah I can imagine.. I also pushed the mesa bugfix release for kinetic (22.2.5, last of the series)
[18:29] <tjaalton> sil2100: this is the version that jammy will eventually get, once the bootstrapping is done
[18:37] -queuebot:#ubuntu-release- New sync: ruby-image-processing (lunar-proposed/primary) [1.10.3-2]
[18:43] <ricotz> hello, libreoffice/kinetic is ready :) - https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1997333
[18:43] -ubottu:#ubuntu-release- Launchpad bug 1997333 in libreoffice (Ubuntu Kinetic) "[SRU] libreoffice 7.4.3 for kinetic" [High, Fix Committed]
[18:45] <bdmurray> "shonky" he said while reading the scrollback
[19:29] <vorlon> RikMills[m]: so we dropped a delta that made neochat build on riscv64, and now it FTBFS?  Why would we remove the binaries instead of restoring the delta?
[19:29] <vorlon> also it looks like neochat is built in -proposed now
[19:30] <RikMills> vorlon: the delta was to cmake, which LocutusOfBorg wanted to keep dropped
[19:30] <RikMills> the neochat in proposed has a fix that we would try to upstream now
[19:31] <vorlon> well we don't regress ports just because one Ubuntu developer wants to not have a delta
[19:31] <vorlon> anyway seems it's sorted now
[19:31] <RikMills> yes, pending a permanent fix
[20:34] -queuebot:#ubuntu-release- Unapproved: accepted postgresql-14 [source] (kinetic-proposed) [14.6-0ubuntu<IP_ADDRESS>]
[20:35] -queuebot:#ubuntu-release- Unapproved: accepted postgresql-14 [source] (jammy-proposed) [14.6-0ubuntu<IP_ADDRESS>]
[20:36] -queuebot:#ubuntu-release- Unapproved: accepted postgresql-12 [source] (focal-proposed) [12.13-0ubuntu<IP_ADDRESS>]
[20:37] <vorlon> https://code.launchpad.net/~ubuntu-archive/ubuntu-archive-tools/+git/ubuntu-archive-tools/+merge/434590 a trinket to help people identify in-progress transitions that might need attention
[20:38] -queuebot:#ubuntu-release- Unapproved: accepted postgresql-10 [source] (bionic-proposed) [10.23-0ubuntu<IP_ADDRESS>]
[20:49] <vorlon> process-removals has somehow regressed to where it will not download the Debian source indices for me.  But I can download them fine with wget :/
[20:51] <vorlon> ah it doesn't handle the http->https redirect cleanly, somehow
[20:53] <vorlon> kanashiro[m]: puppet-agent seems stalled due to failing autopkgtests?
[20:56] <cjwatson> process-removals should probably be converted from the stdlib's `urllib` to `requests`
[20:57] <cjwatson> (unless you enjoy hard work)
[20:58] <kanashiro[m]> vorlon: I took a look at those failures yesterday but I was not able to sort them out yet. I was able to reproduce the failures locally, but if I get a shell and rerun the same test script the tests pass
[21:06] -queuebot:#ubuntu-release- Packageset: Added nvidia-graphics-drivers-525-server to i386-whitelist in focal
[21:06] -queuebot:#ubuntu-release- Packageset: Added nvidia-graphics-drivers-525-server to i386-whitelist in jammy
[21:06] -queuebot:#ubuntu-release- Packageset: Added nvidia-graphics-drivers-525-server to i386-whitelist in kinetic
[21:06] -queuebot:#ubuntu-release- Packageset: Added nvidia-graphics-drivers-525 to i386-whitelist in lunar
[21:06] -queuebot:#ubuntu-release- Packageset: Added nvidia-graphics-drivers-525-server to i386-whitelist in lunar
[21:33] -queuebot:#ubuntu-release- Unapproved: update-notifier (jammy-proposed/main) [<IP_ADDRESS> => <IP_ADDRESS>] (ubuntu-desktop, ubuntu-server)
[21:36] -queuebot:#ubuntu-release- Unapproved: update-notifier (focal-proposed/main) [<IP_ADDRESS> => <IP_ADDRESS>] (ubuntu-desktop, ubuntu-server)
[21:39] -queuebot:#ubuntu-release- Unapproved: update-notifier (bionic-proposed/main) [<IP_ADDRESS> => <IP_ADDRESS>] (ubuntu-desktop, ubuntu-server)
[21:40] -queuebot:#ubuntu-release- Unapproved: update-notifier (xenial-proposed/main) [3.168.17 => 3.168.18] (ubuntu-desktop, ubuntu-server)
[22:13] -queuebot:#ubuntu-release- Unapproved: accepted ca-certificates-java [source] (jammy-proposed) [20190909ubuntu1]
[22:18] -queuebot:#ubuntu-release- Unapproved: accepted gnome-remote-desktop [source] (kinetic-proposed) [43.2-0ubuntu1]
[22:21] -queuebot:#ubuntu-release- Unapproved: accepted gnome-remote-desktop [source] (jammy-proposed) [42.7-0ubuntu1]
[22:29] -queuebot:#ubuntu-release- New sync: nvidia-graphics-drivers-525-server (lunar-proposed/primary) [525.60.13-0ubuntu1]
[22:29] <bdmurray> coreycb: what are your plans for updating manila and horizon in lunar? The Kinetic SRUs will have a greater version than Lunar.
[22:30] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-525-server [sync] (lunar-proposed) [525.60.13-0ubuntu1]
[22:34] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-525-server [i386] (lunar-proposed/none) [525.60.13-0ubuntu1] (i386-whitelist)
[22:36] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-525-server [amd64] (lunar-proposed/none) [525.60.13-0ubuntu1] (i386-whitelist)
[22:37] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-525-server [arm64] (lunar-proposed/none) [525.60.13-0ubuntu1] (i386-whitelist)
[22:38] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-525-server [amd64] (lunar-proposed) [525.60.13-0ubuntu1]
[22:38] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-525-server [i386] (lunar-proposed) [525.60.13-0ubuntu1]
[22:38] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-525-server [arm64] (lunar-proposed) [525.60.13-0ubuntu1]
[22:40] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-525 [i386] (lunar-proposed/none) [525.60.11-0ubuntu1] (i386-whitelist)
[22:44] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (kinetic-proposed) [2.791.1]
[22:44] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-525 [amd64] (lunar-proposed/none) [525.60.11-0ubuntu1] (i386-whitelist)
[22:44] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-525 [arm64] (lunar-proposed/none) [525.60.11-0ubuntu1] (i386-whitelist)
[22:44] <coreycb> bdmurray: hey, thanks for the reminder. I'm planning to soon.
[22:47] -queuebot:#ubuntu-release- New binary: knotifications [s390x] (lunar-proposed/universe) [5.101.0-1] (kubuntu)
[22:48] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (jammy-proposed) [2.765.14]
[22:48] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-525 [amd64] (lunar-proposed) [525.60.11-0ubuntu1]
[22:48] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-525 [i386] (lunar-proposed) [525.60.11-0ubuntu1]
[22:48] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-525 [arm64] (lunar-proposed) [525.60.11-0ubuntu1]
[22:48] -queuebot:#ubuntu-release- New binary: knotifications [amd64] (lunar-proposed/universe) [5.101.0-1] (kubuntu)
[22:48] -queuebot:#ubuntu-release- New binary: knotifications [ppc64el] (lunar-proposed/universe) [5.101.0-1] (kubuntu)
[22:49] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (focal-proposed) [2.664.45]
[22:50] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (bionic-proposed) [2.525.61]
[22:51] -queuebot:#ubuntu-release- New binary: knotifications [arm64] (lunar-proposed/universe) [5.101.0-1] (kubuntu)
[22:52] -queuebot:#ubuntu-release- New binary: knotifications [armhf] (lunar-proposed/universe) [5.101.0-1] (kubuntu)
[22:55] -queuebot:#ubuntu-release- Unapproved: accepted evince [source] (kinetic-proposed) [43.0-1ubuntu1]
[23:15] -queuebot:#ubuntu-release- New binary: knotifications [riscv64] (lunar-proposed/universe) [5.101.0-1] (kubuntu)
[23:26] -queuebot:#ubuntu-release- New: accepted knotifications [riscv64] (lunar-proposed) [5.101.0-1]
[23:27] -queuebot:#ubuntu-release- New: accepted golang-google-grpc [armhf] (lunar-proposed) [1.32.0-3]
[23:27] -queuebot:#ubuntu-release- New: accepted golang-google-grpc [riscv64] (lunar-proposed) [1.32.0-3]
[23:27] -queuebot:#ubuntu-release- New: accepted knotifications [amd64] (lunar-proposed) [5.101.0-1]
[23:27] -queuebot:#ubuntu-release- New: accepted knotifications [armhf] (lunar-proposed) [5.101.0-1]
[23:27] -queuebot:#ubuntu-release- New: accepted knotifications [s390x] (lunar-proposed) [5.101.0-1]
[23:27] -queuebot:#ubuntu-release- New: accepted golang-google-grpc [ppc64el] (lunar-proposed) [1.32.0-3]
[23:27] -queuebot:#ubuntu-release- New: accepted knotifications [arm64] (lunar-proposed) [5.101.0-1]
[23:27] -queuebot:#ubuntu-release- New: accepted golang-google-grpc [s390x] (lunar-proposed) [1.32.0-3]
[23:27] -queuebot:#ubuntu-release- New: accepted knotifications [ppc64el] (lunar-proposed) [5.101.0-1]
[23:27] -queuebot:#ubuntu-release- New: accepted bootstrap-icons [amd64] (lunar-proposed) [1.10.2+dfsg-1]
[23:27] -queuebot:#ubuntu-release- New: accepted opensubdiv [amd64] (lunar-proposed) [3.5.0-2]
[23:27] -queuebot:#ubuntu-release- New: accepted opensubdiv [armhf] (lunar-proposed) [3.5.0-2]
[23:28] -queuebot:#ubuntu-release- New: accepted opensubdiv [riscv64] (lunar-proposed) [3.5.0-2]
[23:28] -queuebot:#ubuntu-release- New: accepted golang-google-grpc [amd64] (lunar-proposed) [1.32.0-3]
[23:28] -queuebot:#ubuntu-release- New: accepted opensubdiv [ppc64el] (lunar-proposed) [3.5.0-2]
[23:28] -queuebot:#ubuntu-release- New: accepted opensubdiv [arm64] (lunar-proposed) [3.5.0-2]
[23:28] -queuebot:#ubuntu-release- New: accepted opensubdiv [s390x] (lunar-proposed) [3.5.0-2]
[23:29] -queuebot:#ubuntu-release- New binary: pigx-rnaseq [amd64] (lunar-proposed/none) [0.1.0-1.1] (no packageset)


[01:53] <_mup_> Bug #921895 was filed: local provider should offer ability to turn on '--force-unsafe-io' for dpkg to speed up package installs. <juju:New> < https://launchpad.net/bugs/921895 >
[09:08] <mpl> rog: and tomorrow is?
[09:08] <mpl> hi all
[09:08] <rog> mpl: almost the weekend!
[09:10] <mpl> hehe, that's right.
[09:10] <mpl> hopefully I'll finally have some time for some juju hacking then
[13:05] <hazmat> gary_poster, ping
[13:05] <gary_poster> hey hazmat
[13:07] <hazmat> gary_poster, i think i might have a line on the problem you where experiencing, but one question first.. what ubuntu version are you running on the host?
[13:08] <gary_poster> hazmat, did you see the email I sent you?  I think it was explainable simply by my environment.yaml (but maybe I'm wrong :-) ).  My host is precise.
[13:13] <hazmat> gary_poster, cool, so i think the problem is the 'distro' version of juju differs between precise and oneiric significantly. the oneiric containers are getting a much older version of juju.. if you add a line to your environment with 'juju-origin': 'ppa' that should resolve it.
[13:15] <gary_poster> hazmat, cool, yeah, it did, thanks.  Like I said in email, I also added an edit to http://askubuntu.com/questions/65359/how-do-i-configure-juju-for-local-usage to hopefully help others.  I actually explicitly had "juju-origin: distro" because of cargo-cult (or at least following-the-fine-manual-cult).
[13:15] <hazmat> doh
[13:15] <gary_poster> :-)
[13:49] <smoser> hazmat, ping
[13:49] <hazmat> smoser, pong
[13:50] <smoser> local provider.... if i just juju deploy say N things at once
[13:50]  * hazmat nods
[13:50] <smoser> is there anything that will protect the initial create form happening N times ?
[13:50] <hazmat> smoser, serial instantiation
[13:50] <smoser> i think in juju terms, that is the creation of "master template" that i'm talking about.
[13:50] <smoser> are you saying I should do that serially? or you're saying juju covers that for me..
[13:51] <hazmat> smoser, indeed, juju should cover that for you
[13:51] <hazmat> it will create the unit containers serially not in parallel
[13:52] <hazmat> smoser, question for you re getting a cloud image suitable for lxc
[13:52] <smoser> so i'm just curious, where/how is that accomplished?
[13:52] <smoser> cloud images should boot in lxc.
[13:52] <hazmat> afaics, i need to qemu-nbd or guestfs to mount the qcow2 and then copy it over to an fs dir or lvm mount
[13:52] <smoser> ah. don't use the disk image
[13:52] <smoser> and you might be duplicating effort
[13:52] <hazmat> smoser, what should i use?
[13:53] <smoser> utlemming might also be looking at createing 'ubuntu-cloud-image' (ie, in 'lxc-create -t ubuntu-cloud-image')
[13:53] <smoser> the easiest consumable thing for you is the .tar.gz file
[13:53] <hazmat> it should be an additional option to the ubuntu template
[13:53] <hazmat> maybe not
[13:54] <hazmat> smoser, what format is that in? tar.gz?
[13:54] <hazmat> i mean the f iles inside
[13:54] <smoser> you'll unfortunately have to extract it (tar -Sxvzf image.tar.gz "*.img" && mount -o loop *.img /mnt && rsync -a ....)
[13:54] <smoser> .img file, kernel, ramdisk.
[13:54] <smoser> we used to create a .img.tar.gz,which was just a sparse partition image compressed with sparse tar
[13:54] <smoser> but stopped doing that.
[13:55] <smoser> so you'll aste the download of th e ocmpressed kernel and ramdisk
[13:55] <smoser> more annoyhing (to me) is that the .tar.gz isn't immediately useful like the qemu image is.
[13:56] <smoser> you can use the qemu image, if you'd like. but using the partition image will mean you don't have to deal with qemu-nbd
[13:57] <smoser> hazmat, if it would make your life massively simpler, i would consider adding a filesystem contents tarball
[13:58] <smoser> although i worry about somewhat arbitrarily adding things to the downloads.
[13:59] <smoser> hazmat, SpamapS pointed me at http://paste.ubuntu.com/816820/ which he started on
[14:12] <hazmat> smoser, thanks, thats useful
[14:16] <smoser> hazmat, so were you looking to create an lxc template script?
[14:20] <hazmat> smoser, i was just looking at the problem, we could either bypass and do the download in juju or use a new template script
[14:20] <smoser> i think the template script in lxc is generally more useful
[14:20] <smoser> it serves a wider audience.
[14:20] <hazmat> probably won't fly with others, but i was leaning towards trying to do the download in juju to be able to give the user some feedback
[14:21] <hazmat> true
[14:21] <smoser> a middle of the road solution..
[14:21] <smoser> woudl be to let juju do the download (duplicating download code)
[14:21] <smoser> and then let it pass '--image' to lxc
[14:22] <smoser> although.. id dont' know.
[16:01] <dpb_> Was looking for information on how to properlly configure .juju/environments.yaml for an openstack deployment.  I understand the basic stuff (url, key, secret key), but what about control-bucket and admin-secret?
[16:02] <dpb_> Also, do I need a special branch?  or would the packages on oneiric suffice?
[16:05] <m_3> dpb_: control-bucket and admin-secret can be anything afaik... juju generates it when you try to run 'juju' without an environemnts.yaml file
[16:06] <m_3> dpb_: I typically let vi replace it with `echo "some junk" | md5sum` when creating a new env
[16:06] <jimbaker> m_3, the control bucket simply needs to be unique globally for s3
[16:07] <m_3> right.. thanks
[16:07] <dpb_> m_3: OK, great, thanks for the info
[16:08] <m_3> dpb_: here's a cleaned-up example I use atm http://paste.ubuntu.com/817806/
[16:09] <dpb_> m_3: awesome, thanks!
[16:10] <m_3> dpb_: obviously, make the default match.. that's a typo
[16:15] <jorge> hi folks! I'm testing juju with a diablo openstack installation. when i run 'juju status', i get an error but the command do what is expected.
[16:15] <jorge> root@sold016:~# juju status
[16:15] <jorge> 2012-01-26 14:07:54,476 INFO Connecting to environment.
[16:15] <jorge> 2012-01-26 14:07:59,576 ERROR SSH forwarding error: bind: Cannot assign requested address
[16:16] <jorge> machines:
[16:16] <jorge>   0: {dns-name: <IP_ADDRESS>, instance-id: i-0000001b}
[16:16] <jorge> services: {}
[16:16] <jorge> 2012-01-26 14:08:05,313 INFO 'status' command finished successfully
[16:16] <jorge> Is that normal?
[16:21] <m_3> jorge: it's normal for some networking setups
[16:22] <jorge> ok
[16:22] <m_3> jorge: you have to associate a public address with the bootstrap instance
[16:22] <jorge> now I lost my connection.
[16:22] <m_3> then it should respond to subsequent juju commands
[16:22] <jorge> Cannot connect to machine i-0000001b (perhaps still initializing): could not connect before timeout after 2 retries
[16:23] <koolhead17> m_3: is there a proper doc on this part available somewhere? i tried my best and failed to get it working.
[16:23]  * m_3 looking for using openstack with juju docs
[16:23] <m_3> koolhead17: ha!
[16:24] <koolhead17> and i thought its happening because whole openstack infra is behind proxy
[16:24] <koolhead17> even nova
[16:24] <m_3> koolhead17: the setup can vary... greatly
[16:24] <koolhead17> m_3: yeah i have not been successful with my deployment :(
[16:25] <m_3> koolhead17: lemme see if I can find my notes for the openstack cloud I'm using now
[16:25] <koolhead17> although juju works with my LXC
[16:26] <jorge> i'm using proxy too
[16:27] <jorge> when running the euca* commands you cannot have the http_proxy variables set up.
[16:27] <m_3> so I'm using euca2ools... that's probably the first place to start
[16:28] <m_3> from a machine where you can hit the endpoint urls directly
[16:29] <m_3> (so either your endpoints need to be public or your client machine needs to be in a visible network segment)
[16:31] <SpamapS> jorge: if there is a box in between you and the instances that you can SSH bounce off of, you don't need a public address, btw
[16:31] <SpamapS> jorge: you just have to setup ~/.ssh/config to bounce properly
[16:32] <jorge> some information more:
[16:33] <jorge> when I run juju bootstrap and after juju status (the first time), all worked fine.
[16:33] <jorge> after some minutes, stop to work.
[16:34] <jorge> now I can ssh to the instance using just the ssh command, with the ip of the instance. i'm on the controller and the instance in running on it. all in the same host.
[16:34] <koolhead17> jorge: your executing all this from the same internal network as of the instances
[16:35] <koolhead17> hey SpamapS
[16:35] <jorge> yes. my instances are in <IP_ADDRESS>/24 and i'm executing these commands from the network controller (from the host with ip <IP_ADDRESS>)
[16:36] <jorge> the connectivity to the instance are ok using ssh from command line. I can log in that.
[16:36] <jorge> see that
[16:36] <jorge> juju -v status
[16:36] <jorge> DEBUG Spawning SSH process with remote_user="ubuntu" remote_host="<IP_ADDRESS>" remote_port="2181" local_port="41754".
[16:36] <SpamapS> koolhead17: o/
[16:37] <SpamapS> jorge: right, thats so juju can talk to zookeeper over a secure connection
[16:37] <koolhead17> jorge: k. does it tries to connect with user ubuntu
[16:38] <koolhead17> also home your using smoser`s cloud-image for the instances
[16:38] <jorge> 2181 is zookeeper?
[16:40] <jorge> let me think... shouldn't i create a rule to permit this port? maybe iptables is dropping this connection.
[16:40] <jorge> euca-authorize -P ....
[16:41] <jorge> i'm going to start tcpdump in the instance to see the connections attempts.
[16:45] <SpamapS> jorge: no, you don't need to euca-authorize 2181
[16:45] <SpamapS> jorge: its connecting to it on <IP_ADDRESS> *through* an ssh tunnel
[16:45] <jorge> humm, ok
[16:46] <SpamapS> jorge: can you pastebin the whole failure? like 'juju -v status 2>&1 | pastebinit'
[16:47] <negronjl> m_3: ping
[16:47] <m_3> negronjl: hey
[16:52] <jorge> SpamapS: http://pastebin.com/SHmAszL7
[16:53] <koolhead17> SpamapS: i was getting similar error
[17:01] <SpamapS> jorge: is there something listening on port 54122 ?
[17:03] <jorge> SpamapS: no. I've tried many times and juju tries to use other ports and the problem is the same.
[17:03] <jorge>  DEBUG Spawning SSH process with remote_user="ubuntu" remote_host="<IP_ADDRESS>" remote_port="2181" local_port="50093".
[17:04] <jorge> ERROR SSH forwarding error: bind: Cannot assign requested address
[17:05] <SpamapS> jorge: try ssh -v -L 50093:<IP_ADDRESS>:2181<EMAIL_ADDRESS>[17:06] <jorge> Ok, just a minute because i destroy the environment. It is starting again.
[17:19] <jorge> SpamapS: ssh -v -L 45039:<IP_ADDRESS>:2181<EMAIL_ADDRESS>WORKED!!! I've changed the port because I've started the env again.
[17:20] <jorge> but juju status return error.
[17:20] <SpamapS> jorge: ok, thats good, and on that box, do you see zookeeper running?
[17:21] <jorge> SpamapS: yes, a java process and port 2181 opened.
[17:21] <SpamapS> jorge: ok, same juju status error though?
[17:24] <jorge> SpamapS: yes
[17:25] <SpamapS> jorge: really puzzling
[17:25] <jcastro> hazmat: I need to drop off for another call, thanks for inviting me!
[17:25] <hazmat> jcastro, thanks for joining
[17:54] <jorge> SpamapS: inttermitent problems. I run the juju status and in the first attemp i can see an error, in the second it worked. and, trying one more time, error. see http://pastebin.com/T4xE3KAG
[17:57] <SpamapS> jorge: I wonder if this is somehow related to the fact that you're running this on the network controller
[17:57]  * hazmat lunches
[18:25] <jcastro> http://pad.ubuntu.com/charmschool
[19:39] <_mup_> juju/deploy-invalid-conf r448 committed by<EMAIL_ADDRESS>[19:39] <_mup_> validate config before deploying service.
[19:58] <hazmat> bcsaller, jimbaker could i get a +1 on this trivial?  its a fix for bug 903149
[19:58] <_mup_> Bug #903149: juju fails silently with empty revision file. <juju> <juju:New> < https://launchpad.net/bugs/903149 >
[19:58] <hazmat> http://paste.ubuntu.com/818065/
[20:00] <bcsaller> hazmat: so you don't trap ServiceConfigError anymore? Thats more than just revision and can stop the processing of the repository, right?
[20:01] <hazmat> bcsaller, CharmError is a base class for serviceconfigerror
[20:01] <hazmat> its a more generic handling case
[20:01] <bcsaller> ahh, ok
[20:01] <bcsaller> +1
[20:22] <jcastro> niemeyer: I have this work item on the community charm docs for you "[niemeyer] drive dicussion about interface documentation on juju mailing list"
[20:22] <jcastro> have we done this yet?
[20:33] <niemeyer> jcastro: yo
[20:33] <niemeyer> jcastro: We haven't, but I'm on a roll on some development here ATM.. would you mind to ping me about this tomorrow?
[20:34] <jcastro> sure
[20:34] <niemeyer> jcastro: Thanks!
[20:36] <jcastro> SpamapS: you've got one WI too
[20:36] <jcastro> [clint-fewbar] add README to 'charm create' template
[21:25] <_mup_> juju/repo-find-report-charm-error r448 committed by<EMAIL_ADDRESS>[21:25] <_mup_> [trivial] Repositories report/log charm structural errors. [r=bcsaller][f=901495]
[21:29] <SpamapS> jcastro: ACK, that one should be done b4 FF
[21:29] <jcastro> SpamapS: ok, just keeping an eye on our burndown, ta.
[22:16] <statik> hey niemeyer, newbie question about lbox
[22:16] <statik> I tried goinstalling lbox on precise, and got some dependency package? errors
[22:16] <statik> I'm think I'm running the golang packages from precise. http://pastebin.ubuntu.com/818207/
[22:17] <statik> any tips on how to get lbox installed? I'm probably missing something simple
[22:43] <sidnei> bcsaller, hey, around?
[22:43] <bcsaller> sidnei: hey, whats up?
[23:19] <niemeyer> statik: Hey
[23:19] <niemeyer> statik: Ah, yes, I see
[23:20] <niemeyer> statik: You'll have to install golang-tip from the ppa
[23:21] <niemeyer> statik: Optionally, you can install lbox from the PPA as well
[23:21] <niemeyer> statik: pre-built
[23:26] <SpamapS> Watching debug-log .. its kind of a bummer that the output of the hooks is double-newlined
[23:29] <SpamapS> hrm.. upgrade-charm needs to re-join all peer relationships
[23:29] <SpamapS> Otherwise if you change joined/changed hooks.. they won't be re-run
[23:30] <adam_g> any way to specificy an environments.yaml located somewhere other than ~/.juju/environments.yaml?
[23:32] <adam_g> ya, specificy
[23:52] <m_3> adam_g: you might get away with resetting HOME for a subshell of juju commands... it'd move .ssh too I guess though


[00:29] <omac2> good evening...where are the apis for fileopen/filesave/fileselection dialogs with ubuntu-sdk
[00:30] <omac2> running with devel on nexus4.  everything phone/SMS text works, but mobile data(3g) still not working out of the box.
[00:34] <omac2> devel channel image 32's wifi seems to work fine for me, but not the mobile data(3g). 3g icon still flashes on and off and then settles to off.
[00:35] <omac2> I have had the same mobiled data(3g) buggy behaviour in the saucy stable version and the trusty devel version image 32.
[01:43] <nlsielicki> hey all. My name's Nick.  I'm interested in flashing ubuntu touch to my nexus 4.
[01:43] <nlsielicki> I'm a CS student and so I'm interested in writing some apps too, could be fun.
[01:43] <nlsielicki> my question revolves around how featured the phone is yet-- is 3g radio supported on the nexus 4?
[01:44] <nlsielicki> I need to be sure that basic features like calling, text messaging, and 3g data connectivity is supported.
[01:44] <nlsielicki> battery life, speed, etc. are less concerning problems.
[04:41] <crocket> ubuntu touch for the win!!!!
[07:34] <dholbach> good morning
[09:02] <Oria> je suis parti sur l'irc #ubuntu-touch/part
[09:03] <some_dude> Hi there, I've been checking the online spreadsheet that tracks progress of Ubuntu Touch for the Galaxy Nexus (etc). To me, it looks like there's no more progress (and it's still not usable). So, my question: is Ubuntu Touch dead already?
[09:10] <dholbach> some_dude, not really
[09:10] <dholbach> some_dude, check http://people.canonical.com/~j-lallement/touch/changes/ for changes which landed
[09:36] <some_dude> dholbach, thanks, was getting worried seeing all those other phones/OSs coming out recently and Ubuntu not really being launched
[09:37] <dholbach> some_dude, everybody's putting loads of work into it :)
[09:38] <some_dude> Ok, cool, I'll stand by... :-)
[10:00] <ogra_> barry, https://jenkins.qa.ubuntu.com/view/Trusty/view/AutoPkgTest/job/trusty-adt-system-image/ARCH=amd64,label=adt/lastCompletedBuild/console ....
[10:00] <ogra_> still failing ... (FYI)
[10:21] <janimo`> ogra_, hey, what was the main blocker to getting the x86 images on cdimage, incomplete as they are?
[10:21] <janimo`> I only remember the click packages being hardcoded to armhf right now
[10:21] <ogra_> well, adding x86 support at all to cdimage
[10:21] <ogra_> (for touch)
[10:22] <ogra_> it currently only knows about armhf and the android subarches ...
[10:22] <janimo`> ogra_, oh, I figured that was simple from your conversation with rsalveti back then
[10:22] <ogra_> it was simple for goldfish, since thats just an armhf subset
[10:22] <ogra_> s/set/arch/
[10:23] <janimo`> ogra_, is the ubuntu.zip dependent on whether it runs on goldfish or on actual hw?
[10:24] <ogra_> no
[10:24] <ogra_> thats as generic as a rootfs can be
[10:24] <janimo`> ogra_, ok, I just did not see why golfish mattered for the ubuntu.zips
[10:25] <ogra_> it isnt over complicated to add publishing support for it ... just needs a bit of work
[10:25] <ogra_> oh, it didnt
[10:36] <mterry> pitti, hello!  I love your phonesim-autostart stuff.  Is there a way to simulate receiving a text message?
[10:36] <pitti> mterry: kind of; you can send one and get it bounced back, sec
[10:38] <mterry> hmm
[10:39] <pitti> mterry: http://bazaar.launchpad.net/~phablet-team/messaging-app/trunk/view/head:/tests/autopilot/messaging_app/tests/test_messaging.py#L123
[10:40] <pitti> mterry: sorry, forget about the bouncing, I mixed that up with calls
[10:40] <pitti> mterry: you can probably copy "def receive_sms()" as it is
[10:41] <mterry> pitti, that's some black magic.  pointing at js over dbus?
[10:41] <mterry> pitti, but awesome!
[10:41] <mterry> pitti, thanks
[10:41] <shuduo> hello, where is right place to report bug for system-settings-touch? there is no 'report a bug' in lp:~system-settings-touch page[B
[10:42] <pitti> mterry: yes, that's how to drive a Qt GUI remotely
[10:42] <pitti> mterry: ofono-phonesim runs on a private D-BUS as nobody, to avoid introducing a security problem
[10:43] <pitti> mterry: I agree it's ugly, but it's the only way that exists
[10:43] <mterry> pitti, yar, I noticed it was nobody.  Sure.  Plus, phonesim isn't exactly a common thing
[10:43] <mterry> pitti, yup, not hating on it, just impressed with its hackery
[10:43] <pitti> mterry: https://kernel.googlesource.com/pub/scm/network/ofono/phonesim/+/master/doc/scriptable.txt FYI
[10:44] <pitti> mterry: if we need this outside of messaging-app, it seems we should add that as a convenience script to ofono-phonesim
[10:45] <pitti> $ ofono-phonesim-receive-sms "sender" "text"
[10:45] <pitti> or so
[10:45] <mterry> pitti, just useful for testing greeter right now
[10:45] <pitti> wrap the ugly innards into a shiny CLI :)
[10:45] <mterry> not sure it's a widely useful thing
[10:58] <davmor2> Morning all
[11:05] <asac> mzanetti: Saviq: there?
[11:05] <mzanetti> asac: yes
[11:08] <asac> mzanetti: heard you guys really land regression tests for bugs?
[11:08] <mzanetti> asac: is that really a question?
[11:08] <asac> yes :)
[11:08] <asac> i suspected that noone did it, but heard you guys really do it
[11:08] <asac> which is great news :P
[11:09] <mzanetti> yeah, we try as much as we can
[11:11] <asac> mzanetti: you use qmlttests right? and we cant run that in our infrastructure yet?
[11:11] <mzanetti> asac: we run qml tests in the upstream merger
[11:12] <mzanetti> asac: we also use autopilot for integration tests. but we couldn't test everything with autopilot for multiple reasons. So yeah. most of our tests are qmltests with mocked backends
[11:17] <asac> mzanetti: can i run qmltests against an image if i wanted?
[11:17] <asac> mzanetti: could we package them so we have them available pre-built?
[11:19] <mzanetti> asac: well, so the backends are mocked which means it wouldn't reveal any breakage in things like services or such (which is where we use autopilot). But it would still add *a lot* of tests for example for SDK components. So yes, I'd say running them in the release jenkins would make sense
[11:19] <mzanetti> asac: as regard to packaging: IMHO a massive waste of time
[11:22] <mzanetti> asac: those tests are build time tests and rely on the source code file structure. So they also do coverage measurements etc which requires source files in place etc
[11:23] <mzanetti> that said. I'm not entirely sure what would be the best way to run them in the release jenkins. I would need to think a bit about it
[11:23] <mzanetti> but I'm sure there would be a nice way (although most likely involving tasks to extend those jenkins jobs with some building capabilities etc)
[11:24] <asac> mzanetti: i was hoping to use them as a second option for UI testing at image level... could qmltests be used that way at all?
[11:25] <mzanetti> asac: yes. it would be possible
[11:25] <asac> (e.g. without mocked backend and with maybe just debug symbols)
[11:33] <mzanetti> asac: so... for qml only applications (or well, applications which are launched using qmlscene) it's a no brainer. Just use it and it'll work
[11:34] <mzanetti> asac: for applications that have their own c++ main(), that main() would need to be adjusted in a way that it doesn't do much on their own but just call some other function for initialisation, so we could use QT_TEST_MAIN which just calls the same and then we'd be ready to go
[11:35] <mzanetti> asac: or maybe we could find a way to load the qmltestrunner stuff in the applications main (for example calling it with --test or the like)
[11:35] <asac> mzanetti: so we could make our framework that folks dont write main, but ubuntu_main and then have a generic main that does the right thing when run in test env?
[11:35] <mzanetti> asac: so bottom line is: for qmlscene based apps we could just use it right now. for C++ it'd be a little effort to make it happen, but nothing really critical
[11:36] <mzanetti> yes.. something like that would work
[11:36] <asac> mzanetti: so question is if upstream would like writing qmlscene more than autopilots :)?
[11:36] <asac> and if we also maybe fix a feww flakiness problems
[11:37] <mzanetti> asac: I'm all for it
[11:37] <mzanetti> a big fat +1000 actually from me
[11:37] <asac> i still believe autopilot is needed somewhat, but maybe just to test that the mouse pointer etc. thing
[11:37] <asac> mzanetti: ok i would suggest that we really play this through by maybe adding a trivial UI test this way to one of our apps
[11:37] <mzanetti> asac: I guess there are things where AP still has good value. especially for full stack integration testing
[11:37] <asac> and at best for unity
[11:38] <asac> mzanetti: right, but we should cover the mass of our UI functions in qmltests as far as i understand
[11:38] <mzanetti> I'd say yes
[11:38] <asac> and really just see autopilot as a layer that then also tests things from the mouse pointer level
[11:39] <mzanetti> asac: qmltestrunner supports mouse interaction quite nicely
[11:40] <asac> mzanetti: hmm. but you said autopilot would test full stack integration... so what can autopilot test that we cant test in qmltests?
[11:40] <mzanetti> asac: but it injects events directly into the framework, so you'd bypass e.g. X11 (which is actually where a lot of autopilot's flakyness comes from)
[11:40] <asac> i hoped the diff is minimal
[11:40] <asac> ah ok... yeah.
[11:41] <mzanetti> asac: qmltestrunner could not (easily) do things like this: you set an alarm in the clock app, and then connect to the alarm service to check if everything set up in there
[11:41] <asac> mzanetti: so assuming everyione has great UI testing coverage that we can run against our images ... can you think of a systematic way to understand what exactly we would need to test on top in autopilot to cover the gaps left with just qml?
[11:41] <asac> mzanetti: ok i see... are we doing that?
[11:41] <asac> :)
[11:41] <mzanetti> asac: you could obviously set the alarm in there and then still check if the whole round-trip has been successful, but not easily to IPC to other processes than the tested one
[11:42] <asac> yeah. wonder how much we use autopilot that way right now
[11:42] <mzanetti> asac: just saying... that's the difference and that's where autopilot has more possiblities
[11:42] <asac> somehow feels we are just doing full roundtrip atm
[11:42] <asac> (in AP)
[11:42] <mzanetti> asac: yes. see my mail on the phablet mailing list a while back
[11:42] <mzanetti> lemme search
[11:42] <asac> maybe autopilot could collaborate with qmltest?
[11:42] <asac> e.g. drive UI through qmltest, but then also add logic like this on top?
[11:43] <asac> mzanetti: whats the output format of junit? is that compatible with our autopilot format?
[11:44] <mzanetti> asac: would need to think more about combining both...
[11:44] <mzanetti> asac: re output format:
[11:44] <mzanetti>  -txt                : Output results in Plain Text
[11:44] <mzanetti>  -xunitxml           : Output results as XML XUnit document
[11:44] <mzanetti>  -xml                : Output results as XML document
[11:44] <mzanetti>  -lightxml
[11:44] <asac> ok. guess AP uses junit?
[11:45] <mzanetti> I think it's just the same. let me search for a jenkins job with an example
[11:46]  * asac notes down to talk to bfiller and sergio next
[11:50] <totos> Hello, I am thinking of buying a Nexus 10, to use it for simple tasks like web browsing and reading books. Is there a nexus 10 that is more stable than the others with the ubuntu touch installed?
[11:51] <mzanetti> asac: can't find a real xml file as jenkins seems to parse them and just show data in the website: e.g. http://s-jenkins:8080/job/unity-phablet-qmluitests-trusty/596/testReport/
[11:51] <mzanetti> asac: anyways, that means jenkins is fine with the output format
[11:52] <totos> I have read on the internet, that nexus exynos plays well with ubuntu touch.
[11:54] <asac> tdaitx__: nexus exynos? N4?
[11:54] <asac> totos: ^ ?
[11:54] <asac> (sorry tdaitx__ )
[11:56] <totos> asac: Nexus exynos isn't supported for 10 inches? My bad...
[11:57] <ogra_> nexus 10 is supported ... but it is a lot more buggy than i.e. the nexus 4
[11:57] <ogra_> we only start to focus on tablets this cycle
[12:00] <totos> ogra_: so is any installation of ubuntu to nexus 10, that is less buggy than the others?
[12:02] <ogra_> no, its all the same
[12:09] <totos> ogra_: nice, thanks.
[12:32] <t1mp> when I phablet-flash ubuntu-system, without options, I get INFO:phablet-flash:Pushing /home/tim/Downloads/phablet-flash/imageupdates/stable/maguro/version-100.tar.xz to /cache/recovery/
[12:32] <t1mp> is that correct? that version-100 file has a timestamp of October
[12:35] <ogra_> t1mp, yes, thats correct ... you are flashing stable/saucy if you dont pick a different channel
[12:41] <t1mp> normally I use --channel trusty-proposed
[12:41] <t1mp> ogra_: I guess what I want now is trusty. Is there a way to see which channels are available?
[12:43] <ogra_> t1mp, --list-channels is in sergios new go based flash tool, but thats not ready yet ...
[12:44] <ogra_> stable = saucy, stable-proposed = saucy-proposed, devel = trusty, devel-proposed = trusty-proposed.... on release day trusty will become stable and the U release will become devel ...
[12:46] <t1mp> ogra_: great, thanks :)
[12:47] <ogra_> i would suggest to stay away from release names and just stick with devel or stable ;) using devel will acutally get you a somewhat rolling release (since the name underneath will just change at release day)
[12:52] <t1mp> ok
[13:12] <sasi> hi
[13:13] <sasi> can any one please guide porting steps of ubuntu-touch on to arm cortex A9 processor
[13:14] <ogra_> see the channel topic, there is a link to the porting guide
[13:25] <sasi> Hi orga i didnt found any link to the porting guide can u please post it over here
[13:31] <cwayne> mardy: ping
[13:31] <popey> sasi: look in the /topic of this channel
[13:32] <popey> | Porting guide (advanced) https://wiki.ubuntu.com/Touch/Porting |
[13:33] <ogra_> and if you dont typo my nickname i actually get a notification ;)
[13:37] <sasi> hi popey thanks for your information, i'm new to this.. can you please guide me how to look in /topic of this channel
[13:38] <sasi> popey: hi popey thanks for your information, i'm new to this.. can you please guide me how to look in /topic of this channel
[13:39] <popey> sasi: its at the top of your browser window
[13:41] <sasi> popey: sorry i can't able to find it. i can only see "Status" and "#ubuntu-touch" can you please help me
[13:42] <popey> i pasted it
[13:42] <popey> 13:32:10 < popey> | Porting guide (advanced) https://wiki.ubuntu.com/Touch/Porting |
[13:42] <popey> that link
[13:43] <sasi> popey: i am asking about /topic, where can i find this
[13:44] <popey> sasi: if you're using some kind of web based irc client it should be on screen somewhere in your browser window
[13:45] <popey> it starts "Ubuntu Touch Support & Discussion... "
[13:46] <sasi> popey: ok fine thanq
[13:46] <t1mp> sasi: what happens when you type "/topic" in the same box where you type your chat messages?
[13:51] <sasi> t1mp: i didnt understood about "/topic" clearly. as i came to know that i am in "Ubuntu Touch Support & Discussion... " i think this indicates "/topic"
[13:54] <rsalveti> ogra_: janimo`: adding x86 images into cdimage should be easy now, after I added support for goldfish
[13:54] <janimo`> rsalveti, great
[13:55] <ogra_> rsalveti, goldfish only affected subarches
[13:55] <rsalveti> ogra_: right, but I changed that code in a way that it makes way easier to support a new arch
[13:55] <ogra_> we need to change the toplevel arches and make sure only the zip and tgz are published for it)
[13:55] <rsalveti> right
[13:56] <ogra_> it *might* even just work and we could possibly just add i386 to default-arches for touch
[13:56] <ogra_> since the file schema for zip and tgz should be the same (modulo the arch name) ...
[13:56] <rsalveti> atm we'd only publish the zip file, right?
[13:57] <rsalveti> we actually need to change a few things in there, as the piece that generates the zip file is still armhf specific
[13:57] <rsalveti> we need a x86 compatible updater-script in the zip file
[14:01] <pitti> is there a standard way to run "make test" or "ctest" during package build?
[14:01] <pitti> or do I need to put in the full override_dh_auto_test / check for "nocheck" / call ctest dance?
[14:02] <barry> ogra_: can't that be easily retried?
[14:02] <barry> ogra_: *can
[14:02] <ogra_> no idea, ask in #ubuntu-release
[14:02] <ogra_> rsalveti, oh, right
[14:03] <ogra_> rsalveti, hmm, the zip *creation* should be arch agnostic ... we just need the other binary ... but then ... we dont have android bits anyway yet, we could just go with the tarball for the start
[14:08] <rsalveti> ogra_: yeah
[14:23] <bhalu> how to install ubuntu touch on development arm boards
[14:23] <bhalu> ?
[14:25] <mardy> cwayne: pong (I'm on holiday and my VM is not running, but if I can help even like this, I'll help gladly :-) )
[14:26] <mardy> jdstrand: hi! Any ETA for bug 1245903? I'd a branch which depends on that, waiting to merge
[14:26] <cwayne> mardy: ah, sorry to barge in on your holiday!  I just wanted to let you know that I've got click-hooks working for account-plugins :D  and was gonna ask if you'd think it 'd make sense to bundle them with u-s-s-o-a or just create a new package
[14:26] <mardy> cwayne: they should be bundled
[14:28] <cwayne> mardy: ack, thanks.  now go enjoy your holiday :)
[14:28] <bhalu>
[14:28] <bhalu>                                                                                how to install ubuntu touch on development arm boards
[15:12] <MacSlow> rsalveti, btw... https://code.launchpad.net/~macslow/unity8/fix-1257312
[15:13] <kenvandine> mpt, ping
[15:14] <kenvandine> mpt, looking for some clarification on the background panel spec
[15:15] <mpt> kenvandine, I just removed the scaled-back v1 design, leaving only the original design behind … Did I over-trim?
[15:15] <kenvandine>  “Same background for both” is set, the welcome screen and home screen thumbnails combined should function as a single tappable button"
[15:15] <kenvandine> not that
[15:15] <mpt> ah
[15:15] <kenvandine> i read that as merging them so you only see one
[15:16] <kenvandine> if it is set to dupe
[15:16] <kenvandine> but now i'm not sure that what you meant
[15:16] <kenvandine> note:  i implemented that last night :)
[15:16] <mpt> kenvandine, you still see both thumbnails, and they’re in exactly the same positions as they were before, but they are now inside a single button
[15:16] <mpt> rather than being in separate adjacent buttons
[15:16] <kenvandine> ok
[15:21] <kenvandine> mpt, another question
[15:21] <kenvandine> on the preview page
[15:21] <kenvandine> you say to make the page and header transparent
[15:21] <kenvandine> which makes sense
[15:21] <kenvandine> but the sdk doesn't give us a clean way of doing that
[15:22] <kenvandine> and it breaks the visual design guidelines
[15:22] <kenvandine> but i do think it makes sense for a background preview
[15:22] <kenvandine> maybe hide the header instead of making it transparent?
[15:23] <mpt> kenvandine, I wouldn’t expect it to be in the SDK or the visual design guidelines, because it’s a one-off.
[15:23] <kenvandine> yeah
[15:23] <kenvandine> so the sdk doesn't give us a clean way of doing it
[15:23] <mpt> kenvandine, we could hide the header, but then we would still need something to tell you what the screen is for. :-)
[15:23] <kenvandine> i have a nasty hack that changes the header to transparent
[15:24] <kenvandine> but it is tricker to change the header text color
[15:24] <kenvandine> at least i haven't found a way there
[15:24] <kenvandine> and i have to be careful to change the background color back after previewing is done
[15:24] <kenvandine> it's nasty :)
[15:24] <kenvandine> so if we really want this, i think we need to request it to be added to the sdk
[15:24] <kenvandine> mpt, i could hide the header
[15:24] <mpt> Maybe it’s a matter of copying, pasting, and tweaking the header code from the SDK implementation?
[15:25] <kenvandine> and then add some text
[15:25] <kenvandine> mpt, yeah... but i worry about maintenance
[15:25] <kenvandine> as they change API
[15:25] <kenvandine> etc
[15:25] <mpt> If you’re using your own copy, any API change is irrelevant, right?
[15:25] <kenvandine> not completely
[15:25] <kenvandine> depends on how much i copy
[15:25] <mpt> The worst that can happen is the visual design of the standard header changes, and you’re still using the previous font size or whatever
[15:26] <kenvandine> we'd have to have our own PageStack
[15:26] <mpt> whoa, really?
[15:26] <kenvandine> i think so
[15:26] <kenvandine> or maybe Page
[15:26] <kenvandine> but that is still quite a bit
[15:26] <mpt> Okay, I think a Page with no header should be part of the SDK, at least
[15:26] <kenvandine> mpt, how about a popover bubble kind of thing?
[15:26] <kenvandine> mpt, i think i can make it hide the header pretty easily
[15:27] <kenvandine> or maybe some text above the buttons?
[15:28] <mpt> kenvandine, could you hide the header and then put some text in the same position and size that header text would be?
[15:29] <kenvandine> should be able to
[15:29] <kenvandine> let me see if i can hide the header in a clean way
[15:29] <mpt> kenvandine, cool, and maybe add a shadow to the text in case that part of the image happens to be white :-)
[15:29] <kenvandine> the risk there is the visual might become inconsistent if they change the page component
[15:30] <mpt> Understood. I think that risk is fine.
[15:30] <kenvandine> mpt, maybe the header area could have a semitransparent black background?
[15:30] <kenvandine> with white text?
[15:30] <kenvandine> so it's easier to read
[15:31] <mpt> kenvandine, that sounds very similar to the original design. :-D
[15:31] <kenvandine> and you changed it?
[15:31] <kenvandine>  :)
[15:32] <mpt> No, I mean the design that's in the spec now
[15:32] <mpt> Maybe I’m misunderstanding what you’re suggesting
[15:32] <davmor2> n
[15:32] <kenvandine> well that doesn't have a darker header
[15:32] <kenvandine> making the header area have a background rectangle of black, with opacity of like 0.5
[15:33] <kenvandine> and the white text
[15:33] <kenvandine> you can still see the background through it
[15:33] <mpt> It’s kinda hard to tell because of the clouds, but I think it is semitransparent black
[15:33] <mpt> Anyway, yes, that would be good
[15:33] <kenvandine> ok
[15:33] <kenvandine> cool
[15:35] <mpt> Thanks!
[15:37] <bhalu> how to install ubuntu touch on  arm dev boards?
[15:38] <ogra_> you would have to port it
[15:48] <bhalu> ogra: I mean how to port it?
[15:48] <ogra_> bhalu, see the channel /topic ... there is a url
[15:48] <ogra_> (to the porting guide)
[15:57] <mhall119> kenvandine: are you still working on content hub this cycle?
[15:57] <kenvandine> mhall119, yes
[15:58] <mhall119> kenvandine: do we have a roadmap on when features should land?  I want to plan the next app showdown for a time when we have new APIs/services to use
[16:00] <mhall119> olli_: tvoss: who is going to be working on the push notifications API?
[16:01] <mpt> charles, https://wiki.ubuntu.com/Bluetooth?action=diff&rev2=35&rev1=34
[16:01] <kenvandine> mhall119,    https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0As1Fg7XBGWTjdGUtbm0yQUFFYjE2czNVNlVqbXlfTWc&usp=drive_web#gid=0
[16:01] <olli_> mhall119, client side?
[16:01] <kenvandine> mhall119, doesn't have eta's though
[16:01] <mhall119> olli_: yes
[16:01] <olli_> mhall119, ricmm or somebody on that team
[16:02] <olli_> mhall119, that's for the implementation
[16:02] <olli_> the definition is driven by Chipaca
[16:02] <mhall119> thanks olli_
[16:02] <mhall119> ricmm: ping me when you have a minute to talk about push notifications
[16:21] <ricmm> mhall119: hi
[16:21] <ricmm> sup?
[16:23] <pmcgowan> mhall119, what a very well constructed ping
[16:24] <mhall119> pmcgowan: I wouldn't want to start another long email thread
[16:24] <mhall119> ricmm: hey, I was wondering if we had a roadmap with delivery dates for the push notifications API
[16:25] <mhall119> ricmm: I'm starting to plan the next app showdown, and I would like to make it late enough that push notifications are available to start using
[16:29] <mhall119> alright, one more question, who was working on the sensor service and haptics feedback?
[16:34] <rickspencer3> mhall119, I think that is ChickenCutlass or his team
[16:37] <ogra_> mhall119, ChickenCutlass wrote usensord ... just needs to be packaged (which is a bit tricky sine it is in go and one of the first go packages we have at all)
[16:38] <ogra_> mhall119, https://plus.google.com/109707276156531554811/posts/LAoPzq9DZhG
[16:42] <mhall119> thanks ogra_, rickspencer3
[16:42] <mhall119> ChickenCutlass: ping me when you have a few minutes to talk about haptics/sensor service roadmap
[16:57] <ChickenCutlass> mhall119 ok
[17:13] <mhall119> ChickenCutlass: hey, so I'm starting to plan the next app showdown, and I'd like to time it so that some of the new APIs are available, do you have a roadmap with delivery dates for the work on sensors and haptics
[17:13] <mhall119> ?
[17:14] <pitti> can someone please ack https://code.launchpad.net/~thomas-voss/process-cpp/fix_pkgconfig_setup/+merge/198025 ? (blocking sensor testing)
[17:16] <door> getting a 'checking for auto-deploy.zip auto deploy.zip not found error
[17:16] <ChickenCutlass> mhall119 so we are trying to land the new sensor service soon.  Like next week.  It will only have haptics implemented.
[17:16] <mhall119> kenvandine: got time for a couple questions?
[17:16] <ChickenCutlass> mhall119 still working out the API
[17:16] <ChickenCutlass> on the Platform API side
[17:16] <mhall119> ChickenCutlass: do you think by mid-January the API will be available, even if it's just a first version?
[17:16] <ChickenCutlass> yes
[17:16] <mhall119> and will it be available in QML from the start?
[17:17] <ChickenCutlass> of course
[17:17] <mhall119> perfect, thanks ChickenCutlass
[17:17] <ChickenCutlass> mhall119 the API will be much like the android one.
[17:17] <ChickenCutlass> on / off
[17:17] <ChickenCutlass> and pattern
[17:17] <mhall119> cool, let me know when it starts to come together and I'll make sure we get the docs published early on
[17:18] <ChickenCutlass> ok
[17:18] <door> sorry to interrupt, but is this the right room to discuss installing Ubuntu onto andriod?
[17:18] <mhall119> door: depends on what you mean
[17:19] <mhall119> door: are you talking about installing Ubuntu's phone OS on an Android device?
[17:19] <kenvandine> mhall119, sure
[17:19] <door> yes
[17:19] <mhall119> beuno: do we have an ETA on getting ratings and reviews working in the store and dash?
[17:19] <door> a Nexus 4
[17:20] <mhall119> door: then you're in the right place
[17:20] <mhall119> door: https://wiki.ubuntu.com/Touch/Install has instructions for installing it, it's easy if you have Ubuntu on your desktop/laptop, otherwise it's the same as flashing an Android ROM
[17:21] <mhall119> kenvandine: so the work that an app would need to tell the Content Hub that it can open, say, a PDF, do you think that will land by mid-January?
[17:21] <door> has anyone heard of / seen the error E: Can't open /cache/recovery/ubuntu_command ?
[17:21] <kenvandine> mhall119, yes
[17:21] <jdstrand> mardy: sorry, I didn't know you were blocked (I knew you wanted the fix of course). I'll prioritize for monday
[17:21] <mhall119> kenvandine: awesome, thanks!
[17:21] <kenvandine> np
[17:21] <beuno> mhall119, I refer you to ralsina
[17:22] <mhall119> ralsina: do we have an ETA on getting ratings and reviews working in the store and dash?
[17:22] <jdstrand> mardy: I started what I needed to finish before that upload yesterday and have a good handle on it
[17:22]  * jdstrand wanders off
[17:23] <mhall119> kenvandine: also, box2d and it's qml plugin are in the trusty archives now, right?
[17:23] <kenvandine> yes
[17:23] <mhall119> what do we need to do to make that part of the platform available to click apps?
[17:23] <kenvandine> yes
[17:23] <kenvandine> or, it could be bundled in
[17:23] <kenvandine> which someone did already
[17:24] <mhall119> hmmm, bundling might be safer for compatibility
[17:24] <mhall119> kenvandine: could you put together a .tar.gz that somebody could just download and un-pack into their project folder in order to use it?
[17:25] <kenvandine> seb128, which screen did you think my margins were too big on?
[17:25] <kenvandine> mhall119, not sure it's that easy... do you know who it was that had bundled it?
[17:25] <seb128> kenvandine, the grid
[17:25] <mhall119> nope
[17:25] <kenvandine> it uses qmake, and our default project templates don't
[17:26] <kenvandine> i don't think
[17:26] <mhall119> kenvandine: it was seagull strike, wasn't it?
[17:26] <kenvandine> ah, yes
[17:26] <mhall119> Michael Sheldon then
[17:26] <seb128> kenvandine, compare http://ubuntuone.com/20q4XFO8ZhvbJpxen4ifoR and https://wiki.ubuntu.com/Appearance?action=AttachFile&do=get&target=phone-background-welcome.mockup.png
[17:26] <kenvandine> maybe we can ask him what he did
[17:26] <kenvandine> seb128, so margins and spacing?
[17:26] <mhall119> yeah, I'll do that, thanks kenvandine
[17:27] <kenvandine> mhall119, np!
[17:27] <seb128> kenvandine, yes
[17:28] <kenvandine> seb128, can you try out what i just pushed?
[17:28] <kenvandine> see if you like that better
[17:28] <kenvandine> it includes all the other changes we talked about earlier
[17:33] <seb128> kenvandine, building (u-s-s is slow to build nowadays :/)
[17:35] <seb128> kenvandine, the spacing between column is still at least double of what it should be...
[17:36] <seb128> kenvandine, http://ubuntuone.com/1AMoi15hjexkImhM9YW4RY
[17:37] <kenvandine> -        spacing: units.gu(1)
[17:37] <kenvandine> +        spacing: units.dp(5)
[17:37] <kenvandine> seb128, try that in WallpaperGrid.qml
[17:39] <seb128> kenvandine, that's give me much bigger spaces...
[17:39] <seb128> which is what you would expect from increasing the spacing
[17:39] <kenvandine> ?
[17:39] <kenvandine> no
[17:39] <kenvandine> dp
[17:39] <kenvandine> not gu
[17:40] <Elleo> kenvandine / mhall119: I'm Mike Sheldon, what were you wanting to ask?
[17:40] <seb128> kenvandine, oh!
[17:41] <seb128> kenvandine, yeah, that looks better ;-)
[17:42] <seb128> kenvandine, even a bit less is better, e.g 3
[17:42] <mhall119> Elleo: ah, hello!
[17:43] <mhall119> Elleo: I was wanting to make it easy for app developers to use Box2d in their apps
[17:43] <mhall119> Elleo: I was wondering how you bundled it with Seagull Strike, and how it worked with the build process
[17:43] <seb128> kenvandine, in fact deleting the spacing line makes it about right...
[17:44] <seb128> kenvandine, though margins are bit small then, you might want margins: 3 * spacing or something
[17:46] <Elleo> mhall119: I basically just did a quick and dirty bundling of it; built qml-box2d, shove libBox2D and a qmldir definition in my package and set added it to the QML plugin include path from C++
[17:47] <mhall119> Elleo: how/where did you build it? on an arm device or using cross-compiling?
[17:48] <Elleo> mhall119: just on-device
[17:48] <Blackwizard> Hi
[17:48] <mhall119> Elleo: ok
[17:48] <Elleo> I do have a scratchbox environment setup for some arm dev, but it targets armv6
[17:48] <mhall119> Elleo: are the files you used for this available somewhere I can download them?
[17:48] <Blackwizard> How can I find tablets support ubuntu touch?
[17:49] <Elleo> mhall119: https://gitorious.org/qml-box2d/qml-box2d/ <-- you'll want the qt5 branch
[17:49] <Elleo> should build without any real difficulties
[17:49] <mhall119> Blackwizard: the original Nexus 7 and Nexus 10 are the only officially supported tablets at this time
[17:49] <mhall119> thanks Elleo!
[17:49] <kenvandine> seb128, spacing defaults to 0, so that breaks some of the calculations a bit
[17:49] <Elleo> mhall119: one thing I noticed that might cause you issues is that qmlscene on UT doesn't seem to support custom plugin paths, it's --help claims it has the option, but it then doesn't recognise it when you try to use it
[17:49] <kenvandine> but i can make it real small :)
[17:49] <Blackwizard> what about Samsung Note 8
[17:50] <Elleo> and iirc the .desktop launcher doesn't like environment variables being set in the Exec line
[17:50] <mhall119> Elleo: using -I ?
[17:50] <Elleo> yeah
[17:50] <seb128> kenvandine, well, even at 0 it's more spacing than the mockup, that's weird
[17:50] <mhall119> hmmm, ok, I'll check on that, thanks again
[17:50] <Elleo> no problem
[17:50] <kenvandine> seb128, some of that is the itemWidth i use, to allow room for the border on the current image
[17:51] <kenvandine> seb128, the design shows that border larger than the thumb
[17:51] <seb128> kenvandine, I see
[17:51] <Blackwizard> Does Samsung Note 8 Supports Ubuntu touch?
[17:57] <kenvandine> seb128, try now :)
[18:03] <ralsina> mhall119: maybe a week or two. Paul Liu is working on it and ran into some snags.
[18:06] <seb128> kenvandine, the spacing being previews look fine ;-) the margins on the left/right of the grid should be more though (the mockup has those on the right of the titles)
[18:06] <davmor2> Blackwizard: https://wiki.ubuntu.com/Touch/Devices
[18:06] <Blackwizard> tnx
[18:06] <Blackwizard> :D
[18:15] <mhall119> ralsina: by mid-January do you think we'll have an API developers can start using?
[18:16] <mhall119> oh wait, that's R&R, ignore that comment
[18:16] <ralsina> mhall119: well, the API is there for creating ratings and reviews, what's not done yet is showing/creating them from the dash
[18:16] <mhall119> thanks ralsina
[18:16] <ralsina> mhall119: right
[18:23] <mhall119> alex-abreu: are we still on trach to have a unified HTML5 template & plugin by end of December?
[18:25] <mhall119> alex-abreu: also, any idea when Ubuntu will be added to http://cordova.apache.org/docs/en/edge/guide_platforms_index.md.html#Platform%20Guides ?
[19:21] <om26er> when does the next image build ?
[20:24] <blmvxer> Hello guys, I am running Ubuntu 14.04 Touch on my Nexus 7(2012) and have a craked screen where the upper half is dead. is there anyway to rotate only while being inside an app?
[20:38] <airking> So I think I got the issue where the battery won't charge on my Nexus 4
[20:38] <airking> What can be done to fix this?
[20:43] <cyphermox> airking: does anything show up in dmesg or /var/log/syslog when it's plugged?
[20:43] <airking> I tried adb devices
[20:43] <airking> no dice
[20:43] <airking> let me try again
[20:44] <airking> nope
[20:48] <airking> A couple minutes ago, when switching from wall power to pc, I got the little red light to turn on, and the screen light up with the charging logo (battery with lightning bolt), but then I accidentally unplugged the USB, and haven't been able to get that back.
[20:50] <airking> cyphermox: What else should I try?  Is there anything else I can do?
[21:00] <airking> ifI hold down voldown+power a little red light comes on
[21:08] <airking> It's on!
[21:23] <cyphermox> airking: right, it's just very low battery you need to wait for it to charge