kellin opened a new pull-request against the project: `pungi-fedora` that you are following:
``
Add post-compose rsync script
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/438
walters opened a new pull-request against the project: `pungi-fedora` that you are following:
``
WIP: Add fedora-atomic-ws config
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/502
tstellar reported a new issue against the project: `pungi-fedora` that you are following:
``
The i686 packages for compiler-rt are no longer available in the x86_64 repositories starting with Fedora 27. Could you mark this package as multilb.
See https://bugzilla.redhat.com/show_bug.cgi?id=1513286
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/issue/501
kellin reported a new issue against the project: `pungi-fedora` that you are following:
``
The way we rsync composes today is a one-liner bash script that is not very durable and requires that a release engineer babysit it through the entire four hour rsync process.
I am going to make this more durable, however, it will also slightly change our process behind the scenes.
Today if a process works or is DOOMED after a full run it is assigned an RC release number. (EG: 1.1, 1.2, 1.3, etc). If the compose fails quickly from something such as a failure to have signed packages then it will not be assigned a release candidate.
Per @mohanboddu there is not a durable way to identify the all of the different ways the special case DOOMed composes occur so they will be assigned an RC number after the automation is deployed.
The only visible change will be extra gaps in the RC composes in /pub/alt/stage that represent these extra numbers being inserted to the sequence.
@mohanboddu is fine with this change; does anyone else have objections?
@ausil , @kevin , @puiterwijk please let me know. The initial script PR will be coming within the next two business days.
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/issue/426
tibbs reported a new issue against the project: `releng` that you are following:
``
So I know I used to be able to untag a package but now that fails due to me not having autosign permissions (and probably other things).
Today I merged a PR against redhat-rpm-config but wasn't able to test it sufficiently locally due to my local rawhide box not having received gcc 8 yet. I foolishly built it anyway and immediately broke all of rawhide. 100% my fault. It's a one line fix, but I can't untag it and nobody is online with permissions to do so.
Since as of late I have been doing a number of changes to that and other related packages which can potentially break all of rawhide/fedora/epel, it would be useful for me to be able to untag in case something goes wrong.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7288
hobbes1069 reported a new issue against the project: `releng` that you are following:
``
```
From checkout.log:
$ git clone -n https://src.fedoraproject.org/rpms/blender.git /var/lib/mock/f28-build-11036148-838686/root/tmp/scmroot/blender
Cloning into '/var/lib/mock/f28-build-11036148-838686/root/tmp/scmroot/blender'...
error: RPC failed; curl 18 transfer closed with outstanding read data remaining
fatal: The remote end hung up unexpectedly
fatal: protocol error: bad pack header
```
```
$ git rev-list --objects --all | grep "\.rpm\|\.gz"
6115a22040643818e89404f301faa1d4a4ce4a56 results_blender/2.77a/1.fc23/blender-2.77a-1.fc24.src.rpm
2340a78e377e89c3a3b751a997ce0a563a9714ff results_blender/2.77a/1.fc23/blender-2.77a-1.fc24.x86_64.rpm
7966c177500299784bcaa963381f14b74eddc108 results_blender/2.77a/1.fc23/blender-debuginfo-2.77a-1.fc24.x86_64.rpm
014423f48c5697e0c256cc93c789823800883d85 results_blender/2.77a/1.fc23/blender-rpm-macros-2.77a-1.fc24.noarch.rpm
e2e943ce223ac62904fde4717ceac8e4f3387018 results_blender/2.77a/1.fc23/blenderplayer-2.77a-1.fc24.x86_64.rpm
e3c53ce853edd37b76bc5b4d422f85b14a1a10c5 results_blender/2.77a/1.fc23/fonts-blender-2.77a-1.fc24.noarch.rpm
5b6716c806f9ef18beaeed55beb07b2c162179b6 results_blender/2.77a/1.fc26/blender-2.77a-1.fc26.src.rpm
12a5eee6eb79f3ec8c257cc4b02a16e1c0774966 results_blender/2.77a/1.fc26/blender-2.77a-1.fc26.x86_64.rpm
8a7e6d7dc970f5b1fdd66e9a9e57e814db4de9a2 results_blender/2.77a/1.fc26/blender-debuginfo-2.77a-1.fc26.x86_64.rpm
ac7b7d731e06bf30deb8cfcbbf2a7002b3cef7c4 results_blender/2.77a/1.fc26/blender-rpm-macros-2.77a-1.fc26.noarch.rpm
9b783965dbe33cdc8a670a70d5212e62442094ec results_blender/2.77a/1.fc26/blenderplayer-2.77a-1.fc26.x86_64.rpm
dee39b967a93774562690fc7a898013bbdd831e5 results_blender/2.77a/1.fc26/fonts-blender-2.77a-1.fc26.noarch.rpm
7bffb5068eb55df30d688d8608cd9264a77c8cf3 results_blender/2.78/1.fc26/blender-2.78-1.fc26.src.rpm
c89795526e03033ff0255495f94ced42cea86271 results_blender/2.78/1.fc26/blender-2.78-1.fc26.x86_64.rpm
12907ae1397483d284498820e3fac62ad7e17c07 results_blender/2.78/1.fc26/blender-debuginfo-2.78-1.fc26.x86_64.rpm
b518a731b7f38961433cbf8f6b2b9c4716fce785 results_blender/2.78/1.fc26/blender-rpm-macros-2.78-1.fc26.noarch.rpm
4cd2e44e3562eb77ddf4c3193e80f69389469090 results_blender/2.78/1.fc26/blenderplayer-2.78-1.fc26.x86_64.rpm
6459a4e4cf1ac226117b091ddd7a59bec6cfc6b5 results_blender/2.78/1.fc26/fonts-blender-2.78-1.fc26.noarch.rpm
30bb773c1b4242fdb48b33788e53374a4a900e14 blender-2.77a-1.el7.src.rpm
a6c477b254d54ebe07ed11df6b2ec41e132ddded blender-2.77a-1.fc23.src.rpm
a34c5c49de2fcd378e3d7f74cecfc1dcf77082af blender-2.77a-1.fc26.src.rpm
e17f27a4415c31a747f76e10a68e592bf5d25b47 blender-2.78-1.el7.src.rpm
0e7cb8ad4bf7571ac1123c853e5636854e622124 blender-2.78-1.fc26.src.rpm
a4a9f0f6a24e622799cfefccf1804cae48cdfcae blender-2.78.tar.gz
```
Can these files be removed?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7265
kevin reported a new issue against the project: `releng` that you are following:
``
As noted in this post:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org…
it seems we are only syncing out the drpms made in that specific compose. We should keep a (ideally configurable) amount of older ones around. I think for rawhide we were keeping 2 weeks, we could start with that.
as it is now unless someone updates on the day an update is pushed they won't get the advantage of the drpm.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7215
sedrubal reported a new issue against the project: `releng` that you are following:
``
[casync](https://github.com/systemd/casync) is like a new and better rsync for directory trees, binary files and system images. It can speed up downloads if the user already has a similar image on his local machine.
For example if a user already has fedora 26 and he wants to download fedora 27 he can use fedora 26 as local seed and download only differences using casync. The same applies if he has fedora workstation and he wants to download fedora server.
It was great if you provide a `.caibx` index file for each image and a (global) `.castr` object storage on the fedora ftp mirrors.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7275
kellin opened a new pull-request against the project: `pungi-fedora` that you are following:
``
Make release-candidate.sh script more durable
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/433
ralph opened a new pull-request against the project: `releng` that you are following:
``
A SOP for adjusting EOLs on arbitrary branches.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/pull-request/7119