Nekochan Net • View topic - Nekoware-current

View unanswered posts | View active topics View unread posts

Board index » SGI » SGI: Development

All times are UTC - 8 hours

Forum rules

Any posts concerning pirated software or offering to buy/sell/trade commercial software are subject to removal.

Nekoware-current

Page 1 of 58

[ 865 posts ]

Go to page 1, 2, 3, 4, 5 ... 58 Next

Print view

Previous topic | First unread post | Next topic

Author

Message

squeen

Post subject: Nekoware-current

Posted: Tue Feb 24, 2004 5:02 am

Moderator

Joined: Fri May 09, 2003 5:10 am
Posts: 2930
Location: Maryland, USA

<!...>

EDIT:
This thread is for all your feedback regarding the GNOME/GTK 2 Office for IRIX project.
Checkout the products in g2office section of the Nekochan.net download arena.

Please don't hold back -- air all of your grips and complaints -- that's the only way we can improve the product.

Personally, I would like to thank semifly for his huge effort and of course Neko for making it all possible.

Enjoy!

Last edited by squeen on Thu Aug 12, 2004 3:11 am, edited 3 times in total.

Top

squeen

Post subject:

Posted: Mon Aug 14, 2006 9:30 am

Moderator

Joined: Fri May 09, 2003 5:10 am
Posts: 2930
Location: Maryland, USA

OK. I'm going to continue to champion beta practices. When a major componet like GTK+, Perl, readline etc. gets updated and has the potential to massive disable nekoware, there needs to be a buffer---that's /beta. For top level apps with no child dependancies, it probably is less useful.

As for feeling disappointed about feedback, for the most part we port apps to meet a personal need and/or scratch an itch. That won't neccessarily translate to the community in general...well at least not immediately. But sometimes, maybe a year or so later, you will have made somebody's day/week/month in a big way. Let's hope's he/she takes the time to say thank you. My feeling is that most folks around here do. But, now that most the "core" apps have been ported, the odd-bits are less likely to win you immediate praise---which is unfortunate, because schleusel you do a fantastic job and we all benefit greatly from your hard work.

Last edited by squeen on Mon Aug 14, 2006 9:36 am, edited 1 time in total.

Top

nekonoko

Post subject:

Posted: Mon Aug 14, 2006 9:36 am

Site Admin

Joined: Thu Jan 23, 2003 1:31 am
Posts: 7947
Location: Pleasanton, California

squeen wrote:

I agree, but without feedback it's generally not too useful of a buffer. I try to test what I can myself but I have to wear so many hats just keeping up with my regular job testing is not something I can keep on top of on my own. I'll install/test things I have an immediate need for, but a lot of stuff falls through the cracks.

_________________
Twitter: @neko_no_ko
IRIX Release 4.0.5 IP12 Version 06151813 System V
Copyright 1987-1992 Silicon Graphics, Inc.
All Rights Reserved.

Top

squeen

Post subject:

Posted: Mon Aug 14, 2006 9:42 am

Moderator

Joined: Fri May 09, 2003 5:10 am
Posts: 2930
Location: Maryland, USA

Neko, you shouldn't have to bear the burden for sure. Instead, the packager should razz the community "SOMEONE PLEASE TEST MY APP", not, "Neko, why haven't you moved my app out of beta?". I don't really see the issue with apps lingering in beta for awhile if no one tests them., but that just suits my needs. Again, for the no deps, we can skip this step. But, I really depend on IRIX and Nekoware every day and instability is a major bane for me. For a casual (dare I say Linux) mentality, maybe new=better works. OK, that was a cheap shot...

Top

joerg

Post subject:

Posted: Mon Aug 14, 2006 10:43 am

Joined: Thu Jan 08, 2004 6:57 am
Posts: 2222
Location: In an origin rack - Germany

Pete,
about your tests with mysql 5.0.22. These version was a security only release and it contains no other fixes like the patches with correct the behaviour with the using of the wrong signals.

For more information about this issue take a look to
http://bugs.mysql.com/bug.php?id=15869

Some time ago i have talk to Foetz about this issue and he confirm that all of his own mysql builds also effected. But he did not care if the problem and didnt create a bug report.

But its fixed in the bitkeeper cvs and with the last 5.0.24 release.

regards
Joerg

_________________
http://www.irixworld.net

Top

nekonoko

Post subject:

Posted: Mon Aug 14, 2006 10:55 am

