Note - it sounds like the dos2unix package may be preferable for those
wanting a more general-purpose conversion tool, and the command names
that are missing from tofrodos. That is according to the tofrodos
package documentation (as noted in #2). Here is the relevant text from
/usr/share/doc/tofr
How about a backport? Lucid is a LTS, so you'd expect these kind of
fixes to appear when they are fixed in later releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/523264
Title:
[lucid] dos2uni
This seems to be fixed on natty
** Changed in: command-not-found
Status: New => Invalid
** Changed in: command-not-found (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
I agree with David and I'm unsubscribing from this bug saddened that a
discussion about this is going on for an entire year.
--
[lucid] dos2unix is not in tofrodos but dos2unix
https://bugs.launchpad.net/bugs/523264
You received this bug notification because you are a member of Ubuntu
Bugs, which
Actually, the REAL problem here is that fundamental, documented behavior
has been changed in an LTS release.
The is a symptom of a larger problem: established norms randomly
changing with every new release, completely breaking backwards
compatibility.
Where in the world did the "fromdos" and "tod
Bruno,
This bug is a misnomer. Ubuntu decided to replace the tofromdos modules
with their own utilities as standard with the Lucid version. The issue
is that the former links of dos2unix and unix2dos are not set properly
but it is hard to determine this during the install; the Lucid version
is mis
The title of this bug doesn't make sense to me. The dos2unix is supposed
to be in the dos2unix package, but I can't find it:
bruno...@brunojcm-laptop:~/Downloads$ sudo apt-get install dos2unix
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn
The easier way around this problem is to make a soft link to todos and
fromdos. If you have sudo administrative rights, you can make the soft
link in the same directory as follows...
sudo ln -s fromdos dos2unix
sudo ln -s todos unix2dos
Or if do not have sudo privileges, you can make the soft lin
Try to use alias:
alias unix2dos="/usr/bin/fromdos -u" (or todos)
alias dos2unix="/usr/bin/fromdos -d" (or just fromdos)
--
[lucid] dos2unix is not in tofrodos but dos2unix
https://bugs.launchpad.net/bugs/523264
You received this bug notification because you are a member of Ubuntu
Bugs, which
That workaround is not working for me.
--
[lucid] dos2unix is not in tofrodos but dos2unix
https://bugs.launchpad.net/bugs/523264
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
The quick workaround now is to create a link to the new package files.
"fromdos" = "dos2unix" and "todos" = "unix2dos" Both files can be found
under /usr/bin/
--
[lucid] dos2unix is not in tofrodos but dos2unix
https://bugs.launchpad.net/bugs/523264
You received this bug notification because you
** Also affects: command-not-found
Importance: Undecided
Status: New
--
[lucid] dos2unix is not in tofrodos but dos2unix
https://bugs.launchpad.net/bugs/523264
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
12 matches
Mail list logo
