ignatenkobrain reported a new issue against the project: `releng` that you are following:
``
Not sure why it didn't work automatically...
```
➜ rust-quickcheck0.4 git:(master) fedpkg retire "No need for this compat package anymore"
rm '.gitignore'
rm 'README.md'
rm 'quickcheck-0.4.1-fix-metadata.diff'
rm 'rust-quickcheck0.4.spec'
rm 'sources'
[master 7f5e2a1] No need for this compat package anymore
6 files changed, 1 insertion(+), 81 deletions(-)
delete mode 100644 .gitignore
delete mode 100644 README.md
create mode 100644 dead.package
delete mode 100644 quickcheck-0.4.1-fix-metadata.diff
delete mode 100644 rust-quickcheck0.4.spec
delete mode 100644 sources
Counting objects: 3, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (1/1), done.
Writing objects: 100% (3/3), 317 bytes | 317.00 KiB/s, done.
Total 3 (delta 0), reused 0 (delta 0)
remote: Sending to redis to log activity and send commit notification emails
To ssh://pkgs.fedoraproject.org/rpms/rust-quickcheck0.4
7d08a41..7f5e2a1 master -> master
➜ rust-quickcheck0.4 git:(master) ✗
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7192
mbriza reported a new issue against the project: `releng` that you are following:
``
Please build it after the new release madness has settled.
It makes the available versions (WS 27, Server 26) more clear in the UI. Also, some bugs are fixed.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7163
mohanboddu opened a new pull-request against the project: `releng` that you are following:
``
Adjust EOL of all components in a branch
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/pull-request/7209
mohanboddu opened a new pull-request against the project: `releng` that you are following:
``
Update freeze doc for final freeze
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/pull-request/7169
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
churchyard reported a new issue against the project: `releng` that you are following:
``
Could you please review our self-contained change proposal on https://fedoraproject.org/wiki/Changes/Django20 ?
We'll kindly ask releng to bulk retire some packages during the change, but only if FESCo approves that list first. The number of packages should not be extremely large (I'd guess something between 3 and 20).
Thanks
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7211
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
yselkowitz reported a new issue against the project: `releng` that you are following:
``
With the public release of [RHEL for ARM version 7.4] (https://www.redhat.com/en/blog/red-hat-introduces-arm-server-support-red-ha…) the RHELSA Development Preview is no longer supported. Please switch the epel7 aarch64 buildroots to use the following repositories:
rhel-7-for-arm-64-rpms
rhel-7-for-arm-64-optional-rpms
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7161
lsedlar reported a new issue against the project: `releng` that you are following:
``
Since Dec 12, the compose is failing due to `f25` not being a valid build target in Koji. The cron job for this compose should probably be stopped to not waste resources.
```
2017-12-15 05:45:36 [ERROR ] Compose run failed: Could not find task ID in output. Command 'koji --profile=compose_koji image-build --config=/mnt/koji/compose/Fedora-Docker-25-20171215.0/work/image-build/Docker/docker_Fedora-Docker-Base_armhfp-x86_64.cfg --wait' returned
'GenericError: Unknown build target: f25
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7214