FreeBSD Port: xtrabackup-2.1.7_1
Hello, could you please update the xtrabackup port in near future? It’s quite old now. Thanks in advance! — Mit freundlichen Gruessen / Kind regards, Thomas Babut IT-Administration mobileObjects AG ... für die mobilen Einheiten Ihres Unternehmens Lindberghring 2-4 D-33142 Bueren/Ahden Telefon: +49 (0) 29 55 - 7 47 23-260 Telefax: +49 (0) 29 55 - 7 47 23-20 Mail : tba...@mobileobjects.de Web : http://www.mobileObjects.de Amtsgericht Paderborn - HRB 6068 - Sitz der Gesellschaft 33142 Bueren Vorstaende: Kurt Denk (Vorsitzender), Karl-Heinz Kolle Aufsichtsratsvorsitzender: Frank Hölzle ___ 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: percona56-server-5.6.19.67.0
Hello, could you please update the Percona MySQL ports to the newest version? Thanks in advance! :) — Mit freundlichen Gruessen / Kind regards, Thomas Babut IT-Administration mobileObjects AG ... für die mobilen Einheiten Ihres Unternehmens Lindberghring 2-4 D-33142 Bueren/Ahden Telefon: +49 (0) 29 55 - 7 47 23-260 Telefax: +49 (0) 29 55 - 7 47 23-20 Mail : tba...@mobileobjects.de Web : http://www.mobileObjects.de Amtsgericht Paderborn - HRB 6068 - Sitz der Gesellschaft 33142 Bueren Vorstaende: Kurt Denk (Vorsitzender), Karl-Heinz Kolle Aufsichtsratsvorsitzender: Frank Hölzle ___ 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: Getting rid of my ports
On Tue, 18 Nov 2014, Paul Schmehl wrote: > I am retiring at the end of January. I will no longer be able to maintain > ports (nor will I have much interest in doing so), so I need volunteers to > take them over. They should all be up to date (although I haven't checked > today.) > > Here's the list: > > # make search key="pa...@utdallas.edu" | grep Port > Port: byaccj-1.15 > Port: liblognorm-1.0.0_1 > Port: p5-Iodef-Pb-Simple-0.21 > Port: p5-Net-DNS-Match-0.05 > Port: p5-Parse-Range-0.96 > Port: p5-IP-Anonymous-0.04 > Port: p5-Net-Nessus-XMLRPC-0.30_1 > Port: argus-sasl-3.0.8 > Port: argus-clients-sasl-3.0.8 > Port: p5-Net-Abuse-Utils-Spamhaus-0.04 > Port: afterglow-1.6.2 > Port: barnyard2-1.13 > Port: barnyard2-sguil-1.13 > Port: chaosreader-0.94_1 > Port: p5-Snort-Rule-1.07 > Port: sancp-1.6.1_5 > Port: spybye-0.3_4 > Port: p5-Linux-Cpuinfo-1.8 > Port: p5-CIF-Client-0.21 > Port: p5-REST-Client-249 > Port: iwidgets-4.0.1_1 > Port: p5-Gtk2-Ex-Dialogs-0.11_5 > Port: p5-Gtk2-Ex-Utils-0.09_6 > Port: p5-Gtk2-GladeXML-1.007_3 > Hello, If nobody for p5-*, you can set p...@freebsd.org as maintainer. We will take care of them. Regards, -- Philippe Audéoud ___ 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: How to recover local.sqlite (pkg(8) problem)
On Wed, 19 Nov 2014 01:21:27 +0100 Baptiste Daroussin wrote > On Tue, Nov 18, 2014 at 04:18:33PM -0800, Chris H wrote: > > Greetings, > > During the building of a meta-port in the ports tree. My > > /var/db/pkg/local.sqlite database became corrupted. I > > spent some time, both with the pkg man pages, and with > > sqlite3 itself attempting to use one of the backups > > created by periodic(8). Located in /var/backups. But all > > to no avail. For the record, I used > > pkg backup -r /var/backup/pkg.sql.xz, as well as unpacking > > a copy of that file, and issuing the same. Moving (renaming) > > the corrupted database aside, prior to. I also issued > > sqlite3 local.sqlite > > followed by > > read pkg.sql > > and > > quit > > went w/o issue. But issuing > > pkg info > > emitted several error messages. Which appeared to be from > > sqlite3(8). > > This is on RELENG_9, w/source, and kernel world from about > > 1 week ago. I know that the backup is in good shape, as I > > had been using it w/o issue. > > Is this a bug? > > > > Thank you for all your time, and consideration. > > > This is really surprising and first time this can of things get reported, can > you provide me the the pkg.sql.xz file? > > Are you runing on nfs? if yes start the lockd first (pkg should fallback on a > working solution (I need to check for pkg backup) but sqlite3 cli tool does > not and sqlite3 cli tool on nfs without proper locking is known to corrupt > database file. Thank you for your rapid reply, Baptiste! No. This is UFS2 only -- no nfs, no zfs. I'll send you a copy of the pkg.sql.xz directly. I did notice that when I used the sqlite3 cli, that the database was created, and that the size looked correct. But issuing pkg info resulted in many SQL related errors. Anyway. I'll send you the file. Thanks, again. --Chris > > Best regards, > Bapt ___ 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: How to recover local.sqlite (pkg(8) problem)
On Wed, Nov 19, 2014 at 01:21:27AM +0100, Baptiste Daroussin wrote: > On Tue, Nov 18, 2014 at 04:18:33PM -0800, Chris H wrote: > > Greetings, > > During the building of a meta-port in the ports tree. My > > /var/db/pkg/local.sqlite database became corrupted. I > > spent some time, both with the pkg man pages, and with > > sqlite3 itself attempting to use one of the backups > > created by periodic(8). Located in /var/backups. But all > > to no avail. For the record, I used > > pkg backup -r /var/backup/pkg.sql.xz, as well as unpacking > > a copy of that file, and issuing the same. Moving (renaming) > > the corrupted database aside, prior to. I also issued > > sqlite3 local.sqlite > > followed by > > read pkg.sql > > and > > quit > > went w/o issue. But issuing > > pkg info > > emitted several error messages. Which appeared to be from > > sqlite3(8). > > This is on RELENG_9, w/source, and kernel world from about > > 1 week ago. I know that the backup is in good shape, as I > > had been using it w/o issue. > > Is this a bug? > > > > Thank you for all your time, and consideration. > > > This is really surprising and first time this can of things get reported, can > you provide me the the pkg.sql.xz file? > > Are you runing on nfs? if yes start the lockd first (pkg should fallback on a > working solution (I need to check for pkg backup) but sqlite3 cli tool does > not > and sqlite3 cli tool on nfs without proper locking is known to corrupt > database > file. > > Best regards, > Bapt Right checked I forgot to add the lock workaround on pkg backup I'll fix in 1.4.0 in the mean time you just have to start lockd (service lockd start) and the recovery will just work. It might have been corrupted because a background backup (without the proper lock workaround) happened at the same time you were via the ports tree running the pkg command. Best regards, Bapt pgpSVJmpuTpFa.pgp Description: PGP signature
Re: How to recover local.sqlite (pkg(8) problem)
On Tue, Nov 18, 2014 at 04:18:33PM -0800, Chris H wrote: > Greetings, > During the building of a meta-port in the ports tree. My > /var/db/pkg/local.sqlite database became corrupted. I > spent some time, both with the pkg man pages, and with > sqlite3 itself attempting to use one of the backups > created by periodic(8). Located in /var/backups. But all > to no avail. For the record, I used > pkg backup -r /var/backup/pkg.sql.xz, as well as unpacking > a copy of that file, and issuing the same. Moving (renaming) > the corrupted database aside, prior to. I also issued > sqlite3 local.sqlite > followed by > read pkg.sql > and > quit > went w/o issue. But issuing > pkg info > emitted several error messages. Which appeared to be from > sqlite3(8). > This is on RELENG_9, w/source, and kernel world from about > 1 week ago. I know that the backup is in good shape, as I > had been using it w/o issue. > Is this a bug? > > Thank you for all your time, and consideration. > This is really surprising and first time this can of things get reported, can you provide me the the pkg.sql.xz file? Are you runing on nfs? if yes start the lockd first (pkg should fallback on a working solution (I need to check for pkg backup) but sqlite3 cli tool does not and sqlite3 cli tool on nfs without proper locking is known to corrupt database file. Best regards, Bapt pgppVwIVRXXd4.pgp Description: PGP signature
How to recover local.sqlite (pkg(8) problem)
Greetings, During the building of a meta-port in the ports tree. My /var/db/pkg/local.sqlite database became corrupted. I spent some time, both with the pkg man pages, and with sqlite3 itself attempting to use one of the backups created by periodic(8). Located in /var/backups. But all to no avail. For the record, I used pkg backup -r /var/backup/pkg.sql.xz, as well as unpacking a copy of that file, and issuing the same. Moving (renaming) the corrupted database aside, prior to. I also issued sqlite3 local.sqlite followed by read pkg.sql and quit went w/o issue. But issuing pkg info emitted several error messages. Which appeared to be from sqlite3(8). This is on RELENG_9, w/source, and kernel world from about 1 week ago. I know that the backup is in good shape, as I had been using it w/o issue. Is this a bug? Thank you for all your time, and consideration. --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"
Re: help w/ port just installing files...
John-Mark Gurney wrote this message on Tue, Nov 18, 2014 at 12:42 -0800:
> John-Mark Gurney wrote this message on Tue, Nov 18, 2014 at 12:35 -0800:
> > John-Mark Gurney wrote this message on Mon, Nov 17, 2014 at 19:31 -0800:
> > > So, I'm trying to get a port that will install the NIST's KAT vectors
> > > so I can write a test program using them...
> >
> > Ok, so here is a port I'm submitting for reivew so that I can commit it.
>
> Oops, forgot to run portlist -A on it before submitting... I've fixed
> the direct use of chmod, mkdir and cp... I moved the MASTER_SITES and
> DISTFILES to the earlier section...
>
> Now portlint only says:
> WARN: Makefile: [25]: possible use of "${CHMOD}" found. Use @owner/@group
> operators in pkg-plist instead.
> FATAL: Makefile: extra item "BASE_URL" placed in the PORTNAME section.
> WARN: Makefile: Consider defining LICENSE.
>
> I can't do much about the CHMOD warning as that is necessary unless we
> want world writable files installed by the package...
>
> I could move BASE_URL to after the COMMENT, and it would work (because
> make), but I find that less that readable...
>
> Attached is the new Makefile...
Sorry for the constant emails, learning new things as I go...
> # We want each dist file in it's own subdir
> EXTRACT_CMD= ${MKDIR} ${PORTNAME}/$${file%.zip} && ${TAR}
> EXTRACT_AFTER_ARGS=-C ${PORTNAME}/$${file%.zip} && \
> ${CHMOD} -R a-w ${PORTNAME}/$${file%.zip}
With the below change, this simply drops the CHMOD to be:
EXTRACT_AFTER_ARGS=-C ${PORTNAME}/$${file%.zip}
[...]
> do-install:
> ${MKDIR} ${STAGEDIR}${LOCALBASE}/share && \
> ${CP} -Rp ${WRKSRC}/${PORTNAME} ${STAGEDIR}${LOCALBASE}/share
Is now:
do-install:
${MKDIR} ${STAGEDIR}${LOCALBASE}/share && \
(cd ${WRKSRC}/${PORTNAME} && ${COPYTREE_SHARE} . ${STAGEDIR}${DATADIR})
so that proper ownership and modes are automaticly applied...
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
___
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: bind-tools port version
+--On 18 novembre 2014 16:27:24 +0100 Andrei Brezan wrote: | Hi all, | | It seems something odd happened with the bind-tools port. Was it reverted | recently? Somehow I managed to be a version ahead. | | bind-tools-9.10.1_2> succeeds port (port has 9.10.1_1) | | % svnlite ls -v /usr/ports/dns/bind-tools/ | 371360 mat Oct 22 17:08 ./ | 371360 mat 747 Oct 22 17:08 Makefile | 369309 mat 328 Sep 26 10:31 pkg-descr | 359094 mat 700 Jun 24 17:15 pkg-plist | | Anyone know what happened? I've only built from ports. and 9.10.1_2 was | pulled in on Nov 2'nd. Hum, no, it's me forgetting that bind-tools is a slave of bind910, I just fixed it. -- Mathieu Arnold ___ 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: cfengine36-3.6.1_3,1
Hi Jurica- On Mon, Nov 17, 2014 at 12:18 PM, Jurica Borozan wrote: > Hi, > > I am trying to run cfengine 3.6.1 and 3.5.8 but it will not work with > XML files: "error: Cannot edit XML files without LIBXML2" It looks like the current version of the port doesn't have the option to pull in libxml2 to enable this feature. Can you try out this patch and let me know if it solves your issue? https://people.freebsd.org/~skreuzer/patches/cfengine36-libxml.patch The following commands will download the patch into your home directory, apply the changes to the port and build and install a version of cfengine with xml support $ cd ~ $ fetch https://people.freebsd.org/~skreuzer/patches/cfengine36-libxml.patch $ cd /usr/ports $ patch < ~/cfengine36-libxml.patch $ cd /usr/ports/sysutils/cfengine36 $ sudo make WITH="LIBXML2" install Let me know if you have any problems. Thanks ___ 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: Getting rid of my ports
Kurt Jaeger wrote: >>> Port: byaccj-1.15 >>> Port: chaosreader-0.94_1 >> >> I'd be happy to adopt the above two. > > You have those two. Thanks. I can submit PRs tomorrow (new maintainer address, additional distfile mirror, etc.) if you want. AvW -- Imbibo, ergo sum. pgpRtqAHl9U82.pgp Description: PGP signature
Re: Getting rid of my ports
Hi! > > Port: byaccj-1.15 > > Port: chaosreader-0.94_1 > > I'd be happy to adopt the above two. You have those two. -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ 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: Getting rid of my ports
Paul Schmehl wrote: > I will no longer be able to maintain ports [snip] > so I need volunteers to take them over. [snip] > Port: byaccj-1.15 > Port: chaosreader-0.94_1 I'd be happy to adopt the above two. Regards, AvW -- Imbibo, ergo sum. pgpT3Z5CEgyKN.pgp Description: PGP signature
Re: Getting rid of my ports
Hi, I would like to volunteer. BR, Muhammad On Wed, Nov 19, 2014 at 4:06 AM, Paul Schmehl wrote: > I am retiring at the end of January. I will no longer be able to maintain > ports (nor will I have much interest in doing so), so I need volunteers to > take them over. They should all be up to date (although I haven't checked > today.) > > Here's the list: > > # make search key="pa...@utdallas.edu" | grep Port > Port: byaccj-1.15 > Port: liblognorm-1.0.0_1 > Port: p5-Iodef-Pb-Simple-0.21 > Port: p5-Net-DNS-Match-0.05 > Port: p5-Parse-Range-0.96 > Port: p5-IP-Anonymous-0.04 > Port: p5-Net-Nessus-XMLRPC-0.30_1 > Port: argus-sasl-3.0.8 > Port: argus-clients-sasl-3.0.8 > Port: p5-Net-Abuse-Utils-Spamhaus-0.04 > Port: afterglow-1.6.2 > Port: barnyard2-1.13 > Port: barnyard2-sguil-1.13 > Port: chaosreader-0.94_1 > Port: p5-Snort-Rule-1.07 > Port: sancp-1.6.1_5 > Port: spybye-0.3_4 > Port: p5-Linux-Cpuinfo-1.8 > Port: p5-CIF-Client-0.21 > Port: p5-REST-Client-249 > Port: iwidgets-4.0.1_1 > Port: p5-Gtk2-Ex-Dialogs-0.11_5 > Port: p5-Gtk2-Ex-Utils-0.09_6 > Port: p5-Gtk2-GladeXML-1.007_3 > > -- > Paul Schmehl, Senior Infosec Analyst > As if it wasn't already obvious, my opinions > are my own and not those of my employer. > *** > "It is as useless to argue with those who have > renounced the use of reason as to administer > medication to the dead." Thomas Jefferson > "There are some ideas so wrong that only a very > intelligent person could believe in them." George Orwell > > ___ > 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"
Getting rid of my ports
I am retiring at the end of January. I will no longer be able to maintain ports (nor will I have much interest in doing so), so I need volunteers to take them over. They should all be up to date (although I haven't checked today.) Here's the list: # make search key="pa...@utdallas.edu" | grep Port Port: byaccj-1.15 Port: liblognorm-1.0.0_1 Port: p5-Iodef-Pb-Simple-0.21 Port: p5-Net-DNS-Match-0.05 Port: p5-Parse-Range-0.96 Port: p5-IP-Anonymous-0.04 Port: p5-Net-Nessus-XMLRPC-0.30_1 Port: argus-sasl-3.0.8 Port: argus-clients-sasl-3.0.8 Port: p5-Net-Abuse-Utils-Spamhaus-0.04 Port: afterglow-1.6.2 Port: barnyard2-1.13 Port: barnyard2-sguil-1.13 Port: chaosreader-0.94_1 Port: p5-Snort-Rule-1.07 Port: sancp-1.6.1_5 Port: spybye-0.3_4 Port: p5-Linux-Cpuinfo-1.8 Port: p5-CIF-Client-0.21 Port: p5-REST-Client-249 Port: iwidgets-4.0.1_1 Port: p5-Gtk2-Ex-Dialogs-0.11_5 Port: p5-Gtk2-Ex-Utils-0.09_6 Port: p5-Gtk2-GladeXML-1.007_3 -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell ___ 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: help w/ port just installing files...
John-Mark Gurney wrote this message on Tue, Nov 18, 2014 at 12:35 -0800:
> John-Mark Gurney wrote this message on Mon, Nov 17, 2014 at 19:31 -0800:
> > So, I'm trying to get a port that will install the NIST's KAT vectors
> > so I can write a test program using them...
>
> Ok, so here is a port I'm submitting for reivew so that I can commit it.
Oops, forgot to run portlist -A on it before submitting... I've fixed
the direct use of chmod, mkdir and cp... I moved the MASTER_SITES and
DISTFILES to the earlier section...
Now portlint only says:
WARN: Makefile: [25]: possible use of "${CHMOD}" found. Use @owner/@group
operators in pkg-plist instead.
FATAL: Makefile: extra item "BASE_URL" placed in the PORTNAME section.
WARN: Makefile: Consider defining LICENSE.
I can't do much about the CHMOD warning as that is necessary unless we
want world writable files installed by the package...
I could move BASE_URL to after the COMMENT, and it would work (because
make), but I find that less that readable...
Attached is the new Makefile...
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
# Created by: John-Mark Gurney
# $FreeBSD$
PORTNAME= nist-kat
DISTVERSION=1.0
CATEGORIES= security
BASE_URL= http://csrc.nist.gov/groups/STM/cavp/documents
MASTER_SITES= ${BASE_URL}/aes/:aes
MASTER_SITES+= ${BASE_URL}/des/:des
MASTER_SITES+= ${BASE_URL}/mac/:mac
DISTFILES= KAT_AES.zip:aes
DISTFILES+= XTSTestVectors.zip:aes
DISTFILES+= KAT_TDES.zip:des
DISTFILES+= gcmtestvectors.zip:mac
DISTFILES+= hmactestvectors.zip:mac
MAINTAINER= j...@freebsd.org
COMMENT=Collection of NIST's Know Answer Test Vectors
#LICENSE= PUBLICDOMAIN
# We want each dist file in it's own subdir
EXTRACT_CMD=${MKDIR} ${PORTNAME}/$${file%.zip} && ${TAR}
EXTRACT_AFTER_ARGS=-C ${PORTNAME}/$${file%.zip} && \
${CHMOD} -R a-w ${PORTNAME}/$${file%.zip}
NO_BUILD=
NO_WRKSUBDIR=
do-install:
${MKDIR} ${STAGEDIR}${LOCALBASE}/share && \
${CP} -Rp ${WRKSRC}/${PORTNAME} ${STAGEDIR}${LOCALBASE}/share
.include
___
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: help w/ port just installing files...
John-Mark Gurney wrote this message on Mon, Nov 17, 2014 at 19:31 -0800: > So, I'm trying to get a port that will install the NIST's KAT vectors > so I can write a test program using them... Ok, so here is a port I'm submitting for reivew so that I can commit it. Thanks. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ 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: help w/ port just installing files...
Waitman Gobble wrote this message on Mon, Nov 17, 2014 at 12:37 -0800:
> On Mon, November 17, 2014 12:14 pm, Waitman Gobble wrote:
>
> > On Mon, November 17, 2014 7:31 pm, John-Mark Gurney wrote:
> >
> >> So, I'm trying to get a port that will install the NIST's KAT vectors
> >> so I can write a test program using them...
> >>
> >> I don't know what is the best way to handle plist creation and
> >> installation. I have this Makefile so far: # Created by: John-Mark
> >> Gurney
> >>
> >> # $FreeBSD$
> >>
> >> PORTNAME= nist-kat
> >> DISTVERSION= 1.0
> >> CATEGORIES=security
> >>
> >> MAINTAINER=j...@freebsd.org
> >> COMMENT= Collection of NIST's Know Answer Test Vectors
> >>
> >> #LICENSE= PUBLICDOMAIN
> >>
> >> BASE_URL= http://csrc.nist.gov/groups/STM/cavp/documents
> >> MASTER_SITES= ${BASE_URL}/aes/:aes
> >> MASTER_SITES+= ${BASE_URL}/des/:des
> >> MASTER_SITES+= ${BASE_URL}/mac/:mac
> >>
> >> DISTFILES= KAT_AES.zip:aes
> >> DISTFILES+=XTSTestVectors.zip:aes
> >> DISTFILES+=KAT_TDES.zip:des
> >> DISTFILES+=gcmtestvectors.zip:mac
> >> DISTFILES+=hmactestvectors.zip:mac
> >>
> >> # We want each dist file in it's own subdir
> >> EXTRACT_CMD= mkdir $${file%.zip}; ${TAR}
> >> EXTRACT_AFTER_ARGS=-C $${file%.zip}
> >>
> >> NO_BUILD=
> >> NO_WRKSUBDIR=
> >>
> >> do-install:
> >> mkdir -p ${PREFIX}/share/nist-kat && \ cp -Rp ${WRKSRC}/
> >> ${PREFIX}/share/nist-kat
> >>
> >> .include
> >>
> >> But the cp command copies more than I want, including the staging dir.
> >>
> >> Does someone know an easier way to do this?
> >
> > I tested this, it seems to work. But it installs everything in
> > /usr/local/share/nist-kat without sub-directories. (if you want that?)
> >
> > There's no need to create the directory under /usr/local/share...
> >
> > 'make deinstall' also removes all the rsp files, which is good i think.
> >
> > do-install:
> > cd ${WRKSRC}/KAT_AES && ${COPYTREE_SHARE} . ${DOCSDIR} && \ cd
> > ${WRKSRC}/XTSTestVectors && ${COPYTREE_SHARE} . ${DOCSDIR} && \
> > cd ${WRKSRC}/KAT_TDES && ${COPYTREE_SHARE} . ${DOCSDIR} && \ cd
> > ${WRKSRC}/gcmtestvectors && ${COPYTREE_SHARE} . ${DOCSDIR} && \
> > cd ${WRKSRC}/hmactestvectors && ${COPYTREE_SHARE} . ${DOCSDIR}
>
> OOPs, jumped the gun. It's putting in /usr/local/share/doc.
>
> If you want in /usr/local/share/${PORT_NAME} then use ${DATADIR}
>
> Also, it's not removing them on make deinstall, I was looking in the wrong
> place. :(
I decided to improve my extract so things wouldn't be in the root of
WRKDIR, so extract is now:
EXTRACT_CMD=mkdir -p ${PORTNAME}/$${file%.zip} && ${TAR}
EXTRACT_AFTER_ARGS=-C ${PORTNAME}/$${file%.zip} && \
chmod -R a-w ${PORTNAME}/$${file%.zip}
The chmod is required because tar doesn't honor umask, and uzip w/o
permissions default to 0666.
I decided to try to make install install to stagedir instead of
PREFIX even though bsd.port.mk still says that you should:
# Variables that serve as convenient "aliases" for your *-install targets.
# Use these like: "${INSTALL_PROGRAM} ${WRKSRC}/prog ${PREFIX}/bin".
That example should probably read ${WRKSRC}/prog ${STAGEDIR}${LOCALBASE}/bin
But, if I install to STAGEDIR like so:
do-install:
mkdir -p ${STAGEDIR}${LOCALBASE}/share && \
cp -Rp ${WRKSRC}/${PORTNAME} ${STAGEDIR}${LOCALBASE}/share
Every thing seems to work fine... I'll follow on w/ another email w/
the complete port for review.
Thanks.
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
___
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: mail/claws-mail: freezes when using mail/claws-mail-rssyl
On Tue, 18 Nov 2014 15:33:07 +0200 Beeblebrox wrote: > I have been using mail/claws-mail for some time with the > mail/claws-mail-rssyl together with several other plugins. > > A recent update (probably r371528 or r371648) broke the mail/claws-mail-rssyl > such that: > * When started, claws-mail flickers and items in left panel move erratically. > * Does not respond to any mouse action and freezes. > * Can only be killed with "kill -9" > > Uninstalling mail/claws-mail-rssyl returns claws-mail to normal behaviour. > All other plugins continue to function normally. > +1 :( it stop works as expected on r371528 -- wbr, tiger ___ 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"
pkg hangs on 10.1 (ZFS-filesystem) in huge pkg update -f
Hi! I have a test box (10.1-REL amd64, ZFS filesystem), where pkg hangs in a pkg update -f operation: [448/2310] Reinstalling graphviz-2.38.0_2: 100% load: 0.15 cmd: dot 13636 [urdlck] 42255.22r 0.01u 0.03s 0% 6548k load: 0.15 cmd: dot 13636 [urdlck] 42255.39r 0.01u 0.03s 0% 6548k load: 0.15 cmd: dot 13636 [urdlck] 42255.53r 0.01u 0.03s 0% 6548k load: 0.15 cmd: dot 13636 [urdlck] 42255.69r 0.01u 0.03s 0% 6548k I can still log on that box (ssh). Running a pkg info brings, after a while (seen by the ctrl-t output): load: 0.47 cmd: pkg 18350 [nanslp] 26.65r 0.00u 0.03s 0% 5808k pkg: sqlite error while executing PRAGMA user_version; in file pkgdb.c:2291: database is locked A ktrace on the urdlck'ed pid did not show anything: ktrace -f /tmp/traceit -p 13636 [waiting a bit] ktrace -C and: -rw--- 1 root wheel 0 Nov 18 19:21 /tmp/traceit I have no idea why updating graphviz causes dot to be run ? Any ideas on how I can debug this further ? -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ 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: symlinked ports directory -> problem to resolve dependencies in portmaster
Am 16.11.2014 um 07:26 schrieb Alexander Leidinger: > Hi, > > my /usr/ports directory is a symlink to /space/system/usr_ports, when I > try now to update a port with portmaster, it fails when it tries to > follow dependencies. > > Example: > ---snip--- > # portmaster webcamd- > ===>>> Package installation support cannot be used with pkgng yet, >it will be disabled > > > ===>>> Currently installed version: webcamd-3.17.0.6 > ===>>> Port directory: /usr/ports/multimedia/webcamd > > ===>>> Launching 'make checksum' for multimedia/webcamd in background > ===>>> Gathering dependency list for multimedia/webcamd from ports > ===>>> Launching child to install /space/system/usr_ports/devel/pkgconf > > ===>>> webcamd-3.17.0.6 >> /space/system/usr_ports/devel/pkgconf (1/1) > > ===>>> No valid installed port, or port directory given > ===>>> Try portmaster --help > > > ===>>> Update for /space/system/usr_ports/devel/pkgconf failed > ===>>> Aborting update > > # realpath /usr/ports/devel/pkgconf > /space/system/usr_ports/devel/pkgconf > > # make -C /usr/ports -V PORTSDIR > /space/system/usr_ports > > # grep PORTSDIR /etc/make.conf > > ---snip--- > > I can't find an entry in UPDATING which looks related. Any ideas what's > wrong here? Hi Alexander, there was a change to the .mk files which requires the attached patch to portmaster (repeated inline, but probably with mangled white-space): --- portmaster~ +++ portmaster @@ -359,7 +359,7 @@ if [ "$$" -eq "$PM_PARENT_PID" ]; then if [ -z "$pd" ]; then if [ -z "$PORTSDIR" ]; then - [ -d /usr/ports ] && pd=/usr/ports + [ -d /usr/ports ] && pd=`realpath /usr/ports` [ -z "$pd" ] && pd=`pm_make_b -f/usr/share/mk/bsd.port.mk -V PORTSDIR 2>/dev/null` else I always wanted to create a PR that mentions that patch, but forgot about it and was just reminded by you ;-) Best regards, STefan --- portmaster~ +++ portmaster @@ -359,7 +359,7 @@ if [ "$$" -eq "$PM_PARENT_PID" ]; then if [ -z "$pd" ]; then if [ -z "$PORTSDIR" ]; then - [ -d /usr/ports ] && pd=/usr/ports + [ -d /usr/ports ] && pd=`realpath /usr/ports` [ -z "$pd" ] && pd=`pm_make_b -f/usr/share/mk/bsd.port.mk -V PORTSDIR 2>/dev/null` else ___ 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: claws-mail's build dependency on Tex Live
On Tue, 18 Nov 2014, RW wrote: > If you build claws-mail from ports you might want to think about > unchecking the manual option. It brings in a build dependency on > textproc/docbook-utils which in turn depends on print/texlive-texmf. > This has a 1663 MB distfile and installs 1477 MB of files. I found the same thing when installing Gnuplot (FreeBSD 9.3); I quickly cancelled it, as I was already close to my download limit... In the meantime, I just have to clean up whatever broke in the ports area when going from 8.2 to 9.3 (I could've sworn I'd followed the instructions for the new ports system). -- Dave Horsfall DTM (VK2KFU) "Bliss is a MacBook with a FreeBSD server." http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ 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"
claws-mail's build dependency on Tex Live
If you build claws-mail from ports you might want to think about unchecking the manual option. It brings in a build dependency on textproc/docbook-utils which in turn depends on print/texlive-texmf. This has a 1663 MB distfile and installs 1477 MB of files. Obviously the manual option needs to be on by default, but perhaps there should be a warning in the port menu. pkg doesn't show build dependencies, so it's not obvious where texlive came from. ___ 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: after 10.0 -> 10.1 rebuild: how to force pkg reinstall ?
On Sun, Nov 16, 2014, at 07:43, Kurt Jaeger wrote: > Hi! > > > | Thanks for the hint. I'll compare them at the next opportunity. > > > Well, you don't need to compare them, we build packages for branches on the > > oldest supported release, so 8.4 built on 8.4, the packages for 9.1, 9.2 > > and 9.3 built on 9.1, and the packages for 10.0 and 10.1 built on 10.0 :-) > > I build on 10.1 for repo.opsec.eu. And that's why I wanted to force > the upgrade. I *guess* if I build a package in a 10.0 poudriere > and in a 10.1 poudriere, they differ ? > Yes. But if you don't want to maintain two repositories it's safe to have one repository built against 10.0 and install those packages on 10.0, 10.1, 10.2... etc :-) ___ 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"
bind-tools port version
Hi all, It seems something odd happened with the bind-tools port. Was it reverted recently? Somehow I managed to be a version ahead. bind-tools-9.10.1_2> succeeds port (port has 9.10.1_1) % svnlite ls -v /usr/ports/dns/bind-tools/ 371360 mat Oct 22 17:08 ./ 371360 mat 747 Oct 22 17:08 Makefile 369309 mat 328 Sep 26 10:31 pkg-descr 359094 mat 700 Jun 24 17:15 pkg-plist Anyone know what happened? I've only built from ports. and 9.10.1_2 was pulled in on Nov 2'nd. Thanks, -- Andrei ___ 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"
mail/claws-mail: freezes when using mail/claws-mail-rssyl
I have been using mail/claws-mail for some time with the mail/claws-mail-rssyl together with several other plugins. A recent update (probably r371528 or r371648) broke the mail/claws-mail-rssyl such that: * When started, claws-mail flickers and items in left panel move erratically. * Does not respond to any mouse action and freezes. * Can only be killed with "kill -9" Uninstalling mail/claws-mail-rssyl returns claws-mail to normal behaviour. All other plugins continue to function normally. -- FreeBSD_amd64_11-Current_RadeonKMS ___ 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: Deleting ports distfiles
On Mon, 17 Nov 2014 07:40:03 -0600 Adam Vande More wrote: > On Mon, Nov 17, 2014 at 7:12 AM, RW > wrote: > > > portmaster removes any files not associated with currently installed > > packages, the other two do can do that, but also have the option to > > leave any files that are still up-to-date with respect to the ports > > tree. > > > This is a misleading statement. portmaster also has that option. My mistake. I'd always assumed that in "-t --clean-distfiles" the "-t" had its usual meaning of recurse through port dependencies. What makes that particularly confusing is that recursing to handle missing dependencies would be a useful option. I'd still recommend distviper over portmaster because it's faster. ___ 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: three-months-long maintainer timeout
Hi! > Three months ago PR 192746 was manually assigned to maintainer. > Since then the patch and test logs were twice renewed to new version and > once to new standards of pkg-plist. > But no moves from the maintainer. > Could it be that wicked Bugzilla simply forgot to notify the maintainer? No, but there are many different reasons why nothing happened. > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192746 Done. -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ 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"
three-months-long maintainer timeout
Hi, Three months ago PR 192746 was manually assigned to maintainer. Since then the patch and test logs were twice renewed to new version and once to new standards of pkg-plist. But no moves from the maintainer. Could it be that wicked Bugzilla simply forgot to notify the maintainer? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192746 Regards, Sergei ___ 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"
