0004721: Sparc package includes 386 files.

(0008875)
phil (reporter)
2011-03-08 18:03

I plonked a new version in http://buildfarm.opencsw.org/experimental/phil/ [^]
Please take a look.

(would certainly explain the problem I was having. I meant to recompile it sooner or later, so this was a good prod for me to do it "sooner" :)

I gave it a try, and it works for me at least.

(0008876)
james (reporter)
2011-03-08 18:39

I've not looked but it the files are the right arch (or you intended them to be there) you've passed my test which was not functional anyway.

(0008877)
phil (reporter)
2011-03-08 19:02

okay then. new packages released.

(0008878)
dam (administrator)
2011-03-08 19:31

Hi Phil,

that package has a ton of problems in checkpkg:
http://pkg.opencsw.org/pkgbrowser/reports/pkgbrowse-phil.html#d5ebb76b17defc6c9b83dc12b71e17dc-error_tags [^]

(0008879)
phil (reporter)
2011-03-08 19:39

Hmm.
Most of those are bogus.
The dependancy thing is valid I suppose... although its not so much "wrong", as "out of date".

It would have been picked up by me properly, if the library packages on the build machines were up to date.
How about fixing that?

(0008880)
dam (administrator)
2011-03-08 21:49

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@.

Best regards

-- Dago

(0008881)
phil (reporter)
2011-03-08 22:23

"[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.

(0010347)
maciej (manager)
2013-04-21 12:19

The package is now rebuilt with GAR and released.

Notes
(0008875) phil (reporter) 2011-03-08 18:03	I plonked a new version in http://buildfarm.opencsw.org/experimental/phil/ [^] Please take a look. (would certainly explain the problem I was having. I meant to recompile it sooner or later, so this was a good prod for me to do it "sooner" :) I gave it a try, and it works for me at least.

(0008876) james (reporter) 2011-03-08 18:39	I've not looked but it the files are the right arch (or you intended them to be there) you've passed my test which was not functional anyway.

(0008877) phil (reporter) 2011-03-08 19:02	okay then. new packages released.

(0008878) dam (administrator) 2011-03-08 19:31	Hi Phil, that package has a ton of problems in checkpkg: http://pkg.opencsw.org/pkgbrowser/reports/pkgbrowse-phil.html#d5ebb76b17defc6c9b83dc12b71e17dc-error_tags [^]

(0008879) phil (reporter) 2011-03-08 19:39	Hmm. Most of those are bogus. The dependancy thing is valid I suppose... although its not so much "wrong", as "out of date". It would have been picked up by me properly, if the library packages on the build machines were up to date. How about fixing that?

(0008880) dam (administrator) 2011-03-08 21:49	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@. Best regards -- Dago

(0008881) phil (reporter) 2011-03-08 22:23	"[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.

(0010347) maciej (manager) 2013-04-21 12:19	The package is now rebuilt with GAR and released.

Relationships

OpenCSW Bug Tracker