Summary: | mail-mta/ssmtp-2.62-r3: cram-md5 does not work on x64 architecture. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ingo <lundril> |
Component: | Current packages | Assignee: | Net-Mail Packages <net-mail+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | lundril, nertzy |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397149 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 304069 | ||
Bug Blocks: | |||
Attachments: |
Fixes UINT5 type definition, so it works for AMD64 platform. (Should also work for 32 bit platforms!)
Fixes UINT4 type definition by using u_int32_t instead, |
Description
Ingo
2008-10-26 15:19:57 UTC
Created attachment 169938 [details, diff]
Fixes UINT5 type definition, so it works for AMD64 platform. (Should also work for 32 bit platforms!)
I think it would be a lot cleaner to use "u_int16_t" and "u_int32_t", but this would require to include "sys/types.h". Not sure if this is wanted.
Created attachment 169940 [details, diff]
Fixes UINT4 type definition by using u_int32_t instead,
This patch uses "u_int32_t" from "sys/types.h", but unfortunately this means a bigger patch.
Choose which one you like
Did you report those patches upstream? (In reply to comment #3) > Did you report those patches upstream? > Sorry for answering so late. It seems I did not get this via regular E-Mail. I didn't report this upstream. But now that you mentioned it I mailed the patch to 397149@bugs.debian.org and A.Monsalve.Salazar@IEEE.org (the Maintainer of ssmtp ?) I hope this helps ? > ...
> But now that you mentioned it I mailed the patch to
> 397149@bugs.debian.org
> and
> A.Monsalve.Salazar@IEEE.org (the Maintainer of ssmtp ?)
>
> I hope this helps ?
>
Currently there seems to be no activity upstream.
Would it be possible to just integrate this patch into gentoo ?
so long
Ingo
PS: Just updated my system and again had to apply the patch myself...
I've also encountered this issue and would like to see the patch applied to the official ebuild. This was fixed upstream for 2.64 so it's in tree now. |