Search Results: "ag"

18 June 2007

Christoph Berg: Debconf: Arrived

You know you have left the continent when you see this: I've arrived all well, only that I made the same mistake as always - leaving the house without writing down (or even looking up) the precise address where to go. Luckily the information centre at the EDI airport had a web browser. (And they didn't get scared away by repeated "This page contains insecure media" warnings on debconf.org.)

17 June 2007

Daniel Burrows: Freudian slips in commit messages


changeset: 700:d8308a89c519

user: Daniel Burrows

date: Sun Jun 17 16:22:43 2007 -0700

summary: Call pre_package_state_changed() before undoing, to resent the dependency resolver; call package_state_changed() after an undo if necessary.

Joerg Jaspert: DebConf7 - Blogging from the Cabal Secret Headquarters

I’m now already 9 days in Edinburgh (started writing this at day 5 already :) ), and all of them have been days of “get up at 8h, breakfast, goto Teviot, work until 23h, go back to Hostel”, with some short breaks in Teviots Bar and for Lunch/Dinner. Sounds stressful but actually was (mostly) a lot of fun, preparing the network, setting up all the core servers together with two other admins while at the same time getting a lot of request to change various parts of our Conference Management System Pentabarf to fit some peoples need at various places. The airline managed to get me to EDI, together with a few other Debian people on Friday, 8th June, around noon, where Mark (mhy) Hymers did wait already, so I didn’t need to take a bus to get into the town. On the way to Teviot I also remembered some of the places from back when we did the Venue visit for the DC7 decision. But not many, of course one forgets a lot over the time. At least I was able to remember some food places, which is always a good sign. :) At Teviot we met with Stephen (sgran) Gran to (unsorted list) have some food, unload the car, think about the way to get our uplink to our server room, check into the hostel - and whatever else we did at that day. Next day, officially called Setup day, we started to get two cables from our server room to the place our uplink is - you can see them if you go to the left site of Teviot. (The other two got there a bit later). After that we started with the setup of the network, which is pretty nice this year. We have a lot of sponsored machines that are doing various tasks, a nice network layout involving a lot of vlans to seperate stuff and a lot of (good) crack. What, you dont want to listen to boring details? Ok, here they come: - The main machine is, again, called Homer. Connected with a 2Gbit link to our master switch. It does those little things noone needs, like firewall, local mirror, dns, nagios, routing between various nets we have here, the schedule bot, etc. - There is also a Marge, who is the central point for the whole wireless network, running chillispot to have authentication for it. - Barney is used as a storage server for the video team, having some 1.5TB (raid5) space for the video data. It has 2 additional disks, 500G each, to copy data on and get them home to a video team after the conference. - Our streaming master machine at DC7 is called Lisa, and does not more than streaming for all the local clients and sending the stream out to our streaming master somewhere in the internet which then relays it to our streaming servers kindly offered by a lot of admins all over the world. - We also have Bart and Maggie, which serve as public build boxes for the attendees, where Maggie even runs a distcc open to the whole local network. - You can add the same amount of servers to this list which all do various tasks for the video team. This stuff is all glued together by a set of managed switches building our core backbone, running a number of vlans to seperate the different network segments. Which actually works quite nicely, as even at the time some expert managed to plug a cable into the same switch twice (yay, loop) - the only affected network part was that where he was in. The rest of the conference didn’t even notice it - until all of the admins jumped out of the admin room at once, looking for that fuckup. :) Sounds like crack? Probably is, but is a nice setup all together, and it was fun to set it all up together with Mark and Stephen, the two main admins for this conference who designed most of the whole structure and are the ones that really know it. I already “volunteered” them for the next DebConf to help as admins and really hope they decide to do it. Later on during DebCamp we also had Peter (weasel) Palfrader joining the local admin team. His main work here is related to the video team by hosting the geodns setup for the streaming and by running a local nagios to check the things we need to check. This enabled us to simply tell everyone Use streams.video.debconf.org:8000 wherever you are and you will get to the right server for you. Explaining this in a short way basically goes as “a monitoring tool keeps track of which servers are up and only enables them to resolve. Our geodns server then replies with the right server IPs, depending on in which region of the world you are.”. Which means streams.video.debconf.org will resolve to the local streaming server lisa while you are here, at the same time resolve to a number (those that are up) servers in Europe if you are in Europe or to those in the US if you are there. Nice. (And while I’m already blogging - I do hate my laptops suspend, err - I mean non-suspend mode. Somehow it got worse in the last days, sometimes needing multiple minutes (like 10) to decide to suspend to disk, and the suspend-to-ram still wont work. I should really get someone here that knows this stuff having a look at it. :) ).

Romain Francoise: A .dsc/.changes aware scp

Every time I make a new emacs-snapshot release I have to copy the source package from my amd64 desktop to my i386 laptop to build it, then copy the built packages back in order to upload them. This scp'ing gets tiring after a while, so I wrote a trivial script called dscp which acts as a Debian-aware wrapper around scp, using python-deb822. It's similar in spirit to Myon's dget script, which does pretty much the same thing with wget.

Note that unlike scp it can only copy files to other machines, and currently does no command-line parsing at all, so you cannot pass options to scp (other than the user@host:/bla part, of course).

Also note that if the destination is local it will serve as a .dsc/.changes aware cp, which is also handy in some situations.

If there's interest I could probably add some sanity checks and propose it for inclusion into devscripts.

Stefano Zacchiroli: packages svn maintained on alioth

Figures About SVN-Maintained Packages For fun and profit I and gares have just harvested a bit alioth to discover how many packages are currently maintained using subversion. The overall result is larger than I expected 3492 source packages (to be compared with 11786 total packages in unstable) are maintained using Subversion. The numbers might be a bit approximated, I report what we did to extract these number for review. The number of subversion-ed source packages have been computed running on alioth the script harvest source fields.sh (which in turn uses svnlook grep.py) its stdout can be redirected to a .txt file. Once sorted and removed of duplicates you will get something like source pkgs on svn.txt; its length approximates the number of source packages maintained via svn:
$ wc -l source_pkgs_on_svn.txt
3493

The approximation is due to the fact that debian/control are looked for everywhere in a repository, hence it can find old packages no longer in the archive or never uploaded, and some fake package (like "MODULE NAME", but it seems to be the only one). The amount of packages which are in the above list but not in the archive is about 900 packages. Still I don't think it would be fair to exclude all of them since I guess a non trivial part of that are packages that haven't yet uploaded and hence are arguably part of the active development of Debian. Excluding them, the percentage of unstable maintained using SVN on alioth is about 22%. To that you should add the packages maintained using other version control systems. The total number of source packages in unstable have been computed on my laptop as follows:
$ cd /var/lib/apt/lists/
$ ls *Sources
ftp.it.debian.org_debian_dists_unstable_contrib_source_Sources
ftp.it.debian.org_debian_dists_unstable_main_source_Sources
ftp.it.debian.org_debian_dists_unstable_non-free_source_Sources
security.debian.org_dists_testing_updates_contrib_source_Sources
security.debian.org_dists_testing_updates_main_source_Sources
$ cat *Sources   grep ^Package:   sort -u   wc -l
11786

The broader goal was to discover how many packages are maintained using any versioning system on alioth, but we were fluent only in svn internals. Dear lazyweb, feel free to harvest and forward to me your data for the other versioning systems available on alioth, I'll keep this post updated with news.

Bernd Zeimetz: hacking at debconf

hacking at debconf Zenoss Stefano reported about the work on the Zenoss packages yesterday, now I m proud to be able to present the first screenshot from Zenoss, freshly installed by using dpkg -i. There s still a lot of work waiting for Fabio, Stefano and me, but it s great to see the first results. It s really great to work together with them, here on the Debconf. I m really happy that I can be here. At the moment we re waiting for Sean Finney no arrive, as we have some questions about dbconfig-common. hacklab pano 3 Again, here s another pano from the hacklab 1, taken yesterday evening. Sorry for the bad stitching, didn t have the time to fix it, but I hope it ll still give am impression of the great atmosphere here in the Teviot.

Meike Reichle: What I learned during my thesis ...

Right, so as announced I finished my thesis this week. Its translated title is (if anyone want to know)

"Design and Implementation of a Model for the Retrieval of Free/Libre Open Source Software using a Case-Based Reasoning System".

Writing it certainly was an educational experience but I am still happy it's done now. Especially the last weeks where rather unfunny, more so since about ten days before my deadline we had a massive heat wave here in Lower Saxony. Now that it's done I am still waiting for enthusiam to kick in. So far weariness still prevails. Maybe also because finishing my thesis does not yet end my studies. We also have to do written and oral examinations which will take place in July and after. So at the moment I spend my days mostly sleeping and trying to muster up enough wanderlust for my trip to DebConf7. (At the moment the prospect of traveling long distance with trains and cheap flights and then be surrounded by a few hundred happy people is still rather daunting.) Anyway, in order to give an impression of my last weeks and months and to sum this all up, a list of random notes, taken during the last weeks, of what I learned while writing my thesis:

