On Feb 8 21:24, Achim Gratz wrote:
Corinna Vinschen writes:
Please apply.
Done. The notice via cygwin-apps-cvs was lost while the mailer was
having trouble to recognize the cygwin.com mailing lists.
The patch is in, that's the important part :)
Thanks,
Corinna
--
Corinna Vinschen
Corinna Vinschen writes:
Please apply.
Done. The notice via cygwin-apps-cvs was lost while the mailer was
having trouble to recognize the cygwin.com mailing lists.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
SD adaptations for Waldorf Q V3.00R3 and
On Feb 5 22:47, Achim Gratz wrote:
Corinna Vinschen writes:
...in other words, just drop the last three lines in your setup.hint,
and the external-source hint.
Done.
I noticed just in time that the preremove scripts can't be dash scripts
at the moment.
Here's a patch to change that
Corinna Vinschen writes:
On Feb 5 22:57, Achim Gratz wrote:
Oh, and while you are so deep in the bowels of setup.exe, would it be
possible to somehow fake a pty to shell scripts and a console to cmd so
that the scripts run by setup.exe produce their output in line-buffered
instead of fully
On Feb 6 12:25, Achim Gratz wrote:
Corinna Vinschen writes:
On Feb 5 22:57, Achim Gratz wrote:
Oh, and while you are so deep in the bowels of setup.exe, would it be
possible to somehow fake a pty to shell scripts and a console to cmd so
that the scripts run by setup.exe produce their
On Feb 5 22:57, Achim Gratz wrote:
Oh, and while you are so deep in the bowels of setup.exe, would it be
possible to somehow fake a pty to shell scripts and a console to cmd so
that the scripts run by setup.exe produce their output in line-buffered
instead of fully buffered mode?
Er...
On 02/06/2015 02:24 AM, Corinna Vinschen wrote:
On Feb 5 22:57, Achim Gratz wrote:
Oh, and while you are so deep in the bowels of setup.exe, would it be
possible to somehow fake a pty to shell scripts and a console to cmd so
that the scripts run by setup.exe produce their output in
On Feb 6 07:00, Eric Blake wrote:
On 02/06/2015 02:24 AM, Corinna Vinschen wrote:
On Feb 5 22:57, Achim Gratz wrote:
Oh, and while you are so deep in the bowels of setup.exe, would it be
possible to somehow fake a pty to shell scripts and a console to cmd so
that the scripts run by
Corinna Vinschen writes:
...in other words, just drop the last three lines in your setup.hint,
and the external-source hint.
Uploaded. Let's see what upset does with this.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
SD adaptations for KORG EX-800
On Feb 5 10:19, Corinna Vinschen wrote:
On Feb 5 10:12, Achim Gratz wrote:
Corinna Vinschen writes:
Yaakov, can we *please* get this done so we can upload the new
_autorebase?
I guess we can do it anyway, it's not creating a new problem if these
files are provided a few days
On Thu, 2015-02-05 at 16:24 +0100, Achim Gratz wrote:
Achim Gratz writes:
Corinna Vinschen writes:
...in other words, just drop the last three lines in your setup.hint,
and the external-source hint.
Uploaded. Let's see what upset does with this.
The pending update is currently
Corinna Vinschen writes:
...in other words, just drop the last three lines in your setup.hint,
and the external-source hint.
Done.
I noticed just in time that the preremove scripts can't be dash scripts
at the moment.
Here's a patch to change that and also allow .cmd scripts, just like
Corinna Vinschen writes:
The pending update is currently blocked by a duplicate python-doc
package...
I just had a look and there's no x86/release/python/python-doc directory.
It must have been removed in the last couple of minutes.
With that out of the way… can someone please hand over
On Feb 2 10:17, Corinna Vinschen wrote:
On Jan 30 20:13, Achim Gratz wrote:
Corinna Vinschen writes:
Btw., when, do you think, is showtime for _autorebase 2.0?
Sometime during the next week would be good, if not then another window
I'm on vaca today, but this week sounds good to me.
Achim Gratz writes:
Corinna Vinschen writes:
...in other words, just drop the last three lines in your setup.hint,
and the external-source hint.
Uploaded. Let's see what upset does with this.
The pending update is currently blocked by a duplicate python-doc
package...
Regards,
Achim.
--
Oh, and while you are so deep in the bowels of setup.exe, would it be
possible to somehow fake a pty to shell scripts and a console to cmd so
that the scripts run by setup.exe produce their output in line-buffered
instead of fully buffered mode?
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305
Yaakov Selkowitz writes:
The pending update is currently blocked by a duplicate python-doc
package...
Yes, we know; it's fixed now.
Rats, it had removed the !ready files before the transfer took place.
I'll have to arm it again.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb
On Feb 5 16:24, Achim Gratz wrote:
Achim Gratz writes:
Corinna Vinschen writes:
...in other words, just drop the last three lines in your setup.hint,
and the external-source hint.
Uploaded. Let's see what upset does with this.
The pending update is currently blocked by a duplicate
On Feb 5 10:12, Achim Gratz wrote:
Corinna Vinschen writes:
Yaakov, can we *please* get this done so we can upload the new
_autorebase?
I guess we can do it anyway, it's not creating a new problem if these
files are provided a few days later. Let me know when you've switched
off the
Corinna Vinschen writes:
Yaakov, can we *please* get this done so we can upload the new
_autorebase?
I guess we can do it anyway, it's not creating a new problem if these
files are provided a few days later. Let me know when you've switched
off the _autorebase autodep and version increment
On Thu, 2015-02-05 at 09:57 +0100, Corinna Vinschen wrote:
On Feb 2 10:17, Corinna Vinschen wrote:
On Jan 30 20:13, Achim Gratz wrote:
Corinna Vinschen writes:
Btw., when, do you think, is showtime for _autorebase 2.0?
Sometime during the next week would be good, if not then
Marco Atzeri writes:
done.
You are no co-owner with Corinna
Great, just in time to re-trigger the upload before the next sync.
:-)
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
SD adaptation for Waldorf rackAttack V1.04R1:
On 2/5/2015 8:18 PM, Achim Gratz wrote:
Corinna Vinschen writes:
With that out of the way… can someone please hand over (co-)ownership of
_autorebase in cygwin-pkg-maint and !packages to me so that I can
actually upload the new package?
done.
You are no co-owner with Corinna
Regards,
Hi Ken,
On Feb 3 16:50, Ken Brown wrote:
On 2/3/2015 10:27 AM, Corinna Vinschen wrote:
On Feb 3 08:04, Ken Brown wrote:
On 2/3/2015 6:33 AM, Corinna Vinschen wrote:
Hey guys,
On Jan 28 21:23, Corinna Vinschen wrote:
https://cygwin.com/setup-test-x86.exe
Corinna Vinschen writes:
Try this:
Works a treat, please install.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
On Feb 3 22:27, Corinna Vinschen wrote:
On Feb 3 22:04, Corinna Vinschen wrote:
On Feb 3 21:37, Achim Gratz wrote:
I'm not sure we're talking about the same thing. I've recently added
code to print an error message along with the parameter usage when a
wrong option or other
Corinna Vinschen writes:
I just applied a bigger patch, which not only changed exit, but the way
how the actual LogFile instance gets accessed in general. I removed the
variable theLog entirely and now, rather than
[...]
Please give it a try. For your convenience I created test releases
On Feb 4 12:19, Achim Gratz wrote:
Corinna Vinschen writes:
I just applied a bigger patch, which not only changed exit, but the way
how the actual LogFile instance gets accessed in general. I removed the
variable theLog entirely and now, rather than
[...]
Please give it a try. For
On Feb 4 10:01, Corinna Vinschen wrote:
On Feb 3 22:27, Corinna Vinschen wrote:
On Feb 3 22:04, Corinna Vinschen wrote:
On Feb 3 21:37, Achim Gratz wrote:
I'm not sure we're talking about the same thing. I've recently added
code to print an error message along with the parameter
Corinna Vinschen writes:
Did you test this version? Is it ok to become the release version of
setup?
WJFFM. I didn't test the downgrade scenario since none of my
installations have test or prev packages in setup.ini, though.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb
On Feb 3 16:09, Achim Gratz wrote:
Achim Gratz writes:
[TEST 2]
[TEST 3]
*frown*
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
pgpSYYQo2uQAv.pgp
Description: PGP signature
[TEST]
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
DIY Stuff:
http://Synth.Stromeko.net/DIY.html
[TEST 2]
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
Achim Gratz writes:
[TEST 2]
[TEST 3]
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
On Feb 3 08:04, Ken Brown wrote:
On 2/3/2015 6:33 AM, Corinna Vinschen wrote:
Hey guys,
On Jan 28 21:23, Corinna Vinschen wrote:
https://cygwin.com/setup-test-x86.exe
https://cygwin.com/setup-test-x86_64.exe
These should fix the aforementioned bug I introduced, as well as
On Feb 3 14:56, ASSI wrote:
Corinna Vinschen writes:
Did you test this version? Is it ok to become the release version of
setup?
WJFFM. I didn't test the downgrade scenario since none of my
installations have test or prev packages in setup.ini, though.
You're a user of the new -m
Hey guys,
On Jan 28 21:23, Corinna Vinschen wrote:
https://cygwin.com/setup-test-x86.exe
https://cygwin.com/setup-test-x86_64.exe
These should fix the aforementioned bug I introduced, as well as another
subtil problem when checking and unchecking the Bin/Src boxes. If both
boxes
Corinna Vinschen writes:
You're a user of the new -m option if I understood you correctly.
Does it work for you?
Yes, very well indeed.
What about allowing to specify this in the GUI? I was mulling over
adding a fourth option to the Choose A Download Source dialog:
o Install from
On Feb 3 17:07, Achim Gratz wrote:
Corinna Vinschen writes:
You're a user of the new -m option if I understood you correctly.
Does it work for you?
Yes, very well indeed.
What about allowing to specify this in the GUI? I was mulling over
adding a fourth option to the Choose A
Corinna Vinschen writes:
On Feb 3 16:09, Achim Gratz wrote:
Achim Gratz writes:
[TEST 2]
[TEST 3]
*frown*
Sorry for that, but the mail server I use needed a configuration change
and this is the only mailing list that was affected so I had to test
directly. Things are back to normal, I
Corinna Vinschen writes:
How so? Setup is not a Cygwin application.
Good point. Then I've no idea at all, save the compiler.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
Factory and User Sound Singles for Waldorf Blofeld:
On 2/3/2015 6:33 AM, Corinna Vinschen wrote:
Hey guys,
On Jan 28 21:23, Corinna Vinschen wrote:
https://cygwin.com/setup-test-x86.exe
https://cygwin.com/setup-test-x86_64.exe
These should fix the aforementioned bug I introduced, as well as another
subtil problem when checking and
On Feb 3 21:37, Achim Gratz wrote:
Corinna Vinschen writes:
On Feb 3 18:08, Achim Gratz wrote:
Corinna Vinschen writes:
How so? Setup is not a Cygwin application.
Good point. Then I've no idea at all, save the compiler.
I had a look into this and even rearranged the behaviour
On Feb 3 18:08, Achim Gratz wrote:
Corinna Vinschen writes:
How so? Setup is not a Cygwin application.
Good point. Then I've no idea at all, save the compiler.
I had a look into this and even rearranged the behaviour when --help
output is requested...
However, I'm mildly sure this
Corinna Vinschen writes:
On Feb 3 18:08, Achim Gratz wrote:
Corinna Vinschen writes:
How so? Setup is not a Cygwin application.
Good point. Then I've no idea at all, save the compiler.
I had a look into this and even rearranged the behaviour when --help
output is requested...
On Feb 3 22:04, Corinna Vinschen wrote:
On Feb 3 21:37, Achim Gratz wrote:
Corinna Vinschen writes:
On Feb 3 18:08, Achim Gratz wrote:
Corinna Vinschen writes:
How so? Setup is not a Cygwin application.
Good point. Then I've no idea at all, save the compiler.
I had a
On 2/3/2015 10:27 AM, Corinna Vinschen wrote:
On Feb 3 08:04, Ken Brown wrote:
On 2/3/2015 6:33 AM, Corinna Vinschen wrote:
Hey guys,
On Jan 28 21:23, Corinna Vinschen wrote:
https://cygwin.com/setup-test-x86.exe
https://cygwin.com/setup-test-x86_64.exe
These should fix the
On Jan 30 20:13, Achim Gratz wrote:
Corinna Vinschen writes:
Btw., when, do you think, is showtime for _autorebase 2.0?
Sometime during the next week would be good, if not then another window
I'm on vaca today, but this week sounds good to me. I will release
1.7.34, too, later this week.
On 1/30/2015 8:13 PM, Achim Gratz wrote:
Corinna Vinschen writes:
Btw., when, do you think, is showtime for _autorebase 2.0?
Sometime during the next week would be good, if not then another window
would be two weeks later. From the responses so far I gathered that
Marco doesn#t think he
Corinna Vinschen writes:
Btw., when, do you think, is showtime for _autorebase 2.0?
Sometime during the next week would be good, if not then another window
would be two weeks later. From the responses so far I gathered that
Marco doesn#t think he needs to do something for Octave and R, I will
On 1/30/2015 11:11 PM, Marco Atzeri wrote:
On 1/30/2015 8:13 PM, Achim Gratz wrote:
Corinna Vinschen writes:
Btw., when, do you think, is showtime for _autorebase 2.0?
Octave no, but R yes.
I will upload the R_autorebase-001001-1.tar.xz together with the new
3.1.2 build as soon ready
On Jan 29 18:27, Achim Gratz wrote:
Corinna Vinschen writes:
Thank you for this!
Well, I added it for entirely selfish reasons, so I'm not sure I deserve
getting thanks :)
I thanked you for the selfish reason that I got this crossed off my TODO
list without any effort on my part, so
Corinna Vinschen writes:
Thank you for this!
Well, I added it for entirely selfish reasons, so I'm not sure I deserve
getting thanks :)
I thanked you for the selfish reason that I got this crossed off my TODO
list without any effort on my part, so we're even. ;-)
Regards,
Achim.
--
+[Q+
On Jan 28 22:55, Achim Gratz wrote:
Corinna Vinschen writes:
This version also introduces an experimental option -m/--mirror-mode.
Thank you for this!
Well, I added it for entirely selfish reasons, so I'm not sure I deserve
getting thanks :)
In the meantime I tried what happens if the
On Jan 27 22:14, Corinna Vinschen wrote:
On Jan 27 22:04, Achim Gratz wrote:
Corinna Vinschen writes:
Or today. Can you try this patch? Most of it is a bit of reformatting,
the importnat part is the last set_action call.
I think I'll get this wedged in sometime tomorrow.
Thanks.
Corinna Vinschen writes:
This version also introduces an experimental option -m/--mirror-mode.
Thank you for this!
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
Waldorf MIDI Implementation additional documentation:
Corinna Vinschen writes:
On Jan 27 07:55, Achim Gratz wrote:
You may have solved a long-standing problem. Let's see if everything
else still works... :-)
Orpahned package removal doesn't work anymore, but I have no time to
take a closer look this week.
BTW, if you switch one package to test
On 1/27/2015 7:25 PM, Achim Gratz wrote:
Corinna Vinschen writes:
On Jan 27 07:55, Achim Gratz wrote:
You may have solved a long-standing problem. Let's see if everything
else still works... :-)
Orpahned package removal doesn't work anymore, but I have no time to
take a closer look this
Corinna Vinschen writes:
Example? I just tried the libppl and libmpc1 packages, and they simply
don;'t show up anymore, neither in the current setup 2.859, nor ithe
test setup 2.861. I don't see a difference in behaviour.
You have to use the -o / --delete-orphans option for this to kick in.
On Jan 27 07:55, Achim Gratz wrote:
Corinna Vinschen writes:
I checked in code which fixes this issue, which simplifies the package
choosing algorithm when clicking on the package line, and which
implements the default package in a way which never downgrades a
package without the user's
On Jan 27 21:37, Corinna Vinschen wrote:
On Jan 27 20:59, Achim Gratz wrote:
Corinna Vinschen writes:
Example? I just tried the libppl and libmpc1 packages, and they simply
don;'t show up anymore, neither in the current setup 2.859, nor ithe
test setup 2.861. I don't see a difference
On Jan 27 20:59, Achim Gratz wrote:
Corinna Vinschen writes:
Example? I just tried the libppl and libmpc1 packages, and they simply
don;'t show up anymore, neither in the current setup 2.859, nor ithe
test setup 2.861. I don't see a difference in behaviour.
You have to use the -o /
Corinna Vinschen writes:
Why not? Consider: I want to *run* the new DLL, but I want to *build*
packages for the current release. That means, I need cygwin-1.7.34-005
but cygwin-devel-1.7.33-1.
That's exactly why I properly package all snapshots by integrating them
with their base packages.
Corinna Vinschen writes:
That's exactly why I properly package all snapshots by integrating them
with their base packages. I've posted the Makefile before but, it has
changed a bit in the last few months, so if you're interested I can post
it again.
You lost me here. What snapshots?!?
At
Corinna Vinschen writes:
Or today. Can you try this patch? Most of it is a bit of reformatting,
the importnat part is the last set_action call.
I think I'll get this wedged in sometime tomorrow.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
SD
On Jan 27 22:04, Achim Gratz wrote:
Corinna Vinschen writes:
Or today. Can you try this patch? Most of it is a bit of reformatting,
the importnat part is the last set_action call.
I think I'll get this wedged in sometime tomorrow.
Thanks. I think I have a better one, though. The
On Jan 27 21:50, Achim Gratz wrote:
Corinna Vinschen writes:
Why not? Consider: I want to *run* the new DLL, but I want to *build*
packages for the current release. That means, I need cygwin-1.7.34-005
but cygwin-devel-1.7.33-1.
That's exactly why I properly package all snapshots by
On Jan 27 19:25, Achim Gratz wrote:
Corinna Vinschen writes:
On Jan 27 07:55, Achim Gratz wrote:
You may have solved a long-standing problem. Let's see if everything
else still works... :-)
Orpahned package removal doesn't work anymore, but I have no time to
take a closer look this
On Jan 26 11:45, Corinna Vinschen wrote:
On Jan 26 11:15, Achim Gratz wrote:
Corinna Vinschen writes:
No, no. Thanks for noticing! I was sure that the comparison operators
are comparing using compareVersions() under the hood so I didn't check.
How embarrassing. Now I see that they
Corinna Vinschen writes:
I checked in code which fixes this issue, which simplifies the package
choosing algorithm when clicking on the package line, and which
implements the default package in a way which never downgrades a
package without the user's explicit consent by choosing the lower
On Jan 25 18:20, Corinna Vinschen wrote:
Example:
foo-1.22-1 is installed
foo-1.23-1 is curr
foo-1.24-1 is test
== Setup chooses 1.23-1 as default.
User installs 1.24-1. Next Setup run:
foo-1.24-1 is installed
foo-1.23-1 is curr
foo-1.24-1 is test
== Setup chooses
Corinna Vinschen writes:
No, no. Thanks for noticing! I was sure that the comparison operators
are comparing using compareVersions() under the hood so I didn't check.
How embarrassing. Now I see that they only do a casecompare, as you said.
That's arguably a bug in the comparison operator
Corinna Vinschen writes:
What if the test version gets removed, without updating curr?
Then there presumably was a good reason to pull that test version.
What would make more(?) sense is sticking to installed instead,
because the version number is higher than the curr version. This
On Jan 26 11:20, Achim Gratz wrote:
Corinna Vinschen writes:
What if the test version gets removed, without updating curr?
Then there presumably was a good reason to pull that test version.
What would make more(?) sense is sticking to installed instead,
because the version number
On Mon, 2015-01-26 at 10:58 +0100, Corinna Vinschen wrote:
On Jan 25 18:20, Corinna Vinschen wrote:
Example:
foo-1.22-1 is installed
foo-1.23-1 is curr
foo-1.24-1 is test
== Setup chooses 1.23-1 as default.
User installs 1.24-1. Next Setup run:
foo-1.24-1 is
Hi Achim,
On Jan 25 19:42, Achim Gratz wrote:
Corinna Vinschen writes:
Instead of always defaulting to the curr version, Setup now checks if
the installed version of a package is higher than the curr version of
the package. If so, and if a test version exists for this package, it
will
Hi David,
On Jan 25 23:46, David Stacey wrote:
On 25/01/15 17:20, Corinna Vinschen wrote:
Instead of always defaulting to the curr version, Setup now checks if
the installed version of a package is higher than the curr version of
the package.
This sounds like a great idea - providing that
On Jan 26 11:15, Achim Gratz wrote:
Corinna Vinschen writes:
No, no. Thanks for noticing! I was sure that the comparison operators
are comparing using compareVersions() under the hood so I didn't check.
How embarrassing. Now I see that they only do a casecompare, as you said.
That's
Corinna Vinschen writes:
Instead of always defaulting to the curr version, Setup now checks if
the installed version of a package is higher than the curr version of
the package. If so, and if a test version exists for this package, it
will choose the test version by default. A welcome side
On 25/01/15 17:20, Corinna Vinschen wrote:
Instead of always defaulting to the curr version, Setup now checks if
the installed version of a package is higher than the curr version of
the package.
This sounds like a great idea - providing that the logic to compare two
version numbers is
80 matches
Mail list logo
