-
Notifications
You must be signed in to change notification settings - Fork 443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RPM build fails on Kubuntu 11.04 #4
Comments
I've seen this as well. Which version of rpmbuild are you using? I'd I should have a fix later this week.
|
You're correct, version 4.8.1 |
Hmm, my most recent patch for ubuntu (rpmbuild 4.9) appears to work again. I'm going to watch this issue, because i think something odd is causing it. |
As a workaround, is it not possible to remove the |
|
Ah, good catch there. I can fix that. |
Related to a report in #4 about directory-only packages.
Just in case, the directory I've specified in package mapping was not empty. I've assumed that it'll be copied recursively to the package. linuxPackageMappings <+= target map { target =>
val src = target / "webapp"
val dest = "/opt/app"
packageMapping(src -> dest)
} This code doesn't work as expected (well, by me) with either Debian or RPM packages. My way of dealing with it: linuxPackageMappings <+= target map { target =>
val src = target / "webapp"
val dest = "/opt/app"
LinuxPackageMapping(
for {
path <- (src ***).get
if !path.isDirectory
} yield path -> path.toString.replaceFirst(src.toString, dest)
)
} It would be nice though to have this code on the library side for consistent and expected behavior. Also in a package with lots of files every additional recursion through the file system is a performance hit. |
Can you open a feature request for that? The only reason it's not done now is because tools that do so grant |
Closing, since no feedback here. |
When attempting to build an RPM release I get the following error output
The rpmbuild command used is
and the generated spec file is:
I have rpm and rpmbuild available on my system.
The text was updated successfully, but these errors were encountered: