Hi all, this has been silent recently, too silent ;-) Lets try to get some concrete action items we can work on. First step should be to have an overview over all packages the Invis server needs. In a perfect world, these should all be part of the openSUSE:Factory project as that garantees the best integration with the distribution. For packages that do absolutely not fit into Factory for what reason ever, I suggest to create the server:invis project in OBS and put them there. Later on, we can put the Kiwi-Image file, which is used to create the iso image of the openSUSE Invis Server, into the server:invis repo and let OBS create the image. In the ideal world we only would have the product kiwi file in server:invis. Is everybody agreeing on that? As a first action item, we should go through the list of packages installed through the Invis setup script and check if they are in Factory. If not, we should move them to Factory, or, as a second possibility, to server:invis. I created a list of packages some time ago which get directly installed by the Invis setup script (attached again). The list of packages which are not yet in Factory is comparably short: afio -> home:flacco ipcalc -> home:flacco smbldap-tools -> home:flacco php5-APC -> server:php:extensions php5-pear-mail -> server:php:applications phpMyAdmin -> server:php:applications We should try to push these to Factory. Anybody volunteering? A good read how that works is http://en.opensuse.org/openSUSE:How_to_contribute_to_Factory Stefan, are there other packages needed? regards, Klaas
Hi all,
this has been silent recently, too silent ;-) Lets try to get some concrete action items we can work on.
First step should be to have an overview over all packages the Invis server needs. In a perfect world, these should all be part of the openSUSE:Factory project as that garantees the best integration with the distribution. Agree For packages that do absolutely not fit into Factory for what reason ever, I suggest to create the server:invis project in OBS and put them there. Later on, we can put the Kiwi-Image file, which is used to create the iso image of the openSUSE Invis Server, into the server:invis repo and let OBS create the image. In the ideal world we only would have the product kiwi file in server:invis.
Is everybody agreeing on that? Agree As a first action item, we should go through the list of packages installed through the Invis setup script and check if they are in Factory. If not, we should move them to Factory, or, as a second possibility, to server:invis.
I created a list of packages some time ago which get directly installed by the Invis setup script (attached again). The list of packages which are not yet in Factory is comparably short:
afio -> home:flacco ipcalc -> home:flacco These both packages are kicked of the openSUSE OSS Repos in the newer
Hi Klaas, sorry for the silence. We had a lot of work to do in the past two weeks. By the way. At OpenRheinRuhr we talked to a lot of people who are interested to help us at invis server developement. Am 18.11.2010 17:00, schrieb Klaas Freitag: past. Get them back into the Distribution wood be nice. Jürgen Weigert told me the reason for kicking afio. There is no maintainer for this package. If we want to do this it should be easy to get it back.
smbldap-tools -> home:flacco
php5-APC -> server:php:extensions
php5-pear-mail -> server:php:applications phpMyAdmin -> server:php:applications
We should try to push these to Factory. Anybody volunteering? A good read how that works is Agree.
In my OBS repo i build the whole PHP5-standard-packages because the openSUSE packages didn't support PTYs (pseudo terminals). We need PTY-support for the builtin-Samba-Access of our Groupware Group-e. In the past there was a big discussion between PHP-developers about security problems with PTY-Support. For a short time it was kicked off PHP. But the PTY-support is again included in PHP5 but not in openSUSE. (english is difficult, hope you understand what i wrote)
http://en.opensuse.org/openSUSE:How_to_contribute_to_Factory
Stefan, are there other packages needed? We have to build packages for our third-party software:
- LX-Office (lx-erp) (and later Pirmin Brauns IntarS and/or OpenERP) - Group-e - PHPLDAPadmin - Dokuwiki Next is our "invis Portal" and "CorNAZ" our Mailaccount-Configuration tool. But i think, that i first have to work on it... Then we need the packages from Ingo Göppert (home:igoeppert). He is the maintainer of Faxgate (an capisuite extension). He told me, that he is interested to help us working on invis server. For the future it would be nice to include alfresco document management and openbenno mailarchive, but we have to discuss this because of "german law restrictions".
regards, Klaas There's a lot of work to do ;-)
regards, Stefan -- www.invis-server.org Stefan Schäfer Vogelsbergstr. 27 63679 Schotten -- To unsubscribe, e-mail: opensuse-invis+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-invis+help@opensuse.org
Am Donnerstag 18 November 2010, 17:32:45 schrieb Stefan Schäfer: Hey,
sorry for the silence. We had a lot of work to do in the past two weeks.
By the way. At OpenRheinRuhr we talked to a lot of people who are interested to help us at invis server developement.
Cool, have you dragged them in here ;-) ? The idea now is to push all needed packages to openSUSE:Factory for best integration.
afio -> home:flacco ipcalc -> home:flacco
These both packages are kicked of the openSUSE OSS Repos in the newer past. Get them back into the Distribution wood be nice. Jürgen Weigert told me the reason for kicking afio. There is no maintainer for this package. If we want to do this it should be easy to get it back. It should, if somebody volunteers to maintain it. Is actually somebody volunteering?
smbldap-tools -> home:flacco
php5-APC -> server:php:extensions
php5-pear-mail -> server:php:applications phpMyAdmin -> server:php:applications
Here again: Is somebody volunteering? If not on this list, we need to ask at opensuse-packaging list. But people are of course not so keen on maintaining stuff others have interest in, so it would be easier if we do it or find packager who are interested in
In my OBS repo i build the whole PHP5-standard-packages because the openSUSE packages didn't support PTYs (pseudo terminals). We need PTY-support for the builtin-Samba-Access of our Groupware Group-e. In the past there was a big discussion between PHP-developers about security problems with PTY-Support. For a short time it was kicked off PHP. But the PTY-support is again included in PHP5 but not in openSUSE. I am in contact about that with Christian Rodriguez, the PHP maintainer. He will help us to fix this.
We have to build packages for our third-party software:
- LX-Office (lx-erp) (and later Pirmin Brauns IntarS and/or OpenERP) LX-Office is already in the OBS in home:computersalat:devel. We need to ask him to maintain it in server:invis - Group-e not yet in OBS, needs to be packaged - PHPLDAPadmin already in server:php_applications
- Dokuwiki already in hoem:werfl
Next is our "invis Portal" and "CorNAZ" our Mailaccount-Configuration tool. But i think, that i first have to work on it...
Is the code for these public accessible?
Then we need the packages from Ingo Göppert (home:igoeppert). He is the maintainer of Faxgate (an capisuite extension). He told me, that he is interested to help us working on invis server. Cool, so he volunteers to maintain the packages?
There's a lot of work to do ;-) Sure, but I haven't still given up that we have the packages sorted for 11.4. Lets see :-)
regards, Klaas -- To unsubscribe, e-mail: opensuse-invis+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-invis+help@opensuse.org
Hi, Am Donnerstag, 2. Dezember 2010 schrieb Klaas Freitag: [...]
Then we need the packages from Ingo Göppert (home:igoeppert). He is the maintainer of Faxgate (an capisuite extension). He told me, that he is interested to help us working on invis server.
Cool, so he volunteers to maintain the packages?
yes, here I am :-) What do I have to do?
There's a lot of work to do ;-)
Sure, but I haven't still given up that we have the packages sorted for 11.4. Lets see :-)
Regards, Ingo -- ## Open & free -- http://www.invis-server.org/ ## Windows, Linux und Mac Office-Suite -- http://de.openoffice.org/ ## Die OpenOffice.org PrOOo-Box -- http://prooo-box.org/
Am Donnerstag 02 Dezember 2010, 20:14:24 schrieb Ingo Göppert: Hi Ingo, > [...] > > > > Then we need the packages from Ingo Göppert (home:igoeppert). He is > > > the maintainer of Faxgate (an capisuite extension). He told me, > > > that he is interested to help us working on invis server. > > > > Cool, so he volunteers to maintain the packages? > > yes, here I am :-) Cool! Nice that you're here :-) > What do I have to do? - Get to know the OBS, which you obviously already do :) - Wait until we have the server:Invis project in OBS and push the packages in there. I'll take care of the creation of server:Invis and let you know. regards, Klaas -- To unsubscribe, e-mail: opensuse-invis+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-invis+help@opensuse.org
Am Donnerstag 02 Dezember 2010, 20:14:24 schrieb Ingo Göppert: Hey Ingo,
Then we need the packages from Ingo Göppert (home:igoeppert). He is the maintainer of Faxgate (an capisuite extension). He told me, that he is interested to help us working on invis server.
Cool, so he volunteers to maintain the packages?
yes, here I am :-) What do I have to do?
I added your useraccount ingogoeppert as maintainer to project spins:invis. Would be great if you move the two packages to spins:invis. Currently the invis project has less repos than your home project, but we can add the missing ones to the invis project if others agree. regards, Klaas
There's a lot of work to do ;-)
-- To unsubscribe, e-mail: opensuse-invis+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-invis+help@opensuse.org
Am Mittwoch, 8. Dezember 2010 schrieb Klaas Freitag:
Would be great if you move the two packages to spins:invis. Currently the invis project has less repos than your home project, but we can add the missing ones to the invis project if others agree.
I moved the faxgate package to spins:invis, the other package "sox" is no longer needed. Also I think there is no need to add more repos. Regards, Ingo -- ## Open & free -- http://www.invis-server.org/ ## Windows, Linux und Mac Office-Suite -- http://de.openoffice.org/ ## Die OpenOffice.org PrOOo-Box -- http://prooo-box.org/
Am Donnerstag 18 November 2010, 17:32:45 schrieb Stefan Schäfer: Hi,
afio -> home:flacco ipcalc -> home:flacco
These both packages are kicked of the openSUSE OSS Repos in the newer past. Get them back into the Distribution wood be nice. I investigated a bit on these two. afio was dropped and it has a questionable license, check the wikipedia article. I would not want to take it back into Factory.
I attached a patch that patches afio out of bin/alldump in Invis, that seems the only place where its used. afio has the advantage over other programs to compress before archiving, I simulated that by first bzip2'ing all dumps and archive them via tar later. Is that acceptable? regards, Klaas
Hi Am 07.12.2010 16:09, schrieb Klaas Freitag:
Am Donnerstag 18 November 2010, 17:32:45 schrieb Stefan Schäfer: Hi,
afio -> home:flacco ipcalc -> home:flacco These both packages are kicked of the openSUSE OSS Repos in the newer past. Get them back into the Distribution wood be nice. I investigated a bit on these two. afio was dropped and it has a questionable license, check the wikipedia article. I would not want to take it back into Factory. At the Conference i talked to Jürgen Weigert about this problem. That's what he told me about afio (Sorry it's in german):
"Hi Stefan! Ich habs mal eben nachgeschlagen. Afio wurde aus rein technischen Gründen von der Distribution genommen. Die rechtliche Seite ginge klar. 14.03.05, denicolo: Packages licenses have been checked and approved. Einmal scheint die Non-commercial Klausel sehr schwach. Zum Zweiten hatten wir 1998 den damaligen Upstream Koen Holtman direkt auf diese Klausel angesprochen und seine Zustimmung eingeholt. 2008-08-15radmanic@novell.com it's completely outdated, lacks specific features like ACL support and is unmaintained since 2003, we should drop this package! 2009-05-20mt@novell.com Changed status to dropped Approved by:ro@novell.com D.h. wir hatten schlicht niemand mehr, der es maintained. Einfache Lösung: mach einen submitrequest und schlage Dich gleich selbst als Maintainer vor. $ osc submitpac home:flacco afio openSUSE:Factory -m "I use the package, I'll maintain it." cheers, JW-"
I attached a patch that patches afio out of bin/alldump in Invis, that seems the only place where its used. afio has the advantage over other programs to compress before archiving, I simulated that by first bzip2'ing all dumps and archive them via tar later.
Is that acceptable? afio is a very good tool an i wish it back, but i test your patch. regards,
Klaas
regards Stefan -- To unsubscribe, e-mail: opensuse-invis+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-invis+help@opensuse.org
Hi,
At the Conference i talked to Jürgen Weigert about this problem. That's what he told me about afio (Sorry it's in german):
"Hi Stefan!
Ich habs mal eben nachgeschlagen. Afio wurde aus rein technischen Gründen von der Distribution genommen. Die rechtliche Seite ginge klar.
14.03.05, denicolo: Packages licenses have been checked and approved. Einmal scheint die Non-commercial Klausel sehr schwach. Zum Zweiten hatten wir 1998 den damaligen Upstream Koen Holtman direkt auf diese Klausel angesprochen und seine Zustimmung eingeholt.
2008-08-15radmanic@novell.com it's completely outdated, lacks specific features like ACL support and is unmaintained since 2003, we should drop this package!
2009-05-20mt@novell.com Changed status to dropped Approved by:ro@novell.com
D.h. wir hatten schlicht niemand mehr, der es maintained. hmm, und es ist halt seit 2003 auch upstream nicht mehr maintained.
I attached a patch that patches afio out of bin/alldump in Invis, that seems the only place where its used. afio has the advantage over other programs to compress before archiving, I simulated that by first bzip2'ing all dumps and archive them via tar later.
Is that acceptable?
afio is a very good tool an i wish it back, but i test your patch. of course you can get it back, but if we take it to the invis project it means that we as a team have to maintain it for Factory.
I think we have work enough and should reduce the needed packages where possible. And in this case we have good replacements that are maintained anyway in Factory. regards, Klaas -- To unsubscribe, e-mail: opensuse-invis+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-invis+help@opensuse.org
participants (3)
-
Ingo Göppert -
Klaas Freitag -
Stefan Schäfer