Laurent Blume | 8 Feb 14:24 2016

Some 64 bit subdirectories not merged into pkgroot

Hello all,

It's been pointed to me that the Samba 3 package does not contain the
needed symlinks to have NSS/PAM work in 64 bit.
This is odd, because when I worked on it, I took time to check it was
working.

I've double-checked my recipe, it appears to be creating the symlinks
for each MEMORY_MODEL, and that shows in the install directories, all good:
work/install-isa-pentium_pro/usr/lib/nss_winbind_csw.so.1
work/install-isa-pentium_pro/usr/lib/nss_wins_csw.so.1
work/install-isa-pentium_pro/usr/lib/security/pam_winbind_csw.so
work/install-isa-pentium_pro/usr/lib/security/pam_smbpass_csw.so

work/install-isa-amd64/usr/lib/amd64/nss_winbind_csw.so.1
work/install-isa-amd64/usr/lib/amd64/nss_wins_csw.so.1
work/install-isa-amd64/usr/lib/security/amd64/pam_winbind_csw.so
work/install-isa-amd64/usr/lib/security/amd64/pam_smbpass_csw.so

But in the pkgroot, only the 32 bit version is there, no 64:
work/pkgroot/usr/lib/nss_winbind_csw.so.1
work/pkgroot/usr/lib/nss_wins_csw.so.1
work/pkgroot/usr/lib/security/pam_smbpass_csw.so
work/pkgroot/usr/lib/security/pam_winbind_csw.so

How come? mgar acting up? Considering the age of the current Samba 3
package, it would have been for around a year, at least.

Laurent

(Continue reading)

rupert THURNER | 6 Feb 21:03 2016

ConfigParser.NoSectionError: No section: 'rest'

i currently try to respin python builds to somehow remove the old gcc
path, as i am still not sure where it is coming from. i get the below
error and i am not sure where this comes from:

rupert <at> experimental10s
[experimental10s]:~/opencsw/lang-python/pysetuptools/trunk > mgar
spotless package
...

## Packaging complete.
mkp: exec( pkgtrans -s /home/rupert/spool/5.10-sparc
/tmp/py_setuptools_stub-3.8.1,REV=2016.02.06-SunOS5.10-all-CSW.pkg
CSWpysetuptools )
Transferring <CSWpysetuptools> package instance
mkp: exec( gzip -9 -f
/tmp/py_setuptools_stub-3.8.1,REV=2016.02.06-SunOS5.10-all-CSW.pkg )
mkp: exec( mv /tmp/py_setuptools_stub-3.8.1,REV=2016.02.06-SunOS5.10-all-CSW.pkg.gz
/home/rupert/pkgs/06.Feb.2016 )
mkp: exec( rm -rf /home/rupert/spool/5.10-sparc/CSWpysetuptools )
Traceback (most recent call last):
  File "/home/rupert/opencsw/.buildsys/v2/gar//bin/../lib/python/checkpkg2.py",
line 268, in <module>
    main()
  File "/home/rupert/opencsw/.buildsys/v2/gar//bin/../lib/python/checkpkg2.py",
line 140, in main
    debug=options.debug)
  File "/home/rupert/opencsw/.buildsys/v2/gar/lib/python/package_stats.py",
line 115, in __init__
    pkgdb_url=self.config.get('rest', 'pkgdb'),
  File "/opt/csw/lib/python2.6/ConfigParser.py", line 532, in get
(Continue reading)

Riccardo Mottola | 5 Feb 16:31 2016

freetype header problem / CFLAGS

Hi,

I am trying to update gnustep-back and extend it to solaris 9 too. I 
just installed an updated version of FreeType which matches solaris 10.
pkg config is installed too, same version.

/opt/csw/bin/pkg-config --cflags freetype2
-I/opt/csw/include/freetype2 -I/opt/csw/include

That is "freetype2" is the sound thing.

when I do build, I see this:
  Compiling file XGFont.m ...
In file included from ../../Headers/x11/wraster.h:46:0,
                  from ../../Headers/xlib/XGPrivate.h:34,
                  from XGFont.m:40:
/usr/openwin/include/X11/Xlib.h:32:0: warning: ignoring #pragma ident 
[-Wunknown-pragmas]
In file included from ../../Headers/x11/wraster.h:47:0,
                  from ../../Headers/xlib/XGPrivate.h:34,
                  from XGFont.m:40:
/usr/openwin/include/X11/Xutil.h:56:0: warning: ignoring #pragma ident 
[-Wunknown-pragmas]
In file included from /usr/openwin/include/X11/Xft/Xft.h:35:0,
                  from ../../Headers/xlib/XGGState.h:38,
                  from XGFont.m:41:
/opt/csw/include/ft2build.h:56:38: fatal error: 
freetype/config/ftheader.h: No such file or directory
compilation terminated.
gmake[7]: *** [obj/xlib.obj/XGFont.m.o] Error 1
(Continue reading)

Carsten Grzemba | 4 Feb 12:07 2016
Picon
Gravatar

IPS package build

I commited some changes for gar.pkg.mk and some other minor changes. I hope there are no side effects for SVR4 package building.

Carsten

Carsten Grzemba | 1 Feb 15:35 2016
Picon
Gravatar

IPS buildhost

Hi Dago,

it is possible to get a Solaris 11 build zone with no installed CSW SVR4 packages, except the build system: mgar, compiler, ...
So we can build IPS packages  successively with the correct dependencies.

What do you think?

Carsten

İhsan Doğan | 30 Jan 22:31 2016
Face

Disk needed for mail server

Hi,

One of the disks on the OpenCSW has failed:

  pool: rpool
 state: DEGRADED
