Re: Bug#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
Hi Sorry for the lack of information. auto preseed, not expert: https://github.com/ozitraveller/star-live-build/blob/master/xfce-64/config/includes.installer/preseed.cfg version: jessie install media: iso image mounted as virtual CDROM : yes Yes that is the dialog I got, only not QEMU. Yes I understand the other options thanks. I hope this helps. regards On Fri, Sep 12, 2014 at 10:18 AM, Steven Chamberlain wrote: > Hi, > > On 12/09/14 00:54, Ozi Traveller wrote: > > I've noticed that this happens when I'm installing into a virtualbox vm, > > and there is only single partition. > > Thanks, this is useful information for me. But please could you be more > specific: was this a default, automatic (preseed) or expert-mode > install? Of which version (wheezy, jessie daily build?)) and from what > type of install media (ISO image? mounted as virtual CDROM drive or as > a hard disk?) > > Did you get this dialog first: > > | Install the GRUB boot loader to the master boot record? > | > > or do you only see this: > > | Device for boot loader installation: > | [o] Enter device manually > | [ ] /dev/sda (ata-QEMU_HARDDISK_QM1) > > and in case of the latter -- was "Enter device manually" the > pre-selected option (if you were to hit Enter), or was /dev/sda > pre-selected? > > > Seems like a silly question when > > there is only 1 choice. > > There are actually other choices if you were to "Enter device manually" > - you could install GRUB to a partition instead of the MBR. Or to some > other device that GRUB wasn't able to detect. We need to provide a way > to do that. > > Thanks, > Regards, > -- > Steven Chamberlain > ste...@pyro.eu.org >
Re: Bug#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
Hope you guys don't mind me adding my comment here?? I've noticed that this happens when I'm installing into a virtualbox vm, and there is only single partition. Seems like a silly question when there is only 1 choice. regards On Fri, Sep 12, 2014 at 7:51 AM, Steven Chamberlain wrote: > On 11/09/14 22:48, Cyril Brulebois wrote: > >> I've been trying to document the existing processes here: > >> https://wiki.debian.org/DebianInstaller/Bugs/GrubInstaller > > > > This page is missing cases involving firmware on a USB stick, so > > no, even installation from CD/DVD/PXE can fail the same way. > > OK, I'd like to document that as a test case. Actually with this there > could be two situations: > * the USB stick was plugged in already at boot time > * the USB stick is plugged in later > and could lead to different ordering. > > Regards, > -- > Steven Chamberlain > ste...@pyro.eu.org > >
Re: Q: How to rebuild d-i or initrd?
asupplicant-udeb zlib1g-udeb
Reading package lists... Done
Building dependency tree... Done
E: Unable to locate package acpi-modules-3.12-1-amd64-di
E: Couldn't find any package by regex 'acpi-modules-3.12-1-amd64-di'
E: Unable to locate package fat-modules-3.12-1-amd64-di
E: Couldn't find any package by regex 'fat-modules-3.12-1-amd64-di'
E: Unable to locate package fb-modules-3.12-1-amd64-di
E: Couldn't find any package by regex 'fb-modules-3.12-1-amd64-di'
E: Unable to locate package hyperv-modules-3.12-1-amd64-di
E: Couldn't find any package by regex 'hyperv-modules-3.12-1-amd64-di'
E: Unable to locate package input-modules-3.12-1-amd64-di
E: Couldn't find any package by regex 'input-modules-3.12-1-amd64-di'
E: Unable to locate package kernel-image-3.12-1-amd64-di
E: Couldn't find any package by regex 'kernel-image-3.12-1-amd64-di'
E: Unable to locate package nic-modules-3.12-1-amd64-di
E: Couldn't find any package by regex 'nic-modules-3.12-1-amd64-di'
E: Unable to locate package nic-pcmcia-modules-3.12-1-amd64-di
E: Couldn't find any package by regex 'nic-pcmcia-modules-3.12-1-amd64-di'
E: Unable to locate package nic-usb-modules-3.12-1-amd64-di
E: Couldn't find any package by regex 'nic-usb-modules-3.12-1-amd64-di'
E: Unable to locate package nic-wireless-modules-3.12-1-amd64-di
E: Couldn't find any package by regex 'nic-wireless-modules-3.12-1-amd64-di'
E: Unable to locate package pcmcia-modules-3.12-1-amd64-di
E: Couldn't find any package by regex 'pcmcia-modules-3.12-1-amd64-di'
E: Unable to locate package usb-modules-3.12-1-amd64-di
E: Couldn't find any package by regex 'usb-modules-3.12-1-amd64-di'
E: Unable to locate package usb-storage-modules-3.12-1-amd64-di
E: Couldn't find any package by regex 'usb-storage-modules-3.12-1-amd64-di'
E: Unable to locate package virtio-modules-3.12-1-amd64-di
E: Couldn't find any package by regex 'virtio-modules-3.12-1-amd64-di'
make[2]: *** [stamps/get_udebs-netboot-stamp] Error 100
make[1]: *** [_build] Error 2
make: *** [build_netboot] Error 2
On Mon, Jan 6, 2014 at 8:36 AM, Cyril Brulebois wrote:
> Ozi Traveller (2014-01-06):
> > I changed the debian/rules file as follows:
> >
> > #! /usr/bin/make -f
> >
> > ARCH=$(shell dpkg-architecture -qDEB_BUILD_ARCH)
> > VERSION=$(shell LC_ALL=C dpkg-parsechangelog | grep ^Version: | cut -d '
> '
> > -f 2)
> > DATE=$(shell echo $(VERSION) | cut -d '.' -f 1)
> > SUITE=$(shell LC_ALL=C dpkg-parsechangelog | grep ^Distribution: | cut
> -d '
> > ' -f 2)
> > # ifeq (${SUITE},UNRELEASED)
> > # USE_UDEBS_FROM=unstable
> > # TRANSSTATUS=
> > # BOOTMENU_BEEP=n
> > # else
> > # USE_UDEBS_FROM=jessie
> > USE_UDEBS_FROM=wheezy
> > USE_PROPOSED_UPDATES=0
> > TRANSSTATUS=translation-status
> > BOOTMENU_BEEP=y
> > # endif
> >
> > however sources.list.udeb still has unstable.
>
> Err, I mentioned debian/rules so that you see how a regular debian build
> is supposed to work. dpkg-buildpackage and friends call ./debian/rules,
> which runs make in build/ with appropriate variables set. If you're only
> changing debian/rules and then manually running make under build/,
> nothing is going to change.
>
> So either tweak debian/rules and use dpkg-buildpackage, or use “make
> USE_UDEBS_FROM=wheezy” under build/, after having removed generated
> files (that includes sources.list.udeb).
>
> Mraw,
> KiBi.
>
Re: Q: How to rebuild d-i or initrd?
I changed the debian/rules file as follows:
#! /usr/bin/make -f
ARCH=$(shell dpkg-architecture -qDEB_BUILD_ARCH)
VERSION=$(shell LC_ALL=C dpkg-parsechangelog | grep ^Version: | cut -d ' '
-f 2)
DATE=$(shell echo $(VERSION) | cut -d '.' -f 1)
SUITE=$(shell LC_ALL=C dpkg-parsechangelog | grep ^Distribution: | cut -d '
' -f 2)
# ifeq (${SUITE},UNRELEASED)
# USE_UDEBS_FROM=unstable
# TRANSSTATUS=
# BOOTMENU_BEEP=n
# else
# USE_UDEBS_FROM=jessie
USE_UDEBS_FROM=wheezy
USE_PROPOSED_UPDATES=0
TRANSSTATUS=translation-status
BOOTMENU_BEEP=y
# endif
however sources.list.udeb still has unstable.
On Sun, Jan 5, 2014 at 11:38 PM, Cyril Brulebois wrote:
> Ozi Traveller (2014-01-05):
> > Sorry for so many questions. The host I'm build on is wheezy and I want
> to
> > make a wheezy debian-installer.
> >
> > The contents of sources.list.udeb are:
> >
> > # This file is automatically generated, edit sources.list.udeb.local
> > instead.
> > deb [trusted=yes] copy:/home/xxx/debian-installer/installer/build/
> > localudebs/
> > deb http://ftp.au.debian.org/debian unstable main/debian-installer
> >
> > I'm not sure where the unstable comes from. How can I force it to use
> > stable rather than unstable?
> >
> > To build I did:
> >
> > $ make reallyclean$ fakeroot make build_netboot
>
> You need to specify USE_UDEBS_FROM=wheezy (see debian/rules for the
> heuristics that are used in the regular Debian package build).
>
> Mraw,
> KiBi.
>
Re: Q: How to rebuild d-i or initrd?
Sorry for so many questions. The host I'm build on is wheezy and I want to
make a wheezy debian-installer.
The contents of sources.list.udeb are:
# This file is automatically generated, edit sources.list.udeb.local
instead.
deb [trusted=yes] copy:/home/xxx/debian-installer/installer/build/
localudebs/
deb http://ftp.au.debian.org/debian unstable main/debian-installer
I'm not sure where the unstable comes from. How can I force it to use
stable rather than unstable?
To build I did:
$ make reallyclean$ fakeroot make build_netboot
Cheers
Ozi
On Sat, Jan 4, 2014 at 3:13 PM, Cyril Brulebois wrote:
> Ozi Traveller (2014-01-04):
> > Ok I've managed to get the source and be able to build. Now I'm getting
> > build errors, see attached log.
> >
> > 922 symbols, 644 unresolved
> > Traceback (most recent call last):
> > File "/usr/bin/mklibs", line 562, in
> > raise Exception("No library provides non-weak %s" % name)
> > Exception: No library provides non-weak __fdelt_chk@glibc_2...@libc.so.6
> > make[2]: *** [stamps/tree-netboot-stamp] Error 1
> > make[1]: *** [_build] Error 2
> > make: *** [build_netboot] Error 2
> >
> > What do I have to do to rectify this ?
>
> Build in the right suite. Meaning you need a jessie chroot to build a
> jessie image, or a wheezy chroot to build a wheezy image.
>
> (A chroot is only needed if the target image isn't the same suite as the
> host system.)
>
> Mraw,
> KiBi.
>
Re: Q: How to rebuild d-i or initrd?
Unfortunately, I'm inexperienced in building packages, I'm still learning. I'm hoping there might be a step-by-step processs I could follow? I only have a couple of tasks to do to complete my distro, so far only a private distro, and a learning experience for me. https://wiki.debian.org/DebianInstaller/CheckOut https://wiki.debian.org/DebianInstaller Cheers Ozi On Sun, Dec 29, 2013 at 11:32 PM, Philipp Kern wrote: > On Sun, Dec 29, 2013 at 08:36:12AM +1100, Ozi Traveller wrote: > > I made a replacement for rootskel-gtk, using the previous version > > rootskel-gtk_1.27_amd64.udeb as the source, with a higher version number. > > I've changed the theme and the logo. > > > > I've been told that the way to have the d-i use this new version is to > rebuild > > d-i (preferably) or > > the initrd (at least). > > > > My question is, how do I rebuild the d-i and then how do I incorporate > the > > new d-i in my build? > > Check out debian-installer, put the udeb into localudebs and run `make > build_netboot' should do the trick. Remember to use `make > rebuild_netboot' from then on. You can check the MANIFEST to see if your > (luckily higher versioned) udeb was included. > > Kind regards > Pihlipp Kern >
Q: How to rebuild d-i or initrd?
I made a replacement for rootskel-gtk, using the previous version rootskel-gtk_1.27_amd64.udeb as the source, with a higher version number. I've changed the theme and the logo. I've been told that the way to have the d-i use this new version is to rebuild d-i (preferably) or the initrd (at least). My question is, how do I rebuild the d-i and then how do I incorporate the new d-i in my build? Cheers
Re: Q: How can I repack a udeb package?
Thanks KiBi On Wed, Dec 25, 2013 at 11:40 AM, Cyril Brulebois wrote: > Ozi Traveller (2013-12-25): > > I'm trying to change the png images in the /usr/share/graphics folder and > > the Clearlooks theme in rootskel-gtk_1.27_amd64.udeb for a custom > > live-build. > > > > How do I unpack the repack the udev? > > Hrm. I'll answer the following question, since it's way easier than what > people mean by repacking: “how do I rebuild an existing udeb with some > modifications?”. > > You fetch the source package for the said udeb: > dget -x > http://ftp.de.debian.org/debian/pool/main/r/rootskel-gtk/rootskel-gtk_1.27.dsc > > (Or use links from http://packages.debian.org/source/stable/rootskel-gtk) > > You modify the source package as you see fit, probably by updating the > source .svg files to whatever you like. Then you build the binary > package(s) as usual in Debian: “dpkg-builpackage -b” or “debuild -b”. > > You'll then find the resulting udeb(s) in the parent directory. You > might want to specify a new changelog entry (therefore a new version > number) using e.g. “dch --local +mystuff” before building the binary > packages using dpkg-buildpackage or debuild. > > Mraw, > KiBi. >
Fwd: Q: How can I repack a udeb package?
Sorry, I forgot to add I'm doing a Wheezy build. Cheers
Q: How can I repack a udeb package?
I'm trying to change the png images in the /usr/share/graphics folder and the Clearlooks theme in rootskel-gtk_1.27_amd64.udeb for a custom live-build. How do I unpack the repack the udev? Cheers
