[09:44] In the past udev didn't use a bios relative naming scheme. === hasselmm1 is now known as hasselmm [11:41] 'Morning all === ztane_ is now known as ztane [17:11] the day has come!: http://paste.ubuntu.com/14030245/ [19:54] hiii, how can i fix this: W: Failed to fetch http://swupdate.openvpn.net/apt/dists/trusty/Release No Hash entry in Release file /var/lib/apt/lists/partial/swupdate.openvpn.net_apt_dists_trusty_Release, which is considered strong enough for security purposes [19:54] i cant find any good info on google, maybe im noob [19:54] CryptoSiD: they don't have a xenial release yet because xenial isn't released yet... [19:55] i know but trusty release was working fine for a while on xenial [19:55] started having problem last week [19:55] that's the hazard of using an experimental build: not all of your software is going to work. [19:55] well, xenail of this week != xenial of last week [19:55] well there is no hash on the release file, i found a way to disable the hash check on apt yesterday but i cant find it back [20:18] https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/1526267/comments/6 [20:18] Launchpad bug 1526267 in apt-xapian-index (Ubuntu) ".../softwarecenter/backend/scagent.py : no module named "spawn_helper"" [Undecided,Confirmed] [20:18] this bug is mission critical [20:18] cant update packages unless this is fixed [20:27] who maintains apt-xapian-index [20:29] retrojeff: https://anonscm.debian.org/gitweb/?p=collab-maint/apt-xapian-index.git [20:29] owner Enrico Zini [20:29] so its more a debian problem [20:29] also see: https://packages.debian.org/source/sid/apt-xapian-index [20:30] for bug reports. [20:46] this bug is downstream [20:46] I dont see anything in git that would cause this bug [20:47] oh it said right in the bug title that its softwarecenter [20:47] hold on while I smash my keyboard on my face [20:54] possible fix [20:54] apt-get install --reinstall software-center [20:55] nope [20:59] http://www.omgubuntu.co.uk/2015/11/the-ubuntu-software-centre-is-being-replace-in-16-04-lts [20:59] we haven't seen this yet, but it's coming. [21:22] ok [21:22] so I can ignore these warnings in the mean time