rpm dependency failed because the directory path doesn't exist

devzero2000 pinto.elia at gmail.com
Mon Jun 15 19:31:43 UTC 2009

On Mon, Jun 15, 2009 at 9:09 PM, zhang zjmtt <jullyzhang at gmail.com> wrote:

> Hi Guys,
> I am using a new version of RPM. It looks like it acts in differently way
> than before.

What version ? New respect to what ?

> If the directory of a file doesn't exist, it will fail the dependency
> instead of automatically creating the directory.

You are likely using rpm > 4.4.2.x.y.x <> rpm 4.4.6/4.4.7 that reinforce
parent-dir/linkto dependency  (good packaging habit want this, some
packaging guideline also). See this

> For example, abc.rpm contains a file fileDIR/fileNAME. If fileDIR is not
> installed, abc.rpm will fail the dependency check.

If fileDir have not ownership from other package, well, it is of your
package at minimum.

> Is there any option for rpm or rpmlib to force it automaticaly create the
> directory?

Put %dir fileDir in your spec file if you think this is correct for your
packaging repo clousure.


> _______________________________________________
> Rpm-list mailing list
> Rpm-list at lists.rpm.org
> http://lists.rpm.org/mailman/listinfo/rpm-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-list/attachments/20090615/f9748448/attachment.htm>

More information about the Rpm-list mailing list