Qmail-LDAP
[Top] [All Lists]

Fail to patch qmail-1.03-20060201.patch with qmail-ldap patch and qmail-

To: qmail-ldap@qmail-ldap.org
Subject: Fail to patch qmail-1.03-20060201.patch with qmail-ldap patch and qmail-1.03-jms1.6c5.patch
From: "sato x" <gladiol4@gmail.com>
Date: Tue, 13 Feb 2007 11:15:08 +0700
Delivered-to: sp-com-lists@consult.net
Delivered-to: qmail-ldap-list@securepoint.com
Delivered-to: mailing list qmail-ldap@qmail-ldap.org
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=B30YVgetYGbpx5vAulsDYF1wfx5eACJUYwAGG8RFAwi/f9LNKtdKX08yjbKN0UpEQrMHfSde9mahMzRnXc6MH4koJrYg2zgH9gwqsRmrrpjq+tnZ0T/TZIZvFJ6EqlqkzNKhxkk5m8EXOLUj78SWHSu0ZK2tX2594QIcK5/j6do=
Mailing-list: contact qmail-ldap-help@qmail-ldap.org; run by ezmlm
Dear guys,
I've patched a clean qmail-1.03 source code with qmail-ldap-1.03-20060201.patch in Fedore Core 3 and it succeed.  But later I failed to patch it again with qmail-1.03-jms1.6c5.patch (or even just the ext_todo-20030105.patch) from www.jms1.net. What come into my question are:
- is it possible to patch qmail-1.03 that way? (patching a qmail-ldap-patched qmail-1.03 source code with the big combined patch from jms1.net or vice-versa - patching it with jms1.net patch before qmail-ldap-1.03-20060201 patch)
- does qmail-ldap-1.03-20060201 include all (or maybe just some ) patches from jms1.net?
- is it safe to run a qmail-ldap server without patching it with ext_todo-20030105.patch on a busy mail server?

Below is a sort of the message:

qmail-1.03># patch < ../qmail-1.03-jms1.6c5.patch
  The next patch would create the file EXTTODO, which already exists!
  Assume -R? [n] n
  Apply anyway? [n] y
  Patch attempted to create file EXTTODO, which already exists.
  Hunk #1 FAILED at 1
  ...
  14 out of 28 hunks FAILED -- saving rejects to file Makefile.rej
  ... # etc ...

If anyone ever resolved it before, please share some information with me (us). Thank you in advance for your kindness and sorry for the language.

Best regards,

sato


<Prev in Thread] Current Thread [Next in Thread>