status: One or more devices has experienced an unrecoverable error.  An
        attempt was made to correct the error.  Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
        using 'zpool clear' or replace the device with 'zpool replace'.
   see: http://www.sun.com/msg/ZFS-8000-9P
 scan: scrub repaired 2.64M in 1h10m with 0 errors on Sun Jan 18
04:55:11 2015
config:

        NAME          STATE     READ WRITE CKSUM
        rpool         DEGRADED     0     0     0
          mirror-0    DEGRADED     0     0     0
            c1t0d0s0  ONLINE       0     0     0
            c1t1d0s0  DEGRADED     0     0    23  too many errors

Does anybody has or is willing to sponsor a 73 GB disk for a T2000 machine?

Ihsan

--

-- 
ihsan@...        http://blog.dogan.ch/

Carsten Grzemba | 27 Jan 15:55 2016
Picon
Gravatar

Install SMF's in standard locations

Some questions

1. In Solaris11 is an SMF 'manifest-import' which can triggered if a new SMF is installed. But this SMF covers only the standard locations for SMF /lib/svc/manifest and /var/svc/manifest. I would prefer to use this SMF and install our SMF's also in standard location /var/svc/manifest.

2. Package Repositories: How want we handle our concept of catalogs unstable, testing, ... Want we cover this with different repositories/publishers?

3. Package naming: Our SVR4 packages use a "flat" namespace. IPS use a hirachical one but this is only cosmetics. There are aome lists of the relation of SVR4 and IPS names for some application like this:
https://github.com/MrStaticVoid/spec-files-extra/blob/master/experimental/packagenames.sort_newnames.ts
Should we keep the flat namespace and prefix with opencsw or also establish such hierachic?

4. Packages for x86 and Sparc: IPS can deliver both architectures in one package. Has anyone some experience in building dual-arch IPS packages. Have we made the mgar platform target mandatory for that? 

Any thoughts

Carsten

Juraj Lutter | 26 Jan 17:31 2016

OpenSSL

Hi,

I don't know if you noticed, but FYI:

http://www.securityweek.com/openssl-patch-high-severity-vulnerability

/j

Dagobert Michelsen | 25 Jan 11:28 2016
Gravatar

Buildfarm IPS server for experimental IPS packages

Hi folks,

I setup an experimental IPS repo server on the buildfarm that behaves similar
to /home/experimental for SVR4-packages.

* Creating a new repo

On a Solaris 11 host (like unstable11s or unstable11x) use
  cd /home/ips
  pkgrepo create <reponame>
The repository can now receive packages from inside the buildfarm.

* Using the repo

The IPS repo is accessible at
  https://buildfarm.opencsw.org/ips/
which gives a list about the available repository. The list is currently static and
rebuild every 10 minutes. Please note that Safari is not able to browse the repo
for some technical reason, Firefox and Chrome work fine, though.

dam <at> unstable11s [unstable11s]:/home/ips > pkgrepo list -s http://buildfarm.opencsw.org/ips/dam
HERAUSGEBER NAME                                          O VERSION
opencsw     lsof                                            4.89,5.11:20151229T152446Z
opencsw     lsof                                            4.88,5.11:20150322T130102Z
opencsw     lsof                                            4.88,5.11:20150302T160752Z
opencsw     lsof                                            4.88,5.11:20150301T212923Z
opencsw     sudo                                            1.8.12,5.11:20150309T110254Z

Technically there is a forwarder from the „web“ zone to the „ipsrepo“ zone
which runs on the m3000. From there another Apache is getting the requests and
distrbutes them to the local repo server instances which each run on a different
tcp port.

At the moment the repos are not cleaned up, but I wanted to give you an early
heads up. Just let me know if you encounter any issues.

 <at> Carsten: What do you think about publising build IPS-packages directly into
/home/ips/≤user> ?

Best regards

  — Dago

--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

Jan Holzhueter | 20 Jan 15:55 2016

Reboot T5220 (Buildfram downtime)

Hi,
we need to reboot the T5220 again.
(Still some performance problems we hope to improve)
So this will be another downtime for the buildfram as login etc are
affected too.
I will do this tomorrow morning.
Sorry for the inconvenience

Greetings
Jan

Dagobert Michelsen | 19 Jan 10:33 2016
Gravatar

Re: Python 2.7.11

Hu Jubal,

Am 19.01.2016 um 10:19 schrieb Jubal Skaggs <jubal@...>:
> Ah yes!  Thank you Dago,
> 
> I was able to test it out on sparc and x86 and everything has worked well for me.  I was ready to bring it up to the
next level and get it into "testing" but fear got the best of me.  I'd be happy to bump it up to 2.7.11, can you
give me some guidance as to how to promote the package and what kind of review process there is for something
in place for the promotion?  I'd hate to push something out that didn't meet opencsw standards.

First commit your changes. The rule is „commit early“ so changes do not get lost.
„svn status“ must give an empty result, when you have that UNCOMMITED goes away:
  http://buildfarm.opencsw.org/experimental.html#jubal
Please do not distribute any stuff that as UNCOMMITTED in the name as it is not
reproducable.

Just bump to 2.7.11, commit and put new packages in the experimental directory,
then ask people to test (e.g. on IRC and maintainers <at>  and users <at> ). If there is
no negative feedback in a couple of days you can upload the packages with
  csw-upload-pkg <pkg1> <pkg2> …
from „login“. The promotion to testing is automatic after 14 days without reported
bugs:
  http://buildfarm.opencsw.org/package-promotions/promote-packages.html

Best regards

  — Dago

--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896


Gmane