Re: handling of symlinks to symlinks in spec file

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I can reproduce this problem, can you provide a minimal reproducer. Ideally the 
srpm package from which the problematic rpm can be built.

Lubos


----- Original Message -----
> From: "Domen Vrankar" <domen.vrankar@xxxxxxxxx>
> To: "General discussion about the RPM package manager" <rpm-list@xxxxxxxxxxxxx>
> Sent: Monday, April 11, 2016 9:02:09 PM
> Subject: handling of symlinks to symlinks in spec file
> 
> Hi,
> 
> Someone reported to me an issue regarding rpm and symlinks to symlinks.
> I've reproduced it on Fedora 21 and 23.
> 
> Let's assume, I have a library, e.g. liblibrary.so.5.6.7 and I have
> two symbolic links, so the result of "ls -l" would look like this
> 
> liblibrary.so -> liblibrary.so.0
> liblibrary.so.0 -> liblibrary.so.5.6.7
> liblibrary.so.5.6.7
> 
> and part of spec file would look like this
> 
> %files
> %defattr(-,root,root,-)
> "/usr/lib/liblibrary.so"
> "/usr/lib/liblibrary.so.0"
> "/usr/lib/liblibrary.so.5.6.7"
> 
> When running "rpm -i project1.1-Linux.rpm" it outputs a dependency
> resolution error
> 
> error: Failed dependencies:
>     libtest_lib.so()(64bit) is needed by project1-1.2.1-1.x86_64
> 
> Either removing library.so from spec file or setting
> 
> Autoreq: NO
> 
> in it removes the error.
> 
> Is this a bug in rpmbuild automatic dependency resolution for symlinks
> to simlyinks?
> Is there is something that should be set in spec file for such cases?
> 
> Thanks,
> Domen
> _______________________________________________
> Rpm-list mailing list
> Rpm-list@xxxxxxxxxxxxx
> http://lists.rpm.org/mailman/listinfo/rpm-list
> 
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxxxxx
http://lists.rpm.org/mailman/listinfo/rpm-list



[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux