similar to: openssh-3.1p1, buildpkg.sh on Solaris 8

I am attempting to successfully run the buildpkg.sh script which is located in the contrib/solaris directory. I am receiving the following error: Building pkginfo file... Building prototype file... Building package.. ## Building pkgmap from package prototype file. ## Processing pkginfo file. pkgmk: ERROR: parameter <VERSION> cannot be null ## Packaging was not successful. pkgtrans: ERROR:

I've just commited the patch below to buildpkg.sh.in to HEAD Just in case anyone is using "make package" to build a SVR4 style package, I thought I'd give a heads the default name for $POST_MAKE_INSTALL_FIXES has changed. --- buildpkg.sh.in.old 2005-12-28 14:24:55.856729016 -0800 +++ buildpkg.sh.in 2006-02-12 10:04:06.383475017 -0800 @@ -35,7 +35,7 @@ SYSVINITSTART=S98

http://bugzilla.mindrot.org/show_bug.cgi?id=1038 Summary: buildpkg.sh postinstall script does not install RC links using installroot and non-symlinks. Product: Portable OpenSSH Version: 4.0p1 Platform: UltraSparc OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component:

Hi, version.h in OpenSSH_3.1p1 has an Newline after #define SSH_VERSION "OpenSSH_3.1p1" so tail -1 ../../version.h | sed -e 's/.*_\([0-9]\)/\1/g' | sed 's/\"$//' does give back a version number regards Oliver -- Oliver F?nger - Phone +49 201 8501 319 Cityweb Network GmbH & Co. KG Friedrichstr. 12 - Fax +49 201 8501 104 45128 Essen - email

Hello all, I was finally able to create the OpenSSH package for Solaris 8 10/01. The problem I have now is that I will still need to have entropy ready prior to openssh-3.1p1 package installation. Otherwise there is no entropy pool available (with the new servers) and key generation fails. With the previous versions of openssh, I used SUN's "makeOpenSSHPackage.ksh" script and was

I have a minor issue with the 'buildpkg.sh' script in the contrib/solaris directory for OpenSSH (3.4p1 in my case) that I'm hoping might be solvable. First off, I'd like to say that I've been quite happy with the script; for interactive installs, it's worked great. My problem is occurring due to my attempts to make it work non-interac- tively, however, within an init

Hello, I don't know how off the wall this question will be, but first let me say that I've found your buildpkg.sh script very useful in creating an OpenSSH package for use on my Solaris systems. Currently I'm trying to set up a fully automated JumpStart system at my workplace, and I'm realizing that the 'postinstall' script (and possibly some of the other install scripts)

Hi, The line grabbing the version out of version.h is slightly broken in 3.1p1: VERSION=`tail -1 ../../version.h | sed [.....] because there's an extra blank line at the end of version.h. It would be more robust if the script did something like this instead: VERSION=`grep SSH_VERSION ../../version.h | sed [....] Cheers, Chris

Hi, thanks for this great work. Just a minor point - maybe you should mention the rm -rf $FAKE_ROOT command within your README file: It caught me unexpected and I was looking a couple of minutes for the package artifact before I actually read the last line. Regards, Burkhard Kohl Lead Engineer Content Management burkhard.kohl at intershop.de INTERSHOP? http://www.intershop.de INTERSHOP

(Shame on me: wrong filename in last posting, now here are correct diffs) in contrib/solaris/ (openssh-SNAP-20011017.tar.gz) 1) buildpkg.sh makes wrong link for /etc/init.d/opensshd 2) /etc/init.d/opensshd has not-working killproc here my version tested on Solaris 2.4 and 8 (no pgrep with solaris 2.4, XARGS was undefined, simpler syntax) J?rg --- contrib/solaris/buildpkg.sh Fri Oct 12

Hello Ben Lindstrom, I tried your package creation scripts for Solaris which are contributed with the new OpenSSH Version 3.0.0p1. Nice that you develop these scripts but I run into a major problem installing the package which was created by the script. On our Solaris hosts /usr/local is only a symbolic link to /opt/local. After installing the OpenSSH package the symbolic link was removed and a

Here is a small patch for OpenSSH 3.2.3p1.. When the package postinstall script runs, it presumes that the package will be installed relative to the current / directory.. If this package is installed as part of a Solaris Jumpstart installation, this will not be the case. Consequentially, the /etc/ssh/sshd_config.default will never get copied to /etc/ssh/sshd_config on the new operating system.

I've made some changes to buildpkg.sh to make it easier for package builders to add their local changes. I'd like people that use buildpkg.sh to test and comment on these changes before I commit them to CVS. None of the defaults have changed. Some of the patch is is just moving chunks of code to a different location to make some of the enhancements work. Some things you may find

The message is a warning message, (which is new), but it still works. I guess the notes could warn you a warning was coming! We might re-think this, I suggest. It began as an example that forced you to come to grips with the recycling rule, but it is a bit obsolete now. In S-PLUS 6.x it actually fails. Perhaps we don't need to be quite so thorough about this after all and use a more

Ben, I am trying to create a package for Openssh.3-1p1, but the /contrib/solaris/buildpkg.sh script failes with the following errors: ./mkinstalldirs /tools/OpenSSH/openssh-3.1p1/contrib/solaris/package/usr/local/b in mkdir /tools/OpenSSH/openssh-3.1p1/contrib/solaris/package/usr/local/bin ./mkinstalldirs /tools/OpenSSH/openssh-3.1p1/contrib/solaris/package/usr/local/s bin mkdir

(Sent to linux-raid, linux-kernel and ext3-users since I'm not sure what type of issue this is) I've got a test system here running Redhat 7.1 + stock 2.4.9 with these patches: http://www.fys.uio.no/~trondmy/src/2.4.9/linux-2.4.9-NFS_ALL.dif http://www.zip.com.au/~akpm/ext3-2.4-0.9.6-249.gz http://domsch.com/linux/aacraid/linux-2.4.9-aacraid-20010816.patch All three patches applied

leave it for another day to be sure. > It would help running the driver in debug mode > > /path/to/usbhid-ups -DDD -a upsname > > The interesting parts will have 'HIDGetDataValue' in them and a few > lines before that will tell us which report it attempted to retrieve. I've done that and included the syslog output in the same file. The logfile is attached and

Dear all, we seek a talented and motivated post-doc to develop computational methods for inferring the molecular basis of genetic diseases by integration of personal omics data. Research topics include: identifying causal mutations of rare disease patients by meta-analysis; inferring disease-causing molecular pathways from genotype, phenotypes, and omics profile of patient-derived cell lines

OK, I feel like an idiot, but I can't get 3.1p1 to compile under Solaris 8. Older versions I've gotten set up, but can't with this latest one. I have followed both the general directions and the directions in contrib/solaris, and neither one works. Since I have Solaris, here's the output from the directions in contrib/solaris... ./configure --with-pam

Forwarded message: > In $openSSH/contrib/solaris/buildpkg.sh > line 13: > VERSION=`tail -1 ../../version.h | sed -e 's/.*_\([0-9]\)/\1/g' | sed 's/\"$//'` > needs to change to > line 13: > VERSION=`tail -2 ../../version.h | sed -e 's/.*_\([0-9]\)/\1/g' | sed 's/\"$//'` > > This fixes the pkgcreation problem on Solaris 8 This