Re: [Slackbuilds-users] lighttpd.SlackBuild needs new maintainer

2016-08-11 Thread Matteo Bernardini
2016-08-12 4:44 GMT+02:00 Andrzej Telszewski :
> Hi,
>
> I contacted current maintainer of lighttpd, Paul Wisehart, and he said he
> will no longer maintain the lighttpd.SlackBuild.
>
> I'm no expert in the area, but I would like to point a few things for the
> new maintainer:
>
> 1. In
> https://slackbuilds.org/slackbuilds/14.2/network/lighttpd/README.SLACKWARE
> the location of php.ini should no longer be /etc/httpd, but /etc.
>
> 2. I'm not sure about that, but since the SlackBuild allows for changing
> user/group, the following line in
> https://slackbuilds.org/slackbuilds/14.2/network/lighttpd/conf/lighttpd.logrotate:
>
> create 0644 lighttpd lighttpd
>
> should be changed to:
>
> create 0644 @USER@ @GROUP@
>
> or simply:
>
> create
>
> 3. Probably it would be a good idea to provide more recent configuration
> file example.
>
>
> On a side note, (lighttpd2)
> https://slackbuilds.org/slackbuilds/14.2/network/lighttpd2/README.SLACKWARE,
> also contains /etc/httpd/php.ini, which should be changed to /etc/php.ini
> and possibly hardcoded user name in the logrotate conf file.

as I use lighttpd, if it's ok I'll step up as a maintainer.

Matteo

P.S. thanks Andrzej, I'll have a look at it.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



[Slackbuilds-users] lighttpd.SlackBuild needs new maintainer

2016-08-11 Thread Andrzej Telszewski

Hi,

I contacted current maintainer of lighttpd, Paul Wisehart, and he said 
he will no longer maintain the lighttpd.SlackBuild.


I'm no expert in the area, but I would like to point a few things for 
the new maintainer:


1. In 
https://slackbuilds.org/slackbuilds/14.2/network/lighttpd/README.SLACKWARE 
the location of php.ini should no longer be /etc/httpd, but /etc.


2. I'm not sure about that, but since the SlackBuild allows for changing 
user/group, the following line in 
https://slackbuilds.org/slackbuilds/14.2/network/lighttpd/conf/lighttpd.logrotate:


create 0644 lighttpd lighttpd

should be changed to:

create 0644 @USER@ @GROUP@

or simply:

create

3. Probably it would be a good idea to provide more recent configuration 
file example.



On a side note, (lighttpd2) 
https://slackbuilds.org/slackbuilds/14.2/network/lighttpd2/README.SLACKWARE, 
also contains /etc/httpd/php.ini, which should be changed to 
/etc/php.ini and possibly hardcoded user name in the logrotate conf file.


--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Comments required for iperf3 submission

2016-08-11 Thread Sebastian Arcus


On 11/08/16 16:04, Thomas Szteliga wrote:

On 11.08.2016 16:42, Willy Sudiarto Raharjo wrote:

I use iperf3 from time to time and find it very useful. I noticed that
SBo only has iperf2 - and would like to submit scripts for iperf3. Is
there much interest in this, and also, is there any reason why SBo
shouldn't have iperf3?

the maintainer is no longer active i guess
his last update was 6 years ago
i think you can take over this package and update it to iperf3



I would not update it to iperf3 but create a separate
iperf3 SlackBuild, because there are iperf2 and iperf3
clients out there, and v2 is not compatible with v3.

https://iperf.fr/iperf-download.php

Not every platform has iperf3 available and both
v2 and v3 are AFAIK still under development,
so I think it would be good to have both
available. Just a thought.


Yes - I think iperf2 and iperf3 are not compatible. I think having both 
iperf2 and iperf3 on SBo would be best.

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Comments required for iperf3 submission

2016-08-11 Thread Thomas Szteliga

On 11.08.2016 16:42, Willy Sudiarto Raharjo wrote:

I use iperf3 from time to time and find it very useful. I noticed that
SBo only has iperf2 - and would like to submit scripts for iperf3. Is
there much interest in this, and also, is there any reason why SBo
shouldn't have iperf3?

the maintainer is no longer active i guess
his last update was 6 years ago
i think you can take over this package and update it to iperf3



I would not update it to iperf3 but create a separate
iperf3 SlackBuild, because there are iperf2 and iperf3
clients out there, and v2 is not compatible with v3.

https://iperf.fr/iperf-download.php

Not every platform has iperf3 available and both
v2 and v3 are AFAIK still under development,
so I think it would be good to have both
available. Just a thought.


--
Thomas Szteliga




smime.p7s
Description: S/MIME Cryptographic Signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Comments required for iperf3 submission

2016-08-11 Thread Willy Sudiarto Raharjo
> I use iperf3 from time to time and find it very useful. I noticed that
> SBo only has iperf2 - and would like to submit scripts for iperf3. Is
> there much interest in this, and also, is there any reason why SBo
> shouldn't have iperf3?

the maintainer is no longer active i guess
his last update was 6 years ago

i think you can take over this package and update it to iperf3


-- 
Willy Sudiarto Raharjo



signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Fwd: monit change request

2016-08-11 Thread Sebastian Arcus


On 08/08/16 13:32, Bryan Harris wrote:

Interesting re: the restart command.  I think it's fixed by using
"monit quit" for the implementation of /etc/rc.d/rc.monit stop ---
i.e. more like what the upstream authors would do.  It's instantly
restarted on my machine when I do restart (using rc.monit script from
my last web form submission to SBo).

Can you test if it still behaves that way with the latest/current SBo package?


I just did - and it still kills monit
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Version bump - syncthing 14.4

2016-08-11 Thread Sebastian Arcus


On 11/08/16 10:57, Willy Sudiarto Raharjo wrote:

Please find attached a version bump (plus a few minor corrections) for
syncthing


Please use the submission form as usual since the submission is now
open. This applies to Navit that you sent earlier


Sure - thank you Willy

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Version bump - syncthing 14.4

2016-08-11 Thread Willy Sudiarto Raharjo
> Please find attached a version bump (plus a few minor corrections) for
> syncthing

Please use the submission form as usual since the submission is now
open. This applies to Navit that you sent earlier


-- 
Willy Sudiarto Raharjo



signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



[Slackbuilds-users] Comments required for iperf3 submission

2016-08-11 Thread Sebastian Arcus
I use iperf3 from time to time and find it very useful. I noticed that 
SBo only has iperf2 - and would like to submit scripts for iperf3. Is 
there much interest in this, and also, is there any reason why SBo 
shouldn't have iperf3?

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



[Slackbuilds-users] Version bump - syncthing 14.4

2016-08-11 Thread Sebastian Arcus
Please find attached a version bump (plus a few minor corrections) for 
syncthing


syncthing.tar.gz
Description: application/gzip
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Are new submission accepted yet?

2016-08-11 Thread Sebastian Arcus

On 10/08/16 18:35, Rob McGee wrote:

On Wed, Aug 10, 2016 at 09:51:40AM +0100, Sebastian Arcus wrote:

On 09/08/16 15:56, Matteo Bernardini wrote:

2016-08-09 16:50 GMT+02:00 Sebastian Arcus :

I've searched the list messages over the last few weeks but can't
figure the answer. Is SBo open to new submissions yet - or there
will be no more new stuff until next version of Slackware, or how
does it work? As some of you know I've helped prepare the Navit
SBo scripts, but that was just before 14.2 was released so I was
told to hold fire. When should I submit it?


maybe you missed Willy's message on july 24th

https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-July/016643.html


I certainly did - thank you for that! I confess I can't manage to
read all the messages on the list - so I just did a search by
subject. Thank you again for pointing it out.


Do we need an announcement list?


Maybe a much simpler solution would be to post important announcements 
as a new post, on their own - with a suitable subject line - such as 
"Announcement: New submissions accepted etc. etc". That's actually 
what I searched for initially - by subject line. If announcements are 
included inside another longer post, it is more difficult to find them. 
Then again, this is a friendly list, and one way or another answers are 
always forthcoming :-)

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



[Slackbuilds-users] New submission - Navit

2016-08-11 Thread Sebastian Arcus
As previously mentioned on this list, I'd like to submit the package 
Navit (www.navit-project.org) for inclusion at SBo. I think the 
appropriate category would be GIS. Many thanks to David Spencer for help 
with testing and corrections.


navit.tar.gz
Description: application/gzip
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/