Issue 127774 - Updating 4.1.5 to 4.2.0 fails with error
Summary: Updating 4.1.5 to 4.2.0 fails with error
Status: RESOLVED FIXED
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: 4.2.0-dev
Hardware: All Linux, all
: P3 Normal (vote)
Target Milestone: 4.2.0
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: regression
: 127645 128062 (view as issue list)
Depends on:
Blocks:
 
Reported: 2018-05-07 21:07 UTC by Pedro
Modified: 2020-11-03 13:56 UTC (History)
6 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: 4.1.7
Developer Difficulty: Medium
jim: 4.2.0_release_blocker+


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Pedro 2018-05-07 21:07:30 UTC
Bug happens with the very recent version 
AOO420m1(Build:9800) - Rev. 1830998
2018-05-05_20:25:59 - Rev. 1831002

The last version that updates correctly from 4.1.5 to 4.2.0 is r1816311 from Jim's archive

All newer versions return

dpkg: error processing archive openoffice-core01_4.2.0-1_amd64.deb (--install):
trying to overwrite '/opt/openoffice4/program/gconfbe1.uno.so', which is also in package openoffice-gnome-integration 4.1.5-1

Errors were encountered while processing:
openoffice-core01_4.2.0-1_amd64.deb

I'm using the following commands

sudo dpkg -i *.deb
cd desktop-integration
sudo dpkg -i *.deb

If I run sudo dpkg -i openoffice-core01*.deb again, it works. But this is a workaround.
Comment 1 Matthias Seidel 2018-09-15 10:46:36 UTC
Confirmed by several user reports.
Comment 2 damjan 2018-09-22 08:28:42 UTC
In the latest trunk:

$ grep gconfbe1 scp2 -R
scp2/source/gnome/file_gnome.scp:    Name = STRING(CONCAT2(gconfbe1.uno,UNXSUFFIX));

and that main/scp2/source/gnome/file_gnome.scp has:

#ifdef ENABLE_GCONF
File gid_File_Lib_Gconfbe
    TXT_FILE_BODY;
    Styles = (PACKED);
    Dir = SCP2_OOO_BIN_DIR;
    Name = STRING(CONCAT2(gconfbe1.uno,UNXSUFFIX));
End
#endif

That file is identical in branches/AOO410, branches/AOO415, and branches/AOO416.

Where does that DEB come from?
Comment 3 damjan 2018-09-22 09:26:07 UTC
Apparently in main/setup_native/source/packinfo/packinfo_office.txt:

Start
module = "gid_Module_Optional_Gnome"
solarispackagename = "%BASISPACKAGEPREFIX%WITHOUTDOTOOOBASEVERSION-gnome-integratn"
solarisrequires = "%BASISPACKAGEPREFIX%WITHOUTDOTOOOBASEVERSION-core01, SUNWgnome-config, SUNWgnome-vfs, SUNWlibC, %BASISPACKAGEPREFIX%WITHOUTDOTOOOBASEVERSION-core04, %BASISPACKAGEPREFIX%WITHOUTDOTOOOBASEVERSION-core05"
packagename = "%BASISPACKAGEPREFIX-gnome-integration"
linuxreplaces = "ooobasis3.0-gnome-integration,ooobasis3.1-gnome-integration,ooobasis3.2-gnome-integration,ooobasis3.3-gnome-integration,ooobasis3.4-gnome-integration"
freebsdrequires = "%BASISPACKAGEPREFIX-core01"
requires = "%BASISPACKAGEPREFIX-core01"
findrequires = "find-requires-gnome.sh"
copyright = "2012-2018 by The Apache Software Foundation"
solariscopyright = "solariscopyrightfile"
vendor = "Apache Software Foundation"
description = "Gnome integration module for %APACHEPROJECTNAME %PRODUCTVERSION"
destpath = "/opt"
packageversion = "%OOOPACKAGEVERSION"
End

but the only changes to that file between branches/AOO4xx and trunk are to copyright years.
Comment 4 Pedro 2018-09-23 14:46:28 UTC
(In reply to damjan from comment #2)

> That file is identical in branches/AOO410, branches/AOO415, and
> branches/AOO416.

That is expected. The bug is in the trunk (4.2.0) not in branch 4.1.x
 
> Where does that DEB come from?

From the Buildbot. Example AOO420m1(Build:9800) - Rev. 1841506
2018-09-20_22:11:13-Rev.1841519
from
https://ci.apache.org/projects/openoffice/install/linux32/
Comment 5 Pedro 2019-01-25 11:15:34 UTC
Bug still occurs with build 4.2.0-dev-r1851640
Propose as Release Blocker
Comment 6 Mechtilde 2019-03-13 19:43:09 UTC
(In reply to damjan from comment #3 and#2)

I saw that message today (2019-03-13).

This means the file gconfbe1.uno.so changes from the deb package openoffice-gnome-integration 4.1.6-1 to openoffice-core01_4.2.0-1

This is an issue of packaging.

If you can tell me the location where I can find the definition which files go into which packages I will have a look.

Kind regards

Mechtilde
Comment 7 Mechtilde 2019-03-13 19:45:51 UTC
*** Issue 128062 has been marked as a duplicate of this issue. ***
Comment 8 Mechtilde 2019-03-18 18:46:04 UTC
*** Issue 127645 has been marked as a duplicate of this issue. ***
Comment 9 Ariel Constenla-Haile 2019-10-24 14:50:03 UTC
(In reply to Mechtilde from comment #6)
> If you can tell me the location where I can find the definition which files
> go into which packages I will have a look.

* main/scp2/source/gnome/file_gnome.scp defines the file

  gid_File_Lib_Gconfbe

* main/scp2/source/gnome/module_gnome.scp defines the module

  gid_Module_Optional_Gnome which includes gid_File_Lib_Gconfbe

* main/setup_native/source/packinfo/packinfo_office.txt defines the name of the package for that module

  module = "gid_Module_Optional_Gnome" 
  packagename = "%BASISPACKAGEPREFIX-gnome-integration"

Quite strange the library ends up inside openoffice-core01
Comment 10 truckman 2020-10-31 12:53:46 UTC
This call in solenv/bin/par2script.pl:
  print "Adding definitions without assignment to the root\n";
  par2script::module::add_to_root_module();
assigns gid_File_Lib_Gconfbe and many other gids, including many font entries.  The lower level code where this is happening is in solenv/bin/modules/par2script/module.pm:
                my $gid;
                foreach $gid ( keys %{$definedgids} )
                {
                        if ( ! exists( $assignedgids->{$gid} ))
                        {
                                if ( $gidstring eq "" )
                                {
                                        $gidstring = $gid;
                                }
                                else
                                {
                                        $gidstring = "$gidstring,$gid";
                                }

                                $assignedgids->{$gid} = 1;
                        }
                }

The font upgrades between AOO417 and AOO418 may be triggering a bug that affects the packaging of other files.
Comment 11 truckman 2020-10-31 23:42:59 UTC
Should be fixed by a4f1bfeeff787044d837fdb2375117a5aeed8a04 (trunk) and
843e393eeebd20e429574a4ceb7b5beb1cd55b39 (AOO42X)
Comment 12 Pedro 2020-11-03 13:56:08 UTC
Fixed in build

AOO420m3(Build:9822)  -  Rev. 59c05f3d3d
2020-11-01_12:42:56 - Rev. 59c05f3d3d636b173ac1a8a4efed0e0ff04eadd1

Updated from 4.1.7 without any errors!

Thank you Don!