Arch Linux User Repository

oama is the successor of mailctl from the same author.

Please, report oama related issues upstream and use this place for AUR related problems only.

@Igneo676 I appreciate your concerns but don't share your priorities. I might not have chosen the best way to do it in retrospect but don't want to spend more time on this deprecation issue.

Both of your problems can be solved easily. Ignore mailctl-bin in pacman.conf. You can install the last proper version of mailctl-bin on a new systems by cloning its AUR repo, and installing the version you need by makepkg.

@petrus7 please don't force an error on build here. If you're looking to specify that the package is deprecated, please include it in the package itself with a notification instead of at build time

For one, if I'm setting up a new computer today and I haven't migrated to oama, then I'm now forced to do the switch instead of being able to migrate at my own pace. Not to mention the general confusion when my upgrades now fail on my computers

@petrus7 I'm not talking about empty binary package, but empty source package, i.e. PKGBUILD that does nothing. It will only confuse new users who find it here while old users will get a notification when the package is merged/deleted.

@lahwaaz thanks, but I do not want either of them.

This PKGBUILD is intentionally set to fail during install, no empty package get installed. I was hoping that the pre_install, pre_upgrade will show the message so all of my old users get a notification about oama. Some of them don't/can't immediately change. Unfortunately, nothing shown by pre_upgrade, I don't know why.

Edit: Success: the package() function finally shows the message before failing so mailctl users gradually get notified about oama.

@petrus7 You can ask for this package to be deleted or merged into oama-bin instead of leaving empty: https://wiki.archlinux.org/title/AUR_submission_guidelines#Requests

Unfortunately, the replaces functionality does not work for AUR packages, only for the official and user package repositories. However, I figured out a trick to work around this limitation so users of mailctl will be notified soon.

The transition and config of oama is easy just read the docs.

If oama is the replacement for mailctl, then it might be useful to use the PKGBUILD function replaces.

https://wiki.archlinux.org/title/PKGBUILD#replaces

This combined with an upgrade/migration script could result in an automated and seamless transition for its users. I am not sure if this is actually possible, but hopefully it is.

Hi Peter,

Thanks for all your efforts!

I have several machines still using mailctl-bin. Is there a 'migration guide' available to make my life easier? :)

oama is the successor of mailctl from the same author.

Please, report oama related issues upstream and use this place for AUR related problems only.