Created attachment 2539 [details] spec file for ahuramazda fonts Hello, coud you package ahuramazda font please? With it, we can read Avestan script. You have an example here: https://en.wikipedia.org/wiki/Avestan_alphabet I attach a spec file for this package. It works fine for me.
URL: (none) => http://www.skytower.org/~ernstjtremel/Ahuramazda/AhuramzdaFont.htmSource RPM: (none) => fonts-ttf-ahuramazda
Severity: normal => enhancement
@ Olivier Please tell us whether you still need this font. I'm now assigning this report to the new default assignee for package requests, but wouldn't want anyone to spend time on it if it is no longer needed.
Keywords: (none) => NEEDINFOCC: (none) => marja11Assignee: bugsquad => pkg-bugs
Yes, I still would like to have this font packaged.
(In reply to Olivier Delaune from comment #2) > Yes, I still would like to have this font packaged. OK, I wish I had time to help with that, to me it is very important that we have at least one font for each different script/alphabet. @ Shlomi Would you maybe manage to make some time?
Keywords: NEEDINFO => (none)CC: (none) => shlomif
(In reply to Marja van Waes from comment #3) > (In reply to Olivier Delaune from comment #2) > > Yes, I still would like to have this font packaged. > > OK, I wish I had time to help with that, to me it is very important that we > have at least one font for each different script/alphabet. > > @ Shlomi > > Would you maybe manage to make some time? I think I could - I'll keep you posted.
@Olivier: thanks for your contribution. However, I ran into some problems with your .spec file. First of all, I was unable to find the Ahuramazda-Avestan-Font-%{version}.zip file (due to the fact the version is 1.0) and after I downloaded the .zip file from http://www.skytower.org/~ernstjtremel/Ahuramazda/AhuramzdaFont.htm and renamed it I got an error that the directory could not be found. It also had a BuildRoot: directive that is no longer necessary, and a bogus date (9 July 2012 was not a Friday - http://www.dayoftheweek.org/?m=July&d=9&y=2012&go=Go ). Anyway, I corrected the problems and submitted the package to Cauldron. See: http://pkgsubmit.mageia.org/ . @Marja: should we package it for mga v5 too?
(In reply to Shlomi Fish from comment #5) @Marja: should we package it for mga v5 too? That would be nice :-) I suppose it can only go into backports?
(In reply to Marja van Waes from comment #6) > (In reply to Shlomi Fish from comment #5) > > @Marja: should we package it for mga v5 too? > > That would be nice :-) > > I suppose it can only go into backports? I don't know. Is the backports repository functional?
Also - since this bug is filed against cauldron - can I resolved/fixed it?
(In reply to Shlomi Fish from comment #8) > Also - since this bug is filed against cauldron - can I resolved/fixed it? yes, of course. I forgot that backporting it will take some effort of QA team, too, while there is a good chance that the mga6 package will install fine in mga5
Status: NEW => RESOLVEDResolution: (none) => FIXED