Change rpm autodeps command from fc-query to fc-scan

Bug #633644 reported by Jeff Johnson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
RPM
New
Wishlist
Unassigned
Fedora
In Progress
Medium

Bug Description

Tracker

Revision history for this message
In , Nicolas (nicolas-redhat-bugs) wrote :

In bug #517789 Behdad requests that rpm changed the command it uses to collect font metadata from fc-query to fc-scan
point 7 of https://bugzilla.redhat.com/show_bug.cgi?id=517789#c11

Revision history for this message
In , Nicolas (nicolas-redhat-bugs) wrote :
Revision history for this message
In , Panu (panu-redhat-bugs) wrote :

Given your worry about fontconfig files not being in buildroot in that comment, to which I don't see a response from Behdad so far... are you guys really sure this change should go in?

Revision history for this message
In , Nicolas (nicolas-redhat-bugs) wrote :

I'm only relaying Behdad's instructions there, so if you needinfo, needinfo him :)

From what I understand of fontconfig changing fc-query to fc-scan now is low impact and will at least take make rpm take into account the fontconfig rules shipped within the fontconfig package itself. Then once Behdad adds some way to point fc-scan to fontconfig files outside fontconfig default paths, it we can improve the system more by adding an argument to the fontconfig files in the buildroot to the fc-scan call

Of course, Behdad may have better ideas than me here

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message
In , Behdad (behdad-redhat-bugs) wrote :

Oki doki, the machinery is already there.

RPM should use fc-query, and set envvar FONTCONFIG_FILE to the absolute path of a file containing the following:

<fontconfig>
<cachedir>path/to/build/dir/var/cache/fontconfig</cachedir>
<dir>path/to/build/dir/etc/fonts/conf.d</dir>
</fontconfig>

The cachedir is unused, but needs to be available. Alternatively you can point it to /tmp.

Let me know if it works.

Revision history for this message
In , Nicolas (nicolas-redhat-bugs) wrote :

Panu, is this something you can work with ? It does not seem the kind of stuff a package can request itself

Revision history for this message
In , Nicolas (nicolas-redhat-bugs) wrote :

Panu, I think that in F14 it's possible to move font autodep detection from rpm to other patckages. Would you be ok with moving this stuff in fontpackages-devel? (every font package in the distro depends on it) Can you give me some hints on how to do it?

Revision history for this message
Jeff Johnson (n3npq) wrote :

macro config change.
rpm5 needs font config?

Changed in rpm:
importance: Undecided → Low
importance: Low → Wishlist
Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Revision history for this message
In , Jens (jens-redhat-bugs) wrote :

Reopening based on comment 7.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Revision history for this message
In , Paul (paul-redhat-bugs) wrote :

Still needed.

Revision history for this message
In , Panu (panu-redhat-bugs) wrote :

(In reply to Nicolas Mailhot from comment #7)
> Panu, I think that in F14 it's possible to move font autodep detection from
> rpm to other patckages. Would you be ok with moving this stuff in
> fontpackages-devel? (every font package in the distro depends on it) Can you
> give me some hints on how to do it?

Uhm, somehow all these years passed...

Since rpm 4.9.x the font provides generation is controlled by two files:
/usr/lib/rpm/fileattrs/font.attr and /usr/lib/rpm/fontconfig.prov

To move the control to font SIG where it IMO belongs, just grab a copy of those into fontpackages-devel in same fs location and once its ready to build, drop me a note to axe them from rpm-build. And that's it. Well, perhaps explicit conflicts for a while wouldn't hurt, but that'd be "minor details".

Switching component to fontpackages as that's where the willingness to commit to the change and first step(s) need to come from.

Changed in fedora:
importance: Unknown → Medium
status: Unknown → In Progress
Revision history for this message
In , fedora-admin-xmlrpc (fedora-admin-xmlrpc-redhat-bugs) wrote :

This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.