Launchpad itself

Please add support for .orig.tar.bz2

Bug #225151 reported by Bryan Donlan
34
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Jelmer Vernooij
Launchpad itself 10.02

Bug Description

When uploading a PPA package with a .orig.tar.bz2:

Rejected:
Unable to identify file openc2e_0.1a.orig.tar.bz2 (contrib/games) in changes.
Further error processing not possible because of a critical previous error.

This message is rather unclear, but moreover since dpkg supports .orig.tar.bz2, it would be nice to have support in the build infastructure for this as well. Although it's trivial to repack the archive, it's good for the uploaded .orig tarball to be exactly identical to the upstream tarball, for verification purposes.

Revision history for this message
Bryan Donlan (bdonlan) wrote :

(note; reuploading the package with the tarball recompressed as .orig.tar.gz worked without any other changes; it's not a problem with contrib/ or anything AFAICS)

Revision history for this message
Celso Providelo (cprov) wrote :

RIght, bz2 orig tarballs are not supported in PPAs either in ubuntu PRIMARY archive. We plan to migrate to the hardy's dpkg by the end of July (in time to support lenny packages)

Changed in soyuz:
assignee: nobody → cprov
importance: Undecided → High
status: New → Triaged
Revision history for this message
James Henstridge (jamesh) wrote :

Has there been any progress on this? I just got some similar upload rejections for my PPA.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

Hi James

This is not a trivial change for us to make. I'm going to schedule it for 2.1.12 for now as there is too much work already planned for .10 and .11 to fit this in.

In the meantime if there's enough interest in this, I can consider juggling some priorities to move this one up.

Changed in soyuz:
importance: High → Medium
milestone: none → 2.1.12
Julian Edwards (julian-edwards)
Changed in soyuz:
milestone: 2.1.12 → pending
Revision history for this message
Morten Kjeldgaard (mok0) wrote :

Nudge nudge!

Revision history for this message
Julian Edwards (julian-edwards) wrote :

sync-source.py is also hard-coded to expect orig.tar.gz, this should be fixed at the same time as the upload processor.

Changed in soyuz:
assignee: Celso Providelo (cprov) → nobody
Revision history for this message
Steve Langasek (vorlon) wrote :

Since we now have orig.tar.bz2 in the archive originating as syncs from Debian, this is now rather critical to have supported for lucid:
there are 8 source packages in Debian that should be synced to newer versions according to our sync policy, but can't be because sync-source.py will not allow them because they reference a previously-seen .orig.tar.bz2.

Muharem Hrnjadovic (al-maisan)
Changed in soyuz:
milestone: pending → 10.02
importance: Medium → High
Revision history for this message
Muharem Hrnjadovic (al-maisan) wrote :

What Debian source package format version are these packages awaiting synchronization?

I understand Debian source package format version 1 may not have bz2 orig tar balls and we have support for source package format version 3 in place already.

Revision history for this message
William Grant (wgrant) wrote :

The bug here is an orig.tar.gz hardcoding in sync-source.py that I missed in my work -- the check that allows syncs to contain an orig tarball that already exists in the archive. This needs to be extended to any file matching the ORIG or COMPONENT_ORIG regexps.

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

Uploading orig.tar.bz2 files seems to work fine for v3 source packages. I've just uploaded a converted version of tdb to my PPA, and it was accepted without problems (https://edge.launchpad.net/~jelmer/+archive/ppa/+packages, see tdb 1.2.0a-2).

Revision history for this message
Muharem Hrnjadovic (al-maisan) wrote :

OK, so this is purely a source package synchronization issue now.

Revision history for this message
Steve Kowalik (stevenk) wrote :

But it doesn't even seem to be that. I synced usb-modeswitch-data yesterday which uses an .orig.tar.bz2 and quilt (3.0) source format, and it was pulled in via sync-source just fine, and went through source and binary NEW just fine.

Revision history for this message
Steve Langasek (vorlon) wrote :

No, the issue is that *subsequent* Debian revisions of the package can't be synced because sync-source.py won't accept references to an existing .orig.tar.bz2 in the database.

So Muharem and William have accurately triaged this bug, please let them fix it :)

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

  status inprogress
  assignee jelmer

Changed in soyuz:
assignee: nobody → Jelmer Vernooij (jelmer)
status: Triaged → In Progress
Revision history for this message
Diogo Matsubara (matsubara) wrote : Bug fixed by a commit

Fixed in devel r10307 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/revision/10307>

Changed in soyuz:
status: In Progress → Fix Committed
Jelmer Vernooij (jelmer)
Changed in soyuz:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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