Search Results: "ag"

15 August 2008

DebConf 8 video: the Debian Videoteam -- Behind the Scenes

Since 2005, the talks at Debconf have been recorded on video, to be
published online. Beginning in 2006, talks have also been streamed
live. One of the goals is to get recordings in high quality online
immediately, with little or no post-production work. The video
switcher dvswitch, realized in software, and a disk-based recording
workflow is bringing us closer to that goal. Tape is still used as
backup in case of failures, but we expect those to become rarer as
the system matures. A large part of the post production work is
restoring failed recordings.

Dvswitch was developed by Ben Hutchings just in time for the Debconf7
in Edinburgh. It enabled a multi-camera live production using cheap
cameras and modest laptops. The laptops relays DV streams over
TCP/IP. This avoids any degradation due to long cable stretches, and
makes cabling cheap and convenient. The output is DV straight from
the cameras, producing a very crisp master video.

Dvswitch works with sources and sinks. The sources send video from a
file or a firewire port to a listening instance of dvswitch, which can
run on a remote machine.
dvswitch listens to several sources and displays a scaled down black
and white preview image of each one. One of the sources is displayed
at full resolution in colour; this is the outgoing stream, which is
sent to the listening sinks. Each sink may send the stream to disk or
to an encoder for live streaming. It is common to do both; store the
raw master to disk, and forward the master to an encoder, and
subsequently to a streaming server.

While dvswitch saves us a bundle in hardware, the video team is still
heavy on manpower. Remotely operated cameras would help, and we are
still looking for affordable solutions that work well on Linux.


The talk will cover the hardware, software and manpower required for
a typical dvswitch usecase. Some caveats and challenges regarding
sound, lighting and rigging will be discussed. A live demonstration
of dvswitch in use will be given. We would also like to offer
rehearsal sessions with the demo rig for those who are interested.Full event details

DebConf 8 video: the Debian Videoteam -- Behind the Scenes

Since 2005, the talks at Debconf have been recorded on video, to be
published online. Beginning in 2006, talks have also been streamed
live. One of the goals is to get recordings in high quality online
immediately, with little or no post-production work. The video
switcher dvswitch, realized in software, and a disk-based recording
workflow is bringing us closer to that goal. Tape is still used as
backup in case of failures, but we expect those to become rarer as
the system matures. A large part of the post production work is
restoring failed recordings.

Dvswitch was developed by Ben Hutchings just in time for the Debconf7
in Edinburgh. It enabled a multi-camera live production using cheap
cameras and modest laptops. The laptops relays DV streams over
TCP/IP. This avoids any degradation due to long cable stretches, and
makes cabling cheap and convenient. The output is DV straight from
the cameras, producing a very crisp master video.

Dvswitch works with sources and sinks. The sources send video from a
file or a firewire port to a listening instance of dvswitch, which can
run on a remote machine.
dvswitch listens to several sources and displays a scaled down black
and white preview image of each one. One of the sources is displayed
at full resolution in colour; this is the outgoing stream, which is
sent to the listening sinks. Each sink may send the stream to disk or
to an encoder for live streaming. It is common to do both; store the
raw master to disk, and forward the master to an encoder, and
subsequently to a streaming server.

While dvswitch saves us a bundle in hardware, the video team is still
heavy on manpower. Remotely operated cameras would help, and we are
still looking for affordable solutions that work well on Linux.


The talk will cover the hardware, software and manpower required for
a typical dvswitch usecase. Some caveats and challenges regarding
sound, lighting and rigging will be discussed. A live demonstration
of dvswitch in use will be given. We would also like to offer
rehearsal sessions with the demo rig for those who are interested.Full event details

DebConf 8 video: Managing 666 packages, or how to tame the beast

Maintaining one of the largest set of packages in Debian, the Debian Perl Group
needed a tool for sorting the work, showing progress made by other
members and easing the sponsoring of uploads, as many active members of the
group aren't DDs.

Based on previous ad-hoc scripts, PET was written almost from scratch with the
idea of making it usable by other packaging groups, and it even is useful
for individuals tracking their own packages. It separates completely
presentation from data retrieval, and its modular structure allows to create
easily new sources of data and checks. (For more information, see
http://wiki.debian.org/Teams/DebianPerlGroup/DebianQA)

Today it helps a small group of people maintain over seven hundred packages (we
passed the 666 mark recently, so the joke is already old) without going insane.

Main functions:
* track new upstream versions
* show which packages prepared by non-DDs are ready for upload
* highlight several problems with packages and repo organisation
* follow uploaded packages' journey to the archive
* and lots of information packed in one place

This talk will introduce this tool, show how it's best used and a bit about its
internals so you can customize it (and contribute patches!).
Full event details

DebConf 8 video: Locating bugs to kill with SOAP

A tutorial on using the SOAP interface to the BTS as well as other
methods of tracking, organizing, modifying, and killing bugs in the
interest of developer sanity.

* Introduction to SOAP interface
- Using the bts select tool to do complex selects
- Using the soap interface directly
- perl, python and ruby examples
* Using usertags and usercategories
- How to customize views
- Commonly used bug tags
* Triaging bugs
* Using the new summary feature
* Running a local mirror of the bts using new debbugs packages
- Selecting bugs to mirror
- Tracking changes
* Finding abandoned bugs
Full event details

DebConf 8 video: Packaging with version control systems

A lot of Debian is already using version control for the task, but everyone cooked up something of their own, more or less. We think the situation is similar in the other distros: the current approach to package maintenance doesn t scale too well, given today s needs (teams, offline work, increasing number of users and increased use of the bug trackers), and discussions of how to improve things are on the way, but have not yet carried fruit.

Furthermore, maintainers of a specific package in all distros basically have the same task. We could benefit from each other if we joined forces: less workload, improved access to patches in use by other distros, more structured communication, a wider spread of innovation, etc..

The goal of the vcs-pkg.org project is to integrate version control with distro package maintenance. We want to recognise all involved in the process, from upstream, the package maintainers of the various distributions, their security and release teams, and power users, who aren t afraid to fix their own bugs, and give maximum flexibility to them.

vcs-pkg.org is a (D)VCS-agnostic effort, so you don't have to fear advocacy. Instead, I would like to deliver to you the status quo and hope to get your valuable feedback. We've made good progress, but we haven't reached our goal, so your input will make a difference.Full event details

Steve Kemp: My ass is on fire! Spank my ass

This has been a rather random few days. For those of you that don't know it mod_perl is an Apache module which embeds perl into your webserver. You can use this to write extensions, handlers, and all kinds of fun things in pure perl. Me? I just changed the beefy CGI script that I use to power a couple of my sites from being plain-CGI to being mod_perl-CGI - that means: The downside is that I have to "/etc/init.d/apache2 reload" if I change my script, or any of my custom modules it uses. (I suspect this is something I can fix; I just don't know how yet :) All that was possible, with zero changes to my applications as I use the CGI::Application framework - lucky? or planned? I'll let you decide ... In terms of speedup I can now process about 100 requests a second, compared to 10. As reported by the Apache-benchmark tool. Cool. ObFilm: The Mummy: Tomb of the Dragon Emperor

DebConf team: DebConf Talk Feedback (Posted by Joerg Jaspert)

Like last year, we have a feedback system available again. If you attended an event during DebConf and want to give feedback on it, including free-form text to the presenter, this is your chance! As an attendee To give feedback please look at the schedule and select the event you want to comment on. You will notice a box saying Did you attend this event? Give Feedback, follow its link and fill out the form. As a speaker If you want to see what feedback your event got, please log in to the submission system and select the event you want to know more about. You will see a tab named Feedback, behind which you can find all the newly-written love letters.

Sune Vuorela: maemo + packaging + kde4

maemo sdk seems to come with a cdbs, debhelper and dpkg-dev too old to make it easy to build several debian unstable packages like kde4.
maemo seems to come with glibc2.5 and debian/armel kde4 packages depends on 2.7 or greater.
trying to build a newer dpkg in maemo environment requires several perl modules not available - and when buildling those, a circular build dependency is quickly reached. So - dear lazyweb, what does smart man do now?

Kartik Mistry: Debian Lenny on Macbook


* Not much tweak needed for installation, except following lines before installing LILO:
chroot /target aptitude install refit
/target/sbin/gptsync /dev/sda
Now weekend is for other things to make them work by reading long Debian on Macbook Wiki page.

Joachim Breitner: Debian on the FreeRunner

I ve been at DebConf for almost two week, but haven t blogged a lot about it. It s mostly because we ve been working on getting Debian to run on the OpenMoko FreeRunner. Today we finally sent out the official annoucement for this, because it seems that the installer script and packages seem to work so far.Great thing about this is the sheer amount of software that s now available on my phone. I already blogged about running Xmonad on it, and I have also ran my screen-message program, on it, as can be seen here. I only did minimal testing of the phone features, because it would be relatively expensive here in Argentinia with my German SIM card, but it seems to work as well.

Stefano Zacchiroli: edos-builddebcheck

Statically detecting FTBFS with edos-builddebcheck Here at DebConf8, after my talk about Mancoosi, I got in touch with several people interested in the QA implication of the EDOS/Mancoosi tools. Me and Ralf have for example been contacted by Ubuntu people which are setting up theirs equivalent of http://edos.debian.net. A guy working on a mirroring tool made an interesting hack using edos-debcheck: out of a mirror with broken dependencies he can mirrors a subset of packages which do not suffer of the same problem. But now to the more interesting development, following a bug report by Atomo and discussions with Lucas (the RC-bug-filing-master), me and Ralf implemented edos-builddebcheck. You can invoke it on a pair of Packages/Sources package list, and it will check whether some packages will FTBFS due to unsatisfiable dependencies. The results on Lenny main/amd64 as of today are, ... erm ..., scary : 49 packages will FTBFS. The RC-bug-filing-master and Ralf are working on filing them, "don't worry". You can find edos-builddebcheck in the edos-debcheck package, starting from version 1.0-7 (in incoming at the time of writing). Update yes, ATM edos-builddebcheck does not know anything about P-A-S packages, so there are some false positive. Still, 33 source packages are proper hits.

Romain Beauxis: Byte swap and amd64..

Some really weird issue just poped to my eyes today, while coding some big->little endian code for liquidsoap. We have a 2 bytes swaping code that does the following: ((x) & 0x00ff) 8 ((x) & 0xff00) >> 8) However, this is not working at all on my amd64/x86_64 box (core2duo CPU). I get a horrible saturated sound.. So, I copy-pasted this from oss4:
static inline short
bswap_16 (short x)

short y = 0;
unsigned char *a = ((unsigned char *) &x) + 1;
unsigned char *b = (unsigned char *) &y

*b++ = *a--;
*b++ = *a--;

return y;
.. which is working.. ! So, I'm stuck with one function that I understand, should be working, but isn't, and one that I don't understand, but is working.. May a C guru give me some pointers about this issue ? I believe it's connected to some sort of architecture specific issue... Thanks in advance !! PS: the bswap_16 function included in byteswap.h from libc6-dev doesn't work either, and yields the same saturated sound..

Clint Adams: Dey knows what dey is talking about

Once there was a professor, and they assigned a paper on epicene singular they in common usage around their school. One student interviewed other students as part of their research, and another student cited their paper as part of their research. They handed in their papers on time, as did most of the rest of the students, and the professor graded them. There was a hint of plagiarism in them, and they didn't know what to do about them. In the end, they appealed to the Academic Integrity Committee, and they discussed the matter with them. Some of the them redefined success. They said that they reaped the benefits of flexibility, whether political or not, and that they did not suffer from problems of ambiguity or sounding illiterate. They, but not all of them, also said that prescriptive grammar was oppressing them, and that evidence of epicene singular they from the Middle Ages was clear basis for belief that subjunctives were dead and that they were only used by sticklers and language bigots. They maintained that they were keeping them down. The grades did not necessarily reflect this. They could infer from them that they had seen a world where they could use several anonymous antecedents of varying gender and number, and they would not need to use artificial gender-neutral pronouns when they could just rely on good and proper epicene singular they. They knew that once language shaped thought enough, there would be no need to expend the extra effort to clarify the doubts introduced by them using the same word to mean fifty different things, because they would just know what they were saying. They didn't care at all that it sounded incredibly stupid. They only cared that they were right.

Jeff Bailey: Mouse hunting?

Not the plastic kind, the squishy furry kinda that need to GET THE HELL OUT OF MY HOUSE.

GRRR

