Package Details: otf-libertinus-git 6.6.r30.g6f5da00-1

Git Clone URL: (read-only)
Package Base: otf-libertinus-git
Description: Libertinus font family, a fork of Linux Libertine and Linux Biolinum with bugfixes and an OpenType math companion.
Upstream URL:
Licenses: custom: OFL
Conflicts: otf-libertinus
Provides: otf-libertinus
Submitter: aksr
Maintainer: aksr (caleb)
Last Packager: caleb
Votes: 6
Popularity: 0.000001
First Submitted: 2016-01-21 15:28
Last Updated: 2018-09-01 14:02

Latest Comments

1 2 Next › Last »

jmx commented on 2016-03-01 10:15

@aksr, @caleb: Great, thanks to both of you!

caleb commented on 2016-03-01 10:12

@jmx et all: This package's version field now has a semantic relation to the release version numbers.

caleb commented on 2016-02-29 13:54

@jmx Since my package was merged in to this one, I don't have access to fix this. @aksr would you might terribly adding me to the maintainers list so I can straighten this out?

jmx commented on 2016-02-29 12:26

It would also be great to add otf-libertinus (the "stable" package) to the conflicts.

jmx commented on 2016-02-19 18:11

Hi caleb, hi aksr,

I see that the merge has taken place. Would anyone of you mind to change the versioning scheme as it was once intended? This would finally sync this development package to the stable one in terms of versioning.


caleb commented on 2016-01-25 07:27

I filed a merge request. Lets see what comes of that.

caleb commented on 2016-01-25 07:24

@askr I'm a little confused about the methods available in the new AUR-4 repos. Maybe you know how this goes. There used to be a rename option, but I don't see it any more. There is a way to request a "merge", but I'm not sure which repo should be merged into what and how that would affect the git history. Baring knowing how that works, the only way I can think of is to delete this so that I can push the older repo history from scratch. Either way once we get it sorted out lets keep both of us on as co-maintainers for the most timely updates for users.

jmx commented on 2016-01-22 11:51

@caleb: I've also seen the new package... let's hope that its creator will get back to you soon, as this whole thing really has turnend into quite a mess now, with two -git packages and their conflicting versioning.

I have sent a message to my orphan request thread on aur-requests in order to ask them to delete it. It is now pending for moderation, I hope that it gets through soon.

Obviously now, I am also not able to reproduce the issue I had back in November. Once in a while I use to upgrade all my *-git packages with a call to `yaourt -Syua --devel`. When this came to otf-libertine-git, the call to `git describe --long --tags` was failing with a message like 'fatal: no tags found.' It might be a bug with yaourt, as it somehow also managed to create the package when I installed it for the first time, using the date as you'd intended it in your PKGBUILD.

Thanks for adding me as a maintainer here, too.

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.