Supersede does not fully delete old records of package?

Asked by Florian Riedl on 2017-11-27

We have a packaging problem that seems to be related to superseding a package does not fully work.

Up until now, we had a package and all its sub-packages on the same level. Eg. all builds were mostly similar from Trusty upwards. Now, we had a dependency change, which affects a sub-package. The dependency is available for Xenial and newer, but not on Trusty. So we decided to stop producing the sub-package on Trusty.

The problem is, that if you want to install the package on Trusty or try to update it, apt will find the updated base package and all other sub-packages, but for this particular sub-package it finds a record to a older version, which cannot be installed because the files are no longer there.

Updating the apt cache or even clearing it does not help. It will always find that old sub-package again.

Before we file a bug, we'd rather know if someone knows a solution to this problem. Or at least has seen this before, so we can pinpoint the source.

Thanks.

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu rsyslog Edit question
Assignee:
No assignee Edit question
Last query:
2017-11-27
Last reply:
2017-12-13
Launchpad Janitor (janitor) said : #1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.