This bug was fixed in the package postgrey - 1.32-5ubuntu0.1
---
postgrey (1.32-5ubuntu0.1) maverick-proposed; urgency=low
* Drop preinst and thus dependency on dbutil-4.7. (LP: #537472)
-- Stefano RiveraSun, 19 Dec 2010 07:01:15 +
** Changed in: postgrey (Ubuntu Maverick)
** Tags added: verification-done
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/537472
Title:
upgrade from hardy to lucid fails
--
ubuntu-bugs mailing list
ubun
Martin: I was testing with local build result, but I've fired up a VM
and verified that the maverick-proposed debs upgrade from maverick and
run as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Stefano, are you using the debs from maverick-proposed or a local build?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/537472
Title:
upgrade from hardy to lucid fails
--
ubuntu-bugs mailing list
u
I obviously tested the upgrade path when I prepared the patch, I'm
pretty sure it works. Although the SRU testing does obviously benefit
from * independent* verification :P
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Quick note: I installed the lucid-proposed postgrey *after* encountering
and working around the original bug, so I've verified that the new
package works (no compiler/linker/library issues etc.) but I haven't
verified that the new postinst script handles the upgrades correctly.
I've another Hardy
** Tags removed: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/537472
Title:
upgrade from hardy to lucid fails
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
On Tue, 2011-01-25 at 14:25 +, Martin Pitt wrote:
>
> Only very few people have -proposed enabled,
While everything is working, yes, I agree.
> so there they aren't a
> real benefit.
There is when somebody has discovered that something is broken and
either goes looking for a bug and discov
This bug was fixed in the package postgrey - 1.32-4ubuntu0.1
---
postgrey (1.32-4ubuntu0.1) lucid-proposed; urgency=low
* Drop preinst and thus dependency on dbutil-4.7. (LP: #537472)
-- Stefano RiveraSun, 19 Dec 2010 07:07:06 +
** Changed in: postgrey (Ubuntu Lucid)
Thanks Marius! Leaving v-needed for the maverick proposed update.
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/537472
Title:
upgrade from hardy to lucid fails
--
Brian J. Murrell [2011-01-25 13:40 -]:
> Is there really any harm in leaving them in proposed just in case
> somebody comes to the party even later than those patches?
Only very few people have -proposed enabled, so there they aren't a
real benefit. So we must ensure that the package at least
I've installed postgrey from lucid-proposed. It works fine so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/537472
Title:
upgrade from hardy to lucid fails
--
ubuntu-bugs mailing list
ubuntu
On Tue, 2011-01-25 at 09:13 +, Martin Pitt wrote:
> Any testers of the lucid/maverick-proposed packages? As these have been
> in -proposed for nearly three months,
I suspect those patches {we,a}re too late to the party. I mean really,
we are talking about issues upgrading from n-2 to n-1. T
Any testers of the lucid/maverick-proposed packages? As these have been
in -proposed for nearly three months, I'll remove them soon if there is
no feedback. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Changed in: postgrey (Debian)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/537472
Title:
upgrade from hardy to lucid fails
--
ubuntu-bugs mailing l
** Branch linked: lp:ubuntu/maverick-proposed/postgrey
** Branch linked: lp:ubuntu/lucid-proposed/postgrey
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/537472
Title:
upgrade from hardy to lucid fa
Accepted postgrey into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
> something needs to call db_upgrade to update it to the 4.7 format.
It appears that libberkeleydb-perl handles this itself, which was why
people run into issues where it tries to upgrade to 4.7 in preinst, but
the DB is already 4.8.
--
You received this bug notification because you are a member
I fail to see how the current upload to proposed is a solution for this.
If you upgrade from hardy and thus postgrey is using a 4.6 database,
something needs to call db_upgrade to update it to the 4.7 format.
Arguably this should happen in the postinst, not in the preinst, but
completely dropping t
** Branch linked: lp:ubuntu/postgrey
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/537472
Title:
upgrade from hardy to lucid fails
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
** Changed in: postgrey (Ubuntu Lucid)
Status: New => Fix Committed
** Changed in: postgrey (Ubuntu Maverick)
Status: New => Fix Committed
** Changed in: postgrey (Ubuntu Maverick)
Importance: Undecided => Medium
** Changed in: postgrey (Ubuntu Lucid)
Importance: Undecided =>
This bug was fixed in the package postgrey - 1.32-5ubuntu1
---
postgrey (1.32-5ubuntu1) natty; urgency=low
[ Stefano Rivera ]
* Upload 1.32-6 from VCS (LP: #537472)
[ Antonio Radici ]
* Drop preinst and thus dependency on dbutil-4.7. (Closes: #594451)
+ patch provided by
The postinst shouldn't need to call db4.Xupgrade, libberkeleydb-perl
takes care of that.
** Also affects: postgrey (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: postgrey (Ubuntu Maverick)
Importance: Undecided
Status: New
** Changed in: postgrey (Ubuntu)
** Changed in: postgrey (Debian)
Status: New => Fix Committed
--
upgrade from hardy to lucid fails
https://bugs.launchpad.net/bugs/537472
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
** Changed in: postgrey (Debian)
Status: Unknown => New
--
upgrade from hardy to lucid fails
https://bugs.launchpad.net/bugs/537472
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
** Tags added: patch
--
upgrade from hardy to lucid fails
https://bugs.launchpad.net/bugs/537472
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/l
Here is a patch against postgrey_1.32-5 that I believe correct this
issue.
** Patch added: "postgres-use-db4.8-upgrade.patch"
https://bugs.edge.launchpad.net/debian/+source/postgrey/+bug/537472/+attachment/1486072/+files/postgres-use-db4.8-upgrade.patch
--
upgrade from hardy to lucid fails
** Bug watch added: Debian Bug tracker #575581
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575581
** Also affects: postgrey (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575581
Importance: Unknown
Status: Unknown
--
upgrade from hardy to lucid fails
https://b
This is a bug in the preinst script of the Lucid package. It
specifically calls /usr/bin/db4.7_upgrade but the DB environment is 4.8.
You can work-around the problem for the upgrade by temporarily
redirecting /usr/bin/db4.7_upgrade to db4.8_upgrade:
sudo -i
cd /usr/bin
mv db4.7_upgrade db4.7_upgr
** Description changed:
Binary package hint: postgrey
While trying to upgrade my hardy installation to lucid today I got the
following failure to upgrade postgrey:
Preparing to replace postgrey 1.31-2 (using .../postgrey_1.32-4_all.deb) ...
invoke-rc.d:
You don't actually need to wipe your white list with --purge
--
upgrade from hardy to lucid fails
https://bugs.launchpad.net/bugs/537472
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
apt-get -remove --purge postgrey
apt-get -install postgrey
does get it working but you will lose your DB and whit list files if you
don't make a copy of them
--
upgrade from hardy to lucid fails
https://bugs.launchpad.net/bugs/537472
You received this bug notification because you are a member of
Hi - Has anyone found a workaround, yet?
Thanks.
--
upgrade from hardy to lucid fails
https://bugs.launchpad.net/bugs/537472
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
33 matches
Mail list logo
