Bug#760849: transition: glew
Control: tags -1 confirmed
On 09/11/15 10:17, Matteo F. Vescovi wrote:
> Dear Release Team,
>
> FYI, the 1.13.0 stable version has been released meanwhile by upstream
> on October 15, 2015.
>
> On October 25, 2015 a first testing-purpose package has been uploaded
> to experimental and with the huge help (as usual) from Luca Falavigna
> (dktrkranz) and his Deb-O-Matic infrastructure (on amd64 architecture)
> it was tested building with all its 63 reverse dependencies again.
>
> Most conditions for the package building haven't changed in this period.
> A couple of packages are become new reverse dependencies of GLEW.
>
> Almost all the r-deps are doing file on test rebuilds and those
> failing are not caused by GLEW.
>
> Extensive list of the packages and their state of rebuilding following:
>
> * avogadro_1.0.3-13 => OK
> * ball_1.4.2+20140406-1.1 => FTBFS (no glew-related)
> * bino_1.6.0-1 => FTBFS (no glew-related)
> * blender_2.74+dfsg0-4 => OK
> * bzflag_2.4.2+ds1-5 => OK
> * calligra_1:2.8.5+dfsg-1.2 => FTBFS (no glew-related)
> * cegui-mk2_0.7.6-3.3 => FTBFS (no glew-related)
> * colobot_0.1.6-1 => OK
> * darkradiant_2.0.2-2 => OK
> * dolphin-emu_4.0.2+dfsg2-1 => OK
> * enblend-enfuse_4.1.4+dfsg-2 => OK
> * freeorion_0.4.5-1 => OK
> * frogatto_1.3.1+dfsg-2 => OK
> * fs-uae_2.6.1+dfsg-2 => OK
> * gambas3_3.5.4-2 => FTBFS (no glew-related)
> * gem_1:0.93.3-9 => OK
> * gemrb_0.8.2-1 => OK
> * gimp-plugin-registry_7.20140602 => OK
> * gource_0.43-1 => OK
> * hedgewars_0.9.21.1-5 => OK
> * hugin_2015.0.0~rc3+dfsg-1 => FTBFS (no glew-related)
> * imagevis3d_3.1.0-4 => OK
> * info-beamer_1.0~pre3-1 => OK
> * k3d_0.8.0.3-8 => FTBFS (no glew-related)
> * kodi_15.2~rc3+dfsg1-1 => OK
> * libgltf_0.0.2-4 => OK
> * libreoffice_1:5.0.3~rc1-2 => CHECK
> * lightspark_0.7.2+git20150512-2 => OK
> * linphone_3.6.1-2.4 => OK
> * logstalgia_1.0.6-1 => OK
> * megaglest_3.11.1-2 => OK
> * mesa-demos_8.2.0-1 => FTBFS (no glew-related)
> * meshlab_1.3.2+dfsg1-2 => OK
> * mupen64plus-video-z64_2.0.0+13+g72af4f0-2 => OK
> * mygui_3.2.2-4 => OK
> * openclonk_6.1-1 => OK
> * opencsg_1.4.0-1 => OK
> * openctm_1.0.3+dfsg1-1.1 => OK
> * openimageio_1.5.20~dfsg0-1 => FTBFS (no glew-related)
> * openmsx_0.12.0-1 => OK
> * openscad_2015.03-1+dfsg-2 => FTBFS (no glew-related)
> * performous_1.0+git150721-1 => OK
> * phlipple_0.8.5-2 => OK
> * projectm_2.1.0+dfsg-3 => OK
> * pymol_1.7.2.1-2.1 => OK
> * quesoglc_0.7.2-5 => OK
> * qutemol_0.4.1~cvs20081111-3.2 => OK
> * rbdoom3bfg_1.0.3+repack1+git20150806-1 => OK
> * renpy_6.17.6-1.1 => OK
> * rlvm_0.14-1 => OK
> * root-system_5.34.19+dfsg-1.2 => FTBFS (no glew-related)
> * rss-glx_0.9.1-6 => OK
> * scorched3d_43.3.d+dfsg-1.1 => OK
> * sofa-framework_1.0~beta4-10 => OK
> * soya_0.15~rc1-10 => OK
> * spring_100.0+dfsg-2 => OK
> * supertux_0.3.5a-2 => OK
> * trigger-rally_0.6.1-0.1 => OK
> * tulip_4.7.0dfsg-2 => FTBFS
> * utopia-documents_2.4.4-2.1 => FTBFS (no glew-related)
> * warzone2100_3.1.1-2 => OK
> * widelands_1:18-3 => OK
> * witty_3.3.4+dfsg-5 => FTBFS (no glew-related)
>
> What am I supposed to do now?
> Is it a good time for uploading it to unstable?
Yes, you can go ahead.
BTW please make sure those packages that fail to build have RC bugs reported
against them.
Cheers,
Emilio
Reply to: