Perhaps it's unnecessary to point out that this went to the wrong
reply address, 100% my fault, mostly harmless though.
Top posted because it seemed appropriate in this case.
On November 30, 2022 at 22:43 b...@theworld.com (b...@theworld.com) wrote:
>
> FWIW this has come up on World sin
FWIW this has come up on World since more or less the beginning and
our policy thus far has been to consider an account name permanently
in use even if the underlying account has been closed.
One big problem here is that getting someone's email is enough to, for
example, steal domains they may o
On Sat, 26 Nov 2022 13:03:27 -0500, Mark Murawski wrote:
What would the best way to go about getting an updated build of a
specific package?
Right now I'm particularly interested in getting the latest version of
terminator.
Post with subject e.g. "python terminator upgrade Attn: maintainer" an
On Sat, Nov 26, 2022 at 01:03:27PM -0500, Mark Murawski wrote:
> Hi!
>
>
> What would the best way to go about getting an updated build of a specific
> package?
>
> Right now I'm particularly interested in getting the latest version of
> terminator.
>
>
> Terminator Terminal Package:
>
> Late
Hi!
What would the best way to go about getting an updated build of a
specific package?
Right now I'm particularly interested in getting the latest version of
terminator.
Terminator Terminal Package:
Latest in Debian: 2.1.2-1
Latest in cygwin: 0.98-1
Thanks.
--
Problem reports:
On 2017-07-05 08:27, Corinna Vinschen wrote:
> On Jul 5 13:32, Nellis, Kenneth wrote:
>> Curious about an error that setup.exe reported today related to upgrading
>> package cygwin-doc to 2.8.1-1, saying:
>>
>> Postinstall script errors
>> These do not necessarily mean that affected packages
On Jul 5 13:32, Nellis, Kenneth wrote:
> Curious about an error that setup.exe reported today related to upgrading
> package cygwin-doc to 2.8.1-1, saying:
>
> Postinstall script errors
> These do not necessarily mean that affected packages will fail to
> function
> properly, but pl
Curious about an error that setup.exe reported today related to upgrading
package cygwin-doc to 2.8.1-1, saying:
Postinstall script errors
These do not necessarily mean that affected packages will fail to
function
properly, but please check /var/log/setup.log.full and report any
On 2016-03-17 12:10, Jonathan D Johnston wrote:
Usage of freshclam (1) reports that the recommended version of ClamAV is
0.99.1, but the most recent version in https://cygwin.com/packages/ is
0.98.7 . Version 0.98.7 isn't functional with the current ClamAV
databases. Can this package be updated
Attention package clamav maintainer (Reini Urban?)
Usage of freshclam (1) reports that the recommended version of ClamAV is
0.99.1, but the most recent version in https://cygwin.com/packages/ is
0.98.7 . Version 0.98.7 isn't functional with the current ClamAV
databases. Can this package be updat
: Request for package update
Attention package clamav maintainer (Reini Urban?)
Usage of freshclam (1) reports that the recommended version of ClamAV is
0.99.1, but the most recent version in https://cygwin.com/packages/ is
0.98.7 . Version 0.98.7 isn't functional with the current ClamAV
data
The same number of CMake unit tests passed with an unpatched bootstrap
straight from the upstream sources, so I didn't get the entire rationale.
-Tony
PathCygwinToWin32 was using a deprecated cygwin_conv_to_win32
that is not present in x86_64 version of cygwin.
I've updated this set of patche
On 01/10/2014 04:42, Tony Kelman wrote:
When you do so, please be sure to include the patchset:
http://sf.net/p/cygwin-ports/cmake
These patches are required for a usable cmake on Cygwin.
FYI, I updated Yaakov's patches for 3.0.2 here
https://github.com/tkelman/cygwin-cmake
Although I never g
When you do so, please be sure to include the patchset:
http://sf.net/p/cygwin-ports/cmake
These patches are required for a usable cmake on Cygwin.
FYI, I updated Yaakov's patches for 3.0.2 here
https://github.com/tkelman/cygwin-cmake
Although I never got an answer on cygwin-apps for exactly w
On 30/09/2014 18:27, Bill Hoffman wrote:
On 9/23/2014 12:45 AM, Tony Kelman wrote:
Bump. Any update from the cmake maintainer? Upstream is at 3.0.2 now.
Sorry folks...
I will try to get 3.0.2 up in the next week.
-Bill
Hi Bill,
welcome back, hope everything is fine.
Please note that in ad
On 2014-09-30 11:27, Bill Hoffman wrote:
On 9/23/2014 12:45 AM, Tony Kelman wrote:
Bump. Any update from the cmake maintainer? Upstream is at 3.0.2 now.
Sorry folks...
I will try to get 3.0.2 up in the next week.
When you do so, please be sure to include the patchset:
http://sf.net/p/cygwin
On 9/23/2014 12:45 AM, Tony Kelman wrote:
Bump. Any update from the cmake maintainer? Upstream is at 3.0.2 now.
Sorry folks...
I will try to get 3.0.2 up in the next week.
-Bill
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentat
today we are in the situation that
32 bit has cmake-2.8.9-2
64 bit has cmake-2.8.11.2-1 that was not
uploaded by Bill if I remember right
and the 64bit version surely need at least one patch,
that I am aware of.
Bill,
I would appreciate to see both version at 2.8.12.2.
Could you take care or we s
On 13/07/2014 11:05, Yaakov Selkowitz wrote:
On 2014-07-12 23:17, Marco Atzeri wrote:
Bill,
are you planning to update the cygwin package any time soon ?
Please not that the 32bit is still at
cmake-2.8.9-2 version
while last upstream 2.9.x version is 2.9.12.
IIUC 2.9 was a development branch
On 2014-07-12 23:17, Marco Atzeri wrote:
Bill,
are you planning to update the cygwin package any time soon ?
Please not that the 32bit is still at
cmake-2.8.9-2 version
while last upstream 2.9.x version is 2.9.12.
IIUC 2.9 was a development branch leading to a stable 3.0 release, so we
don't
Bill,
are you planning to update the cygwin package any time soon ?
Please not that the 32bit is still at
cmake-2.8.9-2 version
while last upstream 2.9.x version is 2.9.12.
Thanks in advance
Marco Atzeri
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cyg
On Tue, Nov 27, 2012 at 08:13:01AM -0500, Earnie Boyd wrote:
> On Mon, Nov 26, 2012 at 8:55 PM, Ryan Johnson wrote:
> > Out of curiosity, what typically holds back releasing a new version?
> > Do you often end up having to deal with bugs and patches?
>
> Usually it is a round tuit. (http://en.wikt
On 27/11/2012 8:13 AM, Earnie Boyd wrote:
On Mon, Nov 26, 2012 at 8:55 PM, Ryan Johnson wrote:
Out of curiosity, what typically holds back releasing a new version?
Usually it is a round tuit. (http://en.wiktionary.org/wiki/round_tuit)
Awesome. I needs me one of those.
--
Problem reports:
On Mon, Nov 26, 2012 at 8:55 PM, Ryan Johnson wrote:
>
> Out of curiosity, what typically holds back releasing a new version?
Usually it is a round tuit. (http://en.wiktionary.org/wiki/round_tuit)
--
Earnie
-- https://sites.google.com/site/earnieboyd
--
Problem reports: http://cygwin.com/p
On Mon, Nov 26, 2012 at 08:55:32PM -0500, Ryan Johnson wrote:
>On 26/11/2012 8:35 PM, Jason Tishler wrote:
>> Ryan,
>>
>> On Mon, Nov 26, 2012 at 03:09:01PM -0500, Ryan Johnson wrote:
>>> Hi all (attn python maintainer),
>>>
>>> Would it be possible to update to python 2.7? The current released
>>>
On 26/11/2012 8:35 PM, Jason Tishler wrote:
Ryan,
On Mon, Nov 26, 2012 at 03:09:01PM -0500, Ryan Johnson wrote:
Hi all (attn python maintainer),
Would it be possible to update to python 2.7? The current released
package (2.6.8-2) lacks several features available in 2.7.
Are you psychic? I ju
Ryan,
On Mon, Nov 26, 2012 at 03:09:01PM -0500, Ryan Johnson wrote:
> Hi all (attn python maintainer),
>
> Would it be possible to update to python 2.7? The current released
> package (2.6.8-2) lacks several features available in 2.7.
Are you psychic? I just started today. Sorry, but I don't h
Hi all (attn python maintainer),
Would it be possible to update to python 2.7? The current released
package (2.6.8-2) lacks several features available in 2.7.
Thanks,
Ryan
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
I use MinGW-W64 to cross-compile libs and apps from cygwin environment..
But lately I can't build some gnu libraries because of a bothering
problem in mingw 64-bit headers.. Current version on cygwin mirrors is
3.0b-svn5134 and that is the one which give me headaches.. The MinGW-W64
team has fixed
On 8/7/2012 1:06 PM, Diego Biurrun wrote:
On Mon, Aug 06, 2012 at 08:48:47PM +0200, Diego Biurrun wrote:
The NASM package in Cygwin is getting a tad long in the tooth. There is
NASM 2.08.02 available, but 2.10.03 is current, i.e. NASM has done two
major releases in the meantime. The package f
On Mon, Aug 06, 2012 at 08:48:47PM +0200, Diego Biurrun wrote:
>
> The NASM package in Cygwin is getting a tad long in the tooth. There is
> NASM 2.08.02 available, but 2.10.03 is current, i.e. NASM has done two
> major releases in the meantime. The package for Cygwin was created
> over two year
Hello everybody!
The NASM package in Cygwin is getting a tad long in the tooth. There is
NASM 2.08.02 available, but 2.10.03 is current, i.e. NASM has done two
major releases in the meantime. The package for Cygwin was created
over two years ago.
Newer NASM versions are required to assemble mod
Hello,
I intend to build rawstudio (rawstudio.org) - somebody stated that he could do
it, but I couldn't contact him so far.
At configure step, rawstudio thrown the error saying he needs a newet gtk that
cygwin provides by standard setup.
I've took the lates gtk+ packages from www.gtk.org.
I've
33 matches
Mail list logo
