lckdo is obsolete: functionality merged in moreutils

Bug #157663 reported by Marco Rodrigues on 2007-10-27
10
Affects Status Importance Assigned to Milestone
lckdo (Ubuntu)
Wishlist
Unassigned
moreutils (Ubuntu)
Wishlist
Unassigned

Bug Description

Binary package hint: lckdo

We have moreutils 0.24 at Hardy, so it can be removed..

Debian reason: RoM; superseded by moreutils 0.23

lckdo | 0-1 | source, alpha, amd64, arm, hppa, hurd-i386, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc

Closed bugs: 441005

Changed in lckdo:
importance: Undecided → Wishlist
Marco Rodrigues (gothicx) wrote :

I don't know if it will break upgrade from Dapper to Hardy, but if lckdo is included in moreutils since 0.23, and hardy has now 0.24, it should work ? or not...

Emmet Hikory (persia) wrote :

Removal request not acknowledged:

Dapper -> Hardy has no issue, as lckdo was introduced in Gutsy
Gutsy -> Hardy needs transition support (to be dropped in hardy +1)

As the lckdo implementation was directly imported into moreutils, a simple transition is simple:

No transition is required in Debian, as lckdo was not shipped in a stable release

Please prepare a new lckdo dummy package that depends on moreutils (>= 0.23), and notes in the changelog that transition support may be dropped in gutsy+1

Please also prepare a new moreutils revision that adjusts the Conflicts/Replaces on lckdo to be Conflicts/Replaces on lckdo (<= 0-1) so that the new lckdo dummy package may be installed in parallel, and note that this transition support may be dropped in hardy+1

Changed in lckdo:
status: New → Confirmed
Changed in moreutils:
importance: Undecided → Wishlist
Emmet Hikory (persia) wrote :

Err.. My apologies: transition support for the lckdo dummy package may be dropped in HARDY+1, not gutsy+1.

Matt Zimmerman (mdz) wrote :

It would be sensible for the dummy upgrade package to be built by moreutils itself, rather than keeping around an extra source package just to build an empty package.

Emmet Hikory (persia) wrote :

Excellent point. This is much better resolved with moreutils than with lckdo, although I'd still discourage removal of lckdo until an updated moreutils was available.

Changed in moreutils:
status: New → Confirmed
James Westby (james-w) wrote :

Hi,

Here is an attempted patch to moreutils to fix this issue.

I'll subscribe u-u-s to get review.

Thanks,

James

James Westby (james-w) wrote :

Oops, one with the maintainer field updated as well.

Thanks,

James

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package moreutils - 0.26ubuntu1

---------------
moreutils (0.26ubuntu1) hardy; urgency=low

  * Add a transition package for lckdo. It is now included in moreutils,
    so we would like to remove the old lckdo source package. As lckdo
    was shipped in gutsy we need to provide the transition, but Debian
    do not, so we just apply this as a Ubuntu delta (LP: #157663).
    This transitional package can be dropped in hardy+1.
  * Modify Maintainer value to match the DebianMaintainerField
    specification.

 -- James Westby <email address hidden> Sat, 23 Feb 2008 16:36:49 +0000

Changed in moreutils:
status: Confirmed → Fix Released
Emmet Hikory (persia) wrote :

Based on the presence of a transition package, ACK'ing the lckdo source package task as a removal request.

Steve Langasek (vorlon) wrote :

Appears that this was already done back in November:

[Date: Fri, 30 Nov 2007 11:28:48 +0000] [ftpmaster: Launchpad Archive Manager]
Removed the following packages from hardy:

     lckdo | 0-1 | source, amd64, hppa, i386, ia64, lpia, powerpc, sparc

------------------- Reason -------------------
(From Debian) RoM; superseded by moreutils 0.23

----------------------------------------------

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

Other bug subscribers