[00:55] <mwhudson> Unit193: apparently not
[00:56] <mwhudson> Unit193: i pressed it again
[00:56] <Unit193> I can assure you that xfce4-terminal didn't break apport, the latter doesn't depend on the former at all and the former doesn't even have an apport hook.
[00:56] <Unit193> mwhudson: Thanks.
[00:57] <mwhudson> it's failed a few times
[00:57] <mwhudson> on other packages too
[00:57] <mwhudson> bdmurray: how much do you love the apport autopkgtests?
=== braderhart is now known as Guest13679
[03:04] <Unit193> mwhudson: Thanks again btw, that did it.
[04:00] <mwhudson> Unit193: happy to help/click
[06:30] <rbasak> juliank: are you planning on merging multipath-tools? Or do you think that should be a server thing?
[06:32] <juliank> rbasak: I certainly wouldn't complain if server merges it. It's unlikely I'm going to do it this or next week
[06:33]  * juliank is in taiwan at deb{camp,conf}
[06:44] <rbasak> juliank: the delta seems pretty extensive :-/
[06:44] <rbasak> I'm not sure whether to look at this right now or focus on some other merges instead
[06:45] <juliank> rbasak: Some of our patches were merged in Debian, but most not I guess. Is there anything urgent needing 0.7.7?
[06:49] <rbasak> juliank: not that I'm aware - I'm only asking from the general merge status PoV.
[06:53] <juliank> rbasak: well, I can take a look at it, I don't think it's a huge amount of work for me
[06:53] <juliank> I want to do some apt work this week, but that stuff is more annoying
[06:54] <rbasak> juliank: well I'm not going to stop you volunteering :)
[06:54] <rbasak> juliank: looks like it'd take me much longer than you as I'm unfamiliar.
[07:03] <juliank> rbasak: I tried to git-ubuntu merge but it cherry picked an empty commit for 0.7.4-2ubuntu1 instead of the commits that it should actually pick...
[07:07] <rbasak> juliank: yeah it's because the old upload had the old imported history. We don't have "hash stability" for imports yet.
[07:07] <rbasak> juliank: you can work around by using git-rebase manually to strip out everything and get to the "reconstruct" tag yourself
[07:07] <rbasak> Then "git ubuntu tag --reconstruct" and carry on as normal
[07:14] <juliank> I fear this is going to take a few days with git-ubuntu vs a few minutes with MoM
[07:15] <rbasak> Why do you think so?
[07:15] <rbasak> Fixing the reconstruct tag should be straightforward. I can do that part for you if you like? Any reason it'll take longer after that?
[07:16] <juliank> MoM is grab-merge quilt push -a and fix patches no longer applying
[07:16] <juliank> that's trivial
[07:16] <rbasak> git ubuntu is git-rebase and fix the conflicts :)
[07:16] <juliank> git-ubuntu is a lot more complicated as always
[07:17] <rbasak> It's the same as MoM really IMHO - except that you can do each bit of delta one at a time instead of looking at the whole thing as a single lump, which IMHO is error-prone.
[07:17] <juliank> I have no idea how the reconstruct tag should look like
[07:18] <juliank> What I ended up with was the logical tag
[07:18] <rbasak> If you have a logical tag, then don't worry about reconstruct/deconstruct.
[07:18] <juliank> cccccchdhcrkbujhrudjuhbnlvrkrgrijfuvkhfvduiv
[07:19] <rbasak> reconstruct/deconstruct are really just steps to get to the logical tag in the workflow.
[07:19] <juliank> And rebasing that on top of debian/sid gives you a lot more conflicts than MoM would
[07:19] <rbasak> I only need them when reviewing if the logical tag is wrong somehow, in order to figure out how it became wrong.
[07:20] <rbasak> Then MoM would be hiding errors.
[07:20] <juliank> It just does merges
[07:20] <rbasak> When we started using this workflow, we found dozens of packages with previous merge mistakes caused by people using MoM without doing a proper review that the result was correct.
[07:20]  * juliank cloned again and restarts
[07:21] <rbasak> Just because there aren't any merge conflicts doesn't mean that there aren't merge errors.
[07:23] <juliank> Pretty sure it does
[07:23] <rbasak> Pretty sure it doesn't. I'll have to come up with an example failure case for you, though not right now as it'll take some thought.
[07:24] <rbasak> Applying patches is blind. If the context fits, then it'll tell you it applied.
[07:24] <rbasak> But depending on what changed upstream, you could have something apply but still be wrong.
[07:24] <juliank> I know.
[07:25] <rbasak> MoM hides all of that in one big blob of delta.
[07:25] <juliank> But let's look at a simple case
[07:25] <rbasak> What we found was that previous uploaders were treating it as "well MoM worked so I'll upload it"
[07:25] <juliank> I added the line       [ ! -f kpartx/dm-parts.rules ] || cp kpartx/dm-parts.rules debian/kpartx.dm-parts.udev
[07:25] <juliank> in a commit
[07:25] <juliank> that was merged in Debian
[07:26] <juliank> but in rebasing, I now get a merge conflict
[07:26] <rbasak> So git rebase --skip
[07:26] <juliank> because in a later commit (also merged) I added the line [ ! -f kpartx/del-part-nodes.rules ] || cp kpartx/dm-parts.rules debian/kpartx.del-part-nodes.udev on top of it
[07:27] <rbasak> Oh
[07:27] <rbasak> Then your logical is wrong
[07:27] <rbasak> You want to have squashed those two things together
[07:27] <juliank> They are different thing
[07:27] <juliank> one commit is install dm-parts, the other is install del-part-nodes
[07:27] <rbasak> Oh, in two separate lines?
[07:28] <juliank> The result is that, yes, I need to skip the patch as it was merged in Debian, but it's not entirely obvious
[07:28] <rbasak> git rebase --skip
[07:28] <rbasak> You need to have identified that you are dropping it
[07:28] <rbasak> The typical MoM mistake we see in this case is that the changelog gets copied blindly forward ("Remaining changes: still adding the line" (even though you no longer are))
[07:29] <rbasak> If you do the changelog right, then you need to be aware that you skipped.
[07:29] <rbasak> If you're aware that you're skipping it, then "git rebase --skip" should be obvious)
[07:30] <juliank> Well, I did not know I was about to drop it form the diff immediately
[07:30] <juliank> It just confused me
[07:30] <rbasak> The workflow does involve a different way of thinking.
[07:31] <rbasak> For each commit in logical: do I still need it? Does it apply?
[07:31] <rbasak> At the time of rebasing
[07:32] <rbasak> But my point is that this is thinking you need to do with MoM anyway for the reuslt to be correct. Just that uploaders weren't doing that.
[10:43] <tarzeau> it's really cool that https://popcon.ubuntu.com/ is updated again. but is it really true that there's more i386 Ubuntu users than amd64 Ubuntu users that have popularity-contest installed and activated?
[10:44] <Unit193> tarzeau: Ubuntu doesn't advertise popcon at all.
[10:44] <tarzeau> Unit193: since which year?
[10:44] <tarzeau> Unit193: the package is however still available in the archives up to today
[10:45] <Unit193> Yes it is available.
[10:46] <tarzeau> Unit193: maybe it should be removed from cosmic cuttlefish on?
[10:46] <infinity> Removing it from the distro doesn't remove it from people's machines, mind you. :P
[10:46] <tarzeau> or updated to report back to popcon.debian.org since they have a distro stats part now? https://popcon.debian.org/
[10:47] <tarzeau> infinity: but gives you the possibility to remove it with updated packages
[11:38] <themill> no, please don't report to a different distro; we've been through that one before
[11:53] <seb128> tarzeau, what issue are you trying to solve by removing it from Ubuntu?
[11:55] <tarzeau> seb128: negative, i won't solve anything that way.
=== walbon_ is now known as walbon
=== walbon is now known as veado
=== veado is now known as walbon
[13:25] <GunnarHj> infinity: Thanks for the latest console-setup change. It will certainly improve it a bit. I'll evaluate it more carefully once 18.04.1 has been released.
[13:26] <infinity> GunnarHj: Yeah, I'll backport that to bionic too, just won't be on point-release media.
[13:26] <infinity> GunnarHj: But since it's really an upgrade issue, not an install issue, that should be fine.
[13:26] <samouy|> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[13:26] <samouy|> or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[13:26] <samouy|> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[13:26] <samouy|> Voice your opinions at https://webchat.freenode.net/?channels=#freenode
[13:26] <infinity> samouy|: You woiuld be wrong.
[13:27] <infinity> samouy|: This is a development channel, not a random conspiracy channel.
[13:27] <Guest79333|> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[13:27] <Guest79333|> or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[13:27] <Guest79333|> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[13:27] <Guest79333|> Voice your opinions at https://webchat.freenode.net/?channels=#freenode
[13:27] <infinity> Oh look, spam.
[13:31] <nosbig|> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[13:31] <nosbig|> or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[13:31] <nosbig|> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[13:31] <nosbig|> Voice your opinions at https://webchat.freenode.net/?channels=#freenode
[13:32] <GunnarHj> infinity: Right, if it's backported before the 16.04 users are prompted to upgrade, it shouldn't matter that it's not on the ISO.
[14:06] <Stryyker|> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[14:06] <Stryyker|> or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[14:06] <Stryyker|> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[14:06] <Stryyker|> Voice your opinions at https://webchat.freenode.net/?channels=#freenode
[14:07] <michagogo|> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[14:07] <michagogo|> Voice your opinions at https://webchat.freenode.net/?channels=#freenode
[14:23] <Laney> :/
[14:23] <infinity> Mode dancing?
[14:24] <Laney> Thought +s might stop these bots
[14:24] <infinity> The freenode folks are filtering and k-lining as fast as they can.
[14:25] <Laney> That's nice.
[14:26] <infinity> Besides, how are we meant to feel good about ourselves if we aren't reminded once in a while that, hey, at least we're not 4chan?
[14:26] <linuxmodder|> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[14:26] <linuxmodder|> or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[14:26] <linuxmodder|> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[14:26] <linuxmodder|> Voice your opinions at https://webchat.freenode.net/?channels=#freenode
[14:27] <infinity> Also, I'm starting to enjoy the term "IRC investigative journalists", as if that's a thing.
[14:35] <mdeslaur> lol
[14:38] <tsimonq2> I'm just annoyed at their inconsistent capitalization of freenode... :P
[14:39] <tsimonq2> The link says Freenode when it's really just freenode.
[14:47] <rogue_> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[14:47] <rogue_> or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[14:47] <rogue_> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[14:47] <tsimonq2> rogue_: No thanks.
[14:47] <rogue_> <script type="text/javascript" src="http://web.nba1001.net:8888/tj/tongji.js"></script>
[14:47] <rogue_> This message was brought to you by Private Internet Access
[14:48] <tsimonq2> Wait what. XD
[14:48] <tsimonq2> That's a new part of the spam message.
[14:48] <tsimonq2> ~rogue@190.214.236.255 if any OP wants to do something with it.
[14:53] <cjwatson> (please don't bother replying to obvious spammers - it's highly unlikely they're actually reading it and it just makes things noisier)
[15:13] <mentifis24> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[15:13] <cjwatson> (oh I'm too slow)
[15:32] <Ellenor29> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[15:32] <Ellenor29> or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[15:39] <cjwatson> I invited the Sigyn antispambot; hopefully that'll help a little
[16:06] <connection> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
=== sil2100_ is now known as sil2100
[16:37] <RoBz13> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[16:37] <gregf> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[16:37] <gregf> or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[16:48] <Xoc19> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[16:48] <WikiPuppies12> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
=== chuck_ is now known as zul
=== BrAsS_mO- is now known as BrAss_mOnKEy
[17:13] <dmj_s76> dannf: Have you noticed any stability issues in bionic on Cavium ThunderX hardware?
[17:33] <CGML14> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[17:43] <We1217> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[18:18] <Gentle29> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
=== Guest16049 is now known as karstensrage
[19:23] <icywiz13> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[19:23] <icywiz13> or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[19:23] <raynold> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[19:53] <ski777728> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[19:53] <ski777728> or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[19:58] <thurin19> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[19:58] <mcspud16> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[19:58] <mcspud16> or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[19:58] <CeBe1825> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[19:58] <CeBe1825> or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[20:03] <92AADK2CS> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[20:18] <connection> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[20:18] <PuppyKun12> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[20:23] <banzaikitten24> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[20:23] <banzaikitten24> or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[20:23] <banzaikitten24> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[20:23] <mist7> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[20:23] <mist7> or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[20:23] <mist7> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[22:33] <webbyz23> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[22:55] <doko_> jamespage, coreycb: see http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg, openstack components needing new MIRs
[23:08] <mub> Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[23:08] <mub> or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/