vcswatch reports that
this package seems to have new commits in its VCS but has
not yet updated debian/changelog. You should consider updating
the Debian changelog and uploading this new version into the archive.
Here are the relevant commit logs:
commit ccfa8f76f807beec0aa8e6eb3e003b7efd005b44
Author: Sunil Mohan Adapa <sunil@medhas.org>
Date: Sat Jan 11 11:35:58 2025 -0800
builders: i368: Drop all i386 targets
- Looks like Debian has decided to stop (or will stop) supporting i386
architecture. This means no kernel and debian-installer support will be present.
Users can use i386 inside chroot or with multi-arch support.
- Builds for i386 on buildbot have been failing for a while because the kernel
package we use for it is no longer in testing.
- We haven't come across hardware that needs i386 in a long time. I have a very
old laptop that can't run VM (with hardware support) in amd64 arch even though
the CPU is amd64. I haven't touch that laptop in quite a while.
Tests:
- Unit tests work (without running VM tests).
Signed-off-by: Sunil Mohan Adapa <sunil@medhas.org>
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
commit afc1d72085f31c81edb0d2febf087a533e2d16ef
Author: James Valleroy <jvalleroy@mailbox.org>
Date: Sat Jan 18 12:39:18 2025 -0500
d/tests: Add breaks-testbed restriction
This fixes autopkgtest issues when systemd-resolved is installed.
Signed-off-by: James Valleroy <jvalleroy@mailbox.org>
commit e1d689d33910bef275f7c08d8182006afab98908
Author: Sunil Mohan Adapa <sunil@medhas.org>
Date: Sun Sep 22 10:36:59 2024 -0700
d/control: Add dependency on systemd-resolved
Latest version of freedombox package depends on systemd-resolved. After
systemd-resolved is installed, the file /etc/resolv.conf is a symlink to a file
that lists 127.0.0.53 as the only resolver. Since there are no daemons running
inside the chroot environment, all further resolutions will fail unless the host
machine performing the chroot is running systemd-resolved (and listening on
127.0.0.53).
Tests:
- Latest image build on CI server succeeds if systemd-resolved is installed on
the machine building the image.
- Buildbot is able to build the images without failing.
Signed-off-by: Sunil Mohan Adapa <sunil@medhas.org>
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
commit 389f3af44169a5d848311d7900b785e2c03e0d06
Author: Sunil Mohan Adapa <sunil@medhas.org>
Date: Thu Aug 15 17:47:19 2024 -0700
vagrant: Build vagrant box without virtualbox
- This makes the builds more reliable.
- The generated .vmdk file inside the .box file is not compressed leading to
slightly increased size.
- The .box file is a tarball with contents according to
https://developer.hashicorp.com/vagrant/docs/boxes/format.
- Perform customization operations on the image while it being built.
Signed-off-by: Sunil Mohan Adapa <sunil@medhas.org>
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
commit 83f219eedf822b7e691fcc439d1f71b4f58e1da1
Author: Sunil Mohan Adapa <sunil@medhas.org>
Date: Thu Aug 15 22:55:13 2024 -0700
internal: Allow builders to customize the built image
Signed-off-by: Sunil Mohan Adapa <sunil@medhas.org>
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
commit 96d0962392c8624ccf9c81105fb75caa48f38d80
Author: Philippe Coval <rzr@users.sf.net>
Date: Sat Feb 10 14:36:54 2024 +0100
builder: Add support for Olimex A20-OLinuXino-MICRO-eMMC
Those who have the eMMC version of the board,
could be interested to be able to use this extra space
even if freedombox is not currently using it.
For the record, I came to this change while testing a u-boot change
that enable reboot on Olimex A20 micro.
Relate-to: https://salsa.debian.org/debian/u-boot/-/merge_requests/34
Forwarded: https://salsa.debian.org/freedombox-team/freedom-maker/-/merge_requests/242
Signed-off-by: Philippe Coval <rzr@users.sf.net>
![[bug history graph]](https://qa.debian.org/data/bts/graphs/f/freedom-maker.png){kind=link}