Skip to content
This repository has been archived by the owner on Mar 1, 2023. It is now read-only.

Fix EOL in bin/velma for *nix releases #1

Open
lasselasse opened this issue Apr 2, 2013 · 2 comments
Open

Fix EOL in bin/velma for *nix releases #1

lasselasse opened this issue Apr 2, 2013 · 2 comments
Assignees
@blaubaer
Labels
bug duplicate

Comments

@lasselasse
Copy link
Contributor

I've successfully installed the deb package, but executing bin/velma fails with the error message:

/bin/sh^M: bad interpreter: No such file or directory

This is because the file contains MS-DOS style EOL characters (show up as ^M in vim). Once fixed to Unix-style EOL, Velma runs just fine.
@ghost ghost assigned blaubaer Apr 4, 2013
@blaubaer
Copy link
Member

blaubaer commented Apr 8, 2013

Duplicate of #2

@blaubaer blaubaer closed this as completed Apr 8, 2013
blaubaer added a commit that referenced this issue Apr 11, 2013
@blaubaer
Merge pull request #2 from lasselasse/issue-1
f99fb05 
fixes #1: ensure unix line endings for script files in unix packages
@dwerder
Copy link
Member

dwerder commented Apr 15, 2013

Is not fixed as long as there are no new releases on the repo server for the linux packages ;-)

@dwerder dwerder reopened this Apr 15, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@blaubaer blaubaer

Labels
bug duplicate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lasselasse @blaubaer @dwerder