Re: the state of daily-builds

2010-04-01 Thread Andreas Barth
* Frans Pop (elen...@planet.nl) [100331 21:38]:
 On Wednesday 31 March 2010, Andreas Barth wrote:
  The svn update inside the chroot fails now - nothing to worry, but
  would be nice if that wouldn't happen.
 
 Looks like you currently call 'daily-build build' which also does an 
 update. How about adding a 'build-only' option that skips the update?

Sounds good to me. If the build-only could also be more verbose (i.e.
logging during build) I'd appreciate that even more.


  If there are any more questions, or things to change, please don't
  hesitate to contact me.
 
 Which arches have been set up according to this system and which (existing 
 ones) are still to be done?

mips, mipsel and ia64 are setup this way (but the mipsel buildd is
down since 2 days for hardware issues).

As of now, hppa and armel (besides kfreebsd*) can't be done this way,
because they have no lvm chroots yet. hppa should be available soon,
armel probably only after new hardware exists.



 There have been no amd64 builds the last few days. Any idea why?

Yes. They used keys w/o a forced command.

 Can you give an estimate when daily builds for hppa, mips and powerpc could 
 be available again?

mips is as of now (I enabled that yesterday before sending out the
mail, but the status page is updated only very seldom). hppa waits on
DSA right now. powerpc sometimes this week. (I sent the mail after I
reached a state where I thought now this really works, and just needs
to be rolled out to the buildds - what stays open is just going
through the list of arches not building now, and adding them if
possible.)


 And a last question for both you and the D-I team.
 
 Should we now set up all arches this way, or do people want to keep their 
 existing builds? I would be happy to have the s390 builds (which I 
 currently run) done on a buildd.

I don't mind. It doesn't take too much effort to set it up, once all
the preconditions are in place. And it's just yet another thing
built.



Andi


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100401060012.go27...@mails.so.argh.org



Re: the state of daily-builds

2010-04-01 Thread Christian PERRIER
Quoting Frans Pop (elen...@planet.nl):

 And a last question for both you and the D-I team.
 
 Should we now set up all arches this way, or do people want to keep their 
 existing builds? I would be happy to have the s390 builds (which I 
 currently run) done on a buildd.


I think that the more we can get rid of SPOFs, the better it is. So,
progressively moving all daily builds to Andi's setup *and* arrange to
have the logs posted in the mailing list is the safest way to
guarantee that build failures won't be ignored.

This mail also to confirm that I still consider myself as part of the
D-I team even though my apparent work in there is low nowadays...




signature.asc
Description: Digital signature


Re: the state of daily-builds

2010-04-01 Thread Frans Pop
On Thursday 01 April 2010, Andreas Barth wrote:
 * Frans Pop (elen...@planet.nl) [100331 21:38]:
  On Wednesday 31 March 2010, Andreas Barth wrote:
   The svn update inside the chroot fails now - nothing to worry, but
   would be nice if that wouldn't happen.
 
  Looks like you currently call 'daily-build build' which also does an
  update. How about adding a 'build-only' option that skips the update?

 Sounds good to me.

I've added the 'build-only' target.

 If the build-only could also be more verbose (i.e. logging during build)
 I'd appreciate that even more. 

Would it be OK if you have to set 'LOG_TO_STDOUT=1' for that in the 
environment? If it is, I have a patch (not yet committed) that does that.

The patch is a bit of a hack due to the use of the pipefail option (needed 
in order not to lose the exit code from make in the pipe to tee), which 
requires bash. But it's the simplest way I could make it work. The main 
changes are included below in case anyone sees a more elegant solution.

  There have been no amd64 builds the last few days. Any idea why?

 Yes. They used keys w/o a forced command.

Ah, OK. It would have been nice if disabling that could have waited until 
after the buildd was converted. Please give re-enabling amd64 priority 
over other arches.

 hppa waits on DSA right now. powerpc sometimes this week.

Great. Please let us know when builds are activated so we can update the 
D-I web page.

  Should we now set up all arches this way, or do people want to keep
  their existing builds? I would be happy to have the s390 builds (which
  I currently run) done on a buildd.

 I don't mind. It doesn't take too much effort to set it up, once all
 the preconditions are in place. And it's just yet another thing
 built.

