FBR: Move python-blivet-3.1.0-2.fc29 from FEDORA-2018-85853d46b5 to FEDORA-2018-f16a71bc92
Context: https://pagure.io/releng/issue/7825
In order to fix that issue, I propose running the following commands on bodhi-backend01:
$ sudo -u apache pshell /etc/bodhi/production.ini 2018-09-18 16:09:51,892 INFO [bodhi][MainThread] Using the FakeBugTracker
2018-09-18 16:09:51,892 DEBUG [bodhi][MainThread] Using DevBuildsys 2018-09-18 16:10:26,842 INFO [bodhi.server][MainThread] Bodhi ready and at your service!
Python 3.6.6 (default, Jul 19 2018, 14:25:17)
[GCC 8.1.1 20180712 (Red Hat 8.1.1-5)] on linux
Type "help" for more information.
Environment:
app The WSGI application.
registry Active Pyramid registry.
request Active request object.
root Root of the default resource tree.
root_factory Default root factory used to create `root`.
Custom Variables:
m bodhi.server.models
s bodhi.server.Session
blivet = m.Build.query.filter_by(nvr='python-blivet-3.1.0-2.fc29').one() update = m.Update.query.filter_by(alias='FEDORA-2018-85853d46b5').one() update.builds.remove(blivet) update.comment(m.Session(), "python-blivet-3.1.0-2.fc29 has been removed from this update.", author='bowlofeggs') m.Session().commit()
The output above was taken from a practice run I did in Bodhi's development environment.
+1's?
On Tue, 18 Sep 2018 at 12:19, Randy Barlow bowlofeggs@fedoraproject.org wrote:
Context: https://pagure.io/releng/issue/7825
blivet = m.Build.query.filter_by(nvr='python-blivet-3.1.0-2.fc29').one() update = m.Update.query.filter_by(alias='FEDORA-2018-85853d46b5').one() update.builds.remove(blivet) update.comment(m.Session(), "python-blivet-3.1.0-2.fc29 has been removed from this update.", author='bowlofeggs') m.Session().commit()
I see this removing it from 85853d46b5 but how does it connect to the other update?
On 9/18/18 12:22 PM, Stephen John Smoogen wrote:
I see this removing it from 85853d46b5 but how does it connect to the other update?
Hi Smooge!
I'm trying to do the minimum amount needed in the FBR, so I plan to use Bodhi's normal features after doing this to add the build to the other update, using my proven packager privileges (i.e., I'll just use the pointy-clicky web UI to do that part). I *could* do that here too, but in the spirit of the freeze I thought it'd be better to minimize what I do on a Python shell like this. Unfortunately, there isn't a way to use Bodhi's normal features to do this bit, so this part just has to be done in this kinda ugly way.
On Tue, 18 Sep 2018 at 12:30, Randy Barlow bowlofeggs@fedoraproject.org wrote:
On 9/18/18 12:22 PM, Stephen John Smoogen wrote:
I see this removing it from 85853d46b5 but how does it connect to the other update?
Hi Smooge!
I'm trying to do the minimum amount needed in the FBR, so I plan to use Bodhi's normal features after doing this to add the build to the other update, using my proven packager privileges (i.e., I'll just use the pointy-clicky web UI to do that part). I *could* do that here too, but in the spirit of the freeze I thought it'd be better to minimize what I do on a Python shell like this. Unfortunately, there isn't a way to use Bodhi's normal features to do this bit, so this part just has to be done in this kinda ugly way.
No problem. I just wanted to make sure that all the commands were there that were needed and something didn't get dropped. +1
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
+1 here.
kevin
Also the formatting on this e-mail was terrible. Sorry for that. Next time I'll just attach a file so Thunderbird doesn't try to get too smart.
This FBR is applied on production.
infrastructure@lists.fedoraproject.org
-
Kevin Fenzi -
Randy Barlow -
Stephen John Smoogen