Bug 2212080 - macros inconsistency between Fedora and EPEL9
Summary: macros inconsistency between Fedora and EPEL9
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: cmake
Version: 39
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Björn Esser (besser82)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-03 16:57 UTC by Mattia Verga
Modified: 2024-11-27 21:12 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-11-27 21:12:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mattia Verga 2023-06-03 16:57:35 UTC
I'm not sure if I have to report this against Fedora or EPEL (or RH, since I can't find cmake package for EPEL9).
But maybe it's me doing something wrong with macros.

Anyway, in the test section of libindi package I use this to run tests:
%ctest --test-dir %_vpath_builddir/test

This translates in Fedora as:
+ /usr/bin/ctest --test-dir redhat-linux-build --output-on-failure --force-new-ctest-process -j6 --test-dir redhat-linux-build/test
Internal ctest changing into directory: /builddir/build/BUILD/indi-2.0.2/redhat-linux-build/test

While on EPEL (at least, in COPR):
+ /usr/bin/ctest --output-on-failure --force-new-ctest-process -j2 --test-dir redhat-linux-build/test
Internal ctest changing into directory: /builddir/build/BUILD/indi-2.0.2/redhat-linux-build/redhat-linux-build/test
Failed to change working directory to "/builddir/build/BUILD/indi-2.0.2/redhat-linux-build/redhat-linux-build/test" : No such file or directory

Reproducible: Always

Comment 1 Fedora Release Engineering 2023-08-16 08:10:06 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 2 Cristian Le 2024-02-14 08:11:47 UTC
Looking at F34 it seems at that point they did a `cd` [1] before that. Anyway you should not be specifying `--test-dir` manually. Instead redefine `%_vpath_builddir` if needed, or in your case, patch the source to add `add_test` at the top-level CMakeLists.txt

[1]: https://src.fedoraproject.org/rpms/cmake/blob/cc03ad334fea0b8abd6d8eccc89b5c3aea051bb9/f/macros.cmake#_53

Comment 3 Cristian Le 2024-02-14 08:12:45 UTC
s/add_test/enable_testing

Comment 4 Aoife Moloney 2024-11-08 10:53:06 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Aoife Moloney 2024-11-27 21:12:40 UTC
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.