2020-08-09T02:29:28 #kisslinux <muevoid> Hello, I am trying to get pulseaudio working with flatpak however flatpak still does not have sound and says cannot find pulse am I doing something wrong?
2020-08-09T02:30:26 #kisslinux <Himmalerin> did you start it with `pulseaudio -D` first?
2020-08-09T02:30:46 #kisslinux <muevoid> Yes I did
2020-08-09T02:35:57 #kisslinux <muevoid> Figured it out was to do with pulse server not being set
2020-08-09T05:21:00 #kisslinux <konimex> dilynm: I can't reproduce your problem
2020-08-09T05:28:03 #kisslinux <aosync> Hi
2020-08-09T06:55:44 #kisslinux <dylanaraps> o/
2020-08-09T08:32:19 #kisslinux <r3dux> *
2020-08-09T08:34:14 #kisslinux <r3dux> -h
2020-08-09T08:36:17 #kisslinux * r3dux hello
2020-08-09T08:50:39 #kisslinux <r3dux> Pg around with birch... so far I am really liking it. Thank you Dylan.
2020-08-09T08:59:45 #kisslinux <dylanaraps> No problem
2020-08-09T08:59:46 #kisslinux <dylanaraps> :)
2020-08-09T09:00:07 #kisslinux <dylanaraps> Oh yeah, I've found a solution to this issue: https://github.com/kisslinux/repo/issues/209
2020-08-09T09:00:14 #kisslinux <dylanaraps> Please leave yourr thoughts everyone
2020-08-09T09:00:18 #kisslinux <dylanaraps> your*
2020-08-09T09:03:01 #kisslinux <j`ey> dylanaraps: yes that makes way more sense than hacking this in the package manager
2020-08-09T09:03:30 #kisslinux <dylanaraps> Yeah
2020-08-09T09:03:57 #kisslinux <j`ey> this is a repo organisation issue, not a package manager one
2020-08-09T09:10:27 #kisslinux <dylanaraps> Here's an example: https://github.com/dylanaraps/kiss-submodule-links
2020-08-09T09:11:50 #kisslinux <j`ey> easy
2020-08-09T09:12:45 #kisslinux <dylanaraps> Yup. Package manager also supports updating submodules during 'kiss update'
2020-08-09T09:13:32 #kisslinux <dylanaraps> Though I wonder if this should be disabled/configurable.
2020-08-09T09:14:36 #kisslinux <dylanaraps> ie, should the package manager update submodules or should it be left to the repository owner (can it be left to the repository owner(?)).
2020-08-09T09:15:00 #kisslinux <dylanaraps> The former is the current behavior without my proposed solution basically. (same outcome)
2020-08-09T09:15:31 #kisslinux <dylanaraps> BUT.. It'd be nice to let repository owners /pin/ their packages to a "known good" instance of the repositories.
2020-08-09T09:16:53 #kisslinux <dylanaraps> Actually, we should be good. Ignore me. :P
2020-08-09T09:16:58 #kisslinux <dylanaraps> > Update the registered submodules to match what the superproject expects by cloning missing submodules, fetching missing commits in submodules and updating the working tree of the submodules.
2020-08-09T09:17:11 #kisslinux <dylanaraps> > If --recursive is specified, this command will recurse into the registered submodules, and update any nested submodules within.
2020-08-09T09:17:19 #kisslinux <dylanaraps> > This option is only valid for the update command. Initialize all submodules for which "git submodule init" has not been called so far before updating.
2020-08-09T09:17:32 #kisslinux <dylanaraps> The package manager calls: git submodule update --init --recursive
2020-08-09T09:17:39 #kisslinux <dylanaraps> Above is documentation for each part of it.
2020-08-09T09:18:21 #kisslinux <j`ey> yah, doesnt actually 'update' it
2020-08-09T09:19:18 #kisslinux <dylanaraps> Hm. konimex makes a good point though: > Won't the repository owner lose advantage of the current model if git-submodule is used if in the end they must update manually?
2020-08-09T09:22:23 #kisslinux <j`ey> if you want to use one of those forks... you have to put the repo whre they expect it
2020-08-09T09:22:32 #kisslinux <j`ey> doesnt feel like a big deal
2020-08-09T09:22:50 #kisslinux <j`ey> or just add a symlink there
2020-08-09T09:24:45 #kisslinux <dylanaraps> Well, submodules would make this entirely transparent to the user. They wouldn't need to do a thing.
2020-08-09T09:25:08 #kisslinux <dylanaraps> It also makes "dependence" /explicit/ rather than implicit.
2020-08-09T09:25:41 #kisslinux <j`ey> right, just saying that if you wanted to do it the old way, and and keep the advantage of not updating it manually, you can do
2020-08-09T09:25:57 #kisslinux <dylanaraps> Another benefit is that you can lock the submodule to a specific commit (or even roll it back) independently (no reliance on /var/db/kiss/repo)
2020-08-09T09:26:06 #kisslinux <j`ey> this change doesnt affect the old way, if you clone the repo to the old place still
2020-08-09T09:26:17 #kisslinux <dylanaraps> Yes
2020-08-09T09:26:32 #kisslinux <dylanaraps> Though repositories will likely update to using submodules
2020-08-09T09:26:45 #kisslinux <dylanaraps> Old behavior is still there for those who want it, yeah
2020-08-09T09:27:51 #kisslinux <j`ey> I dont think it makes sense for kiss to update submodules
2020-08-09T09:27:56 #kisslinux <j`ey> since that could break things
2020-08-09T09:30:59 #kisslinux <dylanaraps> How so?
2020-08-09T09:31:46 #kisslinux <j`ey> well say an update to version X now needs new build configs or whatever
2020-08-09T09:32:19 #kisslinux <j`ey> so the sources etc are symlinked, but the user has a custom build file, then it will try to update, but fail to build
2020-08-09T09:32:28 #kisslinux <konimex> I don't really know how submodules in files work (since iirc I works on directories)
2020-08-09T09:32:48 #kisslinux <konimex> whoops, mistyped before i've even done
2020-08-09T09:33:17 #kisslinux <konimex> I don't really know how submodules in files work (since iirc I only know that it works on directories), but won't updating the submodules require new commits?
2020-08-09T09:33:36 #kisslinux <j`ey> oh yeah, that too
2020-08-09T09:33:38 #kisslinux <dylanaraps> konimex: If a user sets: git config branch.master.mergeOptions --recurse-submodules
2020-08-09T09:33:46 #kisslinux <dylanaraps> a git pull will update the submodule from its origin too
2020-08-09T09:34:09 #kisslinux <dylanaraps> This could also be done automatically by the package manager.
2020-08-09T09:34:15 #kisslinux <konimex> exactly, then won't the repo be "dirty"?
2020-08-09T09:34:26 #kisslinux <konimex> since we've done changes to the submodule
2020-08-09T09:34:41 #kisslinux <dylanaraps> Let me do some testing
2020-08-09T09:35:23 #kisslinux <j`ey> I think kiss should only make sure the submodules are up to date with what the repo has, not update them to anything than what they expect
2020-08-09T09:35:36 #kisslinux <dylanaraps> This is what it currently does
2020-08-09T09:36:18 #kisslinux <dylanaraps> The issue then is that the repository owner must update submodules manually (unless automated one each push(?))
2020-08-09T09:36:34 #kisslinux <j`ey> I dont think that's such a big deal.. is it?
2020-08-09T09:36:54 #kisslinux <dylanaraps> I'm not sure
2020-08-09T09:36:56 #kisslinux <j`ey> maybe if kiss got tons more updates / packages? But community is where most of the packages seem to end up
2020-08-09T09:37:22 #kisslinux <konimex> yeah but community is officially "unsupported" directly by dylan so community doesn't really matter in this case
2020-08-09T09:37:41 #kisslinux <konimex> we're talking about the main repo here, of course
2020-08-09T09:37:49 #kisslinux <dylanaraps> Yeah
2020-08-09T09:38:09 #kisslinux <j`ey> I was just using it to say that most of the forks are probably going to make changes to the core repo
2020-08-09T09:38:18 #kisslinux <j`ey> and updating that manually might not be a big deal
2020-08-09T09:38:59 #kisslinux <konimex> man not sure about "not a big deal" there from my perspective
2020-08-09T09:39:40 #kisslinux <dylanaraps> ^
2020-08-09T09:41:00 #kisslinux <j`ey> but you can still do the old way with it checked out in /var etc
2020-08-09T09:41:10 #kisslinux <j`ey> it's just that the chroot tarballs wont have that
2020-08-09T09:41:19 #kisslinux <dylanaraps> Exactly
2020-08-09T09:41:25 #kisslinux <dylanaraps> So it can't be relied on
2020-08-09T09:42:44 #kisslinux <j`ey> the forks will usually have some readme though wont they?
2020-08-09T09:42:45 #kisslinux <konimex> we can make use of relative paths, but then kiss-repo and it's symlinked forks must be placed in the same directory, and with the same name for the source repo (in case of kiss, "repo")
2020-08-09T09:43:36 #kisslinux <dylanaraps> The name can be changed with git
2020-08-09T09:43:57 #kisslinux <konimex> the name of the repo or the symlink?
2020-08-09T09:44:18 #kisslinux <dylanaraps> The repo
2020-08-09T09:44:22 #kisslinux <dylanaraps> "repo" in this case
2020-08-09T09:45:29 #kisslinux <konimex> unfortunately, it will break the "same name for the source repo" since in the fork's perspective it will expect ../repo, that's the caveat
2020-08-09T09:47:03 #kisslinux <dylanaraps> That can be changed too
2020-08-09T09:47:17 #kisslinux <dylanaraps> I misunderstood
2020-08-09T09:47:32 #kisslinux <dylanaraps> It can also live anywhere in the git repository.
2020-08-09T09:47:38 #kisslinux <dylanaraps> Could put it in .repos or something.
2020-08-09T09:56:11 #kisslinux <dylanaraps> konimex: "ignore = all" can be added to configuration to prevent dirtying the repository.
2020-08-09T09:57:10 #kisslinux <dylanaraps> Basically, with this set you can change which commit the submodule points to at will.
2020-08-09T09:57:23 #kisslinux <dylanaraps> Won't dirty anything.
2020-08-09T09:58:58 #kisslinux <dylanaraps> We could use this + have the package manager always pull from remote.
2020-08-09T09:59:07 #kisslinux <dylanaraps> Does this solve all issues?
2020-08-09T10:00:35 #kisslinux <j`ey> I guess if you dont want the update behaviour you can then fork the upstream repo, and use that as your submodule
2020-08-09T10:00:49 #kisslinux <konimex> hmmm... so a manual config? that's ugly I think, but a workable solution, I'll need a third opinion from a guy who *also* maintains "fork-type" repo
2020-08-09T10:00:59 #kisslinux <dylanaraps> Yeah
2020-08-09T10:01:03 #kisslinux <dylanaraps> Need to hear from others
2020-08-09T10:01:13 #kisslinux <dylanaraps> The package manager could also set this option fyi
2020-08-09T10:01:25 #kisslinux <dylanaraps> It could also "undo" our fast forward to master.
2020-08-09T10:01:35 #kisslinux * j`ey still prefers the kiss-doesnt-do-anything approach
2020-08-09T10:01:36 #kisslinux <dylanaraps> ie, no config changes needed. Would "undirty" on exit.
2020-08-09T10:01:57 #kisslinux <dylanaraps> j`ey: Issue then is how the submodule is updated.
2020-08-09T10:02:03 #kisslinux <dylanaraps> I would prefer that too.
2020-08-09T10:03:21 #kisslinux <dylanaraps> OK. So there's an option specifically for saying "submodule does not need to be tracked by parent": git config submodule.<name>.active false
2020-08-09T10:05:40 #kisslinux <j`ey> for a user to use one of these forks, they have to clone the fork repo
2020-08-09T10:06:08 #kisslinux <j`ey> is there an issue with the fork readme saying 'you should also check out the kiss core repo at <path>'?
2020-08-09T10:06:37 #kisslinux <dylanaraps> Yes
2020-08-09T10:06:48 #kisslinux <dylanaraps> This new behavior would be a regression
2020-08-09T10:07:03 #kisslinux <dylanaraps> Right now it's very easy
2020-08-09T10:07:10 #kisslinux <dylanaraps> The solution shouldn't make it hard
2020-08-09T10:07:50 #kisslinux <dylanaraps> Also, the change to the package manager would be the addition of a line or two
2020-08-09T10:07:54 #kisslinux <j`ey> I wouldn't consider a second clone hard
2020-08-09T10:08:18 #kisslinux <dylanaraps> Right now it's seamless
2020-08-09T10:08:47 #kisslinux <dylanaraps> This also enforces a standard location for repo if they have to clone it somewhere /outside/ of the fork.
2020-08-09T10:09:02 #kisslinux <dylanaraps> And this sub repository would still need to somehow be kept up-to-date.
2020-08-09T10:09:25 #kisslinux <dylanaraps> ie, the package manager would need to become aware of nested repositories anyway (and how to update them).
2020-08-09T10:09:46 #kisslinux <dylanaraps> Then we're basically just dealing with manual submodules. :P
2020-08-09T10:10:26 #kisslinux <j`ey> I was thinking both would be added to the KISS_PATH. A 'partial' fork, still wants the normal repo in it's path, but I guess a full fork doesnt
2020-08-09T10:10:26 #kisslinux <dylanaraps> Actually. The package manager already updates submodules from remote on pull.
2020-08-09T10:10:37 #kisslinux <dylanaraps> This requires no change to the package manager.
2020-08-09T10:11:02 #kisslinux <dylanaraps> j`ey: You're describing exactly what we have right now.
2020-08-09T10:11:33 #kisslinux <dylanaraps> The only change on my side would then be dropping the repository from the chroot and having them manually clone it to /var/db/kiss/repo
2020-08-09T10:11:55 #kisslinux <j`ey> that's what seems to make the most sense for me
2020-08-09T10:12:38 #kisslinux <dylanaraps> The main goal is to drop the hardcoded /var/db/kiss/repo. There's no reason it should exist.
2020-08-09T10:12:49 #kisslinux <dylanaraps> Users should be free to setup repositories however they like.
2020-08-09T10:13:10 #kisslinux <dylanaraps> This is already the case though forks must rely on it.
2020-08-09T10:13:21 #kisslinux <dylanaraps> I'm trying to fix this.
2020-08-09T10:14:30 #kisslinux <j`ey> what was wrong with the relative symlink approach?
2020-08-09T10:14:39 #kisslinux <dylanaraps> Whereby one can clone the fork and have it "just work" as the fork contains a shallow copy of the repository it is "layering" on top of.
2020-08-09T10:15:05 #kisslinux <j`ey> ok, relative symlink means git cloning two things
2020-08-09T10:15:14 #kisslinux <dylanaraps> j`ey: Relative to where? Also, this is what the submodules approach requires.
2020-08-09T10:15:26 #kisslinux <dylanaraps> ../../repo/core/zlib/version for example
2020-08-09T10:15:42 #kisslinux <dylanaraps> if zlib is in dylan-repo/zlib/version
2020-08-09T10:16:17 #kisslinux <j`ey> you can do relative symlinks with or without submodules, which is why I was thinking if you wanted it to auto update, you'd just clone it as a separate repo
2020-08-09T10:16:27 #kisslinux <j`ey> and then the usual git pull by kiss would update it
2020-08-09T10:16:39 #kisslinux <j`ey> if you wanted it at a fixed version, you'd use a submodule
2020-08-09T10:17:35 #kisslinux <dylanaraps> That then forces a directory structure /outside/ of the repositories
2020-08-09T10:18:05 #kisslinux <dylanaraps> It does remove the requirement for /var/db/kiss/repo though
2020-08-09T10:18:45 #kisslinux <j`ey> yeah it means you need the core repo and the fork repo to be in the same directory, I can't imagine a use case where that would cause issues?
2020-08-09T10:19:22 #kisslinux <dylanaraps> You may want to keep the official repositories in a system-wide location for example.
2020-08-09T10:19:30 #kisslinux <dylanaraps> Others may want to keep them entirely in their /home
2020-08-09T10:19:48 #kisslinux <dylanaraps> This would require either all system-wide or all in /home
2020-08-09T10:20:01 #kisslinux <dylanaraps> I'm trying to remove all restrictions
2020-08-09T10:21:16 #kisslinux <j`ey> with the submodule approach, you will have two copies of the kiss repo
2020-08-09T10:21:31 #kisslinux <j`ey> if you want one in the systemwide location
2020-08-09T10:21:59 #kisslinux <dylanaraps> Yes
2020-08-09T10:22:06 #kisslinux <j`ey> same with what I said
2020-08-09T10:22:08 #kisslinux <dylanaraps> The submodule copy would be shallow however
2020-08-09T10:33:56 #kisslinux <elgoogle> dylanaraps: what are the CNAME files in some of the git repos (wiki + website)? I've seen them in other people's repos too, mainy ones that are mirrors of actual sites.
2020-08-09T10:34:19 #kisslinux <elgoogle> but i don't know what their purpose is
2020-08-09T10:34:44 #kisslinux <elgoogle> i suppose i should have googled it
2020-08-09T10:35:32 #kisslinux <dylanaraps> They're for the custom domain
2020-08-09T10:37:35 #kisslinux <elgoogle> I see. are you using github pages?
2020-08-09T10:38:18 #kisslinux <dylanaraps> Yes
2020-08-09T10:38:28 #kisslinux <elgoogle> cool. makes sense then. thanks
2020-08-09T10:56:56 #kisslinux <dylanaraps> OK. Summed up exactly what needs to be done for this change to be made: https://github.com/kisslinux/repo/issues/209
2020-08-09T10:57:10 #kisslinux <dylanaraps> No changes to the package manager needed.
2020-08-09T10:57:51 #kisslinux <dylanaraps> One small manual step (if required) (not required when you are only pulling and not also pushing)
2020-08-09T10:59:37 #kisslinux <j`ey> in https://github.com/dylanaraps/kiss-submodule-links it links to repo @ f49aad4, are you saying that kiss will currently, on kiss u, update that to what master is?
2020-08-09T11:00:15 #kisslinux <dylanaraps> Yes
2020-08-09T11:00:27 #kisslinux <dylanaraps> This is already the behavior
2020-08-09T11:00:33 #kisslinux <dylanaraps> Has been for a while
2020-08-09T11:01:59 #kisslinux <dylanaraps> See: https://github.com/CarbsLinux/outsource
2020-08-09T11:02:10 #kisslinux <dylanaraps> Also: https://github.com/jedahan/kiss-universe
2020-08-09T11:02:20 #kisslinux <dylanaraps> People are already using submodules in this way for repositories.
2020-08-09T11:02:39 #kisslinux <j`ey> ok, I didn't realise that was the current behaviour, only just saw that it uses --remote
2020-08-09T11:03:04 #kisslinux <dylanaraps> Yeah
2020-08-09T11:03:41 #kisslinux <aosync> That's pretty nice
2020-08-09T11:03:41 #kisslinux <j`ey> ok, and users can (as I said before), just fork kiss-repo if they want a fixed version
2020-08-09T11:05:18 #kisslinux <dylanaraps> Yes
2020-08-09T11:05:24 #kisslinux <dylanaraps> This change requires no code
2020-08-09T11:05:30 #kisslinux <j`ey> that sounds reasonable to me
2020-08-09T11:06:03 #kisslinux <dylanaraps> Will give others time to also share their thoughts about it.
2020-08-09T11:06:16 #kisslinux <dylanaraps> I think I've solved all queries thus far though.
2020-08-09T11:06:53 #kisslinux <j`ey> you could also put: 2) Change symlinks to point to the subrepo
2020-08-09T11:07:53 #kisslinux <dylanaraps> Ah yes
2020-08-09T11:08:22 #kisslinux <dylanaraps> That's in the "See repo" link but I'll also add it to the issue.
2020-08-09T11:09:36 #kisslinux <j`ey> a 'how to fork kiss' or something might be a nice wiki page
2020-08-09T11:09:55 #kisslinux <j`ey> detailing some of the ways people have done it
2020-08-09T11:19:38 #kisslinux <aosync> I still have to contribute to the wiki page to add hummingbird init
2020-08-09T14:22:36 #kisslinux <redsith> hey guys, i cant get any fonts to be visible in qt apps. this a known bug?
2020-08-09T16:50:22 #kisslinux <illiliti> claudia02: i need your help
2020-08-09T16:50:29 #kisslinux <illiliti> plug joystick and send me output of this command: cat /sys/class/input/js*/device/uevent
2020-08-09T16:50:56 #kisslinux <claudia02> illiliti: let me try
2020-08-09T16:55:52 #kisslinux <claudia02> illiliti: theres no 'js' in input. Only 'input1-x'.
2020-08-09T16:56:10 #kisslinux <claudia02> I guess I have to rebuild the kernel first
2020-08-09T16:56:50 #kisslinux <claudia02> Should I try with udev-zero or eudev?
2020-08-09T16:57:34 #kisslinux <illiliti> no difference
2020-08-09T16:57:36 #kisslinux <illiliti> try this: cat /sys/class/input/*/device/uevent
2020-08-09T16:59:12 #kisslinux <claudia02> Here it is: https://termbin.com/99qk
2020-08-09T17:03:56 #kisslinux <illiliti> thanks
2020-08-09T17:04:44 #kisslinux <claudia02> no problemo
2020-08-09T17:27:34 #kisslinux <aosync> Could you recommend some other cool Linux/Unix related discussion channels?
2020-08-09T17:27:34 #kisslinux <aosync> I want to use IRC at its fullest
2020-08-09T18:09:08 #kisslinux <M4R10zM0113R> Is there some extra step to get amdgpu working or does it only work with radeon
2020-08-09T18:39:18 #kisslinux <claudia02> M4R10zM0113R: maybe this can help you: https://k1ss.org/wiki/kernel/firmware#3.2
2020-08-09T18:41:25 #kisslinux <M4R10zM0113R> That part is done, thank you. It's taken from gentoo's amdgpu wiki
2020-08-09T18:55:58 #kisslinux <M4R10zM0113R> I fixed it... I think?
2020-08-09T18:56:12 #kisslinux <M4R10zM0113R> Nope
2020-08-09T19:09:29 #kisslinux <M4R10zM0113R> I had to create /etc/X11/xorg.conf.d/amdgpu.conf to make it use that driver
2020-08-09T19:14:26 #kisslinux <M4R10zM0113R> This other problem concerns more, emacs doesn't wanna build
2020-08-09T19:39:28 #kisslinux <aosync> M4R10zM0113R: What's the error?
2020-08-09T19:41:31 #kisslinux <Arsi> Hello!
2020-08-09T19:45:24 #kisslinux <illiliti> dylanaraps: neovim fails to build. log - termbin.com/9b6x
2020-08-09T19:49:11 #kisslinux <M4R10zM0113R> aosync: http://sprunge.us/8TYXuB
2020-08-09T19:49:33 #kisslinux <M4R10zM0113R> It just segfaults
2020-08-09T19:51:57 #kisslinux <aosync> weird
2020-08-09T19:54:39 #kisslinux <M4R10zM0113R> Probably related to doing ”-O3 -march=native -mtune=native", but it didn't error like such before
2020-08-09T19:56:11 #kisslinux <aosync> Try to build an earlier version
2020-08-09T19:56:18 #kisslinux <aosync> of the package
2020-08-09T21:06:41 #kisslinux <j`ey> dylanaraps: "Regarding 'shfm' in the initrd, as reported yesterday:
2020-08-09T21:06:42 #kisslinux <j`ey> "
2020-08-09T21:06:57 #kisslinux <j`ey> dylanaraps: "It is so handy, that I have included it in the main filesystem, at /usr/sbin/shfm"