Re: lazarus broken dep?
I'm still thinking on the proper solution. Meanwhile, I submitted a band-aid build: https://koji.fedoraproject.org/koji/taskinfo?taskID=61412479 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: lazarus broken dep?
On Thu, Feb 4, 2021 at 3:47 AM Artur Frenszek-Iwicki
wrote:
> Yes, I was gonna post a "Help wanted" message about this to the list, but
> as it happens, procrastination got in the way.
>
> The gist is: In lazarus.spec, we have a "%qt5pas_release" macro, and then
> there's "Requires: qt5pas-devel = %{qt5pas_version}-%{qt5pas-release}", and
> the qt5pas sub-package has "Release: %{qt5pas-release}". When the mass
> rebuild occurs, releng scripts slap ".1" at the end of qt5-pas's Release,
> so then there's a mismatch, because lazarus Requires "qt5pas = ver-rel",
> and qt5pas is "ver-rel.1".
>
> Having to undo this every time a Mass Rebuild comes around is getting
> tedious, so I'm looking into finding a different way of handling this.
>
Can we get the packaged band-aided until the better fix is in place or are
you getting close? I still have a couple of FTBFS packages that need a
working package.
Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: lazarus broken dep?
Yes, I was gonna post a "Help wanted" message about this to the list, but as it
happens, procrastination got in the way.
The gist is: In lazarus.spec, we have a "%qt5pas_release" macro, and then
there's "Requires: qt5pas-devel = %{qt5pas_version}-%{qt5pas-release}", and the
qt5pas sub-package has "Release: %{qt5pas-release}". When the mass rebuild
occurs, releng scripts slap ".1" at the end of qt5-pas's Release, so then
there's a mismatch, because lazarus Requires "qt5pas = ver-rel", and qt5pas is
"ver-rel.1".
Having to undo this every time a Mass Rebuild comes around is getting tedious,
so I'm looking into finding a different way of handling this.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
lazarus broken dep?
cqrlog is failing due to a dep issue with lazarus: DEBUG util.py:444: Error: DEBUG util.py:444: Problem: conflicting requests DEBUG util.py:444:- nothing provides qt5pas-devel(x86-64) = 2.6-2001006.fc34 needed by lazarus-2.0.10-6.fc34.x86_64 But the lazarus build should be providing the package for itself... It looks like a "rightmost" bump occurred just on the qt5pas-devel package? lazarus-2.0.10-6.fc34.x86_64.rpm (info) (download) qt5pas-2.6-2001006.*fc34.1.*x86_64.rpm (info) (download) qt5pas-devel-2.6-2001006.fc34.1.x86_64.rpm (info) (download) lazarus-debuginfo-2.0.10-6.fc34.x86_64.rpm (info) (download) lazarus-debugsource-2.0.10-6.fc34.x86_64.rpm (info) (download) qt5pas-debuginfo-2.6-2001006.fc34.1.x86_64.rpm (info) (download) Weird. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
