On 19/01/2024 18:23, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
On 18/01/2024 19:40, Jon Turney wrote:
On 18/01/2024 19:31, Jon Turney via Cygwin-apps wrote:
[...]
python-wx-devel wxWidgets C++ application framework (Python
bindings)
[...]
python-wx-devel is the last remnant
On 18/01/2024 19:40, Jon Turney wrote:
On 18/01/2024 19:31, Jon Turney via Cygwin-apps wrote:
[...]
python-wx-devel wxWidgets C++ application framework (Python
bindings)
[...]
python-wx-devel is the last remnant of python2 bindings for wx (the
python3 binding comes from a different,
On 27/09/2022 16:59, Jon Turney wrote:
On 27/09/2022 16:33, Hamish McIntyre-Bhatty wrote:
Hi there,
While trying to get the latest version of wxWidgets 3.0.x to build, I
found that I need to use an older version of autoreconf, as the
format seems to have changed in a slightly incompatible
On 27/09/2022 17:03, Jon Turney wrote:
On 27/09/2022 16:37, Hamish McIntyre-Bhatty wrote:
Hi there,
I recently noticed that the git repo pages (for example
https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/2048-cli.git;a=summary)
suggest cloning with HTTP, instead of HTTPS
Hi there,
I recently noticed that the git repo pages (for example
https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/2048-cli.git;a=summary)
suggest cloning with HTTP, instead of HTTPS.
HTTPS is available, so this seems like a more secure option to offer
instead of HTTP.
Hamish
Hi there,
While trying to get the latest version of wxWidgets 3.0.x to build, I
found that I need to use an older version of autoreconf, as the format
seems to have changed in a slightly incompatible way.
The "cygautoreconf" command seems to always use the latest version of
autoreconf, and
Hi there,
Admittedly a very minor issue, but I thought I should at least mention it.
Most of cygport's commands aren't abbreviated, but prepare is
abbreviated to "prep". It'd be nice if "prepare" was accepted too for
consistency.
Thanks for all the work put into this tool, I can't imagine
On 15/09/2022 20:24, Achim Gratz wrote:
Hamish McIntyre-Bhatty writes:
Today I'm attempting to update my python-imaging package, but I'm now
finding that cygport has made the warning about duplicated files an
error.
I don't think anything has changed there lately?
The source is at: https
Hi there,
Today I'm attempting to update my python-imaging package, but I'm now
finding that cygport has made the warning about duplicated files an error.
The source is at: https://gitlab.com/hamishmb/cygwin-python-imaging
Files are duplicated in these packages because there are .py files
On 04/08/2022 14:30, Hamish McIntyre-Bhatty wrote:
On 04/08/2022 13:50, Adam Dinwoodie wrote:
On Thu, 4 Aug 2022 at 11:13, Hamish McIntyre-Bhatty
wrote:
I'm considering moving my Cygwin packaging repos over to gitlab, as I
find it easier to organise and use. Are there any potential
problems
On 04/08/2022 13:50, Adam Dinwoodie wrote:
On Thu, 4 Aug 2022 at 11:13, Hamish McIntyre-Bhatty
wrote:
I'm considering moving my Cygwin packaging repos over to gitlab, as I
find it easier to organise and use. Are there any potential
problems/lost features from me doing this?
Where are your
Hi all,
I'm considering moving my Cygwin packaging repos over to gitlab, as I
find it easier to organise and use. Are there any potential
problems/lost features from me doing this?
Hamish
On 06/07/2022 20:28, Brian Inglis wrote:
On 2022-07-06 09:13, Hamish McIntyre-Bhatty wrote:
On 05/07/2022 10:22, Christian Franke wrote:
Hamish McIntyre-Bhatty wrote:
I was wondering if the maintainer for GNU ddrescue could update to
1.26 please?
1.27-pre2 is already released, so I wait
On 05/07/2022 10:22, Christian Franke wrote:
Hamish McIntyre-Bhatty wrote:
I was wondering if the maintainer for GNU ddrescue could update to
1.26 please?
1.27-pre2 is already released, so I wait for 1.27 final.
Fair enough. Do you know if there's a mailing list or similar to be
notified
Hi there,
I was wondering if the maintainer for GNU ddrescue could update to 1.26
please?
Thanks,
Hamish
On 29/06/2022 16:36, Hamish McIntyre-Bhatty wrote:
On 31/12/2021 10:00, Marco Atzeri wrote:
Attached patch moves "default" from 3.6 to 3.9
Additional changes:
Remove 3.5 from all
Change future to 3.10
Other point:
As 3.5 was never reall deployed, I think we can remo
On 29/06/2022 16:46, Marco Atzeri wrote:
On 29.06.2022 17:36, Hamish McIntyre-Bhatty wrote:
On 31/12/2021 10:00, Marco Atzeri wrote:
Attached patch moves "default" from 3.6 to 3.9
Additional changes:
Remove 3.5 from all
Change future to 3.10
Other point:
As 3.5 was never real
On 31/12/2021 10:00, Marco Atzeri wrote:
Attached patch moves "default" from 3.6 to 3.9
Additional changes:
Remove 3.5 from all
Change future to 3.10
Other point:
As 3.5 was never reall deployed, I think we can remove it from the
distibution.
As we have a lot of python3-* is obsoleded
On 20/01/2022 14:56, Hamish McIntyre-Bhatty wrote:
Hi there,
This is a follow-up to Marco Atzeri and I talking about tox in the
Python 3.9 email thread. I have just started trying to use tox for
testing python-imaging.
I have found that tox has some issues on Python 3.6 and 3.7, namely
On 22/01/2022 05:34, Marco Atzeri wrote:
On 21.01.2022 17:03, Hamish McIntyre-Bhatty wrote:
On 21/01/2022 14:06, Jon Turney wrote:
On 20/01/2022 15:50, Hamish McIntyre-Bhatty wrote:
Hi there,
Recently, I created a test package for python-imaging, and the CI
system gave a build error that I
On 21/01/2022 14:06, Jon Turney wrote:
On 20/01/2022 15:50, Hamish McIntyre-Bhatty wrote:
Hi there,
Recently, I created a test package for python-imaging, and the CI
system gave a build error that I didn't see locally:
*** ERROR: unknown wheel filename.
This only occurred for the Python
On 20/01/2022 14:33, Jon Turney wrote:
To try to avoid packages lingering in the 'test' status indefinitely
(which leads to them not being installed by most users, as they don't
run setup with 'consider test packages' enabled, thus these packages
generally aren't getting used, so having them
On 20/01/2022 20:38, Brian Inglis wrote:
On 2022-01-20 10:10, Hamish McIntyre-Bhatty wrote:
I've been having trouble compiling the unit tests for
wxWidgets3.1-3.1.5 on Cygwin. The same tests build just fine on my
Linux Mint 20.3 install, however that is using GCC 9.3.0 instead of
Cygwin's
Hi there,
I've been having trouble compiling the unit tests for wxWidgets3.1-3.1.5
on Cygwin. The same tests build just fine on my Linux Mint 20.3 install,
however that is using GCC 9.3.0 instead of Cygwin's 11.2.0.
Attached is the full build log, but I will also point out my ideas about
Hi there,
Recently, I created a test package for python-imaging, and the CI system
gave a build error that I didn't see locally:
*** ERROR: unknown wheel filename.
This only occurred for the Python 3.8 build (3.6 and 3.7 are
unaffected). Considering some of the library name changes between
Hi there,
This is a follow-up to Marco Atzeri and I talking about tox in the
Python 3.9 email thread. I have just started trying to use tox for
testing python-imaging.
I have found that tox has some issues on Python 3.6 and 3.7, namely that:
3.6:
typing-extensions (on PyPI) is required for
base to
work on 32-bit before, will ask another question soon. Are all the
32-bit packages going offline after support ends or will it remain as a
kind of graveyard?
Hamish McIntyre-Bhatty
On 31/12/2021 11:45, Marco Atzeri wrote:
On 28.12.2021 11:12, Hamish McIntyre-Bhatty wrote:
On 28/12/2021 07:17, Marco Atzeri wrote:
On 27.12.2021 00:14, Hamish McIntyre-Bhatty wrote:
On 25/12/2021 07:19, Marco Atzeri wrote:
I think the "test" limitation is not needed.
Reg
On 28/12/2021 07:17, Marco Atzeri wrote:
On 27.12.2021 00:14, Hamish McIntyre-Bhatty wrote:
On 25/12/2021 07:19, Marco Atzeri wrote:
I think the "test" limitation is not needed.
Regards
Marco
Perhaps, but I need to sort the unit tests, they won't even compile
right now.
On 25/12/2021 07:19, Marco Atzeri wrote:
On 17.12.2021 19:35, Hamish McIntyre-Bhatty wrote:
On 12/12/2021 22:14, Marco Atzeri wrote:
On 09.12.2021 07:26, Marco Atzeri wrote:
After the latest update of python 3.6-3.8 I have started the
deployment of python39
Hamish,
can you upload a new
On 12/12/2021 22:14, Marco Atzeri wrote:
On 09.12.2021 07:26, Marco Atzeri wrote:
After the latest update of python 3.6-3.8 I have started the
deployment of python39
I will send the Announcement when I will be a bit more in depth
on the deployment of the python39-* packages
$ cygcheck
On 12/12/2021 22:14, Marco Atzeri wrote:
On 09.12.2021 07:26, Marco Atzeri wrote:
After the latest update of python 3.6-3.8 I have started the
deployment of python39
I will send the Announcement when I will be a bit more in depth
on the deployment of the python39-* packages
$ cygcheck
Version 3.1.5-1 of "wxWidgets3.1" has been uploaded as a test package.
wxWidgets3.1 is a cross-platform GUI toolkit for GTK written in C++.
This update provides the following packages:
- wxWidgets3.1 (source package).
- wxWidgets3.1-debuginfo
- wxWidgets3.1-doc
- libwx_baseu3.1_5
-
Hi there,
Just sending this out so I can update wxWidgets to 3.1.5 (I currently
maintain 3.0.x).
Packages are already built and tested, and can be downloaded from:
https://www.hamishmb.com/files/cygwin-temp/
I have also built and tested wxPython 4.1.1 against these and am in the
process
On 12/12/2021 22:14, Marco Atzeri wrote:
On 09.12.2021 07:26, Marco Atzeri wrote:
After the latest update of python 3.6-3.8 I have started the
deployment of python39
I will send the Announcement when I will be a bit more in depth
on the deployment of the python39-* packages
$ cygcheck
On 12/12/2021 22:14, Marco Atzeri wrote:
On 09.12.2021 07:26, Marco Atzeri wrote:
After the latest update of python 3.6-3.8 I have started the
deployment of python39
I will send the Announcement when I will be a bit more in depth
on the deployment of the python39-* packages
$ cygcheck
Hi Marco,
Just emailing to let you know that the scripts you sent me before have
been merged into a collection of more general Cygwin scripts at
https://github.com/michaelgchu/Cygwin_Specific_Repo, under the
Marco_Atzeri subfolder.
Licensing has been made clear and everything, but let me know if
On 19/01/2021 18:36, Marco Atzeri via Cygwin-apps wrote:
> On 19.01.2021 19:11, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> On 18/01/2021 18:39, Marco Atzeri via Cygwin-apps wrote:
>>> On 18.01.2021 18:57, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>>>> Hi al
On 18/01/2021 18:39, Marco Atzeri via Cygwin-apps wrote:
> On 18.01.2021 18:57, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> Hi all,
>>
>> In the (hopefully!) near future I plan to package python3-wx (aka
>> wxPython) version 4.1.1. This is a backwards-incompatible
Hi all,
In the (hopefully!) near future I plan to package python3-wx (aka
wxPython) version 4.1.1. This is a backwards-incompatible change with
wxPython 4.0.x, so I was wondering if there was a way to retain
python3-wx 4.0.x and its binary packages in the repos after I do this
update?
Hamish
On 22/11/2020 09:43, Achim Gratz wrote:
> Brian Inglis writes:
>> Push your cygport to the git-cygwin-packages playground repo (see Jon
>> Turney's recent reply to me in this list) which all maintainers can
>> push to, as you don't yet own the git-cygwin-packages wxWidgets repo;
>> check the CI
On 16/12/2020 20:37, Brian Inglis wrote:
> On 2020-12-16 10:36, Marco Atzeri via Cygwin-apps wrote:
>> On 16.12.2020 13:13, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>>> So I know it's been mentioned a lot that fork is slow on Cygwin, but
>>> compared to other
Hi,
So I know it's been mentioned a lot that fork is slow on Cygwin, but
compared to other people's machines, eg when building, it seems way
slower for me.
First I'd like to know if there's a good way to measure this that anyone
has found, because I'm not sure how to measure it. If I print
On 14/12/2020 20:21, Marco Atzeri via Cygwin-apps wrote:
> On 14.12.2020 10:46, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> On 13/12/2020 20:12, Marco Atzeri via Cygwin-apps wrote:
>>> On 09.12.2020 21:55, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>>>> On 25/
On 13/12/2020 20:12, Marco Atzeri via Cygwin-apps wrote:
> On 09.12.2020 21:55, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> On 25/11/2020 10:02, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>>>> Okay, so attached is my latest cygport file. I'm still building for
>&g
On 25/11/2020 10:02, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> Okay, so attached is my latest cygport file. I'm still building for
>> 32-bit, so I'll upload and link to the new packages tomorrow.
>>
>> Changes:
>>
>> - Split BUILD_REQUIRES across
On 27/11/2020 18:28, Brian Inglis wrote:
> On 2020-11-27 10:57, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> On 24/11/2020 21:06, Brian Inglis wrote:
>>> On 2020-07-08 14:05, Brian Inglis wrote:
>>>> wget2 is the successor of wget supplying a shared library AP
On 24/11/2020 21:06, Brian Inglis wrote:
> On 2020-07-08 14:05, Brian Inglis wrote:
>> wget2 is the successor of wget supplying a shared library API like
>> curl to
>> build a modern, fast, multi-threaded, parallel downloader using
>> HTTP/2, HTTP
>> compression and If-Modified-Since headers; see:
> Okay, so attached is my latest cygport file. I'm still building for
> 32-bit, so I'll upload and link to the new packages tomorrow.
>
> Changes:
>
> - Split BUILD_REQUIRES across two lines for definitely build time and
> probably only runtime deps.
>
> - Use system regex library explicitly.
>
>
On 24/11/2020 10:43, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> Ignore that message, I made a silly mistake.
>
> On 24/11/2020 10:15, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> Well, something's gone wrong with my Cygwin install I think, because
>> even with previ
Ignore that message, I made a silly mistake.
On 24/11/2020 10:15, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> Well, something's gone wrong with my Cygwin install I think, because
> even with previously working cygport recipes, I can no longer produce a
> working build.
>
> T
Well, something's gone wrong with my Cygwin install I think, because
even with previously working cygport recipes, I can no longer produce a
working build.
The samples tend to either exit immediately or segfault, and trying to
use wxPython yields:
"
Traceback (most recent call last):
File
On 23/11/2020 20:05, ASSI wrote:
> Hamish McIntyre-Bhatty via Cygwin-apps writes:
>> Okay, wow that is a LOT quicker. I haven't timed mine precisely buts
>> it's something like:
> Just look at the files in the log/ folder.
Okay, shall do once this build is done.
>
>>
On 23/11/2020 19:24, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 23/11/2020 19:16, ASSI wrote:
>> Hamish McIntyre-Bhatty via Cygwin-apps writes:
>>> That is strange if it's so much faster on your system.
>> I've checked again to be sure:
>>
>> Compi
On 23/11/2020 19:16, ASSI wrote:
> Hamish McIntyre-Bhatty via Cygwin-apps writes:
>> That is strange if it's so much faster on your system.
> I've checked again to be sure:
>
> Compile 41 minutes, install 7 (32bit) / 4 (64bit) minutes, packaging 5
> minutes.
Okay, wow tha
On 23/11/2020 15:26, ASSI wrote:
> Hamish McIntyre-Bhatty via Cygwin-apps writes:
>> 1. I have separated these onto another line. I've kept this enabled for
>> manual testing, and also because other things in my Cygwin install need
>> some of these dependencies - I can't eas
On 22/11/2020 09:41, Achim Gratz wrote:
> Hamish McIntyre-Bhatty via Cygwin-apps writes:
>> *bump* in case this went unnoticed.
> It didn't, I just know that this GNOME crap will always need another 40
> packages installed before I can even start looking.
>
>> I k
On 12/11/2020 18:00, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 11/11/2020 17:36, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> Ignore my previous message - whatever was wrong is now fixed. I didn't
>> change anything much so I think it was a dependency th
On 11/11/2020 17:36, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> Ignore my previous message - whatever was wrong is now fixed. I didn't
> change anything much so I think it was a dependency that had an issue
> and was since recompiled.
>
> 64-bit build is done and seems to
Ignore my previous message - whatever was wrong is now fixed. I didn't
change anything much so I think it was a dependency that had an issue
and was since recompiled.
64-bit build is done and seems to work fine. I'm testing it using the
samples, nearly all of which work, and new things that
On 28/10/2020 08:40, Achim Gratz wrote:
> Hamish McIntyre-Bhatty via Cygwin-apps writes:
>> Another interesting thing is that I get the following messages when
>> running cygport install:
>>
>> Warning: x was not linked with -Wl, --enable-auto-image-base
>>
>&g
On 28/10/2020 08:40, Achim Gratz wrote:
> Hamish McIntyre-Bhatty via Cygwin-apps writes:
>> Another interesting thing is that I get the following messages when
>> running cygport install:
>>
>> Warning: x was not linked with -Wl, --enable-auto-image-base
>>
>&g
On 27/10/2020 13:16, ASSI wrote:
> Hamish McIntyre-Bhatty via Cygwin-apps writes:
>> Unfortunately, the unit tests do not run correctly for me, but it seems
>> they were originally disabled by Yakkov, probably for this exact reason.
> I believe many of the Gtk packages were eit
On 21/10/2020 19:39, Achim Gratz wrote:
> Brian Inglis writes:
>> I should now add [branch "playground"] entries to make testing appveyor CI
>> builds cleaner and easier, as I usually don't do this stuff enough to
>> remember
>> how to do it, so I muddle through, and then forget what I need to
On 19/10/2020 16:31, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 17/10/2020 16:04, Brian Inglis wrote:
>> On 2020-10-17 07:17, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>>> On 17/10/2020 01:21, Lemures Lemniscati via Cygwin-apps wrote:
>>>> On Fri, 16 O
On 17/10/2020 16:04, Brian Inglis wrote:
> On 2020-10-17 07:17, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> On 17/10/2020 01:21, Lemures Lemniscati via Cygwin-apps wrote:
>>> On Fri, 16 Oct 2020 20:20:53 +0100, Hamish McIntyre-Bhatty via Cygwin-apps
>>>> Just se
On 17/10/2020 01:21, Lemures Lemniscati via Cygwin-apps wrote:
> On Fri, 16 Oct 2020 20:20:53 +0100, Hamish McIntyre-Bhatty via Cygwin-apps
>> Hi there,
>>
>> Just sending this out so I can update wxWidgets to 3.0.5.1. I've pulled
>> in new patches from Fedora, but I can
Hi there,
Just sending this out so I can update wxWidgets to 3.0.5.1. I've pulled
in new patches from Fedora, but I can't find
mirror://portage/x11-libs/wxGTK/files/wxGTK-3.0.3-collision.patch
anywhere. Does anyone happen to have a copy of this?
My hope is that it is no longer needed, but
On 13/09/2020 17:07, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 13/09/2020 15:57, Jon Turney wrote:
>> I don't see a statement here or on the website of the license this is
>> under.
>>
>> Assuming the answer to that is satisfactory:
>>
>> +1
>
On 13/09/2020 17:08, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 13/09/2020 16:02, Brian Inglis wrote:
>> On 2020-09-13 01:39, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>>> On 13/09/2020 07:13, Achim Gratz wrote:
>>>> Hamish McIntyre-Bhatty via Cygwin-apps
On 13/09/2020 16:02, Brian Inglis wrote:
> On 2020-09-13 01:39, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> On 13/09/2020 07:13, Achim Gratz wrote:
>>> Hamish McIntyre-Bhatty via Cygwin-apps writes:
>>>> Hmm, who decides (and how) what counts as a Linux distro?
On 13/09/2020 15:57, Jon Turney wrote:
> On 03/09/2020 14:44, marco atzeri via Cygwin-apps wrote:
>> On Wed, Sep 2, 2020 at 10:59 PM Hamish McIntyre-Bhatty via
>> Cygwin-apps wrote:
>>>
>>> On 02/09/2020 19:05, Marco Atzeri via Cygwin-apps wrote:
>>>>
On 13/09/2020 07:13, Achim Gratz wrote:
> Hamish McIntyre-Bhatty via Cygwin-apps writes:
>> Hmm, who decides (and how) what counts as a Linux distro?
> Something that is capable of and has actually done a license review.
Seems fair.
>> Either way, could anyone provide some ins
On 09/09/2020 11:36, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 04/09/2020 14:38, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>>
>> Thank you, that seemed to work well.
>>
>> New build dependencies added (also util-linux, binutils, cygwin, and
>> co
On 12/09/2020 22:20, Brian Inglis wrote:
> On 2020-09-12 09:03, Ken Brown via Cygwin-apps wrote:
>> On 9/11/2020 12:07 PM, Andrew Schulman via Cygwin-apps wrote:
>>> cygport has automated a lot of the work of building and maintaining
>>> packages for Cygwin. But one area where it doesn't help yet
On 04/09/2020 14:38, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>
> Thank you, that seemed to work well.
>
> New build dependencies added (also util-linux, binutils, cygwin, and
> coreutils), and updated as a noarch package with no other changes. The
> new files
On 03/09/2020 19:50, Ken Brown via Cygwin-apps wrote:
> On 9/3/2020 1:27 PM, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> On 03/09/2020 18:13, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>>>
>>> Good to know, and oh yeah, I'll do that tomorrow.
>>>
>
On 03/09/2020 18:13, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>
> Good to know, and oh yeah, I'll do that tomorrow.
>
> Cheers for the vote.
>
> Hamish
>
I should note that this is a pure python package - can it be a noarch
package? I'm not sure how to configure the
On 03/09/2020 17:34, Ken Brown via Cygwin-apps wrote:
> On 9/3/2020 10:10 AM, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> On 03/09/2020 14:44, marco atzeri via Cygwin-apps wrote:
>>> just to avoid misunderstandings, you have my vote, so
>>> you need only other 3
On 03/09/2020 14:44, marco atzeri via Cygwin-apps wrote:
> just to avoid misunderstandings, you have my vote, so
> you need only other 3 approvals as you count as 1
>
> Regards
> Marco
Thanks for your vote Marco :) Hopefully we can get some others onboard.
Just double-checked dependencies, and
On 02/09/2020 19:05, Marco Atzeri via Cygwin-apps wrote:
>
> Hi Hamish,
>
> it builds fine and there are no problem on tests.
>
> Are you missing some dependencies ?
>
> "On Cygwin, you need the smartmontools and blkid packages".
>
> but they are not there:
>
> $ cygport
*bump* in case this has not been seen.
Hamish
On 26/08/2020 10:35, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> Okay, I have updated the packages (same location:
> https://www.hamishmb.com/files/cygwin-temp/). It should now handle fork
> errors better.
>
> If it fails aga
for someone else to have a go as well - would be good to know
multiple people can reproduce this issue as I have still had no luck
doing that.
Thanks for your patience,
Hamish
On 21/08/2020 16:33, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 20/08/2020 07:01, Marco Atzeri via Cygwin-apps wr
On 20/08/2020 07:01, Marco Atzeri via Cygwin-apps wrote:
> On 19.08.2020 13:22, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> On 19/08/2020 06:53, Marco Atzeri via Cygwin-apps wrote:
>>>
>>> so
On 21/08/2020 15:24, ASSI wrote:
> Hamish McIntyre-Bhatty via Cygwin-apps writes:
>> How does cross compiling for 32-bit Cygwin work? I think it'd be useful
>> for me too - in one instance I've found that stripping debug symbols can
>> take 3 times as long to run under 32-
On 20/08/2020 20:47, Brian Inglis wrote:
> On 2020-08-20 12:18, Achim Gratz wrote:
>> Brian Inglis writes:
>>> Does it matter if I build mingw64 packages under Cygwin 64 or 32 bit: do I
>>> have
>>> to match the package being built, or does it not matter?
>> FWIW, I build my cross-compiled
On 19/08/2020 06:53, Marco Atzeri via Cygwin-apps wrote:
>
> something looks wrong on test
>
> ==
> ERROR: test_get_info (tests.getdevinfo_tests_cygwin.TestGetInfo)
> Test that the information can be collected on this system
On 17/08/2020 14:33, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> Hello,
>
> This email signals my intent to package getdevinfo.
>
> (https://www.hamishmb.com/html/downloads.php?program_name=getdevinfo)
> for Cygwin.
>
> getdevinfo is module I wrote for colle
.
Once I have done these things, I intend to improve Cygwin's device
information detection capabilities and release a further update to make
this more complete.
If anyone has feedback I'd appreciate it very much.
Hamish McIntyre-Bhatty
0x87B761FE07F548D6.asc
Description: application/pgp-keys
On 15/08/2020 16:35, Marco Atzeri via Cygwin-apps wrote:
> On 15.08.2020 15:32, Achim Gratz wrote:
>> Hamish McIntyre-Bhatty via Cygwin-apps writes:
>>> Who currently maintains python-bs4?
>>
>> Yaakov. You can find out for yourself by looking at cyg
On 15/08/2020 14:32, Achim Gratz wrote:
> Hamish McIntyre-Bhatty via Cygwin-apps writes:
>> Who currently maintains python-bs4?
> Yaakov. You can find out for yourself by looking at cygwin-pkg-maint on
> the server.
>
>
> Regards,
> Achim.
Oh yeah, I forgot that. Doe
Hello,
Who currently maintains python-bs4? Marco, if this is you I might
have to take you up on your offer and ask you to build a package for
Python 3.8 :)
If not I guess I'll do a one-time update to build for Python 3.8.
Hamish
0x87B761FE07F548D6.asc
Description: application/pgp-keys
On 23/07/2020 12:02, marco atzeri via Cygwin-apps wrote:
> On Thu, Jul 23, 2020 at 11:33 AM Hamish McIntyre-Bhatty via Cygwin-apps
> wrote:
>> Hello,
>>
>> Who currently maintains python-requests? Marco, if this is you I might
>> have to take you up on your offer
Hello,
Who currently maintains python-requests? Marco, if this is you I might
have to take you up on your offer and ask you to build a package for
Python 3.8 :)
If not I guess I'll do a one-time update to build for Python 3.8.
Hamish
0x87B761FE07F548D6.asc
Description: application/pgp-keys
On 19/07/2020 20:09, Marco Atzeri via Cygwin-apps wrote:
> https://cygwin.mirror.uk.sargasso.net/noarch/release/python-olefile/
>
> same packages are arch indipendent
Ah of course, so I was being a bit stupid :)
Okay, it ended up being today because python3-wx took so long to build,
but test
On 19/07/2020 18:09, Marco Atzeri via Cygwin-apps wrote:
> I assume you need to rebuild, as I saw python36-olefile and
> python37-olefile picked as dependency, so somewhere they were mentioned
> in the packages.
Okay, shall do tomorrow then. I note that while I can find the source
and binary
On 18/07/2020 21:07, Marco Atzeri via Cygwin-apps wrote:
> I change maintainership to you.
>
> Before uploading can you rebuild so to pick dependency on all
> version of python3x-olefile ?
Sure. I believe I can just change the cygport and hint files rather than
rebuilding for that?
Hamish
On 14/07/2020 15:41, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 10/07/2020 13:24, marco atzeri via Cygwin-apps wrote:
>> On Fri, Jul 10, 2020 at 12:28 PM Hamish McIntyre-Bhatty via Cygwin-apps
>> wrote:
>>> On 10/07/2020 01:20, airplanemath via Cygwin-apps wr
On 10/07/2020 13:24, marco atzeri via Cygwin-apps wrote:
> On Fri, Jul 10, 2020 at 12:28 PM Hamish McIntyre-Bhatty via Cygwin-apps
> wrote:
>> On 10/07/2020 01:20, airplanemath via Cygwin-apps wrote:
>>>> I tend to use loops like
>>>>
>>>> f
On 10/07/2020 01:20, airplanemath via Cygwin-apps wrote:
>> I tend to use loops like
>>
>> for ver in ${PYTHON_WHEEL_VERSIONS//:/ };
>> do
>> /usr/bin/python${ver} script
>> done
>>
>> for the tests. Also, I believe ${ARCH} is the same as $(uname -m) here,
>> if you want to streamline the
1 - 100 of 138 matches
Mail list logo
