Jason Pyeron writes:
> If I have a CI build for *.cygport - is it expected to have
> conditional logic based on which package is being processed?
Not necessarily, I understand you were talking about default behaviour
and how the current default doesn't match your / your CI's expectation.
To reiter
Name: Jason Pyeron
BEGIN SSH2 PUBLIC KEY
Comment: "2048-bit RSA for use with Cygwin publishing"
B3NzaC1yc2EBIwAAAQEA+TM6VXYM0eSxZdJ20jKcEDsCiZG6e0TZQs07VtXWq0
rmm1xn0tPQoQqBKmKqqUGlsdhh3cXDWYYP7yWMgT+zIsR7ch5g3SKzmgO/Z+HUSpkKAPm2
I5HAY9G6Rz2mP2YrxRIliD1w2t0g/0bZOqGV/7G/TXOOlPsRITG
Hi folks,
Trying to update libidn2, but both arch get:
>>> Checking packages for unexpected, missing or duplicate files
*** Warning: Packages are missing files:
-usr/lib/libidn2-0.def
*** ERROR: Packages are missing files:
$ l libidn2-2.3.1-1.x86_64/**/*.def
libidn2-2.3.1-1.x86_64/build/lib/lib
On 2021-05-18 10:05, Marco Atzeri via Cygwin-apps wrote:
On 18.05.2021 15:47, Brian Inglis wrote:
Needed dependency for libidn build missing from x86.
It seems Rafel has missed to note the need to build for
both architectures.
Ping Rafel Amer - need x86 gengetopt build please!
--
Take care
> -Original Message-
> From: Achim Gratz
> Sent: Tuesday, May 18, 2021 4:16 PM
>
> Jason Pyeron writes:
> > If I put it in ~/.config/cygport.conf it will impact all packages, not
> > just the "one". The only place it is limited to applicable package is
> > in the package.cygport file, or a
Jason Pyeron writes:
> If I put it in ~/.config/cygport.conf it will impact all packages, not
> just the "one". The only place it is limited to applicable package is
> in the package.cygport file, or am I missing something?
You can always override these settings when starting a build on a CI
(eith
> -Original Message-
> From: Achim Gratz
> Sent: Tuesday, May 18, 2021 1:13 PM
>
> Jason Pyeron writes:
> > I am assuming that I should not include cygport in the build
> > requires.
>
> Yes, we currently assume cygport and its transitive dependencies to be
> available for a cygport based
> -Original Message-
> From: ASSI
> Sent: Tuesday, May 18, 2021 12:37 AM
>
> Jason Pyeron writes:
> > What is the historic rationale behind the "OR true" after the make
> > check?
>
> Not historic for the most part, I'd say. Cygport can also do
> cross-builds of packages and in those cas
Hi Marco,
I would greatly appreciate you adopting and updating this package. I no
longer use it in my day job.
Regards,
David
On 5/18/2021 9:49 AM, Marco Atzeri via Cygwin-apps wrote:
David,
It seems this package is still python 2.7 one.
If you want I can take over and adapt to python 3.8
Jason Pyeron writes:
> I am assuming that I should not include cygport in the build
> requires.
Yes, we currently assume cygport and its transitive dependencies to be
available for a cygport based package. The build requires should enable
the CI to build the package correctly.
Regards,
Achim.
-
David,
It seems this package is still python 2.7 one.
If you want I can take over and adapt to python 3.8
Forwarded Message
Subject: outdated git-review version
Date: Tue, 18 May 2021 11:50:38 +
From: Rutkowska, Anna (Nokia - PL/Wroclaw)
Hi,
Latest available git-review p
On 18.05.2021 15:47, Brian Inglis wrote:
Needed dependency for libidn build missing from x86.
It seems Rafel has missed to note the need to build for
both architectures.
Needed dependency for libidn build missing from x86.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
On 17.05.2021 21:59, Jason Pyeron wrote:
-Original Message-
From: Marco Atzeri
Sent: Sunday, May 9, 2021 3:55 PM
General suggestion:
- add BUILD_REQUIRES="libpcre-devel libgcrypt-devel libpoppler-cpp-devel"
the test suite seems to need tcl so you may need to add more packages
I
14 matches
Mail list logo
