Arch Linux User Repository

Ah sorry for the delay, and now it works again.

@irb: Ah seems it changed again, I'll update PKGBUILD tomorrow, thanks for the report :)

In the pkgver() function, there's a sed line that causes the build to fail:

sed -n '1s/[^[:digit:]]//gp' src/version.py

there is no "version.py" in src/.

now the merge requests have been accepted, and I've rewrited the pkgbuild,

and after installation, you can safely remove limnoria-python3-git yourself,

or wait for a month (transition period) and I'll remove it in the next update.

I've submitted merge requests a day ago, and TUs haven't fulfilled them, so I guess it's better to write my solution here first (PKGBUILD has been rewrited indeed):

E.g. for limnoria-git & limnoria-python3-git, I make a package base named limnoria-git to build both package, where limnoria-git contains all the data file, and limnoria-python3-git is just an empty package that make it easier for previous users to upgrade using aur managers.

And after the period of transition (a month is enough I guess), I'll push the second version that only build limnoria-git, and also put limnoria-python3-git into "replaces" array, to safely remove it.

@sanerb:

thanks for the notice :)

to be exact I have 2 limnoria packages that work with python 2 and 3 (limnoria-python3 to be exact),

so now I need to find a way to make it easier for users of another package to migrate,

I'll deal with it in a day or 2 I guess, hmm

limnoria now no longer supports python2. Please modify the PKGBUILD to build with python3.

@irb ok, fixed, thanks for your report :)

This package installs with the version string "%s.10974.0d627c05-1" which I don't think is right, since it says it's going to install "0.83.4.1.10347.530c246-1". Perhaps some automation gone awry?

Note: It's not the version itself but the "%s" in the version that I'm curious about.

@Beini:
patch applied, Thanks bro :)