在 2013-8-15 AM1:23，"Rex Dieter" 写道：
> See
> https://fedoraproject.org/wiki/Packaging:Alternatives
>
> and use
> Requires(post): %{_sbindir}/update-alternatives
> ...etc...
Good, don't hardcode paths.
What about creating an RFE for all affected packages?
--
devel mailing list
devel@lists.fedorapr
Sérgio Basto wrote:
> I take a look in "my" Virtualbox.spec and it use /sbin/ldconfig but not
> in Requires, is not a error use Requires: /sbin/ldconfig ?
depends, see
https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Shared_libraries
whether an explicit dependency is needed (or not).
-
Sérgio Basto wrote:
> On Qua, 2013-08-14 at 18:59 +0800, Christopher Meng wrote:
>> Seems another victim appeared in test list.
>>
>> This time is for /sbin/alternatives.
>
> rpm -qf /sbin/alternatives
> chkconfig-1.3.60-3.fc19.x86_64
>
> once again , I think Requires: /sbin/alternatives is w
On Qua, 2013-08-14 at 18:59 +0800, Christopher Meng wrote:
> Seems another victim appeared in test list.
>
> This time is for /sbin/alternatives.
rpm -qf /sbin/alternatives
chkconfig-1.3.60-3.fc19.x86_64
once again , I think Requires: /sbin/alternatives is wrong
should be Requires: chkconfi
On 08/14/2013 12:59 PM, Christopher Meng wrote:
Seems another victim appeared in test list.
This time is for /sbin/alternatives.
Sorry for no contexts, but what about removing /sbin or /bin from every
spec?
Not a clever idea.
Very oversimplified, in RPM-provides/requires, "full paths" symbols
Seems another victim appeared in test list.
This time is for /sbin/alternatives.
Sorry for no contexts, but what about removing /sbin or /bin from every
spec? I think RPM can handle this without fullpath.
Thanks.
Sent from Note I
--
devel mailing list
devel@lists.fedoraproject.org
https://admi
On Ter, 2013-08-13 at 19:54 -0500, Rex Dieter wrote:
> Christopher Meng wrote:
>
> > Can we modify all affected specs to solve the problem?
>
> Better to just not modify glibc in a way that's not backward compatible.
I take a look in "my" Virtualbox.spec and it use /sbin/ldconfig but not
in Req
Christopher Meng wrote:
> Can we modify all affected specs to solve the problem?
Better to just not modify glibc in a way that's not backward compatible.
-- rex
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: ht
Can we modify all affected specs to solve the problem?
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Ter, 2013-08-13 at 16:13 -0400, Miro Hrončok wrote:
> Hi,
> I believe there's something wrong in Koji Rawhide buildroot, as it
> appears nothings provides /sbin/ldconfig.
>
> DEBUG util.py:264: Error: Package: foo
> DEBUG util.py:264: Requires: /sbin/ldconfig
repoquery --releas
On 08/13/2013 10:19 PM, Kyle McMartin wrote:
> On Tue, Aug 13, 2013 at 04:13:20PM -0400, Miro Hrončok wrote:
>> Hi,
>> I believe there's something wrong in Koji Rawhide buildroot, as it
>> appears nothings provides /sbin/ldconfig.
>>
>> DEBUG util.py:264: Error: Package: foo
>> DEBUG util.py:264:
On Tue, Aug 13, 2013 at 04:13:20PM -0400, Miro Hrončok wrote:
> Hi,
> I believe there's something wrong in Koji Rawhide buildroot, as it
> appears nothings provides /sbin/ldconfig.
>
> DEBUG util.py:264: Error: Package: foo
> DEBUG util.py:264: Requires: /sbin/ldconfig
>
> http://koj
On Tue, Aug 13, 2013 at 3:13 PM, Miro Hrončok wrote:
> Hi,
> I believe there's something wrong in Koji Rawhide buildroot, as it appears
> nothings provides /sbin/ldconfig.
>
> DEBUG util.py:264: Error: Package: foo
> DEBUG util.py:264: Requires: /sbin/ldconfig
>
> http://kojipkgs.fed
Hi,
I believe there's something wrong in Koji Rawhide buildroot, as it
appears nothings provides /sbin/ldconfig.
DEBUG util.py:264: Error: Package: foo
DEBUG util.py:264: Requires: /sbin/ldconfig
http://kojipkgs.fedoraproject.org//work/tasks/2927/5812927/root.log
Is this somethin
On Tue, 23 Oct 2012 15:57:37 +0200
Simone Caronni wrote:
> On 23 October 2012 15:25, Eric "Sparks" Christensen
> wrote:
> > On Tue, Oct 23, 2012 at 5:24 AM, Simone Caronni
> > wrote:
> >> Hello,
> >>
> >> yesterday I had some "invalid channel policy" errors when trying to
> >> build packages wi
On 23 October 2012 15:25, Eric "Sparks" Christensen
wrote:
> On Tue, Oct 23, 2012 at 5:24 AM, Simone Caronni wrote:
>> Hello,
>>
>> yesterday I had some "invalid channel policy" errors when trying to
>> build packages with koji. Tasks were never ending with the "building"
>> status on.
>> I cance
On Tue, Oct 23, 2012 at 5:24 AM, Simone Caronni wrote:
> Hello,
>
> yesterday I had some "invalid channel policy" errors when trying to
> build packages with koji. Tasks were never ending with the "building"
> status on.
> I canceled the builds after few hours and today I tried again to build them
Hello,
yesterday I had some "invalid channel policy" errors when trying to
build packages with koji. Tasks were never ending with the "building"
status on.
I canceled the builds after few hours and today I tried again to build them.
The jobs always fail because I have errors like the following (3
18 matches
Mail list logo
