From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from omta001.cacentral1.a.cloudfilter.net (omta001.cacentral1.a.cloudfilter.net [3.97.99.32]) by sourceware.org (Postfix) with ESMTPS id D06F63858D38 for ; Fri, 30 Sep 2022 17:55:11 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org D06F63858D38 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=systematicsw.ab.ca Received: from shw-obgw-4003a.ext.cloudfilter.net ([10.228.9.183]) by cmsmtp with ESMTP id eHSpowE5LS8WreKEBoAqTR; Fri, 30 Sep 2022 17:55:11 +0000 Received: from [10.0.0.5] ([184.64.124.72]) by cmsmtp with ESMTP id eKEAo9Vxtg786eKEAorhBw; Fri, 30 Sep 2022 17:55:11 +0000 X-Authority-Analysis: v=2.4 cv=a94jSGeF c=1 sm=1 tr=0 ts=63372d7f a=oHm12aVswOWz6TMtn9zYKg==:117 a=oHm12aVswOWz6TMtn9zYKg==:17 a=IkcTkHD0fZMA:10 a=GHR8O2WEAAAA:20 a=uYT-Tk0qkVT609LjNaIA:9 a=QEXdDO2ut3YA:10 Message-ID: Date: Fri, 30 Sep 2022 11:55:10 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.13.1 Reply-To: Cygwin Applications Subject: Re: gsasl 2 libgsasl{18,-common,-devel,-doc} Content-Language: en-CA To: Cygwin Applications References: <8c52863b-9717-3442-11d6-2d8a951720a0@gmail.com> <61cd6277-3665-2dd6-b75c-8fe7a7210c96@SystematicSw.ab.ca> Cc: Brian.Inglis@SystematicSw.ab.ca From: Brian Inglis Organization: Systematic Software In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4xfJdhLGupo6C2kGYsb2tbsP4fyAc+F0jl3LLMR1sZMz6uVTRBvrOVVUWblv4jfhGDrG8/s2d2jY8hUrjMlKsSawR++ppiq6ikTcFtYhrkL7tCctQ8OKIk 4iQp9kxcfoDzxQ5Y/FGgwsk+qoOYPeOXo++vZXxdoRl9e7Tr4iMlmCiwy08G3neq5Q/aD/iBPvasbGFCKvvWhswbgdTcQGO0/ZiLL5siWCIFQLWd0skhA0hh lZfsmnhV6RG/MJPsDJrjTw== X-Spam-Status: No, score=-1164.0 required=5.0 tests=BAYES_00,KAM_DMARC_STATUS,KAM_LAZY_DOMAIN_SECURITY,NICE_REPLY_A,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 2022-09-30 06:39, Jon Turney wrote: > On 29/09/2022 07:49, Brian Inglis wrote: >> >> Hi folks, [Please Reply All as ISP blocking Cygwin mail] >> >> It looks as if gsasl 2 is ABI 18 compatible with gsasl 1.10, so I am >> looking to release 2.2 as a continuation of the existing versions, and >> that is consistent with FreeBSD and Debian, where the developer >> appears to be among the package maintainers. >> >> One issue is that autoreconfig replaces the package provided >> gtk-doc.make with one from /usr/share/gtk-doc/data/gtk-doc*.make and >> they (all) need patched to build PDFs with DESTDIR builds. >> >> I handled this with local patches, added a src_patch_apply_hook to >> apply these for scallywag builds, and submitted patches upstream to >> the gsasl list and gtk-doc repo. > > Is this the relevant patch? > > https://gitlab.gnome.org/GNOME/gtk-doc/-/issues/147 > >> The current orphaned gtk-doc cygport build seems to work automagically >> from the upstream tar(.xz) included in the source package, and I am >> too ignorant of Gnome, GTK, dblatex, TeX, etc., that I am >> uncomfortable adopting gtk-doc, as I have enough backlogged package >> updates. >> >> Suggestions for doing a non-maintainer update? > I'm not sure what you are asking for here. > > If you like, I can review and apply that patch to our package, and > rebuild it (since it seems I made the last one). > > If you'd like NMU privileges, I think that would be ok also (in current > upload authorization scheme certain maintainers are allowed to upload > orphaned packages, there is no general NMU upload privilege). > > The gtk packages are kind of important, it's unfortunate that we don't > have a maintainer for them. I've tried building gtk-doc, locally and in Scallywag, but check gives me more FAILs than PASSes, so if you can build with PASSes, that would be better! -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.]