Joachim Breitner: Shift-Caps-2

The Caps lock key is quite useless, most people agree with me here. So I configured my system to make the Caps-Key a general control key: Caps-E starts a terminal, Caps-t lists my tomboy notes, Caps-Down selects the next workspace, Caps-2 selects the second workspace. For the workspace switching commands, there are also variants with Shift that move the current window, so that Shift-Caps-Down moves the window to the next workspace, Shift-Caps-3 moves the window to the third workspace and Shift-Caps-2 does nothing.At first I thought it was a misconfiguration, but upon closer inspection I found out: As soon as Shift and Caps are pressed, all keys in the line F1-2-W-S-X, as well as the key are not registered, not even by the kernel, it seems. Is this some old legacy problem with PC keyboards, when the bits of a key code were hardwired in the keyboard? And is there a way around it?

Michal Čihař: Motorola support in Gammu

As I wrote in past, one of targets in next stable Gammu release is to have much better support for Motorola phones. The biggest problem with them is that Motorola separated AT commands in two separate subsets and each can be issued in different phone mode. I just hacked support for this into Gammu, so basic operations with Motorola phones should work. If you have Motorola phone, I'll welcome you to test new code. Just download current snapshot or use subversion to get latest code, compile it and run against your phone.

Anthony Towns: Dunc-tank Report Ideas

Okay, so with the “Bits from the DPL” talk that Sam and I shared now out of the way, that hopefully means finishing off the whole dunc-tank thing won’t imply any more conflicts of interest, potential or otherwise. And since we’ve now had the post-etch release team report, there shouldn’t be much to wait around for. I’d been kinda hoping to be able to come to debconf with a pre-prepared report of similar quality to the debconf6’s final report (or debconf5’s for that matter); but while I was going back through the discussion threads, it just got harder and harder to find a way of writing the report that didn’t seem like it’d just inspire the same arguments again. I think that’s avoidable – I know some of the people who were against the way dunc-tank ended up have indicated there are other approaches they might support, and it ought to be possible to summarise the dunc-tank experience in a way that lets us have a better idea what to do in the future based on that experience, than have the same disagreements we’ve already had. Anyway, my best guess is to try crafting the report via blogging or put it on a wiki or something. Anyway, there are three things that I thought we could usefully have in a report that wouldn’t devolve into the same old arguments (after all, if we at least have new arguments, that’s some sort of progress!). First of all is trying to have a real understanding of what happened with etch – getting a release out is complicated with lots of potential blockers beyond just “release management” work: d-i, kernel, toolchain, CDs, builds, bug tracking, whatever. Presumably dunc-tank only ever had a chance of removing release management as a blocker, and since we can’t redo the etch release while changing parameters like dunc-tank or Vancouver, at least having as clear as possible understanding of which blockers happened when, and what other influences might have been important the release process seems like a good way of understanding the influences that were and weren’t important, so we can have a better idea what to do in future. I’m figuring a reasonable structure might be something like: The theory is that the above should provide the information to make a good judgement of what (if any) effect dunc-tank (or the other projects) had on the release, without implying a preconceived conclusion of whether dunc-tank’s “good” or “bad” or whatever. As well as looking at the release stuff in some depth, it seems to me to be pretty sensible to do a report on how dunc-tank worked financially. Anyone doing any similar sort of “let’s raise funds, then spend them on free software” is going to have similar issues in getting publicity, collecting funds, and actually spending them, no matter how they end up deciding on the harder questions of deciding who or what to fund. There’s not a lot to say there, and I don’t think there’s much that’s controversial there either, but there are a few problems and approaches to solving them that are worth reporting on. I think that’s about as far as you can get trying to cleverly avoid the controversy though. And presuming we rule out the idea of choosing a position on some of the controversial questions and advocating for that (“dunc-tank was good, paying release managers was awesome, we should do it again for everyone!”), the best idea I’ve had so far is to just try summarising some of the controversial questions that remain open, which Debian, or dunc-tank, or whoever can then address in whatever way we like – by GRs, or further debate, or more experiments, or leaving it to other people to do for us, or whatever. So having the questions and some of the arguments for various answers and summarising what happened with dunc-tank seems like a plausible way to go. The questions I’ve got: No promises as to whether they’re the best questions, the best sub-points, or that we’re going to be able to come to an answer on any of them. :) Anyway, that’s my theory so far, no I need to grab some lunch before the next lot of talks – feel free to mail me, or talk to me in person, or blog responses or whatever…

Russell Coker: A Lack of Understanding of Nuclear Issues

Ben Fowler writes about the issues related to nuclear power in Australia. He spends 8 paragraphs discussing the issues on the “Right” side of politics - of which 6 concern the an Australian nuclear weapons capability and then spends 3 out of 5 paragraphs related to the “Left” side explaining that he thinks that everyone who opposes nuclear power is a Luddite. Ben didn’t bother providing any links or statistics to back up his claims, so I’ll assist him in analysing these issues by providing some facts that we can discuss. In March Spain had wind power provide 27% of all electricity (making wind power the main source of power for the country). I blogged about this at the time. While Spain has an ongoing program of building new wind power stations the majority of wind turbines in Spain are quite old (the Model T of wind power) and not nearly as efficient as modern turbines that would be installed for Australian power plants. The Danish government has announced plans to use wind power for 75% of their electricity. Denmark has a much smaller land area than Australia, which means that generating so much electricity from wind power is more technically challenging for them than it would be for us. A larger land area means that when one area has low wind speeds other areas can be used to provide power. For home electricity generation wind turbines have not yet been proven to be practical. The linear speed of the blade is determined by the wind speed and the rotational speed is therefore a factor of the wind speed divided by the radius of the blades. This means that smaller turbines have higher rotational speeds which causes more noise (bad for getting council approval), also to avoid turbulence a wind turbine will ideally be some distance above the ground (8 meters is good) which again gives problems when getting approval. The O’Connor Hush Turbine is supposed to solve the noise component of this problem. It will be interesting to see whether home based wind power becomes practical in future - if so I would like to get an O’Connor turbine on my house! Home solar power has been proven to work well, in the form of both solar-electric and solar hot water (I know several people who have been happily using them for years). You don’t get cold showers when the sun isn’t shining, you instead use gas or electricity to heat the water (it’s a standard feature in a solar hot water system). Also your home electricity doesn’t go off when the sun stops shining, you have batteries that are charged during sunny times to run things overnight, and when they get flat you pay for power from the grid. It is quite realistic to stick solar power systems on every roof in the country. The added cost to the process of building or purchasing a house is negligible and the benefits include having electricity when mains power is unavailable (NB water is used in generating electricity from coal or nuclear power plants so a bad drought will eventually become a time of limited mains power). Even the smallest home solar electric system will produce enough electricity to power a fridge and freezer 24*7 so it’s a very useful backup for essential power. The government is subsidising the installation of solar electric systems, so it seems that they expect everyone to get one eventually. Dr. Ziggy Switkowski (the main advocate of nuclear power in Australia) says “the introduction of a carbon tax could make nuclear power the cheapest option by the 2020s”. In consecutive paragraphs Ben derides “carbon trading” and claims that nuclear power is “practical”. Unfortunately the main advocate of nuclear power in Australia does not believe that it is practical without a carbon tax. Ziggy also states that it would take at least 15 years to complete a nuclear power plant, unfortunately we don’t have the luxury of waiting for 15 years before starting to try and reduce the damage that we are doing to the environment. The Stern report makes the economic consequences of inaction quite clear. I am not a Luddite. I oppose nuclear power because of the risks related to accidental release of radioactive material and the routine release of radioactive material as part of the uranium mining process, and the dangers related to long-term storage of nuclear waste (let’s not assume that Star Trek science can make it all non-radioactive). Nuclear power is not cost effective for Australia and will take so long to develop that it won’t save us from the serious economic damage predicted by the best scientific models as presented in the Stern report. For large scale power generation wind power works now, can be easily implemented and has no hidden costs or risks. There will never be a Chernobyl type accident with wind power, it is inherently a safe technology. For small scale power generation (something you can add to your home) solar power works well, is not expensive (when considering the price of a house and especially when the government subsidy is counted) and has the potential to seriously reduce the amount of carbon dioxide produced.

Wouter Verhelst: DebCamp/DebConf

After having been here in Edinburgh for about a week now and not having blogged about it, I'm starting to feel slightly guilty about it. Only slightly so, however. I did figure out that the wireless on my PowerBook doesn't work with 2.6.21, whereas it seems to (flakily) work with 2.6.18. Yay broadcom. Not. Anyway, life here in Edinburgh has been fun so far. Mostly. I had a bit of Mao-playing, some bit of "putting faces to names", a bit of Scotch-tasting (of which I still need to remember taking one (1) bottle home for $BROTHER who really likes the stuff), and a bit of getting-so-drunk-I-woke-up-not-yet-completely-sober-and-decided-it-might-be-nice-to-find-my-bed-again, too. Like I said, mostly fun. The guy puking on my luggage last night wasn't fun, but at least he managed to puke most of it right next to my luggage. But I'll still have some laundry to do, I guess. DebCamp to me isn't about being productive, so much as it is about meeting people and getting to know the environment. But I still managed to do some work on nbd-server, which is now at version 2.9.3 (plus some patches stolen from svn) in Debian. That helps, too. In an hour or two, I'll be doing my m68k got kicked out of etch!?!?! Oh noes! BoF. The schedule already lists 11 people who will be attending, so that's cool. Let's hope we get something productive out of it.

Meike Reichle: Just when you are about to give up ...

It actually seemed as though I wouldn't be going to DebConf this year. I didn't get to work much the last two months, since I wanted to spend all my time on the near completion of my thesis so I didn't have the money to pay for a flight (or train) to EDI and back myself. Due to that same thesis I also didn't have the time to prepare a talk this year so I was also not a speaker. Since I am also neither a DD nor in NM I was pretty sure I wouldn't be eligible for travel sponsorship this year. And, as expected, I was indeed very far down the queue, so when I still hadn't heard anything about being sponsored until about a week before DebConf was starting I had pretty much given up on the whole thing and resigned to the fact that this year's DebConf would happen without me. However, on 10 June I had a mail in my Inbox. Subject: "Your travel cost sponsorship request for DebConf7". It seems the DebConf team was able to dig up some more money and do another run on the sponsorship queue. This was three days before I had to get my thesis to the print shop and I wasn't really doing anything else except for frantically going over my proof readers' annotations, doing last minute additions, changes etc. and occasionally lie down for a few hours of rather uneasy sleep. So my first reaction was something along the lines of "What?! Now?! I don't have time for this now! Go away!" and I was pretty close to answering the mail saying "Thank's but that's too short notice. I won't be coming, have fun, see you all next year." Luckily Tolimar prevented this though and actually managed to find a flight for me that not only goes on the actual days that I had originally planned to arrive and leave but that is also not far over my travel sponsorship! So, long story short, I'll be flying to EDI on Wednesday. It'll only be for the very last few days and I am probably already missing out on lots and lots of stuff, but at least I'll be able to attend for a few days. And in time for debian-women's third birthday! :) I just hope everything will go well, it seems there's a lot of trouble with flying to DebConf this year, at least judging from what I read on planet and heard on irc. See you all soon!

MJ Ray: Blogging from debconf7: The Journeyer

