Re: [oi-dev] Firefox 52 preliminary testing

[Alexander Pyhalov]

On 12.05.2017 09:43, Alexander Pyhalov wrote:

Hello.

It seems I've reached the state when FF doesn't crash now and then.
Some testing is required.

I've prepared two packages, debug and non-debug.

Debug package:
pkg://userland/web/browser/firefox@52.1.1,5.11-2017.0.0.0:20170511T214409Z
( size ~ 2 GB )
Release package:
pkg://userland/web/browser/firefox@52.1.1,5.11-2017.0.0.0:20170512T061040Z
( size ~ 283 MB)
Both packages are available from 
http://buildzone.oi-build.r61.net:1000/


Don't forget to backup your ~/.mozilla directories before updating.

So far it seems there's issue with high CPU usage (two FF processes
eat ~ 100% cpu for just communicating to each other).
a) Need to confirm this on other installations.
b) Need help in debugging the issue :)


For those who wants to build it himself, component is here:
https://github.com/pyhalov/oi-userland/tree/firefox-52


---
System Administrator of Southern Federal University Computer Center


___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] Firefox 52 preliminary testing

[Alexander Pyhalov]

Hello.

It seems I've reached the state when FF doesn't crash now and then.
Some testing is required.

I've prepared two packages, debug and non-debug.

Debug package:  
pkg://userland/web/browser/firefox@52.1.1,5.11-2017.0.0.0:20170511T214409Z 
( size ~ 2 GB )
Release package: 
pkg://userland/web/browser/firefox@52.1.1,5.11-2017.0.0.0:20170512T061040Z 
( size ~ 283 MB)

Both packages are available from http://buildzone.oi-build.r61.net:1000/

Don't forget to backup your ~/.mozilla directories before updating.

So far it seems there's issue with high CPU usage (two FF processes eat 
~ 100% cpu for just communicating to each other).

a) Need to confirm this on other installations.
b) Need help in debugging the issue :)
--
System Administrator of Southern Federal University Computer Center

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] exiv2 broken?

[Carsten Grzemba]

On 11.05.17 21:20, Andreas Wacknitz   wrote: 
> 
> 
>   
> 
> 
> 
>  
> Sorry, I haven't been able to help here. I am quite busy with private things 
> at the moment.
>  
> Regards,
>  Andreas
>  
>  
> Am 11.05.17 um 13:42 schrieb Carsten Grzemba:
>  
>  
> > 
> >  
> >  On 10.05.17 07:21, Carsten Grzemba  
> > (javascript:main.compose() wrote:  
> > >  
> > > 
> > >  
> > >  On 09.05.17 23:16, Adam Števko  
> > > (javascript:main.compose() wrote:  
> > > >  
> > > > Hey,
> > > >  
> > > >  yes and possibly submit a fix, please.
> > > >  
> > > >  Thanks,
> > > >  Adam
> > > >  
> > > >  > On May 9, 2017, at 7:56 PM, Andreas Wacknitz 
> > > > (javascript:main.compose() wrote:
> > > >  > 
> > > >  > Ok, after reading the sources a little bit more I found out that the 
> > > > missing include file should be generated.
> > > >  > So it's a problem in our build. Shall I create a ticket?
> > > >  > 
> > > >  > Andreas
> > > >  > 
> > > >  > 
> > > >  > Am 09.05.17 um 19:15 schrieb Andreas Wacknitz:
> > > >  >> Hi,
> > > >  >> 
> > > >  >> when I try to build geeqie or gthumb packages with exiv2 installed 
> > > > I get compiler errors like this:
> > > >  >> 
> > > >  >> In file included from /usr/include/exiv2/types.hpp:35:0,
> > > >  >> from /usr/include/exiv2/image.hpp:39,
> > > >  >> from 
> > > > /oibuild/oi-userland/components/image/geeqie/geeqie-1.3/src/exiv2.cc:25:
> > > >  >> /usr/include/exiv2/config.h:10:23: fatal error: exv_conf.h: No such 
> > > > file or directory
> > > >  >> # include "exv_conf.h"
> > > >  >> ^
> > > >  >> compilation terminated.
> > > >  >> 
> > > >  >> It seems as if the exiv2 package is missing this important 
> > > > configuration file. As far as I can tell this not
> > > >  >> only a problem with our exiv2 package but also with the original 
> > > > sources as well. For me it looks as if
> > > >  >> this library has only been used and tested with Visual Studio. What 
> > > > do you think?
> > > >  >> 
> > > >  >> Regards
> > > >  >> Andreas
> > > >  
> > >  
> > >  I didn't include this header file because it is a result of configure 
> > > step, so I thought it will also regenerated if you use the lib for other 
> > > OSS projects. 
> > >  I hope I will have the time to look at this week.
> > >  
> > >  A ticket with your steps on gegl are wellcome.
> > >  
> > >  Carsten 
> > >  
> >  I created a PR which includes exv_conf.h in package 
> 
> 
>  
> 
It should be fixed, please try build of geeqie again.

Carsten
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Can I still install older perl and python?

[Alexander Pyhalov]

Hi.

On 12.05.2017 02:14, Gordon Ross wrote:

I've been trying out the latest OI build, and most things look great!
(Thanks to everyone who helped.)

However, I have some 3rd party stuff that wants older versions of perl
(5.10.0, 5.16) and python (2.6) and I can't figure out how to get pkg
to let me install those along side the current ones (perl 5.22, python
2.7).
Some time ago, it was possible to install multiple versions of perl
and/or python.
Is that still possible?


It's still possible to have python 2.7 and 3.4 or perl 5.22 and 5.24 
coinstalled,
but older versions were marked 'Obsolete', which means IPS will refuse 
to install
them and will attempt to remove as long as there's no installed 
dependent packages.
I suppose, you understand, why we don't want to have software, which is 
not longer

supported by projects itself in our repository.

From other packages which I'd like to mark Obsolete I see all 
MySQL(percona, mariadb) versions

before 5.7 and PostgreSQL 9.3 (perhaps, 9.4)...
---
System Administrator of Southern Federal University Computer Center


___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Discussing maintainers visibility in oi-userland

[Alexander Pyhalov]

On 11.05.2017 22:13, Peter Tribble wrote:

On Thu, May 11, 2017 at 6:56 PM, Aurélien Larcher <
aurelien.larc...@gmail.com> wrote:



The question raised is whether we should formalize a maintaining 
process

for some important components or groups of components.

At some point I joked about a campaign going like "Adopt a package".



There are downsides to having a formal owner: they can become a
bottleneck, and it might discourage others to contribute in an area
where there's an individual (or individuals) listed. Also, people may 
be

reluctant to contribute if there's a prospect of being lumbered with
the responsibility going forward.

But, if you can avoid that, then there are benefits to having what we
would call "Subject Matter Experts" for components or groups. Having
someone who is reasonably familiar with the component, preferably
someone who uses it, is useful as a source of help and advice, and
having a list of such people and their specialities would be useful to
other contributors.

Putting such a list on display would also show that OI wasn't just a
one or two person effort, which would be good.


Yes, this idea seems reasonable. BTW, recently github started suggesting 
reviewers

and it does it rather well.
---
System Administrator of Southern Federal University Computer Center


___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Discussing maintainers visibility in oi-userland

[Aurélien Larcher]

À Jeudi 11 mai 2017, Adam Števko a écrit :
> Hello,
> 
> I would like to keep the status quo in this. We don’t have formal maintainers 
> and basically every change to the package/component is reviewed by relevant 
> person (me/alp/aurelien//jimklimov/wacki/agnar). I would really like to see 
> this list to grow and reach the phase that we need to start think about 
> maintainers, but we are not yet there. The situation right now is that even 
> if a person reviews the change and think that other person should have a 
> look, e.g. me when I am reviewing some libs that might affect GUI i ask alp 
> for crossreview or when alp touches X11 things, he ask aurelien etc.
> 
> I would avoid creating a dedicated maintainers for now. If people really 
> think it should be done, I would say it should be done on a technology 
> stacks, e.g. Python, Ruby, webservers, X11, databases etc. In such cases 
> every change would need to be approved by a relevant person. However, I think 
> that might introduce latency and bureaucracy, which is really non-existent 
> right now. I would like to keep it that way if possible.

Maybe maintainer was a bad word, probably, as Peter suggested, it is more about 
having reference persons per group, so that questions could be directed. I do 
not know.
I am happy about the current system.
The question occured because I wondered whether people exterior to our group 
may find the apparent lack of formal organization confusing.
If it is the case, is there anything to do about it?

Darek's question shows that something could be mentioned about lack of 
ownership of components and review of PRs.
Just to formalize the informal nature of the process. ;) 

> 
> Cheers,
> Adam
> 
> > On May 11, 2017, at 9:13 PM, Peter Tribble  wrote:
> > 
> > On Thu, May 11, 2017 at 6:56 PM, Aurélien Larcher 
> > mailto:aurelien.larc...@gmail.com>> wrote:
> > 
> > The question raised is whether we should formalize a maintaining process 
> > for some important components or groups of components.
> > 
> > At some point I joked about a campaign going like "Adopt a package".
> > 
> > There are downsides to having a formal owner: they can become a
> > bottleneck, and it might discourage others to contribute in an area
> > where there's an individual (or individuals) listed. Also, people may be
> > reluctant to contribute if there's a prospect of being lumbered with
> > the responsibility going forward.
> > 
> > But, if you can avoid that, then there are benefits to having what we
> > would call "Subject Matter Experts" for components or groups. Having
> > someone who is reasonably familiar with the component, preferably
> > someone who uses it, is useful as a source of help and advice, and
> > having a list of such people and their specialities would be useful to
> > other contributors.
> > 
> > Putting such a list on display would also show that OI wasn't just a
> > one or two person effort, which would be good.
> > 
> > --
> > -Peter Tribble
> > http://www.petertribble.co.uk/  - 
> > http://ptribble.blogspot.com/ 
> > ___
> > oi-dev mailing list
> > oi-dev@openindiana.org
> > https://openindiana.org/mailman/listinfo/oi-dev
> 
>

-- 
Thanks for sailing Jolla :)
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] Can I still install older perl and python?

[Gordon Ross]

I've been trying out the latest OI build, and most things look great!
(Thanks to everyone who helped.)

However, I have some 3rd party stuff that wants older versions of perl
(5.10.0, 5.16) and python (2.6) and I can't figure out how to get pkg
to let me install those along side the current ones (perl 5.22, python
2.7).
Some time ago, it was possible to install multiple versions of perl
and/or python.
Is that still possible?

Thanks,
Gordon

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Discussing maintainers visibility in oi-userland

[Adam Števko]

Hello,

I would like to keep the status quo in this. We don’t have formal maintainers 
and basically every change to the package/component is reviewed by relevant 
person (me/alp/aurelien//jimklimov/wacki/agnar). I would really like to see 
this list to grow and reach the phase that we need to start think about 
maintainers, but we are not yet there. The situation right now is that even if 
a person reviews the change and think that other person should have a look, 
e.g. me when I am reviewing some libs that might affect GUI i ask alp for 
crossreview or when alp touches X11 things, he ask aurelien etc.

I would avoid creating a dedicated maintainers for now. If people really think 
it should be done, I would say it should be done on a technology stacks, e.g. 
Python, Ruby, webservers, X11, databases etc. In such cases every change would 
need to be approved by a relevant person. However, I think that might introduce 
latency and bureaucracy, which is really non-existent right now. I would like 
to keep it that way if possible.

Cheers,
Adam

> On May 11, 2017, at 9:13 PM, Peter Tribble  wrote:
> 
> On Thu, May 11, 2017 at 6:56 PM, Aurélien Larcher  > wrote:
> 
> The question raised is whether we should formalize a maintaining process for 
> some important components or groups of components.
> 
> At some point I joked about a campaign going like "Adopt a package".
> 
> There are downsides to having a formal owner: they can become a
> bottleneck, and it might discourage others to contribute in an area
> where there's an individual (or individuals) listed. Also, people may be
> reluctant to contribute if there's a prospect of being lumbered with
> the responsibility going forward.
> 
> But, if you can avoid that, then there are benefits to having what we
> would call "Subject Matter Experts" for components or groups. Having
> someone who is reasonably familiar with the component, preferably
> someone who uses it, is useful as a source of help and advice, and
> having a list of such people and their specialities would be useful to
> other contributors.
> 
> Putting such a list on display would also show that OI wasn't just a
> one or two person effort, which would be good.
> 
> --
> -Peter Tribble
> http://www.petertribble.co.uk/  - 
> http://ptribble.blogspot.com/ 
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



signature.asc
Description: Message signed with OpenPGP
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] exiv2 broken?

[Andreas Wacknitz]

Sorry, I haven't been able to help here. I am quite busy with private 
things at the moment.


Regards,
Andreas

Am 11.05.17 um 13:42 schrieb Carsten Grzemba:



On 10.05.17 07:21, *Carsten Grzemba *  wrote:



On 09.05.17 23:16, *Adam Števko *  wrote:

Hey,

yes and possibly submit a fix, please.

Thanks,
Adam

> On May 9, 2017, at 7:56 PM, Andreas Wacknitz  
wrote:

>
> Ok, after reading the sources a little bit more I found out that 
the missing include file should be generated.

> So it's a problem in our build. Shall I create a ticket?
>
> Andreas
>
>
> Am 09.05.17 um 19:15 schrieb Andreas Wacknitz:
>> Hi,
>>
>> when I try to build geeqie or gthumb packages with exiv2 
installed I get compiler errors like this:

>>
>> In file included from /usr/include/exiv2/types.hpp:35:0,
>> from /usr/include/exiv2/image.hpp:39,
>> from 
/oibuild/oi-userland/components/image/geeqie/geeqie-1.3/src/exiv2.cc:25:
>> /usr/include/exiv2/config.h:10:23: fatal error: exv_conf.h: No 
such file or directory

>> # include "exv_conf.h"
>>   ^
>> compilation terminated.
>>
>> It seems as if the exiv2 package is missing this important 
configuration file. As far as I can tell this not
>> only a problem with our exiv2 package but also with the original 
sources as well. For me it looks as if
>> this library has only been used and tested with Visual Studio. 
What do you think?

>>
>> Regards
>> Andreas


I didn't include this header file because it is a result of configure 
step, so I thought it will also regenerated if you use the lib for 
other OSS projects.

I hope I will have the time to look at this week.

A ticket with your steps on gegl are wellcome.

Carsten

I created a PR which includes exv_conf.h in package


___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev


___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Discussing maintainers visibility in oi-userland

[Peter Tribble]

On Thu, May 11, 2017 at 6:56 PM, Aurélien Larcher <
aurelien.larc...@gmail.com> wrote:

>
> The question raised is whether we should formalize a maintaining process
> for some important components or groups of components.
>
> At some point I joked about a campaign going like "Adopt a package".
>

There are downsides to having a formal owner: they can become a
bottleneck, and it might discourage others to contribute in an area
where there's an individual (or individuals) listed. Also, people may be
reluctant to contribute if there's a prospect of being lumbered with
the responsibility going forward.

But, if you can avoid that, then there are benefits to having what we
would call "Subject Matter Experts" for components or groups. Having
someone who is reasonably familiar with the component, preferably
someone who uses it, is useful as a source of help and advice, and
having a list of such people and their specialities would be useful to
other contributors.

Putting such a list on display would also show that OI wasn't just a
one or two person effort, which would be good.

-- 
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] Discussing maintainers visibility in oi-userland

[Aurélien Larcher]

Hi,
following an offlist discussion with Darek, he asked:

Is there any list of components, which have maintainers?
> This case shows that some components need maintainers. I guess some people
> decide whether a component needs a maintainer or not.
>

I explained that there are no officially defined maintainers since
oi-userland is quite recent and the original build systems were diverse.

I noted that:

There are "official" maintainers for a few major components, and they are
listed on the Wiki somehow.

[...]

So far:
- cluster/*
- database/*
- desktop/mate/*
- desktop/e/*
- gfx-drm
- git
- librecad
- multimedia/*
- nodejs*
- sysutils/*
- x11/*

have identified regular contributors on x86 and two persons work on SPARC
builds.
The question raised is whether we should formalize a maintaining process
for some important components or groups of components.
At some point I joked about a campaign going like "Adopt a package".

What is your thought on that?

Aurélien

-- 
---
Praise the Caffeine embeddings
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Components archive url availability

[Dariusz Sendkowski]

Ok guys, thanks for the clarification.


2017-05-11 19:15 GMT+02:00 Till Wegmüller :

> Hello.
>
> Yes IPS uses precompiled Packages. However it does not distribute them as
> tarball archives but as seperate files. These fiels are Linked together by
> the manifests of a Package. Which is a Textfile describing all files,
> symlinks, mediators, etc. of a package.
>
> IPS itself does not use the source archive property. This is only relevant
> for OI-userland.
>
> OI userland is our version of Ports and also our Buidl system for packages.
>
> You can grab yourself the latest git revision of oi-userland and compile
> every package for yourself localy with it. Once you have installed
> build-essential package.
>
> Our Jenkins build servers do the same.
>
> Have a look at http://docs.openindiana.org/dev/userland/ for more details
> on how to get started with oi-userland
>
>
> Greetings
> Till
>
> On 11.05.2017 13:28, Aurélien Larcher wrote:
>
>>
>>
>> On Thu, May 11, 2017 at 12:18 PM, Dariusz Sendkowski <
>> dsendkow...@gmail.com > wrote:
>>
>> I guess that is exactly how it is done in OpenBSD. You have
>> precompiled binaries, which you can fetch and install. You can also
>> build them by yourself using OpenBSD ports system. If the original
>> site is unavailable, the sources are downloaded directly from
>> OpenBSD servers, for example:
>>
>> # cd /usr/ports/x11/libxdg-basedir/
>> # make fetch
>> ===>  Checking files for libxdg-basedir-1.2.0p0
>> >> Fetch http://nevill.ch/libxdg-basedir/downloads/libxdg-basedir-1.
>> 2.0.tar.gz > 2.0.tar.gz>
>> ftp: connect: Connection refused
>> >> Fetch https://ftp.openbsd.org/pub/OpenBSD/distfiles//libxdg-basedi
>> r-1.2.0.tar.gz
>> > ir-1.2.0.tar.gz>
>> libxdg-basedir-1.2.0.t... 100%
>>
>> Well, of course one can always clone oi-userland and build the
>> packages by oneself.
>>
>> Anyway, I just wanted to know how exactly it is done in OI.
>>
>> Btw, I wanted to add libxdg-basedir to oi-userland but as you can
>> see, the original site is not available any more.
>>
>>
>> There is a mirror with archived tarballs at:
>>
>> http://dlc.openindiana.org/oi-userland/source-archives/
>>
>> which can be used automatically if you set the EXTERNAL_ARCHIVE_MIRROR
>> variable.
>>
>> I do not know what you mean exactly by "precompiled package".
>> IPS is not based on "tarballs" and you can create pkg(5) archives for a
>> given package version just by pkgrecv from the publisher, this seems a bit
>> redundant.
>>
>> HTH
>>
>>
>> regards,
>> Darek
>>
>>
>>
>> 2017-05-11 11:49 GMT+02:00 Nikola M > >:
>>
>>
>> On 05/11/17 10:53 AM, Dariusz Sendkowski wrote:
>> > Hi,
>> >
>> > What happens when a component archive url points to a web
>> resource
>> > that is unavailable temporarily or, even worse, permanently?
>> How does
>> > it impact the package availability?
>> >
>> > Are all these oi-userland components precompiled and stored
>> somewhere
>> > on the publisher server along with the sources? So when users
>> install
>> > some packages they fetch the precompiled packages regardless of
>> the
>> > corresponding archive urls availability?
>>
>> I asked that 3+ years ago and i think they are stored on Oi build
>> servers, but not accessible from outside.
>>
>> It would be the best to always have all sources available at any
>> time,
>> so all source is fetched from OI servers, but it could be a
>> project for
>> itself to make upstream sources available locally on OI servers.
>>
>> Maintainers didn't like this, because fetching source archives
>> from
>> remote server is more simple for a building process.
>>
>> I also used to point out the legality of even distributing
>> precompiled
>> binaries before, without providing sources at any time. (and for
>> any
>> distributed binary).
>> Having local store of source archives from the upstream projects,
>> having all sources always available at OI site, would fix both
>> legal and
>> build problems and elevate problem if network source is not
>> available.
>> Maybe just make local source code archives on Oi servers,
>> visible to all
>> users?
>>
>>
>>
>>
>> ___
>> oi-dev mailing list
>> oi-dev@openindiana.org 
>> https://openindiana.org/mailman/listinfo/oi-dev
>> 
>>
>>
>>
>>
>> --
>> ---
>> Praise the Caffeine embeddings
>>
>>
>> ___
>> oi-dev ma

Re: [oi-dev] Components archive url availability

[Till Wegmüller]

Hello.

Yes IPS uses precompiled Packages. However it does not distribute them 
as tarball archives but as seperate files. These fiels are Linked 
together by the manifests of a Package. Which is a Textfile describing 
all files, symlinks, mediators, etc. of a package.


IPS itself does not use the source archive property. This is only 
relevant for OI-userland.


OI userland is our version of Ports and also our Buidl system for packages.

You can grab yourself the latest git revision of oi-userland and compile 
every package for yourself localy with it. Once you have installed 
build-essential package.


Our Jenkins build servers do the same.

Have a look at http://docs.openindiana.org/dev/userland/ for more 
details on how to get started with oi-userland



Greetings
Till

On 11.05.2017 13:28, Aurélien Larcher wrote:



On Thu, May 11, 2017 at 12:18 PM, Dariusz Sendkowski 
mailto:dsendkow...@gmail.com>> wrote:


I guess that is exactly how it is done in OpenBSD. You have
precompiled binaries, which you can fetch and install. You can also
build them by yourself using OpenBSD ports system. If the original
site is unavailable, the sources are downloaded directly from
OpenBSD servers, for example:

# cd /usr/ports/x11/libxdg-basedir/
# make fetch
===>  Checking files for libxdg-basedir-1.2.0p0
>> Fetch http://nevill.ch/libxdg-basedir/downloads/libxdg-basedir-1.2.0.tar.gz 

ftp: connect: Connection refused
>> Fetch 
https://ftp.openbsd.org/pub/OpenBSD/distfiles//libxdg-basedir-1.2.0.tar.gz

libxdg-basedir-1.2.0.t... 100%

Well, of course one can always clone oi-userland and build the
packages by oneself.

Anyway, I just wanted to know how exactly it is done in OI.

Btw, I wanted to add libxdg-basedir to oi-userland but as you can
see, the original site is not available any more.


There is a mirror with archived tarballs at:

http://dlc.openindiana.org/oi-userland/source-archives/

which can be used automatically if you set the EXTERNAL_ARCHIVE_MIRROR 
variable.


I do not know what you mean exactly by "precompiled package".
IPS is not based on "tarballs" and you can create pkg(5) archives for a 
given package version just by pkgrecv from the publisher, this seems a 
bit redundant.


HTH


regards,
Darek



2017-05-11 11:49 GMT+02:00 Nikola M mailto:minik...@gmail.com>>:

On 05/11/17 10:53 AM, Dariusz Sendkowski wrote:
> Hi,
>
> What happens when a component archive url points to a web resource
> that is unavailable temporarily or, even worse, permanently? How does
> it impact the package availability?
>
> Are all these oi-userland components precompiled and stored somewhere
> on the publisher server along with the sources? So when users install
> some packages they fetch the precompiled packages regardless of the
> corresponding archive urls availability?

I asked that 3+ years ago and i think they are stored on Oi build
servers, but not accessible from outside.

It would be the best to always have all sources available at any
time,
so all source is fetched from OI servers, but it could be a
project for
itself to make upstream sources available locally on OI servers.

Maintainers didn't like this, because fetching source archives from
remote server is more simple for a building process.

I also used to point out the legality of even distributing
precompiled
binaries before, without providing sources at any time. (and for any
distributed binary).
Having local store of source archives from the upstream projects,
having all sources always available at OI site, would fix both
legal and
build problems and elevate problem if network source is not
available.
Maybe just make local source code archives on Oi servers,
visible to all
users?




___
oi-dev mailing list
oi-dev@openindiana.org 
https://openindiana.org/mailman/listinfo/oi-dev





--
---
Praise the Caffeine embeddings


___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev



___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Volunteer needed to take over the Twitter feed

[Aurélien Larcher]

On Wed, May 10, 2017 at 5:05 PM, Cezary Podbilski via oi-dev <
oi-dev@openindiana.org> wrote:

> Aurélien,
>
>
> Awesome, sounds good! Please brief away
>

Very good! Let us handle the details off-list.
Kind regards

Aurelien


>
>
> Regards
>
>
> Cezary
>
>
> À Mercredi 10 mai 2017, Cezary Podbilski via oi-dev a écrit :
> > Hi Guys,
> > This seems like a good place to start! I am happy to volunteer for the
> Twitter management!
>
> Nice!
> I use Tweetdeck, an extension provided by Twitter that allows delegating
> the ability to tweet from other accounts.
> I could brief you about my current practices.
> Alexander and Adam, what do you think?
>
> Kind regards
>
> Aurélien
>
> > Thanks
> > Cezary
> > Message: 1
> > Date: Tue, 9 May 2017 16:07:03 +0200
> > From: Dariusz Sendkowski 
> > To: OpenIndiana Developer mailing list 
> > Subject: Re: [oi-dev] Volunteer needed to take over the Twitter feed
> > Message-ID:
> >  mail.gmail.com>
> > Content-Type: text/plain; charset="utf-8"
> >
> > I thought the twitter feeds were done automatically, at least when a PR
> was
> > merged.
> > If this is not the case, maybe it could be better to make it auto?
> >
> > regards,
> > Darek
> >
> > 2017-05-08 19:32 GMT+02:00 Aur?lien Larcher  gmail.com>:
> >
> > > Hi,
> > > I have managed the Twitter feed:
> > >
> > > https://twitter.com/OpenIndiana
> > >
> > > in the past months but I will not have time to do so anymore.
> > >
> > > We need a volunteer to handle this task, at least for a few
> weeks/months.
> > > This news feed is important to update people on the activity of the
> > > project and advertise security updates.
> > > Kind regards
> > >
> > > Aur?lien
> > >
> > > --
> > > ---
> > > Praise the Caffeine embeddings
> > >
> > > ___
> > > oi-dev mailing list
> > > oi-dev at openindiana.org
> > > https://openindiana.org/mailman/listinfo/oi-dev
> > >
> > -- next part --
> > An HTML attachment was scrubbed...
> > URL:  20170509/d655b9bf/attachment-0001.html>
> >
> > --
> >
> > Message: 2
> > Date: Tue, 9 May 2017 16:13:36 +0200
> > From: Aur?lien Larcher 
> > To: OpenIndiana Developer mailing list 
> > Subject: Re: [oi-dev] Volunteer needed to take over the Twitter feed
> > Message-ID:
> >  mail.gmail.com>
> > Content-Type: text/plain; charset="utf-8"
> >
> > On Tue, May 9, 2017 at 4:07 PM, Dariusz Sendkowski  gmail.com>
> > wrote:
> >
> > > I thought the twitter feeds were done automatically, at least when a PR
> > > was merged.
> > > If this is not the case, maybe it could be better to make it auto?
> > >
> >
> > Not every PR deserves a tweet so we should decide about specific keywords
> > in the PR title to trigger publication.
> > We talked about such automation but it is not something we had time to
> > investigate.
> > If someone wants to think about it and implement it this is even better.
> >
> > Kind regards
> >
> > Aur?lien
> >
> >
> > >
> > > regards,
> > > Darek
> > >
> > > 2017-05-08 19:32 GMT+02:00 Aur?lien Larcher  gmail.com>:
> > >
> > >> Hi,
> > >> I have managed the Twitter feed:
> > >>
> > >> https://twitter.com/OpenIndiana
> > >>
> > >> in the past months but I will not have time to do so anymore.
> > >>
> > >> We need a volunteer to handle this task, at least for a few
> weeks/months.
> > >> This news feed is important to update people on the activity of the
> > >> project and advertise security updates.
> > >> Kind regards
> > >>
> > >> Aur?lien
> > >>
> > >> --
> > >> ---
> > >> Praise the Caffeine embeddings
> > >>
> > >>
> > Message: 6
> > Date: Tue, 9 May 2017 23:20:40 +0200
> > From: Adam ?tevko 
> > To: OpenIndiana Developer mailing list 
> > Subject: Re: [oi-dev] Volunteer needed to take over the Twitter feed
> > Message-ID: <6D965F3F-3A67-4E93-8B3B-EE6BD5AC5442 at gmail.com>
> > Content-Type: text/plain; charset="utf-8"
> >
> > Hey Darek,
> >
> > unfortunately, we can?t automate it. Right now, only valuable PRs are
> tweeted and doing that automatically would be spamming people. Social media
> requirement a dedicated person unfortunately. With Twitter we saw a nice
> boost in the project marketing and spreading news.
> >
> > Cheers,
> > Adam
> >
> > > On May 9, 2017, at 4:07 PM, Dariusz Sendkowski  gmail.com> wrote:
> > >
> > > I thought the twitter feeds were done automatically, at least when a
> PR was merged.
> > > If this is not the case, maybe it could be better to make it auto?
> > >
> > > regards,
> > > Darek
> > >
> > > 2017-05-08 19:32 GMT+02:00 Aur?lien Larcher  gmail.com >:
> > > Hi,
> > > I have managed the Twitter feed:
> > >
> > > https://twitter.com/OpenIndiana 
> > >
> > > in the past months but I will not have time to do so anymore.
> > >
> > > We need a volunteer to handle this task, at least for a few
> weeks/months.
> > > This news feed is importan

Re: [oi-dev] exiv2 broken?

[Carsten Grzemba]

On 10.05.17 07:21, Carsten Grzemba   wrote: 
> 
> 
> 
> On 09.05.17 23:16, Adam Števko   wrote: 
> > 
> > Hey,
> > 
> > yes and possibly submit a fix, please.
> > 
> > Thanks,
> > Adam
> > 
> > > On May 9, 2017, at 7:56 PM, Andreas Wacknitz  wrote:
> > > 
> > > Ok, after reading the sources a little bit more I found out that the 
> > > missing include file should be generated.
> > > So it's a problem in our build. Shall I create a ticket?
> > > 
> > > Andreas
> > > 
> > > 
> > > Am 09.05.17 um 19:15 schrieb Andreas Wacknitz:
> > >> Hi,
> > >> 
> > >> when I try to build geeqie or gthumb packages with exiv2 installed I get 
> > >> compiler errors like this:
> > >> 
> > >> In file included from /usr/include/exiv2/types.hpp:35:0,
> > >> from /usr/include/exiv2/image.hpp:39,
> > >> from 
> > >> /oibuild/oi-userland/components/image/geeqie/geeqie-1.3/src/exiv2.cc:25:
> > >> /usr/include/exiv2/config.h:10:23: fatal error: exv_conf.h: No such file 
> > >> or directory
> > >> # include "exv_conf.h"
> > >> ^
> > >> compilation terminated.
> > >> 
> > >> It seems as if the exiv2 package is missing this important configuration 
> > >> file. As far as I can tell this not
> > >> only a problem with our exiv2 package but also with the original sources 
> > >> as well. For me it looks as if
> > >> this library has only been used and tested with Visual Studio. What do 
> > >> you think?
> > >> 
> > >> Regards
> > >> Andreas
> > 
> 
> I didn't include this header file because it is a result of configure step, 
> so I thought it will also regenerated if you use the lib for other OSS 
> projects. 
> I hope I will have the time to look at this week.
> 
> A ticket with your steps on gegl are wellcome.
> 
> Carsten 
> 
I created a PR which includes exv_conf.h in package
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Components archive url availability

[Aurélien Larcher]

On Thu, May 11, 2017 at 12:18 PM, Dariusz Sendkowski 
wrote:

> I guess that is exactly how it is done in OpenBSD. You have precompiled
> binaries, which you can fetch and install. You can also build them by
> yourself using OpenBSD ports system. If the original site is unavailable,
> the sources are downloaded directly from OpenBSD servers, for example:
>
> # cd /usr/ports/x11/libxdg-basedir/
>
> # make fetch
> ===>  Checking files for libxdg-basedir-1.2.0p0
> >> Fetch http://nevill.ch/libxdg-basedir/downloads/libxdg-
> basedir-1.2.0.tar.gz
> ftp: connect: Connection refused
> >> Fetch https://ftp.openbsd.org/pub/OpenBSD/distfiles//libxdg-
> basedir-1.2.0.tar.gz
> libxdg-basedir-1.2.0.t... 100%
>
> Well, of course one can always clone oi-userland and build the packages by
> oneself.
>
> Anyway, I just wanted to know how exactly it is done in OI.
>
> Btw, I wanted to add libxdg-basedir to oi-userland but as you can see,
> the original site is not available any more.
>

There is a mirror with archived tarballs at:

http://dlc.openindiana.org/oi-userland/source-archives/

which can be used automatically if you set the EXTERNAL_ARCHIVE_MIRROR
variable.

I do not know what you mean exactly by "precompiled package".
IPS is not based on "tarballs" and you can create pkg(5) archives for a
given package version just by pkgrecv from the publisher, this seems a bit
redundant.

HTH


>
> regards,
> Darek
>
>
>
> 2017-05-11 11:49 GMT+02:00 Nikola M :
>
>> On 05/11/17 10:53 AM, Dariusz Sendkowski wrote:
>> > Hi,
>> >
>> > What happens when a component archive url points to a web resource
>> > that is unavailable temporarily or, even worse, permanently? How does
>> > it impact the package availability?
>> >
>> > Are all these oi-userland components precompiled and stored somewhere
>> > on the publisher server along with the sources? So when users install
>> > some packages they fetch the precompiled packages regardless of the
>> > corresponding archive urls availability?
>>
>> I asked that 3+ years ago and i think they are stored on Oi build
>> servers, but not accessible from outside.
>>
>> It would be the best to always have all sources available at any time,
>> so all source is fetched from OI servers, but it could be a project for
>> itself to make upstream sources available locally on OI servers.
>>
>> Maintainers didn't like this, because fetching source archives from
>> remote server is more simple for a building process.
>>
>> I also used to point out the legality of even distributing precompiled
>> binaries before, without providing sources at any time. (and for any
>> distributed binary).
>> Having local store of source archives from the upstream projects,
>> having all sources always available at OI site, would fix both legal and
>> build problems and elevate problem if network source is not available.
>> Maybe just make local source code archives on Oi servers, visible to all
>> users?
>>
>
>>
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



-- 
---
Praise the Caffeine embeddings
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Components archive url availability

[Dariusz Sendkowski]

I guess that is exactly how it is done in OpenBSD. You have precompiled
binaries, which you can fetch and install. You can also build them by
yourself using OpenBSD ports system. If the original site is unavailable,
the sources are downloaded directly from OpenBSD servers, for example:

# cd
/usr/ports/x11/libxdg-basedir/

# make fetch
===>  Checking files for libxdg-basedir-1.2.0p0
>> Fetch
http://nevill.ch/libxdg-basedir/downloads/libxdg-basedir-1.2.0.tar.gz
ftp: connect: Connection refused
>> Fetch
https://ftp.openbsd.org/pub/OpenBSD/distfiles//libxdg-basedir-1.2.0.tar.gz
libxdg-basedir-1.2.0.t... 100%

Well, of course one can always clone oi-userland and build the packages by
oneself.

Anyway, I just wanted to know how exactly it is done in OI.

Btw, I wanted to add libxdg-basedir to oi-userland but as you can see, the
original site is not available any more.

regards,
Darek



2017-05-11 11:49 GMT+02:00 Nikola M :

> On 05/11/17 10:53 AM, Dariusz Sendkowski wrote:
> > Hi,
> >
> > What happens when a component archive url points to a web resource
> > that is unavailable temporarily or, even worse, permanently? How does
> > it impact the package availability?
> >
> > Are all these oi-userland components precompiled and stored somewhere
> > on the publisher server along with the sources? So when users install
> > some packages they fetch the precompiled packages regardless of the
> > corresponding archive urls availability?
>
> I asked that 3+ years ago and i think they are stored on Oi build
> servers, but not accessible from outside.
>
> It would be the best to always have all sources available at any time,
> so all source is fetched from OI servers, but it could be a project for
> itself to make upstream sources available locally on OI servers.
>
> Maintainers didn't like this, because fetching source archives from
> remote server is more simple for a building process.
>
> I also used to point out the legality of even distributing precompiled
> binaries before, without providing sources at any time. (and for any
> distributed binary).
> Having local store of source archives from the upstream projects,
> having all sources always available at OI site, would fix both legal and
> build problems and elevate problem if network source is not available.
> Maybe just make local source code archives on Oi servers, visible to all
> users?
>
>
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] Components archive url availability

[Dariusz Sendkowski]

Hi,

What happens when a component archive url points to a web resource that is
unavailable temporarily or, even worse, permanently? How does it impact the
package availability?

Are all these oi-userland components precompiled and stored somewhere on
the publisher server along with the sources? So when users install some
packages they fetch the precompiled packages regardless of the
corresponding archive urls availability?


regards,
Darek
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev