Package Details: otf-libertinus-git 6.12.r3.gddf6c2f-1

Git Clone URL: (read-only, click to copy)
Package Base: otf-libertinus-git
Description: The Libertinus font family, a fork of Linux Libertine and Biolinum with OpenType math
Upstream URL:
Licenses: OFL
Conflicts: otf-libertinus
Provides: otf-libertinus
Submitter: aksr
Maintainer: aksr (caleb)
Last Packager: caleb
Votes: 6
Popularity: 0.000000
First Submitted: 2016-01-21 15:28
Last Updated: 2020-07-03 14:24

Dependencies (13)

Required by (2)

Sources (1)

Pinned Comments

caleb commented on 2020-02-24 06:22

PSA: I've started hosting this as a prebuilt package in my repository for those that want to install it using pacman without messing around with building from the AUR.

Latest Comments

« First ‹ Previous 1 2 3

caleb commented on 2016-01-22 11:36

@jmx Sorry I didn't get back to you on the versioning issue in November. I was going with the upstream authors use of date strings to refer to his work, and it my testing the pkgver function wasn't disrupting installation. I'm kind of curious why I wasn't able to replicate the issue you had, but at some point I forgot to go back and respond. An out of date flag might have helped there, but no worries. You'll also listed on this package now. Also I'm trying to sort out what to do about the package rename issue. I have a fix for it here but I can't push it because somebody else claimed the otf-libertinus-git package name earlier today. I'd like to get this one renamed and the obsoletes stuff worked out but can't do it from this end with that package in the way. Alternatively they need to fix up that package and maybe a merge will clean up the mess.

jmx commented on 2016-01-22 11:20

Hi caleb,

I had already pinged you in November, as you can see down in the comments. You did not react to that, and therefore I thought that you might have lost interest in this package. I was having issues with how you had set the version string back then, which caused yaourt to fail fatally whenever it tried to update otf-libertine-git, because there were no tags upstream then.

So filing an orphan request was not meant to be an act of rudeness or hastiness. Please do not be offended by this. I did file it yesterday, because after I had created the stable package, I wanted to bring both packages in sync again, and to do so I would have needed to become push access to the package.

I see now that I might have also tried to flagged it out of date or email you directly first. I'm sorry for not doing so.

You've just been added as a maintainer for otf-libertinus, so you can keep it up to date as well, if might be absent one day.

Excuse me again for all the noise.

Best, jmx.

caleb commented on 2016-01-22 11:03

I've been maintaining this package under it's original name for some time. The upstream project rename was just announced 13 hours ago, so I'm a little disappointed to find that I can't push a package rename through because this took the name. Is there any chance I could convince you to orphan or delete it so there can be some continuity with the versioning for upgraders? I have a version of the repo to push with the rename and obsoletes and such taken into account (as well as a version scheme that won't conflict as much with the tagged versions).

caleb commented on 2016-01-22 10:35

You filed an orphan request for something that changed in the upstream project just a couple days ago (hours in the case of the rename)? That's a little hasty don't you think? The AUR rules say not to file one until having pinged the maintainer and it has been flagged out of date for a long time. Just for future reference...

I'll be filing to get this renamed as well as submitting updates to the latest upstream changes soon. If you'd like to add me as a co-maintainer to the versioned release package I'd be glad to help catch updates as they happen or when you're indisposed. I do follow the upstream pretty closely and have other ties with the developer, I just happened to be on the road this week until last night.

jmx commented on 2016-01-22 10:18

Hi caleb,
great to hear from you! I already created a otf-libertinus package for the tagged releases yesterday (and I have just it updated to v6.1). I can add your name to the maintainers there, if you want to have push access.
It would be great if you could update the git package as well, then I can revoke my orphan request here.
Best, jmx.

caleb commented on 2016-01-22 10:03

The upstream project has changed names anyway, I will setup packages for both the git and tagged release versions.

jmx commented on 2016-01-21 09:21


could you perhaps reupload your PKGBUILD, as since yesterday there is a git tag in the repo which (for the fist time) makes your pkgver function work as intended. However, the new version 6.0 is smaller than 20150701, so all AUR helpers will constantly inform you that your installed, newer package is outdated. Thank you!


jmx commented on 2015-11-26 13:02

Since there are no git tags upstream (yet), `git describe --long --tags` in `pkgver()` does not give a meaningful result.

The Wiki ( suggests to "use number of revisions since beginning of the history" via

printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)"

instead. Would you mind changing this?

Thanks, jmx.