Re: Speeding up l10n/calc-release-status

[Christian PERRIER]

Quoting Cyril Brulebois (k...@debian.org):

> > > partman-zfs is kfreebsd-* only; others are powerpc-specific, which is no
> > > longer a release architecture. Christian, which update would be the best
> > > one to reflect those changes? Add a minus sign after those packages in
> > > packages_list? Or remove them from there entirely?
> > 
> > I'd suggest tomove them to the attic, at leat the PPC ones. Not sure
> > about partman-zfs, though.
> 
> ACK for the attic move for ppc packages, but mu question was more about
> the l10n part of it.

Well, if the packages are moved to the attic and removed from
packages_list, the translation will vanish from the master files at
the next l10n-sync runand therefore will not interfere with statistics.

> 
> I think partman-zfs should stay where it is (out of the attic), but its
> translations shouldn't be taken into account for stats purposes?

Well, we never did that (not counting arch-specific packages in
statistics), which would enforce the idea that some arches are "more
important" than others. But that's of course debatable given that the
number of people installing a kFreeBSD system in anything else than
English is probably near to zero.

For sure, such packages' translations shoudl be marked for levels 3
and higher and shouldn't clutter the stats for levels 1 and 2.

-- 




signature.asc
Description: PGP signature

Re: Speeding up l10n/calc-release-status

[Cyril Brulebois]

Christian PERRIER  (2017-06-26):
> Quoting Cyril Brulebois (k...@debian.org):
> 
> > Current errors are:
> > E: error getting madison info for partman-newworld for 'testing'
> > E: error getting madison info for partman-zfs for 'testing'
> > E: error getting madison info for prep-installer for 'testing'
> > E: error getting madison info for quik-installer for 'testing'
> > E: error getting madison info for yaboot-installer for 'testing'
> > 
> > partman-zfs is kfreebsd-* only; others are powerpc-specific, which is no
> > longer a release architecture. Christian, which update would be the best
> > one to reflect those changes? Add a minus sign after those packages in
> > packages_list? Or remove them from there entirely?
> 
> I'd suggest tomove them to the attic, at leat the PPC ones. Not sure
> about partman-zfs, though.

ACK for the attic move for ppc packages, but mu question was more about
the l10n part of it.

I think partman-zfs should stay where it is (out of the attic), but its
translations shouldn't be taken into account for stats purposes?


KiBi.


signature.asc
Description: Digital signature

Re: Speeding up l10n/calc-release-status

[Christian PERRIER]

Quoting Cyril Brulebois (k...@debian.org):

> Current errors are:
> E: error getting madison info for partman-newworld for 'testing'
> E: error getting madison info for partman-zfs for 'testing'
> E: error getting madison info for prep-installer for 'testing'
> E: error getting madison info for quik-installer for 'testing'
> E: error getting madison info for yaboot-installer for 'testing'
> 
> partman-zfs is kfreebsd-* only; others are powerpc-specific, which is no
> longer a release architecture. Christian, which update would be the best
> one to reflect those changes? Add a minus sign after those packages in
> packages_list? Or remove them from there entirely?

I'd suggest tomove them to the attic, at leat the PPC ones. Not sure
about partman-zfs, though.



signature.asc
Description: PGP signature

Speeding up l10n/calc-release-status

[Cyril Brulebois]

Hi,

It's been an annoyance during all releases: this script processes all
packages in turn, and that takes quite a while. I've tried to make it
run in parallel by defining a function and calling parallel on it, but
it would need a few other functions and variables to be exported as
well, so I've taken an easier route and split the interesting part into
a calc-release-status-helper script, to be called for each and every
package.

Now, calc-release-status will treat packages in a parallel manner, using
as many cores as available, and it now finishes in under 3 minutes on my
d-i development machine, which makes me quite happy. :)

Other consequence: output will no longer be sorted by package name due
to parallelism.


Current errors are:
E: error getting madison info for partman-newworld for 'testing'
E: error getting madison info for partman-zfs for 'testing'
E: error getting madison info for prep-installer for 'testing'
E: error getting madison info for quik-installer for 'testing'
E: error getting madison info for yaboot-installer for 'testing'

partman-zfs is kfreebsd-* only; others are powerpc-specific, which is no
longer a release architecture. Christian, which update would be the best
one to reflect those changes? Add a minus sign after those packages in
packages_list? Or remove them from there entirely?


Note: It's still on my todo list to make it run on dillon regularly,
instead of waiting until release day to possibly notice missing git
pushes (see bug report #762055).


KiBi.


signature.asc
Description: Digital signature

Bug#762055: marked as done (d-i.debian.org: run calc-release-status regularly to catch missing tags)

[Debian Bug Tracking System]

Your message dated Sun, 25 Jun 2017 03:21:35 +0200
with message-id <20170625012135.ga...@mraw.org>
and subject line Re: Bug#762055: d-i.debian.org: run calc-release-status 
regularly to catch missing tags
has caused the Debian Bug report #762055,
regarding d-i.debian.org: run calc-release-status regularly to catch missing 
tags
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
762055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: d-i.debian.org
Severity: normal

Part of a debian-installer upload is about including a file computed
by calc-release-status; it's somewhat frustrating to see it fail
because this or that tag wasn't pushed to a repository, meaning a
failed checkout/translation lookup for said package. Then I get to
chase people instead of keeping on preparing the upload.

It would probably be a good idea to integrate that in a crontab to
help detect such issues as soon as possible, and to get a quicker
release step when everything else is ready.

Mraw,
KiBi.
--- End Message ---
--- Begin Message ---
Cyril Brulebois <k...@debian.org> (2014-09-18):
> Part of a debian-installer upload is about including a file computed
> by calc-release-status; it's somewhat frustrating to see it fail
> because this or that tag wasn't pushed to a repository, meaning a
> failed checkout/translation lookup for said package. Then I get to
> chase people instead of keeping on preparing the upload.
> 
> It would probably be a good idea to integrate that in a crontab to
> help detect such issues as soon as possible, and to get a quicker
> release step when everything else is ready.

Closing as a duplicate of #763578… Oops.


KiBi.


signature.asc
Description: Digital signature
--- End Message ---

Bug#763578: d-i.debian.org: run calc-release-status in a crontab

[Cyril Brulebois]

Christian PERRIER bubu...@debian.org (2014-10-01):
 Quoting Cyril Brulebois (k...@debian.org):
  Package: d-i.debian.org
  Severity: normal
  
  Every time a release is getting prepared one has to run calc-release-status,
  which can:
   1) take a while;
   2) and most annoyingly: fail because of a missing tag and similar things.
  
  It's a usual source of frustration and time loss when stuff should just be 
  being
  wrapped up and forgotten about.
  
  Having it run in a crontab would make it possible to detect those issues in 
  a
  preemptive fashion, and possibly make updating the l10n status as simple as 
  a
  file transfer. (Failing a quick resolution of #762053, scp from dillon would
  just work.)
 
 Just had a brief try tonight, which failed, probably because of:
 
 # ssh franck.debian.org is used to work around #699268; we want dak 
 ls.
 madison=$(ssh franck.debian.org dak ls -s $SUITE $package -a source)
 
 d-i@dillon:~/trunk/scripts/l10n$ ssh franck.debian.org dak ls
 Permission denied (publickey).
 
 
 Not investigated further, though

rmadison supports being told where to look, and UDD got fixed anyway. If
needed, we can still point rmadison at the ftp-master URL instead.

I've also committed r70009 which makes it possible to point at local git
checkouts instead of downloading stuff from git.debian.org, which speeds
things up, and should work fine as long as they're updated regularly
(and that happens already due to various crontab entries).

I've used it this way:
  GITREPO=/home/kibi/debian-installer/packages ./calc-release-status

I'll probably look into implementing something for #763578 after Stretch
Alpha 1 is out.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#763578: d-i.debian.org: run calc-release-status in a crontab

[Christian PERRIER]

Quoting Cyril Brulebois (k...@debian.org):
 Package: d-i.debian.org
 Severity: normal
 
 Every time a release is getting prepared one has to run calc-release-status,
 which can:
  1) take a while;
  2) and most annoyingly: fail because of a missing tag and similar things.
 
 It's a usual source of frustration and time loss when stuff should just be 
 being
 wrapped up and forgotten about.
 
 Having it run in a crontab would make it possible to detect those issues in a
 preemptive fashion, and possibly make updating the l10n status as simple as a
 file transfer. (Failing a quick resolution of #762053, scp from dillon would
 just work.)

Just had a brief try tonight, which failed, probably because of:

# ssh franck.debian.org is used to work around #699268; we want dak ls.
madison=$(ssh franck.debian.org dak ls -s $SUITE $package -a source)

d-i@dillon:~/trunk/scripts/l10n$ ssh franck.debian.org dak ls
Permission denied (publickey).


Not investigated further, though



signature.asc
Description: Digital signature

Bug#763578: d-i.debian.org: run calc-release-status in a crontab

[Cyril Brulebois]

Package: d-i.debian.org
Severity: normal

Every time a release is getting prepared one has to run calc-release-status,
which can:
 1) take a while;
 2) and most annoyingly: fail because of a missing tag and similar things.

It's a usual source of frustration and time loss when stuff should just be being
wrapped up and forgotten about.

Having it run in a crontab would make it possible to detect those issues in a
preemptive fashion, and possibly make updating the l10n status as simple as a
file transfer. (Failing a quick resolution of #762053, scp from dillon would
just work.)

Mraw,
KiBi.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20141001031237.15622.35337.report...@wodi.home.mraw.org

Bug#762055: d-i.debian.org: run calc-release-status regularly to catch missing tags

[Cyril Brulebois]

Package: d-i.debian.org
Severity: normal

Part of a debian-installer upload is about including a file computed
by calc-release-status; it's somewhat frustrating to see it fail
because this or that tag wasn't pushed to a repository, meaning a
failed checkout/translation lookup for said package. Then I get to
chase people instead of keeping on preparing the upload.

It would probably be a good idea to integrate that in a crontab to
help detect such issues as soon as possible, and to get a quicker
release step when everything else is ready.

Mraw,
KiBi.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20140918002045.19803.6219.report...@arya.home.mraw.org

Bug#757985: kfreebsd-* release status?

[Steven Chamberlain]

On 19/08/14 00:40, Cyril Brulebois wrote:
 [ I'm adding -release@ to the loop. I tried to refrain from mentioning
 my concerns in the Jessie Beta 1 announce, that's why I used a quite
 neutral wording, but let's be honest: kfreebsd-* is looking bad right
 now. ]

I was drafting a quite long reply to this, but after 15 minutes, I
realised whatever precious time we have, needs to be spent fixing the
bugs, not discussing this.  So I'll reply to each of the bugs individually.

In short, yes I think kfreebsd does have high workload right now;  we
could use more help as the freeze approaches, but I'm not worried.

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org



signature.asc
Description: OpenPGP digital signature

Bug#757985: kfreebsd-* release status? (was: #757985: kfreebsd: d-i hangs)

[Cyril Brulebois]

[ I'm adding -release@ to the loop. I tried to refrain from mentioning
my concerns in the Jessie Beta 1 announce, that's why I used a quite
neutral wording, but let's be honest: kfreebsd-* is looking bad right
now. ]

Cyril Brulebois k...@debian.org (2014-08-14):
 Steven Chamberlain ste...@pyro.eu.org (2014-08-13):
  Some new installer components have appeared since wheezy, such as
  partman-iscsi, which is arch: all.  It is of no use without
  open-iscsi-udeb, which is linux-any.
  
  Is it a bug that it is added into kfreebsd images with unsatisfied
  dependencies?  And/or, must we work around it by making
  partman-iscsi arch: linux-any?
  
  I know it is not very big, but it is shown in the partman menu,
  despite it not going to work. I don't think we'll have userland
  iSCSI initiator support for jessie.
 
 (Non-)installability seems quite orthogonal to the fact that we're
 hitting ENOSPC right after locale-related settings, doesn't it? If a
 single extra udeb (or udeb size increase, which happens from time to
 time) is going to break kfreebsd-*, it seems to me that their status
 is far too brittle.

To expand a bit on my earlier reply: that wouldn't be the first
partman-* package being uninstallable. See the edos/dose reports
(table or graphs):
  http://d-i.debian.org/edos/#unstable
  http://d-i.debian.org/edos/graph-unstable-kfreebsd-amd64.png
  http://d-i.debian.org/edos/graph-unstable-kfreebsd-i386.png

 I'm also quite astonished about being the one reporting that. Did I
 miss developer/porter testing and/or user reports?
 
 This kind of breakage is so bad that I would have expected reports
 way earlier, or at least before my own noticing that these images
 are unusable…

Is anyone currently working on figuring out what exactly the problem
is, and how to fix it?

FWIW the current state of d-i on kfreebsd-*, along with unfixed (not
even replied to) serious bug reports in kfreebsd headers (#750836,
#756553), and upgradability issues (kernel removal, #756464) kind of
get me worried about kfreebsd-* releasability for jessie.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Re: Etch Beta 3 release - status update

[Frans Pop]

On Friday 07 July 2006 00:01, Frans Pop wrote:
 On Thursday 22 June 2006 22:29, Frans Pop wrote:
  I will post a more detailed release plan as soon as it is clear when
  the 2.6.16 kernel packages will migrate to testing. Some information
  about Beta 3 is already available from [1].

 As this has not yet happened, there is no real progress on the release,
 although a lot of general preparation has been done.

 There is some activity to resolve the issues around 2.6.16, but there
 is also a real chance that the migration will not happen and that we
 will have to cancel Beta 3.

I'm a bit more positive although things are still moving slowly. There is 
now a new source package that provides the needed kernel meta packages 
waiting in NEW for testing-proposed-updates.

A further delay will be caused by the two major kernel security issues 
published this week which means a new linux-2.6.16 is needed. We will 
need to also update the kernel udebs after that.

I still intend to post a more detailed release plan when the kernel is 
ready to migrate. As the past month has shown, it is useless to do so 
before that time.

Cheers,
FJP


pgpC5myFdnXCT.pgp
Description: PGP signature

Etch Beta 3 release - status update

[Frans Pop]

On Thursday 22 June 2006 22:29, Frans Pop wrote:
 I will post a more detailed release plan as soon as it is clear when
 the 2.6.16 kernel packages will migrate to testing. Some information
 about Beta 3 is already available from [1].

As this has not yet happened, there is no real progress on the release, 
although a lot of general preparation has been done.

There is some activity to resolve the issues around 2.6.16, but there is 
also a real chance that the migration will not happen and that we will 
have to cancel Beta 3.


pgpiX6EqLhWHG.pgp
Description: PGP signature

Re: Etch Beta 3 release - status update

[Christian Perrier]

Quoting Frans Pop ([EMAIL PROTECTED]):

 There is some activity to resolve the issues around 2.6.16, but there is 
 also a real chance that the migration will not happen and that we will 
 have to cancel Beta 3.

Does this mean that Etch would be released with 2.6.15?


Or cancelling Beta3 is more postponing it?

I suspect an issue that could affect the whole release process. Am I wrong?


-- 




signature.asc
Description: Digital signature

Re: release status

[Sven Luther]

On Mon, Aug 09, 2004 at 01:52:24AM +0200, Christian Leimer wrote:
 Sven Luther wrote:
 
  On Sat, Aug 07, 2004 at 10:18:09PM +0200, Christian Leimer wrote:
  Sven Luther wrote:
  
   On Sat, Aug 07, 2004 at 05:02:31PM +0200, Holger Levsen wrote:
   Hi,
   
Well, i have no idea what you are trying to do, but my guess is that
you are not looking in the right place. The miboot 2.4 floppies are
at
:
   
 
  http://people.debian.org/~luther/d-i/images/daily/powerpc-small/floppy/
   
   hmm the boot.img from 2004-08-06, 21:24 (still) doesn't boot and
   the root.img is too big to fit on a floppy :-(
   
   :/ We need to find out why this happens. Do you know how to build it
   :yourself ?
   
  
  Hi!
  
  I today copied the vmlinux.coff kernel from
  kernel-build-2.4.25-powerpc-small to a hfs floppy and was able to boot
  from openfirmware with: boot fd:vmlinux(renamed kernel). The kernel loads
  but hangs because of no root fs. So whoever is building the boot floppies
  
  The initrd should have the root fs modules, so this should not be a
  problem. I have no idea how you specify a initrd with the OF, but my guess
  is that you need to produce a kernel with builtin initrd, like we do for
  chrp or prep.
  
  The best guess would be to use a 2.6.7-powerpc kernel, and use :
  
mkvmlinuz 2.6.7-powerpc
  
  to generate vmlinuz-2.6.7-powerpc, which you can then boot from the OF.
  This is rather untested though, but mkvmlinuz supports the generation of
  the .coff image.
  
  Maybe d-i should provide such .coff images, since so it is not needed to
  have either bootx nor miboot. But since this is only available from the
  serial console, it cannot be a generic solution for old world.
  
  should take this kernel and add some root or ram stuff to make a di boot
  floppy. Also it seems that the ofonly and the normal kernels are equal.
  Should this be so? And they still dont work error: unrecognized Client
  Programm formatstate not valid. Maybe some sort of wrong format it should
  be xcoff or?
  
  No idea about this.
  
 
 Hi again!
 
 Take a look at:
 http://people.debian.org/~luther/d-i/images/2004-08-08/build_powerpc-small_floppy_boot.log
 
 And you can see that the floppy was built with a 2.4 kernel. And I think
 that it should stay so and not take an 2.6 kernel, because I never was able

Well, it probably will anyway for sarge, as Jens refused to create a smallish
version of the 2.6.7 powerpc config.

 to boot on later after sarge installed on my Umax(oldworld clone mac).

That said, various reports of 2.6.7 based installer working using the bootx
method make me feel like it would be not a problem. Now, if you have trouble
booting the debian 2.6.7 kernel on your oldworld, your duty is to report bugs
about the issue, so we get a chance to fix it.

 Also look at line nine from the end of the file its:
 hcopy -r ./tmp/powerpc-small_floppy_boot-ofonly/vmlinux.gz :vmlinuz
 it seems that a gziped vmlinux file becomes vmlinuz. Do I understand that
 right? But It should be a coff file, dont know if compressed or not. So the
 error formatstate blabla at openfirmwae is a result of loading a gz file.

Mmm, well it is supposed to be a format that miboot is able to read, not one
you launch directly from the OF.

 Maybe someone (how to find out how?)can change the build script to make a
 coff file and the I can test if the resulting floppy will work.

I don't think this will change anything, and i don't think this is the
problem. I will modifify the build scripts to build a .coff oldworld netboot
kernel, maybe you will want to test this one ? 

 Since d-i rc1 is out now there should be a boot floppy for people how dont
 have macos to boot from cd on an oldworld.

Sure, but i have no oldworld hardware, and people testing the miboot floppies
have been very few and none of them recently. Your contribution is welcome to
participate in debian-installer oldworld support, as well as to unassemble the
miboot boot block and provide us with data on how to reimplement it in a free
way.

Friendly,

Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[John Summerfield]

Joey Hess wrote:
John Summerfield wrote:
 

I set out to find whether the new manual provides that kind of 
information, or pointer to where it may be found.  In the course of my 
search I have discovered:
a)  http://d-i.alioth.debian.org/manual/en.arm/apas03.html contains links 
to
a.1 The Multi Disk HOWTO 
http://www.tldp.org/HOWTO/Multi-Disk-HOWTO.html which is quite old and 
seriously out of date. I doubt whether any but the most frugal would be 
satisfied, for example, with the partitions sizes recommended on 
http://www.tldp.org/HOWTO/Multi-Disk-HOWTO-10.html#ss10.1. If nobody 
wants to take on the task of revising it, I suggest the link be dropped.
   

It's only two years out of date and looks generally correct to me as far
as workable minimum sizes go. I see no real reason to drop the link.
 

a.2 A link to Partitioning Strategies 
http://www.tldp.org/HOWTO/mini/Partition/partition-5.html#SUBMITTED 
which gets a 404.
   

Removed.
 

b) No manuals for PowerPC or s390.
   

I see both in the table at http://d-i.alioth.debian.org/manual/
 

I saw the links there and got errors following them:
Quite possibly I misinterpreted this error:
1091938534.561704 192.168.9.114 TCP_MISS/503 1466 GET 
http://d-i.alioth.debian.org/manual/en.s390/index.html - NONE/- text/html
Host: d-i.alioth.debian.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) 
Gecko/20040413 Debian/1.6-5
Accept: text/xml,application/xml,application/xhtml 
xml,text/html;q=0.9,text/plain;q=0.8,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1
Accept-Language: en-au,en-us;q=0.7,en;q=0.3
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-15,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Proxy-Connection: keep-alive
Referer: http://d-i.alioth.debian.org/manual/

HTTP/1.0 503 Service Unavailable
Server: squid/2.5.STABLE6
Mime-Version: 1.0
Date: Sun, 08 Aug 2004 04:15:34 GMT
Content-Type: text/html
Content-Length: 1117
Expires: Sun, 08 Aug 2004 04:15:34 GMT
X-Squid-Error: ERR_CONNECT_FAIL 101
Sorry for the woft.
--
Cheers
John
-- spambait
[EMAIL PROTECTED]  [EMAIL PROTECTED]
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Sven Luther]

On Sat, Aug 07, 2004 at 10:18:09PM +0200, Christian Leimer wrote:
 Sven Luther wrote:
 
  On Sat, Aug 07, 2004 at 05:02:31PM +0200, Holger Levsen wrote:
  Hi,
  
   Well, i have no idea what you are trying to do, but my guess is that
   you are not looking in the right place. The miboot 2.4 floppies are at
   :
  

 http://people.debian.org/~luther/d-i/images/daily/powerpc-small/floppy/
  
  hmm the boot.img from 2004-08-06, 21:24 (still) doesn't boot and the
  root.img is too big to fit on a floppy :-(
  
  :/ We need to find out why this happens. Do you know how to build it
  :yourself ?
  
 
 Hi!
 
 I today copied the vmlinux.coff kernel from
 kernel-build-2.4.25-powerpc-small to a hfs floppy and was able to boot from
 openfirmware with: boot fd:vmlinux(renamed kernel). The kernel loads but
 hangs because of no root fs. So whoever is building the boot floppies

The initrd should have the root fs modules, so this should not be a problem. I
have no idea how you specify a initrd with the OF, but my guess is that you
need to produce a kernel with builtin initrd, like we do for chrp or prep.

The best guess would be to use a 2.6.7-powerpc kernel, and use :

  mkvmlinuz 2.6.7-powerpc

to generate vmlinuz-2.6.7-powerpc, which you can then boot from the OF. This
is rather untested though, but mkvmlinuz supports the generation of the .coff
image.

Maybe d-i should provide such .coff images, since so it is not needed to have
either bootx nor miboot. But since this is only available from the serial
console, it cannot be a generic solution for old world.

 should take this kernel and add some root or ram stuff to make a di boot
 floppy. Also it seems that the ofonly and the normal kernels are equal.
 Should this be so? And they still dont work error: unrecognized Client
 Programm formatstate not valid. Maybe some sort of wrong format it should
 be xcoff or?

No idea about this.

 If a new kernel is ready some time I can test if needed.

Hope this helps, 

Friendly,

Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[John Summerfield]

Joey Hess wrote:
Joey Hess wrote:
 

http://dragon/~joey/blog/entry/d-i_retrospective-2004-08-07-19-46
   

I guess anyone not on my home network would prefer this url:
http://kitenet.net/~joey/blog/entry/d-i_retrospective-2004-08-07-19-46
 

A partcular concern I have is the reason for so many Apache packages. 
I've never discovered documentation as to why there are apache, 
apache-ssl and apache-perl, and how to decide which one(s) to install.

I set out to find whether the new manual provides that kind of 
information, or pointer to where it may be found.  In the course of my 
search I have discovered:
a)  http://d-i.alioth.debian.org/manual/en.arm/apas03.html contains links to
a.1 The Multi Disk HOWTO 
http://www.tldp.org/HOWTO/Multi-Disk-HOWTO.html which is quite old and 
seriously out of date. I doubt whether any but the most frugal would be 
satisfied, for example, with the partitions sizes recommended on 
http://www.tldp.org/HOWTO/Multi-Disk-HOWTO-10.html#ss10.1. If nobody 
wants to take on the task of revising it, I suggest the link be dropped.
a.2 A link to Partitioning Strategies 
http://www.tldp.org/HOWTO/mini/Partition/partition-5.html#SUBMITTED 
which gets a 404.
b) No manuals for PowerPC or s390.


--
Cheers
John
-- spambait
[EMAIL PROTECTED]  [EMAIL PROTECTED]
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Joey Hess]

John Summerfield wrote:
 I set out to find whether the new manual provides that kind of 
 information, or pointer to where it may be found.  In the course of my 
 search I have discovered:
 a)  http://d-i.alioth.debian.org/manual/en.arm/apas03.html contains links 
 to
 a.1 The Multi Disk HOWTO 
 http://www.tldp.org/HOWTO/Multi-Disk-HOWTO.html which is quite old and 
 seriously out of date. I doubt whether any but the most frugal would be 
 satisfied, for example, with the partitions sizes recommended on 
 http://www.tldp.org/HOWTO/Multi-Disk-HOWTO-10.html#ss10.1. If nobody 
 wants to take on the task of revising it, I suggest the link be dropped.

It's only two years out of date and looks generally correct to me as far
as workable minimum sizes go. I see no real reason to drop the link.

 a.2 A link to Partitioning Strategies 
 http://www.tldp.org/HOWTO/mini/Partition/partition-5.html#SUBMITTED 
 which gets a 404.

Removed.

 b) No manuals for PowerPC or s390.

I see both in the table at http://d-i.alioth.debian.org/manual/

-- 
see shy jo


signature.asc
Description: Digital signature

Re: release status

[Christian Leimer]

Sven Luther wrote:

 On Sat, Aug 07, 2004 at 10:18:09PM +0200, Christian Leimer wrote:
 Sven Luther wrote:
 
  On Sat, Aug 07, 2004 at 05:02:31PM +0200, Holger Levsen wrote:
  Hi,
  
   Well, i have no idea what you are trying to do, but my guess is that
   you are not looking in the right place. The miboot 2.4 floppies are
   at
   :
  

 http://people.debian.org/~luther/d-i/images/daily/powerpc-small/floppy/
  
  hmm the boot.img from 2004-08-06, 21:24 (still) doesn't boot and
  the root.img is too big to fit on a floppy :-(
  
  :/ We need to find out why this happens. Do you know how to build it
  :yourself ?
  
 
 Hi!
 
 I today copied the vmlinux.coff kernel from
 kernel-build-2.4.25-powerpc-small to a hfs floppy and was able to boot
 from openfirmware with: boot fd:vmlinux(renamed kernel). The kernel loads
 but hangs because of no root fs. So whoever is building the boot floppies
 
 The initrd should have the root fs modules, so this should not be a
 problem. I have no idea how you specify a initrd with the OF, but my guess
 is that you need to produce a kernel with builtin initrd, like we do for
 chrp or prep.
 
 The best guess would be to use a 2.6.7-powerpc kernel, and use :
 
   mkvmlinuz 2.6.7-powerpc
 
 to generate vmlinuz-2.6.7-powerpc, which you can then boot from the OF.
 This is rather untested though, but mkvmlinuz supports the generation of
 the .coff image.
 
 Maybe d-i should provide such .coff images, since so it is not needed to
 have either bootx nor miboot. But since this is only available from the
 serial console, it cannot be a generic solution for old world.
 
 should take this kernel and add some root or ram stuff to make a di boot
 floppy. Also it seems that the ofonly and the normal kernels are equal.
 Should this be so? And they still dont work error: unrecognized Client
 Programm formatstate not valid. Maybe some sort of wrong format it should
 be xcoff or?
 
 No idea about this.
 

Hi again!

Take a look at:
http://people.debian.org/~luther/d-i/images/2004-08-08/build_powerpc-small_floppy_boot.log

And you can see that the floppy was built with a 2.4 kernel. And I think
that it should stay so and not take an 2.6 kernel, because I never was able
to boot on later after sarge installed on my Umax(oldworld clone mac).

Also look at line nine from the end of the file its:
hcopy -r ./tmp/powerpc-small_floppy_boot-ofonly/vmlinux.gz :vmlinuz
it seems that a gziped vmlinux file becomes vmlinuz. Do I understand that
right? But It should be a coff file, dont know if compressed or not. So the
error formatstate blabla at openfirmwae is a result of loading a gz file.

Maybe someone (how to find out how?)can change the build script to make a
coff file and the I can test if the resulting floppy will work.

Since d-i rc1 is out now there should be a boot floppy for people how dont
have macos to boot from cd on an oldworld.

Ciao Chris.

 



 


 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[John Summerfield]

Joey Hess wrote:
John Summerfield wrote:
 

I set out to find whether the new manual provides that kind of 
information, or pointer to where it may be found.  In the course of my 
search I have discovered:
a)  http://d-i.alioth.debian.org/manual/en.arm/apas03.html contains links 
to
a.1 The Multi Disk HOWTO 
http://www.tldp.org/HOWTO/Multi-Disk-HOWTO.html which is quite old and 
seriously out of date. I doubt whether any but the most frugal would be 
satisfied, for example, with the partitions sizes recommended on 
http://www.tldp.org/HOWTO/Multi-Disk-HOWTO-10.html#ss10.1. If nobody 
wants to take on the task of revising it, I suggest the link be dropped.
   

It's only two years out of date and looks generally correct to me as far
as workable minimum sizes go. I see no real reason to drop the link.
 

I have a minimimal Sarge install. it's 200 Mbytes.
That rules out Learning.
I don't know what hoppies one can practice with 300 Mbytes of free disk 
and no optional packages, but it seems to me you'd be constrained.

If you want a GUI disktop and a reasonable set of software, 2 gbytes is 
about the going rate: it's what I used on RHL 7.3, it's about what the 
progeny install I just did takes. SuSE 9.0 came out a bit lite at 1.4. I 
don't have a recent equivalent Sarge to look at.

I know my 30 Gbyte drive is bulging at the perimeter. If I thought to 
master DVDs it would be nowhere near enough.


--
Cheers
John
-- spambait
[EMAIL PROTECTED]  [EMAIL PROTECTED]
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Holger Levsen]

Hi,

 Well, i have no idea what you are trying to do, but my guess is that you
 are not looking in the right place. The miboot 2.4 floppies are at :

   http://people.debian.org/~luther/d-i/images/daily/powerpc-small/floppy/

hmm the boot.img from 2004-08-06, 21:24 (still) doesn't boot and the 
root.img is too big to fit on a floppy :-(


regards,
Holger

p.s.: please excuse my long absense from this list. i've been to busy with 
other stuff. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status (checklist)

[Holger Levsen]

Hi,

On Tuesday 03 August 2004 16:43, Joey Hess wrote:
   The test
   checklist in installer/doc/checklist is still missing many entries and
   the more complete it is the better I'd feel about calling this release
   rc1 instead of beta5.
  If you'll send me a pointer (URL?) to the test checklist, I'll try to
  make sure that it gets as done as possible for OldWorld PowerPC hardware.

 http://d-i.alioth.debian.org/svn/debian-installer/installer/doc/checklist

i've got some questions regarding the ppc-specific entries:

powerpc
basic netinst cd
basic businesscard cd   ok
floppy + cd [not newworld]
floppy + network [not newworld]
netboot
using pcmcia network card
32 mb ram
48 mb ram


1. is it true, that if 32mb ram installs work, 48mb will always work, too ?

2. I think oldworld would be less confusing than not newworld ? generally 
I would prefer to refer to the exact subarch...


regards,
Holger


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status (checklist)

[Joey Hess]

Holger Levsen wrote:
 1. is it true, that if 32mb ram installs work, 48mb will always work, too ?

No. The system only enters lowmem mode at a given cutoff point, so we
have to test the lowest supported amount of memory, as well as making
sure that the cutoff point is at a place where there is enough memory
for the install to work without lowmem mode.

-- 
see shy jo


signature.asc
Description: Digital signature

Re: release status

[Sven Luther]

On Sat, Aug 07, 2004 at 05:02:31PM +0200, Holger Levsen wrote:
 Hi,
 
  Well, i have no idea what you are trying to do, but my guess is that you
  are not looking in the right place. The miboot 2.4 floppies are at :
 
http://people.debian.org/~luther/d-i/images/daily/powerpc-small/floppy/
 
 hmm the boot.img from 2004-08-06, 21:24 (still) doesn't boot and the 
 root.img is too big to fit on a floppy :-(

:/ We need to find out why this happens. Do you know how to build it yourself ?

Friendly,

Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Christian Leimer]

Sven Luther wrote:

 On Sat, Aug 07, 2004 at 05:02:31PM +0200, Holger Levsen wrote:
 Hi,
 
  Well, i have no idea what you are trying to do, but my guess is that
  you are not looking in the right place. The miboot 2.4 floppies are at
  :
 
   
http://people.debian.org/~luther/d-i/images/daily/powerpc-small/floppy/
 
 hmm the boot.img from 2004-08-06, 21:24 (still) doesn't boot and the
 root.img is too big to fit on a floppy :-(
 
 :/ We need to find out why this happens. Do you know how to build it
 :yourself ?
 

Hi!

I today copied the vmlinux.coff kernel from
kernel-build-2.4.25-powerpc-small to a hfs floppy and was able to boot from
openfirmware with: boot fd:vmlinux(renamed kernel). The kernel loads but
hangs because of no root fs. So whoever is building the boot floppies
should take this kernel and add some root or ram stuff to make a di boot
floppy. Also it seems that the ofonly and the normal kernels are equal.
Should this be so? And they still dont work error: unrecognized Client
Programm formatstate not valid. Maybe some sort of wrong format it should
be xcoff or?
If a new kernel is ready some time I can test if needed.

Hope this helps.

Bye Chris.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Joey Hess]

I've released d-i rc1. Great job!

Also, some may find this worth reading:
http://dragon/~joey/blog/entry/d-i_retrospective-2004-08-07-19-46
Would someone who was active while I wasn't working on d-i like to fill
in the gap?

-- 
see shy jo


signature.asc
Description: Digital signature

Re: release status

[Joey Hess]

Joey Hess wrote:
 http://dragon/~joey/blog/entry/d-i_retrospective-2004-08-07-19-46

I guess anyone not on my home network would prefer this url:

http://kitenet.net/~joey/blog/entry/d-i_retrospective-2004-08-07-19-46

-- 
see shy jo


signature.asc
Description: Digital signature

Re: release status

[Frederik Dannemare]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tuesday 03 August 2004 05:55, Joey Hess wrote:
 At this point the only delay is waiting for the autobuilders, which
 are overloaded from all the other uploads surrounding the sarge
 release, to catch up and build the d-i images. In the past 24 hours,
 we've gotten builds for hppa, ia64, s390, and sparc, plus a manual
 build for alpha. That leaves arm, m68k (building), mips, mipsel, and
 powerpc. d-i is far back in the queue for most of these arches[1] and
 is even slipping further behind on some as more high-urgency package
 uploads happen.

 Since it's looking like it could easily take days for some of these
 buildds to catch up, we may need to do manual builds on some of these
 architectures. It would be nice if we could get all the builds done
 before the next dinstall run. If you do a manual build, please take
 careto make it in an up-to-date and clean sid chroot.

 Other than that, we seem to be on track for a release. I'm not aware
 of any showstopper issues, and the current errata list is quite
 small. Once the initrd builds get in and the CDs are built with them,
 we will have one final day for last minute testing before the
 release. The test checklist in installer/doc/checklist is still
 missing many entries and the more complete it is the better I'd feel
 about calling this release rc1 instead of beta5.

I have a suggestion for an errata item (relates to Bug#241179)...

PCMCIA device shifting (between CD-ROM and NIC) during install:

If you choose to install Debian via CD, but you only have your CD-ROM 
drive and NIC (which you want to setup and use as primary NIC during 
installation) accessible via a single PCMCIA slot in your computer, 
here is what you can do to work around this situation.

Boot the installer with the CD-ROM device plugged into the PCMCIA slot 
and do a normal 1st stage installation, except that you should skip 
network setup or just type in dummy values at this point.

Then when it says Installation complete, choose 'Go back' to drop back 
to the main menu. Now change the PCMCIA device from CD-ROM to NIC, and 
choose to 'Detect network hardware'. Your NIC should now be detected 
and you can continue (again 'Go back' to main menu) to 'Network 
configuration'.

If your NIC is a wireless, press Alt+F2 to get a shell. Change the 
PCMCIA device from NIC to CD-ROM and type in the shell:
 chroot /target
 mount /cdrom
 apt-get install wireless-tools
 umount /cdrom
 exit
Go back to Alt+F1 and change the PCMCIA device from CD-ROM to NIC.

Choose 'Continue' to reboot (with NIC in PCMCIA slot) and thereby finish 
the 1st stage of the installation process.

When 2st stage comes up after the reboot, you should have a working NIC 
and as such you can choose to download extra packages via ftp, http, 
etc.

Should you, however, not have a working NIC at this point, go to the 
shell (Alt+F2) and try to reload your NIC:
 ifdown iface  ifup iface
Return to Alt+F1 and continue installation (assuming networking now 
works)...

- --
Frederik Dannemare | mailto:[EMAIL PROTECTED]
GnuPG key: search for 'dannemare' on http://pgpkeys.mit.edu
Key fingerprint: BB7B 078A 0DBF 7663 180A  F84A 2D25 FAD5 9C4E B5A8
http://frederik.dannemare.net | http://www.linuxworlddomination.dk
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBE3T+LSX61ZxOtagRAr+8AJwM7pXr5cG2612RaWlV1TXJJESjrwCdFOBS
dyJ+XZV56rkkXSTbWGL8ytE=
=5eRd
-END PGP SIGNATURE-

Re: release status

[Joey Hess]

Yet another update: We seem to be on schedule for a release tomorrow.
All images are built except for full CDs (building for next 24+ hours).
To do prerelease testing, use the 20040801 images from the archive, and 
the 20040806 arge_d-i CDs. Official release will be after dinstall
tomorrow.

-- 
see shy jo


signature.asc
Description: Digital signature

Re: release status

[Sven Luther]

On Thu, Aug 05, 2004 at 12:07:21AM +0200, Christian Leimer wrote:
  Since the most oldworld use scsi to boot it is very important that this
  works.
  
  Maybe 2.4 should be the standard for oldworld macs since I have a lot of
  problems getting a 2.6 kernel to work with quik.
  
  2.4 is the default for the miboot oldworld floppies, which are the default
  oldworld install. The bootx one depending on a non-free OS cannot be
  recomended by debian.
  
 
 I today tested the boot-floppies but miboot is gone there is only a hfs disk
 with vmlinux file. I booted via openfirmware and got: unrecognized Client
 Programm formatstate not valid. So it is not possible for me to boot the
 installer from floppy.

Well, i have no idea what you are trying to do, but my guess is that you are
not looking in the right place. The miboot 2.4 floppies are at : 

  http://people.debian.org/~luther/d-i/images/daily/powerpc-small/floppy/

 The only thing that works well is di(2.4 kernel) with BootX here on my Umax
 S900. 

Ok.

Friendly,

Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Kenshi Muto]

At 3 Aug 04 03:55:21 GMT,
Joey Hess wrote:
 At this point the only delay is waiting for the autobuilders, which are
 overloaded from all the other uploads surrounding the sarge release, to
 catch up and build the d-i images. In the past 24 hours, we've gotten
 builds for hppa, ia64, s390, and sparc, plus a manual build for alpha.
 That leaves arm, m68k (building), mips, mipsel, and powerpc. d-i is far
 back in the queue for most of these arches[1] and is even slipping
 further behind on some as more high-urgency package uploads happen.
 [1] http://people.debian.org/~igloo/status.php?packages=debian-installer

Well, what's current status of d-i release...? We delay some days.
From [1], arm and mipsel seem need to build. Is this a show stopper?

Thanks,
-- 
Kenshi Muto
[EMAIL PROTECTED]

Re: release status

[Joey Hess]

Kenshi Muto wrote:
 Well, what's current status of d-i release...? We delay some days.
 From [1], arm and mipsel seem need to build. Is this a show stopper?

We got the last of the initrd builds today, it's just waiting on the
ftp-master to move them into place, and then the CD builds.

-- 
see shy jo


signature.asc
Description: Digital signature

Re: release status

[Kenshi Muto]

Hi,

At 6 Aug 04 04:23:48 GMT,
Joey Hess wrote:
 Kenshi Muto wrote:
  Well, what's current status of d-i release...? We delay some days.
  From [1], arm and mipsel seem need to build. Is this a show stopper?
 
 We got the last of the initrd builds today, it's just waiting on the
 ftp-master to move them into place, and then the CD builds.

Oh, that's good news. Thank you.

Thanks,
-- 
Kenshi Muto
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Christian Leimer]

