Summary: | building mdds fails because of mdds 0.5.1 ist not bundled but mdds 0.3.0 | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Gerold Jens Wucherpfennig <gjwucherpfennig> |
Component: | Installation | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | trivial | ||
Priority: | low | ||
Version: | 3.3.0 RC3 | ||
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Gerold Jens Wucherpfennig
2011-01-15 05:44:33 UTC
3.3 wants 0.3.0 and that is correct. (and it actually will fail to build with 0.5.x) What needs 0.5.x is *master* (aka to-be-3.4), and guess what?: rene@frodo:~/LibreOffice/master/build/bootstrap$ grep mdds ooo.lst 5d991377b0ee1ae396c82963bc0084c1-mdds_0.5.1.tar.bz2 -> INVALID I downloaded: http://download.documentfoundation.org/libreoffice/src/libreoffice-build-3.3.0.3.tar.gz then unpacked it, then used "autogen.sh", then used the script "download". The script "download" downloads cf8a6967f7de535ae257fa411c98eb88-mdds_0.3.0.tar.bz2 But in In clone/bootstrap/ooo.lst there is 5d991377b0ee1ae396c82963bc0084c1-mdds_0.5.1.tar.bz2 When building LibreOffice I get the error in the module mdds that mdds 0.5.1 is not available... Is there something wrong with my setup? most probably: rene@frodo:~/LibreOffice/libreoffice-3-3/build/clone/bootstrap$ git status ooo.lst # On branch libreoffice-3-3 nothing to commit (working directory clean) rene@frodo:~/LibreOffice/libreoffice-3-3/build/clone/bootstrap$ grep mdds ooo.lst cf8a6967f7de535ae257fa411c98eb88-mdds_0.3.0.tar.bz2 Are you sure ./download got the correct branch (libreoffice-3-3) instead of master? I wouldn't think so. Switch your clones to libreoffice-3-3 then (bin/g checkout -b libreoffice-3-3 origina/libreoffice-3-3). Might be a bug in download, but it surely is not a bug in the mdds version required. Thanks, I had master instead of the 3.3 branch... |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.