From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: Cygwin Applications <cygwin-apps@cygwin.com>
Cc: Brian.Inglis@SystematicSw.ab.ca
Subject: Re: gsasl 2 libgsasl{18,-common,-devel,-doc}
Date: Fri, 30 Sep 2022 11:55:10 -0600 [thread overview]
Message-ID: <dae67503-a628-bb38-ff7c-960b58bb705b@SystematicSw.ab.ca> (raw)
In-Reply-To: <f604a98c-fe23-236f-ec3a-2d34cf7e023a@dronecode.org.uk>
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.]
next prev parent reply other threads:[~2022-09-30 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 5:10 [ITA] gsasl libgsasl{7,-common,-devel,-doc} gsasl 2 Brian Inglis
2022-07-18 11:43 ` Marco Atzeri
2022-07-18 15:18 ` Brian Inglis
2022-09-29 6:49 ` gsasl 2 libgsasl{18,-common,-devel,-doc} Brian Inglis
2022-09-30 12:39 ` Jon Turney
2022-09-30 17:55 ` Brian Inglis [this message]
2022-07-18 16:14 ` [ITA] gsasl libgsasl{7,-common,-devel,-doc} gsasl 2 ASSI
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dae67503-a628-bb38-ff7c-960b58bb705b@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).