Joey Hess wrote:

 Rick Thomas wrote:
 Bug#261460: Non-DHCP network config step of d-i is broken If you
 choose to manually configure the network (don't use DHCP) the
 installer keeps coming back to the configure network step, and if
 you force it to move forward, after the reboot, the network is not
 configured.  This seems to be unique to OldWorld PowerPC hardware
 (I've tried it on two different types of OldWorld machines and it
 breaks identically on both of them.  However, it works on a couple of
 NewWorld machines I tried it on.)  Also, accepting the default of
 DNSserver==gateway makes it work OK.  Verrry strange!
 
 I don't think this is powerpc specific, see bug #261527. Whatever it is,
 it doesn't seem to affect many installs.
 
 Bug#262201: PowerMac (OldWorld) - no driver for onboard SCSI
 
 It's not clear to me how many machine this effects.
 
 Bug#262865: With two network interfaces after reboot uses the wrong
 one
 
 Does not seem like a common bug to me. Looks likely to have been a
 discover version skew or something between the version used by the
 installer and that in testing. (If so it's already fixed; the image you
 tested is 11 days old after all.)
 

Hi I today tried the di form:
http://people.debian.org/~luther/d-i/images/2004-08-04/powerpc/netboot/
with BootX.

It does not detect mesh and mace on oldworld. So there may be a problem in
autodetect hardware on oldworld and loading the correct modules for scsi
and ethernet. The mace driver I could choose from a list before DHCP config 
starts, which then works without problem. But the mesh I had to activate
with insmod then I was able to install to my internal scsi disk. 

Since the most oldworld use scsi to boot it is very important that this
works.

Maybe 2.4 should be the standard for oldworld macs since I have a lot of
problems getting a 2.6 kernel to work with quik.

Also there should be a warning in the installer that quik works only with
ext2 before I run into a problem trying to install quik on ext3 or other
filesystems.

And the installer should ask to reboot and not do it automatic after the
config of the base system.

Thanks a lot so far for the good work to the debian-installer developers.

Only the bootloader is a problem for me now, quik does not install correct.

I send a complete report when beta 4 is out.


Bye chris.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Sven Luther]

On Wed, Aug 04, 2004 at 01:48:32PM +0200, Christian Leimer wrote:
 Joey Hess wrote:
 
  Rick Thomas wrote:
  Bug#261460: Non-DHCP network config step of d-i is broken If you
  choose to manually configure the network (don't use DHCP) the
  installer keeps coming back to the configure network step, and if
  you force it to move forward, after the reboot, the network is not
  configured.  This seems to be unique to OldWorld PowerPC hardware
  (I've tried it on two different types of OldWorld machines and it
  breaks identically on both of them.  However, it works on a couple of
  NewWorld machines I tried it on.)  Also, accepting the default of
  DNSserver==gateway makes it work OK.  Verrry strange!
  
  I don't think this is powerpc specific, see bug #261527. Whatever it is,
  it doesn't seem to affect many installs.
  
  Bug#262201: PowerMac (OldWorld) - no driver for onboard SCSI
  
  It's not clear to me how many machine this effects.
  
  Bug#262865: With two network interfaces after reboot uses the wrong
  one
  
  Does not seem like a common bug to me. Looks likely to have been a
  discover version skew or something between the version used by the
  installer and that in testing. (If so it's already fixed; the image you
  tested is 11 days old after all.)
  
 
 Hi I today tried the di form:
 http://people.debian.org/~luther/d-i/images/2004-08-04/powerpc/netboot/
 with BootX.
 
 It does not detect mesh and mace on oldworld. So there may be a problem in
 autodetect hardware on oldworld and loading the correct modules for scsi
 and ethernet. The mace driver I could choose from a list before DHCP config 
 starts, which then works without problem. But the mesh I had to activate
 with insmod then I was able to install to my internal scsi disk. 

A discover related problem maybe ? 

 Since the most oldworld use scsi to boot it is very important that this
 works.
 
 Maybe 2.4 should be the standard for oldworld macs since I have a lot of
 problems getting a 2.6 kernel to work with quik.

2.4 is the default for the miboot oldworld floppies, which are the default
oldworld install. The bootx one depending on a non-free OS cannot be
recomended by debian.

 Also there should be a warning in the installer that quik works only with
 ext2 before I run into a problem trying to install quik on ext3 or other
 filesystems.
 
 And the installer should ask to reboot and not do it automatic after the
 config of the base system.

Well, i don't know how you boot, but asking is indeed the default behavior.

 Thanks a lot so far for the good work to the debian-installer developers.
 
 Only the bootloader is a problem for me now, quik does not install correct.

Work on quik only started recently, so this may be the reason for it. I would
very much like to have a better understanding of the 2.6 problem. Could you
tell me the module name involved and the pci id of the device that fail ? 

Or you could check directly in : 

  /usr/share/discover/pci.lst

and fill a bug report against discover if it doesn't show up.

Friendly,

Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Christian Leimer]

 Since the most oldworld use scsi to boot it is very important that this
 works.
 
 Maybe 2.4 should be the standard for oldworld macs since I have a lot of
 problems getting a 2.6 kernel to work with quik.
 
 2.4 is the default for the miboot oldworld floppies, which are the default
 oldworld install. The bootx one depending on a non-free OS cannot be
 recomended by debian.
 

I today tested the boot-floppies but miboot is gone there is only a hfs disk
with vmlinux file. I booted via openfirmware and got: unrecognized Client
Programm formatstate not valid. So it is not possible for me to boot the
installer from floppy.

The only thing that works well is di(2.4 kernel) with BootX here on my Umax
S900. 

Thanks chris


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status (checklist)

[Joey Hess]

Rick Thomas wrote:
 
 Joey Hess wrote:
 
  The test
  checklist in installer/doc/checklist is still missing many entries and
  the more complete it is the better I'd feel about calling this release
  rc1 instead of beta5.
 
 If you'll send me a pointer (URL?) to the test checklist, I'll try to make sure that 
 it gets as done as possible for OldWorld PowerPC hardware.

http://d-i.alioth.debian.org/svn/debian-installer/installer/doc/checklist

-- 
see shy jo


signature.asc
Description: Digital signature

Re: release status

[Joey Hess]

Rick Thomas wrote:
 Bug#261460: Non-DHCP network config step of d-i is broken If you
 choose to manually configure the network (don't use DHCP) the
 installer keeps coming back to the configure network step, and if
 you force it to move forward, after the reboot, the network is not
 configured.  This seems to be unique to OldWorld PowerPC hardware
 (I've tried it on two different types of OldWorld machines and it
 breaks identically on both of them.  However, it works on a couple of
 NewWorld machines I tried it on.)  Also, accepting the default of
 DNSserver==gateway makes it work OK.  Verrry strange!

I don't think this is powerpc specific, see bug #261527. Whatever it is,
it doesn't seem to affect many installs.

 Bug#262201: PowerMac (OldWorld) - no driver for onboard SCSI

It's not clear to me how many machine this effects.

 Bug#262865: With two network interfaces after reboot uses the wrong
 one

Does not seem like a common bug to me. Looks likely to have been a
discover version skew or something between the version used by the
installer and that in testing. (If so it's already fixed; the image you
tested is 11 days old after all.)

-- 
see shy jo


signature.asc
Description: Digital signature

Re: release status OldWorld PowerPC mesh scsi

[Rick_Thomas]

On Tue, 2004-08-03 at 10:51, Joey Hess wrote:
 Rick Thomas wrote:
  Bug#261460: Non-DHCP network config step of d-i is broken If you
  choose to manually configure the network (don't use DHCP) the
  installer keeps coming back to the configure network step, and if
  you force it to move forward, after the reboot, the network is not
  configured.  This seems to be unique to OldWorld PowerPC hardware
  (I've tried it on two different types of OldWorld machines and it
  breaks identically on both of them.  However, it works on a couple of
  NewWorld machines I tried it on.)  Also, accepting the default of
  DNSserver==gateway makes it work OK.  Verrry strange!
 
 I don't think this is powerpc specific, see bug #261527. Whatever it is,
 it doesn't seem to affect many installs.

It affects both my beige G3 minitower and my PowerMac 6500.  It does not
affect my gray G4.  Debian has problems with the video on my BlueWhite
G3, so I can't test it there.

The beige G3 minitower is a popular server machine because it has a
case/motherboard that is very easy to upgrade with RAM and has 3 open
PCI card slots and a couple of extra disk bays.

I have provided Josh with a DEBCONF_DEBUG=5 logfile, but I haven't heard
back whether it helped in narrowing down the problem.  I assume he's too
busy to look at it.


 
  Bug#262201: PowerMac (OldWorld) - no driver for onboard SCSI
 
 It's not clear to me how many machine this effects.

Justabout every OldWorld PCI PowerMac has a mesh SCSI chip.  Apple
didn't switch to IDE until fairly late in the game.  So there are a lot
of OldWorld PowerMacs out there with SCSI being the *only* way to talk
to peripherals.

 
  Bug#262865: With two network interfaces after reboot uses the wrong
  one
 
 Does not seem like a common bug to me. Looks likely to have been a
 discover version skew or something between the version used by the
 installer and that in testing. (If so it's already fixed; the image you
 tested is 11 days old after all.)

I'll try it on the latest daily and let you know what I find.

Rick


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Joey Hess]

Joey Hess wrote:
 At this point the only delay is waiting for the autobuilders, which are
 overloaded from all the other uploads surrounding the sarge release, to
 catch up and build the d-i images. In the past 24 hours, we've gotten
 builds for hppa, ia64, s390, and sparc, plus a manual build for alpha.
 That leaves arm, m68k (building), mips, mipsel, and powerpc. d-i is far
 back in the queue for most of these arches[1] and is even slipping
 further behind on some as more high-urgency package uploads happen.

We still need arm, mips. and mipsel.

-- 
see shy jo


signature.asc
Description: Digital signature

release status

[Joey Hess]

At this point the only delay is waiting for the autobuilders, which are
overloaded from all the other uploads surrounding the sarge release, to
catch up and build the d-i images. In the past 24 hours, we've gotten
builds for hppa, ia64, s390, and sparc, plus a manual build for alpha.
That leaves arm, m68k (building), mips, mipsel, and powerpc. d-i is far
back in the queue for most of these arches[1] and is even slipping
further behind on some as more high-urgency package uploads happen.

Since it's looking like it could easily take days for some of these
buildds to catch up, we may need to do manual builds on some of these
architectures. It would be nice if we could get all the builds done
before the next dinstall run. If you do a manual build, please take careto make it in 
an up-to-date and clean sid chroot.

Other than that, we seem to be on track for a release. I'm not aware of
any showstopper issues, and the current errata list is quite small. Once
the initrd builds get in and the CDs are built with them, we will have
one final day for last minute testing before the release. The test
checklist in installer/doc/checklist is still missing many entries and
the more complete it is the better I'd feel about calling this release
rc1 instead of beta5.

-- 
see shy jo

[1] http://people.debian.org/~igloo/status.php?packages=debian-installer


signature.asc
Description: Digital signature

Re: release status

[Rick Thomas]

Joey Hess wrote:
 
 At this point the only delay is waiting for the autobuilders, which are
 overloaded from all the other uploads surrounding the sarge release, to
 catch up and build the d-i images. In the past 24 hours, we've gotten
 builds for hppa, ia64, s390, and sparc, plus a manual build for alpha.
 That leaves arm, m68k (building), mips, mipsel, and powerpc. d-i is far
 back in the queue for most of these arches[1] and is even slipping
 further behind on some as more high-urgency package uploads happen.
 
 Since it's looking like it could easily take days for some of these
 buildds to catch up, we may need to do manual builds on some of these
 architectures. It would be nice if we could get all the builds done
 before the next dinstall run. If you do a manual build, please take careto make it 
 in an up-to-date and clean sid chroot.
 
 Other than that, we seem to be on track for a release. I'm not aware of
 any showstopper issues, and the current errata list is quite small. Once
 the initrd builds get in and the CDs are built with them, we will have
 one final day for last minute testing before the release. The test
 checklist in installer/doc/checklist is still missing many entries and
 the more complete it is the better I'd feel about calling this release
 rc1 instead of beta5.
 

Over the last couple of weeks, I've submitted three (what I consider to be) serious 
bug report for d-i on OldWorld PowerPC machines, along with several more that are more 
in the line of annoyances.

Any one of these three bugs will render debian-installer unusable for anyone with 
anything but a plain vanilla hardware or networking environment who doesn't have 
help from a competant System Administrator, or have such skills personally.  Since I'm 
the only one on this list who cares two figs about OldWorld PowerPC hardware, and I 
have UNIX SysAdmin experience going back 25 years (including some pretty unusual 
hardware!), I guess it's not a show stopper...  Still, there *might* be some folks out 
there in the real world (TM), who will be disappointed that they can't figure out 
how to install the new Debian release on their particular old Macintosh hardware.  You 
never know!

For reference, here are the bug numbers and a short description of each:

Bug#261460: Non-DHCP network config step of d-i is broken
If you choose to manually configure the network (don't use DHCP) the installer 
keeps coming back to the configure network step, and if you force it to move 
forward, after the reboot, the network is not configured.  This seems to be unique to 
OldWorld PowerPC hardware (I've tried it on two different types of OldWorld machines 
and it breaks identically on both of them.  However, it works on a couple of NewWorld 
machines I tried it on.)  Also, accepting the default of DNSserver==gateway makes it 
work OK.  Verrry strange!

Bug#262201: PowerMac (OldWorld) - no driver for onboard SCSI

Bug#262865: With two network interfaces after reboot uses the wrong one


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Rick Thomas]

OOOps... I accidentally hit send when I meant to hit save... Here's the complete 
message as I intended it to be!

Rick

Joey Hess wrote:
 
 At this point the only delay is waiting for the autobuilders, which are
 overloaded from all the other uploads surrounding the sarge release, to
 catch up and build the d-i images. In the past 24 hours, we've gotten
 builds for hppa, ia64, s390, and sparc, plus a manual build for alpha.
 That leaves arm, m68k (building), mips, mipsel, and powerpc. d-i is far
 back in the queue for most of these arches[1] and is even slipping
 further behind on some as more high-urgency package uploads happen.
 
 Since it's looking like it could easily take days for some of these
 builds to catch up, we may need to do manual builds on some of these
 architectures. It would be nice if we could get all the builds done
 before the next dinstall run. If you do a manual build, please take careto make it 
 in an up-to-date and clean sid chroot.
 
 Other than that, we seem to be on track for a release. I'm not aware of
 any showstopper issues, and the current errata list is quite small. Once
 the initrd builds get in and the CDs are built with them, we will have
 one final day for last minute testing before the release. The test
 checklist in installer/doc/checklist is still missing many entries and
 the more complete it is the better I'd feel about calling this release
 rc1 instead of beta5.
 

Over the last couple of weeks, I've submitted three (what I consider to be) serious 
bug report for d-i on OldWorld PowerPC machines, along with several more that are more 
in the line of annoyances.

Any one of these three bugs will render debian-installer unusable for anyone with 
anything but a plain vanilla hardware or networking environment who doesn't have 
help from a competent System Administrator, or have such skills personally.  Since I'm 
the only one on this list who cares two figs about OldWorld PowerPC hardware, and I 
have UNIX SysAdmin experience going back 25 years (including some pretty unusual 
hardware!), I guess it's not a show stopper...  Still, there *might* be some folks out 
there in the real world (TM), who will be disappointed that they can't figure out 
how to install the new Debian release on their particular old Macintosh hardware.  You 
never know!

For reference, here are the bug numbers and a short description of each:

Bug#261460: Non-DHCP network config step of d-i is broken
If you choose to manually configure the network (don't use DHCP) the installer 
keeps coming back to the configure network step.  And if you force it to move 
forward, then after the reboot, the network interface is not configured.  This seems 
to be unique to OldWorld PowerPC hardware (I've tried it on two different types of 
OldWorld machines and it breaks identically on both of them.  However, it works on a 
couple of NewWorld machines I tried it on.  Go figure!)  Also, accepting the default 
of DNSserver==gateway seems to make it work OK.  Verrry strange!

Bug#262201: PowerMac (OldWorld) - no driver for onboard SCSI

The 2.6.7 kernel version of d-i for PowerPC does not recognize Apple's old mesh 
onboard SCSI controller.  Seeing as how lots of OldWorld machines have no other way 
than SCSI of attaching disks or CD-ROM drives, this renders them ineligible for 
installation using the 2.6.7 kernel.  It works OK with the 2.4.25 kernel.

Bug#262865: With two network interfaces after reboot uses the wrong one

On a machine with two Network interface cards, only one of which is to be used (e.g. 
my situation with an onboard 10BaseT and a PCI 100BaseT but I only want to use the 
faster interface, and ignore the slower) after the reboot, the wrong interface is 
configured.

Enjoy!

Rick


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status (checklist)

[Rick Thomas]

Joey Hess wrote:

 The test
 checklist in installer/doc/checklist is still missing many entries and
 the more complete it is the better I'd feel about calling this release
 rc1 instead of beta5.

If you'll send me a pointer (URL?) to the test checklist, I'll try to make sure that 
it gets as done as possible for OldWorld PowerPC hardware.

Thanks!

Rick


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

release status update

[Joey Hess]

I've submitted what I hope will be the final debian-installer build to the
autobuilders, but it seems that recent dependency breakage in newt will
cause some of the builds to fail. I hope I can ask the autobuilders to
retry, but this will likely delay things for a few days.

At this point it's probably too late to get any changes into udebs in
the initrds, and there are probably only a few days left to make changes
to other udebs. Any changes will be synced to testing on a per-udeb
basis again until we release, so you have to give me a very good reason
to put in a change.

In the meantime, the daily built images (but still the sid_d-i CDs, not
sarge_d-i) are very close to what we will release, so please test them
as much as you can, and update installer/doc/checklist. I'm mailing
everyone in doc/testers.txt to try to get some broader testing. I still
don't know if this release should be called beta5 or rc1, and I think
the best way to decide is to see how well it gets tested and how many
errata-level problems we find.

There is also a DRAFT release announcement in installer/doc. Maybe I
forgot some noteworthy features, please check.

-- 
see shy jo


signature.asc
Description: Digital signature

Re: release status update

[Sven Luther]

On Thu, Jul 29, 2004 at 03:11:11PM -0400, Joey Hess wrote:
 I've submitted what I hope will be the final debian-installer build to the
 autobuilders, but it seems that recent dependency breakage in newt will
 cause some of the builds to fail. I hope I can ask the autobuilders to
 retry, but this will likely delay things for a few days.
 
 At this point it's probably too late to get any changes into udebs in
 the initrds, and there are probably only a few days left to make changes
 to other udebs. Any changes will be synced to testing on a per-udeb
 basis again until we release, so you have to give me a very good reason
 to put in a change.

Please consider including the base-installer 1.01 and the nobootloader 0.17
.udebs i uploaded today. The 1.01 base-installer include a nicer way to handle
powerpc kernels with builtin initrd, and also makes sure that kernel upgraded
after the install will be functional.

The nobootloader change include giving exacter booting instructions for the
powerpc/chrp_pegasos (a thing which could be cloned for other arches without
boot loader but with known boot procedures), as well as add the logic for the
generic case. Ideally, a string change would be needed to tell the user about
the partition in which to find the kernel in the generic case, but this can
wait for after the beta5/rc1 release, but it would look nicer. The string
change is not a sever one though, just adding on partition ${BOOT} in the
boot instruction to know where the kernel is.

Friendly,

Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

discover on powerbook [was: Re: release status update]

[Giuseppe Sacco]

Il dom, 2004-04-25 alle 00:13, Petter Reinholdtsen ha scritto:
 [Giuseppe Sacco]
  A second problem I understand only now is that the powerpc discover
  we have in testing now is broken: every time I switch on my laptop
  (powerbook g4, 15, 867Mhz) it hangs when discover run and probe for
  parallel port devices. This means that I have to press the keyboard
  combination to reset the machine.
 
 I believe this is fixed in the version of discover1 that went into
 sarge last night.  Discover was instructed to not probe paralell and
 serial ports at boot time, but there was a bug making it ignore this
 instruction.  Please test if this is fixed or not, and add info to bug
 #237603 (and possibly #214790).
 
  Now I am upgrading the machine and it is downloading the new
  discover 2.0.4-3 with discover-data 2.2004.04.09-1, so this might be
  changed. I will let you know.
 
 I do not know if this is fixed in version 2 of discover.  I suspect it
 is not.

the upgrade was from testing 2004-04-17 to 2004-04-24 and discover
changed from 1.5-2 to 2.0.4-3. The problem seems fixed, but I only tried
once. I will do some more tests and I'll update the bug reports.

Bye,
Giuseppe



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#237603: release status update

[Giuseppe Sacco]

I just upgraded to discover 2.0.4-3 with discover-data 2.2004.04.09-1
and it seems that the problem is fixed.

Bye,
Giuseppe



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status update

[Joey Hess]

Steve Langasek wrote:
 - qlogicisp driver doesn't work right with many (most?) SCSI cards;
   bug #238593 et al.
 - both the de4x5 and the tulip drivers fail to work with many
   DECChip-based ethernet cards in the 2.4.2x series alpha kernels;
   bug #228654.

Both of these sound like reasonable candidates for errata if they're not
fixed, and not release blockers. Do you want them in the errata?

 It also seems fairly certain that the netboot images don't work on alpha
 (unless they were fixed while I wasn't looking).  I don't seem to have a
 way to test these anyway, as telling SRM to boot from ethernet generates
 no network traffic here.

Right, I see that's marked as being nonfunctonal on the ports status page.

-- 
see shy jo


signature.asc
Description: Digital signature

Re: release status update

[elijah wright]

  - both the de4x5 and the tulip drivers fail to work with many
DECChip-based ethernet cards in the 2.4.2x series alpha kernels;
bug #228654.

 Both of these sound like reasonable candidates for errata if they're not
 fixed, and not release blockers. Do you want them in the errata?

does this bug affect the onboard tulip ethernet that comes with most of
the alpha hardware?  if so, its a real bad bug.

elijah


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status update

[Steve Langasek]

On Sat, Apr 24, 2004 at 12:54:18PM -0400, Joey Hess wrote:
 Steve Langasek wrote:
  - qlogicisp driver doesn't work right with many (most?) SCSI cards;
bug #238593 et al.
  - both the de4x5 and the tulip drivers fail to work with many
DECChip-based ethernet cards in the 2.4.2x series alpha kernels;
bug #228654.

 Both of these sound like reasonable candidates for errata if they're not
 fixed, and not release blockers. Do you want them in the errata?

Yes, please.

-- 
Steve Langasek
postmodern programmer


signature.asc
Description: Digital signature

Re: release status update

[Steve Langasek]

On Sat, Apr 24, 2004 at 12:16:44PM -0500, elijah wright wrote:
   - both the de4x5 and the tulip drivers fail to work with many
 DECChip-based ethernet cards in the 2.4.2x series alpha kernels;
 bug #228654.

  Both of these sound like reasonable candidates for errata if they're not
  fixed, and not release blockers. Do you want them in the errata?

 does this bug affect the onboard tulip ethernet that comes with most of
 the alpha hardware?  if so, its a real bad bug.

It affects many (I don't know if we can say most) onboard tulip chips
that came with alphas.  There are actually a wide range of chips covered
by the tulip and de4x5 drivers that were distributed by Digital; I don't
know yet if there's a clear pattern of which chips are affected, or if
the problem has more to do with the associated hardware (such as PCI
configuration and chipsets).

It is a very bad bug, but I don't know that it's feasible to do much
about it in the 2.4 kernel series in time for sarge.

Cheers,
-- 
Steve Langasek
postmodern programmer


signature.asc
Description: Digital signature

Re: release status update

[Giuseppe Sacco]

Il gio, 2004-04-22 alle 18:55, Joey Hess ha scritto:
[...]
 - powerpc: need list of working subarches (oldworld?)

I would like to have powerpc release only after having
kernel-image-2.4.25-powerpc-* version 2.4.25-8 in testing
because of #245012.

A second problem I understand only now is that the powerpc discover we
have in testing now is broken: every time I switch on my laptop
(powerbook g4, 15, 867Mhz) it hangs when discover run and probe for
parallel port devices. This means that I have to press the keyboard
combination to reset the machine.

The problem appear *only* when the machine is powered on, and it's not
appearing when I reboot it.

When it hangs, the keyboard isn't working and the led (the only one this
machine has) is on.

Now I am upgrading the machine and it is downloading the new discover
2.0.4-3 with discover-data 2.2004.04.09-1, so this might be changed. I
will let you know.

Bye,
Giuseppe


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status update

[Petter Reinholdtsen]

[Giuseppe Sacco]
 A second problem I understand only now is that the powerpc discover
 we have in testing now is broken: every time I switch on my laptop
 (powerbook g4, 15, 867Mhz) it hangs when discover run and probe for
 parallel port devices. This means that I have to press the keyboard
 combination to reset the machine.

I believe this is fixed in the version of discover1 that went into
sarge last night.  Discover was instructed to not probe paralell and
serial ports at boot time, but there was a bug making it ignore this
instruction.  Please test if this is fixed or not, and add info to bug
#237603 (and possibly #214790).

 Now I am upgrading the machine and it is downloading the new
 discover 2.0.4-3 with discover-data 2.2004.04.09-1, so this might be
 changed. I will let you know.

I do not know if this is fixed in version 2 of discover.  I suspect it
is not.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status update

[Joey Hess]

Giuseppe Sacco wrote:
 I would like to have powerpc release only after having
 kernel-image-2.4.25-powerpc-* version 2.4.25-8 in testing
 because of #245012.

If I'm expanding yuor wildcard correctly, they seem to go in
tonight/tomorrow. Anyway, you have several days to get them in, but this
does not feel like a release blocker to me if they do not make it.

-- 
see shy jo


signature.asc
Description: Digital signature

Re: release status update

[Martin Michlmayr]

* Joey Hess [EMAIL PROTECTED] [2004-04-22 22:15]:
  was loaded since it has a different sub-architecture (however, iirc,
  delo-installer is also loaded on Cobalt, so I assume sub-arch handling
  is broken).
 
 Argh, not again. libdebian-installer 0.22 went into the archive today
 with some fixes for subarch handling, in particular #243692. Was that
 version on your image?

No, I had 0.21.1.  I'll test with 0.22 tonight; thanks for pointing
this out.
-- 
Martin Michlmayr
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status update

[Martin Michlmayr]

* tbm [EMAIL PROTECTED] [2004-04-23 01:43]:
  - arm: ?
 
 arm/netwinder most definitely works.  It worked recently and there is

It works; the only problem I had was that the wrong kernel was
installed.  For some reason, debian-installer/kernel/subarchitecture
was not set.  Unfortunately, I cannot quite figure out why.  (I just
tried on mipsel and it definitely gets set there.)

-- 
Martin Michlmayr
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status update

[Thiemo Seufer]

Martin Michlmayr wrote:
 * tbm [EMAIL PROTECTED] [2004-04-23 01:43]:
   - arm: ?
  
  arm/netwinder most definitely works.  It worked recently and there is
 
 It works; the only problem I had was that the wrong kernel was
 installed.  For some reason, debian-installer/kernel/subarchitecture
 was not set.  Unfortunately, I cannot quite figure out why.  (I just
 tried on mipsel and it definitely gets set there.)

Does archdetect show the correct output for netwinder?


Thiemo


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status update

[Martin Michlmayr]

* Thiemo Seufer [EMAIL PROTECTED] [2004-04-23 16:32]:
 Does archdetect show the correct output for netwinder?

Yes.

-- 
Martin Michlmayr
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status update

[Martin Michlmayr]

* Joey Hess [EMAIL PROTECTED] [2004-04-22 22:15]:
 Argh, not again. libdebian-installer 0.22 went into the archive today
 with some fixes for subarch handling, in particular #243692. Was that
 version on your image?

I tried it with 0.22 now and still see the same... it's quite strange.
Just for reference: colo-installer is for mipsel/cobalt while
delo-installer is for mipsel/r3k-kn02 and mipsel/r4k-kn04.  On
mipsel/r3k-kn02, it installs colo-installer and delo-installer, but on
mipsel/cobalt it only installs colo-installer.  Looking at the logs, I
get this on mipsel/r3k-kn02 (egrep -n (colo|delo)-install syslog):

396:Apr 23 18:30:52 (none) user.debug anna[825]: DEBUG: install delo-installer, 
priority = standard 
452:Apr 23 18:30:53 (none) user.debug anna[825]: DEBUG: search for package resolving 
kernel-installer, dependency from delo-installer 
453:Apr 23 18:30:53 (none) user.debug anna[825]: DEBUG: install di-utils-mapdevfs, 
dependency from delo-installer 
482:Apr 23 18:30:53 (none) user.debug anna[825]: DEBUG: install colo-installer, 
dependency from prebaseconfig 
498:Apr 23 18:30:53 (none) user.debug anna[825]: DEBUG: search for package resolving 
kernel-installer, dependency from colo-installer 
499:Apr 23 18:30:53 (none) user.debug anna[825]: DEBUG: install di-utils-mapdevfs, 
dependency from colo-installer 
566:Apr 23 18:34:30 (none) user.debug main-menu[145]: DEBUG: search for package 
resolving kernel-installer, dependency from colo-installer 
569:Apr 23 18:34:30 (none) user.info main-menu[145]: INFO: Falling back to the package 
description for colo-installer 
...

On mipsel/cobalt, I get:

417:Jan  1 00:01:09 (none) user.debug anna[924]: DEBUG: install colo-installer, 
priority = standard 
487:Jan  1 00:01:09 (none) user.debug anna[924]: DEBUG: search for package resolving 
kernel-installer, dependency from colo-installer 
488:Jan  1 00:01:09 (none) user.debug anna[924]: DEBUG: install di-utils-mapdevfs, 
dependency from colo-installer 
531:Jan  1 00:01:09 (none) user.debug anna[924]: DEBUG: search for package resolving 
kernel-installer, dependency from colo-installer 
532:Jan  1 00:01:09 (none) user.debug anna[924]: DEBUG: install di-utils-mapdevfs, 
dependency from colo-installer 
596:Jan  1 00:02:26 (none) user.debug main-menu[143]: DEBUG: search for package 
resolving kernel-installer, dependency from colo-installer 
599:Jan  1 00:02:26 (none) user.info main-menu[143]: INFO: Falling back to the package 
description for colo-installer 
667:Jan  1 00:02:44 (none) user.debug main-menu[143]: DEBUG: search for package 
resolving kernel-installer, dependency from colo-installer 
...

AFAICT, the packages are done properly:

 Package: delo-installer
 Version: 0.003
 Section: debian-installer
 Priority: standard
 Architecture: mipsel
 Depends: cdebconf-udeb, kernel-installer, di-utils-mapdevfs
 Provides: bootable-system
 Installed-Size: 44
 Maintainer: Debian Install System Team [EMAIL PROTECTED]
 Description: Install Delo on a hard disk
  This udeb will install Delo on the hard disk.
 installer-menu-item: 73
 subarchitecture: r3k-kn02 r4k-kn04

and:

 Package: colo-installer
 Version: 0.02
 Section: debian-installer
 Priority: standard
 Architecture: mipsel
 Depends: cdebconf-udeb, kernel-installer, di-utils-mapdevfs
 Provides: bootable-system
 Installed-Size: 24
 Maintainer: Debian Install System Team [EMAIL PROTECTED]
 Description: Install the Cobalt boot loader on your disk
  This udeb will install the Cobalt loader colo on your hard disk.
 installer-menu-item: 73
 subarchitecture: cobalt

Any idea what's going on?
-- 
Martin Michlmayr
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status update

[Steve Langasek]

On Thu, Apr 22, 2004 at 12:55:06PM -0400, Joey Hess wrote:
 I'm trying to track status of various architectures at the top of TODO,
 here is what I have so far.

 - ia64: There is a devpts/sysvinit/glibc file conflict of some
 sort that breaks debootstrap. Need a bug #. (Might be
 related to #230857)

This is bug #238963, which also affects alpha; it has been (hopefully)
fixed by the recent -12 upload of glibc, which is currently in unstable
but not in testing.

 - alpha: still SCSI cd problems?

I've just seen that this is fixed in version 2.4.25-3 of the
kernel-image-2.4.25-1-generic package.  I can do a rebuild of the d-i
kernel package this evening (~3hrs), or if anyone else is willing and
able to get this uploaded sooner, feel free.

-- 
Steve Langasek
postmodern programmer


signature.asc
Description: Digital signature

release status update

[Joey Hess]

Today's the last day of the string freeze, leaving this left in the timeline
for release:

23 aprilupload translated udebs to archive
23 aprilwrite release announcement
24 aprillast possible changes to udebs on initrds
25 aprilinitrd builds
26 aprilinitrd builds continue (slow autobuilders)
27 aprilcd building, testing
28 aprilrelease beta 4

I'm trying to track status of various architectures at the top of TODO,
here is what I have so far.

- s390: FTBFS, still no success installing
- hppa: Hangs at discrete points during install, different on
different machines, needs to be investigated (bdale).
- arm: ?
- mips: reported ok
- mipsel: looks good
- powerpc: need list of working subarches (oldworld?)
- ia64: There is a devpts/sysvinit/glibc file conflict of some
sort that breaks debootstrap. Need a bug #. (Might be
related to #230857)
- alpha: still SCSI cd problems?
- m68k: need list of working subarches
- sparc: need successful install reports from cdrom, both subarches
- i386: Broken discover in testing makes installed system 
problimatic. Needs new discover stuff propigated in.

Please let me know of any other issues or corrections. At the moment
s390 is looking unlikely to be part of this release, while hppa should
be, and arm and mipsel are certian.

The most worrying things at the moment are the discover problem, and
the file conflict; if testing is not in a releasable state, we can't
release d-i.

We need to begin doing final testing now, to make sure all arches are
working with no regressions. We also need to do better testing of full
CD images this time around, not just netinst CDs.

A draft release announcement is now in subversion.

-- 
see shy jo


signature.asc
Description: Digital signature

Re: release status update

[Stephen R Marenka]

On Thu, Apr 22, 2004 at 12:55:06PM -0400, Joey Hess wrote:
 - m68k: need list of working subarches

mac and amiga are fully supported.

I hope to have support for the rest in the next couple of weeks or so, 
but if they aren't ready for release, so be it.

-- 
Stephen R. Marenka If life's not fun, you're not doing it right!
[EMAIL PROTECTED]


signature.asc
Description: Digital signature

Re: release status update

[Martin Michlmayr]

* Joey Hess [EMAIL PROTECTED] [2004-04-22 12:55]:
 - mipsel: looks good

I just did a successful installation on a DECstation 5000/133 via the
serial console.  Everything worked fine, apart from one thing: both
colo-installer and delo-installer got loaded, and colo-installer was
executed instead of delo-installer.  I have no idea why colo-installer
was loaded since it has a different sub-architecture (however, iirc,
delo-installer is also loaded on Cobalt, so I assume sub-arch handling
is broken).

p2 said that bogl crashes when he tries a DECstation install with a
video card, but it worked for Karsten recently.  I asked Karsten to
see if it works for him.

In any case, d-i definitely works on DECstation via the serial console
and is ready for beta4.  That is, mipsel/r3k-kn02 and mipsel/r4k-kn04
(DECstation with R3000 and R4000 CPUs).

mipsel/cobalt also works.  The only problem is that you (currently)
need an existing Linux installation in order to boot d-i.  This will
be fixed after beta4 (I'm waiting for the upstream author of colo to
implement net booting).  Apart from this, Cobalt installations work.
-- 
Martin Michlmayr
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status update

[Martin Michlmayr]

* Joey Hess [EMAIL PROTECTED] [2004-04-22 12:55]:
 I'm trying to track status of various architectures at the top of TODO,
 here is what I have so far.
 
 - arm: ?

arm/netwinder most definitely works.  It worked recently and there is
afaict nothing that broke it in the meantime.  arm/bast and
arm/riscstation probably work as well.

I hope I can do a test on arm/netwinder tomorrow to confirm.
-- 
Martin Michlmayr
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status update

[Joey Hess]

Martin Michlmayr wrote:
 I just did a successful installation on a DECstation 5000/133 via the
 serial console.  Everything worked fine, apart from one thing: both
 colo-installer and delo-installer got loaded, and colo-installer was
 executed instead of delo-installer.  I have no idea why colo-installer
 was loaded since it has a different sub-architecture (however, iirc,
 delo-installer is also loaded on Cobalt, so I assume sub-arch handling
 is broken).

Argh, not again. libdebian-installer 0.22 went into the archive today
with some fixes for subarch handling, in particular #243692. Was that
version on your image?

-- 
see shy jo


signature.asc
Description: Digital signature

Re: release status

[Sven Luther]

On Sun, Mar 14, 2004 at 11:26:31PM +0100, Giuseppe Sacco wrote:
 Il dom, 2004-03-14 alle 21:00, Joey Hess ha scritto:
 [...]
powerpc: autobuilding. kdb-chooser, airport wifi (#237894)
 
 What is the problem with autobuilding? I don't know if that port still
 uses the kernel I compile, but I had some problem lately and I manage to
 put it up again two days ago (now it uses the daily-build script.)

Huh? Since when are you compiling powerpc kernels ? 

Friendly,

Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Giuseppe Sacco]

Il mar, 2004-03-16 alle 10:05, Sven Luther ha scritto:
 On Sun, Mar 14, 2004 at 11:26:31PM +0100, Giuseppe Sacco wrote:
  Il dom, 2004-03-14 alle 21:00, Joey Hess ha scritto:
  [...]
 powerpc: autobuilding. kdb-chooser, airport wifi (#237894)
  
  What is the problem with autobuilding? I don't know if that port still
  uses the kernel I compile, but I had some problem lately and I manage to
  put it up again two days ago (now it uses the daily-build script.)
 
 Huh? Since when are you compiling powerpc kernels ? 

Hi Sven,
I just setup an autobuilder for manty in december. Then, in january, I
went to know that those builds where used by debian-cd.

Have a look at this thread:
http://lists.debian.org/debian-boot/2004/debian-boot-200401/msg01172.html
and at the next to last message:
http://lists.debian.org/debian-boot/2004/debian-boot-200401/msg01352.html

I would like to understand if this is still used or not. Do you have
more infos?

Thanks,
Giuseppe


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Sven Luther]

On Sun, Mar 14, 2004 at 03:00:55PM -0500, Joey Hess wrote:
 Assuming we release tomorrow, the deadline is now past for changes to
 udebs that go in the initrds. All translations are uploaded. The string
 freeze is over. Please limit changes to important fixes. If there are
 any final fixes to build/, add them soon; I upload the final cut of that
 tonight for the autobuilders.
 
 Here is the port status. We seem to be close to go on i386, mips,
 powerpc, ia64, sparc, and alpha. I still need more info about ia64 and
 alpha though, to be sure.
 
   i386: go!
   mips: autobuilding. Installs work (except some generic debootstrap
 issue TBD).
   powerpc: autobuilding. kdb-chooser, airport wifi (#237894)

Kernel installation is broken on powerpc when choosing testing.
base/kernel-installer choose the 2.4.25 kernel, while it has not yet
made it into testing (9 days of 10 so it will be soon).

Still, i believe that base/kernel-installer should have warned that
there is no appropriate kernel available, instead of silently installing
a wrong one.

Also, the -powerpc-small .udebs are still installed, pulled in by the
lvm stuff and the ext3 and reiserfs partman, if i remember well.

It is seriously broken that a module for a kernel different than the one
running is downloaded.

Apart from that, and the yaboot issue, everything seems to be working
fine. About yaboot, i should seriously think about porting yaboot to
pegasos, despites Ethan's claim that i should not and work on yaboot2
instead, since it seems nobody apart me and the pegasos users are doing
regular full installs.

Friendly,

Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Christian Perrier]

Quoting Joey Hess ([EMAIL PROTECTED]):
 Assuming we release tomorrow, the deadline is now past for changes to

I couldn't find the release annoucement file you mentioned me
yesterday on IRC, and I lost my logs for checkingI remember you
mentioning some file in doc/. Where is it ?



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Bastian Blank]

On Mon, Mar 15, 2004 at 07:13:19AM +0100, Petter Reinholdtsen wrote:
 If we release the CDs tomorrow, please note that a missing s390 upload
 blocks packages tasksel and shadow from entering testing.

Both are marked as installed in w-b.

Bastian

-- 
No one may kill a man.  Not for any purpose.  It cannot be condoned.
-- Kirk, Spock's Brain, stardate 5431.6


signature.asc
Description: Digital signature

Re: release status

[Christian Perrier]

Quoting Joey Hess ([EMAIL PROTECTED]):
 Christian Perrier wrote:
  Quoting Joey Hess ([EMAIL PROTECTED]):
   Assuming we release tomorrow, the deadline is now past for changes to
  
  I couldn't find the release annoucement file you mentioned me
  yesterday on IRC, and I lost my logs for checkingI remember you
  mentioning some file in doc/. Where is it ?
 
 I moved it over the the web site cvs, where I have not checked it in. So
 it's in html now -- here's a copy.

Well, that's fine. No change to suggest

For the errata file, maybe mention that BIDI languages ()Arabic and
Hebrew) will not display properly.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Bastian Blank]

