On Wed, 2014-08-13 at 20:12 +0100, Adam Dinwoodie wrote:
On Mon, Aug 04, 2014 at 10:41:06PM +0100, Adam Dinwoodie wrote:
Just to update folk: I've bumped to v2.0.4, and everything's working a
lot more nicely. I've managed CVS imports using both 32-bit and 64-bit,
and I'm in the process of
Corinna Vinschen wrote:
Hi Daniel,
On Aug 14 21:05, D. Boland wrote:
Hi group,
I intend to adopt the Cygwin package for the procmail program, version
3.22. The
original maintainer, Jason Tishler has given me permission to do so.
The difference with previous Cygwin releases is
On Thu, Aug 14, 2014 at 10:24:58PM -0600, Eric Blake wrote:
On 08/13/2014 01:37 PM, Eric Blake wrote:
Packaging isn't quite right. After unpacking the -src tarball, I see a
file git-2.0.4-1.src.patch, with contents:
Binary files origsrc/git/t/lib-gpg/random_seed and
On Fri, Aug 15, 2014 at 09:24:52AM +0100, Adam Dinwoodie wrote:
snip
Beware the To/Cc headers in that last reply. I'm not sure how I maanged
to screw them up like that. I'm going to blame the fact that I'm still
trying to get used to Mutt's interface.
On Aug 15 09:53, D. Boland wrote:
Corinna Vinschen wrote:
Hi Daniel,
On Aug 14 21:05, D. Boland wrote:
Hi group,
I intend to adopt the Cygwin package for the procmail program, version
3.22. The
original maintainer, Jason Tishler has given me permission to do so.
On Aug 14 23:29, Marco Atzeri wrote:
On 14/08/2014 22:51, Corinna Vinschen wrote:
On Aug 14 22:28, Marco Atzeri wrote:
The build methods is maintainer choice.
I use cygport but I don't see a reason to mandate it.
Tiny correction: New packages should use cygport. We should really all
On 14/08/2014 22:47, Achim Gratz wrote:
Marco Atzeri writes:
Ultimately the need for this file should go away except for
bootstrapping a new maintainer.
I guess we will always need a maintainer database
I plan to produce a list of sources by arch as by product of
the current analysis.
Hi Corinna,
Corinna Vinschen wrote:
Works for me. Did you forget the `prep' stage?
$ cygport procmail.cygport prep
Preparing procmail-3.22-13.x86_64
*** Info: gnupg must be installed in order to check signatures.
Unpacking source procmail-3.22.tar.gz
*** Info: applying
On Tue, 2014-08-12 at 10:59 +0200, Corinna Vinschen wrote:
On Aug 12 09:45, Thomas Wolff wrote:
While revising the upload structure, please consider folding out the source
package (e.g. into no-arch/ or src/) because it's not a convincing burden to
have to upload the same package twice.
Hello!
Sorry for perhaps stupid question. But i cannot correctly upload my
new package. I have read both instructions on the web and recent
emails about flat layout, and did the following:
1. Created directory /x86_64/release/onc-rpc-devel
2. Placed my package (source, binary
Pavel Fedin writes:
Today in the afternoon i have checked x86-64 setup, no new package
appeared. Now i'm looking at the SFTP, onc-rpc-devel directory is
still there, but is empty. !ready file is also deleted.
You didn't do anything wrong and the package has been correctly uploaded
to
On 15/08/2014 21:11, Achim Gratz wrote:
Pavel Fedin writes:
Today in the afternoon i have checked x86-64 setup, no new package
appeared. Now i'm looking at the SFTP, onc-rpc-devel directory is
still there, but is empty. !ready file is also deleted.
You didn't do anything wrong and
On Aug 15 17:53, D. Boland wrote:
Hi Corinna,
Corinna Vinschen wrote:
Works for me. Did you forget the `prep' stage?
$ cygport procmail.cygport prep
Preparing procmail-3.22-13.x86_64
*** Info: gnupg must be installed in order to check signatures.
Unpacking source
On 15/08/2014 21:39, Pavel Fedin wrote:
Hello, Marco.
Friday, August 15, 2014, 23:22:49 you wrote:
Pavel,
the fastest way to check is:
https://cygwin.com/packages/x86_64/onc-rpc-devel/
Thank you, i'll know that.
By the way, package list at https://cygwin.com/packages/ also doesn't
On Aug 15 12:21, Yaakov Selkowitz wrote:
On Tue, 2014-08-12 at 10:59 +0200, Corinna Vinschen wrote:
On Aug 12 09:45, Thomas Wolff wrote:
While revising the upload structure, please consider folding out the
source
package (e.g. into no-arch/ or src/) because it's not a convincing
On Fri, 2014-08-15 at 22:11 +0200, Corinna Vinschen wrote:
On Aug 15 12:21, Yaakov Selkowitz wrote:
However, what I did suggest earlier was to have a separate
noarch/release hierarchy for entirely noarch packages, which would
prevent having to upload noarch twice:
Achim Gratz writes:
Achim Gratz writes:
1) ITA perl_vendor and provide an umbrella plus all dependencies for
perl-5.14.2. I'd use current versions for these, not the original ones
from perl_vendor.
If you want to test this, please use http://cygwin.stromeko.net as your
only or additional
Yaakov Selkowitz writes:
A few things would have to be changed on the infrastructure side, but I
think it's doable. The biggest issue may be that maintainers need to
mark their packages ARCH=noarch as appropriate, and then remember to
upload to a separate directory. The latter could be
On Fri, 2014-08-15 at 22:46 +0200, Achim Gratz wrote:
That only really works for pure noarch packages of which there aren't
all that many.
There are more than you think. In Ports, over 46% of the source
packages are completely noarch.
As you say, this is doable today with not too much
On Fri, 2014-08-15 at 22:38 +0200, Achim Gratz wrote:
Achim Gratz writes:
Achim Gratz writes:
1) ITA perl_vendor and provide an umbrella plus all dependencies for
perl-5.14.2. I'd use current versions for these, not the original ones
from perl_vendor.
If you want to test this, please
On 15/08/14 22:15, Yaakov Selkowitz wrote:
Where did we leave off wrt breaking out
perl_vendor?
Back in April, Reini expressed a desire to keep perl_vendor, claiming
that it is the easiest solution for both user and maintainer [1].
Whilst there are some of us who might question this, Reini
On Fri, 2014-08-15 at 23:00 +0100, David Stacey wrote:
On 15/08/14 22:15, Yaakov Selkowitz wrote:
Where did we leave off wrt breaking out
perl_vendor?
Back in April, Reini expressed a desire to keep perl_vendor, claiming
that it is the easiest solution for both user and maintainer [1].
CVSROOT:/cvs/src
Module name:src
Changes by: cori...@sourceware.org 2014-08-15 21:21:59
Modified files:
winsup/cygwin : ChangeLog winsup.h configure configure.ac
Log message:
* winsup.h (_GNU_SOURCE): Define. Explain why.
* configure.ac: Convert to new
CVSROOT:/cvs/src
Module name:src
Changes by: cori...@sourceware.org 2014-08-15 21:23:11
Modified files:
winsup/doc : ChangeLog configure configure.ac
Log message:
* configure.ac: Convert to new AC_INIT style.
* configure: Regenerate.
Patches:
CVSROOT:/cvs/src
Module name:src
Changes by: cori...@sourceware.org 2014-08-15 21:23:45
Modified files:
winsup/lsaauth : ChangeLog configure configure.ac
Log message:
* configure.ac: Convert to new AC_INIT style.
* configure: Regenerate.
Patches:
CVSROOT:/cvs/src
Module name:src
Changes by: cori...@sourceware.org 2014-08-15 21:24:36
Modified files:
winsup/utils : ChangeLog configure configure.ac
Log message:
* configure.ac: Convert to new AC_INIT style.
* configure: Regenerate.
Patches:
Achim Gratz Stromeko at NexGo.DE writes:
For building 32bit packages I've set up an additional installation on the
same server. To use it from the outside (like) I'm trying to configure a
second sshd on the server. So I've installed a cygserver23 and sshd32
service with otherwise identical
The following packages have been added or updated for both arches:
* perl-IO-Socket-IP-0.22-1
* perl-IO-Socket-SSL-1.997-1
* perl-MailTools-2.12-1
* perl-Net-SSLeay-1.65-1
* perl-TimeDate-2.30-1
These perl modules have been added or updated as prerequisites for
working git send-email support.
Hi Yaakov,
I just noted a strange effect
during installation phase of openmpi a certain numbers of links to exe
files are created as
(cd /pub/devel/openmpi/64bit/openmpi-1.8.2rc4-1.x86_64/inst/usr/bin; rm
-f mpirun.exe; ln -s orterun.exe mpirun.exe)
and they are there during the cyginstall
On Fri, Aug 15, 2014 at 1:52 AM, Yaakov Selkowitz yselkow...@cygwin.com wrote:
The following packages have been updated in the Cygwin distribution:
* man-db-2.6.7-2
man-db is an implementation of the standard Unix documentation system
accessed using the man command. It uses a Berkeley DB
Hi,
while computing test.c with doxygen and texlive I became the following error
message from latex.
It seems that the doxygen do not generate proper options for the latex flow
objects,
in this case the figures, any more.
(./test_8c.tex (/usr/share/texmf-dist/tex/latex/psnfss/ts1phv.fd)
!
On 8/15/2014 9:26 AM, Pach Roman (DGS-EC/ESG4) wrote:
Hi,
while computing test.c with doxygen and texlive I became the following error
message from latex.
It seems that the doxygen do not generate proper options for the latex flow
objects,
in this case the figures, any more.
This doesn't
On 2014-08-15 07:22, Michael DePaulo wrote:
This release removes the cache database generation from the postinstall step
due to its often excessive length. Users will need to manage the database
themselves with mandb(1) in order to use whatis/apropos(1).
IMHO, this sounds like a serious
On 15/08/2014 13:26, Marco Atzeri wrote:
Hi Yaakov,
I just noted a strange effect
Is it possible that latest binutils update is fooling cygport ?
In the past, it seems they were renamed ( mpirun.exe to mpirun)
looking further, it seems not a cygport issue at all
$ touch a.exe
$ ln -s
On Aug 15 16:47, Marco Atzeri wrote:
On 15/08/2014 13:26, Marco Atzeri wrote:
Hi Yaakov,
I just noted a strange effect
Is it possible that latest binutils update is fooling cygport ?
In the past, it seems they were renamed ( mpirun.exe to mpirun)
looking further, it seems not a
Hello,
I'd like to inform that a new version of weechat is available.
Official changelog can be found here.
http://weechat.org/files/changelog/ChangeLog-1.0.html
For developers, consider packaging it for cygwin upgrade.
Thanks.
--
Problem reports: http://cygwin.com/problems.html
FAQ:
On Fri, Aug 15, 2014 at 11:11:05PM +0700, Alive4Ever wrote:
Hello,
I'd like to inform that a new version of weechat is available.
Official changelog can be found here.
http://weechat.org/files/changelog/ChangeLog-1.0.html
For developers, consider packaging it for cygwin upgrade.
On 08/15/2014 09:16 AM, Corinna Vinschen wrote:
On Aug 15 16:47, Marco Atzeri wrote:
On 15/08/2014 13:26, Marco Atzeri wrote:
Hi Yaakov,
I just noted a strange effect
Is it possible that latest binutils update is fooling cygport ?
In the past, it seems they were renamed ( mpirun.exe to
On Fri, Aug 15, 2014 at 10:20 AM, Yaakov Selkowitz
yselkow...@cygwin.com wrote:
On 2014-08-15 07:22, Michael DePaulo wrote:
This release removes the cache database generation from the postinstall
step
due to its often excessive length. Users will need to manage the
database
themselves with
Version 1.0-1 of weechat has been uploaded.
ChangeLog and release notes:
http://weechat.org/files/changelog/ChangeLog-1.0.html
http://weechat.org/files/releasenotes/ReleaseNotes-1.0.html
DESCRIPTION
WeeChat is a fast, light and extensible chat client. It runs on many platforms
like Linux, Unix,
Greetings, Michael DePaulo!
This release removes the cache database generation from the postinstall
step
due to its often excessive length. Users will need to manage the
database
themselves with mandb(1) in order to use whatis/apropos(1).
IMHO, this sounds like a serious decrease in
I'm trying unsuccesfully to get cron to work under 64-bit cywin under Win7
Pro. First, I tried running as myself (running cygwin with system
administrator privilege):
$ cron-config
Do you want to install the cron daemon as a service? (yes/no) yes
Enter the value of CYGWIN for the daemon: [ ]
Do
Suppose a makefile or similar for this issue, would handle only man
pages that have changed since the last update:
The TL;DR version of the issue is that compilation of database is slow and
prone to fail, plus the database should be re-indexed each time a page is
added, removed or changed.
If
On Fri, Aug 15, 2014 at 8:05 PM, Andrey Repin anrdae...@yandex.ru wrote:
Greetings, Michael DePaulo!
This release removes the cache database generation from the postinstall
step
due to its often excessive length. Users will need to manage the
database
themselves with mandb(1) in order to
Version 1.0-1 of weechat has been uploaded.
ChangeLog and release notes:
http://weechat.org/files/changelog/ChangeLog-1.0.html
http://weechat.org/files/releasenotes/ReleaseNotes-1.0.html
DESCRIPTION
WeeChat is a fast, light and extensible chat client. It runs on many platforms
like Linux, Unix,
45 matches
Mail list logo
