• Uploading is done through HTTP PUT directly in debexpo, and handled immediately. This means that packages can be available within seconds of you uploading the package instead of having to wait for a cron job running an importer.
• debexpo supports plugins for several stages of package life-cycle. The main use of these are for QA purposes on the package, such as automatically running Lintian, checking the watch file, or checking bugs closed actually belong to the package in question, but there is scope for much more. Plugins are easy so you can customize a repository to check for whatever you want. Other cool plugins allow features such as pulling an orig.tar.gz from Debian if it is absent from the upload and not in the repository already. Plugins provide you the option to customize your repository for any purpose.
• Users will be able to have their own personal repository (much like Launchpad’s PPAs) to host binary packages. This is simply achieved by creating a new user, uploading, and adding the appropriate entry to your sources.list.
• Sponsors will be able to tell debexpo what kind of packages he or she likes to see, and a filtered package list will be shown. These kind of filters will include whether it’s a python package, or C library, whether it uses CDBS or straight debhelper, or even whether the maintainer is in the New Maintainer process (this is clearly a mentors-specific feature).
• Packages will be able to be commented on by other users, in the same way as Ubuntu’s REVU tool. This keeps package discussion in one place, and Debian Developers can claim to have uploaded the package. This is useful to stop the scenario of a Debian Developer reviewing a package that has requested a sponsor, and then finding the package has been uploaded already after the initial uploader left no mention of this.
• And more to come.

#include <cwidget/toplevel.h>

#include <cwidget/dialogs.h>

namespace cw = cwidget;

cw::toplevel::init();

1. cwidget is Unicode-aware and the ok() routine expects the message string to be a wide-character string. In this case, that means that we need to pass in a wide-character string (indicated by typing L in front of the string).
2. The second argument tells cwidget what to do when the ok button is pressed. The expression

     sigc::ptr_fun(cw::toplevel::exitmain);
   

   creates a slot using libsigc++. Briefly, a slot is a reference to a function or to a method of a class instance. When invoked, this particular slot will call cwidget::toplevel::exitmain(), which causes the main cwidget loop to exit. The slot is wrapped in cwidget::util::arg, a utility function that handles passing slots as optional arguments.

cw::widgets::widget_ref dialog =
    cw::dialogs::ok(L"Hello, world!",
                    cw::util::arg(sigc::ptr_fun(cw::toplevel::exitmain)));

cw::toplevel::settoplevel(dialog);

cw::toplevel::mainloop();

cw::toplevel::shutdown();

$ g++ -o hello hello.cc $(pkg-config --cflags --libs cwidget)

my-device-name:x:1801:1801:my-device-name,,,:/home/my-device-name:/usr/local/sbin/cerealshell

$ cat /usr/local/sbin/cerealshell
#!/bin/bash
set -eu
cereal attach $(id --user --name)
$

#!/bin/bash
createconsole()  
  NAME=“$1”
  PORT=“$2”
  BAUD=“$3”
  MUID=“$ PORT/USBserial/180 ”
  echo sudo addgroup --force-badname --gid $MUID $NAME
  echo sudo adduser --force-badname --gecos “$NAME,,,” --ingroup $NAME --uid $MUID --disabled-password
$NAME
  echo sudo adduser $NAME dialout
  echo sudo mkdir -p /home/$NAME/.ssh
  echo sudo chmod 755 /home/$NAME/.ssh
  echo sudo touch /home/$NAME/.ssh/authorized_keys
  echo sudo chmod 644 /home/$NAME/.ssh/authorized_keys
  echo sudo chown $NAME:$NAME /home/$NAME/.ssh /home/$NAME/.ssh/authorized_keys
  echo sudo cereal-admin create $1 /dev/$2 $3 $1 $1
  echo sleep 2
    echo sudo cereal-admin start $1
  echo echo -----
 
createconsole my-device-1 USBserial1 9600
createconsole my-device-2 USBserial3 115200

• I was actually expecting a deeper technical content on some of the talks.
• Some speakers were just very bad at presenting, they were either boring with a very exciting topic or lacked the spark to get the audience attentive.
• Some people on the IRC channel kept criticizing what some (not very known in the Perl circle) speakers were talking about. For instance, the usual stupid argument of "why to do this, if we can already make it with...", or "yeah, but we can do that with Foo::Bar and ZMOFGML". After all, just as Andy Lester once wrote, let's see people's work, let's see their new ideas or new ways to implement things. Heck, TIMTOFWTDI.
• Wireless connectivity was very poor, apparently due to ad-hoc nodes and malware on the cloud.
• Since I'm used to DebConfs, it was nice to see, though, a job fair and some circles discussing new ways to do business with Perl development.
• Around 40% of the attendees were attending their actual first YAPC. Apparently, there are a lot of newcomers to Perl conferences, but they usually don't come back that often or get a bit scared.
• Being a community conference, makes it, after all, a bit special. YAPC was mostly, as Jos Castro stated, just about people and beer.
• Organizers gave their best to make this happen successfully, you could see, feel that.
• I met some guys that after introducing us, I was confused were they were from, which was mainly because of my huge ignorance of US geography. For instance, people would tell they are from South Benton, from Omaha or from Columbus, between others. At the moment I felt it'd be tacky to ask on what states those cities are on, but now I know ;) Indiana, Nebraska and Ohio. Heh.
  
• Chicago is a beautiful city and stuffed pizza kicks ass.
• What I liked from the Perl community: They usually get things done and don't fool around too much with senseless shit.
  
• What I didn't like: If you are not a regular into the circle, it's quite difficult to feel involved or part of it. To this, add being from another country :P
• What I liked the most on talks: Ricardo SIGNES's talk about email which was awesome and the lightning talks (specially the improvised ones).
  

$ ps2pdf fa_808.ps fa_808.pdf
/usr/bin/ps2pdfwr: line 45: exec: gs: not found

$ ls /usr/bin/gs
ls: cannot access /usr/bin/gs: No such file or directory
$ wajig find-file /usr/bin/gs
ghostscript: /usr/bin/gs
$ wajig list ghostscript
ii  ghostscript                                             8.61.dfsg.1-1               The GPL Ghostscript PostScript/PDF interpret
ii  ghostscript-x                                           8.61.dfsg.1-1               The GPL Ghostscript PostScript/PDF interpret

$ wajig reinstall ghostscript
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libwine-capi libstdc++5 libopenal0a xgnokii libglut3 libcapi20-3
  libggi-target-x lib64gfortran2 libsvg1 lib64gomp1 libggi2 libgii1
  libgii1-target-x libxine1-gnome cups-pdf lib64objc2
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  akregator gs kaddressbook kaddressbook-plugins kalarm kandy kappfinder karm
  kate kcontrol kdebase-bin kdebase-data kdelibs-data kdelibs4c2a
  kdepim-kfile-plugins kdepim-kio-plugins kdepim-kresources kdepim-wizards
  kdesktop kghostview kicker kitchensync kleopatra kmplayer kmplayer-common
  kpersonalizer ksplash libarts1c2a libgnutls26 libgs8 libilmbase6 libkcal2b
  libkdepim1a libkleopatra1 libkmime2 libkonq4 libkpimidentities1 libktnef1
  libopenexr6
Suggested packages:
  kdeaddons-doc-html ntpdate ntp-simple perl-suid egroupware ffmpeg xawtv
  gnutls-bin
The following packages will be REMOVED:
  digikam kde-amusements kde-core kdeaddons kdebase kdebase-kio-plugins kdepim
  kmail kmailcvt kmplayer-plugin knights konq-plugins konqueror
  konqueror-nsplugins korn smb4k
The following NEW packages will be installed:
  gs libgnutls26 libilmbase6 libopenexr6
The following packages will be upgraded:
  akregator ghostscript kaddressbook kaddressbook-plugins kalarm kandy
  kappfinder karm kate kcontrol kdebase-bin kdebase-data kdelibs-data
  kdelibs4c2a kdepim-kfile-plugins kdepim-kio-plugins kdepim-kresources
  kdepim-wizards kdesktop kghostview kicker kitchensync kleopatra kmplayer
  kmplayer-common kpersonalizer ksplash libarts1c2a libgs8 libkcal2b
  libkdepim1a libkleopatra1 libkmime2 libkonq4 libkpimidentities1 libktnef1
36 upgraded, 4 newly installed, 16 to remove and 683 not upgraded.
Need to get 53.1MB of archives.
After this operation, 42.9MB disk space will be freed.
Do you want to continue [Y/n]? n
Abort.

$ wget http://snapshot.debian.net/archive/2008/03/02/debian/pool/main/g/ghostscript/ghostscript_8.61.dfsg.1-1_i386.deb
$ wajig install ./ghostscript_8.61.dfsg.1-1_i386.deb

$ ls /usr/bin/gs
/usr/bin/gs

• [1] http://en.wikipedia.org/wiki/List_of_Intel_chipsets


• [2] http://taviso.decsystem.org/virtsec.pdf


• [3] http://udrepper.livejournal.com/tag/virtualization

Share This

pausingAction :: IO (Either (CoroutineT IO a) a)

