 wxl @tsimonq2 meta updated https://phab.lubuntu.me/D30
[01:20] -lugito:#lubuntu-devel- [Needs Review] added screengrab: https://phab.lubuntu.me/D30
[02:04] -lugito:#lubuntu-devel- [rMANUALfe6049a640d7: Style X button] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALfe6049a640d7
[02:25] -lugito:#lubuntu-devel- [rMANUAL6c14eccdf15d: Add firefox downloads screenshots] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL6c14eccdf15d
[02:37] -lugito:#lubuntu-devel- [rMANUAL8f250f61a01b: Add note downward pointing arrow only with lots of tabs] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL8f250f61a01b
[02:55] -lugito:#lubuntu-devel- [rUPDATENOTIFIER0f71dbbcc069: fixing lintian] Hans P Möller <hmoller@uc.cl> committed: https://phab.lubuntu.me/rUPDATENOTIFIER0f71dbbcc069
[03:04] -lugito:#lubuntu-devel- [rUPDATENOTIFIERb91e94838d52: fixing lintian] Hans P Möller <hmoller@uc.cl> committed: https://phab.lubuntu.me/rUPDATENOTIFIERb91e94838d52
[03:38] -lugito:#lubuntu-devel- [T56: Transfer testcases to the actual testcase branch] guiverc (Chris Guiver) commented on the task: https://phab.lubuntu.me/T56#1978
[05:08] -lugito:#lubuntu-devel- [T56: Transfer testcases to the actual testcase branch] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T56#1980
[05:46] -lugito:#lubuntu-devel- [T56: Transfer testcases to the actual testcase branch] guiverc (Chris Guiver) commented on the task: https://phab.lubuntu.me/T56#1982
 @The_LoudSpeaker [idk if it's just happening with me. whenever in pcmanfm-qt, the sidebar where bo …], ^
[16:58] -lugito:#lubuntu-devel- [T109: Manual as PDF] apt-ghetto (apt-ghetto) just created this task: https://phab.lubuntu.me/T109
[17:54] -lugito:#lubuntu-devel- [T56: Transfer testcases to the actual testcase branch] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T56#1992
 (Photo, 720x1280) https://i.imgur.com/kbxpv0G.jpg
 i found this on lubuntu site.. what does it mean? does it mean i should first test latest version of lubuntu before installing it in my hard disk?
 Lubuntu.me is the official site
 Don't follow anything said on Lubuntu.net
 and is the latest version good to go?
 @tsimonq2 [Don't follow anything said on Lubuntu.net], ohk
 Yeah
 is that a fake site
 @heogj [is that a fake site], Yeah
 is there any other linux distribution lighter than lubuntu?
 what is your opinion on OpenSUSE?
 Asking this in "Lubuntu Development" seems like a way to get a very biased answer
[19:20]  * The_LoudSpeaker yucks at OpenSUSE
 @UniversalSuperBox [Asking this in "Lubuntu Development" seems like a way to get a very biased answe …], i am a beginner
 i just learned what linux distribution means
 😅
 many suggested linux mint
 https://telegram.lubuntu.me/offtopic is the right place, best of luck in your Linux journey!
 I would also recommend the BDLL group
 but i think lubuntu is much lightweight as compared to linux mint
 @heogj [but i think lubuntu is much lightweight as compared to linux mint], am i right btw?
 @tsimonq2 [https://telegram.lubuntu.me/offtopic is the right place, best of luck in your Li …], okay bro
 @tsimonq2 [https://telegram.lubuntu.me/offtopic is the right place, best of luck in your Li …], when i open this link....👇
 (Photo, 720x1280) https://i.imgur.com/CVpzVuM.jpg
 ok i will use vpn
 @heogj [<reply to image>], this is the development channel, the other is the offtopic
 okay gotcha
[19:27] <apt-ghetto> You can join #lubuntu-offtopic
[19:27] <apt-ghetto> The link is for Telegram users
 you mean t.me/lubuntuofftopic
 ?
[19:28] <apt-ghetto> Yes
[19:30] <apt-ghetto> https://lubuntu.me/links/
 https://t.me/joinchat/DH6s1EKjxEYc6M3YGRGt-Q
 got the link
 telegram.lubuntu.me is an alias
 Now I'll have to change it again to prevent spammers.
 for some stupid reason indian government banned telegram website
 @The_LoudSpeaker did they? ^^
 @tsimonq2 [Now I'll have to change it again to prevent spammers.], you mean private link?
 @heogj [you mean private link?], Yeah
 @tsimonq2 [Yeah], of offtopic group?
 ...yes
 (Photo, 720x1280) https://i.imgur.com/Qd2fEnk.jpg whenever i open telegram.org or any telegram link outside of telegram app it either doesnt show up(which means keeps on loading or doesnt load at all ) or shows up with an error like this
 @teward001 ^
 @tsimonq2 [@The_LoudSpeaker did they? ^^], Nope I guess.
 @teward001
 @The_LoudSpeaker [@teward001], ooops! mistake
 try this one https://t.me/joinchat/DH6s1EKjxEYc6M3YGRGt-Q
 Yes, let's keep pinging @teward001
 (Photo, 1280x719) https://i.imgur.com/3WWQU2p.jpg
 @The_LoudSpeaker [<reply to image>], This is what I was about to paste
 @tsimonq2 [Yes, let's keep pinging @teward001], XD
 @The_LoudSpeaker [<reply to image>], seems like its the issue with jio then
 He's in a meet I guess. atleasat he said he was, untill 10 mins ago
 btw which part of india are you from?
 @heogj [seems like its the issue with jio then], Maybe.
 @heogj [btw which part of india are you from?], Let's continue in offtopic
 okay
[19:39]  * kc2bez pings @teward001 because @tsimonq2 told me to. 
 ^
 @teward001 AWAKENS
[19:40] <apt-ghetto> Please don't ping @teward001
 Why can't I ping @teward001?
 because i'mma drag you out back and shoot ya if you keep it up
 XD
 telegram.lubuntu.me wouldn't be an NGINX issue, unless for some reasno you're hammering the server.  that just returns a 301
 and it SEEMS to work fine
 i'd need details on the specific environment where the 403 is triggering
 ... who the heck is using a Note 4 to get onto the site o.O
 @teward001 [telegram.lubuntu.me wouldn't be an NGINX issue, unless for some reasno you're ha …], its because of this jio network
 they have banned many sites including porn ones and several others which apparently includes telegram.org t.me telegram.me etc
 ah
 so then it is NOT something I can fix
 and everyone can stop pinging me now.
 *shoots @tsimonq2*
 yeah we can't fix that
 @teward001 [so then it is NOT something I can fix], Yes it is, now go fix it
 *shot*
 😂
 yeah you'll notice Simon and I regularly go off on each other in what would NORMALLY seem like a CoC violation, but we just smack each other around regularly :)
 keeps us all sharp
 This is true, on a serious note I appreciate having Thomas around and he's a great part of the team :)
 albeit i'm annoying as heck ;)
 The vast majority of the time for good reason :)
 @teward001 [yeah you'll notice Simon and I regularly go off on each other in what would NORM …], coc? clash of clans?
 Code of Conduct
 signedby Ubuntu Members, Ubuntu Devs, and Lubuntu Members, as well as against the Lubuntu Constitution, but with Simon I just smack him around with good reason and we just 'accept it' as not being CoC-noncompliant xD
 ... I need more coffee... oh good I get to leave early today back later.
 @teward001 [signedby Ubuntu Members, Ubuntu Devs, and Lubuntu Members, as well as against th …], very informative
[19:52] -lugito:#lubuntu-devel- [rMANUALad268c1faea1: Add how to search through history on firefox] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALad268c1faea1
 @heogj [coc? clash of clans?], 😂😂😂
 @The_LoudSpeaker [😂😂😂], back then it was insanely famous in my area.. now its pubg era
 Play ring of Elysium. You won't play pubg.
[20:09] -lugito:#lubuntu-devel- [rMANUAL0a3bb508f1dc: Add sorting option by right click] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL0a3bb508f1dc
[20:13] -lugito:#lubuntu-devel- [rMANUALb34b15896446: Fix capitilization] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALb34b15896446
[20:21] -lugito:#lubuntu-devel- [rMANUAL86f445a1afb4: Add connect to server screenshot] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL86f445a1afb4
[20:40] -lugito:#lubuntu-devel- [T103: Properly deal with translations on the blog] tsimonq2 (Simon Quigley) commented on the task: https://phab.lubuntu.me/T103#1997
 wxl, @kc2bez: Would either of you or both of you be interested in doing something roughly described as a MOTU training session? Basically just walking through some complexities of the archive and work that you can do
[21:11] -lugito:#lubuntu-devel- [rMANUALad985dda0c54: Fix clear filter bar keyobard shortcut] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALad985dda0c54
[21:19] -lugito:#lubuntu-devel- [rMANUALff45f61156c1: Reword clearing filter bar] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALff45f61156c1
 @tsimonq2 [wxl, @kc2bez: Would either of you or both of you be interested in doing somethin …], My intent is not to be exclusionary, because I want to do something like that here and it's good to learn from, but others might want to focus on becoming Lubuntu Developers first :)
[21:22] -lugito:#lubuntu-devel- [rMANUALffe8a50d281d: Reword keep filter bar but show all files] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALffe8a50d281d
[21:43] -lugito:#lubuntu-devel- [rMANUAL0108650dfe89: Style x button] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL0108650dfe89
[21:46] -lugito:#lubuntu-devel- [rMANUAL1c8b4b4d7bda: Add keyboard shortcut to quit] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL1c8b4b4d7bda
[21:51] -lugito:#lubuntu-devel- [rMANUAL7c49c309d33f: Reduce wordiness] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL7c49c309d33f
[22:01] -lugito:#lubuntu-devel- [rMANUALb0b2a1aa381a: Fix capitilization] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALb0b2a1aa381a
[22:16] -lugito:#lubuntu-devel- [T56: Transfer testcases to the actual testcase branch] guiverc (Chris Guiver) commented on the task: https://phab.lubuntu.me/T56#1998
[23:29] <kc2bez> @tsimonq2 I am not sure what your timeframe is. 
 @kc2bez [<kc2bez> @tsimonq2 I am not sure what your timeframe is.], I don't have one in mind right now :)
 Hopefully before Feature Freeze
[23:30] <kc2bez> Ok. That is next week :P
 You busy tonight? I can walk you through one to get the process down
[23:31] <kc2bez> I am available. 
 Do you have a preferred time? (Now, in an hour or two?)
[23:33] <kc2bez> <2 hours is preferred but anytime before that. Whatever works for you.
 10 mins from now wfm. :P
[23:35] <kc2bez> Sounds good.
[23:40] <tsimonq2> Hi.
[23:40] <tsimonq2> Finding a good package to work with here.
[23:43] <kc2bez> Gotcha.
[23:45] <tsimonq2> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html <-- this right here is the Magical Page.
[23:45] <tsimonq2> Most of the time, it's the main thing to look at.
[23:46] <tsimonq2> So, let's take a standard entry on this page.
[23:47] <tsimonq2> Each bullet point has the name of a package in proposed. (VERSION to VERSION) is formatted as ("version currently in the release pocket" to "version uploaded to proposed")
[23:47] <tsimonq2> On this page you can find the results of all of the reverse dependencies' autopkgtests.
[23:48] <tsimonq2> So, for example, let's look at packer.
[23:48] <tsimonq2> packer (1.0.4+dfsg-1 to 1.3.4+dfsg-4)
[23:48] <tsimonq2>     Maintainer: Debian Go Packaging Team
[23:48] <tsimonq2>     Section: universe/misc
[23:48] <tsimonq2>     145 days old
[23:48] <tsimonq2>     autopkgtest for packer/1.3.4+dfsg-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Regression ♻ , s390x: Pass
[23:48] <tsimonq2>     Not considered 
[23:49] <tsimonq2> 1.0.4+dfsg-1 is the version currently in the release pocket, 1.3.4+dfsg-4 is the version currently in proposed, it's been in proposed for 145 days, and its autopkgtests fail on ppc64el so it is not considered for migration to the release pocket.
[23:49] <tsimonq2> Does that make sense so far?
[23:49] <kc2bez> I'm with you so far
[23:49] <tsimonq2> Cool.
[23:50] <tsimonq2> So, on the excuses page, there's a link to the autopkgtest that's failing.
[23:50] <tsimonq2> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/ppc64el/p/packer/20190624_084504_7ec1a@/log.gz
[23:50] <tsimonq2> The hardest part of this whole process is deciphering these logs.
[23:51] <tsimonq2> However, I can see this right here:
[23:51] <tsimonq2> fatal error: runtime: out of memory
[23:52] <tsimonq2> My thought process when looking at this is "oh, so the ppc64el runner running this test has ran out of memory, but no other architectures have. Is this intentional, or is there something else at play here?"
[23:52] <tsimonq2> So I'm going to look at the log further.
[23:53] <tsimonq2> I don't see anything else from scanning the log, so I'm going to look at the retry history, because sometimes with OOM errors, a simple retry does the trick.
[23:53] <tsimonq2> On the excuses page I can get there by clicking "ppc64el": http://autopkgtest.ubuntu.com/packages/p/packer/eoan/ppc64el
[23:54] <tsimonq2> Okay, so this is a nice demonstration of a concept that's useful when doing this.
[23:54] <tsimonq2> Thankfully this page is pretty clean:
[23:54] <tsimonq2> Version 	Triggers 	Date 	Duration 	Requester 	Result 	
[23:54] <tsimonq2> 1.0.4+dfsg-1 	glibc/2.29-0ubuntu3 	2019-07-07 18:32:33 UTC 	0h 06m 28s 	- 	fail 	log   artifacts   ♻
[23:54] <tsimonq2> 1.3.4+dfsg-4 	packer/1.3.4+dfsg-4 	2019-06-24 08:45:04 UTC 	0h 08m 39s 	xnox 	fail 	log   artifacts   ♻
[23:54] <tsimonq2> 1.0.4+dfsg-1 	glibc/2.28-0ubuntu1 	2018-08-25 06:18:01 UTC 	0h 11m 51s 	- 	pass 	log   artifacts   
[23:55] <tsimonq2> When it was first tried about a year ago, it passed, but since it has been retried against itself, and the version against release.
[23:55] <tsimonq2> The important thing to note here is that the version currently in the release pocket, 1.0.4+dfsg-1, is experiencing the same regression as the one in the proposed pocket.
[23:55] <tsimonq2> To confirm that, I'm going to check out the latest log.
[23:56] <tsimonq2> And, sure enough:
[23:56] <tsimonq2> /usr/lib/go-1.11/pkg/tool/linux_ppc64le/link: running gcc failed: fork/exec /usr/bin/gcc: cannot allocate memory
[23:56] <tsimonq2> So, here is my next step.
[23:56] <tsimonq2> First I want to do a simple retry to confirm that at the current state of the release pocket plus this package from proposed, this error can consistently be reproduced.
[23:57] <kc2bez> That makes sense so far
[23:58] <tsimonq2> If it can be, the next step is to retry the version in the release pocket. If the version in the release pocket fails, you hop into #ubuntu-release with the two logs and ask for them to hint it through.
[23:58] <tsimonq2> If it passes however, then it's a problem with the version in proposed that needs to be figured out.
[23:58] <tsimonq2> Does that part make sense as well?
[23:59] <kc2bez> Yes
[23:59] <tsimonq2> Cool.
[23:59] <tsimonq2> So the next step is to craft the actual request to the autopkgtester.