Skip to content
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

Cleaning up Lintian errors and warnings #122

Merged
merged 2 commits into from
Jan 6, 2014

Conversation

aparkinson
Copy link
Contributor

/etc/.. files related to Upstart and SystemV weren't correctly marked as configuration files and upgrading the package could cause any changes made by the system administrator to be lost. This generates a 'file-in-etc-not-marked-as-conffile' error in Lintian.

Symlinks to files which are in the same top-level directory should be relative according to debian policy; handy when installing packages into a jail or using non-standard system layout. Symlinks created in /usr/bin weren't creating a relative symlink to /usr/share//bin

This fixes the common Lintian errors but there are one or two warnings remaining

@@ -88,7 +88,7 @@ trait GenericPackageSettings
if !file.isDirectory
if name startsWith "bin/"
if !(name endsWith ".bat") // IGNORE windows-y things.
} yield LinuxSymlink("/usr/" + name, installLocation+"/"+pkg+"/"+name)
} yield LinuxSymlink("/usr/" + name, installLocation.stripPrefix("/usr/")+"/"+pkg+"/"+name)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice and simple.

@jsuereth
Copy link
Member

jsuereth commented Jan 6, 2014

Thanks for the fixes!

jsuereth added a commit that referenced this pull request Jan 6, 2014
Cleaning up Lintian errors and warnings
@jsuereth jsuereth merged commit cc8f726 into sbt:master Jan 6, 2014
@aparkinson
Copy link
Contributor Author

@jsuereth Happy to help. Sorry for being late to the party on reviewing the docs in your PR

@jsuereth
Copy link
Member

jsuereth commented Jan 6, 2014

@aparkinson Feel free to review them. It's not to late to fix em. I pushed an M1, I'm hoping to push an M2 in another week with RPM support. I'd love for you to help write more docs. They need some massive improvements to actually be useful :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants