From: Jon Turney <jon.turney@dronecode.org.uk>
To: Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: cygwin-apps@cygwin.com
Subject: Re: Unmaintained packages in base package set
Date: Sun, 7 Jan 2024 12:54:35 +0000 [thread overview]
Message-ID: <b560262b-969b-4050-82fa-88ef49c17ba5@dronecode.org.uk> (raw)
In-Reply-To: <ea8dd725-f4b5-4ac4-a29a-806ac2edcf60@gmail.com>
On 03/01/2024 07:49, Marco Atzeri via Cygwin-apps wrote:
> On 03/01/2024 05:59, Takashi Yano via Cygwin-apps wrote:
>> On Sat, 23 Dec 2023 04:51:22 +0100
>> Marco Atzeri wrote:
>>> On 23/12/2023 04:42, Takashi Yano via Cygwin-apps wrote:
>
>>> I suggest to start with the smaller beasts one by one or small groups
>>> I suspect GTK3 needs a lot of effort
>>
>> Thanks for the advice.
>>
>> Now, GTK3 package of 3.24.39 has been successfully built and packaged
>> in my environment with updating some other related packages.
>>
>> So, firstly, I would like to take over following packages that are
>> related
>> to GTK3.
>>
>> fribidi 0.19.7 -> 1.0.13
>> libdatrie 0.28 -> 0.2.13
>> libthai 0.1.26 -> 0.1.29
>> pango1.0 1.40.14 -> 1.51.0
>> atk1.0 2.26.1 -> 2.38.0
>> gtk3 3.22.28 -> 3.24.39
>>
Firstly, thanks for taking over these.
> ERROR: package 'atk1.0-src' version '2.38.0-1' build-depends: 'girepository(GLib-2.0)', but nothing satisfies that
> ERROR: package 'atk1.0-src' version '2.38.0-1' build-depends: 'pkgconfig(glib-2.0)', but nothing satisfies that
> ERROR: package 'libatk1.0-doc' version '2.38.0-1' has empty install tar file, but it's not in ['_obsolete'] category
I guess I should ask about these errors and how you fixed them:
* This documented but unimplemented style of dependency atom was dropped
[1], because we don't have a good way of supporting it.
But rather than just removing them, they should probably have been
replaced with the appropriate package names (those containing
GLib-2.0.gir and glib-2.0.pc, i.e. girepository-GLib2.0 and
libglib2.0-devel)
* Are you sure that libatk1.0-doc should be empty now (and not that it
requires some tool to build the documentation which isn't installed)?
If it is the case that the documentation doesn't exist any more, I think
you should perhaps make some arrangement for obsoleting the package,
rather than simply stopping generating it, allowing the previous version
to linger indefinitely in places where it is already installed.
(e.g. obsoleting it by the devel package, or marking the package as
self-destruct)
[1]
https://cygwin.com/cgit/cygwin-apps/cygport/commit/?id=c8cb44a50377fb87c579280a490fc127562ced40
next prev parent reply other threads:[~2024-01-07 12:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 0:38 [NMU] inkscape 0.92.3-2 (Test) Mark Geisert
2023-11-30 13:45 ` Jon Turney
2023-12-01 9:17 ` Mark Geisert
2023-12-03 15:33 ` Jon Turney
2023-12-03 17:50 ` Brian Inglis
2023-12-05 13:07 ` Jon Turney
2023-12-06 17:19 ` Brian Inglis
2023-12-06 17:30 ` Brian Inglis
2023-12-20 12:16 ` Unmaintained packages in base package set Jon Turney
2023-12-21 4:27 ` Marco Atzeri
2023-12-22 2:06 ` Mark Geisert
2023-12-22 16:37 ` Jon Turney
2023-12-23 3:42 ` Takashi Yano
2023-12-23 3:51 ` Marco Atzeri
2024-01-03 4:59 ` Takashi Yano
2024-01-03 7:49 ` Marco Atzeri
2024-01-07 12:54 ` Jon Turney [this message]
2024-01-07 13:35 ` Takashi Yano
2024-01-07 15:14 ` Takashi Yano
2024-01-07 15:44 ` ASSI
2024-01-26 5:03 ` Marco Atzeri
2024-01-03 15:39 ` 1dakotaxi
2023-12-11 19:21 ` [NMU] inkscape 0.92.3-2 (Test) ASSI
2023-12-14 6:57 ` Mark Geisert
2023-12-23 0:37 ` Mark Geisert
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=b560262b-969b-4050-82fa-88ef49c17ba5@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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).