I have updated pungi on compose-x86-01 compose-x86-02 and branched- composer to 4.1.19
the full transaction on all boxes was
[root@branched-composer ~][PROD]# yum --enablerepo updates-testing update pungi Fedora 26 - x86_64 - Test Updates
58 MB/s | 2.6 MB 00:00 Last metadata expiration check: 0:00:00 ago on Sat 30 Sep 2017 05:35:47 PM UTC. Dependencies resolved. ======================================================================= ======================================================================= ========================================================== Package Arch Version Repository Size ======================================================================= ======================================================================= ========================================================== Upgrading: kobo noarch 0.6.0- 1.fc26 updates 108 k kobo- rpmlib noarch 0.6.0- 1.fc26 updates 32 k pungi noarch 4.1.19- 1.fc26 updates- testing 778 k pungi- utils noarch 4.1.19- 1.fc26 updates- testing 72 k
Transaction Summary ======================================================================= ======================================================================= ========================================================== Upgrade 4 Packages
Total download size: 989 k Is this ok [y/N]: y Downloading Packages: (1/4): kobo-rpmlib-0.5.2-3.fc26_0.6.0- 1.fc26.noarch.drpm 3.3 MB/s | 22 kB 00:00 (2/4): kobo-0.5.2-3.fc26_0.6.0- 1.fc26.noarch.drpm 2.3 MB/s | 35 kB 00:00 (3/4): pungi-utils-4.1.19- 1.fc26.noarch.rpm
9.5 MB/s | 72 kB 00:00 (4/4): pungi-4.1.19- 1.fc26.noarch.rpm
24 MB/s | 778 kB 00:00 [DRPM 1/2] kobo-rpmlib-0.5.2-3.fc26_0.6.0-1.fc26.noarch.drpm: done
[DRPM 2/2] kobo-0.5.2-3.fc26_0.6.0-1.fc26.noarch.drpm: done
--------------------------------------------------------------------- --------------------------------------------------------------------- -------------------------------------------------------------- Total
5.2 MB/s | 907 kB 00:00 Delta RPMs reduced 1.0 MB of updates to 0.9 MB (8.1% saved) Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction
Preparing :
1/1 Upgrading : kobo-0.6.0- 1.fc26.noarch
1/8 Upgrading : kobo-rpmlib-0.6.0- 1.fc26.noarch
2/8 Upgrading : pungi-4.1.19- 1.fc26.noarch
3/8 Upgrading : pungi-utils-4.1.19- 1.fc26.noarch
4/8 Cleanup : pungi-utils-4.1.17- 2.fc26.noarch
5/8 Cleanup : pungi-4.1.17- 2.fc26.noarch
6/8 Cleanup : kobo-rpmlib-0.5.2- 3.fc26.noarch
7/8 Cleanup : kobo-0.5.2- 3.fc26.noarch
8/8 Verifying : pungi-4.1.19- 1.fc26.noarch
1/8 Verifying : kobo-0.6.0- 1.fc26.noarch
2/8 Verifying : pungi-utils-4.1.19- 1.fc26.noarch
3/8 Verifying : kobo-rpmlib-0.6.0- 1.fc26.noarch
4/8 Verifying : pungi-4.1.17- 2.fc26.noarch
5/8 Verifying : kobo-0.5.2- 3.fc26.noarch
6/8 Verifying : kobo-rpmlib-0.5.2- 3.fc26.noarch
7/8 Verifying : pungi-utils-4.1.17- 2.fc26.noarch
8/8
Upgraded: kobo.noarch 0.6.0-1.fc26 kobo-rpmlib.noarch 0.6.0-1.fc26 pungi.noarch 4.1.19- 1.fc26 pungi-utils.noarch 4.1.19- 1.fc26
Complete!
We can downgrade if they have problems. The reason I went and updated pungi was to pull in the patch https://pagure.io/pungi/c/fcbc3ed4aeeab8 1056fc5b18d4c4f4445009d915?branch=master which has caused some pretty big issues with Beta.
Dennis
I have updated pungi on compose-x86-01 compose-x86-02 and branched- composer to 4.1.19
the full transaction on all boxes was
[root@branched-composer ~][PROD]# yum --enablerepo updates-testing
...
Complete!
We can downgrade if they have problems. The reason I went and updated pungi was to pull in the patch https://pagure.io/pungi/c/fcbc3ed4aeeab8 1056fc5b18d4c4f4445009d915?branch=master which has caused some pretty big issues with Beta.
I'm +1 to this, but could you tag the updated packages into the infra tag, so that if we rebuild the box for whatever reason, we get this newer version?
Dennis
El sáb, 30-09-2017 a las 17:47 +0000, Patrick マルタインアンドレアス Uiterwijk escribió:
I have updated pungi on compose-x86-01 compose-x86-02 and branched- composer to 4.1.19
the full transaction on all boxes was
[root@branched-composer ~][PROD]# yum --enablerepo updates-testing
...
Complete!
We can downgrade if they have problems. The reason I went and updated pungi was to pull in the patch https://pagure.io/pungi/c/fcbc3ed4ae eab8 1056fc5b18d4c4f4445009d915?branch=master which has caused some pretty big issues with Beta.
I'm +1 to this, but could you tag the updated packages into the infra tag, so that if we rebuild the box for whatever reason, we get this newer version?
Done
Thanks
Dennis
On 09/30/2017 10:41 AM, Dennis Gilmore wrote:
I have updated pungi on compose-x86-01 compose-x86-02 and branched- composer to 4.1.19
...snip...
We can downgrade if they have problems. The reason I went and updated pungi was to pull in the patch https://pagure.io/pungi/c/fcbc3ed4aeeab8 1056fc5b18d4c4f4445009d915?branch=master which has caused some pretty big issues with Beta.
Sounds fine here. +1
kevin
infrastructure@lists.fedoraproject.org