Search Results: "ed"

17 February 2011

David Welton: Random github idea: show pull requests on the network

Another day, another "which ^(&^%*&*^&()* version should I use?!" with github: https://github.com/gramos/easy-fckeditor/network Github is nice, but very, very often all the forks are the very model of a modern major paradox of choice. Which one should I use? Which one is best? Do the forks exist because 1) the original author stopped bothering? 2) because the forkers just wanted to be 'cool' and have their own fork? 3) because the forkers don't have a clue about open source and don't attempt to submit their patches back? Who the hell knows, in most cases. This is frustrating. I had a random idea that might help some: if the 'network' view were able to show you, at a glance, the amount of interaction between different forks: pull requests accepted and rejected. At least we'd get an idea of what sort of community is forming around the project, and also have an idea whether the forkers and/or the authors are good open source citizens or not. Of course, as my friend Salvatore says, "pull requests are not conversations", but it's better than nothing.

Cyril Brulebois: Debian XSF News #5

Time for a fifth Debian XSF News issue!

16 February 2011

Steve McIntyre: Progress Linux

Saw Daniel's announcement about Progress Linux today. Best of luck with the project - it's great to see more and more Debian derivatives, each focussing on the bits that they care about most.

Lucas Nussbaum: Introducing the Debian packaging tutorial

One of the common complains about Debian packaging is that it s hard to learn because, while there is quite a lot of high-quality documentation, it is often written more as a reference manual than as a tutorial: it s great if you already know everything and want to check some detail, but not so great if you want to learn everything from scratch. I have been volunteered (i.e, someone decided I volunteered) for a Debian packaging tutorial at work, so I decided to give a try at tackling this issue. I also volunteered (voluntarily this time) for a similar talk at RMLL 2011 to make sure I would be forced to do the work and prepare the actual tutorial. I m also considering teaching this next year in Licence Pro ASRALL, but I haven t made up my mind about it yet. The result is a work in progress (hey, I still have a lot of time), but in the release-early-release-often tradition, I m making it public now in the hope that someone will pick up the idea and do all the work for me (you never know). I ve decided to create a set of slides using Latex Beamer. The current version can be found here. The sources are available in a git repository, and all contributions are welcomed (including plain comments or suggestions). The last slide is the current TODO list.

David Welton: Rails Application Templates

Thanks to some friends on twitter, I recently discovered RailsWizard which is a very handy way of generating new Rails applications with the "right" things included. I liked what it did a lot, so I took the generated file and saved it as a github gist: https://gist.github.com/829521
Which provides me with a very handy starting place for new Rails projects. This is a great way to get some of the housekeeping out of the way before we start: ensure we're using jQuery, add some gems that I always use like exception_notifier and will_paginate, and so on.

Steve Kemp: Upgrading from Lenny to Squeeze

Rather than waiting for a few months, as I typically do, I decided to be brave and upgrade my main virtual machine from Lenny to Squeeze. That host runs QPSMTPD, Apache, thttpd, and my blogspam server; nothing too complex or atypical. The upgrade was mostly painless; I was interrupted several times by debconf asking me if I wished to replace configuration files I'd modified, but otherwise there were only two significant messages in the process:
crm114
crm114 warned me that its spam database and/or configuration files had changed and would most likely result in brokenness, post-upgrade, and I should do something to stop avoiding lost mail. Happily this was expected.
sysv-rc
It transpired I had a couple of local init scripts which didn't have dependency information succesfully encoded into them; so I couldn't migrate to dependency-based bootup. Given that this server gets a reboot maybe once every six months that wasn't really worth telling me about; but nevermind. No harm done.
That aside there were no major surprises; all services seemed to start normally and my use of locally-compiled backports meant that custom services largely upgraded in a clean fashion. The only exception was my patched copy of mutt which was replaced unexpectedly. That meant my lovely mutt-sidebar was horribly full of mailboxes, rather than showing only new messages. I created a hasty backported mutt package for Squeeze and made it available. (This patch a) enables the side-bar, and b) allows you to toggle between the display of all mailboxes and those with only new mail in them. It is buggy if you're using IMAP; but works for me. I would not choose to live without it.) Now that I've had a quick scan over the machine the only other significant change was an upgrade of the mercurial revision control system, the updated templates broke my custom look & feel and also required some Apache mod_rewrite updates to allow simple clones via HTTP. (e.g. "hg clone http://asql.repository.steve.org.uk/"). So in conclusion: ObQuote - "Hmm, upgrades " - The Matrix Reloaded (shudder).

Dirk Eddelbuettel: RcppArmadillo 0.2.12

A new version 1.1.2 of Conrad Sanderson's Armadillo templated C++ library for linear algebra came out a couple of days ago. This has now been wrapped into a new version 0.2.12 of RcppArmadillo, our Rcpp-based integration into R. The short NEWS file extract follows, also containing Conrad's entry for 1.1.2:
0.2.12  2011-02-15
    o   Upgraded to Armadillo Version 1.1.2    Flood Kayak 
         * Faster prod()
         * Faster solve() for compound expressions
         * Fix for compilation using GCC's C++0x mode
         * Fix for matrix handling by subcubes
And courtesy of CRANberries, here is the diff to the previous release 0.2.11:
Diff between RcppArmadillo versions 0.2.11 dated 2011-01-08 and 0.2.12 dated 2011-02-16
 RcppArmadillo-0.2.11/RcppArmadillo/inst/include/armadillo_bits/syslib_proto.hpp             only
 RcppArmadillo-0.2.12/RcppArmadillo/ChangeLog                                                    6 
 RcppArmadillo-0.2.12/RcppArmadillo/DESCRIPTION                                                 17 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/NEWS                                                   12 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/doc/RcppArmadillo-unitTests.pdf                     binary
 RcppArmadillo-0.2.12/RcppArmadillo/inst/doc/unitTests-results/RcppArmadillo-unitTests.html      6 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/doc/unitTests-results/RcppArmadillo-unitTests.txt      30 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/README                                          1 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo                                      13 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/Base.hpp                        15 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/Col_meat.hpp                    14 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/Col_proto.hpp                    8 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/Cube_meat.hpp                    6 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/Mat_meat.hpp                    20 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/Mat_proto.hpp                   15 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/Row_meat.hpp                    14 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/Row_proto.hpp                    8 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/arma_config.hpp                 10 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/arma_version.hpp                 8 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/arrayops_meat.hpp            only
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/arrayops_proto.hpp             448 +---------
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/auxlib_meat.hpp                 63 -
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/auxlib_proto.hpp                10 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/compiler_setup.hpp               8 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/config.hpp                      20 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/debug.hpp                       27 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/fn_conv_to.hpp                  60 -
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/fn_prod.hpp                     40 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/glue_solve_meat.hpp             10 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/glue_solve_proto.hpp             4 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/injector_meat.hpp                6 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/op_dot_meat.hpp                  2 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/op_prod_meat.hpp                29 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/op_reshape_meat.hpp              8 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/op_trans_meat.hpp                2 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/op_trimat_meat.hpp               4 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/podarray_meat.hpp                4 
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/subview_cube_meat.hpp           50 -
 RcppArmadillo-0.2.12/RcppArmadillo/inst/include/armadillo_bits/subview_meat.hpp                 8 
 39 files changed, 339 insertions(+), 667 deletions(-)
More information is on the RcppArmadillo page. Questions, comments etc should go to the rcpp-devel mailing list off the R-Forge page.

Stefano Zacchiroli: in the news - Debian and the FreedomBox

Fellow geeks who have attended FOSDEM this year probably remember Eben Moglen's announcement about the creation of a foundation to support the development of FreedomBox-es. The FreedomBox foundation and its goals have been featured in a New York Times article appeared yesterday, together with a nice Debian mention which points to our wiki. Debian is also prominently present on the (ikiwiki-powered) website of the foundation. Yet another reason why I'm proud of being part of Debian.
(thanks to Faidon for the heads up)

David Welton: The UnderPerformingStocks.com sale - halfway in

A few weeks ago, I had an "out-there" idea to try creating and selling a site at the same time. So far, it's not exactly raking in a major amount of cash: www.underperformingstocks.com is For Sale on Flippa! At $100 with a couple of bids, it doesn't look like I'll be able to retire on it! That said, I haven't spent a great deal of time on it, and part of the idea of the experiment was to limit the amount of time the 'new idea' would distract me from other things. I did hope to receive a few more "audience requests" in terms of what to build on Flippa.com, though. Hopefully, things will heat up a bit during the final two weeks of the auction, but I don't think "flipping" web sites is really a business I want to be in. It's been fun to see how much you can build with how little, though, what with all the widgets and API's out there these days. Since I'm a coder at heart, I also released some Ruby code that utlizes Google's stock screener API: https://github.com/davidw/google-screener - it's under the Apache license, and is kind of neat to play around with, I think, and is what I use to fetch information for the site.

Michal Čihař: SF.net has back git email notifications

As I have complained quite loudly in this blog, I think it's fair to post a status update again. Yesterday the emails started suddenly to work. So the major reason for my complains is gone. What I still don't like that this issue was not at all communicated to project admins. It stopped to work, what was sort of announced in blog post. It started to work again without any announcement and last status update in blog still claims they do not work. At least for direct question, we've received reply that they have intentionally re-enabled this service.

Filed under: English Phpmyadmin 0 comments Flattr this!

Gintautas Miliauskas: Interviewing with Google

I somehow made it through Google's phone interviews in one piece, and now they are flying me in for an on-site interview in Munich (Germany), which will take place tomorrow. Keep your fingers crossed for me!

I will be landing in Munich in a few hours, and today I am free to look around the city. Anyone from here up for lunch or a beer?

Kartik Mistry: Nexenta is hiring!

* It is always fantastic being with Kernel, Device Drivers, File Systems and Network Protocol and yeah, Illumos, NCP and NexentaStor! So, if you re around or in St. Petersburg, Krasnodar or Northen Boston (or even somewhere else too) read below :) we re hiring! From, John Goerzen s recent post,
Oh, and if you d like to work for us, you should probably be sending me an email. No, I m not going to list the address here on this blog post. If you can t figure it out, I don t want to hear from you

Michal Čihař: Photo of a week 6

Better late than never. Here comes photo from sixth week. Taken during tour in Cantillion brewery in Brussels. Gueuze in Cantillion

Filed under: English Photography 0 comments Flattr this!

Daniel Baumann: Progress Linux 1.0.0~pre1 (artax)

The Progress Linux project is pleased to announce the availability of the first prerelease of the upcoming Progress Linux 1.0 (artax). The images are available for download at: http://archive.progress-linux.org/progress-images/artax/ A full list of changes may be viewed at: http://www.progress-linux.org/releases/artax/1.0.0_pre1/

Gunnar Wolf: Responsible biking: We are not exempt from the traffic rules!

As you know, I very often advocate using the bycicle as the main means of transportation in Mexico City. The city is very apt for biking through it, and contrary to the fears of mostly everybody, the city is neither aggressive nor as dangerous as people say. However, I have seen cyclists which seem to be looking for the best ways to be hit by a car, or to hit a pedestrian. Yesterday, I read this note in La Jornada: The local Environment Secretary calls cyclists to respect vial regulations. Many cyclists assume they are a special case of pedestrians, and zig-zag as they please between the road and the walkway, or just stay in the walkway. That is dangerous, both to pedestrians and to themselves. You might find children, elderly or motion-challenged people on your way. Also, not only will pedestrians only expect other people in the walkway, moving at their pace or slightly more, but cars will also not expect somebody moving at 10-20Km/h. A car driver pulling out of his garage, or crossing a street, will not have enough warning when he sees you, and you are very likely to end up in an accident. Since ~5 years ago, Mexico City is growing a grid of Metrob s and confined troleb s cero emisiones (trolleybus) lanes. Many cyclists use those lanes That is VERY dangerous. Public transport vehicles are large, have a lot of inertia, and will take longer to react to finding you ahead of them. Besides, they can go way faster than a regular bike (~60Km/h for metrob s, ~40Km/h for troleb s), and have to stop every couple of blocks. So, you will be uncomfortable if trailing them, and you will be a liability to ~100 people if you go ahead of them. Besides, it is illegal to drive in the confined lanes if you are not a public, semimassive transport vehicle! Surprisingly many people have argued they prefer riding their bicycles against the traffic I think they prefer staring at Death into its blue, glowing eyes (or into its long, thin whiskers)... By far, most cars that hit a bicycle do so from the side, when crossing a road. And if you arrive at a crossing from the wrong way, the way a driver does not expect you, don't expect the driver to be aware of you. Also, in the much less likely event of a car running into you, would it be better to be hit at 80Km/h (60Km/h of the car plus 20Km/h of your own speed on a full frontal crash), or at 40Km/h (substracting instead of adding)? Yes, some people say that looking at the car will allow you to maneuver How far in advance would you know a car coming from the front will hit you? One second? That's 22 meters at 80Km/h (again, if you realize the 60Km/h car is heading straight to you, at 20Km/h). Too short notice for you to do anything Any maneuver will most likely end in an accident. And the driver would not be so much to blame, as he would not be anticipating you riding against the traffic. Make sure you get seen. By night, always use proper lights (red on the back, white on the front, and reflective material to the sides). Day or night, wear bright, reflective clothes (or over-clothes material). Act in a predictable fashion. Remember you are riding a vehicle and are subject to the same rules any driver is A cyclist is not exempt from driving correctly! Do not jump red lights. Never ride on the walkway. Do your best to enjoy the ride. And ride. Yes, ride, take the streets, enjoy the streets. But don't attempt to drive the traffic out of it The streets belong to us all, and we can all share them. PS I also saw this note in the same paper: Sunday Rides in "Campo Militar N mero Uno". The main military field was open as a park this weekend! I have to make sure it is regularly open I am definitively going there!

Russell Coker: Mplayer, Squeeze, and SE Linux on i386

I ve just updated my SE Linux repository for Squeeze to better support running mplayer on the i386 architecture, below is the APT sources.list line:deb http://www.coker.com.au squeeze selinuxThe first issue is a bug in the compilation of the SDL libraries which makes them request an executable stack (bug #613535). Recompiling the libraries on my system caused this bug to go away, so it must be some issue with the compilation process. I have previously summarised the execstack issue, but we haven t solved this yet [1].The next issue is the fact that the ffmpeg libraries require execmod access (see my previous post for the details of the execmod issue [2]. The execmod issue with ffmpeg is pretty much the same as it was when I first wrote about the issue in 2008 [3]Finally the allow_execmem boolean needs to be set on i386 with the command setsebool -P allow_execmem 1 to allow libGL the access it needs. This is an issue I haven t been able to solve, I don t know why libGL needs write and execute access to memory, I posted to the SE Linux list about this some time ago but didn t get any good answers [4]. Any suggestions would be appreciated.

15 February 2011

Lars Wirzenius: Experiences with SD

For a few months now I've been using SD for tracking bugs in many of my personal projects. SD is a distributed bug tracker, and I believe such systems to be the future, just like distributed version control has become the obviously correct choice. Distributed bug tracking is still in its infancy, and the tools are still developing. However, SD, at least, is already usable, at least for the small kinds of projects as mine are. I have no idea, at least yet, how it scales up to large projects with many developers. Life with SD is similar to life with a DVCS. You have your bug repository, and you make changes there as find bugs, fix them, and so on. When it is suitable and convenient, you synchronise your repository with others. I mainly sync to my server, so that others can sync from that if they wish. (I don't know if anyone does that.) There are several distributed bug trackers. I chose SD because it seemed the most mature one, but also because it does not tie the bug repository with the source code version control tree. This is quite important, I think. If there's a bug in the project's website, then that does not need to be committed to the project's source code. If I work on a bug in a separate code branch, I would like to make any necessary notes about it in a central bug repository for all the branches on my laptop. This is helpful, for example, if I have to back out of my code changes, because I did something stupid, but want to keep the notes I took in the bug repository. SD is not without its weirdness. The command line syntax is a bit un-Unixy, and it requires setting an environment variable to specify the location of the bug repository. (I wrote a little wrapper script to set it: all my branches for project foo are in ~/foo, and the bug repository is in ~/foo/bugs.) It could perhaps also be faster, but it's not exactly slow, either: it is a joy to be able to just run sd ticket close 123 rather than open a web browser, navigate to the right bug, and click close there. Also, once you have a bunch of projects, each with its own bug repository, it becomes an effort to synchronise each of them. I'm hoping mr will someday support SD, but until then I'm using a little wrapper that syncs my SD repositories to my server. I also have a third wrapper that allows me to run an SD command on each repository, so that I can, for example, easily get a list of all open bugs in all projects, which is helpful for my GTD weekly review.

Torsten Werner: Are we slaves?

We still have more than 300 new packages in Debian that needs manual checks and we have a lot of open bugs. I don t get paid for working on dak (the Debian Archive Kit) nor do I feel a deep passion on doing such work. I am contributing to Debian because it is a great project and because contributing is my way to say Thank you to all who made (and still make) it possible. BUT: are we slaves that are supposed to do any stuff for other people? Yesterday someone asked for an enhancement for dak via IRC. I ve kindly asked him: do you want to send a patch? (words are copied from the IRC session). Instead of answering no he sent a patch for 2 plain text files within 4 minutes after I told him the URL to dak s git repository. I could not do it faster by myself and I ve got many other open tasks. I ve applied the patch and activated it on ftp-master.debian.org. But today he ranted about my rudeness and he did not even managed to quote me correctly ( Please send a patch ).

Dirk Eddelbuettel: Rcpp 0.9.1

A new release 0.9.1 of Rcpp went to CRAN and Debian yesterday. This version contains mostly bug-fixes and rather few enhancements. The changes are mostly 'internal fixes' and not user-facing; they mostly address some issues in memory management which, while not tripping up the unit tests or common usage, caused trouble for advanced Rcpp modules use and repeated memory allocation / deallocation. This bit Doug Bates repeatedly, and he put his head down and debugged the issue. A number of changes fairly deep-down in Rcpp (as well as in R-devel) later, this looks much better and we owe him a hearfelt Thank You! A big Thanks! also goes to Luke Tierney who out some new memory debugging code into R-devel which the --enable-strict-barrier in R 2.13.0 (due in April) will enable. A related fix is also in R 2.12.2 due on the 25th. The NEWS entry is below; more detail is in the ChangeLog file in the package.
0.9.1   2011-02-14
    o   A number of internal changes to the memory allocation / protection of
        temporary objects were made---with a heartfelt "Thank You!" to both
        Doug Bates for very persistent debugging of Rcpp modules code, and to
        Luke Tierney who added additional memory allocation debugging tools
        to R-devel (which will be in R 2.13.0 and may also be in R 2.12.2)
        
    o   Removed another GNU Make-specific variable from src/Makevars in order
        to make the build more portable; this was noticed on FreeBSD
    o   On *BSD, do not try to compute a stack trace but provide file and
        line number (which is the same behaviour as implemented in Windows)
    o   Fixed an int conversion bug reported by Daniel Sabanes Bove on r-devel,
        added unit test as well
    
    o   Added unit tests for complex-typed vectors (thanks to Christian Gunning)
    
    o   Expanded the Rcpp-quickref vignette (with thanks to Christian Gunning)
    o   Additional examples were added to the Rcpp-FAQ vignette
Thanks to CRANberries, there is also a diff to the previous release 0.9.0. As always, even fuller details are on the Rcpp Changelog page and the Rcpp page which also leads to the downloads, the browseable doxygen docs and zip files of doxygen output for the standard formats. A local directory has source and documentation too. Questions, comments etc should go to the rcpp-devel mailing list off the R-Forge page

Lucas Nussbaum: Re: please send a patch

It seems that Matthew Palmer misread my blog post as a complaint against developers asking for patches in exchange of pet feature requests. He really should pay more attention, since I gave pet feature requests as an example of case where it would be appropriate to ask for a patch:
Of course, there are cases where it s perfectly reasonable to ask for a patch: when the task is expected to take hours, or when the result is of limited interest to everybody except the demander.
But even then, it s not clear. This morning I got an email from a someone involved in PHP packages maintenance, who said that Bugs Search @ UDD was a great tool, but that he would love to have a way to list all bugs affecting packages with the implemented-in::php debtag.
To produce a working patch for this would probably take him at least an hour. You need to set up a copy of the CGI on alioth, understand the DB structure, dig into the code, etc. If you don t understand SQL and Ruby, it could be a really difficult process. Also, it s probably quite uninteresting for him to do that, since he is unlikely to stick around developing UDD.
Instead, it didn t take me more than 5 minutes to produce a one-liner.
The net result for Debian in that case? 55 minutes saved by a developer. Update:
Torsten Werner wrote an angry reply to my post. It s true that yesterday s episode triggered my blog post, because I felt quite frustrated to have to provide a patch for something that simple, and would have preferred to use the time for a Debian task where I would be more efficient. But I was not particularly angry at that episode, since that s something I ve seen on several occasions. That s also why I did not mention any team in particular.
The feature request I was making was reasonable, and cannot really be considered a pet feature request (though I might be biased with my QA hat on): mentionning in the dak templates used for bug closure that packages removed from Debian can still be found on snapshot.d.o. The fact that he thinks that addressing this himself turns him into a slave raises interesting questions.

Next.

Previous.