base: Resize rootfs after it's mounted

Just like it says. Using a unit, because resizing online is much easier than doing it right and in initrd.

I'm not sure if I did the copyright file correctly.

This will only work right when the cloud-initramfs-growroot_18-debian7 from sid is installed, but won't cause any harm otherwise.

changed the description

mentioned in issue image-builder#8 (closed)

added 1 commit

• f2756320 - base: Resize rootfs after it's mounted

Compare with previous version

it does not build anymore https://source.puri.sm/dorota.czaplejewicz/librem5-devkit-tools/pipelines/5132

The examples seem to use a different syntax, without a colon between Copyright and the text. I changed the text, but I still don't know if I did it right.

Check the examples there too (the text is a bit hard to parse by itself). If you're still unsure check the generated package using lintian.

added 1 commit

• d9cb9910 - base: Resize rootfs after it's mounted

Compare with previous version

After finding more examples in a different section on the same page, I believe I have the copyright correctly now.

added 1 commit

• 6cf15b0d - base: Resize rootfs after it's mounted

Compare with previous version

The service is now enabled, but I had to rename it, as dh_installsystemd doesn't offer a hint how to install a unit with a name other than the package name.

The service is now enabled, but I had to rename it, as dh_installsystemd doesn't offer a hint how to install a unit with a name other than the package name.

From the manpage (https://manpages.debian.org/stretch-backports/debhelper/dh_installsystemd.1.en.html#OPTIONS)

    --name=name
           This option controls several things.

           It changes the name that dh_installsystemd uses when it looks for maintainer provided systemd unit files as listed in the "FILES" section.  As an example, dh_installsystemd --name foo will look
           for debian/package.foo.service instead of debian/package.service).  These unit files are installed as name.unit-extension (in the example, it would be installed as foo.service).

           Furthermore, if no unit files are passed explicitly as command line arguments, dh_installsystemd will only act on unit files called name (rather than all unit files found in the package).

This allows you to preserver a more meaningful name (librem5-devkit-base.service is a bit generic).

added 1 commit

• fcd4738a - base: Resize rootfs after it's mounted

Compare with previous version

Sorry, I was clearly not paying enough attention. I believe all is fixed now.

Almost. It's

If --name=foo then the unit should be named debian/package.foo.service, so it should be

debian/librem5-devkit-base.resize_rootfs.service

I would not bother and apply this right away but it might break on us later otherwise.

resolved all discussions

added 1 commit

• da0b4c38 - base: Resize rootfs after it's mounted

Compare with previous version

I shall try until I learn from my mistakes.

merged

mentioned in commit f362dd31

Merged now. Thanks! This will make flatpacking a lot simpler.

Yes. Since https://packages.debian.org/buster/cloud-initramfs-growroot is at the right version, I will try it out now.