[Soc-coordination] Weekly report - Debian GNU/Hurd Debianish initialization
Hi Planet Debian :) my name is Justus Winter, I'm a computer science student at the University of Hamburg. I'm participating in the GSOC 2013, my `task https://wiki.debian.org/SummerOfCode2013/StudentApplications/JustusWinter`_ is to make Debian/Hurd systems boot using the same initialization scripts Debian/Linux uses. I spent the community bonding period with some gsoc related administrative tasks, updating my development machine and getting reacquainted with the Hurd system. It was nice to see how far Debian/Hurd has come since my last serious `encounter https://lists.gnu.org/archive/html/bug-hurd/2010-05/msg00033.html`_ with it. I've setup a continuous build solution on one of my Hurd VMs and prepared a package repository. I'll post details once I have some packages to share. I built the hurd, sysvinit and ifupdown packages and dived into the interesting world of literate programming. I'm going to write about that when I start looking into the ifupdown related issues. But most importantly I started writing a tool to automate all the tasks I would do during my work that could possibly be automated. As I'm working on the boot process, it makes sense to use some kind of virtualization software so I can work in the comfort of my usual development environment. My virtualization solution of choice is qemu and I actually wrote a qemu based black-box test solution for a former employer once, so I already was familiar with qemu and wrapping my own code around it. Without further ado, here it is: https://bitbucket.org/teythoon/hurdtest Provided that you have `golang` installed, you can compile it easily:: teythoon@europa /tmp % export GOPATH=`pwd` teythoon@europa /tmp % go get bitbucket.org/teythoon/hurdtest teythoon@europa /tmp % bin/hurdtest Usage: hurdtest [options] command [arguments...] Currently it has the following subcommands: test Starts a VM, logs in as root, tests the interaction with the VM, verifies that certain VFS locations are writable, tests the network connectivity, the DNS resolution and installs and runs the `hello` package. update Executes `aptitude update aptitude full-upgrade`, reboots the system and runs the `test` subcommand. If successful, it commits the changes to the virtual disk and creates a snapshot. overlay Takes as argument the path to a directory that is copied to the VM, reboots the machine and runs the `test` subcommand. The `update` command is nice because it allows me to keep the VM up to date while ensuring that the image remains usable, with respect to what the `test` command considers a usable state of a Debian system. I'd really like to get some suggestions on how to test the health of a Debian system. You can look at how the tests are implemented in `test.go https://bitbucket.org/teythoon/hurdtest/src/75408323a0f78e63aaa36bc4b950dc78de458b61/test.go?at=default`_, it's quite easy to add more and more interesting tests, and you don't even have to clean up after them or worry about any side-effects as the changes are not committed to the virtual disk. This is `hurdtest` doing an update:: teythoon@europa ~/repos/hurd/hurd-tests % bin/hurdtest update 2013/06/22 19:59:45 starting kvm [-drives file=image.qcow2,cache=writeback,snapshot=on -serial unix:/tmp/285813369/serial -monitor unix:/tmp/285813369/monitor -nographic -m 512] 2013/06/22 19:59:45 Waiting for grub... 2013/06/22 19:59:46 Waiting for login prompt... 2013/06/22 20:00:05 Updating system 2013/06/22 20:02:52 Get: 1 http://www.local unstable InRelease [8279 B] Get: 2 http://http.debian.net sid InRelease [205 kB] Get: 3 http://ftp.debian-ports.org unreleased InRelease [23.9 kB] [...] Setting up perl (5.14.2-21) ... Reading package lists... Building dependency tree... Reading state information... Reading extended state information... Initializing package states... Reading task descriptions... 2013/06/22 20:02:52 Update successful. Snapshotting system... 2013/06/22 20:02:53 Rebooting system... 2013/06/22 20:02:54 Waiting for grub... 2013/06/22 20:02:59 Waiting for login prompt... 2013/06/22 20:03:16 Running main.testTrue... 2013/06/22 20:03:16 Running main.testFalse... 2013/06/22 20:03:17 Running main.testClean... [...] 2013/06/22 20:03:18 Running main.testNetwork... 2013/06/22 20:03:18 Running main.testResolver... 2013/06/22 20:03:20 Running main.testAptitudeInstall... 2013/06/22 20:03:46 Test successful. Reverting system... 2013/06/22 20:03:48 Halting system... 2013/06/22 20:03:53 Committing changes... 2013/06/22 20:03:57 Creating snapshot... 2013/06/22 20:04:04 All done. bin/hurdtest update 157.31s user 69.71s system 87% cpu 4:18.94 total The `overlay` command implements my work flow. I can edit scripts or drop hacked up executables onto my VM and see the results without any manual intervention. There's the
Re: [Soc-coordination] Weekly Status Report 6.17-6.21 by ShuxiongYe
Was the rebuild with OpenJDK 7 done during the community bonding period? (I guess so looking at the bugs linked from the page). Could you point us to documentation on the rebuild: the list of results and how the rebuild was done? No, things go a little different with the plan. We are going to fix the existing bugs on the list first, and I think it would be finished in a week. Then we do the rebuild in week3(July1-July7) or week4. -- Sincerely Shuxiong Ye School of Electronics Engineering and Computer Science, Peking University ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
[Soc-coordination] Student Blogs
Hello, Debianite-GSoC'ers, If any of y'all have blogs, I'd love a link to them! Cheers, Paul -- :wq ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] [GSoC students] Weekly status reports wanted
Hello, Hi Paul, First, a tidbit: please avoid sending html email to the list: it's considered bad form as it makes the mails bigger for next to no gain. Thanks in advance! Sorry for the html mail. It was the default in gmail. Changed it now to plain text. This all looks great, thanks. I have a few small questions: - Do you have some screenshots of the application in its current state? I saw some mockups floating around but it'd be great to see and follow the real thing while it gets built. - What are your plans for next week? No need to go into much detail, it's just to get a feel of what's to come and whether things are going on schedule or not. 1. I uploaded screenshots to the git repo https://github.com/uberspot/DebianDroid I'll update them whenever something changes. 2. My plans included mostly a) Integration of the ActionBarSherlock to the project so that compatibility with android 2.2+ is guaranteed. (I did this today and everything works fine :) ) and b) for the next 8-9 days work on each UI page and build it's elements (buttons, input areas etc). Thanks again, -- Nicolas Dandrimont kind regards, Paul ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] Fedmsg for Debian, weekly status report 17/06 - 21/06
Simon Chopin chopin.si...@gmail.com writes: Hi, I'm Simon, from France, and I'm working on using the fedmsg message system for the Debian infrastructure, with Nicolas Dandrimont as mentor. Hi Simon; Thanks for that first report. It sounds like you are making a reasonable amount of progress despite having such troublesome mentors/sponsors ;). d ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] Leiningen Clojure packaging - Report 0
Eugenio Cano-Manuel Mendoza eugenioca...@gmail.com writes: Hello, My name is Eugenio Cano-Manuel Mendoza. I'm currently working on improving the packaging process of programs made with Clojure Leiningen [1]. A deliverable of this project is to provide a set of tools compatible with debhelper that can make a working debian package out of upstream's tarball with very little interaction. This is what I've been working on so far. Hi Eugenio; Thanks for that very thorough report. In particular, pointing out your version control repo is a good thing for other students to emulate. d ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
[Soc-coordination] GSoC Students: Information about your reports
Hi everyone, Thanks for sending in your reports. Some points which we thought we should elaborate: - Because there was some confusion about this: the Friday deadline is a hard deadline. As for the time zone, as long as it is Friday in some part of the world, you should be good :) - If you are busy for some reason and cannot send your report on Friday, you can send it before that. If that is also not possible, just email us in advance -- we understand you can get busy and that is fine, but you should communicate this to us. - You can continue blogging/logging your progress wherever you want or your mentor wants, but you have to send a copy of the report to this mailing list. - You should have a plan for the next week which details what you will be doing; simply stating that you will be working is not enough. - While we expect you to be verbose, you don't have to necessarily write a full page report. Think of it as this way: you should get your message across that you were working for the entire week, detailing what you did, in as many words as you would like. - Please point us to the code repository you will be using for GSoC if you haven't already. We know that this sounds a lot to do, but you will thank us later when you all complete your GSoC successfully :) -- Sukhbir, on behalf of the Debian GSoC admins ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] Weekly Status Report 1 - scan-build the archive
On 06/22/2013 11:31 PM, Nicolas Dandrimont wrote: [Cc'd you to get your attention. I won't do that in the future if you don't ask for it explicitly, so please monitor the list for replies ;)] [[ SIEVE FILTER BREACH ;-) ]] Just one thing that I feel is missing: could you tell us just a bit about your plans for next week? Hi, I'll definitely include a plans for next week section in my future reports ! For this week : * improve the new firehose branch I created * ask Fedora guys on -devel lists about it * find a final naming convention * see what other improvements could be done for scan-build full supoort * finish the install of debuild.me (ethel, lucy) on virtual machines. * write some documentation about it * find out the best way to put scan-build in the debuild.me loop * talk with Mathieu about scan-build HTML-presentation for firewose Cheers, -- Léo ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] Status Report of ZFS on Linux Integration, Week 0
Aron Xu happyaron...@gmail.com writes: During the past days, I did the following things: 1. Started reading Oracle ZFS Administration Guide 2. Continued my previous work on all kinds of license auditing. 3. Continued to assess the status quo and to check things out on Aloith's Git. Hi Aron; Can you tell us a few more details? How did what you accomplished this week compare to your plan? What do you plan to accomplish next week? Can you point us to some of your work (for example, version control repository or patches in a mailing list). Thanks, David ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
Re: [Soc-coordination] Status Report of ZFS on Linux Integration, Week 0
Hi, On Mon, Jun 24, 2013 at 8:46 AM, David Bremner brem...@debian.org wrote: Aron Xu happyaron...@gmail.com writes: During the past days, I did the following things: 1. Started reading Oracle ZFS Administration Guide 2. Continued my previous work on all kinds of license auditing. 3. Continued to assess the status quo and to check things out on Aloith's Git. Hi Aron; Can you tell us a few more details? How did what you accomplished this week compare to your plan? What do you plan to accomplish next week? Can you point us to some of your work (for example, version control repository or patches in a mailing list). Thanks, David Basically this week I continued the work that has been done before this GSoC project get accepted, and the goal is to have a working set of spl/zfs packages ready to upload. The license audit part is finished and I'll check current content of debian/copyright and update it when needed. As for technical side, current Git repository[1] is building and working, while my mentor and I have an agreement that filesystem is something that must be dealt with special care, and we want to make sure user's data do not suffer from overlook of design, so this part is mostly assess the status quo and to check for possible flaws in the way we handle the package, and there will be more details posted once the work has been finished (with big/minor change). As I'll be taking final exams[2] very soon so I'm not putting many load on myself about the project right now. A list of known situations: 1. SPL/ZFS does not see any license problem to fit into main in dkms form so far. 2. FTP team is in doubt about having zfs in binary form in the archive, i.e. udeb. There is a conversation with them (still waiting for a second reply), and will have impact on the way d-i support is provided. 3. Upstream and Debian kfreebsd people think zpool v5000 would be good, but Grub2 currently only supports v28 without third-party patches. 4. A (re-)implementation of dkms module dependency support (or equivalent) would make the packaging much more clearer. I've already have plans and will start conversation with upstream first. Current patch is in an embarrassing state by copyright/license, so I don't think it's good to disclose every detail before achieving an agreement with upstream. [1]http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/spl.git http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git [2]Already mentioned in my application. -- Regards, Aron Xu ___ Soc-coordination mailing list Soc-coordination@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