data CoroutineT m a = CoroutineT  unCoroutineT :: (m (Either (CoroutineT m a) a))  

instance (Monad m) => Monad (CoroutineT m) where
    return v = CoroutineT (return (Right v))
    a >>= b = CoroutineT $ do
          r <- unCoroutineT a
          case r of
            Left  paused   -> return $ Left (paused >>= b)
            Right unpaused -> unCoroutineT (b unpaused)

runCoroutineT :: Monad m => CoroutineT m () -> m (Maybe (CoroutineT m ()))
runCoroutineT a = either (Just) (const Nothing)  liftM  unCoroutineT a

pause :: Monad m => CoroutineT m ()
pause = CoroutineT (return (Left (CoroutineT (return (Right ())))))

example n = keepGoingFor n $ do
        liftIO $ putStrLn "This is the coroutine"
        forM_ [1..10] $ \i -> do
            liftIO $ putStrLn $ "Counting to "++ show i ++" while you keep calling it"
            pause
  where --keepGoing :: Monad m => CoroutineT m () -> m ()
      keepGoingFor 0 _   = putStrLn "Here I just abort the run"
      keepGoingFor n cor = do
        resume <- runCoroutineT cor
        case resume of
            Just runAgain -> keepGoingFor (n-1) runAgain
            Nothing       -> putStrLn "Finally stopped"

*CouroutineT> example 5
This is the coroutine
Counting to 1 while you keep calling it
Counting to 2 while you keep calling it
Counting to 3 while you keep calling it
Counting to 4 while you keep calling it
Counting to 5 while you keep calling it
Here I just abort the run
*CouroutineT> example 14
This is the coroutine
Counting to 1 while you keep calling it
Counting to 2 while you keep calling it
Counting to 3 while you keep calling it
Counting to 4 while you keep calling it
Counting to 5 while you keep calling it
Counting to 6 while you keep calling it
Counting to 7 while you keep calling it
Counting to 8 while you keep calling it
Counting to 9 while you keep calling it
Counting to 10 while you keep calling it
Finally stopped

pausingForM_ :: Monad m => Int -> [a] -> (a -> CoroutineT m ()) -> CoroutineT m ()
pausingForM_ period list action = pausing' 0 list
  where pausing' _ []     = return ()
        pausing' n (x:xs) = do action x
                       if n==period then pause >> pausing' 0     xs
                                    else          pausing' (n+1) xs

"Americans can always be depended upon to do the right thing—after they've tried everything else."

• How to turn a serial GPS into a data logger with 6 hours battery life . Then attach it to your bike using magnets from broken hard drives. Totally rocks!
• Previous OpenStreetMap data was collected by only one person, who took the fancy new High Speed Rail from the opposite side of the country and joined the party. This also made discussion about standardising tags for Taiwan rather easy.
• A group of people appeared wielding a number of "totally insane in every regard" Garmin GPSMAP units: it turns out they are with a civil action group that goes around mapping historical trails, abandoned railroads, aboriginal routes and mountain crosses and so on. Apparently, they did not know about OpenStreetMap: hopefully they'll join in.

• The eeePC was very popular, and very handy for going around storing tracks, as you can just chuck it in one bag. JOSM runs fine, although it could really use an interface redesign to fit in the small screen. In fact, it could really use an interface redesign to fit in the standard 1024x768 screen of my laptop.
• We could not use the tracks made with the Garmins because we did not know we had to do "Setup -> Map -> Lock On Road = Off" and it was on by default. Now we know it for next time.
• Something like a SirfStarIII really helps in a city made mainly of very tall buildings with lots of steel and glass. My Sony-based cheap gps receiver that worked ok in the Bolognese countryside was next to useless here, continously losing the fix and producing a crazy zigzagging track of doom, only useful to figure out big long straight roads.
• Geocorrelation of digital camera pictures rocks! Who needs to store waypoints when you can just take pictures with the digital camera and have them show up as waypoints in JOSM? The trick of taking a picture of the GPS time and use that to compute time offset is great. Also, we found it easier to just fire up gpscorrelate to do the geocorrelation rather than figuring out how the tools in JOSM work.

• There is a strong need for a zh_TW translation plugin of JOSM; I'll try to find out how to do it and pass on the information to who can do it.
• Road names could be written either in English or in Chinese characters. Currently English has been used for the name tag because osmarender cannot render Chinese characters. There is some planining to create an OSM mirror in Taiwan which renders twice, and allows to choose the rendering language for the map. I will try to get a planet.osm extract for Taiwan that people can use to experiment with this; thanks to people in #osm for giving me names of people to contact. I will try later after Europe wakes up from this even-earlier-than-usual sunday morning.