Corinna Vinschen writes:
>> Sure, but co-maintenance _is_ possible, with each of the maintainers
>> having their own separate upload area.
>
> Yes, but Michael still has to become maintainer, even if co-maintainer.
True, in the absence of anything better he should probably ITA the
package and
Yaakov Selkowitz writes:
> Is anyone using the cygwin32- and/or cygwin64-* cross-compiling
> toolchain for anything besides cross-building cygwin itself? I would
> like to remove most of these from the distro if at all possible.
Never used them… :-)
Regards,
Achim.
--
+<[Q+ Matrix-12
Jon Turney writes:
> I think currently UTF-8 displays correctly in the HTML package pages,
> but neither encoding displays correctly in setup.
>
> I'd suggest that we specify UTF-8 and eventually fix setup to handle that.
UTF-8 these days, please.
> I'd suggest this mangling is removed, and
On Feb 8 17:42, Tony Kelman wrote:
> >> Tony@LAPTOP-O230JCFF ~/github/cygwin-p7zip
> >> $ cygport p7zip-15.09-2.cygport upload
> > Uploading p7zip-15.09-2.x86_64
> > Running lftp sftp://cyg...@cygwin.com
> >> Password:
> >> cd: Fatal error: Host key verification failed
> >
On Feb 8 20:13, Achim Gratz wrote:
> Corinna Vinschen writes:
> > This is not quite how it works. The maintainer has upload permissions
> > using his/her ssh key. You only get to do that if you become package
> > maintainer. See https://sourceware.org/cygwin-apps/package-upload.html
>
> Sure,
While I've been looking at replacement/improvement for the current upset
script, I've come across some minor issues related to
under-specification or under-documentation of setup.hint:
* The encoding of setup.hint is unspecified.
Historically both ISO-8859-1 and UTF-8 have been used. (e.g.
On Feb 9 13:18, Jon Turney wrote:
>
> While I've been looking at replacement/improvement for the current upset
> script, I've come across some minor issues related to under-specification or
> under-documentation of setup.hint:
>
> * The encoding of setup.hint is unspecified.
>
> Historically
> Is anyone using the cygwin32- and/or cygwin64-* cross-compiling
> toolchain for anything besides cross-building cygwin itself? I would
> like to remove most of these from the distro if at all possible.
FWIW, I've tried to cross-compile some of my packages between i386 and x86_64,
and it's
>> I don't have anything for sourceware or cygwin.com in
>> ~/.ssh/known_hosts, should I?
>
> In theory, yes. It's usually collected the first time you connect to
> the host. The idea is to have a known key to compare the host against
> to disallow MITM attacks.
Hm okay, what's the best way to
