Issue 56329 - m135: offapi breaker
Summary: m135: offapi breaker
Status: CLOSED FIXED
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: current
Hardware: All All
: P1 (highest) Trivial (vote)
Target Milestone: OOo 2.0.1
Assignee: pavel
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-20 18:53 UTC by pavel
Modified: 2005-12-09 08:28 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description pavel 2005-10-20 18:53:02 UTC
Hi,

while building m135's offapi:

regcompare -f -t -u -r1 ../type_reference/OO_20/types.rdb -r2
../unxlngi6.pro/ucr/types.db
regcompare -f -t -u -r1 ../type_reference/OO_20/types_doc.rdb -r2
../unxlngi6.pro/ucrdoc/types_doc.db \
        && echo > ../unxlngi6.pro/misc/registrycheck.flag
SERVICE: /UCR/com/sun/star/sdb/OfficeDatabaseDocument
  incompatible change: Reference 2 ('XCloseable') of r2 is a new reference
compared to this service in r1 and is not 'optional'
SERVICE: /UCR/com/sun/star/text/Text
    service1 contains 1 more references as service2
  incompatible change: Reference 5 ('XEnumerationAccess') in 'r1' is not longer
a reference of this service in 'r2'
regcompare: registries are incompatible: 2 differences!
dmake:  Error code 11, while making '../unxlngi6.pro/misc/registrycheck.flag'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/disk3/oo/BuildDir/ooo_SRC680_m135_src/offapi/util

Replacing the directory OO_20 with m134 files helped.
Comment 1 pavel 2005-10-20 20:58:40 UTC
Why we do have these *large* and *binary* files in CVS?

They are probably generated -> generate them in the build process?

-rw-r--r--    1 oo       users     3375104 Apr  5  2005 types.rdb
-rw-r--r--    1 oo       users     7438336 Apr  5  2005 types_doc.rdb
Comment 2 rt 2005-10-21 08:48:33 UTC
-> Pavel: they are in CVS because we from now on have to compare everything
against OOo2.0 release for compatibility. These files are the reference to check
against.

-> JSC: Jürgen, what's wrong here? Please check and assign this issue to the
correct owner.
Comment 3 rt 2005-10-21 10:23:07 UTC
Just FYI:
This one slipped through our build because the registry check states
'incompatible change', but nothing about 'error'. So it did not trigger the
error filters of our build server. I just added a new filter especially for this
mesage to prevent such problems in the future.
Comment 4 jsc 2005-10-21 10:38:54 UTC
I have corrected the type library. There were two types containing compatible
changes which were not in the reference type library.
Its always a problem when the reference library changed on a cws and other
changes on other cw's integrated on the master in the same step.
Comment 5 jsc 2005-10-27 16:28:47 UTC
please verify

re-open issue and reassign to pjanik@openoffice.org
Comment 6 jsc 2005-10-27 16:36:13 UTC
second try, please verify and close

Comment 7 pavel 2005-10-27 17:15:59 UTC
verified in my local build.
Comment 8 pavel 2005-10-27 17:17:28 UTC
verified, closing.
Comment 9 thorsten.ziehm 2005-12-09 08:28:46 UTC
Fixed in master m135, therefore I set the target to OOo2.0.1.