Developers' Blogs: VMiklos

Archives for: July 2008

Thu, 31 Jul 2008

11:44:19 pm, Categories: packages, Posted by: vmiklos

using git-bzr

It seems recently one of my favorite topics is 'how to convert from $random SCM to git'

So, I already had a configuration using tailor, but that was slow. I know this already. Tailor is good because it always works, it isn't good because it's fast.

First, you need git-1.6.0rc0 or higher, you can find an fpm in my bmf repo.

Second, you need the bzr fastimport plugin:

bzr branch lp:bzr-fastimport

Then enable the plugin:

cd ~/.bzr/plugins; ln -s /path/to/bzr-fastimport fastimport

Now you can clone git-bzr itself:

git clone git://github.com/pieter/git-bzr.git

Put it to your PATH:

cd ~/bin; ln -s /path/to/git-bzr/git-bzr .

NOTE: so you should not symlink the dir, but the script inside the dir.

Okay, this is done, now clone (branch in bzr terms) the bzr repo you want to convert. For example:

bzr branch http://code.bitlbee.org/bitlbee/

Finally do the conversion (from the git-bzr README):

git bzr add upstream ../bzr-branch
git bzr fetch upstream
git checkout -b local_branch bzr/upstream
: hack hack hack
git bzr push upstream

Actually for now I only needed a one-directional convert, so my update-bitlbee.sh now looks like:

cd ~/scm/bzr/bitlbee
bzr pull
cd - # so we are again under bitlbee.git, it works in bare repos as well!
git bzr fetch upstream

And yes, the resulting trees match perfectly!

(Yes, I plan to package git-bzr and bzr-fastimport but I want to give it a good testing first.)

Leave a comment

Mon, 21 Jul 2008

11:07:16 pm, Categories: packages, Posted by: vmiklos

fun on the gsoc list

The GSoC student list is not public, and to be honest, usually it's boring. In most cases you just want to read the mails matching ^From:.*google.com, and just delete the remaining junk. However, there was a funny thread there, about how others deal with the usual problem: if you want to describe others (read: who is not a geek) what do you do (hack PaX, rewrite git-merge, etc.) you probably need a half an hour. Or maybe it's better not describing your job at all. Let's see some funny quotes:

The "I gave up" one:

After the first 10 fails, I decided to say the following as fast as I can:
Me: "I am doing "something" and Google is paying me to do it. I don't know why they are, but I assume its' because they aren't evil and stuff. End of story".
Other: Oh.
(Coding resumes)

BTW, the guy adds vim support to anjuta. :)

If you have nice friends, you'll get:

People who don't understand usually state as much, followed by, "...but if Google is paying you, that's pretty neat."

The "involved" one:

Unfortunately, I end up rambling for twenty-plus minutes and they are sorry they ever asked...

The "practical" one:

In my case, everyone in my university thinks it is an intern program so they ask me when I am going to travel. I have memorized the response.

The "religious":

I spent about twenty minutes explaining to a reporter from business week the finer points of open source vs free software.

And the typo kign:

> thanks very much gays ......
>
GUYS .... really, I was miss typed ...
now, again. Thanks very much GUYS

(I hope this post does not count as a leak, though. :P)

Leave a comment

Sun, 20 Jul 2008

02:27:12 am, Categories: packages, Posted by: vmiklos

git podcast

in this mailing list post, the recent gsoc podcast is linked, which is actually about git. two times my project is explained as well, about 11m14s and about 26m09s.

it's usually hard to describe to people what i'm doing in my project, maybe this'll help a bit?

Leave a comment

Mon, 14 Jul 2008

12:41:58 am, Categories: packages, Posted by: vmiklos

asciidoc vs dblatex

so, in the latest stable version of asciidoc, the default pdf backend of a2x is dblatex, not fop.

given that this way we can avoid Java, that must be a good thing ;) (faster, freeer, etc)

here are a few tricks:

if you want to hide the "revision history" page:

<xsl:param name="latex.output.revhistory">0</xsl:param>

if you want to avoid the dblatex logo, just comment out the line:
```
<xsl:param name="doc.publisher.show">1</xsl:param>
```
it seems that atm the $$$ math expression $$$ form is not supported, but you can do for example:
```
++++
<inlineequation><alt>
\[ \$\alpha + \$\beta = \$(\alpha + \beta) \]
</alt></inlineequation>
++++
```
AFAIK this was not possible till now, using fop. :)

Leave a comment

Developers' Blogs: VMiklos

homepage

July 2008
Mon	Tue	Wed	Thu	Fri	Sat	Sun
<< <		> >>
	1	2	3	4	5	6
7	8	9	10	11	12	13
14	15	16	17	18	19	20
21	22	23	24	25	26	27
28	29	30	31

Search

Linkblog

Fw Backend

Back to life again
As most of the devels know, i'm back again. But i have no own packages, i maintain slin's packages till he has not enough time to do it. And i maintain the x86_64 buildserver (called helicon) again.
Another thing: i created a testing bts, where you can test the changes of Flyspray before applying to the "stable" BTS. The current version is a development version of 0.9.9, but the final 1.0.0 is coming very soon, so i don't want to upgrade now, i'd like to wait for the final release. So please test the current version of the test site and tell me here, in comment or in email to iron (a) ironiq dot hu.
One another thing: there will be another i686 buildserver available. Now i'm waiting for the M/B and a HDD, other things are here, so if the last part will be arrived, i can install it and can go to its location. Maybe the whole procedure will end in 2-3 weeks.
BTS
Hi all...

Today our BTS is already up and working (have to test). The base problem was, that 2 of our disks gone wrong due overheating (the refrigeation of the room gone wrong). Fortunately there wasn't significant data loss. The disks were replaced with new ones, and a new hd controller card replaced the one on the motherboard. And this caused the second fault: something was wrong with card (or the driver), but caused nice failures. I had to reinstall the sys and put back to the integrated controller to get work the disks properly. Now we are working on the cleaning of the sys and re-syncing the raid arrays.

Sorry for the long failure.
BTS upgrade - last procedure
Due noone send me bugreport about the new testing BTS, i decided to upgrade the main BTS (http://bugs.frugalware.org). The upgrade will start on Monday (17th July) and will last approx. 2-3 days (i hope so). During this time the BTS will NOT be available, because i have to clean the database and upgrade it.

Please be patient during this time.
BTS upgrade - not far from the end
Well, maybe some of you have seen the test BTS. Now it's upgraded to the devel version. I also added a small feature into it (and accepted by the author, so that will be available soon in svn). So maybe it will be available soon on the main site.
BTS upgrade end
Today i did the upgrade. There was a small database cleanup (fortunately this was more simplier now then the testing was) before the upgrade. That's why the upgrade was faster then i thought. After this i copied the files from the testing BTS and the main things were ok. After small changes the site got its current status. So, the new BTS is ready to work.
Bugs downtime
Well, maybe you noticed, that bugs.frugalware.org is down. On weekend i wasn't at home, so i noticed the error only on sunday evening. The host was up again at 9pm, so i hoped that this was the last error. After this, slin and i was seeking for a better datacenter. We found a better one and wanted to start the procedure (TTL change in DNS, waiting for spreading, hosting change, dns change and so on) today, but i noticed that the host is down again. So we speed up the procedure and maybe today or tomorrow the machine will be available by IP and will be available by hostname at the end of this week.

Sorry for the long timeout again...
bugs is down
As some people noticed, bugs.frugalware.org is down (and also mail.frugalware.org is affected). Yesterday we noticed some heating problem, but had no time to examine the machine. Before rebooting the operator said that the fan is not working. But unfortunately i had absolutely no time to solve this problem. Maybe yesterday.
bugs up
Yes, it's up and working again. The downtime was a bit longer then i thought, but now the heating is quiet good: 2pcs of 8cm fan and a 12cm fan works now as heating. The HDDs' temperatures are below 40 Celsius (about 104 Fahrenheit). The raid1 arrays were OK after reboot.

Sorry for the "long" timeout...
Czech lang support & homepage-ng
This week the translation to czech language is started. The webpages is almos ready, now maybe comes the NEWS file or other translations (pacman and so).

AlexExtreme started comtributing to the new webpage. He has got some idea, me too. The base of the new news system is ready, i just have to implement to the webpage. I think next week or so there will be some viewable thing.
Frugalware Blog System
Welcome to our new blog system. As you can see, the blog is already at its final place, so here you can read our devels' posts. It's still not 100% complete, you'll see changins on the site (skin and so on), maybe a skin-change will come, but the core is ok.

I'd like to ask all of our devels to contact me in mail to create them a blog and a user.
fwlive 0.1rc12
After a longer testing period, 0.1rc12 is available.
There isn't any official announcement, because it's just a testversion. If everything is ok with this version, after a few small modification the livecd will be released (maybe next week).
Fwng - The new webpage
As you know, I'm on creating the new webpage for Frugalware. Well, some days ago i've got a big help, AlexExtreme. He created a new layout for the webpage and helped me to port the current fwng code to the new layout. Till he created this, i've made the rss, roadmap, authors, about, screenshot and the news page. Also the news page has a new feature: the news can be shown individually. Now we are working on simplifying the page access with mod_rewrite. Please see the page and comment it here or on #frugalware irc channel.
genesis-ng news
The new main server was under a big memtest that ended this morning (i switched off the machine). The result is quiet good: the memtest was running more then 120 hours without error. The contact was informed that we'd like to replace the old genesis to the new one. Currently we are waiting for a contact time when we can do the change.
Helicon downtime
Because of unknown reason the sw raid1 broke up and the OS could not start correctly. With the local sysadmin i started working on the problem, but the buildserver won't be available tomorrow and if the problem cannot be solved, then on weekend, too. Sorry for the long timeout. Also the darcsweb is affected.
Helicon downtime and BTS upgrade
Helicon downtime:
At this weekend there will be a complete network donwtime at out x86_64 buildserver's network provider. The downtime will be on 8-9th of July (this weekend). Because of this, helicon won't be available from saturday morning till sunday evening (or so). We hope everything will go well and won't be any problem or slippage. Please don't start longer builds that cannot end on Friday. Thanks...

BTS upgrade
I started upgrading our BTS to a newer version. But this is not as easy as i'd like to. I realized that a previous upgrade changed the database structure a bit. I copied to a new one and cleaned it and as i could see, without any problem. But i'm not sure about it, so please test it and report on frugalware-devel mailing list. The test page is available here: bugs.ironiq.hu.
Main Server Change
Today the main server - called "genesis" - was changed to the new one. The downtime lasted about 1hour. This time we did some upgrade. The new server's response time is much better than the old one. Thanks for all of the donators.
New build server
Well... Yesterday we have got a donation, that we have been waiting for a long time. A brand new Athlon64 mainboard with CPU and DDR400 memory (here are the parts' specs, with a modification: the memory is a Hynix 512MB DDR400). These tools are in my hand and will be put into its place maybe next week (if everything will be ok). I'll put pictures here, as i'll have enough time to work with it.
New buildserver...
As you know, we've got a big donation, a new x86_64 buildserver. Well, the machine is ready and will be put into its final place in this week, maybe tomorrow or the next day. Its name is "helicon" and will be available for the devels maybe on this week.
Other...
If the devels want to have a blog here for its news or side-projects, send me an email to iron(a)frugalware.org with the username and the wanted blog name and I'll create it
New webpage is coming...
I've been talking with VMiklos and we decided to rewrite the whole webpage. We are waiting for a new design. Till it is not ready, we were talking the new things. For example the pkg search page will be rewritten. The database will be redesigned, because the current version is a bit slow and a bit buggy. We would like to create a better and easier way to translate the page: using gettext (if it's possible).
As we were talking about these things, i've been thinking about the FwLive homepage. The new subdomain will be ready perhaps this night or tomorrow. The address is: http://fwlive.frugalware.hu . Here will be available the scripts I've written for the live configuration. This weekend i'll continue writing the scripts, next week i'll install the 32bit version of Frugalware and will test the scripts. If everything is ready, maybe after Christmas the LiveCD will be ready.
Other, but important weekend work
Yesterday evening i decided to search and implement a new anti-spam thing. I didn't know which one should be useful, but i've had idea. I decided previously to implement somehow the captcha security. After some searching i've found a nice plugin to this blog engine. I decided to include this. After some hacking the security is now working. Maybe not so nice, but working and this is the most important for me.

Syndicate this blog

RSS 2.0: Posts, Comments

Original template design by François PLANQUE.