1 you send to wrong mailing list, meego-dev is for external development 
discussion purpose, many people here don't use osc and many people using osc in 
intel don't subscribe this mailing list, although someone from external like 
opensuse will be possible to read this email;
2 you should send to meego-commits (external) or meego-dist (internal) for 
getting answer ASAP;
3 specific to your question, I don't know if it is any workaround, but from 
point of building system, it is right thing to do; if your pkgs are not very 
'core' (many others are depending on it), then you will not see so long block 
list, if your pkg is really core, then you really should wait for those 
dependency building safety, or if your pkg was not so many dependency but other 
people trigger the some 'core' pkgs building, then you should wait for the 
result, otherwise, you used old files to make your current building successful, 
but it is risk to fail to work.
Give you a example: if I change/trigger glibc rebuild, then many pkgs will be 
re-build, because glibc is so 'core' and every pkg will use it, at this time, 
if your pkg A is 'buildrequire' B, but B is blocked to wait glibc, then your A 
will have to wait. Otherwise you're A will build with old B, which was built 
against OLD glibc, it would be very risk to run into runtime failure.


From: [email protected] [mailto:[email protected]] On 
Behalf Of Wang, Quanxian
Sent: Friday, July 02, 2010 3:00 PM
To: [email protected]
Subject: [MeeGo-dev] Help: Anyone know how to make it passed?

Hi, All
When I submit one commit, I come across the blocked list. Anyone has some 
solution. Seems the blocked list become so long. You will wait long time to 
build your packages until the previous packages finish the building.

However if the building hang there, it will stop the following package 
building. Any solution for that?

Can we change the rule to use the previous building results not the current so 
that none can be stopped by such case?

Here are some output. I am just afraid the blocked list will become longer and 
longer, at last no one can build the package. :(

Command: Osc results

  7 standard        armv5el    blocked: aaa-meego-accelerator, rpm, binutils, 
glibc, rpm-build, libtool, perl-Module-Build, perl-Test-Pod, 
perl-Test-Pod-Coverage, db4-utils, glib    c-devel, basesystem, xz, 
perl-ExtUtils-MakeMaker, perl-Archive-Tar, perl-ExtUtils-CBuilder, 
perl-ExtUtils-ParseXS, perl-Test-Simple, perl-Pod-Coverage, util-linux-ng, 
perl-ve    rsion, perl-Module-Pluggable, perl-Pod-Simple, perl-devel, 
perl-Test-Harness, perl-Compress-Zlib, perl-IO-Zlib, perl-Devel-Symdump, 
libuuid, libblkid, perl-Pod-Escapes, perl-    IO-Compress-Base, 
perl-Compress-Raw-Zlib, perl-IO-Compress-Zlib   (repository is blocked)
  8 standard        armv7el    blocked: aaa-meego-accelerator, rpm, binutils, 
glibc, rpm-build, libtool, perl-Module-Build, perl-Test-Pod, 
perl-Test-Pod-Coverage, db4-utils, glib    c-devel, basesystem, xz, 
perl-ExtUtils-MakeMaker, perl-Archive-Tar, perl-ExtUtils-CBuilder, 
perl-ExtUtils-ParseXS, perl-Test-Simple, perl-Pod-Coverage, util-linux-ng, 
perl-ve    rsion, perl-Module-Pluggable, perl-Pod-Simple, perl-devel, 
perl-Test-Harness, perl-Compress-Zlib, perl-IO-Zlib, perl-Devel-Symdump, 
libuuid, libblkid, perl-Pod-Escapes, perl-    IO-Compress-Base, 
perl-Compress-Raw-Zlib, perl-IO-Compress-Zlib   (repository is blocked)
  9 standard        i586       blocked: rpm, binutils, gcc, glibc, rpm-build, 
libtool, perl-Module-Build, perl-Test-Pod, perl-Test-Pod-Coverage, db4-utils, 
glibc-devel, cpp, base    system, xz, perl-ExtUtils-MakeMaker, 
perl-Archive-Tar, perl-ExtUtils-CBuilder, perl-ExtUtils-ParseXS, 
perl-Test-Simple, perl-Pod-Coverage, coreutils-libs, util-linux-ng, gmp,     
mpfr, ppl, perl-version, perl-Module-Pluggable, perl-Pod-Simple, perl-devel, 
perl-Test-Harness, perl-Compress-Zlib, perl-IO-Zlib, perl-Devel-Symdump, 
libuuid, libblkid, perl    -Pod-Escapes, perl-IO-Compress-Base, 
perl-Compress-Raw-Zlib, perl-IO-Compress-Zlib   (repository is blocked)


Regards

Quanxian Wang

_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to