package is not upgraded on hardy upgrade

Bug #194112 reported by JoseStefan
20
Affects Status Importance Assigned to Milestone
no-ip (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: no-ip

Package is not upgraded on hardy upgrade.
Furthermore, manually installing "noip2" (hardy) does not remove "no-ip" (gutsy) from the system.
Leaving a (local or obsolete) package.

Should package Conflict with the "no-ip" version on gutsy?

Revision history for this message
Cesare Tirabassi (norsetto) wrote :

There is no dummy package therefore there is no automatic upgrade, the package noip2 both provides and replaces no-ip but the upgrade has to be done manually.

Changed in no-ip:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Johan Euphrosine (proppy) wrote :

Please review that the attached debdiff correct this issue.

Revision history for this message
Johan Euphrosine (proppy) wrote :

Attached debdiff remove Provides and add versionned Conflicts Replaces over the dummy package.

Revision history for this message
Johan Euphrosine (proppy) wrote :

Corrected a typo in dummy package description.

Revision history for this message
Siegfried Gevatter (rainct) wrote :

Why the "(<< ${source:Version})" in Conflicts/Replaces?

Revision history for this message
Luca Falavigna (dktrkranz) wrote :

Transitional package should be enough to fix this.

Revision history for this message
Cesare Tirabassi (norsetto) wrote :

The Conflicts/Replaces are not there for the purpose of the dist-upgrade.
If a user however installs noip2 (2.1.7-7ubuntu1) over a system which has noip (<<2.1.7-7ubuntu1) what will happen if there is no Conflicts/Replaces?
Thats why "its better" to have it .....

Revision history for this message
Cesare Tirabassi (norsetto) wrote :

no-ip (2.1.7-7ubuntu1) hardy; urgency=low

  * Add no-ip transitional package
  * Update maintainer field in debian/control

 -- Johan Euphrosine < <email address hidden>> Fri, 22 Feb 2008 13:20:59 +0100

Changed in no-ip:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.