Re: a little confuse with case-sensitive name ports and multiple ports with some name
And i forget to say for one else problem with {archivers,mis}/deco:
both of them produced one binary file in /usr/local/bin/deco.
cd /usr/ports/archivers/deco
make install
...
(i have deco archivers)
pkg_add -r deco
(deco/NC-clone replace /usr/local/bin/deco)
pkg_which /usr/local/bin/deco
[Updating the pkgdb in /var/db/pkg ... - 718 packages found
(-1 +1) (...). done]
deco-3.9_4 deco-1.6
pkg_delete -f deco-3.9\*
..
On Thursday 16 April 2009 20:16:25 Oleg Ginzburg wrote:
> On Thursday 16 April 2009 19:52:38 Chris Rees wrote:
> > 2009/4/16 Oleg Ginzburg :
> > > Hello maillist!
> > >
> > > I have two examples of ports with which arises some complexities by
> > > operation with pkg_add and argument "-r".
> > >
> > > One of ports is "security/keepassx". His name is registered in
> > > lowercase, however at installation in/var/db/pkg is registered as
> > > KeepAssX. If to try to install port with pkg_add -r keepassx it will be
> > > fail and it will be correct with pkg_add -r KeepAssX. Probably it is
> > > an error in naming of port?
> > >
> > > One more problem with port - deco. It is present at two locations:
> > >
> > > % cat /usr/ports/{archivers,misc}/deco/pkg-descr
> > > Deco is a Un*x script able to extract various archive file formats.
> > > Supported archive formats: 7z, ace, ar, arc, arj, bz2, cab, cpio, deb,
> > > flac, gz, jar, lha, lzma, lzo, rar, rpm, tar, zip, zoo.
> > >
> > > WWW: http://hartlich.com/deco/
> > > A clone of Norton Commander for Unix. Text-based,
> > > full featured file manager intuitive interface.
> > >
> > > WWW: http://deco.sourceforge.net/
> > >
> > > Whether there is a way to specify to what category to me it is required
> > > to download package of "deco"?
> > >
> > > whereis -sq deco
> > > /usr/ports/archivers/deco - its archivers
> > >
> > > By command pkg_add -r deco - I've receive in the system fine NC-clone,
> > > but not the archivers.
> > >
> > > When number of port with equal name will be increase - expected results
> > > may can not coincide with result pkg_add, and case-sensitive naming
> > > port make works a bit difficult .
> > >
> > >
> > > ___
> > > 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"
> >
> > Try appending the version number?
>
> Do you mean pkg_add -r deco-N.M (in my example?)
>
> % pkg_add -r deco-3.9_4
> Error: FTP Unable to get
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-
> current/Latest/deco-3.9_4.tbz: File unavailable (e.g., file not found, no
> access)
> pkg_add: unable to fetch
> 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-
> current/Latest/deco-3.9_4.tbz' by URL
>
> [r...@oleg lftp]# lftp
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-current/Latest/
> cd ok, cwd=/pub/FreeBSD/ports/i386/packages-8-current/Latest
> lftp ftp.freebsd.org:/pub/FreeBSD/ports/i386/packages-8-current/Latest> ls
> | grep deco-3.9
> lrwxr-xr-x 1 1006 1006 21 Feb 22 01:30 deco.tbz -> ../All/deco-3.9_4.tbz
>
> - on ftp servers packages without version as i see.
>
> Anyway, its not protect in situation with equal name and equal version of
> diffrent ports.
>
> > Or use portinstall -PP archivers/deco
>
> Ok, this may be solution. BTW, portinstall still not in FreeBSD base system
> ;)
>
> > Chris
>
> ___
> 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-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: a little confuse with case-sensitive name ports and multiple ports with same name
On Friday 17 April 2009 14:09:51 Miroslav Lachman wrote:
> Oleg Ginzburg wrote:
> > And i forget to say for one else problem with {archivers,mis}/deco:
> > both of them produced one binary file in /usr/local/bin/deco.
> >
> > cd /usr/ports/archivers/deco
> > make install
> > ...
> > (i have deco archivers)
> > pkg_add -r deco
> >
> > (deco/NC-clone replace /usr/local/bin/deco)
> >
> > pkg_which /usr/local/bin/deco
> > [Updating the pkgdb in /var/db/pkg ... - 718 packages
> > found (-1 +1) (...). done]
> > deco-3.9_4 deco-1.6
> >
> > pkg_delete -f deco-3.9\*
>
> Can you open a PR for this problem? I think it is really bad. If two
> ports are installing same files, then there must be set CONFLICTS in
> Makefile.
Ok.
>
> The next thing is that I think there should not be the two ports with
> the same name.
IMHO, soon or later, problems like that will be surface is frequency . More
so, a package numbers is increase day by day. May be location like
/usr/local/bin/* most certainly controlling by some stuff through
analyzing/scanning pkg-plist files for stop potential collision?
>
> Miroslav Lachman
___
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"
DCC permission question
Hello. I'm using MIMEDefang -> SpamAssassin -> DCC & Razor. Lately I started seeing a lot of messages like the following in my logs: dccproc[54019]: /usr/local/dcc: Permission denied These are all the concerned permissions (as per default port install, I guess, since I didn't change them manually). #ls -l /usr/local/|grep dcc drwxr-xr-x5 root wheel 512 Apr 2 14:35 dcc # ls -l /usr/local/dcc/ total 78 drwxr-xr-x 2 dcc wheel 512 Apr 2 14:35 cgi-bin -rw-r--r-- 1 dcc wheel 5482 Apr 2 14:35 dcc_conf -rw-r--r-- 1 dcc wheel 5482 Apr 2 14:35 dcc_conf.sample -rw-r--r-- 1 dcc wheel 797 Apr 2 14:35 flod -rw-r--r-- 1 dcc wheel 797 Apr 2 14:35 flod.sample -rw-r--r-- 1 dcc wheel 427 Apr 2 14:35 grey_flod -rw-r--r-- 1 dcc wheel 427 Apr 2 14:35 grey_flod.sample -rw-r--r-- 1 dcc wheel 496 Apr 2 14:35 grey_whitelist -rw-r--r-- 1 dcc wheel 496 Apr 2 14:35 grey_whitelist.sample -rw--- 1 dcc wheel 2433 Apr 2 14:35 ids -rw--- 1 dcc wheel 2433 Apr 2 14:35 ids.sample drwxr-xr-x 2 dcc wheel 1024 Apr 2 14:35 libexec drwx--x--- 2 dcc wheel 512 Apr 2 14:35 log -rw--- 1 dcc wheel 7564 Apr 17 09:47 map -rw--- 1 dcc wheel 7564 Apr 2 14:35 map.sample -rw--- 1 dcc wheel 405 Apr 2 14:35 map.txt -rw--- 1 dcc wheel 405 Apr 2 14:35 map.txt.sample -rw-r--r-- 1 dcc wheel 4138 Apr 2 14:35 whiteclnt -rw-r--r-- 1 dcc wheel 4138 Apr 2 14:35 whiteclnt.sample -rw-r--r-- 1 dcc wheel 1667 Apr 2 14:35 whitecommon -rw-r--r-- 1 dcc wheel 1667 Apr 2 14:35 whitecommon.sample -rw-r--r-- 1 dcc wheel 864 Apr 2 14:35 whitelist -rw-r--r-- 1 dcc wheel 864 Apr 2 14:35 whitelist.sample # ls -l /usr/local/bin/dccproc -r-sr-xr-x 1 dcc wheel 435522 Apr 2 14:35 /usr/local/bin/dccproc Any hint? Does dccproc need to write in /usr/local/dcc/? Also, I get: mimedefang-multiplexor[94437]: Slave 1 stderr: pyzor: check failed: internal error Any hint on how to start debugging this? bye & Thanks av. ___ 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: mythtv 0.21 - trouble compiling the port
On Thu, 16 Apr 2009 18:23:27 -0400 Greg Larkin wrote: > Bernhard Fröhlich wrote: > > On Mon, April 13, 2009 8:34 pm, Torfinn Ingolfsen wrote: > >> Hello, > >> > >> 2009/4/13 Bernhard Fröhlich : > >>> Here are the patches that i've needed to get both ports working again. > >>> > >>> > >>> multimedia/mythtv: > >>> > >>> http://home.bluelife.at/ports/mythtv/patch-libs-libmyth-libmyth.pro > >>> http://home.bluelife.at/ports/mythtv/patch-programs-mythtranscode-mythtranscode.pro > >> On a freshly updated ports tree and with those two patches, I still > >> get this error: > >> g++ -c -pipe -march=k8 -fomit-frame-pointer -O3 -g -Wall -Wno-switch > >> -Wpointer-arith -Wredundant-decls -Wno-non-virtual-dtor > >> -D__STDC_CONSTANT_MACROS -I/usr/local/include/artsc -D_REENTRANT > >> [snip] > > > > Looks like another missing patch. Now i've double checked with your list > > and this is the last missing one. (also taken from mythtv-frontend) > > > > http://home.bluelife.at/ports/mythtv/patch-libs-libmythtv-libmythtv.pro > > > > > >>> multimedia/mythtv-frontend: > >>> > >>> http://home.bluelife.at/ports/mythtv/patch-libs-libmyth-libmyth.pro > >> But 'make' in mythtv-frontend works with this patch (completes without > >> errors), on the same machine. > Thanks very much for all of the work organizing the patches. The ports > tree is frozen right now, but once it thaws, I'll commit these changes. Well, but patches that recover ports are accepted. This is the main goal of ports freezing. Just ask an approval from port...@. WBR -- bsam ___ 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: a little confuse with case-sensitive name ports and multiple ports with some name
2009/4/17 Oleg Ginzburg :
> And i forget to say for one else problem with {archivers,mis}/deco:
> both of them produced one binary file in /usr/local/bin/deco.
>
> cd /usr/ports/archivers/deco
> make install
> ...
> (i have deco archivers)
> pkg_add -r deco
>
> (deco/NC-clone replace /usr/local/bin/deco)
>
> pkg_which /usr/local/bin/deco
> [Updating the pkgdb in /var/db/pkg ... - 718 packages found
> (-1 +1) (...). done]
> deco-3.9_4 deco-1.6
>
> pkg_delete -f deco-3.9\*
>
> ..
>
OK, that's seriously annoying. That can't possibly be by design
By the way, please don't top-post
http://www.freebsd.org/doc/en/articles/mailing-list-faq/etiquette.html
Chris
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
___
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: a little confuse with case-sensitive name ports and multiple ports with same name
Oleg Ginzburg wrote:
And i forget to say for one else problem with {archivers,mis}/deco:
both of them produced one binary file in /usr/local/bin/deco.
cd /usr/ports/archivers/deco
make install
...
(i have deco archivers)
pkg_add -r deco
(deco/NC-clone replace /usr/local/bin/deco)
pkg_which /usr/local/bin/deco
[Updating the pkgdb in /var/db/pkg ... - 718 packages found
(-1 +1) (...). done]
deco-3.9_4 deco-1.6
pkg_delete -f deco-3.9\*
Can you open a PR for this problem? I think it is really bad. If two
ports are installing same files, then there must be set CONFLICTS in
Makefile.
The next thing is that I think there should not be the two ports with
the same name.
Miroslav Lachman
___
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: a little confuse with case-sensitive name ports and multiple ports with some name
On Fri, Apr 17, 2009 at 10:45:46AM +0100, Chris Rees wrote:
> 2009/4/17 Oleg Ginzburg :
> > And i forget to say for one else problem with {archivers,mis}/deco:
> > both of them produced one binary file in /usr/local/bin/deco.
> >
> > cd /usr/ports/archivers/deco
> > make install
> > ...
> > (i have deco archivers)
> > pkg_add -r deco
> >
> > (deco/NC-clone replace /usr/local/bin/deco)
> >
> > ?pkg_which /usr/local/bin/deco
> > [Updating the pkgdb in /var/db/pkg ... - 718 packages
> > found
> > (-1 +1) (...). done]
> > deco-3.9_4 deco-1.6
> >
> > pkg_delete -f deco-3.9\*
> >
> > ..
> >
>
> OK, that's seriously annoying. That can't possibly be by design
It is because misc/deco is not marked as having a conflict with
archivers/deco, but archivers/deco does have a conflict with misc/deco
recorded. If you were to install misc/deco before archivers/deco the
situation would become obvious.
One of the two should probably change their pkgname so that pkg_add -r
can properly find it. Right now pkg_add appears to get misc/deco, even
if you want archivers/deco.
Opening a PR for both these is likely the next best step.
-- WXS
___
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"
freetype vulnerabilities
There were some pretty serious vulnerabilities found in freetype: http://secunia.com/advisories/34723/ I think we need to fix these before the tag. There's the patch: https://bugzilla.redhat.com/show_bug.cgi?id=491384 -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ 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: ports/132800: vuxml submission for net-im/ejabberd
I'm following up regarding this apparent maintainer timeout. It's not my intention to place blame, but to me it is unacceptable that important security (vuxml) updates are sometimes blocked by unresponsive maintainers. It is not in the best interest of the users or FreeBSD to let these things slip. The vuxml updates should be reviewed & committed without waiting on the maintainer of the port. Perhaps a simple non-blocking heads-up (Cc:) to the maintainer is more appropriate. Once publicized, the security notifications (via portaudit) become known to a wider, targetted audience. This establishes an important feedback loop as opposed to keeping the problem a "secret", since the users are more likely to either nudge the maintainer for an update to the port or submit one (via send-pr) themselves. -- I hate rascists. Mark D. Foster http://mark.foster.cc/ | http://conshell.net/ ___ 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: ports/132800: vuxml submission for net-im/ejabberd
On Fri, Apr 17, 2009 at 08:38:12AM -0700, Mark Foster wrote: > I'm following up regarding this apparent maintainer timeout. It's not my > intention to place blame, but to me it is unacceptable that important > security (vuxml) updates are sometimes blocked by unresponsive > maintainers. It is not in the best interest of the users or FreeBSD to > let these things slip. Agreed. This one managed to slip through the cracks. Sorry about that. > The vuxml updates should be reviewed & committed without waiting on the > maintainer of the port. Perhaps a simple non-blocking heads-up (Cc:) to > the maintainer is more appropriate. Once publicized, the security > notifications (via portaudit) become known to a wider, targetted > audience. This establishes an important feedback loop as opposed to > keeping the problem a "secret", since the users are more likely to > either nudge the maintainer for an update to the port or submit one (via > send-pr) themselves. I agree. VuXML submissions should be committed promptly. I'll work this one now and get it in the tree. Again, sorry for the delay. -- WXS ___ 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: mythtv 0.21 - trouble compiling the port
Hi, 2009/4/17 Greg Larkin : > Would you mind applying this small patch to mythtv/files/pkg-install.in? > > http://people.freebsd.org/~glarkin/diffs/mythtv-pkg-install.in.diff Not at all. :-) > Since the "Unable to start mysqld" message is emitted in two different > places, I'd like to know which one you are getting. I think that the > spurious error might be caused by checking for the process existence too > quickly, but I could be wrong. > > If you have a chance to re-install the port, let me know which message > appears now when it attempts to start mysqld. Here goes: Added group "mythtv". Added user "mythtv". Starting mysql. 2: *** Unable to start mysqld *** Error code 1 Stop in /usr/ports/multimedia/mythtv. *** Error code 1 Stop in /usr/ports/multimedia/mythtv. HTH, Have a nice weekend, everybody! -- Regards, Torfinn ___ 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"
Unable to get MAN pages installed
I am in the process of creating a new port. I cannot seem to get the
'man' file installed correctly; however. This is the error message at
the end of the install process. The file 'scamp.1' exists in the $WRKSRC
directory when I extract the distro.
===> Compressing manual pages for scamp-5.2a
gzip: can't stat: /usr/local/man/man1/scamp.1: No such file or directory
===> Registering installation for scamp-5.2a
This is the Makefile for the port. It will probably wrap incorrectly!
# New ports collection makefile for:scamp
# Date created: 31 March 2009
# Whom: Gerard Seibert
#
# $FreeBSD$
PORTNAME= scamp
PORTVERSION=5.2a
CATEGORIES= security
MASTER_SITES= http://site1/ ${MASTER_SITE_SOURCEFORGE:S/$/:sourceforge,TEST/}
DISTFILES= scamp/scamp-5.2a.tar.gz:sourceforge
MAINTAINER= ger...@seibercom.net
COMMENT=Download & Install additional definition files for Clamav
.include
.if exists (${LOCALBASE}/bin/wget) && ! exists (${LOCALBASE}/bin/curl)
RUN_DEPENDS+= wget>=1.11.4:${PORTSDIR}/ftp/wget \
bash>=3.2.48_1:${PORTSDIR}/shells/bash3 \
clamav>=0.95:${PORTSDIR}/security/clamav \
gnupg>=2.0.11:${PORTSDIR}/security/gnupg \
rsync>=3.0.5:${PORTSDIR}/net/rsync
.else
RUN_DEPENDS+= curl>=7.19.2:${PORTSDIR}/ftp/curl \
bash>=3.2.48_1:${PORTSDIR}/shells/bash3 \
clamav>=0.95:${PORTSDIR}/security/clamav \
gnupg>=2.0.11:${PORTSDIR}/security/gnupg \
rsync>=3.0.5:${PORTSDIR}/net/rsync
.endif
NO_BUILD= yes
SUB_FILES= pkg-message
MAN1= scamp.1
MANCOMPRESS=no
post-patch:
@${REINPLACE_CMD} -e
's|SIG_DB=$${SIG_DB:-""}|SIG_DB=$${SIG_DB:-"/var/db/clamav"}|g'
${WRKSRC}/${PORTNAME}.sh
@${REINPLACE_CMD} -e
's|CONFIG_DIR="/etc/scamp"|CONFIG_DIR="/usr/local/etc/scamp"|g'
${WRKSRC}/${PORTNAME}.sh
post-install:
@${INSTALL_DATA} ${FILESDIR}/scamp.conf.sample ${PREFIX}/etc/
@if [ ! -f ${PREFIX}/etc/scamp.conf ]; then \
${CP} -p ${PREFIX}/etc/scamp.conf.sample \
${PREFIX}/etc/scamp.conf ; \
fi
do-install:
cd ${WRKSRC} && ${INSTALL_SCRIPT} ${PORTNAME}.sh ${PREFIX}/bin
.ifndef(NOPORTDOCS)
@${MKDIR} ${DOCSDIR}
cd ${WRKSRC} && ${INSTALL_DATA} README CHANGE.LOG INSTALL Release.html
${DOCSDIR}
.endif
${CAT} ${PKGMESSAGE}
.include
Obviously, I am doing something wrong; I just cannot find it. A scan
with 'portlint -A' did not turn up a single error on the port.
I assume I am giving it the wrong PATH; however, I do not know how
to correct it.
--
Jerry
ges...@yahoo.com
Blessed is he who expects nothing, for he shall never be disappointed.
Alexander Pope
___
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"
