<     May 2017     >
Su Mo Tu We Th Fr Sa  
    1  2  3  4  5  6  
 7  8  9 10 11 12 13  
14 15 16 17 18 19 20  
21 22 23 24 25 26 27  
28 29 30 31
00:05 blueness joined
00:06 LouisA joined
00:09 rfs613 joined
01:42 irclogger_com joined
01:42 Topic for
01:53 s33se joined
02:19 <xentec> well that was funny. I hacked abuild to build my packages in /tmp (tmpfs) which returns a size of 0 (instead of 4) for $pkgdir and therefore the whole package
02:21 <xentec> thats one mystery solved but I still wonder, what makes apk behave "drunk" when it sees a 0 byte package
02:46 <kaniini> humm
02:46 <kaniini> can you tell me how you created the 0 byte package?
02:51 <kaniini> oh i see. use a tmpfs
03:17 bfritz joined
04:08 <TemptorSent> kaniini: Would you mind throwing some test cases at this when you get a chance? http://termbin.com/q6b6
04:09 <TemptorSent> It's a simple tree-growth implementation that should be ~O(3N)
04:10 <TemptorSent> Accepts deps in tab separated format, first column is the target, remainder are immediate deps.
04:11 <TemptorSent> Builds complete dep chain for each target starting from root targets (those with only an entry in the first column)
04:11 <TemptorSent> Can also build the broken dep chain
04:12 <TemptorSent> So not a SAT solver, but also not NP complete complexity.
04:15 <TemptorSent> To test, source the file and cat deplist to it.
04:15 <TemptorSent> options to control which lists are printed are fwd-deps, broken-deps, fwd-raw, rev-raw
04:39 tmh1999 joined
05:14 mmlb joined
05:44 BitL0G1c joined
07:01 cyteen joined
08:10 stateless joined
09:23 jailbox joined
10:16 fekepp joined
10:20 LouisA joined
11:20 t0mmy joined
14:44 blueness joined
14:57 cyteen joined
15:39 <BitL0G1c> can nginx-naxsi be pulled please ?
15:54 gromero joined
16:02 <pickfire> kaniini: I need help!
16:02 <pickfire> Can main/python[2-3]-tkinter be moved to main/py[2-3]-tkinter?
16:02 <pickfire> I think it is better to keep those python modules py-
16:04 <pickfire> I have added some added/updated some python packages, some will break stuff.
16:05 <pickfire> But I don't get to split py3-numpy into py3-numpy-dev, not sure how.
16:11 <pickfire> I hope d5409f57dd274647052e4a4d2057e1232a2a36a6 don't fix it that way.
16:16 <jirutka> BitL0G1c: what modules from nginx-naxsi do you currently use/need?
16:28 YoursTruly joined
16:30 LouisA joined
16:37 <BitL0G1c> jirutka - I would like nginx without pax disabled - my server gets brute forced all the time
17:07 __0xAX joined
17:31 <Shiz> ncopa: i think the gpg-remailer infra is fully done
17:31 <Shiz> including automation :P
18:35 <Shiz> clandmeter: ping
18:45 fekepp joined
18:49 minimalism joined
18:56 <clandmeter> pong
21:03 nidan_ joined
21:04 <nidan_> Hello. =)
21:08 <nidan_> I'm trying to compile glibc 2.25 on Alpine, keeping it in /opt (done this before with 2.22 on an older Alpine), but now I get a relocation error.
21:08 <nidan_> After a ton of googling it seems to be related to gcc's hardened specs, but I'm not sure.
21:09 <nidan_> It's rather weird as the command line (abbr.) is: gcc -nostdlib -nostartfiles -static -o ... some objs n' so ... crtn.o
21:11 <nidan_> And the error it spits out is: .../ld: .../crt1.o: relocation R_X64_64_32S against symbol `__libc_csu_fini` can not be used when making a shared object; recompile with -fPIC
21:11 <nidan_> But I'm rather certain that glibc's makefile doesn't lack -fPIC where necessary, AND the commandline has -static on it..
21:11 czart__ joined
21:12 <nidan_> Only thing I've found that seem to, perhaps, be relevant is https://bugzilla.redhat.com/show_bug.cgi?id=1304277#c1
21:24 <nidan_> Could the specs for gcc and ld differ in alpine?
21:24 <nidan_> Longshot...
21:28 <jirutka> <nidan_>: I'm trying to compile glibc 2.25 on Alpine … Don’t. Just don’t.
21:28 <nidan_> jirutka: I know the pain. But it's not an option to me unfortunately. =/
21:28 <jirutka> nidan_: then use glibc-based distro
21:28 <nidan_> jirutka: 2.22 worked on edge a couple of months (before 3.5) ago.
21:29 <nidan_> jirutka: Not an option either.
21:29 <jirutka> then Linux From Scratch…?
21:29 <Shiz> im not sure what causes the issue you're encountering
21:30 <Shiz> but it may be that glibc doesn't like static PIE
21:30 <nidan_> That's an option in the long run, not right now though. I have a program that REALLY needs glibc that runs fine with glibc in /opt.
21:30 <nidan_> Shiz: I'm rusty, fill me in?
21:31 <Shiz> would this perhaps be more useful to you? https://github.com/sgerrand/alpine-pkg-glibc
21:31 <Shiz> im afraid otherwise we can't really help you either
21:33 <nidan_> Shiz: Probably, thanks for the hint!
21:34 <Shiz> also, re: static PIE: the alpine toolchain supports statically linked PIE binaries which create a different ELF output type
21:34 <Shiz> that may interfere with build processes that tinker with low-level details like detials of the generated ELF files
21:34 <Shiz> may be that glibc's build process doesn't like that
21:35 <Shiz> anyway, standard disclaimer from jirutka applies to above
21:36 <Shiz> we don't support glibc, so any frustrations that arise from dealing with it are purely your own :P
21:37 <nidan_> Shiz: Thanks.
21:37 <nidan_> Shiz: Yeah, I know, just looking for hints. =)
21:38 <nidan_> Come to think of it, it's been a long time since I tried that other software with libc6-compat, maybe it will work today. =)
21:38 <nidan_> Spoken like a true optimist! =)
21:39 <Shiz> :)
21:39 <Shiz> if it's software you have source code for, i'll even help you porting it to musl and packaging it if that takes you away from glibc on alpine
21:39 <Shiz> :P
21:41 <nidan_> Shiz: I don't unfortunately.. I might be able to pull a few strings to get them to release a version that doesn't depend on glibc but I wouldn't get my hopes up. =/
22:09 fekepp1 joined
22:12 rfs613_ joined
22:15 tg` joined
22:21 sigjuice joined
22:23 stwa joined
22:37 tdtrask joined
22:37 HEROnymous joined
22:41 cyteen joined
22:42 minimalism joined
22:42 robtec joined
22:57 mmlb joined