Bug 715580 - Incorrect macros definition
Summary: Incorrect macros definition
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 14
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-23 12:35 UTC by Pavel Alexeev
Modified: 2011-07-01 11:57 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-24 19:54:17 UTC
Type: ---


Attachments (Terms of Use)

Description Pavel Alexeev 2011-06-23 12:35:12 UTC
Description of problem:
LANG=C fedpkg local
[snip]
RPM build errors:
    File must begin with "/": %{_unitdir}/3proxy.service
Could not build locally: Non zero exit

Ended when file in spec appeared as:
%{_unitdir}/%{name}.service
in %files section, when it looks like:
/%{_unitdir}/%{name}.service
rpm built.

Version-Release number of selected component (if applicable):
$ rpm -qa systemd\*
systemd-units-10-2.fc14.1.i686

How reproducible:
Always

Comment 1 Pavel Alexeev 2011-06-23 12:45:51 UTC
It seams completely undefined:
$ rpm -E %{_unitdir}
%{_unitdir}

Comment 2 Bill Nottingham 2011-06-24 19:54:17 UTC
This appears to be fixed on F-15.

Comment 3 Pavel Alexeev 2011-06-30 19:01:58 UTC
Could you please push updates for Fedora 14 too?

Comment 4 Michal Schmidt 2011-07-01 11:57:23 UTC
systemd is not maintained in F14. There should not be any expectations of it working there. It had a purpose as something to play with for early testers, that's all.

Do not add systemd unit files to packages in F14 (and neither to F15).

From http://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Packages_migrating_to_a_systemd_unit_file_from_a_SysV_initscript :
  Packages are strictly forbidden from migrating to systemd within updates to
  a Fedora release. The migration is only allowed between Fedora releases.


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