public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] python-getdevinfo
Date: Wed, 2 Sep 2020 20:05:55 +0200	[thread overview]
Message-ID: <610f9c29-0f34-9b07-7848-e3d90c08728f@gmail.com> (raw)
In-Reply-To: <DB7PR02MB399639851153E2868959B89DE72F0@DB7PR02MB3996.eurprd02.prod.outlook.com>

On 02.09.2020 17:29, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> *bump* in case this has not been seen.
> 
> Hamish
> 
> On 26/08/2020 10:35, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> Okay, I have updated the packages (same location:
>> https://www.hamishmb.com/files/cygwin-temp/). It should now handle fork
>> errors better.
>>
>> If it fails again, please post the full output from the test command so
>> I can see what version(s) of Python the tests are failing on. It might
>> be useful for someone else to have a go as well - would be good to know
>> multiple people can reproduce this issue as I have still had no luck
>> doing that.
>>

Hi Hamish,

it builds fine and there are no problem on tests.

Are you missing some dependencies ?

  "On Cygwin, you need the smartmontools and blkid packages".

but they are not there:

  $ cygport python-getdevinfo.cygport deps|cat
python36-3.6.10-1
python36-bs4-4.9.1-1
python36-getdevinfo-1.1.0-1
python37-3.7.7-1
python37-bs4-4.9.1-1
python37-getdevinfo-1.1.0-1
python38-3.8.3-1
python38-bs4-4.9.1-1
python38-getdevinfo-1.1.0-1


Is already in some Linux distribution ?
Otherwise we need 5 votes from maintainers

  reply	other threads:[~2020-09-02 18:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-17 13:33 Hamish McIntyre-Bhatty
2020-08-17 13:34 ` Hamish McIntyre-Bhatty
2020-08-19  5:53   ` Marco Atzeri
2020-08-19 11:22     ` Hamish McIntyre-Bhatty
2020-08-20  6:01       ` Marco Atzeri
2020-08-21 15:33         ` Hamish McIntyre-Bhatty
2020-08-26  9:35           ` Hamish McIntyre-Bhatty
2020-09-02 15:29             ` Hamish McIntyre-Bhatty
2020-09-02 18:05               ` Marco Atzeri [this message]
2020-09-02 20:58                 ` Hamish McIntyre-Bhatty
2020-09-03 13:44                   ` marco atzeri
2020-09-03 14:10                     ` Hamish McIntyre-Bhatty
2020-09-03 16:34                       ` Ken Brown
2020-09-03 17:13                         ` Hamish McIntyre-Bhatty
2020-09-03 17:27                           ` Hamish McIntyre-Bhatty
2020-09-03 18:50                             ` Ken Brown
2020-09-04 13:38                               ` Hamish McIntyre-Bhatty
2020-09-09 10:36                                 ` Hamish McIntyre-Bhatty
2020-09-12 22:19                                   ` Hamish McIntyre-Bhatty
2020-09-13  6:13                                     ` Achim Gratz
2020-09-13  7:39                                       ` Hamish McIntyre-Bhatty
2020-09-13 15:02                                         ` Brian Inglis
2020-09-13 16:08                                           ` Hamish McIntyre-Bhatty
2020-09-14 18:29                                             ` Hamish McIntyre-Bhatty
2020-09-13 14:57                     ` Jon Turney
2020-09-13 16:07                       ` Hamish McIntyre-Bhatty
2020-09-22 13:32                         ` Hamish McIntyre-Bhatty

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=610f9c29-0f34-9b07-7848-e3d90c08728f@gmail.com \
    --to=marco.atzeri@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).