[00:24] <pmatulis_> for my presseding i've started using a proxy (squid-deb-proxy)
[00:24] <pmatulis_> d-i    mirror/http/proxy       string http://hostname:8000/
[00:24] <pmatulis_> this works
[00:24] <pmatulis_> but GPG keyserver port gets blocked (my preseed contains installation of a PPA)
[00:25] <pmatulis_> 1399421481.033      0 192.168.1.102 TCP_DENIED/403 3612 GET http://keyserver.ubuntu.com:11371/pks/lookup? - HIER_NONE/- text/html
[00:25] <pmatulis_> what to do?
[00:41] <pmatulis_> disregard, squid-deb-proxy is for 'debs', imagine that
[23:23] <cjenkin2> I'm having trouble getting Ubiquity to recognize a new (custom) keyboard layout. It is definitely in keyboard_names.py but it does not show up in the selectable list
[23:24] <cjenkin2> I'm thinking that adding this line in preseed.conf would help: keyboard-configuration keyboard-configuration/unsupported_layout boolean true
[23:24] <cjenkin2> But the problem is I am a complete newbie and can't seem to find where this file lives!
[23:24] <xnox> cjenkin2: what layout are you trying to add?
[23:25] <cjenkin2> xnox: A Spanish variant. I don't know what to call it other than a company internal name, SPPP
[23:25] <cjenkin2> The tilde key is less than / greater than
[23:25] <cjwatson> You probably need to update console-setup in a similar way and make sure that's installed in the live filesystem.
[23:25] <cjenkin2> I couldn't find a keyboard layout that matched so I made my own, and in userspace it seems to work
[23:25] <cjwatson> ubiquity relies on that for some bits.
[23:26] <cjwatson> And you should certainly have it in xkb-data.
[23:26] <cjwatson> The way this is done is basically optimised for us propagating things up from xkb-data, so if you're adding something custom you're best off starting there.
[23:26] <cjenkin2> cjwatson: It is in my custom version of xkb-data
[23:26] <cjwatson> Right, you may just be missing a console-setup update then.
[23:27] <cjwatson> The separate package as well as the partial copy of it embedded in ubiquity (sorry)
[23:27] <cjenkin2> Even though I can see the keyboard in keyboard_names.py ? Interesting
[23:27] <cjwatson> Yes
[23:27]  * cjwatson -> bed
[23:27] <cjenkin2> cjwatson: Interesting. Should I just rebuild it then?
[23:27] <cjenkin2> Ah, ok
[23:27] <cjwatson> I think it has an update rule somewhere
[23:28] <cjwatson> make KeyboardNames.pl or some such
[23:28] <cjenkin2> cjwatson: That makes sense.
[23:28] <cjwatson> Or actually it might update itself if you just rebuild
[23:28] <cjwatson> Try it :-)
[23:29] <cjenkin2> cjwatson: It should, I think it's make MyKeyboardNames.pl though, actually
[23:29] <cjwatson> Yeah, I *think* a rebuild against your modified xkb-data is sufficient, without any manual steps
[23:29] <cjenkin2> Rebuilding takes years because it's an arm machine, but hopefully that will do it
[23:29] <cjwatson> given
[23:29] <cjwatson> xkbdir = /usr/share/X11/xkb
[23:29] <cjwatson>         $(MAKE) xkbdir=$(xkbdir)
[23:29] <cjwatson>         cd Keyboard && $(MAKE) build-mini xkbdir=$(xkbdir)
[23:29] <cjwatson> in debian/rules
[23:30] <cjenkin2> Yes, that seems correct
[23:30] <cjenkin2> ubiquity found it there, anyway
[23:30] <cjwatson> anyhow, sleep before I leave a keyboard imprint on my forehead
[23:30] <cjenkin2> cjwatson: Thanks! :)
[23:30] <cjwatson> np