=== tcerjxveqccjszjz is now known as ayeatlopzvanwxlc
=== ayeatlopzvanwxlc is now known as LordOfBikes
[00:35] <tsimonq2> willdeberry: Hey :)
[00:36] <willdeberry> hey
[00:36] <tsimonq2> willdeberry: So that packaging guide is horribly outdated
[00:36] <tsimonq2> BUT
[00:36] <tsimonq2> I can walk you through
[00:36] <tsimonq2> What package are you looking to modify?
[00:36] <willdeberry> that would be awesome as i am just looking to get started working with a bigger community
[00:36] <tsimonq2> Sure, I totally get it :D
[00:37] <willdeberry> one of the low hanging fruit tickets was logged against pidgin, so i was starting there
[00:37] <tsimonq2> Sure, got a link to the bug report?
[00:37] <willdeberry> https://bugs.launchpad.net/hundredpapercuts/+bug/1602386
[00:37] <ubottu> Launchpad bug 1602386 in pidgin (Ubuntu) "Config directory ~/.purple should be ~/.config/purple" [Low,Confirmed]
[00:38] <willdeberry> figured that would be a good ticket to get the hang of the release workflow
[00:38] <willdeberry> i have the lp account, ssh and gpg keys taken care of, just not sure how to get the code itself
[00:38] <tsimonq2> I see, gotcha.
[00:39] <tsimonq2> willdeberry: Do you have the ubuntu-dev-tools, build-essential, and devscripts packages installed?
[00:39] <willdeberry> i do
[00:39] <tsimonq2> Alright, excellent.
[00:39] <willdeberry> i just happen to create debian packages for work related code as well, just not sure how to work within the confines of ubuntu :)
[00:40] <tsimonq2> willdeberry: In your working directory, try this command: pull-lp-source PACKAGE
[00:40] <tsimonq2> i.e. pull-lp-source pidgin
[00:40] <tsimonq2> Sure, I get it :)
[00:40] <willdeberry> i assume this is after running bzr init correct?
[00:40] <tsimonq2> Nope
[00:40] <willdeberry> or just create the working dir and run what you refereced?
[00:40] <tsimonq2> Yep
[00:41] <tsimonq2> We no longer use Bazaar at all in our packaging workflow
[00:41] <willdeberry> switched to git i assume?
[00:41] <tsimonq2> Nope, we're working in that direction though.
[00:41] <willdeberry> i assume that is where tools like git-ubuntu are going to come in handy down the road?
[00:41] <tsimonq2> Not all packages have been imported yet.
[00:42] <tsimonq2> Yep.
[00:42] <tsimonq2> Just not in this case.
[00:42] <willdeberry> awesome, sounds like a good future at least ;)
[00:42] <tsimonq2> :D
[00:42] <willdeberry> ok, so now i finally got code locally
[00:42] <tsimonq2> Yay!
[00:42] <tsimonq2> Ok, do you know the change you want to make?
[00:43] <willdeberry> i know the idea, just hadn't figured out where to make it yet
[00:44] <willdeberry> figured it would be a combination of a debian patch file to make sure the new config directory is used and potentially a postinst to handle migration across package updates
[00:44] <tsimonq2> willdeberry: This is the part where I can't really help because I don't know enough about the package, problem, and codebase, but I'd recommend this guide here: https://raphaelhertzog.com/2012/08/08/how-to-use-quilt-to-manage-patches-in-debian-packages/
[00:44] <tsimonq2> willdeberry: You said you've already had some packaging experience in Debian?
[00:45] <willdeberry> i do mainly around the workflow using git-buildpackage
[00:45] <Unit193> willdeberry: Just as a heads-up, Ubuntu sponsors will liekly not be too fond of diverging from Debian on this, and I'd give a guess same with Debian and upstream.
[00:46] <willdeberry> so for something like this, probably best to submit upstream then huh
[00:46] <willdeberry> that's the kind of stuff that i am hoping to gather and get my feet wet with
[00:46] <tsimonq2> Unit193: Sure, I failed to mention that
[00:46] <willdeberry> code is obviously only half the battle
[00:47] <tsimonq2> willdeberry: Yeah, so once you have the patch, even though you could easily get it in Ubuntu, it's preferred to get it in Debian.
[00:47] <tsimonq2> Like Unit193 said
[00:48] <Unit193> https://developer.pidgin.im/ticket/4911 - https://developer.pidgin.im/ticket/10029 fyi.
[00:48] <Unit193> (That's also not really what I said.)
[00:48] <willdeberry> lol
[00:49] <tsimonq2> Unit193: But that was the point you were trying to make from what I gather.
[00:49] <tsimonq2> ("easily" get it in Ubuntu, not meaning sponsors will accept it, I mean in a technical sense)
[00:49] <willdeberry> so what's the gist of when things go into ubuntu vs upstream (debian or package directly)
[00:49] <tsimonq2> willdeberry: Try to get as much as possible in Debian
[00:50] <Unit193> willdeberry: For example, crashing or CVE fixes would be desired as soon as possible, same with failure to build.
[00:50] <tsimonq2> ^
[00:50] <willdeberry> so if it needs to get out now, then probably good to submit to ubuntu, otherwise work with upstream
[00:51] <Unit193> One must remember that it doesn't just have to be pushed, it'll also have to be maintained by whoever merges it in the future.  If a package is in sync with Debian, they'll want you to clarify why you should break sync.
[00:51] <willdeberry> makes sense
[00:52] <Unit193> I don't say this to discourage you, just to inform.
[00:52] <willdeberry> definitely understand
[00:52] <Unit193> You can see in 10029 there's quite a bit of talk about this, most recent was 9 months ago though.
[00:52] <willdeberry> now i get to learn a new process :P
[00:53] <Unit193> \o/
[00:57] <willdeberry> so other than finding bug tickets to work on, any recommendations on giving back to ubuntu?
[00:57] <Unit193> Merges.
[00:59] <willdeberry> updating ubuntu packages based on debian packages?
[01:00] <tsimonq2> willdeberry: Yep, merges.ubuntu.com lists them :)
[01:01] <willdeberry> lol, mom...i love it
[01:01] <tsimonq2> :D
[01:10] <Unit193> As a side note, https://bugs.launchpad.net/ubuntu/+source/pasystray/+bug/1639867 are my favorite type of bugs, ones with no information. :P
[01:10] <ubottu> Launchpad bug 1639867 in pasystray (Ubuntu) "/usr/bin/pasystray:6:pa_context_errno:pulseaudio_connect:init:main" [Undecided,New]
[01:24] <Unit193> Rhonda: Ping!
[01:27] <willdeberry> so any insight on when to do which?
[01:27] <willdeberry> Run ../merge-genchanges , ../merge-buildpackage or ../merge-debuild when done
[01:28] <willdeberry> wouldn't the last two options be similar?
[01:36] <tsimonq2> willdeberry: When done, I'd suggest creating a PPA, run ../merge-buildpackage -S -d -sa, then dput ppa:USERNAME/PPA-NAME
[01:36]  * tsimonq2 has to go AFK, ttyl
[01:36] <willdeberry> rgr, ty tsimonq2
[01:37] <willdeberry> I found https://wiki.ubuntu.com/UbuntuDevelopment/Merging so I am going through those steps now
[01:59] <willdeberry> and now lp is not letting me in, well damn lol
[02:00] <willdeberry> Unit193: thanks again for all the help as well and direction. as soon as lp stops being a pain, I will definitely be looking into uploading some of these merges to help out
[02:24] <Unit193> willdeberry: Fantastic, I presume you've looked where it said for proposing changes?  (And can't answer about the scripts, I don't use them.)
[02:25] <Unit193> http://reqorts.qa.ubuntu.com/reports/sponsoring/ you'll want them to show up there.
[02:26] <willdeberry> right. i was in the process of getting logged back into lp when it started being a pain, but was going to follow the process in the article i linked: create a bug report, then on the merge page place the ticket in the sometimes hidden box on the right and then work out the issue
[02:26] <willdeberry> i assume by filling out the merge site that gets it to the page you linked just now
[02:28] <willdeberry> this is what i was about to follow: https://wiki.ubuntu.com/UbuntuDevelopment/Merging#File_a_merge_bug
[02:33] <Unit193> Huh, wonder when the last time that page was generated...
[02:33] <willdeberry> that seems to be a trend ;)
[02:34] <willdeberry> but basically, update this page for the package: https://merges.ubuntu.com/universe.html with the ticket number is what i got out of it
[02:37] <Unit193> That is to say, I noticed xfwm4 on there, but at an older version.  There's a couple other xfce packages that are "newer" in Ubuntu too..
[02:38] <Unit193> (Like xfdesktop4..)
[02:41] <willdeberry> yea mom shows last modified from 2016 :-/
[02:41] <willdeberry> at least for xfwm4
[02:42] <willdeberry> definitely newer in the listings: xfwm4/artful 4.12.4-0ubuntu1 amd64
[02:42] <willdeberry> i guess if a human never cleans up old conflicts they don't get pruned?
[02:44] <Unit193> Dunno, looked at the date at the bottom of the page, certainly pulling old data from somewhere.
[02:44] <willdeberry> all this is news to me so I am just following yalls lead at this point
[02:44] <willdeberry> lol
[02:51] <Unit193> I'm a flavor dev (Xubuntu), so I keep a close eye on any Xfce related packages for example.  I also push fixes to MOTU packages when I see them (and honestly?  Think it'll make it through the queue), and try to filter through delta and push anything interesting back to Debian.  Recently did a transition that was aided by watching autopkgtests too.
[02:53] <willdeberry> so is MOTU just basically a place for people to assist especially where packages don't fall under a specific umbrella of devs?
[02:54] <Unit193> Most of the Xubuntu packages are in universe actually, main just means that Canonical security team will keep an eye on it (baaasically.)
[02:56] <willdeberry> and MOTU just focuses on universe packages mainly?
[02:57] <willdeberry> i would assume by the name
[02:59] <Unit193> It's more of a subset of core-dev, that way you can give people permission to upload packages, but not yet to core packages that are important to Ubuntu desktop or Ubuntu server.  If you're a core-dev, you likely will still upload to Universe too.
[02:59] <Unit193> So, I've got packageset upload rights, meaning I can pretty much upload any package relating to Xubuntu, but not all of universe.  Doesn't mean I can't get things sponsored though, just a subset of direct upload privs.
[03:01] <willdeberry> really bothers me that lp is having this issue with my account right now otherwise i'd walk through some of these steps knowing you are actually responding. guess it will just have to wait till tomorrow though
[03:02] <willdeberry> i really do appreciate the insight on things though Unit193
[03:02] <willdeberry> being a OS dev at work but in a much smaller scale, it just makes me appreciate things more seeing all the moving cogs that have to work in sync
[03:02] <Unit193> Keep in mind that I'm not MOTU, and also that I personally may not do things "the normal way", but sure!  Glad you're interested in getting involved, more so that you have some prior Debian work.
[03:03] <Unit193> Also, what specifically in regards to LP?  You have your GPG set I presume, and am signing the upload?
[03:04] <willdeberry> so i found out that i had gotten accounts crossed and using multiple emails accounts. Found this out when trying to add my main email to the already created account.
[03:05] <willdeberry> now lp has me logged in on their end but what i think happened is that the account IDs and emails don't line up anymore for the session that is open on that end
[03:05] <willdeberry> so i am stuck till it "logs out" on the server side
[03:05] <willdeberry> not a huge deal, just puts a damper on doing anything tonight
[03:06] <willdeberry> if not resolved by morning, then i will be more concerned
[03:07] <willdeberry> i just like seeing the other tools that are involved in the process too. my main workflow usually revolves around gbp command (git-buildpackage) doing all the heavy lifting for me. ie: auto generating debian/changelog and tags for me
[03:08] <willdeberry> but we have pytest tied into the deb build process for unit tests and autopkgtest integrated for integration testing of the package which utilizes throw away VMs inside aws
[03:09] <willdeberry> have had to deal with the struggles of the debhelper process and overwriting the standard postinst files so we can do things a bit different in a couple situations. mainly dealing with kernel modules
[03:10] <willdeberry> so it would be nice to take some of this new found knowledge and actually give back to the distro we so heavily lean on. and learn some new tricks along the way of course
[03:11] <Unit193> Yep, I use git-buildpackage, though not for doing the actual package builds, just the packaging.  Veeery nice and useful.  Contributions to Debian also contribute to Ubuntu too, just as a reminder.
[03:12] <willdeberry> that's fair
[03:12] <willdeberry> already learning and realizing new things :D
[03:13] <willdeberry> alright, well i am done for tonight especially since lp is broke for me. will try this again tomorrow. thanks again Unit193
[03:15] <Unit193> Sure thing, and if it's still broken I'd give #launchpad a lookup, though on a Sunday...Not likely.
[03:15] <Unit193> Glad to have been of at least some service!