<henri>
Without the -f option the rm call in the installPhase fails for Mathematica 12
<infinisil>
henri: Feel free to make a PR to the release-20.03 branch and ping the people of the original PR and @NixOS/backports
kalbasit has quit [Ping timeout: 240 seconds]
drakonis has quit [Quit: WeeChat 2.8]
<henri>
infinisil: Thanks. Although after further consideration I decided not to backport this commit, since this might break users' existing installations in that Mathematica will suddenly default to version 12.1 when users only have 12.0 installed. This is an issue because the derivation requires a binary asset to be inserted into the Nix store manually and depending on which license users have bought it might not be possible to simply
<henri>
upgrade.
drakonis has joined #nixos-dev
drakonis has quit [Client Quit]
justanotheruser has quit [Ping timeout: 260 seconds]
cole-h has quit [Quit: Goodbye]
henri has quit [Quit: ERC (IRC client for Emacs 26.3)]
orivej_ has joined #nixos-dev
orivej has quit [Ping timeout: 256 seconds]
justanotheruser has joined #nixos-dev
orivej has joined #nixos-dev
orivej_ has quit [Ping timeout: 264 seconds]
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-dev
ixxie has joined #nixos-dev
infinisil has quit [Quit: Configuring ZNC, sorry for the joins/quits!]
infinisil has joined #nixos-dev
orivej has quit [Ping timeout: 264 seconds]
orivej_ has joined #nixos-dev
__monty__ has joined #nixos-dev
orivej_ has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-dev
noonien has joined #nixos-dev
alp has joined #nixos-dev
__monty__ has quit [Quit: leaving]
v0|d has quit [Ping timeout: 246 seconds]
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 240 seconds]
alp has quit [Ping timeout: 240 seconds]
alp has joined #nixos-dev
symphorien has quit [Quit: WeeChat 2.8]
<ryantm>
I'm trying out a version of r-ryantm/nixpkgs-update that runs passthru.updateScript for packages with that. Please ping me if you notice any strange PRs.
<infinisil>
ryantm: Neat!
<domenkozar[m]>
niceee
alp has quit [Remote host closed the connection]
alp has joined #nixos-dev
teto has joined #nixos-dev
alp has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-dev
symphorien has joined #nixos-dev
cole-h has joined #nixos-dev
symphorien has quit [Ping timeout: 244 seconds]
symphorien has joined #nixos-dev
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-dev
teto has quit [Quit: WeeChat 2.9]
orivej_ has joined #nixos-dev
orivej has quit [Ping timeout: 265 seconds]
orivej_ has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-dev
__monty__ has joined #nixos-dev
alp has joined #nixos-dev
rajivr has quit [Quit: Connection closed for inactivity]
orivej_ has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 256 seconds]
orivej_ has joined #nixos-dev
alp has quit [Remote host closed the connection]
<Valodim>
I wonder if it wouldn't be a good idea to make the updateScript explicit for all packages
<Valodim>
(just brainstorming)
<Valodim>
it's currently pretty magical that some packages get auto updates, but others not. I maintain a few packages, and some got updates, others not..
<Valodim>
Making "how will this package stay up to date" part of the packaging process might be valuable? I imagine there'd be a small set of default functions that will just work for many packages (i.e. the ones nixpkgs-update currently uses)
<Valodim>
or is that already there? I should check the packager manual before pondering stuff like this that might already be there :D (I'm sure nixpkgs is magical like that not just for me every now and then)
<ryantm>
Valodim: https://r.ryantm.com/log/ you can look for your package in the logs to see why it isn't updating
<Valodim>
oh, good to know
<ryantm>
I'd like to make it better, like a directory for each maintainer, and a list of failing updates.
<Valodim>
that'd be great
<Valodim>
it would be amazing to process PRs that add packages, and leave a report for the packager
<Valodim>
"Hi, I'm r-ryantm, I'm a bot who keeps packages up to date in nixpkgs. Here's how I see this package, and here's some tips on what you can do to help this process along"
<ryantm>
I suspect most of that stuff should move into nixpkgs-review. It already has a feature for commenting automatically if you give it your github token.
<ryantm>
Though I guess nixpkgs-review is really in the model of needing to build all the reverse dependencies, which isn't feasible on core packages.
orivej_ has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-dev
alp has quit [Ping timeout: 260 seconds]
ixxie has quit [Remote host closed the connection]
__monty__ has quit [Quit: leaving]
AlwaysLivid has quit [Read error: Connection reset by peer]