Thanks for the headsup.
> Once you have upgraded to cygport 0.22.0, maintainers MUST email a list
> of their package(s) which qualify as noarch AND are already marked
> ARCH=noarch or will be with the next release.
atool
discus
stow
Achim,
The next version of Biber will have a dependency on Lingua::Translit.
Can you add that to the distro when you get a chance?
Thanks.
Ken
On 2016-05-11 03:15, Andrew Schulman wrote:
atool
discus
stow
Moved to noarch.
--
Yaakov
On 2016-05-11 01:11, Thomas Wolff wrote:
I wonder why this list or this action does not include all the source
packages, which might even save more disk space than all the others
together.
Possibly, but at this time there is not support for separate parts of
packages in different directories.
On 11/05/16 07:17, Yaakov Selkowitz wrote:
On 2016-05-11 00:07, Marco Atzeri wrote:
So at this stage not the documentation subpackages, but only if all
subpackages are in this category. correct ?
At this time we are only considering those where all subpackages are
noarch, i.e. ARCH=noarch is
On 05/10/2016 04:11 PM, Yaakov Selkowitz wrote:
> Package Maintainers,
>
> cygport 0.22.0 is on its way to the mirrors. With this release, and
> thanks to Jon Turney's continuing work on calm (the replacement for
> upset which generates setup.ini), packages marked ARCH=noarch will be
> uploaded o
fish 2.3 is currently bundling and building its own copy of libpcre2.
There's an issue[1] open to unbundle it and use distributions' own
versions, but libpcre2 hasn't been packaged for Cygwin yet.
Yaakov, are you interested in packaging and maintaining pcre2? It builds
fine OOTB for me, and it lo
Am 11.05.2016 um 14:27 schrieb Ken Brown:
The next version of Biber will have a dependency on Lingua::Translit.
Can you add that to the distro when you get a chance?
I'll have a look at that. Not this week, though.
--
Achim.
(on the road :-)
On 5/10/2016 6:11 PM, Yaakov Selkowitz wrote:
Once you have upgraded to cygport 0.22.0, maintainers MUST email a list
of their package(s) which qualify as noarch AND are already marked
ARCH=noarch or will be with the next release.
bzr-fastimport
biber
emacs-auctex
texlive-collection-basic-doc
t
On 11/05/2016 08:17, Yaakov Selkowitz wrote:
On 2016-05-11 00:07, Marco Atzeri wrote:
So at this stage not the documentation subpackages, but only if all
subpackages are in this category. correct ?
At this time we are only considering those where all subpackages are
noarch, i.e. ARCH=noarch is
On 2016-05-11 11:36, Eric Blake wrote:
Question: can cygport be enhanced to validate and/or have heuristics for
this?
Possibly, I'd have to consider how exactly.
For example, cygport already has a pass that strips/separates
debuginfo out of binaries compiled by gcc - if any stripping occurs,
On 11/05/2016 00:11, Yaakov Selkowitz wrote:
Package Maintainers,
Once you have upgraded to cygport 0.22.0, maintainers MUST email a list
of their package(s) which qualify as noarch AND are already marked
ARCH=noarch or will be with the next release. (Note that inheriting
cross.cygclass impl
On 10/05/2016 07:20, Andrew Schulman wrote:
If this is what's happened, we need to update https://cygwin.com/setup.html with
the new information (the page is overdue for an overhaul anyway).
I agree that page is very bad at communicating the information it needs
to communicate. Perhaps it wou
The versions containing hyphens are no longer present.
---
past_mistakes.py | 16
1 file changed, 16 deletions(-)
diff --git a/past_mistakes.py b/past_mistakes.py
index d8280d1..5e1132f 100644
--- a/past_mistakes.py
+++ b/past_mistakes.py
@@ -30,8 +30,6 @@
# package names which
On 2016-05-11 12:56, Marco Atzeri wrote:
On 11/05/2016 08:17, Yaakov Selkowitz wrote:
On 2016-05-11 00:07, Marco Atzeri wrote:
So at this stage not the documentation subpackages, but only if all
subpackages are in this category. correct ?
At this time we are only considering those where all s
On 2016-05-11 11:26, David Stacey wrote:
On 11/05/16 07:17, Yaakov Selkowitz wrote:
On 2016-05-11 00:07, Marco Atzeri wrote:
So at this stage not the documentation subpackages, but only if all
subpackages are in this category. correct ?
At this time we are only considering those where all sub
On 2016-05-11 12:26, Ken Brown wrote:
On 5/10/2016 6:11 PM, Yaakov Selkowitz wrote:
Once you have upgraded to cygport 0.22.0, maintainers MUST email a list
of their package(s) which qualify as noarch AND are already marked
ARCH=noarch or will be with the next release.
bzr-fastimport
biber
emac
On 2016-05-11 13:38, Marco Atzeri wrote:
On 11/05/2016 00:11, Yaakov Selkowitz wrote:
Package Maintainers,
Once you have upgraded to cygport 0.22.0, maintainers MUST email a list
of their package(s) which qualify as noarch AND are already marked
ARCH=noarch or will be with the next release.
On 11/05/2016 22:48, Yaakov Selkowitz wrote:
On 2016-05-11 13:38, Marco Atzeri wrote:
On 11/05/2016 00:11, Yaakov Selkowitz wrote:
Package Maintainers,
Once you have upgraded to cygport 0.22.0, maintainers MUST email a list
of their package(s) which qualify as noarch AND are already marked
On 2016-05-11 16:02, Marco Atzeri wrote:
On 11/05/2016 22:48, Yaakov Selkowitz wrote:
But what about the following?
octave-nan
octave-octcdf
octave-stk
octave-tsa
/usr/lib/octave/packages/
contains the arch specific in this case in mex variant.
Oops, it seems cygport knows nothing of this,
On 5/11/2016 4:35 PM, Yaakov Selkowitz wrote:
I haven't moved these yet, but what about the rest of the collections? IIRC the
TEXLIVE_ARCH_PKGS do have CPU-cygwin paths in the "sources", but are they
*really* archful?
No, the only issue is the sources. As it stands, if someone downloads the
s
On 2016-05-11 16:55, Ken Brown wrote:
On 5/11/2016 4:35 PM, Yaakov Selkowitz wrote:
I haven't moved these yet, but what about the rest of the collections?
IIRC the
TEXLIVE_ARCH_PKGS do have CPU-cygwin paths in the "sources", but are they
*really* archful?
No, the only issue is the sources. As
On 5/11/2016 6:17 PM, Yaakov Selkowitz wrote:
On 2016-05-11 16:55, Ken Brown wrote:
On 5/11/2016 4:35 PM, Yaakov Selkowitz wrote:
I haven't moved these yet, but what about the rest of the collections?
IIRC the
TEXLIVE_ARCH_PKGS do have CPU-cygwin paths in the "sources", but are
they
*really* ar
Yaakov,
I needed the latest version of perl-PAR-Packer, so I built it and
discovered that I needed the attached patch. It just adds back a line
that was present prior to version 1.030. The build fails with
"undefined reference to `__stack_chk_fail'" without that line.
I'm not suggesting th
On 2016-05-06 08:15, Mike DePaulo wrote:
This package is currently in Cygwin Ports at version 4.7.2-2, as well
as in major distros like Fedora & Debian.
The 5.0.x series has a new upstream. They also removed the PKG-INFO file.
The sources on PyPI -- which you get if you drop SRC_URI -- still h
On 2016-05-11 17:30, Ken Brown wrote:
On 5/11/2016 6:17 PM, Yaakov Selkowitz wrote:
On 2016-05-11 16:55, Ken Brown wrote:
On 5/11/2016 4:35 PM, Yaakov Selkowitz wrote:
I haven't moved these yet, but what about the rest of the collections?
IIRC the
TEXLIVE_ARCH_PKGS do have CPU-cygwin paths in
On 2016-05-11 15:35, Yaakov Selkowitz wrote:
On 2016-05-11 12:26, Ken Brown wrote:
texlive-collection-fontsextra
texlive-collection-fontsrecommended
texlive-collection-genericextra
texlive-collection-genericrecommended
texlive-collection-langafrican
texlive-collection-langarabic
texlive-collecti
On 2016-05-11 13:38, Marco Atzeri wrote:
All these are arch independent as contain only scripts
(for the time being)
octave-bim
octave-bsltl
octave-cgi
octave-data-smoothing
octave-dataframe
octave-divand
octave-financial
octave-fpl
octave-fuzzy-logic-toolkit
octave-ga
octave-generate_html
octav
28 matches
Mail list logo