Date: Sat, 05 Mar 2022 09:55:02 +0000 From: bugzilla-noreply@freebsd.org To: office@FreeBSD.org Subject: [Bug 262008] editors/libreoffice failed to build Message-ID: <bug-262008-25061-wpRApehc3u@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-262008-25061@https.bugs.freebsd.org/bugzilla/> References: <bug-262008-25061@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262008 --- Comment #43 from Guido Falsi <madpilot@FreeBSD.org> --- (In reply to Tomoaki AOKI from comment #41) > Unfortunately, no commit messages on bumps mention about the commits I've= mentioned. > This would make future developers confuse because of unsane traceability. In the ports tree we are often grabbing __FreeBSD_version values near the affected commits, because often one exactly at the affected commit is often missing. Also quite often the commit actually bumping __FreeBSD_version hap= pens a few commits after the fact, so even when there is an actual specific bump= it is not exactly matching the event in the history. So this objection is moot in practice, just grab the nearest bump, that is = good enough, especially since we are talking about head and stable, people will anyway upgrade past the event at some point. Chances of people falling in o= ne of the commits in between is really low. > Moreover, if further MFC to stable/12 is planned, depending on __FreeBSD_= version (OSVERSION on ports) should force another update. > As editors/libreoffice is a giant, requiring several hours to build, this= would be a pain. This depends on the nature of the fix. As far as I can understand this is a build fix, while already built binaries keep working (except ones built usi= ng hacks to try to work around the issue, but that's user action that they will need to fix themselves), so we simply need to change the conditional, no PORTREVISION bump is required for build fixes. If I'm wrong and this is a runtime also issue and thus need to force package being rebuilt you get a point here, but a minor one. If the package is brok= en there is no alternative than rebuilding it to fix it. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262008-25061-wpRApehc3u>