From: Jon Turney <jon.turney@dronecode.org.uk>
To: Brian Inglis via Cygwin <cygwin@cygwin.com>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Setup reinstall incomplete script does nothing
Date: Mon, 6 Feb 2023 14:50:46 +0000 [thread overview]
Message-ID: <139a8bbb-d9b0-6326-2f27-5c79b77c47f5@dronecode.org.uk> (raw)
In-Reply-To: <715117ac-7352-d298-b6db-cc9bf5b6f47e@Shaw.ca>
On 02/02/2023 22:42, Brian Inglis via Cygwin wrote:
> Hi folks,
>
> Using previously posted reinstall incomplete packages script as a number
> of my packages are now flagged Incomplete.
> The script now seems to do nothing to any package as setup comes up with
> a blank list of packages.
> Also tried a number of variations including shell script invocations,
> and adding options.
> Are there any missing or identical package conditions, options required,
> cmd, shell script, or setup program arg limits that might affect a
> remove/install?
>
> The package list used for ...\setup-X86_64 -x ... -P ... is:
> alacarte,antiword,bash,cron,ctags,dbus,debianutils,e2fsprogs,email,f22-backgrounds-extras,fbpanel,flaw,GeoIP-database,getent,gnu-free-fonts,gnupg,htmldoc,icon-naming-utils,initscripts,libcaca-devel,libcrypt-devel,liberation-fonts,libiconv-devel,libnspr-devel,libnss-devel,libopts-devel,libpng-devel,libpng16-devel,libproj12,mksh,perl_manpages,poppler,postfix,postfix-tools,procmail,python27,recode,sendmail,statgrab,sysvinit,tcp_wrappers,usbredir,usbutils,vim-clang-format,wodim,xml2po,zsh
>
Frowny face.
Yes, it looks like we've broken that. In fact, it seems like -x doesn't
work anymore.
If you could bisect old versions of setup [1] and tell us when it broke,
that would be very helpful.
[1] https://cygwin.com/setup/
prev parent reply other threads:[~2023-02-06 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 22:42 Brian Inglis
2023-02-06 14:50 ` Jon Turney [this message]
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=139a8bbb-d9b0-6326-2f27-5c79b77c47f5@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@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).