My original design and implementation explicitly did not suffer from this flaw; the @hidden links account for this. I initially thought that the changes made in bug 1479001 were responsible for this bug because this is the type of conflicting requirement I expected to be caused by those changes; but I've just looked through the code and I don't in fact see how it could cause this particular symptom.
Could I get the output of "find /usr/share/click/preinstalled/ /custom/click/ /opt/click.ubuntu.com/ -ls" at each of the following stages:
* initial installation of OTA8.5
* after running "sudo click unregister" on the list of apps in question (BTW, you don't need "sudo" here, but it shouldn't hurt since we check $SUDO_USER)
* after applying OTA9
My original design and implementation explicitly did not suffer from this flaw; the @hidden links account for this. I initially thought that the changes made in bug 1479001 were responsible for this bug because this is the type of conflicting requirement I expected to be caused by those changes; but I've just looked through the code and I don't in fact see how it could cause this particular symptom.
Could I get the output of "find /usr/share/ click/preinstal led/ /custom/click/ /opt/click. ubuntu. com/ -ls" at each of the following stages:
* initial installation of OTA8.5
* after running "sudo click unregister" on the list of apps in question (BTW, you don't need "sudo" here, but it shouldn't hurt since we check $SUDO_USER)
* after applying OTA9