FBR: hotfix robosignatory to fix ostree signing issue

[Dusty Mabe]

We hit a bug every release where the directories haven't yet been
created for the refs we want to sign [1]. The bug has been fixed in
the latest code [2] but hasn't been deployed to prod yet.

We'd like to deploy that small patch to prod so we can make sure
we never hit this again.

Dusty

[1] https://pagure.io/robosignatory/issue/19
[2]
https://pagure.io/robosignatory/c/f462fc2c81b7cad15acb2da630c69114b30ef3d...

[Mohan Boddu]

+1 to build the package and update the box with the newer rpm.

On Thu, Aug 29, 2019 at 2:25 PM Dusty Mabe <dusty(a)dustymabe.com&gt; wrote:

>  We hit a bug every release where the directories haven't yet
> been
>  created for the refs we want to sign [1]. The bug has been fixed in
>  the latest code [2] but hasn't been deployed to prod yet.
>
>  We'd like to deploy that small patch to prod so we can make sure
>  we never hit this again.
>
>  Dusty
>
>  [1] https://pagure.io/robosignatory/issue/19
>  [2]
>  https://pagure.io/robosignatory/c/f462fc2c81b7cad15acb2da630c69114b30ef3d...
>  _______________________________________________
>  infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
>  To unsubscribe send an email to
>  infrastructure-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]...
>

[Clement Verna]

We have changed robosignatory to use fedora-messaging in some of the last
commits. I am not sure if this was deployed to prod but I assume not so
that maybe something to keep in mind.

On Thu, Aug 29, 2019, 20:35 Mohan Boddu <mboddu(a)bhujji.com&gt; wrote:

>  +1 to build the package and update the box with the newer rpm.
>
>  On Thu, Aug 29, 2019 at 2:25 PM Dusty Mabe <dusty(a)dustymabe.com&gt; wrote:
>
> > We hit a bug every release where the directories haven't yet been
> > created for the refs we want to sign [1]. The bug has been fixed in
> > the latest code [2] but hasn't been deployed to prod yet.
> >
> > We'd like to deploy that small patch to prod so we can make sure
> > we never hit this again.
> >
> > Dusty
> >
> > [1] https://pagure.io/robosignatory/issue/19
> > [2]
> >
> https://pagure.io/robosignatory/c/f462fc2c81b7cad15acb2da630c69114b30ef3d...
> > _______________________________________________
> > infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
> > To unsubscribe send an email to
> > infrastructure-leave(a)lists.fedoraproject.org
> > Fedora Code of Conduct:
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> > https://lists.fedoraproject.org/archives/list/[e-mail]...
> >
>  _______________________________________________
>  infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
>  To unsubscribe send an email to
>  infrastructure-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]...
>

[Kevin Fenzi]

On 8/29/19 11:48 AM, Clement Verna wrote:
>  We have changed robosignatory to use fedora-messaging in some of the
> last
>  commits. I am not sure if this was deployed to prod but I assume not so
>  that maybe something to keep in mind. 
Yeah, I saw there were a ton of commits, but I don't think we want to
upgrade all that much, just the one we have now + this simple patch.

We can look at upgrading it to the new major version after freeze.

kevin
--
>  
>  On Thu, Aug 29, 2019, 20:35 Mohan Boddu <mboddu(a)bhujji.com&gt; wrote:
>  
> > +1 to build the package and update the box with the newer rpm.
> >
> > On Thu, Aug 29, 2019 at 2:25 PM Dusty Mabe <dusty(a)dustymabe.com&gt; wrote:
> >
> >> We hit a bug every release where the directories haven't yet been
> >> created for the refs we want to sign [1]. The bug has been fixed in
> >> the latest code [2] but hasn't been deployed to prod yet.
> >>
> >> We'd like to deploy that small patch to prod so we can make sure
> >> we never hit this again.
> >>
> >> Dusty
> >>
> >> [1] https://pagure.io/robosignatory/issue/19
> >> [2]
> >>
> https://pagure.io/robosignatory/c/f462fc2c81b7cad15acb2da630c69114b30ef3d...
> >> _______________________________________________
> >> infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
> >> To unsubscribe send an email to
> >> infrastructure-leave(a)lists.fedoraproject.org
> >> Fedora Code of Conduct:
> >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> >> List Archives:
> >>
> https://lists.fedoraproject.org/archives/list/[e-mail]...
> >>
> > _______________________________________________
> > infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
> > To unsubscribe send an email to
> > infrastructure-leave(a)lists.fedoraproject.org
> > Fedora Code of Conduct:
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> > https://lists.fedoraproject.org/archives/list/[e-mail]...
> >
>  
>  
>  _______________________________________________
>  infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
>  To unsubscribe send an email to infrastructure-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]...
>

[Kevin Fenzi]

On 8/29/19 11:24 AM, Dusty Mabe wrote:
>  We hit a bug every release where the directories haven't yet
> been
>  created for the refs we want to sign [1]. The bug has been fixed in
>  the latest code [2] but hasn't been deployed to prod yet.
>  
>  We'd like to deploy that small patch to prod so we can make sure
>  we never hit this again.
>  
>  Dusty
>  
>  [1] https://pagure.io/robosignatory/issue/19
>  [2]
> https://pagure.io/robosignatory/c/f462fc2c81b7cad15acb2da630c69114b30ef3d...
+1 here also. I have already built the package. :)

kevin