Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

graylog: 3.3.9 -> 4.0.1 #105645

Closed
wants to merge 1 commit into from
Closed

Conversation

r-ryantm
Copy link
Contributor

@r-ryantm r-ryantm commented Dec 2, 2020

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/graylog/versions.

meta.description for graylog is: "Open source log management solution"

meta.homepage for graylog is: "https://www.graylog.org/"

meta.changelog for graylog is: ""

Updates performed
  • Version update
To inspect upstream changes
Impact
Checks done (click to expand)

Rebuild report (if merged into master) (click to expand)
4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)


First fifty rebuilds by attrpath
graylog
Instructions to test this update (click to expand)

Either download from Cachix:

nix-store -r /nix/store/wmr14gyk8mah7c97clh7kplc2zg3q2x0-graylog-4.0.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.

Or, build yourself:

nix-build -A graylog https://github.com/r-ryantm/nixpkgs/archive/68919de6533088cb527bb6e547f04ec3e04bdc25.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/wmr14gyk8mah7c97clh7kplc2zg3q2x0-graylog-4.0.1
ls -la /nix/store/wmr14gyk8mah7c97clh7kplc2zg3q2x0-graylog-4.0.1/bin


Pre-merge build results

We have automatically built all packages that will get rebuilt due to
this change.

This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.

Result of nixpkgs-review 1

1 package built:
  • graylog

Maintainer pings

cc @fadenb for testing.

Copy link
Contributor

@fadenb fadenb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The license of Graylog changed to an unfree license from version from 3.x to 4.x.

We should not allow this update without a clear transition strategy and/or providing both versions in parallel for a release or two.

That aside, I personally will not invest any time/energy in maintaining Graylog with an unfree license in NixOS (but am happy to keep the 3.x branch up to date as before).

@SuperSandro2000
Copy link
Member

This would be similar to #83433.

@Ma27
Copy link
Member

Ma27 commented Dec 2, 2020

@fadenb first of all, thanks a lot for your efforts regarding graylog in nixpkgs!

Does graylog intend to keep 3.x active for a noticeable amount of time? If that's the case we could rename graylog to graylog_3 and add 4.x if people are interested.

cc @ryantm I'm wondering if nixpkgs-update should be able to detect licensing changes as well.

@fadenb
Copy link
Contributor

fadenb commented Dec 3, 2020

Does graylog intend to keep 3.x active for a noticeable amount of time? If that's the case we could rename graylog to graylog_3 and add 4.x if people are interested.

I am still waiting for a response on that topic from Graylog. I will ask them again with the via another channel and let you know what they say.

@fadenb
Copy link
Contributor

fadenb commented Dec 11, 2020

Does graylog intend to keep 3.x active for a noticeable amount of time? If that's the case we could rename graylog to graylog_3 and add 4.x if people are interested.

I am still waiting for a response on that topic from Graylog. I will ask them again with the via another channel and let you know what they say.

Unfortunately I did not get any response from the folks at Graylog as of now.
I would operate under the assumption that Graylog 3 is "dead" as they are aggresively pushing v4 wherever possible.

@mweinelt mweinelt mentioned this pull request Mar 27, 2021
4 tasks
@stale
Copy link

stale bot commented Jun 9, 2021

I marked this as stale due to inactivity. → More info

@stale stale bot added the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jun 9, 2021
@fadenb
Copy link
Contributor

fadenb commented Jun 10, 2021

As nothing changed I am going to close this PR.
Independently I plan to upgrade the 3.x Graylog to the latest available version as soon as I can find the time for it.

@fadenb fadenb closed this Jun 10, 2021
@r-ryantm r-ryantm deleted the auto-update/graylog branch June 14, 2021 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants