[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

maildir-utils 1.10 [Was: Re: Bug#1037765: maildir-utils: ftbfs with GCC-13]



On 2023-07-15, at 12:19:52 +0100, Jeremy Sowden wrote:
> On 2023-07-15, at 07:29:54 -0300, David Bremner wrote:
> > Matthias Klose <doko@debian.org> writes:
> > 
> > > Package: src:maildir-utils
> > > Version: 1.8.14-1
> > > Severity: normal
> > > Tags: sid trixie
> > > User: debian-gcc@lists.debian.org
> > > Usertags: ftbfs-gcc-13
> > >
> > > [This bug is targeted to the upcoming trixie release]
> > >
> > > Please keep this issue open in the bug tracker for the package it
> > > was filed for.  If a fix in another package is required, please
> > > file a bug for the other package (or clone), and add a block in this
> > > package. Please keep the issue open until the package can be built in
> > > a follow-up test rebuild.
> > 
> > I suspect we should probably move to a new upstream version rather than
> > adding yet another patch.
> 
> I did start looking at what would be involved and the new upstream
> version 1.10 has removed the deprecated autootools-based which is used
> in the 1.8 package, so I decided to leave alone. :)

I went back and took another look at the work required to package the
new upstream version, and updating the package to use the new build
system didn't turn out to be particularly tricky.  More time-consuming
was fixing all the Lintian warnings related to the man-pages (the new
version has replaced the old troff files with Org mode sources which are
converted using ox-man at build-time).

At this point, everything looks pretty good.  Lintian is reasonably
happy, the Salsa CI pipeline passes, the packages install successfully,
and the software seems to work.

I've pushed all the work to my fork:

  https://salsa.debian.org/azazel/maildir-utils/-/tree/packaging-1.10

for review.  I haven't raised an MR against the team repo, 'cause
obviously there are tags and multiple branches involved.

J.

> > However, if for some reason we want to stay with 1.8.14, it looks like
> > this specific issue is fixed by upstream commit
> > 
> >    ce9446465260bd108bcf554cf503f72304f4276b
> 
> The diff in that commit is:
> 
>   diff --git a/lib/utils/mu-error.hh b/lib/utils/mu-error.hh
>   index 55a8002c71e2..6472ce83b4d4 100644
>   --- a/lib/utils/mu-error.hh
>   +++ b/lib/utils/mu-error.hh
>   @@ -22,6 +22,7 @@
>    
>    #include <stdexcept>
>    #include <string>
>   +#include <cstdint>
>    
>    #include "mu-utils-format.hh"
>    #include <glib.h>
>   
> which is all that is needed to fix the FTBFS.

Attachment: signature.asc
Description: PGP signature


Reply to: