[00:25] <karstensrage> whats involved in getting backport bugs addressed
[00:31] <lamont> I don't like it when apt-get dist-upgrade says this:
[00:31] <lamont> Fetched 7,012 kB in 25s (275 kB/s)
[00:31] <lamont> Segmentation fault
[00:33] <karstensrage> is that 16.04?
[00:36] <GunnarHj> karstensrage: Ping someone in https://launchpad.net/~ubuntu-backporters
[00:42] <karstensrage> anyone? there are only 10?
[00:43] <karstensrage> the pending members have been pending for quite some time O.O
[00:45] <karstensrage> broder, maybe you might be interested?
[00:59] <karstensrage> whats the criteria for backporting new
[00:59] <karstensrage> stuff
[14:19] <fastercat> Is there any additonal debug output I can turn on for a video driver?
[14:20] <fastercat> It is crashing with cryptic messages like NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[14:20] <fastercat> and a lot of NVRM: Xid (PCI:0000:07:00): 3, C 00000002 SC 00000003 M 00000104 Data 00000000
[14:21] <fastercat> It is:07:00.0 VGA compatible controller: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1)
[17:14] <Unit193> zigo: LP 1562358 finally filed, along with LP 1562356.  Just FYI.
[19:19] <juliank> lamont: If the crash was in xenial, apt 1.2.8 fixes a known segfault. It just needs to be synced. It would still make sense to have a full backtrace, if possible.
[19:20] <juliank> Oh wait, no, 1.2.8 fixes an update segfault.
[19:20] <juliank> So a full bt would be *really* useful
[19:22] <juliank> If it's APT that's crashing, otherwise I don't care :)
[21:00] <infinity> Skuggen: usr/include/mysql/mysql/client_plugin.h:103:38: fatal error: mysql/plugin_auth_common.h: No such file or directory
[21:00] <infinity> compilation terminated.
[21:00] <infinity> Skuggen: MySQL's fault, or mythtv's?
[21:13] <infinity> superm1: mythtv seems to hate you.
[21:15] <Skuggen> infinity: mysql.h includes mysql/client_plugin.h in 5.7, and didn't in 5.6
[21:15] <Skuggen> It needs include/mysql on the include path to work
[21:16] <infinity> Skuggen: Is that not provided by pkg-config or similar (or is mythtv not using it?)
[21:16] <Skuggen> The header structure is a bit of a mess. Devs are working on cleaning it up, but wasn't ready for the 5.7 release :|
[21:16] <Skuggen> Yeah, I haven't seen that issue outside mythtv so far
[21:16] <Skuggen> So it's part that the directory structure is weird and part that mythtv does something a bit differently, I think
[21:17] <infinity> Yeah.  Looking now.
[21:18] <superm1> I explicitly patched to fix that
[21:18]  * superm1 shrugs
[21:18] <infinity> superm1: You may have patched the wrong bit.  The g++ command sure doesn't have the include.
[21:19]  * infinity grabs the source.
[21:23] <superm1> I patched the header check and the .pro to add the includes. It did all work correctly in my local test build
[21:23] <superm1> I'm afk atm I'll look when I get to computer
[21:30] <lamont> juliank: gdb apt-get; r dist-upgrade.... and it's working :(
[21:30] <lamont> oh, right .. let's do this on the correct machine
[21:30] <infinity> Hah.
[21:31] <lamont> apt-get dist-upgrade ==> segv.  apt-get install gdb ==>runs to completion fine.
[21:32] <lamont> bug inbound against apt with the trqace
[21:32] <infinity> You're lucky the latter didn't fix the former.
[21:32] <lamont> I KNOW
[21:32]  * lamont was quite concerned actually
[21:33] <infinity> I'd have unpacked a dpkg deb without dpkg or apt's databases being involved, probably. :P
[21:33] <lamont> I see that 1.2.8 is there, I'll try that after I file the bug.
[21:33] <infinity> s/dpkg deb/gdb deb/
[21:33] <lamont> heh
[21:33] <lamont> you know it's a red letter day, when you get to type Yes, do as I say!, twice.
[21:34] <infinity> I don't think I've had to type that in years.
[21:34] <infinity> I get the prompt all the time, but that's my own stupid fault, and it's saving me from myself.
[21:35] <lamont> oh yes, that prompt is the machine going, no seriously, think about this one before you say yes, multiple times.
[21:35] <lamont> if you ever determine that you should really type it, it's time to file a bug.
[21:35] <infinity> It's triggered by removing an Essential package, IIRC.  Not a whole lot of logic behind it.
[21:35] <infinity> And yes, absolutely a distro bug if it happens without you explicitly removing something you shouldn't.
[21:37] <lamont> yep.  removing essential is the whole and sole cause of that
[21:39]  * infinity upgrades his IBM PowerStation from 14.04 to 16.04 for the lolz.
[21:40]  * lamont attaches the trace from 1.2.8
[21:40] <lamont> juliank: over to you sir, lp #1562402
[21:41] <infinity> Man, this disk (and the SAS controller it's attached to) were wildly overspecced for this machine.
[21:41] <juliank> Oh no
[21:42] <juliank> Two different backtraces :/
[21:42] <infinity> I do believe this is the only 15k RPM disk in my house.
[21:42] <lamont> infinity: is it time for me to start shifting the home infra to xenial?
[21:42] <infinity> But I guess this is what happens when you ask IBM to make an "affordable workstation".
[21:42] <juliank> lamont: Can you generate a bt with dbgsyms?
[21:42] <lamont> maybe
[21:42] <infinity> lamont: That's what I'm doing right now.  I think we still have one or two upgrade bugs you might want to wait on, though.
[21:43]  * lamont hasn't bothered with dbgsyms in ages... process?
[21:43] <infinity> lamont: Definitely have one that fubars upgrades in GUIs.
[21:43] <infinity> lamont: I'm seeing now how serverish upgrades go.
[21:43] <lamont> infinity: I see
[21:43]  * lamont will let infinity embrace the suck on his behalf
[21:44] <infinity> Right now, all I can report is that server upgrades are fast.  If you have a disk that can actually keep up with your CPU.
[21:44] <infinity> Or, in this case, a disk that might be faster than my CPU. :P
[21:44] <juliank> lamont: and/or run it in valgrind
[21:45] <juliank> (preferably and)
[21:45] <infinity> lamont: dbgsyms == install libc6-dbg and install the matching lib and apt ddebs from http://ddebs.ubuntu.com/pool/main/a/apt/
[21:45] <lamont> sigh.  installed valgrind (and the most recent maas, because of huh), and then ran apt-get dist-upgrade... and it's running
[21:46] <infinity> lamont: Yes, you can add ddebs.u.c to sources.list and 'apt-get install apt-dbgsym' too, if apt is working.
[21:46] <infinity> Oh.  Or valgrind broke you.  \o/
[21:46] <juliank> :(
[21:46] <lamont> yeah  it could have been that the maas ppa install tickled it into happiness, too
[21:46] <infinity> Yay for perturbing databases until it works. :(
[21:46] <lamont> but valgrind and I are about to have some fun
[21:46] <lamont> infinity: no yay
[21:46]  * lamont loves hard failurs
[21:46] <infinity> Saving /var/lib/dpkg, /var/cache/apt, and /var/lib/apt might have been nice.
[21:47] <infinity> If you have a time machine.
[21:47] <infinity> DO YOU HAVE A TIME MACHINE?!
[21:47] <lamont> "dammit, I wish I'd created that lvmsnapshot that I didn;t think to do this time"
[21:47] <lamont> ah, but I do have a backup of yesterday that includes /var/lib/dpkg
[21:47] <infinity> Indeed you would.
[21:48] <infinity> If you know what you've installed since, it's pretty safe to restore the old dpkg bits.  Well, safe-ish.
[21:48] <infinity> And just reinstall overtop again.
[21:48] <infinity> After debugging. :P
[21:48] <lamont> sigh
[21:48] <lamont> backup excludes for /var: lib/dpkg/
[21:49] <infinity> lamont: /var/backups
[21:49] <lamont> I'll rewind the maas bits, maybe
[21:49] <lamont> oh!
[21:50] <juliank> lamont: Do you perhaps have /var/backups/dpkg.status.0{,1.gz,2.gz}
[21:50] <infinity> It's not the entirety of /var/lib/dpkg, IIRC, but it's the databases apt cares about.
[21:50]  * juliank has that on Debian
[21:50] <juliank> but not sure why
[21:50] <lamont> yeah
[21:50] <lamont> do I care about more than dpkg.status?
[21:50] <infinity> Possibly apt.extended_states.0 too, depending on where the crash was.
[21:51] <juliank> That should be it. You can just pass -o Dir::State::Status=/var/backups/dpkg.status.0  to APT I'd think
[21:52] <lamont> Segmentation fault
[21:52] <lamont> \o/
[21:52] <juliank> Yay! Let's go valgrinding that bastard.
[21:53]  * lamont installs dbg syms
[21:53] <lamont> W: Failed to fetch http://ddebs.ubuntu.com/ubuntu/dists/xenial-proposed/main/binary-amd64/Packages  404  Not Found
[21:53] <lamont> W: Failed to fetch http://ddebs.ubuntu.com/ubuntu/dists/xenial-proposed/main/binary-amd64/Packages  404  Not Found
[21:53] <lamont> infinity: sigh.. what does that ddebs line look like?
[21:54] <infinity> lamont: No ubuntu.
[21:54] <lamont> ta
[21:54] <infinity> Just ddebs.u.c/ $series $comp $comp
[21:54] <infinity> We really should put an ubuntu symlink in there to /
[21:54] <juliank> infinity: oh, thanks for the 1.2.8 sync.
[21:54] <infinity> Maybe I'll do that right now.
[21:55] <infinity> juliank: I caught you talking about it in backscroll, changelog looked sane, so you're welcome.
[21:55] <lamont> http://paste.ubuntu.com/15514548/ <-- with dbgsyms
[21:55] <stgraber> infinity: yes we should! it's been bugging me SO many times
[21:55] <infinity> stgraber: Done.
[21:56]  * infinity tests.
[21:56] <juliank> I don't think it's mentioned in the changelog, but I made the flaky tests retry, so I hope it passes CI on all architectures now, even the always-failed armhf
[21:56] <lamont> http://paste.ubuntu.com/15514567/ <-- juliank
[21:56] <lamont> looking forward to 1.2.9 :D
[21:56] <stgraber> yay
[21:56] <infinity> Looks like that did the trick.
[21:56] <infinity> lamont: Works with ubuntu now too. :P
[21:57]  * lamont hugs infinity
[21:57] <infinity> Err.
[21:57] <juliank> hmm, seems like those dbgsym do not match your installed version :(
[21:57] <infinity> Except for apt yelling at me about it.
[21:57] <lamont> oh, yeha
[21:57] <infinity> Oh, but that's true regardless of the path.
[21:57] <infinity> It just needs fixing still.
[21:58] <juliank> Anyway, that's fairly weird stuff
[21:58] <infinity> Or I need to ship the key in the distro.  Derp.
[21:58] <Unit193> ddebs could likely be useful to add commented out in the default sources.list these days.
[21:58] <lamont> juliank: that's 1.2.7 syms with 1.2.8 apt. :(
[21:58]  * juliank thought so
[21:58] <infinity> So get 1.2.8 syms?
[21:58] <juliank> seems the new ones are not available yet
[21:59] <infinity> They're available in LP.
[21:59] <infinity> https://launchpad.net/ubuntu/+source/apt/1.2.8/+build/9403755
[21:59] <lamont> http://paste.ubuntu.com/15514599/ <-- full valgrind
[21:59] <lamont> infinity: reinstalled 1.2.7
[21:59] <infinity> That works too.  But I suspect he wants both if they're different.
[21:59] <lamont> http://paste.ubuntu.com/15514613/
[22:00] <lamont> juliank: ^^ 1.2.7 bt
[22:00] <juliank> lamont: reinstall libapt-pkg5.0=1.2.7
[22:00] <infinity> lamont: Also, dude, learn to autoremove.
[22:00] <lamont> meh
[22:00] <juliank> You only pulled in the apt binaries, not the library
[22:00] <lamont> infinity: I do.. this is me not perturbing the db
[22:00] <juliank> infinity: Now both are the same...
[22:00] <juliank> Oh well, sorry, library is not downgraded yet.
[22:01] <lamont> ii  libapt-pkg5.0:amd64                 1.2.7                               amd64        package management runtime library
[22:01] <juliank> weird
[22:01] <lamont> dpkg -l | grep 1.2.8 yields only zlib1g
[22:02] <lamont> infinity: lp #1543683 has me being generous in my keeping of kernels
[22:03] <juliank> To be fair, I have no idea what's going on. It seems that we are iterating to a broken dependency
[22:03] <juliank> (in both cases)
[22:03] <lamont> and sometime between now and mondya, I need to boot a kernel so that I can definitively say that the "fix released" there is an outright lie
[22:04] <lamont> juliank: there is one small lie in the status file, that I don't think should matter... Package: perl5 Depends: perl, because I haven't rebuilt a binary yet to depend on perl instead of perl5
[22:04] <lamont> mentioned in the interests of full disclosure
[22:05]  * lamont tries one other thing
[22:08] <lamont> interesting... if I drop the maas ppas, then all is happy and right in the world again
[22:08]  * lamont bisects
[22:08]  * infinity still resents that he needs to do this after do-release-upgrade:
[22:08] <infinity> dpkg -l | awk '/^rc/ {print $2}' | xargs dpkg -P
[22:08] <lamont> amusingly, /var/backups is in my backup
[22:09] <infinity> lamont: Could the maas PPA have a broken control file somewhere that dpkg somehow missed?
[22:09] <lamont> I have been doing rm /var/lib/apt/lists/*; apt-get update each pass
[22:09] <juliank> infinity: Would you rather do apt purge ?config-files
[22:10] <infinity> juliank: I didn't know that was a thing.
[22:10] <lamont> File descriptor 3 (pipe:[5854305]) leaked on vgs invocation. Parent PID 3149: /usr/sbin/grub-probe
[22:10] <juliank> infinity: It isn't
[22:10] <lamont> stupid grub-probe
[22:10] <infinity> juliank: But it's not the shell pipe that I resent, it's that I can't upgrade-with-purge via the release-upgrader.  ie: it's our bug. :P
[22:10] <juliank> infinity: It's an aptitude thing right now...
[22:10] <juliank> But I definitely want patterns in APT soon-ish
[22:12] <infinity> lamont: As to the parallel topic, a serverish do-release-upgrade -d seemed to DTRT.  Packages all installed, postinsts all succeeded, the only unexpected removal was aptitude (which I almost consider a feature, but I suppose I should look into).
[22:12] <lamont> heh
[22:12] <infinity> Rebooting now to be sure it actually worked...
[22:12] <lamont> yeah, they'll squawk about that
[22:13] <infinity> And it boots!
[22:13] <infinity> All systemdish and kernel 4.4ish.
[22:14] <juliank> lamont: YOu might want to run with Debug::pkgPackageManager=yes and see which package causes that (it should be the last printed in a line starting with SmartUnPack)
[22:14] <juliank> then you can see if there's anything odd about that
[22:16] <juliank> We need to retry the APT test on armhf
[22:16] <lamont> \o/
[22:17] <lamont> dist-upgrade with everything but http://ppa.launchpad.net/maas-maintainers/experimental3/ubuntu enabled, ran fine.  uncommented that one, and *splat*
[22:17] <infinity> Erm.  Reboot worked okay except that my / is read-only now.  WTF, systemd.
[22:17] <lamont>     SmartUnPack maas-region-controller-min:amd64 (replace version 2.0.0~alpha3+bzr4810-0ubuntu1 with Segmentation fault
[22:17] <lamont> how appropriate
[22:18] <infinity> Replace it with a SEGV indeed.
[22:18] <infinity> juliank: Retried.
[22:18] <juliank> infinity: thx
[22:18] <lamont> http://paste.ubuntu.com/15514818/
[22:19] <juliank> lamont: What's the apt-cache policy output for that?
[22:19] <lamont> http://paste.ubuntu.com/15514824/ <-- almost pasted before you asked
[22:21] <juliank> lamont: apt-cache showpkg would be good to have too
[22:22] <lamont> http://paste.ubuntu.com/15514844/ <-- showpkg juliank
[22:22] <infinity> That's show, not showpkg.
[22:22] <lamont> -kohlrabi(root) 381 : apt-cache showpkg maas-region-controller-min > zz
[22:22] <lamont> might be, but iz showpkg.
[22:22] <juliank> infinity: BTW: The failed test tries to detect that progress reporting works (start at 0, pulses somewhere in the middle, and stops at 100). It tests a 800k file download, at speed 1600/i where i is in [1..10]
[22:23] <juliank> So it actually loads the 800 KB file at 160 KB/s
[22:23] <infinity> lamont: showpkg looks more like http://paste.ubuntu.com/15514856/
[22:24] <lamont> oh haha
[22:25] <lamont> http://paste.ubuntu.com/15514869/ <-- actually different and correct this time
[22:26] <juliank> But if it crashes after the "replaces ... with" part, it's actually worse than I though
[22:27] <juliank> Well, it makes sense, though
[22:28] <juliank> maybe it's a regression from bug #1550741
[22:28] <juliank> hmm, typo
[22:30] <juliank> That is: The problem now appears to be that the cache has an invalid version selected for installation.
[22:30] <juliank> Which might be a regression from http://anonscm.debian.org/cgit/apt/apt.git/commit/?id=0390edd5452b081f8efcf412f96d535a1d959457
[22:31] <lamont> \o/
[22:31] <lamont> juliank: and reproduced on another machine!
[22:31] <lamont> juliank: point me at an ssh key for you?
[22:32] <juliank> Second or third one of https://launchpad.net/~juliank/+sshkeys
[22:35] <lamont> http://paste.ubuntu.com/15514948/
[22:36] <lamont> | fa1b75a1-152b-4479-a80e-9b8edaea6caa | ubuntu-released/ubuntu-xenial-16.04-beta1-amd64-server-20160223.1-disk1.img  | ACTIVE |                                      |
[22:38] <juliank> hmm, where do I get that nova tool?
[22:38] <lamont> juliank: see also /query
[22:38] <lamont> that
[22:38] <lamont> s python-novaclient
[22:43] <infinity> Oh, you can't be serious.
[22:44] <infinity> lamont: Okay, one glaring effin' regression from upstart/mountall->systemd that I can't believe I'm the first to run into.
[22:44] <lamont> oh?
[22:44] <lamont> do I even want to know?
[22:44] <infinity> lamont: It fails to remount / rw if there's no (OTHERWISE COMPLETELY POINTLESS) entry for / in fstab.
[22:44] <lamont> lol
[22:44] <lamont> how's that readnoly thing going?
[22:45] <infinity> Well, fine now that I added an fstab entry. :P
[22:45] <infinity> Stupid bug is stupid.
[22:46] <infinity> And completely counter to the "empty /etc" goal, so I have no idea WTF.
[22:46] <lamont> infinity: you know what's hilarious?  "Myspace for dummies", published 2008
[22:47] <karstensrage> infinity, do you pull from unstable or just testing? for xenial?
[22:47] <lamont> juliank: amuslingly? apt-get install maas fix0rs everything
[22:47] <infinity> karstensrage: Unstable.
[22:47] <karstensrage> sweet
[22:47] <karstensrage> its up there
[22:47] <infinity> karstensrage: Does "it" have a name?
[22:48] <lamont> note also that the automatic pulling from unstable stopped for xenial a while ago
[22:48] <karstensrage> one sec
[22:48] <infinity> lamont: Yeah, he's trying to get something NEW in.
[22:48] <infinity> lamont: Which would be easier with a package name.
[22:48] <infinity> *hint, hint*
[22:48] <lamont> heh
[22:48] <lamont> infinity: what, can't you just do a for loop checking for new packages? :p
[22:49]  * lamont has lost faith
[22:49] <infinity> lamont: We effectively do just that when autosyncing, but not past DIF.
[22:49] <karstensrage> https://packages.debian.org/unstable/libpam-ufpidentity
[22:50] <infinity> karstensrage: FWIW, source packages are the real interest, so https://packages.qa.debian.org/libpam-ufpidentity would be the more relevant URL for such requests (happens that binary and source match this time, though).
[22:50] <infinity> karstensrage: And synced.
[22:51] <karstensrage> thank you so much
[22:52] <infinity> karstensrage: And https://launchpad.net/ubuntu/+source/libpam-ufpidentity to follow along at home.
[22:52]  * lamont wanders off for a bit
[22:58] <infinity> "Bash script for wrapping cron jobs to prevent excess email sendin" ... Because that extra 'g' would have been too much.
[22:59] <Unit193> Hah. :D
[22:59] <Unit193> Thanks for reviewing cronic!
[22:59] <infinity> Unit193: "Review" is a strong word for what I do with direct Debian syncs.
[23:00] <Unit193> Still, thanks.
[23:00] <infinity> But now all I can think of is some redneck worryin' about too much email sendin' on his dialup.
[23:01] <Unit193> Ahaha. :D
[23:01]  * Unit193 is from Ohio, but city parts!
[23:03] <juliank> lamont: infinity: Issue caused by the commit I linked.
[23:03] <juliank> So: Yay, it's mvo's fault!
[23:04] <infinity> juliank: Man, that mvo guy sure is a jerk.
[23:04] <infinity> Oh, wait, no.  The other thing.
[23:04] <lamont> ohio has  city parts?
[23:04] <infinity> lamont: Cleveland?
[23:05] <lamont> I guess so
[23:05] <infinity> lamont: Population of 400k.  Doesn't qualify as a "city" to me, but it does to most people. :P
[23:05] <lamont> infinity: for you, it's not a city until it's big enough to have an underbelly?
[23:05] <Unit193> Welp, I don't know what I live in then, it certainly isn't a 'city' though if CLE isn't. >_>
[23:06] <infinity> On, and Columbus is 800k.
[23:06] <infinity> That's approaching a real city.
[23:07] <lamont> Unit193: tbf, the post office serving my house is for a town that might be 4500 now, and the next closest town has about a 150k population
[23:08] <juliank> maas-region-controller-min:amd64 Depends on maas-common [ amd64 ] < 2.0.0~alpha3+bzr4810-0ubuntu1 -> 2.0.0~alpha4+bzr4843-0ubuntu1~xenial2 > ( net ) (= 2.0.0~alpha4+bzr4837-0ubuntu1~xenial1) can't be satisfied!
[23:08] <infinity> lamont: But you no longer get your Internet via Pringles can, so you're moving up in the world.
[23:08] <Unit193> lamont: ...The metro area has 124,475. >_>
[23:09] <lamont> infinity: but I hate paying for my T1
[23:10] <lamont> which, tbf, is about 1/7 the bandwidth of the radio that's still on the tower, just not used by me
[23:10] <infinity> lamont: I thought you finally got cheap residential cable out there?
[23:10] <lamont> hahaha
[23:10] <lamont> cable comes to about 2 miles away
[23:10] <infinity> Oh. :P
[23:10] <infinity> 2 miles is pretty close!
[23:10] <lamont> the DSLAM is 17000 feet -- tariff is 15000... and "T1" is a total misnomer for a pair of bonded hdsl lines
[23:11] <lamont> and that is why I have an office in town
[23:11] <infinity> Oh, it's not actual ISDN/T1 old skool tech?  Just DSL sold at T1 speeds?
[23:11] <lamont> I could have DSL if the firestation were 1/2 mile closer
[23:12] <lamont> not entirely sure... "4-wire T1"
[23:12] <lamont> but I'm given to understand that it's hdsl pretending to be a T1... 2-pair to the house, and then magically 1-pair to get to the terminus in the computer room
[23:14] <lamont> http://goo.gl/BTcjCE <-- infinity
[23:14] <lamont> that's the box in the comp room
[23:15] <lamont> the next step down was 128kbps ISDN for about 2/3 the price of the T1
[23:15] <lamont> amusingly, it's not uncommon for me to see 180KB/s from the T1
[23:15] <infinity> That sounds like real old skool analog tdm T1.
[23:16] <lamont> yeah - it's more the 2-pair from the ped to the demark that leads me to believe it's playing games
[23:16] <infinity> But maybe their magic ... Yeah.
[23:16] <juliank> Almost fixed
[23:16] <infinity> lamont: It must be weird living in the past.
[23:16] <lamont> totally
[23:17] <infinity> lamont: Did you have to brush up on WTF Frame Relay is? :P
[23:17] <lamont> also, screw you. :p
[23:17] <lamont> I don't think they're actually using frame relay, either.
[23:18] <infinity> Well, Frame or ATM would seem like the protocols of choice.
[23:18] <infinity> Perhaps with a PPPo in front of it if they hate their customers.
[23:18] <lamont> the funniest part?  they deliver me 3 voice circuits from that adtran, which then go into a telephony card
[23:18] <lamont> BECAUSE THE ISP DOESN'T DO VOIP
[23:19] <lamont> oh, the actual service for me:  their adtran is configured on a 1918 network talking to my router and passing me a /29 (and sometimes, even their tier 2 is most confused how that even works)
[23:20] <lamont> so from my perspective, it's just "ip route default via 192.168...."
[23:20] <lamont> and, of course, they advertise my /24 from the swamp for me, at no additional charge
[23:22] <lamont> anyrate, afk
[23:22] <infinity> juliank: Are you going to tag a 1.2.9 with this fix "soonish", or should I just yoink the commit for an ubuntu1?
[23:23] <juliank> infinity: I'll do some more testing and upload this tomorrow I think
[23:23] <infinity> juliank: WFM.
[23:23] <infinity> juliank: I'm in no rush, lamont got unstuck, and I'm guessing it's a bit of a corner case.  Just want it in xenial sometime soonish.
[23:26] <juliank> https://github.com/julian-klode/apt/commit/71f2ab088f8e077ba8375e87ee9bb595655f954a
[23:26] <juliank> That should fix it
[23:28] <juliank> I should also come up with a test case, though
[23:31] <juliank> infinity: I'm not sure if removing maas-region-controller-min and installing maas-region-controller is the right choice, though, but it's what APT < 1.2.7 did and does not crash
[23:32] <juliank> I see, maas-region-controller-min is not up to date enough
[23:32] <juliank> (4837 and the rest 4843)
[23:33] <juliank> Now I need to build a test case where one package needs to be removed to allow another package to be installed.
[23:33] <juliank> Let's see if I can do that
[23:46] <lamont> juliank: maas-region-controller-min got renamed to maas-region-api
[23:48] <lamont> juliank: ^^
[23:48] <juliank> Yeah, saw that.
[23:48] <lamont> so before was maas-region-controller{,-min} and now is maas-region-{api,controller}
[23:49] <juliank> It unfortunately works in a minimized example test case
[23:49] <lamont> of course it does. :(
[23:49] <lamont> SCIENCE!
[23:56] <infinity> ● nosferatu
[23:56] <infinity>     State: running
[23:56] <infinity>      Jobs: 0 queued
[23:56] <infinity>    Failed: 0 units
[23:56] <infinity> ● leviathan
[23:56] <infinity>     State: running
[23:56] <infinity>      Jobs: 1783695312 queued
[23:56] <infinity>    Failed: 1783695312 units
[23:56] <infinity> I WONDER IF THAT MIGHT BE AN ENDIAN BUG.
[23:57] <infinity> Ooo, even better on s390x.
[23:57] <infinity> ● z13-028
[23:57] <infinity>     State: running
[23:57] <infinity>      Jobs: 3804834690 queued
[23:57] <infinity>    Failed: 3804834690 units
[23:57] <infinity> SO MANY JOBS!
[23:58] <infinity> xnox: ^-- Some lolz for you.  nosferatu = amd64, leviathan = powerpc, z13-028 = s390x.
[23:59] <infinity> systemd, you never cease to amaze.