Learn more about these different git repos.
Other Git URLs
limb is willing to maintain it
http://pkgs.fedoraproject.org/cgit/at-spi.git/commit/?id=eff8848d7573c64848034c1eb81cb164a2a37642
"library no longer used and long EOL" is factually incorrect on the "no longer used" part. dasher uses it currently.
Doesn't dasher work with the newer at-spi2 ?
https://git.gnome.org/browse/dasher/tree/configure.ac#n331 seems to indicate that it does - it has a build dep on atspi-2 pkgconfig file that's shipped in the at-spi2-core-devel package in Fedora.
Even if it does I currently don't have the capacity to try and get a newer dasher snapshot in. The last time I tried 4.11 it was hairy.
Fair enough.
Unfortunately for me something else broke dasher in rawhide, so I was compelled to deal with the newer snapshot. So it currently doesn't depend on at-spi.
Doesn't mean the request for unblocking should be ignored.
Was there already a re-review? Please post the link here.
Replying to [comment:5 till]:
I somehow missed your question last week, sorry.
IMHO a re-review for this would be the height of pointless exercises... If the person who decided (pbrobinson) was at least a bit cordial with his co-maintainers (limb) or the actual users of this library(me), none of this would be necessary.
Actually "dnf repoquery" was what was reporting to me there were no more users in exactly the same way the old yum-utils one did.
With the rebase of dasher to 4.11 and it's support for at-spi2 what is the requirement for unblocking at-spi?
Replying to [comment:7 pbrobinson]: ..
Perhaps there was something broken with repoquery at that time. Currently on f22 repoquery for at-spi gives me:
at-spi-devel-0:1.32.0-14.fc22.i686 at-spi-devel-0:1.32.0-14.fc22.x86_64 at-spi-python-0:1.32.0-14.fc22.x86_64 brltty-at-spi-0:5.2-2.fc22.x86_64 brltty-at-spi-0:5.2-3.fc22.x86_64 dasher-0:4.10.1-15.fc22.x86_64 xmms-1:1.2.11-22.20071117cvs.fc22.x86_64
As limb said in the commit message - LDTP at-spi > at-spi-python -> ldtp
Currently on f22 repoquery for at-spi gives me:
F-22 is irrelevant in this context.
at-spi-devel-0:1.32.0-14.fc22.i686 at-spi-devel-0:1.32.0-14.fc22.x86_64 at-spi-python-0:1.32.0-14.fc22.x86_64
The above are part of the package itself.
brltty-at-spi-0:5.2-2.fc22.x86_64 brltty-at-spi-0:5.2-3.fc22.x86_64
The brltty package now uses at-api2 in F-23+
dasher-0:4.10.1-15.fc22.x86_64
Uses at-spi2 in F-23+
xmms-1:1.2.11-22.20071117cvs.fc22.x86_64
Was an incorrect dependency as it didn't link against at-spi, fixed in F-23+
With the rebase of dasher to 4.11 and it's support for at-spi2 what is the requirement for unblocking at-spi? As limb said in the commit message - LDTP at-spi > at-spi-python -> ldtp
Should use the at-spi2 python bindings.
Replying to [comment:9 pbrobinson]: ...
As limb said in the commit message - LDTP at-spi > at-spi-python -> ldtp Should use the at-spi2 python bindings.
What matters is what it is actually using and not what's most convenient for you to justify your rash retirement of the package on the development branches.
Should use the at-spi2 python bindings. What matters is what it is actually using and not what's most convenient for you to justify your rash retirement of the package on the development branches.
Actually there's been support to use the at-spi2 bindings since 2012 if you look at the ldtp2 upstream git logs
I've just fixed ldtp so there is now no users of this in F-23+
Login to comment on this ticket.