(Mozilla) Thunderbird time zone issue

2019-10-25 Thread Nick Holland
Hiya. I live in EST5EDT. (actually, I normally use /usr/share/zoneinfo/right/US/Michigan ) Mozilla's Thunderbird seems to think I live in MST7MDT. All my e-mail's time stamps are off a couple hours, for both messages sent and received. In fact, the date line on my messages is, um, amusing:

Re: (Mozilla) Thunderbird time zone issue

2019-10-26 Thread Nick Holland
On 2019-10-25 17:45, Christian Weisgerber wrote: > Nick Holland: > >> I live in EST5EDT. (actually, I normally use >>/usr/share/zoneinfo/right/US/Michigan ) > ^ > I suspect this to be the trigger for your problem. You have put > yourse

Ports upgrade advisories?

2013-03-25 Thread Nick Holland
For the first time in a number of releases, I see very few [ports] notices in current.html. Did we really have a full release cycle with only one (postgresql) "exciting" package upgrades that a lot of users are going to wish they knew about? If so, great, if not, please get me proposed wording fo

Re: tweak for faq15.html

2013-05-01 Thread Nick Holland
On 05/01/13 17:23, Stuart Henderson wrote: > +CC ports > > On 2013/05/01 21:45, Maurice Janssen wrote on www@: >> The first chunk is obvious, I think. >> The second chunk is for consistency only. > > I think this page needs further tweaking; This section needs a re-working. screen? I picked tha

Re: Fix devel/cvsweb for 5.6

2014-07-26 Thread Nick Holland
On 07/26/14 06:57, Christian Weisgerber wrote: > Only overdue by four months: Fix devel/cvsweb's chroot instructions > to work with the perl version we actually ship with in 5.6. > > While here, drop some obsolete configuration examples and tweak the > default man.cgi URL. > > OK or not important

Re: Fix devel/cvsweb for 5.6

2014-07-26 Thread Nick Holland
On 07/26/14 15:43, Christian Weisgerber wrote: > On 2014-07-26, Nick Holland wrote: > >> (next I'll ask for nginx support :-D ) > > Huh? > The cvsweb port works nicely with nginx and slowcgi. I run it like > that locally. > > nginx_flags= > slowcgi_fla

Re: patch: mention wsrc in ports(7)

2014-10-22 Thread Nick Holland
On 10/22/14 06:33, Ingo Schwarze wrote: > Hi Nick, > > here is a patch better explaining sudo(8) configuration for ports. > > I'm not just asking for an OK to commit; i also hope for a cluestick > to understand what's up with faq15.html versus ports/ports.html. > Both seem largely duplicate, and

Re: unzels

2011-08-30 Thread Nick Holland
On 08/30/11 17:13, Matthias Kilian wrote: > On Tue, Aug 30, 2011 at 02:58:11PM -0600, Matt Jibson wrote: >> What does "unzels" mean? pvalchev was using "dudes" and moid provided >> the German translation? >> >> http://marc.info/?l=openbsd-ports-cvs&m=105553742412504&w=2 > > Never ask ports@ for t

upgrade45.html packages advisories

2009-03-16 Thread Nick Holland
In upgrade41.html, we introduced a "warning" section about packages with unusually traumatic upgrades. In the 4.0 -> 4.1 upgrade, (and again for 4.3 -> 4.4) postgresql required a database dump before the upgrade and a restore afterwards, if one neglected to do this, they would be hurting after ins

Re: EPIC4 perl flavor

2009-04-12 Thread Nick Holland
James Wright wrote: > Attached patch for EPIC4 adding a perl flavor which lets you run perl > scripts. Also included is 'CFLAGS+= -O0' which fixes a problem (on i386 > at least), where hitting ctl-C (to add colours), hangs EPIC. If the > latter needs to stay in my private tree until a better s

Re: EPIC4 perl flavor

2009-04-14 Thread Nick Holland
James Wright wrote: Nick Holland holland-consulting.net> writes: Does it make sense to add features to EPIC4? Scripts that depend on epic4, epic4 and epic5 do not have compatible interfaces that would certainly be an issue... There's a nasty bug in EPIC4 which causes epic to

Re: EPIC4 perl flavor

2009-04-14 Thread Nick Holland
Stuart Henderson wrote: > On 2009/04/14 11:08, Nick Holland wrote: >> It is really easy to reproduce...in X, ssh to machine with Epic, start >> Epic4 in an xterm, now resize the x-term. Boom. Epic4 is now locked, >> and soaking all available CPU time. > > I can r

Re: Update: postgresql 8.4.0

2009-07-22 Thread Nick Holland
Henning Brauer wrote: > * Jason Dixon [2009-07-21 23:06]: ... [postgresql needs a dump and reload as part of upgrade] ... >> Reasonable solution (examples): >> >> http://marc.info/?l=openbsd-ports-cvs&m=120637961514930&w=2 >> http://marc.info/?l=openbsd-misc&m=120631560919405&w=2 >> http://undead

current.html now including ports issues (was Re: Update: postgresql 8.4.0)

2009-07-23 Thread Nick Holland
Stuart Henderson wrote: > On 2009/07/22 22:09, Nick Holland wrote: >> Henning Brauer wrote: >> > >> > the upgrade47.html entry is the most important really. >> >> I'm inclined to agree. I may be biased, but really...a mail list >> or chat board

Re: Building X11, was: Re: expat dependencies

2007-10-23 Thread Nick Holland
Toni Mueller wrote: > Hi, > > On Tue, 23.10.2007 at 10:50:12 +0200, Toni Mueller <[EMAIL PROTECTED]> wrote: >> IOW, I'll have to fiddle with it to get the expat port compile in order >> to subsequently avoid installing xbase which I can't compile. How do >> you guys actually bootstrap it? > > tha

upgrade43.html packages advisories?

2008-03-29 Thread Nick Holland
In upgrade41.html, we introduced a "warning" section about packages with unusually traumatic upgrades. In the 4.0 -> 4.1 upgrade, (and for 4.3 -> 4.4, apparently) postgresql required a database dump before the upgrade and a restore afterwards, if one neglected to do this, they would be hurting aft

Re: Modifying software written to a "Standards" document - was Re: DRM in xpdf

2008-04-25 Thread Nick Holland
Ian McWilliam wrote: ... > Can anybody explain why is it acceptable to modify a "standard" for > "ports" but not not for "base"? I think "Standards" is a bogus argument here. That's not what this is about. Try this way of looking at it: The author of xpdf wants DRM in the source code. That is

Re: DJBware ports

2008-06-30 Thread Nick Holland
Eduardo Alvarenga wrote: > Hi guys, > > I'm willing to port all DJB's public domain software, including djbdns, > qmail, daemontools, etc. > If made, It can be easily accepted on ports or, for historical reasons, i > will not be imported? I'm not a porter, I don't have final say in this at all, b

Re: DJBware ports

2008-07-01 Thread Nick Holland
Vadim Zhukov wrote: 1 July 2008 ?. 13:55:46 Stuart Henderson wrote: On 2008/07/01 11:21, Roberto FERNANDEZ wrote: Don't know if my vote counts but here it is. normalize +1 daemontools dependency -1 Then it wouldn't be DJBDNS, and you are going against the author's wishes, and you are making t

upgrade44.html packages advisories

2008-08-16 Thread Nick Holland
In upgrade41.html, we introduced a "warning" section about packages with unusually traumatic upgrades. In the 4.0 -> 4.1 upgrade, (and I recall something about this again for 4.3 -> 4.4) postgresql required a database dump before the upgrade and a restore afterwards, if one neglected to do this, t

upgrade42.html packages advisories?

2007-10-10 Thread Nick Holland
In upgrade41.html, we introduced a "warning" section about packages with unusually traumatic upgrades. In the 4.0 -> 4.1 upgrade, postgresql required a database dump before the upgrade and a restore afterwards, if one neglected to do this, they would be hurting after installing the new version. I

Re: Thunderbird performance

2009-09-26 Thread Nick Holland
Edward Ahlsen-Girard wrote: > It seems to me that Thunderbird 2.0.0.23 performance on the 9/21 > snapshot is pretty bad. What I see is a lag of minutes before > downloaded messages actually display. I have one account delivering to > the Local folders. Under the 9/17 snapshot the message down

Re: [Update] Dovecot 1.2.1 with Managesieve

2009-10-07 Thread Nick Holland
Matthew Weigel wrote: > Pierre-Emmanuel André wrote: > >>> You must be very carefull if you want to try this update ! > > I think this information should get wider distribution; I would favor > something in MESSAGE-server linking to > http://wiki.dovecot.org/Upgrading/1.2 - it's too late for pe

upgrade46.html packages advisories

2009-10-07 Thread Nick Holland
In upgrade41.html, we introduced a "warning" section about packages with unusually traumatic upgrades. In the 4.0 -> 4.1 upgrade, (and again for 4.3 -> 4.4) postgresql required a database dump before the upgrade and a restore afterwards, if one neglected to do this, they would be hurting after ins