Just stopped off in Derby on the way to Edinburgh. It was a good move in one way, because my inbound train was running over 30 minutes late (diverted due to the floods in the Midlands) and my outbound one is only 10 minutes late... but the manager just announced flooding in West Yorkshire, so I guess we'll see. The inbound train was called Vyjaer Kernewek (or something like that), which was nice to see. Derby was useful in another way (besides a good wifi-enabled light meal at the big blue coffee shop). I bought a laptop case. I didn't plan that when I set off, but by Bristol it was already obvious that I couldn't carry all my widgets in one bag. I also couldn't get the laptop out on the train, for fear of a packing explosion. So, Derby has shops. It also seems to have a market-free market place as the focus of the city centre. There's a view up to the cathedral, a small waterfall... and the Derby Mountain Rescue. I suppose the peaks are near, but mountains? The market wasn't in the marketplace. It seemed to be under cover in two parts. One is in the guildhall and the other is in a shopping centre that seems to have an identity crisis - is it the Eagle Centre, or is it Westfield? - and also has a building site attached that greets you as you approach from the railway. Not good tourist promotion. Until the building site, the City-Rail Trail is signposted well, about 5 minutes walk, but the signposts are a bit odd. I noticed the funny ridges first and dismissed them as an anti-spin thing, but then I noticed some bronze floppy disks (I'll post a photo once I find the right USB lead). Other attachments included spark plugs and glasses. There's no sign explaining it that I saw. What the heck is that all about? Coda: No, it wasn't a good move. Apparently there's more flooding in South Yorkshire, so I arrived about midnight and this is posted the next day. At least I'm having a better time of it than damog, who's stuck in New York and I wonder whether other tales of woe will appear on Planet Debian as people find net access. Now for breakfast and planning the day.

Junichi Uekawa: I managed to use the washing machine at Budget Backpackers.

On the way I managed to wash and dry the Debconf badge, but it seems like it survived. Good news.

Isaac Clerencia: Foocast, podcast for (Spanish speaking) dudes

Several of my workmates and I are regular listeners of technology-related podcasts like Diggnation, TWiT or FLOSS Weekly (which BTW is as “weekly” as the Halley comet). Some days ago we realized that there weren’t similar podcasts in Spanish (or at least we didn’t know about them), so we thought that creating one would be cool. During this week we recorded our pilot, we had some problems with sound and I spoke a bit too fast, but I think it’s nice overall, at least I would enjoy listening to it :) Trying to emulate people like Kevin Rose or Leo Laporte (in the media business since 1991), who create podcasts professionally, is quite hard for amateurs like us, but we’ll do our best. Be sure to check it at Foocast (sorry, Spanish only, that’s the whole point :P )

16 June 2007

Aigars Mahinovs: You are next!

We need you ...You are next! Tokkee and I are doing the mugshots this year and we need your cooperation. Mugshots are a great way for people to link the name to a face and remember that link even after several years. Liw did this as his project last year and it was great success - many people have now a better way to link a persons IRC nickname to their face which in turn reduces the tension in communication as you can very easily know who is the person you are speaking to.
There are people who avoid the mugshots and i wanted to ask them to reconsider. Mugshots is not a beauty pageant - in Debian people are judged by their merits. Mugshots are useful tools in future on-line communications, tools that could reduce the aggressiveness and flammability in the Debian IRC and mailing lists.
It is not the holy grail, but it helps. So I ask every participant of Debconf - help us make this mugshot gallery complete by contributing your own picture. And thank you very much to the many people that already did.
If you want to have your mugshot taken then listen out to when mugshot sessions are taking place - we take all mugshots in front of the cafeteria door, usually during the food times, so you have easy time finding me and tokkee there. UPDATE: First 120 mugshots are uploaded here. Next mugshot shooting session will be tomorrow - on the 18th of June, during scheduled lunch and dinner.

Michael Janssen: Ask the Interwebs #1

Lately I have been thinking about switching source code management systems. In years gone by, I have used CVS, Subversion, arch, and most recently bazaar-ng for managing all the source code that I have to change. Lately I have been unhappy with the speed that bazaar takes to get some things done, and after watching a Google talk by Linus about Git, I thought I would give it a look.

I was surprised to find out that it actually models the way that I work normally slightly better than the bazaar model does. The main thing is that a repository holds a bunch of branches, but the working directory only has one of those branches checked out at any point in time. I use bazaar with about 4-5 branches per project, and only work on one of them at once (normally, sometimes I want to transport a bug across a couple branches) - so the "working space replaced by branch you want to work on" actually works out OK for me. I also need to collaborate with a bunch of projects at school and work that use other systems including CVS and Subversion, which Git seems to make it easy to do.

I did run into some questions that I don't really have a good answer to, however, therefore the new segment on the blog: Ask the interwebs. Normally I would just ask on some IRC channel, but the Minneapolis public library doesn't seem to allow anything but HTTP out. On to the question!

When using Git, how do you manage having multiple computers (at multiple locations) that you work on? I have approximately 5 different computers that I use regularly. Luckily I have enough space to have git installed on all of them, and I also have a web server that I can use WebDAV on if necessary. What I would like to have is a repository that I can pull from before I start work (if I am connected) and then push to when I finish so that the next computer I sit down at I can just pull again and get everyting. I would like this to include any branches I may have made on the first computer. Is this possible, hard, or easy for Git users? How much do I need to worry about slowdown? My WebDAV server is in the cloud, and I would prefer to be able to get up and go on say, a minute's notice.

I'm also interested on what your workflow is like even if it doesn't match the model I just described. I'm open to changing - the bazaar-ng to git change is big enough that I can probably incorporate a new workflow as well.

Comments: (8) Trackbacks: (1)

Comments
  1. adrian: hi, i'm a just a newbie so can't help much.
    You can host your push repository in http://repo.or.cz.
    If you prefer to do it your own you have git-daemon (Have a look to tutorials). Good luck!
  2. Michael Janssen: I looked at the public repo.or.cz, but decided against it, because while I want my branches to be available at some point, I'd rather not all of them at the same time. People randomly finding them is okay, but I'm sure I'll check in unworkable/uncompilable code in this state, because I would basically be using git as an easy sync between computers at times.

    I'm just really interested in how other people deal with this issue of needing semi-location-independent access to the branches.
  3. mike: Sounds already good for you to use git.

    Enjoy!
  4. R mi Vanicat: I haven't answer to the synchronization problem on my blog post because it is one I don't have. Still, you can make a git repository that can be pull and push from, and git can use https/dav or ssh or its on git protocol for this.

    Just read man git-remote, man git-push, man git-pull and man git
  5. JM Ibanez: Just upload a bare git repository (e.g. copy /.git in particular) to a server you have ssh access to. Then, in your working copy in git 1.5:

    <br />
      $ git remote add upstream git+ssh:///path/to/bare/git<br />
     


    You can then

    <br />
      $ git pull upstream .<br />
     


    or
    <br />
      $ git pull upstream/some-upstream-branch my-local-branch<br />
     


    or
    <br />
      $ git push upstream/some-upstream-branch<br />
     
  6. Josh Triplett: A followup to that: you can do the same thing without ssh access, by using WebDAV. See Documentation/howto/setup-git-server-over-http.txt in the Git source (also available various other places in other formats).
  7. Steven Walter: Whenever I want to create a non-local git repository for push, whether for sharing the code or just backing it up on another system, I follow this procedure:

    ssh remoteserver
    mkdir myproject.git
    cd myproject.git
    git --bare init --shared=all # world readable, group writeable
    chgrp -R git .
    vi description
    exit
    # back on local system
    git remote add origin git+ssh://remoteserver/path/to/git
    git push origin master:master
    git push origin branch2:branch2 # repeat for other branches

    You may then want to re-create your local branches so that they "track" the remote branches. "man git-branch" for more details on this.

    Hope that helps!
  8. brian m. carlson: For your workflow, you can try this:
    [geshi lang=sh]
    # first time on each machine only (you can use DAV, too)
    git remote add server git+ssh://server-hostname/path/project.git

    # every time
    git push server
    ssh anothermachine
    git fetch server
    git pull server branch-on-server-to-merge-from
    # merge happens; continue working
    # start over again from the push
    [/lang]
Trackbacks
  1. How I use git
    Michael Janssen ask about workflow and git, so I will explain mine. I have three types of git repositories: git-svn repositories where I don’t have write access on the upstream subversion repositories. git-svn repositories where I do have write ...

Stefano Zacchiroli: debcamp excitement

Debcamp is productive Shame on me for having underestimated the productiveness of DebCamp/DebConf. This year I'm overwhelmed by things to do and the first (for me) 2 days of DebCamp have really been productive. Yesterday the Zenoss packaging has taken off. We have already implemented (thanks to Fabio) the needed changes in dzhandle to properly handle ZEO databases, added user management for the zenoss system user, updated the documentation and we started working on the dbconfig-common stuff (we also have just noticed that Seanius, dbconfig-common author, is arriving tomorrow at DebConf, what a great occasion!). Today I've worked more on the OCaml packaging side. A first working version of OCaml 3.10.0 is now available in experimental .. ehm, oops, I meant in the NEW queue; CamlP4 available in there has been finally properly split into (huge) pieces and people can start rebuilding OCaml packages against it. Next day, actually hour, exciting adventures for me include: Wow, I'm overwhelmed, but it's actually soooo fun!

Gustavo R. Montesino: bzutils 0.1

Following with the Summer of Code, I've just released bzutils 0.1. The release announcement:

---

I'm pleased to announce the release of bzutils 0.1.

bzutils is a python module to interact with bugzilla servers.

Current features:

* Query bug reports through boogle (gnome's bugzilla search improvements)
or boolean charts.

* For each bug report, gets the following metadata: id, product, component,
status, resolution, reporter, assignee, summary, priority and severity

The source code for bzutils 0.1 is available at
http://bug-triage.alioth.debian.org/

Debian packages are being worked on and should be available soon.

Next.

Previous.