Broken version of wsdd released in EPEL7

[Nick Howitt]

When it was announced that wsdd-0.7.1-1.el7 was available for testing, I 
responded to the announcement that it was a bad installation with 
breaking changes and raised a bug 
https://bugzilla.redhat.com/show_bug.cgi?id=2253415. Unfortunately, my 
bug report and mailing list response have been ignored and now there has 
bee a breaking release. How can we get it fixed and what could I have 
done differently to get it fixed prior to release?

Regards,

Nick

[Nick Howitt]

On 15/12/2023 08:20, Nick Howitt wrote:
> When it was announced that wsdd-0.7.1-1.el7 was available for testing, 
> I responded to the announcement that it was a bad installation with 
> breaking changes and raised a bug 
> https://bugzilla.redhat.com/show_bug.cgi?id=2253415. Unfortunately, my 
> bug report and mailing list response have been ignored and now there 
> has bee a breaking release. How can we get it fixed and what could I 
> have done differently to get it fixed prior to release?
>
> Regards,
>
> Nick

Not only are the changes breaking, but it can never run in the released 
state because it looks for its parameters in /etc/defaults/wsdd, but 
creates them in /etc/sysconfig/wsdd leading to an immediate failure on 
start.

[Troy Dawson]

The way to stop it from being pushed is to give it negative karma in it's
bodhi testing.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-4e7c9d636e

You know what's strange, the updates-testing report that get's
automatically generated, doesn't put the bodhi link in for the new
packages.  It gives all sorts of details about the new package, but not the
bodhi testing link.
But it does give the link for the older packages.

On Fri, Dec 15, 2023 at 12:20 AM Nick Howitt via epel-devel <
[e-mail]> wrote:
> When it was announced that wsdd-0.7.1-1.el7 was available for testing, I
> responded to the announcement that it was a bad installation with
> breaking changes and raised a bug
> https://bugzilla.redhat.com/show_bug.cgi?id=2253415. Unfortunately, my
> bug report and mailing list response have been ignored and now there has
> bee a breaking release. How can we get it fixed and what could I have
> done differently to get it fixed prior to release?
>
> Regards,
> Nick
>
> epel-devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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]...
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

[Nick Howitt]

I'll see if I can remember that next time.

In the meanwhile, how does it get fixed? Does the package get pulled and 
0.7.0-1 re-released until the maintainer builds, perhaps, a 0.7.1-2? 
Obviously, untagging 0.7.1 and re-tagging 0.7.0 won't help anyone who 
has already picked up the update.

On 15/12/2023 14:46, Troy Dawson wrote:
> The way to stop it from being pushed is to give it negative karma in 
> it's bodhi testing.
> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-4e7c9d636e
>
> You know what's strange, the updates-testing report that get's 
> automatically generated, doesn't put the bodhi link in for the new 
> packages.  It gives all sorts of details about the new package, but 
> not the bodhi testing link.
> But it does give the link for the older packages.
>
> On Fri, Dec 15, 2023 at 12:20 AM Nick Howitt via epel-devel 
>  wrote:
> When it was announced that wsdd-0.7.1-1.el7 was available for
> testing, I
> responded to the announcement that it was a bad installation with
> breaking changes and raised a bug
> https://bugzilla.redhat.com/show_bug.cgi?id=2253415.
> Unfortunately, my
> bug report and mailing list response have been ignored and now
> there has
> bee a breaking release. How can we get it fixed and what could I have
> done differently to get it fixed prior to release?
>
> Regards,
>
>
> Nick
> --
> _______________________________________________
> epel-devel mailing list -- [e-mail]
> To unsubscribe send an email to
> [e-mail]
> 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]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
>
> --
> _______________________________________________
> epel-devel mailing list [e-mail]
> To unsubscribe send an email [e-mail]
> 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]...
> Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue