e is being well maintained, before finding out so
> after having to waste time and effort trying to install and make it
> it work.
Start the build. Go off and do something useful while it builds.
After a reasonable time come back and see if it works. If it does
not, you can move on, having invested
s for SBo submissions.
You can still keep your @broadpark.no address in the INFO file.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailm
control. We don't want
them to be penalized because of lack of clue (or indeed, malice) at
their email provider.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists
sed
> all the havoc. Every subscriber who was removed from the list should
> have received their notification of removal. The problem was not a
> matter of gmail not accepting mail from us; only that the DMARC
> perpetrator was listed in the From: header. Not a factor for the
> removal
On Sun, Mar 18, 2018 at 03:20:04PM -0500, Rob McGee wrote:
> We have placed the list on emergency moderation mode for now.
> Please, no more posts about this until I get it resolved. I will
> reply here when it is.
DEFAULT_DMARC_MODERATION_ACTION = 1
This will rewrite the From
mail from us; only that the DMARC
perpetrator was listed in the From: header. Not a factor for the
removal notification mails from Mailman.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.
pic asking here, but your answer is,
"Probably not."
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https
ow enabled by
default. IIRC the existing SBo script didn't even offer sqlite3
support, and it offered Cyrus vs. Dovecot as an either/or choice
(you actually get Dovecot SASL support if you enable Cyrus.)
I would recommend using the build in -current.
--
Rob McGee - /de
essages received. What gets to the submitter's
browser is inadequate for troubleshooting.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuild
nection refused
> - telnet to lists.slackbuilds.org port http gets connection refused
Yep, thanks for the notice. For some reason yet unknown, httpd
wasn't running. It's started now, and IWFM.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBu
supported) but this could be useful.
It is good to have this documented in the list archive, but as for
your suggestion, it sounds like the problem will be resolved before
it gets to Slackware. :)
Thank you for the report.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
_
note that the http: is converted to https: because of the
domain's SSL policy. Does https://slackbuilds.org/remove/ work?
Perhaps this is a SSL/TLS problem on your end?
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-use
lworkman.net
> http://slackpkg.org
>
> The usual web, ftp, and git services of SBo will *not* be
> affected, as those are hosted on a different machine.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
email encryption methods. System admins at both ends have the
ability to "snoop" on unencrypted mail. What DANE does is limit
snoopability and prevent "man-in-the-middle" attacks.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
gest either digest mode or
"nomail", so you are still a subscriber and still allowed to post.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/
t;official policy." If you want to make a qmail build, you are
welcome to develop and to submit it.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.sla
On Sat, Nov 05, 2016 at 02:43:14AM +0100, Thomas Szteliga wrote:
> On 11/05/2016 01:56 AM, Rob McGee wrote:
> > At least 3 problems I see with that as it implies:
> > 1. that you have your CA on an openvpn server or client;
> > 2. that you will be running these scr
g this my suggestion is:
>
>
> /usr/share/easyrsa without patching KEY_DIR (keys placed in subdir)
Hehe, actually I don't have any strong feelings against this
suggestion. It's as good as any.
> and users will have to copy the contents of /usr/share/easyrsa
> t
everal ways to DTRT.)
> idea? Maybe they are redundant and there are other tools in place
> already doing this job?
They are just scripts which wrap around openssl commands. It's
possible (albeit not easy, BTDT) to read them and figure out what
they'r
tian, with no more than a few posts per year. When submissions
close, when they open, any major changes, ...
Is that a good idea? I'm not convinced that it is, myself, because
we also have IRC, and the /topic has this information.
Also, the submission form
The hardware upgrade was completed successfully. But we did not get
up on the kernel we wanted, so another reboot will take place in a
short while ... this should be a less than two minute outage.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
ed if you are in the market for quality
colocation services.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archiv
: As usual, "Robby and I" is shorthand for "Robby will do the work
while I stand around and try to look important."
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@
be
possible to add a syncthing:syncthing user/group to the SBo draft
list, to be used by the install script?
Hi Sebastian,
user:group synchting:synchting (uid:gid 307:307) have been added.
Please review carefully to see if any characters were tranpsosed.
;)
--
Rob McGee - /dev/rob0
to revert this change.
Thanks for the suggestion, and to all posters for their comments.
We're sorry for any inconvenience regarding your howto.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users
howtos -- if
any? I don't think I have seen one -- show how this is done.)
So my concern here is twofold: one, it promotes virtual mail to
users who should not be using it; and two, it promotes the less
secure means of doing it, under a single UID/GID.
--
Rob McGee - /dev/rob0 - r
not; only in the less usual case of
Postfix having to authenticate at an upstream relay, would Cyrus
become necessary.
All the details are here:
http://www.postfix.org/SASL_README.html
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
. In that
case, you can usually succeed by trying again in 5 minutes or so.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds
failure at setting up
LinkedIn. (I'm not.)
/me wanders off grumbling about social media email harvesting scams
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http
for his e-mail address.
May I take it over?
Thanks. I've been considering the same thing. In fact IIRC the
previous update to the script was what I sent him. :)
Please go ahead and submit it. IIRC from looking at it, some
significant rewriting of the script might be necessary.
--
Rob McGee
, Unix manual's
section 8, and Slackware's A series to find a few more examples.
Fonts might more properly fit into office or desktop IMO. If
enough of them are packaged, a fonts category makes sense.
Jm2cw. And Willy, your superb contributions to SBo are greatly
appreciated.
--
Rob McGee
of the maintainers ;-)
Of course, as someone who doesn't work on the web site, that's
easy for me to say.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http
messages, but I guess this
is not essential, as this new provider seems to be fine. :)
Yes, thank you.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org
cause now
seems to be when a provider has users with spammer-compromised
credentials, and that provider has inadequate means of cleaning
their outbound stream. Then they get listed on DNSBLs as a spam
source (and rightly so, because they are.)
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
and disagree.)
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds
, that it's a post to a mailing list.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http
each boot, like it or not. (I've
gotten out of the habit of using /tmp for things which are not
temporary.)
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http
On Fri, Nov 15, 2013 at 06:47:27PM +, Nick Warne wrote:
Rob McGee wrote, On 15/11/13 18:40:
SBo Slackbuilds support a feature which makes this unnecessary:
$OUTPUT. Run your build as such:
root@darkstar:~# OUTPUT=/root/pkg ./foo.Slackbuild
Or, you could set OUTPUT=/root/pkg in one
okay for now. We won't ask for contributions
often, and certainly not this soon before a Slackware release.
https://store.slackware.com/cgi-bin/store/slackdonation
https://store.slackware.com/ -- buy your subscription or donate!
Slackware is what SBo is all about.
--
Rob McGee - /dev/rob0 - r
that the
inevitably early failures waste.
Ideally the downtime will be brief. We'll know more and let you know
in a bit.
On Fri, Jun 21, 2013 at 06:15:21AM -0500, JB wrote:
On Fri, 21 Jun 2013 00:10:56 -0500
Rob McGee r...@slackbuilds.org wrote:
Note: this is NOT a solicitation
.
The default_login_user setting, dovenull, should definitely exist
for a Dovecot 2.x install. Compare with:
http://wiki.dovecot.org/UserIds
This did not exist in 1.x.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds
to lose trust in us, I suggest that it is no great loss.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives
On Mon, Oct 01, 2012 at 03:42:01PM +0100, Eugéne Suter wrote:
giving them up to whoever is willing to take them.
snip
network/mailman
If no one else volunteers for this, I will take it. If someone else
wants it, that's fine too.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
attempt is successful.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org
RFC822/2822/5322 headers.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org
for setting graylist.
Can someone point me in the right direction please...
Talk to your provider? or just try again?
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http
IPv6-ChangeLog
file. Also, back in January Wietse threw another curveball at us:
there's now a pflogsumm_quickfix.txt file which definitely belongs
with the documentation.
Sorry, no brick text this time. Maybe next time.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
for the report. Same thing happens for me. We'll figure out
what's going on and get it fixed.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman
=-L/usr/lib${LIBDIRSUFFIX}/sasl2 -lsasl2 ;;
*) SASLARGS=''
SASLLIBS= ;;
esac
Hope that helps,
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http
On Saturday 10 December 2011 11:27:35 Bob Snyder wrote:
On 12/10/2011 12:51 AM, Eugen Wissner wrote:
2011/12/10 Bob Snyder bob.sny...@cox.net
When building lilypond (with sbopkg) I get the following
error:
ERROR: Please install required programs: mf-nowin mf
mfw
':
lwgeom_accum.c:110: error: 'WindowAggState' has no member named 'wincontext'
make[1]: *** [lwgeom_accum.o] Error 1
make[1]: Leaving directory /tmp/SBo/postgis-1.4.0/postgis'
make: *** [postgis] Error 2
Guidance on what to do to build this package is appreciated.
--
Rob McGee - /dev/rob0 - r
?
It's not Niels. It's Michiel. We have suspected it all along, and
have known it for quite some time. I'm afraid is is too late now.
Relax and cooperate with him; he might not hurt you.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds
,
but surely the Exim mailer logged it. If you're the omnitude.net
postmaster, you'll have to try to figure it out.
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http
.
But that comes out wrong if being built for a different machine,
which could easily be the case. Perhaps augment it with a check of
the variable:
if [ -z $SSE2 ] ; then true
elif grep -wq sse2 /proc/cpuinfo ; then ...
--
Rob McGee - /dev/rob0 - r...@slackbuilds.org
On Tue, May 25, 2010 at 10:02:01PM +0200, Antoine NONYME wrote:
Rob McGee:
xz is a fine tool, possibly superior to gz in every way. But it
has not been around as long. I run numerous older boxes, some of
which are not likely to get upgraded soon if ever, and sometimes
it's nice
On Tue, May 25, 2010 at 11:03:47AM -0400, Ben Mendis wrote:
On Tue, May 25, 2010 at 10:36 AM, Eugen Wissner
belka...@gmail.com wrote:
Should we use .txz as extension or $PKGTYPE variable as earlier?
I think we should still use $PKGTYPE, but the question is whether
the default should be
On Friday 28 August 2009 03:35:29 Morten Juhl-Johansen Zölde-Fejér
wrote:
Second, my Thinkpad doesn't work very well with encrypted networks
using the Ath5k driver, and so I have relied on Madwifi so far. I
see from the previous Slackbuilds-users email that Madwifi won't
build on 13.0. Any
57 matches
Mail list logo
