[00:32] -queuebot:#ubuntu-release- Unapproved: supertux (xenial-proposed/universe) [0.4.0-1 => 0.4.0-1ubuntu1] (no packageset)
[09:16] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (yakkety-proposed) [2.02~beta2-36ubuntu11.1]
[09:16] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (yakkety-proposed) [2.02~beta2-36ubuntu11.1]
[09:23] <Laney> if anyone is good at alignment issues
[09:23] <Laney> pdl/armhf...
[09:27] <Laney> xnox: could you look at libterm-readline-gnu-perl and libtext-bibtex-perl which both fail on s390x please?
[09:27] <Laney> even if to decide if they should be removed
[09:34] <cjwatson> robru,oSoMoN: you don't need to ask me whether it's in production yet, just watch the status of the Launchpad task on https://bugs.launchpad.net/launchpad/+bug/1633608 (though I don't recall whether this will apply to copies)
[09:34] <ubot5`> Ubuntu bug 1633608 in Launchpad itself "Bileto PPA upload rejections are lost to the ether" [High,In progress]
[09:35] <oSoMoN> cjwatson, thanks, I subscribed to the bug
[09:54]  * cjwatson blacklists the GHC 8 transition for now
[09:54] <cjwatson> (this time in a less hacky way)
[10:03] <xnox> Laney, i want to say that those failures are normal, because terminals are weird on s390x. Let try building it on a possibly slightly more conventional installation, to see if e.g. the launchpad builder's configuration can be tweaked.
[10:03] <xnox> however these things did build before. somehow.
[10:22] <apw> cjwatson, is there any way we could get the rejection messages to queuebot ?
[10:23] <apw> cjwatson, or perhaps cc: the emails to -changes or something
[10:28] <cjwatson> a few years ago there was a bunch of work to store them for later auditing
[10:28] <cjwatson> but it was never quite completed
[10:28] <cjwatson> probably better to finish that than to add hacks
[10:35] <xnox> Laney, https://launchpad.net/ubuntu/+source/libtext-bibtex-perl/0.76-1ubuntu1
[10:35] <xnox> and https://rt.cpan.org/Public/Bug/Display.html?id=96593
[10:36] <Laney> xnox: nice, that's a handy find
[10:43]  * Laney might have a patch for pdl
[10:43]  * Laney is new to this alignment shizzle though
[10:43]  * Laney test builds
[10:49] <xnox> Laney, somehow readline state ends up as NONE(0) instead of INITIALIZED(2), there is INITIALIZING(1) in between as well.
[10:49] <xnox> enoclue at the moment why =)
[10:51] <xnox> found it, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840689 will get a better fix for it, but first coffee.
[10:51] <ubot5`> Debian bug 840689 in libterm-readline-gnu-perl "libterm-readline-gnu-perl: FTBFS on 64-bit big endian architectures" [Serious,Open]
[11:09] <Laney> xnox: yeah, saw that - the upstream dude says he will do a proper fix, whatever that means :-)
[11:10] <xnox> it means use unsigned, when unsigned is due
[11:15] <apw> xnox, hopefully it means use long when long is due
[11:15] <Laney> always long your longs
[11:16] <xnox> yeah.
[11:16] -queuebot:#ubuntu-release- Unapproved: webbrowser-app (xenial-proposed/main) [0.23+16.04.20160413-0ubuntu1 => 0.23+16.04.20161028-0ubuntu1] (ubuntu-desktop, ubuntu-qt-packages) (sync)
[11:16] <xnox> Gnu.xs:539:5: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types] horum. I fail this morning
[11:16] <apw> it was broken then moment they had a cast in there to anything other than void*
[11:23] <xnox> needs patching perl code as well. and magic bridge functions to/from C
[11:23] <xnox> argh
[11:33] <apw> xnox, if there is a proper upstream fix coming ... could we not use the dirty hack until it comes ?
[11:34] <xnox> apw, well dirty hack is scary to me =) if 64 bit, and if big endian, point randomly to the next memory address, as that will be the "right" half of long.
[11:34] <xnox> I think i have it properly in a second. And if not, will upload dirty hack.
[11:34] <apw> xnox, the layout of a long in BE is pretty well defined
[11:34] <xnox> true
[11:35] <apw> what they are doing makes me physically sick, but it likely is "safe"
[11:35] <xnox> there is handing for charp vs pint, adding pulong there.
[11:36] <xnox> to keep up with their sickness
[11:50] <xnox> Laney, apw - https://rt.cpan.org/Public/Bug/Display.html?id=118371#txn-1679838
[11:50] <xnox> uploaded
[11:52] <xnox> all is good https://launchpad.net/ubuntu/+source/libterm-readline-gnu-perl/1.34-1ubuntu1
[11:53] <Laney> xnox: Ta
[11:54] <Laney> and my pdl seems to build so I'll copy that
[11:55] <xnox> apw, wanna shed some light into bus errors that started to appear on armhf in the galera-3 icinga2 and percona-galera-3 packages? http://people.canonical.com/~ubuntu-archive/transitions/html/boost1.61.html
[11:55] <xnox> i have a theory that the new arm64 builders are better at emitting bus errors, and they simply were there the whole time.
[11:56] <xnox> i.e. unaligned access or some such.
[11:56] <Laney> unaligned access indeed
[11:56] <xnox> also have you ever seen this before: https://launchpadlibrarian.net/291194249/buildlog_ubuntu-zesty-s390x.libbitcoin_2.11.0-1ubuntu1_BUILDING.txt.gz
[11:56] <xnox> devlibs error: There is no package matching [ld64-1-dev] and noone provides it, please report bug to d-shlibs maintainer
[11:57] <xnox> ah https://lists.debian.org/debian-mentors/2016/06/msg00648.html
[12:00] <doko> xnox: the change to 64bit kernels triggered a few unaligned accesses for armhf, but I'm not aware of any triggered on arm64
[12:00] <xnox> doko, right, i see three new failures / unagligned accesses triggered on armhf.
[12:00] <xnox> =(
[12:01]  * xnox is reading https://lists.debian.org/debian-mentors/2016/06/msg00652.html and does not understand
[12:01] <cjwatson> We're intentionally not putting any effort into that because it brings us closer to where we wanted to be anyway for phones
[12:01] <cjwatson> (Because the Android kernel does much the same thing; there was previously a problem whereby stuff would succeed on builders and then fail on devices)
[12:02] <cjwatson> So the unaligned accesses should be fixed in packages
[12:02] <xnox> yeah, i understand that the right thing to do is to fix the packages.
[12:51] <Laney> slangasek: I don't understand https://bazaar.launchpad.net/~ubuntu-release/britney/hints-ubuntu/revision/2074 - doesn't look like they were gone from proposed to me?
[12:51] <Laney> and they've moved back to release now
[12:55] <xnox> Laney, slangasek - i wonder if we can remove remaining broken / untransitioned binaries for perl to get it migrate. =) or are they non-leaf packages?
[12:55] <xnox> as in is all of uwsgi, or just the perl uwsgi?
[12:59] <Laney> xnox: They were demoted
[12:59] -queuebot:#ubuntu-release- Unapproved: metacity (xenial-proposed/main) [1:3.18.7-0ubuntu0.1 => 1:3.18.7-0ubuntu0.2] (ubuntu-desktop)
[13:00] <Laney> I guess we'll see what britney has to say about it (if it's only these packages or if there are other problems too)
[13:00] <xnox> Laney, but you should remove binaries & demote src to -proposed. That way it will be stuck with failure to build and will not migrate by virtue of miracles.
[13:00] <xnox> or keep a block-proposed bug against them.
[13:01] <Laney> They were blocked
[13:01] <xnox> ok. /me goes back to finishing boost1.61 transition laggers =)
[13:02] <Laney> there's a few random failures @ proposed-migration
[13:23] <apw> Laney, there appear to be a coulple of cases where the armhf builds are missing too
[13:24] <apw> Laney, and indeed similarly for s390x, which is oddness
[13:24] <Laney> apw: I think those are ones that just got uploaded
[13:25] <apw> Laney, ahh ok, then i'll wait a bit ... before listing them
[13:26] <Laney> pdl, some readline thing
[13:26] <Laney> and something else
[13:26] <apw> pdl yay
[13:37] <xnox> slangasek, powerpc dropped as release arch in debian
[14:01] -queuebot:#ubuntu-release- Unapproved: ido (xenial-proposed/main) [13.10.0+15.10.20151002-0ubuntu1 => 13.10.0+16.04.20161028-0ubuntu1] (ubuntu-desktop) (sync)
[14:16] <Laney> Just those few (re)removals and autopkgtest failures then
[14:36] -queuebot:#ubuntu-release- Unapproved: apt (xenial-proposed/main) [1.2.14 => 1.2.15] (core)
[15:32] -queuebot:#ubuntu-release- Unapproved: nova-lxd (xenial-proposed/main) [13.0.0-0ubuntu3 => 13.0.0-0ubuntu3.1] (ubuntu-server)
[15:57] <slangasek> Laney: I did remove those packages from zesty-proposed; which ones do you see still there, at the perl 5.22 versions?
[15:58] <slangasek> Laney: regardless, demoting them to -proposed was the wrong thing in the first place
[16:00] <slangasek> Laney: it's possible there was a race between my removal being processed, and p-m re-copying them from -proposed after I dropped the hints but before the publisher had finished making them disappear from -proposed; this was all done during the window when publishing was really slow
[16:00] <slangasek> Laney: (re-removed now from zesty)
[16:00] <Laney> slangasek: Riiiight - so what's your rule of thumb for demotion vs removal then?
[16:01] <slangasek> Laney: the only time we ought to demote a package is if it depends on something else that's being removed, but itself is not buggy and requires no changes to become installable
[16:02] <Laney> slangasek: If you remove them, they won't come back via autosync, right?
[16:02] <slangasek> Laney: they absolutely will
[16:03] <Laney> I thought it checked for an explicit removal
[16:03] <slangasek> which is what we want to happen, if the package has gotten an upload in Debian that (hopefully) fixes the RC bug that got it removed from testing
[16:03] <slangasek> if it does, that's news to me and behavior that I think should be corrected
[16:03] <slangasek> it won't try to re-autosync at the same /version/
[16:04] <Laney> I certainly see entries that look like that in http://people.canonical.com/~ubuntu-archive/auto-sync/current.log
[16:04] <cjwatson> Uh
[16:04] <Laney> salmon, sga
[16:04] <cjwatson> slangasek: Checking for removals was absolutely deliberate and not something I think should be corrected
[16:04] <Laney> (So that's why I was asking for demotion rather than removal)
[16:05] <slangasek> cjwatson: really?  I thought we had the sync-blacklist for things we were removing and didn't want back
[16:05] <cjwatson> slangasek: That was a nightmare
[16:05] <slangasek> hmm
[16:05] <slangasek> well, I didn't get the memo that this behavior had ever changed ;)
[16:05] <cjwatson> slangasek: It was around the time auto-sync moved to client side, and I banged on about it for a while :)
[16:05] <slangasek> and, as I commented on ubuntu-release, leaving stuff in -proposed is also a bit of a nightmare
[16:06] <cjwatson> IMO and IME auto-syncing stuff that's been removed is just too error-prone
[16:06] <slangasek> I'd much rather require AAs to maintain the sync-blacklist (which I still was!) than to bump stuff in -proposed and make update_excuses unusable
[16:06] <slangasek> :/
[16:07] <cjwatson> The auto-sync log shows what hasn't been synced due to a previous removal
[16:07] <cjwatson> I think it's sufficient to just take a brief glance through that from time to time
[16:07] <slangasek> ok
[16:07] <cjwatson> (I used to do that)
[16:08] <slangasek> but if my first inclination, when glancing at what's not been synced for this reason, is to sync them all and see what sticks? :)
[16:08] <slangasek> anyway
[16:08] <slangasek> gotta go chase dinner on the streets of Bucharest now
[16:08] <cjwatson> slangasek: the auto-sync log tries to give you an indication of why things were removed
[16:09] <cjwatson> IME it's a mix of short-term and long-term reasons
[16:09] <cjwatson> I don't at all object to things being added to the sync-blacklist when the decision is that they should never be shipped in Ubuntu
[16:10] <Laney> apw: Could you take care of my 4 new requests on https://bugs.launchpad.net/ubuntu/+source/kvirc/+bug/1636804 please?
[16:10] <ubot5`> Ubuntu bug 1636804 in nama (Ubuntu) "perl 5.24 demotions" [Undecided,New]
[16:10] <cjwatson> But quite often the next Debian upload after a removal doesn't in fact address the reason it was removed in Ubuntu, e.g. due to stricter build requirements; or the last version in Ubuntu had a delta that should be reapplied if the package is reintroduced
[16:10] <Laney> I don't know if this conversation establishes a new rule about whether you should remove or demote, sorry :(
[16:10] <cjwatson> And there was an antipattern I observed where people added stuff to the sync-blacklist that wasn't actually for a long-term reason
[16:11] <cjwatson> For instance, people were blacklisting things that were removed because they currently failed to build
[16:11] <cjwatson> That was really undiscoverable and so a bunch of packages were inadvertently not shipped when they could have been
[16:11] <cjwatson> So I tried to push for blacklisting only for long-term reasons
[16:12] <Laney> I like(d) using demotion of in-sync things to mean "this will probably be fixed by the next autosync"
[16:12] <Laney> I grant that it does cause excuses to become cluttered if that takes a while
[16:12] <cjwatson> I think it would be good to surface auto-sync's log output in a less plaintexty way
[16:33] <xnox> slangasek, imho removing binaries + demote src to -proposed is fine. and let those things stuck failing to build.
[16:33] <xnox> and auto-sync back in, if and when debian fixes things.
[16:34] <xnox> we need to mimic "removed from testing, broken in sid" somehow on our side.
[16:40] -queuebot:#ubuntu-release- New binary: libcgicc [ppc64el] (zesty-proposed/universe) [3.2.16-0.1~build1] (no packageset)
[16:40] -queuebot:#ubuntu-release- New binary: libcgicc [amd64] (zesty-proposed/universe) [3.2.16-0.1~build1] (no packageset)
[16:40] -queuebot:#ubuntu-release- New binary: libcgicc [armhf] (zesty-proposed/universe) [3.2.16-0.1~build1] (no packageset)
[16:40] -queuebot:#ubuntu-release- New binary: libcgicc [arm64] (zesty-proposed/universe) [3.2.16-0.1~build1] (no packageset)
[16:42] -queuebot:#ubuntu-release- New binary: libcgicc [i386] (zesty-proposed/universe) [3.2.16-0.1~build1] (no packageset)
[16:43] -queuebot:#ubuntu-release- New binary: libcgicc [powerpc] (zesty-proposed/universe) [3.2.16-0.1~build1] (no packageset)
[16:43] -queuebot:#ubuntu-release- New binary: libcgicc [s390x] (zesty-proposed/universe) [3.2.16-0.1~build1] (no packageset)
[17:26] <wxl> so ppc has been dropped as a release architecture from debian. does that mean we're going to be canning the support in ubuntu? (note this does NOT apply to ppc64el) https://lists.debian.org/debian-powerpc/2016/10/msg00125.html
[17:30] <mdeslaur> wxl: infinity's main workstation is a powerpc ;)
[17:39] <wxl> mdeslaur: so i guess i shouldn't expect a response from him any time soon XD
[17:44] -queuebot:#ubuntu-release- New: accepted fwupd [amd64] (zesty-proposed) [0.7.4-2]
[17:46] <balloons> cyphermox, slangasek, I have confirmed $DPKG_MAINTSCRIPT_ARCH is blank during initial installation. This causes the debconf message about invalid arch to appear on valid architecture systems. How would you like to fix the logic?
[19:02] -queuebot:#ubuntu-release- Unapproved: isc-dhcp (precise-proposed/main) [4.1.ESV-R4-0ubuntu5.11 => 4.1.ESV-R4-0ubuntu5.12] (core)
[19:03] -queuebot:#ubuntu-release- Unapproved: isc-dhcp (trusty-proposed/main) [4.2.4-7ubuntu12.7 => 4.2.4-7ubuntu12.8] (core)
[19:04] -queuebot:#ubuntu-release- Unapproved: isc-dhcp (xenial-proposed/main) [4.3.3-5ubuntu12.3 => 4.3.3-5ubuntu12.4] (core)
[19:04] -queuebot:#ubuntu-release- Unapproved: isc-dhcp (yakkety-proposed/main) [4.3.3-5ubuntu15 => 4.3.3-5ubuntu15.1] (core)
[19:06] -queuebot:#ubuntu-release- Unapproved: nova (xenial-proposed/main) [2:13.1.1-0ubuntu1.1 => 2:13.1.2-0ubuntu2] (openstack, ubuntu-server)
[19:25] -queuebot:#ubuntu-release- Unapproved: rejected nova [source] (xenial-proposed) [2:13.1.2-0ubuntu2]
[19:38] -queuebot:#ubuntu-release- Unapproved: openstack-trove (xenial-proposed/universe) [1:5.1.1-0ubuntu1 => 1:5.1.1-0ubuntu2] (no packageset)
[19:48] <cyphermox> balloons: I think we want not DPKG_MAINTSCRIPT_ARCH in the .config file; I shipped an attempt at fixing this in my PPA friday, I will look in a few seconds
[19:48] <cyphermox> can someone please reject shim-signed in yakkety queue?
[19:48] <balloons> cyphermox, ack. I switched it out to replace the arch by using deb_host_arch in rules, and writing out the config.in file
[19:49] <balloons> what do you think of that approach?
[19:49] <cyphermox> yuck
[19:49] <cyphermox> but hey, if it works...
[19:49] <cyphermox> I'd need to see the diff
[19:52] <balloons> cyphermox, heh. Well I can say just pushing back the dpkg --print-architecture version does work
[19:52] <balloons> would you prefer that?
[19:53] <cyphermox> yea, I would
[19:54] <cyphermox> want to get me a debdiff against the juju currently in proposed, I could sponsor that now? :)
[19:54] <balloons> sure thing. I have one for yak/zest too
[19:58] <cyphermox> what for? that one wouldn't prompt
[19:58] <cyphermox> but we also need the xenial
[19:59] <balloons> cyphermox, ohh, for the missing dh_install and missing dependency in the first upload
[19:59] <cyphermox> oh, right
[20:01] <cyphermox> jderose: hey
[20:01] <jderose> cyphermox: hey back :)
[20:16] -queuebot:#ubuntu-release- Unapproved: accepted nova [source] (xenial-proposed) [2:13.1.2-0ubuntu2]
[20:19] <balloons> cyphermox, xenial: http://paste.ubuntu.com/23408418/
[20:20] -queuebot:#ubuntu-release- Unapproved: accepted nova-lxd [source] (xenial-proposed) [13.0.0-0ubuntu3.1]
[20:26] <balloons> cyphermox, I hope this works for yakkety/zesty: http://paste.ubuntu.com/23408442/
[20:31] <cyphermox> can we close a bug that describes the regression on yakkety/zesty please?
[20:32] <cyphermox> and is there one for the prompting on xenial?
[20:34] <balloons> cyphermox, ohh, new bugs? This is follow-up imho on the current SRU bugs
[20:35] <balloons> I need to put verification failed in there, or however you wish
[20:35] <cyphermox> I think we might want to track them separately on account of having to upload on top of something already in proposed
[20:35] <cyphermox> or maybe re-close, yeah,
[20:36] <balloons> I would typically see it as verification failed, new upload, re-verify
[20:36] <cyphermox> wfm
[20:36] <balloons> I guess we should re-mention the specific bugs?
[20:36] <cyphermox> yes
[20:37] <balloons> cyphermox, bug 1631038 for sysctl. We don't technically have a bug for the arch issues in the conf script. I guess I would use bug 1617440
[20:37] <ubot5`> bug 1631038 in juju-release-tools "Need /etc/sysctl.d/10-juju.conf" [High,Fix committed] https://launchpad.net/bugs/1631038
[20:37] -queuebot:#ubuntu-release- Unapproved: shim-signed (yakkety-proposed/main) [1.21.3 => 1.21.4] (core)
[20:37] <ubot5`> bug 1617440 in juju-core (Ubuntu Yakkety) "[SRU] Juju 2 GA" [High,Fix committed] https://launchpad.net/bugs/1617440
[20:38] <cyphermox> isn't there something for the no-longer-supports-32bit?
[20:39] <slangasek> cjwatson: +1 for only blacklisting due to long-term issues; -1 for pushing to -proposed, which leaves the bottom of update_excuses full of things that are not actionable :)
[20:39] <balloons> cyphermox, bug 1614969
[20:39] <ubot5`> bug 1614969 in juju-core-1 (Ubuntu) "Juju packaging allows builds for unsupported architectures" [Undecided,New] https://launchpad.net/bugs/1614969
[20:40] <slangasek> balloons: "blank during initial installation" - er it should always be set, whether initial install or upgrade.... oh, are you checking this variable from the .config script?
[20:40] <slangasek> right, cyphermox responded. ok
[20:40] <balloons> slangasek, yep. Absolutely confirmed nothing is set when run during install
[20:41] <slangasek> balloons: it's not 'during install', it's "when used from the .config script"
[20:41] <slangasek> because the .config script is called from apt initially, /not/ via dpkg
[20:41] <balloons> slangasek, it IS set if I run a dpkg-reconfigure. sure ...
[20:43] -queuebot:#ubuntu-release- Unapproved: rejected shim-signed [source] (yakkety-proposed) [1.21.4]
[20:43] <balloons> slangasek, are you comfortable then just using dpkg --print-architecture for the config?
[20:43] <balloons> I converted the config file to use a .in file, and set it based on DEB_HOST_ARCH in debian rules and was playing with that, but it wasn't as desired, so, we're back to as it was
[20:44] <slangasek> balloons: yes, in that context it's probably better
[20:56] <cyphermox> slangasek: all good, I'll do the sponsorings for balloons now
[21:05] <cyphermox> slangasek: could you please also review that new shim-singed? :)
[21:07] <ginggs> shim-singed as in sung or slightly burnt?
[21:08] <slangasek> cyphermox: probably not tonight yet, sorry
[21:08] <cyphermox> ginggs: as in slightly burnt
[21:08] <cyphermox> permanently-renamed, too
[21:08] <cyphermox> maybe I'll consider shim-sung for the next upload
[21:09] <cyphermox> slangasek: ack
[21:24] -queuebot:#ubuntu-release- Unapproved: juju-core (xenial-proposed/main) [2.0.0-0ubuntu<IP_ADDRESS> => 2.0.0-0ubuntu<IP_ADDRESS>] (ubuntu-server)
[21:24] -queuebot:#ubuntu-release- Unapproved: juju-core (yakkety-proposed/main) [2.0.0-0ubuntu<IP_ADDRESS> => 1:2.0.0-0ubuntu<IP_ADDRESS>] (ubuntu-server)
[21:24] <cyphermox> please reject juju-core in yakkety
[21:24] <cyphermox> crap :/
[21:26] <cyphermox> ^ epoch is very bad, shouldn't have been in that debdiff
[21:26] <cyphermox> bad ballons ;)
[21:26]  * tsimonq2 gives balloons the epoch hat
[21:26] <stgraber> done
[21:26]  * balloons feels ashamed
[21:27] -queuebot:#ubuntu-release- Unapproved: rejected juju-core [source] (yakkety-proposed) [1:2.0.0-0ubuntu<IP_ADDRESS>]
[21:27] <cyphermox> stgraber: ta
[21:27] <tsimonq2> balloons: Don't worry, you don't have to wear it as long as the Ducky Tie. :P
[21:28] <stgraber> balloons: we'll find you a corner to sit in next week :)
[21:28] <cyphermox> balloons: there was another subtle issue too, see if you can spot it ;)
[21:28] <balloons> yea. I wonder how many minutes (days?!) I'll have to do that
[21:28] <tsimonq2> stgraber: You guys going to a sprint next week? Make him an actual physical epoch hat. XD
[21:29] <tsimonq2> heheheheheheheheh ;)
[21:29] <stgraber> yeah, bunch of us sprinting in Budapest next week :)
[21:29] <cyphermox> balloons: that would be scary, if there were seconds involved.
[21:29] <tsimonq2> stgraber: Oh nice! :D
[21:29] <stgraber> cyphermox: already in Santa Fe I take it?
[21:29] <stgraber> cyphermox: I'm on a plane to Denver here
[21:30] <cyphermox> yes, already there, about to leave for dinner
[21:30] <stgraber> isn't 3pm a bit early for dinner? :)
[21:30] <balloons> he's stuck fixing my epochs
[21:30] <cyphermox> (basically, as soon as I'm done with this, then I'll be back after)
[21:30] <tsimonq2> balloons: XD
[21:30] <cyphermox> 3pm US dinner.
[21:31] <cyphermox> wait wat
[21:31] -queuebot:#ubuntu-release- Unapproved: juju-core (yakkety-proposed/main) [2.0.0-0ubuntu<IP_ADDRESS> => 2.0.0-0ubuntu<IP_ADDRESS>] (ubuntu-server)
[21:31] <cyphermox> annoying clocks.
[21:31] <tsimonq2> I'm handing out halloween candy, so I can munch on that. :P
[21:34] <cyphermox> stgraber: feels like it's way beyond 3pm here, and even way past 5pm cyphermox-standard-time. perhaps I've been up for too long.
[21:36] <stgraber> that's why I booked late flights, get to sleep in before leaving and not see the timezone change :)
[21:36] <stgraber> though that's just 2 hours west, the 9 hours east I'll have next weekend will be a bit harder to deal with I suspect ;)
[21:36] <cyphermox> pfft
[23:53] -queuebot:#ubuntu-release- New binary: libcgicc [amd64] (zesty-proposed/universe) [3.2.16-0.1] (no packageset)
[23:53] -queuebot:#ubuntu-release- New binary: libcgicc [ppc64el] (zesty-proposed/universe) [3.2.16-0.1] (no packageset)
[23:54] -queuebot:#ubuntu-release- New binary: libcgicc [arm64] (zesty-proposed/universe) [3.2.16-0.1] (no packageset)
[23:54] -queuebot:#ubuntu-release- New binary: libcgicc [i386] (zesty-proposed/universe) [3.2.16-0.1] (no packageset)
[23:54] -queuebot:#ubuntu-release- New binary: libcgicc [armhf] (zesty-proposed/universe) [3.2.16-0.1] (no packageset)
[23:54] -queuebot:#ubuntu-release- New binary: libcgicc [s390x] (zesty-proposed/universe) [3.2.16-0.1] (no packageset)
[23:54] -queuebot:#ubuntu-release- New binary: libcgicc [powerpc] (zesty-proposed/universe) [3.2.16-0.1] (no packageset)


[00:00] <lifeless> yes, I can understand that
[00:00] <lifeless> I think its reasonable to write a plugin to encode/decode bad names
[00:00] <sportman1280> ok well question then.  the filename. does it just have to be valid CURRENTLY, or does it have to be valid all trough the repository history.  we have 10,000 revisions....
[00:01] <sportman1280> so if i can just change the file thats in the svn repository, then thats great
[00:01] <lifeless> sportman1280: if you are converting all your history, it has to be valid for all of history. Are you wanting to evaluate bzr to move to it, or you just want to use it to hack on current code?
[00:01] <sportman1280> lifeless: the plan is to move to it
[00:02] <lifeless> sportman1280: I'd look at editing a fastexport dump then, I think its probably best overall
[00:02] <sportman1280> ok. now i have to figure out how to fastexport svn
[00:02] <sportman1280> thanks
[00:03] <sportman1280> btw, i agree there should be a plugin that can handle these situations :(
[00:04] <sportman1280> lifeless: ok the fast importer. i played with it for hours earlier today. but had no success at even running it. any help?  i have the plugin installed int he .bazaar/plugins folder
[00:05] <lifeless> sportman1280: well, you'll want the svn-fast-export to get your data out
[00:05] <lifeless> as for bzr fast-import, what happened when you tried to run it ?
[00:05] <lifeless> does the plugin show up in 'bzr plugins'
[00:05] <sportman1280> thats the thing i couldnt get it to run at all
[00:07] <sportman1280> http://pastebin.com/m661c1d68
[00:08] <lifeless> ok, thats the fast-export side
[00:08] <lifeless> you need pysvn installed from the look of it
[00:11] <sportman1280> ok done trying again
[00:13] <sportman1280> lifeless: I still get the same error :(
[00:14] <lifeless> what does 'python -c import svn' do?
[00:14] <lifeless> mwhudson: do you recall which package has the python module 'svn'
[00:14] <mwhudson> i think that's the python-subversion bindings that you have to read the C api docs to use
[00:15] <lifeless> sportman1280: which precise package did you install; there are multiple python svn bindings
[00:15] <mwhudson> (package is called python-subversion iirc)
[00:15] <sportman1280> python-svn is the only one i saw
[00:16] <sportman1280>  python -c import svn
[00:16] <sportman1280>   File "<string>", line 1
[00:16] <sportman1280>     import
[00:16] <sportman1280>          ^
[00:16] <sportman1280> SyntaxError: invalid syntax
[00:16] <lifeless> try 'python-subversion'
[00:18] <sportman1280> lifeless: it can't download from a internet repository can it?
[00:18] <lifeless> sportman1280: I don't know
[00:18] <sportman1280> lifeless: dang
[00:25] <sportman1280> ok thats it. i give up. 7 hours later and the stupid thing still doesn't work. bazaar clearly just isnt meant to be used :(
[00:28] <sportman1280> now i get svn.core.SubversionException: ("Expected repository format '3' or '5'; found format '9'", 165005)
[00:28] <sportman1280> :(
[00:34] <lifeless> sportman1280: :(
[00:35] <sportman1280> lifeless: ok i'll try a little more before giving up
[00:35] <sportman1280> is there another way to dump the data and then import it back into svn?
[00:36] <lifeless> svnadmin
[02:39] <markh> is loading submodules a "supported" usecase for lazy imports - eg "from bzrlib import (ui, ui.text,)" - its failing for me in a py2exe environment...
[02:39] <markh> (with the above in a string used by the normal lazy_import stuff...)
[02:40] <spiv> markh: it is, yes.
[02:41] <spiv> I'm not sure that "from x import y.z" is used much in our lazy_imports so far, though, so there may be a bug there.
[02:41] <lifeless> markh: the brackets look odd
[02:41] <markh> bugger - that means I need to look into a lazy_import bug rather than just rearrange the imports ;)
[02:41] <lifeless> markh: try
[02:41] <lifeless> from bzrlib import ui
[02:41] <markh> lifeless: yes, the code in question is a larger block
[02:41] <lifeless> in fact
[02:41] <lifeless> what is 'from bzrlib import ui.text' *meant* to do
[02:41] <markh> in a py2exe environment, 'ui.text' causes an attribute error, and dir(ui) doesn't show a 'text' attribute.  all works fine run from source
[02:42] <spiv> lifeless: import "bzrlib.ui.text", and add "ui" to the local namespace.
[02:42] <lifeless> markh: in bzrlib.ui add a lazy_import of bzrlib.ui.text as text
[02:42] <lifeless> markh: lazy_import definitely doesn't know what to do with that import I think
[02:43] <markh> it does from source, which is strange.
[02:43] <lifeless> markh: I'm fairly sure its being masked
[02:43] <spiv> markh: from source something else might be importing it ui.text?
[02:43] <jamesh> I don't think the normal Python import statement would know what to do
[02:44] <lifeless> I've checked the code and it claims to have support for this
[02:44] <spiv> Oh, huh.
[02:44] <lifeless> markh: up to you if you want to work around or dig deep
[02:44]  * spiv wonders why he thought "from x import y.z" should work
[02:44] <lifeless> lazy_import.py line 168
[02:44] <markh> jamesh appears to be correct - its not valid Python anyway!
[02:45] <markh> "from bzrlib import ui, ui.text" is a syntax error
[02:46] <markh> lifeless: but you are saying lazy imports *should* support it regardless?
[02:46] <lifeless> markh: no
[02:46] <lifeless> I'm saying that the docstring in the code claims to support
[02:46] <lifeless> from bzrlib import ui.text
[02:47] <markh> strangely, it *does* support it!
[02:47] <markh> just not in a py2exe environment
[02:47] <jamesh> one of the perils of putting code in strings
[02:47] <lifeless> jamesh: all code is strings
[02:47] <markh> ok, thanks.  The code is in qbzr, so I'll take it up with them!
[02:48] <lifeless> markh: I would try editing ui.__init__
[02:48] <lifeless> as I suggested before
[02:49] <markh> lifeless: I'm a bit lost then - you saying it *should* support that even though it would be a syntax error in normal python, and I should edit ui.__init__ to try and make it work in a py2exe env?
[02:49] <lifeless> markh: did you see my suggesetion at 13:39?
[02:50] <jamesh> lifeless: well, in this case it'd probably be possible to write a version of lazy_imports that didn't involve embedding code in strings
[02:51] <markh> I think we have time skew, but yes.  However, I also saw your comment saying it should not support in the first place given its a syntax error, hence my confusion
[02:51] <jamesh> which would let Python parse and syntax check the imports
[02:51] <jamesh> and might let other tools see the imports without modifications
[02:52] <lifeless> jamesh: suggestions appreciated
[02:52] <lifeless> jamesh: I imagine an import hook might allow it but at a very convoluted cost
[02:52] <markh> to my mind, the code I quoted is clearly wrong as it would be a syntax error in normal cases.  So I'm still confused if the consensus is bzrlib should support it, or should barf on it...
[02:53] <markh> if it isn't that bzrlib should support it, I'm confused what my edits to __init__ would be aiming for.
[02:53] <lifeless> markh: they may work around the problem
[02:53] <markh> right - but presumably that woudn't be accepted as a patch?
[02:54] <markh> which means it doesn't actually solve the problem I'm having in binary builds that anyone else (eg, John) creates.
[02:54] <lifeless> markh: I'd accept it, as lazy importing a deep module like that is plain weird IMO
[02:54] <lifeless> markh: and it will provide info on how lazy_import may be failing
[02:54] <markh> lifeless: I'm really confused now :)  You would accept a patch that allows bzr's lazy imports to accept "plain wierd" things, rather than asking the code change to not be wierd?
[02:55] <lifeless> markh: uhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
[02:55] <lifeless> markh: AIUI you are not getting a barf, you are getting ui.text not imported
[02:55] <lifeless> so ui is imported but ui.text isn't
[02:55] <markh> my thoughts exactly.  I'm confused why the advice isn't simply "fix the wierd code" :)
[02:55] <lifeless> 13:41 < lifeless> markh: up to you if you want to work around or dig deep
[02:56] <markh> but why would I want to dig deep to support something plain weird?
[02:56] <lifeless> if py2exe is failing to copy in ui.text, then jamesh's thoughts about a different style of import hook may be useful long term
[02:56] <markh> clearly I should just fix the import to code that would be valid in regular python and everyone is happy!
[02:57] <lifeless> markh: sure, I never suggested that you don't change it
[02:57] <markh> right - I'm confused though why you would consider supporting it if it wasn't changed - but that's fine - I'll just quit while I'm ahead :)
[02:58] <jamesh> lifeless: if you bung the imports into a function body, you can either (a) disassemble the code to find the imports or (b) run the code with a custom __import__() to catch the imports
[02:59] <jamesh> tools like py2exe generally handle imports in function bodies just fine
[03:02] <markh> yeah - py2exe just uses the modulefinder package, and that does scan the bytecode for imports iiuc.
[03:03] <markh> jamesh: you comments above about using Python to check the syntax implies you think the behaviour I described (ie, that my example works anywhere) is actually a bug rather than a feature?
[03:04] <jamesh> markh: I'd prefer that the lazy imports syntax mirrored what was possible with normal imports and not more
[03:04] <jamesh> having something that is almost but not quite compatible but looks the same is going to cause bugs
[03:04] <markh> so that is a "yes" :)
[03:04] <jamesh> yeah.
[03:05] <markh> ok thanks - just trying to make sure I wasn't *totally* misunderstanding things!
[03:05] <lifeless> I don't see any reason for lazy imports to be more than regular import can do
[03:10] <markh> lifeless: right - but my example shows they can in some cases, right?
[03:10] <lifeless> markh: yes
[03:11] <lifeless> markh: however thats in qbzr isn't it? I'm not aware of smartass stuff like that in bzr itself
[03:11] <markh> but longer term, the best interests of everyone would imply noone tries to take advantage, let alone extend, the current behaviour and should use valid python syntax.
[03:11] <markh> well - I'd call it plain "wrong" rather than smart-arse :) but yeah...
[03:29] <markh> damn - changing the import to a python compatible "from bzrlib import ui; from bzrlib.ui import text" still doesn't work unless I make the change suggested by lifeless anyway (ie, adding 'import bzrlib.ui.text as text' to the lazy import block in ui\__init__.py).  Should I submit a patch even though I don't have a test case?
[04:01] <garyvdm> If I do a repository.lock_read() and I *don't* do a repository.unlock() , nothing bad seams to happen.
[04:01] <garyvdm> This is surprising!
[04:02] <markh> tortoise itself works well with 1.11 though, including 64bit windows, so that's my bzr work for the day done...
[04:03] <garyvdm> Is it ok to do that?
[04:04] <lifeless> garyvdm: not in general
[04:04] <garyvdm> Ok
[04:04] <lifeless> markh: cool
[04:05] <mwhudson> garyvdm: don't you get a warning printed somewhere when you do that?
[04:05] <garyvdm> No
[04:06] <garyvdm> I do get a warning if I don't unlock a branch.
[04:06] <garyvdm> But not with a repository.
[04:06] <poolie> spiv: is bzr+ssh://host/~/thing supposed to work now?
[04:07] <spiv> poolie: not yet; there's a quick patch on a bug IIRC.
[04:12] <lifeless> garyvdm: not sure why you don't see a warning; likely its because the pack family of repositories does its locking more lazily than branch
[04:12] <lifeless> garyvdm: all the same, you should lock/unlock
[04:12] <garyvdm> Ok
[04:14] <poolie> ok, i just misremembered
[04:16] <lifeless> 334 revs to go
[04:19] <lifeless> poolie: that evo fix I did at UDS has been committed upstream :)
[04:20] <poolie> yay
[04:27] <thumper> lifeless: 334 revs to go until what?
[04:27] <lifeless> thumper: my local repo has all the bad revs identified and the rest copied to a clean --1.9 repo
[04:27] <lifeless> thumper: I need to do this to start dogfooding lp for my bzr branches amongst other things
[04:28] <thumper> ah, ok
[04:57] <lifeless> poolie: I'm done for the day I think
[04:57] <spiv> spm: bzr's pqm appears stuck?
[04:57] <spm> spiv: oki, fixoring
[04:58] <spiv> spm: ta
[04:59] <spm> spiv: cause was another one from vila: "Rev 3934: (vila) Fix bug 315737 by correctly querying the test feature" :-(
[04:59] <spm> should be ok again now
[05:01] <spiv> spm: thanks.  I'm surprised that that change by vila would cause pqm problems.
[05:02] <spm> spiv: it's a resonably common (for a rare occourance) seems to hang on the email sending side for some reason.  Other grammer errors left alone.
[05:06] <poolie> i thought we tracked this down...
[05:06] <poolie> :/
[05:06] <poolie> there might be a patch attached to a bug in pqm?
[05:06] <poolie> spm, didn't you and me look at this
[05:06] <poolie> lifeless: night
[05:07] <spm> poolie: I don't recall chasing that down? But you could well be right - I know we have chased other stuff down. :-)
[06:58] <vila> hi all
[07:19] <bitmonk> i'm trying to use bzr-svn, recent from packages on ubuntu 8.10, to push a branch to a new svn location, is this not possible? i get 'http does not support mkdir()'
[07:20] <bitmonk> and if i try to point at a local path, i get 'parent of ___ doesn't exist', which makes sense, as it's a subloc of an svn repo with other packages..
[07:21] <poolie> i think there's a separate command to create the new branch
[07:21] <poolie> dpush?
[07:21] <poolie> the repository must already exist
[07:24] <bitmonk> trying clone..
[07:24] <bitmonk> the repo exists, but i'm pushing to a subdir of a repo, so the file:/// path doesn't actually exist, a portion of it is within an svn repo..
[07:38] <igc1> hey vila
[07:41] <vila> spm: you said "seems to hang on the email sending side"... did you track it down to being *mail* related ? I had only see it occurs when I use a "lp:" url so I thought it was ssh related instead
[07:41] <vila> but it's hard to tell from outside :-/
[07:42] <vila> spm: I also tried to *stop* using "lp:" url (not that masochistic you know...) but pqm then just ignored my submissions without feedback (giving me hope to fix the problem :/)
[07:42] <spiv> vila: well, the web interface said it got as far as "success: merge lp:~vila/bzr/bzr.integration/ http://bazaar-vcs.org/bzr/bzr.dev"
[07:42] <vila> spiv: I know...
[07:43] <vila> And, to me, that sounds like some connection not being gc'ed or something...
[07:43] <vila> where both client and server are waiting the other end to say: I'm done
[07:44] <vila> especially because when the pqm process is *killed* then my submission is successfully proceeded (sp?)
[07:48] <bitmonk> vila: processed
[07:49] <bitmonk> (nw)
[07:49] <vila> bitmonk: thks
[07:49] <bitmonk> np :)
[07:49] <bitmonk> assuming you are not a native english speaker, whatever your language is, i'm sure i couldn't say client or server or computer or address or network ;)
[07:50] <bitmonk> if you are, well, no offense, i'm glad to help with vocab where your high school left off ;)
[07:50]  * vila needs one lost coffee to finish full boot
[07:50] <bitmonk> (last)
[07:50] <bitmonk> keep in mind that green tea has comparable caffeine to coffee, but is less addictive..
[07:50] <vila> bitmonk: not native but I welcome feedback on any error I can make (language or anything else)
[07:50]  * bitmonk broke the coffee adiction year sago
[07:50] <bitmonk> vila: i love non-native english speakers, if only for the opportunity to be helpful when others aren't..
[07:51]  * vila is already having a hell of a time curing its tobacco addiction, coffee helps in the mean time :)
[07:51]  * bitmonk has often thought of moving out of the USA and can't imagine what it would be like to face the same social and economic challenges without barely knowing how to say "i'm sorry, but my clients have paid late.."
[07:51] <bitmonk> yah i hear that
[07:51] <bitmonk> gotta pick battles
[07:51]  * bitmonk has cut back a lot on tobacco but hasnt killed like coffee
[07:51] <bitmonk> i probably drink more than i would if i drank coffee, but i look for other sources of caffeine, whether i'm right or wrong, i dont like the coffay feeling.
[07:52] <bitmonk> and that said when i used to liv eon coffee i honestly drank a crap load of canadian whiskey every night with my coworkers
[07:52]  * bitmonk is pretty sure somewhere in that haze he lost a perfectly good automobile
[07:52] <bitmonk> that light pole had a bad attitude! :-P
[07:52]  * bitmonk hides
[07:54] <bitmonk> anyway, eh, i still never figurd out how to push something initialized in bzr to svn, i swear i have before, i'll figure it later, for testing sake i just put the code into place with bzr where it's expected to have pulled from svn.
[07:55] <vila> poolie: (reading logs backwards) I thought the pqm-stucked-problem was fixed too... and truth is it didn't manifest itself for sometimes... but no hard numbers there as often when tracking erratic bugs :-/
[07:55]  * bitmonk tries to determine if building his Dom0 kernel in a DomU from the same sources, with same options, will take a comparable amount of time..
[07:56] <bitmonk> oh wrong chan ;d
[07:58] <vila> bitmonk: the answer should be: "it should", but that's a wild guess, I'm not using xen :-)
[07:59] <bitmonk> vila: actually it took just under 8min when it takes almost 30min in Dom0, I must have missed something when mrproper-ing, or left a bunch of stuff out of menuconfig.. this, i find difficult to believe..
[07:59] <bitmonk> esp as people on comparable hardware have told me that general kernel build takes around 25-30min (3.0GHz C2D)
[07:59] <bitmonk> anyway, way out of scope for #bzr join in ##xen if you want to continue :)
[08:00] <bitmonk> maybe it was helped by LVM having the right blocks cached, as i built the kernel in Dom0, then unmounted the LVM volume, restarted DomU, mounted the xfs vol, and build the same code after a mrproper..
[08:00] <bitmonk> also the DomU has like 512M of RAM and Dom0 has like 3.5-4.0
[08:00] <bitmonk> anyway, again, out of scope
[08:00]  * bitmonk scuttles off to ##xen
[08:02] <vila> bitmonk: thanks for the offer :-) I may try xen in a couple of months but virtualbox is enough for my needs so far
[08:03] <bitmonk> xen i find quite interesting, though i've been a kernel-hearted-fool since high school some years ago ;)
[08:03]  * bitmonk heart menuconfig
[08:46] <igc> night all
[11:29] <Haffi___> Hi, I'm trying to set up bzr on a server, I've published a branch to it via sftp. When I run bzr branch sftp://... and fetch the tree, edit a file, commit the changes, and finally run 'bzr send' then I get this error: bzr: ERROR: No mail-to address specified.
[11:30] <Haffi___> How do I specify the mail-to address?
[11:31] <bob2> --mail-to
[11:31] <Haffi___> Do I have to specify it?
[11:31] <bob2> third last paragraph of 'bzr help send'
[11:33] <luks> that's not really accurate
[11:33] <luks> the email address is only required for some clients (like the simple editor+smtp one)
[11:33] <luks> if you are using a gui client, it's usually optional
[11:33] <bob2> for /to/ or /from/?
[11:34] <luks> to
[11:35] <luks> e.g. I have it configured to use evolution, I just run bzr send and type the address in evolution's window
[11:35] <bob2> oh
[11:36] <Haffi___> but does the mail have to be sent? If I just skip sending the mail when evolution opens, does it matter?
[11:36] <bob2> then you want -o
[11:36] <Haffi___> right, then it's written to file or stdout
[11:37] <bob2> where do you want the bundle then?
[11:38] <Haffi___> It still seems like the changes aren't published
[11:39] <bob2> all 'send' does is produce a bundle and optionally email it somewhere
[11:39] <Haffi___> oh
[11:39] <bob2> it doesn't affect any branches - are you trying to update the branch you branched from?
[11:39] <Haffi___> hehe, yes
[11:39] <Haffi___> I misunderstood the command
[11:40] <Haffi___> which command should I use then? I guess 'merge' is to fetch changes from main branch?
[11:41] <luks> bzr push
[11:44] <Haffi___> yep, it worked
[11:44] <Haffi___> thanks
[12:15] <Peng_> Is it valid to have a revision ID "" (I mean, an empty string, not literally two double-quotes)?
[12:15] <luks> I don't think revision IDs have any specified format
[12:16] <luks> so I'd say it's valid, but I'd expect some code to break on that
[12:16] <luks> because NULL revisions used to be represented as None
[12:18] <Peng_> The exception raised is NoSuchRevision. It would likely be something else if it was actually invalid..
[12:19] <spiv> Peng_: At a glance, the code would treat that as a valid revision ID I think.
[12:19] <spiv> Why do you want to know?
[12:20] <Peng_> I just wrote an email about it, actually, in Benn Finney's thread.
[12:20] <spiv> It's bad enough that bzr's history has a revision "A" ;)
[12:20] <Peng_> Haha, how'd that happen?
[12:21] <Peng_> "silly commit"?
[12:21] <Peng_> ...Creating a file called "b"?
[12:22] <spiv> Peng_: I think a test that made a test commit accidentally modified that developer's real bzr.dev repo instead of a throwaway repo.
[12:22] <Peng_> Anyway, I wanted to know because of Loggerhead. The URL "/files/" raises an error because it's a nonexistant revision, instead of doing something more useful like showing the index page.
[12:22] <Peng_> But if it is a valid revision, that's correct behavior, if not convenient...
[12:22] <spiv> Back before the test suite was as good as it is now at insulating tests from reality.
[12:22] <spiv> (and vice versa)
[12:23] <spiv> I think it'd be reasonable to disallow "" as a revision ID.
[12:23] <spiv> It seems more likely to cause bugs than be helpful.
[12:25] <Peng_> I don't disagree, but I don't care strongly enough to do anything about it. :P
[12:25] <spiv> Well, you already did, by mailing the list ;)
[12:27] <Peng_> Heh, good point.
[14:26] <phinze> is there a quick way to tell bzr: 'add all of the files in the unknown list' ?
[14:27] <beuno> phinze, bzr add?
[14:27] <phinze> beuno: doh!  that was way too easy :)
[14:27] <beuno> :)
[14:30]  * phinze was automatically thinking of subversion where he had to do xargs magic for that sort of thing... and consequently didn't read line 1 of the help
[14:33] <phinze> here's another one... is `bzr co foo; cd foo; bzr unbind` the equivalent of `bzr branch foo` ?
[14:34] <beuno> I'm not sure, I don't use checkouts much
[14:34] <luks> yes, it is
[14:35] <phinze> luks: cool, thanks. just trying to get my head around this stuff
[14:37] <abentley> phinze: It is *roughly* the same.  "bzr co" won't set the parent location, but "bzr branch" will.
[14:38] <phinze> abentley: really, that's interesting, you'd almost think it would be the other way around
[14:38] <phinze> that the checkout would be tethered to a parent and the branch would be free floating
[14:38] <abentley> phinze: The parent location is used for pulling.  You shouldn't pull in a checkout.  You should update in a checkout, which uses the bound location.
[14:39] <phinze> ahh
[14:40] <phinze> so really for the decentralized workflow `bzr branch` is really what you'd want to use
[14:42] <phinze> because bzr co + bzr unbind leaves you without a pull source
[14:44] <rocky> phinze: yeah but the first time you pull into a branch that has no pull source, it remembers the new source
[14:45] <phinze> rocky: okay nice, so there isn't all that much difference between the two in the end
[14:46] <rocky> yeah, and you can always change the pull source again with --remember
[14:51] <andresmujica> hi are newbies question allowed?? .. :)
[14:51] <nDuff> andresmujica, absolutely
[14:51] <andresmujica> hehe thks
[14:51] <LarstiQ> does anyone here use bzr-hookless-email?
[14:52] <andresmujica> i'm using a sw called 5-a-day, as far as i've check it uses bzr internally
[14:52] <andresmujica> the problem is that i'm using from 2 different computers
[14:52] <andresmujica> so i wonder
[14:52] <andresmujica> which is the right procedure to use it
[14:52] <andresmujica> when i change computers
[14:53] <andresmujica> somehow update the local .bzr before any update??
[14:53] <nDuff> andresmujica, are both systems able to connect to each other, or do you want to coordinate through somewhere (any SFTP/WebDAV/FTP/etc. space) they can both get through?
[14:53] <andresmujica> there's a main place (code.kaunchpad.net)
[14:53] <andresmujica> both point there
[14:53] <nDuff> andresmujica, I think it might be easier to have both of them use bound branches
[14:53] <nDuff> ahh
[14:54] <andresmujica> but the revisions numbers are different because i mainly work at one of them, and sometimes at the other...
[14:54] <andresmujica> so i suspect i've got to merge or pull or something like that before start my work...
[14:54] <andresmujica> at the less used computer
[14:54] <nDuff> if they're bound, that would make every commit automatically push to the server, and every update automatically check the server... but yes, you're right, you'd want to do some merging while setting it all up.
[14:55] <nDuff> if the more-often-used computer has a superset of everything at the less-often-used system, you should be able to do a push to the server, bind the branch there (on the more-often-used system), go to the less-often-used system, do a pull and then bind that one as well.
[14:56] <nDuff> ...if the more-often-used one doesn't have a superset, do a merge on it before the push.
[14:57] <nDuff> ...do you have RSA keys or somesuch to get to the remote system? The software may be surprised if it gets prompted for a password during commit/update/etc. if it's written to expect that its repository will always be unbound (and otherwise purely local).
[14:57] <nDuff> ("the software" == "5-a-day")
[14:57] <andresmujica> yeap 5-a-day.. i'm making a mess with my branch :(
[14:58] <andresmujica> yeap i've got the keys already in place on both systems
[15:14] <seb_kuzminsky> in a distributed workflow with no central server, can i give my team-mates' branches nicknames locally?
[15:14] <seb_kuzminsky> i want to be able to say "bzr merge alice", "bzr merge bob", etc
[15:14] <seb_kuzminsky> and have "alice" and "bob" expand to the urls of those team mates
[15:14] <james_w> seb_kuzminsky: not currently, though you may want to look at the bzr-bookmarks plugin
[15:15] <seb_kuzminsky> thanks james_w :-)
[15:23] <seb_kuzminsky> bzr-bookmarks is winrar!!  :-D
[15:27] <rbriggsatuiowa> I am encountering the different rich-root support error while trying to clone
[15:28] <rbriggsatuiowa> http://pastie.org/358686
[15:28] <rbriggsatuiowa> I tried the suggestions on https://bugs.launchpad.net/bzr/+bug/272425
[15:28] <rbriggsatuiowa> but get an bzr: ERROR: The branch format Bazaar-NG meta directory, format 1 is already at the most recent format. error
[15:29] <rbriggsatuiowa> when trying to do a  bzr upgrade --rich-root-pack
[15:31] <rbriggsatuiowa> bzr co works just fine
[15:33] <phinze> hi all i'm in the same spot as rbriggsatuiowa
[15:33] <phinze> rbriggsatuiowa: if you bzr init --rich-root-pack foo; cd foo; bzr pull remote-foo; it works
[15:34] <phinze> basically bzr clone is creating a repository of format pack-0.92
[15:34] <phinze> which is not right
[15:36] <phinze> because the remote bzr server is using rich-root-pack
[15:36] <rbriggsatuiowa> stupid gentoo
[15:37] <phinze> rbriggsatuiowa: mine's doing it too (ubuntu 8.10, bzr 1.6.1)
[15:37] <rbriggsatuiowa> I double-checked the USE flags and don't seem to be missing anything
[15:43] <phinze> rbriggsatuiowa: which version you on
[15:44] <rbriggsatuiowa> Bazaar (bzr) 1.6.1
[15:44] <phinze> yeah let's try upgrading to 1.10 (which the server is on)... msging you details
[15:56] <phinze> yep, the problem was using a 1.6.1 client with a 1.10 remote branch
[16:00] <andresmujica> ok, guys. i 've learned how to do it.  Thanks for your help!!!!
[16:00] <andresmujica> see ya!
[17:12] <ollie___> bzr mv concrete/blocks/autonav/ blocks/autonav
[17:12] <ollie___> bzr: ERROR: Could not move autonav => autonav: blocks/autonav is already versioned.
[17:12] <ollie___> could someone tell me why i am getting that message?
[17:13] <ollie___> there is currently nothing in blocks/autonav
[17:13] <ollie___> so i don't see how it can already be versioned
[17:13] <ollie___> bzr remove blocks/autonav
[17:13] <ollie___> blocks/autonav does not exist.
[17:38] <rsc-> hi guys. I have a branch i'm working on. I make some changes, but instead I change my mind -- i want to commit those changes into a NEW branch. how do i do that?
[17:38] <LarstiQ> rsc-: have you made the changes yet?
[17:38] <rsc-> yes
[17:38] <LarstiQ> rsc-: if so, you could `bzr merge --uncommitted path/to/branch/with/changes` from the one where you want them
[17:39] <rsc-> ahh.
[17:39] <rsc-> cool :)
[17:39] <LarstiQ> did that help?
[17:39] <rsc-> that should be automatic, yeah? no need for my intervention?
[17:39] <rsc-> (assuming that both branches are identical)
[17:40] <rsc-> (...except that one of them has uncomited changes)
[17:40] <LarstiQ> should be, yeah.
[17:40] <rsc-> cool.
[17:40] <rsc-> you learn something new everyday.
[17:40] <rsc-> thanks :)
[17:40] <LarstiQ> Possibly you want to list a couple of files you want the changes from, and not others.
[17:47] <adeel> can bzr handle resource forks (found in macs)?
[17:48] <LarstiQ> adeel: I don't think it does anything special with them.
[17:48] <LarstiQ> as most things are wont to do.
[17:49] <adeel> LarstiQ, well i know svn has issues with it...where if i check in a file with a resource fork attached, it won't come out the same
[17:50] <jelmer> adeel, I don't think it handles them at the moment
[17:50] <jelmer> at least it doesn't handle extended attributes (Linux) or streams (Windows)
[17:50] <LarstiQ> adeel: that doesn't suprise me, almost nothing handles them.
[17:51] <adeel> yeah that's what it seems like
[17:52] <jelmer> It would actually be interesting to seem them being used to store VCS metadata
[17:53] <adeel> all i know is that bzr has been confusing the hell out of me...conceptually i get the idea, but actually getting my repo started has been a royal pita
[18:10] <NfNitLoop> adeel: How has bzr been confusing you?
[18:18] <jam> jelmer: ping
[18:18] <jelmer> jam, pong
[18:19] <jam> hi jelmer, for the win32 installers, I went ahead and kept using 0.4.16
[18:19] <jam> Should I be trying to switch to the 0.5 series?
[18:19] <jelmer> jam, no, at least not for any production-oriented setups
[18:19] <jam> k, that's what I thought, but I figured I'd check, since there wasn't an 0.4.17 yet
[18:20] <jelmer> I hope to release another rc in the next couple of days, then maybe 0.5.0 after that
[18:21] <jam> jelmer: is 0.5 compatible with an 0.4 conversion? (I'm guessing not, but figured I'd check)
[18:22] <jelmer> jam, no, although it does support using 0.4-style mappings if explicitly configured
[18:23] <jam> jelmer: but it would create all new revision-ids, right?
[18:23] <jelmer> jam, if the 0.4-style mappings are enabled, no
[18:23] <jelmer> it would create the same revision ids that 0.4 would
[18:23] <jam> so by default 0.5 isn't compatible, but it can be made so?
[18:23] <jelmer> jam: yes
[18:23] <jam> It would be good to have that well documented for an 0.5 upgrade
[18:24] <jelmer> There's a README.UPGRADING file
[18:24] <jam> It would probably be important enough to make sure it would get into the NEWS items for whatever bzr starts including it
[18:24] <jelmer> jam: yeah, probably
[18:25] <jelmer> jam, one of the things I hope to do in the future (as part of the effort to make bzr more aware of foreign branch support) is to have a subclass of DivergedBranches that indicates different mappings (but the same foreign revision)
[18:26] <jelmer> including referncing the right docs about upgrading between bzr-<foreign vcs> mappings
[18:56] <rocky> jelmer: remember that bug i showed you a while back with bzr-svn where it couldn't find the parent branch of a tag? don't suppose you've made any progress on that?
[19:19] <jelmer> rocky, not sure
[19:19] <jelmer> rocky, I've fixed *some* bugs, not sure if that included yours
[19:19] <jelmer> do you remember the bug #?
[19:21] <rocky> i dont'... but i did update from bzr-svn 0.5 branch and discovered that it now seems to depend on bzr 1.11
[19:21] <rocky> so that means there won't be a 0.5 version that works on bzr 1.10 ?
[19:21] <rocky> regardless, i tried with bzr 1.11rc1 + bzr-svn 0.5 branch (as of a couple days ago) and got the same error ...
[19:22] <rocky> jelmer: just try "bzr co svn+https://dev.serverzen.com/svn/collective/Products.eXtremeManagement/trunk" and watch it complain about tags
[19:29] <jelmer> rocky, that appears to require a password?
[19:33] <rocky> jelmer: oh sorry, try the non https version
[19:33] <rocky> that's anonymous use
[19:34] <jelmer> ah, thanks
[19:35] <jelmer> rocky, that seems to redirect me to the https url
[19:38] <LarstiQ> ronny: what does the workingset accomodate?
[19:43] <rocky> jelmer: ok, http://svn.plone.org/svn/collective/Products.eXtremeManagement/trunk/ definitely works, i just browsed to it in a browser ;)
[19:44] <ronny> LarstiQ: manages a set of n branches, i view heads as branches
[19:46] <LarstiQ> ronny: ok
[19:46] <ronny> LarstiQ: im not entirely sure on the abstraction
[19:46] <LarstiQ> ronny: what prompted you to include it?
[19:47] <ronny> LarstiQ: stuff like hg's named branches
[19:47]  * LarstiQ looks that up
[19:47] <ronny> LarstiQ: and of course gits moving tag based branches
[19:48] <ronny> thats clearly different than bze's directory branches
[19:48] <ronny> *bzr
[20:14] <ronny> LarstiQ: made a sense out of all stuff?
[20:18] <LarstiQ> ronny: I read through http://www.selenic.com/mercurial/wiki/index.cgi/NamedBranches, but that isn't very enlightening
[20:21] <ronny> LarstiQ: named branches are basically static tags on a revision
[20:21] <ronny> LarstiQ: it can be used for tihngs like separate vendor branches or very long-lifed global branches
[20:22] <jelmer> rocky, that's bug 312272, not fixed yet
[20:22] <ronny> hmm
[20:29] <rocky> jelmer: ah cool ... don't suppose you have an eta? :)
[20:35] <jelmer> rocky, should be pretty soon now
[20:36] <rocky> great...  it's actually stopping me from getting anymore work done on my eXtremeManagement branch :(
[20:36] <rocky> jelmer: btw, will 0.5.0 final run on bzr 1.10 ?
[20:36] <jelmer> rocky, no, it will require at least 1.11
[20:37] <rocky> jelmer: that's strange since 0.5rc1 worked on 1.10
[20:37] <rocky> but no biggie
[20:37] <jelmer> still quite some things have changed since rc1
[20:39] <jelmer> ~20 bugs have been fixed since rc1 so far, that number will probably end up around 25
[20:39] <rocky> gotcha
[20:39] <rocky> no big deal, i don't mind upgrading to bzr 1.11 ... do you know when eta on 1.11 final is?
[20:39] <rocky> that one bzr-svn bug is killing me tho
[20:40] <jelmer> I think 1.11 final is already out actually
[21:22] <jam> jelmer: just 1.11rc1
[21:22] <jam> rocky: 1.11 final is this fri
[21:25] <lifeless> hi jam
[21:25] <jam> hi lifeless
[21:25] <jam> good morning
[21:28] <lifeless> jam: how are you going with merging stuff to bbc?
[21:28] <jam> I've gotten a few things landed
[21:29] <jam> I have a test suite run going to see if there is anything we need to focus on
[21:29] <jam> hmmm.. 22 failures 13 errors
[21:29] <jam> a lot of them close to trivial
[21:29] <jam> like not using "assert" in the code
[21:31] <jam> hmm. and a really random error from a piece of code getting a negative number that didn't expect one
[21:49] <markh> jam: qbzr is broken in the 1.11rc1 :(
[21:50] <markh> (and therefore most of tortoise)
[21:50] <jam> Thanks for the heads up. Any idea why?
[21:50] <jam> I just used the 0.9.6 release, I can go back to 0.9.5 if you think it is necessary
[21:51] <markh> lazy imports :)
[21:51] <markh> I mentioned it yesterday in IRC, but the discussion just fizzled out as I'm not sure exactly how to resolve it.
[21:52] <jam> so lazy imports don't work with the packaging?
[21:52] <markh> in short, qbzr does 'from bzrlib import ui.text' in a lazy import block, and while that works from source it fails in py2exe.  A potential solution was to fix bzr itself by having the ui package itself lazily import text
[21:53] <markh> indeed, that was the only solution I could see - re-arranging the imports in qbzr also failed
[21:54] <jam> do you have the tracebacks to why it is failing with py2exe?
[21:54] <spiv> Why did rearranging the imports in qbzr fail?
[21:54] <jam> It seems like it should be working
[21:54] <markh> the discussion on IRC yesterday stalled after I asked if I should submit a patch even though I don't have tests, but that went unanswered...
[21:54] <jam> And may signify a bug in the lazy import code
[21:54] <spiv> markh: submitted code is > unsubmitted code.
[21:55] <spiv> markh: (and code with tests > code without tests, but having a patch in the first place is a good start...)
[21:55] <markh> spiv: I'm not sure why they failed to be honest, but I assume it was still something related to lazy imports
[21:56] <spiv> markh: Hmm.  Maybe question that assumption? :)
[21:56] <spiv> I'm just guessing.
[21:57] <jam> so, for my immediate fix, I can do a 1.11rc1-2 with qbzr 0.9.5
[21:57] <jam> at least people will have something that works
[22:00] <jam> markh: I don't see any "import.*ui" or "import.*text"
[22:00] <jam> in qbzr
[22:00] <jam> (well, aside from the 'gettext' lines)
[22:00] <markh> in commands.py
[22:00] <igc> morning
[22:00]  * markh finds it
[22:01] <markh> mornin' ian
[22:01] <jam> ah, there it is
[22:01] <jam> lib/commands.py
[22:01] <jam> I would guess the problem is doing:
[22:01] <spiv> markh: wow, and it's a totally gratuitous lazy_import anyway :)
[22:01] <jam> from bzrlib import (
[22:01] <jam>  ui,
[22:01] <jam>   ui.text,
[22:01] <jam> )
[22:01] <jam> I wouldn't expect that to be valid
[22:02] <markh> yeah, we had this discussion yesterday with lifeless :)
[22:02] <jam>      from bzrlib import ui.text
[22:02] <jam>                           ^
[22:02] <jam>  SyntaxError: invalid syntax
[22:02] <markh> yeah
[22:02] <jam> That syntax isn't valid python import
[22:02] <spiv> jam: right, there's a bug that lazy_import allows that.
[22:03] <spiv> (and a bug that qbzr does that)
[22:03] <markh> but - it fails if you try the "obvious" thing that is valid Python syntax.  The detaisl escape me now and I'm yet to have my morning coffee :)
[22:03] <spiv> markh: the obvious thing is "from bzrlib.ui.text import TextUIFactory", IMO
[22:04] <markh> oh - well, I was trying "from bzrlib.ui import text" under the assumption the text name was needed - but you are probably correct that it isn't.
[22:04] <spiv> markh: no, the code is clearly needing "ui.text" so it can use "ui.text.TextUIFactory" at the moment
[22:05] <markh> yes - I was assuming it also used other attributes from that module
[22:05] <jam> markh: http://paste.ubuntu.com/104124/
[22:05] <jam> Would be my suggsetion
[22:05] <markh> but - at lifeless' suggestion, the code as written works if you add "import bzrlib.ui.test as text" to the lazy import code in ui\__init__.py
[22:06] <markh> jam: so just remove them from lazy imports?
[22:06] <spiv> markh: actually I'd expect "from bzrlib import ui; import bzrlib.ui.text" in qbzr would work too.
[22:06] <markh> s/them/it/
[22:06] <jam> markh: they are used right away
[22:06] <hsn_> is there way to define alias for URL which i can use with bzr push?
[22:06] <jam> lazy doesn't do anything
[22:07] <jam> hsn_: there is a "bookmarks" plugin
[22:07] <jam> lp:bzr-bookmarks IIRC
[22:07] <jam> then you get "bm:XXX"
[22:07] <markh> yeah - in this case it needs to be fully imported anyway
[22:07] <hsn_> jam: in bzrtools?
[22:07] <jam> hsn_: bzr-bookmarks *is* the plugin
[22:09] <hsn_> got it.
[22:10] <hsn_> is there way to checkout just some directories from branch?
[22:13] <jam> hsn_: not yet
[22:25] <hsn_> http://bazaar-vcs.org/NestedTreeSupport -> this thing works already?
[22:27] <lifeless> o
[22:27] <lifeless> no
[22:35] <markh> jam: so the plan is you will re-release with an earlier version of qbzr, and I'll ping the mailing list in the hope of a new release tomorrow?
[22:35] <markh> new qbzr release
[22:36] <markh> or will you hack the existing qbzr into shape?
[22:37] <jam> markh: I just patched 0.9.6 => 0.9.6-win32 with a trivial 'don't make it lazy" fix
[22:37] <jam> And I'll send that to the qbzr list
[22:37] <markh> awesome - thanks
[22:39] <NCommander> I was wondering if someone could try and confirm a bug in bzr-svn?
[22:39] <NCommander> (I'm not sure if there is something locally thats causing the issue or not)
[22:40] <jelmer> NCommander, sure
[22:41] <lifeless> NCommander: moar details needed :P
[22:42] <jam> poolie: ping
[22:42] <NCommander> lifeless, I'm trying to checkout the following SVN repo:
[22:42] <NCommander> bzr co svn://uclibc.org/trunk/buildroot
[22:42] <NCommander> It bombs out with a UTF error
[22:43] <poolie> jam, pong
[22:43] <jam> poolie: Are we going to start back up with doing a weekly direct call between you and I?
[22:43] <jam> We seemed to have faltered on that after the new year
[22:44] <poolie> ah we have a bit
[22:44] <NCommander> jelmer, also ^
[22:44] <poolie> that would be good though
[22:44] <poolie> should we talk now, or maybe tomorrow morning?
[22:45] <jam> poolie: tomorrow would work best, I think
[22:45] <jelmer> jam, that reminds me, I've been meaning to ask you what happened to the "This week in Bazaar" blogposts
[22:46]  * igc food
[22:46] <jam> I sort of "lost steam" in writing them. Well that and lost statik as my motivator
[22:47] <jam> I'm a bit of a too-many-details sort of person, so it worked best to have someone who would know what a community would want to hear
[22:48] <jam> markh: I uploaded 1.11rc1-2
[22:48] <jam> can you give it a shot?
[22:48] <markh> sure
[22:48] <poolie> hello markh
[22:48] <rockstar> jam, I'm still willing to help out on those.
[22:48] <markh> hi poolie
[22:49]  * NCommander pulsechecks lifeless
[22:49] <jelmer> NCommander, when does it fail, which revision?
[22:49] <jelmer> (approx)
[22:49] <NCommander> jelmer, after its done importing and starts building the bazaar tree
[22:50] <NCommander> jelmer, I'm running the bazaar from Jaunty, so it might be a little behind the current release version
[22:50] <lifeless> NCommander: can you get the backtrace from ~/.bzr.log please
[22:51] <jam> rockstar: maybe we should give it another go this week. If you have the chance, try to think about things that we might want to talk about
[22:51] <rockstar> jam, sounds good.
[22:52] <lifeless> statik is still alive yes
[22:52] <NCommander> lifeless, and jelmer http://paste.ubuntu.com/104142/
[22:52] <jelmer> jam, Ah
[22:53] <jelmer> jam, I thought they were quite useful
[22:53] <lifeless> thats still in bzr-svn
[22:54] <NCommander> oh
[22:54] <NCommander> Any ideas how I can fix it, or at least work around it?
[22:54] <jelmer> NCommander, I'm trying to reproduce it here
[22:54] <NCommander> jelmer, it died for me in the high 22000s
[22:55] <jelmer> NCommander: Ah, it died during "fetching revision info" ?
[22:55] <markh> jam: now failing due to the svn plugin wanting 1.10 it seems
[22:55] <NCommander> yeah, I reran it
[22:55] <markh> or maybe bzrtools - its not clear
[22:55]  * markh checks the log
[22:55] <jelmer> NCommander, that's not occurring here, so at least this bug is fixed in 0.5
[22:56] <NCommander> someone should update the ubuntu packaging
[22:56] <jam> markh: I would expect it to be bzr-svn, just because I did pick bzrtools 0.11.0
[22:56] <jam> but if you could poke a bit closer, I would appreciate it
[22:56] <jelmer> NCommander, 0.5.0 isn't out yet
[22:56] <NCommander> oh
[22:56] <jelmer> debian experimental has a 0.5rc packaged fwiw
[22:56] <NCommander> is it available in a PPA?
[22:57] <markh> jam: the traceback isn't clear but it looks like svn:
[22:57] <markh> 0.313  bzr-svn: using Subversion 1.5.4 ()
[22:57] <markh> 4.361  Traceback (most recent call last):
[22:57] <markh> ...
[22:57] <markh>   File "bzrlib\api.pyo", line 82, in require_api
[22:57] <markh> IncompatibleAPI: The API for "<module 'bzrlib' from 'C:\Program Files (x86)\Bazaar\lib\library.zip\bzrlib\__init__.pyo'>" is not compatible with "(1, 10, 0)". It supports versions "(1, 11, 0)" to "(1, 11, 0)".
[22:57] <jelmer> markh, could very well be bzr-svn
[22:57] <markh> certainly as of yesterday, svn failed like that
[22:57] <jelmer> markh, that doesn't look like a released version of bzr-svn
[22:57] <lifeless> markh: whats the caller above in the backtrace
[22:58]  * markh needs glasses :)
[22:58] <markh> 2 entries up is svn's __init__
[22:58] <NCommander> jelmer, where can I find the bzr-svn snapshots or bazaar branch?
[22:58] <jelmer> NCommander, http://people.samba.org/bzr/jelmer/bzr-svn/0.5
[22:58] <NCommander> jelmer, empty folder
[22:59] <jelmer> NCommander, it's a bzr branch
[22:59] <markh> jelmer: is there a bzr-svn jam should be using with the 1.11 windows binaries?
[22:59] <jam> markh, jelmer: lifeless originally made a change that bumped the bzrlib api number
[22:59] <jam> that was supposed to land in 1.9, I updated it because it landed in 1.11
[22:59] <enigma42> jelmer: I just checked out a branch from svn. After running a "bzr check" on the repo, I get "4 inconsistent parents". Is that bad?
[22:59] <jam> I don't remember what off-hand
[23:00] <jelmer> what happened to API-specific versions? :-)
[23:00] <jam> ah, it was the "add_inventory_by_delta" change
[23:01] <jelmer> ah, ok
[23:01] <jelmer> that shouldn't be relevant to bzr-svn
[23:01] <jelmer> I'll release a 0.4.17
[23:01] <enigma42> jelmer: "And I get a bzr: ERROR: No such file" message when I try to branch over sftp.
[23:01] <enigma42> (But not locally, interestingly enough.)
[23:02] <jelmer> enigma42, hmm, that's strange - what version of bzr-svn?
[23:02] <jam> jelmer: just make sure your tag propagates to bzr-svn's trunk :)
[23:02] <jam> (lp:bzr-svn)
[23:03] <enigma42> jelmer: bzr-svn 0.5 trunk revno 2281
[23:03] <enigma42> jelmer: Let me pull up to revno 2293 and try again.
[23:03] <jelmer> enigma42, the two things should not be related
[23:04] <jelmer> enigma42, what file exactly does it give the error about?
[23:04] <enigma42> bzr: ERROR: No such file: ('iovariableplugin.gro-20081110215858-yuu32hfdt8apjga0-1', 'kirby@kirby-ubuntu-dev-20090105202353-tv2de4iskr45pl68')
[23:04] <jelmer> enigma42, hmm, in that case it could actually be related
[23:04] <jelmer> enigma42, does the repository in question contain any revisions pushed with previous versions of bzr-svn?
[23:05] <enigma42> This is a fresh branched just checked out of svn.
[23:05] <markh> jam: seeing you need to make a new build, could you update tsvn too?  I've made some doc improvements yesterday and bumped the version to 0.2-candidate
[23:05] <enigma42> jelmer: Yes.
[23:05] <enigma42> enigma42: The *svn* repository contains revisions pushed with the previous version of bzr-svn
[23:05] <markh> ack
[23:05] <enigma42> jelmer: But the *bzr* repo was a fresh checkout from svn.
[23:05] <markh> jam: actually, maybe scratch that, unless you are also willing to make a trivial change to the .cog
[23:06] <enigma42> Just to make sure we're both talking about the same "repository" here. ;-)
[23:07] <markh> (which would be the s/index.html/*.html/ patch I submitted yesterday that was apparently not looked upon favourably by bundlebuggy)
[23:08] <jelmer> enigma42: this error is likely caused by incorrect bzr-svn metadata set by a development version of bzr-svn, but it's hard to say for sure
[23:09] <enigma42> jelmer: Is there a way I can zap the metadata in SVN?
[23:09] <enigma42> enigma42: I'm fine with loosing merge history in this case.
[23:09] <markh> jam: I need to run out for an hour any time in the next hour.  Do you expect to have new builds up soon?  If so, I'll wait and test them before leaving.
[23:10] <jelmer> enigma42, only by doing a "svnadmin dump" and removing them in the svndump
[23:10] <enigma42> jelmer: Oh boy.
[23:11] <enigma42> jelmer: With 0.5, is that changing?
[23:11] <enigma42> jelmer: Since it will use revision properties instead?
[23:11] <jelmer> enigma42, yeah, it's easier with 0.5 indeed (but only if you have subversion 1.5)
[23:11] <NCommander> jelmer, so how do I use 0.5, I installed it and now get: No module named foreign
[23:11] <jelmer> NCommander, you need bzr 1.11
[23:12] <jelmer> sorry, 1.11rc1
[23:12] <NCommander> I assume no packages exist ...
[23:12] <jelmer> I think there may be some in the bzr ppa
[23:13] <NCommander> nope
[23:13] <NCommander> where do I find the source tarballs :-)
[23:13] <NCommander> hey lamont
[23:13] <enigma42> jelmer: Yeah, I get the same "No such file" error with bzr-svn 0.5 trunk revno 2293
[23:16] <enigma42> jelmer: Do you know of a way of fixing up the bzr repo by hand rather than purging the svn properties?
[23:16] <james_w> NCommander: try ~bzr-beta-ppa
[23:16] <NCommander> Of course now that I actually have everything installed from source does james_w pop up with the handy to use PPA
[23:16] <NCommander> :-P!
[23:18] <NCommander> jelmer, and as an aside, the issue fixed in the latest bazaars
[23:18] <NCommander> Thanks for the tip
[23:18] <jelmer> enigma42, not really - the svn repository contains corrupt metadata, it's impossible to create a bzr branch from that
[23:19] <jelmer> I guess we could add a svn-import option to skip reading any bzr-svn metadata
[23:19] <enigma42> jelmer: That would be quite nice. :-)
[23:20] <lifeless> james_w: the beta ppa doesn't have bzr-svn
[23:20] <spiv> jelmer: thinking of bzr-svn options...
[23:20] <enigma42> jelmer: I don't control the svn server, so I can't do a svn-dump.
[23:20] <markh> bb in an hour...
[23:20] <spiv> jelmer: I've seen a few people get surprised that bzr-svn will operate on a .svn checkout, specifically when they have .bzr and .svn control dirs for the same directory
[23:20] <enigma42> jelmer: So I guess I'm out-of-luck than.
[23:21] <lifeless> spiv: installing bzr-svn by default would fix that
[23:21] <spiv> jelmer: it might be nice if there were a way to disable that feature in ~/.bazaar/locations.conf
[23:21] <jelmer> spiv, that seems more like something for the bzr format probe logic
[23:24] <jelmer> spiv: or do you mean being able to completely turn off support for .svn directories?
[23:24] <lifeless> jelmer: if you probe in a subdir of the root of a svn tree, does bzr get told 'no branch' and keeps probing, or do you 'find' it immediately and return the root?
[23:25] <jelmer> lifeless, it's always a BzrDir
[23:26] <jelmer> whether bzr-svn considers a Branch to be present depend son the repository layout
[23:26] <lifeless> jelmer: well, Tree I mean
[23:26] <lifeless> jelmer: cause of the .svn dir
[23:26] <jelmer> lifeless, same goes for tree
[23:26] <lifeless> ok
[23:26] <lifeless> so at the root of a tree, the bzr probe should occur first
[23:26] <spiv> jelmer: the latter, at least for a given location
[23:26] <lifeless> and thus a .bzr dir will win
[23:27] <lifeless> in a subdir though, it might be nice for it not to find a ControlDir unless its the root of the tree, that would let colocated .bzr and .svn 'work as expected'
[23:27] <lifeless> without needing special facilities
[23:27] <lifeless> spiv: I don't really like the idea of turning it off
[23:27] <spiv> jelmer: So I think it'd be possible to make SvnCheckout.probe_transport consult locations.conf before actually probing.
[23:27] <jelmer> lifeless, the problem also appears to be that people try to "bzr add" .svn directories
[23:28] <lifeless> jelmer: when a svn tree is under a bzr tree?
[23:28] <jelmer> lifeless, or at the same location
[23:28] <jelmer> that's actually what I've seen happen so far, rather than the use case spiv is mentioning
[23:28] <spiv> It'd probably be enough to make .bzr always take precedence over a .svn.
[23:28] <spiv> Because people can always use /usr/bin/svn to manipulate .svn dirs.
[23:31] <lifeless> jelmer: smart_add will skip .svn dirs if they probe successfully as a branch
[23:32] <jelmer> lifeless, what I mean is that people *want* to version the .svn dirs in some cases
[23:33] <lifeless> jelmer: oh. they are insane?
[23:33] <lifeless> hmm, bzrdir.is_control_filename needs to be pluggable
[23:33] <lifeless> jelmer: ^
[23:34] <lifeless> spiv: .bzr should already mostly take precedence; except for when bzr is run in a subdir of a .svn tree I think; I'd aargue that that is a valid bug
[23:35] <spiv> lifeless: sure.  It's definitely been observed by various people that it doesn't necessarily take precedence.
[23:36] <lifeless> spiv: the reason I am con making this toggleable is that its an option that adds complexity, and is pretty clearly only useful if the functionality isn't right
[23:36] <jelmer> spiv, it does when they exist in the same directory, but .svn has control dirs in subdirectories as well, not just the tree root
[23:36] <lifeless> jelmer: so whats the use case for versioning .svn ?
[23:37] <jelmer> lifeless, poor mans tracking of an upstream branch in svn
[23:38] <spiv> lifeless: If everything Just Works, then that's great.
[23:38] <lifeless> jelmer: oh
[23:39] <spiv> lifeless: Until it does, I'd rather have a toggle that can at least make working the way the user intends possible than not.
[23:39] <lifeless> spiv: IME such toggles become the end result
[23:43] <jelmer> jam, 0.4.17 pushed