satyr soname bump

[Ernestas Kulik]

satyr 0.30 was built with a bumped soname. AFAIK, this will only affect
us, but for anyone else out there - beware.

-- 
Ernestas Kulik
Associate Software Engineer - Base Operating Systems (Core
Services/ABRT)
Red Hat Czech, s.r.o.

[Igor Gnatenko]

What does it mean "us? I see that ABRT has broken dependencies in
rawhide. I would appreciate if you could use side tag to build new
version + rebuild all packages which depend on it in there.

On Thu, Feb 6, 2020 at 3:15 PM Ernestas Kulik <ekulik(a)redhat.com&gt; wrote:
>
> satyr 0.30 was built with a bumped soname. AFAIK, this will only affect
> us, but for anyone else out there - beware.
>
> --
> Ernestas Kulik
> Associate Software Engineer - Base Operating Systems (Core
> Services/ABRT)
> Red Hat Czech, s.r.o.
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-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 Fri, Feb 07, 2020 at 07:17:51AM +0100, Igor Gnatenko wrote:
>  What does it mean "us? I see that ABRT has broken dependencies
> in
>  rawhide. I would appreciate if you could use side tag to build new
>  version + rebuild all packages which depend on it in there. 
So, this was breaking rawhide composes as well... 

I have untagged libreport-2.12.0-1.fc32 and satyr-0.30-1.fc32 for now
and hopefully we can get a compose.

https://pagure.io/releng/failed-composes/issue/963

kevin
--
>  
>  On Thu, Feb 6, 2020 at 3:15 PM Ernestas Kulik <ekulik(a)redhat.com&gt; wrote:
>  >
>  > satyr 0.30 was built with a bumped soname. AFAIK, this will only affect
>  > us, but for anyone else out there - beware.
>  >
>  > --
>  > Ernestas Kulik
>  > Associate Software Engineer - Base Operating Systems (Core
>  > Services/ABRT)
>  > Red Hat Czech, s.r.o.
>  > _______________________________________________
>  > devel mailing list -- devel(a)lists.fedoraproject.org
>  > To unsubscribe send an email to devel-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]
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-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]

[Ernestas Kulik]

On Fri, 2020-02-07 at 07:17 +0100, Igor Gnatenko wrote:
>  What does it mean "us? I see that ABRT has broken dependencies
> in
>  rawhide. I would appreciate if you could use side tag to build new
>  version + rebuild all packages which depend on it in there. 
I don’t know, seems pretty self-explanatory to me what “us” is.

We were using overrides, since it’s just a handful of packages. I
suppose not everything was built yesterday, so we have a situation now.

-- 
Ernestas Kulik
Associate Software Engineer - Base Operating Systems (Core
Services/ABRT)
Red Hat Czech, s.r.o.

[Fabio Valentini]

On Fri, Feb 7, 2020 at 8:25 AM Ernestas Kulik <ekulik(a)redhat.com&gt; wrote:
>  On Fri, 2020-02-07 at 07:17 +0100, Igor Gnatenko wrote:
>  > What does it mean "us? I see that ABRT has broken dependencies in
>  > rawhide. I would appreciate if you could use side tag to build new
>  > version + rebuild all packages which depend on it in there.
>
>  I don’t know, seems pretty self-explanatory to me what “us” is. 
(snip)

>  We were using overrides, since it’s just a handful of packages. I
>  suppose not everything was built yesterday, so we have a situation now. 
You were using buildroot overrides on *rawhide*?
Last time I read about this, that didn't work as expected and even
caused builds to be stuck and mis-tagged in koji.

If creating overrides in rawhide still works, can we teach bodhi some
logic to deny creating buildroot overrides "if not
release.composed_by_bodhi" or something?

Fabio

> --
> Ernestas Kulik
> Associate Software Engineer - Base Operating Systems (Core
> Services/ABRT)
> Red Hat Czech, s.r.o.
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-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]