John Marino wrote:
> maybe you could open one final PR and provide a patch that does this?
Fair enough, will do.
Fonz
--
A.J. "Fonz" van Werven
Notice: this e-mail address wil expire on Sat 24 Dec 2016.
signature.asc
Description: PGP signature
Michael Gmelin wrote:
> Maybe you could elaborate a bit more what you find so annoying about
> running "poudriere testport origin" before doing "svn commit" that you
> are willing to drop port maintainership over it?
Sure. In this case it's the precedent that bugs me.
Needless to say, not being
John Marino wrote:
> In fact, anyone that updates ports should use either poudriere testport
> or synth test.
Then consider these relinquished:
/usr/ports/archivers/zip
/usr/ports/astro/wmmoonclock
/usr/ports/astro/xearth
/usr/ports/devel/byaccj
/usr/ports/devel/csmith
/usr/ports/devel/gzstream
Anastasios Mageirias wrote:
> wow it's not listed in "pkg search -o lame"
There's a *port* for it, but not a binary package. That has to do with
patent issues.
Fonz
--
A.J. "Fonz" van Werven
mailsig: Help! I'm a prisoner in a Chinese fortune cookie factory.
signature.asc
Description: PGP si
Julian H. Stacey wrote:
> FYI in case newer than yours, Fonz, I have
> MD5 (9.2-RELEASE/wmfortune-0.241.tar.gz) = fa8db5d9a46d9afe7757f498c781e8c9
> SHA256 (9.2-RELEASE/wmfortune-0.241.tar.gz) =
> b149067b7e3521f7e03354b12754baaf9c5556af4d286bbd6d169b1db9f6dba0
>
> It builds & run on my 9.2,
Dave Horsfall wrote:
>> There used to be "offensive" (a term to be taken rather loosely in this
>> case) fortune cookies, but they got kicked out somewhere in 9.X. That
>> was the base system though; not the ports tree.
>
> Not to mention "fortune -o" (to get the obscene versions) and there wer
Louis Epstein wrote:
> In any event,portmaster -a -i updates now abort because misc/jive is
> detected on my system.
>
> This goes beyond "We will no longer provide this application" to
> "we will no longer let you upgrade your applications as long as you
> have this one installed".
To be fair,
Mark Linimon wrote:
>>>
>>
>> Answering opposition/criticism with violence isn't exactly my style.
>
> If you say something that makes me want to plow my face into my hands,
> that's violence?
I stand corrected. Something got lost in translation there.
Fonz
--
A.J. "Fonz" van Werven
mailsi
Mark Linimon wrote:
>
Answering opposition/criticism with violence isn't exactly my style. I
tend to take it as an indication that one has run out of rational
arguments.
Moreover, I think you'll find that the word you're looking for is
.
> It's not delusions of moral superiority. It's common
Grzegorz Junka wrote:
> Could you maybe have a separate category in ports, called "uncensored" or
> something? We are all adults and can take care of ourselves, can't we?
If memory serves me well, that has been suggested before and there were
reasons (which I don't remember) for not doing that. M
andrew clarke wrote:
> Is this the first time a port has been deleted for being "offensive"?
There used to be "offensive" (a term to be taken rather loosely in this
case) fortune cookies, but they got kicked out somewhere in 9.X. That was
the base system though; not the ports tree.
Come to think
Jonathan Moore wrote:
> I was wondering it OrbFit was in the ports. I really haven't looked yet.
I can't find it in the ports tree. I'd be happy to see if I can create a
port for it, *provided* I can find the time.
HTH,
Fonz
--
A.J. "Fonz" van Werven
mailsig: Help! I'm a prisoner in a Chines
Kevin Golding wrote:
> and about the same time someone did a blanket update of RUN_DEPENDS in
> my ports. Including a PORTREVISION bump. It's easy to argue that's a
> very trivial change that doesn't needs maintainer involvement, but it
> also impacted my day.
[snip]
> Had I known about the blanke
Doug Sampson wrote:
> it crashes as follows:
>
> ###
> <...snip...>
> iozone.c:1297:1: error: unknown type name 'off64_t'; did you mean 'off_t'?
> off64_t offset = 0; /*offset for random I/O */
> ^~~
> off_t
> /usr/include/sys/types.h:173:18: note: 'off_t' declared here
> type
Grzegorz Junka wrote:
> I will review the suggestions and re-post on the jails list if something
> still needs to be clarified.
By the way: if you really have your heart set on combining all jail
reports into a single e-mail you could do something along the following
lines:
1. Decrease verbosity
Grzegorz Junka wrote:
> I am wondering if there is any standard way of dealing with those emails
> in installations where there is many more jails than in my case?
This has nothing to do with ports, but still:
1. You can have the output of the periodic(8) scripts sent to a logfile
instead of e-m
Steve Kargl wrote:
>> Sounds like a job for the port's maintainer...
>
> I'm going under the assumption that if one is a maintainer, then s/he
> will be reading this list.
Ideally, yes. But in practice I doubt that every maintainer is subscribed
to ports@ -- and reads it frequently. Hence, I alw
Steve Kargl wrote:
> Please supply either a science/hdf5-1.8 port, revert the 1.10.0
> update, or consider the above patches.
Sounds like a job for the port's maintainer...
% make -C /usr/ports/science/hdf5 maintainer
HTH,
AvW
--
A.J. "Fonz" van Werven
mailsig: Ob technicas difficultates, lu
Christoph Brinkhaus wrote:
>> I recommend doing what the port says. The Handbook appears to be incorrect
>> at this point and probably needs updating.
>
> I have created a patch as
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209831
> and referred to this discussion.
Thanks. There really
Matt Smith via freebsd-ports wrote:
> Anybody else notice that pkg updating -d has been broken for a while? Or
> is it just me?
>
> # grep 2016 /usr/ports/UPDATING | head -4
> 20160526:
> 20160525:
> 20160523:
> 20160511:
>
> # pkg updating -d 20160523
Just to be sure: you do know that "pkg upd
Grzegorz Junka wrote:
> If you installed from ports then this is what works for me:
>
> sendmail/usr/local/sbin/sendmail
> send-mail /usr/local/sbin/sendmail
> mailq /usr/local/sbin/sendmail
> newaliases /usr/local/sbin/sendmail
> hoststat/usr/local/sbin/sendm
Marko Cupa? wrote:
> Are they both correct, or one of them needs to be updated?
I recommend doing what the port says. The Handbook appears to be incorrect
at this point and probably needs updating.
HTH,
Fonz
--
A.J. "Fonz" van Werven
mailsig: Ob technicas difficultates, lux in fine cuniculum
Fernando Apestegua wrote:
> Damn it! I was starting to cry of happiness. I hope it's back soon :)
As much as I loathe the semi-illiterate "language" of Twitter, texting,
MSN and what have you, here's a "+1". Redports was a blessing for port
maintainers and I hope it gets back into full swing soon
Jim Ohlstein wrote:
> Mailman logs show connection errors.
I don't know exactly how Postfix and Mailman (try to) communicate with one
another, but is it possible that SysV IPC has to be enabled for the jail?
Or maybe raw sockets, although that's probably less likely.
Fonz
--
A.J. "Fonz" van W
Matthias Apitz wrote:
>> I'm looking to create an email campaign with a nice newsletter or email
>> I really don't want to spam. ...
>
> Any email you send to someone who has not given you the email addr for
> such campaign and has not agreed in receive such mails, is per definition
> to be consi
Clinton Bessesen wrote:
> after trying many different things, it seems to have been a DNS issue.
Glad I could help.
Note that I symlinked svnlite to svn because otherwise
# make -C /usr/ports update
doesn't work: "svn" is hardwired into one of the Makefiles somewhere. If
you use svn directly (e
Clinton Bessesen wrote:
> Running freebsd 10.2 and have been able to checkout the ports/head using
> svnlite for quite sometime in the past.
[snip]
> unable to run "/usr/bin/svnlite checkout --depth empty
> svn://svn.freebsd.org/ports/head /tmp/ports/tree"
I don't know how others handle this, but
Walter Schwarzenfeld wrote:
> But this could be overwritten with the next update.
[snip]
> But this could also [sic] overwritten.
You're using portsnap for your updates, I presume? Subversion will not
override local changes (at least not without asking first). I have a tree
here that contains loc
John Marino wrote:
> Well, if I make the assume that Kevin has been using portmaster, and
> that using Synth revealed 42 obsolete cached configurations, I would
> have to conclude PM doesn't do this anymore or does it very poorly and
> misses a large number of configs.
Using the latest version of
Freddie Cash wrote:
>> A) An option is added
>> B) An option is removed
>> C) An option default changed.
>> D) Any other option configuration changed.
>>
>> Synth is the *only* tool that detects this.
> ???portmaster used to do this; was this option removed? It was one of the
> nicer features o
30 matches
Mail list logo
