[Piuparts-devel] [PATCH] Re: tagging piuparts-detected bugs that affect other packages

Andreas Beckmann debian at abeckmann.de
Mon Jan 23 13:00:35 UTC 2012

On 2012-01-23 10:51, Holger Levsen wrote:
> This doesnt seem to work: I sent this mail:

> found 655715 lvm2/2.02.66-5


> squeeze2wheezy
> lvm2/2.02.88-2: Maybe the bug was filed earlier: 655715 against lvm2/2.02.66-5


the upgrade tests are a bit special - they are based on the target
version number, but the failure actually already occurs when installing
the *old* version from squeeze.

we can't do
  found 655715 lvm2/2.02.88-2
as that would be incorrect.

So my affects/fuond instructions probably don't apply to upgrade tests.

For lvm2 we have 2 solutions:
* get this fixed in a stable point release
* add an exception - install udev before testing lvm2 (or a dependency)
  - I have hacked this into my setup, getting proper a patch is not

slapd/2.4.28-1.1: Maybe the bug was filed earlier: 655845 against

  Preparing to replace slapd 2.4.23-7.2 (using
.../slapd_2.4.28-1.1_amd64.deb) ...
  invoke-rc.d: policy-rc.d denied execution of stop.
    Dumping to /var/backups/slapd-2.4.23-7.2:
    - directory dc=debian,dc=org... slap_sasl_init: auxprop add plugin
  slapcat: slap_init failed!
  dpkg: error processing
/var/cache/apt/archives/slapd_2.4.28-1.1_amd64.deb (--unpack):
   subprocess new pre-installation script returned error exit status 1
  configured to not write apport reports
    Backing up /etc/ldap/slapd.d in /var/backups/slapd-2.4.28-1.1... done.
  invoke-rc.d: policy-rc.d denied execution of start.

==> found 655845 2.4.28-1.1


More information about the Piuparts-devel mailing list