On Mon, Mar 15, 2004 at 07:09:42PM +0100, Petter Reinholdtsen wrote:
 [Bastian Blank]
  Both are marked as installed in w-b.
 I'm not sure what that means.  Does that give us anything we can use
 to find out where the binaries are?

It means that w-b saw it in the parsed Packages file.

Bastian

-- 
Live long and prosper.
-- Spock, Amok Time, stardate 3372.7


signature.asc
Description: Digital signature

Re: release status

[Nikolai Prokoschenko]

On Mon, Mar 15, 2004 at 09:27:00AM +0100, Christian Perrier wrote:

 file you mentioned me yesterday on IRC, 

It's good you mentioned it. Which IRC channel do you use?

-- 
Nikolai Prokoschenko 
[EMAIL PROTECTED] / Jabber: [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Nikolai Prokoschenko]

On Mon, Mar 15, 2004 at 08:50:55PM +0100, Nikolai Prokoschenko wrote:
  file you mentioned me yesterday on IRC, 
 It's good you mentioned it. Which IRC channel do you use?

Forget it, I should have looked before I asked... :(

-- 
Nikolai Prokoschenko 
[EMAIL PROTECTED] / Jabber: [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Geert Stappers]

On Mon, Mar 15, 2004 at 07:14:44PM +0100, Bastian Blank wrote:
 On Mon, Mar 15, 2004 at 07:09:42PM +0100, Petter Reinholdtsen wrote:
  [Bastian Blank]
   Both are marked as installed in w-b.
  I'm not sure what that means.  Does that give us anything we can use
  to find out where the binaries are?
 
 It means that w-b saw it in the parsed Packages file.
 

And w-b is short for Web-Builder???


Geert Stappers


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Colin Watson]

