[07:14] <mborzecki> morning
[07:17] <zyga> mborzecki o/
[07:18] <zyga> mborzecki left a note on the snap-confine PR
[07:18] <mborzecki> zyga: hey
[08:03] <pstolowski> morning
[08:11] <mvo> good morning pstolowski and mborzecki
[08:11] <mborzecki> mvo: pstolowski hey
[08:26] <mvo> mborzecki: can I squash merge 10054 (the usr-lib-snapd.mount fix)?
[08:26] <mborzecki> mvo: i pushed a little tweak there, so we need to wait for spread to finish, but otherwise yes
[08:27] <mvo> mborzecki: cool
[08:27] <mvo> mborzecki: yeah, happy to wait
[08:32] <pstolowski> need 2nd review for https://github.com/snapcore/snapd/pull/10079
[08:32] <mup> PR #10079: api: provide meaningful error message on connect/disconnect for non-installed snap <Bug> <Created by stolowski> <https://github.com/snapcore/snapd/pull/10079>
[08:36] <mup> PR snapd#10082 opened: github: try out golangci-lint <Simple 😃> <Skip spread> <⛔ Blocked> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/10082>
[11:32] <mvo> mborzecki: is squash-merging 10081 okay?
[11:33] <mborzecki> mvo: yes
[11:36] <mup> PR snapd#10054 closed: overlord/snapstate, wrappers: add dependency on usr-lib-snapd.mount for services on core with snapd snap <Squash-merge> <Created by bboozzoo> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/10054>
[12:01] <mup> PR snapd#10083 opened: [RFC] systemd: enrich UnitStatus returned by systemd.Status() with Installed flag <Created by stolowski> <https://github.com/snapcore/snapd/pull/10083>
[12:03] <pstolowski> mvo, mborzecki ^ wdyt?
[12:08] <mvo> pstolowski: I like this, UnitFileState seems to be more predicatable than status and it's well documented in https://man7.org/linux/man-pages/man5/org.freedesktop.systemd1.5.html
[12:09] <mvo> pstolowski: but let's move this to 2.50, it seems to grow too much for 2.49, thanks for investigating and getting to the bottom of this though!
[12:10] <pstolowski> mvo: yeah, ok, i'd prefer not to rush it as well
[12:11] <mup> PR snapd#10084 opened: snap-seccomp: fix seccomp test on ppc64el <Created by mvo5> <https://github.com/snapcore/snapd/pull/10084>
[12:13] <mvo> ijohnson[m][m]: I will merge 10051 now but I think I won't squash because for 2.49 I will also need to collect all the prereqs from samuele so it needs to be a PR anyway, does that sound okay?
[12:16] <ijohnson> mvo that sounds good to me
[12:26] <mup> PR snapd#10085 opened:  cmd/snap-bootstrap/initramfs-mounts: move time forward using assertion times (2.49) <Run nested> <Created by mvo5> <https://github.com/snapcore/snapd/pull/10085>
[12:31] <mup> PR snapd#10065 closed: tests: reset the system while preparing the test suite <Simple 😃> <Created by sergiocazzolato> <Merged by sergiocazzolato> <https://github.com/snapcore/snapd/pull/10065>
[12:32] <mvo> ijohnson: I will force-merge 10051 after lunch, just running the nested 18.04 test here locally to double check. it fails in gce right now but it looks like a fluke
[12:33] <mvo> (and re-running the full thing for this seems wasteful)
[12:33] <ijohnson> Sure thanks for checking on that
[13:13] <mborzecki> hmm can't get annotations to work in https://github.com/snapcore/snapd/pull/10082
[13:13] <mup> PR #10082: github: try out golangci-lint <Simple 😃> <Skip spread> <⛔ Blocked> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/10082>
[13:18] <mborzecki> haaa it works
[13:19] <ijohnson> woahhhhh that's super cool!
[13:23] <mborzecki> i'll make it non-fatal for now until we can tune it
[13:38] <zyga> mborzecki I second that - that's totally awesome
[13:46] <mvo> mborzecki: \o/ nice!
[13:52] <mup> PR snapd#10086 opened: tests: unifying the core20 nested suite with the core nested suite <Run nested> <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/10086>
[14:12] <mup> PR snapd#10078 closed: tests: handle "snap refresh" returning an empty reply gracefully <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/10078>
[14:37] <mup> PR snapd#10051 closed: cmd/snap-bootstrap/initramfs-mounts: move time forward using assertion times <Run nested> <Squash-merge> <UC20> <Created by anonymouse64> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/10051>
[14:47] <mup> PR snapd#10081 closed: interfaces, interfaces/apparmor, overlord/snapstate: late removal of snap-confine apparmor profiles <Squash-merge> <Created by bboozzoo> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/10081>
[14:52] <mup> PR snapd#10084 closed: snap-seccomp: fix seccomp test on ppc64el <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/10084>
[15:01] <mvo> ijohnson: I'm sitting on the fence a bit about 10085, it's 2k lines to backport everything we need to do the initramfs timetravel, I'm wondering if it's too risky for a .N release, wddyt?
[15:01] <ijohnson> hmm
[15:02] <ijohnson> mvo: let me take a look at the pr
[15:05]  * cachio lunch
[15:09] <ijohnson> mvo: well most of that pr is tests only change
[15:09] <ijohnson> the thing I would be most concerned about is the changes to seed, as they are extensive
[15:09] <ijohnson> the refactoring that pedronis did is difficult to reason about imho, so while it was approved, I guess I'm not sure how comfortable I am putting it into a .N release
[15:44] <mvo> mborzecki: I guess we can close 10056, 10066 now?
[15:45] <mborzecki> mvo: both shoudl be closed already
[15:46] <mvo> mborzecki: aha, great, soory, then the GH view I had confused me
[16:12] <mup> PR snapd#10087 opened: release: 2.49.2 <Simple 😃> <Skip spread> <Created by mvo5> <https://github.com/snapcore/snapd/pull/10087>
[17:25] <mvo> cachio: 2.49.2 is in core/beta (only ppc64el still uploading)
[17:25] <cachio> mvo, nice, thanks
[17:25] <cachio> I'll make sure all the tests are executed
[17:25] <mvo> cachio: if we could get it into candidate on monday that would be ideal
[17:25] <mvo> cachio: thanks!
[17:25] <mvo> cachio: snapd should also be ready soon (within the next 30min)
[17:25] <cachio> mvo, nice
[17:26] <cachio> mvo, ta
[17:26] <mvo> thank you!
[17:33] <mvo> cachio: snapd is also in beta
[17:43] <blackboxsw> Hey folks, question about expectations for installing confined snaps running on a Desktop LiveCD? Do we expect this to be working currently? https://forum.snapcraft.io/t/confined-snaps-dont-work-on-live-images-due-to-apparmor-path-mapping/3767/10
[17:44] <blackboxsw> I ask becaouse I get errors from snapd/snap-confine:error while laoding shared libraries: libudev.so.1: cannot open shared object file: No such file or directory)
[19:38]  * cachio afk
[20:00] <ijohnson> blackboxsw: do you mean on an Ubuntu Desktop LiveCD ?
[20:01] <ijohnson> it should be supported, I know we have had issues with it before and i.e. overlayfs but last I tried it with 20.04 a few weeks ago it worked fine for me
[20:02] <blackboxsw> ijohnson: thanks. I was just running on xenial DesktopLiveCD trying to install canonical-livepatch for testing purposes. I'll try bionic and focal now
[20:02] <blackboxsw> likely something not available on Xenial maybe
[20:02] <ijohnson> hmm yeah dunno about xenial, but definitely should work on bionic and focal
[20:02] <blackboxsw> thx for the FYI, I can test the full install instead of livecd on xenial if needed
[20:03] <ijohnson> well snaps surely work on a fully installed system of xenial, we have many hundreds of test that run daily for this situation
[20:03] <ijohnson> we don't test live cd systems though
[20:03] <oerheks> live iso would have an too old snapd, xenial.
[20:03] <ijohnson> ah yeah that's a good point, probably need to update the snapd deb in the live cd after you've booted it
[20:04] <blackboxsw> ahh that's the ticket. yep I bet. will upgrade the deb there.
[21:18] <mup> PR snapd#10088 opened: o/configstate/configcore/picfg.go: use ubuntu-seed config.txt in uc20 run mode <Bug> <Needs Samuele review> <UC20> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/10088>
[22:23] <mup> PR snapd#10089 opened: o/configstate/configcore: simple refactors in preparation for new function <Simple 😃> <UC20> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/10089>


[10:21]  * trapni waves
[10:22] <trapni> hey. did anyone ever run into http://pastie.org/3255470 while trying to install upstart from source?
[10:27] <jodh> trapni: I'm guessing you are attempting to build this on lucid?
[10:28] <trapni> jodh: exactly! :)
[10:28] <trapni> jodh: the thing is, I have to use lucid
[10:28] <jodh> trapni: problem is that your libnih and also your libdbus are too old - no support for DBUS_TYPE_UNIX_FD.
[10:29] <trapni> jodh: and unfortunately, the other thing is, I cannot use OpenVZ, so I am using linux-vserver (lucid is the guest, Gentoo is the hypervisor), and I am trying to get around the getpid() > 1 error
[10:29] <trapni> aha!
[10:29] <trapni> yeah, just installed libnih from source (1.0.2)
[10:29] <trapni> so I got to install dbus from source, too?
[10:29] <trapni> or can I just add another repo to the sources.list w/o conflicting too much against lucid?
[10:30] <trapni> I am not *that* experienced with ubuntu yet :|
[10:30] <jodh> jodh: I believe you'll need to rebuild dbus, yes.
[10:30] <trapni> fine with me, just wanted to make sure there's something better in place :)
[10:31]  * trapni just hopes these packages will not conflict with the remaining binaries in the system :)
[10:31] <jodh> trapni: good luck!
[10:31] <trapni> haha, thanks :)
[10:32] <trapni> jodh: maybe you know, is it okay to just ./configure --prefix=/usr or how's dbus configured on ubuntu for the bin packages?
[10:32] <trapni> ah, and --sysconfdir=/etc/dbus-1
[10:33] <jodh> trapni: here's the current i386 lucid build log showing the configure line: https://launchpadlibrarian.net/76041392/buildlog_ubuntu-lucid-i386.dbus_1.2.16-2ubuntu4.3_BUILDING.txt.gz
[10:34] <trapni> ah
[10:34] <trapni> thanks :)
[10:35] <trapni> jodh: hm, that's strange, the log says  --sysconfdir=/etc but on my system it seems to be /etc/dbus-1 ...
[10:36] <jodh> trapni: maybe the 'dbus-1' gets tacked onto sysconfdir prefix?
[10:38] <trapni> that would be unusual, but i'll see
[10:40] <trapni> jodh: I start to get the feeling, that I have to compile more by hand on non-source distros as on source distros :-)
[10:43] <trapni> jodh: you were right, --sysconfdir=/etc puts files into /etc/dbus-1.
[10:43] <trapni> whatever...
[10:49] <trapni> jodh: http://pastie.org/3255560 now I am running into this compile error :(
[10:49] <trapni> do you know where this comes from?
[10:49] <jodh> trapni: looks like the build isn't using the latest version of nih-dbus-tool
[10:50] <jodh> trapni: check your path to ensure it's picking up the version from your 1.0.2 build.
[10:50] <jodh> trapni: if it is, make sure you reconfigure.
[10:50] <trapni> mhm...
[10:50] <trapni> yep
[10:52] <trapni> i'm getting crazy, make distclean && ./configure --the-recommended-things && make runs now into http://pastie.org/3255572 (nih-dbus-tool --version returns 1.0.2)
[10:53] <trapni> should I try 1.0.3 instead? (AFAIR I could download that one, too on code.google.com)
[10:58] <jodh> trapni: it stil looks like you're using the wrong nih-dbus-tool.
[11:02] <trapni> hmm
[11:02] <trapni> trying to reinstall nih then
[11:03] <trapni> jodh: not that wrong, look at http://pastie.org/3255626 /usr/bin/nih-dbus-tool links against [no /usr]/lib/libnih.so.1
[11:06] <trapni> it's because libnih1's lib is in /lib, but I passed --prefix=/usr to it
[11:27] <trapni> jodh: I am really pretty sure to run against the right libnih/dbus version, please see http://pastie.org/3255731 - hope it helps :)
[11:29] <jodh> trapni: you're using an old nih-dbus-tool - you need 1.0.3
[11:30] <trapni> mom
[11:31] <trapni> jodh: okay, I read about >= 1.0.2 in configure.ac. let me use 1.0.3 then :)
[11:31] <jodh> trapni: why did you choose 1.0.2 out of interest?
[11:33] <trapni> jodh: because that's been what I read in upstart's configure.ac file
[11:33] <jodh> trapni: you're using an old upstart too though :)
[11:33] <trapni> lucid comes with 1.0.1 by default, so upstart's ./configure script failed initially
[11:33] <trapni> I first just hacked this line to 1.0.1 and assumed it's just containing "bug fixes" as diff between 1.0.1 and 1.0.2, however it appearantly didn't
[11:34] <trapni> so I reset upstart's configure{,.ac} and installed libnih 1.0.2 from source, and then ran into the dbus issues
[11:34] <trapni> feel all like a mess
[11:34] <trapni> jodh: but FYI, with 1.0.3 the upstart now compiles fine :)


[08:43] <antonopo> Hi
[08:44] <antonopo> I have a question if you can help
[08:45] <antonopo> if i will add the sudo add-apt-repository ppa:xubuntu-dev/staging will i face problem by upgrading 22.04 to 24.04 in the problem?
[08:46] <antonopo> What do you think?
[08:53] <Unit193> Those are all backports from newer releases, but the version will be *lower* than the new release version's, so there should be a smooth upgrade.
[08:55] <Unit193> Eg, it's gearing up now to be backports *from* 24.04 to 22.10 and 22.04, all versions must first hit 24.04 and thus the backported versions can't be newer than what's in 24.04.
[08:59] <antonopo> So the add-apt-repository ppa:xubuntu-dev/staging  is like a backport repository?
[09:00] <Unit193> Yeah, pretty sure it didn't end up getting used how we expected, but wouldn't make sense to delete and create a new one now, it'd just break on people's systems.
[09:13] <antonopo> Thanks a lot i understand it yes. But yes my main question was if i will face problems if i will put this ppa:xubuntu-dev/staging repo in order to have the latest xfce on my LTS 22.04 and then be able to upgrade without any problem. So if we will not have problem with the future upgrade from 22.04 to 24.04 i will add it and i will do a full-upgrade
[12:29] <terminaleNSI_> salut
[12:47] <nhimmm> zzz
[12:47] <nhimmm> zzzz
[12:47] <nhimmm> z
[12:47] <nhimmm> z
[12:47] <nhimmm> z


