From: Warren Young <warren@etr-usa.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: How to correctly rebase?
Date: Wed, 14 Oct 2015 21:30:00 -0000 [thread overview]
Message-ID: <9275354A-6BFA-4964-BA05-008441168922@etr-usa.com> (raw)
In-Reply-To: <87si5dqmh9.fsf@Rainer.invalid>
On Oct 14, 2015, at 1:27 PM, Achim Gratz wrote:
>
> Warren Young writes:
>> I propose that the _autorebase maintainer
>> add those directories to the package, so they’re always available.
>
> They actually are packaged, so I'm not sure why they wouldn't be
> available on your system.
I’ve just checked the source package, and you’re right. That means my system got broken sometime after February 5, 2015 the last time _autorebase was updated.
> In other words you should see an "incomplete"
> package from cygcheck and a re-installation should fix it.
Alas, I already reinstalled it while debugging the problem.
>> /var/cache/rebase is the critical one: without it, the rebase-trigger
>> script can’t set the trigger, so the rebasing will never happen. The
>> lack of the others just causes nonfatal complaints.
>
> I'll check if I can just re-create the directory if it doesn't exist.
Put "mkdir -p ${b}" somewhere near the top of 0p_000_autorebase.dash or rebaselst.
>> (Which makes me wonder how it got broken, since the Windows VM I
>> tested this on isn’t used heavily, and was created not all that long
>> ago.)
>
> Maybe if you find something in /var/log/setup.log you could let me know.
Well, here’s a fun find: The last time that file was written to was November 4, 2014, even though I did two or there setup.exe passes today while composing my prior reply.
$ getfacl /var/log/setup.log
# file: /var/log/setup.log
# owner: Warren
# group: Warren
user::rw-
group::---
other:r—
So, why is setup.exe not writing to it? 604 is a weird permission set, but does it really need world writability?
I get the same permission set when saying “touch x” on this box.
Windows 10, 64-bit.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2015-10-14 21:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 14:26 Dr Rainer Woitok
2015-10-14 17:27 ` Warren Young
2015-10-14 19:27 ` Achim Gratz
2015-10-14 21:30 ` Warren Young [this message]
2015-10-14 22:08 ` Warren Young
2015-10-14 22:37 ` Warren Young
2015-10-15 7:53 ` Achim Gratz
2015-10-15 7:15 ` Achim Gratz
2015-10-15 13:16 ` Dr Rainer Woitok
2015-10-15 20:54 ` Warren Young
2015-10-15 21:10 ` Ken Brown
2015-10-16 12:57 ` Dr Rainer Woitok
2015-10-16 12:58 ` Ken Brown
2015-10-16 15:08 ` Ken Brown
2015-10-16 15:16 ` cyg Simple
2015-10-16 15:29 ` Ken Brown
2015-10-16 15:50 ` Andrey Repin
2015-10-18 11:15 ` Dr Rainer Woitok
2015-10-18 11:59 ` Achim Gratz
2015-10-18 12:45 ` Ken Brown
2015-10-18 16:20 ` Dr Rainer Woitok
2015-10-19 23:59 ` Warren Young
2015-10-20 16:55 ` Dr Rainer Woitok
2015-10-16 7:21 ` Achim Gratz
2015-10-16 20:11 ` Warren Young
2015-12-18 16:28 ` Achim Gratz
2015-10-14 19:58 ` Achim Gratz
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=9275354A-6BFA-4964-BA05-008441168922@etr-usa.com \
--to=warren@etr-usa.com \
--cc=cygwin@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).