Site Admin

Joined: Thu Jan 23, 2003 1:31 am
Posts: 7947
Location: Pleasanton, California

joerg wrote:

For more information about this issue take a look to
http://bugs.mysql.com/bug.php?id=15869

I don't think it's the same issue. It's not that I couldn't shut the server down - it's that it would crash whenever phpBB2 tried to query the database through PHP5 (whenever a user hits the page, crash/restart).

_________________
Twitter: @neko_no_ko
IRIX Release 4.0.5 IP12 Version 06151813 System V
Copyright 1987-1992 Silicon Graphics, Inc.
All Rights Reserved.

Top

joerg

Post subject:

Posted: Mon Aug 14, 2006 11:50 am

Joined: Thu Jan 08, 2004 6:57 am
Posts: 2222
Location: In an origin rack - Germany

squeen wrote:

Neko, you shouldn't have to bear the burden for sure. Instead, the packager should razz the community "SOMEONE PLEASE TEST MY APP", not, "Neko, why haven't you moved my app out of beta?".

I hope you got something wrong. The only thing what i have ask for if its time to move the packages out of the beta directory. Nothing more and nothing less.

It might be possible that you build your packages why you need them for your own. Thats not true for me. I have build most of them by request from the community. The other half are needed because of dependencies or why i like to build something with all of the extras and not only a limited versions.

Quote:

I don't really see the issue with apps lingering in beta for awhile if no one tests them.

If the beta dir is growing and the packages are aging over the time it makes is harder to create new packages, because you have to take care of versioning and dependancies. So from time to time we have to move the bunch of packages.

Btw:
If i would like so see something in /current i would place it there.

regards
Joerg

_________________
http://www.irixworld.net

Top

squeen

Post subject:

Posted: Mon Aug 14, 2006 12:31 pm

Moderator

Joined: Fri May 09, 2003 5:10 am
Posts: 2930
Location: Maryland, USA

joerg wrote:

I hope you got something wrong.

Yes I did. I meant to include you with schleusel, neko (and others) in my praise for the prolific and excellent work you have done.

I see your point on stale beta dependancies, but all that is required to move from beta to current is only one other member to validate it works OK on their system. Too often our build systems can accumulate items that are missing from the packages. It's just a check on that.

Quote:

Btw:
If i would like so see something in /current i would place it there.

Sorry, I don't follow what you are saying here.

Oh well...I see value in a /beta-staging, but also sense that Neko would rather do without the added responsibility. I totally understand that, and only want to deflect that responsibility to the developers and community members instead.

Top

whiter

Post subject:

Posted: Tue Aug 15, 2006 8:52 am

Joined: Tue Apr 29, 2003 1:02 pm
Posts: 966
Location: Rijswijk, The Netherlands. Reigate, England.

in beta:

neko_irssi-0.8.10a-tardist

Updated the version by Timo to the latest version, and to use perl 5.8.8.
There were a few weirdnesses in the package, which I fixed. But there's one I'm not sure about how inst handles it:

A file was packaged in subsystem neko_irssi.sw.perl while it actualy belonged in neko_irssi.sw.lib. In the new version of the tardist I moved this. What will inst do when upgrading the previously installed version of the package to this new one?

_________________
Shall I describe it to you? Or do you want me to get you a box?

Top

nekonoko

Post subject:

Posted: Tue Aug 15, 2006 10:59 am

Site Admin

Joined: Thu Jan 23, 2003 1:31 am
Posts: 7947
Location: Pleasanton, California

Just a followup on neko_mysql-5.0.24 - I wasn't able to get it to work

Same issue:

Code:

060815 11:50:38  InnoDB: Started; log sequence number 0 47650
060815 11:50:38 [Note] /usr/nekoware/mysql5/libexec/mysqld: ready for connections.
Version: '5.0.24'  socket: '/usr/nekoware/var/run/mysql5/mysql.sock'  port: 3306  Source distribution
mysqld got signal 6;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=16777216
read_buffer_size=258048
max_used_connections=1
max_connections=100
threads_connected=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 92783 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

060815 11:50:39  mysqld restarted

Oh, and I noticed that /etc/init.d/neko_mysql5 has:

Code:

PROG=neko_mysql4

Instead of:

Code:

PROG=neko_mysql5

So it wouldn't start until that was changed.

Sorry for the outage guys - just wanted to give it another shot.

