SFE IPS Package Repository

  • Posted on: 13 July 2016
  • By: tomww

In a hurry to get IPS packages? Go to: http://sfe.opencsw.org/quickrepolinks

These IPS Packages are built from RPM style build recipes hosted as a open source repository here http://pkgbuild.svn.sourceforge.net/viewvc/pkgbuild/spec-files-extra/trunk/

Comments

Hi,

Getting errors when downloading following pckages:
Processing packages for publisher localhosts11 ...
Retrieving and evaluating 1502 package(s)...
PROCESS ITEMS GET (MB) SEND (MB)
sfe/developer/gcc/src 0/11 1.6/107.6 0.0/145.8pkgrecv: Invalid contentpath usr/share/src/SFEgcc-5.4.0/SOURCES/gcc-5.4.0.tar.bz2: chash failure: expected: 679fd795182576d44eb36801aa3dc16c60e6bd0e computed: 9efff1cd69d4ed49d24dd5673b0e176537d6bb22. (happened 4 times)

and on localhost12 also
Processing packages for publisher localhosts12 ...
Retrieving and evaluating 829 package(s)...
PROCESS ITEMS GET (MB) SEND (MB)
sfe/developer/gcc/src 0/7 1.6/119.3 0.0/161.0pkgrecv: Invalid contentpath usr/share/src/SFEgcc-5.4.0/SOURCES/gcc-5.4.0.tar.bz2: chash failure: expected: 679fd795182576d44eb36801aa3dc16c60e6bd0e computed: 9efff1cd69d4ed49d24dd5673b0e176537d6bb22. (happened 4 times)

So i am guessing that there are some issues with the repo
REgards
Filip

Hi Filip,
your pkgrecv looks like you are doing a (not terribly useful) mirroring of the repository. It is very much too big for that.
First of all this is a repository which changes rapidly. So once you finish the receive process, you would have to start over to get the next bunch of fixes and on and on...
Secondly, the hosting is not of a sizing which can take the load of mirroring it.
So please do not mirror this repository. You might not have use for many many gigabytes of dead source archive packages. You must know it contains all, sources and compiled packages.
However it is perfectly okay to do a "pkgrecv -r" for exactly those packages you need. This produces the same load for the system as if someone actually installs packages.

The file you noted in the error message is indeed too short, normally the next repository sync will repairs this.

Mirroring the development repos was never intended. However, there are plans to make up kind of a "release" repository. But this would need some helping hands to test and then promote the packages which are working well to the release repository.

Regards,
Thomas