On Mon, Mar 15, 2004 at 11:13:39PM +0100, Geert Stappers wrote:
 On Mon, Mar 15, 2004 at 07:14:44PM +0100, Bastian Blank wrote:
  On Mon, Mar 15, 2004 at 07:09:42PM +0100, Petter Reinholdtsen wrote:
   [Bastian Blank]
Both are marked as installed in w-b.
   I'm not sure what that means.  Does that give us anything we can use
   to find out where the binaries are?
  
  It means that w-b saw it in the parsed Packages file.
 
 And w-b is short for Web-Builder???

wanna-build, the database that Debian buildds query to find out what to
do.

-- 
Colin Watson  [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Christian Perrier]

Quoting Nikolai Prokoschenko ([EMAIL PROTECTED]):

 Forget it, I should have looked before I asked... :(

When it comes to me, don't expect me online very often on IRCI
still get connection problems for getting what I consider a good IRC
client (gaim) connected though a SSH tunnel when I'm at work (ssh
tunneling is my only way to use anything else than web due to security
constraints).

So, I often leave another client opened...but with no sound support,
so if I'm busy elsewhere, I may miss people pinging me.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

release status

[Joey Hess]

Assuming we release tomorrow, the deadline is now past for changes to
udebs that go in the initrds. All translations are uploaded. The string
freeze is over. Please limit changes to important fixes. If there are
any final fixes to build/, add them soon; I upload the final cut of that
tonight for the autobuilders.

Here is the port status. We seem to be close to go on i386, mips,
powerpc, ia64, sparc, and alpha. I still need more info about ia64 and
alpha though, to be sure.

  i386: go!
  mips: autobuilding. Installs work (except some generic debootstrap
issue TBD).
  powerpc: autobuilding. kdb-chooser, airport wifi (#237894)
  ia64: autobuilding. USB issues
  m68k: go!
  hppa: autobuilding, but broken
  sparc: autobuilding. Seems go on sparc32 and sparc64
- There is bug #234404 in installed system. Can be worked
  around by booting from d-i media and passing root=
- serial console support is broken (joshk)
  s390: autobuilding. partconf fails; parted needs IBM disklabel
support
  alpha: autobuilding. Problems with SCSI CDs (#237604)

-- 
see shy jo


signature.asc
Description: Digital signature

Re: release status

[Nathan Poznick]

Thus spake Joey Hess:
 Assuming we release tomorrow, the deadline is now past for changes to
 udebs that go in the initrds. All translations are uploaded. The string
 freeze is over. Please limit changes to important fixes. If there are
 any final fixes to build/, add them soon; I upload the final cut of that
 tonight for the autobuilders.
 
 Here is the port status. We seem to be close to go on i386, mips,
 powerpc, ia64, sparc, and alpha. I still need more info about ia64 and
 alpha though, to be sure.
 
   i386: go!

Out of curiosity, was anything figured out on bug #232415?


-- 
Nathan Poznick [EMAIL PROTECTED]

I was once arrested for walking in someone else's sleep. -Stephen
Wright



signature.asc
Description: Digital signature

Re: release status

[Joey Hess]

Nathan Poznick wrote:
 Out of curiosity, was anything figured out on bug #232415?

Not that I know of except that for some reason the dev files are missing
for cciss drives (whatever those are). Sounds like it's a bug in
debootstrap or makedev.

-- 
see shy jo


signature.asc
Description: Digital signature

Re: release status

[Giuseppe Sacco]

Il dom, 2004-03-14 alle 21:00, Joey Hess ha scritto:
[...]
   powerpc: autobuilding. kdb-chooser, airport wifi (#237894)

What is the problem with autobuilding? I don't know if that port still
uses the kernel I compile, but I had some problem lately and I manage to
put it up again two days ago (now it uses the daily-build script.)

Bye,
Giuseppe


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Joey Hess]

Giuseppe Sacco wrote:
 Il dom, 2004-03-14 alle 21:00, Joey Hess ha scritto:
 [...]
powerpc: autobuilding. kdb-chooser, airport wifi (#237894)
 
 What is the problem with autobuilding?

Nothing. That means it is autobuilding.

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#237534: release status

[Andrew Pollock]

On Fri, Mar 12, 2004 at 12:10:37AM +, Martin Michlmayr wrote:
 * Andrew Pollock [EMAIL PROTECTED] [2004-03-12 10:04]:
  A lot of your problems sound like they stemmed from the wrong
  partition type for the partition you wanted to use as a physical
  volume, but then 83 is a short typo from 8e, so you may have had it
  right.
 
 Oh, I wrote 83... yes, that's a typo.  It definitely was 8e/LVM (grrr,
 just typed 83 again ;).
 
  lvm2 isn't in the 2.4 series kernels is it?).
 
 Yes, it is.  At least our Debian kernel has it.  (It might be in
 2.4.25 upstream now, not sure; but we had it since 2.4.24 or so.)

Hmm, okay. I just read Joey's email with deadlines for udeb changes. I'm not
sure if I'm going to be able to retest an LVM install to see if I can
reproduce your problems between now and then. If lvm10 and lvm2 will coexist
(which I think they can) it might be worthwhile altering the postinst for
lvmcfg to install both packages and getting it in for beta3.

Andrew


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Martin Michlmayr]

* Andrew Pollock [EMAIL PROTECTED] [2004-03-07 13:38]:
  I've uploaded a package with your patch.
 
 I tested the daily build for 20040305, which included lvmcfg 0.17, and it
 now works properly, lvm10 is installed on a system that uses LVM.

And that works for you?  The LVM is created is version2, and so lvm10
cannot even see it.  At least I think this is what happens here on my
system (#237534).
-- 
Martin Michlmayr
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Andrew Pollock]

On Thu, Mar 11, 2004 at 11:56:07PM +, Martin Michlmayr wrote:
 * Andrew Pollock [EMAIL PROTECTED] [2004-03-07 13:38]:
   I've uploaded a package with your patch.
  
  I tested the daily build for 20040305, which included lvmcfg 0.17, and it
  now works properly, lvm10 is installed on a system that uses LVM.
 
 And that works for you?  The LVM is created is version2, and so lvm10
 cannot even see it.  At least I think this is what happens here on my
 system (#237534).

Hmm, yes, it did work for me. I just read your epic adventure (#237534).

A lot of your problems sound like they stemmed from the wrong partition type
for the partition you wanted to use as a physical volume, but then 83 is a
short typo from 8e, so you may have had it right. AFAIK, d-i isn't doing
lvm2 yet, so lvm10 should be appropriate still (lvm2 isn't in the 2.4
series kernels is it?).

I'm going away for the weekend, but Monday's a public holiday, so I'll try
and hose my machine completely on Monday and test with the latest daily
build.

Andrew


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#237534: release status

[Martin Michlmayr]

* Andrew Pollock [EMAIL PROTECTED] [2004-03-12 10:04]:
 A lot of your problems sound like they stemmed from the wrong
 partition type for the partition you wanted to use as a physical
 volume, but then 83 is a short typo from 8e, so you may have had it
 right.

Oh, I wrote 83... yes, that's a typo.  It definitely was 8e/LVM (grrr,
just typed 83 again ;).

 lvm2 isn't in the 2.4 series kernels is it?).

Yes, it is.  At least our Debian kernel has it.  (It might be in
2.4.25 upstream now, not sure; but we had it since 2.4.24 or so.)
-- 
Martin Michlmayr
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status update

[Sven Luther]

On Mon, Mar 08, 2004 at 10:29:28PM -0500, Joey Hess wrote:
   3. at least one successful installation report per boot method
 
 I have not had time to track installation reports. Could someone take
 a pass through the list of recent reports and post a summary to the list
 please? My vague impressions:
 
 - i386 is generally working ok
 - powerpc is working ok the subarches that worked last time
 - once again we are almost out of time on including any more powerpc
   subarches

No, this is not quite exact.

chrp, chrp-rs6k and prep will be working this time around, i think
everything is there, but i need to fiddle the build system for it still
to build the initrd images, but i do this already by hand, and
everything is in place for it. This would use the powerpc netboot
initrd. 

the cdrom initrd is too big though, i will not have time to fix the
kernel for this, so maybe building a new specialized initrd image with
all the apple stuff removed would do, not sure though.

The powerpc-small floppy target will probably not be on time. Jeremie is
working on the miboot upload, and once that reaches the archive, the
build system can be fixed.

power3 and power4/G5 kernels and initrd are not yet done, but i will
have a go at them this week, so hopefully that will be ok. Kernels for
G5 powerpmac have not been tested, despite my call for volunteer, but if
they don't work out, 2.6 kernels will be needed.

It needs linux-kernel-di support for the modules, which i hear is
problematic, and some volunteer to test them.

  Here is a short list of things that need to be done still before release:
 
 And an update, as if you can't read the top of TODO yourselves. :-)
 
  - partman
 - testing!
 - clean up lvmcfg UI issue
 - probably go for i386, powerpc; other arches unknown

I tested it on powerpc, altough couldn't do much tests. My disk has
vital information i cannot afford to loose. More to this in a separate
mail.

Friendly,

Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status update

[Denis Barbier]

On Mon, Mar 08, 2004 at 10:29:28PM -0500, Joey Hess wrote:
[...]
 The string freeze has not quite started, since a few strings were
 changed today. Hopefully we've seen the last of that

I also just rewrote most of the strings for the cdebconf text frontend.
They should certainly be reviewed by a native English speaker though,
one only has to commit changes in cdebconf-text-udeb.templates as usual,
and I will patch source files accordingly.

Denis


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status update

[Joey Hess]

Sven Luther wrote:
 chrp, chrp-rs6k and prep will be working this time around, i think
 everything is there, but i need to fiddle the build system for it still
 to build the initrd images, but i do this already by hand, and
 everything is in place for it. This would use the powerpc netboot
 initrd. 
 
 the cdrom initrd is too big though, i will not have time to fix the
 kernel for this, so maybe building a new specialized initrd image with
 all the apple stuff removed would do, not sure though.
 
 The powerpc-small floppy target will probably not be on time. Jeremie is
 working on the miboot upload, and once that reaches the archive, the
 build system can be fixed.
 
 power3 and power4/G5 kernels and initrd are not yet done, but i will
 have a go at them this week, so hopefully that will be ok. Kernels for
 G5 powerpmac have not been tested, despite my call for volunteer, but if
 they don't work out, 2.6 kernels will be needed.
 
 It needs linux-kernel-di support for the modules, which i hear is
 problematic, and some volunteer to test them.

Unless I see patches in the archive in the next day or two for the
above, I can't imagine you'll make it.

-- 
see shy jo


signature.asc
Description: Digital signature

Re: release status update (grub notes)

[Walter Tautz]

  - lowmem package must enter archive
  - Check archive for udebs that need to be built on various arches;
make sure everything is up-to-date. Also, make sure that eg,
appropriate kernel debs have entered the archive on each
architecture.

one thing I noticed with a recent daily build (March 3 I believe is
that the GRUB installer does NOT seem to offer the option of putting
in other bootable entries, much like the lilo installer in woody would
offer the user




  - Write a release announcement.

 --
 see shy jo



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Re: release status

[bornagain]

Peter Karbaliotis wrote:
 Joey Hess wrote:
  Thomas Poindessous wrote:
  
 On Fri, Mar 05, 2004 at 05:34:09PM -0900, Joey Hess wrote:
 
 Thomas Poindessous wrote:
 
 demo must be disabled in config/sparc.cfg. I took the right to do it in
 CVS.
 
 Hmm, that must make the debian-installer-demo package rather useless.
 
 yes, I didn't realize that, sorry :(
 
 
 What's the problem with building the demo?
 
 some variables used by pkg-list weren't defined, then no udeb was
 installed, and later building failed. I corrected that.
 
 I redid a test (not in pbuilder) and it does work. Maybe sparc can be
 added to Architectures line in debian/control ?
  
  
  I'd be glad to, if someone has managed a largely successful install on
  sparc too. Not sure if that has happened yet.
  
 
 Please see Bug #236364 for my sparc installation report (just made 
 yesterday).
 
 -- 
 [EMAIL PROTECTED] 780-492-7660
 Computing and Network ServicesUniversity of Alberta
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Re: release status

[bornagain]

Joey Hess wrote:
 Thomas Poindessous wrote:
  On Fri, Mar 05, 2004 at 05:34:09PM -0900, Joey Hess wrote:
   Thomas Poindessous wrote:
demo must be disabled in config/sparc.cfg. I took the right to do it in
CVS.
   
   Hmm, that must make the debian-installer-demo package rather useless.
  
  yes, I didn't realize that, sorry :(
  
   What's the problem with building the demo?
  
  some variables used by pkg-list weren't defined, then no udeb was
  installed, and later building failed. I corrected that.
  
  I redid a test (not in pbuilder) and it does work. Maybe sparc can be
  added to Architectures line in debian/control ?
 
 I'd be glad to, if someone has managed a largely successful install on
 sparc too. Not sure if that has happened yet.
 
 -- 
 see shy jo
 
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

release status update

[Joey Hess]

I wrote:
 We're still on track for release on the 15th. Here's a schedule up to
 then:
 
 March 3rd   No changes to libraries past this point.
 March 6th   Final code changes for i386 enter the archive.
   (except new udebs and possibly partman)
 March 7th   All udebs to be copied from unstable to testing.
 First possibly final i386 CDs built; testing.
 String freeze begins.
 March 10th  String feeeze ends.
 March 14th  Final changes to udebs in archive.
 Final image and CD builds.
 March 15thRelease.

We're about a day behind on this schedule at the moment. The set of
udebs in unstable was copied to testing on Saturday, which gives me
something to fall back on if changes unexpectedly break something. The
March 7th cd images were not final quality, due to some initrd bloating,
and some new stuff not getting on in time. It's possible that today or
tomorrow's images will be something close to final release quality for i386.

The string freeze has not quite started, since a few strings were
changed today. Hopefully we've seen the last of that, and at least the
translators are doing well, with several languages already at 100% and
many  90%. Also, the alioth move caused some problems. We'll push the 
end of the string freeze back to the 12th because of this late start.

The 14th is still the last day for changes to udebs, and the 13th is a
more practical deadline.

 Here, again is a checklist for what needs to be done for an architecture
 before release:
 
  1. CD images builds should be working (if applicable)

AFAIK, this is currently true for alpha, hppa, i386, ia64, and powerpc.
We need sparc and m68k CDs, I think work is in progress for m68k, but I
have heard nothing about sparc.

  2. images must be in debian archive

Currently it's a bit of a mess:

- i386 is ok
- sparc images autobuilt for the first time today. Good job guys!
- powerpc continues to build every time w/o fail.
- hppa failed to build due to a missing build dep; trying that again.
- ia64 failed to build due to external breakage; trying that again.
- m68k failed to build due to using the wrong kernel; trying that again.
- mips succeeded with the previous version 3 days ago, but has not
  started/finished the latest version.

It would help if more porters could watch
http://buildd.debian.org/build.php?arch=pkg=debian-installer and fix
problems as they show up. I appreciate those of you who do.

No other arches are being autobuilt at this time. If we want s390 or
something to be included in this release, it needs to be added to
debian/control ASAP.

  3. at least one successful installation report per boot method

I have not had time to track installation reports. Could someone take
a pass through the list of recent reports and post a summary to the list
please? My vague impressions:

- i386 is generally working ok
- powerpc is working ok the subarches that worked last time
- once again we are almost out of time on including any more powerpc
  subarches
- s390 is working up to partitioning, and that is probably the only
  serious issue there
- m68k is working on amiga
- mips ??? haven't seen anything lately
- hppa ??? no activity lately, probably won't release
- ia64 ???
- sparc is working, mostly. May have some bad debs in testing though.
- arm is being worked on, but will not make this release (prove me
  wrong, please)

 Here is a short list of things that need to be done still before release:

And an update, as if you can't read the top of TODO yourselves. :-)

 - partman
- testing!
- clean up lvmcfg UI issue
- probably go for i386, powerpc; other arches unknown
 - i18n:
- bterm-unifont reloading. Bug#232397
 - lowmem package must enter archive
 - Check archive for udebs that need to be built on various arches;
   make sure everything is up-to-date. Also, make sure that eg,
   appropriate kernel debs have entered the archive on each
   architecture.
 - Write a release announcement.

-- 
see shy jo


signature.asc
Description: Digital signature

Re: release status

[Joey Hess]

Thomas Poindessous wrote:
 On Fri, Mar 05, 2004 at 05:34:09PM -0900, Joey Hess wrote:
  Thomas Poindessous wrote:
   demo must be disabled in config/sparc.cfg. I took the right to do it in
   CVS.
  
  Hmm, that must make the debian-installer-demo package rather useless.
 
 yes, I didn't realize that, sorry :(
 
  What's the problem with building the demo?
 
 some variables used by pkg-list weren't defined, then no udeb was
 installed, and later building failed. I corrected that.
 
 I redid a test (not in pbuilder) and it does work. Maybe sparc can be
 added to Architectures line in debian/control ?

I'd be glad to, if someone has managed a largely successful install on
sparc too. Not sure if that has happened yet.

-- 
see shy jo


signature.asc
Description: Digital signature

Re: release status

[Peter Karbaliotis]

Joey Hess wrote:
Thomas Poindessous wrote:

On Fri, Mar 05, 2004 at 05:34:09PM -0900, Joey Hess wrote:

Thomas Poindessous wrote:

demo must be disabled in config/sparc.cfg. I took the right to do it in
CVS.
Hmm, that must make the debian-installer-demo package rather useless.
yes, I didn't realize that, sorry :(


What's the problem with building the demo?
some variables used by pkg-list weren't defined, then no udeb was
installed, and later building failed. I corrected that.
I redid a test (not in pbuilder) and it does work. Maybe sparc can be
added to Architectures line in debian/control ?


I'd be glad to, if someone has managed a largely successful install on
sparc too. Not sure if that has happened yet.
Please see Bug #236364 for my sparc installation report (just made 
yesterday).

--
[EMAIL PROTECTED]   780-492-7660
Computing and Network Services  University of Alberta
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: release status

[Joey Hess]

Peter Karbaliotis wrote:
 Please see Bug #236364 for my sparc installation report (just made 
 yesterday).

Looks like you're close..

-- 
see shy jo


signature.asc
Description: Digital signature

Re: release status

[Andrew Pollock]

On Thu, Mar 04, 2004 at 07:12:59PM -0500, Joey Hess wrote:
 
 I've uploaded a package with your patch.

I tested the daily build for 20040305, which included lvmcfg 0.17, and it
now works properly, lvm10 is installed on a system that uses LVM.

Thanks.

Andrew


signature.asc
Description: Digital signature

Re: release status

[Thomas Poindessous]

On Mon, Feb 23, 2004 at 06:05:25PM -0800, Jeff Bailey wrote:
 On Mon, Feb 23, 2004 at 08:39:23PM -0500, Joey Hess wrote:
 
   - Make sure the debian-installer package builds for your arch in a
 clean chroot, and let me know so I can add your architecture to the
 control file. Currently only i386, powerpc, mips, and ia64 are listed.
 
 I'll check this for sparc tomorrow.  

Hi,

since I didn't hear any reports about this, I did a check with pbuilder
and a sid environment.

debian-installer package for sparc will build, but with these changes :

demo must be disabled in config/sparc.cfg. I took the right to do it in
CVS.
I also did a copy of INSTALLATION-HOWTO in build/debian, but I'm sure
that I miss something in the build process.

If somebody can confirm this result, you may add sparc in
build/debian/control.

current build process :

cd build
cp ../doc/INSTALLATION-HOWTO debian/
dpkg-buildpackage -S
cd ..
sparc32 pbuilder build debian-installer_20040304.dsc


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]