Processing commands for cont...@bugs.debian.org:
tags 428095 + pending
Bug #428095 [apache2-prefork-dev] apache2-prefork-dev: apache2-prefork-dev
should Provides: apache2-dev
Added tag(s) pending.
tags 620347 + pending
Bug #620347 [apache2.2-common] Include conf.d/ should really be Include
Processing commands for cont...@bugs.debian.org:
merge 610297 639237
Bug#610297: apache2: Apache2 based applications relying on a DBMS might not
start at boot time
Bug#639237: base: Wrong startup order
Mismatch - only Bugs in same state can be merged:
Values for `package' don't match:
#610297
Processing commands for cont...@bugs.debian.org:
tags 500558 - upstream + ipv6
Bug #500558 [libapr1] apache2.2-common: Apache fails to start on boot after
upgrade Etch - Lenny
Removed tag(s) upstream.
Bug #500558 [libapr1] apache2.2-common: Apache fails to start on boot after
upgrade Etch -
Processing commands for cont...@bugs.debian.org:
tags 294648 - fix-upstream + confirmed + upstream
Unknown tag/s: fix-upstream.
Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid
help security upstream pending sarge sarge-ignore experimental d-i confirmed
ipv6 lfs
Hello
I recently found some strange behavior in dns resolution at boot time, when
eth0 has no ipv4 yet. (#500558)
Do you use DHCP for your other interface (eth0)?
What is the result of `grep CONCURRENCY /etc/init.d/rc' ?
Does the bug is still there if you set up a static ip address in
5 matches
Mail list logo