Yesterday was visit 4? 5? from the exterminators. We got them to lay more traps. And this morning (I love my son dearly. Especially the opportunity to cuddle him to sleep at 4am. *sigh* I'm actually mostly serious. I've only been able to hold him for a few weeks now, and weaning means that I'm getting to do a lot more with him that only [info]auzure_skies could do before. And how long will a child let himself be cuddled to sleep? This is just mixing poorly with the jetlag from the recent trip) I had the joy of watching the mouse run out from beside where one trap is, and behind the couch where another trap is, triggering neither of them.

What I really need is a flame thrower and a forgiving insurance company.

GRRR

John Goerzen: Asus violating GPL again?

There was a small firestorm last year when people realized that Asus was not releasing source code to GPL'd components of the EeePC. At the time, they eventually did post source code on their website.

Recently I bought an Eee 901. Asus has modified the kernel's ACPI driver. They released the source code to that on an 8G surf model, but the 901 has additional hardware features in the ACPI space (bluetooth radio power toggle, for instance) that are not in the source they released back then. There are no sources released at all under the 901 section of their website.

Anyone know whom to contact at Asus about this?

Junichi Uekawa: Recovered Macbook.

Recovered Macbook. Thanks to several people at Debconf who have helped me out in this task, I have Debian running on my MacBook, again, on a new harddrive. The silliest part was not noticing that disk was GPT partitioned and not noticing it was, thinking that I partitioned with MBR/FAT partitioning.

MJ Ray: Gov.UK Consults on Forced ISP Snooping: Please Say NO

Argh! Our beloved leaders have just started a consultation on making it mandatory for internet service providers to keep email and web logs for a year and deliver them to local councils and police on request. Large ISPs have already been doing this, in order to make friendly-friendly with gov.uk, (do their customers know they are being watched?) but requiring it of all ISPs might put some small user co-operative hosting services out of business because it will drive up costs (need more disk to store that data and staff time to distribute it on request). Not what I expected from a Labour and Co-operative Party government. Fortunately, the Lib Dems and Tories are speaking sense like this:-
“Ministers have proven time and time again that they are not to be trusted with sensitive data, but they seem intent on pressing ahead with this snoopers’ charter. ” (Source: BBC)
However, I’m pretty sure when the EU-level parts of this were being discussed, the Lib Dems and the Tories agreed with it. Something I’ll ask Neil Parish MEP when asking him about the progress of the promised reply to my three strikes by the backdoor questions. You can see why I’m sceptical about the “but it doesn’t mean what it appears to say” assurances, can’t you? They were worthless last time, and the time before that, and the time before that (yes, I’ve been doing this so long that I supported ST@ND). The consultation closes after this year’s Parliament and the Internet conference, which could also be an interesting place to ask questions about it. And it’s another consultation I should ask the Phone Co-op (aff) about. Please reply to the consultation and give a loud “NO” - if you have particularly good reasons, please let me know in a comment. I’ve no argument against policing, but a year’s logs? Local councils? There are too many holes in this to let it pass unchallenged. Thanks.

14 August 2008

Holger Levsen: What has a pirate flag to do with Debian?

Some people asked me during the group photo why I brought a pirate flag to the group picture. One explaination is is pretty simple, but not the real answer: since DebConf5 there always has been a pirate flag at DebConf. The real answer to me is, that if the content mafia wants to label the cultural technique of copying, which is as old as humankind and the base of all our inventions as "pirating", them I'm very proud and happy to be a pirate.

A somewhat longer answer will give you the films "steal this movie", part 1 and 2, which are available (under a CC licence) for direct download on homer at DebConf8 (please use the wired network..) or via torrents on their website.

The first part mostly tells the story of the raid of the piratebay servers in Sweden, while the second part tries (and IMO succeeds very well) to paint the bigger picture. My favorite quote from the movies is "when the winds of change are blowing, some people are building shelters and others are building windmills".

Another insightful (and scary) quote is "you can't stop filesharing without a police state", and if you look around, that's what's being tried. So why is the content mafia afraid of file sharing? It's not really because of us consumers being consumers and "stealing" some content. I'm sure they can live with the "loss", that's not the reason. What they can't stand (nor survive) is millions of consumers becoming producers (and sellers of content). That's the threat they need to prevent.

And that's in very short why I think a pirate flag is appropiate at DebConf. We are producers and if free production of ideas and art is only possible for pirates, I say allrrrrrright ;-)

I very much recommend these two movies to everybody who is slightly interested in this topic and look forward for part 3, which should be in production by now. I hope this blog post made you curious to watch them, even though I feel that I couldn't summarize the movies as good as I would like to. DebConf8 took some tolls on me. I haven't even blogged about this wunderbare conference yet :-)

I also plan to bring a Debian flag to DebConf9 :-) If you happen to be an artist and want to create a design, I'd be very happy. At the moment I'm not fully sure if the flag will be printed or embroidered so the design should probably pretty basic. A red swirl on white (or black?) background, maybe accompanied with the letters "Debian". Other ideas or comments?

Eddy Petrișor: crazy idea: user supported snapshot.debian.net

I just had this crazy idea about solving snapshot.debian.net's space issue which just might work if done right.

We all know that snapshot.debian.net has ran out of space in early May this year and we all lost a valuable service. Since there are probably many users, developers and maintainers which find this service useful, it might make sense to think that the users themselves could solve the problem.

How? Think about implementing a really distributed storage/file system (not necesarly a real file system) that can rely on cluster nodes that can enter or exit at any time and the nodes are contributed by users, very much alike the GoogleFS file system (or maybe clients in a torrent swarm).


First problems that I can already see:

Other ideas:
What do other people think?

Jacobo Tarrío Barreiro: Blacklights

I’ve been playing with a blacklight here at Debconf, during the keysigning party. (Hey, I’m a geek; what did you expect.) Of course, I cannot resist sharing what I saw: I looked at more passports, but those are the ones I can remember off the top of my head. A couple of notes before I publish this post:

Next.

Previous.