Bug 963027
| Summary: | includes huge ChangeLog | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Matthias Clasen <mclasen> |
| Component: | glusterfs | Assignee: | Kaleb KEITHLEY <kkeithle> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | joe, jonathansteffan, kalevlember, kkeithle, ndevos, silas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-08-14 11:19:19 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: | 958426 | ||
|
Description
Matthias Clasen
2013-05-15 02:17:36 UTC
fixed in 3.4.0betaX and in the forthcoming 3.3.2. I see that instead of the 6M ChangeLog, glusterfs now ships a 1M compressed ChangeLog.bz2. This actually makes it hurt even more than shipping an uncompressed 6M ChangeLog: The iso media and rpm use xz compression, but when a file is already bz2 compressed, xz doesn't manage to compress it any further. Would it be possible to just drop the ChangeLog.bz2, or trim it like mclasen suggests? Maybe we should just put the url to the git log in there? Sure, sounds good to me. The plan is to trim the ChangeLog to the most recent 50 lines and include a link to a git-tag'd commit log like https://forge.gluster.org/glusterfs-core/glusterfs/commits/v3.4.0beta3 |