On Thu, 2019-06-27 at 17:47 +, Stevenson, Bob [US] (MS) wrote:
> Are there plans to make the postgresql 11.4 packages available to the Cygwin
> community?
https://cygwin.com/faq/faq.html#faq.using.old-packages
--
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ:
Cygwin/X users,
Last fall, with Jon's technical assistance, I took on updating the
long-unmaintained Cygwin/X and released X11R7.4. Since then we have
released over 30 package updated, including six patch revisions to the
server. Work on preparing X.Org Server 1.6 and GNOME 2.26 for Cygwin
1.7
FYI, the power supply on my development computer went. I'll be AFK
until I can get a replacement, hopefully sometime next week.
Yaakov
Cygwin/X
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
Ah, yes, much better way of fixing the makefile, thank you.
When you deal with as many packages as I have, you get to know autotools
really well. :-)
Tested this with a few more remote GLX demo programs and clients, seems
to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John Emmas wrote:
Oops, I meant to ask another question (almost a variation on the same
theme). Does Cygwin itself (or more correctly, its linker) link
automatically to any of the standard Windows libs (such as kernel32.lib,
user32.lib etc).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dr. Volker Zell wrote:
09:40 PM [531] cat /usr/lib/X11/proxymngr/pmconfig | grep /X11
lbx managed /usr/X11R6/bin/lbxproxy
lbxproxy is obsolete and long gone, so this is harmless.
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dr. Volker Zell wrote:
Actually only FONTDIR and ENCODINGSDIR are fixed.
My true feelings about imake are simply not printable. What other
package this size would take 8 releases to (maybe) get right?
At least cygport takes care of /usr/man -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Phan, Linh H wrote:
I went to setup-1.7.exe to get the libGLw-devel. setup put libGLw.dll in
/usr/lib/libGLw.dll.a but it also put all these files:
in /usr/bin and removed it from my /usr/X11R6/bin. It also removed alot of
other
files from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dr. Volker Zell wrote:
When generating Makefiles with latest xmkmf the resulting Makefiles have
some bogus entries.
Fixed in xorg-cf-files-1.0.2-7. But I'm curious, what are you building
that still uses imake so extensively?
Yaakov
Cygwin/X
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net distribution:
*** xorg-cf-files-1.0.2-7
This release fixes the definitions of MANPATH, FONTDIR, and ENCODINGSDIR.
Yaakov
Cygwin/X
DOWNLOAD:
=
Note that downloads from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dr. Volker Zell wrote:
motif-config references -L/usr/X11R6/lib in latest libXm-devel-0.95.0-2
This is actually hard-coded in the source, not because it was using that
directory (I zapped my /usr/X11R6 before the transition). Since
everything has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon,
Looking further into Xinerama, I think I brushed it off too early. It
is *very* widely supported[1], and while XRandR is supposed to replace
it, actual implementation and usage may be some time off.
I also think that there may be some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dr. Volker Zell,
A few suggestions for the ghostscript package:
1) With the X11 transition, is the native/x11 split really necessary
anymore? While gs-x11 adds several additional library dependencies, you
wouldn't be pulling in as much as you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net distribution:
*** xscope-1.1-2
This package has been rebuilt with the newest xtrans to silence the
messages about /tmp/.X11-unix creation and ownership.
Yaakov
Cygwin/X
DOWNLOAD:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
Works for me.
Note that you don't actually need to the formatting of the log file name
yourself, LogInit() already has code to replace %s in the log file name with
the display name.
I was aware of that, but it wasn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Florent Fievez wrote:
I have a problem running new X server 1.5.3 with openGL. Since this
update, X crash when launching an OpenGL client from SunOS server.
Since the application we are developing use OpenGL, it's a big problem
for me (I have to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net distribution:
*** libXaw6-1.0.5-1
*** libXaw7-1.0.5-1
*** libXaw-devel-1.0.5-1
This is the latest upstream release.
Even though all references to the xaw.m4 macro has been removed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net distribution:
*** xtrans-1.2.2-3
I added a patch to avoid the bogus error euid != 0, directory
/tmp/.X11-unix will not be created from the X servers, once they are
rebuilt.
Yaakov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net distribution:
*** xorg-server-1.5.3-3
These are the changes in this release:
* Log changes:
- - In addition to the XWin logs now being found in /var/log (as of the
last release), now a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon,
Following up on our discussion about multiwindow not honouring
_NET_WM_STATE_SKIP_TASKBAR. The attached patch was what I had in mind
but it has no effect. I'm posting this now to at least start the
discussion.
You may wish to refer to the
type system to build documentation from the code and its
comments, but I'm not aware of any such system for bash. Perhaps there
is, I just don't know.
And maybe some helper is needed to detect changes in previous .list files.
Huh?
Yaakov
Cygwin Ports
-BEGIN PGP SIGNATURE-
Version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Angelo Graziosi wrote:
I have seen that after the release of X11R7, many problems are partially
resolved by rebasing. Some time ago, I remember that on cigwin-apps list
there was the suggestion that the package maintainer should build their
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been added to the Cygwin net release:
+++ nas-1.9.1-2
+++ libaudio2-1.9.1-2
+++ libaudio-devel-1.9.1-2
The Network Audio System is a network-transparent, client/server audio
system based on X11.
Yaakov
Cygwin/X
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Back, Michael wrote:
I solved this one by guessing and loading the right font pack...
Which font pack contains this one?:
app-image-san-004:station: Warning: Can't chmod /dev/console
XView warning: Cannot load font set
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
[EMAIL PROTECTED] wrote:
How's that? What, exactly, does libtool have to do with cygwin's fork
emulation code?
The closest libtool comes to this issue is the fact that it
automatically turns on enable-auto-image-base -- which should help
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jonathan Johansen wrote:
I've tried installing the Cygwin X11 server to try to be able to run an
X app, but the cygwin installation packages were completely different to
the ones mentioned on the website and in the documentation. I had to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
Wouldn't it make sense to create a symlink /usr/X11R6/bin/xauth
additionally for backward compatibility as it exists on some Linux
systems? Openssh might not be the only affected application.
I'm not about to rebuild
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
I'm not talking about providing symlinks to all binaries in
/usr/X11R6/bin, just xauth. It's the one serious X application called
from other applications for authentication purposes. The current
transition method breaks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Voelker, Bernhard wrote:
my openbox window manager is not usable anymore: the menues, window
titles etc. are not rendered correctly and can't be read anymore.
Is openbox supported with the new xorg version?
Any other ideas?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Scott Fordin wrote:
Just so you all know, it looks like installing the Xorg-related
packages on my Solaris 10 machine (not difficult using the Sun
Update Manager tool (/bin/updatemanager)) did the trick. No more
X resource crashes on things like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
Please find at the URL below a small update to the xorg server patch
set.
Committed; could you please svn up and test? I also changed the log
location patch to use a separate log for each display (e.g. XWin.0.log),
as is done
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark Rousell wrote:
Is there a dig tool for Cygwin? It's usually part of Bind I think, but I
can't see a Bind package for Cygwin.
I know I can use nslookup but I'm just more used to dig.
Cygwin Ports provides a bind package.
Yaakov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mike Conley wrote:
Hi. After upgrading my X server, I find that X programs ignore most keyboard
input entirely, with the exception of the numeric keypad. I tried again with
a
fresh install and got the same results. Log file (generated by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark A. Ziesemer wrote:
I don't have a multihead setup, so I'm unable to test any of this.
I'm sorry. Do you just not have one, or you don't want one? :-)
http://cygwin.com/donations.html :-)
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
http://cygwin.com/acronyms/#PCYMTWLL !!
Uh Huh wrote:
I think the problem lies with the Windows-style window manager xwinwm?
http://cygwin.com/ml/cygwin-xfree-announce/2008-11/msg0.html
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark A. Ziesemer wrote:
However, it seems that some part of this (the XWin window manager?) is getting
confused by the multi-monitor window geometry. I have 2 monitors, 1280x1024,
with the primary on the right and the secondary on the left.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Cesar Strauss wrote:
There is a GTK application (gschem from www.geda.seul.org) that saves
the position of its sub-dialogs when they close, so they reopen at the
same place.
Up to now, on Cygwin/X, this didn't always work well: in multi-window
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
For all those having issues with untrusted X11 forwarding (IOW ssh -X):
1) First, please (re-)read this:
http://x.cygwin.com/docs/faq/cygwin-x-faq.html#remote
2) I can confirm that ssh is hardcoded to look for xauth in
/usr/X11R6/bin. The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
I was actually thinking the other day about how the bit of code which does
this might be wrong. :S
I suspect the problem is that when you have the secondary to the left of the
primary, the windows on that monitor have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net distribution:
*** libXi6-1.1.4-1
*** libXi-devel-1.1.4-1
This is the latest upstream bugfix release.
Yaakov
Cygwin/X
DOWNLOAD:
=
Note that downloads from sources.redhat.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ian Puleston wrote:
OK, I've now removed the /usr/lib/X11 link as per the notes and then ran
setup to reinstall everything that I had installed in the x11 section of
setup, plus rxvt. It re-created a /usr/lib/X11 directory containing just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna,
We're getting a number of bug reports that ssh has a hardcoded path to
/usr/X11R6/bin/xauth. As part of the X11 transition, xauth was moved to
/usr/bin, so ssh claims not to find it. A strings check on ssh does
indeed show such a path as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
The gc package at least might be useful for others as well.
If by gc you mean the Boehm-Demers-Weiser garbage collector library,
it's already packaged as libgc.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
The Bitstream Vera TTF font family has gone AWOL in the upgrade to X.Org R7.4
(it was previously contained in the xorg-x11-fscl package)
Which makes me wonder if there are other such cases...
If possible, the stub
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net distribution:
*** xinit-1.1.0-3
This release adds a Windows Start Menu shortcut to the startxwin script,
making it easier to launch XWin and an xterm.
Yaakov
Cygwin/X
DOWNLOAD:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net distribution:
*** xorg-server-1.5.3-2
These are the changes in this release:
* Additional fixes to multiwindow mode: Qt4 program icons display
correctly; window geometry take window
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ken Brown wrote:
gcc -o xdvi-xaw.exe browser.o dl_list.o dvi-draw.o dvi-init.o dvisel.o
encodings.o events.o exit-handlers.o filehist.o font-open.o gf.o
string_list.o hypertex.o image-magick.o main.o mime.o my-snprintf.o
my-vsnprintf.o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
Hmmm it seems that ssh needs to run xauth to do connection forwarding, but
is still trying to use /usr/X11R6/bin/xauth, rather than /usr/bin/xauth (and
prints a slightly misleading message in this case)
In which case,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
I hope I catched everything. Would you mind to take a quick look?
lesstif was broken up, adding libXm2 and libXm-devel. AFAICS that's
everything.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Albert van der Velde wrote:
Could you help me with the next problem I'm facing. I use Cygwin within
our company to automate some tasks on a Windows server. Thefor I
installed inetutils and use rlogind and rshd to login without password.
On Unix
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net distribution:
*** xtrans-1.2.2-2
I added a patch to silence the bogus warning Owner of /tmp/.X11-unix
should be set to root from the X servers, once they are rebuilt.
Yaakov
Cygwin/X
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
bali asur wrote:
Fatal server error:
Can't read lock file /tmp/.X0-lock
Stale lock?
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
http://cygwin.com/acronyms/#PCYMTWLL !!
Joseph Ess wrote:
The upgrade yesterday did bad things to Openbox. See this screenshot for
reference:
http://w3.gwis.com/~slomojoe/images/openboxscreenshot.jpg
Ouch.
Any advice for getting openbox
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dr. Volker Zell wrote:
I'm in the process of packaging Xaw3D. Your latest patch to
xorg-xf-files works by the way.
Glad to hear it.
I have a question regarding packaging library only packages like for
example your libXmu package.
The setup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
Sadly, I have no theory about how this could be happening, except perhaps it
could be related to 'unusual' permissions on /tmp which could somehow let you
create but not rename a file (so the output of 'ls -al /tmp' might
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
Works for me.
It doesn't seem to be possible to build Xwin using just the stuff in the
cygwin distro: Kdrive's kxv.c requires headers from videoproto. I guess this
is failing to honour a configure check properly somewhere.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Lassauge wrote:
Rebuilt xman package because a problem remains for /etc/X11/app-defaults/Xman,
as Windows is not uppercase aware xman.exe gets installed as
etc/X11/app-defaults/Xman.exe instead of Xman-*.ad (you can verify in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
Ok, my archaeological investigations in this area have revealed that this
locking code probably wasn't enabled in 6.8.99. I don't think it is actually
giving any benefit, since we also have a native named mutex is used in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
Actually, this seems to be more complex than I first thought. Running any of
the mesa demo programs works fine locally, but causes a server segfault when I
do it over ssh to a linux box
Let me give you some background.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
(Resending here because it wasn't echoed at the time and obviously a lot
of people haven't seen it.)
Cygwin/X has been updated to X.Org X11R7.4.
WHAT'S NEW IN X11R7.4?
==
* Each program, library, set of headers, set of fonts,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net distribution:
*** xman-1.0.3-3
This release fixes the installation of the app-defaults file and groff
formatting handling, and adds man.conf support.
Yaakov
Cygwin/X
DOWNLOAD:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
Hmm.. thinking about this, perhaps the best thing to do is create a new
shortcut which links to startxwin.bat, so that the end-user at least has some
chance of a discoverable means of launching the server which should work.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been added to the Cygwin net release:
+++ giflib-4.1.6-2
+++ libgif4-4.1.6-2
+++ libgif-devel-4.1.6-2
*** libungif4-4.1.4-2
+++ libungif-devel-4.1.4-2
All known LZW (GIF compression) patents have expired, so there is no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
I'm trying to keep track of the maintainership changes due to the
new X.Org stuff but I'm somewhat overwhelmed by the mere number.
:-)
I assume the entire X.Org subdir and all of its packages are yours
right now. Are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Maarten Vanneste wrote:
Thanks for your quick reply and suggestions. The nedit suggestion does
the trick. I notice that the fonts are a bit messed up, as the text
appears very big (much larger than the original setting).
The keyboard issue is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
bali asur wrote:
Noticing Yahov's e-mail about the new X11 releases, I have
been attempting to follow Yakov's upgrade path instructions.
The instruction seem to imply that the following packages
must be installed.
The instructions tell you that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dr. Volker Zell wrote:
When generating the Makefile with xmkmf from latest X11R7.4
for Xaw3d I get the following lines in the Makefile
SOXAWREV = SharedXawRev
DEPXAWLIB =
XAWLIB = -lXaw
and the following with the old release.
SOXAWREV
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Please be aware that announcements on cygwin-xfree-announce are not
currently being echoed to this list as they were in the past. We are
working on automating this, but in the meantime please subscribe to the
- -announce list separately if you want
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jan Nieuwenhuizen wrote:
Ouch. Sorry for the late response, please adopt and go ahead.
No problem. Thanks,
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I propose to add giflib to (mostly) replace libungif (which is currently
mine). The latter is no longer maintained because there are no
remaining legal impediments to using giflib.
The only difference between these packages is the name of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package maintainers,
Modular X11 has been pushed into the distro. I need all maintainers of
X11-related packages to update their installation and test their
packages to make sure they still work correctly.
Yaakov (Cygwin Ports) wrote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yaakov (Cygwin Ports) wrote:
4) An announcement will be made on cygwin-xfree-announce@ with all the
details.
I sent an announcement this morning, and it showed on
cygwin-xfree-announce@, but it wasn't echoed to [EMAIL PROTECTED] The last
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
Can you hold off uploading until X11 is in place (hopefully by
tomorrow)? I'm having enough trouble keeping the staging area in sync
with release as it is.
Sure.
X11 is in place now, so whenever you're ready.
Yaakov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David Rothenberger wrote:
I start the X server in multiwindow mode using /bin/startxwin.sh. If I
then type
xterm -geometry +0+0
into the visible XTerm, the new XTerm shows up in the top-left of the
screen, but the title bar is off the top
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
*** fontconfig-2.6.0-1
*** libfontconfig1-2.6.0-1
*** libfontconfig-devel-2.6.0-1
This is an update to the latest upstream release, and has been
configured to use the new modular
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
*** gnome-common-2.24.0-1
This is an update to for GNOME 2.24.
Yaakov
DOWNLOAD:
=
Note that downloads from sources.redhat.com (aka cygwin.com) aren't
allowed due to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
*** intltool-0.40.5-1
This is an update for GNOME 2.24.
Yaakov
DOWNLOAD:
=
Note that downloads from sources.redhat.com (aka cygwin.com) aren't
allowed due to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
*** libexif12-0.6.17-1
*** libexif-devel-0.6.17-1
This is an update to the latest upstream release.
Yaakov
DOWNLOAD:
=
Note that downloads from sources.redhat.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
*** netpbm-10.44.2-1
*** netpbm-doc-10.44.2-1
*** libnetpbm10-10.44.2-1
*** libnetpbm-devel-10.44.2-1
This is an update to the latest upstream release, built against X11R7.4.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
*** perl-ExtUtils-PkgConfig-1.12-1
This is an update to the latest upstream release.
Yaakov
DOWNLOAD:
=
Note that downloads from sources.redhat.com (aka cygwin.com)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Larry Adams wrote:
pkg-config-0.23.tar.gz - No sure.
Yes, the distro provides pkg-config-0.23a.
pixman-0.10.0.tar.gz - Not sure
Just added as part of the X11R7.4 release. Look for libpixman1-devel in
the X11 category.
cairo-1.6.4.tar.gz -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
*** fontconfig-2.6.0-1
*** libfontconfig1-2.6.0-1
*** libfontconfig-devel-2.6.0-1
This is an update to the latest upstream release, and has been
configured to use the new modular
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
*** gnome-common-2.24.0-1
This is an update to for GNOME 2.24.
Yaakov
DOWNLOAD:
=
Note that downloads from sources.redhat.com (aka cygwin.com) aren't
allowed due to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
*** intltool-0.40.5-1
This is an update for GNOME 2.24.
Yaakov
DOWNLOAD:
=
Note that downloads from sources.redhat.com (aka cygwin.com) aren't
allowed due to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
*** libexif12-0.6.17-1
*** libexif-devel-0.6.17-1
This is an update to the latest upstream release.
Yaakov
DOWNLOAD:
=
Note that downloads from sources.redhat.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
*** netpbm-10.44.2-1
*** netpbm-doc-10.44.2-1
*** libnetpbm10-10.44.2-1
*** libnetpbm-devel-10.44.2-1
This is an update to the latest upstream release, built against X11R7.4.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
upset: *** setup-2.ini: warning - package ORBit2-devel requires non-existent
package minires-devel
upset: *** setup-2.ini: warning - package atk requires non-existent package
glib2-runtime
upset: *** setup-2.ini:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
The mktemp package is obsolete. It comes from coreutils these days.
Then the transition wasn't correctly handled, because the latest
mktemp-1.5-4 is a real package. An empty 1.5-5 package should have been
created at the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
I'm on it.
Can you hold off uploading until X11 is in place (hopefully by
tomorrow)? I'm having enough trouble keeping the staging area in sync
with release as it is.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Reini Urban wrote:
The cygwin clamav packages (Clam AntiVirus - GPL anti-virus toolkit)
has been updated to 0.94-1
Reini,
libclamav.la is broken again[1][2], this time with a fake libbz2.la.
PLEASE, get rid of all the fake .la files from your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
Even the rollup patch?
ftp://invisible-island.net/${PN}/${PV}/${PN}-${PV}-20060909-patch.sh.bz2
Yes.
It only breaks the ABI (B?) if you do it the way you suggested:
http://cygwin.com/ml/cygwin/2008-05/msg00038.html
Yes,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
They were called rollup patches. T.E.D. releases patches roughly every
week, and then every month (or two, or three), he combines all patches
dating back to an official release into a rollup patch -- and these
rollup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andrew Schulman wrote:
Several of my packages require multiple patches to compile and run properly in
Cygwin. Instead of maintaining them all together as One Big Patch, I find it
easier to manage them as individual, discrete patch files, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
Okay, so these are (mostly) your own custom patches needed to port the
code to cygwin, and not official patches from somewhere else, like
1) bugfixes taken wholesale from another distro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yaakov (Cygwin Ports) wrote:
Good; there are no other messages from upset in the staging area. All I
need then is permission to adopt fontconfig and lesstif.
Just waiting for fontconfig now. ITA sent five days ago and no response
from Jan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ralph Hempel wrote:
Hmmm - I never thought to look there, apparently you've
done a lot of the work already :-)
And looking at the ports list, it seems that all the libs I
was hoping to port over are already there!
I'm not exactly sure what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
http://cygwin.com/acronyms/#PCYMTWLL
André Bleau wrote:
The applications using freeglut can be compiled and linked without problems,
but I now realize that native GLUT applications cannot be compiled
correctly if the libglut-devel package is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André Bleau wrote:
This cannot work as the order of system directories cannot be changed by -I.
Oops.
What could be done is that I update the opengl package with an additionnal
directory:
/usr/include/opengl that will contain only a symbolic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
Incidentally, I set up a scratch area:
/sourceware/snapshot-tmp/yselkowitz
Thanks for setting up the staging area. Looks like everything is ready
now, EXCEPT:
1) I get PROBLEMS WITH errors on the new xorg-x11-* empty
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I hereboy propose to take maintainership of Cygwin/X.
It was over two years ago that I started to work on the (then brand-new)
modular X11, and it was indeed in consideration of the sheer number of
packages involved that I created cygport. Both
1 - 100 of 492 matches
Mail list logo
