Bug#825840: localechooser: image display inverts red and blue color
On Fri, Sep 2, 2016 at 9:28 PM, Ben Hutchings wrote: > Control: tag -1 moreinfo > > On Fri, 2016-09-02 at 20:56 +0200, Mathieu Malaterre wrote: >> Control: reassign -1 localechooser 2.68 >> Control: retitle -1 localechooser: image display inverts red and blue >> color > > How could this possibly be the fault of localechooser? Right. Either way: 1. debian-installer is calling localechooser with a non-default option (I could not find which) 2. localechooser is reading some env variables. In both cases it starts rendering in some byte-swapped color mode, which I believe should be removed or at least clarified so that case (1) is changed in debian-installer. Comments ?
Processed: Re: Bug#825840: localechooser: image display inverts red and blue color
Processing control commands: > reassign -1 bterm-unifont 1.4 Bug #825840 [localechooser] localechooser: image display inverts red and blue color Bug reassigned from package 'localechooser' to 'bterm-unifont'. No longer marked as found in versions localechooser/2.68. Ignoring request to alter fixed versions of bug #825840 to the same values previously set Bug #825840 [bterm-unifont] localechooser: image display inverts red and blue color Marked as found in versions bterm-unifont/1.4. > retitle -1 bterm: inverts red and blue in localechooser Bug #825840 [bterm-unifont] localechooser: image display inverts red and blue color Changed Bug title to 'bterm: inverts red and blue in localechooser' from 'localechooser: image display inverts red and blue color'. -- 825840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#825840: localechooser: image display inverts red and blue color
Control: reassign -1 bterm-unifont 1.4 Control: retitle -1 bterm: inverts red and blue in localechooser On Sat, Sep 3, 2016 at 11:37 AM, Mathieu Malaterre wrote: > On Fri, Sep 2, 2016 at 9:28 PM, Ben Hutchings wrote: >> Control: tag -1 moreinfo >> >> On Fri, 2016-09-02 at 20:56 +0200, Mathieu Malaterre wrote: >>> Control: reassign -1 localechooser 2.68 >>> Control: retitle -1 localechooser: image display inverts red and blue >>> color >> >> How could this possibly be the fault of localechooser? > > Right. Either way: > > 1. debian-installer is calling localechooser with a non-default option > (I could not find which) > 2. localechooser is reading some env variables. > > In both cases it starts rendering in some byte-swapped color mode, > which I believe should be removed or at least clarified so that case > (1) is changed in debian-installer. > > Comments ? Answering myself: With the default TERM=linux, localechooser behave as expected on PowerPC/MacMiniG4 # localechooser However with TERM=bterm, localechooser behave in some sort of inverted (byte-swap?) red is blue background: # bterm -f /lib/unifont.bgf localchooser Hopefully this is the last time I re-assign this bug. Thanks
Processed: Re: Bug#825840: localechooser: image display inverts red and blue color
Processing control commands: > reassign -1 bogl-bterm 0.1.18-11 Bug #825840 [bterm-unifont] bterm: inverts red and blue in localechooser Bug reassigned from package 'bterm-unifont' to 'bogl-bterm'. No longer marked as found in versions bterm-unifont/1.4. Ignoring request to alter fixed versions of bug #825840 to the same values previously set Bug #825840 [bogl-bterm] bterm: inverts red and blue in localechooser Marked as found in versions bogl/0.1.18-11. -- 825840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#825840: localechooser: image display inverts red and blue color
Control: reassign -1 bogl-bterm 0.1.18-11 > Hopefully this is the last time I re-assign this bug. Spoke too soon. This time should be right.
Re: How to preseed.cfg with official installation cdrom
On 9/3/2016 7:24 AM, Mario Gummies wrote: 02.09.2016, 20:17, "Mario Gummies" : Hi, I am planning a fancy debian installation session next week on a real machine and I want to do it with the preseeding method called "file". Therefore I downloaded and burned a cd-image from the official server. Please note: This is not a case of a mastered cd, I speak of. Given I found a preseed.cfg, which I put in a parallel partition on the hd, ready to be loaded into the installation routine. Reading the docs here is the point, where I loose track: This case, loading a preseed.cfg within an ordinary cd installation from hard disk, seems not included within the examples given, does not it? These are btw the terms I did web search for: installing preseed from file cdrom debian-boot@lists.debian.org Any idea or discussion on how to perform it, any pointer? Tia Hi once more, Ps: If it comes out that this feature for some reason or the other is not "covered", to say it is not implemented. The Howto does not mention it explicitly: So keeping silence should insinuate: Docs say it is not there. Right? I would, however, opt to care for its implementation instead. So: as well points for the question of 1) wish or 2)effort of the implementation of this feature are welcome. This question would be more appropriate on debian-user. You don't mention what documentation you are using. Appendix B. of the Installation Guide covers preseeding [chose appropriate guide at https://www.debian.org/releases/stable/installmanual]. Also read the thread at http://lists.debian.org/508445a7.40...@cloud85.net useful. HTH
Re: How to preseed.cfg with official installation cdrom
02.09.2016, 20:17, "Mario Gummies" : > Hi, > I am planning a fancy debian installation session next week on a real machine > and I want to do it with the preseeding method called "file". Therefore I > downloaded and burned a cd-image from the official server. Please note: This > is not a case of a mastered cd, I speak of. Given I found a preseed.cfg, > which I put in a parallel partition on the hd, ready to be loaded into the > installation routine. > Reading the docs here is the point, where I loose track: > > This case, loading a preseed.cfg within an ordinary cd installation from hard > disk, seems not included within the examples given, does not it? > > These are btw the terms I did web search for: > installing preseed from file cdrom debian-boot@lists.debian.org > > Any idea or discussion on how to perform it, any pointer? > Tia Hi once more, Ps: If it comes out that this feature for some reason or the other is not "covered", to say it is not implemented. The Howto does not mention it explicitly: So keeping silence should insinuate: Docs say it is not there. Right? I would, however, opt to care for its implementation instead. So: as well points for the question of 1) wish or 2)effort of the implementation of this feature are welcome.
Re: How to preseed.cfg with official installation cdrom
On Sat, Sep 03, 2016 at 08:40:12AM -0500, Richard Owlett wrote: > On 9/3/2016 7:24 AM, Mario Gummies wrote: > >02.09.2016, 20:17, "Mario Gummies" : > >>Hi, > >>I am planning a fancy debian installation session next week on a > >>real machine and I want to do it with the preseeding method called > >>"file". Therefore I downloaded and burned a cd-image from the > >>official server. Please note: This is not a case of a mastered cd, > >>I speak of. Given I found a preseed.cfg, which I put in a parallel > >>partition on the hd, ready to be loaded into the installation routine. > >>Reading the docs here is the point, where I loose track: > >> > >>This case, loading a preseed.cfg within an ordinary cd installation > >>from hard disk, seems not included within the examples given, does > >>not it? > >> > >>These are btw the terms I did web search for: > >>installing preseed from file cdrom debian-boot@lists.debian.org > >> > >>Any idea or discussion on how to perform it, any pointer? > >>Tia > > > >Hi once more, > >Ps: If it comes out that this feature for some reason or the other > >is not "covered", to say it is not implemented. The Howto does not > >mention it explicitly: So keeping silence should insinuate: Docs say > >it is not there. Right? > > I would, however, opt to care for its implementation instead. > >So: as well points for the question of 1) wish or 2)effort of the > >implementation of this feature are welcome. > > > > > > This question would be more appropriate on debian-user. > You don't mention what documentation you are using. > Appendix B. of the Installation Guide covers preseeding [chose > appropriate guide at > https://www.debian.org/releases/stable/installmanual ]. > Also read the thread at > http://lists.debian.org/508445a7.40...@cloud85.net useful. In that thread is https://lists.debian.org/debian-user/2012/10/msg01130.html it says "passed on the kernel command line to the installer." A kernel boot parameter is the link between having a CD-ROM and preseed file. As a happy user of network installs do I lack CD-ROM install exprience ... Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Re: Debian kernel 4.7.2-1 build on Sid and Jessie fails
Much appreciated, Ben! On Fri, Sep 2, 2016 at 8:49 AM, Ben Hutchings wrote: > On Fri, 2016-09-02 at 03:35 -0700, Jose R Rodriguez wrote: >> Niltze, all! >> >> Currently running Reiser4-patched kernel 4.7 built from pristine >> source upstream: >> >> Linux mictlantecuhtli 4.7.0.tezcatlipoca #1 SMP PREEMPT Wed Aug 10 >> 05:04:17 PDT 2016 x86_64 GNU/Linux >> >> On the other hand, I have experienced multiple issues building >> Debian'ized kernel 4.7.2-1 -- first building on Jessie modified for >> GCC 4.9; >> and then attempting build on Jessie-built GCC 5.3. And finally I >> attempted the build on Debian Unstable and it failed, as well. >> Below are the offending sections -- which, by the way -- roughly >> correspond in all instances of Debian and GCC: > [...] > > This happens if you invoke debian/rules directly and not through dpkg- > buildpackage. > > debian/rules.real does: > > ifdef OVERRIDE_HOST_TYPE > CROSS_COMPILE := $(OVERRIDE_HOST_TYPE)- > else ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH)) > CROSS_COMPILE := $(DEB_HOST_GNU_TYPE)- > else > CROSS_COMPILE := > endif > > So the assumption is that all those architecture variables, or none, > are defined. dpkg-buildpackage does define them all. > > However, debian/rules does: > > DEB_HOST_ARCH := $(shell dpkg-architecture -qDEB_HOST_ARCH) > > and does not define any other architecture variables. > > We should probably include /usr/share/dpkg/architecture.mk in > debian/rules instead. > As I began to learn how to build a kernel 'the debian way', I had been using as reference: https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official-vcs Accordingly, up to this debian'ized kernel, the directive fakeroot debian/rules binary-arch worked well to generate both DEBs *and* UDEBs successfully. Now, following your advice, Ben, I have replaced the above directive with dpkg-buildpackage -d -b -us -uc -T binary-arch (option -d is to override apparent flex dependency show-stopper -- but: "flex is already the newest version", according to apt). *also* with or without including switches, -us -uc, the kernel build procedure finishes -- apparently successfully as it generates the *.deb files; notwithstanding, it fails to generate *.udeb files -- which are required to build Debian-Installer (d-i) --- kernel/sound/pci/snd-intel8x0m.ko kernel/sound/pci/snd-via82xx-modem.ko kernel/sound/synth/emux/snd-emux-synth.ko kernel/virt/lib/irqbypass.ko kernel-wedge strip-modules 4.7.0-1+reiser4.0.1-amd64 kernel-wedge check kernel-image-4.7.0-1+reiser4.0.1-amd64-di nic-modules-4.7.0-1+reiser4.0.1-amd64-di nic-wireless-modules-4.7.0-1+reiser4.0.1-amd64-di nic-shared-modules-4.7.0-1+reiser4.0.1-amd64-di serial-modules-4.7.0-1+reiser4.0.1-amd64-di usb-serial-modules-4.7.0-1+reiser4.0.1-amd64-di ppp-modules-4.7.0-1+reiser4.0.1-amd64-di pata-modules-4.7.0-1+reiser4.0.1-amd64-di cdrom-core-modules-4.7.0-1+reiser4.0.1-amd64-di firewire-core-modules-4.7.0-1+reiser4.0.1-amd64-di scsi-core-modules-4.7.0-1+reiser4.0.1-amd64-di scsi-modules-4.7.0-1+reiser4.0.1-amd64-di loop-modules-4.7.0-1+reiser4.0.1-amd64-di btrfs-modules-4.7.0-1+reiser4.0.1-amd64-di ext4-modules-4.7.0-1+reiser4.0.1-amd64-di isofs-modules-4.7.0-1+reiser4.0.1-amd64-di jfs-modules-4.7.0-1+reiser4.0.1-amd64-di reiser4-modules-4.7.0-1+reiser4.0.1-amd64-di ntfs-modules-4.7.0-1+reiser4.0.1-amd64-di xfs-modules-4.7.0-1+reiser4.0.1-amd64-di fat-modules-4.7.0-1+reiser4.0.1-amd64-di md-modules-4.7.0-1+reiser4.0.1-amd64-di multipath-modules-4.7.0-1+reiser4.0.1-amd64-di usb-modules-4.7.0-1+reiser4.0.1-amd64-di usb-storage-modules-4.7.0-1+reiser4.0.1-amd64-di pcmcia-storage-modules-4.7.0-1+reiser4.0.1-amd64-di fb-modules-4.7.0-1+reiser4.0.1-amd64-di input-modules-4.7.0-1+reiser4.0.1-amd64-di event-modules-4.7.0-1+reiser4.0.1-amd64-di mouse-modules-4.7.0-1+reiser4.0.1-amd64-di nic-pcmcia-modules-4.7.0-1+reiser4.0.1-amd64-di pcmcia-modules-4.7.0-1+reiser4.0.1-amd64-di nic-usb-modules-4.7.0-1+reiser4.0.1-amd64-di sata-modules-4.7.0-1+reiser4.0.1-amd64-di core-modules-4.7.0-1+reiser4.0.1-amd64-di acpi-modules-4.7.0-1+reiser4.0.1-amd64-di i2c-modules-4.7.0-1+reiser4.0.1-amd64-di crc-modules-4.7.0-1+reiser4.0.1-amd64-di crypto-modules-4.7.0-1+reiser4.0.1-amd64-di crypto-dm-modules-4.7.0-1+reiser4.0.1-amd64-di efi-modules-4.7.0-1+reiser4.0.1-amd64-di ata-modules-4.7.0-1+reiser4.0.1-amd64-di mmc-core-modules-4.7.0-1+reiser4.0.1-amd64-di mmc-modules-4.7.0-1+reiser4.0.1-amd64-di nbd-modules-4.7.0-1+reiser4.0.1-amd64-di squashfs-modules-4.7.0-1+reiser4.0.1-amd64-di speakup-modules-4.7.0-1+reiser4.0.1-amd64-di virtio-modules-4.7.0-1+reiser4.0.1-amd64-di uinput-modules-4.7.0-1+reiser4.0.1-amd64-di sound-modules-4.7.0-1+reiser4.0.1-amd64-di hyperv-modules-4.7.0-1+reiser4.0.1-amd64-di udf-modules-4.7.0-1+reiser4.0.1-amd64-di fuse-modules-4.7.0-1+reiser4.0.1-amd64-di dh_fixpe
Re: Debian kernel 4.7.2-1 build on Sid and Jessie fails
On Fri, 2016-09-02 at 16:49 +0100, Ben Hutchings wrote: > On Fri, 2016-09-02 at 03:35 -0700, Jose R Rodriguez wrote: > > > > Niltze, all! > > > > Currently running Reiser4-patched kernel 4.7 built from pristine > > source upstream: > > > > Linux mictlantecuhtli 4.7.0.tezcatlipoca #1 SMP PREEMPT Wed Aug 10 > > 05:04:17 PDT 2016 x86_64 GNU/Linux > > > > On the other hand, I have experienced multiple issues building > > Debian'ized kernel 4.7.2-1 -- first building on Jessie modified for > > GCC 4.9; > > and then attempting build on Jessie-built GCC 5.3. And finally I > > attempted the build on Debian Unstable and it failed, as well. > > Below are the offending sections -- which, by the way -- roughly > > correspond in all instances of Debian and GCC: > [...] > > This happens if you invoke debian/rules directly and not through dpkg- > buildpackage. Rather, it can happen in some circumstances, but... > debian/rules.real does: > > ifdef OVERRIDE_HOST_TYPE > CROSS_COMPILE := $(OVERRIDE_HOST_TYPE)- > else ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH)) > CROSS_COMPILE := $(DEB_HOST_GNU_TYPE)- > else > CROSS_COMPILE := > endif > > So the assumption is that all those architecture variables, or none, > are defined. dpkg-buildpackage does define them all. > > However, debian/rules does: > > DEB_HOST_ARCH := $(shell dpkg-architecture -qDEB_HOST_ARCH) > > and does not define any other architecture variables. ...variable definitions in debian/rules don't automatically propagate to debian/rules.real, so this doesn't explain the failure. And although I have seen this failure myself, I can't reproduce it now. > We should probably include /usr/share/dpkg/architecture.mk in > debian/rules instead. I now think it should be included in debian/rules.real. However, until I have a way to reproduce the problem, I'm not going to attempt a fix. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Re: Bug#836446: libc6-dev: depends on linux-libc-dev:$arch, breaking debootstrap
clone 836446 -1 reassign -1 debootstrap retitle -1 debootstrap: doesn't support arch-qualified dependencies affects -1 libc6-dev thanks On 2016-09-03 11:28, Sven Joachim wrote: > Package: libc6-dev > Version: 2.24-1 > Severity: important > > The fix for bug #834706 has the side effect that libc6-dev now depends > on linux-libc-dev:$arch : > > , > | $ apt-cache show libc6-dev | grep ^Depends > | Depends: libc6 (= 2.24-1), libc-dev-bin (= 2.24-1), linux-libc-dev:i386 (>= > 4.6.4-1) > ` > > While dpkg and apt obviously don't have a problem with that, debootstrap > cannot cope with it, and "debootstrap --variant=buildd" fails to even > download linux-libc-dev. See the attached log. That's definitely a bug in debootstrap. In the future it's more and more likely that we'll have arch-qualified dependencies in the bases packages, so this has to be fixed. I am therefore cloning and reassigning the bug. > Please clone/reassign to debootstrap as you see fit, but in any case it > would be nice to remove the extraneous arch qualification in the > dependency. Note that arch qualification is automatically added by dpkg-query, so we'll have to mangle the output. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Processed: Re: Bug#836446: libc6-dev: depends on linux-libc-dev:$arch, breaking debootstrap
Processing commands for cont...@bugs.debian.org: > clone 836446 -1 Bug #836446 [libc6-dev] libc6-dev: depends on linux-libc-dev:$arch, breaking debootstrap Bug 836446 cloned as bug 836525 > reassign -1 debootstrap Bug #836525 [libc6-dev] libc6-dev: depends on linux-libc-dev:$arch, breaking debootstrap Bug reassigned from package 'libc6-dev' to 'debootstrap'. No longer marked as found in versions glibc/2.24-1. Ignoring request to alter fixed versions of bug #836525 to the same values previously set > retitle -1 debootstrap: doesn't support arch-qualified dependencies Bug #836525 [debootstrap] libc6-dev: depends on linux-libc-dev:$arch, breaking debootstrap Changed Bug title to 'debootstrap: doesn't support arch-qualified dependencies' from 'libc6-dev: depends on linux-libc-dev:$arch, breaking debootstrap'. > affects -1 libc6-dev Bug #836525 [debootstrap] debootstrap: doesn't support arch-qualified dependencies Added indication that 836525 affects libc6-dev > thanks Stopping processing here. Please contact me if you need assistance. -- 836446: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836446 836525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836525 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#836525: Bug#836446: libc6-dev: depends on linux-libc-dev:$arch, breaking debootstrap
Aurelien Jarno (2016-09-03): > clone 836446 -1 > reassign -1 debootstrap > retitle -1 debootstrap: doesn't support arch-qualified dependencies > affects -1 libc6-dev > thanks Thanks for this. > On 2016-09-03 11:28, Sven Joachim wrote: > > Package: libc6-dev > > Version: 2.24-1 > > Severity: important > > > > The fix for bug #834706 has the side effect that libc6-dev now depends > > on linux-libc-dev:$arch : > > > > , > > | $ apt-cache show libc6-dev | grep ^Depends > > | Depends: libc6 (= 2.24-1), libc-dev-bin (= 2.24-1), linux-libc-dev:i386 > > (>= 4.6.4-1) > > ` > > > > While dpkg and apt obviously don't have a problem with that, debootstrap > > cannot cope with it, and "debootstrap --variant=buildd" fails to even > > download linux-libc-dev. See the attached log. > > That's definitely a bug in debootstrap. In the future it's more and more > likely that we'll have arch-qualified dependencies in the bases packages, > so this has to be fixed. I am therefore cloning and reassigning the bug. Do you plan to implement a workaround in glibc for now, or should this bug report (on the debootstrap side) be raised to RC and fixed before we can think of a new d-i release? (I have no such plan right now, but it might be nice not to wait too much once linux has migrated). KiBi. signature.asc Description: Digital signature
Bug#836525: Bug#836446: libc6-dev: depends on linux-libc-dev:$arch, breaking debootstrap
On 2016-09-03 20:54, Cyril Brulebois wrote: > Aurelien Jarno (2016-09-03): > > clone 836446 -1 > > reassign -1 debootstrap > > retitle -1 debootstrap: doesn't support arch-qualified dependencies > > affects -1 libc6-dev > > thanks > > Thanks for this. > > > On 2016-09-03 11:28, Sven Joachim wrote: > > > Package: libc6-dev > > > Version: 2.24-1 > > > Severity: important > > > > > > The fix for bug #834706 has the side effect that libc6-dev now depends > > > on linux-libc-dev:$arch : > > > > > > , > > > | $ apt-cache show libc6-dev | grep ^Depends > > > | Depends: libc6 (= 2.24-1), libc-dev-bin (= 2.24-1), linux-libc-dev:i386 > > > (>= 4.6.4-1) > > > ` > > > > > > While dpkg and apt obviously don't have a problem with that, debootstrap > > > cannot cope with it, and "debootstrap --variant=buildd" fails to even > > > download linux-libc-dev. See the attached log. > > > > That's definitely a bug in debootstrap. In the future it's more and more > > likely that we'll have arch-qualified dependencies in the bases packages, > > so this has to be fixed. I am therefore cloning and reassigning the bug. > > Do you plan to implement a workaround in glibc for now, or should this bug > report (on the debootstrap side) be raised to RC and fixed before we can > think of a new d-i release? (I have no such plan right now, but it might > be nice not to wait too much once linux has migrated). I have just committed a workaround in glibc, I'll upload it in the next days. It would be nice to have this bug fixed for Stretch though, so that we can use arch-qualified dependencies in Buster. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net signature.asc Description: PGP signature
Re: How to use a local Debian mirror when installing with preseed (PXE)?
Hallo Frank, Frank Thommen (2016-09-01): > I'm currently setting up an unattended, PXE-based network installation of > Debian with preseeding. We also have a complete local Debian mirror for > inhouse use. However I haven't found a way to configure the installer to > use this mirror instead of one of the official Debian mirrors (and takes > accordingly long) for downloading the packages. I have set > > d-i apt-setup/local0/repository string http://our.debmirror stable main > > in the preseed file but the installer doesn't seem to download any files > from there a part from some index files (Packages.xz, Translation-en.bz2 > ecc.) > > How can I preseed our local mirror as primary/only installation source? Take a look at the preseed example file[1]? While it doesn't contain all preseedable settings, the part you're interested in seems covered: | ### Mirror settings | # If you select ftp, the mirror/country string does not need to be set. | #d-i mirror/protocol string ftp | d-i mirror/country string manual | d-i mirror/http/hostname string http.us.debian.org | d-i mirror/http/directory string /debian | d-i mirror/http/proxy string 1. https://www.debian.org/releases/jessie/example-preseed.txt This is handled by choose-mirror, which runs way before apt-setup (which you were trying to configure). KiBi. signature.asc Description: Digital signature
Re: How to preseed.cfg with official installation cdrom
03.09.2016, 15:55, "Richard Owlett" : > On 9/3/2016 7:24 AM, Mario Gummies wrote: >> 02.09.2016, 20:17, "Mario Gummies" : >>> Hi, >>> I am planning a fancy debian installation session next week on a real >>> machine and I want to do it with the preseeding method called "file". >>> Therefore I downloaded and burned a cd-image from the official server. >>> Please note: This is not a case of a mastered cd, I speak of. Given I found >>> a preseed.cfg, which I put in a parallel partition on the hd, ready to be >>> loaded into the installation routine. >>> Reading the docs here is the point, where I loose track: >>> >>> This case, loading a preseed.cfg within an ordinary cd installation from >>> hard disk, seems not included within the examples given, does not it? >>> >>> These are btw the terms I did web search for: >>> installing preseed from file cdrom debian-boot@lists.debian.org >>> >>> Any idea or discussion on how to perform it, any pointer? >>> Tia >> >> Hi once more, >> Ps: If it comes out that this feature for some reason or the other is not >> "covered", to say it is not implemented. >> The Howto does not mention it explicitly: So keeping silence should >> insinuate: Docs say it is not there. Right? >> I would, however, opt to care for its implementation instead. >> So: as well points for the question of 1) wish or 2)effort of the >> implementation of this feature are welcome. > > This question would be more appropriate on debian-user. > You don't mention what documentation you are using. > Appendix B. of the Installation Guide covers preseeding [chose > appropriate guide at > https://www.debian.org/releases/stable/installmanual]. > Also read the thread at > http://lists.debian.org/508445a7.40...@cloud85.net useful. > HTH >> The nature of the problem is that I have found *NO NONE NADA* >> complete explicit instructions of what to do when handed THREE >> objects: >> 1. dedicated laptop capable of running Debian >> 2. Debian 6.0.5 DVD 1 of 8 >> 3. a USB stick which may be partitioned and formatted as required >> on which can be placed a pressed.cfg. >> NOTE BENE: The word "network" does not appear in that description. > > OK. I am not familiar with trying it this way. I've only done it by > fetching the preseed file over the web via url= passed > on the kernel command line to the installer. > >> What I have found is incomplete and conflicting descriptions of >> portions of the procedure(s) required drawn from various Debian >> releases. > > Yes. Me too. Hi, so if the answer to that would be: push a the hint for "out of box kind" use cases, "to try it with two computers connected by internet protocol, choosing the http installation method instead of http as a default option" . missing in the docs, well, it would be false. Now it keeps still open the question: Is not there a documentation deprivation or some thing? So what can one see from here is, that one is set as a user to a situation, in that one could not explain not even still on how to do it just: "automatically, but yes out of the box.". If this sounds obscene to someone, - could be. So, further news: if it is really the seemingly case, that the "file"-kind automatic installation method, is defunct since - ever? - and news over news: the second best installation method after routing it hopefully through your commercial software bios, kind of no go, is waiting to the dhcp connection - on the bios or when some kernel install is done, do not know - or lets say nothing acceptable because requiring human interaction, destroys the "automatic" in the feature "automatic install". In this cases it is that all the tool has already gotten to the state of limited, because broken, orphaned usage state, unable to basic usage, not even able to give notice of such lack to the docs. Has it even gotten to a point of "sensationally crippling", one fears. I wont like that, but wont fail to investigate that neither: Sorry. Well, Question: So what could one campaign or achieve as a volunteer to help to fix this bug in end and in these cases and after all? Boo! some secrets!?! Some Tips from your part for on how to help it from here? Some pointers on how to precede for such cases? If so, then thanks for it and I am really tented for acknowledging solution ideas for it. (;
Re: Processed: tagging 787044
Quoting Debian Bug Tracking System (ow...@bugs.debian.org): > Processing commands for cont...@bugs.debian.org: > > > tags 787044 + pending > Bug #787044 [src:libdebian-installer] libdebian-installer: please make new > Build-Depends: check optional via build profiles > Added tag(s) pending. > > thanks > Stopping processing here. > > Please contact me if you need assistance. > -- > 787044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787044 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > With this change, I can't build libdebian-installer anymore: pdebuild --pbuilder cowbuilder -- --basepath /var/cache/pbuilder/base-sid.cow --distribution sid .../... Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: i386 Maintainer: Debian Pbuilder Team Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder to satisfy the build-dependencies of the package being currently built. Depends: dpkg-dev (>= 1.13.5), debhelper (>= 9), dh-autoreconf, doxygen, pkg-config, check dpkg-deb: error: parsing file '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy/DEBIAN/control' near line 8 package 'pbuilder-satisfydepends-dummy': 'Depends' field, syntax error after reference to package 'check' E: pbuilder-satisfydepends failed. -- signature.asc Description: PGP signature
