-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
A buffer underflow vulnerability has been reported in file allowing for
the user-assisted execution of arbitrary code.
Solution: bump to =4.20 (current is 4.19).
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-1536
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Is there a method to detect errors in setup.hint's or setup.ini? As
setup.exe is choking on my setup.ini file, I could really use this.
Either that, or setup.exe (both stable and snapshot) doesn't like a
1.2MB setup.ini (created from 2283
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Brian Dessent wrote:
If you configure setup with --enable-inilint it should build the inilint
tool as a standalone app. I don't know if it has bitrotted to pieces or
not.
That's good to know. But trying to build inilint in the current
snapshot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Max Bowsher wrote:
Well, I got it to compile again, but I couldn't get it to link. It
seems that the setup classes have become interdependent to the point at
which it's no longer possible to call the parser standalone from the
rest of setup any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Brian Dessent wrote:
If you configure setup with --enable-inilint it should build the inilint
tool as a standalone app. I don't know if it has bitrotted to pieces or
not.
Does anybody have a working inilint, or better yet, can get it to
compile
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Brian Dessent wrote:
Is this the one on the Cygwin Ports site? If you give me a link to the
.ini file I'll try to debug setup.exe with it.
ftp://sunsite.dk/projects/cygwinports/setup-broken.ini.bz2
Yaakov
Cygwin Ports
-BEGIN PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Brian Dessent wrote:
Is this the one on the Cygwin Ports site? If you give me a link to the
.ini file I'll try to debug setup.exe with it.
Never mind; I finally found it the old fashioned way. Fortunately it
was near the beginning of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Two vulnerabilities have been discovered in Lighttpd, each allowing for
a Denial of Service.
Solution: upgrade to = 1.4.14 (current is 1.4.9)
More information:
http://security.gentoo.org/glsa/glsa-200705-07.xml
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
The next upstream release of coreutils will provide arch:
http://www.nabble.com/adding-%22arch%22-%28aka-uname--m%29-to-the-coreutils-
tf3871420.html
But this is currently provided by util-linux, so there will need to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
src_install_fini_hook() {
cd ${D}
mv usr/share/doc/${PN}/* usr/share/doc/${PN}-${PV}/
rmdir usr/share/doc/${PN}
}
I can either
(1) make a note in the README with a link to the cygport patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Reini Urban wrote:
I want to it take over from Gerrit.
Great, thank you.
But one thing, PLEASE give some heads-up before stabilizing 5.9/5.10?
That upgrade will require rebuilding all perl modules, and I've got over
100 of them.
Yaakov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jan Nieuwenhuizen wrote:
Can we have a freetype update, LilyPond 2.12 will require at least
2.1.10?
Done as announced. Thanks for the kind nudge.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
IIRC libexif was previously Gerrit's. Did someone else take this over
already? I have it already in Ports.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
There are no short-term plans to change the license of Cygwin, rather we
just wait until the OSI certifies the GPLv3 as open source license
according to the definitions. As Brian already noted, as soon as the
OSI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
Red Hat will not enforce the GPLv2-only state of
Cygwin on the back of GPLv3 packages. So, tar 1.18 can stay in the
distro if Eric trusts Red Hat not to sue him.
I'll trust Red Hat much more than other companies that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bo Peng wrote:
I maintain the cygwin port of lyx. Lyx will release 1.5.0 soon but
1.5.0 is based on qt4. I can compile lyx 1.5.0 with qt4 open source
myself, but I think it is impractical (or illegal) to distribute qt4
with lyx. Will there be a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna,
It's been a while since you last posted the list of package maintainers.
Would you be able to do so again?
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
Thank you, but... where are the packages? I don't see the updated
packages in release/exif.
Logged into sourceware, I see them in release/exif/libexif/. I haven't
checked the mirrors.
Yaakov
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
Sure. Only the list of unmaintained packages or the whole list?
The whole list, if you don't mind.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
I moved libexif10 to _obsolete.
Thank you.
Another question: The exif package was Gerrit's package, too, and
it's still on version 0.6.9. Any chance that you could take this one
over as well?
I'll take a look at it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yaakov (Cygwin Ports) wrote:
Corinna Vinschen wrote:
Another question: The exif package was Gerrit's package, too, and
it's still on version 0.6.9. Any chance that you could take this one
over as well?
I'll take a look at it tomorrow.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
FWIW, libpopt0 was, the last time I checked, linked to rpm and rpm had
become particularly hard to port to cygwin, also the last time I
checked.
I'm not sure what you mean by linked to rpm. While I'm aware that
popt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jari Aalto wrote:
Here is adoption of exif (Gerrit's)
1) The current upstream version is 0.6.15, please use that.
requires: cygwin cygexif cygintl8 cygpopt0 cygiconv2
This line is all wrong.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Attention gd maintainer: see attached.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGu+/0piWmPGlmQSMRCEOLAJ0aV8zJNDObmtECHr0KGOYfLv/etQCg51pq
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dr. Volker Zell wrote:
Ross Smith, writes:
I would like to adopt cppunit (orphaned at 1.9.14)
It would be nice if you could apply the following patch to cppunit.m4
1.12.0 builds OOTB nor does it need this patch. Maybe the OP should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dr. Volker Zell wrote:
/lib/X11/app-defaults directory looks strange. Other X packages install
to /etc/X11/app-defaults.
He needs to pass --with-app-defaults=/etc/X11/app-defaults to configure.
Yaakov
-BEGIN PGP SIGNATURE-
Version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
A directory traversal bug has been found in GNU tar.
Patch:
http://sources.gentoo.org/viewcvs.py/*checkout*/gentoo-x86/app-arch/tar/files/tar-1.15.1-alt-contains-dot-dot.patch
More information:
http://security.gentoo.org/glsa/glsa-200709-09.xml
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave Korn wrote:
On 19 September 2007 14:54, Corinna Vinschen wrote:
Here's the list. I take the opportunity to thank all Cygwin package
maintainers for their efforts. THANK YOU!
142 Yaakov S
standing ovation
Thanks, but please save
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
clamav maintainer,
It's time to upgrade clamav again; see attached.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Lapo,
AFAIK rsync is yours. Besides the update, the necessary patches are at:
http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-misc/rsync/files/rsync-2.6.9-stats-fix.patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The Perl Locale::gettext module wraps gettext() and company for perl,
allowing for localized perl programs.
This module is already in Debian etch, Ubuntu, Fedora 7, and SUSE 10.1.
I'm ITP-ing this now for the benefit of help2man, whose next
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Lapo,
Here's another buffer overflow, this time affecting lighttpd's mod_fastcgi.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Brian Dessent wrote:
However, when you re-run autoreconf --force --verbose --install it is
supposed to regenerate everything using the latest version, which means
this embedded automake-1.9 reference should . I'm not sure why in Ross'
case it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David Rothenberger wrote:
sdesc: PDF manipulation without Acrobat.
ldesc: Pdftk allows you to manipulate PDF easily and freely. It
does not require Acrobat.
category: Publishing
requires: cygwin libiconv2 zlib
Built from sources; tried a
install pkg
cp foo-0.9.4-1/patch/foo-0.9.4-1.src.patch .
cp -r foo-0.9.4-1/dist/foo/ ../../path/to/release/
cygport foo-0.9.4-1 finish
rm -f *.gz *.bz2
cvs rm foo-0.9.3-1.cygport foo-0.9.3-1.src.patch
cvs add foo-0.9.4-1.*
cvs ci
Yaakov
Cygwin Ports
-BEGIN PGP SIGNATURE-
Version: GnuPG
here?
IMO it should be added.
Yaakov
Cygwin Ports
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHXiIOpiWmPGlmQSMRCMPIAKDLUfGQBX38IjdrNkGh+BAsaToIAwCgiq7C
LMN3e/iq6vDPe4qcP46V9Y8=
=q98g
-END PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
Not a problem. Updated links:
GTG.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
On cygwin ports, Yaakov used prerequisites of perl-YAML,
perl-ExtUtils-CBuilder, and perl-ExtUtils-ParseXS. It would be nice to
also package those modules, but since perl-Module-Build comes with its own
subset of YAML support,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Lapo Luchini wrote:
PS: AFAIR the g-b-s' deps target lists them all, but cygport's dep
does not.
The g-b-s deps check was based on cygcheck, which shows the entire
dependency tree, where cygport uses objdump, which lists only those that
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
| Now that upstream coreutils 6.10 includes mktemp and arch as standard
| programs, should we obsolete the mktemp package and reduce the scope of
| the util-linux package? I won't promote coreutils 6.10 to current until
| we come
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nicholas Wourms wrote:
| While you are at it, if/when you do another release of util-linux,
| please update the cygport to install more.exe in /usr/bin, rather than
| /bin (util-linux arch.exe is also doing this, too). It's superficial,
| but it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yaakov (Cygwin Ports) wrote:
| Moving arch to coreutils makes sense to me, but let me look at
| util-linux 2.13 before I commit to anything.
OK, I've built 2.13; let's go with moving arch to coreutils.
Please give me a heads-up so that we can
/projects/cygwinports/release/util-linux/setup.hint
ftp://sunsite.dk/projects/cygwinports/release/util-linux/util-linux-2.13.1-1-src.tar.bz2
ftp://sunsite.dk/projects/cygwinports/release/util-linux/util-linux-2.13.1-1.tar.bz2
Yaakov
Cygwin Ports
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Kostya Altukhov wrote:
| requires: libncurses8 cygwin perl glib2 openssl libintl3 libiconv2 crypt
Why libintl3? The current version of gettext provides libintl8.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Please upload:
ftp://sunsite.dk/projects/cygwinports/release/cygport/cygport-0.3.8-1-src.tar.bz2
ftp://sunsite.dk/projects/cygwinports/release/cygport/cygport-0.3.8-1.tar.bz2
ftp://sunsite.dk/projects/cygwinports/release/cygport/setup.hint
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dr. Volker Zell wrote:
| util-linux-2.13.1-1 has the following two conflicting binaries:
Ooops. Why do these basic programs have to be provided by SO many
sources? (kill, for instance, is included with cygwin, is a bash
built-in, and can be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| Is there any reason why you don't reply to me on the cygwin-apps mailing
| list for a month now?
|
| What do I have to do to get your attention?
Send a message in a thread that I am actually following? :-)
I'm sorry, I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Volker Quetschke wrote:
| But I am open for suggestions. Does anyone have a better name? Or
| shall I just call it libMagick1 ?
+1
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dr. Volker Zell wrote:
| I would like to adopt and maintain the 'libXft/libXft2/libXft-devel'
packages from Harold Hunt.
Unfortunately this needs to be done together with the rest of modular
X11R7, because xft.pc requires xproto.pc and xrender.pc.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Reini,
My perl packages are now ready for 5.10, as soon as you're ready to
stabilize:
ftp://sunsite.dk/projects/cygwinports/release/help2man/help2man-1.36.4-2-src.tar.bz2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
There's been a LOT of back and forth over the 1.7 DLL and release
directory. Could someone (who actually knows what they're talking
about) please outline the *conclusion* of all that discussion, namely:
* where can a list of practical changes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
For those that may be interested in adoption, there are updated versions
of some of these now in Ports:
| * apr1 aprutil1
http://cygwin-ports.cvs.sourceforge.net/cygwin-ports/ports/libs/apr1/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave Korn wrote:
| Your sense of timing is perfect. I just spent an evening trying to
build
| this myself and finally got going with some half-working crudely
limping along
| static build...
It's been in Ports for over a year...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Warren Young wrote:
| Is there a way I can get Cygport to generate this patch for me? It
| seems like it should be able to take the source package, the README, and
| the setup.hint and generate the patch during the prep stage. I can't
| see how
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
| Not an error. dlopen'ed modules -- such as m4-2.0 and perhaps
| ImageMagick/GraphicsMagick -- might be named .dll but will live in
| /usr/lib/somewhere/
HUNDREDS of packages have dlopen'ed modules:
$ find /usr/lib -name
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Brian Dessent wrote:
| - setup.hint missing any of: sdesc, requires, category
Some -doc packages don't have any requires.
| - contains postinstall/preremove script without requiring bash (this
| matters for the order in which scripts are run)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
| - Existence of /usr/man, /usr/doc rather than /usr/share/man
/usr/share/doc.
Also /usr/info.
| - Missing /usr/share/doc/Cygwin/* (probably a warning).
Most of the time when building foo/libfooX/libfoo-devel packages,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Max Bowsher wrote:
| There is a copy of the libpng source code embedded in the doxygen source
| package. By default it builds a private copy of libpng and embeds it in
| the doxygen binaries. This seemed to me like needless duplication, so I
| made
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
| automake's dist-lzma already functions if you install lzma (I know,
| because I used it when creating m4 1.4.10b); automake uses 'tar | lzma'
| rather than 'tar --lzma'.
Furthermore, 'make distcheck' uses 'unlzma | tar'. Our
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Reini Urban wrote:
| Current changes from -3 to -4:
| No API changes, just one added DynaLoader.o in libperl and added one
| missing Win32CORE.a, so your packages will be fine.
I'll admit that I know nothing of Perl internals, but could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Reini Urban wrote:
| I tried both ways.
| The standard perl way with Win32CORE.a explicitly added to
| the linker line via $Config{static_ext}, and
Of course, but that makes things difficult when linking *other packages*
against libperl with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Reini Urban wrote:
| I see. To summarize:
| DynaLoader.o is contained in libperl.dll.a,
| Win32CORE.a not.
| ExtUtils::Embed ldopts is correct, but not libtool compatible.
So far, correct.
| Note: the next -e 'cmd' looks weird, but is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David Rothenberger wrote:
| 1.4.6 won't build with libtool 2.x.
Why not? I've been working with 2.2.2 since it's release, and just
about anything else builds with 2.x, even if originally packaged with 1.5.
Yaakov
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Reini Urban wrote:
| Yaakov already updated his cygports to this version.
| I need test versions be uploaded.
| I'll switch the hints then from test to curr.
|
| I only see perl-Tk, postgresql-perl, perl-Locale-gettext and
| perl-ExtUtils-*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| ICU is really a build requirement for perl6? If so, I have a hard time
| to require 5 votes for this package...
|
| Anyway, let's start here: +1
I will point out that the previous version of icu is in Debian stable:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nathan Thern wrote:
| I'm getting ready to ITP chicken scheme, but I would like to know what
| exactly does he mean by debian links?
URL on packages.debian.org showing that the package you ITP is in stable
(etch). A package which is in debian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nathan Thern wrote:
| OK, the chicken version in etch is 2.3, and the version I want to ITP
| is 3.3. Does that matter?
Generally it hasn't, assuming that 2.3 and 3.3 are basically the same
animal. :-)
Yaakov
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| again I would like to encourage the Cygwin maintainers, to try the new
| Cygwin 1.7.0 release and to look for problems in their packages which
| might be a result of the fairly massive changes in Cygwin 1.7. I
| attached
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| When 1.7 goes gold, the idea is to install over an 1.5 install. Or not.
| It's the choice of the user. Installing over 1.5 is supported by the
| base-cygwin package, which is supposed to convert the registry mount
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
As we start preparing for 1.7, I know that until now the focus has been
on the development of Cygwin itself. I'll admit that I know little
about Cygwin's internals, and hence have contributed very little to the
DLL itself, but I do very much
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I would like to make some proposals as to setting up the development
toolchain for 1.7:
1) binutils
Thanks to cgf, we've got a current binutils available now; I'm not sure
if binutils itself benefits from 1.7 (save the long path handling).
There
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| Honestly, I don't know. Maybe it isn't. But so far I'm still thinking
| that a parallel 1.7 install should only be a temporary solution for
| developers and maintainers. It's not something I would like to drag
| on for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| I'm not sure if there's really a big difference between these two points.
| Since we're using two different installation directories, we can get rid
| of old cruft, if we just look carefully what's still used and what not.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
| It seems like maybe another change to setup.exe would be in order here
| or maybe there could be a base package which did any cleanup required to
| purge unneeded packages.
Could setup-1.7 know if the last installation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Our X11R6 hasn't been updated in almost three years now. Since then,
X.org has moved to a modular R7 where each library, executable, font
set, etc. have their own autotooled package.
It seems that our X11 is used for two different things: 1) to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| are you still with us? There was a joe problem reported on the main
| list two weeks ago. It looks like you're still not subscribed to the
| cygwin mailing list. How do you think you can help users and find out
| about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| What if we add an obsoletes: line to setup.{ini,hint}?
|
| The idea is that you don't have to provide empty replacement packages
| for the old packages anymore, and setup removes all packages noted in
| the obsoletes: line
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave Korn wrote:
| I've got libgcc shared and working fine and correctly, either with a
| separate static libgcc_eh, or with it shared, although that's only an
option
| if you also have shared libstdc++.
|
| Getting libstdc++ to work shared is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| - Creating filenames with special DOS characters '', '*', ':', '',
| '', '|' is supported.
|
| - Creating files with special DOS device filename components (aux,
| nul, prn) is supported.
|
| - File name are case
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| setup is a Win32 application. It won't know about this. Thou shalt
| not create packages which rely on case-sensitivity as part of the
| net distro.
That's what I thought. So while managed mounts will no longer be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| Illegal? The only illegal chars are slash and backslash, even on
| case-insensitive mounts. Does it really occur often that you have two
| filenames in the same dir only differing by case?
For Cygwin I understand that,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Having just used cvs2svn to successfully migrate Ports, I think it would
make a good addition to the distro.
An older version is currently in Debian stable[1]; this version is in
testing[2].
[1] http://packages.debian.org/etch/cvs2svn
[2]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| are you still with us? There was a joe problem reported on the main
| list two weeks ago.
Jari,
There are also outstanding security issues with three of your packages:
mercurial: Directory traversal (CVE-2008-2942)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David Rothenberger wrote:
| I'm ITP'ing this in preparation for packaging subversion-1.5.1.
|
| serf[1] is included in Debian testing[2], but I could not find it in
| Fedora or SuSE.
Probably because subversion-1.5 itself is only in testing.
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Almost six weeks ago, Corinna Vinschen wrote:
| I have no idea. 7.2a is the first beta. But vim is otherwise very
| stable so I don't expect more than another beta. If I might venture a
| guess, I'd say, (much) less than 4 weeks.
Or maybe not.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David Rothenberger wrote:
| I'm confused by this. You're suggesting that I have the following?
|
| * serf0: empty
| * libserf0_0: DLL and docs
| * libserf0-devel: headers and link libraries
|
| Why do I need serf0?
Because the package needs a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David Rothenberger wrote:
| I've updated the packaging to address Yaakov's suggestions, although
| I used serf as the package name for the empty (source) package
| instead of serf0.
|
| Updated hints and files are below. I think I have two votes to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| Packaging looks ok to me, but why the dependency to rcs?!?
It was based on the Gentoo ebuild's deps, but digging deeper, it seems
as with at least this version it's optional. I'll remove it before
moving it into release.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| Now that 7.2 is final we can put this plan into realization.
Thanks, here you are:
http://ftp.sunsite.dk/projects/cygwinports/release/GNOME/gvim/gvim-7.2-1-src.tar.bz2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| Perhaps I screwed something up with my patches which worked before,
| but it worked fine for me, so I don't know. Please give it a try
| and report back.
Thanks!
I haven't tested it extensively, but I was able to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
A few ideas about package documentation for 1.7:
1) Info pages
Per a recent discussion on the main list, GNU info 'dir' will be managed
solely by _update-info-dir. Packagers should no longer use postinstall
scripts for this purpose; the next
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
| Any reason this version insists on maximizing itself when going to the
| package selection screen, rather than remaining at the size of the
| previous screen?
Because someone programmed it that way. :-)
For the record, while
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Before packagers start focusing on 1.7, it appears that we still have a
number of security updates required for the 1.5 tree:
By maintainer
=
ORPAHNED: apache2
Jari Aalto: mercurial, pngcrush, python-paramiko
Lapo Luchini: lighttpd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
I hate to suggest another mailing list but I wonder if we should have
another unarchived, closed list for discussing security issues. The
recent setup.exe problem got me thinking that we might need something
like this.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
Personally I'm kind of not interested to go this road. If I learn about
a problem in an upstream package, I update. If anybody else want's to
take over responsibility for security problems, I certainly don't stand
in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
upset: *** warning package gnome-common requires non-existent package
gnome-doc-utils
upset: *** warning package gnome-common requires non-existent package
gnome-doc-utils
This is mine; gnome-doc-utils isn't in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
What if we add an obsoletes: line to setup.{ini,hint}?
The idea is that you don't have to provide empty replacement packages
for the old packages anymore, and setup removes all packages noted in
the obsoletes: line
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jari Aalto wrote:
I have no objection of dropping Cygwin 'lzma' package if you take over
the maintenance. The SDK + Debian patches (GNU --long option interface)
is pain to maintain because the SDK uses windows style CRLF.
+1. Replacing the SDK
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
One of these days, I'll learn to check cygwin-ports before porting a new
package.
I do make the repository available for a reason, you know. :-)
http://cygwin.cwilson.fastmail.fm/ITP/lzma-utils-4.32.7-1-src.tar.bz2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
Libarchive is a programming library that can create and read several
different streaming archive formats, including most popular tar
variants and several cpio formats. It can also write shar archives and
read ISO9660 CDROM
1 - 100 of 153 matches
Mail list logo
