Bug#705647: mailavenger: Missing SASL support and macutil
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/01/15 05:10, Philip Hands wrote: > Hi Dererk, > > Dererk writes: > >> Agreed to everything said. >> >> Not to excuse myself, but the reason why I originally removed this >> functionality was, mostly, because lack of testing env, and 580397 >> trigger no real interest on conserve it. > > Ah, I see -- so that was a fix for that conflict? Not at all, as I said, this was more like the last reason for me to remove it :-) > The comment didn't > really allow me to guess that ;-) Sorry about that, wasn't intended. >> That said, preparing the next upload... > > Fair enough. > > BTW would it be possible to add this to jessie-backports? (or at least > build it against jessie libraries so it's not too hard for people to > grab it from unstable). > > Actually, while I doubt that fixing this would be accepted into jessie, > perhaps adding a note to the jessie version's README saying that it was > fixed later would be -- is that worth doing? I think that something in > the README would have saved me from hunting for it. I'm definitely interested, unfortunately, I'm not really sure whether that backports FTP-masters would allow a backport that has never been at Testing at all. Usually on normal situations (i.e., not during freeze time), they require at least 10 days for accepting packages into backports. We can try requesting a freeze exception. What do you think? I've checked and seems to build nicely on Jessie, which makes sense. I'm up to ideas! Cheers, Dererk - -- BOFH excuse #82: Yeah, yo mama dresses you funny and you need a mouse to delete files. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUqyRrAAoJEGin9OG0lUUKEMsQAKyxPVfk0lm3TUpg1GmZgJyd CnzDBcNf/ee5xjKXau13lfKqWHTKOHDQF0sM8/6CoOuEKZB5Y7iHxxjLvyhBhG7n tcHJWhf8HrQsTRMepyKacehiQb7zw92kyO+j4xVi14tlKG/s6AujX3rJLdUE8Kee XX34Z2iGAoT9mAMb4lIB0fqwgtE51rpqdbOZZ1y023VoQOlhL7+Rz4+gTl0sU7xS KJ6JdcBIUtU5n+Jp4pAsGpzn2Uu/tqiqfjZIXHhVhxz+YiK31a2eqWPTGqBN0kuL laV4vA8+AbHs8qjbckNsOKd08FLQ+TpLu6jyK7oSLXIdJD675aPOcURsFo8JHXmD 4MszCALpNDhCZOwWnp4tJDvvUfc5bGWJgjqmYSON9sm4wKL8RudYo9aXBtErF7RP B6UTylM9Ewf0FWlX2oZ7i//12b7xrgQpdRDfKBeHUmIZXm3EiE4ET6t0y8PkaMyt rH1yGGy6CBOGbubmZTss53GlYMxismKVrNN84CUkPt0THrNpFfesxzutULyJ8wm/ gzCfIs5QYjXCAse4pW6Xga6p5Bhd6Uo5qP9Zpi4qCl7cjOoy432+OCMHKt71bkUv ujoFmdrZYRAeA8HLu/7GjCSpyEU/deZl7mz0Ol4FnBdKyXGQffuO44eUIy+kGa6T l+BMkEa1p38TDmXdnOpS =u3Tp -END PGP SIGNATURE-
Bug#705647: mailavenger: Missing SASL support and macutil
Philip Hands writes: > I guess you should get macutils to do that, and then do a versioned > depends. s/depends/conflicts/ pgpv0eOiSThIy.pgp Description: PGP signature
Bug#705647: mailavenger: Missing SASL support and macutil
Hi Dererk, Dererk writes: > Agreed to everything said. > > Not to excuse myself, but the reason why I originally removed this > functionality was, mostly, because lack of testing env, and 580397 > trigger no real interest on conserve it. Ah, I see -- so that was a fix for that conflict? The comment didn't really allow me to guess that ;-) BTW the correct fix for that bug would probably be to rename the macutil man page. Especially since macutils does not ship a command called macutil (so it seems a bit odd to have a section 1 man page called that in the first place). The simplest fix would seem to be to move the other package's man page to section 7 (which seems like e.g. gnupg(7)). I'd suggest also renaming it to be macutils at the same time, since that is actually the package name that it's supposed to be documenting. Alternatively, given that it includes: BUGS This manual page is hopelessly incomplete! it could be simply removed, but renaming it and putting it in a different section fixes 580397 and still allows it to be found easily without needing to specify the section. I guess you should get macutils to do that, and then do a versioned depends. In the mean time you could just put your man page in section 8 for now. > If there is someone requesting this feature, I'll gladly re-enable! In case it was not clear, I'm requesting it. :-) > That said, preparing the next upload... Fair enough. BTW would it be possible to add this to jessie-backports? (or at least build it against jessie libraries so it's not too hard for people to grab it from unstable). Actually, while I doubt that fixing this would be accepted into jessie, perhaps adding a note to the jessie version's README saying that it was fixed later would be -- is that worth doing? I think that something in the README would have saved me from hunting for it. Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg,GERMANY pgp7hcpoZxt7K.pgp Description: PGP signature
Bug#705647: mailavenger: Missing SASL support and macutil
Agreed to everything said. Not to excuse myself, but the reason why I originally removed this functionality was, mostly, because lack of testing env, and 580397 trigger no real interest on conserve it. If there is someone requesting this feature, I'll gladly re-enable! That said, preparing the next upload... Cheers, Dererk -- BOFH excuse #82: Yeah, yo mama dresses you funny and you need a mouse to delete files. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#705647: mailavenger: Missing SASL support and macutil
Package: mailavenger Version: 0.8.3rc1-1 Followup-For: Bug #705647 Hi Dererk, I installed this package a couple of days before the freeze. Ata ny other time I'd have just done a delayed NMU with this bug fixed, since you seem to be OK with fixing it, but have obviously overlooked it. I think it's a bit of a shame that you didn't bother to mention in the README that you'd stripped out the macutil stuff, especially since you've left the man pages untouched, so that avenger(1) has a SEE ALSO that refers to macutil(1) which then (after searching around for some time) turns out to not exist in Debian -- which strike one as a bit odd. I must say that when I eventually found the: don't really need MAC stuff in our free world =) comment, I wasn't greatly pleased. BTW is there something non-free about the macutil? I fail to see what. Anyway, since then I set things up without using macutil to protect my bounces, and find that my fake bounce problem has almost completely disapeared due to SPF, so I'm much less vexed about the lack of macutil now, and the time wasted on looking for it has almost certianly been more than compensated for with the time not spent setting it up :-) Perhaps you could at least ddocument it in the next upload? I think you should just remove your patch though (as you seemed to intend originally). Cheers, Phil. -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/3 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mailavenger depends on: ii adduser 3.113+nmu3 ii libc6 2.13-38+deb7u6 ii libdb5.15.1.29-5 ii libgcc1 1:4.7.2-5 ii libpcap0.8 1.3.0-1 ii libssl1.0.0 1.0.1e-2+deb7u13 ii libstdc++6 4.7.2-5 ii lsb-base4.1+Debian8+deb7u1 ii postfix [mail-transport-agent] 2.9.6-2 mailavenger recommends no packages. mailavenger suggests no packages. -- Configuration Files: /etc/avenger/asmtpd.conf changed [not included] /etc/avenger/unknown changed [not included] /etc/default/mailavenger changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#705647: mailavenger: Missing SASL support and macutil
severity 705647 normal thanks On 17/04/13 22:03, Alex Z wrote: > Package: mailavenger > Version: 0.8.3rc1-1 > Severity: important > > Hi all. I've found several issues need to be fixed in package. > > According to http://www.mailavenger.org/macutil.html: > > "macutil, sendmac − Message Authentication Code utility" > > Messages during build process: > 8< > # don't really need MAC stuff in our free world =) > rm > /home/alex/assembly/mailavenger/mailavenger-0.8.3rc1/debian/mailavenger/usr/bin/sendmac > rm > /home/alex/assembly/mailavenger/mailavenger-0.8.3rc1/debian/mailavenger/usr/bin/macutil > rm > /home/alex/assembly/mailavenger/mailavenger-0.8.3rc1/debian/mailavenger/usr/share/man/man1/macutil.1 > 8< > > wait, what? > > > > The second issue is more complicated. > > First of all, you missed build dependency: libsasl2-dev. But this is only one > of lacks. Hi Alex Z! What you experienced is, basically, a functionality I silently opted-out from mailavenger, sorry about that. It's a satellite functionality at the moment I package this was not really interested in, although I didn't remove the reference to this functionality from the pkg description, what's wrong... Since this is basically a 'request feature', I plan to add support for it, even though I don't use it myself. As I explained, this is an isolated functionality that is not broken but disabled. Having explain that, I'm downgrading this to normal and not wishlist because of the undocumented reference of this feature being disabled. Thanks for reporting this. Cheers, Dererk -- BOFH excuse #97: Small animal kamikaze attack on power supplies signature.asc Description: OpenPGP digital signature
Bug#705647: mailavenger: Missing SASL support and macutil
Package: mailavenger Version: 0.8.3rc1-1 Severity: important Hi all. I've found several issues need to be fixed in package. According to http://www.mailavenger.org/macutil.html: "macutil, sendmac − Message Authentication Code utility" Messages during build process: 8< # don't really need MAC stuff in our free world =) rm /home/alex/assembly/mailavenger/mailavenger-0.8.3rc1/debian/mailavenger/usr/bin/sendmac rm /home/alex/assembly/mailavenger/mailavenger-0.8.3rc1/debian/mailavenger/usr/bin/macutil rm /home/alex/assembly/mailavenger/mailavenger-0.8.3rc1/debian/mailavenger/usr/share/man/man1/macutil.1 8< wait, what? The second issue is more complicated. First of all, you missed build dependency: libsasl2-dev. But this is only one of lacks. Code to check SASL support from configure.in: 8< enable_sasl=no) if test yes = "$enable_sasl"; then for dir in "$prefix" /usr/local /usr; do test -f "$dir/include/sasl/sasl.h" \ -a \( -f "$dir/lib/libsasl2.la" -o -f "$dir/lib/libsasl2.a" \) \ && sasl="$dir" && break done elif test -n "$enable_sasl" -a no != "$enable_sasl"; then sasl="$enable_sasl" fi unset LIBSASL if test -n "$sasl"; then if test -f "$dir/lib/libsasl2.la"; then LIBSASL="$dir/lib/libsasl2.la" else LIBSASL="-L$dir/lib -lsasl2" fi CPPFLAGS="$CPPFLAGS -I$sasl/include/sasl" AC_DEFINE(SASL, 1, [Define to use Cyrus libsasl2.]) fi AC_SUBST(LIBSASL) 8< On x86_64 system this library locates in "/usr/lib/x86_64-linux-gnu/libsasl2.a" On another architectures this path will be different also. So, i got the following during startup: 8< asmtpd: /etc/avenger/asmtpd.conf:108: unknown directive SASL 8< -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mailavenger depends on: ii adduser 3.113+nmu3 ii libc6 2.13-38 ii libdb5.15.1.29-5 ii libgcc1 1:4.7.2-5 ii libpcap0.8 1.3.0-1 ii libssl1.0.0 1.0.1e-2 ii libstdc++6 4.7.2-5 ii lsb-base4.1+Debian8 ii postfix [mail-transport-agent] 2.9.6-2 mailavenger recommends no packages. mailavenger suggests no packages. -- Configuration Files: /etc/avenger/asmtpd.conf changed [not included] /etc/avenger/unknown changed [not included] /etc/default/mailavenger changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
