Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Doesn't this depend on the way round your particular setup is? It makes
sense to depend on $remote_fs if your system requires it to boot, for
example, and the access to the remote filesystems is _not_ over the
network that is managed by quagga. I'd expect this to be the normal
case, as it seems like quite a bit of server overloading to be putting
quagga on the same instance as something serving files, for example.
You edit files in /etc directly to suit your specific needs; packaging
is designed not to stomp on your changes.
Therefore it's not clear to me that this is a bug; rather it's just that
the default configuration shipped is the opposite of what you happen to
need in your particular case.
Accordingly I'm setting the status to Incomplete, but if you disagree,
please feel free to explain and reopen.
** Changed in: quagga (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777348
Title:
init.d/quagga has erroneous $remote_fs in LSB headers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/quagga/+bug/1777348/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
