resolvconf fails to install/upgrade because of immutable /etc/resolv.conf
Bug #378844 reported by
Amr El-Sharnoby
This bug affects 17 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
resolvconf (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: resolvconf
Maybe this was caused by an immutable /etc/resolv.conf
$ lsattr /etc/resolv.conf
----i------------e- /etc/resolv.conf
I don't like that it get changed by network manager so I set it this way ..
ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.04
ErrorMessage: subprocess post-installation script returned error exit status 1
NonfreeKernelMo
Package: resolvconf 1.43ubuntu1
PackageArchitec
SourcePackage: resolvconf
Title: package resolvconf 1.43ubuntu1 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Uname: Linux 2.6.28-11-generic i686
Related branches
Changed in resolvconf (Ubuntu): | |
status: | New → Confirmed |
summary: |
- package resolvconf 1.43ubuntu1 failed to install/upgrade: subprocess - post-installation script returned error exit status 1 + resolvconf fails to install/upgrade because of immutable + /etc/resolv.conf |
Changed in resolvconf (Ubuntu): | |
status: | Invalid → New |
Changed in resolvconf (Ubuntu): | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
First, resolvconf should not fail and block an update. Fix would be to check if /etc/resolv.conf is writable in package control scripts.
Second, I think a debconf notice should be used to tell users who have immutable resolv.conf that they probably don't want resolvconf installed. I know that debconf notices should be used sparsely, but I guess this would be a proper case: almost all users won't see it, and the other ones would be happy to know that they can safely remove this package.