Date: Wed, 24 Sep 2014 04:15:21 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 193693] mail/dspam: Merge mail/dspam-devel in to mail/dspam Message-ID: <bug-193693-13-GGx7YqPU6n@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-193693-13@https.bugs.freebsd.org/bugzilla/> References: <bug-193693-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193693 danny@dannywarren.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #147461|0 |1 is obsolete| | --- Comment #7 from danny@dannywarren.com --- Created attachment 147628 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147628&action=edit dspam-merge-20140923 Here is the latest merge patch, I think we might be ready to commit at this point. This includes a small fix for an incorrect pidfile location introduced in dspam 10.3.2 upstream. I'm getting really strange results from redports, at this point I am going to assume that not seeing a major obvious build failure means that it is ok. Examples: My uncommitted patch: https://redports.org/buildarchive/20140924025042-25991/ Running test again on same code, different result from redports: https://redports.org/buildarchive/20140924035335-38166/ Known good version of mail/dspam, same random fails from redports: https://redports.org/buildarchive/20140924031800-49163/ -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-193693-13-GGx7YqPU6n>