Re: What to do when a packaging branch is out of date
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/20/2012 11:31 AM, James Westby wrote:
On Tue, 20 Mar 2012 10:00 -0400, Scott Kitterman
ubu...@kitterman.com wrote:
On Tuesday, March 20, 2012 10:56:27 AM Andreas Hasenack wrote:
So apparently a package update can be prepared using udd,
released into the archive, and the packaging branch still be
out of date:
$ bzr branch ubuntu:landscape-client
landscape-client-12.04-0ubuntu1 Most recent Ubuntu version:
12.04-0ubuntu1
Packaging branch version: 11.07.1.1-0ubuntu2 Packaging branch
status: OUT-OF-DATE Branched 40 revisions. $
It's like it was released before being committed.
What should I do if I want to prepare another fix? Wait? Ping
someone to commit and then branch again? Do it with debdiffs
and not worry about branches anymore?
I emailed ubuntu-devel-discuss and someone told me that
somebody has to manually commit to the udd branch, and that
this is normal.
It's normal for there to be some delay. It will (normally) be
automatically updated from what was uploaded. The only way there
isn't some delay is if someone manually commits the branch.
I'm not sure how much delay is considered normal these days.
The logs show that this package was updated at
Time (UTC): 2012-03-20 13:07
Approximately 14 hours after the upload.
The reason for this is that the importer was throttled a week or so
ago in order to help tracking down a service that was overloading
Launchpad. That service was found and corrected but the importer
was never turned back up to a reasonable speed. I've just done
that now. Apologies for the delay.
Hi, can you take another look? It seems there is a delay again:
$ bzr branch ubuntu:landscape-client precise-already-done
Most recent Ubuntu version: 12.04.3-0ubuntu1
Packaging branch version: 12.04.2-0ubuntu1
Packaging branch status: OUT-OF-DATE
Branched 44 revisions.
There is an error for it in the package importer:
http://package-import.ubuntu.com/status/landscape-client.html#2012-03-30
06:12:01.518169
bzrlib.errors.UnknownErrorFromSmartServer: Server sent an unexpected
error: ('error', 'xmlrpclib.Fault', Fault -1: 'Unexpected Zope
exception: RequestExpired: request expired.')
- --
Andreas Hasenack
andr...@canonical.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk98mCkACgkQeEJZs/PdwpB2sQCgmaIgDJV9RZ/1Lxv5fS1pT6lo
s/UAn1AtqBgVEsbv2FT3kZtxewXKwIRy
=sWd4
-END PGP SIGNATURE-
--
ubuntu-distributed-devel mailing list
ubuntu-distributed-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: What to do when a packaging branch is out of date
On Wed, 04 Apr 2012 15:51:21 -0300, Andreas Hasenack andr...@canonical.com
wrote:
Hi, can you take another look? It seems there is a delay again:
$ bzr branch ubuntu:landscape-client precise-already-done
Most recent Ubuntu version: 12.04.3-0ubuntu1
Packaging branch version: 12.04.2-0ubuntu1
Packaging branch status: OUT-OF-DATE
Branched 44 revisions.
There is an error for it in the package importer:
http://package-import.ubuntu.com/status/landscape-client.html#2012-03-30
06:12:01.518169
bzrlib.errors.UnknownErrorFromSmartServer: Server sent an unexpected
error: ('error', 'xmlrpclib.Fault', Fault -1: 'Unexpected Zope
exception: RequestExpired: request expired.')
Hi,
It is now up to date again.
Thanks,
James
--
ubuntu-distributed-devel mailing list
ubuntu-distributed-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: What to do when a packaging branch is out of date
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/04/2012 04:24 PM, James Westby wrote: Hi, It is now up to date again. Thanks! - -- Andreas Hasenack andr...@canonical.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk98oQAACgkQeEJZs/PdwpDrEACfeL/fkp3+8u+GX/LXEO4ildow EIMAn2qaTQ7asVZI2/Cw9JMFtuXMJghZ =qvhq -END PGP SIGNATURE- -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: What to do when a packaging branch is out of date
On Tuesday, March 20, 2012 10:56:27 AM Andreas Hasenack wrote: So apparently a package update can be prepared using udd, released into the archive, and the packaging branch still be out of date: $ bzr branch ubuntu:landscape-client landscape-client-12.04-0ubuntu1 Most recent Ubuntu version: 12.04-0ubuntu1 Packaging branch version: 11.07.1.1-0ubuntu2 Packaging branch status: OUT-OF-DATE Branched 40 revisions. $ It's like it was released before being committed. What should I do if I want to prepare another fix? Wait? Ping someone to commit and then branch again? Do it with debdiffs and not worry about branches anymore? I emailed ubuntu-devel-discuss and someone told me that somebody has to manually commit to the udd branch, and that this is normal. It's normal for there to be some delay. It will (normally) be automatically updated from what was uploaded. The only way there isn't some delay is if someone manually commits the branch. I'm not sure how much delay is considered normal these days. Scott K -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: What to do when a packaging branch is out of date
Quoting Scott Kitterman (ubu...@kitterman.com): On Tuesday, March 20, 2012 10:56:27 AM Andreas Hasenack wrote: So apparently a package update can be prepared using udd, released into the archive, and the packaging branch still be out of date: $ bzr branch ubuntu:landscape-client landscape-client-12.04-0ubuntu1 Most recent Ubuntu version: 12.04-0ubuntu1 Packaging branch version: 11.07.1.1-0ubuntu2 Packaging branch status: OUT-OF-DATE Branched 40 revisions. $ It's like it was released before being committed. What should I do if I want to prepare another fix? Wait? Ping someone to commit and then branch again? Do it with debdiffs and not worry about branches anymore? I emailed ubuntu-devel-discuss and someone told me that somebody has to manually commit to the udd branch, and that this is normal. It's normal for there to be some delay. It will (normally) be automatically updated from what was uploaded. The only way there isn't some delay is if someone manually commits the branch. I'm not sure how much delay is considered normal these days. For some packages, the auto importer refuses to run. So I manually go into the checked-out tree and do 'bzr import-dsc next-version.dsc, one version at a time, until it's caught up. Then push. If there was just a one-time import error, this will get past it. If the importer just refuses to run because of errors in older releases, then you just have to do this every time if you want to enable UDD. (You can find the .dsc links from the pad.lv/u/packagename page by following the 'view full publishing history at the right) -serge -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
