| [04:16] <youlysses> t | |
| [04:57] <scientes> whats with all the orphaned bzr plugins in debian http://www.debian.org/devel/wnpp/orphaned ? | |
| [04:59] <mgrandi> if youc click on them you'll see that jelmer is requesting an adopter | |
| [04:59] <mgrandi> so they are probably still developed but they need a maintainer that creates debs (thats almost a job in itself) of the latest versions and whatnot | |
| [05:00] <scientes> well why can't whoever is doing the ubuntu work, just pick up debian? | |
| [05:00] <mgrandi> they have different policies =P | |
| [05:01] <mgrandi> and its probably a lot of work | |
| [05:01] <mgrandi> if creating deb files wasn't black magic i might see if i could do it haha | |
| [05:02] <scientes> meh its not that hard | |
| [05:02] <spiv> mgrandi: maybe now's a good time to learn ;) | |
| [05:02] <mgrandi> i can't even find a good guide | |
| [05:02] <mgrandi> ive only seen guides on how to use easyinstall and other helpers | |
| [05:02] <spiv> I'm sure jelmer would be glad to help a willing volunteer | |
| [05:02] <scientes> you just need to write a makefile, and if your package works with automake, its mostly "magic" and done for you | |
| [05:02] <mgrandi> these are python plugins so i dont think they have makefiles | |
| [05:02] <scientes> (same for some other build systems) | |
| [05:03] <mgrandi> makefiles themselves are black magic | |
| [05:03] <scientes> ^^^ | |
| [05:04] <mgrandi> id also probably need a debian install haha | |
| [05:06] <scientes> yes you would, but you can use "debootstrap" to do it all in a chroot | |
| [05:06] <scientes> which will run from any distribution | |
| [05:06] <scientes> http://wiki.debian.org/Debootstrap | |
| [05:10] <mgrandi> looks like it would just be easier to shrink a partition then try to run debian ontop of something else | |
| [08:09] <mgz> morning! | |
| [08:23] <jelmer> mgz! | |
| [08:25] <mgz> ! | |
| [08:36] <vila> jelmer, mgz: hey | |
| [09:10] <gour> morning all | |
| [09:24] <gour> fast-export/import from fossil --> git fails...otoh, fossil --> git works as 'fossil export --git ../repo.fossil | git fast-import' withing git repo...is it possible to use bzr's fast-import via fossil's pipe so that we can convert our fossil repos straight into bzr? | |
| [09:25] <jelmer> gour: s/git/bzr/ for the first occurance of git? | |
| [09:25] <jelmer> I think there were some known issues with the fossil fastexporter, it removed all files for each revision or something along those lines | |
| [09:27] <gour> for now, fossil does export --git only | |
| [09:28] <jelmer> gour: It's worth a shot to try --git and feed that output into bzr fastimport | |
| [09:29] <jelmer> I vaguely recall there were issues with fossil fastexport output format though | |
| [09:29] <jelmer> or maybe that was Monotone? | |
| [09:30] <gour> jelmer: i'm trying that, but no idea how to feed that output into bzr fastimport...fossil export --git task.fossil | bzr fast-import neither fossil export --git task.fossil | bzr fast-import task.bzr works | |
| [09:32] <gour> i sent a post to fossil list but the attachement exceeds 40k quota there :-( | |
| [09:34] <jelmer> gour: you might want to try generating an intermediate file with the fastimport data | |
| [09:34] <jelmer> gour: 'bzr fast-import' takes two arguments: the filename of the fastimport stream to read and the branch to import to | |
| [09:36] <gour> jelmer: it crashes with the same mark as git import | |
| [09:37] <gour> jelmer: http://pastebin.com/9wsUWgeF | |
| [09:38] <gour> jelmer: i can email you *.fi file | |
| [09:38] <gour> git import fails with "fast-import fatal: mark :711 not declared" | |
| [09:39] <jelmer> if git fails too, I would put the blame on fossil | |
| [09:39] <jelmer> gour: there's not much I can do with that, I'm not a fossil contributor :) | |
| [09:39] <gour> right...the problem is that i could not post *.fi file there... | |
| [09:39] <gour> ok | |
| [09:40] * gour just wants to import repos from fossil to bzr... | |
| [10:17] <gour> there is no addremove in bzr to add all unversioned files and rm all missing ones? | |
| [10:19] <jelmer> gour: "bzr add" without arguments will add all unversioned files | |
| [10:19] <jelmer> and bzr commit will automatically remove files that were rmeoved | |
| [10:20] <gour> thank you | |
| [13:42] <WasserDragoon> hi how to get the release code from version 3.1 from https://launchpad.net/egtk | |
| [13:43] <WasserDragoon> there are no tags and i don't want to look into the .tar.gz download always whats the last revision (in .bzr folder) | |
| [13:48] <mgz> WasserDragoon: surely that's a question for the maintainers of that project rather than bzr | |
| [13:49] <WasserDragoon> mgz: i don't have a good connection to these guys ;-) | |
| [13:51] <mgz> neither do I, but the launchpad page makes it clear enough who to ask | |
| [13:51] <mgz> try email or irc given on https://launchpad.net/~danrabbit | |
| [13:53] <mgz> just guessing from log/release timestamps, you probably want r491 | |
| [14:00] <WasserDragoon> mgz: right but i don't want to look in all next releases what the last revision was | |
| [14:00] <WasserDragoon> but i will send a mail to danrabbit | |
| [14:02] <mgz> you can suggest `bzr tag -r491 egtk-3.1.0` to him | |
| [14:10] <WasserDragoon> mgz: to late i already sent the mail but thanks i'll do that in the next mail ;-) | |
| [17:44] <Mook_as> hmm, I guess starting with bzr 2.4, `bzr revert dir/file` also tried to revert the containing directory if there are no other changes in that directory? (steps to reproduce in http://pastebin.com/5Awyr8Bg ) | |
| [19:12] <gour> /q | |