Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#78340 - [neomutt] addition of --ubsan flag causing runtime error

Attached to Project: Community Packages
Opened by Jason Croyle (croyleje) - Sunday, 30 April 2023, 17:51 GMT
Last edited by freswa (frederik) - Friday, 12 May 2023, 13:06 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Leonidas Spyropoulos (inglor)
freswa (frederik)
Maxim Baz (maximbaz)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
runtime error caused by addition of --ubsan build flag. This is a known issue and has been patch and merged into the neomutt main branch upstream
I have supplied the links to relevant bug reports and change logs below.


Additional info:
* package version(s)
* config and/or log files etc.
* link to upstream bug report, if any

NeoMutt 20230407

Neomutt bug report, fix and merger
https://github.com/neomutt/neomutt/issues/3833

This issue is related to an issue that was patched earlier those links are below.
https://bugs.archlinux.org/task/77987
https://github.com/neomutt/neomutt/issues/3774

Steps to reproduce:
Install current Arch build of Neomutt package and delete mail from remote(imap) account.

Note: I have looked but been unable to determine if the patch used to correct issue 3774 has been merged into the
main branch also so I do believe the patch is still required to resolve issue 3774.
This task depends upon

Closed by  freswa (frederik)
Friday, 12 May 2023, 13:06 GMT
Reason for closing:  No response
Comment by freswa (frederik) - Sunday, 30 April 2023, 19:37 GMT
Please do as you're told and test the changes in https://github.com/neomutt/neomutt/issues/3833
Comment by Jason Croyle (croyleje) - Monday, 01 May 2023, 01:57 GMT
I am unsure if this comment was directed to me or not but I will do as I wish and if you bothered to read the supplied information you would see the issue has already been taken care of upstream and merged into the main branch. So do as your told and read the report.
Comment by Toolybird (Toolybird) - Monday, 01 May 2023, 06:02 GMT
Hey, as a fellow grumpy ass, I can relate to the response from @freswa. Apologies for the tone but it wasn't clear if the changes had been tested by you. I see the merge and it's all fine now. @freswa was in the middle of a massive toolchain update/rebuild which is enough to make anyone cranky, trust me :)
Comment by freswa (frederik) - Monday, 01 May 2023, 08:48 GMT
Ouch. Sorry for the tone, it wasn't my intention to come across as grumpy or cranky.

On topic:
Thank you for taking the time to report the issue upstream and here!
There has been a code review and a request in the issue to have a look at/test the PR branch to which I can't find an answer just now. I'd kindly ask you to test the change, applied to the latest neomutt release, first before we backport it :)
If you lack the time, please feel free to use neomutt-git in the meantime. I guess a neomutt release will happen in a few weeks anyways :)

Loading...