[14:00] <ttx> Who's around for the java team meeting ?
[14:00] <ludovicc> me
[14:01] <ttx> persia is excused, I'll run the show today
[14:02] <ludovicc> ok, anybody else?
[14:02] <ttx> ...
[14:02] <ttx> ok, let's start then
[14:02]  * dantalizing is listening in
[14:03] <ludovicc> what's the topic?
[14:03] <ttx> #startmeeting
[14:03] <MootBot> Meeting started at 08:03. The chair is ttx.
[14:03] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[14:03] <ttx> [TOPIC] Roadmap review
[14:03] <MootBot> New Topic:  Roadmap review
[14:03] <ttx> hhmmmkay, so Robilad, persia and slytherin aren't around
[14:03] <ttx> which leaves some status update on Java-Contents stuff
[14:04] <ludovicc> ok
[14:04] <ttx> I'll be producing Jaunty's Java-Contents file before the end of the week
[14:04] <ludovicc> that's tomorrow!
[14:05] <ttx> euh. Yes.
[14:05] <ludovicc> have you looked at the javahelper package, there are some tools to dicover java classes in the installed jars
[14:05] <ttx> ludovicc: no
[14:05] <ttx> I'll have a look
[14:05] <ttx> On the "attract java packagers" side...
[14:06] <ttx> I'll try to run a packaging class
[14:06] <ttx> sometime in May
[14:06] <ttx> based on https://wiki.ubuntu.com/JavaTeam/LibraryPackaging
[14:06] <ttx> that's all in Roadmap.
[14:07] <ttx> ludovicc: Should we add "Maven support / debian-java sync" to the Roadmap ?
[14:07] <ludovicc> ok, when I'm more ready with the Maven packaging, I will add a tutorial there as well
[14:07] <ludovicc> yes, that would be a good idea
[14:07] <ttx> ok, let's assume there already was. I'm editing the page as we speak
[14:07] <ttx> could you give us some update on that ?
[14:08] <ludovicc> right, I have updated most of the packages used by Maven (plexus, modello, doxia soon) to include Maven POMs
[14:09] <ttx> ludovicc: in Debian ?
[14:09] <ludovicc> those POMs will then be useful when building other Maven based packages
[14:09] <ttx> ludovicc: did those mods make it to unstable yet ?
[14:09] <ludovicc> it's still in my PPA https://launchpad.net/~ludovicc/+archive/ppa/
[14:10] <ludovicc> I will push them to Debian anytime soon
[14:10] <ttx> ludovicc: cool. If they make it to unstable we will pick the changes up at Karmic sync/merge time
[14:11] <ttx> that's the best way, since the java experts are essentially on the debian side
[14:11] <ludovicc> ok, that's good. I have seen already many new Java packages in Jaunty, keep going!
[14:12] <ttx> ludovicc: Did you sort out your membership details ?
[14:12] <ludovicc> next step, I will update maven-debian-helper to work with my last work
[14:13] <ludovicc> after that we should be able to package about any Maven stuff
[14:13] <ludovicc> not yet, I'm waiting for some news. I will try to contact Persia directly
[14:13] <ludovicc> I was expecting to chat with him now...
[14:14] <ttx> ludovicc: you already applied to ubuntu-java, right ?
[14:14] <ttx> yes, I see it now
[14:14] <ludovicc> yes I did, pressed the button
[14:15] <ttx> doko: could you approve "Ludovic Claude" on ~ubuntu-java ? Or delegate to persia or me the ability to do so ?
[14:16] <ttx> ok, thanks for the update
[14:16] <ttx> [TOPIC] Open Discussion
[14:16] <MootBot> New Topic:  Open Discussion
[14:16] <ttx> Anything / anyone wants to discuss ?
[14:17] <ludovicc> ttx, can you review the package maven-repo-helper? I'm generating with it some postinst,postrm scripts, would appreciate a review of those
[14:17] <ttx> ludovicc: sure, i'll have a look
[14:18] <ttx> I can take it from your PPA ?
[14:18] <ludovicc> the instructions for how this package is supposed to be used are here: http://wiki.debian.org/Java/MavenRepoHelper
[14:18] <ludovicc> yes
[14:19] <ttx> ok. Anything else ?
[14:19] <ludovicc> all other packages published on my PPA use maven-repo-helper so you have lots of examples
[14:20] <ludovicc> nothing else
[14:20] <ttx> [TOPIC] Next meeting
[14:20] <MootBot> New Topic:  Next meeting
[14:20] <ttx> Same date, same place, next week ? Your regular host should be back.
[14:21] <ttx> Have a nice week :)
[14:21] <ttx> #endmeeting
[14:21] <MootBot> Meeting finished at 08:21.
[14:21] <ludovicc> not sure about it, I may start a contract. We'll keep in touch anyway
[16:44] <vikashkoushik> anybody there?
[16:45] <cody-somerville> no
[16:45] <vikashkoushik> hi
[16:45] <vikashkoushik> may i know who you are?
[16:46] <vikashkoushik> Is there any one in this room who has already got an @ubuntu.com email id?
[16:46] <cody-somerville> I have one
[16:47] <vikashkoushik> hey Cody i have a doubt.
[16:47] <vikashkoushik> Pls help me
[16:47] <cody-somerville> What is your doubt?
[16:47] <vikashkoushik> I have completed all the work to apply for the e-mail id.
[16:47] <vikashkoushik> I live in India
[16:48] <vikashkoushik> I haven't Contributed much like making a Seminar or things like that
[16:48] <vikashkoushik> but i did contribute by distributing CD's & solving people's problems in Launch Pad.
[16:49] <vikashkoushik> Do you think there is a chance for me to get an e-mail id?
[16:49] <vikashkoushik> Pls reply Cody
[16:50] <cody-somerville> vikashkoushik, Usually we look for a sustained and significant contribution
[16:50] <vikashkoushik> So u think I won't be able to get one?
[16:51] <vikashkoushik> But i did contribute by solving problems & i earned more than 10,000 karma's only by solving people's problems
[16:51] <davmor2> vikashkoushik: are you an ubuntu member?
[16:51] <vikashkoushik> An Ubuntero? Yes
[16:52] <vikashkoushik> Hey Cody pls reply
[16:52] <cody-somerville> vikashkoushik, To get a Ubuntu e-mail, you must be a Ubuntu member.
[16:52] <cody-somerville> To learn more about how to do so, please see http://www.ubuntu.com/community/processes/newmember
[16:53] <vikashkoushik> hey cody I've completed all those procedure
[16:54] <vikashkoushik> All I need to do is attend the meeting
[16:54] <cody-somerville> vikashkoushik, Wonderful. Well, I wish you luck at the meeting :)
[16:54] <vikashkoushik> Thanks dude.
[16:54] <vikashkoushik> But pls tell me
[16:55] <vikashkoushik> what kind of things do they ask you in the meeting?
[16:55] <vikashkoushik> Pls reply Cody
[16:56] <cody-somerville> vikashkoushik, You'll be asked about your contributions to Ubuntu.
[17:00] <vikashkoushik> Can someone pls tell me whether my contributions are enough to get an @ubuntu.com e-mail id?
[17:01] <cody-somerville> vikashkoushik, Do you have a wiki page describing your contributions?
[17:02] <vikashkoushik> Yes. the page is https://wiki.ubuntu.com/S.Vikash Koushik
[17:02] <vikashkoushik> hey you have to include Koushik also
[17:03] <vikashkoushik> leave space between Vikash & Koushik
[17:03] <vikashkoushik> Pls tell me Cody
[17:04] <vikashkoushik> Do you think it is enough?
[17:05] <cody-somerville> vikashkoushik, It seems that you're only been contributing for about two weeks. Unfortunately, we look for a much longer period of sustained and significant contribution from membership candidates.
[17:05] <vikashkoushik> How long should I contribute?
[17:06] <cody-somerville> Several months
[17:07] <vikashkoushik> Is 2 months enough?
[17:07] <cody-somerville> Probably not
[17:07] <vikashkoushik> But I have been distributing CD's since January
[17:08] <vikashkoushik> Which means that I have been Contributing for 3 months rite?
[17:09] <vikashkoushik> I have been copying the CD's and passing to my friends since Jan
[17:09] <cody-somerville> Most people do
[17:10] <vikashkoushik> So can't you consider my contribution started from January?
[17:11] <vikashkoushik> pls reply
[17:12] <vikashkoushik> pls reply Cody
[17:13] <davmor2> vikashkoushik: It needs to be continued contribution that can be seen.  Just continue the work you're doing and you'll see that the time will soon fly by.  Also you'll need to get support from people who can recommend you for the work you are doing
[17:13] <vikashkoushik> I didn't get your second line.
[17:14] <vikashkoushik> To who should they come and recommend ?
[17:16] <vikashkoushik> To whom should they recommend?
[17:16] <Ampelbein> vikashkoushik: https://wiki.ubuntu.com/Membership for a complete overview
[17:18] <vikashkoushik> Hey Ampelbein I have completed all the steps over there.I just have to attend the meeting.
[17:18] <vikashkoushik> I just wanted to know to whom should people come & recommend for the work that i am doing?
[17:18] <vikashkoushik> Pls reply
[17:20] <Ampelbein> vikashkoushik: they should attend the scheduled meeting. and please don't say "pls reply" directly after your response. at least give us a chance to type our answer.
[17:20] <vikashkoushik> i am sorry Amplebein.
[17:20] <Ampelbein> vikashkoushik: on what wikipage have you added yourself as a prospective member?
[17:21] <vikashkoushik> https://wiki.ubuntu.com/S.Vikash Koushik
[17:21] <vikashkoushik> Note: After Vikash leave a gap before typing Koushik
[17:21] <Ampelbein> vikashkoushik: please read https://wiki.ubuntu.com/Membership again to find out where to correctly add yourself to the agenda.
[17:21] <vikashkoushik> i know that.
[17:21] <Ampelbein> hint: it's with one of the regional approval boards.
[17:22] <vikashkoushik> I am busy on 14th.
[17:22] <vikashkoushik> So I am planning to attend it on the next meeting
[17:22] <Ampelbein> vikashkoushik: so add yourself now with a note that you'll be there on the meeting after next.
[17:23] <vikashkoushik> Is it necessary that the person who is going to recommend for my work already has the id?
[17:24] <Ampelbein> vikashkoushik: not that i know.
[17:26] <vikashkoushik> Is it ok if the people who is going to recommend my work leave a testimonial on my wiki page?
[17:27] <Ampelbein> vikashkoushik: as that is described in https://wiki.ubuntu.com/Membership on the bottom, yes.
[17:27] <vikashkoushik> thanks
[17:28] <vikashkoushik> I really need to get that @ubuntu.com id.
[17:28] <cody-somerville> vikashkoushik, why do you need it so much?
[17:29] <vikashkoushik> Its because I LOVE ubuntu that much
[17:31] <vikashkoushik> Ever since I heard about ubuntu i've always been speaking about ubuntu,ubuntu and only ubuntu.
[17:32] <vikashkoushik> and i want people to know about ubuntu as i send a lot of e-mails on a single day
[17:35] <vikashkoushik> Is there any chance of me to get the id on 14th if I attend the meeting with the testimonials on my wiki page?
[17:39] <vikashkoushik> Is there any chance of me to get the id on 14th if I attend the meeting with enough testimonials on my wiki page?
[17:42] <Ampelbein> vikashkoushik: don't message me privately. just ask in the channel and when someone knows the answer he will reply.
[17:43] <vikashkoushik> I have more than 10,000 karma's just by solving people's problems. Do you think that is a significant contribution?
[17:51] <GunbladeIV> vikashkoushik, i think they wll look into your contribution.  Just update your wiki and submit your application on their wiki site.
[17:53] <vikashkoushik> all i've contributed is distributing CD's & solving people's problem in launch pad & i've earned 10,000 karma's.Is that enough?
[17:54] <GunbladeIV> vikashkoushik, they wanted to see sustained contribution. vikashkoushik you can try, but the board will decide.  I've tried once, and will try again.
[17:55] <vikashkoushik> What are were your contributions when you tried the first time?
[17:56] <GunbladeIV> vikashkoushik, im more into web thingy for my loco.. im the webmaster.  i do involve with some events for my loco. but they want to see sustained effort from me.
[17:56] <vikashkoushik> hmm...
[17:57] <GunbladeIV> vikashkoushik, it's not a bad thing actually, at least you will ty harder and it will be more precious once you are being approve
[17:59] <vikashkoushik> the thing is that i get disappointed if i am rejected.
[18:01] <GunbladeIV> vikashkoushik, dont get disappointed yet.  Just give it a try
[18:01] <GunbladeIV> vikashkoushik, make sure you put every contribution in your wiki even it's a small contribution
[18:02] <vikashkoushik> Like i said The only contribution that i've made are distributing cd's & solving people's problems.
[18:03] <vikashkoushik> As i live in India there is no way for me to conduct Seminar like many people that i've seen on the wiki page.
[22:00] <NCommander> #startmeeting
[22:00] <MootBot> Meeting started at 16:00. The chair is NCommander.
[22:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[22:01] <lool> yay!
[22:01] <NCommander> lool, :-)
[22:01] <lool> [link] https://wiki.ubuntu.com/MobileTeam/Roadmap
[22:01] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/Roadmap
[22:01]  * NCommander just updated that too
[22:02]  * NCommander waits for the pages to save
[22:02] <NCommander> [link] https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20090409
[22:02] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20090409
[22:03] <NCommander> Ok, lets begin
[22:03] <NCommander> [topic] Specification Review
[22:03] <MootBot> New Topic:  Specification Review
[22:03] <NCommander> [topic] offline-installer (ogra)
[22:03] <MootBot> New Topic:  offline-installer (ogra)
[22:04] <ogra> co
[22:04] <ogra> err
[22:04] <NCommander> do we have persia today?
[22:04] <ogra> dont we start with action items ?
[22:04] <NCommander> ah ****
[22:04]  * NCommander is still not used to charing
[22:04] <NCommander> [topic] Action Item Review
[22:04] <MootBot> New Topic:  Action Item Review
[22:04] <lool> It's weird to see NCommander post the checklist he has to follow and then start doing something else
[22:04] <lool> I was wondering whether I had forgotten how meetings were happening :)
[22:04]  * ScottK hands NCommander an 'i'
[22:05] <lool> an 'i' char
[22:05] <NCommander> Ok, no persia
[22:05] <NCommander> SO his items carry over
[22:05] <NCommander> [topic] lool to spec ec2-package-builder for jaunty+1 (co)
[22:05] <MootBot> New Topic:  lool to spec ec2-package-builder for jaunty+1 (co)
[22:05] <lool> co++
[22:05] <NCommander> [topic] ogra to trim selection-of-arm-images to a smaller scope (co)
[22:05] <MootBot> New Topic:  ogra to trim selection-of-arm-images to a smaller scope (co)
[22:05] <ogra> co
[22:05] <NCommander> [topic] ogra to trim selection-of-arm-images to a smaller scope (co)
[22:05] <MootBot> New Topic:  ogra to trim selection-of-arm-images to a smaller scope (co)
[22:05] <ogra> (for the rest as well)
[22:06] <NCommander> Oh
[22:06] <NCommander> #topic GrueMaster to test new Aspire One kernel
[22:06] <NCommander> er
[22:06] <NCommander> [topic] GrueMaster to test new Aspire One kernel
[22:06] <MootBot> New Topic:  GrueMaster to test new Aspire One kernel
[22:06] <GrueMaster> what is this new kernel?
[22:06] <ogra> i didnt have any time to work on anything but babbage ... same goes for lool i guess
[22:06] <NCommander> hrm, that should have been testing the last kernel upload on the aspire one
[22:06] <NCommander> ^- lool
[22:06] <lool> ?
[22:07] <GrueMaster> If that's the case, then it is done as it is in the new image.
[22:07] <GrueMaster> I'm assuming this is referring to the acer-wmi issue.
[22:07] <lool> I don't recall this action
[22:07] <lool> Oh right
[22:07] <NCommander> Apr 02 17:26:42 <ubottu>	Launchpad bug 319825 in linux "acer_wmi in Jaunty on Aspire One exposes non-functional (always disabled) rfkill device" [Medium,Fix released] https://launchpad.net/bugs/319825
[22:07] <NCommander> Apr 02 17:27:04 <lool>	All last bugs dropped
[22:07] <NCommander> Apr 02 17:27:06 <lool>	fix released
[22:07] <NCommander> Apr 02 17:27:12 <GrueMaster>	Will retest once new kernel is in the image.
[22:07] <GrueMaster> Looks good.
[22:07] <lool> Cool
[22:08] <NCommander> [topic] GrueMaster to test newer version of Hildon Desktop to see if it resolves cat kills MID bug
[22:08] <MootBot> New Topic:  GrueMaster to test newer version of Hildon Desktop to see if it resolves cat kills MID bug
[22:08] <GrueMaster> WIP.  Just started on it this morning.
[22:08]  * NCommander carries over
[22:08] <NCommander> Thats it on action items
[22:09] <NCommander> [topic] Spec Review
[22:09] <MootBot> New Topic:  Spec Review
[22:09] <NCommander> [topic]  arm-library-optimisation (lool)
[22:09] <MootBot> New Topic:   arm-library-optimisation (lool)
[22:09] <lool> Pushed pango and gtk+ to PPA; pango looking good, gtk takes ages to build there, also building on my babbage now
[22:10] <NCommander> [topic]  general-resolution-for-touchscreen-handling
[22:10] <MootBot> New Topic:   general-resolution-for-touchscreen-handling
[22:10] <lool> Will attack cairo next; ffmpeg-debian is for persia
[22:10] <lool> (unless persia preempts cairo)
[22:10] <ogra> KK topic, will register a new spec
[22:10] <NCommander> [topic] arm-softboot-loader
[22:10] <MootBot> New Topic:  arm-softboot-loader
[22:10] <NCommander> KK, new spec will be written
[22:10] <NCommander> [topic] selection-of-arm-images
[22:10] <MootBot> New Topic:  selection-of-arm-images
[22:11] <persia> Don't create new specs: just revise the old ones: all the right people are already subscribed.
[22:11] <ogra> implemented, will have to be revisited if we get new subarches
[22:11] <NCommander> oh, persia is here
[22:11] <ogra> persia, the touchscreen stuff will need a completely new one
[22:12] <NCommander> [topic] mobile-setup-wizard (persia)
[22:12] <MootBot> New Topic:  mobile-setup-wizard (persia)
[22:12] <persia> no change in status.  Mostly an issue with interface size at this point.
[22:12] <NCommander> [topic] poulsbo-packaging (persia)
[22:12] <MootBot> New Topic:  poulsbo-packaging (persia)
[22:12] <persia> no change.
[22:12] <NCommander> [topic] lpia-versus-i386 (lool)
[22:13] <MootBot> New Topic:  lpia-versus-i386 (lool)
[22:13] <lool> Opened a RT to add a wrapper
[22:13] <lool> We need to implement this wrapper
[22:13] <NCommander> wrapper?
[22:13] <lool> A gcc wrapper to set -Os
[22:13] <NCommander> Oh, is this the lets build with -Os?
[22:13] <NCommander> lool, do we need an action item for this?
[22:13] <lool> I'm taking volunteers with CFT to implement that before karmic
[22:13] <NCommander> VFT?
[22:13] <NCommander> *CFT?
[22:13] <lool> Copious Free Time
[22:14] <NCommander> I'll take it
[22:14] <GrueMaster> 1...2...3...not it.
[22:14] <lool> Ok; you should start from hardening wrapper, will send you the email
[22:14] <NCommander> [action] NCommander to coordinate with lool and re-purpose hardening-wrapper to pass -Os on lpia builds
[22:14] <MootBot> ACTION received:  NCommander to coordinate with lool and re-purpose hardening-wrapper to pass -Os on lpia builds
[22:15] <lool> NCommander: I've sent you the info
[22:15] <NCommander> thanks
[22:15] <NCommander> [topic] mobile-spec-cleanup (persia)
[22:15] <MootBot> New Topic:  mobile-spec-cleanup (persia)
[22:16] <NCommander> Guess ENOPERSIA
[22:16] <persia> I've raised the priority on this, with UDS coming up, and now expect to finish pre-release.
[22:16] <NCommander> Oh
[22:17] <NCommander> [topic] Ongoing Projects
[22:17] <MootBot> New Topic:  Ongoing Projects
[22:17] <NCommander> [topic] Babbage Enablement (ogra)
[22:17] <MootBot> New Topic:  Babbage Enablement (ogra)
[22:17] <ogra> done !
[22:17] <NCommander> yay!
[22:17] <ogra> still has small issues, but generally good
[22:17] <ogra> we wait for an NM upload
[22:17] <ogra> ubiquity is up but not in the image yet
[22:17] <ogra> usplash doesnt work
[22:18] <NCommander> ogra, I'm trying to find out if it works on PowerPC which is also VESA lacking
[22:18] <ogra> and there was one watchdog oops with the wired NIC that didnt cause any issues but showed up
[22:18] <ogra> it does
[22:18] <ogra> or it did when i used my PPC last which is a while ago
[22:18] <ogra> like gutsy
[22:19] <ogra> but its not really relevant, we wont be able to fix it in jaunty
[22:19] <NCommander> ogra, I know usplash USED to support fb devices
[22:19] <ogra> and in KK the whole thing will change
[22:19] <NCommander> There's an open bug on it
[22:19] <ogra> yes, fb devices that are able to report vesa modes
[22:19] <ogra> we have only one fixed size we can support
[22:20] <ogra> what someone should test is to create an 800x600 usplash.conf, re-roll initramfs and test that
[22:20] <NCommander> I'll take that, since I'm already setup to
[22:20] <NCommander> [action] NCommander to test usplash at 800x600
[22:20] <MootBot> ACTION received:  NCommander to test usplash at 800x600
[22:20] <ogra> it might work with a fixed predefined size (though i'm not sure about that)
[22:21] <NCommander> [topic] High Priority Bugs
[22:21] <MootBot> New Topic:  High Priority Bugs
[22:21] <ogra> one open thing we still have is to test kernel upgrades
[22:21] <lool> ogra: Could you test them?
[22:21] <ogra> we are nopt sure yet if update-initramfs properly triggers flash-kernel
[22:21] <ogra> now ? ... hmm
[22:21] <plars> lool: on babbage?
[22:21] <ogra> ok
[22:21] <lool> No, not now, soon
[22:21] <ogra> plars, yes
[22:21] <NCommander> [action] ogra to test kernel updates
[22:21] <lool> plars: yup
[22:21] <MootBot> ACTION received:  ogra to test kernel updates
[22:21] <ogra> ok, will do
[22:21] <plars> it worked with the kernel you rerolled a while back lool
[22:22] <plars> don't know if that was representative though
[22:22] <lool> plars: Did you see the update-initramfs call as well?
[22:22] <ogra> plars, did it run update-initramfs before running flash-kernel ?
[22:22] <ogra> the order is important
[22:22] <lool> What would be good is an udev upgrade
[22:22] <plars> hmm... that was about 2 weeks ago, I slept since then
[22:22] <lool> Just reinstall one initramfs package, such as udev
[22:22] <ogra> you did ?
[22:22] <lool> That should be enough
[22:22] <ogra> geez
[22:23] <ogra> lool, make a note plars still has time to sleep ... not enough workload yet :P
[22:23]  * NCommander wonders if that should be a bug or an action item :-)
[22:23] <knome> bug!
[22:23] <plars> heh
[22:24] <NCommander> [topic] bug #328167: gnome-keyring-daemon eats all CPU on ARM when starting a GNOME session
[22:24] <MootBot> New Topic:  bug #328167: gnome-keyring-daemon eats all CPU on ARM when starting a GNOME session
[22:24]  * ogra runs apt-get install --reinstall udev as we speak
[22:25] <ogra> NCommander, worked around but not fixed, please drop the bug from roadmap but keep the action item for me
[22:25] <ogra> lool, no flash-kernel :(
[22:25] <lool> No surprize
[22:25] <ogra> against what do i file that ?
[22:25]  * NCommander always remembers on the slug it was a manual step
[22:26] <ogra> initramfs-tools ?
[22:26] <lool> ogra: Yeah
[22:26] <NCommander> [action] ogra to continue investigation of #328167
[22:26] <MootBot> ACTION received:  ogra to continue investigation of #328167
[22:26] <ogra> NCommander, well, actually only providing a BT to upstream
[22:26] <ogra> so they can find the cause (i thought you did one yesterday though)
[22:26] <NCommander> ogra, I can do that; I have a full backtrace from the ddebs (I thought I posted it but it seems I'm loosing it)
[22:27] <NCommander> ogra, my BTs however only showed one thread running so if you want to run one as well, it would help
[22:27] <ogra> NCommander, on the upstream bug please
[22:27] <NCommander> [action] ogra and NCommander to post backtraces of #328167 for upstream
[22:27] <MootBot> ACTION received:  ogra and NCommander to post backtraces of #328167 for upstream
[22:28] <NCommander> [topic] bug #338148: VNC4 FTBFS
[22:28] <MootBot> New Topic:  bug #338148: VNC4 FTBFS
[22:29] <NCommander> This moved from persia's plate to my own, I confirmed the Debian source package does build fine on Ubuntu. It looks like we can simply sync it, but it I need to test to make sure all patches have been properly merged or gone upstream
[22:29] <persia> Except we can't sync it because our X trees differ.
[22:29] <NCommander> oh
[22:29] <NCommander> so much for that idea.
[22:29] <persia> And parts of the X trees are merged.
[22:29] <persia> Otherwise it would be easy :)
[22:30] <NCommander> persia, I'm suprised it even built on Ubuntu then
[22:30] <NCommander> What a PTIA
[22:30] <persia> Your experience mirrors mine: "That's easy, wait..." :)
[22:30] <NCommander> Not to be a pill, but this isn't an ARM issue
[22:30] <ogra> lool, bug 358762
[22:30] <NCommander> Can't we toss this onto the X guys plate?
[22:30] <ogra> lool, do you want that milestoned etc ?
[22:31] <lool> Yes
[22:31] <lool> High
[22:31] <ogra> can you confirm it ?
[22:31] <NCommander> ogra, I added that on the Roadmap
[22:31] <ogra> good
[22:31]  * ogra would like to not confirm it himself
[22:32] <NCommander> [topic] bug #349504: if system date is set to 01-01-1970 users are enforced to update their password
[22:32] <MootBot> New Topic:  bug #349504: if system date is set to 01-01-1970 users are enforced to update their password
[22:32] <NCommander> That was mine, fixed released :-)
[22:32] <NCommander> *fix released
[22:32] <plars> I can confirm it works now
[22:33] <NCommander> woo
[22:33] <plars> now if I could just keep the date after setting it on my system :(
[22:33] <NCommander> plars, mine survives reboots, but it goes away if I unplug the box
[22:33] <NCommander> :-/
[22:33] <lool> update-initramfs: deferring update (trigger activated)
[22:33] <lool> No flash-kernel
[22:33] <ogra> lool, hmm, update-initramfs has detection code for lilo based systems .. there it only spills a warning
[22:33] <plars> NCommander: right
[22:33] <NCommander> [topic] Low priority bugs
[22:33] <MootBot> New Topic:  Low priority bugs
[22:34] <ogra> but doesnt run lilo
[22:34] <NCommander> [topic] #299847 libipc-sharelite-perl FTBFS on armel
[22:34] <MootBot> New Topic:  #299847 libipc-sharelite-perl FTBFS on armel
[22:34] <lool> ogra: You need to target to release
[22:34] <lool> I did that now
[22:34] <NCommander> No progress, none excepted until its either reproduced on something beside the buildds, or we replace the buildds :-)
[22:34] <NCommander> [topic] bug #280669: DMA mode and driver on jax10
[22:34] <MootBot> New Topic:  bug #280669: DMA mode and driver on jax10
[22:35] <NCommander> Talked with apw, decided we didn't need the patch.
[22:35] <NCommander> Scratched off the roadmap :-)
[22:35] <NCommander> [topic] Open Discussion
[22:35] <MootBot> New Topic:  Open Discussion
[22:35] <ogra> lool, ah, no, the warning is only for the case where lilo and grub are both installed, else it runs lilo
[22:35] <ogra> lool, so we can just steal that code
[22:35] <GrueMaster> bug #337809
[22:35] <persia> So, I posted a call for specs for karmic.  Has everyone registered a couple yet?
[22:35] <NCommander> ogra, are you taking the update-initramfs issue?
[22:35] <NCommander> Oh, right
[22:35] <NCommander> Ahem
[22:36] <NCommander> [topic] Specs for karmic
[22:36] <MootBot> New Topic:  Specs for karmic
[22:36] <persia> Anyone have questions about the procedure or the deadline?
[22:36] <ogra> why is that still there ?
[22:36] <knome> persia, what is the deadline?
[22:36] <ogra> it was just a notification from david
[22:36] <GrueMaster> Procedure, yes.
[22:36] <persia> GrueMaster, what's the question?
[22:36] <plars> persia: having never been through it before, not even sure what to ask
[22:36] <NCommander> ogra, it wasn't on the roadmap, I brought it up for persia
[22:37] <GrueMaster> need to find the email again first, then I'll ask.
[22:37] <ogra> NCommander, ah, but it shouldnt be a constant item
[22:37] <NCommander> ogra, its not on the roadmap
[22:37] <ogra> good
[22:37] <lool> ogra: well it would be cool to avoid running flash-kernel twice
[22:37] <persia> plars, Basically, we determine what we're going to look at for the next cycle, and start drafting specifications for discussion at UDS.
[22:37] <ogra> lool, well, i doubt you can
[22:37] <lool> ogra: perhaps check discussion in debian-boot?
[22:38] <ogra> you will only run it twice if a kernel is installed as well
[22:38] <lool> That's what I mean
[22:38] <knome> NCommander, maybe you have a minute after the meeting?
[22:38] <ogra> it will run once on normal update-initramfs runs
[22:38] <lool> We only rebuild initrd once
[22:38] <NCommander> knome, sure
[22:38] <lool> Would be nice to only flash-kernel once
[22:38] <knome> NCommander, just ping me once you are free
[22:38] <lool> ogra: Anyway, I don't want to discuss this tonight => /me is tired
[22:39] <plars> persia: I understand that much, but are these basically wishlist items? or things that have already been fully architected, designed, and have a start on implementation?  Also, with the requirement about needing to sign up to implement it, not sure what to do at this point
[22:39] <NCommander> GrueMaster, I haven't had that APCI issue on real hardware
[22:39]  * ogra just doesnt understand if its dangerous or cosmetic issues lool has with that
[22:39] <lool> plars: It's exactly in between: stuff which will be implemented and we need to architect properly
[22:39] <ogra> if its the latter we shouldnt care in jaunty
[22:39] <GrueMaster> I have.  Crown Beach and Acer Aspire One.
[22:39] <persia> plars, Somewhere between wishlist and started :)  It should be achievable within the timeframe, and testable for release.
[22:40] <lool> ogra: It's cosmetic; I'm trying to shoot for the proper design first when I can though
[22:40] <NCommander> GrueMaster, can you try to reproduce with the alternate image? (I just want to see if its live only, since I haven't seen it)
[22:40] <GrueMaster> Goes away if you add apci=ht to the kernel
[22:40] <NCommander> GrueMaster, its on the roadmap
[22:40] <ogra> lool, right, but we'Re at a point where changes need to be minimal
[22:40] <lool> Yes
[22:40] <ogra> proper design means big changes in this case
[22:40]  * persia waves the specifications flag harder, in the hopes that people notice that the deadline is *before* release.
[22:40] <lool> I agree you have little time to think about this and it's likely we hardcode a call to flash-kernel $somewhere
[22:41] <ogra> but lets discuss that later, not tonight
[22:41] <lool> persia: I'm afraid I'm buried in release stuff
[22:41]  * ogra agrees with the tiredness
[22:41]  * lool beats persia with the release flag
[22:41] <ogra> persia, davidm said all that last week
[22:41] <persia> lool, I understand, but anything not put up before the 21st won't make UDS.
[22:41] <persia> I didn't make up the deadline, and it's fairly firm.
[22:42] <ogra> its only about registering slots in the UDS schedule
[22:42] <lool> Perhaps we could move the release by a week to work a little on the specs?   ;-)
[22:42] <persia> heh :)
[22:43] <persia> Anyway, the specs don't need to be *done*, just outlined.  Registration, title, summary, etc.
[22:43] <ogra> not even that
[22:43] <davidm> Sorry guys I know it's a pain but I'm getting pushed hard on this.
[22:43] <persia> Yes, all of that.
[22:43] <ogra> LP blueprint and entry on the wikipage for the schedule
[22:43] <persia> ogra, And summary.
[22:43]  * NCommander notes we are two weeks from release
[22:43] <ogra> its really only for the schedule
[22:43] <NCommander> REPENT, THE END IS NEAR!
[22:43] <NCommander> :-)
[22:44] <GrueMaster> When is RC?
[22:44] <ogra> thu
[22:44] <NCommander> GrueMaster, 7 days
[22:44] <NCommander> Oooooh
[22:44] <NCommander> that remidns me
[22:44] <NCommander> Someone needs to get Babbage on the ISO tester
[22:44] <ogra> milestones and releases are always on thursdays
[22:44] <ogra> we're the thursday distro ;)
[22:45]  * NCommander wonders if that was true for Dapper as well ...
[22:45] <persia> Yes.
[22:45] <lool> Ah I have a topic to add
[22:45] <NCommander> dapper will always have a special place in my heart for its version
[22:45] <NCommander> lool, go ahead
[22:45] <lool> what images do we want to test for release exactly?
[22:46] <lool> I had in mind to test ubuntu live (gnome) for babbage, perhaps the xubuntu one; I wonder about the server one
[22:46] <ogra> nslu2, babbage versatile, UNR, MID
[22:46] <lool> And then UNR MID as usual and the netboots
[22:46] <NCommander> lpia alternative
[22:46] <NCommander> (now that we have them)
[22:46] <GrueMaster> With all of the images currently available, we need to divvy up the load a bit.
[22:47] <lool> Are all of these in the tracker
[22:47] <NCommander> lool, no
[22:47] <NCommander> lool, well, UNR and MID are. NSLU2, Babbage, Versatile, and lpia alt are not
[22:47] <lool> GrueMaster: ack, they are too many, i'm losing track of what to test
[22:47] <NCommander> BTW, will we be getting Babbage alternatives? (the installer works)
[22:47] <NCommander> (we just need the image building bits)
[22:47] <lool> NCommander: there's an entry for netboot I think
[22:47]  * ogra would actually prefer to not have NSLU2 on the tracker :P
[22:48] <lool> NCommander: You tried alternate armel on SD card?
[22:48] <lool> I made it build, but never heard of anybody running it
[22:48] <NCommander> lool, yeah, both netboot and cdrom
[22:48] <NCommander> Both work and run through the entire install
[22:48] <lool> Oh the d-i ones, not the alternate ones
[22:48] <NCommander> At the time it didn't install the kernel though, but that was about a week ago, so that should be fixed.
[22:48] <GrueMaster> The reason I suggest spreading the load is due to download and install times.  It takes almost an hour to download and install babbage image, let alone do any substantive testing.
[22:48] <lool> Err a week ago we weren't building SD cards for alternate
[22:49] <NCommander> lool, I was on the impression the SD cards for alternative didn't have the initrd in place, if thats changed, I'll test them
[22:49] <lool> NCommander: What did you test exactly?  The d-i bits?
[22:50] <lool> You grabbed stuff from ports.u.c, right?
[22:50] <lool> GrueMaster: ack
[22:50] <NCommander> lool, I took the d-i kernel and initramfs, put them on the SD card and ran the install
[22:50] <lool> GrueMaster: one hour sounds a bit long; it's shorter here, and I'm not rich in bandwidth
[22:50] <NCommander> It completed except for installing the kernel and bootloader since at that point the postinst had not been implemented to my knowledge.
[22:50] <lool> GrueMaster: I think we need to split the testing more, and limit the number of images
[22:51] <lool> davidm: What images do we really need well tested?
[22:51] <GrueMaster> That includes install.  My install just completed, and I started it at the beginning of the meeting.
[22:51] <plars> Do we have hardware for all of these images?  I've had poor success getting the arm netboot images running well under qemu
[22:51] <lool> NCommander: Ok, what I was speaking about with alternate images were the cdimage ones below /ports/daily
[22:52] <lool> plars: They should work
[22:52] <lool> plars: Unless they are broken, which is possible
[22:52] <lool> That's for versatile
[22:52] <NCommander> lool, that I can test
[22:52] <lool> For iop32x, I have hardware (but nobody cares) and for ixp4xx NCommander and ogra have hardware
[22:52] <plars> lool: versatile is the one I'm trying right now, and it takes somewhere around 12 hours just to complete the install
[22:52] <lool> That's all netboots
[22:52] <lool> That's long
[22:52] <NCommander> I thought one of us had orion5x hardware as well
[22:52] <ogra> lool, well, i just saw infinity complaining that libc6-vfp gets pulled in on all armel arches
[22:53] <ogra> lool, the versatile slowness could be caused by that
[22:53] <lool> Uh no
[22:53] <lool> Does it claim VFP?
[22:53] <ogra> no idea, but vfp is a dep of ubuntu-minimal
[22:53] <lool> Yes, that's intended
[22:53] <persia> I have orion5x hardware, but I was told that kernel was dropped.
[22:53] <lool> Just like i686
[22:54] <NCommander> persia, not yet to my knowledge
[22:54] <lool> plars, ogra: Could one of you confirm whether libc6-vfp is the culprit?
[22:54] <lool> And file a bug
[22:54] <persia> Oh, then I'll try an install once I get the rest of the VFP stuff sorted.
[22:54] <lool> We could perhaps still fix that
[22:54] <ogra> lool, i have nslu2
[22:54] <lool> In qemu
[22:54] <ogra> plars, ^^^ can you care for versatile ?
[22:55] <lool> ogra: It wont slow down on NSLU2 for sure
[22:55] <ogra> no, but nslu2 eats my time
[22:55] <lool> The question is in qemu, perhaps emulating a VFP via qemu is slower than running emulated floats in qemu
[22:55] <plars> ogra: I can try, but it's almost too slow to even try to test anything
[22:55] <ogra> so i would prefer to stick with babbage and nslu2 if i'm not urgently needed
[22:55] <lool> plars: Use a shell and move the vfp lib away
[22:55] <lool> plars: See if that helps in qemu
[22:55] <plars> lool: I'll try that
[22:56] <persia> NCommander, According to https://launchpad.net/ubuntu/+source/linux/2.6.28-11.41/+build/941224 it is gone.
[22:56] <ogra> plars, if you need help i'm there
[22:56] <plars> ogra: thanks
[22:56] <ogra> i just dont want to lead this additionally
[22:56] <NCommander> persia, then feel free to ignore me
[22:56] <NCommander> So who wants the action item to see that getting onto the release tracker?
[22:56] <lool> davidm: What images do we really need well tested?
[22:57] <plars> NCommander: I can probably see about that if I have a good list of what should be there exactly
[22:57]  * persia points out that there are 3 minutes left.
[22:58] <NCommander> Oh, important heads up
[22:59] <lool> plars: Let's stick with the conservative: MID, UNR -- already there; we need to split netboot probably, and then imx51 live, and perhaps lpia alternate
[22:59] <NCommander> I'm not going to be around tomorrow for Easter, or if I am, I will only be so in the morning in all likelyhood.
[22:59] <plars> same here
[23:00] <GrueMaster> I'll be around unless the sun comes out, then I'll be at the golf course hiding my golf balls around the course.  :P
[23:02] <NCommander> Anyway
[23:02] <NCommander> Final announcements going in 3
[23:02] <NCommander> 2
[23:02] <NCommander> 1
[23:02] <NCommander> #endmeeting
[23:02] <MootBot> Meeting finished at 17:02.
[23:02] <ogra> thanks NCommander
[23:03] <lool> yes, thanks NCommander
[23:03] <NCommander> np ogra and lool
[23:03] <NCommander> minutes are up already


[03:19] -queuebot:#ubuntu-release- Unapproved: update-motd (focal-proposed/main) [3.6-0ubuntu6 => 3.6-0ubuntu6.1] (core)
[03:40] -queuebot:#ubuntu-release- Unapproved: openjfx (focal-proposed/universe) [11.0.7+0-2ubuntu1 => 11.0.7+0-2ubuntu2] (no packageset) (sync)
[04:30] <amurray> Laney bdmurray sil2100: would someone from the release team be able to take a look at iptables FFe bug https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1894195 ? thanks :)
[04:49] -queuebot:#ubuntu-release- Unapproved: libfprint (focal-proposed/main) [1:1.90.2+tod1-0ubuntu1~20.04.1 => 1:1.90.2+tod1-0ubuntu1~20.04.2] (desktop-core, ubuntu-desktop)
[05:08] <rafaeldtinoco> Sorry to bother release team. I need FFe for https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1896223 and Im just highlighting that because next week I'm likely moving into new job role for some months and I would like to guarantee the upload, if possible, before that happens. Thanks for understanding and sorry for the rush, I know you're
[05:08] <rafaeldtinoco> all very busy.
[06:14] <LocutusOfBorg> vorlon, libdc1394 took over the -dev packages from libdc1394-22, so I presume everything (e.g. opencv, gst-plugins-bad1.0, ffmpeg) now needs it
[06:15] <LocutusOfBorg> I plan to do the no change rebuilds so we can remove libdc1394-22 from i386
[06:15] <LocutusOfBorg> right now ffmpeg is waiting for it
[06:21] <LocutusOfBorg> debian already did the rebulds
[06:43] <LocutusOfBorg> I issued rebuilds
[07:35] <sil2100> Hello! Can I get an ubuntu-release member to take a look at my ubuntu-image FFe? https://bugs.launchpad.net/ubuntu/+source/ubuntu-image/+bug/1896744
[07:59] -queuebot:#ubuntu-release- Unapproved: gnome-flashback (focal-proposed/universe) [3.36.4-0ubuntu1 => 3.36.4-0ubuntu2] (edubuntu)
[08:00] -queuebot:#ubuntu-release- Unapproved: gnome-flashback (bionic-proposed/universe) [3.28.0-1ubuntu1.4 => 3.28.0-1ubuntu1.5] (edubuntu)
[08:00] -queuebot:#ubuntu-release- Unapproved: gnome-flashback (focal-proposed/universe) [3.36.4-0ubuntu1 => 3.36.4-0ubuntu1.1] (edubuntu)
[08:01] <Mirv> ^ please remove the focal with wrong SRU version ubuntu2
[08:03] -queuebot:#ubuntu-release- Unapproved: rejected gnome-flashback [source] (focal-proposed) [3.36.4-0ubuntu2]
[08:04] <Laney> vorlon: In _merge_binaries() I made oodarchs [sic?] a dict keyed by arch. It was deciding that the package was out of date on i386 (correctly I guess, arch:all binary) and merging those binaries into -proposed. But then this was carrying over to all the later arches, and so the dropped binaries for those were merged into proposed too, which made them show up as NBS in proposed.
[08:05] <Laney> I've been doing fixups, because eventually I'll be submitting most of this stuff upstream, and it's easier if the commits are already close to that state
[08:31] <sil2100> cpaelzer: hey! Looking at the libvirt focal SRU right now - you think we could get IBM's -proposed package verification in the nearest time, or you think this what we got is the best we can count for?
[08:35] <Laney> sil2100: I'll look at ubuntu-image for you now, was hoping someone else would :P
[08:37] <Laney> is it possible to run that test case before uploading or does it need to be a PROPOSED=1 build?
[08:38] <apw> Laney, out-of-date-archs ?
[08:42] <Laney> apw: seems unlikely as a python variable name :p
[08:42] <apw> :) it is rather short for python that is for sure
[08:42] <Laney> https://git.launchpad.net/~ubuntu-release/britney/+git/britney2-ubuntu/tree/britney2/inputs/suiteloader.py#n244
[08:42] <Laney> oodsrcs!
[08:55] <sil2100> Laney: you mean the ubuntu-image test case?
[08:56] <Laney> yus
[08:56] <Laney> in the bug description
[08:56] <cpaelzer> sil2100: I don't think we can expect them verifying it again anytime soon
[08:56] <Laney> basically I want to say to you 'have you run that for groovy?'
[08:56] <Laney> but then I thought you might say no, that has to be done in the archive
[08:56] <Laney> :>
[08:56] <cpaelzer> sil2100: I did the x86 bits tha I could, but that particular s390x featu they look for isn't enabled on our box
[08:57] <sil2100> Laney: hah, ubuntu-image is just a set of python scripts and as mentioned, this change is already in the snap - so yeah, I did run it and I don't think it matters that it wasn't run against packages in the archive
[08:59] <Laney> mmm ok
[08:59] <sil2100> cpaelzer: hm hmm, ok, tricky then, I wouldn't want this SRU to just idle for too long because of this
[08:59] <Laney> that bit is a bit confusing to be honest, all the bits about some stuff being distro patched
[08:59] <Laney> it made me think it's not clear what is actually changing in this ffe upload
[08:59] <sil2100> cpaelzer: how big you think the risk of the PPA packages giving different results from the ones in the archive is?
[09:00] <apw> (are they copied with binaries or without)
[09:01] <sil2100> Laney: I might have written that a bit confusing ;p Since I guess the only things that are already in the archive are the dep-changes for fdisk, a test-fix and some flake8 compliance fixes
[09:02] <sil2100> Those are also in 1.10, but were distro-patched in the archive already - all the 'new features' are specific to the 1.10 upload
[09:02] <cpaelzer> sil2100: on the s390x side I'm less concerned
[09:02] <cpaelzer> sil2100: if anything I'm more concerned about missing an unexpected effect on x86
[09:02] <cpaelzer> sil2100: which I didn't find, but that does not mean it does not exist
[09:03] <cpaelzer> sil2100: yet the missing s390x verification wouldn't help with that anyway :-/
[09:06] <vorlon> LocutusOfBorg: thanks for the clarification, libdc1394/i386 triggered now
[09:07] <vorlon> Laney: ok. I'm wondering if somehow this change has anything to do with https://people.canonical.com/~ubuntu-archive/proposed-migration/groovy_uninst.txt suddenly showing pm-utils as uninstallable, even though its single dependency exists... not sure what else changed that would cause this
[09:08] <vorlon> seb128, Laney: would someone follow through on the updates needed for gst doc package removals? https://people.canonical.com/~ubuntu-archive/nbs.html
[09:17] <Laney> vorlon: it looks right, pm-utils is uninstallable in a chroot for me
[09:18] <vorlon> hmm, wasn't when I tested earlier
[09:18] <Laney> https://launchpad.net/ubuntu/groovy/amd64/powermgmt-base
[09:18] <Laney> wat
[09:18]  * vorlon double-checks
[09:18] <vorlon> wut
[09:19] <Laney> and ack on gstreamer, I was just reminded of that too by some conversations in #debian-gnome
[09:20] <cjwatson> powermgmt-base> This is another instance of bug 1896790 (compare https://launchpad.net/ubuntu/groovy/i386/powermgmt-base).  What's with all these single-architecture priority changes?
[09:20] <Laney> ah yes, of course. I'll copy it back
[09:21] <Laney> can we detect other instances of this proactively?
[09:21] <cjwatson> vorlon, please hold off on any further single-arch priority changes until we figure out what's going on here
[09:22] <cjwatson> I'm not sure, it's rather hard to detect and I couldn't think of a straightforward way to do it yesterday.  But I suppose I can think harder
[09:22] <cjwatson> Anything to do with the dominator algorithm always takes me a run-up
[09:23] <Laney> Might be easiest for vorlon to check shell history
[09:24] <vorlon> ah yes, powermgmt-base was also in the list of priority mismatches for i386 (and I had changed it at the same time as libdrm-common)
[09:24] <vorlon> I will definitely hold off
[09:25] <vorlon> based on shell history, I believe those should be the only two packages affected
[09:25] <cjwatson> (I think it's only single-arch override changes of Architecture: all packages, but that's slightly guesswork)
[09:25] <vorlon> yeah there were 9 packages that got overridden, only the two arch: all ones had problems
[09:26] <Laney> should be coming back now
[09:34] -queuebot:#ubuntu-release- Packageset: Removed libcdaudio from i386-whitelist in groovy
[09:34] -queuebot:#ubuntu-release- Packageset: Removed libusrsctp from i386-whitelist in groovy
[09:34] -queuebot:#ubuntu-release- Packageset: Added libdc1394 to i386-whitelist in groovy
[09:34] -queuebot:#ubuntu-release- Packageset: Added qttranslations-opensource-src to i386-whitelist in groovy
[09:55] <dgadomski> sil2100: hi, could you please take a look at initramfs-tools in x/b upload queues and cryptsetup in b/f if you have a moment?
[10:24] <sil2100> dgadomski: sure! Will do after lunch
[10:24] <dgadomski> great, thank you
[11:29] -queuebot:#ubuntu-release- New binary: linux-signed-azure-4.15 [amd64] (bionic-proposed/main) [4.15.0-1097.107] (no packageset)
[11:29] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (groovy-proposed/main) [5.8.0-20.21] (core, kernel)
[11:29] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (groovy-proposed/main) [5.8.0-20.21] (core, kernel)
[11:29] -queuebot:#ubuntu-release- New binary: linux-signed [s390x] (groovy-proposed/main) [5.8.0-20.21] (core, kernel)
[11:31] -queuebot:#ubuntu-release- New binary: linux-signed [arm64] (groovy-proposed/main) [5.8.0-20.21] (core, kernel)
[11:36] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (groovy-proposed) [5.8.0-20.21]
[11:36] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (groovy-proposed) [5.8.0-20.21]
[11:36] -queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (groovy-proposed) [5.8.0-20.21]
[11:36] -queuebot:#ubuntu-release- New: accepted linux-signed [s390x] (groovy-proposed) [5.8.0-20.21]
[11:36] -queuebot:#ubuntu-release- New: accepted linux-signed-azure-4.15 [amd64] (bionic-proposed) [4.15.0-1097.107]
[11:50] <Trevinho> sil2100: hey, have you seen my ping about that mutter FTBFS in bionic? No need to do it now, just to know... :)
[11:58] -queuebot:#ubuntu-release- Unapproved: mdadm (focal-proposed/main) [4.1-5ubuntu1 => 4.1-5ubuntu1.1] (core, i386-whitelist)
[12:44] <teward> rbasak: and AAs/SRU: SRU for sup-mail https://bugs.launchpad.net/ubuntu/+source/sup-mail/+bug/1888749 has been in NEW since July, if you want to go poking.
[12:45] <teward> (rbasak prodded in -motu RE: it so I thought i'd poke again)
[13:04] <sil2100> Trevinho: hey! Might have missed it!  We have a shim/shim-signed combo in -proposed right now, I see all the bugs for shim-signed verified, but the shim one is not - but also I don't see any test case there
[13:31] <sil2100> juliank: do you remember what's the story with that one?
[13:31] <juliank> sil2100: that was the regression in the 0ubuntu1 that got fixed in 0ubuntu2 but did not affect old releases
[13:32] <juliank> sil2100: now we can't really test that sensibly, as it was a path lookup/parsing gone wrong, and you need actual fwupd binaries to test it. However: the binaries are the same in all releases, so we checked it against groovy
[13:32] <juliank> sil2100: But: Should we also check whether loading those fwupd EFI binaries of older releases work even though that was not what the bug was about?
[13:36] <sil2100> cpaelzer: oh, uh, actually! Re: libvirt, doesn't comment #28 actually indicate testing using the -proposed packages?
[13:40] <sil2100> juliank: hm, no, I think that won't be necessary
[13:40] <sil2100> Ok, thank for clearing things out for me then
[13:44] <cpaelzer> sil2100: es #20 was on the PPA and #28 on -proposed
[13:44] <cpaelzer> so yes
[13:53] <LocutusOfBorg> doko, I syncd pypdf2, no reverse dependencies for python2 binding...
[13:56] -queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [source] (bionic-proposed) [0.130ubuntu3.11]
[13:59] -queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [source] (xenial-proposed) [0.122ubuntu8.17]
[14:03] <Trevinho> apw: any luck you can merge https://code.launchpad.net/~3v1n0/ubuntu-archive-tools/sru-review-bileto-support/+merge/364193 ? :)
[14:05] -queuebot:#ubuntu-release- Unapproved: bolt (focal-proposed/main) [0.8-4 => 0.8-4ubuntu1] (desktop-core, ubuntu-server)
[14:06] <sil2100> cpaelzer: \o/
[14:17] -queuebot:#ubuntu-release- Unapproved: python2.7 (focal-proposed/universe) [2.7.18~rc1-2 => 2.7.18-1~20.04] (i386-whitelist, kubuntu) (sync)
[14:24] -queuebot:#ubuntu-release- Unapproved: gcc-9-cross-mipsen (focal-proposed/universe) [4+c2ubuntu2 => 4+c2ubuntu2.1] (no packageset) (sync)
[14:25] -queuebot:#ubuntu-release- Unapproved: gcc-10-cross-mipsen (focal-proposed/universe) [2+c1 => 2+c1ubuntu1.1] (no packageset) (sync)
[14:30] -queuebot:#ubuntu-release- Unapproved: rejected mdadm [source] (focal-proposed) [4.1-5ubuntu1.1]
[14:32] -queuebot:#ubuntu-release- Unapproved: gnome-clocks (focal-proposed/universe) [3.36.0-1ubuntu0.2 => 3.36.2-1~ubuntu20.04.1] (desktop-extra)
[14:40] <bdmurray> sil2100: What do you think about the verification of bug 1894919 now?
[14:41] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (groovy-proposed/main) [5.8.0-1006.6] (core, kernel)
[14:41] -queuebot:#ubuntu-release- New binary: linux-signed-gcp [amd64] (groovy-proposed/main) [5.8.0-1004.4] (core, kernel)
[14:42] -queuebot:#ubuntu-release- New binary: linux-signed-oracle [amd64] (groovy-proposed/main) [5.8.0-1003.3] (core, kernel)
[14:43] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (groovy-proposed) [5.8.0-1006.6]
[14:43] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle [amd64] (groovy-proposed) [5.8.0-1003.3]
[14:43] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (groovy-proposed) [5.8.0-1004.4]
[14:45] <bdmurray> cjwatson: Could you look at the moderation queue for the ubuntu-release mailing list?
[14:49] <Laney> ah
[14:50] <Laney> I was going to ask around for the password for that list yesterday
[14:50] <Laney> Trevinh_o sent a mail that I would have moderated
[14:50] <Laney> maybe it could be shared about?
[14:51] -queuebot:#ubuntu-release- Unapproved: accepted mdadm [source] (focal-proposed) [4.1-5ubuntu1.1]
[14:56] <sil2100> bdmurray: looking!
[14:59] <juliank> sil2100: I marked the shim one as verified now and added a comment explaining why
[15:01] <sil2100> juliank: excellent! Will deal with it after the meeting
[15:01] <cjwatson> bdmurray: done
[15:01] <cjwatson> Laney: added you to the list, will MM you the password
[15:01] <Laney> cjwatson: Merci
[15:24] -queuebot:#ubuntu-release- Unapproved: gnome-control-center (focal-proposed/main) [1:3.36.4-0ubuntu1 => 1:3.36.4-0ubuntu2] (ubuntu-desktop)
[15:24] -queuebot:#ubuntu-release- Unapproved: accepted python2.7 [sync] (focal-proposed) [2.7.18-1~20.04]
[15:26] -queuebot:#ubuntu-release- Unapproved: accepted gcc-9-cross-mipsen [sync] (focal-proposed) [4+c2ubuntu2.1]
[15:27] -queuebot:#ubuntu-release- Unapproved: accepted gcc-10-cross-mipsen [sync] (focal-proposed) [2+c1ubuntu1.1]
[15:43] <juliank> Laney: (less often) baseline retesting for stable releases, does that make sense?
[15:43] <juliank> just a thought that popped into my mind right this second
[15:45] <Laney> feels like it probably does
[15:47] <Laney> I wonder how long it'll take to chew through, but it could make sense to try to do a round right after release, before accepting any SRUs
[15:57] <bdmurray> sil2100: so about that bug verification. ;-)
[16:24] <sil2100> bdmurray: yes! Just need this meeting to finish :)
[16:24] <sil2100> (on which you are not!)
[16:35] <LocutusOfBorg> vorlon, if you want... https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963924
[16:35] <LocutusOfBorg> so we remove one i386 package :p
[16:35] <LocutusOfBorg> stuff is migrating in a britney run or two
[16:36] <LocutusOfBorg> not yet removed in Debian but should be kicked out
[16:37] -queuebot:#ubuntu-release- New sync: sagemath (groovy-proposed/primary) [9.2~beta12-1]
[16:39] <tjaalton> who has the power to handle updates to partner repos? AA's?
[16:44] <sil2100> tjaalton: not sure if there's not some special team for that, I have the power if anything
[16:44] <sil2100> bdmurray: hm hmm
[16:50] <bdmurray> sil2100: So I guess the really weird thing is in comment #9 where those 3 packages were kept after the upgrade
[16:51] <bdmurray> sil2100: So those could end up being cruft that is carried around between upgrades
[16:51] <tjaalton> sil2100: there are some flashplugin updates on the xenial/bionic/focal queues, been there for a long time now..
[16:51] <bdmurray> sil2100: And there could be more cruft depending on the package set you have installed
[16:56] <sil2100> bdmurray: yeah, makes me a bit worried to be honest
[16:57] <bdmurray> sil2100: Okay, let's remove it and I'l just release note the 'apt autoremove' having stuff to do issue
[17:00] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (focal-proposed) [1:20200714.1-0ubuntu<IP_ADDRESS>]
[17:01] <sil2100> Since it just leaving stuff for later autoremoval would be fine, like what we discussed yesterday - but this is just weird, since packages are suddenly not autoremovable even though they were before
[17:01] <sil2100> bdmurray: +1 on that, sadly :<
[17:01] <sil2100> tjaalton: ok, accepting those
[17:02] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (bionic-proposed) [1:20200714.1-0ubuntu<IP_ADDRESS>]
[17:03] <sil2100> bdmurray: while we're talking about SRUs, there's a few juicy ubuntu-image ones for focal, bionic and xenial
[17:04] <bdmurray> sil2100: are you trying to cut the line?
[17:06] <sil2100> ...sorry!
[17:08] <LocutusOfBorg> xnox, klibc... is it syncable?
[17:08] -queuebot:#ubuntu-release- Unapproved: rejected adobe-flashplugin [source] (xenial-proposed) [1:20200114.1-0ubuntu<IP_ADDRESS>]
[17:08] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (xenial-proposed) [1:20200714.1-0ubuntu<IP_ADDRESS>]
[17:11] <tjaalton> sil2100: thanks, makes the list easier on the eye :)
[17:12] <bdmurray> now only if those backports could go somewhere
[17:15] <tjaalton> exactly
[18:57] -queuebot:#ubuntu-release- Unapproved: file-roller (focal-proposed/main) [3.36.2-0ubuntu1 => 3.36.3-0ubuntu1] (ubuntu-desktop)
[19:42] -queuebot:#ubuntu-release- Unapproved: cheese (focal-proposed/main) [3.34.0-1build1 => 3.34.0-1ubuntu1] (desktop-core, desktop-extra)
[19:43] <rbasak> tjaalton, sil2100: it's ~canonical-partner-dev that can upload to partner
[19:43] <rbasak> As listed at https://launchpad.net/ubuntu/ anyway
[19:43] <rbasak> Steve, Lukasz, Dann and security
[19:44] <tjaalton> ah, indeed
[20:51] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (xenial-proposed/main) [4.15.0-1097.107~16.04.1] (kernel)
[20:54] -queuebot:#ubuntu-release- Unapproved: apport (bionic-proposed/main) [2.20.9-0ubuntu7.17 => 2.20.9-0ubuntu7.18] (core)
[20:59] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-image [source] (focal-proposed) [1.10+20.04ubuntu1]
[21:04] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-image [source] (bionic-proposed) [1.10+18.04ubuntu1]
[21:06] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-image [source] (xenial-proposed) [1.10+16.04ubuntu1]
[21:10] -queuebot:#ubuntu-release- Unapproved: apport (xenial-proposed/main) [2.20.1-0ubuntu2.24 => 2.20.1-0ubuntu2.25] (core)


[10:42] <davmor2> Yay my old bluetooth dongle work under karmic again :)
[12:43]  * ara -> lunch
[13:20] <davmor2> Morning Oh fader_ one
[13:20] <fader_> Howdy, davmor2.4
[13:20]  * davmor2 slaps fader_
[13:20] <fader_> :'(
[13:21] <davmor2> fader_: fixed empathy I switched off auto-connect
[13:21] <davmor2> now I can have as many windows open as I want
[13:21] <fader_> Huh, and that was the problem?
[13:21] <fader_> Weird.
[13:26] <davmor2> fader_: it would only open 11 tabs but it open the other and didn't display them so you were stuffed
[13:27] <fader_> Hmm
[13:27] <fader_> I've noticed some weirdness with its tab handling also... e.g. it doesn't open a tab when a message is received, only when I click on the notification applet.  OTOH, sometimes it would randomly open a tab when someone logged in but didn't send me a message.
[13:29] <davmor2> :D
[13:30] <davmor2> fader_: and of course you're reporting these bugs to make the user experience better in lucid right ;)  /me runs away
[13:30] <davmor2> off for lunch ttyl
[14:04] <moustafa> Goooood moorrning 'buntu!
[14:12] <davmor2> moustafa: You sound far to happy don't worry though we'll have cr3 beat that out of you ;)
[14:14] <moustafa> davmor2: I wish him luck for that!
[14:15] <fader_> moustafa: davmor2 and cr3 did it to me.  I used to be happy, once.
[14:15] <fader_> :'(
[14:16] <davmor2> fader_: I thought it was having to be responsible did that to you, we just didn't help :P
[14:16] <cr3> fader_: was is the whips or the chains that did it for you?
[14:16] <fader_> Heh
[14:19] <davmor2> cr3: that just got him excited ;)
[14:20] <cr3> davmor2: I once saw a bumper sticker that read: sticks and stones will break my bones, but whips and chains excite me.
[14:20] <cr3> I almost had to stop on the side of the road because I was laughing too much
[14:20] <davmor2> lmao
[14:21] <moustafa> cr3: 1: Was there a woman inside? 2: If the answer was yes: Did you get the liscence plate on that car?
[14:22] <cr3> moustafa: it was a pickup truck, do you still want to know the answer?
[14:23] <moustafa> cr3: I'm not quite sure how I want to answer that :p
[14:23] <moustafa> cr3: There are hot cowgirls in texas that ride in pickup trucks
[14:24] <moustafa> cr3: Buuuut, we're in Montreal, and the closest thing to a woman in a pickup truck we can get is a butch or worse
[14:24] <cr3> moustafa: I've never been to texas, this happened on home turf
[14:25] <davmor2> moustafa: You might want to watch that remember public recorded channel and ladies present  (fader_ close your eyes your too young to see this)
[14:26] <moustafa> davmor2: Duly noted
[14:26] <moustafa> davmor2: But if that's the case, then why is everyone speaking of getting excited with whips and chains?
[14:26] <moustafa> Also, kids these days don't much use IRC
[14:27] <fader_> moustafa: It's mostly related to the "POOR IMPULSE CONTROL" tattoo that cr3 has on his forehead ;)
[14:28] <moustafa> fader_: HE HAS A TATOO? (yes, the caps are very much implied)
[14:29] <cr3> I think there's a distinction between offending everyone and just offending a segment of the population. for some weird social reason, the former is more acceptable than the latter
[14:31] <moustafa> cr3: That's because the impact zone is spread around, rather than concentrated on one area.  It's like being stepped on the face with a boot, or high heel shoes.  Both hurt, but only one really gets painful.
[14:32] <cr3> personally, if I were excluded from an offense, I would feel offended
[14:32] <davmor2> moustafa: the fact you know that makes me wonder what cr3 wears on his feet to work ;)
[14:33] <moustafa> davmor2: Nothing I can mention on a public channel
[14:33] <davmor2> moustafa: now you're getting it ;)
[14:41] <moustafa> cr3: could you give this bug a look?  In case I missed something https://bugs.launchpad.net/checkbox/+bug/472743
[14:41] <ubot4> Launchpad bug 472743 in checkbox "checkbox skips certain tests / does not return to defaults" [Undecided,New]
[14:42] <davmor2> mother-in-law is in a bad way need to go to hospital now
[14:44] <cr3> moustafa: can't look at that one today, sorry
[14:44] <moustafa> no probs
[14:56] <moustafa> Well, everyone, I uploaded a pic of me on Launchpad.  Now all of you can bask in my horrendous glory!
[15:09] <possiventura> hello
[15:12] <moustafa> brb
[20:41] <fuller9box> hi
[20:41] <moustafa> Hello
[20:41] <fuller9box> hello moustafa
[20:42] <moustafa> hello fuller9box.  As you can see, there's not much going on here at the moment
[20:43] <fuller9box> can you help me decide what to do pls?
[20:43] <moustafa> I'll see what I can do
[20:43] <moustafa> fuller9box: what do you need help with?
[20:44] <fuller9box> i would like to do some testing of Lucid - but being new(ish) 2 ubuntu have not yet done setting up 9.10 (for myself)
[20:45] <moustafa> Lucid's currently in the planning stages, so testing of Lucid won't happen yet
[20:45] <fuller9box> i i have a laptop on which is now running 9.10 - i have some spare hd space that i could devote to testing
[20:46] <fuller9box> but 9.10 is not running for me as smooth as 9,04 did
[20:46] <moustafa> what's your laptop's configuration?
[20:47] <moustafa> Also: what do you mean by "not as smooth?"
[20:47] <fuller9box> dell latt d610 8gb / 1.5gb ram 1.5gb swap 60gb data 9
[20:49] <fuller9box> 60gb data (/home) rest i could devote to lucid ( using my present data)
[20:49] <fuller9box> compiz, strea,tuner rhythmbox giving kernel oops
[20:50] <moustafa> Like I said, Lucid's still in planning stages.  First Alpha's in December (December 10th, to be specific)
[20:50] <fuller9box> i like things like randon login screens
[20:50] <fuller9box> ok gives me time to sort out!
[20:50] <moustafa> Have you filed a bug report for your kernel oops?
[20:51] <fuller9box> y but still feeling my way around so dont know exact progress
[20:52] <fuller9box> sent this 1 earlier WARNING: at /build/buildd/linux-2.6.31/mm/page_alloc.c:1751 __alloc_pages_slowpath+0x459/0x480()
[21:22] <moustafa> fuller9box: I can't seem to find what the error might be.  I suggest you look on the forums to see if there's any similar issues occurring.
[21:26] <fuller9box> Hey - thanks 4 looking - not sure myself if there is a *fault* or i may not have correctly configured things on this end
[21:27] <moustafa> Worse case scenario, a re-install might solve the issues
[21:28] <moustafa> Else, look if you have activated the backports sources, and see if you have any non-free drivers installed.
[21:29] <fuller9box> will try that as last resort - but i still have 90.4 on another root part that i can use through grub
[21:29] <fuller9box> non free (1) for bcm wireless card - that's all
[21:30] <moustafa> If it was working before installing the driver, maybe removing it could help sort some issues
[21:30] <moustafa> Can't guarantee it, thought
[21:30] <moustafa> *though
[21:31] <fuller9box> your telling me that testing starts in dec - gives me some time to fix - and learn some more - thanks for looking - appreciated
[21:32] <moustafa> First Alpha in December.  No probs, that's what the community's here for ;)
[21:33] <fuller9box> i will try to have this fixed and pimped - ready to help out if i can!
[21:33] <fuller9box> lol
[21:33] <moustafa> Awesome :)
[21:35] <fuller9box> dropping heavy hints here on the home front for a dual core that has kvm - for virtualisation = more testing
[21:57] <moustafa> cr3, fader_: good evening, see you guys tomorrow
[21:58] <fader_> moustafa: Adios!


