libtifiles failed to upload: conflicts with libtifiles2

Bug #507741 reported by Kamal Mostafa
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
libticalcs (Ubuntu)
Invalid
Undecided
Unassigned
libtifiles (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

http://launchpadlibrarian.net/36604200/upload_1385939_log.txt

2009-12-08 23:14:47 WARNING Upload was rejected:
2009-12-08 23:14:47 WARNING libtifiles2-5_1.1.1-1_i386.deb: Version older than that in the archive. 1.1.1-1 <= 1.1.2-0ubuntu1

The actual problem is that Ubuntu's renamed package "libtifiles2" in Lucid blocks Debian package "libtifiles" from uploading. Likewise, Ubuntu's renamed "libticalcs2" will be in conflict with Debian's "libticalcs". The plan for Lucid is to merge Lucid's "libtifiles2" and "libticalcs2" into "libtifiles" and "libticalcs" (respectively) and then remove the "2" packages.

Related branches

Changed in libtifiles (Ubuntu):
assignee: nobody → Kamal Mostafa (kamalmostafa)
status: New → In Progress
Changed in libticalcs (Ubuntu):
assignee: nobody → Kamal Mostafa (kamalmostafa)
status: New → In Progress
description: updated
Revision history for this message
Emmet Hikory (persia) wrote :

Um, Ubuntu's libtifiles2 predates Debian's libtifiles. It may be worth working with the Debian maintainer of libtifiles and the recent uploaders of libtifiles2 to come to a common shared maintenance model, rather than bothering with any sort of Ubuntu-local merge.

Revision history for this message
Scott Howard (showard314) wrote :

Re Emmet's comment:

I believe the Ubuntu-local merge is a quick "band-aid" to at least get Debian's and Ubuntu source package names the same. This way the properly named and versioned binaries are built (and don't conflict with each other because they build packages with the same name) and packages that depend on them can build properly without ubuntu diffs. See tiemu, for example. That package requires an ubuntu-local merge because of this bug. Ideally, once this back merge happens, we can sync the depending packages back to their debian sources, then can pass whatever changes or patches needed in the backmerge up to debian. You're right, this bug occured because of a lack of a common shared maintenance model, so we have to put it back on track so that the two can eventually be in sync again.

Revision history for this message
Kamal Mostafa (kamalmostafa) wrote :

Attached branch merges Ubuntu's libtifiles2 - 1.1.2-0ubuntu1 into the 'libtifiles' tree to create libtifiles - 1.1.2-0ubuntu2. After this branch is uploaded, package 'libtifiles' should be removed.

Changed in libtifiles (Ubuntu):
assignee: Kamal Mostafa (kamalmostafa) → nobody
status: In Progress → Confirmed
Revision history for this message
Kamal Mostafa (kamalmostafa) wrote :

Correction to comment #3: After this branch is uploaded, package 'libtifiles2' should be removed (not 'libtifiles').

Changed in libticalcs (Ubuntu):
assignee: Kamal Mostafa (kamalmostafa) → nobody
status: In Progress → Confirmed
Emmet Hikory (persia)
Changed in libtifiles (Ubuntu):
assignee: nobody → Emmet Hikory (persia)
status: Confirmed → In Progress
Revision history for this message
Emmet Hikory (persia) wrote :

marking the libticalcs task invalid, as the bug in libticalcs is similar (but different) to the bug in libtifiles. The libticalcs bug is better tracked as bug #507740

Changed in libticalcs (Ubuntu):
status: Confirmed → Invalid
Emmet Hikory (persia)
Changed in libtifiles (Ubuntu):
assignee: Emmet Hikory (persia) → Kamal Mostafa (kamalmostafa)
importance: Undecided → Medium
Revision history for this message
Kamal Mostafa (kamalmostafa) wrote :

New attached branch ("merge-507741-3") libtifiles 1.1.2-0ubuntu2 is based off of upstream's libtifiles 1.1.2 orig tarball and includes the new autoconf-generated files as well as the one small source change in 1.1.2. Ubuntu's 1.1.2-0ubuntu1 changes have been merged as well (minus the libtifiles"2" nomenclature). Resulting diff is very large compared to the libtifiles 1.1.1 branch that it replaces (due to the autoconf stuff) but very small compared to upstream.

Changed in libtifiles (Ubuntu):
assignee: Kamal Mostafa (kamalmostafa) → nobody
status: In Progress → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libtifiles - 1.1.2-0ubuntu2

---------------
libtifiles (1.1.2-0ubuntu2) lucid; urgency=low

  * Merge from Ubuntu libtifiles2 1.1.2-0ubuntu1 (LP: #507741):
    - bzr merge-upstream --package libtifiles --version 1.1.2 ../libtifiles2
        libtifiles2 (1.1.2-0ubuntu1)
        * New upstream version (LP: #181358).
        * debian/control:
          - Bump libticonv-dev build-dep to 1.1.0.
          - Add build-deps on zlib1g-dev, tfdocgen and doc-base.
          - Use ${binary:Version} in place of ${Source-Version}.
          - Add Homepage field.
          - Bump Standards-Version.
        * debian/rules:
          - Make lintian happy.
        * debian/libtifiles2-dev.docs:
          - Correctly install the documentation.
        * debian/libtifiles2-dev.doc-base:
          - Register the documentation with doc-base.
        * SO version bump 3 -> 5.
        [Chris Coulson <email address hidden>]
    - restore binary package name libtifiles2-dev to libtifiles-dev
 -- Kamal Mostafa <email address hidden> Sun, 21 Feb 2010 09:23:25 -0800

Changed in libtifiles (Ubuntu):
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.