Re: Fwd: broken strings compiled-in into mutt

2015-08-07 Thread Kurt Jaeger
Hi! > According to the mutt mailinglist: it's an issue with sed. By copying > attached file as "files/patch-txt2c.sh" to the mutt port fixes it. I will > submit an port-update in the next couple of days which also fixes other > issues. Tested this patch, works. -- p...@freebsd.org +49 1

Re: Fwd: broken strings compiled-in into mutt

2015-08-07 Thread Schweigert, Udo
According to the mutt mailinglist: it's an issue with sed. By copying attached file as "files/patch-txt2c.sh" to the mutt port fixes it. I will submit an port-update in the next couple of days which also fixes other issues. Udo On Tue, Aug 04, 2015 at 21:48:24 +0200, Kurt Jaeger wrote: > Hi! > >

Re: Fwd: broken strings compiled-in into mutt

2015-08-07 Thread Matthias Apitz
El día Friday, August 07, 2015 a las 07:51:42PM +0200, Schweigert, Udo escribió: > According to the mutt mailinglist: Yes, I know; because I nailed it down and sent it to the mutt' mailinglist :-) > it's an issue with sed. No, it's not an issue with sed itself, but with the usage of sed by some

Re: Proposal: make portsnap generate INDEX-${OSREL:R} only by default

2015-08-07 Thread Jamie Landeg-Jones
Xin Li wrote: > > I was going to suggest this too. Isn't this information available > > using /bin/freebsd-version -u ? > > Client side: yes. > > Server side: someone has to tell the server to start building for new > - -CURRENT or stop building for old -STABLE. Ahhh! Gotcha! Thanks for the qui

Re: Proposal: make portsnap generate INDEX-${OSREL:R} only by default

2015-08-07 Thread Xin Li
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 08/07/15 08:50, Jamie Landeg-Jones wrote: > Xin Li wrote: > >> On 8/6/15 22:24, Kevin Oberman wrote: >>> Or the code in portsnap could be modified to get the current >>> running version. >> >> I thought about this today but it won't work as ad

Re: Proposal: make portsnap generate INDEX-${OSREL:R} only by default

2015-08-07 Thread Jamie Landeg-Jones
Xin Li wrote: > On 8/6/15 22:24, Kevin Oberman wrote: > > Or the code in portsnap could be modified to get the current > > running version. > > I thought about this today but it won't work as advertised: someone > (currently me) still have to tweak the portsnap builder configuration > to announce

FreeBSD ports you maintain which are out of date

2015-08-07 Thread portscout
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