at does not have a pristine tar entry for the latest version

Bug #1802962 reported by Christian Ehrhardt  on 2018-11-12
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
usd-importer
High
Unassigned

Bug Description

Hi,
we just worked on "at" and realized that after a clone we have:

$ git branch -av | grep prist
  remotes/pkg/importer/debian/pristine-tar c8a7613 pristine-tar data for at_3.1.20.orig.tar.gz
  remotes/pkg/importer/ubuntu/pristine-tar faca66e pristine-tar data for at_3.1.20.orig.tar.gz

$ git show pkg/debian/sid:debian/changelog | head
at (3.1.23-1) unstable; urgency=medium

  * New release 3.1.23:
    - Finished the release script.
  * New release 3.1.22:
    - Draft of a release script.
  * New release 3.1.21:
    - Fix call to fcntl (Closes: #832368).
    - Improvements to ayd.service (Closes: #892819).
    - On reboot remove stale jobs (Closes: #885891).

How can there be no 3.1.23-1 tarball on the pristine-tar branches.

tags: added: import

I will need to check, but this is probably due to known issues with "gbp
import-orig" which causes it to sometimes not work.

Umm, this also affects dovecot.
Both imported fine in the past.

I slowly get the feeling every new tarball might be missing :-/

Let me bump the prio to make you aware, it would be really nice if you could give it a look.

Changed in usd-importer:
importance: Undecided → High

What's your use case that is broken by the pristine tar data being
missing?

> What's your use case that is broken by the pristine tar data being
> missing?

TL;DR: Doing merges

Detail:
We want to `git ubuntu export-orig` what is imported at the Debian
import when doing a merge.
It also is needed for `git ubuntu build-source --for-merge` and all such.
But that fails, so we have to fall back to pull-debian-source + moving
the tarball around.
I always appreciated that with the pristine-tar branches you could
export-orig - and thereby build - any version that you could check out
from the USDI repos.

Robie Basak (racb) wrote :

On Thu, Nov 15, 2018 at 03:38:59PM -0000,  Christian Ehrhardt  wrote:
> Detail:
> We want to `git ubuntu export-orig` what is imported at the Debian
> import when doing a merge.

export-orig is supposed to fall back to using pull-lp-source or
pull-debian-source automatically. Does that not work? If not, it may be
easier to fix the fallback than I think it will be to fix the
pristine-tar imports.

As we just talked about it:
1. fallback is not working
2. I want proper pristine tar if possible

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers