Re: [Cooker] Re: [Maintainers] Cooker and AMD64

[Gwenole Beauchesne]

Hi,

At this moment I've got over 250 cooker packages with the same 
version-release number as in i586 cooker, but that aren't in the amd64 
tree.
Wrong. They are but not synchronized yet to the mirror until the next 
beta. Again, you can't have more packages than are available now since 
the remaining 85 ones (down from 300 or so) need to be manually fixed 
first. And by package, I mean SRPM. Counting RPMs as you appear to do, 
there are approx. 379 that changed since beta 2.

Can these packages be of any use? I think it would be more effective 
if MDK staff would spend their time testing the product instead of 
building it (manually).
You are still wrong. I already explained to you that packages that are 
manually built are those that need to be fixed first. Others are 
auto-rebuilt, of course.

In the end, most packages won't need to be changed, and for the 
packages that are changed (after testing as revealed a fault), those 
changes will end up in the SRPMS.
That's what is happening...

Bye,
Gwenole.

[Cooker] Re: [Maintainers] Cooker and AMD64

[Stefan van der Eijk]

Frederic,

I've got access to an amd64 machine and have been rebuilding cooker main 
and contrib packages on that host with slbd. I've been uploading the 
contrib packages, but not the main packages due to specific request from 
Gwenole. At this moment I've got over 250 cooker packages with the same 
version-release number as in i586 cooker, but that aren't in the amd64 
tree. For alpha and sparc these packages would be uploaded by my upload bot.

Can these packages be of any use? I think it would be more effective if 
MDK staff would spend their time testing the product instead of building 
it (manually). In the end, most packages won't need to be changed, and 
for the packages that are changed (after testing as revealed a fault), 
those changes will end up in the SRPMS.

and, I guess most contributors are waiting for cooker/main to open up 
again. This may speed up this process (without sacrificing quality).

just trying to help out...

Stefan

Frederic Lepied wrote:

Cooker is still frozen and will remain frozen until the 9.2 AMD64
version is finished. Only src.rpm modified for the AMD64 port are
allowed to be uploaded in main. We need to do that because we don't
want to fork the 9.2. To be able to use these src.rpm for 9.2 security
updates on the ia32 architecture, recompile your packages on ia32 and
test them to see if there is a regression. If all is ok, upload the
resulting binaries to cooker. If there is a problem, create a new
src.rpm with a new release, upload them to cooker and send a mail to
Gwenole to warn him about the problem.
 




smime.p7s
Description: S/MIME Cryptographic Signature