On 1 February 2012 10:18, Barry Warsaw ba...@ubuntu.com wrote:
Hi all,
I have a merge proposal to update the UDD documentation part of the packaging
guide. I'm hoping this can be reviewed, merged, and published before my UDW
session tomorrow (it's okay if it can't).
That was great,
I haven't dug into whether these are new, or whether there is already
a bug for them, but they do seem to be new. I see
https://bugs.launchpad.net/udd/+bug/553668 about supporting xz in
bzr-builddeb: does that perhaps need to be deployed on Jubany?
-- Forwarded message --
From:
On 19 January 2012 11:30, Jelmer Vernooij jel...@samba.org wrote:
bzr-builddeb 2.8.1 has just landed on Debian Sid and Ubuntu Precise. This
version contains some of my improvements from late last year for the handling
of quilt patches in packaging branches.
That's great. I have taken the
I'm going to try writing a Juju charm for the udd importer.
(time passes)
Well, I did start, but I got bogged down in debugging why my lxc
provider won't boot. Details and tiny patches on the juju list (which
you should join.) If someone else wants to have a go, please do.
Plan:
* it runs on
... I was working in lp:~canonical-bazaar/charm/oneiric/udd/trunk
--
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
I think switching from batch html, handcoded sql and ssh access to
higher-level alternatives would be well worth while and Django seems
like a good choice. +1 from me, and also on the specific incremental
changes.
I agree with James, and disagree with Vincent, about bringing these
changes in to
There are two big changes that aren't necessary for us, but would help a lot:
1. Decouple lp:udd from the package-import.canonical.com production
deployment
2. Split the package scanning and the branch importing parts of
lp:udd into separate projects
That sounds good to me, especially #1.
(re-send)
On 8 December 2011 07:13, Martin Pool m...@sourcefrog.net wrote:
There are two big changes that aren't necessary for us, but would help a lot:
1. Decouple lp:udd from the package-import.canonical.com production
deployment
2. Split the package scanning and the branch importing
The buildd update saga is still continuing. We're planning a new
deployment this week which will improve translation functions, and
then after that we will deploy a new launchpad-buildd which will fix
http://pad.lv/891892, building of packages where -sa is needed to
force the source tarball to be
On 18 November 2011 11:23, Scott Ritchie scottritc...@ubuntu.com wrote:
On 11/15/2011 07:07 PM, Martin Pool wrote:
And now that it's deployed I'm getting a different error:
bzr: ERROR: deb-version not fully expanded: {latest-tag}+daily-2018.
Valid substitutions are: ['{time}', '{date
This is producing this launchpad error when I try to change the recipe:
Error parsing recipe:1:22: Unknown format: '0.4'.
Another bug? :)
i'm guessing that means it's not yet deployed rather than an actual
bug. I will look in to it.
--
Martin
--
ubuntu-distributed-devel mailing list
On 18 November 2011 14:16, Martin Pool m...@canonical.com wrote:
This is producing this launchpad error when I try to change the recipe:
Error parsing recipe:1:22: Unknown format: '0.4'.
Another bug? :)
i'm guessing that means it's not yet deployed rather than an actual
bug. I will look
I changed my recipe to use {latest-tag} instead of {debupstream} today,
requested a rebuild, and got a new build failure:
https://launchpadlibrarian.net/85208307/buildlog.txt.gz
https://bugs.launchpad.net/launchpad/+bug/890834
It seems to be a regression.
Thanks for reporting this. It is
One more recent improvement, thanks to Raphaël
https://bugs.launchpad.net/bugs/827935, you can now look at
https://code.launchpad.net/~ubuntu-branches to see the recently
changed official Ubuntu branches.
--
ubuntu-distributed-devel mailing list
ubuntu-distributed-devel@lists.ubuntu.com
Modify
I don't know the answer to this off hand. Does someone else? Maybe
we can add this to the help.l.n documentation?
Martin
-- Forwarded message --
From: Scott Ritchie scottritc...@ubuntu.com
Date: 10 November 2011 06:05
Subject: Thanks for fixing recipes...and Launchpad
Is there a place where I can track this? I'd like to know when it
becomes available. Thanks for the full answer :)
That's a good question, and maybe something that's a bit missing in
lp's communication at the moment.
We will reply on this thread and also put something on the Launchpad
blog
We're in the middle of a fairly epic series of roll-outs to the
Launchpad buildds. Done today, both on staging and production, is an
update to bzr 2.4, which should let large trees be assembled in recipe
builds without running out of memory.
Coming up soon are upgrades to the buildd client
On 27 September 2011 19:34, Martin Pool m...@canonical.com wrote:
progress in recent weeks:
* John did great work to give much faster branching of large linear
histories, like linaro-gcc: this is now 3x faster (down from 3h to 1h
to branch to me in Australia; flatlined pipe would be about
progress in recent weeks:
* John did great work to give much faster branching of large linear
histories, like linaro-gcc: this is now 3x faster (down from 3h to 1h
to branch to me in Australia; flatlined pipe would be about 15m so
there's some room for more)
* package importer is getting
pitti mentioned to me today the issue of ubuntu-namespace branches
that ought to be related to an upstream bzr branch, but that actually
aren't.
lp:indicator-power is one example, and the desktop team actually
maintain an unofficial packaging branch that does share history:
On 14 September 2011 00:42, Jonathan Riddell jridd...@ubuntu.com wrote:
I packaged bzr for openSUSE recently and it was suggested I send some
notes on how their build service compares to Launchpad.
Thanks for writing that up. jml and I (at least) have looked at it
before but there's nothing
On 8 September 2011 07:48, James Westby jw+deb...@jameswestby.net wrote:
Hi,
Thanks for fixing the bugs that were preventing merge proposals for
getting filed for collisions.
This had led to a surge in the number of such merge proposals. This is
mainly due to a backlog, but there have been
On 23 August 2011 17:41, vila v.ladeuil...@free.fr wrote:
Max Bowsher _...@maxb.eu writes:
We currently have 97 packages failing with AppendRevisionsOnlyViolation
- that's around a sixth of all failures.
I think we should roll back the change to the importer to set
On 22 July 2011 11:31, Max Bowsher _...@maxb.eu wrote:
On 22/07/11 00:54, Martin Pool wrote:
https://bugs.launchpad.net/bzr/+bug/806348 seems to be causing a
steadily increasing number of package import failures - if you look at
the failure count graph it is ramping steadily up to the right
We're back on 2.3.4 on Jubany and the importer is at least running.
So far it has not actually found any work to do. I'm going to see if
I can get it to re-run some of these packages and see what effect that
may have, and perhaps try to improve the reporting within the
importer.
--
On 16 July 2011 23:05, John Arbash Meinel j...@arbash-meinel.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/16/2011 11:27 AM, Max Bowsher wrote:
We've lost the ability to run ./selftest.py on jubany, because we've
upgraded to a bzr packaging which splits bzrlib.tests out into
It's done now.
--
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
That makes sense to me too.
--
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
I think we're now up and running again; if you see any continuing
problems please let me know (and/or fix it ;-).
m
--
ubuntu-distributed-devel mailing list
ubuntu-distributed-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
On 4 June 2011 01:28, Mackenzie Morgan maco...@gmail.com wrote:
On Fri, Jun 3, 2011 at 10:50 AM, Barry Warsaw ba...@ubuntu.com wrote:
On Jun 03, 2011, at 10:07 AM, Mackenzie Morgan wrote:
From what I understand, there are people doing things all sorts of ways with
quilt, and I really don't
Sorry I missed it, I had a personal interrupt last night.
--
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
I think it would be great to have a plenary at UDS-O about what people
are doing with Ubuntu branches. I have put a proposal in
https://wiki.ubuntu.com/UDS-O. We have to make a plan for something
to say in 15m that will be exciting, relevant, not waffly, and not a
vastly-truncated tutorial.
Thanks, Barry, that's very neat.
spiv mentioned the other day he found it a bit unclear at the moment
what was on the bzr team's path towards udd was at the moment. In a
nutshell, what we're going to do is get package-import.ubuntu.com
failures down to 0, and work on bugs that are affecting
Robert pointed out
https://lists.ubuntu.com/archives/ubuntu-desktop/2011-April/002940.html,
about moving to 'normal mode' of bzr-builddeb, in which the entire
tree is versioned.
- It is possible to screw up the branches so that bzr merge-package throws a
confusing error (I keep doing it).
Just to have a bit of closure on this: we're going to work on imports
and other bugs (performance, warning about out-of-date branches) for a
bit more, until either we feel the import failures are running dry, or
until a Launchpad squad is free to do this.
Martin
--
ubuntu-distributed-devel
Sorry, I'm going to be about 15m late.
- Martin
On 03/03/2011 4:04 AM, Barry Warsaw ba...@ubuntu.com wrote:
On Mar 02, 2011, at 06:02 PM, Martin Pool wrote:
Those dates work well for me. (I'm going to be offline again on the
10th of March, but here this week and also the 17th.)
I could have
On 18 February 2011 17:27, Robert Collins robe...@robertcollins.net wrote:
On Fri, Feb 18, 2011 at 6:30 PM, Martin Pool m...@canonical.com wrote:
On 18 February 2011 16:27, Robert Collins robe...@robertcollins.net wrote:
What about 3 - have no owner at all: there is a unique path for each
On 18 February 2011 12:07, Scott Kitterman ubu...@kitterman.com wrote:
On Tuesday, February 15, 2011 12:34:28 am Martin Pool wrote:
There are a few options here and we'd appreciate hearing from Ubuntu
people how they think it should work:
0- No change: the nominal owner keeps write access
On 8 February 2011 19:00, Max Bowsher m...@f2s.com wrote:
On 08/02/11 07:00, Martin Pool wrote:
At the moment it seems to me we need to either: import to looms and
mandate using looms; or check in things with everything expanded and
provide glue that will keep the quilt data up to date
On 25 January 2011 03:32, Robert Collins robe...@robertcollins.net wrote:
Should be easy enough to add a hook to get fixes from plugins; the
tricky bit is allowing users to confirm that the detected things are
correct (or perhaps thats overkill?)
Anyhow the bzr-builddeb, commitfromnews,
On 1 December 2010 09:27, Barry Warsaw ba...@ubuntu.com wrote:
Hi Martin, thanks for posting this update, and apologies for taking so long to
get around to reading it.
On Nov 17, 2010, at 08:06 PM, Martin Pool wrote:
At the end of that discussion we picked two specific items for the bzr team
-- Forwarded message --
From: Bilal Akhtar bilalakh...@ubuntu.com
Date: 24 November 2010 02:36
Subject: Proposed bzr-builddeb SRU
To: ubuntu-distributed-devel@lists.ubuntu.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all!
Version 2.6ubuntu0.1 of package
On 19 November 2010 06:34, Francis J. Lacoste
francis.laco...@canonical.com wrote:
On November 18, 2010, John Arbash Meinel wrote:
Anyway, I don't know the net promoter stuff. I certainly don't see how
you get 1-in-35 being -35.
Doh,
My mistake, you are right. I completely missed the 9
Just a few brief notes about UDD discussions at UDS-N. A lot of this
is captured to various degrees in gobby documents and IRC logs at
http://ubottu.com/uds-logs/, but they're pretty long:
http://ubottu.com/uds-logs/%23ubuntu-uds-bonaire2.log
* There was a lot of interest in adopting something
TLDR? Mixed but generally positive feedback. Top issues to fix are
speed of branching/merging from Launchpad; keeping import branches
reliably up to date; getting branches where possible to current
formats; removing various small-medium roadblocks; supporting v3
packages and being smarter about
On 13 February 2010 04:09, James Westby jw+deb...@jameswestby.net wrote:
On Thu, 11 Feb 2010 12:49:22 +1100, Robert Collins
robert.coll...@canonical.com wrote:
On Wed, 2010-02-10 at 21:46 +, James Westby wrote:
Some of them have been upgraded. If it's easier for me to do an info
On 11 February 2010 18:59, Ian Clatworthy ian.clatwor...@canonical.com wrote:
UDD now has an active mailing list, a Launchpad project and a bug/task
list. Does it make sense to begin thinking about UDD as a product? Would
it be valuable to talk about UDD x.y vs x.z?
Code wise, I guess the
On 11 February 2010 13:18, Robert Collins robert.coll...@canonical.com wrote:
James Westby and I had some time together in Portland to talk about UDD
stuff.
We talked about a few things:
* Looms, their use today and where they should go
* The operational issues with the package importer and
On 3 February 2010 22:14, Reinhard Tartler siret...@ubuntu.com wrote:
Your list includes this:
mplayer
categorized package-bug:513282
categorized ok_upstream
lp:mplayer 0 ok_upstream
this cannot be true. mplayer makes heavy use of svn:externals
We had a big push on hottest100 last week, and it was good. A fairly
recent copy of the hottest100 results are below.
To summarize where we got to: most of the upstream branches are now
working; there are a few not correctly registered but that could
probably be fairly easily fixed. In package
We're hacking a bit more on this script (in
http://code.launchpad.net/~canonical-bazaar/udd/hottest100) to make it
do things including
* check both the package and upstream branch for freshness and existence
* cross check the package branch against Madison
* understand some of the branches that
2010/1/26 Martin Pool m...@canonical.com:
lp:accerciser - lp:~vcs-imports/accerciser/main
lp:at-spi - lp:~vcs-imports/at-spi/git-trunk
lp:ekiga - lp:~vcs-imports/ekiga/git-trunk
lp:gconf - lp:~vcs-imports/gconf/trunk
lp:glib - lp:~jjardon/glib/trunk
all done
lp:gnome-common - lp:~vcs
2010/1/18 Scott Kitterman ubu...@kitterman.com:
I feel like I've gone through a process that is far more complex than the old
one for no real benefit. I have some recommendations for improving and
simplifying this process. I think simplification is an essential element
because the learning
2010/1/16 Francis J. Lacoste francis.laco...@canonical.com:
On January 15, 2010, Martin Pool wrote:
In case people are wondering how far this has come.
When we started focussing on the hottest100 a month ago we had about
90 of the hottest100 packages linked to products, and about 52 of them
In case people are wondering how far this has come.
When we started focussing on the hottest100 a month ago we had about
90 of the hottest100 packages linked to products, and about 52 of them
had working branches. Now we have 94 of them linked to products,
which must be just about all that
2010/1/15 Andrew Bennetts andrew.benne...@canonical.com:
Martin Pool wrote:
[...]
The definition of 'working' here may be a bit loose; I'm working on a
script to scan them and report those which are stale. This will also
I suspect that most of the gnome ones are currently stale (hopefully
Here are some specific things people can do to help with hottest100:
* work out how to make package-product links (explain that here :-)
and create them when they're missing
* update the branches pointing to obsolete imports (gnome etc)
* write a script that checks the date of the last
2010/1/8 James Westby jw+deb...@jameswestby.net:
On Fri, 8 Jan 2010 10:58:04 +1100, Martin Pool m...@canonical.com wrote:
Here are some specific things people can do to help with hottest100:
* work out how to make package-product links (explain that here :-)
and create them when they're
2010/1/5 Ian Clatworthy ian.clatwor...@canonical.com:
Martin Pool wrote:
I think after the break we should focus on the vcs-imports of the top
100 Ubuntu packages until they're all working well. jml and spm
helped with some scripts to query their current state, and we can map
I put jml's query output into a Google spreadsheet, so that we can
annotate lines with the relevant bug etc.
http://spreadsheets.google.com/ccc?key=0Ag3S65cphSMHdG1VckNSRXI4OHBmVmxGaklGVW4tcWchl=en_GB.
Some observations:
Some aren't linked to products; that's probably easily fixed.
In some
I think after the break we should focus on the vcs-imports of the top
100 Ubuntu packages until they're all working well. jml and spm
helped with some scripts to query their current state, and we can map
that into a spreadsheet showing the root cause for each failure.
I'll ask the Bazaar team to
2009/12/18 John Arbash Meinel j...@arbash-meinel.com:
James Westby wrote:
On Thu, 17 Dec 2009 14:19:32 +1100, Martin Pool m...@canonical.com wrote:
My hypothesis is that we (Canonical's Bazaar team) will get to grips
with UDD better if there is a tighter medium-term focus.
The key question
2009/12/14 James Westby jw+deb...@jameswestby.net:
Hi,
I wanted to split this out of the large mail so that we could complete
a design of how this would work.
Here's my initial proposal based on the feedback from that thread.
1) bzr-builddeb decorates pull, merge and perhaps a couple of
2009/12/4 Francis J. Lacoste francis.laco...@canonical.com:
On December 3, 2009, Martin Pool wrote:
If there are existing bugs relevant to udd, or you know of
appropriately concrete and self-contained things that can be filed as
bugs, then tagging them and/or mentioning them here would
2009/12/3 James Westby james.wes...@canonical.com:
On Mon Nov 30 20:19:13 -0500 2009 Martin Pool wrote:
I'd like to get a sanity check from UDD people on what the Bazaar team
is going to do for our 2.1 release, which will have a feature freeze
in February and go into Karmic.
From
If by udd you mean ~ubuntu-distributed-devel, then it was an abandoned
attempt to create a team list. (Apparently for unclear reasons this needs
to be on lists.ubuntu.com.) I'll delete it.
- Martin
--
ubuntu-distributed-devel mailing list
ubuntu-distributed-devel@lists.ubuntu.com
Modify
66 matches
Mail list logo
