On 07/12/15 10:57, Muflone wrote: > Hello > > I was going to update the bluegriffon package to the version 1.8. > The package sits in my directory and wasn't moved to any repository yet. > > Now I discovered that the release 1.7.2-5 was already moved by Allan in > the staging repository [1]. > This means that I must not release the package 1.8-1 until the C++ > rebuild is completed as Allan noted. > > The updated gcc package will be directly moved in core when the rebuilt > packages will reach their repositories? > > A public announcement will follow when the rebuild is complete in order > to let me build again the bluegriffon 1.8-1 package against the new gcc? >
The C++ rebuilds should enter [testing] in a day or two (given the current rebuild rate). I do not expect them to stay in [testing] long. Allan
