build qt5 stable (changed subject from: qt5 stable: qengineio: fatal: remote error: access denied or repository not exported)

[Dominik Haumann]

On Monday 31 March 2014 17:27:33 Ben Cooksley wrote:
> On Mon, Mar 31, 2014 at 5:38 AM, Gregor Mi <codeminister at publicstatic.de> 
wrote:
> > On 30/03/14 12:41, Aleix Pol wrote:
> >> On Sun, Mar 30, 2014 at 12:02 PM, Gregor Mi
> >> 
> >> <codeminister at publicstatic.de <mailto:codeminister at publicstatic.de>> 
wrote:
> >>     On 30/03/14 11:29, Gregor Mi wrote:
> >>     > Hi,
> >>     > 
> >>     > has anyone recently build qt5 from scratch as described here [1]?
> >>     > 
> >>     > When doing
> >>     > 
> >>     > $ ./init-repository
> >>     > 
> >>     > the following error occurs:
> >>     > 
> >>     > -----------
> >>     > + git clone git://anongit.kde.org/qt/qtenginio.git
> >>     
> >>     <http://anongit.kde.org/qt/qtenginio.git> qtenginio
> >>     
> >>     > Cloning into 'qtenginio'...
> >>     > fatal: Could not read from remote repository.
> >>     > 
> >>     > Please make sure you have the correct access rights
> >>     > and the repository exists.
> >>     > git clone git://anongit.kde.org/qt/qtenginio.git
> >>     
> >>     <http://anongit.kde.org/qt/qtenginio.git> qtenginio exited with
> >>     
> >>     > status 32768 at ./init-repository line 305.
> >>     > -----------
> >>     > 
> >>     > The other repos are working fine.
> >>     > 
> >>     > Best regards
> >>     > 
> >>     > Gregor
> >>     > 
> >>     > [1] http://community.kde.org/Frameworks/Building, section QT5
> >>     
> >>     When building QT5 as described in [1] the "stable" branch of Qt is
> >>     now
> >>     5.3 (and not 5.2). Is this correct?
> >> 
> >> AFAIK, the building dependency is 5.2 and that probably is outdated, as
> >> stable is a moving target.
> >> 
> >> Either way, I'd suggest you to use stable too.
> >> 
> >> Aleix
> > 
> > Ok. Any idea about the qtenginio "Could not read from remote repository"
> > problem? Do I need special access rights? Or is it possible that the
> > qtenginio repo is offline?
> 
> This is because the upstream Qt developers have added yet another
> module to Qt, which wasn't included in our mirror of Qt.
> Our mirror has now been adjusted to include this new mirror.
> 
> This is a process which has to be done each time they add a new module.
> 
> For those wondering why, we maintain a mirror of Qt on the anongit
> network to ensure that it is always available - at least in the past
> people have had issues accessing the Gitorious repositories.

Hi Ben,

then thanks again for fixing it (again). Question though: Could this error be 
caught earlier, maybe automated?

I'm asking because it cost me (as someone who does 10+ years KDE/Qt 
development) quite some time to get this working. Other developers following 
our official building guide will run into this, too, and probably just give 
up. And that is quite bad.

Greetings,
Dominik