Package Details: libturpial-git

Git Clone URL: (read-only, click to copy)
Package Base: libturpial-git
Description: A library that handles multiple microblogging protocols.
Upstream URL:
Licenses: GPL3
Conflicts: libturpial
Provides: libturpial
Submitter: lucaswerkmeister
Maintainer: lucaswerkmeister
Last Packager: lucaswerkmeister
Votes: 4
Popularity: 0.000000
First Submitted: 2015-08-09 15:23 (UTC)
Last Updated: 2015-08-09 15:52 (UTC)

Required by (0)

Sources (1)

Latest Comments

MarsSeed commented on 2022-06-30 11:58 (UTC) (edited on 2022-06-30 11:59 (UTC) by MarsSeed)

Thanks for your response, you are most helpful and reasonable. :)

Yes, it is a good idea to seek others' opinion first.

Btw, I've just found out, as I am also not a subscriber/member of the AUR/Arch mailing lists, that it is quite problematic.

When replying to AUR requests, my emails are not received by the list server, but silently rejected. That means others don't see my responses I send.

Also, it seems I also don't receive the responses of others if they only reply to the aur-requests address and not forward it to mine.

The only way for me to send something to the aur-requests list is via the AURweb interface, i.e. if I submit a request, or if I revoke (close) a request I've sent in earlier.

The only way for me to receive info is if a responder cc's their email directly to me, or when a TU closes my request with an acceptance or a rejection.

So I've just realized after 6 months of active AUR community participation that I really should subscribe to the relevant lists! ':-)

lucaswerkmeister commented on 2022-06-30 07:47 (UTC)

(The deletion request is here now: – it wasn’t in the archive yet when I wrote my previous comment)

But what do you mean you requested "to point this package to the python3 branch"? That is only possible if someone edits the PKGBUILD, in essence, porting it to the Python 3 fork.

Yes, I would do that, since I’m still the package maintainer :) but I think it’s a good idea to discuss it first, together with the package deletions.

MarsSeed commented on 2022-06-30 03:33 (UTC) (edited on 2022-06-30 03:34 (UTC) by MarsSeed)

Btw, I might have overestimated the momentum of the Python 3 "revival".

It seems there were only a few pull requests by one person that got merged recently for Python 3 in the libturpial repo.

Also, it seems the repo owner themself still does no work on their project. And in the GUI repo (turpial), I see no change.

So this project still seems to be pretty much dead. It would need a huge amount of work to make it functional again.

Therefore deletion is an apt decision I think.

MarsSeed commented on 2022-06-30 03:32 (UTC)

Thanks for the notice. Deletion is fine with me. It seems there is no observable demand for this package here.

But what do you mean you requested "to point this package to the python3 branch"? That is only possible if someone edits the PKGBUILD, in essence, porting it to the Python 3 fork.

lucaswerkmeister commented on 2022-06-29 19:26 (UTC)

I submitted a deletion request (PRQ#36123) proposing to delete turpial, turpial-git and libturpial, and to then point this package to the python3 branch just in case someone finds it useful.

MarsSeed commented on 2022-06-28 17:25 (UTC)

I don't use Turpial myself, so I wouldn't know if it works or if it is needed by anything else.

I am just trying to facilitate moving packages off Python 2 dependencies if possible.

lucaswerkmeister commented on 2022-06-04 14:54 (UTC)

Huh, I wasn’t aware libturpial was still being developed… is the Python 3 version used by anything? ( doesn’t seem to have any active branches.)

I’m also happy to hand this package over to you, if you want to adopt it.

MarsSeed commented on 2022-06-04 01:55 (UTC) (edited on 2022-06-04 01:55 (UTC) by MarsSeed)

The project has a new python3 branch so I think at this point this package should be switched over to that: