From rmottola at opencsw.org  Fri Dec 10 13:07:38 2021
From: rmottola at opencsw.org (Riccardo Mottola)
Date: Fri, 10 Dec 2021 13:07:38 +0100
Subject: built packages, where are they?
In-Reply-To: <8C844679-8976-4EE1-9685-C0EC598B9E69@opencsw.org>
References: <b78f78ad-b5d9-dde0-02f7-d53fc51438bb@opencsw.org>
 <8C844679-8976-4EE1-9685-C0EC598B9E69@opencsw.org>
Message-ID: <05280abe-8fff-148f-a68b-b2d99f32ea78@opencsw.org>

Hi Dago,

Dagobert Michelsen wrote:
> Works for me:
>
> The following packages have been built:  
>   
>   CSWgnustep-make      /home/rmottola/pkgs/gnustep_make-2.9.0,REV=2021.11.15-SunOS5.10-sparc-CSW.pkg.gz  
>   
>         [package-svr4] complete for gnustep-make.  
> rmottola at unstable10s [unstable10s]:~/opencsw/gnustep-make/trunk > ls -l /home/rmottola/pkgs
> total 459
> -rw-r--r--   1 rmottola csw       219865 Nov 15 08:35 gnustep_make-2.9.0,REV=2021.11.15-SunOS5.10-sparc-CSW.pkg.gz
> rmottola at unstable10s [unstable10s]:~/opencsw/gnustep-make/trunk > 

I retried in the weekend and got timeouts when juicing the packages.
Today I retried, everything built:

* Platform solaris9-sparc (built on this host)
? CSWgnustep-make?????
/home/rmottola/pkgs/gnustep_make-2.9.0,REV=2021.12.04-SunOS5.9-sparc-CSW.pkg.gz

* Platform solaris9-i386 (built on host 'unstable9x')
? CSWgnustep-make?????
/home/rmottola/pkgs/gnustep_make-2.9.0,REV=2021.12.10-SunOS5.9-i386-CSW.pkg.gz

* Platform solaris10-sparc (built on host 'unstable10s')
? CSWgnustep-make?????
/home/rmottola/pkgs/gnustep_make-2.9.0,REV=2021.12.10-SunOS5.10-sparc-CSW.pkg.gz

* Platform solaris10-i386 (built on host 'unstable10x')
? CSWgnustep-make?????
/home/rmottola/pkgs/gnustep_make-2.9.0,REV=2021.12.10-SunOS5.10-i386-CSW.pkg.gz

And the packages are indeed there :)

Inserting gnustep_make (i386 SunOS5.10) into catalog unstable i386 SunOS5.10
Inserting gnustep_make (i386 SunOS5.10) into catalog unstable i386 SunOS5.11
Inserting gnustep_make (i386 SunOS5.9) into catalog unstable i386 SunOS5.9
Inserting gnustep_make (sparc SunOS5.10) into catalog unstable sparc
SunOS5.10
Inserting gnustep_make (sparc SunOS5.10) into catalog unstable sparc
SunOS5.11
Inserting gnustep_make (sparc SunOS5.9) into catalog unstable sparc SunOS5.9


May you install them on unstable[9s|9x|10s|10x] so that the hard part
can begin? brand new dependent stuff.

Riccardo

From dam at opencsw.org  Sat Dec 11 14:49:55 2021
From: dam at opencsw.org (Dagobert Michelsen)
Date: Sat, 11 Dec 2021 14:49:55 +0100
Subject: built packages, where are they?
In-Reply-To: <05280abe-8fff-148f-a68b-b2d99f32ea78@opencsw.org>
References: <b78f78ad-b5d9-dde0-02f7-d53fc51438bb@opencsw.org>
 <8C844679-8976-4EE1-9685-C0EC598B9E69@opencsw.org>
 <05280abe-8fff-148f-a68b-b2d99f32ea78@opencsw.org>
Message-ID: <CCA7623B-2700-4BC1-BC9B-4D73BE9057DF@opencsw.org>

Hi Riccardo,

Am 10.12.2021 um 13:07 schrieb Riccardo Mottola via maintainers <maintainers at lists.opencsw.org>:
> And the packages are indeed there :)
> 
> Inserting gnustep_make (i386 SunOS5.10) into catalog unstable i386 SunOS5.10
> Inserting gnustep_make (i386 SunOS5.10) into catalog unstable i386 SunOS5.11
> Inserting gnustep_make (i386 SunOS5.9) into catalog unstable i386 SunOS5.9
> Inserting gnustep_make (sparc SunOS5.10) into catalog unstable sparc
> SunOS5.10
> Inserting gnustep_make (sparc SunOS5.10) into catalog unstable sparc
> SunOS5.11
> Inserting gnustep_make (sparc SunOS5.9) into catalog unstable sparc SunOS5.9
> 
> 
> May you install them on unstable[9s|9x|10s|10x] so that the hard part
> can begin? brand new dependent stuff.

