<cole-h>
If I want to `sed` something between smart quotes, I can't just do `sed "s/'.*'/'lolololol'/"` -- I have to do `sed "s/(find smart quote open and paste).*(find smart quote close and paste)/(find smart quote open and paste)lolololol(find smart quote close and paste)/"`
<infinisil>
Some keyboards/editors might insert these localized marks automatically
<samueldr>
cole-h: compose <" and compose >", <' and >'
<samueldr>
for the french guillements, « << and » >>
<lovesegfault>
I love that TeX's answer to package management was "just have all the packages in the world on your system always"
<lovesegfault>
QED
<MichaelRaskin>
Well, I already have a list of what TeXLive packages I need for various articles I actually need to edit and recompile (as an expression, of course)
<MichaelRaskin>
lovesegfault: CTAN doesn't have that approach, though.
<lovesegfault>
MichaelRaskin: right, but everyone just uses texlive IME
<MichaelRaskin>
Really? Not Debian, which splits it in large chunks, but still splits it quite a lot? Not MikTeX with its GUI for picking CTAN pieces?
<lovesegfault>
MichaelRaskin: I mean individuals, not distros. Whenever you're being taught how to use TeX it's just "install all of texlive"
<lovesegfault>
even if you run a distro that splits things up, like debian or Arch, you'll still find people commonly recommending you just "install everything"
<lovesegfault>
Again, IME
<MichaelRaskin>
It's actually a nontrivial amount of work to install everything of TeXLive in Debian
<MichaelRaskin>
I think there are no metapackages for _that_
<MichaelRaskin>
It's another thing that if a person even needs to be told, there is an incentive to get them to install everything to increase mean time to next question
<lovesegfault>
:D
<MichaelRaskin>
There are enough smooth-curve tutorials that if you are being personally taught…
supersandro2000 has quit [Ping timeout: 246 seconds]
<supersandro2000>
all options, context aware 107KB!
<supersandro2000>
wait... Why am I cloning this... I could just add it to nixpkgs
<supersandro2000>
oh well to lazy right now... already way to much of the merge train
<supersandro2000>
and before anyone asks: that won't really slow down the shell. that only happens if programs wrap their static and never changing completion script behind npm
srk has quit [Ping timeout: 240 seconds]
srk has joined #nixos-chat
eyJhb has quit [Quit: Clever message]
eyJhb has joined #nixos-chat
eyJhb has joined #nixos-chat
eyJhb has quit [Changing host]
eyJhb has quit [Remote host closed the connection]
<lovesegfault>
but I still get a failed build saying it can't find confuse
endformationage has quit [Quit: WeeChat 2.9]
<supersandro2000>
try super.callPackage isntead of pyself
eyJhb has joined #nixos-chat
eyJhb has joined #nixos-chat
eyJhb has quit [Changing host]
<lovesegfault>
supersandro2000: no difference
<supersandro2000>
you sure it uses the overlay?
<lovesegfault>
yes, b/c I see build of beets happening
<lovesegfault>
it's curious
<hexa->
do we have another beets issue? :O
<lovesegfault>
even if I replace `self.python3Packages` with `python3.pkgs` by making things `rec` it still doesn't work
<lovesegfault>
hexa-: no, I'm working on getting the HEAD packaged
<lovesegfault>
since the releases are so slow
<lovesegfault>
I want to have `beets-unstable` in nixpkgs
<hexa->
have you complained to them already? :P
<lovesegfault>
Yes, Adrian is just a busy guy
<hexa->
sounds like something for your NUR repo honestly
<lovesegfault>
He'll cut a release when he has time, no point in waiting
<hexa->
are you missing any particular feature?
<lovesegfault>
yes, I want a new plugin
<hexa->
like I just do `beet import`, have it fix tags, grab coverart and update mpd
<hexa->
do tell
<lovesegfault>
my beets library is... extensive
<hexa->
error: Package ‘perl5.32.0-Glib-Object-Introspection-0.048’ in /etc/nixos/nixpkgs/lib/attrsets.nix:344 is marked as broken, refusing to evaluate.
<hexa->
*sigh*
<hexa->
pretty sure I didn't request this package directly
<lovesegfault>
so I need the `unimported` plugin to check, from time to time, if some nontracked file made it's way into my lib
<lovesegfault>
and that is only on head
<hexa->
lovesegfault: I only have like 150G of music :)
<hexa->
oh ok
<lovesegfault>
Tracks: 15383
<lovesegfault>
Total time: 6.6 weeks
<lovesegfault>
Approximate total size: 565.6 GiB
<lovesegfault>
Artists: 1434
<lovesegfault>
Albums: 1127
<lovesegfault>
Album artists: 610
<lovesegfault>
:P
<hexa->
Tracks: 6507
<hexa->
Total time: 2.2 weeks
<hexa->
Approximate total size: 131.9 GiB
<lovesegfault>
I'm also about to bite the bullet and do something I've been waiting to do forever
<lovesegfault>
re-import all my music using discogs to tag instead of musicbrainz
supersandro2000 has quit [Read error: Connection reset by peer]
<hexa->
that will take days :p
<lovesegfault>
I know, I'm alright with that
<hexa->
I wonder if you'll run into rate limiting
<lovesegfault>
perhaps
supersandro2000 has joined #nixos-chat
eyJhb has quit [Quit: Clever message]
eyJhb has joined #nixos-chat
eyJhb has joined #nixos-chat
eyJhb has quit [Changing host]
eyJhb has quit [Remote host closed the connection]
eyJhb has joined #nixos-chat
eyJhb has joined #nixos-chat
eyJhb has quit [Changing host]
cole-h has quit [Ping timeout: 240 seconds]
lunc has quit [Ping timeout: 240 seconds]
eyJhb has joined #nixos-chat
waleee-cl has quit [Quit: Connection closed for inactivity]
eyJhb has quit [Quit: Clever message]
eyJhb has joined #nixos-chat
eyJhb has quit [Excess Flood]
eyJhb has joined #nixos-chat
eyJhb has joined #nixos-chat
<lovesegfault>
I need a source file available on this website written in PHP
eyJhb has quit [Remote host closed the connection]
eyJhb has joined #nixos-chat
eyJhb has joined #nixos-chat
eyJhb has quit [Changing host]
neeasade has joined #nixos-chat
<sphalerite>
lovesegfault: hm, why that? What's the advantage of discogs?
<lovesegfault>
sphalerite: I have a lot of obscure albums that aren't on musicbrainz
<lovesegfault>
but are on discogs
<lovesegfault>
and migrating them can be a HUGE pita
<lovesegfault>
I just don't have the patience
<sphalerite>
ah, fair
neeasade has quit []
lunc has joined #nixos-chat
<patagonicus>
Heh. While I knew it before, it finally clicked that <nixpkgs> is just as much a path as ./ and I can do stuff like `lib = let foo = <nixpkgs> in import (foo + "/lib");`
<eyJhb>
patagonicus: Yeah it is quite nice! But one can quickly screw it up...
<patagonicus>
Oh, for sure. My use case is pinning nixpkgs in CI, but giving the option of using nixpkgs from NIX_PATHS locally if desired (and I can no toggle that via --arg pinned false).
<patagonicus>
Next step: getting caching of the nix store to work in GitLab CI. That's going to be interesting.
__monty__ has joined #nixos-chat
cosimone has joined #nixos-chat
cosimone has quit [Quit: cosimone]
cosimone has joined #nixos-chat
thibm has joined #nixos-chat
waleee-cl has joined #nixos-chat
cole-h has joined #nixos-chat
spudly1 has quit [Ping timeout: 265 seconds]
cole-h has quit [Ping timeout: 256 seconds]
<infinisil>
lovesegfault: hexa-: 3415 tracks for 2.0 weeks total time for me, only 42.0 GiB :)
<hexa->
infinisil: get more flac :p
<infinisil>
Honestly it makes no sense for me to get flac's
<hexa->
yeah, kidding. But that's probably the difference.
<patagonicus>
Wow. The GitLab CI cache was not working, because GitLab does a git clean -ffdx, which then deletes the cache file. Seems kinda … stupid.
<abathur>
huh, volth lives, at least on discourse
ece has quit [Ping timeout: 264 seconds]
<das_j>
patagonicus: Did you tell it where the cache is? You have to specify that in your gitlab-ci.yml
<infinisil>
Boston Dynamics robots doing a dance together
<patagonicus>
das_j: Yeah, I had the cache specified. But I'm just running it locally, no cache server, with the "docker" executor. But until I also set GIT_CLEAN_FLAGS to not delete the cache it would always delete the file before any of my stuff ran.
<patagonicus>
I'm really not sure how the cache is supposed to work - maybe you're not supposed to have it in the working directory? But I remember reading that it has to be.
<sphalerite>
infinisil: aw yiss cute military tech is the best, almost helps you forget that this stuff is designed to help kill people!! :D :D :D
<infinisil>
-.-
<infinisil>
Of course everything can be used for bad things as well. But these robots are designed to help warehouse operations
<das_j>
patagonicus: We have a node project where the node project is in the working directory, but a directory itself. But we are also using the shell executor
<das_j>
*node cache
<patagonicus>
Hmm
<__monty__>
Tbh, I prefer the pillaged NASA money going into practical robotics over PR or conventional weaponry.
<das_j>
patagonicus: We use `cache: { key: "condor-node-modules", paths: [ "node_modules/" ] }`. Maybe that helps
<patagonicus>
That's roughly what I was doing, didn't work. Are you sure it's actually using the cache? The thing is that these caches are just for performance, so the jobs should succeed even if the caches not there. :D
<patagonicus>
To be fair, my GitLab is on an old version, but the runner is not.
<joepie91>
if I got a dollar for every time "should succeed even if the cache is not there" turned out to be "oops, someone decided to use the cache as a critical persistent datastore without telling anybody"...
* joepie91
glares extra hard at all the JS devs stuffing pretend-not-globals into the module cache
<patagonicus>
joepie91: At least I don't have that problem, because all I'm caching is nix store paths, so if there not there, it shouldn't matter. :)
<andi->
unless you produce those paths impurely or via some weird fixed output stuff that wasn't really a good idea ;)
<patagonicus>
Well, it's working now, although I'm not caching everything. But I am caching the extracted, pinned nixpkgs as well as most build dependencies, so it's not downloading much. I can live with that. Especially because I probably ran the pipeline more often to debug this than I will for the rest of the lifetime of the project. :D
<patagonicus>
andi-: Nah, it's just one buildGoModule with vendored deps and a shell for linting/testing.
<andi->
vendored deps as in they are in the source checkout or are vendored using the nix tooling? :)
<patagonicus>
Source checkout, as I want this to be easily buildable without nix, just Go tooling.
<patagonicus>
Ok, I get the feeling that the cache bit doesn't do anything and the "caching" only works because I told Gitlab not to clean up in between runs.
rajivr has quit [Quit: Connection closed for inactivity]
<hexa->
python-mocket just went from 3.9.4 to 3.9.35 in which they removed a py2 compat layer
<hexa->
I hope it's just a typo
<hexa->
but most probably it reflects minimal supported python version is now 3.5
thibm has quit [Quit: WeeChat 2.6]
<joepie91>
wat
<joepie91>
that is a terrible way to version things
<srk>
patagonicus: is there some guide about running nix builds (and possibly qemu tests) on gitlab pipelines?
<patagonicus>
srk: no idea, but outside of the caching thing it's really simple. Basically just image: nixos/nix:2.3.6 and nix-build --no-build-output. Although my default.nix uses a pinner nixpkgs, otherwise you need to nix-channel --add first.
<srk>
cool
ece3 has joined #nixos-chat
andi- has quit [Quit: WeeChat 2.8]
andi- has joined #nixos-chat
endformationage has joined #nixos-chat
<sphalerite>
infinisil: nah, robots for warehouses don't need fancy leg stuff, they can go on wheels. Boston Dynamics has mostly been funded by DARPA as far as I know.
<sphalerite>
unless I've missed the development of cross-country warehouses with rough terrain :p
<__monty__>
I think firefighting's one of the applications of the bipeds?
<sphalerite>
ah yes, for the famous well-funded fire departments
<samueldr>
so you can have it walk through your oil rig, including stairs, to do automatic inspections
<samueldr>
or a building in construction, to update a map daily, or more often, to track progress
<sphalerite>
oh yeah oil and gas, the pioneers of doing good for humanity.
<sphalerite>
I'm sorry
<sphalerite>
I should just shut up and go to bed :)
<sphalerite>
energizer: oh wow, I think I missed that xkcd! hahaha
<samueldr>
nah, I was mainly thinking about stated use cases
<samueldr>
and anything that can reduce (or eliminate) the risks is good, since we're not close to completely eliminitating their uses yet :(
<samueldr>
in a realist point of view: better have additional checks than none at all on those bad actors
cosimone has quit [Quit: cosimone]
<joepie91>
one major problem that that approach often presents for activists (in general): sometimes the only way to shut down a bad actor is to focus on something relatively minor because the more serious problem is difficult to convey
<joepie91>
focus on it in public communication, I mean
<joepie91>
solving the minor problems can defeat that approach
<energizer>
i think the 'automatic inspections' use case seems pretty weak. just put a camera on the wall
<samueldr>
eh
<samueldr>
if you say so
<samueldr>
I won't try to change your mind
<energizer>
do you think a robot is cheaper or more efficient than a camera? i've never been on an oil rig so i'm not familiar with that environment
<samueldr>
I don't know
<samueldr>
am I accidentally a sales rep now?
<samueldr>
I listed use cases I read on, IIRC, an arstechnica article
eyJhb has joined #nixos-chat
eyJhb has joined #nixos-chat
<energizer>
i just meant to chat, not to put you in any kinda pigeonhole :)
<energizer>
but if you wanna sell me one at a hefty discount i wouldnt be opposed...
<samueldr>
haha, I can sell you one 50% off my regular price
<samueldr>
(I resell them with 300% markup though)
<energizer>
cant wait for nixos-on-robot
Baughn has quit [Ping timeout: 240 seconds]
Baughn has joined #nixos-chat
ElXreno[m] has joined #nixos-chat
<srk>
or put a camera on a quadcopter for fraction of the quadruped cost .. :)
<ElXreno[m]>
Sorry for noob questions here, but I need help with the nvidia driver.
<ElXreno[m]>
I have a laptop with nvidia card which supports only 390xx proprietary driver. After installing and rebooting I see a working gdm and I can log in, but after log in Xorg didn't see any displays and uses the virtual display. How I can fix this?
<ElXreno[m]>
<srk "try #nixos"> There is silence in #nixos, so I decided to ask here.
<srk>
nixos support questions are offtopic here :)
<ElXreno[m]>
Oh, ok, sorry
<srk>
try asking again later or discourse for better persistence
<supersandro2000>
I want some feedback on my new idea: I want to run bloaty (https://github.com/google/bloaty) on all binaries build by nixpkgs-review to check, if we still have debug infos in binaries
<supersandro2000>
Would you think this is useful?
<supersandro2000>
I would filter the ouput for debug_info
<supersandro2000>
or debug
<srk>
objdump might do
<andi->
supersandro2000: I am seriously not sure why you put so much effort into *building* things when we already have ofBorg doing that for us. nixpkgs-review always appeared as a tool to manually *test* the binaries in addition to our common CI. I am honestly a bit annoyed by seeing nixpkgs-review comments in PRs that provide almost no additional benefit over ofBorg. We should improve the generic CI
<andi->
on all PRs and not some tooling that might be ran against a PR.
<bbigras>
I was also wondering if automation was doing the same thing as ofBorg.
<supersandro2000>
ofborg does not build dependant packages, checks are not red if they fail and are super easily missed and I can't easily hook extra things into it. Darwin is also always overloaded. Changed packages are always a few clicks away and failed builds are not shown by default.
<supersandro2000>
also it would take way longer than I want to wait to get new experimental features into ofborg. See it like a test for new things we might want to integrate later in the default CI.
<energizer>
shouldn't that situation be changed? how much does hydra's compute cost?
<supersandro2000>
or long would it take until ofborg checks binarys with bloaty and makes the results visible? Also ofborg is hard to test.
<supersandro2000>
energizer: I am not replacing hydra. if a PR has more than a 100 packages I am skipping it.
<energizer>
or, how much does ofBorg's compute cost?
<supersandro2000>
also I already catched way more errors than I liked in wrong dependencies in python because PRs are not tested good enough
<samueldr>
that discussion should have been on #nixos-dev :), including the initial question from supersandro2000
<samueldr>
(many nixos devs are not idling here, it's unfair to them to discuss here)
<supersandro2000>
also when ofborg fails and I have no clue why I would need to locally build the same PR making the interaction time higher than I like which would mean I would just skip the debugging
cosimone has joined #nixos-chat
<supersandro2000>
samueldr: It is not an official nixos topic so I did not want to notice everyone. More a personal effort to test new ways and things before making them official
<samueldr>
it is discussion about nixos development
<samueldr>
not everything on #nixos-dev is about official tools
<colemickens>
gchristensen: I know you had docbook.rocks, can I ask your thoughts on asciidoc and Antora? I like asciidoc/docbook's xrefs, code-block callouts, etc, and am looking for a slightly more flexible+themable asciidoc-powered mdbook. Antora looks neat, but also like a lot going on for a project I'd not hear of before.
<samueldr>
colemickens: I'm not graham, but I can say I like using asciidoc(tor) to write docs for Mobile NixOS
<samueldr>
the site is all authored using asciidoctor
<colemickens>
oh really.
<colemickens>
nice
<colemickens>
that's excellent to know
<samueldr>
though it's using some messy stuff around asciidoctor for the site generation
<colemickens>
aha!
<colemickens>
I was looking at a2x -> pandoc -> html? But I have no idea. Need to switch gears to authoring content soon though :P
<samueldr>
with that said, it's malleable enough that I never hit a problem where I couldn't do a thing
<samueldr>
colemickens: yikes, looking at the adbook example output and it's... not good
<samueldr>
I can't seem to find how one would *actually* navigate the book
<samueldr>
it seems horizontal scrolling is required to make sense of the content
<samueldr>
but yeah, maybe teething troubles?
<supersandro2000>
finding the right channel is not always easy for me
<colemickens>
I'd really like some more SSG-like things too, that I've not seen examples of with any existing docbook/asciidoc tooling. I'd like to be able to "tag" articles and then offer static pages of articles listed by tag, and also maybe ideally a static-site-friendly js-powered search to allow filtering based on multiple tags. I feel like I've seen these features in zola/hugo type tools.
<samueldr>
things might have changed a lot in a year :)
<samueldr>
I don't dislike the current output, so maybe things evolved
<colemickens>
as a beginner to asciidoc with no experience with asciidoctor, I like the premise that antora and the UI are separate. I feel like with a handlebars template, I could achieve a lot of what I want with all of the frontmatter available to me (and it looks like asciidoc has 'keywords' as a first-class feature)
<samueldr>
as a web integrator, I seem to remember that it was hurting me to use the docs, but not right now
<samueldr>
well, found a nitpicking issue, but that's, like, because everyone who does web design and integration are using macs or systems without a tangible scrollbar
<samueldr>
https://docs.antora.org/antora/2.3/ <- in a narrow window so it uses the "mobile" version, show and hide the side bar, the scrollbar will come and go
<samueldr>
though, a good thing is they didn't fall for the easy pitfall of making the side bar actually disappear so widening the window again means your sidebar is lost
* colemickens
is so happy every time he can join a gitter room from matrix
cole-h has joined #nixos-chat
<colemickens>
samueldr: is hte mobile-nixos website source availalbe? I don't see it in the gh org
<samueldr>
yes
* samueldr
waits on browser that decided to take ages to render a page
<colemickens>
It seems like it asciidoctor is missing any sort of extensibility that lives outside the context of a single article? and that's where you wrote the ruby bits - sitemap,rss, you had to build up those structures yourself
<samueldr>
I did say "badly" :)
<colemickens>
samueldr: not at all, I'm just completing the picture in my head
<samueldr>
though what's great is that everything is laid bare
<colemickens>
(mostly because some of this seems obvious to build into asciidoctor?)
<samueldr>
nothing in private internal structures you can't look into
<samueldr>
I guess maybe into an actual extension
<__monty__>
Since you mentioned pandoc. Isn't that an option? You can write filters in several languages, all languages if you don't mind marshalling to and from JSON.
<samueldr>
but I didn't want to get started with rubygems, while we currently have an asciidoctor package that works
<colemickens>
that's what I mean though, from all appearances the extension documentation only talks about acting on the context of a single article
<colemickens>
but anyway, I'm just spitballing now, this is all super useful info.
<samueldr>
hm, it's so far back that I don't remember the details
<colemickens>
and yeah __monty__ I'll probably poke at that a bit more too
<colemickens>
oh no, when I google "a2x pandoc" now I get the issue I just filed on conix.
<{^_^}>
theNerd247/conix#34 (by colemickens, 13 hours ago, open): Use a2x and pandoc to support asciidoc?
<__monty__>
What's a2x? Doesn't pandoc support asciidoc for reading?
<energizer>
if conix files can get correct syntax highlighting i'm gonna be quite impressed
<colemickens>
__monty__: not from what I saw. I guess maybe a2x was wrong, maybe just asciidoc is used to convert asciidoc to docbook. still learning here :P
<colemickens>
energizer: if it's all a DSL, couldn't you write an expression to run a file through a colorizer? (I don't know, just speculating on what I thought conix's value prop was, and seems possible given the way it uses pandoc already)
<__monty__>
Ah, asciidoc's only supported as output format yeah.
<colemickens>
(while I'm falling down this hole, there's also nix-styx to poke at too)
<energizer>
colemickens: the complication is dynamically figuring out what language it is. a lot of tools sorta give up on that
<colemickens>
uh nix-styx has asciidoc support :O
<colemickens>
energizer: oh I'm used to having to tell them anyway I guess
<__monty__>
Oh, one thing. Since you specifically mention some asciidoc features, like callouts. I'm not sure pandoc conserves these during conversion.
<energizer>
colemickens: i mean because a conix file has multiple languages in it
<energizer>
nix and html/markdown
<colemickens>
but the conix file is just nix using expressions to generate those things