upstart import failing

Bug #813937 reported by James Hunt
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu Distributed Development
Confirmed
Undecided
Unassigned

Bug Description

http://package-import.ubuntu.com/status/upstart.html

This is curious since the error appears to relate to a missing tag:

  bzrlib.errors.NoSuchTag: No such tag: upstream-0.9.7

... and yet lp:ubuntu/upstart *does* contain this tag:

$ bzr tags|grep upstream-0.9.7
upstream-0.9.7 1185.1.12
$

Confused :-)

Revision history for this message
James Hunt (jamesodhunt) wrote :

Hmm. This problem has now morphed into:

  bzrlib.errors.NoSuchTag: No such tag: upstream-1.3

What does this mean??

Changed in udd:
status: New → Confirmed
Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 813937] Re: upstart import failing

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 8/4/2011 6:55 PM, James Hunt wrote:
> Hmm. This problem has now morphed into:
>
> bzrlib.errors.NoSuchTag: No such tag: upstream-1.3
>
> What does this mean??
>

I believe this error happens when it sees that ubuntu's version has been
imported, but the corresponding upstream version has not. (so
1.3-1ubuntu1 is seen in the branch)

It indicates that something is out of sync. Most likely someone pushed
to the branch directly without properly marking what was the upstream
release vs what was the packaging release.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk48HwEACgkQJdeBCYSNAANKmgCdHsy0gw6ffDrPDDcFVx2HxnL3
SPwAoIXogdEAiISMkOy4o7XYLJDkZN+X
=AReT
-----END PGP SIGNATURE-----

Revision history for this message
James Westby (james-w) wrote :

Hi,

In this case it looks as though upstart 1.3 was merged without using
"bzr merge-upstream"

http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/oneiric/upstart/oneiric/revision/1316.1.1

Fixing this is tricky as the bzr history can't be changed.

The tag can just be added at an appropriate revision (bzr tag
upstream-1.3 -r tag:1.3), but the pristine-tar data won't be included
and so packages based on 1.3 won't be buildable without having the
tarball already.

Thanks,

James

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Is this still a bug? the lp:ubuntu/upstart is in active use, but I'm not sure if everyone is co-operating or the importer works.

Revision history for this message
Clint Byrum (clint-fewbar) wrote :

The given status URL references bug #494481 which basically says that
this is happening because merge-upstream wasn't used.

It does seem like the branch is just being updated manually by all
uploaders.

Excerpts from Dmitrijs Ledkovs's message of 2012-08-22 23:57:12 UTC:
> Is this still a bug? the lp:ubuntu/upstart is in active use, but I'm not
> sure if everyone is co-operating or the importer works.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/813937
>
> Title:
> upstart import failing
>
> Status in Ubuntu Distributed Development:
> Confirmed
>
> Bug description:
> http://package-import.ubuntu.com/status/upstart.html
>
> This is curious since the error appears to relate to a missing tag:
>
> bzrlib.errors.NoSuchTag: No such tag: upstream-0.9.7
>
> ... and yet lp:ubuntu/upstart *does* contain this tag:
>
> $ bzr tags|grep upstream-0.9.7
> upstream-0.9.7 1185.1.12
> $
>
> Confused :-)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/udd/+bug/813937/+subscriptions

Revision history for this message
Logan Rosen (logan) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 494481, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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.