> I've noticed this problem with the 3.6 and 3.7 PPA packages at:
> https://launchpad.net/~gluster/+archive/ubuntu/glusterfs-3.6
> https://launchpad.net/~gluster/+archive/ubuntu/glusterfs-3.7
>
> Do you know if there are plans to include this change in those too?
I'm not an expert at Debian packages, but looking at the packaging bits
in git that were used to create the 3.6 .debs -- both in semiosis' old
git repo and the new one at github.com:gluster/glusterfs-debian.git --
it looks to me like the upstart bits are in the 3.6 .debs but not in the
3.7 .debs. Here's an excerpt of the vivid 3.6 rules file, same as 3.5:
...
override_dh_installinit:
dh_installinit -pglusterfs-client --upstart-only --no-start
--name=mounting-glusterfs
dh_installinit -pglusterfs-server --upstart-only
...
I'll add them to the 3.7 builds. How they were not included is certainly
a mystery to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268064
Title:
Remote glusterfs mounts fail during boot because network is not yet
available
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1268064/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
