This bug was fixed in the package resolvconf - 1.63ubuntu14
---
resolvconf (1.63ubuntu14) precise-proposed; urgency=low
* Call db_go after the db_input command so that the debconf error
message is actually shown to the user.
resolvconf (1.63ubuntu13) precise-proposed; urgency=l
** Attachment removed: "VarLogDistupgradeSystemstatetargz.gz"
https://bugs.launchpad.net/bugs/994539/+attachment/3129783/+files/VarLogDistupgradeSystemstatetargz.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Attachment removed: "VarLogDistupgradeAptclonesystemstatetargz.gz"
https://bugs.launchpad.net/bugs/994539/+attachment/3129777/+files/VarLogDistupgradeAptclonesystemstatetargz.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Fix is still good with ubuntu14.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994539
Title:
resolvconf 1.63ubuntu12 failed to install/upgrade -- "lsattr:
Inappropriate ioctl for device While read
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994539
Title:
resolvconf 1.63ubuntu12 failed to install/upgrade -- "lsattr:
Inap
Fix worked fine
Need to get 53.5 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://espelhos.edugraf.ufsc.br/ubuntu/ precise-proposed/main resolvconf
all 1.63ubuntu13 [53.5 kB]
Fetched 53.5 kB in 2s (21.6 kB/s)
Setting up resolvconf (1.63ubuntu12)
This bug was fixed in the package resolvconf - 1.65ubuntu2
---
resolvconf (1.65ubuntu2) quantal; urgency=low
[ Stéphane Graber ]
* In is_immutable_file, if lsattr doesn't return anything on stdout,
return 1 and hide stderr. This fixes lsattr failing on non-ext
filesystems.
** Branch linked: lp:ubuntu/precise-proposed/resolvconf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994539
Title:
resolvconf 1.63ubuntu12 failed to install/upgrade -- "lsattr:
Inappropriate ioct
Hello fer, or anyone else affected,
Accepted resolvconf into precise-proposed. The package will build now
and be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
On Mon, May 07, 2012 at 06:25:57AM -, Thomas Hood wrote:
> Steve: Does the db_input issue explain #995778?
No. 995778 looks like a broken system - and the submitter has noticed this
himself now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Steve: Does the db_input issue explain #995778?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994539
Title:
resolvconf 1.63ubuntu12 failed to install/upgrade -- "lsattr:
Inappropriate ioctl for de
Scott, out of curiosity, what filesystem are you using in these cloud
images such that lsattr is not supported?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994539
Title:
resolvconf 1.63ubuntu12 fa
And worse, I managed to botch the syntax of db_input here, which is why
we're getting the strange exit code (exit 20) - that much at least I've
fixed now, and pushed to Ubuntu trunk, but the lsattr still needs to be
handled correctly so that we don't wind up on this code path on !ext.
--
You rece
Stéphane, can you please follow through on this? This seems to be a
regression from the version in precise, for a non-obvious reason - the
subshell created by use of echo_first_arg $(lsattr ...) doesn't trigger
the set -e handling. But I think we should address that explicitly here
rather than re
** Changed in: resolvconf (Ubuntu)
Importance: Undecided => High
** Changed in: resolvconf (Ubuntu)
Status: Confirmed => Triaged
** Also affects: resolvconf (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: resolvconf (Ubuntu Quantal)
Importance: High
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: resolvconf (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994539
Title:
Are you using reiserfs by any chance? or any non-ext filesystem?
root@castiana:~/Desktop/test/mnt# ls
root@castiana:~/Desktop/test/mnt# touch bla
root@castiana:~/Desktop/test/mnt# lsattr bla
lsattr: Inappropriate ioctl for device While reading flags on bla
root@castiana:~/Desktop/test/mnt# grep re
17 matches
Mail list logo