On a positive note, I was able to turn the blog search back on after the neko_perl-5.8.8 upgrade (and 'DBD::mysql' compile); it was broken after perl-5.8.4 for some reason. Thanks much for the new version whiter!

_________________
Twitter: @neko_no_ko
IRIX Release 4.0.5 IP12 Version 06151813 System V
Copyright 1987-1992 Silicon Graphics, Inc.
All Rights Reserved.

Top

joerg

Post subject:

Posted: Tue Aug 15, 2006 11:25 am

Joined: Thu Jan 08, 2004 6:57 am
Posts: 2222
Location: In an origin rack - Germany

nekonoko wrote:

Just a followup on neko_mysql-5.0.24 - I wasn't able to get it to work :(

Code:

PROG=neko_mysql5

This was from the mysql-5.0.7 version. It was fixed in the current package. But the files is marked as 'noupdate'.

About the other problems i will go and see if i can reproduce it.

regards
Joerg

_________________
http://www.irixworld.net

Top

nekonoko

Post subject:

Posted: Tue Aug 15, 2006 12:06 pm

Site Admin

Joined: Thu Jan 23, 2003 1:31 am
Posts: 7947
Location: Pleasanton, California

joerg wrote:

This was from the mysql-5.0.7 version. It was fixed in the current package. But the files is marked as 'noupdate'.

Ah okay. Makes it difficult to push out changes/bugfixes to the startup script though. Maybe changing it to 'suggest' would be helpful.

Quote:

About the other problems i will go and see if i can reproduce it.

No rush. 5.0.12 works well enough; I just find it odd that later versions are failing spectacularly. Maybe one of these days when I have a moment I'll do a diff between 5.0.12 and 5.0.13 and see if I can find something.

Top

whiter

Post subject:

Posted: Tue Aug 15, 2006 1:11 pm

Joined: Tue Apr 29, 2003 1:02 pm
Posts: 966
Location: Rijswijk, The Netherlands. Reigate, England.

nekonoko wrote:

On a positive note, I was able to turn the blog search back on after the neko_perl-5.8.8 upgrade (and 'DBD::mysql' compile); it was broken after perl-5.8.4 for some reason. Thanks much for the new version whiter!

No problemo. Glad to be of service.
Movabletype is the main reason why I had to work on getting a newer perl in the first place ;)
( Officialy MT 3.2+ requires perl 5.8.6+ )

I managed to get it working on irix running under mod_perl. The speed increase is absolutely stunning. If you're running apache 1.3 and don't use mod_perl yet, it's definnitely worth trying it.

_________________
Shall I describe it to you? Or do you want me to get you a box?

Top

schleusel

Post subject:

Posted: Tue Aug 15, 2006 4:11 pm

Joined: Mon Oct 20, 2003 5:49 am
Posts: 494
Location: NRW, Germany

whiter wrote:

in beta:

neko_irssi-0.8.10a-tardist

cool, works great so far :-)

Quote:

A file was packaged in subsystem neko_irssi.sw.perl while it actualy belonged in neko_irssi.sw.lib. In the new version of the tardist I moved this. What will inst do when upgrading the previously installed version of the package to this new one?

hm, the upgrade simply consists of removing the old content of the updated subsystems and installing the new content, no fancy merge procedure or the like.. so moving files between subsystems will simply work without side effects.

_________________
http://www.kanera.net

Top

schleusel

Post subject:

Posted: Tue Aug 15, 2006 4:21 pm

Joined: Mon Oct 20, 2003 5:49 am
Posts: 494
Location: NRW, Germany

uploaded to beta:

neko_cyrus_imapd-2.2.12.tardist - new package of the same (still current) version because it had some hooks in the old perl tree
neko_cyrus_sasl-2.1.22.tardist new version
neko_db4-4.4.20.tardist new version

the cyrus_imapd build is linked against that new db4 version which apparently introduces some incompatibilities with the db files of existing cyrus imapd installations. Rebuilding them using db_recover (part of the neko_db4 package) fixed it for me. I placed a note about that in the relnotes. No other problems yet..

Anyway, even it its still the same release i'd like to watch it on my mail server for two days before moving it out of beta :-)

_________________
http://www.kanera.net

Top

Page 1 of 58

[ 865 posts ]

Go to page 1, 2, 3, 4, 5 ... 58 Next

Board index » SGI » SGI: Development

All times are UTC - 8 hours

Who is online

Users browsing this forum: No registered users and 2 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum