<    March 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:04 tarpit joined
00:15 <TemptorSent> avih: It appears that mtab is being used again, not sure what exactly the intent was there.
00:16 <tarpit> keep getting errors no matter what mirror I use?
00:22 <TemptorSent> shad0: The initfs builds a run-from-ram system in-place by extracting apks and applying overlays. You don't need to do anythign special to get it to boot, and you can persist your changes with lbu.
00:24 <TemptorSent> shad0: Keep in mind tha lbu defaults to backing up /etc and nothing else, so if you need to modify files elsewhere, you'll need to include them explicitly.
00:25 <TemptorSent> tarpit: What kind of errors and is it still persisting?
00:27 <tarpit> When I added the eth1 it no longer access the Internet.
00:28 <TemptorSent> tarpit: Oh, got it -- check that you still have a default route pointing to a gateway somewhere
00:29 <TemptorSent> tarpit: It sounds like your interface came up but isn't fully configured.
00:31 <tarpit> I turn off the second Ethernet to update software. It works. I will look at adding a static route.
00:32 <TemptorSent> tarpit: You just need to make sur you have a default route that actually goes out to a gatway, the other can be dhcp configured if you want, but you'll want to keep it from overwritign your default route if it's on an internal network.
00:35 blueness joined
00:36 <shad0> TemptorSent, so even on a 'sys' install, it's booting into ram?
00:36 <shad0> (I mean, initfs is loading the operating "image" into ram?)
00:36 <TemptorSent> shad0: No, once you install your sys to media, you're running a normal root.
00:37 <shad0> so setup-alpine with usb sets up a different initfs config than setup-alpine with sys or data?
00:37 <TemptorSent> shad0: You don't need to install anything to get the run-from-ram setup, just boot.
00:37 <shad0> ok... where/how would such a configuration know to look for lbu's to apply during startup?
00:37 <TemptorSent> shad0: I believe so -- it should be a "media" layout for iso/usb and a standard layout for installed systems.
00:37 <shad0> (suppose I dd an iso onto a usb stick to get into run-from-ram territory)
00:38 <shad0> I guess now I'm asking less about run from ram, and more about "run-from-ram with persisted config/changes"
00:38 <TemptorSent> shad0: It's pretty flexible about where you store your data, but I haven't gotten into the guts of how it restores the lbus yet. Right now I'm hacking my way through mkinifs.
00:38 <shad0> ahh
00:39 <TemptorSent> shad0: You can pass a path or url at the kernel prompt to load overlays from wherever.
00:39 <shad0> I'm guessing I may eventually have to do the same. in the short term, I don't mind installing to disk, in the long term it would be nice to be able to run-from-ram off of a usb stick, with lbu's saved back to some folder/partition on that same usb stick. then backing up the system would be a matter of dd'ing all the partitions
00:40 <TemptorSent> shad0: That should be functional now, I just haven't gotten into the details of lbu itself yet.
00:40 <shad0> that's nice, I just wish it was more streamlined than that :)
00:40 <TemptorSent> shad0: Working on it :)
00:41 <shad0> right... I imagine I could make it work, just wondered if it was documented and/or easily supported by existing tooling. from what little I've found online, even going with custom disk partitioning seems to imply having to throw out or heavily modify setup-alpine in order to play nice
00:42 <shad0> sorry, I'm spoiled ;-)
00:42 <TemptorSent> shad0: lbu should jsut do the right thing.
00:42 <shad0> I get that, but I don't understand what that is
00:42 <TemptorSent> shad0: Yeah, working on build tool that should handle all that.
00:43 <shad0> ahh
00:43 <TemptorSent> "Alpine Local Backup Utility"
00:43 <TemptorSent> Docs on the Alpine wiki look usable for it :)
00:43 <shad0> sorry... "I get the idea of the general process, and the goal, but I don't understand the intricacies of how it works or where I could find documentation on how to either learn about and go with the implied flow, or massage said tooling to serve my own selfish desires"
00:44 <shad0> the docs feel a bit surface level to me.
00:44 <TemptorSent> shad0: Yeah, I've been finding more undocumented than documented and donig a lot of UTSL.
00:45 <TemptorSent> shad0: Writing good documentation is often harder than writing the code for the software your documenting!
00:45 <shad0> for example, how can I either set up my own disk partitioning via answer file, or set up the system ahead of time so that either setup-alpine or setup-disks configures the disks without borking anything else up? the closest I've found is having to run setup disks manually, and tell setup-alpine to ignore that step.
00:45 <shad0> but even there, does that mean I also have to run setup-bootable manually to get the disk bootable?
00:45 <shad0> I know, I know...
00:45 <shad0> UTSL?
00:45 <TemptorSent> shad0: Yeah, currently that whole infrastruture is a mess for anythign other than defaults.
00:46 <TemptorSent> Use The Source, Luke :)
00:46 <shad0> I kinda guessed that. I should probably just hush and dig in :)
00:46 <shad0> ahh
00:46 <shad0> I really like the concepts I've read so far about alpine linux, and the size of it
00:46 <TemptorSent> I'm in the middle of pretty much rebuilding the image/system building infrastructure entirely.
00:47 <shad0> oof.
00:47 <shad0> and here I come being all demanding.
00:47 <shad0> well, thank you in advance/middle-of all of your hard work
00:47 <TemptorSent> See branch at https://github.com/TemptorSent/aports/tree/mkimage-refactor-scripts/scripts/mkimage
00:47 <shad0> I'll try to look it over in the next few days
00:48 <TemptorSent> shad0: I thing you just volunteered to help, right? ;)
00:48 <TemptorSent> er think
00:48 <shad0> in the meantime I'll probably see how painful it is to get running on an nvme disk. as of 12-15 months ago, it sounded like it required adding the nvme ko into the initfs
00:48 <shad0> hehe if I get hooked enough, sure
00:48 <TemptorSent> Anyway, I haven't pushed any of the mkinitfs stuff yet as I'm just now working on the surgery to integrate the existing code first, then recombobulate into something sane.
00:49 <shad0> makes sense
00:50 <TemptorSent> shad0: Will be adding the filesystems as plugins and allowing definitions of FS layouts in profiles as I get time.
00:50 <shad0> and all still via bash scripts?
00:50 <shad0> if so, that's badass. I usually chicken out on things that "complex" and grab python or ruby.
00:50 <TemptorSent> shad0: Right now, I'm working on getting it to build initramfses that include only what's necessary for that application and not a huge amount of useless crap.
00:50 <TemptorSent> Yeah, it's all bash.
00:51 <TemptorSent> er, ash,
00:51 <TemptorSent> no b :)
00:51 <shad0> ah
00:51 <TemptorSent> So no arrays either.
00:51 <shad0> oof
00:52 <TemptorSent> Mostly POSIXly correct in fact, with a couple cheaters available like ${var//regex/sub}
00:52 <shad0> I'm sure that complicates things a fair bit for trying to use env vars and config files to support more advanced partitioning schemes
00:52 <TemptorSent> shad0: Nah, it's actually quite easy to support stuff like that - the layout already follows FS conventions.
00:53 <shad0> oh, that's good.
00:53 <shad0> I'm gonna run now, but thank you for your responses. my apologies for being "demanding" about features/functionality/docs, thanks again for your work
00:53 <TemptorSent> shad0: All you need to do is translate the requested partition into whatever flavor mkfs you need.
00:54 <shad0> are you using parted for setting up the partitions?
00:54 <TemptorSent> shad0: No problem -- I just dug in because I need it to work for me to distribute to lights-out applications.
00:55 <shad0> that's my goal application, but my server pool is single digits and my boss is only a dick to other people, not me ;-)
00:55 <TemptorSent> shad0: Take your pick, everythign is sufficiently modular that you can use whichever is appropriate.
00:56 <shad0> given the lack of architectural foresight I have to deal with at the 9-5, even that fairly "basic" level of architectural vision is refreshing
00:56 <TemptorSent> shad0: Basically, you write a plugin that takes an input of partitions to create and spits out commands in your flavor partition editor of choice.
00:57 <TemptorSent> shad0: Yeah, I try to actually make things work, not just temporarily.
00:57 <shad0> our favorite game is "kick the can down the road, just a little bit longer..."
00:57 <shad0> going on 10 years of playing that game.
00:58 <TemptorSent> shad0: My branch currently suffers from having code sourced from at least three different utilities in addition to a lot of scratch code.
00:58 <shad0> that sounds like a bit of a tangle
00:58 <TemptorSent> shad0: Yeah, been there, done that, doesn't often end well.
00:58 <shad0> or at least, it could be
00:58 <shad0> they haven't learned yet. keep scraping by on luck and whipping peoples backs
00:58 <TemptorSent> shad0: Yeah, I thorougly refactored all of the above and have it almost sane at this pont.
00:58 <TemptorSent> point.
00:59 <shad0> and a whole lot of "this is the most critical item for the next 5 minutes"
00:59 <shad0> dang, nice
00:59 <^7heo> moin
00:59 <^7heo> nacht, auch
00:59 <TemptorSent> shad0: Righ now, literally everythign but the outermost layer of the command processing and one loop is a plugin or in a utility file.
01:00 <shad0> excellent
01:00 <TemptorSent> ^7heo: 'evening.
01:00 <^7heo> :)
01:01 <TemptorSent> shad0: I'm also working on documenting every utility function with it's usage and have gotten through adding at least reasonable error checking to 80%.
01:01 <^7heo> It's actually 2 am ;)
01:01 <shad0> overachiever ;-)
01:01 <^7heo> and I'm in my bed
01:01 <TemptorSent> shad0: Self preservation -- it was impossible to debug before!
01:02 <TemptorSent> ^7heo: I've been doing a lot of those lately.
01:02 <shad0> I feel you there. we've got more than a few 1k+ LOC functions at work.
01:03 <TemptorSent> shad0: Yeah, of which 200 should probably be debugging code at that point!
01:03 <shad0> eff that. make it like 10 100 loc functions
01:03 <shad0> or even better.
01:03 <shad0> it's one of those sad things where people debug the wrong things, code in all the wrong anti-patterns, etc.
01:04 <shad0> and if you try to suggest better ways to do things, they look at you like you have 3 heads.
01:04 <TemptorSent> shad0: Oh, 1k LOC functions that don't actually need to be one function. ick.
01:04 <shad0> "what's wrong with storing 200,000 device- and date-specific data files in one folder?"
01:05 <TemptorSent> shad0: I'm so sick about hearing about all these 'patterns' -- that's nice, how about learning to actually UNDERSTAND the code people?
01:05 <shad0> sorry, I think I missed a zero there. we've had a million files in one folder at times
01:05 <shad0> I'd take either one. at least if they thought about patterns, it would imply thinking about something other than the nose in front of their face.
01:05 <TemptorSent> shad0: Sounds like you need an object store and a database, not a filesystem!
01:06 <shad0> these are log files. and most of them are date oriented. which begs the question, why has no one ever considered a yyyy/mm/dd/ hierarchy?
01:06 <shad0> that's like maybe 1-2 hours more work up front. to save countless hours of plain old scrolling for years to come
01:06 <TemptorSent> shad0: Or a julian date perhaps?
01:06 <TemptorSent> shad0: Or any number of sane solutions.
01:06 <shad0> yeah
01:07 <shad0> instead we can actually self-DOS b/c our OS(not linux) chokes on folders with tons of files
01:07 <TemptorSent> *lol* Job security?
01:07 <shad0> we can choke processing queues if one device spams the logs, b/c why would we ever need round-robin?
01:08 <shad0> haha I wish. just lack of concern for quality/real(tm)-engineering
01:08 <TemptorSent> shad0: Why even write logs to files at that point? There are log-oriented database systems for exactly that purpose.
01:08 <dalias> shad0, windows?
01:09 <shad0> it's remote devices writing logs that can be uploaded for central processing later.
01:09 <dalias> as late as xp, maybe later, windows got unusably slow with ~64k files in top-level temp dir
01:09 <shad0> with spotty connections at times
01:09 <shad0> dalias, yep, and we've had folders on 600-800 mhz machines with 6-7 digits worth of files.
01:09 <shad0> at that point, I've had the pleasure of discovering that chkdsk can take 20 minutes
01:09 <TemptorSent> shad0: Right, read them directly into a DB, do not pass go, do not waste 2,000,000 inodes.
01:10 <shad0> TemptorSent, well, to be fair, I doubt they had many (cheap) options like that for embedded solutions 10 years ago
01:10 <shad0> which is why something as simple but effective as creating a couple layers of folders seems asinine to overlook.
01:10 <TemptorSent> shad0: I was doing it 20 years ago on a Pentium-II
01:11 <shad0> I stand corrected, then. my embedded work that long ago was "big"-iron, alphas and such
01:11 <TemptorSent> shad0: It was almost a nobrainer then even.
01:12 <shad0> well, never let it be said that this place takes the easy and technically sound way out. immediately easy, yes
01:12 <TemptorSent> shad0: Yeah, I was working with some of the early 21264 stuff back in the day, damn 64 bit memory space was nice!
01:12 <shad0> they have apps where you have to recompile it to point it to a different server. HELLOOOOOO, config files, anyone?
01:12 <TemptorSent> shad0: PostgreSQL + sed/awk/grep.
01:12 <shad0> I never had to worry about it, thankfully.
01:13 <shad0> (64 bit vs not)
01:13 <shad0> alright, I'm really off now. my exercise equipment is calling my name. you all have a good night :)
01:14 <TemptorSent> shad0: Yeah, I've been at both ends of the spectrum -- both very small embedded environments (256BYTES of ram) all the way up to making stuff work for big clusters.
01:14 <TemptorSent> shad0: Alright, take care.
01:17 <TemptorSent> ^7heo : Insomnia, or your prefered time to get something done?
01:23 <^7heo> TemptorSent: yes
01:26 <^7heo> I'm currently thinking about re-setting up my rpi with alpine
01:26 <^7heo> the only thing is
01:27 gerard joined
01:27 <^7heo> read only root or not
01:28 <gerard> hiya, dump question. i've installed postgresql on my virtualbox, and i cannot login from my host via psql. i can ping it, but cannot log in. what do i have to change?
01:28 Emperor_Earth joined
01:29 <^7heo> gerard: this is not #postgresql
01:30 <^7heo> gerard: but, what did you try? :)
01:31 <TemptorSent> gerard: Almost certainly you need to edit your $PGDATA/pg_hba.conf
01:31 <^7heo> not if it's local no
01:31 <^7heo> hence my question
01:32 <gerard> i have local all all 0.0.0.0/0 trust
01:32 <TemptorSent> ^7heo: Go with the RO root and overlay, less wear and tear on the SD if you use a USB stick for the rest.
01:32 <^7heo> (i.e login via psql via ssh)
01:32 <TemptorSent> ^7heo: Right, if it's local.
01:33 <^7heo> TemptorSent: yeaah that's what I did so far... but it's tiresome to use
01:33 <TemptorSent> ^7heo: Whyfore?
01:33 <^7heo> gerard: if you login via psql via ssh (locally), does it work&
01:34 <^7heo> ?
01:34 <gerard> yes. it works.
01:34 <^7heo> TemptorSent: because then you have to manually save any change
01:34 <TemptorSent> gerard: You need a host entry to allow connectoins remotely.
01:34 <^7heo> gerard: yeah then hba
01:34 <TemptorSent> ^7heo: Overlay-FS
01:34 <^7heo> gerard: as TemptorSent said
01:35 <^7heo> TemptorSent: still need manual operation with lbu, or?
01:36 <TemptorSent> ^7heo: Not if you don't want to generate overlays -- you can just overlay a persistant, writable FS over your RO root. All you need to LBU is the config to get your overlay mounted.
01:36 <TemptorSent> ^7heo: The other option is automating LBU I suppose.
01:37 <TemptorSent> ^7heo: I just mount the root RO and mount my live system around it.
01:37 <^7heo> yeah whichever. what overlay would you use?
01:37 <TemptorSent> ^7heo: Whatever you need :)
01:37 <^7heo> oe that *works*
01:37 <^7heo> one*
01:38 <TemptorSent> ^7heo: That's why I'm adding the overlay generation to mkimage -- make life easier.
01:38 <^7heo> AFAIK there's not a single unionfs on linux that works
01:39 <TemptorSent> ^7heo: You can start with no overlay, boot up in normal RO root, add the overlay mounts, lbu that and write it to your boot media, and go.
01:39 <^7heo> again, with what software?
01:40 <^7heo> bare linux does not do that, does it?
01:40 <TemptorSent> OverlayFS.
01:40 <TemptorSent> Yup :)
01:41 <^7heo> is overlayfs the thing from docker?
01:46 <gerard> i had to change iptables rules as well ( https://www.cyberciti.biz/tips/postgres-allow-remote-access-tcp-connection.html )
01:46 <^7heo> yeah again, this has nothing to do with #alpine-linux
01:46 <^7heo> but more with #postgresql and ##networking
01:46 <TemptorSent> ^7heo: Docker uses it I believe, but it's in the mainline kernel and has been for a while now
01:47 <^7heo> TemptorSent: I thought it has been contributed in by docker
01:48 <TemptorSent> ^7heo: Possibly, although I believe that was a revision they contributed to support their needs better.
01:48 <^7heo> ok
01:50 <TemptorSent> ^7heo: From what I can see, the original merge was back in 3.18 or so, with major changes in 4.x
01:51 <TemptorSent> ^7heo: It's already being used by alpine, just not for quite the same purpose.
01:52 <^7heo> from what I know, there have been two "versions" of it
01:52 <^7heo> the first one being a total fiasco
01:53 <TemptorSent> ^7heo: Yeah, more or less -- the first version was never intended to be used for the purposes it quickly got bent to, which was most of the problem I believe.
01:54 <TemptorSent> ^7heo: Your other option is just to mout right over the top of a skeleton root and ignore what's behind it.
01:55 <^7heo> or confine my interactions to /home
01:55 <^7heo> and expect the rest to be lbu-managed
01:56 <TemptorSent> ^7heo: Yeah, set up LBU to run every couple hours or something to checkpoint, as well as at shutdown.
01:57 <^7heo> I was thinking about hooking it up to sudo
01:57 <^7heo> or something
01:58 <TemptorSent> Setup incron to run on modificatons to anything in /etc.
02:50 andor2007 joined
02:54 s33se_ joined
03:00 minimalism joined
04:04 mguentner joined
04:12 MuffinMedic joined
04:41 ahrs joined
04:43 mguentner joined
05:29 blueness joined
06:11 fabled joined
06:51 slukin joined
07:28 nanohest joined
08:00 nindustries joined
08:00 <nindustries> Hi, how do I run postfix in foreground?
08:00 <nindustries> mode*
08:03 <_ikke_> I don't think postfix runs in the foreground
08:03 <nindustries> grmpf
08:04 <_ikke_> postfix requires many processes
08:05 <nindustries> The darn master process has a -w for foreground, but it still exits prematurely --"
08:10 gogoprog joined
08:46 t0mmy joined
08:52 user__ joined
08:54 stwa joined
08:54 <user__> is it normal, that alpine doesnt "fully" shut down a pc? it gives the last message, that everything is stopped, i heard the components shut down, but the pc is still turned on. i have also noticed this on virtualbox. is there a fix?
08:57 <fabled> user__, what command you used? 'shutdown' works for me. another reason might be also related to kernel missing some driver...
08:57 <user__> i used "halt"
08:58 <fabled> that's it then
08:58 <user__> my vm says that shutdown does not exist
08:58 <fabled> "halt" is intended to just stop everything, but not poweroff
08:58 <fabled> try "poweroff"
08:58 <user__> yep its poweroff
08:58 <fabled> busybox ships poweroff so that's always present
08:58 <user__> i was so much used to "halt"...
08:58 <user__> thanks
09:03 <_ikke_> user__: halt has the -p (poweroff) parameter
09:04 <user__> _ikke_: not in busybox, only d,n,f
09:04 fekepp joined
09:15 czart__ joined
09:20 t0mmy joined
09:24 <ScrumpyJack> morning climbers. hapyp monday
09:25 <ScrumpyJack> happy even
09:37 KSD joined
09:38 <KSD> Hello every one !
09:53 royger joined
10:16 <ncopa> hi
10:24 nabaz45 joined
10:32 nindustries joined
10:54 blueness joined
11:03 <iron_houzi> When wget'ing a dropbox URL from alpine, the file is only ~220K when it should be more like ~450M .. I've installed openssl .. does anybody know what could be causing this or how to troubleshoot?
11:03 <iron_houzi> I'm on 3.5
11:08 <iron_houzi> When running `update-ca-certificates` I get: WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping -- is there any need to be concerned about that?
11:09 <yGweSm1OzVHe> crl is snakeoil anyway, ct is the new god ;)
11:10 <yGweSm1OzVHe> hmmm, gotta check if ct is infact also useful for revocations
11:13 <iron_houzi> yGweSm1OzVHe: is your comment in response to my question?
11:15 <yGweSm1OzVHe> yes
11:16 <yGweSm1OzVHe> crl is a broken mechanism, and if you have no special threat model i think you can ignore this warning
11:16 <fabled> iron_houzi, it's ok, the ca-certificates.crt is the generated one
11:16 <fabled> should probably silence the warning on that name...
11:26 black_rez joined
11:46 <iron_houzi> yGweSm1OzVHe: Is there another way to update or manage ca certs?
11:51 <yGweSm1OzVHe> crl is only for revocation, not updating/managing. and for that it is also a SoP, through DoSing you can force a user to use a revoked cert.
11:51 <yGweSm1OzVHe> s/SoP/SoF/
11:52 <yGweSm1OzVHe> pki/ca-s are broken anyway irrespective of crls
11:53 <iron_houzi> fabled: Do you think that the wget file output corruption could be caused by mismanaged SSL?
11:53 <iron_houzi> yGweSm1OzVHe: ^^
11:54 <yGweSm1OzVHe> nope
11:54 <fabled> iron_houzi, does not sound likely
11:54 <iron_houzi> https://www.dropbox.com/s/xuceam8n27reoey/NDVISR_diff_20160520_20160719.tif
11:54 <yGweSm1OzVHe> if the cert is wrong, you cannot even start, and it will definitely not stop halfway dotnloading
11:54 <iron_houzi> could you guys please try to download it? It should be 450M not 220k
11:55 <yGweSm1OzVHe> i'd look more into network problems and check if the file on dropbox really contains the full file
11:56 <yGweSm1OzVHe> same size here
11:56 <iron_houzi> I tried doing it with a bare alpine:latest docker image which doesn't work .. Doing it in another ubuntu container on the same cluster makes it work ..
11:56 <iron_houzi> yGweSm1OzVHe: You get ~450M ?
11:56 <yGweSm1OzVHe> it seems truncated
11:57 <iron_houzi> yGweSm1OzVHe: .. it works on any other distro ..
11:57 <fabled> works here too
11:57 <fabled> on alpine edge
11:57 <yGweSm1OzVHe> i'm alos on alpine edge
11:57 <yGweSm1OzVHe> looks like network issues
11:57 <fabled> network issue? some firewall or IDS system dropping the connection?
11:58 <iron_houzi> OK, thanks for the help .. I'll continue the digging
12:14 <avih> anyone on edge updated recenly and got a new openrc? does the system boot ok (hdd install) after this update for you?
12:19 <iron_houzi> OK .. this is funny .. there's a wget binary on alpine .. but when explicitly installing `apk --no-cache add ca-certificates wget && update-ca-certificates` .. wget works as intended .. very strange..
12:21 Kruppt joined
12:21 <iron_houzi> .. I mean wget binary exists prior to the apk add command but fails as explained further above .. but when explicitly installing wget with the certs, the file gets correctly downloaded..
12:22 <yGweSm1OzVHe> busybox wget vs full wget
12:25 <iron_houzi> yGweSm1OzVHe: ahhh .. that's news to me .. thanks!
12:30 farosas joined
12:56 stwa joined
13:02 Skele joined
13:07 farosas joined
13:12 <ScrumpyJack> anything wrong with dl-6.a.o or is it just me?
13:15 <_ikke_> Looks down for me as well
13:15 stwa joined
13:20 tmh1999 joined
13:45 alacerda joined
13:56 ogres joined
14:14 coreping left
14:16 coreping joined
14:21 vifino joined
14:24 cyborg-one joined
14:29 MDrights joined
14:50 fekepp joined
14:51 slowpak joined
15:06 fabled joined
15:17 blueness joined
15:33 minimalism joined
15:51 vidr joined
15:53 <clandmeter> We are experiencing issues with our mirrors, we are trying to get them in sync again.
15:54 <Diftraku> clandmeter: I use the same rsync commandline as you do for syncing our internal openwrt repo to our remote end :P
15:57 <Klowner> looks like ssl issues too?
15:58 <Klowner> ah, dns causing the cn issue
16:01 Unic0arn joined
16:03 <clandmeter> Diftraku, its not an rsync issue
16:06 <avih> clandmeter: do you think this issue doesn't affect most users https://bugs.alpinelinux.org/issues/7042 ? i marked it as high priority since i assumed it'd affect many, but considering the lack of and further confirmations, i'm guessing i'm wrong? would you mind updating edge and let me know if you were affected or not?
16:10 orbiter joined
16:40 BitL0G1c joined
17:03 volleyper joined
17:29 ams__ joined
17:41 BitL0G1c joined
17:45 tmh1999 joined
17:46 Somasis joined
17:46 Somasis joined
17:58 chapui_s joined
18:11 farosas joined
18:18 Berra joined
18:22 pmcg joined
18:37 slowpak joined
18:39 gopar joined
18:42 cyborg-one joined
18:50 fabled_ joined
18:59 dlaube joined
19:27 <Madgod> mhm >.> whenever I use uname -p in a docker container using the alpine image i get unknown back >.>
19:28 farosas joined
19:36 mouthbreather joined
19:36 <TemptorSent> Madgod: Same result even on a standard install, probably BB.
19:41 Emperor_Earth joined
19:43 <TemptorSent> Madgod: Confirmed - busybox has processor hard-coded to 'unknown'.
19:43 <Madgod> mhm that's ugly >.>
19:45 <TemptorSent> Agreed.
19:47 <TemptorSent> I believe it should return the same as machine unless there is actually some valid value set.
19:49 <TemptorSent> It appears a bit TOO much space-savings was put into uname in busybox.
19:50 lesion joined
20:02 <TemptorSent> Wow, uname looks generally broken in several ways... What are you using the output of uname -p in Madgod?
20:34 irclogger_com joined
20:34 Topic for
20:35 ahrs joined
20:40 mitemite joined
20:42 Latrina joined
20:44 is_null joined
20:53 mitemite joined
21:18 linuxfreakus joined
21:19 <linuxfreakus> anyone know why an apk listed in the index would be missing from official download mirror(s)?
21:19 <linuxfreakus> for example py2-requests-2.13.0-r0.apk
21:19 ericnoan joined
21:20 <linuxfreakus> i thought maybe i had not used the right command or something, but I looked at the index in a browser and don’t actually see the file
21:21 <TemptorSent> The mirrors experienced a bad sync this morning, which you may still be seeign the after-effects of.
21:21 <linuxfreakus> ah hah
21:21 <linuxfreakus> that might explain it
21:21 <linuxfreakus> indeed
21:22 <linuxfreakus> i found a mirror in germany that does have it
21:22 <TemptorSent> If it persists, try switching mirrors and running apk --update to hopefully clear it.
21:22 <TemptorSent> Good deal. Hopefully the rest prop soon.
21:22 <linuxfreakus> but i was wondering if maybe it was intentionally removed for a security reason or something
21:22 <linuxfreakus> ok
21:22 <linuxfreakus> thanks!
21:25 <TemptorSent> Nope, all the mirrors got synced with a missing arch in the delete I believe from a revision of abuild, which wiped everything from the mirrors essentially, and required a full redist.
21:25 andypost joined
21:25 <TemptorSent> In other words, some of them could take a while to catch up :)
21:28 stwa_ joined
21:53 avih joined
21:53 orbiter joined
21:55 atomi joined
22:08 grugly joined
22:08 zhasha joined
22:13 lilleman joined
22:27 gopar joined
22:38 meena joined
23:00 davidmichaelkarr joined
23:00 wycats joined
23:00 Latrina joined
23:07 grayhemp joined
23:19 gopar joined
23:26 gopar joined
23:44 minimalism joined
23:46 dlaube joined
23:47 Latrina left