summaryrefslogtreecommitdiff
path: root/debian/changelog
AgeCommit message (Collapse)Author
2021-04-07Update changelog for 1:20210407 releasedebian/1%20210407Luca Boccassi
2021-04-05Update changelog for 1:20210405 releaseLuca Boccassi
2021-03-30Update changelog for 1:20210330 releasedebian/1%20210330Luca Boccassi
2021-03-29Fix typo in changelogLuca Boccassi
E: live-build: possible-missing-colon-in-closes Gbp-Dch: ignore
2021-03-29Update changelog for 1:20210329 releasedebian/1%20210329Luca Boccassi
2021-02-16Update changelog for 1:20210216 releasedebian/1%20210216Luca Boccassi
2021-01-22Update changelogRaphaël Hertzog
2021-01-22Update changelog for 1:20210122 releaseRaphaël Hertzog
2021-01-12Update changelogRaphaël Hertzog
2021-01-12Update renamed lintian tag names in lintian overrides.Raphaël Hertzog
Changes-By: lintian-brush Fixes: lintian: renamed-tag See-also: https://lintian.debian.org/tags/renamed-tag.html
2020-09-25Update renamed lintian tag names in lintian overrides.Raphaël Hertzog
Changes-By: lintian-brush Fixes: lintian: renamed-tag See-also: https://lintian.debian.org/tags/renamed-tag.html
2020-03-12Fix typo in changelogLuca Boccassi
Gbp-Dch: ignore
2020-03-05Fix Lintian Warnings about changelog: day-of-week, trailing whitespaceLuca Boccassi
2020-03-05Add some initial changelogRaphaël Hertzog
I do this to manually add the bug closure for #952834 and #952834 since they were merged with an invalid bug closure syntax. Same for #952839 which also was tagged with "Gbp-Dch: Ignore" thus not generating any changelog entry... a changelog entry is required to be able to close a bug!
2019-12-19Update changelog for 1:20191221 releasedebian/1%20191221Raphaël Hertzog
2019-12-19Update changelog for 1:20191220 releasedebian/1%20191220Raphaël Hertzog
2019-12-19Update my email in the Maintainer fielddebian/1%20191219Raphaël Hertzog
The work I do on live-build is done as part of the work I do for Kali.
2019-12-19Update changelog for 1:20191219 releaseRaphaël Hertzog
2019-03-15Open changelog for 1:20190315, close 884553Luca Boccassi
2019-03-11Close 924293 in d/changelogdebian/1%20190311Luca Boccassi
2019-03-11Update changelog for 1:20190311 releaseLuca Boccassi
2018-09-25Update changelog for 1:20180925 releasedebian/1%20180925Luca Boccassi
2018-06-18Update changelog for 1:20180618 releasedebian/1%20180618Luca Boccassi
2018-04-11Update changelog for 1:20180411 releasedebian/1%20180411Luca Boccassi
2018-03-28Update changelog for 1:20180328 releasedebian/1%20180328Luca Boccassi
Set urgency to low to allow for more time in unstable
2018-02-24Update changelogRaphaël Hertzog
2018-02-14Fix Check_package invocation in binary_hdd for ntfs-3gRaphaël Hertzog
/sbin/mkfs.nfts -> /sbin/mkfs.ntfs
2018-02-14Add e2fsprogs to Suggests along with mtd-utils, partedRaphaël Hertzog
Closes: #887278
2017-12-21Failsafe entries rework at binary_loopback_cfgAdrian Gibanel Lopez
[hertzog@debian.org: - Fix conflicts due to renamed variables ] Signed-off-by: Raphaël Hertzog <hertzog@debian.org>
2017-12-21Fix handling of multiple kernels in binary_loopback_cfgAdrian Gibanel Lopez
Now grub.cfg shows all the kernel options. Before this patch when you had more than two kernels it only showed the auto option. Signed-off-by: Raphaël Hertzog <hertzog@debian.org>
2017-12-21Updated binary_loopback_cfg so that it uses Stretch's 686 kernel instead of ↵Adrian Gibanel Lopez
old 486 one. [hertzog@debian.org: Also rename the variables for consistency. ] Signed-off-by: Raphaël Hertzog <hertzog@debian.org>
2017-12-07Prepare release to unstabledebian/1%20171207Raphaël Hertzog
2017-11-20Fix the way the .disk/mkisofs file is createdRaphaël Hertzog
Thanks to Daniel Reichelt <debian@nachtgeist.net> for the patch. Closes: #881941
2017-11-20Don't fail when initramfs is not usedBalint Reczey
Signed-off-by: Raphaël Hertzog <hertzog@debian.org>
2017-11-20Use $SOURCE_DATE_EPOCH when updating timestamps of manual pagesRaphaël Hertzog
This makes the package reproducible at build time. Closes: #879169
2017-09-20Prepare for releasedebian/1%20170920Raphaël Hertzog
2017-09-18Replace "kirkwood" and "orion5x" armel flavors with the new "marvell" oneRaphaël Hertzog
As done by the linux source package since its version 4.4.
2017-09-01Handle hardlinks in binary_hddMatthijs Kooijman
To generate an hdd image, binary_hdd first estimates the needed size of the image using du. By default, when du finds multiple hardlinked copies of a file, it counts them only once. However, when the target filesystem is FAT, which does not support hardlinks, these files will take up more space when finally copying the contents, breaking the build: P: Copying binary contents into image... cp: error writing 'chroot/binary.tmp/live/initrd.img-4.9.0-3-amd64': No space left on device cp: error writing 'chroot/binary.tmp/efi/boot/bootx64.efi': No space left on device cp: error writing 'chroot/binary.tmp/efi/boot/bootia32.efi': No space left on device cp: cannot create directory 'chroot/binary.tmp/boot/grub': No space left on device cp: cannot create directory 'chroot/binary.tmp/isolinux': No space left on device To fix this, pass --count-links to du when the target is FAT, to make the space estimation correct. This problem is exposed by commit 9c974b26b (Instead of renaming kernel for syslinux, create hardlinks), which might need to be separately fixed (to not waste space on FAT targets), but binary_hdd should at least handle hardlinks more gracefully.
2017-09-01Add changelog entryRaphaël Hertzog
2017-09-01Pass --partscan to losetupMatthijs Kooijman
Recent versions of Linux, parted or some other bit of software cause partition devices, like /dev/loop0p1 to be created when running parted mkpart. However, these devices are not cleaned up when running losetup -d to remove /dev/loop0 later, so they linger around and confuse mkfs (which refuses to make a filesystem, thinking there are partitions): mkfs.fat 4.1 (2017-01-24) mkfs.vfat: Partitions or virtual mappings on device '/dev/loop0', not making filesystem (use -I to override) To prevent this behaviour, pass --partscan to losetup when adding a new partition, to clean up any lingering partitions. It seems losetup does not accept --partscan when deleting a loop device, to clean up at that point, but since binary_hdd mounts the partition last, there should not be any lingering partition devices after live-build is done. The --partscan option is available since util-linux 2.21 (released in 2012), so it should be fairly safe to pass it unconditionally.
2017-08-29Update changelogRaphaël Hertzog
2017-08-29Auto-update version strings in manual pages.Raphaël Hertzog
2017-08-29Prepare release to unstabledebian/1%20170829Raphaël Hertzog
2017-08-29Drop all references to live-systems.org and update copyright fileRaphaël Hertzog
Also fix the version string in the manual pages. Closes: #859290
2017-08-29Initialize /etc/default/locale with LANG=C.UTF-8Raphaël Hertzog
That way we always have a valid UTF-8 locale even when we don't have the "locales" (or "locales-all") package installed.
2017-08-10Add .disk/mkisofs file recording the xorriso command lineRaphaël Hertzog
Thanks to Thomas Schmitt <scdbackup@gmx.net> for the suggestion.
2017-08-07Prepare release to unstabledebian/1%20170807Raphaël Hertzog
2017-08-07Drop the --hardlinks option from xorriso command line callRaphaël Hertzog
2017-06-09Add keyboard shortcut on the "Advanced options" syslinux menu entryRaphaël Hertzog
Thanks to Daniel Reichelt <debian@nachtgeist.net> for the patch. Closes: #864386
2017-02-13Prepare release to unstabledebian/1%201702131.2.9-S1cruxRaphaël Hertzog
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-21 06:52:20 +0000