Thanks for the feedback, Mitch! And I agree, I think #2 is probably the best option.
As is probably apparent from the most recent stickied post, there doesn't appear to be a way forward with option #1 and option #3 is encouraging use of no-longer-maintained-software. It's not ideal but it is what it is. Sentry is updating according to their needs, and if it aligns with ours--all the better. If not, well, there's not much we can do!
I'm somewhat reluctant to orphan or request deletion for this package quite yet in the hopes that Clickhouse will (eventually) be fixed, but because it's an issue with one of Intel's packages not building they're more or less blocked by an upstream dependency themselves. I suspect they're not hugely interested in resolving this either since they also offer a Docker image. Sigh.
There was also a discussion on the AUR mailing list from one of the Clickhouse maintainers that hinted to me that I shouldn't be expecting much movement on this matter either as there were some criticisms raised related to the PKGBUILDs that remain unaddressed AFAIK. Regardless, I'll keep an eye out, but I think it's best to assume this package will be retired and eventually deleted.
There's really not much any of us can do about it at this point, and I greatly appreciate your feedback and assistance over the years. Thanks again, Mitch!
Pinned Comments
zancarius commented on 2020-01-23 21:38
I have spent some time exploring options for upgrading this PKGBUILD to the latest version of Sentry and have encountered blocking changes that do not appear to have a clear resolution.
Currently, there were two PKGBUILDs that provide our required Clickhouse dependency but neither of these build successfully. Near as I can tell, some of Clickhouse's upstream dependencies have known issues that as yet have no resolution outside attempting to patch either Clickhouse or wait for the upstream developers to address these deficiencies. This is not something either myself or the maintainer(s) of the Clickhouse PKGBUILD(s) can address (not easily, anyway).
Consequently, I will be updating this PKGBUILD, bumping the pkgrel in effort to increase the visibility of this issue. We will be holding Sentry at its current state until we have a clear path forward.
If you need Sentry 10.x.x in your environment, consider installing their official Docker packages. This is the currently recommended method for installing Sentry.
zancarius commented on 2020-01-17 06:45
Sentry v10.0.0 is out, but I will not be upgrading this package for some time. In fact, I'm not sure when an upgrade will be available because the number of additional service dependencies has since exploded.
To illustrate, Sentry v10.x now depends on:
I don't believe Snuba can be disabled in Sentry post-v9.1.2. If this is true, then this means that Sentry now has an implicit dependency on the JRE which may be prohibitive for those users who are running Sentry on lower end hardware or memory-constrained environments.
The official installation guide recommends installing the on-premise edition of Sentry via Docker and advises against source installation, which is what we're doing here.
This leaves us with a couple of options (plus a third thrown in as an either/or):
1) Upgrade anyway and add a host of other dependencies to the PKGBUILD that may surprise some users. Given that Sentry is a complex piece of software to install, this will only add to the complexity and will require additional packages, configuration, etc., that will need to be completed before Sentry can even be upgraded. (The migration process moves events from the database into Snuba, for example.)
2) Cheat and take the easy way out; deprecate this PKGBUILD and point users to the official Docker images. There's no point trying to wrap the Docker images in a PKGBUILD.
3) Rename this package to something like sentry9.1, freezing it at this version, and then pick options #1 or #2.
When I have some time this weekend, I may ask around for advice. There's no easy solution in this case, and I know from past experience with this package that there are some users who may be uninterested in running Sentry v10 if it requires configuring at least 3 other services. I will leave this package flagged for the time being in the hopes users of this package check here.