- Original Message -
> On Mon, Mar 24, 2014 at 04:55:34AM +0100, Kevin Kofler wrote:
> > > One possible fix would be to rename 'qt' back to 'qt4' explicitly
> > That will have to happen soon anyway, with the move to Qt 5.
>
> Is qt5 going to be shifted to be packaged as generic qt? Is ther
On Mon, Mar 24, 2014 at 04:55:34AM +0100, Kevin Kofler wrote:
> > One possible fix would be to rename 'qt' back to 'qt4' explicitly
> That will have to happen soon anyway, with the move to Qt 5.
Is qt5 going to be shifted to be packaged as generic qt? Is there value in
doing that over leaving it v
Rex Dieter wrote:
> One possible fix would be to rename 'qt' back to 'qt4' explicitly
That will have to happen soon anyway, with the move to Qt 5.
Kevin Kofler
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Condu
Kevin Kofler wrote:
> Ville Skyttä wrote:
>> Looks like there are quite a few packages that don't do that (nor have
>> the Epoch in the dep).
>>
>> $ repoquery --repoid=rawhide-source --archlist=src \
>> --whatrequires qt-devel --qf=" %{NAME}\n%{REQUIRES}"
>
> All those packages (even th
Ville Skyttä wrote:
> Looks like there are quite a few packages that don't do that (nor have
> the Epoch in the dep).
>
> $ repoquery --repoid=rawhide-source --archlist=src \
> --whatrequires qt-devel --qf=" %{NAME}\n%{REQUIRES}"
All those packages (even those which just BR qt-devel witho
On 03/23/2014 03:17 AM, Kevin Kofler wrote:
> Antonio Trande wrote:
>> I need your help with F1LT application[1]. Its latest release (3.0.0)
>> seems not work even if little things are changed in SPEC file.
>
> I see you already resolved your problem with upstream's help:
> https://bitbucket.org/p
On Sun, Mar 23, 2014 at 4:17 AM, Kevin Kofler wrote:
> Basically, NEVER BuildRequire qt-devel, ALWAYS use qt4-devel instead.
Looks like there are quite a few packages that don't do that (nor have
the Epoch in the dep).
$ repoquery --repoid=rawhide-source --archlist=src \
--whatrequires qt-de
Antonio Trande wrote:
> I need your help with F1LT application[1]. Its latest release (3.0.0)
> seems not work even if little things are changed in SPEC file.
I see you already resolved your problem with upstream's help:
https://bitbucket.org/pieczar/f1lt/issue/3/f1lt-commit-7440f9a-does-not-run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all.
I need your help with F1LT application[1]. Its latest release (3.0.0)
seems not work even if little things are changed in SPEC file.
'f1lt' binary doesn't load its data files located in
'usr/share/f1lt-3.0.0' directory; if I unusually copy th
