<aanderse>
so virtual host for "localhost" is constructed and listens on specified ip/port combo
<aanderse>
the "listen" variable defaults to port 80 if you have no ssl, port 443 if you have only ssl, and both 80+443 (creating separate virtual hosts, 1 for ssl, 1 for non, obviously) if you have the add ssl or force ssl option set
<aanderse>
the user is free to go in and specify ip/port combinations to listen on if the defaults do not work
<tilpner>
Is there any way to have my tests not perfectly formatted before I'm allowed to run them?
justanotheruser has joined #nixos-dev
<gchristensen>
on 20.03 I get a surprising amount of very brief lock-ups
<tilpner>
Should I back-port a new test if the module is broken on 20.03?
<worldofpeace>
tilpner: skipLint = true;
<tilpner>
Ahh, thank you! :)
<worldofpeace>
I believe that's in the docs ^
<tilpner>
skipLint does not appear in nixpkgs/doc
<tilpner>
It does in nixpkgs/nixos/doc
<worldofpeace>
tilpner: I don't think the nixos testing driver is documented in the nixpkgs manual?
<tilpner>
Hi! We'll know it was your DNS if you stop replying here
<worldofpeace>
yeah, this as much seems to be working
<tilpner>
You said you had concerns about going to FCP?
<worldofpeace>
Yeah, because I wasn't in the discussion I don't think you can FCP without my 🏁
<worldofpeace>
The first thing was:
<worldofpeace>
I wasn't clear on the timing that was agreed on,
<worldofpeace>
to be more predictable for committers and reduce the evaluations from 12 times a year to just once a year."
<worldofpeace>
In the RFC it said "That year is measured from January 1 to December 31 instead of using a rolling window over the last 12 months,
drakonis_ has joined #nixos-dev
<worldofpeace>
but what I was able to hear from qyliss was that it should happen right away
<worldofpeace>
I value it being predictable
<qyliss>
I think it should happen right away with the 2019 data
<qyliss>
Not a rolling range of the last year.
<tilpner>
Not for 2020, but anyone who hadn't committed during either of 2019 or 2020 would be notified
<qyliss>
Yeah.
<worldofpeace>
Ok, so going forward, what day week do I expect this operation/communication to occur?
<tilpner>
Ideally in January of each year, with "as soon as possible" this year
<worldofpeace>
Because I'm seeing there's a process, you notify, and I believe it was agreed to have a public issue that someone (undecided) was going to create. And then emails are sent out.
<worldofpeace>
And then from there some (undecided) person, or perhaps this is a task that could be shared between anyone who is an owner in NixOS, would remove them on a certain date. Is there a buffer between the time you say "hey, you're going to be removed"?
drakonis has joined #nixos-dev
<worldofpeace>
I get from this meeting there was an agreement on a notification on both email and a github issue. so that as much can be moved out from the Unresolved questions
<qyliss>
I think it should be a month.
<worldofpeace>
So a month of time to respond is in the "Removing an inactive nixpkgs committer" to the issue and email. Do we require them to make contribution?
<genesis>
worldofpeace : lot of jack client refuses to connect, Client name = qjackctl conflits with another running client (same with bristol or samplv1_jack )
<worldofpeace>
* correction. issue or email.
drakonis_ has quit [Read error: Connection reset by peer]
drakonis1 has joined #nixos-dev
<worldofpeace>
Is documentation going to be in the works for this RFC?
<tilpner>
It would belong in the same location as documentation about becoming a committer
<tilpner>
I agree there should be documentation beyond the RFC, but I don't know where it would live
<tilpner>
The nixpkgs manual?
<worldofpeace>
is that even a thing?
<worldofpeace>
like, I don't think becoming a committer is in the docs.
<tilpner>
No, I'm not aware of that being documented either
<worldofpeace>
So I think how can someone get it back is an important thing for people to see?
<tilpner>
It could be a single sentence in the issue that notifies them
<tilpner>
For now, at least
<tilpner>
There won't be that many after the first round, and of them not everyone will want their bit back
<worldofpeace>
So I think generating a .md issue with that info would be implementation
<tilpner>
worldofpeace: As in, stuff that needs to be done after the RFC is accepted, or before it can be accepted?
<worldofpeace>
I believe that's just `related-issues: (will contain links to implementation PRs)` right?
<worldofpeace>
Anyways, this was supposed to be a short meeting 😸 I don't have much more time, but I will write the rest on https://github.com/NixOS/rfcs/pull/55. But I don't think this is ready for FCP IMHO. There isn't enough consensus yet?
<worldofpeace>
yeah, I actually first ran into those bugs when we were on office hours and I had to hard reboot
<gchristensen>
ah incredible
<worldofpeace>
gchristensen: there's soo many though
<gchristensen>
really? it'd be good to collect some specifics
<gchristensen>
(and link to them in the release notes, somehow)
<worldofpeace>
like, I think a google search will give a ton of hits in every distro
<worldofpeace>
(eww, did I really just say a google search?)
<gchristensen>
today they will, but in 3 years time they maybe won't be so easy to find
<worldofpeace>
gchristensen: that's true. I had plans to improve all the notes anyways, but with my current time that's a hopeful aspiration
<gchristensen>
sure
<gchristensen>
so one option is to put the reference links directly in the notes, another would be to create an issue for the regressions and link from there
<worldofpeace>
gchristensen: the latter sounds best
<worldofpeace>
intel graphics regressions for kernel series whatevers
<gchristensen>
cool
<gchristensen>
is it just graphics regressions?
<gchristensen>
ie: is that drm/intel/issues/614 link not sufficient?
<worldofpeace>
not sure, I'd have to research again since these situations make headway
<gchristensen>
don't do that :) I'll make a tracking issue and link to it
drakonis has joined #nixos-dev
drakonis2 has quit [Ping timeout: 272 seconds]
drakonis has quit [Ping timeout: 240 seconds]
drakonis has joined #nixos-dev
drakonis has quit [Read error: Connection reset by peer]
drakonis has joined #nixos-dev
Jackneill has joined #nixos-dev
orivej has joined #nixos-dev
drakonis has quit [Read error: Connection reset by peer]
drakonis has joined #nixos-dev
drakonis_ has joined #nixos-dev
drakonis has quit [Read error: Connection reset by peer]
drakonis2 has joined #nixos-dev
Jackneill has quit [Remote host closed the connection]
drakonis_ has quit [Ping timeout: 252 seconds]
<genesis>
is there a known good visibility of dbus service handling on nixos ?
<genesis>
i need to force installation of a dbus service
drakonis2 has quit [Read error: Connection reset by peer]
drakonis has joined #nixos-dev
drakonis has quit [Read error: Connection reset by peer]
<genesis>
some package doesn't enable service they provide
<genesis>
for example /nix/store/v433wawv8hl23kb2c2qk0lgg86sainc1-a2jmidid-8/share/dbus-1/services/org.gna.home.a2jmidid.service
drakonis1 has quit [Quit: WeeChat 2.6]
<genesis>
some package depending on them, like cadence, would not working since they dep on the service, not the package
<genesis>
so if we choose to enable all the service, cost nothing btw, but we need nix standard cmd
<genesis>
or in the package that need service enable?
<genesis>
service dependancies vs packages dependancies.
<genesis>
ping worldofpeace
<genesis>
service dependancies would mean dependance on a service provider, so we have to rely on provider base.
<worldofpeace>
genesis: on nixos you have to put that package in services.dbus.packages
<genesis>
in a word; today software depends on "org.jackaudio.service" and "org.gna.home.a2jmidid", not really on libjack and a2jmidid.
<worldofpeace>
yes, the dbus inerface. usually a nixos service is enabled along with the program. with jack, likely using its module.
<genesis>
worldofpeace : for example; "org.jackaudio.service" could be some jack1 or jack2 system wide or user wide provider, today i've to fix a package name
<genesis>
i just let idea goes their way, some people would be interesting to participate in reflexion, yes i can fix my current pb forcing overidding a2jmidid with ('--enable-pkg-config-dbus-service-dir=true
<genesis>
worldofpeace : would be interessting how you provide /nix/store/v433wawv8hl23kb2c2qk0lgg86sainc1-a2jmidid-8/share/dbus-1/services/org.gna.home.a2jmidid.service to cadence :)