solved:latest ifupdown broken

[devil]

ifupdown 0.7.3 is broken see bugreport:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23692008

If you have to dist-upgrade today, better put  it on hold for now. This should be fixed really fast though. I will keep you posted.

greetz
devil

[bluelupo]

Package ifupdown is patched now (new version 0.7.4), see bugreport http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23692008

[clubex]

But bug #692110 say that ifupdown 0.7.4 "renders system unbootable".

I haven't even look at the bug yet as I thought best to alert others first. I'll probably hold off until bug #692110 is resolved.

[clubex]

http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1075002.html

It seems that purging 0.7.4/0.7.3 and reverting to ifupdown 0.7.2 is a temporary remedy for those already caught by this bug.

[Bequimão]

No problem here after d-u with ifupdown 0.7.4. as siduction does not use upstart.

Bequimão

[agaida]

@clubex: bugs #692008 and #692110 should not hurt on a system which is wired. if the system use wpasuppl. the things could be different. Would you be so kind and run the following script?

Code: [Select]


$ nano whichinit
if [ -e /lib/lsb/init-functions ]; then
  . /lib/lsb/init-functions
fi

if init_is_upstart; then
  echo "upstart";
else
  echo "systemv"
fi

$ bash whichinit


and post the output?

[agaida]

@bequimao: That was my intention when i wrote that patch. If there anything goes wrong it should be related to upstart.

[clubex]

Please read my posts again. My posts were only a bug report and a remedy. I don't have a problem and I don't use upstart.

I only posted this because when attempting to du bug #692110 was reported so I thought I would warn others. And as I read bug #692008 the update may affect people who don't use upstart.

i.e. from #692008

the modifications introduced to close bug 679549 don't work on systems
which don't use upstart, making it impossible to bring interfaces up or
down.

Apparently the problem also isn't observed until you attempt a reboot.  If you/anyone know for certain this does not happen with systems which don't use upstart then please post.

[agaida]

if the bug say so, you must decide which information you wil trust. And all i know is that:

a) the original bug dont prevent a system from booting (not tested with wireless systems)
b) the patch in .4 is only about the upstart scripts, which will return 0 if no upstart is installed.

So i would say: It is safe to update. if your system dont boot after update this is not the fault of ifupdown. Then there are other problems. But this is only my opinion for these bugs ...

But there is a big chance that i be wrong. I don't know much about linux, esp, inits and networking. :twisted:

[reddark]

hmm, alles englisch ... gilt die Warnung noch?

[agaida]

Weiss ich nicht, ich kanns auch nicht nachvollziehen.

Ich würd aber für die Funktionalität des Patches in debian keinerlei Verantwortung übernehmen wollen, der ist von mir :twisted: Wenn also ein System damit nicht bootet, dann hat das System ein anderes Problem. Im Zweifel kann man sicher updaten und wenn man dann immer noch Bedenken hat:

Code: [Select]


rm /etc/network/*/upstart


Aber ich hab eh keinen Plan von so was.

[reddark]

ok .. danke ...

[Bequimão]

As nobody reported a real crash, we should assume that the issue is fixed or never occurred in siduction, shouldn’t we?

Bequimão

[agaida]

yes.