public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [NMU] inkscape 0.92.3-2 (Test)
Date: Wed, 6 Dec 2023 10:19:50 -0700	[thread overview]
Message-ID: <18e73e20-45c9-4c39-910b-91a8aa114e41@Shaw.ca> (raw)
In-Reply-To: <1a2caefd-ef39-4948-a2c1-c0aeb4dabce0@dronecode.org.uk>

On 2023-12-05 06:07, Jon Turney wrote:
> On 03/12/2023 17:50, Brian Inglis via Cygwin-apps wrote:
>> On 2023-12-03 08:33, Jon Turney via Cygwin-apps wrote:
>>> On 01/12/2023 09:17, Mark Geisert via Cygwin-apps wrote:
>>>>> If you have ideas about how to make things work better, I'm all ears.
>>>>> For the moment, I tweaked things to let your upload through.

>>>> Thanks Jon.  I have only seen a handful of NMUs go by and it didn't occur to 
>>>> me that those doing them were explicitly allowed to.
>>>> ISTM the process works fine as it is.  If I happen to have a future itch to 
>>>> do an NMU should I handle it as I did this one?  Or say something on 
>>>> cygwin-apps beforehand?  I don't expect it will be often.  I'm totally fine 
>>>> not being on the "trusted" list for this type of thing.

>>> If you ask in advance, that's possibly slightly less work for me, but either 
>>> is fine really.
>>> Maybe I should make things so that all maintainers can NMU orphaned packages. 
>>> That seems reasonable I guess?

>> Maybe Unmaintained except Base (i.e. alternatives crypto-policies) or 
>> "toolchain" defined as cygport and cygwin deps and build deps (i.e. bzip2 
>> cocom docbook git-archive-all robodoc); maybe also all their deps and build 
>> deps, even Devel and Libs?

> I was kind of hoping that base packages (and "dependencies of packages in base 
> which aren't in base themselves") aren't unmaintained, but obviously that was 
> being optimistic...

I thought I should take a peek in hopes too, but just in case, not being 
paranoid /much/, but like to have a bigger fan ready just in case! ;^>

Maybe we should work on publishing package adoption priority lists e.g.

1 Base 1.1 crypto-policies 1.2 alternatives
2 Build 1.1 cocom (now dino) 1.2 git-archive-all 1.3 robodoc 1.4 bzip2
	1.5 docbook... [lots of Unmaintained pkgs and deps]
3 Base direct deps
4 Build direct deps
5 Base indirect deps
6 Build indirect deps

I stopped once I looked at docbook...sob...! ;^>

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry


  reply	other threads:[~2023-12-06 17:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30  0:38 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 [this message]
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
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=18e73e20-45c9-4c39-910b-91a8aa114e41@Shaw.ca \
    --to=brian.inglis@shaw.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).