Custom Search
|
Date: December 31, 2006
From: Vagrant Cascadian <vagrant@xxxxxxxxxxxx>
In-reply-to:
<33722.151.199.16.59.1167603004.squirrel@xxxxxxxxxxxxxxxx>
References:
<33722.151.199.16.59.1167603004.squirrel@xxxxxxxxxxxxxxxx>
On Sun, Dec 31, 2006 at 05:10:04PM -0500, lloyd@xxxxxxxxxxx wrote: > On Sun, Dec 31, 2006 at 01:39:08PM -0500, lloyd@xxxxxxxxxxx wrote: > > On Sat, December 30, 2006 7:10 pm, Vagrant Cascadian wrote: > >> Error: > > >> Installation proceeds to install of the base system; then we get the > >> following error: > > >> Debootstrap error > >> Invalid release file: no entry for local/binary-i386/Packages ...snip... > > you've tried with a fresh etch-simple-cdd bzr checkout and made > > absolutely no modifications, running "./build-simple-cdd" with no > > commandline options? on an up to date etch system? if so, i'm stumped, > > as that "works for me". i'm doing another try, just in case. well, it was a bug. thanks for reporting it. should be fixed in etch-simple-cdd bzr branch. update, and hopefully everything will go much more smoothly :) live well, vagrant
Date: December 31, 2006
From: lloyd@xxxxxxxxxxx
Hi Vagrant On Sun, Dec 31, 2006 at 01:39:08PM -0500, lloyd@xxxxxxxxxxx wrote: > On Sat, December 30, 2006 7:10 pm, Vagrant Cascadian wrote: >> Error: >> Installation proceeds to install of the base system; then we get the >> following error: >> Debootstrap error >> Invalid release file: no entry for local/binary-i386/Packages >> Neither LOCAL nor LOCALDEBS are in simple-cdd.conf. We manually added >> "export LOCAL=0" to simple-cdd.conf. But still got error. > is it set in /etc/debian-cd/CONF.sh or /usr/share/debian-cd/CONF.sh ? I'll take a look tomorrow. My son, who was doing the work, is headed back to grad school. > you've tried with a fresh etch-simple-cdd bzr checkout and made > absolutely no modifications, running "./build-simple-cdd" with no > commandline options? on an up to date etch system? if so, i'm stumped, ? as that "works for me". i'm doing another try, just in case. Yes, I believe it was the latest. But, again, I'll double-check all the work tomorrow and Tuesday. > oh, regarding irc clients, i prefer "irssi". if you prefer a GUI, maybe > try "xchat". there's *many* others to choose from. Thanks. I get that set up. Vagrant, have a wonderful holiday and outstanding new year. I much appreciate your guidance. All the best, Lloyd -- To UNSUBSCRIBE, email to debian-custom-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
Date: December 31, 2006
From: Vagrant Cascadian <vagrant@xxxxxxxxxxxx>
In-reply-to:
<33566.151.199.16.59.1167590348.squirrel@xxxxxxxxxxxxxxxx>
References:
<32944.151.199.16.59.1167519816.squirrel@xxxxxxxxxxxxxxxx> <20061231001058.GT30907@fgdefault
> <33566.151.199.16.59.1167590348.squirrel@xxxxxxxxxxxxxxxx>
On Sun, Dec 31, 2006 at 01:39:08PM -0500, lloyd@xxxxxxxxxxx wrote: > On Sat, December 30, 2006 7:10 pm, Vagrant Cascadian wrote: > Error: > > >> Installation proceeds to install of the base system; then we get the > >> following error: > > > >> Debootstrap error > >> Invalid release file: no entry for local/binary-i386/Packages > >> > > > hm. haven't seen that before. possibly some sort of misconfiguration with > > LOCAL and/or LOCALDEBS variables- are those specified in > > simple-cdd.conf ? > > Neither LOCAL nor LOCALDEBS are in simple-cdd.conf. We manually added > "export LOCAL=0" to simple-cdd.conf. But still got error. is it set in /etc/debian-cd/CONF.sh or /usr/share/debian-cd/CONF.sh ? > if using the defaults mirrorring tools(reprepro and > > wget), they shouldn't be- it's not needed. (though *maybe* something is > > broken with using --local-packages to add the simple-cdd-profiles .udeb) > > > > first thing i recommend trying is just building simple-cdd with all the > > defaults- no profiles or anything. > > Tried building with all defaults. Still got error. you've tried with a fresh etch-simple-cdd bzr checkout and made absolutely no modifications, running "./build-simple-cdd" with no commandline options? on an up to date etch system? if so, i'm stumped, as that "works for me". i'm doing another try, just in case. oh, regarding irc clients, i prefer "irssi". if you prefer a GUI, maybe try "xchat". there's *many* others to choose from. live well, vagrant
Date: December 31, 2006
From: lloyd@xxxxxxxxxxx
In-reply-to:
<20061231001058.GT30907@fgdefault
>
References:
<32944.151.199.16.59.1167519816.squirrel@xxxxxxxxxxxxxxxx> <20061231001058.GT30907@fgdefault
>
Hi, On Sat, December 30, 2006 7:10 pm, Vagrant Cascadian wrote: > please ask simple-cdd questions on the debian-custom list(no need to send > to me directly), so others can help (and learn from) the process :) Ok, thanks. Error: >> Installation proceeds to install of the base system; then we get the >> following error: > >> Debootstrap error >> Invalid release file: no entry for local/binary-i386/Packages >> > hm. haven't seen that before. possibly some sort of misconfiguration with > LOCAL and/or LOCALDEBS variables- are those specified in > simple-cdd.conf ? Neither LOCAL nor LOCALDEBS are in simple-cdd.conf. We manually added "export LOCAL=0" to simple-cdd.conf. But still got error. if using the defaults mirrorring tools(reprepro and > wget), they shouldn't be- it's not needed. (though *maybe* something is > broken with using --local-packages to add the simple-cdd-profiles .udeb) > > first thing i recommend trying is just building simple-cdd with all the > defaults- no profiles or anything. Tried building with all defaults. Still got error. and then add a profile with your > packages that are available from debian. This gave error. and then add custom packages, if > any. one step at a time. We don't have custom packages. We did get a working *.ISO by using debian-cd manually with the local mirror that simple-cdd generated. It loaded all of standard packages. > i'm often on irc in irc.debian.org #debian-custom channel, if you'd like > to discuss it there... I'm embarrassed to say that I've never used IRC. Can you recommend a client? My thanks for you help. Lloyd R. Prentice -- To UNSUBSCRIBE, email to debian-custom-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
Date: December 31, 2006
From: Vagrant Cascadian <vagrant@xxxxxxxxxxxx>
In-reply-to:
<32944.151.199.16.59.1167519816.squirrel@xxxxxxxxxxxxxxxx>
References:
<32944.151.199.16.59.1167519816.squirrel@xxxxxxxxxxxxxxxx>
please ask simple-cdd questions on the debian-custom list(no need to send to me directly), so others can help (and learn from) the process :) On Sat, Dec 30, 2006 at 06:03:36PM -0500, lloyd@xxxxxxxxxxx wrote: > Following your instructions, we created our first CDD *.ISO. > Installation went well until install of the base system. We got the > following error: > Debootstrap error > Invalid release file: no entry for local/binary-i386/Packages hm. haven't seen that before. possibly some sort of misconfiguration with LOCAL and/or LOCALDEBS variables- are those specified in simple-cdd.conf ? if using the defaults mirrorring tools(reprepro and wget), they shouldn't be- it's not needed. (though *maybe* something is broken with using --local-packages to add the simple-cdd-profiles .udeb) first thing i recommend trying is just building simple-cdd with all the defaults- no profiles or anything. and then add a profile with your packages that are available from debian. and then add custom packages, if any. one step at a time. i'm often on irc in irc.debian.org #debian-custom channel, if you'd like to discuss it there... live well, vagrant
Date: December 30, 2006
From: lloyd@xxxxxxxxxxx
Hi Vagrant, Following your instructions, we created our first CDD *.ISO. Installation went well until install of the base system. We got the following error: Debootstrap error Invalid release file: no entry for local/binary-i386/Packages Suggestions? Many thanks, Lloyd R. Prentice -- To UNSUBSCRIBE, email to debian-custom-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
Date: December 29, 2006
From: lloyd@xxxxxxxxxxx
Hi, On Fri, Dec 29, 2006 at 5:23:28PM -0500, vagrant@xxxxxxxxxxxx wrote: > please, test the etch version instead :) > just created a short howto from an earlier posting ot this list: > http://wiki.debian.org/Simple-CDD/Howto Outstanding! We've pretty much got things set up now to test. Should get into it tomorrow. I'll keep you posted. Much appreciate your help. Best wishes, Lloyd R. Prentice -- To UNSUBSCRIBE, email to debian-custom-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
Date: December 29, 2006
From: Otavio Salvador <otavio@xxxxxxxxxx>
In-reply-to:
<20061229203328.GQ30907@fgdefault
> (Vagrant Cascadian's message of "Fri, 29 Dec 2006 12:33:28 -0800")
References:
<20061229203328.GQ30907@fgdefault
>
Vagrant Cascadian <vagrant@xxxxxxxxxxxx> writes:
> hi, i would like to create a mailing list for simple-cdd development as
> part of the alioth cdd project(to facilitate group maintenance), since i
> am already hosting simple-cdd's bzr branches as part of the cdd project.
>
> otavio suggested adding me to the cdd admins. if "vagrant-guest" could
> be added to the alioth cdd project admins, i could make the request for
> the mailing list myself.
>
> or, if someone else wanted to create the list on my behalf, that would
> be fine with me too.
>
> "simple-cdd-devel" would probably be a good name for the list.
It can't be that name. It need to be: cdd-simple-cdd-devel or you'll
need to ask for a simple-cdd specific alioth project.
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: otavio@xxxxxxxxxx UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
Date: December 29, 2006
From: Vagrant Cascadian <vagrant@xxxxxxxxxxxx>
hi, i would like to create a mailing list for simple-cdd development as part of the alioth cdd project(to facilitate group maintenance), since i am already hosting simple-cdd's bzr branches as part of the cdd project. otavio suggested adding me to the cdd admins. if "vagrant-guest" could be added to the alioth cdd project admins, i could make the request for the mailing list myself. or, if someone else wanted to create the list on my behalf, that would be fine with me too. "simple-cdd-devel" would probably be a good name for the list. live well, vagrant
Date: December 29, 2006
From: Vagrant Cascadian <vagrant@xxxxxxxxxxxx>
In-reply-to:
<33526.151.199.16.59.1167409948.squirrel@xxxxxxxxxxxxxxxx>
References:
<33526.151.199.16.59.1167409948.squirrel@xxxxxxxxxxxxxxxx>
On Fri, Dec 29, 2006 at 11:32:28AM -0500, lloyd@xxxxxxxxxxx wrote: > Many thanks for your thoughtful reply. of course :) > Our first goal will be to create the simplest, plain-vanilla image we can > -- just to understand the process. that is an excellent way to go. > We've just down-loaded the Simple (sarge) package from the Debian > archives. Will study carefully and see what we come up with. please, test the etch version instead :) just created a short howto from an earlier posting ot this list: http://wiki.debian.org/Simple-CDD/Howto the sarge version, while it works with sarge, is kind of ugly, crude and hackish, and is prone to break. i think the etch-based version is much better. i'd rather get the etch version working well than support the sarge version at this point. live well, vagrant
Date: December 29, 2006
From: lloyd@xxxxxxxxxxx
Hi Vagrant, Many thanks for your thoughtful reply. Our first goal will be to create the simplest, plain-vanilla image we can -- just to understand the process. We've just down-loaded the Simple (sarge) package from the Debian archives. Will study carefully and see what we come up with. Thanks again, Lloyd -- To UNSUBSCRIBE, email to debian-custom-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
Date: December 29, 2006
From: Otavio Salvador <otavio@xxxxxxxxxx>
In-reply-to:
<20061229024040.GN30907@fgdefault
> (Vagrant Cascadian's message of "Thu, 28 Dec 2006 18:40:41 -0800")
References:
<32958.151.199.16.59.1167352134.squirrel@xxxxxxxxxxxxxxxx> <20061229024040.GN30907@fgdefault
>
Vagrant Cascadian <vagrant@xxxxxxxxxxxx> writes:
> unfortunately, simple-cdd wasn't ready to upload before the etch freeze,
> so will still be officially outside of debian for a while. i think it's
> (nearly) ready to upload now, if i can find a sponsor :)
Ping me when ready ;-)
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: otavio@xxxxxxxxxx UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
Date: December 29, 2006
From: Vagrant Cascadian <vagrant@xxxxxxxxxxxx>
In-reply-to:
<32958.151.199.16.59.1167352134.squirrel@xxxxxxxxxxxxxxxx>
References:
<32958.151.199.16.59.1167352134.squirrel@xxxxxxxxxxxxxxxx>
On Thu, Dec 28, 2006 at 07:28:54PM -0500, lloyd@xxxxxxxxxxx wrote: > As work in progress toward building the Debian Creative Arts Custom > Distribution, my son and I have studying the docs and have tried to work > through the Wiki tutorial. But a number of issues have stumped us: > As primary documentation we've been studying: > > a) -- http://wiki.debian.org/CustomDebian > b) -- http://wiki.debian.org/DebianCustomCD > c) -- http://wiki.debian.org/Simple-CDD ...snip... > 1) The documentation pulls us in divergent directions; has left us quite > baffled. > There seem to be several methods for building CDDS: e.g. b,c,e. yes, there are several different methods. while there may be commonalities between different CDDs, there are also differing needs for the target audience of the CDD, and different skill-sets of the people deeloping the CDD. apparently, nobody has produced the perfect suite of CDD related software. :) to make things a little more confusing, some also may also technically be more of a Debian Derived Distribution(DDD), if they choose to include components or use tools outside of Debian itself. and some projects may have the goal of being a "True" CDD, though have been unable to integrate all of their changes directly into Debian. a CDD is something entirely within Debian, though the tools for creating CDDs and DDDs tend to be very similar, if not identical. i will address the features of simple-cdd, as i wrote it and am aware of it's strengths and weaknesses. > -- in the above documentation, what should we study most carefully? > -- are there any documentation sources that we're over-looking? > -- are the documentation sources accurate and up-to-date? simple-cdd documentation needs a fair amount of work, and to be updated for etch. but the basic use of simple-cdd is, well... pretty simple, so it shouldn't be too hard to update the documentation :) > -- how should we select the most appropriate method? it really depends on what your needs are, and what seems to work for you. defining clearly exactly what you want will probably help determine which documentation and tools would be most appropriate. > -- What are the differences between the methods? > -- What are the relative benefits of one method over another, etc. simple-cdd allows you to specify a list of packages to install, pre-answer debconf questions, and takes that information and generates a CD image that will install those packages. it is possible to create several profiles that can be selected at install time, each with different package sets, debconf questions, etc. if all the software you want as part of your CDD is part of etch, simple-cdd should be able to generate a CD image without a lot of trouble. if you want some additional packages outside of debian, it is also possible, though maybe more work. if all you want is to select which packages to install, using simple-cdd should be as easy as providing a list of packages you want installed and using simple-cdd to generate a CD image. > a) Build the debian-installer and move it to an appropriate directory > b) Configure debian-cd > c) Generate the CD with simple-cdd you shouldn't have to generate a debian-installer image for most cases(it uses the debian-installer binaries built for Debian), and it handles the debian-cd configuration and CD generation. > Our confusion starts once we get past this superficial level; e.g.... > > 3) How do we specify which packages to install? in simple-cdd, you define this by providing a list of packages to install in a text file, one package per line. if you want multiple profiles(a.k.a. variants), you provide a list of packages for each profile. > -- do we have to specify every single package down through the base > system, or just the packages that we want to show up in the menus? in simple-cdd, you usually only have to specify what packages you want, and simple-cdd will make sure the dependencies will be included on the CD. > Our understanding is that we need to build meta-packages. But you don't need to use meta-packages with simple-cdd, but it would be useful to create meta-packages if you wanted to make it possible to provide an upgrade mechanism if you later change your mind about what software should be included as part of your CDD- simple-cdd (currenly) only handles installation, not upgrading. > 4) We'd really like to build from etch. But most of the docs seem to > address Sarge. Is it premature to build from etch? What are the > differences? there's been recent work to get simple-cdd working with etch, and i have sucessfully produced some etch CD images using it. unfortunately, simple-cdd wasn't ready to upload before the etch freeze, so will still be officially outside of debian for a while. i think it's (nearly) ready to upload now, if i can find a sponsor :) good luck with your work. live well, vagrant
Date: December 29, 2006
From: lloyd@xxxxxxxxxxx
Hello, As work in progress toward building the Debian Creative Arts Custom Distribution, my son and I have studying the docs and have tried to work through the Wiki tutorial. But a number of issues have stumped us: As primary documentation we've been studying: a) -- http://wiki.debian.org/CustomDebian b) -- http://wiki.debian.org/DebianCustomCD c) -- http://wiki.debian.org/Simple-CDD d) -- http://people.debian.org/~tille/debian-med/talks/paper-cdd/debian-cdd.html/ e) -- examples files in cdd-dev f) -- cdd-common files g) -- http://wiki.debian.org/DebianInstaller h) -- Martin Krafft's The Debian System: Concepts and Techniques 1) The documentation pulls us in divergent directions; has left us quite baffled. There seem to be several methods for building CDDS: e.g. b,c,e. -- in the above documentation, what should we study most carefully? -- are there any documentation sources that we're over-looking? -- are the documentation sources accurate and up-to-date? -- how should we select the most appropriate method? -- What are the differences between the methods? -- What are the relative benefits of one method over another, etc. 2) The documentation seems to address very high-level concepts and (some) very low-level how-to concepts, but give us very little understanding of what we're doing or why and the appropriate sequence. As we undertand it, there are three major steps: a) Build the debian-installer and move it to an appropriate directory b) Configure debian-cd c) Generate the CD Our confusion starts once we get past this superficial level; e.g.... 3) How do we specify which packages to install? -- do we have to specify every single package down through the base system, or just the packages that we want to show up in the menus? Our understanding is that we need to build meta-packages. But -- where do we start? How do we do this? cdd-dev provides a directory and file template but we can't find (or maybe just don't understand) documentation of how to use these templates. -- Are these the meta packages? -- What do we need to do before we create the templates? -- What do we do after we've created them? 4) We'd really like to build from etch. But most of the docs seem to address Sarge. Is it premature to build from etch? What are the differences? I hope our ignorance is not off-putting. We really want to understand how to do this and are willing to work at it. If nothing else, I hope our naive questions will help clarify and improve the documentation. We look forward to your guidance. Many thanks, Lloyd R. Prentice -- To UNSUBSCRIBE, email to debian-custom-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
Date: December 29, 2006
From: Petter Reinholdtsen <pere@xxxxxxxxxx>
In-reply-to:
<33336.151.199.16.59.1167327420.squirrel@xxxxxxxxxxxxxxxx>
References:
<33336.151.199.16.59.1167327420.squirrel@xxxxxxxxxxxxxxxx>
[Lloyd R. Prentice] > The tools should as easy to learn and use as possible. > > Suggestions? Two suggestions: kaffeine for playing media files and audacity for sound editing. Friendly, -- Petter Reinholdtsen
Date: December 28, 2006
From: lloyd@xxxxxxxxxxx
Hi, I'm continuing to evaluate packages for the Debian Creative Arts Custom CD. I've rounded up an outstanding suite of software for the visual and literary arts. But I have no experience with sound; would welcome recommendations. I'm assuming that the users will have minimal technical skills. Would like to provide a well-integrated set of sound tools and utilities that would enable the user to: 1) Play a dvd 2) Play a cd 3) Record live narration, dialog, and music 4) Record sound from recorded sources 5) Synthesize a music track 6) Mix a sound track 7) Edit a sound track 8) Write a sound track to cd In other words, just enough to play a favorite music cd, movie dvd, produce an amateur music cd, sound-effects track for a community theater, or simple sound track for a slide-show or animation. The tools should as easy to learn and use as possible. Suggestions? Many thanks, Lloyd R. Prentice -- To UNSUBSCRIBE, email to debian-custom-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
Date: December 21, 2006
From: "Daniel Andrade" <daniacs@xxxxxxxxx>
In-reply-to:
<302a894a0612210306o4955e7l47b2ccb308ad8846@xxxxxxxxxxxxxx>
References:
<302a894a0612150239x117ce17qbfe941f962aa7b11@xxxxxxxxxxxxxx> <200612151220.51388.elendil@xxxxxxxxx> <302a894a0612210306o4955e7l47b2ccb308ad8846@xxxxxxxxxxxxxx>
On 12/21/06, Daniel Andrade <daniacs@xxxxxxxxx> wrote:
On 12/15/06, Frans Pop <elendil@xxxxxxxxx> wrote: > Please do not cross-post questions. Frans, what would be "cross-post questions"? Whatever it is, sorry if it's not "allowed" in debian lists in general... > On Friday 15 December 2006 11:39, Daniel Andrade wrote: > > "No installable kernel was found in the defined APT sources. > > bla bla bla bla... > > Continue without installing a kernel?" > > You can easily debug this yourself. Some hints: > - check the installer's /var/log/syslog to get an indication of what goes > wrong. There are quite a few messages about the kernel selection > process. - There were messages like [pre-]dependency problems, but i also noticed it on current official etch image. So, that's probably not the problem... - - - - - - - - Dec 20 12:46:23 debootstrap: Unpacking base-passwd (from .../base-passwd_3.5.11_ i386.deb) ... Dec 20 12:46:23 debootstrap: dpkg: base-passwd: dependency problems, but configuring anyway as you request: Dec 20 12:46:23 debootstrap: base-passwd depends on libc6 (>= 2.3.5-1); however: Dec 20 12:46:23 debootstrap: Package libc6 is not installed. - - - - - - - -
Frans, I don't know why the hell, I just removed the Releases.gpg file and everything worked fine.... does anyone know what happened???? o.O
- There were some warnings, just after the identification of CD label (these warnings are not in etch official image)... seems like it is searching for packages which do not exist. I think that is happening cause the file Release in my local mirror makes references to all architectures (alpha, arm, etc) while there are only references to i386 architecture in official CD. But I also believe that is not really the problem, or another packages would not be installed too... - - - - - - - - Dec 20 12:48:52 base-installer: This disc is called: Dec 20 12:48:52 base-installer: 'Debian GNU/Linux 3.2-ceflinux _Etch_ - Unofficial i386 Binary-1 (20061220)' Dec 20 12:48:52 base-installer: Copying package lists... Dec 20 12:48:52 base-installer: gpgv: Dec 20 12:48:52 base-installer: Signature made Fri Dec 15 20:09:20 2006 UTC using DSA key ID 2D230C5F Dec 20 12:48:52 base-installer: gpgv: Dec 20 12:48:52 base-installer: Good signature from "Debian Archive Automatic Signing Key (2006) <ftpmaster@xxxxxxxxxx>" Dec 20 12:48:52 base-installer: Dec 20 12:48:52 base-installer: gpgv: Dec 20 12:48:52 base-installer: Signature made Fri Dec 15 20:09:20 2006 UTC using DSA key ID 6070D3A1 Dec 20 12:48:52 base-installer: gpgv: Dec 20 12:48:52 base-installer: Good signature from "Debian Archive Automatic Signing Key (4.0/etch) <ftpmaster@xxxxxxxxxx>" Dec 20 12:48:52 base-installer: Dec 20 12:48:56 base-installer: E: Dec 20 12:48:56 base-installer: Could not open file /cdrom/dists/etch-secured/contrib/binary-alpha/Packages - open (2 No such file or directory) Dec 20 12:48:56 base-installer: Dec 20 12:48:56 base-installer: E: Dec 20 12:48:56 base-installer: Unable to determine the file size - fstat (9 Bad file descriptor) ... and goes on and on until all architectures and sections are walked through.... - - - - - - - - - It is also saying packages locales and console-tools are not available. However, their entries are present in dists/etch/main/binary-i386/Packages (and Packages.gz) and their path are consistent with the pool directory.... =( - - - - - - - - Dec 20 12:48:57 apt-install: Reading package lists... Dec 20 12:48:57 apt-install: Building dependency tree... Dec 20 12:48:57 apt-install: Package locales is not available, but is referred to by another package. Dec 20 12:48:57 apt-install: This may mean that the package is missing, has been obsoleted, or Dec 20 12:48:57 apt-install: is only available from another source Dec 20 12:48:57 apt-install: E: Package locales has no installation candidate Dec 20 12:48:57 root: register-modules Dec 20 12:48:57 apt-install: Reading package lists... Dec 20 12:48:57 apt-install: Building dependency tree... Dec 20 12:48:57 apt-install: Package console-tools is not available, but is referred to by another package. Dec 20 12:48:57 apt-install: This may mean that the package is missing, has been obsoleted, or Dec 20 12:48:57 apt-install: is only available from another source Dec 20 12:48:57 apt-install: E: Package console-tools has no installation candidate - - - - - - - - - And the last "weird" message is the following, which do not find any linux-images.. Possibly because of some previous error... - - - - - - - - Dec 20 12:48:57 base-installer: chroot: cannot execute install-keymap: No such file or directory Dec 20 12:48:57 apt-install: Reading package lists... Dec 20 12:48:57 apt-install: Building dependency tree... Dec 20 12:48:57 apt-install: E: Couldn't find package installation-report Dec 20 12:48:57 base-installer: info: Found kernels '' - - - - - - - - I tried to chroot /target when the message of missing kernels "popped up"... There was no entries in /etc/apt/sources.list... Well.... if there is something i should do and didn't, i really don't know.... =( Was someone successful in building an etch CD??? Really thanks.... > - 'chroot /target' and run aptitude to see if your kernels are actually > available > - try running the installer in expert mode and see what you are offered. > - try running base-installation with set -x in > /var/lib/dpkg/info/base-installer.postinst > > Cheers, > FJP > > > -- Daniel Analista e Consultor Linux GISUT/BH - Caixa Econômica Federal (Connectcom) UFMG (Ciência da Computação) - 7°/8° períodos
-- Daniel Analista e Consultor Linux GISUT/BH - Caixa Econômica Federal (Connectcom) UFMG (Ciência da Computação) - 7°/8° períodos
Date: December 21, 2006
From: "Daniel Andrade" <daniacs@xxxxxxxxx>
In-reply-to:
<200612151220.51388.elendil@xxxxxxxxx>
References:
<302a894a0612150239x117ce17qbfe941f962aa7b11@xxxxxxxxxxxxxx> <200612151220.51388.elendil@xxxxxxxxx>
On 12/15/06, Frans Pop <elendil@xxxxxxxxx> wrote:
Please do not cross-post questions.
Frans, what would be "cross-post questions"? Whatever it is, sorry if it's not "allowed" in debian lists in general...
On Friday 15 December 2006 11:39, Daniel Andrade wrote: > "No installable kernel was found in the defined APT sources. > bla bla bla bla... > Continue without installing a kernel?" You can easily debug this yourself. Some hints: - check the installer's /var/log/syslog to get an indication of what goes wrong. There are quite a few messages about the kernel selection process.
- There were messages like [pre-]dependency problems, but i also noticed it on current official etch image. So, that's probably not the problem... - - - - - - - - Dec 20 12:46:23 debootstrap: Unpacking base-passwd (from .../base-passwd_3.5.11_ i386.deb) ... Dec 20 12:46:23 debootstrap: dpkg: base-passwd: dependency problems, but configuring anyway as you request: Dec 20 12:46:23 debootstrap: base-passwd depends on libc6 (>= 2.3.5-1); however: Dec 20 12:46:23 debootstrap: Package libc6 is not installed. - - - - - - - - - There were some warnings, just after the identification of CD label (these warnings are not in etch official image)... seems like it is searching for packages which do not exist. I think that is happening cause the file Release in my local mirror makes references to all architectures (alpha, arm, etc) while there are only references to i386 architecture in official CD. But I also believe that is not really the problem, or another packages would not be installed too... - - - - - - - - Dec 20 12:48:52 base-installer: This disc is called: Dec 20 12:48:52 base-installer: 'Debian GNU/Linux 3.2-ceflinux _Etch_ - Unofficial i386 Binary-1 (20061220)' Dec 20 12:48:52 base-installer: Copying package lists... Dec 20 12:48:52 base-installer: gpgv: Dec 20 12:48:52 base-installer: Signature made Fri Dec 15 20:09:20 2006 UTC using DSA key ID 2D230C5F Dec 20 12:48:52 base-installer: gpgv: Dec 20 12:48:52 base-installer: Good signature from "Debian Archive Automatic Signing Key (2006) <ftpmaster@xxxxxxxxxx>" Dec 20 12:48:52 base-installer: Dec 20 12:48:52 base-installer: gpgv: Dec 20 12:48:52 base-installer: Signature made Fri Dec 15 20:09:20 2006 UTC using DSA key ID 6070D3A1 Dec 20 12:48:52 base-installer: gpgv: Dec 20 12:48:52 base-installer: Good signature from "Debian Archive Automatic Signing Key (4.0/etch) <ftpmaster@xxxxxxxxxx>" Dec 20 12:48:52 base-installer: Dec 20 12:48:56 base-installer: E: Dec 20 12:48:56 base-installer: Could not open file /cdrom/dists/etch-secured/contrib/binary-alpha/Packages - open (2 No such file or directory) Dec 20 12:48:56 base-installer: Dec 20 12:48:56 base-installer: E: Dec 20 12:48:56 base-installer: Unable to determine the file size - fstat (9 Bad file descriptor) ... and goes on and on until all architectures and sections are walked through.... - - - - - - - - - It is also saying packages locales and console-tools are not available. However, their entries are present in dists/etch/main/binary-i386/Packages (and Packages.gz) and their path are consistent with the pool directory.... =( - - - - - - - - Dec 20 12:48:57 apt-install: Reading package lists... Dec 20 12:48:57 apt-install: Building dependency tree... Dec 20 12:48:57 apt-install: Package locales is not available, but is referred to by another package. Dec 20 12:48:57 apt-install: This may mean that the package is missing, has been obsoleted, or Dec 20 12:48:57 apt-install: is only available from another source Dec 20 12:48:57 apt-install: E: Package locales has no installation candidate Dec 20 12:48:57 root: register-modules Dec 20 12:48:57 apt-install: Reading package lists... Dec 20 12:48:57 apt-install: Building dependency tree... Dec 20 12:48:57 apt-install: Package console-tools is not available, but is referred to by another package. Dec 20 12:48:57 apt-install: This may mean that the package is missing, has been obsoleted, or Dec 20 12:48:57 apt-install: is only available from another source Dec 20 12:48:57 apt-install: E: Package console-tools has no installation candidate - - - - - - - - - And the last "weird" message is the following, which do not find any linux-images.. Possibly because of some previous error... - - - - - - - - Dec 20 12:48:57 base-installer: chroot: cannot execute install-keymap: No such file or directory Dec 20 12:48:57 apt-install: Reading package lists... Dec 20 12:48:57 apt-install: Building dependency tree... Dec 20 12:48:57 apt-install: E: Couldn't find package installation-report Dec 20 12:48:57 base-installer: info: Found kernels '' - - - - - - - - I tried to chroot /target when the message of missing kernels "popped up"... There was no entries in /etc/apt/sources.list... Well.... if there is something i should do and didn't, i really don't know.... =( Was someone successful in building an etch CD??? Really thanks....
- 'chroot /target' and run aptitude to see if your kernels are actually available - try running the installer in expert mode and see what you are offered. - try running base-installation with set -x in /var/lib/dpkg/info/base-installer.postinst Cheers, FJP
-- Daniel Analista e Consultor Linux GISUT/BH - Caixa Econômica Federal (Connectcom) UFMG (Ciência da Computação) - 7°/8° períodos
Date: December 18, 2006
From: philagui <khaeos@xxxxxxxxxx>
Hi, I've successfully built a Custom Debian Distribution with debian-cd, using the method described here: http://wiki.debian.org/DebianCustomCD But now the distribution is getting bigger and I have to put it on 2 cds. I have a problem though, when debian-cd generates 2 cds. My installation is preseeded and at the end of it, I'm installing automatically some custom packages. Now that I have 2 cds, one of the custom packages is on cd2, and when, at the end of the installation, the script tries to install this specific package, it fails and does not find it. Is there a way to prevent this, so that for example when I try to install a package that is on cd2, it automatically asks the user to insert cd2 ? Thank you for your help. -- View this message in context: http://www.nabble.com/CDD-with-multiple-CDs-tf2839609.html#a7927981 Sent from the debian-custom mailing list archive at Nabble.com.
Date: December 15, 2006
From: Frans Pop <elendil@xxxxxxxxx>
In-reply-to:
<302a894a0612150239x117ce17qbfe941f962aa7b11@xxxxxxxxxxxxxx>
References:
<302a894a0612150239x117ce17qbfe941f962aa7b11@xxxxxxxxxxxxxx>
Please do not cross-post questions. On Friday 15 December 2006 11:39, Daniel Andrade wrote: > "No installable kernel was found in the defined APT sources. > bla bla bla bla... > Continue without installing a kernel?" You can easily debug this yourself. Some hints: - check the installer's /var/log/syslog to get an indication of what goes wrong. There are quite a few messages about the kernel selection process. - 'chroot /target' and run aptitude to see if your kernels are actually available - try running the installer in expert mode and see what you are offered. - try running base-installation with set -x in /var/lib/dpkg/info/base-installer.postinst Cheers, FJP
pgpLhbxxl90QT.pgp
Description: PGP signature
Date: December 15, 2006
From: "Daniel Andrade" <daniacs@xxxxxxxxx>
I'm trying to build an etch CD... Everything goes perfect (at least it seems to).. I'm taking the following steps: 1) Build the debian-installer and moves it to $MIRROR/dists/etch/main/installer-i386 2) Configure debian-cd 3) Generate the CD But when I install it, it says "No installable kernel was found in the defined APT sources. bla bla bla bla... Continue without installing a kernel?" I don't know if the problem is related to debian-installer building or debian-cd configuration On debian-cd, my kernel-task file (similar to debian-installer+kernel-etch task file) has the following entries ... grub lilo linux-image-2.6-486 linux-image-2.6.17-2-486 linux-headers-2.6.17-2 linux-headers-2.6-486 It creates the binary image successfully... taking a look at $CDROM/dists/etch/main/binary- i386/Packages (and also on Packages.gz), I have the following entries (got it with the command => "zcat Packages.gz | sed '/^Package: \|^Filename/!d' | grep linux-" ) Package: linux-headers-2.6.17-2 Filename: pool/main/l/linux-2.6/linux-headers-2.6.17-2_2.6.17-9_i386.deb Package: linux-headers-2.6.17-2-486 Filename: pool/main/l/linux-2.6/linux-headers-2.6.17-2-486_2.6.17-9_i386.deb Package: linux-headers-2.6-486 Filename: pool/main/l/linux-latest-2.6/linux-headers-2.6-486_2.6.17+2_i386.deb Package: linux-image-2.6.17-2-486 Filename: pool/main/l/linux-2.6/linux-image-2.6.17-2-486_2.6.17-9_i386.deb Package: linux-image-2.6-486 Filename: pool/main/l/linux-latest-2.6/linux-image-2.6-486_2.6.17+2_i386.deb Package: linux-image-486 Filename: pool/main/l/linux-latest-2.6/linux-image-486_2.6.17+2_i386.deb Package: linux-kbuild-2.6.17 Filename: pool/main/l/linux-kbuild-2.6/linux-kbuild-2.6.17_2.6.17-3_i386.deb Now I just took a look on the pool directory just to make sure all the files were there and yes, everything was there... Anyone have an idea of what can be happening? I believe it can probably be something wrong with debian-installer, not with debian-cd... Anyway... Thanks for the attention... =) -- Daniel Analista e Consultor Linux GISUT/BH - Caixa Econômica Federal (Connectcom) UFMG (Ciência da Computação) - 8° período
Date: December 09, 2006
From: "Wat Day" <lkgwz@xxxxxxxxxxxx>
Hi everybody,here's another contribution for the logo discussion. Advanced Editing Showcase Ideas - SubPages Ideas - Metadata Enhancement Request for VotePluginJSPWiki Hot Problems! Site support recommended I use the "Tomcat Web Application Manager" to download the JSPWiki. Then you could edit as you please and submit in the standard used by the underlying engine. There were both left hand drive and right hand drive versions of this model which had steering controlled by the roof mounted tyre Cost Unknown and available in orange finish at Unknown scale. ;;;;; Trade Date : Monday, December 11, 2006 Name : Amerossi International T i c k e r : A M S N Price : $0.0006 SHORT TERM 1 DAY PROJECTION : $0.006 - $0.007 Expectations : 5(5) ;;;;; Here's a logo rendered with a pinhole camera during a solar eclipse. Iproperly configured jspwiki. JSPWiki: Adie Wiki.
During the performance, the whale grabbed the trainer's leg in its mouth and pulled him underwater for about a minute. But look at RecentChanges, and see that it states the author is joeuser but it's not linked to the Joeuser page. If anyone has input into a better wiki than JSP- or X-, please let me know. The Korean company has contacted MGM Studios as a possible creative partner for the project. I believe that it also signifies "opportunity". Move over Jaws, chomping sea lion terrorizes swimmers - CNN. With the above, you can remove any reference to the home page you may have in the LeftMenu, and add a link to SystemInfo to replace the original one that was at the top. Flash newsThere is something strange going on which causes JSPWiki. But look at RecentChanges, and see that it states the author is joeuser but it's not linked to the Joeuser page. If there was a Java version of Twiki that behaved like this, that would be great. Maine also denied label applications for Les Sans Culottes, a French ale, and Rose de Gambrinus, a Belgian fruit beer. When the system creates a new page, it is the owner and by default does not provide write access to anyone else. See more Florida theme park deals. In years past, the company has had labels challenged in a few states, including Ohio, North Carolina and Missouri, he said. and the sharp W lines are too nervous with the nice, round framing. One is the logo for Weiring Software, which can't be inlined because it is a gif. Stuff is linked implicitly; you don't have to bracket anything. There is also a TODO list, and a list of recent News. There are several variations. dir", "read"; permission java. The constant they have to deal with is the metallic clang of a pile driver sinking columns for a new campus building. Crying doll gives teen parenting, driving lesson - CNN. Go ahead, add your reasons to this. org, then the answer is simple: don't forget to set up the virtualhosts on Tomcat as well. com to webhost my JSPWiki. What makes JSPWiki special among them? It has nothing to do with JSPWiki. Hi everybody,here's another contribution for the logo discussion. If anyone has input into a better wiki than JSP- or X-, please let me know. The Chicago-area park will present an action-packed, original presentation called "Operation SpyGirl. Go ahead, add your reasons to this. Sea lions accustomed to the easy pickings of seafood scraps in popular fishing areas can become aggressive toward people if they fear their food is about to be taken away, Oswald said. Is there any idea whats going wrong here ? oldI don't remember exactly why - I think it was due to dependencies I was not able to resolve at the time. With black interior and roof panel fitted with Whizzwheels. Read more about the Silver Rapids indoor water park. Are you sure that you have Created the proper directories Unzipped the WAR file? Move over Jaws, chomping sea lion terrorizes swimmers - CNN. But look at RecentChanges, and see that it states the author is joeuser but it's not linked to the Joeuser page. The label for the English-made Santa's Butt Winter Porter features a rear view of a beer-drinking Santa Claus sitting atop a barrel. Actually XWiki is much more than a wiki, you're right, but the idea is to apply the wiki approach to other domains. Then you could edit as you please and submit in the standard used by the underlying engine. Below is a list of possible areas of interest, or feel free to use our Search feature at the top of the page to search by keyword or topic. I, personally, would much rather see an abstract logo, or a text logo without JSP. This Chinese character is just a guy's sirname. These are two Chinese characters which makes a word meaning "crisis". I came across the ideogram for "crisis", of which this graphic is the first character. So far park rangers have not been able to track the attacker down. He drove the car seven days a week, racking up the miles as his work took him through rural Wisconsin. In addition to the plethora of indoor water parks at hotels and theme parks, there is a trend to build the parks at ski resorts. The error I get says "please check the log files". JSPWiki: Why Choose JSP Wiki Wiki. There is also a TODO list, and a list of recent News. Maine also denied label applications for Les Sans Culottes, a French ale, and Rose de Gambrinus, a Belgian fruit beer. The lawsuit was brought by the Maine Civil Liberties Union, which says the beer labels are entitled to First Amendment protection.
Date: December 04, 2006
From: Vagrant Cascadian <vagrant@xxxxxxxxxxxx>
In-reply-to:
<5fabd6fd0612041342u3b884f46s3fec1c44c32bec4e@xxxxxxxxxxxxxx>
References:
<20061202035534.GQ15463@fgdefault
> <5fabd6fd0612041342u3b884f46s3fec1c44c32bec4e@xxxxxxxxxxxxxx>
On Mon, Dec 04, 2006 at 07:42:04PM -0200, Gustavo Franco wrote: > On 12/2/06, Vagrant Cascadian <vagrant@xxxxxxxxxxxx> wrote: ...snip... > >hopefully, with a little more testing, we will see an upload to debian > >soon. > > Let us make clear that it seems that we've missed the Etch boat, but > stuff will be pretty much in a better shape for Lenny if us keep the > work. I'll do my best, and i need to (really). right. though i plan to keep simple-cdd backportable to etch, or maintain a backported branch for as long as reasonably possible. ...snip... > >feedback would definitely be appreciated. if you want to give it a try, > >on an etch system: > > There's a new donut for you in my branch (the splashpng stuff). I'll > add some more minor changes after i bring back my test system, > hopefully sometime soon this week. merged. > >there's a few changes i'd like to finish soon, mentioned in the TODO > >file. > > There's one we've ignored that is related with the default profiles > that are in our bzr branches. I've 3 profiles and of course almost all > the packages i need are listed into default.packages. You've some > profiles and just a few stuff on default.packages. Shouldn't we change > how the 'default' profile stuff works? I think it's better let the > user define if he's using a alternate 'default', got it? That way we > both can keep our default* stuff. Thoughts? ah, yes. this is a good idea. i wanted to keep the "default" profile handling as similar to other profiles as possible, with the main difference being that the default profile always gets installed- this is why there isn't much in the default profile. you might be able to get what you need by creating a simple-cdd.conf, and profiles directory, building and installing the simple-cdd package, and running /usr/share/simple-cdd/build-simple-cdd from the directory simple-cdd.conf is in, and replace the profiles/default.* with your preferred defaults. build-simple-cdd will grab anything missing from /usr/share/simple-cdd/ when run this way. i'm open to ideas and patches of other ways to handle this, though. live well, vagrant
Date: December 04, 2006
From: "Gustavo Franco" <stratus@xxxxxxxxxx>
In-reply-to:
<20061202035534.GQ15463@fgdefault
>
References:
<20061202035534.GQ15463@fgdefault
>
On 12/2/06, Vagrant Cascadian <vagrant@xxxxxxxxxxxx> wrote:
i am very happy to annouce that a version of simple-cdd that works with etch is nearly finished. i've tested it using debian-installe RC1, and it seems to be working fine. http://wiki.debian.org/Simple-CDD many thanks to Gustavo Franco (a.k.a. stratus) for doing much of the work to get simple-cdd back in shape. thanks also to Frans Pop for help troubleshooting debian-installer issues.
You're welcome Vagrant. Thanks for the help and motivation too!
hopefully, with a little more testing, we will see an upload to debian soon.
Let us make clear that it seems that we've missed the Etch boat, but stuff will be pretty much in a better shape for Lenny if us keep the work. I'll do my best, and i need to (really).
the major new change (since the sarge-oriented version) is that it uses a .udeb to integrate into debian-installer. this udeb is simply a skeletal infrastructure for a CDD to select packages for installation, do debconf preseeding/preconfiguration, and run custom post-install scripts. you can define several profiles, with different package/preseeding/post-install sets and select them at install time.
I simply love that. :)
feedback would definitely be appreciated. if you want to give it a try, on an etch system:
There's a new donut for you in my branch (the splashpng stuff). I'll add some more minor changes after i bring back my test system, hopefully sometime soon this week.
(...) there's a few changes i'd like to finish soon, mentioned in the TODO file.
There's one we've ignored that is related with the default profiles that are in our bzr branches. I've 3 profiles and of course almost all the packages i need are listed into default.packages. You've some profiles and just a few stuff on default.packages. Shouldn't we change how the 'default' profile stuff works? I think it's better let the user define if he's using a alternate 'default', got it? That way we both can keep our default* stuff. Thoughts? regards, -- stratus
Date: December 02, 2006
From: Vagrant Cascadian <vagrant@xxxxxxxxxxxx>
i am very happy to annouce that a version of simple-cdd that works with etch is nearly finished. i've tested it using debian-installe RC1, and it seems to be working fine. http://wiki.debian.org/Simple-CDD many thanks to Gustavo Franco (a.k.a. stratus) for doing much of the work to get simple-cdd back in shape. thanks also to Frans Pop for help troubleshooting debian-installer issues. hopefully, with a little more testing, we will see an upload to debian soon. the major new change (since the sarge-oriented version) is that it uses a .udeb to integrate into debian-installer. this udeb is simply a skeletal infrastructure for a CDD to select packages for installation, do debconf preseeding/preconfiguration, and run custom post-install scripts. you can define several profiles, with different package/preseeding/post-install sets and select them at install time. feedback would definitely be appreciated. if you want to give it a try, on an etch system: apt-get install bzr rsync debian-cd reprepro apt-utils wget debhelper cdbs libdebian-installer4-dev libdebconfclient0-dev bzr get http://cdd.alioth.debian.org/bzr/simple-cdd/etch-simple-cdd cd etch-simple-cdd create a profile named NAME: echo list of packages you want installed > profiles/NAME.packages for debconf preseeding, put a debconf-set-selections compatible file into profiles/NAME.preseed for a custom post-install script, place it in profiles/NAME.postinst debuild -us -uc -I.bzr -b (to build the .udeb) ./build-simple-cdd --profiles NAME --local-packages ../simple-cdd-profiles_0.3.0~1_all.udeb this will create a partial package mirror in the dir "mirror", and if all goes well, an .iso file in the "images" dir. (alternately, use ./qemu-test instead of ./build-simple-cdd, which will call build-simple-cdd and attempt to boot the CD with qemu) try "./build-simple-cdd --help" for more options there's a few changes i'd like to finish soon, mentioned in the TODO file. live well, vagrant