While preparing this change, I read the git blame on all of the files I
touched. I saw a working lifetime of building this system which we use
every day and love dearly and keep maintained ourselves. I saw commits
from a 14 year range between 2003 to 2017!! I could not be more thankful
for Eelco's work on building large parts of the foundation of nixpkgs
that all of us rely on now.
However, the end date of that range of the files I looked at the blame
on was 2017. I did not see surviving code from any newer date than that.
Looking at the Git logs, Eelco has been working on other things, and
that's totally fine.
However, it means that our maintenance metadata is out of date on a lot
of packages, and *that*'s the reason I am submitting this change. There
are a lot of packages that don't have anyone with their name on them to
be pinged if they need attention, even if they have had recent activity
(although it is never clear if recent activity was just someone fixing
it because ZHF or because the package actually matters to them).
There are a lot of packages with storied history that maybe don't need
to be in the set anymore at all since they have not been touched in
years; or maybe they are simply finished.
Empty maintainer lists should be a sign that we need to figure out who
maintains it or potentially remove it if it has rotted, and allowing the
maintainer list to be empty if it is already not maintained is part of a
healthy repository ecology.
Either way, I would like to have the maintenance metadata not mislead
anyone into sending Eelco emails about packages he doesn't, in practice,
work on anymore. I have not removed his name from everything; there are
some things that he is the upstream for or has worked on more recently,
for instance, like Nix, which I have left alone.
Removes several patches added in d915eb8 which are now included in-tree.
Notable commits, excluding aforementioned patches:
+ linux/ena: Add rx_overruns to ena-com structs
+ linux/ena: Report RX overrun errors via net device stats
+ linux/ena: Fix incorrect dma sync when SWIOTLB is on
full changelog: https://github.com/amzn/amzn-drivers/compare/ena_linux_2.8.6...ena_linux_2.8.9
This applies some patches that will be in the next version of ena, one
fixing the removal of the adjfreq field in ptp_clock_info, and the
others dealing with devlink changes.
https://hydra.nixos.org/build/221431596
with structuredAttrs lists will be bash arrays which cannot be exported
which will be a issue with some patches and some wrappers like cc-wrapper
this makes it clearer that NIX_CFLAGS_COMPILE must be a string as lists
in env cause a eval failure
* set ENA_PHC_INCLUDE=1 during build to enable ptp hardware stamping
* add sielicki to maintainers
* remove kernel 5.17 broken marker
Signed-off-by: Nicholas Sielicki <nix@opensource.nslick.com>
This update is supposed to give us support for the 5.17 kernel according to the
2.7.0 release notes here: https://github.com/amzn/amzn-drivers/releases/tag/ena_linux_2.7.0
Unfortunately, in practice, it does not build with `linuxPackages_5_17`,
so I left that marked as broken.
It does work for 5.15 though, so we can use that, woo!
There is no maintainer for this package, probably not many users.
It requires effort to fix all third-party modules for this old kernel
versions. It might contain unpatched security holes.
For Pixel chromebooks, we have the samus-kernel.
Apart from that https://github.com/GalliumOS/linux might be a good choice.