[04:17] <mpt> "Dawn of Ubuntu" is pretty
[04:17] <mpt> well done to whoever drew it
[04:18] <mpt> and, hooray for not putting any branding goop in "Ubuntu Sparkle"
[04:28] <mpt> that's all
[06:36] <troy_s> head count is LOW
[08:30] <troy_s> head count critically low
[08:35] <msikma> It's going to get lower. I need to go to work.
[08:36] <msikma> I'll drop by when I arrive.
[08:36] <msikma> Bye.
[10:52] <lapo> hi
[10:54] <msikma> Hi lapo
[10:55] <lapo> yo msikma
[11:01] <msikma> How's it going?
[12:57] <hepheous> hi :)
[03:46] <ompaul> where are the images for cd's and dvd's for dapper I have to submit them to a printer today so I can have them published tomorrow for the session in the *house of celebration of dapper* (cough pub)
[03:58] <bit_doidao> hi all! we (ubuntu-br/ubuntu-mg) are organizing an event here in brazil, and need the photo in full resolution. does anyone knows how to receive permissions to use it?
[03:59] <bit_doidao> i have already sent an email to<EMAIL_ADDRESS>[06:33] <bersace> Do we really need Pool AND Drafts ?
[06:34] <bersace> I suggest that Drafts are for Documentations, Propositions where Pool is for outside content
[06:34] <bersace> but is that useful to distinguish that ?
[06:36] <bersace> troy_s: any ideas ?
[06:36] <troy_s> greetz
[06:36] <troy_s> bersace... no
[06:36] <troy_s> but the problem is that
[06:36] <troy_s> once you start a structure
[06:36] <troy_s> you need to make sure that you keep it simple
[06:36] <troy_s> so i suggest that we put ALL new things into drafts
[06:36] <troy_s> which means pretty much EVERYTHING because none of it has been proofread etc.
[06:37] <troy_s> ompaul, i posted your query to the mailing list...
[06:37] <troy_s> hopefully we can get some resolution quickly.
[06:38] <ompaul> I found it :-) sorry been busy working on it ;-)
[06:39] <troy_s> phew...
[06:39] <ompaul> had to do some mad stuff - let me get the url
[06:39] <troy_s> please do
[06:39] <troy_s> i would like to wiki it for future reference...
[06:40] <ompaul> https://wiki.ubuntu.com/DIYMarketing
[06:40] <ompaul> I have to remove the Red :-(
[06:41] <ompaul> our sponsor has problems with his colour red - he duplicates cds and dvds for a living and we are under time pressure - must have for tomorrow night :-/
[06:41] <ompaul> so without wrecking his day but still producing a large bundle of DVDs
[06:41] <ompaul> fun
[06:43] <troy_s> can you PLEASE post this to the ubuntu art mailing list.
[06:44] <troy_s> i have been trying to straighten all of these sorts of issues TOWARDS that mailing list...
[06:44] <troy_s> it's not your fault that you don't know where to turn, it is ours.
[06:44] <troy_s> That is all old stuff.
[06:44] <troy_s> Is that the best we are going to be able to do for a new release?!??!
[06:44] <troy_s> ack
[06:44] <ompaul> 6.06 is there
[06:45] <ompaul> have you got something better?
[06:45] <troy_s> didn't see the 606 link
[06:46] <troy_s> i suppose that was the domain of the doc project.
[06:46] <troy_s> too bad the coordination wasn't in place for this release.  at least it is done!
[06:46] <troy_s> phew.
[06:47] <ompaul> okay so your not going to fall over on me atm?
[06:47] <ompaul> :-)
[06:47] <troy_s> yah... well the coordination and structure leaves a LITTLE to be desired :)
[06:47] <troy_s> thankfully, the doc team must have completed those.
[06:48] <troy_s> at least one part is organized...
[06:48] <ompaul> right now I am trying to make clean up and get into a printable form the print for the disks
[06:48] <troy_s> so do you still have issue with the red color?
[06:48] <troy_s> ok...
[06:48] <ompaul> yes, they want something lighter
[06:48] <troy_s> so you know that you can tap the rather _currently_ scattered art team resources
[06:48] <troy_s> by sending mail to the mailing list correct?
[06:48] <ompaul> I will do off white
[06:48] <troy_s> mark reads it
[06:48] <troy_s> and he will crack the whip
[06:48] <ompaul> heh
[06:49] <ompaul> well I did not say that red was an problem it is too late for that
[06:49] <troy_s> i suggest you A) do what you need to get it done (because the work ethic is a little ... um... ) then post it so that
[06:49] <troy_s> folks are in the loop
[06:49] <troy_s> yep.
[06:49] <ompaul> well I will join that list tomorrow
[06:49] <troy_s> all i am trying to do now with my limited time is
[06:49] <troy_s> merely get the communication going
[06:49] <ompaul> cheers
[06:50] <ompaul> note note a g or a k but x I am an older person
[06:52] <troy_s> indeed.
[06:52] <troy_s> thanks for all of your last minute effort ompaul.
[06:53] <ompaul> hey what I want is 100 DVDs in the pub tomorrow night - the local lug chairman and I are on a people do stuff campaign so it works
[06:58] <troy_s> what was the exact printing issue?  too deep red?
[06:58] <ompaul> yes
[06:59] <ompaul> it appears that light reds work better and the font size for these machines, the guy fears that they will run into each other
[06:59] <ompaul> this may not say a lot for his printers or maybe he is not using the best in the house
[06:59] <ompaul> but we get a fairly large amount off the advertised retail price
[07:00] <ompaul> so we try to recover 2 euros per DVD and then make more, so far we are operating at a loss :-)
[07:01] <ompaul> but that is not the issue, but keeping the cost down is important it means more disks
[07:02] <ompaul> we want to do the DVD because it is not the CD if you get my drift its "ohh that is different" I can try before I install is what we want to encourage
[07:31] <ompaul> it awaits the modirator I may go back with my comments later
[08:04] <kyledye> msg nickserv set hide email on
[08:04] <kyledye> whoops
[08:19] <ompaul> from the top, no slippages this time :-)
[08:20] <defunkt> hi ya'll
[08:20] <defunkt> i just joined the team :)
[08:28] <bersace> defunkt: welcome
[08:28] <defunkt> thank you :)


[18:28] <newz2000> hi, I've set up a channel #ubuntu-website for website related discussions. In the past I've used #ubuntu-matt but this feels a little more clear
[18:32] <Seveas> newz2000, don't forget to add it to the InternetRelayChat wikipage :)
[18:32] <newz2000> I hit the save button now, so it should save sometime in the next 10m. :-)
[18:35] <Seveas> hehe
[18:36] <Seveas> the archive and websites should be in different datacenters ;)
[18:37] <erUSUL> Seveas: it would be really interesting to read a few blogpasts of the sysadmin of ubuntu servers about what has happened during the release XD
[18:37] <erUSUL> blogposts*
[18:38] <newz2000> I don't think anyone but me blogs about it, and I haven't yet.
[18:38] <Seveas> erUSUL, I heard from a reliable source that ubuntu releases in the past caused nationwide internet problems in smaller, less well-connected countries
[18:39] <Seveas> erUSUL, I don't think there's a reason to assume the problem was less big this time :)
[18:39] <erUSUL> Seveas: that's the juicy details i want to know ;) then people say that noones uses linux ;)
[18:40] <RoAkSoAx> i heard that some mirrors from switzerland and netherlands werent loaded at all... and download was as fast as possible...
[18:40] <erUSUL> newz2000: are you on planet ubuntu ??
[18:40] <newz2000> no
[18:40] <newz2000> this release wasn't very eventful, smooth as silk
[18:41] <newz2000> except the desgn firm delivered the homepage graphics at the last min and they were broken for IE
[18:42] <nalioth> newz2000: IE is broken.
[18:42] <erUSUL> newz2000: congrats then :) but the load on servers was really high wasn't it?
[18:43] <newz2000> our total amount of traffic was up compared to prev releases but the servers were far more responsive than usual.
[18:44] <newz2000> congratulate the sysadmins on that, they did an awesome job


