[bug-notifications] [gtk_engines 0004721]: Sparc package includes 386 files.

Mantis Bug Tracker noreply at opencsw.org
Tue Mar 8 22:23:48 CET 2011


A NOTE has been added to this issue. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4721 
====================================================================== 
Reported By:                james
Assigned To:                phil
====================================================================== 
Project:                    gtk_engines
Issue ID:                   4721
Category:                   packaging
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2011-03-06 16:32 CET
Last Modified:              2011-03-08 22:23 CET
====================================================================== 
Summary:                    Sparc package includes 386 files.
Description: 
$ uname -p
sparc
$ file /opt/csw/lib/gtk-2.0/2.10.0/engines/libclearlooks.so
/opt/csw/lib/gtk-2.0/2.10.0/engines/libclearlooks.so:   ELF 32-bit LSB
dynamic lib 80386 Version 1 [FPU], dynamically linked, stripped


looks suspect.  I've not checked the 386 package for sparc files.
====================================================================== 

---------------------------------------------------------------------- 
 (0008880) dam (administrator) - 2011-03-08 21:49
 https://www.opencsw.org/mantis/view.php?id=4721#c8880 
---------------------------------------------------------------------- 
Which ones are bogus? checkpkg is the authoritative tool. If it reports an
error which is not an error it needs either fixing in checkpkg or
overriding it in the package and properly documenting it in cswreleasemgr.

Please note that overriding or fixing is NOT optional as checkpkg will be
run against the whole catalog and there must be no reported errors on
submitted packages.

The buildfarm is synced upon reuqest as it has always been. As you
obviously know what you have released and what you are building you can
request an update at any time at buildfarm at .

Best regards

  -- Dago 

---------------------------------------------------------------------- 
 (0008881) phil (manager) - 2011-03-08 22:23
 https://www.opencsw.org/mantis/view.php?id=4721#c8881 
---------------------------------------------------------------------- 
"[gar] checkpkg is the authoratative tool"

Says who?
I dont recall a resolution on this. Last I heard, the "documented
policies" are the only "authority".

Nor do I recall any resolution on this "not optional" thing you refer to.

If you really want gar checkpkg to be treated that way, then to be right,
CHANGES to checkpkg should have to be approved in some official way.
That does not happen.

Any rate, I dont feel like arguing further on this. When the machines are
updated, I'll rebuild the package with fixed dependancies, and copyright
notice.

If you think that more should be done to the package, feel free to take it
over yourself.



More information about the bug-notifications mailing list