Issue 111813 - instsetoo_native: Missing .archive flag
Summary: instsetoo_native: Missing .archive flag
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: DEV300m77
Hardware: Unknown All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2010-05-25 09:42 UTC by kendy
Modified: 2013-03-11 15:02 UTC (History)
1 user (show)

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

The proposed patch. (6.08 KB, patch)
2010-05-25 09:44 UTC, kendy
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this issue.
Description kendy 2010-05-25 09:42:25 UTC
I am getting the following when the PKG_FORMAT is unset:

Entering /local/ooo-build/ooo-build/build/dev300-m77/instsetoo_native/util

dmake:  line 222:  Error: -- Missing targets or attributes in rule
ERROR: error 65280 occurred while making

Adding .archive to all such misbehaving targets (as it is in
"openoffice_%{$(PKGFORMAT:^".") .archive}") seems to help, please have a look at
the attached patch.
Comment 1 kendy 2010-05-25 09:44:55 UTC
Created attachment 69618 [details]
The proposed patch.
Comment 2 2010-05-25 16:28:21 UTC
is -> hjs: please have a look at this patch.
Comment 3 hjs 2010-06-11 12:17:59 UTC
@kendy: there had been quite some changes in that area since m77. could you
check if your problem still exists?
on first glance your patch enables packing all installsets as archive and just
fixes your problem by chance...
Comment 4 2010-09-02 09:57:17 UTC
This is a patch.
Comment 5 Rob Weir 2013-03-11 15:02:52 UTC
I'm adding this comment to all open issues with Issue Type == PATCH.  We have 220 such issues, many of them quite old.  I apologize for that.  

We need your help in prioritizing which patches should be integrated into our next release, Apache OpenOffice 4.0.

If you have submitted a patch and think it is applicable for AOO 4.0, please respond with a comment to let us know.

On the other hand, if the patch is no longer relevant, please let us know that as well.

If you have any general questions or want to discuss this further, please send a note to our dev mailing list: