[00:00] <jbicha> based on the apt log attachment
[00:01] <Unit193> That was pretty much my assessment as well.
[01:46] <sunweaver> cjwatson: I see you put nx-libs-lite on the sync-blacklist.txt in 2012. The package has been removed from Debian recently and has been replaced by nx-libs. Any chance, nx-libs can be synced into Ubuntu from Debian unstable.
[01:46] <sunweaver> ?
[08:38] <cjwatson> sunweaver: That sync-blacklist entry isn't what's blocking it.  The question is whether it's OK to override the Ubuntu modifications in the nxproxy source package (because nx-libs builds a binary package that was previously built by nxproxy).  Can you go over the Debian->Ubuntu diff in nxproxy and answer that question?
[14:37] <sunweaver> cjwatson: oh my god, those nxcomp and nxproxy versions are rotten old. I will inspect those pkgs and give feedback.
[15:41] <sunweaver> cjwatson: I just checked nxproxy src:pkg and nxcomp:pkg. All Ubuntu specific changes have been in nx-libs for ages. It should be safe, say rather highly recommendable to drop these old nxcomp/nxproxy package mummies and have them replaced by maintained code from nx-libs.
[15:41] <sunweaver> cjwatson: can you do the required steps for this?
[19:04] <xnox> smoser, systemd/cryptsetup/et.al. migrated \o/
[20:08] <infinity> pitti: Looks like you wiped out your home on lillypilly before you left.  Did the britney-indexes* scripts referenced from https://wiki.ubuntu.com/ProposedMigration/LocalSetup survive somewhere else?