[00:08] <Odd_Bloke> If a bug has inadvertently been fixed since it was filed, should I mark it "Fix Released" or "Invalid"?
[00:11] <jelmer> abentley: did anything change in bundlebuggy's storage format recently?
[00:11] <jelmer> I'm getting schema errors now
[00:30] <ubotu> New bug: #164613 in bzr "``bzr check`` cannot be run on a repository" [Undecided,New] https://launchpad.net/bugs/164613
[00:45] <lifeless> orospakr: fixed, and the releasse it was fixed in as the tag
[00:45] <lifeless> meh
[00:45] <lifeless> Odd_Bloke: ^
[00:46] <orospakr> heh.
[00:46] <lifeless> sorry orospakr
[00:46] <orospakr> YOU'VE RUINED MY LIFE
[00:47] <lifeless> its true
[00:47] <Odd_Bloke> Heh.
[00:52] <lifeless> Odd_Bloke: bug 64783 is not fixed
[00:52] <ubotu> Launchpad bug 64783 in bzr ""bzr check" returns unhelpful "No WorkingTree" error" [Medium,Fix released] https://launchpad.net/bugs/64783
[00:53] <lifeless> Odd_Bloke: and I'm not working on it :)
[00:56] <Odd_Bloke> lifeless: It's happy to check branches without a working tree (removing one of the instances of the error) and reports that there isn't a branch when run directly on a repository.  I've filed bug #164613 for the lack of repository checking.
[00:56] <ubotu> Launchpad bug 164613 in bzr "``bzr check`` cannot be run on a repository" [Undecided,New] https://launchpad.net/bugs/164613
[00:57] <Odd_Bloke> lifeless: And I assigned it to you as it was fixed (or so I thought :p) in one of your branches.
[01:01] <lifeless> Odd_Bloke: well the initial bug report covers the repository case
[01:01] <lifeless> so I think a new bug report is just noise
[01:01] <lifeless> part of the initial report is corrected, but not all of it.
[01:04] <Odd_Bloke> lifeless: Sure.  I've invalided bug #164613.  Apologies for taking your time.
[01:04] <ubotu> Launchpad bug 164613 in bzr "``bzr check`` cannot be run on a repository (dup-of: 64783)" [Undecided,Invalid] https://launchpad.net/bugs/164613
[01:04] <ubotu> Launchpad bug 64783 in bzr ""bzr check" returns unhelpful "No WorkingTree" error" [Medium,Triaged] https://launchpad.net/bugs/64783
[01:05] <lifeless> Odd_Bloke: no problem, I appreciate you putting time into bug database management
[01:06] <lifeless> its prompted me to cleanup bug 64783 to be more clear about what it really represents
[01:06] <ubotu> Launchpad bug 64783 in bzr ""bzr check" does not handle our split up .bzr layout properly (Errors if there is no branch)" [Medium,Triaged] https://launchpad.net/bugs/64783
[01:15] <poolie_> lifeless: text:tar_exporter.py-20051114235828-1f6349a2f090a5d0 corrupt: line-delta from stream references missing parent jaq@spacepants.org-20051229032631-adc1a9413791860f
[02:45]  * igc lunch
[03:05] <ubotu> New bug: #164626 in bzr "branching from hpss doesn't preserve repository format" [Undecided,New] https://launchpad.net/bugs/164626
[03:10] <ubotu> New bug: #164628 in bzr "branching from hpss doesn't preserve repository format" [High,Confirmed] https://launchpad.net/bugs/164628
[03:44] <abentley> jelmer: yes.  I replied to your email.
[03:45] <abentley> Run the "migrate" script.
[06:07] <lifeless> time for turkish
[06:37] <somerville33> How do I clean a branch?
[06:38] <somerville33> ie. remove all the uncommitted changes
[06:42] <poolie_> somerville33, 'bzr revert'
[06:42] <somerville33> I tried that
[06:42] <somerville33> Does it get rid of "unknowns"?
[06:45] <poolie_> no, it doesn't
[06:45] <poolie_> you can use, on unix,
[06:45] <poolie_> bzr ls --unknown |xargs rm -v
[06:45] <poolie_> or install the bzrtools plugin, and use the 'clean-tree' command
[06:54] <somerville33> What does this mean? bzr: ERROR: Generic bzr smart protocol error: <Fault 8002: 'error'>
[07:14] <ubotu> New bug: #164637 in bzr "hpss data_stream from pack repository has deltas out of order, fails with KnitCorrupt exception" [Critical,Confirmed] https://launchpad.net/bugs/164637
[07:38] <poolie_> somerville33, is that coming from launchpad?
[07:39] <poolie_> somerville33, i'm not sure but i think it may mean the path is wrong
[07:39] <poolie_> https://bugs.edge.launchpad.net/launchpad-bazaar/+bug/145894
[07:39] <ubotu> Launchpad bug 145894 in launchpad-bazaar ""Fault 8002" when pushing a branch to an unregistered project" [Medium,Fix released]
[07:40] <ubotu> New bug: #164639 in bzr "rich-root format should use packs" [High,Confirmed] https://launchpad.net/bugs/164639
[07:51] <jamesh> mwhudson was doing some work to improve the error handling to produce better error messages.  I think that is due for the next rollout
[07:51] <jamesh> so hopefully it'll be live on Monday
[08:01] <poolie_> yay
[08:06] <jamesh> If it is pushing to a branch that does not exist, it should actually display "Product foo does not exist." to the user
[08:06] <jamesh> s/branch/product/
[08:06] <jamesh> garr - that should be "Project foo does not exist." :(
[09:36] <acuster> Hey all, having trouble getting started with a repo setup. I have an svn checkout that i'd like to use within bzr
[09:37] <acuster> i'm currently avoiding bzr-svn because it seems to require hitting the network
[09:37] <acuster> I'd like to init-repo and then add trunk/
[09:38] <acuster> if i do (1) init-repo (2) cp trunk . (3) init trunk/ I get two .bzr directories
[09:38] <acuster> one in the repo and one in trunk/
[09:38] <acuster> is that expected?
[09:39]  * acuster tries without the repo
[09:40] <fullermd> Yes, that's expected.
[09:40] <fullermd> The top-level .bzr/ contains your repo, and the .bzr/ in trunk contains the branch and WT metafiles.
[09:42] <acuster> thanks
[09:43] <acuster> what do I branch and checkout from then, the repo or the branch?
[09:44] <fullermd> The branch.
[09:45] <fullermd> Repos are just used to share storage.  You don't refer to them directly (except when making them, of course).  You don't particularly need to use them, especially with only one branch (doesn't gain you anything until you have two with shared history)
[09:46] <acuster> thanks
[10:13] <igc> night all - have a good weekend
[10:40] <dato> if I have a bug reported in Debian's BTS (Debian #452503), can I automatically import it into launchpad?
[10:40] <ubotu> Debian bug 452503 in bzr "bzr: gets confused when editor is killed" [Minor,Open] http://bugs.debian.org/452503
[10:40] <dato> or do I have to enter it by hand, and link them by hand as well?
[10:42] <Kamping_Kaiser> iirc you have to file a new bug and link it
[11:05] <acuster> The --trees/--no-trees command when making a shared repo only affects the behaviour of the bzr branch command?
[11:33] <acuster> to get rid of a branch we merely rm -Rf it?
[11:34] <acuster> what impact does that have on the shared repository?
[11:34] <dato> its revision will stay, unaccessible
[11:34] <acuster> no way to clean that up?
[11:34] <dato> but there is no way to clean them up, at the moment
[11:34] <acuster> thanks
[11:40] <acuster> am I right that the 'trees' flag in shared repos only affects whether branch also checks out a working tree?
[11:42] <dato> I believe so
[11:48] <fullermd> It probably affects (and if it doesn't, it should) other stuff that makes a branch, like init and push.  I know push was fixed recently...
[12:03] <acuster> wow bzr-svn is way faster now
[17:19]  * bitmonk wonders if there area reasons bzr would be especially resistant to working on alternative python implementations..
[17:20] <bitmonk> er s/area/are/
[17:20] <jelmer> it doesn't rely on any C extensions to be able to work (though it will be faster if they're available)
[17:21] <jelmer> so nothing I can think of immediately
[17:21] <bitmonk> does it require setuptools?
[17:21] <jelmer> no, it uses distutils
[17:21] <bitmonk> hm.
[17:22] <jelmer> what sort of things are usually problematic?
[17:22] <bitmonk> well, my target is pypy on mono.
[17:22] <bitmonk> you can't use setuptools or distutils on mono really.  it's a whole 'nother world.
[17:22] <bitmonk> at least i can't quite fathom how to.  i'm sure it's possible, but it sure doesn't work today.
[17:22] <jelmer> you should be able to use bzr out of the source directory
[17:23] <bitmonk> yeah i imagine so..
[17:23] <bitmonk> distutils and setuptools are just friendly helpers.
[17:23] <bitmonk> well, thanks.  i will give it a shot next time i'm looking for fun ;d
[17:23] <mwhudson> i doubt pypy-cli has gzip/bz2 support yet
[17:23] <bitmonk> maybe run some benchmarks
[17:23] <bitmonk> mwhudson: it may not.
[17:24] <bitmonk> but i bet i could access gzip/bz2 support via the cli, even if with a penalty.
[17:24]  * bitmonk is looking more for a 'fathomable project' than a 'working today solution'
[17:24] <mwhudson> can't think of anything else that shouldn't work
[17:24] <bitmonk> awesome
[17:24] <bitmonk> i probably should spend some more time with bzr on cpython first, so that i know how to recognize odd behaviour ;d
[17:26] <ubotu> New bug: #164714 in bzr-eclipse "Whitespace in directory name" [Undecided,New] https://launchpad.net/bugs/164714
[17:30] <TeTeT> is there a way to reduce the disk footprint of a branch? The shared repository with the ubuntu-desktop-course branch occupies 720MB right now
[19:10] <keir> so is 1.0 really going to be released next?
[20:10] <chx> hi
[20:10] <chx> I visited http://bazaar.launchpad.net/~vcs-imports/drupal/main and was surprised.
[20:10] <chx> The requested URL /00/00/0a/af was not found on this server.
[20:11] <chx> oh. i guess wrong channel. moving to #launchpad...
[21:36] <ubotu> New bug: #62249 in bzr "merge from bundles should support io redirection" [Undecided,Incomplete] https://launchpad.net/bugs/62249
[21:41] <ubotu> New bug: #62521 in bzr "bzr should run without bzrlib.tests installed." [Undecided,Incomplete] https://launchpad.net/bugs/62521