I was looking briefly into packaging some Puppet modules, and I was
curious if anyone else has gone down this road.
I'm mainly interested in the Puppetlabs modules,
http://forge.puppetlabs.com/users/puppetlabs , since I imagine these
will have the widest user base, although I'm not an expert on Puppet
Module culture :)
Does anyone have suggestions for package naming conventions? It looks
like the upstream modules include the creators' names as part of the
package names, which strikes me as a little verbose from the
perspective of Fedora packaging.
I'm about to upload PackageKit 0.8.2 which bumps soname due to some
removed API. I'll take care of rebuilding gnome-packagekit and apper.
Yell if you have any worries or questions. Thanks.
> On 07/15/2012 06:01 PM, Nicolas Mailhot wrote:
>>>> C. I tried to dispatch the Arabic variants in the Latin family they
>>>> >> designed to complement, but I may have misunderstood the design
>>>> >> available online.
>>> > Please clarify 'dispatch' :-)
>> Kufi with Sans (masquerading as the Arabic block of Droid Sans) and
>> with Serif the same way (see the long fontconfig ruleset I referenced)
>> states Naskh was designed to complement Serif
>> that chromium uses Kufi with Sans
> That may have been the case, but it is my personal understanding that we
> should dispatch Naskh with both Sans and Serif. Kufi is a horrible font
> body text.
So make kufi a separate family and keep the old droid sans arabic for
sans? Or is it also horrible in some way?
Looks like another week where we can skip the meeting - there's no
significant ongoing business besides the anaconda new UI testing, and
we've already discussed that. No-one proposed any topics. If anyone's
feeling terribly sad about missing meetings, do let me know...
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
test-announce mailing list
python-certifi has certificate bundle generated from mozilla. This package
was needed previously by python-requests. Now python-requests no longer
needs this package, it uses system wide cert bundle. I am retiring
python-certifi for good.
Arun S A G
Thanks for the quick answer!
> On 15 July 2012 21:42, Nicolas Mailhot <nicolas.mailhot(a)laposte.net>
>> A. I used a few hundred MiBs of Android git checkout as source.
> That's the canonical source for Droid, yes.
> (The Roboto fonts in that repo has another canonical source,
Well that's one of the unhelpful Google web sites. Its zip informs you:
"You may use the materials in this file without restriction to develop
your apps and to use in your apps."
I haven't the faintest idea what that means legally. If I was mad enough
to package another set of Google fonts, I'd source Roboto from android git
like Droid, where it is clearly tagged with the Apache license.
>> its relationship with android as upstream is unclear
> They are separate projects and while formally have the same parent
> company, they may as well be different companies with no relationship
> beyond their libre license.
Nice clarification! (I suspected as much but the VCS histories were
unclear on when and why changes were propagated from one to the other)
>> C. I tried to dispatch the Arabic variants in the Latin family they were
>> designed to complement, but I may have misunderstood the design info
>> available online.
> Please clarify 'dispatch' :-)
Kufi with Sans (masquerading as the Arabic block of Droid Sans) and Naskh
with Serif the same way (see the long fontconfig ruleset I referenced)
states Naskh was designed to complement Serif
that chromium uses Kufi with Sans
>> E. If the package description does not correctly attribute the main
>> designers involved, please educate me and I'll correct it.
> I'll see if I can find out more about this.
That would be appreciated. I only found descriptions for the new Arabic
>> F. I've zapped DroidSansFallbackFull DroidSansFallbackLegacy
>> DroidSansArabic DroidNaskh-Regular-SystemUI that seemed redundant. If
>> provide something missing in the other files, please tell me what it is
>> and I'll fix the packages.
> The Fallback fonts have CJK glyphs and others character ranges not
> found in the other fonts. The Legacy one can probably be forgotten.
I should have indicated I kept DroidSansFallback (no idea if it's missing
something important compared to DroidSansFallbackFull and
> The UI variants have adjusted vertical metrics to fit the Android UI's
> vertical space limitations.
Ok that means they can be ignored on a desktop.
Thanks for the useful information!
I've just pushed new Droid font packages to Fedora Rawhide.
Droid are complex font families with a difficult upstream and the
following caveats apply:
A. I used a few hundred MiBs of Android git checkout as source. The fonts
are also available in the Google font directory but it does not permit
convenient checkout (one either needs to collect download URLs
file-by-file, or perform a full-repository multi-gig mercurial checkout),
its relationship with android as upstream is unclear, and it has been
known to cut-down fonts to limit their weight when used in CSS files. As
for other web sites, they are generally more convenient, but their
upstream status is unclear, and they love to zap licensing terms to
“simplify” their users' lives (even in Google-sponsored sites). So I
concluded that what was good enough for Android was good enough for us.
B. The fonts follow Keith Packard's “one font per script” ideal but I
seriously question if fontconfig as it exists today is ready to process
such an ideal. Expect to hit bugs in fontconfig or in apps with
approximative fontconfig calls (the first generation of this package
triggered a Chromium bug; Android uses its own font and font fallback tech
so those fonts are not heavily tested in a fontconfig environment).
Fedora fontconfig files for Droid are available here:
C. I tried to dispatch the Arabic variants in the Latin family they were
designed to complement, but I may have misunderstood the design info
D. Lots of new scripts here. i18n and l10n teams probably need to take a
look to decide it that changes font defaults for some locales, and if
compts changes are needed.
E. If the package description does not correctly attribute the main
designers involved, please educate me and I'll correct it.
F. I've zapped DroidSansFallbackFull DroidSansFallbackLegacy
DroidSansArabic DroidNaskh-Regular-SystemUI that seemed redundant. If they
provide something missing in the other files, please tell me what it is
and I'll fix the packages.
And that's all for this notification. Needless to say for this level of
changes those packages will only be available in F18 after F18 QA and
won't ever be pushed to previous Fedora versions.
blitz-0.10 has updated its license terms.
It has changed from either LGPLv3+ or BSD
to either LGPLv3+ or BSD or Artistic 2.0
It was Artistic 1.0 febore, but as this is not allowed in Fedora, it
This new version will arrive at rawhide soon.