For the love of $deity... test!

[Alver]

It's been a while since I last did some IRIX development, so I fired up the ol' O2 and did a nekosync && update for good measure. Boy, did stuff break... files with bad ownership, causing new users to be created on my system; missing files; binaries linking to obvious build paths in someone's home dir rather than /usr/nekoware; missing dependencies; ...

There's good howtos on creating clean nekoware packages, but it seems they're often forgotten please people, if you dump a tardist in neko's beta ftp, make sure you have installed and tested it on a clean machine - not your regular development box, or at least make sure your dev structure won't interfere. We may need a way to flag bad packages quicker too before more victims are made.

Now to undo this mess before I can start building something...

[PymbleSoftware]

It's been a while since I last did some IRIX development, so I fired up the ol' O2 and did a nekosync && update for good measure. Boy, did stuff break... files with bad ownership, causing new users to be created on my system; missing files; binaries linking to obvious build paths in someone's home dir rather than /usr/nekoware; missing dependencies; ...

There's good howtos on creating clean nekoware packages, but it seems they're often forgotten please people, if you dump a tardist in neko's beta ftp, make sure you have installed and tested it on a clean machine - not your regular development box, or at least make sure your dev structure won't interfere. We may need a way to flag bad packages quicker too before more victims are made.

Now to undo this mess before I can start building something...

Please report what specifically is broken.. We need to know what need to be reverted... I haven't updated nekoware in a awhile but I've not seen anything broken. Please report specific instances.. Testing by someone else while it is still in beta is essential.


R.

[SAQ]

I remember one troubleshoot that was very troublesome - a program had -mips4 in one of the sub-Makefiles that was buried deep in the tree. I changed the global to -mips3 and built it, resulting binary worked just fine on my Origin, but failed on another user's IP22. There's plenty out there to bite ya, and though some testing should be done to get it out of alpha stage do remember that it's called /beta for a reason.

[hamei]

Please report what specifically is broken.. We need to know what need to be reverted... I haven't updated nekoware in a awhile but I've not seen anything broken.

viewtopic.php?f=15&t=16724791

Everything by darkfires, okay ? It's all junk. Install that stuff and your computer will break, bigtime. Busted busted busted no damn good. I tried to bring this up politely and all I got was a bunch of namby-pamby bullshit by josehill. Now you're going to pretend that thread never happened ?

Well guess what, people ? If you want this stuff to work you can just get off your la-dee-da asses and do something about it. Either that or bye-bye SGI usefulness. Without nekoware, this platform is deader than Publius Maximus.

[kshuff]

I've missed you hamei

Please report what specifically is broken.. We need to know what need to be reverted... I haven't updated nekoware in a awhile but I've not seen anything broken.

viewtopic.php?f=15&t=16724791

Everything by darkfires, okay ? It's all junk. Install that stuff and your computer will break, bigtime. Busted busted busted no damn good. I tried to bring this up politely and all I got was a bunch of namby-pamby bullshit by josehill. Now you're going to pretend that thread never happened ?

Well guess what, people ? If you want this stuff to work you can just get off your la-dee-da asses and do something about it. Either that or bye-bye SGI usefulness. Without nekoware, this platform is deader than Publius Maximus.

[ianj]

All of the packages I submit are in use on my own production machines, so I eat the dogfood and do my best to pick out packaging mistakes before uploading. If you notice problems, though, please contact me and I will re-upload ASAP.

As for darkfires - he pulled his SGI out of the closet, blew through a lot of packages at a breakneck pace, then disappeared (to my knowledge). Some of the less ambitious stuff (like neko_xz) works fine, and I use them, but to be honest I never expected anything like the latest GTK package to work. It would be nice to have a procedure for getting the packages that are known not to work out of /beta to avoid confusion, while still leaving them available in some form in case they can be fixed.

Also, is there a clear path for packages to go from /beta to /current? It seems like we're approaching a situation where many commonly-used packages are in /beta, which makes it more of an issue that some of the /beta packages aren't really tested.

[nekonoko]

Also, is there a clear path for packages to go from /beta to /current? It seems like we're approaching a situation where many commonly-used packages are in /beta, which makes it more of an issue that some of the /beta packages aren't really tested.

As I've said before, someone just needs to let me know. I'm not clairvoyant - I don't know which packages you use and have had good success with. I also don't currently have an SGI system running to test myself (all machines are currently in storage or just not hooked up).

By the same token, if packages are totally broken, let me know that as well so they can be moved to the obsolete directory. Once again, I don't have mystical powers of deduction to determine which packages borked your system. You need to tell me.

[ianj]

I want to make clear that I wasn't trying to dump any responsibility on you; I've seen some mentions of suggesting things be moved to /current, but wasn't sure if I was missing anything more concrete. Sometimes I forget that you're pushing those packages around the hierarchy all by yourself...

I haven't been pushing to get my own packages moved to /current because I don't want to come off as promoting my work before at least a few other people have chimed in saying the packages are solid. I have a feeling this kind of information tends not to find its way back to packagers, though. Maybe we need to be more proactive about letting packagers know their submissions are working for us? I haven't been so good at following up this way myself. Most of the packages I submitted have been running on my server for a year or more, but I'd like to know a few other people have laid eyes on them before I start claiming they belong in /current.

What this whole conversation makes me feel like doing is to start taking a walk through the entire /beta directory and note which packages work, which work, but have packaging errors or would break existing /current dependencies, and which are broken. I already use many of these, but I'd like to gather all that information together. I'll let you know what I find.

[ShadeOfBlue]

Just an idea... Would it perhaps be easier if there was a separate subforum for nekoware packages?

The package submitter would create a new thread for each submitted package and add a simple "Works: yes/no" poll to the thread. The users could anonymously vote whether the package works for them or not.

Any problems with that package could be reported in the same thread. If enough users vote that the package works, it's moved to /current.

[bplaa.yai]

Code: Select all

> versions | grep pixbuf
I  neko_gdk_pixbuf      05/02/2011  gdk_pixbuf 2.22.1 - Core libraries for GTK+ and GNOME
I  neko_gdk_pixbuf.man  05/02/2011  man pages
I  neko_gdk_pixbuf.man.manpages  05/02/2011  man pages
I  neko_gdk_pixbuf.opt  05/02/2011  optional software
I  neko_gdk_pixbuf.opt.relnotes  05/02/2011  release notes
I  neko_gdk_pixbuf.sw   05/02/2011  software
I  neko_gdk_pixbuf.sw.eoe  05/02/2011  execution only env
I  neko_gdk_pixbuf.sw.hdr  05/02/2011  header files
I  neko_gdk_pixbuf.sw.lib  05/02/2011  shared library files


Code: Select all

> showfiles neko_gdk_pixbuf.sw.lib | grep libgdk_pixbuf-2.0.so.1
l     0     0 neko_gdk_pixbuf.sw.lib   usr/nekoware/lib/libgdk_pixbuf-2.0.so.1
f 46800 172788 neko_gdk_pixbuf.sw.lib   usr/nekoware/lib/libgdk_pixbuf-2.0.so.1.1


Code: Select all

> ldd /usr/nekoware/lib/libgdk_pixbuf-2.0.so.1
744103: 20:56:44 /usr/nekoware/lib/libgdk_pixbuf-2.0.so.1: rld: Fatal Error exit/longjmp: Cannot Successfully map soname 'libpixops.so.1' under any of the filenames /usr/nekoware/lib/libpixops.so.1:/usr/people/lwhite/glib-2.26.1/glib/.libs/libpixops.so.1:/usr/java2/jre/lib32/libpixops.so.1:/usr/nekoware/mysql5/lib/mysql/libpixops.so.1:/usr/lib32/libpixops.so.1:/usr/lib32/internal/libpixops.so.1:/lib32/libpixops.so.1:/opt/lib32/libpixops.so.1:/usr/nekoware/lib/libpixops.so.1.1:/usr/people/lwhite/glib-2.26.1/glib/.libs/libpixops.so.1.1:/usr/java2/jre/lib32/libpixops.so.1.1:/usr/nekoware/mysql5/lib/mysql/libpixops.so.1.1:/usr/lib32/libpixops.so.1.1:/usr/lib32/internal/libpixops.so.1.1:/lib32/libpixops.so.1.1:/opt/lib32/libpixops.so.1.1:
744103:/usr/nekoware/lib/libgdk_pixbuf-2.0.so.1: rld: Fatal Error: Cannot Successfully map soname 'libpixops.so.1' under any of the filenames /usr/nekoware/lib/libpixops.so.1:/usr/people/lwhite/glib-2.26.1/glib/.libs/libpixops.so.1:/usr/java2/jre/lib32/libpixops.so.1:/usr/nekoware/mysql5/lib/mysql/libpixops.so.1:/usr/lib32/libpixops.so.1:/usr/lib32/internal/libpixops.so.1:/lib32/libpixops.so.1:/opt/lib32/libpixops.so.1:/usr/nekoware/lib/libpixops.so.1.1:/usr/people/lwhite/glib-2.26.1/glib/.libs/libpixops.so.1.1:/usr/java2/jre/lib32/libpixops.so.1.1:/usr/nekoware/mysql5/lib/mysql/libpixops.so.1.1:/usr/lib32/libpixops.so.1.1:/usr/lib32/internal/libpixops.so.1.1:/lib32/libpixops.so.1.1:/opt/lib32/libpixops.so.1.1:


beta/neko_gdk_pixbuf-2.22.1.tardist looks definitly bad to me.

[bplaa.yai]

Just an idea... Would it perhaps be easier if there was a separate subforum for nekoware packages?

The package submitter would create a new thread for each submitted package and add a simple "Works: yes/no" poll to the thread. The users could anonymously vote whether the package works for them or not.

Any problems with that package could be reported in the same thread. If enough users vote that the package works, it's moved to /current.

I think it's a good idea. It would make it easier to track packages submission, especially in case of /beta flooding...

[ianj]

Just an idea... Would it perhaps be easier if there was a separate subforum for nekoware packages?

The package submitter would create a new thread for each submitted package and add a simple "Works: yes/no" poll to the thread. The users could anonymously vote whether the package works for them or not.

Any problems with that package could be reported in the same thread. If enough users vote that the package works, it's moved to /current.

I like this idea. I don't know if there needs to be a separate subforum just for packages, but at the least, I'll sign onto adding a "Works?" poll to all my future upload announcements.

beta/neko_gdk_pixbuf-2.22.1.tardist looks definitly bad to me.

I would not trust any of the packages related to GTK 2.22.1 at this point.

[PymbleSoftware]

I've missed you hamei

ditto.
I think we all have.

R.

[SAQ]

I'm not sure if it's a general thing or special for me, but I can move over my packages when I feel they've been tested enough. Sadly, often I don't get very many reports of tests (don't know if that's MIPS-3 specific or general), so it's hard to gauge the quality. Hint to users: if you try something out from /beta and it works, let the packager know!

Good news, (possibly) - I might be getting a smaller build box (O300) that my wife will let in the house, enabling me to start building MIPS-3 stuff again.

[hamei]

Just an idea... Would it perhaps be easier if there was a separate subforum for nekoware packages?

I asked that once myself. Mr Neko quite rightly pointed out that that's what the "Development" forum is for. There's a "Software" forum for general talk about programs ... although maybe a semi-agreed upon standard for reporting on beta apps could be good. Like the [eBay] label we sort of used to have : maybe [beta report] or similar in the subject line ?

Mr Neko, I did report on a lot of those application, but was trying to be too polite and not drive off a potential developer. Won't make that mistake again : they are BAD. Bad bad bad. Many of them are quite totally broken, as Alver poihted out. The worst of the Linux World came to our little backwater of the Internet. Cosmos is laughing, Tux it up !

If anybody wants to flame me, you have permission. I'll take care of that annoying pain in the ass for you ...