On Jun 3 10:31, Marco Atzeri wrote:
On 6/3/2015 10:19 AM, Corinna Vinschen wrote:
If you're willing to take a look into these upset perl scripts, please
apply for a normal ssh account on sourceware.org via
https://sourceware.org/cgi-bin/pdw/ps_form.cgi
Use my private email address
On 6/3/2015 10:19 AM, Corinna Vinschen wrote:
If you're willing to take a look into these upset perl scripts, please
apply for a normal ssh account on sourceware.org via
https://sourceware.org/cgi-bin/pdw/ps_form.cgi
Use my private email address as approver. And make sure to use
On Jun 2 18:24, Achim Gratz wrote:
Corinna Vinschen writes:
Why? In any case it'd be easy enough to make it switchable.
Transition period. We should do changes like that in two steps, first
updating to a setup which handles the new checksums, then changing the
generation of checksums
On 06/03/2015 05:07 AM, Corinna Vinschen wrote:
On Jun 3 10:31, Marco Atzeri wrote:
On 6/3/2015 10:19 AM, Corinna Vinschen wrote:
If you're willing to take a look into these upset perl scripts, please
apply for a normal ssh account on sourceware.org via
Corinna Vinschen writes:
There's no reason for upset to create more than one style of checksum.
MD5, SHA512, SHA512/base64, whatever. What I'm talking about is the
client side. The setup tool should understand all types of checksums
used. Right now it identifies MD5 vs. SHA512 just by the
On Wed, 2015-06-03 at 10:19 +0200, Corinna Vinschen wrote:
On Jun 2 18:24, Achim Gratz wrote:
Corinna Vinschen writes:
Upset is a beast. It handles ini file creation as well as creating the
package information for https://cygwin.com/cgi-bin2/package-grep.cgi,
as well as the package
Reminded by a recent request as to how to install xorg-server-1.17.1-2, which
has disappeared beyond setup's ken (in order to determine if there was a
regression in the curent version), this is a re-send of a patch I originally
submitted back in 2011 [1], which received an ambiguous response then.
Yaakov Selkowitz writes:
Anyone looking at the sources would be tainted thereby. Because we are
concerned about the licensing of upset, AFAICS we are going to have to
clean-room reverse-engineer this.
So what exactly does upset that genini doesn't when it comes to
generating setup.ini and
I have a package (socat) where I need to set the curr: and test: fields in
setup.hint. I got tired of adding them to the autogenerated setup.hint files
after every build, so I wrote a patch for cygport to support specifying them in
the cygport file. For example, setting
CURR=1.7.3.0-2
