-
-
Notifications
You must be signed in to change notification settings - Fork 25
Build deb with dovecot delay patch #249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
We have forked Debian repo at https://github.com/chatmail/dovecot |
any ideas how we best provide a repository? |
I don't actually get what the problem with the first option is. Does build.opensuse.org support only the latest Debian version? |
This may sound stupid, but after your last message I searched again for some kind of documentation and now I got it. I tried to build the package like described here: https://www.sidorenko.io/post/2016/05/build-packages-with-openbuild-service/ This did not work - but I now found this page (which for some reason doesn't seem indexed by search engines): https://en.opensuse.org/openSUSE:Build_Service_Debian_builds And this explanation actually works :) So yeah, I'm now all in favor of the first option again. |
Hooray, we have a deb and repo: https://download.opensuse.org/repositories/home:/deltachat/Debian_12/ https://build.opensuse.org/package/show/home:deltachat/ Here is the explanation for adding the repo, I'll add instructions tomorrow: https://en.opensuse.org/openSUSE:Build_Service_Debian_builds#Adding_repository_signing_key |
https://build.opensuse.org/package/show/home:deltachat/ gives 404 the input flowing into the build-process there should be committed into a separate "deltachat/debian-builds" one with a proper README -- along with being explicit what kind of permissions/passwords are neccessary. |
The obs is doing odd things - it automatically creates a signing key, but does not sign the deb. The docs imply that it should do that. I'll ask around in the obs matrix channel; until I get a reply this is issue is blocked. We can use the deb, but for that we would have to disable the signing check in apt and that doesn't seem a reasonable solution. |
I always thought Debian solution is usually to sign repositories, not individual .deb files, at least for official repositories. When I compiled Dovecot manually, I just installed it with There is a |
okay, now it finally works. @link2xt, you are correct. And I finally found out how to add the repository. and the key in a way that debian likes. Apparently using apt-add-repository, editing So, here are the steps: Add our signing key to the apt keyring
Add to
Install dovecot 🥳
|
happy to announce that we now have an ARM build for dovecot too :) There is a debian runnner for ARM in the OBS, it's just that the docs are wrong, lol |
We need a deb with dovecot with the patch for #72 included.
I first tried doing this at build.opensuse.org - but building debs with tons of additional backports from debian doesn't seem to be supported there - or at least not at all documented.
We now have (at least) 2 options:
IMO option 2 would be the preferable option, at least until we decide to move chatmail to nixos 😆
Will implement the building part now, we have to see how we best provide a repository then
The text was updated successfully, but these errors were encountered: