Bug 2378488 - ulauncher: Stop using deprecated %py3_build/%py3_install macros [NEEDINFO]
Summary: ulauncher: Stop using deprecated %py3_build/%py3_install macros
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: ulauncher
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Artem
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2376118
TreeView+ depends on / blocked
 
Reported: 2025-07-08 15:28 UTC by Miro Hrončok
Modified: 2025-08-31 21:55 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:
troy: needinfo? (ego.cordatus)


Attachments (Terms of Use)

Description Miro Hrončok 2025-07-08 15:28:24 UTC
Dear package maintainer,

this bugzilla is automated becasue the number of impacted packages it too high to go trough manually.


It appears that your package uses the deprecated %py3_build and/or %py3_install macro.

See https://fedoraproject.org/wiki/Changes/DeprecateSetuppyMacros for why the macros are deprecated.

%py3_install expands to python setup.py install. This has been a deprecated command for 5 years and will likely stop working in Fedora 45.



Please migrate to %pyproject_buildrequires + %pyproject_wheel + %pyproject_install macros instead.

See https://fedoraproject.org/wiki/Changes/DeprecateSetuppyMacros#Migrating_to_%pyproject_macros for migration guide.

See https://github.com/hroncok/pyprojectize/ for a tool that can help you automate the migration.


Thank you. Let me know if you need help.

Comment 1 Troy Curtis 2025-08-31 21:55:24 UTC
Instead of trying to fix the ulauncher v5 build for this, I'd like to propose we start packaging the v6 beta. @atim what do you think? All the devs and most Arch users have been daily driving v6 for well over a year, and there is a big push right now to get it out of beta, possibly by the end of 2025.

I propose that re this ticket because v6 has migrated to pyproject.toml, and the %pyproject_* macros do not play well with ulauncher v5's setup.py configuration. The desktop file is installed in the wrong place, named the wrong thing, and has the wrong Exec path. It seems like there is some issue with how the distutils is detecting "data_path", since even after I manually fix the desktop file, it won't launch for a similar reason:

```
Aug 31 17:33:55 arafel env[218372]:                         ~~~~~~~~~~~~~^^
Aug 31 17:33:55 arafel env[218372]:   File "/usr/lib/python3.13/site-packages/ulauncher/config.py", line 60, in get_data_path
Aug 31 17:33:55 arafel env[218372]:     raise ProjectPathNotFoundError(abs_data_path)
Aug 31 17:33:55 arafel env[218372]: ulauncher.config.ProjectPathNotFoundError: /ulauncher-5.15.7.data/data/share/ulauncher
```

This `/ulauncher-5.15.7.data/...` was the same kind of path issue that it put into the desktop file.

If there is agreement on making the move to v6 now, I can migrate the copr I've already been building periodically.


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