libaom: 2.0.0 -> 2.0.1 v1 PROPOSED

Matthias Beyer: 1
 libaom: 2.0.0 -> 2.0.1

 1 files changed, 2 insertions(+), 2 deletions(-)
Thanks for helping out with reviews! <3
I've been a bit slacking in the last few weeks.

Usually, at least last time this was discussed[0], the preferred way of
handling these patches is to open a PR to allow other maintainers to
comment on the patches. I am not happy with that situation as that
essentially multiplies but freedom has never been for free (and not
wanting to use GitHub is a value that I support).
One more small nit: I usually try to keep the reference to the mail that
submitted the patch in the commit message so, at some point in the
future, we enable users to look them up. This is basically inline with
the "Cherrypicked from ...." lines that we add to backports.
Since that job is boring and annoying I wrote a small [python script] that
takes care of that. And I integrated into my (neo)mutt workflow with a

And a bit of nix+shell glue around the script:
[0]: https://discourse.nixos.org/t/discourse-patch-submission-is-not-fit-for-purpose/4757/28
[python script]: https://github.com/andir/mail2pr
I'll see about writing a blog post and maybe some documentation about
this soon(tm). The nixos.wiki might be a good place to document this as
this workflow isn't really officially supported. I would love to run
this ML on a domain that we control so we can move from sr.ht to
self-hosted etc.. as we need to. Right now we are tied to this platform
(again) due to the fact that I just wanted to play around with this
I agree with both of you. IMO:
- Something like nixpkgs-dev@lists.nixos.org would be nice to have at
  some point / when there are enough users (it would make this list
  official and we'd have full control over the hosting if we need to;
  also: we wouldn't have to host the list and lists.sr.ht might even
  support this in the future [0]).
- But it isn't important right now and switching to a different list
  shouldn't be too disruptive (maybe Drew would even setup a forwarding
  for mails to this list to the new one if we'd ask him nicely and if
  not we could e.g. subscribe a "bot" to ease the transition).
It would require a HUGE political investment to get the nixos/nixpkgs community
to start a mailinglist again.

They killed the wiki because they thought it would be better to document
everything in the repository. This resulted in the worst downgrade in regards to
documentation I have ever seen in a community.

Then they killed the ML, replaced it with discourse, which resulted in the worst
downgrade in user-freedom (regarding preffered UI) I have ever seen in a
community (disourses' mail feature does not count, it's barely usable).

My point is: The nixos community is predestined in bad descisions - at least bad
from our view.

I don't think we will be able to get them to even host a ML within the year.
I would love to see myself disproved, of course!

Matthias Beyer <mail@beyermatthias.de> writes:
Export patchset (mbox)
How do I use this?

Copy & paste the following snippet into your terminal to import this patchset into git:

curl -s https://lists.sr.ht/~andir/nixpkgs-dev/patches/19990/mbox | git am -3
Learn more about email & git

[PATCH] libaom: 2.0.0 -> 2.0.1 Export this patch

CC: "Michael Weiss <dev.primeos@gmail.com>"
CC: "kiloreux <kiloreux@gmail.com>"
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
 pkgs/development/libraries/libaom/default.nix | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pkgs/development/libraries/libaom/default.nix b/pkgs/development/libraries/libaom/default.nix
index 9706cda03f8..c26161eeab6 100644
--- a/pkgs/development/libraries/libaom/default.nix
+++ b/pkgs/development/libraries/libaom/default.nix
@@ -2,12 +2,12 @@

stdenv.mkDerivation rec {
  pname = "libaom";
  version = "2.0.0";
  version = "2.0.1";

  src = fetchgit {
    url = "https://aomedia.googlesource.com/aom";
    rev	= "v${version}";
    sha256 = "1616xjhj6770ykn82ml741h8hx44v507iky3s9h7a5lnk9d4cxzy";
    sha256 = "1vakwmcwvmmrdw7460m8hzq96y71lxqix8b2g07c6s12br0rrdhl";

  patches = [ ./outputs.patch ];
LGTM, thanks!

To github.com:NixOS/nixpkgs.git
   8ab0b85eade..33b610fa098  HEAD -> staging