-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Looks like even though we got the 0.15.1 RPM upload issues sorted out last week, the metadata for the RedHatEnterpriseLinux repos on beaker-project.org still shows 0.14.2 as the latest version :(
The Fedora repos appear fine, almost certainly due to the fact that those are generated differently.
Cheers, Nick.
- -------- Original Message -------- Subject: Re: Requesting/managing upgrades to beaker.fedoraproject.org Date: Tue, 05 Nov 2013 12:50:09 +1000 From: Nick Coghlan ncoghlan@redhat.com Organization: Red Hat Asia-Pacific To: qa-devel@lists.fedoraproject.org
On 11/05/2013 07:15 AM, Tim Flink wrote:
On Fri, 01 Nov 2013 18:43:32 +1000 Nick Coghlan ncoghlan@redhat.com wrote:
On 11/01/2013 05:23 PM, Tim Flink wrote:
I'm fine with either direction for now. My hesitation on getting started with 1) is that having a beaker installation is still an evaluation for us. I have a hard time seeing things not working out but I also don't pretend to be clarvoyant :)
If you guys are fine with putting work into something that will probably change (see comment below about ansible), I can get the ball rolling to separate the ACL for the beaker server and get you all the access you need. Otherwise, I can just apply the updates myself. Let me know if you all have a preference on which route to take right now.
If you're happy to do the update, I think it makes more sense for you to handle this one. The beaker-project.org repos should have 0.15.1 available now, and the upgrade instructions are at http://beaker-project.org/docs/whats-new/upgrade-0.15.html
I tried upgrading today and I don't think that any el6 rpms are available for 0.15 in the yum repos on beaker-project.org.
We had some weirdness with the RPM publication due to the fact 0.15.1 was an upstream-only release, but I thought we resolved that last week.
However, even though we sorted out the RPM upload issues, it appears only the Fedora repos have been generated correctly - the metadata for the various RHEL repos looks like it is still missing the 0.15.x releases :(
We'll dig into it.
Cheers, Nick.
----- Original Message -----
From: "Nick Coghlan" ncoghlan@redhat.com To: "beaker-devel" beaker-devel@lists.fedorahosted.org Sent: Tuesday, November 5, 2013 1:03:09 PM Subject: [Beaker-devel] Beaker 0.15.x missing from beaker-project.org RHEL repos
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Looks like even though we got the 0.15.1 RPM upload issues sorted out last week, the metadata for the RedHatEnterpriseLinux repos on beaker-project.org still shows 0.14.2 as the latest version :(
The Fedora repos appear fine, almost certainly due to the fact that those are generated differently.
Yes, it is specific to anything that is handled by our build scripts. The problem is that running 'make' will build the repos from packaged in brew, and existing repos that has 0.15.1 rpms (el5/el6) would be overwritten and 0.15.1 removed.
In future instances (technically only needed for when upstream is not in brew), we just have to make sure to do it in two steps always:
make createrepo --update --no-database -o <repodata_dir> <rpm_dir>
This will ensure that as long as the latest RPMs reside in <rpm_dir>, the repos will be generated correctly.
Cheers, Nick.
- -------- Original Message --------
Subject: Re: Requesting/managing upgrades to beaker.fedoraproject.org Date: Tue, 05 Nov 2013 12:50:09 +1000 From: Nick Coghlan ncoghlan@redhat.com Organization: Red Hat Asia-Pacific To: qa-devel@lists.fedoraproject.org
On 11/05/2013 07:15 AM, Tim Flink wrote:
On Fri, 01 Nov 2013 18:43:32 +1000 Nick Coghlan ncoghlan@redhat.com wrote:
On 11/01/2013 05:23 PM, Tim Flink wrote:
I'm fine with either direction for now. My hesitation on getting started with 1) is that having a beaker installation is still an evaluation for us. I have a hard time seeing things not working out but I also don't pretend to be clarvoyant :)
If you guys are fine with putting work into something that will probably change (see comment below about ansible), I can get the ball rolling to separate the ACL for the beaker server and get you all the access you need. Otherwise, I can just apply the updates myself. Let me know if you all have a preference on which route to take right now.
If you're happy to do the update, I think it makes more sense for you to handle this one. The beaker-project.org repos should have 0.15.1 available now, and the upgrade instructions are at http://beaker-project.org/docs/whats-new/upgrade-0.15.html
I tried upgrading today and I don't think that any el6 rpms are available for 0.15 in the yum repos on beaker-project.org.
We had some weirdness with the RPM publication due to the fact 0.15.1 was an upstream-only release, but I thought we resolved that last week.
However, even though we sorted out the RPM upload issues, it appears only the Fedora repos have been generated correctly - the metadata for the various RHEL repos looks like it is still missing the 0.15.x releases :(
We'll dig into it.
Cheers, Nick.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJSeF/sAAoJEHEkJo9fMO/LVXYH/jszQ+z0OJVDAs1YCC0QNHLu p7MK67s0KKzs5KTW5G2EuD6/se99YmJR6dKvEFg3h9PispOMl1LTRb+5ZVYS2HKC erBuD3vQTh4E/mMQwWPZmnUhIfdycZOwuAWWphdMhRqgY78xC2wSqujYZSNgWGGP MvEshVfF+i6+yh24njEs56+2gTFluiQ/mUQ6IqMbc0B9QMglSF7Y1gH2zGKEwrmw yDlFUWe/NI5/6YRTn8/D+kW5U03beB+fKF+xKrgiubTYes4G4dhetFFxsVl4eYFB 0x1NLTxHKnvWQUDKWU/fgDQkFbLXzohychGHOhougBjaZybCGqs2SvZ7mSsfqf4= =lykB -----END PGP SIGNATURE----- _______________________________________________ Beaker-devel mailing list Beaker-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/beaker-devel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/05/2013 02:52 PM, Raymond Mancy wrote:
----- Original Message -----
From: "Nick Coghlan" ncoghlan@redhat.com To: "beaker-devel" beaker-devel@lists.fedorahosted.org Sent: Tuesday, November 5, 2013 1:03:09 PM Subject: [Beaker-devel] Beaker 0.15.x missing from beaker-project.org RHEL repos
Looks like even though we got the 0.15.1 RPM upload issues sorted out last week, the metadata for the RedHatEnterpriseLinux repos on beaker-project.org still shows 0.14.2 as the latest version :(
The Fedora repos appear fine, almost certainly due to the fact that those are generated differently.
Yes, it is specific to anything that is handled by our build scripts. The problem is that running 'make' will build the repos from packaged in brew, and existing repos that has 0.15.1 rpms (el5/el6) would be overwritten and 0.15.1 removed.
In future instances (technically only needed for when upstream is not in brew), we just have to make sure to do it in two steps always:
make createrepo --update --no-database -o <repodata_dir>
<rpm_dir>
This will ensure that as long as the latest RPMs reside in <rpm_dir>, the repos will be generated correctly.
Does that need to be run on the appropriate OS version to include the right RPMs?
Cheers, Nick.
- -- Nick Coghlan Red Hat Infrastructure Engineering & Development, Brisbane
Testing Solutions Team Lead Beaker Development Lead (http://beaker-project.org/)
----- Original Message -----
From: "Nick Coghlan" ncoghlan@redhat.com To: beaker-devel@lists.fedorahosted.org Sent: Tuesday, November 5, 2013 3:13:36 PM Subject: Re: [Beaker-devel] Beaker 0.15.x missing from beaker-project.org RHEL repos
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/05/2013 02:52 PM, Raymond Mancy wrote:
----- Original Message -----
From: "Nick Coghlan" ncoghlan@redhat.com To: "beaker-devel" beaker-devel@lists.fedorahosted.org Sent: Tuesday, November 5, 2013 1:03:09 PM Subject: [Beaker-devel] Beaker 0.15.x missing from beaker-project.org RHEL repos
Looks like even though we got the 0.15.1 RPM upload issues sorted out last week, the metadata for the RedHatEnterpriseLinux repos on beaker-project.org still shows 0.14.2 as the latest version :(
The Fedora repos appear fine, almost certainly due to the fact that those are generated differently.
Yes, it is specific to anything that is handled by our build scripts. The problem is that running 'make' will build the repos from packaged in brew, and existing repos that has 0.15.1 rpms (el5/el6) would be overwritten and 0.15.1 removed.
In future instances (technically only needed for when upstream is not in brew), we just have to make sure to do it in two steps always:
make createrepo --update --no-database -o <repodata_dir>
<rpm_dir>
This will ensure that as long as the latest RPMs reside in <rpm_dir>, the repos will be generated correctly.
Does that need to be run on the appropriate OS version to include the right RPMs?
Cheers,
Heh, yes :-)
So what you end up needing to do is something like this:
createrepo --update --no-database --includepkg beaker-client-0.15.1-1.el5.noarch.rpm --includepkg beaker-0.15.1-1.el5.noarch.rpm -o . ../../rpms/
Which would be a pita if we had to do it at all that often. I'll update the docs though for when we are in this situation again.
Nick.
Nick Coghlan Red Hat Infrastructure Engineering & Development, Brisbane
Testing Solutions Team Lead Beaker Development Lead (http://beaker-project.org/) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJSeH6AAAoJEHEkJo9fMO/LbusH/2kxaEJZgkPTICQb/8A/J8FX umds///xYZDdP2gYB94CnBP1OgQUs3QqGKL8nCY2I7E1hJNgDiugYfFHntAoe5WE jpjNVbUIvJeqvHcNj0U++jNzBSMdtBRAmkPKl27U0wofBMcOvMQRGC2L3EN+xMN9 CjoT1DQyQT21F1/pD1SZ1BMVDau6+oXRQg/vGZDqKBiodAy8i5gPGZLaQyfRas8O FJ/dt75X4VULLi2YbOi8L5A9qb+iAXGjEc0dSUs41VQkhNLupQJ7d+eyrVf8hE4J ImAotEHDgKTwtWaO3Im+CyhOoCPfI1xtACdgnVgLFyS5ebV6rJ74ZLLByns8BMY= =xkqf -----END PGP SIGNATURE----- _______________________________________________ Beaker-devel mailing list Beaker-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/beaker-devel
This doesn't seem to have gotten fixed.
http://beaker-project.org/releases/beaker-0.15.1.tar.gz
Is just 20 bytes.
Cheers, George
On 11/05/2013 12:55 AM, Raymond Mancy wrote:
----- Original Message -----
From: "Nick Coghlan" ncoghlan@redhat.com To: beaker-devel@lists.fedorahosted.org Sent: Tuesday, November 5, 2013 3:13:36 PM Subject: Re: [Beaker-devel] Beaker 0.15.x missing from beaker-project.org RHEL repos
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/05/2013 02:52 PM, Raymond Mancy wrote:
----- Original Message -----
From: "Nick Coghlan" ncoghlan@redhat.com To: "beaker-devel" beaker-devel@lists.fedorahosted.org Sent: Tuesday, November 5, 2013 1:03:09 PM Subject: [Beaker-devel] Beaker 0.15.x missing from beaker-project.org RHEL repos
Looks like even though we got the 0.15.1 RPM upload issues sorted out last week, the metadata for the RedHatEnterpriseLinux repos on beaker-project.org still shows 0.14.2 as the latest version :(
The Fedora repos appear fine, almost certainly due to the fact that those are generated differently.
Yes, it is specific to anything that is handled by our build scripts. The problem is that running 'make' will build the repos from packaged in brew, and existing repos that has 0.15.1 rpms (el5/el6) would be overwritten and 0.15.1 removed. In future instances (technically only needed for when upstream is not in brew), we just have to make sure to do it in two steps always: make createrepo --update --no-database -o <repodata_dir>
<rpm_dir> This will ensure that as long as the latest RPMs reside in <rpm_dir>, the repos will be generated correctly.
Does that need to be run on the appropriate OS version to include the right RPMs?
Cheers,
Heh, yes :-)
So what you end up needing to do is something like this:
createrepo --update --no-database --includepkg beaker-client-0.15.1-1.el5.noarch.rpm --includepkg beaker-0.15.1-1.el5.noarch.rpm -o . ../../rpms/
Which would be a pita if we had to do it at all that often. I'll update the docs though for when we are in this situation again.
Nick.
Nick Coghlan Red Hat Infrastructure Engineering & Development, Brisbane
Testing Solutions Team Lead Beaker Development Lead (http://beaker-project.org/) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJSeH6AAAoJEHEkJo9fMO/LbusH/2kxaEJZgkPTICQb/8A/J8FX umds///xYZDdP2gYB94CnBP1OgQUs3QqGKL8nCY2I7E1hJNgDiugYfFHntAoe5WE jpjNVbUIvJeqvHcNj0U++jNzBSMdtBRAmkPKl27U0wofBMcOvMQRGC2L3EN+xMN9 CjoT1DQyQT21F1/pD1SZ1BMVDau6+oXRQg/vGZDqKBiodAy8i5gPGZLaQyfRas8O FJ/dt75X4VULLi2YbOi8L5A9qb+iAXGjEc0dSUs41VQkhNLupQJ7d+eyrVf8hE4J ImAotEHDgKTwtWaO3Im+CyhOoCPfI1xtACdgnVgLFyS5ebV6rJ74ZLLByns8BMY= =xkqf -----END PGP SIGNATURE----- _______________________________________________ Beaker-devel mailing list Beaker-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/beaker-devel
Beaker-devel mailing list Beaker-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/beaker-devel
On 11/07/2013 06:24 AM, George Beshers wrote:
This doesn't seem to have gotten fixed.
http://beaker-project.org/releases/beaker-0.15.1.tar.gz
Is just 20 bytes.
Because we were working on 0.14.2 at the same time, the 0.15.1 release had to rely on some tweaks to the regular build and publication process. It looks like those adjustments just plain haven't worked properly :(
Rather than putting more time into fixing them, we'll focus on getting 0.14.3 out the door this week and then do a 0.15.1 build through the normal release process. That should hopefully iron out any glitches seen in the previous attempt.
Cheers, Nick.
Excerpts from George Beshers's message of 2013-11-07 06:24:10 +1000:
This doesn't seem to have gotten fixed.
http://beaker-project.org/releases/beaker-0.15.1.tar.gz
Is just 20 bytes.
I've replaced the tarballs for 0.15.1 so that they are correct now. The other issues with the yum repos will be fixed after 0.14.3 is released.
On 11/12/2013 12:26 PM, Dan Callaghan wrote:
Excerpts from George Beshers's message of 2013-11-07 06:24:10 +1000:
This doesn't seem to have gotten fixed.
http://beaker-project.org/releases/beaker-0.15.1.tar.gz
Is just 20 bytes.
I've replaced the tarballs for 0.15.1 so that they are correct now. The other issues with the yum repos will be fixed after 0.14.3 is released.
Dan has now fixed the RHEL6 repos, but RHEL5 and RHEL7 still have incorrect metadata which means yum won't see the 0.15.1 RPMs until Dan is able to fix them tomorrow. (The Fedora repos were fine from the start).
Moral of the story: things break when you deviate from your normal release processes, even if it seems like a good idea at the time :P
Cheers, Nick.
beaker-devel@lists.fedorahosted.org
-
Dan Callaghan -
George Beshers -
Nick Coghlan -
Raymond Mancy