| 4 Jun 2021 |
 hexa | that can happen outside of nixpkgs, since the nixpkgs model is easy to fork, but alot of being "lts" is about having moldy versions of software, and nobody likes to work with that for free | 18:09:49 |
| hexa | in debian people are paid for maintaining things, this is especially true for the lts extensions of their releases | 18:10:28 |
| hexa | and following debian releases would mean a change to our release cadence, as else you'd need to support multiple stable releases in parallel - not feasible | 18:12:35 |
| hexa | the one month overlap between the old and new stable is annoying enough fwiw | 18:13:47 |
| hexa | * the one month overlap between the old and new stable right now is annoying enough fwiw | 18:13:55 |
 Sandro | In reply to @hexa:lossy.network
and following debian releases would mean a change to our release cadence, as else you'd need to support multiple stable releases in parallel - not feasible right now we release two times a year a big release. Debian does once every few years. | 18:32:00 |
 philipp | Just to be clear I never said we should change the release schedule, I just wondered whether it would be feasible to use debians patches to keep certain packages around a while longer. | 18:33:15 |
| Sandro | you can always just pin the older version and apply the patches yourself but doing a minor or major update is a lot of times easier | 18:35:42 |
| hexa | In reply to @sandro:supersandro.de
right now we release two times a year a big release. Debian does once every few years. roughly every 2 years | 18:44:19 |
| hexa | applying the patches yourself implies you can't be an end-user | 18:44:33 |
| Sandro | In reply to @hexa:lossy.network
roughly every 2 years yeah https://wiki.debian.org/DebianReleases#Production_Releases | 18:49:19 |
 ris_ | hexa: if a need (and the funding/human-power) for LTS emerged, I'd rather they weren't cast out of the project into a fork, where they would need to set up their own infra, hydra, and cause those who find themselves at the end of a regular release's support to have to consciously switch channels etc. | 19:16:34 |
| ris_ | the worst it would mean for us is more noise in github | 19:16:53 |
| hexa | agreed | 19:17:20 |
| hexa | * agreed, I just said it could be done outside. Can't do that with debian that easily. | 19:17:32 |
| ris_ | sure | 19:17:37 |
| hexa | other than that: pay me! | 19:17:47 |
| hexa | * other than that: pay me! 😛 | 19:18:08 |
| ris_ | one day | 19:18:14 |
 pennae | is there an update to postgres 13.3 that we searching nixpkgs? https://security.archlinux.org/AVG-1956 | 21:54:29 |
| pennae | * is there an update to postgres 13.3 that we missed searching nixpkgs? https://security.archlinux.org/AVG-1956 | 21:55:15 |
| 5 Jun 2021 |
| hexa | pennae: can you please ping marsam? | 02:46:19 |
| hexa | or … well | 02:47:17 |
| hexa | brb | 02:47:18 |
| hexa | https://github.com/NixOS/nixpkgs/pull/125751 | 02:57:52 |
| hexa | I'll let marsam do the reviewing/backporting | 02:58:02 |
| hexa | thanks for pointing out the issue | 02:58:18 |
| pennae | thanks for updating :) | 02:58:33 |
| pennae | would've thought the update bot would pick it up rather quickly | 02:58:56 |
| hexa | you mean r-ryantm? | 03:02:22 |
