Age | Commit message (Collapse) | Author |
|
Closes: #952861
|
|
Closes: #952860
|
|
including:
- spaces replaced with tabs for consistency
- alignment of `;;` in some case statements changed for consistency
Gbp-Dch: Short
Closes: #952857
|
|
--firmware-binary adds firmware to d-i, --firmware-chroot adds to live
Gbp-Dch: Short
|
|
The specifics of what whould be done for it, beyond the disk info
label, needs addressing. (fixme comment left). (#952854).
Partial fix for #952846
Gbp-Dch: Short
Closes: #952846
|
|
Partial fix for #952846
Gbp-Dch: Short
|
|
Gbp-Dch: Ignore
Closes: #952851
|
|
Perhaps it is unnecessary in the other case, but not harm applying
in both to be certain.
Gbp-Dch: Short
Closes: #952850
|
|
after use
Closes: #952849
|
|
Gbp-Dch: Ignore
Closes: #952848
|
|
This has been present in debootstrap since version 1.0.30.
Gbp-Dch: Short
Closes: #952847
|
|
update feb-2020: the bug report is marked as fixed in version 5.0-a7-1,
however there is no such patch merged for that tagged release, nor at all
in master, so this properly closes it.
Gbp-Dch: Short
Closes: #776532
|
|
Update feb-2020:
Both grub2 and syslinux were affected by this issue. Someone else's
patch fixing syslinux only just recently got merged in
2735f3bd38d3d2f0c48ea1ce023a27943ef0ab84 but grub2 was still
affected. I had made patches for both in 2015 which never got
merged. This is the grub2 one.
Gbp-Dch: Short
Closes: #952843
|
|
the sed commands were missing '-i' to actually modify the file (rather
than output to stdout)
Gbp-Dch: Short
Closes: #952842
|
|
all uses of this script pass in a suitable 'pass' param, and a previous
commit added a validation check. Having a fallback to 'binary' should a
param not be supplied is completely unnecessary.
fyi, this script is only ever called from the bootstrap stage and with
'binary' as the param, thus supporting being called with 'source' and
indeed having a 'pass' param at all is surely utterly pointless in itself.
Gbp-Dch: Ignore
|
|
if this had already been in place then it would have caught
bug #952837.
Gbp-Dch: Short
Closes: #952841
|
|
Gbp-Dch: Ignore
Closes #952839
|
|
Gbp-Dch: Short
Closes: #952838
|
|
valid values are binary|source, and source should have been
used here.
Gbp-Dch: Short
Closes: #952837
|
|
Originally removed in 42fb1e197607ac8920b3f8f3a583d1d540c5ae05
Accidentally restored in bc50443cf043616c7087f383e11bf85cd233c54e
(Closes #952835)
|
|
18e0a2f32525e5092be322272e7bf9296f050584 "rebranded live sources" which
included renaming `source_debian-live` to `source_live` but accidentally
left the old file in place.
(Closes #952834)
|
|
|
|
debian-cd changed it that way, we already have it that way in EFI
boot, let's be consistent.
|
|
That change was erroneously committed as part of
44b9b0a6501476de594ce3783cea5df0c141478c
|
|
apt-ftparchive is not able to differentiate between .deb and .udeb so
we have to install them in different pool directories so that we can
regenerate the Packages files without having the .udeb show up
unexpectedly.
Since binary_package-lists can overwrite the Packages files generated
in installer_debian-installer we have to ensure that it also updates
the Release file created formerly.
Ideally we should find a way to avoid the duplication of this logic.
Gbp-Dch: Full
|
|
In the binary stage, chroot is restored from cache/bootstrap, which contains
neither custom repo lists, nor keys. If local packages are present,
chroot_archives will call 'Apt chroot update' after adding custom repo lists
without adding keys. apt-get will then fail instead of warn as of apt version
1.5.
Closes: #941691
|
|
That way it becomes possible to customize grub-efi files.
Closes: #940846
|
|
This makes it possible to build an image against a first distribution
(--distribution-chroot) and have the resulting image point to another
distribution (--distribution-binary). We can use this to build against a
snapshot and have the result use the original distribution that was
snapshotted.
Closes: #888507
|
|
Use a similar trick as for chroot_live-packages.
Relates to #944983.
|
|
Closes: #944983
|
|
Instead of emptying the file temporarily, just tell APT to use /dev/null
instead of /var/lib/dpkg/status. Relates to #944983
|
|
|
|
|
|
|
|
|
|
|
|
handling for ubuntu was dropped 2015-05-03
|
|
--hdd-partition-start
|
|
|
|
|
|
|
|
|
|
|
|
|
|
in the command line get ignored. Adds a documentation line for the other
command line options as well.
|
|
-f was --filesystem
-l was --language
-p was --package-list
-e was --encryption
|
|
functionality was added 2008-11-01, but was not really active.
|
|
|
|
Before Stretch there was an special amd64 kernel in the i386 arch repo.
So if you wanted to install an amd64 kernel alongside an i386 system
you did not need an additional arch repo.
Debian added multiarch support. That way you can install library packages
from multiple architectures on the same machine.
So there is no longer a need for having an amd64 kernel in i386 arch repo.
You can add an amd64 arch repo to an i386 arch system and fetch the amd64
kernel from the am64 arch repo.
live-build can be setup to use several linux kernel flavours in a single
image.
So in the days previous to this patch you could issue:
lb config --linux-flavours "486 amd64"
to use both 486 and amd64 kernel flavours.
Adding additional arch support to linux flavours poses two problems:
* Packages need to have its arch suffix (e.g. amd64:amd64).
If the suffix is not there apt-get insists on search amd64 kernel
package on i386 arch repo and, of course, fails to find it.
* The rest of the code which handles labels (bootloader config files)
or installed filenames (kernel images themselves) do not use the arch suffix.
This patch adds foreign architecture package support to
linux kernel flavours having taken those problems into account.
Practical example usage: i386 system and extra amd64 kernel.
First add amd64 foreign architecture in your i386 system
thanks to:
dpkg --add-architecture amd64
apt-get update
.
Finally enable amd64 kernel from amd64 arch alongside the
i386 system's 686 kernel thanks to:
lb config --architectures i386 --linux-flavours "686 amd64:amd64"
|
|
Turns out gcd works fine after adding /boot/grub/grub.cfg in the img,
as that's the path that gets hardcoded, and adding the EFI/debian/
grub.cfg was not necessary, so remove it.
|