This is back in Jammy and working:
mini-buildd | 1.9.99 | jammy/universe | source, all
It didn't resolve the issue of >1.0 being generally unstable, but what we had
works again.
Thanks
** Changed in: mini-buildd (Ubuntu)
Status: In Progress => Fix Released
--
You received this
The attachment "Invalid email error fix" seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag,
Here is the debdiff patch containing the email fix. Tested and confirmed
using PPA: ppa:lvoytek/mini-buildd-newest-with-email-patch. As a warning
there is no upstream tarball location for mini-buildd so the patch only
works when applied directly rather than through debian/patches
** Patch added:
> Hopefully this can be added in a new version to
> be released soon, otherwise mini-buildd may have to be re-added with a
> temporary delta.
Thank you Lena, but due to time - unless they release super-fast - let
us prepare and add this with delta right away once the beta freeze is
lifted
I managed to fix the error by setting up a custom email validation that
allows hostnames without a '.' in them to work properly. I sent the
merge request upstream. Hopefully this can be added in a new version to
be released soon, otherwise mini-buildd may have to be re-added with a
temporary
** Changed in: mini-buildd (Ubuntu)
Status: New => In Progress
** Changed in: mini-buildd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965724
After digging deeper into mini-buildd stable I can confirm that a transition to
python3 from 1.0.49 would be really difficult and probably not worth all the
effort depending on when 2.0 comes out.
As for the bleeding edge, 1.9.98 and it is still showing the email error shown
above. I'm still
Right now to me it seems we need to choose between pain, pain and more
pain:
- do a python3 transition with mini-buildd 1.0.49
+ that seems to be the reason we had 1.1.19 in Focal, and 1.0.49
isn't ready yet
+ Back in Apr 2021 v2.0 was called 2 weeks away, still not released
today
