#3346 Update Policy Exception Request: crosswords and libipuz
Closed: Accepted a month ago by kevin. Opened 2 months ago by dcavalca.

I'd like to request an update policy exception for the crosswords and libipuz packages (the latter is a library only used by the former). Specifically, I'd like to get crosswords 0.3.14 in f41; this brings over a vastly improved editor, among other things. It also comes with a bump in the libipuz library version and drops s390x support (which I doubt anybody used tbh) in the crosswords package (which is a leaf); s390x support remains in libipuz.


+1

Seems reasonable. If there's no dependent in Fedora the one-week heads up in devel is not needed, right?

❯ fedrq whatrequires -X libipuz
crossword-editor-0.3.13.3-8.fc42.x86_64
crosswords-0.3.13.3-8.fc42.x86_64
crosswords-thumbnailer-0.3.13.3-8.fc42.x86_64

❯ fedrq whatrequires -X libipuz -F source
crosswords

❯ fedrq whatrequires -X libipuz -F source -b f41
crosswords

Note that libipuz Rust stuff in v0.5.1 looks very fishy:
https://gitlab.gnome.org/jrb/libipuz/-/blob/0.5.1/libipuz/rust/Cargo.toml

It depends on two different branches of the GTK bindings at the same time, I don't even know how that compiles ... because it shouldn't. It should depend on either 0.18 or 0.19, not both (also looks like some of those direct dependencies are actually not needed).

Assuming that can be resolved (preferably by moving to 0.19 for everything, v0.18 is deprecated in f42 and I'm planning to file a CP to retire it in f43), I'm +1 for the exception.

Note that libipuz Rust stuff in v0.5.1 looks very fishy:
https://gitlab.gnome.org/jrb/libipuz/-/blob/0.5.1/libipuz/rust/Cargo.toml

It depends on two different branches of the GTK bindings at the same time, I don't even know how that compiles ... because it shouldn't. It should depend on either 0.18 or 0.19, not both (also looks like some of those direct dependencies are actually not needed).

Thanks! Put up https://gitlab.gnome.org/jrb/libipuz/-/merge_requests/81 for that.

Metadata Update from @ngompa:
- Issue tagged with: updates policy exception

2 months ago

Is this a one time request? Or are there expected to be more and this is a request for an ongoing exception?

I'm +1 to a onetime

It's a onetime request.

After a week, as per FESCo voting rules, this request is now marked as APPROVED (+5, 0, 0)

Metadata Update from @kevin:
- Issue tagged with: pending announcement

a month ago

Metadata Update from @kevin:
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

a month ago

Metadata Update from @zbyszek:
- Issue untagged with: pending announcement

a month ago

Log in to comment on this ticket.

Metadata