-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
> There's a few packaging oddities with regards to X fonts requirements,
> which could probably do with tidying up.
Agreed. Opened bug accordingly:
http://sourceware.org/bugzilla/show_bug.cgi?id=9761
Yaakov
Cygwin/X
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
> I'm sorry that I wasn't completely precise but, yes, of course I meant
> the Cygwin/X component.
Could you make me (yselkowitz AT cygwin DOT com) the default
owner/assignee for the Cygwin/X component?
Yaakov
Cygwin/X
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
> Attached is a patch against the xinit package in cygports svn:
>
> * In an attempt to avoid some instances of the ever popular "I upgraded
> X and now my keyboard doesn't work" problem, update the X server
> starting sample scrip
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
> Ah, and what do you think about the attached change to the .cygport file
> itself to propagate the distribution patchlevel into the version number?
I would prefer to use the BUILD_DATE define instead, since that is a
patch to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Paul Loewenstein wrote:
> Sorry, I did the diff backwards. You can tell I don't do this often.
>
> Corrected .diffs attached, so you don't have to use the patch reverse
> option.
Could you please provide these as one unidiff (-u) patch?
Yaakov
C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dr. Volker Zell wrote:
> An old cygwin installation where I haven't updated Xorg yet doesn't show
> this behavior.
>
> So it really looks like some X lib is the culprit.
I've got a hunch. On 1.7, could you try replacing your libxcb1 with the
follo
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
