**** BEGIN LOGGING AT Thu May 18 03:00:03 2017 May 18 11:19:29 hi May 18 11:39:45 hey jonwil May 18 14:49:41 someone renewed the certificate for supl.nokia.com May 18 14:50:53 it's a bit mysterious although i'm not complaining :~) May 18 14:50:57 Looks like the domain is resolving again too May 18 14:51:17 or not May 18 14:51:22 not May 18 14:51:46 yeah its my DNS that's giving me false readings May 18 14:52:30 actually no, a dns record for it seems to exist but pointing to 127.0.0.1 May 18 14:53:01 yes, that's been the case for a while now May 18 14:53:39 if we could know who renews the cert, and get them to fix this May 18 14:54:00 evidently they have a reason to renew the cert May 18 14:55:06 The whois record lists dnsauthority@nokia.com as the admin email, maybe contacting that address would help... May 18 14:55:07 maybe there's an updated supl server name that depends on it ... maybe for lumias or whatever else that had Here maps May 18 14:55:54 job for council maybe? May 18 14:55:59 Yeah possible May 18 14:58:14 Its possible the certificate renewal was some sort of semi-automated process May 18 14:59:34 possible too May 18 15:00:28 thought of that, but still ... that hints at a box somewhere still being maintained (at least kept running, haha) May 18 15:01:21 Subject: C=NL, ST=Noord-Brabant, L=Veldhoven, O=HERE Global BV, CN=supl.nokia.com May 18 15:01:42 Issuer: C=US, O=Symantec Corporation, OU=Symantec Trust Network, CN=Symantec Class 3 Secure Server SHA256 SSL CA May 18 15:05:40 anyhow, what matters is that (with the right hosts file entry) supl on n900 will keep working for now May 18 15:13:17 yeah :~) May 18 16:34:58 sicelo: it might be that DNS resolves different IP depending on the location May 18 16:35:22 if you try to resolve from internet, it leads to amazon servers May 18 16:35:30 not to 127.0.0.1 May 18 16:51:25 freemangordon Hello. I just did apt-get source gtk+2.0 on Devuan. Got warnings about the package signature: May 18 16:51:27 gpgv: keyblock resource `/root/.gnupg/trustedkeys.gpg': file open error May 18 16:51:27 gpgv: Signature made Thu 24 Mar 2016 22:17:12 CET using RSA key ID C37C4E36 May 18 16:51:27 gpgv: Can't check signature: public key not found May 18 16:51:27 dpkg-source: warning: failed to verify signature on ./gtk+2.0_2.24.25-3+deb8u1.dsc May 18 16:52:39 I this normal? I did one time a public key installation, for emdebian. But I just followed instructions. How to correct it here? May 18 17:08:57 Enrico_Menotti: why do you need signed package? May 18 17:09:19 also, why you're using root account? May 18 17:10:41 Enrico_Menotti: also, is this a "stock" devuan or you've played with it a bit? May 18 17:11:16 Well, the root account is just because I had to use it for some tasks (for example debootstrapping Devuan for the N900), and I just kept on using that, so I don't have to do sudo or similar things. It may be it's the wrong way, yes. May 18 17:11:43 This Devuan installation is quite brand new - just did an apt-get dist-upgrade, and installed a few packages. May 18 17:11:54 Enrico_Menotti: dist-upgrade? May 18 17:12:10 Is that wrong? May 18 17:13:05 well, all my work is on jessie May 18 17:13:16 no idea if it will work on newer May 18 17:14:52 But in my sources.list I have Jessie, not newer distributions. I thought a dist-upgrade just downloaded newer versions for packages, without moving to other distributions. May 18 17:14:56 Am I wrong? May 18 17:16:08 no, it is "upgrade" that does it, dist-upgrade upgrades to newer distro version May 18 17:16:28 if available ofc May 18 17:17:14 I had read some things about the difference between apt-get upgrade and apt-get dist-upgrade, and as far as I can understand the difference is manly (or even only) that the former only upgrades installed packages, while the latter also removes/adds packages. Is this correct? May 18 17:17:38 In any case, since I only have Jessie in the sources.list, may I tell that I am still on Jessie? May 18 17:17:41 freemangordon: even when release name is explicitely mentionned in sources.list? *doubt* May 18 17:18:08 ok, I might be wron, however it is OT here May 18 17:18:41 Enrico_Menotti: but apt-get unable to verify signatures smells like a broke package management May 18 17:18:47 *broken May 18 17:21:15 I just read a few things about the gpgv file open error above. I was surely missing debian-keyring. I installed it. However, still no .gnupg directory. I'd try to verify the signature again, but I don't know how to do that without re-downloading the source package for gtk+. May 18 17:30:04 ...had a look around and still not clear. Since it's a bit off-topic here, I will ask on #devuan. May 18 19:15:25 freemangordon Yesterday you said that there is no debian folder in gtk+2.0_2.24.25.orig.tar.xz. I did apt-source and I end up with a gtk+2.0-2.24.25 which contains a debian folder. I will replace it with yours, ok? May 18 19:16:48 Now, for the actual build: the INSTALL file suggests to use ./configure and make. The HACKING file suggests ./autogen.sh, which however does not exist here. You also mentioned pdkg-buildpackage. Is that different from ./configure and make? May 18 20:04:26 dpkg-buildpackage runs .configure and make on its own May 18 20:05:02 dpkg-buildpackage is the preferred way to build stuff on debian-based distros May 19 01:17:13 Huh... https://archive.debian.net/ Down... May 19 01:19:14 Sounds fun: https://packages.debian.org/jessie/chimera2 Except, it depends on https://packages.debian.org/jessie/libjpeg62-turbo , which in turn depends on libc6(>=2.7). May 19 01:26:54 Wikiwide: http://archive.debian.org/ May 19 01:30:37 Thank you :-) May 19 01:32:04 Is there a webpage with search across the repositories? So far, I manually found http://archive.debian.org/debian/pool/main/c/chromium-browser/ May 19 02:32:06 Wikiwide: would "apt-cache search" suffice? **** ENDING LOGGING AT Fri May 19 03:00:01 2017