Jamming With Edward

• Remove repose dependency for the pacman's tooling.

As repose seems to no longer be active, let to use the proper pacman's tooling, such as repo-add and repo-del.

NOTE: tomato may not be able to be updated through tomato, run tomato --remove-update or rebuild tomato from AUR.

I'm not a criminal. Woah, that makes me sound more like a criminal, doesn't it.

• Let tomato repository to be in the alpm user group;
• Fix pikaur invalid configuration;
• Fix makepkg out of date.

This release may be no functional due to #12 .

Hold it right there. Both hands up!

• Fix repose build preventing the --rebuild-image option to operate.

'Fraid I'm fresh outta that stuff.

• Fix the --remote-update option.

NOTE: The 0.8.1 release is broken, and the --remote-update also.

You need to update yourself from the package provided on this release:

• https://github.com/aji-prod/tomato/releases/tag/v0.8.2

Or from the AUR package:

• https://aur.archlinux.org/packages/tomato

Come on, can't you show a little mercy and compassion?

• Fix pikaur build due to a base-devel missing;
• Fix repose unable to import some packages.

NOTE: As an invalid release was published, you may need to call tomato --remote-update to update tomato. (no working, see further release).

Waltz for Venus

• Fix [fakeroot](https://man.archlinux.org/man/fakeroot.1.en) hanging when called within the docker image;
• Fix some noises produced by the pikaur's --print-commands option;
• Add a new TOMATO_ULIMIT= configuration key to tweak the parameter passed to the --ulimit option for docker (the default one is nofile=1024:524288);
• Add a new --remote-update option, in case where tomato is broken, which will download the tomato package from GitHub and will install it on the system.

And it's not repulsive, it's very soothing. It's called heavy metal, by the way.

• Fix the prompt password with sudo when calling pikaur, due to a pikaur change;
• Fix minor alignments with tomato help;
• Output the commands used by pikaur to the console.

NOTE:

You will need to update manually tomato as the previous docker images can no longer call pikaur.
See https://github.com/aji-prod/tomato/tree/v0.7.3#installation

A pre-built package can be found in this release assets.

What are you still doing here?

• Fix non up-to-date archlinux-keyring when building the docker image.

  Sometimes, the docker image cannot be built on the pikaur stage,
  due to a non up to date archlinux-keyring. A fix pacman -Sy archlinux-keyring was present on previous stages be also need to
  be called when building pikaur.

But I did tell you. I told you just now!

• Fix non up-to-date archlinux-keyring.

  Sometimes, the packages are not updated due to untrusted GPG
  key from the archlinux-keyring, as the archlinux-keyring is updated
  too late. Try first to update the archlinux-keyring berfore anything
  else.

Heavy Metal Queen

• Update the archlinux docker base image;
• Add a --default-mirrors option on the image build to use the default
  mirrors from the Dockerfile instead of one of the host;
• Fix an error message from the package-cleanup.hook.