OK. I guess we'll get back to you on that. I'd like to hear what Joey 
thinks of that as he currently runs two arches, including i386.

BTW, what contact address should we use for these builds? I.e, who (or 
better: what team) will be maintaining them?

Thanks again,
FJP


+do_build () {
+   local t=$1
+   local err=0
+
+   # Commands in these two branches should be the same.
+   if [ $LOG_TO_STDOUT = 1 ]; then
+   set -o pipefail
+   (
+   header BUILDING IMAGE FOR $t
+   $ROOTCMD $ROOTCMDOPTS make $t 21
+   ) | tee -a dest/$t.log || err=$?
+   set +o pipefail
+   else
+   (
+   header BUILDING IMAGE FOR $t
+   $ROOTCMD $ROOTCMDOPTS make $t 21
+   )  dest/$t.log || err=$?
+   fi
+
+   return $err
+}
[...]
for t in $TARGETS; do
-   header BUILDING IMAGE FOR $t  dest/$t.log
-   if $ROOTCMD $ROOTCMDOPTS make $t  dest/$t.log 21; then
+   if do_build $t; then
overview $t success
else


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201004011508.11727.elen...@planet.nl



Re: the state of daily-builds

2010-04-01 Thread Andreas Barth
* Frans Pop (elen...@planet.nl) [100401 15:08]:
 On Thursday 01 April 2010, Andreas Barth wrote:

  If the build-only could also be more verbose (i.e. logging during build)
  I'd appreciate that even more. 
 
 Would it be OK if you have to set 'LOG_TO_STDOUT=1' for that in the 
 environment? If it is, I have a patch (not yet committed) that does that.

Anything that could be automated, so yes of course. I'll just add that
to my scripts already now, it shouldn't hurt.


 The patch is a bit of a hack due to the use of the pipefail option (needed 
 in order not to lose the exit code from make in the pipe to tee), which 
 requires bash. But it's the simplest way I could make it work. The main 
 changes are included below in case anyone sees a more elegant solution.
 
   There have been no amd64 builds the last few days. Any idea why?
 
  Yes. They used keys w/o a forced command.
 
 Ah, OK. It would have been nice if disabling that could have waited until 
 after the buildd was converted. Please give re-enabling amd64 priority 
 over other arches.

I can add the amd64 one tonight.


  hppa waits on DSA right now. powerpc sometimes this week.
 
 Great. Please let us know when builds are activated so we can update the 
 D-I web page.

I hope I don't forget to inform you - I'm keen on gettting it done
because we'll get experimental at the same time.


   Should we now set up all arches this way, or do people want to keep
   their existing builds? I would be happy to have the s390 builds (which
   I currently run) done on a buildd.
 
  I don't mind. It doesn't take too much effort to set it up, once all
  the preconditions are in place. And it's just yet another thing
  built.
 
 OK. I guess we'll get back to you on that. I'd like to hear what Joey 
 thinks of that as he currently runs two arches, including i386.
 
 BTW, what contact address should we use for these builds? I.e, who (or 
 better: what team) will be maintaining them?


We didn't finally discuss it yet, but I would like if we could just
use $a...@buildd.d.o like for it. As of today, please continue to keep
me in Cc for any requests or issues, until we have successfully
transitioned to all. (As this is done by the buildd user, any buildd
admin could fix all by himself.)



Andi


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100401135256.gq27...@mails.so.argh.org



Re: the state of daily-builds

2010-04-01 Thread Frans Pop
On Thursday 01 April 2010, Andreas Barth wrote:
 * Frans Pop (elen...@planet.nl) [100401 15:08]:
  On Thursday 01 April 2010, Andreas Barth wrote:
   If the build-only could also be more verbose (i.e. logging during
   build) I'd appreciate that even more.
 
  Would it be OK if you have to set 'LOG_TO_STDOUT=1' for that in the
  environment? If it is, I have a patch (not yet committed) that does
  that.

 Anything that could be automated, so yes of course. I'll just add that
 to my scripts already now, it shouldn't hurt.

OK. Committed. It can always be improved later.

 I can add the amd64 one tonight.

That would be excellent.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201004011621.32906.elen...@planet.nl



Bug#576206: debian-installer: [ppc] does not work with serial console

