Yes, thats the way to gokkremitzki wrote: ↑Sat Apr 14, 2018 10:22 amTry sudo apt remove \*opencascade\* and re-attempt upgrading freecad-daily.

Yes, thats the way to gokkremitzki wrote: ↑Sat Apr 14, 2018 10:22 amTry sudo apt remove \*opencascade\* and re-attempt upgrading freecad-daily.
It's almost surely a bug just like requiring removal of opencascade packages to install OCCT packages (which is just a rename on top of a version bump) but since the workaround is so simple it's something we can address going forward as we refine the packaging.reox wrote: ↑Sat Apr 14, 2018 10:32 amYes, thats the way to gokkremitzki wrote: ↑Sat Apr 14, 2018 10:22 amTry sudo apt remove \*opencascade\* and re-attempt upgrading freecad-daily.But still - you can install different -doc version. I think usually there should be a dependency on the doc package to the version of the binary package.
Code: Select all
...
Error in `/usr/share/doc-base/freecad-daily-development-documentation', line 14: `Index' value missing for format `html'.
Note: `install-docs --verbose --check file_name' may give more details about the above error.
Registering documents with dwww...
Registering documents with scrollkeeper...
Setting up freecad-daily (0.18~beta1+git201804141331~ubuntu16.04.1) ...
Setting up freecad-daily-doc (0.18~beta1+git201804141331~ubuntu16.04.1) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Processing triggers for menu (2.1.47ubuntu1) ...
Where does this come from? I don't think we have this.
It's automatically appended to package names by Launchpad at build time. It's always a 1 at the end. Before that the code name would be added instead (xenial1). Don't ask me why!
Have you tried installing the freecad-daily-doc package? I just did, and I can confirm the error.
We really have this file installed with freecad-daily-doc.
Well, two separate updates, one for FC18 itself, and one for the doc, show up. If the doc did not change, then why did it show up as an update?Besides, why are you updating the documentation every time there's an update? The package never changes from one version to the other, it just got updated for 0.17, and it won't again until the official 0.18 release.