[04:15] <KGB-2> devhelp Mohammed Sadiq 358615 * commented merge request !2 * https://deb.li/i7ICj
[07:07] <tjaalton> evince doesn't support png in kinetic?
[07:08] <tjaalton> oops, tab-complete fail :P
[07:59] <seb128> goood morning desktopers!
[08:01] <ricotz> hello seb128
[08:03] <seb128> tjaalton, hey, our image viewer is eog not evince, why would evince open a png?
[08:03] <seb128> ricotz, hey, how are you?
[08:04] <ricotz> seb128, I am good, thanks, how are you?
[08:04] <seb128> I'm alright, thanks!
[08:04] <ricotz> seb128, I am wondering if this can be fast tracked https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1998444
[08:04] -ubottu:#ubuntu-desktop- Launchpad bug 1998444 in tiff (Ubuntu Kinetic) "Backport security fix for CVE-2022-3970" [Critical, New]
[08:05] <seb128> ricotz, let me see if I can help nagging there
[08:06] <ricotz> seb128, <ebarretto>
[08:06] <ricotz> oops
[08:06] <ricotz> seb128, <ebarretto> answered in #ubuntu-security
[08:06] <seb128> ricotz, he's working on it?
 thanks ricotz, some colleague will sponsor it, we will let you know through the ticket or here
