Thanks for the feedback.
Even if a file were missing that might cause issues in a few
dependency chains, why not allow the install to continue?
Suppose a file was missing halfway through? Why stop the whole
install for the sake of a few missing files? Let the install continue
for those packages
On 2019-06-11 11:19, Achim Gratz wrote:
> Keith Christian writes:
>> Would the maintainers (Achim? Jon?) be willing to consider an option
>> box log errors to the setup.log file and "Skip non-fatal errors and
>> continue?"
>
> You'd first have to teach setup to distinguish between fatal and
> non
On 2019-06-11 11:22, Achim Gratz wrote:
> Keith Thompson writes:
>> On Windows targets (including Cygwin and MinGW), the "-fms-extensions"
>> option is enabled by default. This option enables certain Microsoft
>> extensions -- and apparently inhibits any diagnostics for implicit int.
>>
>> It is u
On 2019/06/10 13:12, Chris Wagner wrote:
> I didn't know about run, thanks for the tip. However when I use it to
> launch something from the Start Menu Run command, it still pops open a
> terminal window of some kind for a fraction of a second. I'm on Windows
> 7.
>
Windows has a flag set in
Keith Thompson writes:
> On Windows targets (including Cygwin and MinGW), the "-fms-extensions"
> option is enabled by default. This option enables certain Microsoft
> extensions -- and apparently inhibits any diagnostics for implicit int.
>
> It is unfortunate, and arguably a bug, that this means
Keith Christian writes:
> Would the maintainers (Achim? Jon?) be willing to consider an option
> box log errors to the setup.log file and "Skip non-fatal errors and
> continue?"
You'd first have to teach setup to distinguish between fatal and
non-fatal errors. A missing package archive is always
Greetings, Keith Christian!
> Today I am reinstalling Cygwin to fix a DLL package, taking awhile but
> worth the wait (-: (-:
> Setup paused with a dialog to report a missing .xz file. I saw the
> error a half hour later.
> Would the maintainers (Achim? Jon?) be willing to consider an option
Hi,
I am following up to check if you're company is interested in acquiring
Attendees List of "National Association of Drug Court Professionals"?
We have discounted Prices this month.
Expo Details:
Date : JULY 14- JULY 17
Location : Na
On 2019-06-11 05:27, Keith Christian wrote:
> On Tue, Jun 11, 2019 at 2:03 AM Henning wrote:
>> On 10/06/2019 23:41, Keith Christian wrote:
>>> Would the maintainers (Achim? Jon?) be willing to consider an option box
>>> log errors to the setup.log file and "Skip non-fatal errors and
>>> continue
On 6/11/2019 4:52 AM, Corinna Vinschen wrote:
> On Jun 7 12:10, Ken Brown wrote:
>> While testing some new pipe code, I'm occasionally seeing a timerfd deadlock:
>> The main thread is stuck in timerfd_tracker::dtor at timerfd.cc:354, waiting
>> for
>> the timerfd thread to close; and the timerfd
Ken, a re-install fixed this issue, thanks for pointing out the
version mismatch.
On Mon, Jun 10, 2019 at 12:00 PM Ken Brown wrote:
>
> On 6/10/2019 1:16 PM, Keith Christian wrote:
> > Strace shows this in a dialog box when it fails:
> > The procedure entry point uname_x could not be loc
And if this option is deemed worthy of implementation, add a command
line option for those who skip the GUI.
Thanks again.
On Tue, Jun 11, 2019 at 2:03 AM Henning wrote:
>
> On 10/06/2019 23:41, Keith Christian wrote:
> >
> > Would the maintainers (Achim? Jon?) be willing to consider an option
On Jun 7 12:10, Ken Brown wrote:
> While testing some new pipe code, I'm occasionally seeing a timerfd deadlock:
> The main thread is stuck in timerfd_tracker::dtor at timerfd.cc:354, waiting
> for
> the timerfd thread to close; and the timerfd thread is stuck at
> timerfd.cc:140,
> waiting t
On 10/06/2019 23:41, Keith Christian wrote:
Would the maintainers (Achim? Jon?) be willing to consider an option
box log errors to the setup.log file and "Skip non-fatal errors and
continue?"
either this, or a prompt asking if the user wants to continue or abort.
Henning
--
Problem reports:
I believe this answer by user "M.M" on Stack Overflow explains the issue:
https://stackoverflow.com/a/56537459/827263
On Windows targets (including Cygwin and MinGW), the "-fms-extensions"
option is enabled by default. This option enables certain Microsoft
extensions -- and apparently inhibits an
15 matches
Mail list logo