[15:00] <sil2100> o/
[15:00] <FourDollars> \o
[15:00] <rbasak> #startmeeting Developer Membership Board
[15:00] <meetingology> Meeting started at 15:00:17 UTC.  The chair is rbasak.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[15:00] <meetingology> Available commands: action, commands, idea, info, link, nick
[15:00] <teward> o/
[15:00]  * sil2100 has a conflicting meeting so he'll be only 75% here
[15:00] <FourDollars> \o
[15:00] <rbasak> Ditto
[15:01] <teward> rbasak: we technically have 'quorate' for Utkarsh, but I think we're missing others, so give it a few to see who else shows up
[15:01] <ddstreet> o/
[15:01] <teward> if we aren't quorate for the meeting then... oh look ddstreet is here
[15:01] <rbasak> #topic
[15:01] <rbasak> #topic Long-term action items (do not need to be mentioned in regular meetings)
[15:01] <rbasak> Oh.
[15:01] <teward> rbasak: unassign the tsimonq2 task for now
[15:01] <rbasak> #info rbasak didn't mention the items not to be mentioned
[15:01] <rbasak> #topic Review of previous action items
[15:01] <teward> i know a lot more than Simon is going to reveal here but he's otherwise too busy at the moment, so someone else will need to pick that up
[15:01] <rbasak> OK
[15:02] <teward> #NotMe
[15:02] <rbasak>     ddstreet edubuntu seed <-> pkgset (carried over)
[15:02] <ddstreet> need to carry over
[15:02] <rbasak>     rafaeldtinoco look at https://lists.ubuntu.com/archives/devel-permissions/2021-March/001635.html (carried over)
[15:02] <rbasak> rafaeldtinoco sends his apologies, so I'll carry that over
[15:02] <rbasak> teward to add amurray to core-dev
[15:03] <teward> ummmmmm
[15:03] <teward> *checks*
[15:03] <teward> yes that's done
[15:03] <rbasak> teward to announce amurray's successful application
[15:03] <teward> I *think* I did that?  I'll have to check the ML archives.
[15:03] <teward> i'm a little discomboulated today :)
[15:03] <rbasak> OK I'll leave that on for now
[15:03] <teward> discombobulated*
[15:03] <rbasak> #topic Package Set/Per Package Uploader Applications
[15:03] <rbasak> #subtopic     [2021-06-28] Shih-Yuan Lee: https://wiki.ubuntu.com/ShihYuanLee/PPUApplication
[15:03] <rbasak> FourDollars: o/
[15:03] <rbasak> Would you like to introduce yourself?
[15:03] <FourDollars> \o
[15:03] <sil2100> o/
[15:04] <FourDollars> Hi
[15:04] <FourDollars> I am $4.
[15:04] <FourDollars> I am a Canonical employee.
[15:04] <FourDollars> I am a Debian developer.
[15:05] <FourDollars> I am a Ubuntu Contributing Developer.
[15:05] <FourDollars> I am a GNOME Emeritus Member.
[15:05]  * FourDollars copied from https://www.linkedin.com/in/fourdollars/.
[15:06] <rbasak> Thanks!
[15:06] <rbasak> Does anyone have any questions for FourDollars?
[15:06] <teward> *is still reading, may have questions*
[15:06] <FourDollars> I deeply involved the design of the implementaion of OEM metapackages.
[15:07] <rbasak> I have a question
[15:07] <FourDollars> Please.
[15:07] <rbasak> I understand the OEM metapackages are limited in terms of what you're supposed to upload.
[15:07] <rbasak> Can you describe those limitations, please?
[15:08] <FourDollars> It can only contain the dependencies of the Debian packages from main.
[15:09] <FourDollars> It can only contain the source list from Canonical OEM archive.
[15:09] <rbasak> Thanks!
[15:09] <rbasak> Are these documented anywhere please?
[15:09] <FourDollars> Let me check.
[15:09] <FourDollars> https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM
[15:10] <rbasak> Great, thanks!
[15:11] <FourDollars> Cool~
[15:11] <FourDollars> Any question else?
[15:11] <ddstreet> just for clarification, you're applying to join this team, right? https://launchpad.net/~canonical-oem-metapackage-uploaders
[15:11] <FourDollars> Yes.
[15:11] <ddstreet> thanks, no other q from me
[15:12] <teward> no q from me
[15:12] <teward> *disappears for 30 seconds to obtain another coffee*
[15:13] <rbasak> Does anyone else have any questions?
[15:13] <rbasak> FourDollars: how do these packages relate to Ubuntu release cycle freezes?
[15:13] <rbasak> Do you expect to be able to upload after feature freeze, and if so, will you be using any special process for that?
[15:14] <FourDollars> rbasak: Basically OEM metapackages will on;y be related to LTS.
[15:14] <FourDollars> s/on;t/only/ typo
[15:14] <rbasak> During development of the LTS, or after?
[15:15] <FourDollars> It depends on the OEM projects' schedules.
[15:15] <rbasak> OK - so SRUs of new metapackages are a possibility?
[15:15] <FourDollars> OEM metapckages will only be expected to appear in LTS' acrhive.
[15:15] <rbasak> Do you have any expectation of changing existing metapackages in SRUs?
[15:15] <FourDollars> No, we still need to do some SRU process for it.
[15:16] <rbasak> OK, thanks.
[15:16] <rbasak> I have no further questions.
[15:16] <FourDollars> Sometimes the customer will add more platforms into the same OEM metapackage.
[15:16] <rbasak> If nobody else has questions, let's move on to the vote.
[15:16] <rbasak> #vote Grant FourDollars upload to the Canonical OEM metapackage packageset
[15:16] <meetingology> Please vote on: Grant FourDollars upload to the Canonical OEM metapackage packageset
[15:16] <meetingology> Public votes can be registered by saying +1, -1 or +0 in channel (for private voting, private message me with 'vote +1|-1|+0 #channelname')
[15:17] <teward> #voters teward rbasak ddstreet sil2100
[15:17] <meetingology> Current voters: ddstreet, rbasak, sil2100, teward
[15:17] <teward> *knows evil things about the IRC side :P)
[15:17] <rbasak> lol
[15:17] <teward> +1
[15:17] <meetingology> +1 received from teward
[15:17] <sil2100> I need a minute or two o/
[15:17] <teward> yep yep
[15:17] <teward> *sips caffeine*
[15:18] <ddstreet> +1 happy with existing work setting up oem process and with endorsement, full confidence in excellent work on directly uploading oem metapkgs
[15:18] <meetingology> +1 happy with existing work setting up oem process and with endorsement, full confidence in excellent work on directly uploading oem metapkgs received from ddstreet
[15:19] <sil2100> +1
[15:19] <meetingology> +1 received from sil2100
[15:19] <rbasak> +1
[15:19] <meetingology> +1 received from rbasak
[15:19] <rbasak> #endvote
[15:19] <meetingology> Voting ended on: Grant FourDollars upload to the Canonical OEM metapackage packageset
[15:19] <meetingology> Votes for: 4, Votes against: 0, Abstentions: 0
[15:19] <meetingology> Motion carried
[15:20] <rbasak> Congratulations!
[15:20] <FourDollars> Cool~ Thanks a lot.
[15:20] <teward> i'm going to be prodding permissions today anyways, so i'll take the "Assign user to group" and "Approval Notice" tasks
[15:20] <rbasak> Any volunteers for taking the actions to put that live and send the announcement?
[15:20] <rbasak> Thanks!
[15:20] <teward> (permissions across things today anyways*)
[15:20] <rbasak> #action teward to add FourDollars to the Canonical OEM metapackage packageset
[15:20] <meetingology> ACTION: teward to add FourDollars to the Canonical OEM metapackage packageset
[15:20] <rbasak> #action teward to announce FourDollars' successful application
[15:20] <meetingology> ACTION: teward to announce FourDollars' successful application
[15:21] <rbasak> #topic Ubuntu Core Developer Applications
[15:21] <rbasak> #subtopic Utkarsh Gupta: https://wiki.ubuntu.com/UtkarshGupta/CoreDevApplication
[15:21] <ddstreet> congratulations FourDollars!
[15:21] <rbasak> utkarsh: hello!
[15:21] <utkarsh> hello! o/
[15:21] <rbasak> Would you like to introduce yourself please?
[15:22] <utkarsh> I am Utkarsh, a 21 y/o. I've been a DD for about ~3 years and actively maintain packages (over ~700 uploads) & also an FTP trainee, reviewing the famous NEW queue (:D). I do a bunch of security related work in Debian as well.
[15:22] <FourDollars> ddstreet: Thx.
[15:22] <utkarsh> Since this February, I joined the Canonical's Server team and have been actively fixing & taking care of stuff. Besides day job, I also try to help and take care of the community side of things. I've written all of things down in my application. \o/
[15:22] <rbasak> (since Utkarsh is a colleague on my team, I'm intend to mostly abstain from the discussion and vote)
[15:22] <rbasak> Thanks!
[15:22] <rbasak> Questions for utkarsh?
[15:23] <teward> none from me
[15:23] <ddstreet> still reading
[15:24] <teward> utkarsh: might steal you for some PHP stuff if PHP 8 misbehaves during the transition with certain applications (and nginx fastcgi_pass stuff to FPM), but other than that, no questions for you :)
[15:24] <utkarsh> teward: haha, absolutely! \o/
[15:28] <sil2100> Ok, I think I have no questions (no capacity to ask any as well)
[15:29] <ddstreet> utkarsh it looks like you have a lot of development-release experience from the last couple months, but not very much before that, and your first upload was feb this year, is that right? https://launchpad.net/~utkarsh/+uploaded-packages
[15:30] <utkarsh> ddstreet: yep, that's correct! and is covered in my application (top part) and rbasak's and kanashiro's endorsement.
[15:30] <ddstreet> so you've only done a couple sru uploads then, right?
[15:30] <utkarsh> I've been fixing lots of Ubuntu-specific things (architecture related) in Debian so as to avoid delta and let them be in sync.
[15:30] <utkarsh> since 2020, for Focal.
[15:31] <utkarsh> that is, for ruby2.7 transition & some for Rails 6.0.
[15:31] <ddstreet> can you explain how the sru process differs from development release process?
[15:32] <utkarsh> Once an Ubuntu release has been completed and published, updates for it are only released under certain circumstances, and must follow a special procedure called a SRU. From the wiki: https://wiki.ubuntu.com/StableReleaseUpdates. I've done SRUs for 8 packages (bionic, focal, groovy, hirsute)
[15:33] <utkarsh> 8 different packages, that is.
[15:34] <sil2100> utkarsh: hm, actually, maybe one question: what's the difference between multiverse and universe?
[15:34] <utkarsh> Once an SRU bug template is prepared, the upload is done to the desired release. A member from the SRU team then check everything & approves or asks for more information.
[15:34] <utkarsh> should I continue describing this process?^
[15:34] <utkarsh> or skip to sil2100's question?
[15:34] <ddstreet> i'd like to hear more, but you can answer him first
[15:35] <utkarsh> sil2100: hey, universe has community-maintained free and open-source software. OTOH, multiverse has s/w restricted by copyright or legal issues.
[15:37] <utkarsh> ddstreet: okay, so once the SRU team acks an upload, it is accepted and available in -proposed. A verification is then requested by the bug submitter (preferably, which anyone can do) to ensure that the fix indeed works as intended.
[15:37] <utkarsh> and we have a wait period for 7 days to ensure everything's fine. Post that, update is available in -updates.
[15:38] <ddstreet> what do you need to include in quilt patches for srus, other than the change itself?
[15:38] <utkarsh> DEP3 headers.
[15:38] <utkarsh> to ensure others can easily track the origin, et al of the patch.
[15:39] <utkarsh> I try my best to include all DEP3 headers in all my uploads, be it SRUs or uploads to the devel release.
[15:39] <utkarsh> as a best practice :)
[15:39] <sil2100> utkarsh: thanks for the answer o/
[15:39] <utkarsh> \o/
[15:40] <ddstreet> let's say you need to fix a bug in bionic; what's your process?
[15:40] <ddstreet> assuming there is no open lp bug for the problem
[15:40] <utkarsh> ah, alrighty.
[15:42] <utkarsh> step 1: reproduce the problem. step 2: prepare the actual fix and the SRU bug template with all the necessary fields. step 3: indeed verify that the fix works fine (by maybe using a PPA or whatever's preferable - I use a PPA).
[15:42] <utkarsh> step 4: upload the package & wait for SRU team to review.
[15:42] <ddstreet> upload the pkg for bionic?
[15:44] <utkarsh> step 5: if the team approves, do the verificaition (I try to let someone else do that so we have a second pair of eyes as well). step 6: also, check for any blockers (in case there's any).
[15:45] <ddstreet> so after all that, do you then fix it for focal?
[15:45] <utkarsh> I got sponsored for isc-dhcp/4.3.5-3ubuntu7.2 for bionic.
[15:45] <utkarsh> oh yes, make sure the fix is for all the release.
[15:45] <utkarsh> I mean, make sure it's fixed in -devel, first of all.
[15:45] <ddstreet> what if it isn't?
[15:46] <utkarsh> if not, prep a fix there and watch for regressions, etc. Let it migrate. Simulteanously, prep a fix for H/G/F/B if all of them are affected.
[15:46] <ddstreet> do you need to fix anywhere else?
[15:47] <utkarsh> in case the problem is in -devel release, I'd definitely forward the fix upstream or to Debian, whatever is appropriate.
[15:47] <ddstreet> does debian need to apply the fix before we fix ubuntu?
[15:48] <utkarsh> it's not necessary but is good to know that they've accepted the fix. For instance, Debian is in a freeze at the moment, so I send MRs and make sure they're accepted at least and so on.
[15:48] <ddstreet> what if it's not fixed upstream, do you need to wait for upstream to patch before fixing ubuntu?
[15:50] <utkarsh> I open PRs, et al upstream always (whenever possible) to make sure it's being tracked and will be subsequently fixed. Whilst it's ideal to be fixed upstream and then we cherry-pick from there but sometimes it so happens that we'd like to fix the bug immeditately, et al.
[15:51] <ddstreet> so is it ok to just open a PR upstream and MR in debian with your fix and then immediately patch ubuntu releases?
[15:52] <utkarsh> only if the fix is immediately needed or is a high-prio or something. Otherwise, it's always better for them to adapt the patch and then we cherry-pick that.
[15:53] <ddstreet> ok thanks, we're coming up on the end of the hour, so no more q from me
[15:53] <utkarsh> for example, I submitted a patch to Debian for them to accept and then did a sync here, when the upload wasn't high-prio.
[15:53] <ddstreet> rbasak i think we're ready to vote unless anyone else has q
[15:53] <sil2100> I might have one last question, more of a formality
[15:53] <rbasak> OK thanks! Any more questions from anyone?
[15:53] <rbasak> Oh sorry, go ahead sil2100
[15:54] <sil2100> How does the upload story change after Final Freeze for an Ubuntu release?
[15:55] <utkarsh> oh, of course. When the archive is frozen, fixes must be manually reviewed and accepted by the release team members.
[15:55] <utkarsh> well documented here (https://wiki.ubuntu.com/FinalFreeze).
[15:55] <sil2100> Can uploaders still upload things to the archive? If yes, what are appropriate uploads at this stage?
[15:57] <sil2100> Ok, since there's not much time left, seeing that you know about the documentation bits - I guess that might be enough for me for now!
[15:57] <utkarsh> the devs should upload to -proposed and the release team will cherry-pick if the circumstances allow. mostly RC bugs.
[15:57] <sil2100> No further questions o/
[15:57] <sil2100> Thanks o/
[15:57] <utkarsh> I'd have added more but time constraints..
[15:57] <utkarsh> thank you!
[15:58] <rbasak> #vote Grant Utkarsh Gupta Ubuntu Core Developer
[15:58] <meetingology> Please vote on: Grant Utkarsh Gupta Ubuntu Core Developer
[15:58] <meetingology> Public votes can be registered by saying +1, -1 or +0 in channel (for private voting, private message me with 'vote +1|-1|+0 #channelname')
[15:59] <sil2100> +1 Solid endorsements, lots of activity and Ubuntu presence
[15:59] <meetingology> +1 Solid endorsements, lots of activity and Ubuntu presence received from sil2100
[15:59] <teward> +1 solid endorsements, lots of activity, I fully believe they meet all the requirements for core-dev
[15:59] <meetingology> +1 solid endorsements, lots of activity, I fully believe they meet all the requirements for core-dev received from teward
[15:59] <teward> sorry handling 3 things at once :)
[16:02] <ddstreet> one sec, sorry
[16:04] <ddstreet> I'm confident in experience/knowledge with the devel release process, but I am concerned about the lack of experience with sru process; for better or worse, the ubuntu process does have lots of special cases and while you do have a good theoretical knowledge of it, without some hands-on sru experience, knowledge of the process alone isn't always enough
[16:04] <ddstreet> Certainly in the past, DMB members have rejected applications from people with more experience
[16:05] <ddstreet> +1 however my opinion isn't that a core dev needs process expertise, as I believe knowledge of the process is secondary to good technical ability, and all your work so far shows excellent technical work, so even if you don't have as much experience as has been required in the past, I'm confident in the actual changes you'll make and also confident you'll handle any unexpected process issues right and ask for help when needed
[16:05] <meetingology> +1 however my opinion isn't that a core dev needs process expertise, as I believe knowledge of the process is secondary to good technical ability, and all your work so far shows excellent technical work, so even if you don't have as much experience as has been required in the past, I'm confident in the actual changes you'll make and also confident you'll handle any unexpected process issues right and ask for help when needed receive
[16:07] <rbasak> +1 already endorsed; I would abstain, but voting to meet quorum as all other votes are unanimous
[16:07] <meetingology> +1 already endorsed; I would abstain, but voting to meet quorum as all other votes are unanimous received from rbasak
[16:07] <rbasak> #endvote
[16:07] <meetingology> Voting ended on: Grant Utkarsh Gupta Ubuntu Core Developer
[16:07] <meetingology> Votes for: 4, Votes against: 0, Abstentions: 0
[16:07] <meetingology> Motion carried
[16:07] <rbasak> Congratulations utkarsh!
[16:07] <utkarsh> thank you, everyone! \o/
[16:08] <teward> i'll take the tasks
[16:08] <utkarsh> ddstreet: duly noted, thank you! :D
[16:08] <ddstreet> congratulations utkarsh!
[16:08] <teward> again :p
[16:08] <teward> rbasak: ^^
[16:09] <rbasak> Thanks teward!
[16:09] <rbasak> #action teward to apply Utkarsh's core dev permissions
[16:09] <meetingology> ACTION: teward to apply Utkarsh's core dev permissions
[16:09] <teward> might take a couple hours FourDollars, utkarsh, but i'll get to your perms at some point today or tomorrow.  Trying to put out a fire on FT job's exchange server
[16:09] <rbasak> #action teward to announce Utkarsh's successful application
[16:09] <meetingology> ACTION: teward to announce Utkarsh's successful application
[16:09] <teward> (i hate that i know more about exchange than half the windows guys... >.<)
[16:09] <utkarsh> teward: absolutely, no rush! \o/
[16:10] <FourDollars> teward: Thx.
[16:10] <rbasak> As we're over time, shall we skip the other standing agenda items for next time?
[16:10] <teward> yep go go go
[16:10] <teward> just for the record:
[16:10] <teward> rbasak: i did that last item you left on agenda
[16:10] <teward> had to dig in the May archives to find it but that was done for amurray's announce
[16:10] <rbasak> Thanks!
[16:10] <teward> *goes to beat his head on microsoft servers now for FT job*
[16:11] <rbasak> #topic Next Chair
[16:11] <rbasak> #info The next chair will be slashd
[16:11] <rbasak> #topic AOB
[16:11] <rbasak> Anything else that needs to be brought up today?
[16:12] <rbasak> I guess not.
[16:12] <rbasak> #endmeeting
[16:12] <meetingology> Meeting ended at 16:12:17 UTC.  Minutes at https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/ubuntu-meeting.2021-06-28-15.00.moin.txt
[16:12] <ddstreet> thanks o/


[16:21] <mvinsc> hey, i have a vid card / audio prob. can anyone help?
[16:21] <holstein> !audio
[16:21] <holstein> mvinsc: whats up?
[16:21] <holstein> i usually install and try pavucontrol
[16:22] <mvinsc> ok... i can't get the proprietary ati drivers to work
[16:23] <mvinsc> the open source driver won't play audio through HDMI
[16:23] <mvinsc> when i install fglrx unity crashes
[16:24] <holstein> i wouldnt expect audio to work through hdmi
[16:24] <mvinsc> i got it the work with xubuntu with the ATI driver
[16:25] <mvinsc> i just don't understand why fglrx worked in one but not the other
[16:26] <holstein> mvinsc: yeah?
[16:26] <holstein> mvinsc: 3d support..
[16:26] <mvinsc> yeah... Radeon 5450
[16:27] <mvinsc> HDMI doesn't show up in sound settings
[16:28] <holstein> i would check for and apply upgrades
[16:28] <holstein> sudo apt-get update && sudo apt-get dist-upgrade
[16:28] <holstein> i would use pavucontrol
[16:29] <holstein> from the terminal, running "aplay -l" will list all the system devices
[16:29] <holstein> if you dont see it in aplay -l, it wont be working
[16:30] <mvinsc> card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
[16:31] <holstein> so, its possible to send audio to that device, in theory
[16:31] <holstein> what would i do? check for and apply upgrade
[16:31] <holstein> i would run pavucontol and alsamixer and trust none of the labels.. i would tweak *everything*
[16:31] <holstein> i would try live CD's and see if a newer/older alsa/kernel version supports the device out of the box
[16:32] <holstein> i would not let using unity effect my decision (personally).. i would just use XFCE
[16:36] <mvinsc> ok.. thanks i'll keep messing around with it...
[16:36] <mvinsc> the only reason i want to use unity is i love my wobbly windows


[06:19] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3359 Needs rebuild due to burned version number
[08:53] -queuebot:#ubuntu-ci-eng- tsimonq2 mitya57 acheronuk, https://bileto.ubuntu.com/#/ticket/3291 Needs rebuild due to burned version number (cosmic/fcitx-qt5, cosmic/gcin, cosmic/kdelibs4support, cosmic/qtwebkit-opensource-src, cosmic/skrooge, cosmic/texmaker). Needs rebuild due to higher version at destination (cosmic/analitza, cosmic/kwin, cosmic/kxmlgui, cosmic/libqtxdg, cosmic/plasma-integration, cosmic/pythonqt, cosmic/qt3d-opensource-src, cosmic/qtav, cosmic/qtbase-
[09:12] -queuebot:#ubuntu-ci-eng- tsimonq2 mitya57 acheronuk, https://bileto.ubuntu.com/#/ticket/3291 Needs rebuild due to higher version at destination (cosmic/analitza, cosmic/kwin, cosmic/kxmlgui, cosmic/libqtxdg, cosmic/plasma-integration, cosmic/pythonqt, cosmic/qt3d-opensource-src, cosmic/qtav, cosmic/qtbase-opensource-src, cosmic/qtcharts-opensource-src, cosmic/qtconnectivity-opensource-src, cosmic/qtcurve, cosmic/qtdeclarative-opensource-src, cosmic/qtgraphicaleffects-
[09:40] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3361 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[09:43] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3361 Generating diffs
[09:50] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3362 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[10:02] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3361 Successfully built
[10:10] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3362 Generating diffs
[11:53] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3352 Needs rebuild due to higher version at destination
[12:03] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3362 Successfully built
[12:04] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3363 Diff missing
[12:15] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3363 Generating diffs
[12:16] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3363 Successfully built
[12:55] -queuebot:#ubuntu-ci-eng- ahasenack, https://bileto.ubuntu.com/#/ticket/3355 Needs rebuild due to higher version at destination
[13:41] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3361 UNAPPROVED queue
[13:50] -queuebot:#ubuntu-ci-eng- ahasenack, https://bileto.ubuntu.com/#/ticket/3364 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[14:45] -queuebot:#ubuntu-ci-eng- ahasenack, https://bileto.ubuntu.com/#/ticket/3364 Pending binary packages
[14:56] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3365 Preparing packages
[14:57] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3365 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[15:05] -queuebot:#ubuntu-ci-eng- ahasenack, https://bileto.ubuntu.com/#/ticket/3364 Diff missing
[15:22] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3362 Needs rebuild due to higher version at destination
[15:25] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3365 Pending binary packages
[15:38] -queuebot:#ubuntu-ci-eng- ahasenack, https://bileto.ubuntu.com/#/ticket/3364 Generating diffs
[15:38] -queuebot:#ubuntu-ci-eng- ahasenack, https://bileto.ubuntu.com/#/ticket/3364 Successfully built
[15:45] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3365 Diff missing
[15:51] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3365 Preparing packages
[16:05] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/3365 Successfully built
[17:25] <ahasenack> hi guys, question about bileto. I'm done with this ticket: https://bileto.ubuntu.com/#/ticket/3355
[17:25] <ahasenack> the package was uploaded, it migrated, etc. Should I finalize it, or abandon it?
[17:25] <ahasenack> or something else?
[17:26] <ahasenack> note: I didn't use bileto's "publish" mechanism for the upload
[17:26] <ahasenack> I only used bileto to run the dep8 tests for me in all arches
[19:25] -queuebot:#ubuntu-ci-eng- ahasenack, https://bileto.ubuntu.com/#/ticket/3364 Uploading build
[19:45] -queuebot:#ubuntu-ci-eng- ahasenack, https://bileto.ubuntu.com/#/ticket/3364 Successfully built
[19:46] -queuebot:#ubuntu-ci-eng- ahasenack, https://bileto.ubuntu.com/#/ticket/3364 Generating diffs
[19:47] -queuebot:#ubuntu-ci-eng- ahasenack, https://bileto.ubuntu.com/#/ticket/3364 Successfully built


[23:37] <genii> Meh adbots
[23:39] <elky> considering the first one typoed i'm guessing not bots
[23:40] <Fuchs> pretty sure that was manual, yes
[23:40] <elky> oh good you saw it
[23:40] <Fuchs> thus I also handled it as "user being stupid"
[23:40] <elky> twice
[23:40] <Fuchs> means: feel free to remove the ban if it was meant to be less than a day
[23:40] <elky> thankies
[23:41] <elky> Unit193: can you add that url to drone until sigyn gets it?


[07:45]  * jussi01 wanders
[07:45] <jussi01>  in
[07:45] <jussi01> :)
[07:46] <jussi01> hrm, whats wrong with #ubuntu-sa ?
[08:00] <Syntux> Morning
[08:02] <Syntux> jussi01, what about #ubuntu-sa ?
[08:03] <jussi01> !sa
[08:04] <Syntux> and?
[08:04] <Syntux> sorry but I did not get it :-)
[08:04] <jussi01> Just wondering why we need another arabic channel...
[08:05] <Syntux> jussi01, https://wiki.ubuntu.com/Ubuntu-Arabic/Proposal
[08:06] <Syntux> jussi01, #ubuntu-sa and all other -Arabic channels aimed for Arabic LoCos disposal not for the general Arabic community which is growing (although it's happening slowly but it's happening)
[08:06] <jussi01> Hrm... Still as long asI can remember there has only been 1 arabic channel anyway - why not continue to use it?
[08:07] <Syntux> jussi01, because there is an Arabic team now
[08:07] <jussi01> or are you planning to redirect -sa to -arabic?
[08:07] <Syntux> https://launchpad.net/~ubuntu-arabic
[08:08] <Syntux> jussi01, Not at all but Arabic support has been redirected to -sa because we did not have an Arabic team,  now we  do.
[08:09] <jussi01> Syntux: ok. once you are done with setup, ping me or one of the other ops and we will get you a factoid/amend the current one
[08:10] <Syntux> jussi01, for reason or another I'm not able to register the channel, I'm not getting any reply from chanserv
[08:10] <Syntux> jussi01, another thing, I do not want to take over -sa as it meant to be Saudi Arabia LoCo team channel
[08:11] <jussi01> hrm
[08:11] <jussi01> did you try again this morning?
[08:12] <Syntux> jussi01, just tried now and the same
[08:12] <jussi01> Syntux: pop into #freenode and ask would be my suggestion
[08:13] <Syntux> they would forward me back to #Ubuntu-irc as it's ubuntu related matter ?
[08:14] <jussi01> no, they shouldnt - its a freenode matter as you cant register a channel...
[08:14] <jussi01> doesnt matter if its ours or someone else...
[08:14] <Syntux> will give it a try
[08:15] <Syntux> actually I'm thinking to register the channel on DALnet network, there are more arabs there.
[08:16] <jussi01> Syntux: Id advise against that
[08:16] <jussi01> Syntux: ubuntu official channels are on freenode - so if you want it to be officialit should be here
[08:17] <Syntux> ok, will keep it here
[08:19]  * Syntux ahbal heh
[08:19] <Syntux> just found that I already registered it like month ago!
[08:20] <jussi01> rofl
[08:24] <Syntux> jussi01, now for the Arabic Support channel, we can settle this issue later; I'm waiting for mailing list setup so I can communicate with the team members.
[16:43] <erUSUL> Someone around??? 17:42 -Son4eto17{f}:#ubuntu- free sex video http://www.brutali.com/b.php?ref=1709
[16:43] <erUSUL> on ubuntu
[16:43] <bazhang> flood bot banned him
[16:44] <erUSUL> bazhang: oki doki ;)
[16:44] <bazhang> kinda scary erUSUL :)
[23:35] <nxvl> hi
[23:35] <nxvl> i was wondering what do we need on the peruvian loco team for the irclog to be saved into irclogs.u.c


