Rafael Ostertag | 16 Apr 08:26 2014

Unable to login on unstable10x

Hi guys

When trying to login on unstable10x, I get the following

 login$ ssh unstable10x
 Connection closed by 192.168.1.33

Any ideas?

TIA

cheers
rafi

Stefan Schnyder | 15 Apr 13:28 2014

Consolidation

Hi guys,

I'd like to share some thoughts about our documentation and information tools.

It's not hard to see, that "all that OpenCSW has" in regards to any kind of information for users/maintainers/devs is spread across a wide variety of tools & places.

Dago & I discussed this at the camp, and as Maciej has mentioned, parts of this have already been discussed earlier:

First of all, here's a list of all the tools & places I could find, that store information or act as a communication platform:
(tell me if I forgot something)
  • www.opencsw.org (Wordpress)
  • www.opencsw.org/manual (Sphinx - Python Documentation Generator)
  • www.opencsw.org/community (OpenSource Q&A)
  • opencsw.wikidot.com (WikiDot)
  • pkgutil.wikidot.com (WikiDot)
  • github.com/opencsw (GitHub with gar, pkg-all, discourse, osqa)
  • opencsw.sourceforge.net (HTML?)
  • sourceforge.net/projects/opencsw (SourceForge Project)
  • sourceforge.net/projects/gar (SourceForge Project)
  • sourceforge.net/apps/trac/gar & sourceforge.net/p/gar/tracwiki/Home (Trac, both sites seem to be the same)

Also - just as an overview - we have/use the following:
  • opencsw.org/mantis
  • buildfarm.opencsw.org
  • #opencsw on irc.freenode.net
  • Mail, Mailing Lists, Lists Archive, Webmail?
  • RSS Feeds
  • Flickr
  • YouTube
  • Google+
  • Twitter
  • Google Docs (group & shared files)
  • Facebook
  • Wikipedia
  • LinkedIn (nearly empty)

I'm not listing all of this because I think we should change it all. Just to raise awareness.

Now my thoughts:
  • I think, that our website doesn't need to contain that much information. It needs to get people started & provide access to further information and tools (Daniel had some nice ideas there).
  • The current info on the website, the manual, the wiki(s) and all info out there should be in one place. Preferably a tool which may be edited over a browser, if we want to give all people the ability to edit as well.
  • I support the idea of separating information from bugtracking from mailing lists from social media, etc. There should be only one place for the same kind of thing, but a place for each kind of thing.
  • The rework should be coupled with the new website that Daniel is working on.
  • It may be worth a thought if we should separate our "product" (the recipes & packages) from our own tools (gar, buildfarm, ...) or combine them. I'm talking about info & bugtracking & (...) for each or for both in one place. Having only one place would/could reduce the maintenance on the tools, but maybe lead to confusion for the users.
  • We should decide what needs to be done first, and what may come later.
I would like to propose, that we decide on a existing or new tool for storing & presenting information and then gradually start moving stuff away from the old locations. I would volunteer to do the moving.

What are your thoughts?

Cheers,
Stefan
Dagobert Michelsen | 13 Apr 16:56 2014

Broken login

Hi folks,

I was updating „login“ yesterday to the latest release and then went on with other stuff
as the update ran for quite a while. As it seems the update got stuck during updating
fontcache (I need to look into that). Regardless from that when I noticed the error the
pkgutil run aborted due to an error during installation in the fontconfig package.
The difficult problem is that pkgutil removes all packages and exits on error without
being able to continue or leaving a trace what is left to be done. It would be very useful
to have some „what is yet to do“ statusfile/script somewhere to pick up at that exact
location and finish the work.

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

Attachment (smime.p7s): application/pkcs7-signature, 3267 bytes
Rafael Ostertag | 13 Apr 11:12 2014

csw-upload-pkg on login

Hi guys

I'm trying to upload package on login. csw-upload-pkg dies with

 -bash: /opt/csw/bin/csw-upload-pkg: /opt/csw/bin/bash: bad interpreter: No such file or directory

Is there something I missed?

cheers
rafi

Maciej (Matchek) Bliziński | 12 Apr 13:07 2014

Killing newpkgs and pkgsubmissions lists

Hi Ihsan,

I propose we kill the newpkgs and pkgsubmissions mailing lists and remove them from the listinfo page[1]. They aren't used any more.

Maciej

Dagobert Michelsen | 10 Apr 15:38 2014

Permissions on www for the manual

Hi folks,

the ownership for the cswmanual was wrong the second time in a few days:

# ls -l;ls -l log
total 20
-rw-r--r--   1 cswmanual csw          405 Jan 27  2013 README
drwxr-xr-x   2 cswmanual csw            3 Jan 16  2013 bin
drwxr-xr-x   2 cswmanual csw            3 Jan 27  2013 log
drwxr-xr-x   7 wwwadmin csw           13 Apr 10 11:15 manual-html
drwxr-xr-x   6 cswmanual csw            7 Jan 16  2013 opencsw-manual
drwxr-xr-x   2 cswmanual csw            2 Dec  2 08:09 tmp
drwxr-xr-x   3 cswmanual csw            3 Dec  2 08:15 web
total 8
-rw-r--r--   1 wwwadmin csw         1637 Apr 10 11:15 buildlog

Is it possible that someone got wwwadmin and regenerated the manual?

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

Attachment (smime.p7s): application/pkcs7-signature, 3267 bytes
Stefan Schnyder | 9 Apr 23:49 2014

www.opencsw.org

Hello maintainers,

As some of you (may) have noticed, the announcements on the frontpage of 
www.opencsw.org didn't really look nice the last few days.
It would take (me) quite some time to have the announcements display the 
same on the frontpage as they do when the entry is displayed fully 
without breaking the rest of the site.
That's why I switched back to summaries - for now.

What's your opinion, do you want the posts to be fully displayed or 
shall we leave it like they are now?

Cheers,
Stefan

Dagobert Michelsen | 9 Apr 06:49 2014

Propagate OpenSSL to all releases

Hi Maciej,

can you please propagate the fixed OpenSSL package to all named releases?
I have made an announcement on the website, please update as you see fit.

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

Attachment (smime.p7s): application/pkcs7-signature, 3267 bytes
Carsten Grzemba | 8 Apr 10:30 2014
Picon

Re: links in CSWcommon



Am 08.04.14 schrieb Carsten Grzemba <grzemba-+og0gcNxkashFhg+JK9F0w@public.gmane.org>:
after some fiddle around why a non autotools package will find 32bit-libs and 64bit-libs not I saw that CSWcommon has a link
/opt/csw/lib/sparcv8 -> .
but it has no link
/opt/csw/lib/sparcv9/sparcv9 -> .

Should we have this link or have we solve this with an explicit listed search path for the base: '-R/opt/csw/lib/64/$ISALIST -R/opt/csw/lib/64'

Btw.: we have a recipe in gar for CSWcommon but it is not listed as 'package source' on http://www.opencsw .org/packages/CSWcommon/ (because it is called cswcommon?).

Carsten
Interesting: binutils creates an empty dir /opt/csw/lib/sparcv9/sparcv9

Carsten Grzemba | 8 Apr 10:25 2014
Picon

links in CSWcommon

after some fiddle around why a non autotools package will find 32bit-libs and 64bit-libs not I saw that CSWcommon has a link
/opt/csw/lib/sparcv8 -> .
but it has no link
/opt/csw/lib/sparcv9/sparcv9 -> .

Should we have this link or have we solve this with an explicit listed search path for the base: '-R/opt/csw/lib/64/$ISALIST -R/opt/csw/lib/64'

Btw.: we have a recipe in gar for CSWcommon but it is not listed as 'package source' on http://www.opencsw.org/packages/CSWcommon/ (because it is called cswcommon?).

Carsten

Migrating documentation to the manual

We have this page: http://www.opencsw.org/use-it/

It's linked off the big "Documentation" link on the green bar, and
it's not very well maintained.

We have our manual at http://www.opencsw.org/manual/ which looks like
a better place for this information. The code is here:

http://sourceforge.net/p/gar/code/HEAD/tree/csw/mgar/pkg/opencsw-manual/trunk/

Would anyone like to volunteer to move the content from the old
"use-it" page to the manual?

Maciej


Gmane