public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 0/6] Update for Berkeley DB
Date: Wed, 15 Jul 2015 15:40:55 +0200	[thread overview]
Message-ID: <1436967661-17353-1-git-send-email-michael.tremer@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2456 bytes --]

This is a patchset that updates the Berkeley DB package in IPFire 2.

It was developed by Erik with the Mail Relay project and I
cherry-picked the changed from that branch that just update
the berkeley package.

However some things do not build, yet. There are several packages
that do not build properly (e.g. cyrus-imapd) which need to be
fixed first. The original branch updates the cyrus-imapd package,
but that is not applicable to be done for this branch. We intend
to ship the massive amount of changes of the mail relay branch
one by one.

So I am sending this to the list as a RFC and would like to
ask the people who are working on the mail proxy feature to
take care of these patches and make the entire branch build.

The packages that FTBFS must be fixed and if there are any
databases that need to be converted when changing berkeley
db, that needs to be done in the package scriptlets as well.

You can also pull these patches from:

  git://git.ipfire.org/people/ms/ipfire-2.x.git berkley-db-update

Best,
-Michael

Erik Kapfer (5):
  berkeley: Update berkeley database to version 6.1.26
  BerkeleyDB: Update berkely DB perl module to 0.55
  php: Fix build with db6
  squidguard: Fix build with db6
  openldap: Update to 2.4.40

Michael Tremer (1):
  postfix: Fix build with db6

 config/rootfiles/common/BerkeleyDB               |    3 +-
 config/rootfiles/common/berkeley                 | 7073 +++++++++++++++++-----
 config/rootfiles/common/openldap                 |  626 +-
 lfs/BerkeleyDB                                   |    9 +-
 lfs/berkeley                                     |   25 +-
 lfs/openldap                                     |   28 +-
 lfs/php                                          |   84 +-
 lfs/postfix                                      |    1 +
 lfs/squidguard                                   |    1 +
 src/patches/openldap-2.4.40-consolidated-1.patch |  399 ++
 src/patches/php-5.3.27_db6.patch                 |   66 +
 src/patches/postfix-2.10-db6.patch               |   11 +
 src/patches/squidguard-1.4.1-db6.patch           |   15 +
 13 files changed, 6452 insertions(+), 1889 deletions(-)
 create mode 100644 src/patches/openldap-2.4.40-consolidated-1.patch
 create mode 100644 src/patches/php-5.3.27_db6.patch
 create mode 100644 src/patches/postfix-2.10-db6.patch
 create mode 100644 src/patches/squidguard-1.4.1-db6.patch

-- 
2.4.3


             reply	other threads:[~2015-07-15 13:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 13:40 Michael Tremer [this message]
2015-07-15 13:40 ` [PATCH 1/6] berkeley: Update berkeley database to version 6.1.26 Michael Tremer
2015-07-15 13:40 ` [PATCH 2/6] BerkeleyDB: Update berkely DB perl module to 0.55 Michael Tremer
2015-07-15 13:40 ` [PATCH 3/6] php: Fix build with db6 Michael Tremer
2015-07-15 13:40 ` [PATCH 4/6] squidguard: " Michael Tremer
2015-07-15 13:41 ` [PATCH 5/6] openldap: Update to 2.4.40 Michael Tremer
2015-07-15 13:41 ` [PATCH 6/6] postfix: Fix build with db6 Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1436967661-17353-1-git-send-email-michael.tremer@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox