You are not logged in.
I had a working setup and decided to patch it with the sidebar patch. The compilation screwed up the flags for some reason and when launching mutt I get this error:
Error in /home/hiro/.mutt/muttrc, line 7: imap_user: unknown variable
Error in /home/hiro/.mutt/muttrc, line 8: imap_pass: unknown variable
Error in /home/hiro/.mutt/muttrc, line 9: smtp_url: unknown variable
Error in /home/hiro/.mutt/muttrc, line 42: imap_passive: unknown variable
Error in /home/hiro/.mutt/muttrc, line 43: imap_keepalive: unknown variable
Error in /home/hiro/.mutt/muttrc, line 71: ssl_force_tls: unknown variable
Error in /home/hiro/.mutt/muttrc, line 72: ssl_starttls: unknown variable
source: errors in /home/hiro/.mutt/muttrc
Press any key to continue...I reinstalled mutt being unable to determine the problem. The problem persists.
The article here describes the same issue and identifies it as the install failing to activate the compile options. The solution presented is to change the flag options before compiling but this person is on Gentoo and I don't see why $ pacman -S mutt won't suffice.
As expected $ mutt -v reads:
Mutt 1.5.21 (2010-09-15)
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: Linux 3.8.6-1-ARCH (x86_64)
ncurses: ncurses 5.9.20110404 (compiled with 5.9)
libidn: 1.26 (compiled with 1.26)
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
+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="/usr/bin/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-dev@mutt.org>.
To report a bug, please visit http://bugs.mutt.org/.
patch-1.5.21.sidebar.20130219.txtSo options like IMAP aren't activated for some reason even after pulling the mutt package from the official repositories. The sidebar patch is listed above so that is fishy. I don't know how to unpatch and I am thinking that may be the next step to try if I can figure that out.
I also have a full system backup so another route may be to replace the necessary directories and files with the backups. Any ideas? I appreciate the support.
Last edited by Divinorum (2013-04-16 11:13:28)
Offline
As expected $ mutt -v reads:
.... To contact the developers, please mail to <mutt-dev@mutt.org>. To report a bug, please visit http://bugs.mutt.org/. patch-1.5.21.sidebar.20130219.txt <----?
You seem to still have the sidebar version installed...
Offline
Rightly so and I didn't think the patch would make pacman treat mutt differently. That is, I thought running $ pacman -Rs mutt would get rid of it but obviously not.
It's probably an easy fix but how would I go about uninstalling the patched version? I reviewed the Lunar Linux website where the patch is made available but there is not documentation on how to unstall. So far I have tried $ pacman -R mutt-1.5.21 and the sort.
Last edited by Divinorum (2013-04-15 23:36:57)
Offline
I agree the patch doesn't seem to have any impact on mutt's compile options. If you installed it from the AUR, then pacman -R should remove it.
FWIW, my mutt from [extra] has the correct flags...
Offline
Yes, this all depends on how you installed the patched mutt in the first place. a "pacman -Rs mutt" would definitely uninstall mutt from the official repos, but not someting you installed with a simple "./configure make make install"
FWIW, I use uber-mutt from the AUR. It is maintained by falconindy and is quite nice. There are a number of patched mutt packages available in the AUR though.
Offline
The patch from the AUR did not yield any result so I followed the wiki entry on mutt to the patch provided on Lunar Linux. I had removed the directory with the patched compilation before discovering this error. Like the previous patch from the AUR I could not get it to work so I went about reinstalling mutt and ran into this problem.
Perhaps I should just hack it by ingnoring the patch and having a custom command point to the vanilla repository install. As of now $ mutt still brings up the patch version of mutt but I can't find where it is and how to remove it.
Much appreciated on the recommendation of uber-mutt. So in ,/configure case how does one normally go about removing such an install? I can not locate any mutt or patch name on my system by the name of sidebar.
Last edited by Divinorum (2013-04-16 00:15:25)
Offline
Well... that is why we use a package manager for these things... to track packages. IF you install with the traditional ./configure -> make -> make install method, you had better hope that upstream provides a nice way for uninstalling the files. But this is not always the case. So if you did it that way, you are going to have to find where these files were installed to from the make file and then take them out by hand I think.
Does it install the mutt binary to /usr/local/bin? Because that is first in your PATH, so if that is where it goes, it will always call that first unless you give an absolute path to another mutt binary.
Offline
A lesson harshly learned. Fortunate for me mutt is not critical to my email habits but I will take this mistake to prevent me from doing so again.
The binary is in /usr/local/bin. I want to avoid digging out all the files put into the system by the patched install if possible so can I go ahead and remove that binary and move ahead with the official repository package?
I do have a full system backup from a few days ago if removing the individual files is too great of a task.
Offline
Install the mutt package from the repos. Then use "pacman -Ql mutt" to get an output of the package contents. There are quite a few files, but mostly in just a few directories. I am sure a bit of simple globbing might make the process easier and faster.
Alternatively, I know that vim can look into the contents of a tar.gz file. Just do "vim mutt-whatever-version-pkg.tar.gz" and it will show you the contents.
Now with the patches and configuration flags, there is no gaurantee that is is the same as the package. Also if it installed in /usr/local/bin, I am assuming that all the files will not be in /usr/share like the package, but /usr/local/share, since that corresponds to the /usr/local/bin directory.
Offline
Thank you, that was the breakthrough I needed. The files were removed and I installed uber-mutt from the AUR. Now I'll need to play around with the configuration for the patches. Is the trash patch included in uber-mutt?
I learned a lot from this so I appreciate it!
Offline
The patches are listed on the AUR page:
https://aur.archlinux.org/packages/uber-mutt/
Offline
Also, you should know that the reason that those variables were unrecognized when you compiled is because you had these flags set:
<snip>
-USE_IMAP -USE_SMTP
-USE_SSL_OPENSSL -USE_SSL_GNUTLS
<snip>Of course, they should have been +USE_IMAP +USE_SMTP etc.
Interestingly, you also had -USE_POP set, so it makes me wonder what you could actually even use it for t that point.
If you are satisfied with the outcome of this thread, please mark it as [Solved]. This can be done by editing the first post.
Offline