Bug 1933072
| Summary: | JDK Mission control About windows shows incorrect information for the version. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Scott Froberg <sfroberg> | ||||||
| Component: | jmc | Assignee: | Alex Macdonald <almacdon> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | OpenJDK QA <java-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 8.4 | CC: | almacdon, jkang, jvanek, lmiksik | ||||||
| Target Milestone: | rc | Keywords: | Triaged | ||||||
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | jmc-8.0.0-8.module+el8.4.0+10229+75da8244 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 1935340 (view as bug list) | Environment: | |||||||
| Last Closed: | 2021-05-18 16:24:08 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1935340 | ||||||||
| Attachments: |
|
||||||||
|
Description
Scott Froberg
2021-02-25 15:54:42 UTC
A scratch build like that would only work for non-modular packages, right? The "stream-rhel8-rhel-8.4.0" release target isn't valid here, and trying to build only the package itself would be missing the modular dependencies. Wouldn't I need to commit to jmc and then empty commit the modular repo and then scratch build from there?
fwiw, the change I'm looking at right now is:
-%mvn_build -j -- -Dmaven.test.failure.ignore=true
+%mvn_build -j -- -Dmaven.test.failure.ignore=true -DbuildId=rhel -DbuildNumber=%{revhash} -Dbuild.date=%{revdate}
In the jmc spec we didn't set the build information when running the maven build like we do in Fedora or rhscl.
(In reply to Alex Macdonald from comment #5) > A scratch build like that would only work for non-modular packages, right? > The "stream-rhel8-rhel-8.4.0" release target isn't valid here, and trying to > build only the package itself would be missing the modular dependencies. > Wouldn't I need to commit to jmc and then empty commit the modular repo and > then scratch build from there? > > fwiw, the change I'm looking at right now is: > > -%mvn_build -j -- -Dmaven.test.failure.ignore=true > +%mvn_build -j -- -Dmaven.test.failure.ignore=true -DbuildId=rhel > -DbuildNumber=%{revhash} -Dbuild.date=%{revdate} > > In the jmc spec we didn't set the build information when running the maven > build like we do in Fedora or rhscl. Ah right, modules. It slipped my mind for some reason. So for modules you can push the changes to the development branches and run a scratch build there via $ rhpkg module-build --scratch --buildrequires platform:el8.4.0 The development branches for packages are 'stream-rhel8' and the development branch for the module is 'rhel8'. Those branches should not have any push restrictions. Created attachment 1760472 [details]
Screenshot of proposed fix
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (jmc:rhel8 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2021:1955 |