Builds for gwibber in Ubuntu Precise

175 of 206 results
[FULLYBUILT] powerpc build of gwibber 3.4.2-0ubuntu2.4 in ubuntu precise PROPOSED
Build started on sulfur (powerpc) and finished taking 10 minutes — see the log
[FULLYBUILT] powerpc build of gwibber 3.4.2-0ubuntu2.4 in ubuntu precise PROPOSED
Build started on sulfur (powerpc) and finished taking 10 minutes — see the log
[FULLYBUILT] i386 build of gwibber 3.4.2-0ubuntu2.4 in ubuntu precise PROPOSED
Build started on kissel (i386/amd64) and finished taking 7 minutes — see the log
[FULLYBUILT] i386 build of gwibber 3.4.2-0ubuntu2.4 in ubuntu precise PROPOSED
Build started on kissel (i386/amd64) and finished taking 7 minutes — see the log
[FULLYBUILT] armhf build of gwibber 3.4.2-0ubuntu2.4 in ubuntu precise PROPOSED
Build started on kishi21 (highbank) and finished taking 11 minutes — see the log
[FULLYBUILT] armhf build of gwibber 3.4.2-0ubuntu2.4 in ubuntu precise PROPOSED
Build started on kishi21 (highbank) and finished taking 11 minutes — see the log
[FULLYBUILT] armel build of gwibber 3.4.2-0ubuntu2.4 in ubuntu precise PROPOSED
Build started on kishi20 (highbank) and finished taking 11 minutes — see the log
[FULLYBUILT] armel build of gwibber 3.4.2-0ubuntu2.4 in ubuntu precise PROPOSED
Build started on kishi20 (highbank) and finished taking 11 minutes — see the log
[FULLYBUILT] amd64 build of gwibber 3.4.2-0ubuntu2.4 in ubuntu precise PROPOSED
Build started on lamiak (i386/amd64) and finished taking 7 minutes — see the log
[FULLYBUILT] amd64 build of gwibber 3.4.2-0ubuntu2.4 in ubuntu precise PROPOSED
Build started on lamiak (i386/amd64) and finished taking 7 minutes — see the log
[FULLYBUILT] powerpc build of gwibber 3.4.2-0ubuntu2.3 in ubuntu precise PROPOSED
Build started on adare (powerpc) and finished taking 13 minutes — see the log
[FULLYBUILT] powerpc build of gwibber 3.4.2-0ubuntu2.3 in ubuntu precise PROPOSED
Build started on adare (powerpc) and finished taking 13 minutes — see the log
[FULLYBUILT] i386 build of gwibber 3.4.2-0ubuntu2.3 in ubuntu precise PROPOSED
Build started on aatxe (i386/amd64) and finished taking 8 minutes — see the log
[FULLYBUILT] i386 build of gwibber 3.4.2-0ubuntu2.3 in ubuntu precise PROPOSED
Build started on aatxe (i386/amd64) and finished taking 8 minutes — see the log
[FULLYBUILT] armhf build of gwibber 3.4.2-0ubuntu2.3 in ubuntu precise PROPOSED
Build started on centaur (panda ES) and finished taking 18 minutes — see the log
[FULLYBUILT] armhf build of gwibber 3.4.2-0ubuntu2.3 in ubuntu precise PROPOSED
Build started on centaur (panda ES) and finished taking 18 minutes — see the log
[FULLYBUILT] armel build of gwibber 3.4.2-0ubuntu2.3 in ubuntu precise PROPOSED
Build started on ain (armhf - panda) and finished taking 17 minutes — see the log
[FULLYBUILT] armel build of gwibber 3.4.2-0ubuntu2.3 in ubuntu precise PROPOSED
Build started on ain (armhf - panda) and finished taking 17 minutes — see the log
[FULLYBUILT] amd64 build of gwibber 3.4.2-0ubuntu2.3 in ubuntu precise PROPOSED
Build started on roseapple (i386/amd64) and finished taking 3 minutes — see the log
[FULLYBUILT] amd64 build of gwibber 3.4.2-0ubuntu2.3 in ubuntu precise PROPOSED
Build started on roseapple (i386/amd64) and finished taking 3 minutes — see the log
[FULLYBUILT] powerpc build of gwibber 3.4.2-0ubuntu2.2 in ubuntu precise PROPOSED
Build started on sagari (powerpc) and finished taking 6 minutes — see the log
[FULLYBUILT] powerpc build of gwibber 3.4.2-0ubuntu2.2 in ubuntu precise PROPOSED
Build started on sagari (powerpc) and finished taking 6 minutes — see the log
[FULLYBUILT] i386 build of gwibber 3.4.2-0ubuntu2.2 in ubuntu precise PROPOSED
Build started on lamiak (i386/amd64) and finished taking 8 minutes — see the log
[FULLYBUILT] i386 build of gwibber 3.4.2-0ubuntu2.2 in ubuntu precise PROPOSED
Build started on lamiak (i386/amd64) and finished taking 8 minutes — see the log
[FULLYBUILT] armhf build of gwibber 3.4.2-0ubuntu2.2 in ubuntu precise PROPOSED
Build started on shedir (armhf panda) and finished taking 18 minutes — see the log
[FULLYBUILT] armhf build of gwibber 3.4.2-0ubuntu2.2 in ubuntu precise PROPOSED
Build started on shedir (armhf panda) and finished taking 18 minutes — see the log
[FULLYBUILT] armel build of gwibber 3.4.2-0ubuntu2.2 in ubuntu precise PROPOSED
Build started on ain (armhf - panda) and finished taking 18 minutes — see the log
[FULLYBUILT] armel build of gwibber 3.4.2-0ubuntu2.2 in ubuntu precise PROPOSED
Build started on ain (armhf - panda) and finished taking 18 minutes — see the log
[FULLYBUILT] amd64 build of gwibber 3.4.2-0ubuntu2.2 in ubuntu precise PROPOSED
Build started on roseapple (i386/amd64) and finished taking 4 minutes — see the log
[FULLYBUILT] amd64 build of gwibber 3.4.2-0ubuntu2.2 in ubuntu precise PROPOSED
Build started on roseapple (i386/amd64) and finished taking 4 minutes — see the log
[FULLYBUILT] powerpc build of gwibber 3.4.2-0ubuntu2.1 in ubuntu precise PROPOSED
Build started on adare (powerpc) and finished taking 12 minutes — see the log
[FULLYBUILT] powerpc build of gwibber 3.4.2-0ubuntu2.1 in ubuntu precise PROPOSED
Build started on adare (powerpc) and finished taking 12 minutes — see the log
[FULLYBUILT] i386 build of gwibber 3.4.2-0ubuntu2.1 in ubuntu precise PROPOSED
Build started on roseapple (i386/amd64) and finished taking 4 minutes — see the log
[FULLYBUILT] i386 build of gwibber 3.4.2-0ubuntu2.1 in ubuntu precise PROPOSED
Build started on roseapple (i386/amd64) and finished taking 4 minutes — see the log
[FULLYBUILT] armhf build of gwibber 3.4.2-0ubuntu2.1 in ubuntu precise PROPOSED
Build started on diphda and finished taking 16 minutes — see the log
[FULLYBUILT] armhf build of gwibber 3.4.2-0ubuntu2.1 in ubuntu precise PROPOSED
Build started on diphda and finished taking 16 minutes — see the log
[FULLYBUILT] armel build of gwibber 3.4.2-0ubuntu2.1 in ubuntu precise PROPOSED
Build started on meissa (armhf panda) and finished taking 16 minutes — see the log
[FULLYBUILT] armel build of gwibber 3.4.2-0ubuntu2.1 in ubuntu precise PROPOSED
Build started on meissa (armhf panda) and finished taking 16 minutes — see the log
[FULLYBUILT] amd64 build of gwibber 3.4.2-0ubuntu2.1 in ubuntu precise PROPOSED
Build started on allspice (i386/amd64) and finished taking 3 minutes — see the log
[FULLYBUILT] amd64 build of gwibber 3.4.2-0ubuntu2.1 in ubuntu precise PROPOSED
Build started on allspice (i386/amd64) and finished taking 3 minutes — see the log
[FULLYBUILT] powerpc build of gwibber 3.4.2-0ubuntu2 in ubuntu precise PROPOSED
Build started on adare (powerpc) and finished taking 9 minutes — see the log
[FULLYBUILT] powerpc build of gwibber 3.4.2-0ubuntu2 in ubuntu precise PROPOSED
Build started on adare (powerpc) and finished taking 9 minutes — see the log
[FULLYBUILT] i386 build of gwibber 3.4.2-0ubuntu2 in ubuntu precise PROPOSED
Build started on aatxe (i386/amd64) and finished taking 7 minutes — see the log
[FULLYBUILT] i386 build of gwibber 3.4.2-0ubuntu2 in ubuntu precise PROPOSED
Build started on aatxe (i386/amd64) and finished taking 7 minutes — see the log
[FULLYBUILT] armhf build of gwibber 3.4.2-0ubuntu2 in ubuntu precise PROPOSED
Build started on ain (armhf - panda) and finished taking 15 minutes — see the log
[FULLYBUILT] armhf build of gwibber 3.4.2-0ubuntu2 in ubuntu precise PROPOSED
Build started on ain (armhf - panda) and finished taking 15 minutes — see the log
[FULLYBUILT] armel build of gwibber 3.4.2-0ubuntu2 in ubuntu precise PROPOSED
Build started on ishigaq (arm panda) and finished taking 15 minutes — see the log
[FULLYBUILT] armel build of gwibber 3.4.2-0ubuntu2 in ubuntu precise PROPOSED
Build started on ishigaq (arm panda) and finished taking 15 minutes — see the log
[FULLYBUILT] amd64 build of gwibber 3.4.2-0ubuntu2 in ubuntu precise PROPOSED
Build started on batsu (i386/amd64) and finished taking 6 minutes — see the log
[FULLYBUILT] amd64 build of gwibber 3.4.2-0ubuntu2 in ubuntu precise PROPOSED
Build started on batsu (i386/amd64) and finished taking 6 minutes — see the log
[FULLYBUILT] powerpc build of gwibber 3.4.2-0ubuntu1 in ubuntu precise PROPOSED
Build started on ross (powerpc) and finished taking 12 minutes — see the log
[FULLYBUILT] powerpc build of gwibber 3.4.2-0ubuntu1 in ubuntu precise PROPOSED
Build started on ross (powerpc) and finished taking 12 minutes — see the log
[FULLYBUILT] i386 build of gwibber 3.4.2-0ubuntu1 in ubuntu precise PROPOSED
Build started on akateko (i386/amd64) and finished taking 7 minutes — see the log
[FULLYBUILT] i386 build of gwibber 3.4.2-0ubuntu1 in ubuntu precise PROPOSED
Build started on akateko (i386/amd64) and finished taking 7 minutes — see the log
[FULLYBUILT] armhf build of gwibber 3.4.2-0ubuntu1 in ubuntu precise PROPOSED
Build started on sigbin (arm panda) and finished taking 15 minutes — see the log
[FULLYBUILT] armhf build of gwibber 3.4.2-0ubuntu1 in ubuntu precise PROPOSED
Build started on sigbin (arm panda) and finished taking 15 minutes — see the log
[FULLYBUILT] armel build of gwibber 3.4.2-0ubuntu1 in ubuntu precise PROPOSED
Build started on meissa (armhf panda) and finished taking 15 minutes — see the log
[FULLYBUILT] armel build of gwibber 3.4.2-0ubuntu1 in ubuntu precise PROPOSED
Build started on meissa (armhf panda) and finished taking 15 minutes — see the log
[FULLYBUILT] amd64 build of gwibber 3.4.2-0ubuntu1 in ubuntu precise PROPOSED
Build started on komainu (i386/amd64) and finished taking 7 minutes — see the log
[FULLYBUILT] amd64 build of gwibber 3.4.2-0ubuntu1 in ubuntu precise PROPOSED
Build started on komainu (i386/amd64) and finished taking 7 minutes — see the log
[FULLYBUILT] powerpc build of gwibber 3.4.1-0ubuntu1.1 in ubuntu precise PROPOSED
Build started on sulfur (powerpc) and finished taking 8 minutes — see the log
[FULLYBUILT] i386 build of gwibber 3.4.1-0ubuntu1.1 in ubuntu precise PROPOSED
Build started on vernadsky (i386) and finished taking 7 minutes — see the log
[FULLYBUILT] armhf build of gwibber 3.4.1-0ubuntu1.1 in ubuntu precise PROPOSED
Build started on nikusui (arm panda) and finished taking 15 minutes — see the log
[FULLYBUILT] armel build of gwibber 3.4.1-0ubuntu1.1 in ubuntu precise PROPOSED
Build started on meissa (armhf panda) and finished taking 14 minutes — see the log
[FULLYBUILT] amd64 build of gwibber 3.4.1-0ubuntu1.1 in ubuntu precise PROPOSED
Build started on batsu (i386/amd64) and finished taking 6 minutes — see the log
[FULLYBUILT] powerpc build of gwibber 3.4.1-0ubuntu1 in ubuntu precise PROPOSED
Build started on sulfur (powerpc) and finished taking 9 minutes — see the log
[FULLYBUILT] powerpc build of gwibber 3.4.1-0ubuntu1 in ubuntu precise PROPOSED
Build started on sulfur (powerpc) and finished taking 9 minutes — see the log
[FULLYBUILT] i386 build of gwibber 3.4.1-0ubuntu1 in ubuntu precise PROPOSED
Build started on vernadsky (i386) and finished taking 7 minutes — see the log
[FULLYBUILT] i386 build of gwibber 3.4.1-0ubuntu1 in ubuntu precise PROPOSED
Build started on vernadsky (i386) and finished taking 7 minutes — see the log
[FULLYBUILT] armhf build of gwibber 3.4.1-0ubuntu1 in ubuntu precise PROPOSED
Build started on shedir (armhf panda) and finished taking 15 minutes — see the log
[FULLYBUILT] armhf build of gwibber 3.4.1-0ubuntu1 in ubuntu precise PROPOSED
Build started on shedir (armhf panda) and finished taking 15 minutes — see the log
[FULLYBUILT] armel build of gwibber 3.4.1-0ubuntu1 in ubuntu precise PROPOSED
Build started on musimon (arm panda) and finished taking 15 minutes — see the log
[FULLYBUILT] armel build of gwibber 3.4.1-0ubuntu1 in ubuntu precise PROPOSED
Build started on musimon (arm panda) and finished taking 15 minutes — see the log
[FULLYBUILT] amd64 build of gwibber 3.4.1-0ubuntu1 in ubuntu precise PROPOSED
Build started on allspice (i386/amd64) and finished taking 3 minutes — see the log
[FULLYBUILT] amd64 build of gwibber 3.4.1-0ubuntu1 in ubuntu precise PROPOSED
Build started on allspice (i386/amd64) and finished taking 3 minutes — see the log
175 of 206 results