=== guruprasad changed the topic of #launchpad to: Help contact: guruprasad (Indian Standard Time UTC+0530 hrs) | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide https://help.launchpad.net/ | Support and spam reporting: https://answers.launchpad.net/launchpad [05:55] what kind of markdown is supported in bug reports? Does ~some text~ work for a strikethrough? [07:27] ciphrCat, markdown is not supported. See https://bugs.launchpad.net/launchpad/+bug/391780 [07:27] Launchpad bug 391780 in Launchpad itself "Support Markdown 'stack overflow' style hyperlinks markup" [Low, Triaged] [16:37] ah, thanks. At least it’ll be easy to remember [16:41] cjwatson: thank you very much, it is working now. [21:00] DEBUG Considering changefile 91106/ubuntu/plasma-workspace_5.25.0-0ubuntu1~ubuntu22.04~ppa2_arm64.changes [21:00] DEBUG Finding fresh policy [21:00] INFO Processing upload plasma-workspace_5.25.0-0ubuntu1~ubuntu22.04~ppa2_arm64.changes [21:00] INFO Rejection during accept. Aborting partial accept. [21:00] INFO Upload was rejected: [21:00] INFO [lplibrarian-public-upload.internal:10004]: [Errno -2] Name or service not known [21:01] INFO Committing the transaction and any mails associated with this upload. [21:01] huh? [21:13] RikMills: when was that from? not today it seems ... [21:14] cjwatson: yes, today at 21:59 [21:14] oh I see, somehow my grep missed that [21:15] https://launchpad.net/~kubuntu-ninjas/+archive/ubuntu/plasma/+build/23846798 [21:15] ah, because I can't type [21:15] I guess we have occasional internal DNS issues, but I'm off for the next two days so won't be something I'm looking at :) [21:15] simplest immediate workaround will just be to retry the build of course [21:16] ok, kool. 2nd time that build did that, but it is superceded now anyway [21:16] somebody who isn't off should raise this with IS though [21:16] (who will probably need to escalate it to BootStack) [21:17] I have a retry scrip that will just poke until it succeeds ;) [21:17] well yeah, but good to chase down this sort of cloud reliability issue [21:17] indeed, hence my mentioning it [21:19] anyway, thanks :)