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
On 13/01/2025 11:52, Clemens Lang wrote:
I don’t think EPEL can reasonably add stability guarantees that
> upstream does not provide except by pinning a package at an old
> version, but that would mean that EPEL would essentially package
> unsupported software.
That's been the practice so far,
Hi,
Has something changed in the Fedora EPEL packaging policy in regards to
package stability?
Since the updates which has arrived since early December 2024, the
updates to sequoia-sq has twice broken my automated scripts.
The first update which broke my scripts changed --recipient-file to
On 08/01/2025 11:04, Miro Hrončok wrote:
On 08. 01. 25 10:27, Daniel P. Berrangé wrote:
On Wed, Jan 08, 2025 at 09:01:33AM -, Hong Xu wrote:
This email follows week 0.step 3 in the nonresponsive
maintainer page:
https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_ma
