Re: NEW: libmpd and gmpc
Here are two ports for gmpc and libmpd (required by gmpc). gmpc is a graphical MPD client which interfaces all features of MPD. Coming up is a gmpccaa port (works for me but needs more tweaking) which allows the client to query and display cover art from cover art servers. Tested on i386 and amd64 The files are available here if the attachment gets removed Did anyone try these out ? gmpc.tgz Description: Binary data libmpd.tgz Description: Binary data
Re: UPDATE: jpilot-0.99.9
On Tue, 19 Sep 2006, Antoine Jacoutot wrote:
This is an update to bring jpilot to the latest stable version.
This port was made against pilot-link-0.12.1 which I sent an updated port for
yesterday (or a couple days ago).
New port with better code for first day of the week ; from jpilot CVS.
See http://bugs.jpilot.org/1722
Works fine with the updated pilot-link-0.12.1 I sent a week ago.
--
Antoinediff -ruN --exclude CVS /usr/ports/comms/jpilot/Makefile jpilot/Makefile
--- /usr/ports/comms/jpilot/MakefileMon Sep 18 19:07:31 2006
+++ jpilot/Makefile Wed Sep 27 09:33:58 2006
@@ -1,9 +1,8 @@
-# $OpenBSD: Makefile,v 1.36 2006/09/18 11:40:07 espie Exp $
+# $OpenBSD: Makefile,v 1.35 2006/08/01 22:19:46 espie Exp $
COMMENT= desktop organizer software for the palm pilot
-DISTNAME= jpilot-0.99.8
-PKGNAME= ${DISTNAME}p3
+DISTNAME= jpilot-0.99.9
CATEGORIES=comms palm
MASTER_SITES= ${HOMEPAGE}
@@ -18,14 +17,14 @@
PERMIT_DISTFILES_CDROM=Yes
PERMIT_DISTFILES_FTP= Yes
-WANTLIB= c readline crypto m ncurses X11 Xext \
- Xrender fontconfig freetype atk-1.0.=800.0 \
- gdk_pixbuf-2.0.=400.14 glib-2.0.=400.8 gmodule-2.0.=400.8 \
- gobject-2.0.=400.8 pango-1.0.=600.0 pangoft2-1.0.=600.0 \
- pangocairo-1.0 cairo glitz png z
+WANTLIB= c crypto m X11 Xext Xrender pthread fontconfig \
+ freetype atk-1.0.=800.0 gdk_pixbuf-2.0.=400.14 \
+ glib-2.0.=400.8 gmodule-2.0.=400.8 usb.=8 \
+ gobject-2.0.=400.8 pango-1.0.=600.0 \
+ pangoft2-1.0.=600.0 pangocairo-1.0 cairo glitz png z
BUILD_DEPENDS= :pkgconfig-*:devel/pkgconfig
-LIB_DEPENDS= pisock.=8::comms/pilot-link \
+LIB_DEPENDS= pisock.=9::comms/pilot-link \
gtk-x11-2.0.=400.13,gdk-x11-2.0.=400.13,gdk_pixbuf-2.0.=400.13::x11/gtk+2
MODULES= devel/gettext
@@ -37,11 +36,10 @@
CONFIGURE_ENV= CPPFLAGS=-I${LOCALBASE}/include \
LDFLAGS=-L${LOCALBASE}/lib
CONFIGURE_ARGS+= ${CONFIGURE_SHARED} \
- --enable-gtk2 \
--with-pilot-prefix=${LOCALBASE} \
--with-gtk-prefix=${LOCALBASE}
-MAN1= jpilot-dump.1 jpilot-sync.1 jpilot-upgrade-99.1 jpilot.1
+MAN1= jpilot-dump.1 jpilot-sync.1 jpilot.1
pre-build:
.for i in ${MAN1}
diff -ruN --exclude CVS /usr/ports/comms/jpilot/distinfo jpilot/distinfo
--- /usr/ports/comms/jpilot/distinfoMon Oct 31 23:47:22 2005
+++ jpilot/distinfo Mon Aug 28 11:13:17 2006
@@ -1,4 +1,4 @@
-MD5 (jpilot-0.99.8.tar.gz) = 4bdb200367e691e64d02bd6dfcdec604
-RMD160 (jpilot-0.99.8.tar.gz) = 9d19e41a8d73f1dbfc5107e0ee1657ac09b55189
-SHA1 (jpilot-0.99.8.tar.gz) = 5ad7c15f4583a15afb7acd96db2c4e8e58311b29
-SIZE (jpilot-0.99.8.tar.gz) = 1589217
+MD5 (jpilot-0.99.9.tar.gz) = c39df29aeed57b84a674524856ebc290
+RMD160 (jpilot-0.99.9.tar.gz) = 0286b9f9579dbbdb8e9bd207384561814bab5114
+SHA1 (jpilot-0.99.9.tar.gz) = 19a76f8815188a1b7993fbff81624e852a3bbc5c
+SIZE (jpilot-0.99.9.tar.gz) = 1671351
diff -ruN --exclude CVS
/usr/ports/comms/jpilot/patches/patch-Expense_Makefile_in
jpilot/patches/patch-Expense_Makefile_in
--- /usr/ports/comms/jpilot/patches/patch-Expense_Makefile_in Mon Oct 31
23:47:22 2005
+++ jpilot/patches/patch-Expense_Makefile_inMon Aug 28 11:21:12 2006
@@ -1,7 +1,7 @@
$OpenBSD: patch-Expense_Makefile_in,v 1.7 2005/10/31 21:08:15 naddy Exp $
Expense/Makefile.in.orig Mon Oct 31 19:48:02 2005
-+++ Expense/Makefile.inMon Oct 31 19:48:19 2005
-@@ -247,7 +247,7 @@ target_alias = @target_alias@
+--- Expense/Makefile.in.orig Thu Aug 24 01:22:09 2006
Expense/Makefile.inMon Aug 28 11:19:49 2006
+@@ -248,7 +248,7 @@ target_alias = @target_alias@
@[EMAIL PROTECTED] = libexpense.la
@[EMAIL PROTECTED] = expense.c
@[EMAIL PROTECTED] = -Wall @PILOT_FLAGS@ @GTK_CFLAGS@ -I$(top_srcdir)
diff -ruN --exclude CVS
/usr/ports/comms/jpilot/patches/patch-KeyRing_Makefile_in
jpilot/patches/patch-KeyRing_Makefile_in
--- /usr/ports/comms/jpilot/patches/patch-KeyRing_Makefile_in Mon Oct 31
23:47:22 2005
+++ jpilot/patches/patch-KeyRing_Makefile_inMon Aug 28 11:21:12 2006
@@ -1,7 +1,7 @@
$OpenBSD: patch-KeyRing_Makefile_in,v 1.3 2005/10/31 21:08:15 naddy Exp $
KeyRing/Makefile.in.orig Mon Oct 31 19:47:32 2005
-+++ KeyRing/Makefile.inMon Oct 31 19:47:50 2005
-@@ -248,7 +248,7 @@ EXTRA_DIST = README.txt
+--- KeyRing/Makefile.in.orig Thu Aug 24 01:22:09 2006
KeyRing/Makefile.inMon Aug 28 11:19:49 2006
+@@ -249,7 +249,7 @@ EXTRA_DIST = README.txt
@[EMAIL PROTECTED] = libkeyring.la
@[EMAIL PROTECTED] = keyring.c
@[EMAIL PROTECTED] = -Wall @PILOT_FLAGS@ @GTK_CFLAGS@ -I$(top_srcdir)
diff -ruN --exclude CVS
/usr/ports/comms/jpilot/patches/patch-SyncTime_Makefile_in
jpilot/patches/patch-SyncTime_Makefile_in
--- /usr/ports/comms/jpilot/patches/patch-SyncTime_Makefile_in Mon Oct 31
23:47:22
Re: milter-regex woes
On Wed 2006.09.27 at 14:49 +1000, Christopher Martin wrote: I am trying to use milter-regex to pre-sort e-mail/spam before passing it on to clamav and spamassassin, but it doesn't seem to be working. Here are my first, slightly lame, rules: reject Spam not welcome header /Subject:/ /\b(PHA)+([a-zA-Z]+(RMA))\b/ reject Spam not welcome header /Subject:/ /\b(PHA)+([a-zA-Z]+(RMACY))\b/ discard header /Subject:/ /TESTSTRING45819203/ I have tried sending mails with the test string (TESTSTRING45819203) but they get through. Are my rules wrong? I am very much a regex newbie, so I suspect my rules are wrong, but I need someone's help! have you enabled the milter in sendmail? you can also watch syslog and see exactly what milter-regex is doing.
Re: [new] silc-plugin for irssi
Hi, I have at least one report of it not working on amd64, where silc-client-1.0.2 does work. Can anyone confirm/deny it? Works perfect on almost fresh OpenBSD install on amd64! Also, consider uncommenting :automake-1.9*:devel/automake/1.9 in BUILD_DEPENDS, otherwise it won't build. Martynas Venckus
Re: [new] silc-plugin for irssi
On 9/27/06, Martynas Venckus [EMAIL PROTECTED] wrote: Hi, I have at least one report of it not working on amd64, where silc-client-1.0.2 does work. Can anyone confirm/deny it? Works perfect on almost fresh OpenBSD install on amd64! Also, consider uncommenting :automake-1.9*:devel/automake/1.9 in BUILD_DEPENDS, otherwise it won't build. Martynas Venckus Done. I thought autoconf would pull automake in, but I apparently misread. Also added commented out dependancy on silc-toolkit, which might be fixing issues on amd64 - if they are there indeed. -- viq irssi-silc-port.tar.gz Description: GNU Zip compressed data
Re: Question about courier-imap and maildrop
While the facts you state are correct, the suggestion that the Courier-IMAP in tree is vulnerable is not. The vulnerabilities you state are either fixed in 3.0.5 or not relevant; see the Changelog at http:/www.courier-mta.org/imap. Indeed, I took a closer look at those vulnerabilities and they mention the affected version being 3.0.2 and older. Though in the changelog there are a few things that sound like bugfixes, or at least let's make it work better, that probably make it worth considering bumping it to 3.0.8. But then again, possibly not ;) Alek, you got an update to 4.1.1 before 4.0 right?
pkg_dig - sh(1) script
pkg_dig is a small sh(1) script that extracts useful information from
installed packages. The reason I decided to implement a script like this
was to provide a missing feature of pkg_delete(1). Let me give you an
example:
Let's say we have 2 packages, Y and Z.
Package: Y
Dependencies: A, B, C
Package: Z
Dependencies: C, D, E
If we decide to install package Y, pkg_add(1) will install A, B and C as
dependencies. If we want to remove this package later on, pkg_delete(1)
will remove only Y leaving A, B and C installed. Let's expand this a
bit.
If we install Y, along with A, B and C as dependencies. Now, let's say
we install Z also. Thus, D and E will be installed additionally as
dependencies. C is already installed as a dependency of Y. At some point
we decide to remove Y. pkg_delete(1) should remove Y, A and B, leaving C
installed as a dependency for Z. Instead, pkg_delete(1) will remove only
Y, leaving A and B as orphan packages. This is of course inefficient and
undesired.
Here is where pkg_dig comes into play. Using the information stored in
/var/db/pkg it will find which of the dependencies of a package can be
safely removed along with the package. Here is a sample output:
[EMAIL PROTECTED] msid $ pkg_dig xpdf
*- Package matched: xpdf-3.01p1
|- Dependencies: ghostscript-fonts-6.0p0 t1lib-5.1.0p0 openmotif-2.1.30.5p1
|- Required by: none
|- You may also delete: openmotif-2.1.30.5p1
[EMAIL PROTECTED] msid $
You may define multiple packages as well. That's all more or less. I
would love to receive feedback on this from whoever is willing to try
it. I know it cannot be merged with pkg_delete(1) in its current form
since the latter is coded in Perl, but, I was merely trying to present a
feature that I consider to be useful. Probably someone more proficient
in Perl than myself can easily implement this feature and merge it with
pkg_delete(1) as an -F option for example. If you find this useless, I
apologize for the noise. You can grab the latest version from:
http://black.daemons.gr/msid/scripts/pkg_dig
--
Sideris Michael
http://black.daemons.gr/msid/
#!/bin/sh
# Copyright (c) 2006, Sideris Michael
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above copyright
# notice, this list of conditions and the following disclaimer in the
# documentation and/or other materials provided with the
# distribution.
# * Neither the name of the author nor the names of its
# contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS
# IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
# TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
# PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
if [ $# -eq 0 ]
then
echo Usage: `echo $0 |sed 's/^\.\///'` [pkg_name ...]
exit 0
fi
echo
for arg in $*
do
if [ true ]
then
pkgdb=/var/db/pkg
pkgname=
search=
counter=0
if [ ! -d $pkgdb ]
then
exit 1
fi
cd $pkgdb
if [ -d $arg ]
then
pkgname=$arg
counter=1
else
search=`find . -maxdepth 1 -type d -name $arg* | sort
| sed 's/^\.\///'`
for x in $search
do
if [ $arg == `echo $x | sed -e 's/^\.\///' -e
's/-[0-9].*//'` ]
then
counter=`expr $counter+1 |bc`
pkgname=${pkgname}\ $x
fi
done
fi
if [ $counter -eq 0 ]
then
echo * No package found: $arg
elif [ $counter -gt 1 ]
then
echo \* Ambiguous: $arg could be `echo $pkgname |sed
's/ /\ or\ /'`
Re: pkg_dig - sh(1) script
Here's a variation on the theme that serves me well.
#!/bin/sh
#
# pkg_nuke - delete unneeded packages
#
# Usage:
# pkg_info wanted
# vi wanted # keep only the lines you want
# pkg_nuke wanted
#
# All packages will be deleted, except the
# wanted packages and their dependencies.
#
[ $# -ne 1 ] exit 1
field1 () { awk '{print $1}'; }
wanted=`mktemp -t`
field1 $1 | sort $wanted
a=0
while true; do
b=`pkg_info | wc -l`
[ $a -eq $b ] break
a=$b
incidental=`pkg_info | field1 | sort | comm -2 -3 - $wanted`
for x in $incidental; do pkg_delete $x; done
done
rm $wanted
Re: milter-regex woes
Okan Demirmen wrote: On Wed 2006.09.27 at 14:49 +1000, Christopher Martin wrote: I am trying to use milter-regex to pre-sort e-mail/spam before passing it on to clamav and spamassassin, but it doesn't seem to be working. Here are my first, slightly lame, rules: reject Spam not welcome header /Subject:/ /\b(PHA)+([a-zA-Z]+(RMA))\b/ reject Spam not welcome header /Subject:/ /\b(PHA)+([a-zA-Z]+(RMACY))\b/ discard header /Subject:/ /TESTSTRING45819203/ I have tried sending mails with the test string (TESTSTRING45819203) but they get through. Are my rules wrong? I am very much a regex newbie, so I suspect my rules are wrong, but I need someone's help! have you enabled the milter in sendmail? you can also watch syslog and see exactly what milter-regex is doing. It is enabled in sendmail, and as I had to resolve some permissions issues to get rid of error messages I am now reasonably sure it's running as it should. I ran the milter with the -d option, and it started passing mails through the milter, but none got picked up. I then trimmed the colon from the Subject entries, and all was well! Here is my basic ruleset: reject Spam not welcome header /Subject/ /\b(PHA)+([a-zA-Z]+(RMA))\b/ reject Spam not welcome header /Subject/ /\b(PHA)+([a-zA-Z]+(RMACY))\b/ reject Testing: it works! header /Subject/ /TESTSTRING45819203/ Debug option saves the day!
Re: pkg_dig - sh(1) script
On Thu, Sep 28, 2006 at 01:27:31AM +0300, Paul Irofti wrote: I like your tool, it's nicer than cat-ing through pkgdb. Thanks. I noticed duplicates with pkgs that are output by your script, some dependencies are printed in the 'You may also delete' field too. There are no duplicates. In the output of the script, what you see in the Dependencies field are the normal dependencies of the package. In the You may also delete field you see which of these dependencies are not needed by any other package on your system once you delete the package you are interested. So, no duplicates. $ ./pkg_dig mutt *- Package matched: mutt-1.5.11p3-hcache-sidebar |- Dependencies: gettext-0.14.5p1 .libs-expat-1.95.6p1 libiconv-1.9.2p3 gdbm-1.8.3p0 |- Required by: none |- You may also delete: .libs-expat-1.95.6p1 gdbm-1.8.3p0 $ ./pkg_dig pine *- Package matched: pine-4.64p1-kerberos-ldap |- Dependencies: openldap-client-2.3.24 .libs-openldap-client-2.3.11p4 |- Required by: none |- You may also delete: .libs-openldap-client-2.3.11p4 The results you are getting though are really strange. The packages you put in the command line should not match the ones you present as output. I provide you with the output I get using mutt as an argument since I do not have pine installed: [EMAIL PROTECTED] msid $ pkg_dig mutt *- Package matched: mutt-1.5.12 |- Dependencies: gettext-0.14.5p1 libiconv-1.9.2p3 |- Required by: none |- You may also delete: none [EMAIL PROTECTED] msid $ This is the actual output you should be getting for mutt. Keep testing and sending feedback so that I can resolve any potential problems in my implementation. -- Sideris Michael http://black.daemons.gr/msid/
Re: Bulk build oddity
On Wednesday 27 September 2006 04:00, Marc Espie wrote: On Tue, Sep 26, 2006 at 03:07:37PM -0400, STeve Andre' wrote: In building the latest set of packages for 4.0-current, I seem to be compiling things multiple times for some packages. One example is devel/gstreamer. On my previous build, it took 30 minutes to compile streamer, then all the flavors. This build, gstreamer + flavors took 10 hours. It also seems that jdk-1.5 took the normal several hours, but then jre-1.5 took about the same amount of time. Looking at the builder right now, it seems that xmane+xmess took two hours, with xmame taking 2 hours as well. I wonder what will happen when it hits KDE. It appears that things get compiled all over again each time, which is why gstreamer took so long(?). You're using `make update' or FORCE_UPDATE, right ? There's a bug there which I'm currently fixing. I should commit as soon as I've convinced myself I've got a fix... No, I was doing my usual make -k package. I've never seen this before. --STeve Andre'
Re: pkg_dig - sh(1) script
I made a modification to resolve a minor inconvenience I noticed.
Trying pkg_dig with python-tkinter was giving me this result:
[EMAIL PROTECTED] msid $ pkg_dig python-tkinter
*- Package matched: python-tkinter-2.4.3p0
|- Dependencies: tcl-8.4.7p1 python-2.4.3p0 tk-8.4.7
|- Required by: none
|- You may also delete: tk-8.4.7
[EMAIL PROTECTED] msid $
The problem here is that tcl-8.4.7p1 can be deleted as well since it is
required only by tk-8.4.7 which, as shown above, can be safely removed.
So, I made it check if any dependency depends on another as well. The
result of this change:
[EMAIL PROTECTED] msid $ pkg_dig python-tkinter
*- Package matched: python-tkinter-2.4.3p0
|- Dependencies: tcl-8.4.7p1 python-2.4.3p0 tk-8.4.7
|- Required by: none
|- You may also delete: tcl-8.4.7p1 tk-8.4.7
[EMAIL PROTECTED] msid $
I forgot to mention from the beginning that the script is totally
harmless. It does not change anything on your system. It serves only for
informational purposes. Finally, refetch, test, send feedback.
http://black.daemons.gr/msid/scripts/pkg_dig
--
Sideris Michael
http://black.daemons.gr/msid/
#!/bin/sh
# Copyright (c) 2006, Sideris Michael
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above copyright
# notice, this list of conditions and the following disclaimer in the
# documentation and/or other materials provided with the
# distribution.
# * Neither the name of the author nor the names of its
# contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS
# IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
# TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
# PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
if [ $# -eq 0 ]
then
echo Usage: `echo $0 |sed 's/^\.\///'` [pkg_name ...]
exit 0
fi
echo
for arg in $*
do
if [ true ]
then
pkgdb=/var/db/pkg
pkgname=
search=
counter=0
if [ ! -d $pkgdb ]
then
exit 1
fi
cd $pkgdb
if [ -d $arg ]
then
pkgname=$arg
counter=1
else
search=`find . -maxdepth 1 -type d -name $arg* | sort
| sed 's/^\.\///'`
for x in $search
do
if [ $arg == `echo $x | sed -e 's/^\.\///' -e
's/-[0-9].*//'` ]
then
counter=`expr $counter+1 |bc`
pkgname=${pkgname}\ $x
fi
done
fi
if [ $counter -eq 0 ]
then
echo * No package found: $arg
elif [ $counter -gt 1 ]
then
echo \* Ambiguous: $arg could be `echo $pkgname |sed
's/ /\ or\ /'`
else
echo \*\- Package matched: $pkgname
if [ -f $pkgname/+REQUIRING ]
then
deps=`cat $pkgname/+REQUIRING`
echo \|- Dependencies: $deps
else
deps=
echo \|- Dependencies: none
fi
if [ -f $pkgname/+REQUIRED_BY ]
then
required_by=`cat $pkgname/+REQUIRED_BY`
echo \|- Required by: $required_by
else
required_by=
echo \|- Required by: none
fi
if [ $deps ]
then
for x in $deps
