@sommerfeld - thanks, similar position myself but for mcedit. Builds fine now.
Search Criteria
Package Details: python2-xlib 0.33-2
Package Actions
| Git Clone URL: | https://aur.archlinux.org/python2-xlib.git (read-only, click to copy) |
|---|---|
| Package Base: | python2-xlib |
| Description: | A fully functional X client library (for Python 2) |
| Upstream URL: | https://github.com/python-xlib/python-xlib |
| Licenses: | LGPL-2.1-or-later |
| Submitter: | sommerfeld |
| Maintainer: | None |
| Last Packager: | MarsSeed |
| Votes: | 9 |
| Popularity: | 0.008914 |
| First Submitted: | 2019-12-24 01:03 (UTC) |
| Last Updated: | 2024-04-04 15:33 (UTC) |
Latest Comments
tjbp commented on 2020-01-06 11:28 (UTC)
sommerfeld commented on 2020-01-05 19:52 (UTC)
Sorry for the delay in fixing the PKGBUILD as I was on vacations.
I should give a little backstory: as one can see in the PKGBUILD I am not the original maintainer. The previous one was @foxboron, a known TU with a very active reddit and irc presence.
I hate python2 and hope it eventually dies, but this package is a dependency for a package I care about (acestream-engine) and there is nothing I can do to change that.
When this package disappeared from the AUR, I hopped on #arch on IRC, chatted a bit with @foxboron and found out that he was the one who purposely deleted it since python2 is officially EOL in 2020. He said that if I cared enough, I could take it on, reuse the PKGBUILD from the python3 version (python-xlib), do a 's/python/python2' and publish it on the AUR with my account.
That is exactly what I did. It's my first every AUR package, so I had to learn some stuff. I noticed right away that the 'cd "$pkgname-$pkgver"' was wrong and caused a failure, so I patched the PKGBUILD right away but unfortunately forgot to push the change to the AUR and went on vacation for 2 weeks...
Let's see how this holds up now. I appreciate any help and suggestions.
stooj commented on 2020-01-03 11:19 (UTC) (edited on 2020-01-03 11:20 (UTC) by stooj)
@the_z0id: edit lines 20 and 25 in the PKGBUILD
Change:
cd "$pkgname-$pkgver"
to
cd "python-xlib-$pkgver"
kmvan commented on 2020-01-01 10:31 (UTC)
Need to rename the filename.
the_z0id commented on 2019-12-30 19:44 (UTC)
Knowing this, is there a fix?
KVF commented on 2019-12-28 04:38 (UTC)
fails because the directory is python-xlib-0.26, not python2-xlib-0.26
lemler3 commented on 2019-12-28 03:55 (UTC) (edited on 2019-12-28 03:57 (UTC) by lemler3)
can confirm, the file name is wrong
abouvier commented on 2019-12-26 18:52 (UTC)
cd "$pkgname-$pkgver" fails because the directory is python-xlib-0.26, not python2-xlib-0.26.
Pinned Comments
sommerfeld commented on 2020-01-05 19:52 (UTC)
Sorry for the delay in fixing the PKGBUILD as I was on vacations.
I should give a little backstory: as one can see in the PKGBUILD I am not the original maintainer. The previous one was @foxboron, a known TU with a very active reddit and irc presence.
I hate python2 and hope it eventually dies, but this package is a dependency for a package I care about (acestream-engine) and there is nothing I can do to change that.
When this package disappeared from the AUR, I hopped on #arch on IRC, chatted a bit with @foxboron and found out that he was the one who purposely deleted it since python2 is officially EOL in 2020. He said that if I cared enough, I could take it on, reuse the PKGBUILD from the python3 version (python-xlib), do a 's/python/python2' and publish it on the AUR with my account.
That is exactly what I did. It's my first every AUR package, so I had to learn some stuff. I noticed right away that the 'cd "$pkgname-$pkgver"' was wrong and caused a failure, so I patched the PKGBUILD right away but unfortunately forgot to push the change to the AUR and went on vacation for 2 weeks...
Let's see how this holds up now. I appreciate any help and suggestions.