encoding rather than hex
to shorten the checksum representation, in recent coreutils.
We all have SSH keys, which I also have as a GPG key, could we also use them for
signing source packages?
Calm could validate ours and checksums, and re-sign with Cygwin key, which setup
could validate.
Could
On 01/05/2024 17:48, Brian Inglis via Cygwin-apps wrote:
On 2024-04-30 23:32, ASSI via Cygwin-apps wrote:
Brian Inglis via Cygwin-apps writes:
Some package upstreams offer only checksums, for example .sha512sum,
.sha256sum,
for verification rather than gpg signatures, for example .asc, .sig,
On 2024-04-30 23:32, ASSI via Cygwin-apps wrote:
Brian Inglis via Cygwin-apps writes:
Some package upstreams offer only checksums, for example .sha512sum, .sha256sum,
for verification rather than gpg signatures, for example .asc, .sig, .sign, etc;
use these checksum files when provided in a
Brian Inglis via Cygwin-apps writes:
> Some package upstreams offer only checksums, for example .sha512sum,
> .sha256sum,
> for verification rather than gpg signatures, for example .asc, .sig, .sign,
> etc;
> use these checksum files when provided in a similar manner to gpg signatures;
> these
From: "Brian Inglis"
Some package upstreams offer only checksums, for example .sha512sum, .sha256sum,
for verification rather than gpg signatures, for example .asc, .sig, .sign, etc;
use these checksum files when provided in a similar manner to gpg signatures;
these files are often provided with
of the analysis I was doing for python2 packages and
the results are now available at [1].
So yeah, it looks like nothing uses 3.5.
There are just a couple of packages using 3.6, I guess I'll ping the
maintainers about those.
[1] https://cygwin.com/packages/reports/python_rebuilds.html
Ake,
Hi Jon
t;>>
> >>>>>> Is it possible to update/rebuild rdiff-backup, which replies upon
> >>>>>> the soon-to-be removed python36?
> >>>>>>
> >>>>>> (Or indicate that you are no longer interested in maintaining this
> >>&g
as the maintainer from that package. I no longer use
it, and no longer have an environment for building packages for Cygwin.
No problem. Thanks for maintaining it in the past.
Is the same true for your other packages?
$ grep Rothenberger cygwin-pkg-maint | grep -v ORPHANED
cyrus-sasl
t you are no longer interested in maintaining this
> >>>> package, which will probably lead to it's removal).
> >>>
> >>> Please remove me as the maintainer from that package. I no longer use
> >>> it, and no longer have an environment for bui
replies upon
the soon-to-be removed python36?
(Or indicate that you are no longer interested in maintaining this
package, which will probably lead to it's removal).
Please remove me as the maintainer from that package. I no longer use
it, and no longer have an environment for building packages
that you are no longer interested in maintaining this
package, which will probably lead to it's removal).
Please remove me as the maintainer from that package. I no longer use
it, and no longer have an environment for building packages for Cygwin.
No problem. Thanks for maintaining it in the past
2021)?
(I'm still dealing with cleaning up the final pieces of python27
detritus, but these should hopefully be much smaller tasks)
nothing should depend from 3.5
not sure for 3.6
I've automated some of the analysis I was doing for python2 packages and
the results are now available at [1
in maintaining this
package, which will probably lead to it's removal).
Please remove me as the maintainer from that package. I no longer use
it, and no longer have an environment for building packages for Cygwin.
No problem. Thanks for maintaining it in the past.
Is the same true for your other
for python2 packages
and the results are now available at [1].
So yeah, it looks like nothing uses 3.5.
There are just a couple of packages using 3.6, I guess I'll ping the
maintainers about those.
[1] https://cygwin.com/packages/reports/python_rebuilds.html
David,
Is it possible to update/rebuild
python{2{,7},3{,6,7,8,9}}-nghttp2?
Does this have to remain in the cygport forever to avoid keeping nghttp2
vx.x.x around?
You could, but that's probably not the correct thing to do unless you really,
really want to forcibly uninstall those packages for anyone who has installed
them, which
2021)?
(I'm still dealing with cleaning up the final pieces of python27
detritus, but these should hopefully be much smaller tasks)
nothing should depend from 3.5
not sure for 3.6
I've automated some of the analysis I was doing for python2 packages and
the results are now available at [1
2021)?
(I'm still dealing with cleaning up the final pieces of python27
detritus, but these should hopefully be much smaller tasks)
nothing should depend from 3.5
not sure for 3.6
I've automated some of the analysis I was doing for python2 packages and
the results are now available at [1
to remain in the cygport forever to avoid keeping nghttp2
vx.x.x around?
You could, but that's probably not the correct thing to do unless you
really, really want to forcibly uninstall those packages for anyone who
has installed them, which seems like unnecessary breakage.
I don't think you have
Turney via Cygwin-apps wrote:
[...]
Not sure why my source package nghttp2 shows python install packages, when
they were dropped after 1.43 IIRC: build deps no longer include python/-devel?
If you haven't taken any specific action to retire the python-3x-nghttp2
packages, the existing ones
source package nghttp2 shows python install packages,
when they were dropped after 1.43 IIRC: build deps no longer include
python/-devel?
If you haven't taken any specific action to retire the python-3x-nghttp2
packages, the existing ones will continue to be available indefinitely.
Firstly
2021)?
(I'm still dealing with cleaning up the final pieces of python27 detritus,
but these should hopefully be much smaller tasks)
nothing should depend from 3.5
not sure for 3.6
I've automated some of the analysis I was doing for python2 packages and the
results are now available at [1
pieces of python27
detritus, but these should hopefully be much smaller tasks)
nothing should depend from 3.5
not sure for 3.6
I've automated some of the analysis I was doing for python2 packages and
the results are now available at [1].
So yeah, it looks like nothing uses 3.5
On 24/03/2024 15:07, Jon Turney wrote:
On 24/09/2023 13:32, Jon Turney via Cygwin-apps wrote:
I assume you are OK with the removal of python 3.5 (EOL Sept 2020) and
3.6 (EOL Dec 2021)?
(I'm still dealing with cleaning up the final pieces of python27
detritus, but these should hopefully
On 24/09/2023 13:32, Jon Turney via Cygwin-apps wrote:
Generally, we have a large number of old, unmaintained packages.
The policy [1] has always been "Packages without an active maintainer
may be pulled from the distribution.", but not actively enforced (in
fact prior to 2022,
,
I'm getting the error:
fatal: remote error: service not enabled: /git/cygwin-packages/sshfs
when I attempt 'git push' to that repository. The same happens
with all the repositories for my packages. It's been this way for
a couple days at least.
Have I forgotten some step in the connection
On 3/14/2024 11:26 AM, Corinna Vinschen via Cygwin-apps wrote:
[...]
You may also want to use https:// rather than git:// for reading
the repository these days, given the insecurity of the git protocol.
Right. I now remember this recommendation too. I will make the change in
all the git
not enabled: /git/cygwin-packages/sshfs
when I attempt 'git push' to that repository. The same happens with
all the repositories for my packages. It's been this way for a
couple days at least.
Have I forgotten some step in the connection at my end? I'm running
ssh-agent.
[...]
What
> > > > I'm getting the error:
> > > >
> > > > fatal: remote error: service not enabled: /git/cygwin-packages/sshfs
> > > >
> > > > when I attempt 'git push' to that repository. The same happens
> > > > with all the repositories for my pa
On 14/03/2024 15:39, Mark Geisert via Cygwin-apps wrote:
On 3/14/2024 2:42 AM, Jon Turney via Cygwin-apps wrote:
On 14/03/2024 05:45, Mark Geisert via Cygwin-apps wrote:
Hi folks,
I'm getting the error:
fatal: remote error: service not enabled: /git/cygwin-packages/sshfs
when I attempt 'git
On 3/14/2024 2:42 AM, Jon Turney via Cygwin-apps wrote:
On 14/03/2024 05:45, Mark Geisert via Cygwin-apps wrote:
Hi folks,
I'm getting the error:
fatal: remote error: service not enabled: /git/cygwin-packages/sshfs
when I attempt 'git push' to that repository. The same happens with
all
On 14/03/2024 05:45, Mark Geisert via Cygwin-apps wrote:
Hi folks,
I'm getting the error:
fatal: remote error: service not enabled: /git/cygwin-packages/sshfs
when I attempt 'git push' to that repository. The same happens with all
the repositories for my packages. It's been this way
Hi folks,
I'm getting the error:
fatal: remote error: service not enabled: /git/cygwin-packages/sshfs
when I attempt 'git push' to that repository. The same happens with all
the repositories for my packages. It's been this way for a couple days at
least.
Have I forgotten some step
' packages from installed.db and pass it via -P to setup.
But in this new installation, all non-Base packages will appear in
"Unneeded" view then.
I guess this is not a regression but longstanding behavior.
Hmm... I certainly envisioned it working that way when I added recording
user_p
.
https://devguide.python.org/versions/#versions
The main packages include postinstall script that
use "alternatives" to define for
/usr/bin/python
/usr/bin/python3
/usr/bin/idle3
/usr/bin/pydoc3
a default to the highest package available.
$ alternatives --display python
pytho
On 03/01/2024 08:49, Marco Atzeri wrote:
+librsvg2 Marco Atzeri
just discovered that librsvg2 requires Rust by long time
** The librsvg 2.40.x series is the last "C only" version
of the library; it was deprecated in 2017.**
On 23/12/2023 04:54, Marco Atzeri wrote:
New test release for
python39 3.9.18-1
python39-doc 3.9.18-1
the packages were promoted to stable
Regards
Marco Atzeri
--
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
The easiest way to unsubscribe is to visit
Takashi Yano via Cygwin-apps writes:
> I found the cause. DISTCLEANFILES in original cygport file removes them.
> Now I can successfully build libatk1.0-doc. Thanks!
No, that means the tarball includes files that should get re-built, but
apparently you somehow failed to do that.
Regards,
Achim.
On Sun, 7 Jan 2024 22:35:02 +0900
Takashi Yano via wrote:
> In the source file, docs/xml directory should have document contents,
> however, it is empty. So, I thought document cannot be built in this
> version. I'll check again.
I found the cause. DISTCLEANFILES in original cygport file removes
On Sun, 7 Jan 2024 12:54:35 +
Jon Turney wrote:
> > 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
>
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
On Wed, Jan 3, 2024 at 12:42 PM matthew patton via Cygwin
wrote:
> Cygwin has an incredible amount of coverage, but it could be pared down to
> 20 packages and I'd be perfectly happy.
>
I suspect most people are in this same position, except that they each have
a different list of 20
that - and replacing the default 'link' to be 'mklink' links instead of
Junctions which some Windows programs do NOT like and fail.
For everything else there is WSL. Seriously. Cygwin has an incredible amount of
coverage, but it could be pared down to 20 packages and I'd be perfectly happy.
StopSent from my T-Mobile 5G Device
Original message From: Takashi Yano via Cygwin-apps
Date: 1/2/24 9:00 PM (GMT-08:00) To:
cygwin-apps@cygwin.com Subject: Re: Unmaintained packages in base package set
On Sat, 23 Dec 2023 04:51:22 +0100Marco Atzeri wrote:> On 23/12/2023
come with qemu packages?
why should an "Unix Emulation layer" that run in "User Space"
trying to run a "Full-system emulation" (https://www.qemu.org/) ?
It seems like using square wheels
Nope. The Qemu packages on LInux have a much more wider functionalit
On Mon, 18 Dec 2023 at 18:33, Brian Inglis via Cygwin wrote:
>
> On 2023-12-18 00:14, Dan Shelton via Cygwin wrote:
> > On Mon, 18 Dec 2023 at 07:54, Marco Atzeri via Cygwin wrote:
> >> On 18/12/2023 07:42, Dan Shelton via Cygwin wrote:
> >>> Does Cygwin come with
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
On Sat, 23 Dec 2023 04:51:22 +0100
Marco Atzeri wrote:
> On 23/12/2023 04:42, Takashi Yano via Cygwin-apps wrote:
> > On Wed, 20 Dec 2023 12:16:05 +
> > Jon Turney via Cygwin-apps wrote:
> >> I tweaked the unmaintained packages report [1] a bit so it identifies
introduced and we will skip 3.10
and 3.11.
https://devguide.python.org/versions/#versions
The main packages include postinstall script that
use "alternatives" to define for
/usr/bin/python
/usr/bin/python3
/usr/bin/idle3
/usr/bin/pydoc3
a default to the highest package
On 23/12/2023 04:42, Takashi Yano via Cygwin-apps wrote:
On Wed, 20 Dec 2023 12:16:05 +
Jon Turney via Cygwin-apps wrote:
I tweaked the unmaintained packages report [1] a bit so it identifies
'base' and 'direct or indirect base dependencies'.
(But you're quite right to point out
On Wed, 20 Dec 2023 12:16:05 +
Jon Turney via Cygwin-apps wrote:
> I tweaked the unmaintained packages report [1] a bit so it identifies
> 'base' and 'direct or indirect base dependencies'.
>
> (But you're quite right to point out that the build requirements for a
> nati
t download mirror list. Only use
> sites
>specified with -s
> ..
> -s --site Download site URL, path or UNC path
> The default is to both download and install packages, unless either
> --download or --local-install is specified.
> ---
On 21/12/2023 04:27, Marco Atzeri via Cygwin-apps wrote:
On 20/12/2023 13:16, Jon Turney via Cygwin-apps wrote:
On 06/12/2023 17:19, Brian Inglis via Cygwin-apps wrote:
On 2023-12-05 06:07, Jon Turney wrote:
[...]
I tweaked the unmaintained packages report [1] a bit so it identifies
Marco Atzeri via Cygwin-apps wrote:
Is anyone looking at QT5 and QT6 ?
I've "looked at" Qt5 in the past, though not to the point of being able to take it
over. I have a patch for the qterminal issue that I'd like to contribute.
There's issues I've had building this I haven't had the time to
On 20/12/2023 13:16, Jon Turney via Cygwin-apps wrote:
On 06/12/2023 17:19, Brian Inglis via Cygwin-apps wrote:
On 2023-12-05 06:07, Jon Turney wrote:
[...]
I tweaked the unmaintained packages report [1] a bit so it identifies
'base' and 'direct or indirect base dependencies
On 06/12/2023 17:19, Brian Inglis via Cygwin-apps wrote:
On 2023-12-05 06:07, Jon Turney wrote:
[...]
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 optimis
On 2023-12-18 00:14, Dan Shelton via Cygwin wrote:
On Mon, 18 Dec 2023 at 07:54, Marco Atzeri via Cygwin wrote:
On 18/12/2023 07:42, Dan Shelton via Cygwin wrote:
Does Cygwin come with qemu packages?
why should an "Unix Emulation layer" that run in "User Space"
trying t
On 18/12/2023 10:57, Cedric Blancher via Cygwin wrote:
Good morning!
Can Cygwin setup.exe be modified to support more than one package
repository, e.g. first the default Cygwin package repro, and then a
company package repro (e.g. fr.pasteur.cygwin.packages ?).
The source code is available,
download mirror list. Only use sites
specified with -s
..
-s --site Download site URL, path or UNC path
The default is to both download and install packages, unless either
--download or -
Good morning!
Can Cygwin setup.exe be modified to support more than one package
repository, e.g. first the default Cygwin package repro, and then a
company package repro (e.g. fr.pasteur.cygwin.packages ?).
Ced
--
Cedric Blancher
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur
On Mon, 18 Dec 2023 at 07:54, Marco Atzeri via Cygwin wrote:
>
> On 18/12/2023 07:42, Dan Shelton via Cygwin wrote:
> > Hello!
> >
> > Does Cygwin come with qemu packages?
> >
> > Dan
>
> why should an "Unix Emulation layer" that run in &
On 18/12/2023 07:42, Dan Shelton via Cygwin wrote:
Hello!
Does Cygwin come with qemu packages?
Dan
why should an "Unix Emulation layer" that run in "User Space"
trying to run a "Full-system emulation" (https://www.qemu.org/) ?
It seems like using square whee
Hello!
Does Cygwin come with qemu packages?
Dan
--
Dan Shelton - Cluster Specialist Win/Lin/Bsd
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com
UPDATE:
Running "cygcheck -rvs" on the updated installation (after all the "Unneeded"
packages were gone),
revealed that a few packages had become "Incomplete":
base-files
libMagickCore6_6
libMagickCore7_9
perl
perl-mapages
squid
I re-ran Setup and chose thes
Hi All,
I was updating my Cygwin installation at home and that had accumulated some
"Unneeded" packages, which were very hard to deal with:
The default disposition is "Keep" (while logically, since they are "safe to be
removed", it should have been "Unins
Am 24.09.2023 um 20:20 schrieb gstrauss via Cygwin-apps:
On Sun, Sep 24, 2023 at 01:32:59PM +0100, Jon Turney via Cygwin-apps wrote:
Generally, we have a large number of old, unmaintained packages.
The policy [1] has always been "Packages without an active maintainer may be
pulled
On Sun, Sep 24, 2023 at 01:32:59PM +0100, Jon Turney via Cygwin-apps wrote:
>
> Generally, we have a large number of old, unmaintained packages.
>
> The policy [1] has always been "Packages without an active maintainer may be
> pulled from the distribution.", but not a
On 2023-09-24 08:10, Thomas Wolff wrote:
Am 24.09.2023 um 14:32 schrieb Jon Turney:
On 08/09/2023 18:29, Brian Inglis wrote:
Thinking we could drop the ancient (8 years) orphaned DJGPP 32-bit (by
definition) packages; they are older than djgpp current, never mind beta on
gcc 13; from DJ's
Am 24.09.2023 um 14:32 schrieb Jon Turney via Cygwin-apps:
On 08/09/2023 18:29, Brian Inglis via Cygwin-apps wrote:
Hi folks,
Thinking we could drop the ancient (8 years) orphaned DJGPP 32-bit
(by definition) packages; they are older than djgpp current, never
mind beta on gcc 13; from
On 08/09/2023 18:29, Brian Inglis via Cygwin-apps wrote:
Hi folks,
Thinking we could drop the ancient (8 years) orphaned DJGPP 32-bit (by
definition) packages; they are older than djgpp current, never mind beta
on gcc 13; from DJ's latest Monthly Mini-FAQ summary:
djdev-2.05 binutils
Generally, we have a large number of old, unmaintained packages.
The policy [1] has always been "Packages without an active maintainer
may be pulled from the distribution.", but not actively enforced (in
fact prior to 2022, this used to say "are pulled", but I moderated
Hi folks,
Thinking we could drop the ancient (8 years) orphaned DJGPP 32-bit (by
definition) packages; they are older than djgpp current, never mind beta on gcc
13; from DJ's latest Monthly Mini-FAQ summary:
djdev-2.05 binutils-2.32 ... gcc-10.2.0 ...
$ cygcheck -p DJGPP
Found 18
On 2023-04-30 12:25, Jon Turney wrote:
On 28/04/2023 06:51, Brian Inglis wrote:
On 2023-04-27 10:11, Jon Turney wrote:
[...]
I think this functionality needs to exist in setup as well, though, as calm
can't possibly have knowledge of packages you might be installing from 3rd
party overlay
On Wed, May 3, 2023 at 3:26 PM Anderson via Cygwin wrote:
>
> Hi,
>
> I need to know if have a limit of packages to install on packages params on
> cygwin setup command line.
>
> I put many packages but some packages are not installed.
>
> Thanks.
>
Hi Ande
Hi,
I need to know if have a limit of packages to install on packages params on
cygwin setup command line.
I put many packages but some packages are not installed.
Thanks.
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation
On Wed, 19 Apr 2023, Brian Inglis wrote:
> As 32 bit Windows systems are no longer getting security updates,
> recommendations for similar legacy systems include running them in VMs with
> access to update executables and libraries blocked.
There is a 32-bit variant of Windows 10; Windows 10 is
On 28/04/2023 06:51, Brian Inglis via Cygwin-apps wrote:
On 2023-04-27 10:11, Jon Turney via Cygwin-apps wrote:
[...]
I think this functionality needs to exist in setup as well, though, as
calm can't possibly have knowledge of packages you might be installing
from 3rd party overlay package
'conflicts:'
markers in hints, etc.)
I think this functionality needs to exist in setup as well, though, as calm
can't possibly have knowledge of packages you might be installing from 3rd party
overlay package repositories.
Please make any of these conflict messages warnings only, as few pa
filenames to sets
of packages. Using multimap instead of the
straightforward map> needs possibly less memory
(not tested). But for multimap it is required that file/package name
pairs are not inserted twice.
I attached a small standalone POC source file using multimap. It
would also detect collisi
lity needs to exist in setup as well, though, as
calm can't possibly have knowledge of packages you might be installing
from 3rd party overlay package repositories.
On 24/04/2023 17:26, Christian Franke via Cygwin-apps wrote:
Jon Turney via Cygwin-apps wrote:
Detect filename collisions between packages
Don't check filenames under /etc/postinstall/ for collisions
Report when filename collisions exist
Add option '--collisions' to enable
IMO a useful
Corinna Vinschen via Cygwin-apps writes:
> Calm could create a database containing all the files from the tar
> archives it uploads, and compare that against the newly uploaded files
> on the fly.
That already exists as the basis for package grep, albeit in the form of
a buiinch of text files.
Hi Jon,
On Apr 23 15:43, Jon Turney via Cygwin-apps wrote:
> This is a woefully underoptimized implementation of detecting filename
> collisions between packages, so it's hidden behind the command line option
> '--collisions' to enable it.
>
> A good implementation probab
Jon Turney via Cygwin-apps wrote:
Detect filename collisions between packages
Don't check filenames under /etc/postinstall/ for collisions
Report when filename collisions exist
Add option '--collisions' to enable
IMO a useful enhancement.
Notes:
Reading file catalog from a package
Detect filename collisions between packages
Don't check filenames under /etc/postinstall/ for collisions
Report when filename collisions exist
Add option '--collisions' to enable
Notes:
Reading file catalog from a package is moderately expensive in terms of
I/O: To extract all the filenames from
This is a woefully underoptimized implementation of detecting filename
collisions between packages, so it's hidden behind the command line option
'--collisions' to enable it.
A good implementation probably (i) collects the filenames at the same time
as checksumming the archive, or has them
On 2023-04-19 05:30, Carlo B. via Cygwin wrote:
after the 32-bit port of CYGWIN has been obsoleted, I was looking for
a way for installing or upgrading the NOARCH packages, like the
libraries for the mingw cross compilers for example.
Unfortunately, I have not found an existing way for doing
On 19/04/2023 12:30, Carlo B. via Cygwin wrote:
Hello,
after the 32-bit port of CYGWIN has been obsoleted, I was looking for
a way for installing or upgrading the NOARCH packages, like the
libraries for the mingw cross compilers for example.
Unfortunately, I have not found an existing way
Hello,
after the 32-bit port of CYGWIN has been obsoleted, I was looking for
a way for installing or upgrading the NOARCH packages, like the
libraries for the mingw cross compilers for example.
Unfortunately, I have not found an existing way for doing it.
Is it possible to do it?
Otherwise, I'm
On 28/03/2023 17:55, Bill Stewart via Cygwin wrote:
On Mon, Mar 27, 2023 at 2:55 PM Jon Turney wrote:
Sorry, based on the previous discussion at [1] this seems to be broken
at the moment, due to '-x' being broken.
[1] https://cygwin.com/pipermail/cygwin/2023-February/252994.html
I think I
://devguide.python.org/versions/#versions
The main packages include postinstall script that
use "alternatives" to define for
/usr/bin/python
/usr/bin/python3
/usr/bin/idle3
/usr/bin/pydoc3
a default to the highest package available.
$ alternatives --display python
python - status is a
://devguide.python.org/versions/#versions
The main packages include postinstall script that
use "alternatives" to define for
/usr/bin/python
/usr/bin/python3
/usr/bin/idle3
/usr/bin/pydoc3
a default to the highest package available.
$ alternatives --display python
python - status is a
On Mon, Mar 27, 2023 at 2:55 PM Jon Turney wrote:
Sorry, based on the previous discussion at [1] this seems to be broken
> at the moment, due to '-x' being broken.
>
> [1] https://cygwin.com/pipermail/cygwin/2023-February/252994.html
>
> If you really need this, please try old setup versions from
3" -P
"package1,package2,package3"'
An option which explicitly just installs the source for a specified
package might be useful.
It seems that
--local-install -x "package[,...]" -P "package[,...]"
...no longer works to automate source download for package
-I -x "package1,package2,package3" -P
>> "package1,package2,package3"'
>>
>> An option which explicitly just installs the source for a specified
>> package might be useful.
>>
>
> It seems that
>
> --local-install -x "package[,...]&
kage3"'
>
> An option which explicitly just installs the source for a specified
> package might be useful.
>
It seems that
--local-install -x "package[,...]" -P "package[,...]"
...no longer works to automate source download for packages already
installed..
On 18/11/2022 14:32, Keith Christian wrote:
Carlo,
Since you are successfully creating Cygwin packages, one thing that
would be very helpful is a detailed set of instructions for cygport to
create a Cygwin package from source.
There are instructions posted on the Cygwin website and other info
On 17/11/2022 15:18, Carlo B. wrote:
Hello,
at this address I did a repository of packages that I made for CYGWIN:
https://github.com/carlo-bramini/packages-cygwin
Sometimes, when I need something not existing (or newer) into the
official list of packages for CYGWIN, I upload it here.
All
Doug,
What would you like me to do here:
- Apply this update and rebuild the package, and/or
- Process this like an ITA
- Something else?
On 25/10/2022 16:25, Chad Dougherty wrote:
I've updated the cygport to the current upstream release version, 0.8.1:
Carlo,
Since you are successfully creating Cygwin packages, one thing that
would be very helpful is a detailed set of instructions for cygport to
create a Cygwin package from source.
There are instructions posted on the Cygwin website and other info
about cygport, but I have not found
On 11/17/2022 10:18 AM, Carlo B. wrote:
Hello,
at this address I did a repository of packages that I made for CYGWIN:
https://github.com/carlo-bramini/packages-cygwin
Sometimes, when I need something not existing (or newer) into the
official list of packages for CYGWIN, I upload it here.
All
1 - 100 of 3984 matches
Mail list logo