2010-04-01 Thread Michal Suchanek hramr...@centrum.cz
Package: debian-installer
Severity: normal


qemu-system-ppc -m 1024 -net nic -net
tap,ifname=tap0,script=no,downscript=nomg -cdrom
debian-504-powerpc-netinst.iso  -boot d -nographic

does not seem to do anything.

Without -nographic a prompt on yellow screen appears where you can type
something to boot an installer.


-- System Information:
Debian Release: 5.0.4
  APT prefers stable
  APT policy: (900, 'stable'), (700, 'testing'), (500, 'unstable'), (110, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.34-rc1-atom64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20100401150449.12524.71052.report...@ipx7a-ion.ruk.cuni.cz



Processed: Re: Bug#576206: debian-installer: [ppc] does not work with serial console

2010-04-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tag 576206 moreinfo
Bug #576206 [debian-installer] debian-installer: [ppc] does not work with 
serial console
Added tag(s) moreinfo.
 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.127013420830230.transcr...@bugs.debian.org



Bug#576206: debian-installer: [ppc] does not work with serial console

2010-04-01 Thread Michal Suchanek


On 04/01/2010 05:03 PM, Frans Pop wrote:

tag 576206 moreinfo
thanks

On Thursday 01 April 2010, Michal Suchanekhramr...@centrum.cz  wrote:
   

qemu-system-ppc -m 1024 -net nic -net
tap,ifname=tap0,script=no,downscript=nomg -cdrom
debian-504-powerpc-netinst.iso  -boot d -nographic
 


Sorry, part of the commandline got lost somehow:

qemu-system-ppc -m 1024 -net nic -net 
tap,ifname=tap0,script=no,downscript=no ppc.img -cdrom 
debian-504-powerpc-netinst.iso -boot d -nographic

does not seem to do anything.

Without -nographic a prompt on yellow screen appears where you can type
something to boot an installer.
 

I think this is an error in how you're trying to boot the installer or your
qemu invocation rather than a bug.
I don't really know anything about powerpc myself, nor how to use qemu for
powerpc, so I suggest you ask on the debian-powerpc list for help.
   
Changing the -boot d to -boot c gives access to the installed system 
with full serial support from the quik bootloader so I don't think this 
is the case.

The installer does have serial console support and I'm not aware of any
issues with that on real powerpc hardware.

   


Perhaps on hardware different from the one qemu emulates?

Thanks

Michal



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4bb4c5ee.9000...@ruk.cuni.cz



Bug#576206: debian-installer: [ppc] does not work with serial console

2010-04-01 Thread Frans Pop
tag 576206 moreinfo
thanks

On Thursday 01 April 2010, Michal Suchanek hramr...@centrum.cz wrote:
 qemu-system-ppc -m 1024 -net nic -net
 tap,ifname=tap0,script=no,downscript=nomg -cdrom
 debian-504-powerpc-netinst.iso  -boot d -nographic

 does not seem to do anything.

 Without -nographic a prompt on yellow screen appears where you can type
 something to boot an installer.

I think this is an error in how you're trying to boot the installer or your 
qemu invocation rather than a bug.
I don't really know anything about powerpc myself, nor how to use qemu for 
powerpc, so I suggest you ask on the debian-powerpc list for help.

The installer does have serial console support and I'm not aware of any 
issues with that on real powerpc hardware.

Cheers,
FJP



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201004011703.23940.elen...@planet.nl



Bug#576206: debian-installer: [ppc] does not work with serial console

2010-04-01 Thread Frans Pop
On Thursday 01 April 2010, Michal Suchanek wrote:
 Changing the -boot d to -boot c gives access to the installed system
 with full serial support from the quik bootloader so I don't think this
 is the case.

Can you provide the boot log for the installer somehow?



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201004011803.32293.elen...@planet.nl



Bug#576206: debian-installer: [ppc] does not work with serial console

2010-04-01 Thread Michal Suchanek


On 04/01/2010 06:03 PM, Frans Pop wrote:

On Thursday 01 April 2010, Michal Suchanek wrote:
   

Changing the -boot d to -boot c gives access to the installed system
with full serial support from the quik bootloader so I don't think this
is the case.
 

Can you provide the boot log for the installer somehow?
   


I can provide a boot log of the installed system or that of an installer 
running with graphics or the installation report with graphics (I think 
the installer saves some such thing somewhere).


I cannot run the installer without graphics. It could be that the 
installer is actually running but does not print anything on the serial 
port but I doubt that is the case because with graphics I have to type 
the name of the image to boot.


Thanks

Michal



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4bb4d5f4.8060...@ruk.cuni.cz



Re: the state of daily-builds

2010-04-01 Thread Joey Hess
Frans Pop wrote:
 OK. I guess we'll get back to you on that. I'd like to hear what Joey 
 thinks of that as he currently runs two arches, including i386.

I would like to get rid of the dedicated machine I have running for
the armel builds. Don't really care about the i386 build overhead, but
also have no need to continue running them.

-- 
see shy jo


signature.asc
Description: Digital signature


Bug#576206: debian-installer: [ppc] does not work with serial console

2010-04-01 Thread Frans Pop
On Thursday 01 April 2010, Michal Suchanek wrote:
 I cannot run the installer without graphics. It could be that the
 installer is actually running but does not print anything on the serial
 port but I doubt that is the case because with graphics I have to type
 the name of the image to boot.

Right, and that suggests to me that it's not an *installer* issue, but at 
most a bootloader configuration problem for the CDs.

As I've said before, I (and most others on the Installer team) have zero 
knowledge of powerpc. Please try to find out what's wrong or needed on the 
d-powerpc list where all the port experts hang out. If a needed change is 
identified we'll be happy to help get it implemented.



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201004011930.59984.elen...@planet.nl



Re: [buildd-tools-devel] the state of daily-builds

2010-04-01 Thread Andreas Barth
* Joey Hess (jo...@debian.org) [100401 19:55]:
 Frans Pop wrote:
  OK. I guess we'll get back to you on that. I'd like to hear what Joey 
  thinks of that as he currently runs two arches, including i386.
 
 I would like to get rid of the dedicated machine I have running for
 the armel builds. Don't really care about the i386 build overhead, but
 also have no need to continue running them.

As of now, we can't move the armel builds yet (as we are waiting for
the new debian machines to be setup). I hope to not forget to mention
it once we have the new machines running.

For i386, I don't mind either way.



Andi


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100401190920.gc19...@mails.so.argh.org



Re: [buildd-tools-devel] the state of daily-builds

2010-04-01 Thread Frans Pop
Thanks for getting amd64 going again so fast.

On Thursday 01 April 2010, Andreas Barth wrote:
 As of now, we can't move the armel builds yet (as we are waiting for
 the new debian machines to be setup). I hope to not forget to mention
 it once we have the new machines running.

 For i386, I don't mind either way.

OK. In that case let's do all the arches we can now and add armel later.

That means the new to set up daily D-I builds on arch buildds are:
- i386
- sparc
- s390

For these we really will need to know when they are set up as we'll need to 
switch a few things over and inform their current buildd admins.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201004012140.47700.elen...@planet.nl



Davis/Austin web developer for Longhorn projects

2010-04-01 Thread Perry Gregg
You want to get more leads from your web site? Are there extensions to your 
pages you know you want to do? Contact me for a free analysis and quote. Email 
me back today.

Perry Gregg
Davis, CA  Austin, TX
cell: (510) 684-4152

P.S. Google or Yahoo Perry Gregg or Perry Gregg tennis, we practice tennis 
periodically at the Austin Tennis Academy with our 9 year old son. 


Bug#343607: Davis/Austin web developer for Longhorn projects

2010-04-01 Thread Perry Gregg
You want to get more leads from your web site? Are there extensions to your 
pages you know you want to do? Contact me for a free analysis and quote. Email 
me back today.

Perry Gregg
Davis, CA  Austin, TX
cell: (510) 684-4152

P.S. Google or Yahoo Perry Gregg or Perry Gregg tennis, we practice tennis 
periodically at the Austin Tennis Academy with our 9 year old son. 


Bug#392221: partman-auto-crypto

2010-04-01 Thread Sam Caldwell
I would second the suggestion for support of implementing loop-aes, as
this must otherwise be done through other means, thereby increasing the
cost (time, labor) of deploying Debian to secure situations.