Bug 270102 - devel/bugzilla50 doesn't work with MySQL 8; fixed in upstream years ago. Also, I think it might not be maintained anymore.
Summary: devel/bugzilla50 doesn't work with MySQL 8; fixed in upstream years ago. Also...
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: bz-ports
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-11 06:58 UTC by Robert William Vesterman
Modified: 2023-07-16 22:52 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (bz-ports)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert William Vesterman 2023-03-11 06:58:48 UTC
The devel/bugzilla50 port does not work with the latest databases/mysql80-server, and I suspect that the listed maintainer might no longer be maintaining it.

It compiles fine, from the point of view of the FreeBSD ports system, but when you then follow the pkg-message installation instructions by running its "checksetup.pl" script, it fails while trying to create its table "groups".

I investigated a bit, and found that this is because "groups" was added as a reserved keyword in MySQL 8 (which was released nearly five years ago), and so can't be used as a table name without employing a little special syntax. The upstream Bugzilla people then put out a fix, in version 5.0.6, about four years ago. Unfortunately, devel/bugzilla50 has never been updated past 5.0.4 (five years ago), and so it fails to work on FreeBSD.

I started a thread on the FreeBSD forums about this, about two weeks ago, and at about the same time sent an email to the listed maintainer about the issue. I have not yet received a response; add that to the fact that it hasn't been updated to a new upstream version that was released four years ago, and I'm thinking maybe it isn't maintained at all anymore?

What I'm really hoping for here is for it to be updated to 5.0.6. Failing that, though, maybe it should be explicitly marked as unmaintained, so as to increase the chance that someone might notice and pick up the mantle? I don't know the standard procedure for this sort of thing.
Comment 1 Kurt Jaeger freebsd_committer freebsd_triage 2023-07-16 11:31:03 UTC
See

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247296

for the discussion on upgrading devel/bugzilla50