Re: ports/148777: [New Port] sysutils/qjail: Utility to deploy large number of jails quickly

2010-11-05 Thread joeb
What is the holdup about adding this simple port to the port system?

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


FreeBSD Port: plone3-3.1.7_2

2010-11-09 Thread joeb
This port is broken and way out of date.
It can not find the Plone-3.1.7.tar.gz file to download.
Plone 4 is the current version.


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Attention ports committers

2011-01-14 Thread joeb
I would like to draw the attention of a ports committer to port 

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/148777

If it needs further work please provide feedback.


Thanks for your attention to commit this port.

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


RE: Attention ports committers

2011-01-19 Thread joeb


-Original Message-
From: r...@codelabs.ru [mailto:r...@codelabs.ru]On Behalf Of Eygene Ryabinkin
Sent: Friday, January 14, 2011 4:46 PM
To: joeb
Cc: po...@freebsd.org
Subject: Re: Attention ports committers

Good day.

Fri, Jan 14, 2011 at 01:18:52PM -0500, joeb wrote:
> I would like to draw the attention of a ports committer to port
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/148777
>
> If it needs further work please provide feedback.

A couple of things about the port:
 - you can just use plain SF instead of a long to type
   ${MASTER_SITE_SOURCEFORGE}; moreover, plain SF/${PORTNAME}
   and no MASTER_SITE_SUBDIR will work too and save you
   one more line;
 - share/examples/qjail in the pkg-plist is better spelled
   as %%EXAMPLESDIR_REL%%; and its ${PREFIX}/share/examples/qjail
   in the Makefile should really be ${EXAMPLESDIR}; also
   you can consider using PORTEXAMPLES to use port's procedures
   to install the examples and to avoid installing them when
   NOPORTEXAMPLES is set;
 - it is better to remove the commented DISTFILES, since
   it is not needed thus just adds the visual clutter;
 - pkg-descr is a way too chatty (in my taste); it can be
   definitely stripped down to provide the idea about
   what qjail is and the whole text can be put to the
   project's Web site;
 - you can put your rc.d script into USE_RC_SUBR inside
   the Makefile; just put your scripts into WRKDIR during
   the build phase; this will enable your port to survive
   any modifications to the process of installation of
   the rc.d scripts, because they will be handled by the
   ports subsystem;
 - pkg-message can be stripped down as well: first line
   looks redundant, since people already know why they
   had installed the port; the other two lines, perhaps,
   can be condensed into "Read qjail-intro(8) for to get
   started."  The said manual page has reference to the
   qjail(8), so people will know what to do after reading
   the introduction.

And please, please, please, try to put your shar(1) archive somewhere
to the Web and add the link to the PR: mail over gnats if not
uuencoded properly makes attachments with partial quoted-printable
stuff left, so download of, for example,
  http://www.freebsd.org/cgi/query-pr.cgi?prp=148777-3-shar&n=/shar-3.sh
will give a non-working shar(1) archive for starters and when '=0A='
will be removed, one will need to dance with the QP '=' characters,
newlines and alike.


May I also add, your software's manual pages can be improved:
 - don't insert empty lines into the groff files, use the
   lone dot if you want the visual separator inside the
   groff sources;
 - use standard macros like .Pa, .Xr, .Nm, .Qq and others
   instead of doing bold font, quoting and other stuff by hand;
 - avoid unneeded usage of the bold attribute; for example,
   qjail-intro(8) needs no bold for the "4th generation",
   "user friendliness" and other stuff;
 - start each sentense inside the manual source from the
   new line: this will provide two spaces between sentences
   in the formatted manual pages and will ease the diffs
   between revisions of the makefile (for you and other
   developers of the qjail, because this way changes in the
   manual pages will show up in the diff output only inside
   their own sentenses; they won't have the parts of other
   sentences in the + and - lines and that's good);
 - you have many trailing spaces; whilst they typically do
   not harm, why to keep them?


And for the qjail scripts themselves:
 - currently qjail is a single block with no subroutines;
   it _may_ be better to split it into logical parts,
   because it will be easier to read, navigate and understand
   for Other People (TM) ;))
 - perhaps you'll be able to use exit codes from sysexits(3).
 - what does jail2 rc.d script?  It terribly reminds me
   /etc/rc.d/jail and diffing the two one finds mostly
   cosmetic differences.  So, what's the point of having
   jail2 at all?


Sorry for a long letter and slightly mentorish tone: meant
no offense, just wanted to improve the stuff.
--
Eygene Ryabinkin,,,^..^,,,
[ Life's unfair - but root password helps!   | codelabs.ru ]
[ 82FE 06BC D497 C0DE 49EC  4FF0 16AF 9EAE 8152 ECFB | freebsd.org ]


WOW  Eygene Ryabinkin you sure missed the point of my post.
Your forensic investigation of my port is far outside the review of the make
file to commit the port.
So lets get back on task.
Scrubbing through your email content I only see you voicing your personal
preferences without any makefile statement errors, which would make the
Makefile invalid. This is a very simple Makefile so lets not make a mountain
out of a molehill. The port description is within the max size and is very
detailed on purpose. I plan to keep it that way.
The whole point of the post is that I am not a port Mak

FreeBSD Port: mysql-server-5.5.9

2011-03-10 Thread joeb
I have been using mysql since fbsd 7.2 and always just issued the
mysql_install_db command on the command line to create mysql's control
databases and it always worked fine.

But now with fbsd 8.2 I get the following error and have no idea why.
I installed using pkg_add -r mysql55-server command.

I see that 3 weeks ago you updated the mysql55-server port from mysql 554 to
559.
I believe there is an error in your update causing the mysql_install_db
command to error out.
The error message follows.


# /usr/local/bin >mysql_install_db --user=mysql  or
#root >mysql_install_db --user=mysql


FATAL ERROR: Could not find ./bin/my_print_defaults

If you compiled from source, you need to run 'make install' to
copy the software into the correct location ready for operation.

If you are using a binary release, you must either be at the top
level of the extracted archive, or pass the --basedir option
pointing to that location.
* end of error msg. 


# /usr/local/bin >locate my_print_defaults
/usr/local/bin/my_print_defaults

As you can see the script the error message says it can not find is really
in the same location as
the mysql_install_db script, so it should have found it.

I ended up pointing to the 8.1 packages with the pkg-add command to install
and then
the mysql-server5.5.4  mysql_install_db command ran from the command line
without any errors.


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


RE: FreeBSD Port: mysql-server-5.5.9

2011-03-10 Thread joeb
Tried that with on results.

-Original Message-
From: Chuck Swiger [mailto:cswi...@mac.com]
Sent: Thursday, March 10, 2011 3:26 PM
To: j...@a1poweruser.com
Cc: FreeBSD Ports Mailing List
Subject: Re: FreeBSD Port: mysql-server-5.5.9

On Mar 10, 2011, at 11:37 AM, joeb wrote:
> FATAL ERROR: Could not find ./bin/my_print_defaults

Does running rehash in your shell help it find the binary?  Or does
using --basedir /usr/local/bin help?

Regards,
--
-Chuck

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


RE: FreeBSD Port: mysql-server-5.5.9

2011-03-11 Thread joeb


-Original Message-
From: Alex Dupre [mailto:a...@freebsd.org]
Sent: Friday, March 11, 2011 3:43 AM
To: j...@a1poweruser.com
Cc: po...@freebsd.org
Subject: Re: FreeBSD Port: mysql-server-5.5.9

joeb ha scritto:
> If you are using a binary release, you must either be at the top
> level of the extracted archive, or pass the --basedir option
> pointing to that location.

You should use the rc.d script, or pass --basedir=/usr/local

--
Alex Dupre

You need to re-read the original post. 
You have missed the meaning of the problem.
Some testing on your part to reproduce the problem is required.
 

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


RE: FreeBSD Port: gtkyahoo-0.18.3_4

2008-10-24 Thread joeb
I installed the package of pidgin and it install pidgin 2.2.2. Even though
pidgin-2.5.2 is in the ports system the package in out of date.  Can the
package be updated for 7.1 release?

-Original Message-
From: Tim Clewlow [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 23, 2008 8:18 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: FreeBSD Port: gtkyahoo-0.18.3_4


> I installed the package of this port.
> Did a rehash from the command line and then startx.
> Can't find it in the gnome desktop.
> What should I do?

The sourceforge page for this project says "GTKyahoo project was
closed down on February 27, 2003." http://gtkyahoo.sourceforge.net/
You may have a much easier time installing something that is being
currently maintained. I believe net-im/pidgin is quite popular and
is actively maintained. Pidgin is a messenger client, and it can
handle quite a few protocols, including yahoo.

Cheers, Tim.

--
The code that never executes at all is the fastest.

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


RE: FreeBSD Port: kdenetwork-kopete-0.12.8

2008-10-26 Thread joeb




On Sun 2008-10-26 18:17:48 UTC+0800, FBSD1 ([EMAIL PROTECTED]) wrote:

> This returns no sources found.
> What is the current status of this port/package?
>
> http://www.freebsd.org/cgi/pds.cgi?ports/net-im/kopete

Are you saying the download fails?  It looks fine to me.

$ cd /usr/ports/net-im/kopete
$ sudo make fetch
===>  Vulnerability check disabled, database not found
=> kdenetwork-3.5.10.tar.bz2 doesn't seem to exist in
/usr/ports/distfiles/KDE.
=> Attempting to fetch from
http://mirrors.isc.org/pub/kde/stable/3.5.10/src/.
kdenetwork-3.5.10.tar.bz2  12% of 9117 kB  255 kBps
-Original Message-
From: andrew clarke [mailto:[EMAIL PROTECTED]
Sent: Sunday, October 26, 2008 6:35 PM
To: FBSD1
Cc: [EMAIL PROTECTED]
Subject: Re: FreeBSD Port: kdenetwork-kopete-0.12.8
No what I am saying is when I go to that link it replies with no sources
found.


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


RE: ports missing their packages.

2008-10-29 Thread joeb
On Wed, October 29, 2008 9:09 am, FBSD1 wrote:
> It's my understanding that a port maintainer has to install the port for
> real any time a change is made to the port make files or a update to the
> source of the software to test and verify the changes work as wanted.
> Creating the package after this is just one command and a ftp upload to
> the
> package server. Why are maintainers being given approval to apply their
> changes without creating the required package? This is just lax management
> on the part of the people who do the authorizing of the changes. Missing
> packages increases user frustration level and makes FreeBSD look like its
> being mis-managed.
>
> An alternate solution to this problem is to allow users to upload missing
> packages to the package server direct or to a staging ftp server so
> port/pkg
> management staff can review first and them populate the production package
> server.
>

There is a certain guideline in place which committers follow. If you have
constructive feedback surely someone will listen to it. Spitting your
frustration is not likely to help. Do note that we have a lot of
maintainers which try to satify each and everyone of us, sending messages
like this is not going to help *you*.

I would have a strong opinion -against- people uploading towarsd the FTP
server directly. That will not be done. .

To give you a better understanding; We have a ports-cluster which builds
packages and uploads them to the appropriate place on the FTP servers,
sometimes that takes a little to become available, donate more facilities
so that we can do that better. Also note that QAT (a ports tinderbox) runs
periodically to make sure every thing is just fine!

Thanks,
Remko

--
/"\   Best regards,  | [EMAIL PROTECTED]
\ /   Remko Lodder   | [EMAIL PROTECTED]
 Xhttp://www.evilcoder.org/  |
/ \   ASCII Ribbon Campaign  | Against HTML Mail and News


-Original Message-
From: Remko Lodder [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 29, 2008 4:17 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED] ORG; [EMAIL PROTECTED]
Subject: Re: ports missing their packages.


Well if you have this cluster build process why have some ports never been
built all the way back to release 5.0 like kdenetwork-kopete-0.12.8. That is
almost 3 years of waiting to get in the cluster build process. I am grateful
to the maintainers for the great job they do, but completing the job by
building the package is such a small additional task in light of they
already have everything in place to build the package.
Posting a email to [EMAIL PROTECTED] or posting a bug report about package
missing does not get the missing package built. Its just considered as
background noise. I have brought this problem to light in past years and new
releases keep coming out with the same packages missing.





___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


RE: ports missing their packages.

2008-10-29 Thread joeb


-Original Message-
From: Erik Trulsson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 29, 2008 4:47 PM
To: FBSD1
Cc: [EMAIL PROTECTED] ORG; [EMAIL PROTECTED]
Subject: Re: ports missing their packages.

On Wed, Oct 29, 2008 at 04:09:23PM +0800, FBSD1 wrote:
> It's my understanding that a port maintainer has to install the port for
> real any time a change is made to the port make files or a update to the
> source of the software to test and verify the changes work as wanted.
> Creating the package after this is just one command and a ftp upload to
the
> package server. Why are maintainers being given approval to apply their
> changes without creating the required package? This is just lax management
> on the part of the people who do the authorizing of the changes. Missing
> packages increases user frustration level and makes FreeBSD look like its
> being mis-managed.

It is not port managers who create or upload packages.  Most of them do not
even have access to the package server.
The downloadable packages are built and uploaded automatically by a cluster
of servers that do little else.

If a particular port does not have a corresponding package it is generally
not due to laxness on anybodys part.

The main reasons why a port might not have corresponding package are:

1) The port has just been created and the package hasn't had time to built
   yet.  Normally a very temporary situation.

2) Legal restrictions.  There are several ports where it is simply not legal
   for the FreeBSD project to distribute the corresponding binary packages.

3) The port is currently broken and cannot be built. (This is of course a
   bug which should be fixed as soon as possible.  For ports without a
   maintainer that might take a while.)

4) One or more of the dependencies of the package is not available as a
   package.  (If port A depends on port B, and there does not exist a
   package for B (for any of the reasons listed here) there will not be
   a package of A either.



>
> An alternate solution to this problem is to allow users to upload missing
> packages to the package server direct or to a staging ftp server so
port/pkg
> management staff can review first and them populate the production package
> server.

All the packages that can be built and distributed are already being built
and uploaded.  Allowing users to upload packages would not help.



--

Erik Trulsson
[EMAIL PROTECTED]



-Original Message-
From: Erik Trulsson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 29, 2008 4:47 PM
To: FBSD1
Cc: [EMAIL PROTECTED] ORG; [EMAIL PROTECTED]
Subject: Re: ports missing their packages.
How does kdenetwork-kopete-0.12.8 or php5-gd or pdflib fit into those
reasons you gave?
These all have ports but no package for many releases of Freebsd.

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"