[07:37] <liuxg> zbenjamin, ping
[07:38] <zbenjamin> liuxg: yes
[07:39] <liuxg> zbenjamin, an armhf click pacakge can only be deployed to a armhf emulator, right?
[07:39] <zbenjamin> liuxg: what else would you do with it
[07:40] <liuxg> zbenjamin, if the developer does not have a phone yet, he can use the armhf emulator to try an armhf click package. is this OK?
[08:23] <tsdgeos> landing \o/
[09:12] <tsdgeos> Saviq: doh, CI still on utopic :/
[09:12] <tsdgeos> FAILURE everywhere
[09:13] <tsdgeos> because libunity-api-dev can't be found
[09:13] <Saviq> tsdgeos, it should switch soon
[09:13] <Saviq> tsdgeos, like tonight
[09:13] <tsdgeos> ok
[09:53] <tsdgeos> Cimi: Saviq-codedive: so i have these changes for the croppedimagesizer to make it more async, question is, do we want it as a third branch on top of the other two (croppedimagesizer->photoscopeimprovements->asyncroppedimagesizer)
[09:53] <tsdgeos> or not?
[09:53] <tsdgeos> because the two branches as we have it are already an improvement
[09:54] <tsdgeos> and this new one introduces more improvements but also more complexity
[09:54] <tsdgeos> wonder if we want it separate just in case we want to eventually only land the first two and this one later
[09:54] <Cimi> tsdgeos, I just want someone to test it
[09:58] <tsdgeos> Cimi: that doesn't asnwer my question :D
[09:58] <Cimi> tsdgeos, if branch works, we can have them together
[09:59] <Cimi> tsdgeos, however, thinking on how management rejects stuff
[09:59] <Cimi> tsdgeos, is probably better to split them, so if async breaks things, we won't revert *all*
[10:05] <tsdgeos> Cimi: that was my thinking
[10:05] <tsdgeos> i'll do a separate branch
[10:37] <Cimi> sorry - back
[10:54] <Saviq-codedive> tsdgeos, separate, yeah
[10:54] <Saviq-codedive> tsdgeos, we might land it all together, but it'll be nice to have some granularity
[10:56] <tsdgeos> can someone remind me how to get the wizard to run again?
[10:57] <tsdgeos> Saviq-codedive: ↑ ?
[10:57] <Saviq-codedive> tsdgeos, phablet-config --help
[10:59] <Saviq-codedive> grr
[11:14] <MacSlow> Is anyone seeing these errors with bzr under vivid ? -> http://pastebin.ubuntu.com/8834245
[11:23] <Saviq-codedive> MacSlow, yes
[11:23] <Saviq-codedive> MacSlow, bug #1366684
[11:25] <Saviq-codedive> MacSlow, you need to downgrade configobj
[11:25] <Saviq-codedive> MacSlow, let me get you a package
[11:30] <Saviq-codedive> MacSlow, it will build soon in https://launchpad.net/~saviq/+archive/ubuntu/ppa/+sourcepub/4552771/+listing-archive-extra
[11:30] <Saviq-codedive> MacSlow, you'll need to downgrade and hold it
[11:31] <MacSlow> Saviq-codedive, ah... thanks
[11:31] <Saviq-codedive> MacSlow, it's because of your surname, and my first name
[11:32] <MacSlow> Saviq-codedive, *sigh* still such issue in 2014
[11:55] <Saviq-codedive> MacSlow, it's built in the PPA now
[12:02] <dandrader> mzanetti, you there?
[12:03] <mzanetti> dandrader: yes
[12:04] <dandrader> mzanetti, so, if I change unity-api, and then unity8 to depend on this newer, unreleased, unity-api. How will that work with recipes in a PPA?
[12:04] <dandrader> mzanetti, ie, how to make the unity8 recipe use this unity-api from another recipe. will that just work as they land on the same PPA? how does that work?
[12:05] <greyback> dandrader: PPA will build against the newest version of the package. If the PPA contains that new version, it'll use that over those in the archive.
[12:06] <greyback> dandrader: so just have unity-api in the PPA (bumped package version), and to be sure, make unity8 depend on that version
[12:07] <dandrader> greyback, so the new unity-api must have been uploaded to the ppa before I trigger the unity8 recipe, right?
[12:07] <mzanetti> yes
[12:07] <mzanetti> dandrader: actually, its clever enough to wait for it
[12:07] <greyback> dandrader: yes. unity8 will sit in a "package dependency wait" until unity-api ready
[12:07] <mzanetti> if the ppa has a older version then the required one
[12:07] <dandrader> greyback, mzanetti hmm, nice. thanks!
[12:08] <tsdgeos> that's because it's based in utopic
[12:08] <tsdgeos> same problem all our CI jobs are having
[13:11] <mzanetti> MacSlow: hey, we're missing you in the team channel
[13:12] <MacSlow> mzanetti, hm... what channel am I missing from?
[13:12] <mzanetti> #unity
[13:12] <facundobatista> Hola
[13:12] <MacSlow> mzanetti, oh... indeed...that's odd...
[13:12] <MacSlow> mzanetti, thanks for the heads-up
[14:12] <mterry> MacSlow|errand, I have questions about how to stop a PIN unlock dialog from appearing in some cases when you get back
[14:24] <greyback> mzanetti: just minor comment on https://code.launchpad.net/~mzanetti/qtmir/sg-imagenode/+merge/240583
[14:24] <mzanetti> greyback: cool, thanks
[14:24] <mzanetti> greyback: what about the jenkins failure? think its a real one?
[14:25] <mzanetti> greyback: some test segfaulted, but I don't really see how it's related
[14:25] <greyback> mzanetti: I didn't check it out, assumed it might be the vivid switch that might screw stuff up
[14:25] <greyback> none of our tests exercise the code you touched anyway
[14:27] <MacSlow> mterry, stop it from appearing? don't trigger the notification! :)
[14:28] <mterry> MacSlow, I'm looking at a situation where we get two SIM unlock dialogs, enter emergency mode via the first one, and thus don't want to see the second one...
[14:30] <mterry> MacSlow, actually, let me confirm whether we get both notifications at same time or serially
[14:31] <mterry> MacSlow, looks like serially.  So yeah, I'd like someway to skip incoming notifications...
[14:34] <MacSlow> mterry, well you can use the close-method
[14:35] <MacSlow> mterry, see lp:unity-notifications/examples/sd-example-incoming-call-canceled.py for an example
[14:58] <mzanetti> greyback: fixed
[14:58] <greyback> mzanetti: ta
[15:04] <greyback> dandrader: hey just trying our your rotation stuff while I wait for desktop to compile, am loving the animation!
[15:04] <greyback> dandrader: panel icons are wrongly placed after the animation though, aware of that?
[15:05] <dandrader> greyback, yes, added a work item to the doc
[15:05] <dandrader> greyback, also, Elleo just fixed ubuntu-keyboard. new package should arrive soon (https://code.launchpad.net/~unity-team/+recipe/ubuntu-keyboard-shellrotation)
[15:06] <dandrader> greyback, if you interact with the indicator panel, the icons shift back to their proper places
[15:08] <greyback_> dandrader: stupid NM - "oh even though you're connected to an AP, I'm gonna move you to another AP for no bloody reason"
[15:53] <pete-woods> hello unity8 people! if I want to do a gradient, e.g. in a scope header, has the syntax / namespace changed?
[15:54] <pete-woods> oh wait
[15:55] <pete-woods> it's just the error message that's confusing
[15:55] <pete-woods> I had gradient:///#aarrggbb/#aarrggbb
[15:55] <pete-woods> and instead of saying the gradient was invalid, it told me the gradient schema was unknown
[16:27] <mterry> MacSlow, what would be the best way to fake notifications in the shell during a test?  I see some tests that use a fake model for a custom Notifications object...  But the actual mock Unity.Notifications plugin seems empty
[16:27] <MacSlow> mterry, need to mock in a qmltest or an autopilot-test?
[16:28] <mterry> MacSlow, I was thinking qmltest
[16:28] <mterry> MacSlow, I *could* do some testing of just the menuitemfactory using a fake model, but had been planning on doing a full shell test
[16:29] <MacSlow> mterry, hm... a full test like that only has been implemented on the autopilot-side
[16:30] <mterry> MacSlow, I've been avoiding autopilot these days  :)
[16:30] <MacSlow> mterry, the mocks (for notifications) on the qmltest-side are just for exercising the pure rendering/layout features
[16:30] <MacSlow> mterry, I totally understand :)
[16:31] <MacSlow> mterry, there are very simplistic action/button-invocation checks on the qmltest-side of things... but nothing is doing full shell-integration testing
[16:31] <mterry> MacSlow, seems like a gap!  But a bit involved for me to implement from scratch for this one small rtm bugfix
[16:32] <mterry> Maybe I'll just go for more targetted testing for now
[16:32] <MacSlow> mterry, well the "gap" is still served by the autopilot-based tests
[16:32] <mterry> MacSlow, right, not that we have no testing.  Just a gap on qmltest side  :)
[16:33] <mterry> MacSlow, fair... I could do an autopilot test anyway
[16:33] <mterry> they won't be dead forever
[16:33] <MacSlow> mterry, you can borrow from lp:unity8/tests/autopilot/unity8/shell/tests/test_notifications.py
[16:35] <robotfuel> mterry: I'd be happy to help you with problems you have when writing autopilot tests, let me know if you'd like a review if you have an issue.
[16:38] <mterry> robotfuel, well it's more about our autopilot test framework giving sketchy results in jenkins
[16:38] <mterry> robotfuel, but will do!
[16:38] <robotfuel> mterry: I am working on fixing the failing tests in the dashboard. so hopefully they will be less sketchy soon
[16:39] <mterry> nice!  :)
[16:56] <dandrader> dednick, hey
[16:56] <dandrader> dednick, how busy are you? working on any RTM task?
[16:56] <dednick> dandrader: howdy
[16:57] <dednick> dednick: none of the uber critical ones at the moment.
[16:57] <dandrader> dednick, I need some help with the indicators in the shellRotation branch
[16:57] <dednick> dandrader: sure
[16:58] <dandrader> dednick, let me push the branch to ~unity-team so that you can work on it as well...
[16:59] <dandrader> dednick, it's here. lp:~unity-team/unity8/shellRotation and this is the ppa: https://launchpad.net/~unity-team/+archive/ubuntu/demo-stuff
[17:00] <dandrader> dednick, the problem is that when unity8 rotates, the icons in the indicator shift to a weird position
[17:00] <dandrader> dednick, they come back into place only once you interact with then again
[17:00] <dednick> dandrader: right
[17:00] <dandrader> dednick, when unity8 rotates it resizes Shell.qml, which resizes the indicators
[17:00] <dednick> dandrader: able to do it on desktop?
[17:01] <dandrader> dednick, unfortunately I couldn't reproduce it in "make tryOrientedShell" :-/
[17:01] <dednick> dandrader: ok. i'll take a look
[17:01] <dandrader> dednick, thanks!
[17:02] <dednick> dandrader: is the ppa for rtm image?
[17:09] <dednick> dandrader: i take it that silo is not for rtm image? ie devel-proposed?
[17:14] <dandrader> dednick, this PPA has packages for both utopic (thus rtm?) and vivid
[17:15] <dandrader> dednick, but the feature is not targeted for RTM at all
[17:15] <dednick> dandrader: i meant 14.09
[17:15] <dandrader> dednick, so it makes sense to use on top of devel-proposed
[17:15] <dednick> dandrader: but nevermind. just using devel
[17:15] <dednick> dandrader: where does unity-shell-launcher come from?
[17:15] <dednick> dandrader: can never remember...
[17:15] <dednick> libunity-api ?
[17:16] <dandrader> dednick, you mean in the cmake files? yeah, comest from unity-api
[17:17] <dednick> dandrader: hm. package 'unity-shell-launcher=5' not found
[17:22] <dandrader> dednick, where do you get it?
[17:22] <dednick> dandrader: on the desktop.
[17:24] <dandrader> dednick, did you "apt-get update && apt-get dist-ugprade"?
[17:24] <dandrader> dednick, is your desktop on vivid?
[17:24] <dandrader> dednick, if all fails, built and install unity-api from trunk
[17:24] <dednick> dandrader: no, still on utopic
[17:24] <dandrader> dednick, that explains it then I guess
[17:25] <dednick> dandrader: but you just said there are packages for both :)
[17:25] <dandrader> dednick, take the leap! :)
[17:25] <dednick> never!
[17:25] <dandrader> dednick, on the PPA there are utopic and vivid packages of the project modified for shell rotation
[17:25] <dandrader> dednick, and unity-api is not one of them yet
[17:26] <dednick> dandrader: ah. the u8 in the ppa does not include your rotation stuff?
[17:26] <dandrader> dednick, it does, of course
[17:26] <dednick> dandrader: well then!
[17:26] <dednick> :)
[17:26] <dandrader> now you confused me
[17:27] <dednick> me too
[17:27] <dednick> it shouldnt build utopic packages for u8 if i can't do it on my utopic machine.
[17:27] <dandrader> dednick, right
[17:27] <Saviq-codedive> we only bumped unity-api overnight
[17:27] <Saviq-codedive> dednick, ↑
[17:28] <dandrader> dednick, now I'm thinking about removing the utopic builds from the recipes. greyback_?
[17:28] <dednick> ah
[17:28] <Saviq-codedive> yeah, utopic is old news!
[17:28] <dednick> dandrader: guess that the silo hasn't rebuilt since then
[17:28] <greyback_> dandrader: if you wish. Can enable it again if we really need them
[17:31] <dednick> fek. i'll do an upgrade in the morning. dont have time now!
[17:33] <dednick> dandrader: ok, i see the problem.
[17:42] <dednick> dandrader: stupid flickable is re-asserting it's control over contentX
[17:42] <dednick> sigh.
[17:42] <dandrader> dednick, are you able to reproduce it in qml tests or only on the device?
[17:43] <dednick> dandrader: only on device now. i havent been able to build on destop
[17:43] <dandrader> ah, right
[17:44] <dednick> dandrader: flickable doesnt really like me messing around with contentX. it's a bit of a hack
[17:44] <mzanetti> mterry: hey, will you add the test here? https://code.launchpad.net/~mterry/unity8/skip-second-sim-unlock/+merge/240737
[17:45] <mterry> mzanetti, I was looking into it, seems we don't have a great framework for adding a qmluitests, but an autopilot test may work.  But then I got distracted by an important ongoing wizard bug and lunch.  I don't want to block the above MP on a test unless reviewers feel it's necessary
[17:48] <dednick> dandrader: i've got to go for the eve. i'll take some more look at it tomorrow
[17:49] <mterry> mzanetti, (I mean, I want to add that test anyway, but just if I don't get to it today, I don't want to block that MP for the next several days just on that)
[17:50] <mzanetti> mterry: https://code.launchpad.net/~mterry/unity8/skip-second-sim-unlock/+merge/240737/comments/592058
[17:50] <mterry> mzanetti, awesome -- yeah as you mention, apparently we don't test the SIM unlock dialog at all right now in our tests, let alone this special case of it
[17:53] <mzanetti> mterry: did you ever notice that weird bug if you use the emergency dialer and then return to normal operation, the first right edge swipe animation is somewhat broken
[17:55] <mzanetti> not sure yet what causes it
[17:58] <mterry> mzanetti, no haven't noticed that
[19:14] <Saviq> om26er, just quick feedback: onClicked: checkBox.checked = !checkBox.checked
[19:15] <Saviq> om26er, not that I like having this in the first place (remember we talked that this should be an SDK feature)
[19:16] <om26er> Saviq, oh, I have probably forgot our last conversation then ;)
[19:17] <om26er> Saviq, also thanks for the simpler version :)