Re: Fedora EPEL - sequoia-sq package and "cli breakages"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jan 13, 2025 at 12:37 PM David Sommerseth <dazo@xxxxxxxxxxxx> wrote:
>
> On 13/01/2025 12:22, Fabio Valentini wrote:
> > This isn't new since December 2024, the sq CLI was*never* stable, and
> > basically every 0.x -> 0.(x+1) release broke some part of the
> > command-line API. The upstream project made it quite explicit that the
> > CLI would only be stable going forward after the 1.0.0 release.
>
> My understanding so far has been that it's the package maintainers
> responsibility to ensure the compatibility is in place.  So if upstream
> break the compatibility, the package maintainer should ensure a package
> upgrade doesn't break.
>
> <https://docs.fedoraproject.org/en-US/epel/epel-policy/#guidelines_and_backgrounds_for_this_policy>
>
> Potentially breaking changes should anyhow be announced.
>
> > With hindsight, it might have been "better" to not provide sq packages
> > for EPEL 9 *at all* until the 1.0.0 release was out. But there was
> > user demand for it, so I built it for EPEL 9, under the assumption
> > that users would know that the sq CLI is not stable yet.
>
> I use Fedora Copr repositories for these use cases myself.  And you can
> in the Copr repo have a clear message about the stability guarantees you
> provide for the packages available there.  Once stable it is considered
> stable, it can be added to EPEL.
>
> Another aspect is that it could probably be highlighted in the package
> summary, like adding a "(currently unstable API)".  That would help when
> searching up the package.
>
> I was generally very happy to see this package in EPEL, as it makes the
> scripting so much simpler and easier than what GnuPG/gpg could ever do.
> But it was just real a smack in the face to starting to receive lots of
> empty mails over the weekend once again after having hit the same issue
> just weeks ago.

I'm sorry about the breakage, but again - using sq < 1.0 you basically
opted in to "this command line interface is unstable, continue at your
own peril" ...
And all that should be moot now anyway, since the CLI will be stable
from 1.0.0 going forward.

Fabio
-- 
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux