/srv/irclogs.ubuntu.com/2008/05/04/#bzr.txt

fbondlifeless: http://bazaar-vcs.org/Documentation/LoomAsSmarterQuilt04:34
fbondlifeless: This is a pretty crude explanation of how I use loom.04:35
fbondlifeless: It needs more detail added, but it is a start.04:35
fbondI'll see if I can flesh things out a bit more.04:35
cybXhello all05:22
cybXanyone alive? good grief...I haven't irc'd in a year05:22
cybXi feel like a newbie all over again05:22
cybXyay05:22
cybXalrighty then06:03
rexbronhmm...10:48
rexbronbzr: ERROR: Repository KnitPackRepository('file:///home/rexbron/packages/quassel/.bzr/repository/') is not compatible with repository SvnRepository('http://svn.quassel-irc.org')10:48
rexbronis it not possible to use bzr-svn inside a repo?10:48
fullermdYes, but only if the repo uses a rich root capable format like bzr-svn requires.10:49
AfCrexbron: yes it is, but you need to make the repository be of format "rich-root-pack"10:49
AfCrexbron: (at least, that's what I had to use a month back)10:49
rexbronok10:49
fullermd(which means you probably don't want to mix it with repos containing other stuff)10:49
AfCfullermd: did they get that rich-root stuff into the default as of 1.4, or are they still faffing about?10:49
rexbronthanks10:49
fullermdIt's not in 1.4 certainly.10:50
fullermdabentley was fiddling.  At one point the next format would be default and rich root.  Last I heard, he was waffling toward switching defaulting rich-root-pack.10:50
AfCrexbron: ... regarding what fullermd just said, if you follow a convention of having a directory (containing a repository) being the parent directory of a bunch of branches all related to the same project, then things work out rather well.10:50
AfCrexbron: [I have10:51
AfC~/src/andrew/project1/branchN10:51
AfC~/src/andrew/project2/branchN10:51
AfC...10:51
AfCand10:51
AfC~/src/otehr/project3/branchN10:51
AfCother*10:51
AfCwhere project3 has a different repo format10:51
AfCbut the real matter is that each of projectN has its own repo10:52
rexbronAfC: that is how I approach it aswell10:52
AfCrexbron: you'll be all set then10:52
AfCjust create a new project directory with10:52
AfC$ bzr init-repo --rich-root-pack project310:53
AfC[or whatever the current recommended format is, {sigh}]10:53
mathrickhttps://launchpad.net/~bzr/+archive <-- bzr debs are mislabelled11:26
mathrickthey all say ~hardy1, when the series listed is different11:27
mathrickin fact, the whole thing confuses me11:29
mathrickhalf of the builds have no corresponding .debs linked11:29
bimberimathrick: Launchpad build records remain even after a package is deleted.12:05
bimberi*Launchpad *ppa*12:05
mathrickah12:07
bimberiwrt the mislabelling, I'm guessing that the new LP feature allowing package copying was used.12:08
bimberiref: https://lists.ubuntu.com/archives/launchpad-users/2008-May/003665.html12:10
=== isubask is now known as isu
nick125Hello20:10
nick125I'm having a *small* issue with bzr ignore...for some reason, it isn't ignoring my pattern. In my .bzrignore file, I have *~ and *.pyc, but it's still adding those files. Am I doing something wrong?20:11
jelmernick125: Are you specifying the files explicitly perhaps?20:17
nick125jelmer: Hmm...that's possible. I did a bzr add *..would that add ignored files?20:18
jelmernick125, yep it would20:19
jelmernick125, try "bzr add" if you want it to obey the ignores file20:19
nick125neat..thanks!20:19
lifelessfbond: thanks21:48
=== abentle1 is now known as abentley

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!