IRC Logs for #crux-devel Saturday, 2018-02-17

*** TheCephalopod has joined #crux-devel01:50
*** john_cephalopoda has quit IRC01:54
*** TheCephalopod has quit IRC02:15
*** __18VADBHIX has quit IRC03:42
*** __18VADBHIX has joined #crux-devel03:43
*** j_v has joined #crux-devel09:15
*** chinarulezzz_ has joined #crux-devel09:25
*** john_cephalopoda has joined #crux-devel10:07
*** maraku has quit IRC11:44
*** maraku has joined #crux-devel11:44
*** erdic_ has joined #crux-devel11:55
*** rmull_ has joined #crux-devel11:55
*** onodera has joined #crux-devel11:57
*** prologic_ has joined #crux-devel11:58
*** erdic has quit IRC12:00
*** prologic has quit IRC12:00
*** rmull has quit IRC12:00
*** chinarulezzz_ has quit IRC12:17
*** chinarulezzz_ has joined #crux-devel12:17
*** onodera has quit IRC12:24
*** onodera has joined #crux-devel12:28
j_vfor first commit when starting as new maintainer of a contrib port, is it preferred to start by simply changing the Maintainer info, then make changes (updates, fixes) after that?12:30
j_vor is it ok if that first commit as new Maintainer includes version updates, manpage dir changes, etc12:31
pedjaj_v, you mean split commits between changing Maintainer line and updates?12:39
j_vyeah, was wondering if that would be cleaner12:40
pedjatechnically, changing Maintainer *is* an update :)12:42
pedjait's maybe cleaner, one commit per change, but it does make history a bit harder to read, imho12:43
j_vok. my inclination is to just do it all in one commit, and just be verbose in my commit comments (which is my preference when it all can't fit on the commit message line).12:45
pedjaI think that's the preferred way. mine, anyway :)12:46
j_vthanks for your input :)12:48
pedjabtw, is 'git pull' from contrib kind of slow for you too, j_v ?12:48
pedjawell, if I am wrong, one of the developers *will* kick my ass for spreading BS12:50
j_vworse case scenario, i'll get told to adjust my methods. i'm a big boy and i can handle getting yelled at. i doubt i'll do anything that will actually upset anyone.12:52
j_vas far as git pull being slow, my isp has seemed less dependable ever since net neutrality went away12:53
j_vso it's hard to decide where a slow down might be coming from12:54
pedjaouch. US ISPs move fast when it suits them, don't they?12:57
j_vyeah, i think that pretty well describes it12:58
j_vi still remember my first modem was a 14.4kbit/s, so i can still think of speeds today as fast, even when i suspect my isp of rate limiting some of my connections13:03
pedjaI'd expect rate throttling for Netflix, or torrents, but ssh?13:11
pedjaotoh, who knows how their minds work13:12
j_vit's really hard to say... i suspect they are rate limiting me because i don't use them for cable tv, which they provide and want to charge more and more for less and less, but then cable tv brings out the grump in me13:13
john_cephalopodaDo I have to send the PGP key and the ssh key to frinnst, or can anybody else take them and plug them into contrib?13:13
john_cephalopoda*somebody else13:14
pedjajohn_cephalopoda, send them to frinnst, but give him some time, it's weekend :)13:15
pedjaj_v, yeah, I hate that packaged deals. net+iptv.13:16
john_cephalopodapedja: He sent me a PM yesterday but I wasn't fast enough generating the keys :þ13:16
pedjacareful, your nerd cred might take a hit if people know that you weren't using gnupg already ;)13:18
pedjaor were you talking about ssh keys?13:19
john_cephalopodaBoth sshh and gpg13:20
john_cephalopodaNobody is using gpg.13:21
pedjablasphemy!13:21
john_cephalopodaI think there is one professor in the university that has a PGP key for mail.13:21
john_cephalopodaElse I don't know anybody.13:21
john_cephalopodaI think the issue witth PGP is, that it is made so complicated.13:22
pedjaneither do I, but I generated mine so I could use password-store13:22
john_cephalopodaI am using OMEMO to encrypt my XMPP chats and pretty much every website uses TLS. OMEMO is one checkbox in my client, TLS doesn't take any configuration.13:23
pedjagpg is like git, or vim, or golf. relatively easy to pick up the basics, takes a lifetime to master13:24
john_cephalopodaBut PGP is hard to set up, with unintuitive command line options.13:25
john_cephalopodaWho thought "gpg --full-generate-key" was a good command name?13:25
john_cephalopodaSSH has "ssh-keygen", which is a completely intuitive command and shows up when I write "ssh" and try to tab-complete.13:26
john_cephalopodaAnd then "gpg --list-public-keys --keyid-format LONG"  instead of "ls .ssh"13:27
pedjaor 'gpg -k'13:30
pedjawith 'keyid-format 0xlong' set in gpg.conf13:32
john_cephalopodaI didn't find that in any online tutorial.13:32
john_cephalopodaIt's completely unintuitive.13:33
pedjathat's a discussion for another channel, not this one13:36
john_cephalopodaYeah, probably.13:39
j_vwhen i pushed commit for nmh port, i noticed a bit about 'Generating repository for directory ...': http://ix.io/Ln913:53
j_vis that because i forget to set push to current in my .gitconfig?13:54
j_vi have push set to simple13:54
j_vsorry about the 'git branch -a' bit... didn't mean to select that part when i was creating the paste13:56
pedjasuggestion at https://crux.nu/Main/ContribHowTo is to set 'default = current' for push13:57
j_vyeah, i read it, just forgot to adjust my .gitconfig before i pushed... just wondering if i created a mess with those '3.{2,3,4}.new' repository messages.14:00
*** onodera has quit IRC14:05
*** onodera has joined #crux-devel14:05
j_vi think it was ok. after fixing my ~/.gitconfig, i still got those messages when i pushed libbsd, so i think it must be part of a post-receive hook on the server14:27
*** jue has quit IRC15:06
pedjathe delay between 'git pull' and it actually completing is weirdly consistent, 65s15:13
frinnstare you using port 22?15:22
frinnstits throttled, use 222215:22
pedjaI already have 2222 as a port for crux.nu in ssh config, that's the weird part :)15:27
*** jue has joined #crux-devel15:30
pedjait worked fine a couple of days ago, so it's probably a network issue15:37
pedjaheh. of course it works if I run Wireshark, trying to see where the issue might be.15:43
john_cephalopodaHmm, there is an issue with symlinked directories.19:43
john_cephalopodaWhen I got a port residing in /usr/lib and want to update the port with a new version that installs to /usr/lib64, it complains that there are conflicting files, although lib64 is linked to lib.19:44
*** john_cephalopoda has quit IRC19:52
*** john_cephalopoda has joined #crux-devel19:53
j_vjue: i'm doing the finishing touches for taking over contrib/qiv port. you are listed as original packager. which would you prefer: update your info, remove the Packager line, or leave the Packager line as is?19:55
*** john_cephalopoda has quit IRC20:09
jaegerwe're removing packager lines these days20:14
*** john_cephalopoda has joined #crux-devel20:16
*** john_cephalopoda has quit IRC20:16
*** john_cephalopoda has joined #crux-devel20:16
john_cephalopodaj_v: How many ports do you got left to update?20:17
john_cephalopodaI don't want to push random stuff when you are just about to push your changes, and by that confuse your local git.20:19
j_voh, anything i've got can wait... go ahead. it'll give me an excuse to take a break, have a smoke... thanks for being so considerate :)20:21
john_cephalopodaOk, just want to push fluidsynth, which I just got ready.20:22
j_vcool20:22
john_cephalopodaDone.20:23
john_cephalopodaI'll update some more things.20:29
j_vand sorry if I caused you any trouble... I realize you may have gotten caught by one of my pushes20:29
john_cephalopodaIt's ok, should have waited one more day :þ20:29
jaegerJust get into the habit of doing a pull before a commit, makes things smoother20:29
j_vmakes sense, thanks for the tip20:30
jaegerNo problem20:30
j_vBeen a while since I used git stash. I'll brush up on that, too. That has saved me some trouble in the past.20:32
jaegeryeah, can definitely be handy20:32
pedja'git fsck --lost-found' saved my sorry ass just now :)20:36
j_vI've never used that one... sounds handy.20:37
pedjait finds dangling objects, so you can 'git show -p $sha' them.20:41
j_vnice20:42
pedjaif you run 'git reset --hard' after staging but not commiting something, like I did20:42
pedjathen it's only a matter of 'git apply $patch'20:43
john_cephalopodaj_v: Is it normal that dev86 displays me a config screen?20:45
j_vyou mean when building the package?20:47
john_cephalopodahttps://ahti-saarelainen.zgrep.org/~jmf/tmp/dev86.png20:47
john_cephalopodaYeah20:47
john_cephalopodaI was quite confused when I suddenly had the choice between things that were presented to me completely out of context :þ20:48
j_vthat's very weird... I just rebuilt it again, and I don't get that.20:49
pedjayup, dev86 gets interactive for me too20:50
j_vcan you try with the original port?20:51
j_vok, i think i see it... should have a fix momentarily20:52
john_cephalopodaJust compileed the original port, the interactive screen doesn't appear there.20:54
john_cephalopodaHmm, I really have to find a fix for my laptop keyboard duplicating letters all the time...20:54
john_cephalopodaI wonder if there is a debounce option in X or the linux driver section.20:55
j_vi took out the 'echo quit | ...' because when i build in containers, it does happen... will re-add it20:56
john_cephalopodaI have to properly containerize my process.20:59
j_vwell, i think i will have to set up testing  builds with fakeroot before i push21:00
john_cephalopodaI also have to set up stuff like that.21:00
j_vcan you try it now so i can be sure i didn't miss anything?21:01
pedjathanks, j_v , it works now :)21:02
j_vcool... i should've known that that part was there for a reason and not assume that just because it builds cleanly in my setup, that it will be fine for all setups...21:03
john_cephalopodaAh, very nice.21:03
john_cephalopodaNow it works.21:03
j_vlive and learn... SOHK (school of hard knocks)21:03
john_cephalopoda♪♪♪ It's a hard knock life for us ♪♪♪21:04
j_vyep, no doubt, good thing i'm used to it21:04
john_cephalopodaI fortunately haven't got big things to change in ports. Only simple version bumps.21:04
john_cephalopodaAnd simple ports.21:05
john_cephalopodaNot working with containers right now, using all methods available to make sure that it works though (checking for footprint changes, etc)21:06
john_cephalopodaI really have to change that, especially once I want to bring some own ports to contrib.21:06
jaegerhttps://github.com/mhoush/crux-docker-image/tree/dist-amd64 <-- here's an automatically updated docker base image you're welcome to use21:07
j_vnice, i was just about to suggest docker, but i think you know about using it more than i do21:08
john_cephalopodaOh, thanks.,21:08
jaegerIt's not too tough to start using docker, fortunately21:08
j_vi've got my own thing called pkgwrap, but it's still a bit WIP yet, so perhaps not really one to start with.21:10
jaegerchroots or VMs are also good options, use whatever works best for you21:12
pedjaI am reusing one container for all ports, which is not the proper way do it, but I really can't build mesa, llvm or qt over and over again :)21:36
pedjahm. anyone have issues downloading tzdata source?21:38
*** teK_ has quit IRC21:42
pedjaargh. I know why my access to contrib repo was so slow. apparently, the relevant option in ssh config is 'HostName' and not 'Hostname' :)21:59
pedjaWireshark ftw22:01
john_cephalopodaOh, I just realized that I wrote a mail to the contrib mail address in January 2017, that lmms is broken. Hasn't been fixed since then :þþ22:06
john_cephalopodaNow I am taking it over.22:06
jaegerpedja: it would be very simple to have one base container image for things not needing X, then another image derived from that base but also with X installed22:12
jaegeror just mesa3d, for example22:12
*** onodera has quit IRC22:18
pedjajaeger, that's the more elegant solution. what I have been trying is to extend the crux image builder script to create more 'flavors', if you will22:24
pedjathat are later converted to Docker images22:24
pedjacurrently, 2 flavors are 'release' and 'snapshot' (your updated ISO)22:26
pedjacore ports only, so far22:29
pedjaperhaps something like multi stage build would be a cleaner solution, but I haven't looked at it yet.22:32
pedjaor using packer, which can make qemu, docker and bunch of other images using one configuration file22:34
john_cephalopodaHmm, for some reason docker just doesn't work.22:41
john_cephalopodaThe daemon appears to be crashing instantly :/22:42
john_cephalopodaA good thing would be, if ports that are not in core and not dependencies (or dependencies of dependencies) would be automatically blacklisted during the building.22:43
jaegerjohn_cephalopoda: if you've not used docker before, run /usr/share/docker/check-config.sh or whatever it is23:30
jaegeryou may be missing kernel options, it needs a lot23:30

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!