[08:07] <ricotz> no idea why this CVE was only handled on xenial :\ https://ubuntu.com/security/CVE-2022-3970
[08:07] -ubottu:#ubuntu-desktop- A vulnerability was found in LibTIFF. It has been classified as critical. This affects the function TIFFReadRGBATileExt of the file libtiff/tif_getimage.c. The manipulation leads to integer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The name of the patch is 227500897dfb07fb7d27f7aa570050e626... <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3970>
[08:10] <ricotz> still puzzling why this libreoffice test failure didn't happen weeks ago when test building
[08:14] <seb128> yeah, I don't know
[09:32] <oSoMoN> good morning desktoppers
[09:33] <seb128> oSoMoN, hey, how are you today?
[09:35] <oSoMoN> seb128, I'm fine, fully recovered from that stomach bug and the rest of the family too
[09:35] <seb128> nice to hear :)
[09:57] <tjaalton> seb128: exactly
[09:57] <tjaalton> my mistake
[09:57] <seb128> tjaalton, so eog refuses to help png files for you?
[09:58] <tjaalton> no, eog works
[09:58] <seb128> so you just got confused and that was a question to ignore? :)
[09:58] <tjaalton> yes
[09:58] <tjaalton> :)
[09:58] <tjaalton> I googled it, and saw someone else did the same mistake, heh
[09:59] <seb128> :)
[12:26] <juliank> oh, gnome-shell dumps core and I don't have apport installed because I'm developing  stuff so need to use systemd-coredump
[12:27] <juliank> #0  0x00007f0c3e148252 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-11/libmutter-clutter-11.so.0
[12:27] <juliank> #1  0x00007f0c3e175579 in _clutter_process_event () from /usr/lib/x86_64-linux-gnu/mutter-11/libmutter-clutter-11.so.0
[12:27] <juliank> #2  0x00007f0c3e18c1f0 in _clutter_stage_queue_event () from /usr/lib/x86_64-linux-gnu/mutter-11/libmutter-clutter-11.so.0
[12:27] <juliank> sweet
[12:28] <juliank> oh this device does not have unattended-upgrades enabled
[12:28] <juliank> no gnome or clutter or mutter updates though
[12:31] <juliank> weird, no debug info
[13:01] <jbicha> good morning
[13:02] <nteodosio> Hey jbicha, good morning!
[13:02] <jbicha> hi :)
[14:08] <seb128> hey jbicha, how are you?
[14:11] <jbicha> good
[14:29] <Trevinho> juliank: no core dups for you from systemd either?
[14:30] <juliank> Trevinho: I don't get line numbers from gdb on the coredump which is weird they should be there via debuginfod
[14:31] <Trevinho> juliank: definitely, can you see if addr2line gives you an info though?
[15:20] <juliank> Trevinho: not that I can figure out
[15:21] <juliank> Trevinho: Well I get
[15:21] <juliank> addr2line -f -e /usr/lib/x86_64-linux-gnu/mutter-11/libmutter-clutter-11.so.0 0x50252
[15:21] <juliank> clutter_actor_set_color_state
[21:07] <Trevinho> juliank: I fell that gets called by JS you should figure it out by call (void) gjs_dumpstack().


[07:02] <dholbach> good morning
[07:04] <sladen> morning dholbach, did you see the moon with a hole?
[07:04] <sladen> excellent view from Heidelberg
[07:05] <dholbach> sladen, I must admit I didn't :)
[08:50] <ogra_> dholbach, what ?!? you didnt stay up til 4:30am to peek at the moon for 5 min ?
[08:50] <ogra_> :)
[09:06] <dholbach> no, not really  :)
[09:06] <dholbach> how about you?
[09:50] <ogra_> i'm fine looking at the photos :)