** Changed in: resolvconf (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995260
Title:
resolvconf 1.63ubuntu11 failed to upgrade: ln: failed to create
Still waiting for more information from Christopher.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995260
Title:
resolvconf 1.63ubuntu11 failed to upgrade: ln: failed to create
symbolic link
My experience is for resolvconf 1.63ubuntu14 not ...11 at the moment but
didn't want to open a new bug report for the very same issue. You
experienced friends maybe edit the title or do something else or maybe
this way is fine.
Three days ago I lauched an EC2 Ubuntu Precise micro instance on
** Attachment added: deniz_var_log_apt_history_log
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/995260/+attachment/3159731/+files/deniz_var_log_apt_history_log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: from_start_of_ssh_to_error
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/995260/+attachment/3159732/+files/from_start_of_ssh_to_error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
With this bug happening, Ubuntu 12.04 LTS EC2 instance gives a weak
impression, affected for sure so I'm adding the project.
** Changed in: resolvconf (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've written and the upgrade resulted with the error: resolvconf
1.63ubuntu11. This is nonsense for sure. A copy paste error. You can
see the actual one in the attachment I've added. It should be:
...and the upgrade resulted with the error: resolvconf: Error:
/etc/resolv.conf isn't a symlink, not
K. Deniz Ogut,
The log you attached shows an entirely different error message from the
one in the title of this bug. Please file a separate bug report.
In your bug report, please show the output of:
ls -l /etc/resolv.conf
cat /etc/resolv.conf
--
You received this bug notification because you
** Changed in: resolvconf (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995260
Title:
resolvconf 1.63ubuntu11 failed to upgrade: ln: failed to create
Steve Langasek (vorlon) wrote: The log you attached shows an entirely
different error message from the one in the title of this bug. Please
file a separate bug report.
Sorry and thanks. I filed a new bug report: Bug #1003595 I'm removing my
attachments here.
** Attachment removed:
Christopher: If you don't provide more information there is no way we
can do anything about the issue you reported (#995260).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995260
Title:
resolvconf
The message ln: failed to create symbolic link `/etc/resolv.conf': File
exists is what you get if you try to create a symbolic link at a target
that already exists and the f option is not given. But the resolvconf
postinst *does* run ln with the f option.
Submitter Christopher: Any chance you
** Summary changed:
- package resolvconf 1.63ubuntu11 failed to install/upgrade: ErrorMessage:
subprocess installed post-installation script returned error exit status 1
+ resolvconf 1.63ubuntu11 failed to upgrade: ln: failed to create symbolic
link `/etc/resolv.conf': File exists
--
You
13 matches
Mail list logo