From: Wayne Porter <wporter82@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] procps-ng
Date: Mon, 21 Mar 2016 21:01:00 -0000 [thread overview]
Message-ID: <CALsG8y2wheE_npPY=ZPkUCYZJuct=x2Shqrj4+PDJgCw73QMTQ@mail.gmail.com> (raw)
In-Reply-To: <20160321105426.GO3422@calimero.vinschen.de>
On Mon, Mar 21, 2016 at 3:54 AM, Corinna Vinschen
<corinna-cygwin@cygwin.com> wrote:
> On Mar 21 10:40, Corinna Vinschen wrote:
>> On Mar 20 14:46, Wayne Porter wrote:
>> > On Sun, Mar 20, 2016 at 2:40 PM, Corinna Vinschen
>> > <corinna-cygwin@cygwin.com> wrote:
>> > > On Mar 20 14:30, Wayne Porter wrote:
>> > >> > On Sun, Mar 20, 2016 at 1:47 PM, Corinna Vinschen
>> > >> > <corinna-cygwin@cygwin.com> wrote:
>> > >> >> Can you please provide direct links to the files, allowing to fetch
>> > >> >> them via wget?
>> > >> >>
>> > >> >>
>> > >> >> Thanks,
>> > >> >> Corinna
>> > >> >> [...]
>> > >>
>> > >> Ok, I have uploaded the files to the location here: http://wayneng.x10host.com/
>> > >> Going to the url will show a list of all the files and you can wget
>> > >> them directly
>> > >> from there. Let me know if you have any issues downloading.
>> > >
>> > > Works, but the procps-ng-3.3.9-1-src.tar.xz and procps-ng-3.3.9-1.tar.xz
>> > > files are invalid xz archives. The other files are ok (and look good
>> > > packaging-wise). Can you reupload those two files, please?
>> > >
>> > >
>> > > Thanks,
>> > > Corinna
>> > >
>> > > --
>> > > Corinna Vinschen Please, send mails regarding Cygwin to
>> > > Cygwin Maintainer cygwin AT cygwin DOT com
>> > > Red Hat
>> >
>> >
>> >
>> > I have uploaded them again.
>>
>> Thanks. I noticed that you updated to 3.3.10 in the meantime, so I
>> inspected only those. Packaging looks mostly fine with two exceptions:
>>
>> - Where's procps? It seems to have gone amiss somehow...
I had a typo in the transform that left it as pscommand.exe. Thanks
for catching that.
>>
>> - The man3 man pages should be packaged with the libproc-ng-devel
>> package.
>>
>> With these fixes I think the package is fine. If you create the 32 bit
>> packages and send your ssh key per
>>
>> https://sourceware.org/cygwin-apps/package-upload.html
>>
>> you are good to go after a final review.
>
> Except, can you please add the following line to your cygport file:
>
> procps_ng_OBSOLETES="procps"
>
> This will generate the package files for procps as well.
>
>
> Thanks,
> Corinna
>
> --
> Corinna Vinschen Please, send mails regarding Cygwin to
> Cygwin Maintainer cygwin AT cygwin DOT com
> Red Hat
There is now a 32 and 64 bit folder with the corresponding packages
available with all the fixes you recommended.
--
Wayne Porter
next prev parent reply other threads:[~2016-03-21 17:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 20:18 Wayne Porter
2016-03-16 20:48 ` Warren Young
2016-03-16 20:51 ` Yaakov Selkowitz
2016-03-19 0:25 ` Wayne Porter
2016-03-20 20:55 ` Corinna Vinschen
2016-03-20 21:41 ` Wayne Porter
2016-03-20 21:47 ` Wayne Porter
2016-03-21 9:40 ` Corinna Vinschen
2016-03-21 10:54 ` Wayne Porter
2016-03-21 12:05 ` Corinna Vinschen
2016-03-21 13:06 ` Corinna Vinschen
2016-03-21 21:01 ` Wayne Porter [this message]
2016-03-22 12:32 ` Corinna Vinschen
2016-03-22 13:46 ` Marco Atzeri
2016-03-22 15:14 ` Corinna Vinschen
2016-03-22 15:16 ` Marco Atzeri
2016-03-22 16:03 ` Chris Sutcliffe
2016-03-22 18:06 ` Wayne Porter
2016-03-22 18:12 ` Chris Sutcliffe
2016-03-22 21:00 ` Wayne Porter
2016-03-24 13:29 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALsG8y2wheE_npPY=ZPkUCYZJuct=x2Shqrj4+PDJgCw73QMTQ@mail.gmail.com' \
--to=wporter82@gmail.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).