The updated distro-info-data is in quantal-updates.
Scott K
Martin Packman martin.pack...@canonical.com wrote:
Currently every[1] package import is failing[2] because the new
'raring'
series is not present in the list of releases obtainted from
distro-info.
The package importer is using
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
On Thursday, September 22, 2011 06:42:48 PM Jelmer Vernooij wrote:
This would more closely mirror how
packages are managed in Debian. However, I'd still want
`bzr branch ubuntu:gtimelog` to give me the full source. I wonder if
nested branches are the answer here. One trick would be
Max Bowsher _...@maxb.eu wrote:
On 23/05/11 07:42, Andrew Bennetts wrote:
Max Bowsher wrote:
A huge amount of the UDD importer's interesting code is in one file,
icommon.py.
I'd like to submit a series of changes to break it up such that only
the
most common bits of code remain there.
Max Bowsher _...@maxb.eu wrote:
Max Bowsher wrote:
package_importer is a bit long. udd works for me, especially as
the
project lives in lp:udd.
On 23/05/11 12:19, Scott Kitterman wrote:
The term udd is, unfortunately, overloaded. It's also 'Ultimate
Debian Database'. I suggest something
I decided to try UDD again for a new upstream version that was just released.
I was following the documentation here:
https://wiki.ubuntu.com/DistributedDevelopment/Documentation/NewUpstreamVersion
I got to this step:
bzr merge-upstream --version 1.2 http://example.org/releases/foo-1.2.tar.gz
On Thursday, April 14, 2011 03:00:23 PM Scott Kitterman wrote:
I decided to try UDD again for a new upstream version that was just
released.
I was following the documentation here:
https://wiki.ubuntu.com/DistributedDevelopment/Documentation/NewUpstreamVer
sion
I got to this step
On Thursday, March 24, 2011 09:50:26 pm Martin Pool wrote:
On 25 March 2011 01:44, Francis J. Lacoste
francis.laco...@canonical.com wrote:
On March 23, 2011, Barry Warsaw wrote:
* The build-from-branch-into-primary LEP is awaiting assignment to an LP
squad for implementation. Martin and
On Tuesday, February 15, 2011 12:34:28 am Martin Pool wrote:
We have a question in https://bugs.launchpad.net/bugs/516709 about
what the permissions on official package branches ought to be, and how
they should be explained to the user.
The basic thing is that Launchpad knows who is allowed
On 28 January 2010 06:14, Reinhard Tartler siret...@ubuntu.com wrote:
...
 - download the orig.tar.gz/orig.tar.bz2 files from debian
The branches are pristine-tar enabled you can just
$ bzr bd them and a tarball will appear in your tarball's directory.
Right, but which tarball? It's not
On 28 January 2010 12:04, Scott Kitterman ubu...@kitterman.com wrote:
On 28 January 2010 06:14, Reinhard Tartler siret...@ubuntu.com wrote:
...
à - download the orig.tar.gz/orig.tar.bz2 files from debian
The branches are pristine-tar enabled you can just
$ bzr bd them and a tarball
On Mon, Jan 18, 2010 at 12:21 PM, Scott Kitterman ubu...@kitterman.com
wrote:
I usually use the ancestor revision shortcut for selecting the revision
to
diff:
Ubuntu patch compared to the common base version:
~/src/pkg-name/lucid/ $ bzr diff -rancestor:../squeeze/
Debian patch compared
forgot mailing list sorry silly gmail
So then you get to read the reply twice. ;-)
-- Forwarded message --
From: Dmitrijs Ledkovs dmitrij.led...@gmail.com
Date: 2010/1/18
Subject: Re: Feedback on merging via bzr
To: Scott Kitterman ubu...@kitterman.com
2010/1/18 Scott
13 matches
Mail list logo
