[releng] Issue #7069: Enable annotaions of binaries compiled by gcc
by Nicholas Clifton
nickc reported a new issue against the project: `releng` that you are following:
``
I would like to enable binary annotations for files compiled by gcc. This will allow extra information to be stored in these files, such as which hardening options were used, the stack size requirements, potential ABI conflicts and so on.
In order to do this I propose patching the redhat-rpm-config rpm to enable the use of the annobin plugin. This plugin will add the extra information to the binary files. Some example scripts in the annobin package demonstrate how this information might be used.
This change has several possible consequences for release engineering:
* It might break the building of any package that uses gcc.
[I have tried to test building various packages locally, and these have all succeeded,
but I do not have the equivalent of an entire Fedora build system].
* The size of gcc built binaries will increase. Not by a huge amount I hope, since
the annotation format is designed to be compact, but it could still be a factor. Note
the information is stored in an unallocated section in the binary, so it will not affect
the size of the executable in memory, only on disk.
* if the annotations work it should allow releng the opportunity to add extra checks
for ABI incompatibilities and hardening problems.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7069
6 years, 2 months
moving around some ostree repos
by Dusty Mabe
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
We are moving to a unified ostree repo model where we compose/ship
content for different releases in a single repo.
- From this we'll basically have one "compose" repo where all the different
branches and rawhide write into it and we'll have two unified repos (one
for atomic workstation and one for atomic host) where the content will be
published to.
When we moved bodhi over to start using pungi we configured it to use a
unified compose repo locatated at https://kojipkgs.fedoraproject.org/compose/updates/atomic/.
The plan is to take this existing repo and mv it to /compose/atomic and
use it for all composes.
The steps are:
1. archive /compose/atomic to /compose/atomic_archive_20180226
2. move the /compose/updates/atomic/ unified repo to /compose/atomic/
3. update all configs to compose into /compose/atomic and sync to /atomic/host and /atomic/workstation/
Summary:
- - rawhide now composes in /compose/atomic/
- - branched now composes in /compose/atomic/
- - bodhi now composes in /compose/atomic
- - FAH rawhide now publishes to /atomic/host/
- - FAW rawhide now publishes to /atomic/workstation/
- - FAH branched now publishes to /atomic/host/
- - FAW branched now publishes to /atomic/workstation/
- - FAH released updates now publishes to /atomic/host/
- - FAW released updates now publishes to /atomic/workstation/
If no one objects patrick and I will perform these changes on Wednesday 02/28 during a period
of time in which no bodhi updates runs are executing.
Thanks,
Dusty
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlqUgSEACgkQMwLb1zlS
5nFqpA//YO/g1+dfvLRK4MFMM9t4h6TbSVMIPpA/fx45dbqpXXQq5ViFJDSvmdqm
F0UTpwN95TmPQvTNu7OSh6qW2LEGxNlrdqqKUN5C9HCNg+tF/sxYG+RXboTJWfyr
ZzfPQYv7dSoPZQvZ92cORVUGUwdSE8BXj1BOXHz59XOQOQRNfVk+XUxRm0P0XEBi
91NycUgqTSsWI7TkrxPidWpUlQdXUMo/nGgWSyeoHsGisLFSA6QrQMaMJ9d1CF0H
Qlnl62OeTmGuSbuiK/8aDOt0Sl+opeX3olTktjkIkHG9csRf4i6sYm0hEYt5lBOA
O6Osexza7M7frQX7X9b4qzUAf9CCSKUOrXEWXPnjm9OyvzTmyRSbMaTG2hCLRm4d
dXyL8wynMMjkNMzHyI6Kn4tZPnv59p7cgVxyfKP+B26O6o4wWbWMjFUPzPjVM7OZ
68b1uLnRLCjuyaJG70PlqeYIgCkullQzMmUC9di4uLUcDCviO5J5tRxsrrEvK5rx
5/0HDG6+4SiNCIlx7rCbbyg+2W8redSahccBXhbQuyPY4Rz6+8fmoLVK3uPz5oCw
2iAdq+CY5/3Z7hlWdljX7gTJXi0/dCClmI1bikrSOypiK3OO9lzex4MfNoHhRlKJ
kADsd82nn3ECrac8euAi37VqEzUe99FTPztGs4Dm2uwvMGSg0X0=
=jOxb
-----END PGP SIGNATURE-----
6 years, 2 months
[releng] Issue #7217: new FLIBS container release for all container images
by Dusty Mabe
dustymabe reported a new issue against the project: `releng` that you are following:
``
These used to be done every two weeks right after the Atomic Host releases. Some ownership of this has changed hands recently, but I believe it is sufficiently automated. Can we please do an ad-hoc release of any new containers and also any existing containers with rebuilt content (i.e. security updates).
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217
6 years, 2 months