After having a CRASH with LO 22.214.171.124alpha+, attempt to get latest Win32 package. Find Dev Win32@51 with a date of 2015-01-09_23.21.44.
Real name : [ libreoffice-4-4~2015-01-09_23.21.44_LibreOfficeDev_126.96.36.199.0_Win_x86_en-US_de_ar_ja_ru_qtz.msi ]
Download, and save in storage vault.
Experience next crash with 4.4 alpha, and get the documentation ready for a bug , but remeber that there is the new build.
Attempt to install new build over existing dev build.
System unpacks package until it gets 1/2 way through. Gets error that CAB is broken.
Think taht something MUST have happened with my D/L getting corrupted, find Dev Build with same date, and earlier build time 11.06.04.
Download this package.
Hey its 145 MB...? 50 MB larger than Dev 23.31.
Download Dev 11.06.04 downloads with no errors. Install runs fine.
Find Dev 23.31, package is only 103 MB...?
Re-download, but no SHA1 verification files.
Assume that build got broken somehow from 11.06 to 23.21.44.
Update to change Platform and Processor type.
Path of DEFECTIVE download at
path with working build at:
I hope this helps.
(In reply to Richard_416282 from comment #0)
> After having a CRASH with LO 188.8.131.52alpha+, attempt to get latest Win32
> package. Find Dev Win32@51 with a date of 2015-01-09_23.21.44.
> Real name : [
> US_de_ar_ja_ru_qtz.msi ]
Tinderbox builds off the tip of the branches (4.3, 4.4, master, etc..) sometimes fail. In general, I'd suggest that you just wait for the next daily and try testing again.
I believe the version should be 184.108.40.206alpha0+ Master, right?
> Attempt to install new build over existing dev build.
> System unpacks package until it gets 1/2 way through. Gets error that CAB is
> Think taht something MUST have happened with my D/L getting corrupted, find
> Dev Build with same date, and earlier build time 11.06.04.
> Download this package.
> Hey its 145 MB...? 50 MB larger than Dev 23.31.
> Download Dev 11.06.04 downloads with no errors. Install runs fine.
> Find Dev 23.31, package is only 103 MB...?
> Re-download, but no SHA1 verification files.
> Assume that build got broken somehow from 11.06 to 23.21.44.
Hmm, hmm. It's probable that some commit didn't quite build correctly. Uusally this will clear up in a day or so, or you can try building that version locally if you're interested in faster test results.
Are you still seeing the same problem with the latest 4.4-branch and 4.5-branch builds?
Status -> NEEDINFO
(change Status -> UNCONFIRMED after you get test results)
LO daily has the latest date of 2015-01-16.
this has a URL of:
IS this what you refer to as 'branch'?
While LO daily master has the URL of:
I am guessing at this point because there is no clear definition(s) of Branch, Master, etc after they are run through the compilers(Make Process?).
Since My PC has a limited HW platform, I am sure I could cobble something together, but it is not very easy, to define the flow on how to create (or roll your own build box) or facilitate the transition to a stand alone build process from the Source and have it regularly updated (RSync perhaps).
Sorry, I am not quite up to the source-make-build-execute level yet.
The best I can do (at the moment) is download the tinderbox builds, and try if they work.
See the image attached from the daily of 2015-01-16.
I am assuming that the path that poins to the 'master', has the code for the 4.5 tree, but not sure which branch level to test against?
There are 3-4 choices for the x86 platform, and nothing specific to AMD processors that can handle x64 stuff (yet).
~Hope this is the info you need. Will give a go with the latest tinderbox 220.127.116.11alpha0 build. So far it is 124 MB. this is a good sign. at least it is not missing the ~25MB of CAB that was missing from the 2015-01-09 Build.
Created attachment 112373 [details]
Image of path to Tinderbox Build (Latest for x64 Win7 Systems??)
Attached Image from previous Comment.
(In reply to Richard_416282 from comment #4)
Any builds in this directory are created daily, and are not designed for production work. They're only for QA and testing:
Those builds may or may not work. If a build doesn't work today, then wait for the next build tomorrow and see if it works.
> Since My PC has a limited HW platform, I am sure I could cobble something
> together, but it is not very easy, to define the flow on how to create (or
> roll your own build box) or facilitate the transition to a stand alone build
> process from the Source and have it regularly updated (RSync perhaps).
What's your goal here? Is there a particular reason to use a daily build vs. a release build?
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.
For more information about our NEEDINFO policy please read the wiki located here:
If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
This NEEDINFO message was generated on: 2015-07-18
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):
a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue.
Please do not:
a) respond via email
b) update the version field in the bug or any of the other details on the top section of FDO
Message generated on: 2015-09-03