Re: Fwd: broken strings compiled-in into mutt
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! Hello Udo (as maintainer), Maybe it's a FreeBSD issue, rather than a mutt one? I see similar effects on 10.1-amd64. Mutt 1.5.23 (2014-03-12) Copyright (C) 1996-2009 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: FreeBSD 10.2-RC2 (amd64) ncurses: ncurses 5.7.20081102 (compiled with 5.7) libiconv: 1.14 libidn: 1.31 (compiled with 1.29) Compiler: F eeBSD clang ve sion 3.4.1 ( ags/RELEASE_34/do 1-final 208032) 20140512 Ta ge: x86_64-unknown-f eebsd10.1 Th ead model: posix Selec ed GCC ins allaion: cc: wa ning: a gumen unused du ing compila ion: '-I /us /local/include' Configure options: '--disable-fcn l' '--wih-ssl=/us ' '--wi h-docdi =/us /local/sha e/doc/mu ' '--sysconfdi =/us /local/e c' '--enable-ex e nal-dolock' '--enable-pop' '--enable-imap' '--disable-wa nings' '--disable-flock' '--wih-libiconv-p efix=/us /local' '--wi h-idn' '--disable-gpgme' '--enable-sm p' '--enable-debug' '--enable-comp essed' '--disable-hcache' '--p efix=/us /local' '--locals a edi =/va ' '--mandi =/us /local/man' '--infodi =/us /local/info/' '--build=amd64-po bld-f eebsd10.1' 'build_alias=amd64-po bld-f eebsd10.1' 'CC=cc -I/us /local/include' 'CFLAGS=-pipe -g -fsack-p o ec o -fno-s ic-aliasing' 'LDFLAGS= -L/us /local/lib -Wl,- pah=/us /local/lib:/us /lib -l infow -Wl,- pah=/us /lib:/us /local/lib -fsack-p o ec o ' 'LIBS=' 'CPPFLAGS=' 'CPP=cpp' Compilation CFLAGS: -pipe -g -fsack-p o ec o -fno-s ic-aliasing Compile options: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP +USE_SMTP +USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL -USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +COMPRESSED +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID -USE_HCACHE -ISPELL SENDMAIL=/usr/sbin/sendmail MAILPATH=/var/mail PKGDATADIR=/usr/local/share/mutt SYSCONFDIR=/usr/local/etc EXECSHELL=/bin/sh -MIXMASTER To contact the developers, please mail to mutt-...@mutt.org. To report a bug, please visit http://bugs.mutt.org/. patch-1.5.4.cd.ifdef.1 patch-1.5.0.ats.date_conditional.1 dgc.deepif.1 vvv.quote vvv.initials rr.compressed -- p...@opsec.eu+49 171 3101372 5 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Tr: mutt port broken with SLANG option [was mutt ports broke portupgrade]
Hi Thierry,
thanks a lot for that, I'm of cause completely OK with it.
Udo
On Wed, Feb 05, 2014 at 10:09:51 +0100, Thierry Thomas wrote:
Hello Udo,
I just committed a quick fix for this problem.
Could you please check it?
Thanks.
Le mer 5 fév 14 à 2:31:35 +0100, Bryan Drewery bdrew...@freebsd.org
écrivait :
On 2/4/2014 5:24 PM, Albert Shih wrote:
hi all,
mutt ports broke portuprade in the last update
[root@ /root]# portupgrade --all
[Reading data from pkg(8) ... - 886 packages found - done]
[Updating the portsdb format:dbm_hash in /usr/ports ... - 24579 port
entries found
.1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000.16000.17000.18000.19000.2.21000.22000.23000.24000.
. done]
Makefile, line 441: Unassociated shell command @${ECHO}
= ${PKGMESSAGE}
Makefile, line 442: Unassociated shell command @${ECHO} You have
installed ${PORTNAME} with SLANG support. ${PKGMESSAGE}
Makefile, line 443: Unassociated shell command @${ECHO} This may work
for a color terminal only when defining ${PKGMESSAGE}
Makefile, line 444: Unassociated shell command @${ECHO} COLORTERM=yes
and COLORFGBG=\color1;color2\ in your ${PKGMESSAGE}
Makefile, line 445: Unassociated shell command @${ECHO} environment.
${PKGMESSAGE}
Makefile, line 446: Unassociated shell command @${ECHO}
= ${PKGMESSAGE}
make: fatal errors encountered -- cannot continue
** Makefile possibly broken: mail/mutt:
** Please report this to the maintainer for mail/mutt
/usr/local/sbin/portupgrade:1580:in `get_pkgname': Makefile broken
(MakefileBrokenError)
from /usr/local/sbin/portupgrade:642:in `block (4 levels) in main'
from /usr/local/sbin/portupgrade:626:in `each'
from /usr/local/sbin/portupgrade:626:in `block (3 levels) in main'
from /usr/local/sbin/portupgrade:599:in `catch'
from /usr/local/sbin/portupgrade:599:in `block (2 levels) in main'
from /usr/local/lib/ruby/2.0/optparse.rb:1408:in `call'
from /usr/local/lib/ruby/2.0/optparse.rb:1408:in `block (2
levels) in parse_in_order'
from /usr/local/lib/ruby/2.0/optparse.rb:1403:in `catch'
from /usr/local/lib/ruby/2.0/optparse.rb:1403:in `block in
parse_in_order'
from /usr/local/lib/ruby/2.0/optparse.rb:1351:in `catch'
from /usr/local/lib/ruby/2.0/optparse.rb:1351:in `parse_in_order'
from /usr/local/lib/ruby/2.0/optparse.rb:1345:in `order!'
from /usr/local/lib/ruby/2.0/optparse.rb:1337:in `order'
from /usr/local/sbin/portupgrade:576:in `block in main'
from /usr/local/lib/ruby/2.0/optparse.rb:885:in `initialize'
from /usr/local/sbin/portupgrade:237:in `new'
from /usr/local/sbin/portupgrade:237:in `main'
from /usr/local/sbin/portupgrade:2371:in `main'
Regards.
JAS
It's more than just portupgrade, the port is broken when you select the
SLANG option.
This block of code needs some help. The ECHO lines used to be in
post-install but are now orphaned, and the PKGMESSAGE seems orphaned
too, I can't find the actual file.
.if ${PORT_OPTIONS:MSLANG}
PKGMESSAGE= ${WRKDIR}/pkg-message
@${ECHO} =
${PKGMESSAGE}
@${ECHO} You have installed ${PORTNAME} with SLANG support.
${PKGMESSAGE}
@${ECHO} This may work for a color terminal only when defining
${PKGMESSAGE}
@${ECHO} COLORTERM=yes and COLORFGBG=\color1;color2\ in your
${PKGMESSAGE}
@${ECHO} environment. ${PKGMESSAGE}
@${ECHO} =
${PKGMESSAGE}
.endif
--
Regards,
Bryan Drewery
--
Th. Thomas.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mutt sidebar patch fails after 1.5.22
A patch to solve this has already been submitted, just waiting for confirmation and svn commit, cf. PR ports/183251. Udo On Sun, Oct 27, 2013 at 01:59:13 +0900, Koichiro IWAO wrote: Hello, After recent update to 1.5.22, sidebar patch fails. [meta@icepick /usr/ports/mail/mutt]$ sudo make patch === Found saved configuration for mutt-1.5.22 === mutt-1.5.22 depends on file: /usr/local/sbin/pkg - found === Fetching all distfiles required by mutt-1.5.22 for building === Extracting for mutt-1.5.22 = SHA256 Checksum OK for mutt/mutt-1.5.22.tar.gz. = SHA256 Checksum OK for mutt/patch-1.5.22.rr.compressed.gz. = SHA256 Checksum OK for mutt/patch-1.5.22.vvv.initials.gz. = SHA256 Checksum OK for mutt/patch-1.5.22.vvv.quote.gz. === Patching for mutt-1.5.22 === Applying distribution patches for mutt-1.5.22 === Applying FreeBSD patches for mutt-1.5.22 1 out of 5 hunks failed--saving rejects to buffy.c.rej 1 out of 9 hunks failed--saving rejects to curs_main.c.rej 1 out of 3 hunks failed--saving rejects to Makefile.in.rej 5 out of 10 hunks failed--saving rejects to menu.c.rej 2 out of 8 hunks failed--saving rejects to pager.c.rej 3 out of 11 hunks failed--saving rejects to compose.c.rej *** [post-patch] Error code 13 Stop in /usr/ports/mail/mutt. *** [patch] Error code 1 Stop in /usr/ports/mail/mutt. -- `whois vmeta.jp | nkf -w` meta m...@vmeta.jp ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Failing to build mutt-devel-lite
I have already submitted a fix for this problem caused by the openssl port: http://www.freebsd.org/cgi/query-pr.cgi?pr=146261 Just wait until it is committed or just apply it yourself. Udo On Tue, May 04, 2010 at 10:54:21 +0200, Benjamin Stier wrote: Hey ports@, I'm trying to build mail/mutt-devel-lite on FreeBSD 7.2-RELEASE-p4. My makeoptions are WITH_MUTT_SMTP=yes WITH_MUTT_IMAP_HEADER_CACHE=yes WITH_MUTT_CYRUS_SASL2=yes WITH_MUTT_SIDEBAR_PATCH=yes make always fails with the following output: === Building for mutt-devel-lite-1.5.20_3 make all-recursive Making all in m4 Making all in po Making all in intl Making all in contrib Making all in imap Making all in . cc -I/usr/local/include -DPKGDATADIR=\/usr/local/share/mutt\ -DSYSCONFDIR=\/usr/local/etc\ -DBINDIR=\/usr/local/bin\ -DMUTTLOCALEDIR=\/usr/local/share/locale\ -DHAVE_CONFIG_H=1 -I. -I. -I. -I./imap -Iintl -I/usr/include -I/usr/local/include -I/usr/local/include -I./intl -O2 -fno-strict-aliasing -pipe -MT mutt_ssl.o -MD -MP -MF .deps/mutt_ssl.Tpo -c -o mutt_ssl.o mutt_ssl.c mutt_ssl.c: In function 'check_host': mutt_ssl.c:655: error: 'STACK' undeclared (first use in this function) mutt_ssl.c:655: error: (Each undeclared identifier is reported only once mutt_ssl.c:655: error: for each function it appears in.) mutt_ssl.c:655: error: 'subj_alt_names' undeclared (first use in this function) mutt_ssl.c: In function 'ssl_cache_trusted_cert': mutt_ssl.c:738: warning: assignment from incompatible pointer type *** Error code 1 Any idea how to fix this? Kind regards, Benjamin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: nessus-2.2.9_1
No, there are no further updates as 2.2.9 is the last open source version. Udo On Tue, Jun 16, 2009 at 12:16:54 -0500, phillip.gonza...@metavante.com wrote: hi, i'm looking at the nessus port on one of my FreeBSD boxes(recently updated ports tree) and it looks like it's at version 2.2.9. has this port not been updated or am i missing something? thanks for your time, Phillip P Gonzalez Information Security Analyst Sr. Security Analysis and Testing Metavante Corporation tel: 414.357.3156 - This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