gnustep_make has been installed on unstable9/10/11 sparc and x86.
unstable11x seems unresponse at the moment, I?ll have a look at this
soon.


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


From rmottola at opencsw.org  Fri Dec 17 15:59:38 2021
From: rmottola at opencsw.org (Riccardo Mottola)
Date: Fri, 17 Dec 2021 15:59:38 +0100
Subject: missing libproc.h
Message-ID: <d15aafca-c9e4-71b3-ffc8-2dfa7c7cc797@opencsw.org>

Hi all,

trying again my luck in porting htop - limiting myself to solaris 10 for
now.

There is explicit Solaris support, which is promising. However build
fails for me with:

In file included from AvailableMetersPanel.c:24:0:
./solaris/Platform.h:20:21: fatal error: libproc.h: No such file or
directory


I couldn't indeed find that file. Does anybody know if there is a
missing package, missing update or if it is a Solaris 11 thing and in
case if I can find an equivalent?

Riccardo

From ihsan at opencsw.org  Wed Dec 29 21:07:58 2021
From: ihsan at opencsw.org (=?utf-8?B?xLBoc2FuIERvxJ9hbg==?=)
Date: Wed, 29 Dec 2021 21:07:58 +0100
Subject: Remove old library
Message-ID: <3B5C7476-7047-4537-B6A2-F1D1652090C8@opencsw.org>

Hello,

I?ve updated today unbound to the most recent version and this version comes also with a new version of libunbound. The new version in the catalog is now libunbound8, but libunbound2 also in the catalog.

How do I get rid of the old version? I guess the easiest is to set a conflict to libunbound2, right?




Regards

Ihsan

From maciej at opencsw.org  Wed Dec 29 21:13:28 2021
From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=)
Date: Wed, 29 Dec 2021 20:13:28 +0000
Subject: Remove old library
In-Reply-To: <3B5C7476-7047-4537-B6A2-F1D1652090C8@opencsw.org>
References: <3B5C7476-7047-4537-B6A2-F1D1652090C8@opencsw.org>
Message-ID: <CALtRa-4QT8S+TUEGD5iW82haFK6kso+QHBYUdHcPOVqyJWh+Yg@mail.gmail.com>

Setting a conflict sounds like a harsh way to do it. Maybe a softer
approach would suffice? We had a way of obsoleting packages, didn't we?

http://wiki.opencsw.org/obsoleting-packages
https://www.opencsw.org/2012/05/pkgutil-cleanup/

?Maciej

?hsan Do?an via maintainers <maintainers at lists.opencsw.org> escreveu no dia
quarta, 29/12/2021 ?(s) 20:08:

> Hello,
>
> I?ve updated today unbound to the most recent version and this version
> comes also with a new version of libunbound. The new version in the catalog
> is now libunbound8, but libunbound2 also in the catalog.
>
> How do I get rid of the old version? I guess the easiest is to set a
> conflict to libunbound2, right?
>
>
>
>
> Regards
>
> Ihsan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20211229/6adae7bf/attachment.html>

From dam at opencsw.org  Wed Dec 29 22:01:51 2021
From: dam at opencsw.org (Dagobert Michelsen)
Date: Wed, 29 Dec 2021 22:01:51 +0100
Subject: Remove old library
In-Reply-To: <CALtRa-4QT8S+TUEGD5iW82haFK6kso+QHBYUdHcPOVqyJWh+Yg@mail.gmail.com>
References: <3B5C7476-7047-4537-B6A2-F1D1652090C8@opencsw.org>
 <CALtRa-4QT8S+TUEGD5iW82haFK6kso+QHBYUdHcPOVqyJWh+Yg@mail.gmail.com>
Message-ID: <F3E1BAAA-500D-499F-BBB6-47EF7B0E0FFF@opencsw.org>

Hi,

Am 29.12.2021 um 21:13 schrieb Maciej (Matchek) Blizi?ski via maintainers <maintainers at lists.opencsw.org>:
> Setting a conflict sounds like a harsh way to do it. Maybe a softer approach would suffice? We had a way of obsoleting packages, didn't we?
> 
> http://wiki.opencsw.org/obsoleting-packages
> https://www.opencsw.org/2012/05/pkgutil-cleanup/
> 
> ?Maciej
> 
> ?hsan Do?an via maintainers <maintainers at lists.opencsw.org> escreveu no dia quarta, 29/12/2021 ?(s) 20:08:
> Hello,
> 
> I?ve updated today unbound to the most recent version and this version comes also with a new version of libunbound. The new version in the catalog is now libunbound8, but libunbound2 also in the catalog.
> 
> How do I get rid of the old version? I guess the easiest is to set a conflict to libunbound2, right?

The normal solution is just to declare a dependency on the new libunbound8
and if users already have libunbound2 it just stays on the machine. We don?t
have information why that package installed in the first place (in general)
and cannot be sure if it is safe to remove - maybe the user has other
(e.g. self-compiled) stuff linked against it.


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