Request to remove inactive software KVM projects

rizzitello commented

2026-07-14 12:33:27 +00:00

Hello,
I am one of the maintainers of Deskflow and I would like to request the removal of the barrier and input-leap packages from future releases. Both of these have been replaced by deskflow. Deskflow can connect to the older versions as well. The settings files do not automatically convert.

Why remove Barrier

Inactive project this project has been in active for several years. repo
It was never setup to use xdg-portals and will fail without X11 sessions
This project was replaced by input-leap; Various bugs have been fixed in Input-Leap including several security related issues.

Why Remove Input-Leap

Inactive for over a year repo
does not fully support xdg-portals (missing for example clipboard support w/ newer libportals)
Various bugs have been fixed in Deskflow, including several security related issues.

Hello, I am one of the maintainers of [Deskflow](https://github.com/deskflow/deskflow) and I would like to request the removal of the `barrier` and `input-leap` packages from future releases. Both of these have been replaced by `deskflow`. Deskflow can connect to the older versions as well. The settings files do not automatically convert. Why remove Barrier 1. Inactive project this project has been in active for several years. [repo](https://github.com/debauchee/barrier) 2. It was never setup to use xdg-portals and will fail without X11 sessions 3. This project was replaced by input-leap; Various bugs have been fixed in Input-Leap including several security related issues. Why Remove Input-Leap 1. Inactive for over a year [repo](https://github.com/input-leap/input-leap) 2. does not fully support xdg-portals (missing for example clipboard support w/ newer libportals) 3. Various bugs have been fixed in Deskflow, including several security related issues.

ngompa added the

meeting

label

2026-07-14 12:45:38 +00:00

ngompa commented

2026-07-14 12:46:43 +00:00

Owner

As the deskflow maintainer, I can add the requisite Obsoletes+Provides stanzas for the two packages in deskflow to guarantee the replacement.

As the `deskflow` maintainer, I can add the requisite Obsoletes+Provides stanzas for the two packages in `deskflow` to guarantee the replacement.

gotmax23 commented

2026-07-14 14:01:42 +00:00

Owner

Have the maintainers of barrier and input-leap been consulted? I don't like the idea of FESCo unilaterally removing packages just because there's (potentially) a better alternative.

As the deskflow maintainer, I can add the requisite Obsoletes+Provides stanzas for the two packages in deskflow to guarantee the replacement.

It sounds like adding Provides would be incorrect, since "the settings files do not automatically convert," so they are not drop-in compatible. Obsoletes, maybe, but we usually only add those as a last resort in the case of unresolvable dependencies or other serious issues.

Have the maintainers of barrier and input-leap been consulted? I don't like the idea of FESCo unilaterally removing packages just because there's (potentially) a better alternative. > As the deskflow maintainer, I can add the requisite Obsoletes+Provides stanzas for the two packages in deskflow to guarantee the replacement. It sounds like adding Provides would be incorrect, since "the settings files do not automatically convert," so they are not drop-in compatible. Obsoletes, maybe, but we usually only add those as a last resort in the case of unresolvable dependencies or other serious issues.

👍 1

ngompa commented

2026-07-14 16:32:21 +00:00

Owner

Well, if the packages are retired, then obsoletes are required somewhere.

Well, if the packages are retired, then obsoletes are required _somewhere_.

zbyszek commented

2026-07-14 16:55:53 +00:00

Owner

barrier is shown as a fork of deskflow in the upstream repo on github. The project is dormant. The fedora package had last update (apart from mass rebuilds and tree-wide fixes) 4 years ago. Retiring seems reasonable.

input-leap upstream was active in November 2025, and the Fedora package has seen updates too.

In both cases, we should get input from the maintainers. @dchen, @aekoroglu, opinions?

`barrier` is shown as a fork of deskflow in the upstream repo on github. The project is dormant. The fedora package had last update (apart from mass rebuilds and tree-wide fixes) 4 years ago. Retiring seems reasonable. `input-leap` upstream was active in November 2025, and the Fedora package has seen updates too. In both cases, we should get input from the maintainers. @dchen, @aekoroglu, opinions?

gotmax23 commented

2026-07-14 19:56:26 +00:00

Owner

ngompa wrote in #3644 (comment):

Well, if the packages are retired, then obsoletes are required somewhere.

Not necessarily.

ngompa wrote in https://forge.fedoraproject.org/fesco/tickets/issues/3644#issuecomment-1062446: > Well, if the packages are retired, then obsoletes are required _somewhere_. Not necessarily.

ngompa commented

2026-07-14 19:59:21 +00:00

Owner

Eventually, yes. Because they aren't getting rebuilt with new dependencies and it will eventually cause a system upgrade failure.

kevin commented

2026-07-14 21:14:56 +00:00

Owner

https://src.fedoraproject.org/rpms/fedora-obsolete-packages probibly. But anyhow, I support trying to talk to the maintainers first before asking fesco to do anything here.

dchen commented

2026-07-15 00:19:14 +00:00

I am dchen. Since I no longer use barrier, thus I agree that we can retire barrier.

Nowadays I use deskflow

I am dchen. Since I no longer use barrier, thus I agree that we can retire barrier. Nowadays I use deskflow

👍 1

salimma commented

2026-07-20 17:58:37 +00:00

Owner

So that leaves input-leap. IIRC the maintainer does not always check Bugzilla, let me loop him in

aekoroglu commented

2026-07-21 05:44:53 +00:00

+1 to remove barrier + input-leap

zbyszek commented

2026-07-21 12:09:31 +00:00

Owner

OK, so we have agreement from all the parties. I'll add this to the meeting agenda for today so that we can have a quick vote.

zbyszek commented

2026-07-21 19:48:36 +00:00

Owner

This was discussed during the meeting today:
AGREED: barrier and input-leap will be retired (without Provides being added) (+5, 0, 0)\

I retired both packages.

This was discussed during the meeting today: AGREED: barrier and input-leap will be retired (without Provides being added) (+5, 0, 0)\ I retired both packages.

zbyszek

2026-07-21 19:48:37 +00:00

closed this issue
added
Status
Accepted
and removed
meeting
labels

Rows
Columns

Request to remove inactive software KVM projects #3644