Reducir los costos y garantizar la calidad de las entregas
En línea y en Vivo / Para todo su Equipo con una sola Conexión Cómo ser el mejor COMPRADOR 12 de octubre - Online en Vivo - 10:00 a 13:00 y de 15:00 a 18:00 Hrs En el pasado, un comprador solo adquiría mercancía…pero ahora ya no. Se espera que también, aparte de solicitar pedidos… negocie para conseguir precios más bajos y un servicio mejor… sepa exactamente lo que debe incluirse en un contrato…. y tenga ideas innovadoras para reducir los costos y garantizar la calidad de las entregas. TEMARIO: 1. Elementos jurídicos de la sociedad cooperativa. 2.Responsabilidades y metas del departamento y de cada puesto del equipo. 3. Identificación del estilo operativo actual de la organización. 4. El facultamiento del personal. 5. Cómo pasar del trabajo individual al colectivo. ...¡Y mucho más! ¿Requiere la información a la Brevedad? responda este email con la palabra: Info - Comprador. centro telefónico: 018002129393 Lic. Pamela Rangel Coordinador de Evento ¿Demasiados mensajes en su cuenta? Responda este mensaje indicando que solo desea recibir CALENDARIO y sólo recibirá un correo al mes. Si desea cancelar la suscripción, solicite su BAJA. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
New port sysutils/node_exporter
Hi, Can someone please commit this new port: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212467 Thank you! -Jev ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Differences when using `make` V `port test`
Hi All, Noob porter here. :) I created a port for prometheus, and opened a ticket here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212468 On the advice of Kubilay, I ran `port test`, and this leads me to my question; When running `port test` the build binaries are not found, (logs below), but when doing a simple `make install` everything works fine, and I can see the binaries in the work/ directory also. I suspect that the pormetheus build process is doing something a little magic, but I'm lookin to understand why the build behaves differently under `port test` compared to a straight `make`. Logs from both `port test` and `make` follow. Thanks, Jev output from `port test` jev@futz /usr/ports/net-mgmt/prometheus port test ===> Using ports tree /usr/ports ===> Validating port with portlint WARN: Makefile: [43]: whitespace before end of line. 0 fatal errors and 1 warning found. ===> flags: PREFIX=/tmp/prometheus-1.1.3 NO_DEPENDS=yes PKG_DBDIR=/tmp/pkg_db.bZyp4Q3g PORTSDIR=/usr/ports -- ===> Cleaning workspace before port test ===> Cleaning for prometheus-1.1.3 ===> License APACHE20 accepted by the user ===> Fetching all distfiles required by prometheus-1.1.3 for building ===> Extracting for prometheus-1.1.3 => SHA256 Checksum OK for prometheus-prometheus-v1.1.3_GH0.tar.gz. ===> Patching for prometheus-1.1.3 ===> Applying FreeBSD patches for prometheus-1.1.3 ===> Configuring for prometheus-1.1.3 ===> Building for prometheus-1.1.3 (cd /usr/ports.svn/net-mgmt/prometheus/work/src/ github.com/prometheus/prometheus ; /usr/bin/env GOPATH="/usr/ports.svn/net-mgmt/prometheus/work:/usr/local/share/go" CGO_CFLAGS="-I/usr/local/include" CGO_LDFLAGS="-L/usr/local/lib" GOBIN="" PREFIX=/usr/ports.svn/net-mgmt/prometheus/work/src/ github.com/prometheus/prometheus gmake build) gmake[1]: Entering directory '/usr/ports.svn/net-mgmt/prometheus/work/prometheus-1.1.3' >> building binaries Using config file: /usr/ports.svn/net-mgmt/prometheus/work/src/ github.com/prometheus/prometheus/.promu.yml > prometheus + go build -a -tags netgo -ldflags "-X github.com/prometheus/prometheus/vendor/github.com/prometheus/common/version.Version=1.1.3 -X github.com/prometheus/prometheus/vendor/github.com/prometheus/common/version.Revision= -X github.com/prometheus/prometheus/vendor/github.com/prometheus/common/version.Branch= -X github.com/prometheus/prometheus/vendor/github.com/prometheus/common/version.BuildUser=jev@futz -X github.com/prometheus/prometheus/vendor/github.com/prometheus/common/version.BuildDate=20160922-21:22:42 -extldflags "-static"" -o /tmp/prometheus-1.1.3/prometheus github.com/prometheus/prometheus/cmd/prometheus > promtool + go build -a -tags netgo -ldflags "-X github.com/prometheus/prometheus/vendor/github.com/prometheus/common/version.Version=1.1.3 -X github.com/prometheus/prometheus/vendor/github.com/prometheus/common/version.Revision= -X github.com/prometheus/prometheus/vendor/github.com/prometheus/common/version.Branch= -X github.com/prometheus/prometheus/vendor/github.com/prometheus/common/version.BuildUser=jev@futz -X github.com/prometheus/prometheus/vendor/github.com/prometheus/common/version.BuildDate=20160922-21:22:42 -extldflags "-static"" -o /tmp/prometheus-1.1.3/promtool github.com/prometheus/prometheus/cmd/promtool gmake[1]: Leaving directory '/usr/ports.svn/net-mgmt/prometheus/work/prometheus-1.1.3' ===> Staging for prometheus-1.1.3 ===> Generating temporary packing list ===> Creating groups. ===> Creating users install -m 555 /usr/ports.svn/net-mgmt/prometheus/work/prometheus-1.1.3/promtool /usr/ports.svn/net-mgmt/prometheus/work/stage/tmp/prometheus-1.1.3/bin install: /usr/ports.svn/net-mgmt/prometheus/work/prometheus-1.1.3/promtool: No such file or directory *** Error code 71 Stop. make: stopped in /usr/ports.svn/net-mgmt/prometheus ===> Error running make stage ===> Cleaning up ✘ jev@futz /usr/ports/net-mgmt/prometheus output from just make; jev@futz /usr/ports/net-mgmt/prometheus sudo make ===> License APACHE20 accepted by the user ===> prometheus-1.1.3 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by prometheus-1.1.3 for building ===> Extracting for prometheus-1.1.3 => SHA256 Checksum OK for prometheus-prometheus-v1.1.3_GH0.tar.gz. ===> Patching for prometheus-1.1.3 ===> Applying FreeBSD patches for prometheus-1.1.3 ===> prometheus-1.1.3 depends on file: /usr/local/bin/go - found ===> prometheus-1.1.3 depends on executable: gmake - found ===> Configuring for prometheus-1.1.3 ===> Building for prometheus-1.1.3 (cd /usr/ports.svn/net-mgmt/prometheus/work/src/ github.com/prometheus/prometheus ; /usr/bin/env GOPATH="/usr/ports.svn/net-mgmt/prometheus/work:/usr/local/share/go" CGO_CFLAGS="-I/usr/local/inclu
multimedia/mplayer2 ignored on poudriere
Hi everyone, I am updating my packages using poudriere and multimedia/mplayer2 is being ignored because my default python version is 2. The port explicitly lists lang/python3 as a build depend, why do I need to set my default version to 3 then? If I do so, other ports (llvm37 I think it was) won't compile either. Thanks. Best regards, Fernando ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: devel/libsysinfo
On Thu, Sep 22, 2016 at 5:13 AM, Mathieu Arnoldwrote: > Le 22/09/2016 à 13:37, Kurt Jaeger a écrit : > > Hi! > > > >> which depends on libsysinfo 0.0.2_1, GNU libc's sysinfo port for FreeBSD > >> devel/libsysinfo > >> which is now > >> "BROKEN: Unfetchable (google code has gone away)" > >> > >> LXDE is a very nice lightweight desktop environment > >> that I have been using while waiting for the LXQt port. > >> > >> I am preparing to upgrade to FreeBSD 11 and recompile my system. > >> > >> Will the ports formally hosted by google code find a new host soon? > > Only if you provide one -- and a patch for the port. > > There's discussion on how to handle the vanished google code repo > > and it's not decided yet. > > There is no discussion, there are two possibilities for each port: > > - The software for the port has a new home, the port should be updated > to reflect that > - The software for the port is dead, and if nobody adopts it (by that, I > mean become upstream), it will eventually be removed. > > -- > Mathieu Arnold > Life should be so simple! There may be two possibilities for each port, but there may be more. I was working on on port, multimedia/mp4v2, the was hosted on Google Code. It was a while ago to GitHub, but was moved twice by two people. Which one is "official"? One has had a release since the move. The other has had patches, but no new release. Which to use? More prosaically, most of these distros are cached on FreeBSD servers. At least the port I was working on has had the BROKEN removed and is downloading the tarball from that cache. As long as no security issues are found, that looks like the best interim solution. If it ain't broke, don't fix it and don't say that it's broken. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Cómo ser el mejor Comprador - En Línea
En línea y en Vivo / Para todo su Equipo con una sola Conexión Cómo ser el mejor COMPRADOR 12 de octubre - Online en Vivo - 10:00 a 13:00 y de 15:00 a 18:00 Hrs En el pasado, un comprador solo adquiría mercancía…pero ahora ya no. Se espera que también, aparte de solicitar pedidos… negocie para conseguir precios más bajos y un servicio mejor… sepa exactamente lo que debe incluirse en un contrato…. y tenga ideas innovadoras para reducir los costos y garantizar la calidad de las entregas. TEMARIO: 1. Elementos jurídicos de la sociedad cooperativa. 2.Responsabilidades y metas del departamento y de cada puesto del equipo. 3. Identificación del estilo operativo actual de la organización. 4. El facultamiento del personal. 5. Cómo pasar del trabajo individual al colectivo. ...¡Y mucho más! ¿Requiere la información a la Brevedad? responda este email con la palabra: Info - Comprador. centro telefónico: 018002129393 Lic. Pamela Rangel Coordinador de Evento ¿Demasiados mensajes en su cuenta? Responda este mensaje indicando que solo desea recibir CALENDARIO y sólo recibirá un correo al mes. Si desea cancelar la suscripción, solicite su BAJA. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: py34-dnspython
> On 22 Sep 2016, at 18:09, Ruslan Makhmatkhanovwrote: > > Kristof Provost wrote on 09/21/2016 11:54: >>> On 20 Sep 2016, at 20:15, Ruslan Makhmatkhanov wrote: >>> Kristof Provost wrote on 09/20/2016 19:40: I found I had a need for dnspython for python 3.4. The port builds only for python 2.7 at the moment. Attached is a patch to introduce py34-dnspython. Regards, Kristof >>> >>> Feel free to commit it. Actually people asked about this in past, but >>> I wasn't able to do that for some reason. >>> >>> I'd only change port directory name to dns/py3-dnspython to not tie it >>> to particular python version, but to use default python3 version >>> (which is 3.4 at the moment). PYTHON_VERSION is better to replace with >>> USES too. >>> >>> Please see audio/py3-mutagen/Makefile for example. >>> >> Thanks for the suggestions. I’ve updated the patch. >> I don’t have a ports commit bit, but I’m in Belgrade for EuroBSD, so I’m >> sure I can find someone ;) >> >> Regards, >> Kristof > > Committed in r422632. Thank you! Thanks! Kristof ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: py34-dnspython
Kristof Provost wrote on 09/21/2016 11:54: On 20 Sep 2016, at 20:15, Ruslan Makhmatkhanov wrote: Kristof Provost wrote on 09/20/2016 19:40: I found I had a need for dnspython for python 3.4. The port builds only for python 2.7 at the moment. Attached is a patch to introduce py34-dnspython. Regards, Kristof Feel free to commit it. Actually people asked about this in past, but I wasn't able to do that for some reason. I'd only change port directory name to dns/py3-dnspython to not tie it to particular python version, but to use default python3 version (which is 3.4 at the moment). PYTHON_VERSION is better to replace with USES too. Please see audio/py3-mutagen/Makefile for example. Thanks for the suggestions. I’ve updated the patch. I don’t have a ports commit bit, but I’m in Belgrade for EuroBSD, so I’m sure I can find someone ;) Regards, Kristof Committed in r422632. Thank you! -- Regards, Ruslan T.O.S. Of Reality ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
pywinrm module
Hi! Has anybody tried to create a port for pywinrm? https://github.com/diyan/pywinrm ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[eclipse plugins] proposal of layout
Hi, Hope you're doing well! I've tried to make ports for few Eclipse plugins: https://github.com/Cka3o4Huk/fbsd-ports-addons/commit/56d4fdc19fd915dacc049b52e8cbf0b94b696c96 Before I've used installation via update sites, i.e. via Eclipse mechanism. But I've found few disadvantages of such approach: - it results in mess of plugins in .eclipse/org.eclipse.../plugins folder. - lack of native support for CDT. CDT doesn't provide FreeBSD support by default, so it requires additional OSGi fragments to bring FreeBSD support. Such fragments can be easily added to ports. As result, I've made bit of work to prepare ports. Here is brief description of porting approach: - NO_BUILD: port downloads ready plugins & features from update sites - dropins: no surprise, port installs downloaded files into share/eclipse//eclipse/{features,plugins} - dependencies: port also downloads/installs dependencies not present in ports (like emf or birt) in share/eclipse//eclipse folder. - distinfo: plugins & features are downloaded separately, file by file. So it results in huge list of files in distinfo. - new plugins: to port new plugin, I start clean Eclipse instance and install plugin in question via update site. Then fill variables PLUGINS/FEATURES/DEPS of Makefile accorging to ~/.eclipse/org.eclipse../{features,plugins} folders. I would like to hear your thoughts about it. May be it's waste of time and best way to install Eclipse plugins is still to use update site. Thank you in advance! P.S. CDT fragments to bring FreeBSD support is in testing now, I'll realize them soon. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: k3b can't find CD drive
On Thu, 22 Sep 2016 20:59:50 +1000 Graham Menhennittwrote: > On 21/09/2016 23:48, Ivan Klymenko wrote: > > On Wed, 21 Sep 2016 22:35:44 +1000 > > Graham Menhennitt wrote: > > > >> Hi all, > >> > >> I'm trying to write a CD using k3b. However, when it starts, it > >> tells me that it can't find a CD drive to work with. Dmesg shows: > >> > >> cd0 at ata0 bus 0 scbus4 target 0 lun 0 > >> cd0: Removable CD-ROM SCSI > >> device cd0: Serial Number NHDL064152WL > >> cd0: 150.000MB/s transfers (SATA, UDMA5, ATAPI 12bytes, PIO > >> 8192bytes) cd0: 0MB (1 2048 byte sectors) > > > > look patch from > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210354 > Ivan, > > Why have you marked the bug as "Closed"? The patch still needs to be > applied. > > Graham https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210354#c4 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
2016/2017 Diplomatic Protocol & Etiquette Conference Invitation
Thank you for accepting this workshop invitation. You may please unsubscribe here if you no longer wish to receive our emails ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
net/samplicator: fix fetch and bump to 1.3.8rc1
Hi there, This moves port fetch to GitHub and (unfortunately) bumps to a newer version since there is no tag for the former version. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212811 The new version was already tested in a production environment and works as expected. Can provide a build log if requested. Thanks, Franco ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
sysutils/msktutil: fix fetch
Hi there, The msktutil home moved to SF. There is also a new version 1.0 that came out two days ago so it's active... but first things first. :) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212810 Thanks, Franco ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: devel/libsysinfo
Le 22/09/2016 à 13:37, Kurt Jaeger a écrit : > Hi! > >> which depends on libsysinfo 0.0.2_1, GNU libc's sysinfo port for FreeBSD >> devel/libsysinfo >> which is now >> "BROKEN: Unfetchable (google code has gone away)" >> >> LXDE is a very nice lightweight desktop environment >> that I have been using while waiting for the LXQt port. >> >> I am preparing to upgrade to FreeBSD 11 and recompile my system. >> >> Will the ports formally hosted by google code find a new host soon? > Only if you provide one -- and a patch for the port. > There's discussion on how to handle the vanished google code repo > and it's not decided yet. There is no discussion, there are two possibilities for each port: - The software for the port has a new home, the port should be updated to reflect that - The software for the port is dead, and if nobody adopts it (by that, I mean become upstream), it will eventually be removed. -- Mathieu Arnold signature.asc Description: OpenPGP digital signature
Re: FreeBSD Port: devel/libsysinfo
Le 22/09/2016 à 13:57, Franco Fichtner a écrit : > Hi Kurt, > >> On 22 Sep 2016, at 1:37 PM, Kurt Jaegerwrote: >> >> Only if you provide one -- and a patch for the port. > Within this Google Code fallout, is there a policy for how the > submitted patches are committed? E.g. do they require maintainer > approval? Are they priority items? Any build fixes fall into a blanket approval from portmgr and can be committed without waiting for approval from the maintainer, see the note in: https://www.freebsd.org/doc/en/books/porters-handbook/makefile-maintainer.html -- Mathieu Arnold signature.asc Description: OpenPGP digital signature
Re: FreeBSD Port: devel/libsysinfo
Hi Kurt, > On 22 Sep 2016, at 1:37 PM, Kurt Jaegerwrote: > > Only if you provide one -- and a patch for the port. Within this Google Code fallout, is there a policy for how the submitted patches are committed? E.g. do they require maintainer approval? Are they priority items? Thanks, Franco ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: devel/libsysinfo
Hi! > which depends on libsysinfo 0.0.2_1, GNU libc's sysinfo port for FreeBSD > devel/libsysinfo > which is now > "BROKEN: Unfetchable (google code has gone away)" > > LXDE is a very nice lightweight desktop environment > that I have been using while waiting for the LXQt port. > > I am preparing to upgrade to FreeBSD 11 and recompile my system. > > Will the ports formally hosted by google code find a new host soon? Only if you provide one -- and a patch for the port. There's discussion on how to handle the vanished google code repo and it's not decided yet. See https://lists.freebsd.org/pipermail/svn-ports-all/2016-September/132364.html and the followups. -- p...@opsec.eu+49 171 3101372 4 years to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: k3b can't find CD drive
On 21/09/2016 23:48, Ivan Klymenko wrote: > On Wed, 21 Sep 2016 22:35:44 +1000 > Graham Menhennittwrote: > >> Hi all, >> >> I'm trying to write a CD using k3b. However, when it starts, it tells >> me that it can't find a CD drive to work with. Dmesg shows: >> >> cd0 at ata0 bus 0 scbus4 target 0 lun 0 >> cd0: Removable CD-ROM SCSI device >> cd0: Serial Number NHDL064152WL >> cd0: 150.000MB/s transfers (SATA, UDMA5, ATAPI 12bytes, PIO >> 8192bytes) cd0: 0MB (1 2048 byte sectors) > > look patch from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210354 Ivan, Why have you marked the bug as "Closed"? The patch still needs to be applied. Graham ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: k3b can't find CD drive
On 21/09/2016 23:48, Ivan Klymenko wrote: > On Wed, 21 Sep 2016 22:35:44 +1000 > Graham Menhennittwrote: > >> Hi all, >> >> I'm trying to write a CD using k3b. However, when it starts, it tells >> me that it can't find a CD drive to work with. Dmesg shows: >> >> cd0 at ata0 bus 0 scbus4 target 0 lun 0 >> cd0: Removable CD-ROM SCSI device >> cd0: Serial Number NHDL064152WL >> cd0: 150.000MB/s transfers (SATA, UDMA5, ATAPI 12bytes, PIO >> 8192bytes) cd0: 0MB (1 2048 byte sectors) >> >> I think I've got all the correct things in my kernel: pass, scb, cd. >> I'm I'm pretty sure it's not a permissions problem as it happens when >> I run k3b as root too. >> >> This is on a recent 11-stable AMD64 with up to date ports. >> > look patch from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210354 Thank you very much Ivan. That fixed it. Graham ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ devel/libcwd| 1.0.4 | 1.0.6 +-+ www/c-icap | 0.4.3 | 0.4.4 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"