<danieldicki...@gmail.com> wrote: > I'm seeing the same error on a fresh repo I just created and tried to > do an initial push to. I'm able to push to an older preexisting repo > just fine.
> On Jan 26, 4:29 am, merehap <mere...@gmail.com> wrote: >> I recently set up a patch-tag repository called HusyHox with the >> intention of pushing a repository on my local machine to it.
>> I have been unable to push the repository with the command stated in >> the instructions.
>> This is after entering my password then approving 17 local patches to >> send.
>> Note that I was able to SSH into mere...@patch-tag.com without any >> issues after this failed.
>> twb on #darcs suspected that this was some edge case where darcs >> doesn't work well with security-conscious hosting providers.
>> Any ideas?
>> Thanks.
> -- > You received this message because you are subscribed to the Google Groups "patch-tag-users" group. > To post to this group, send email to patch-tag-users@googlegroups.com. > To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/patch-tag-users?hl=en.
> There was bad permissioning (too strict) on patch-tag, which probably > resulted from an overall tightening of security I have undertaken.
> Could you try again?
> thomas.
> On Tue, Jan 26, 2010 at 12:25 PM, Daniel Dickison > <danieldicki...@gmail.com> wrote: >> I'm seeing the same error on a fresh repo I just created and tried to >> do an initial push to. I'm able to push to an older preexisting repo >> just fine.
>> On Jan 26, 4:29 am, merehap <mere...@gmail.com> wrote: >>> I recently set up a patch-tag repository called HusyHox with the >>> intention of pushing a repository on my local machine to it.
>>> I have been unable to push the repository with the command stated in >>> the instructions.
>>> fails with >>> --------------------------------------------------------------------------- ------- >>> Enter passphrase for key '/root/.ssh/id_rsa':
>>> darcs failed: Couldn't write >>> `0000003931-950067a323f7a924e38a938bc32623a4ccbc40c9ea7f917c06b560008ab6b09 8' >>> in subdir inventories to sources:
>>> This is after entering my password then approving 17 local patches to >>> send.
>>> Note that I was able to SSH into mere...@patch-tag.com without any >>> issues after this failed.
>>> twb on #darcs suspected that this was some edge case where darcs >>> doesn't work well with security-conscious hosting providers.
>>> Any ideas?
>>> Thanks.
>> -- >> You received this message because you are subscribed to the Google Groups "patch-tag-users" group. >> To post to this group, send email to patch-tag-users@googlegroups.com. >> To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/patch-tag-users?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "patch-tag-users" group. > To post to this group, send email to patch-tag-users@googlegroups.com. > To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/patch-tag-users?hl=en.
> On Jan 26, 2010, at 3:42 PM, Thomas Hartman wrote:
> > There was bad permissioning (too strict) on patch-tag, which probably > > resulted from an overall tightening of security I have undertaken.
> > Could you try again?
> > thomas.
> > On Tue, Jan 26, 2010 at 12:25 PM, Daniel Dickison > > <danieldicki...@gmail.com> wrote: > >> I'm seeing the same error on a fresh repo I just created and tried to > >> do an initial push to. I'm able to push to an older preexisting repo > >> just fine.
> >> On Jan 26, 4:29 am, merehap <mere...@gmail.com> wrote: > >>> I recently set up a patch-tag repository called HusyHox with the > >>> intention of pushing a repository on my local machine to it.
> >>> I have been unable to push the repository with the command stated in > >>> the instructions.
> >>> fails with > >>> --------------------------------------------------------------------------- ------- > >>> Enter passphrase for key '/root/.ssh/id_rsa':
> >>> darcs failed: Couldn't write > >>> `0000003931-950067a323f7a924e38a938bc32623a4ccbc40c9ea7f917c06b560008ab6b09 8' > >>> in subdir inventories to sources:
> >>> This is after entering my password then approving 17 local patches to > >>> send.
> >>> Note that I was able to SSH into mere...@patch-tag.com without any > >>> issues after this failed.
> >>> twb on #darcs suspected that this was some edge case where darcs > >>> doesn't work well with security-conscious hosting providers.
> >>> Any ideas?
> >>> Thanks.
> >> -- > >> You received this message because you are subscribed to the Google Groups "patch-tag-users" group. > >> To post to this group, send email to patch-tag-users@googlegroups.com. > >> To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. > >> For more options, visit this group athttp://groups.google.com/group/patch-tag-users?hl=en.
> > -- > > You received this message because you are subscribed to the Google Groups "patch-tag-users" group. > > To post to this group, send email to patch-tag-users@googlegroups.com. > > To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. > > For more options, visit this group athttp://groups.google.com/group/patch-tag-users?hl=en.- Hide quoted text -
> I'll be able to try in about 4.5 hours. I'll update you then.
> On Jan 26, 12:43 pm, Daniel Dickison <danieldicki...@gmail.com> wrote:
> > It's working now. Thanks!
> > On Jan 26, 2010, at 3:42 PM, Thomas Hartman wrote:
> > > There was bad permissioning (too strict) on patch-tag, which probably > > > resulted from an overall tightening of security I have undertaken.
> > > Could you try again?
> > > thomas.
> > > On Tue, Jan 26, 2010 at 12:25 PM, Daniel Dickison > > > <danieldicki...@gmail.com> wrote: > > >> I'm seeing the same error on a fresh repo I just created and tried to > > >> do an initial push to. I'm able to push to an older preexisting repo > > >> just fine.
> > >> On Jan 26, 4:29 am, merehap <mere...@gmail.com> wrote: > > >>> I recently set up a patch-tag repository called HusyHox with the > > >>> intention of pushing a repository on my local machine to it.
> > >>> I have been unable to push the repository with the command stated in > > >>> the instructions.
> > >>> This is after entering my password then approving 17 local patches to > > >>> send.
> > >>> Note that I was able to SSH into mere...@patch-tag.com without any > > >>> issues after this failed.
> > >>> twb on #darcs suspected that this was some edge case where darcs > > >>> doesn't work well with security-conscious hosting providers.
> > >>> Any ideas?
> > >>> Thanks.
> > >> -- > > >> You received this message because you are subscribed to the Google Groups "patch-tag-users" group. > > >> To post to this group, send email to patch-tag-users@googlegroups.com. > > >> To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. > > >> For more options, visit this group athttp://groups.google.com/group/patch-tag-users?hl=en.
> > > -- > > > You received this message because you are subscribed to the Google Groups "patch-tag-users" group. > > > To post to this group, send email to patch-tag-users@googlegroups.com. > > > To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. > > > For more options, visit this group athttp://groups.google.com/group/patch-tag-users?hl=en.-Hide quoted text -
On Tue, Jan 26, 2010 at 6:07 PM, merehap <mere...@gmail.com> wrote: > OK, works for me now too. Thanks for your support, Thomas!
> On Jan 26, 2:29 pm, merehap <elquesogran...@gmail.com> wrote: >> I'll be able to try in about 4.5 hours. I'll update you then.
>> On Jan 26, 12:43 pm, Daniel Dickison <danieldicki...@gmail.com> wrote:
>> > It's working now. Thanks!
>> > On Jan 26, 2010, at 3:42 PM, Thomas Hartman wrote:
>> > > There was bad permissioning (too strict) on patch-tag, which probably >> > > resulted from an overall tightening of security I have undertaken.
>> > > Could you try again?
>> > > thomas.
>> > > On Tue, Jan 26, 2010 at 12:25 PM, Daniel Dickison >> > > <danieldicki...@gmail.com> wrote: >> > >> I'm seeing the same error on a fresh repo I just created and tried to >> > >> do an initial push to. I'm able to push to an older preexisting repo >> > >> just fine.
>> > >> On Jan 26, 4:29 am, merehap <mere...@gmail.com> wrote: >> > >>> I recently set up a patch-tag repository called HusyHox with the >> > >>> intention of pushing a repository on my local machine to it.
>> > >>> I have been unable to push the repository with the command stated in >> > >>> the instructions.
>> > >>> This is after entering my password then approving 17 local patches to >> > >>> send.
>> > >>> Note that I was able to SSH into mere...@patch-tag.com without any >> > >>> issues after this failed.
>> > >>> twb on #darcs suspected that this was some edge case where darcs >> > >>> doesn't work well with security-conscious hosting providers.
>> > >>> Any ideas?
>> > >>> Thanks.
>> > >> -- >> > >> You received this message because you are subscribed to the Google Groups "patch-tag-users" group. >> > >> To post to this group, send email to patch-tag-users@googlegroups.com. >> > >> To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. >> > >> For more options, visit this group athttp://groups.google.com/group/patch-tag-users?hl=en.
>> > > -- >> > > You received this message because you are subscribed to the Google Groups "patch-tag-users" group. >> > > To post to this group, send email to patch-tag-users@googlegroups.com. >> > > To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. >> > > For more options, visit this group athttp://groups.google.com/group/patch-tag-users?hl=en.-Hide quoted text -
>> > - Show quoted text -
> -- > You received this message because you are subscribed to the Google Groups "patch-tag-users" group. > To post to this group, send email to patch-tag-users@googlegroups.com. > To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/patch-tag-users?hl=en.
This is not fixed for me (I'm brand new to patch-tag):
cosmonaut@starcity:~/src/TAberystwyth$ darcs push Pushing to "C...@patch-tag.com:/r/CalP/TAberystwyth"... Sat Feb 6 21:26:56 GMT 2010 c...@aber.ac.uk * Recording source tree Shall I push this patch? (1/1) [ynWvplxdaqjk], or ? for help: t Invalid response, try again! Shall I push this patch? (1/1) [ynWvplxdaqjk], or ? for help: y Writing pristine 4/13
darcs failed: Couldn't write `0000001788- e85c599f8de08ab45bf006101bb40ebecdc13113072a45bc31457ed07678c945' in subdir inventories to sources:
On Sat, Feb 6, 2010 at 1:45 PM, Cal Paterson <pointybl...@gmail.com> wrote: > This is not fixed for me (I'm brand new to patch-tag):
> cosmonaut@starcity:~/src/TAberystwyth$ darcs push > Pushing to "C...@patch-tag.com:/r/CalP/TAberystwyth"... > Sat Feb 6 21:26:56 GMT 2010 c...@aber.ac.uk > * Recording source tree > Shall I push this patch? (1/1) [ynWvplxdaqjk], or ? for help: t > Invalid response, try again! > Shall I push this patch? (1/1) [ynWvplxdaqjk], or ? for help: y > Writing pristine 4/13
> darcs failed: Couldn't write `0000001788- > e85c599f8de08ab45bf006101bb40ebecdc13113072a45bc31457ed07678c945' > in subdir inventories to sources:
> -- > You received this message because you are subscribed to the Google Groups "patch-tag-users" group. > To post to this group, send email to patch-tag-users@googlegroups.com. > To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/patch-tag-users?hl=en.
<thomashartm...@googlemail.com> wrote: > Could you try that again?
> I ran an (I thought) obsolete admin script that cleans up user > permissions in darcs repos.
> It's possible that there is a permission edge case involving repos > that use gitit wikis.
> If anybody else is experiencing this issue, please speak up so I can > have a better understanding as I track it down.
> thomas.
> On Sat, Feb 6, 2010 at 1:45 PM, Cal Paterson <pointybl...@gmail.com> wrote: >> This is not fixed for me (I'm brand new to patch-tag):
>> cosmonaut@starcity:~/src/TAberystwyth$ darcs push >> Pushing to "C...@patch-tag.com:/r/CalP/TAberystwyth"... >> Sat Feb 6 21:26:56 GMT 2010 c...@aber.ac.uk >> * Recording source tree >> Shall I push this patch? (1/1) [ynWvplxdaqjk], or ? for help: t >> Invalid response, try again! >> Shall I push this patch? (1/1) [ynWvplxdaqjk], or ? for help: y >> Writing pristine 4/13
>> darcs failed: Couldn't write `0000001788- >> e85c599f8de08ab45bf006101bb40ebecdc13113072a45bc31457ed07678c945' >> in subdir inventories to sources:
>> -- >> You received this message because you are subscribed to the Google Groups "patch-tag-users" group. >> To post to this group, send email to patch-tag-users@googlegroups.com. >> To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/patch-tag-users?hl=en.
glith@lafftop:~/code/agda/ctfp10$ darcs push gl...@patch-tag.com:/r/ stevan/ctfp10 Pushing to "gl...@patch-tag.com:/r/stevan/ctfp10"... Sun Mar 7 20:09:27 CET 2010 mortb...@student.chalmers.se * Test Shall I push this patch? (1/1) [ynWsfvplxdaqjk], or ? for help: y
darcs failed: Couldn't write `0000005602-50b660455bdce06adc2b2d3c191d793409362684cd44d3c89d48bc9c4a9230e 5' in subdir inventories to sources:
glith@lafftop:~/code/agda/ctfp10$ darcs push gl...@patch-tag.com:/r/ stevan/ctfp10 Pushing to "gl...@patch-tag.com:/r/stevan/ctfp10"... Sun Mar 7 20:09:27 CET 2010 mortb...@student.chalmers.se * Test Shall I push this patch? (1/1) [ynWsfvplxdaqjk], or ? for help: y
darcs failed: Couldn't write `0000005602-50b660455bdce06adc2b2d3c191d793409362684cd44d3c89d48bc9c4a9230e 5' in subdir inventories to sources:
When this has happened in the past I have a special administrator-only action that fixes the issue. I just ran it again, and all should be good in 5 minutes or so.
What I will do in the near future is add a "fix repo" action that will be runnable by repo owners (for private) or anyone (for public) repos.
And keep trying to get to the underlying cause of course.
If problems persist past 3:15pm pacific time, please ping me/the list.
On Sun, Mar 7, 2010 at 11:34 AM, glith <mortb...@student.chalmers.se> wrote: > Hi.
> I'm getting the same error as Cal Paterson:
> glith@lafftop:~/code/agda/ctfp10$ darcs push gl...@patch-tag.com:/r/ > stevan/ctfp10 > Pushing to "gl...@patch-tag.com:/r/stevan/ctfp10"... > Sun Mar 7 20:09:27 CET 2010 mortb...@student.chalmers.se > * Test > Shall I push this patch? (1/1) [ynWsfvplxdaqjk], or ? for help: y
> darcs failed: Couldn't write > `0000005602-50b660455bdce06adc2b2d3c191d793409362684cd44d3c89d48bc9c4a9230e 5' > in subdir inventories to sources:
> On Feb 7, 1:19 pm, Cal Paterson <pointybl...@gmail.com> wrote: >> On Feb 6, 11:17 pm, Thomas Hartman <thomashartm...@googlemail.com> >> wrote:
>> > Could you try that again?
>> > I ran an (I thought) obsolete admin script that cleans up user >> > permissions in darcs repos.
>> > It's possible that there is a permission edge case involving repos >> > that use gitit wikis.
>> Thanks, now works for me.
>> Finished applying... >> Push successful. >> (By the way, the remote repository has 47 patches to pull.)
> -- > You received this message because you are subscribed to the Google Groups "patch-tag-users" group. > To post to this group, send email to patch-tag-users@googlegroups.com. > To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/patch-tag-users?hl=en.
<prompt> -: darcs push Pushing to "koenclaes...@patch-tag.com:/r/jonas_duregard/ agatapaper"... Mon Mar 22 12:43:56 CET 2010 k...@chalmers.se * title Shall I push this patch? (1/5) [ynWsfvplxdaqjk], or ? for help: a
darcs failed: Couldn't write `0000001802-35ce2c25edb6b336e707577978892bf9eb173a41d634f4e1d678014b14c7ab3 7' in subdir inventories to sources:
> When this has happened in the past I have a special administrator-only > action that fixes the issue. I just ran it again, and all should be > good in 5 minutes or so.
> What I will do in the near future is add a "fix repo" action that will > be runnable by repo owners (for private) or anyone (for public) repos.
> And keep trying to get to the underlying cause of course.
> If problems persist past 3:15pm pacific time, please ping me/the list.
> Best, thomas.
> On Sun, Mar 7, 2010 at 11:34 AM, glith <mortb...@student.chalmers.se> wrote: > > Hi.
> > I'm getting the same error as Cal Paterson:
> > glith@lafftop:~/code/agda/ctfp10$ darcs push gl...@patch-tag.com:/r/ > > stevan/ctfp10 > > Pushing to "gl...@patch-tag.com:/r/stevan/ctfp10"... > > Sun Mar 7 20:09:27 CET 2010 mortb...@student.chalmers.se > > * Test > > Shall I push this patch? (1/1) [ynWsfvplxdaqjk], or ? for help: y
> > darcs failed: Couldn't write > > `0000005602-50b660455bdce06adc2b2d3c191d793409362684cd44d3c89d48bc9c4a9230e 5' > > in subdir inventories to sources:
> > On Feb 7, 1:19 pm, Cal Paterson <pointybl...@gmail.com> wrote: > >> On Feb 6, 11:17 pm, Thomas Hartman <thomashartm...@googlemail.com> > >> wrote:
> >> > Could you try that again?
> >> > I ran an (I thought) obsolete admin script that cleans up user > >> > permissions in darcs repos.
> >> > It's possible that there is a permission edge case involving repos > >> > that use gitit wikis.
> >> Thanks, now works for me.
> >> Finished applying... > >> Push successful. > >> (By the way, the remote repository has 47 patches to pull.)
> > -- > > You received this message because you are subscribed to the Google Groups "patch-tag-users" group. > > To post to this group, send email to patch-tag-users@googlegroups.com. > > To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. > > For more options, visit this group athttp://groups.google.com/group/patch-tag-users?hl=en.
On Mon, Mar 22, 2010 at 5:54 AM, Koen Claessen <koen.claes...@gmail.com> wrote: > I get the same error:
> <prompt> -: darcs push > Pushing to "koenclaes...@patch-tag.com:/r/jonas_duregard/ > agatapaper"... > Mon Mar 22 12:43:56 CET 2010 k...@chalmers.se > * title > Shall I push this patch? (1/5) [ynWsfvplxdaqjk], or ? for help: a
> darcs failed: Couldn't write > `0000001802-35ce2c25edb6b336e707577978892bf9eb173a41d634f4e1d678014b14c7ab3 7' > in subdir inventories to sources:
> On Mar 7, 11:59 pm, Thomas Hartman <thomashartm...@googlemail.com> > wrote: >> Yep, permissions are set incorrectly somehow.
>> When this has happened in the past I have a special administrator-only >> action that fixes the issue. I just ran it again, and all should be >> good in 5 minutes or so.
>> What I will do in the near future is add a "fix repo" action that will >> be runnable by repo owners (for private) or anyone (for public) repos.
>> And keep trying to get to the underlying cause of course.
>> If problems persist past 3:15pm pacific time, please ping me/the list.
>> Best, thomas.
>> On Sun, Mar 7, 2010 at 11:34 AM, glith <mortb...@student.chalmers.se> wrote: >> > Hi.
>> > I'm getting the same error as Cal Paterson:
>> > glith@lafftop:~/code/agda/ctfp10$ darcs push gl...@patch-tag.com:/r/ >> > stevan/ctfp10 >> > Pushing to "gl...@patch-tag.com:/r/stevan/ctfp10"... >> > Sun Mar 7 20:09:27 CET 2010 mortb...@student.chalmers.se >> > * Test >> > Shall I push this patch? (1/1) [ynWsfvplxdaqjk], or ? for help: y
>> > darcs failed: Couldn't write >> > `0000005602-50b660455bdce06adc2b2d3c191d793409362684cd44d3c89d48bc9c4a9230e 5' >> > in subdir inventories to sources:
>> > On Feb 7, 1:19 pm, Cal Paterson <pointybl...@gmail.com> wrote: >> >> On Feb 6, 11:17 pm, Thomas Hartman <thomashartm...@googlemail.com> >> >> wrote:
>> >> > Could you try that again?
>> >> > I ran an (I thought) obsolete admin script that cleans up user >> >> > permissions in darcs repos.
>> >> > It's possible that there is a permission edge case involving repos >> >> > that use gitit wikis.
>> >> Thanks, now works for me.
>> >> Finished applying... >> >> Push successful. >> >> (By the way, the remote repository has 47 patches to pull.)
>> > -- >> > You received this message because you are subscribed to the Google Groups "patch-tag-users" group. >> > To post to this group, send email to patch-tag-users@googlegroups.com. >> > To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. >> > For more options, visit this group athttp://groups.google.com/group/patch-tag-users?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "patch-tag-users" group. > To post to this group, send email to patch-tag-users@googlegroups.com. > To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/patch-tag-users?hl=en.
Well, I was the same problem with darc's write permissions and I solved it creating a new repository and pushing it first time before add the wiki. However, recently I add a new repository member and he hasn't that write access. I attemped to solved it by applying the umask 0002 but i don't know the way to cahnge de darcs configuration files at patch-tag server :S. Is there any way to solve it or I have to wait for a update?
On Tue, Mar 23, 2010 at 12:20 PM, Hacker_Zero <edu...@gmail.com> wrote: > Well, I was the same problem with darc's write permissions and I > solved it creating a new repository and pushing it first time before > add the wiki. However, recently I add a new repository member and he > hasn't that write access. I attemped to solved it by applying the > umask 0002 but i don't know the way to cahnge de darcs configuration > files at patch-tag server :S. Is there any way to solve it or I have > to wait for a update?
> Thanks in advance :)
> -- > You received this message because you are subscribed to the Google Groups "patch-tag-users" group. > To post to this group, send email to patch-tag-users@googlegroups.com. > To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/patch-tag-users?hl=en.
1) Folks, I believe the permissions related problems are resolved as I described, using the umask setting in darcs prefs.
What I haven't done is to implement a per-repository "fix permissions" one off action I proposed above, as I am actually hoping this is no longer necessary since the underlyin problem has been fixed.
If affected users would test and report any issues I would be most obliged. Thanks!
2) I am not sure if this is useful, but you can manipulate the darcs settings files via scp, e
<thomashartm...@googlemail.com> wrote: > Hi, no this is still a problem being worked on.
> On Tue, Mar 23, 2010 at 12:20 PM, Hacker_Zero <edu...@gmail.com> wrote: >> Well, I was the same problem with darc's write permissions and I >> solved it creating a new repository and pushing it first time before >> add the wiki. However, recently I add a new repository member and he >> hasn't that write access. I attemped to solved it by applying the >> umask 0002 but i don't know the way to cahnge de darcs configuration >> files at patch-tag server :S. Is there any way to solve it or I have >> to wait for a update?
>> Thanks in advance :)
>> -- >> You received this message because you are subscribed to the Google Groups "patch-tag-users" group. >> To post to this group, send email to patch-tag-users@googlegroups.com. >> To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/patch-tag-users?hl=en.
I just created a fresh repo and pushing the initial set of patches failed. Not sure what I should be looking for in the _darcs directory (via scp). If it makes any difference, I did enable wiki so there are 3 patches on the server related to that...
$ darcs push Pushing to "danieldicki...@patch-tag.com:/r/danieldickison/blank- paper"... ... darcs failed: Couldn't write `0000001866-10ff867b0dcc012f95fba1b8dbdbaad2498ad4ac9395dd45805ceeb712b2203 3' in subdir inventories to sources:
> 1) Folks, I believe the permissions related problems are resolved as I > described, using the umask setting in darcs prefs.
> What I haven't done is to implement a per-repository "fix permissions" > one off action I proposed above, as I am actually hoping this is no > longer necessary since the underlyin problem has been fixed.
> If affected users would test and report any issues I would be most > obliged. Thanks!
> 2) I am not sure if this is useful, but you can manipulate the darcs > settings files via scp, e
> to examine what you have, and scp upload to modify what's on patch tag.
> Is anybody already doing this? I would be curious about common use cases.
> Cheers, thomas.
> On Fri, Mar 26, 2010 at 2:51 PM, Thomas Hartman
> <thomashartm...@googlemail.com> wrote: > > Hi, no this is still a problem being worked on.
> > On Tue, Mar 23, 2010 at 12:20 PM, Hacker_Zero <edu...@gmail.com> wrote: > >> Well, I was the same problem with darc's write permissions and I > >> solved it creating a new repository and pushing it first time before > >> add the wiki. However, recently I add a new repository member and he > >> hasn't that write access. I attemped to solved it by applying the > >> umask 0002 but i don't know the way to cahnge de darcs configuration > >> files at patch-tag server :S. Is there any way to solve it or I have > >> to wait for a update?
> >> Thanks in advance :)
> >> -- > >> You received this message because you are subscribed to the Google Groups "patch-tag-users" group. > >> To post to this group, send email to patch-tag-users@googlegroups.com. > >> To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. > >> For more options, visit this group athttp://groups.google.com/group/patch-tag-users?hl=en.
OK, I am still on it. This time I will add a per repo "fix permissions" action first, and attempt to solve the underlying issue after, since it keeps coming up.
<danieldicki...@gmail.com> wrote: > I just created a fresh repo and pushing the initial set of patches > failed. Not sure what I should be looking for in the _darcs directory > (via scp). If it makes any difference, I did enable wiki so there are > 3 patches on the server related to that...
> $ darcs push > Pushing to "danieldicki...@patch-tag.com:/r/danieldickison/blank- > paper"... > ... > darcs failed: Couldn't write > `0000001866-10ff867b0dcc012f95fba1b8dbdbaad2498ad4ac9395dd45805ceeb712b2203 3' > in subdir inventories to sources:
> On Mar 29, 3:10 pm, Thomas Hartman <thomashartm...@googlemail.com> > wrote: >> 1) Folks, I believe the permissions related problems are resolved as I >> described, using the umask setting in darcs prefs.
>> What I haven't done is to implement a per-repository "fix permissions" >> one off action I proposed above, as I am actually hoping this is no >> longer necessary since the underlyin problem has been fixed.
>> If affected users would test and report any issues I would be most >> obliged. Thanks!
>> 2) I am not sure if this is useful, but you can manipulate the darcs >> settings files via scp, e
>> to examine what you have, and scp upload to modify what's on patch tag.
>> Is anybody already doing this? I would be curious about common use cases.
>> Cheers, thomas.
>> On Fri, Mar 26, 2010 at 2:51 PM, Thomas Hartman
>> <thomashartm...@googlemail.com> wrote: >> > Hi, no this is still a problem being worked on.
>> > On Tue, Mar 23, 2010 at 12:20 PM, Hacker_Zero <edu...@gmail.com> wrote: >> >> Well, I was the same problem with darc's write permissions and I >> >> solved it creating a new repository and pushing it first time before >> >> add the wiki. However, recently I add a new repository member and he >> >> hasn't that write access. I attemped to solved it by applying the >> >> umask 0002 but i don't know the way to cahnge de darcs configuration >> >> files at patch-tag server :S. Is there any way to solve it or I have >> >> to wait for a update?
>> >> Thanks in advance :)
>> >> -- >> >> You received this message because you are subscribed to the Google Groups "patch-tag-users" group. >> >> To post to this group, send email to patch-tag-users@googlegroups.com. >> >> To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. >> >> For more options, visit this group athttp://groups.google.com/group/patch-tag-users?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "patch-tag-users" group. > To post to this group, send email to patch-tag-users@googlegroups.com. > To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/patch-tag-users?hl=en.
> OK, I am still on it. This time I will add a per repo "fix > permissions" action first, and attempt to solve the underlying issue > after, since it keeps coming up.
> cheers, thomas.
> On Wed, Apr 7, 2010 at 12:48 AM, Daniel Dickison
> <danieldicki...@gmail.com> wrote: > > I just created a fresh repo and pushing the initial set of patches > > failed. Not sure what I should be looking for in the _darcs directory > > (via scp). If it makes any difference, I did enable wiki so there are > > 3 patches on the server related to that...
> > On Mar 29, 3:10 pm, Thomas Hartman <thomashartm...@googlemail.com> > > wrote: > >> 1) Folks, I believe the permissions related problems are resolved as I > >> described, using the umask setting in darcs prefs.
> >> What I haven't done is to implement a per-repository "fix permissions" > >> one off action I proposed above, as I am actually hoping this is no > >> longer necessary since the underlyin problem has been fixed.
> >> If affected users would test and report any issues I would be most > >> obliged. Thanks!
> >> 2) I am not sure if this is useful, but you can manipulate the darcs > >> settings files via scp, e
> >> to examine what you have, and scp upload to modify what's on patch tag.
> >> Is anybody already doing this? I would be curious about common use cases.
> >> Cheers, thomas.
> >> On Fri, Mar 26, 2010 at 2:51 PM, Thomas Hartman
> >> <thomashartm...@googlemail.com> wrote: > >> > Hi, no this is still a problem being worked on.
> >> > On Tue, Mar 23, 2010 at 12:20 PM, Hacker_Zero <edu...@gmail.com> wrote: > >> >> Well, I was the same problem with darc's write permissions and I > >> >> solved it creating a new repository and pushing it first time before > >> >> add the wiki. However, recently I add a new repository member and he > >> >> hasn't that write access. I attemped to solved it by applying the > >> >> umask 0002 but i don't know the way to cahnge de darcs configuration > >> >> files at patch-tag server :S. Is there any way to solve it or I have > >> >> to wait for a update?
> >> >> Thanks in advance :)
> >> >> -- > >> >> You received this message because you are subscribed to the Google Groups "patch-tag-users" group. > >> >> To post to this group, send email to patch-tag-users@googlegroups.com. > >> >> To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. > >> >> For more options, visit this group athttp://groups.google.com/group/patch-tag-users?hl=en.
> > -- > > You received this message because you are subscribed to the Google Groups "patch-tag-users" group. > > To post to this group, send email to patch-tag-users@googlegroups.com. > > To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. > > For more options, visit this group athttp://groups.google.com/group/patch-tag-users?hl=en.
On Sun, Apr 11, 2010 at 4:54 AM, Grégoire <gdet...@crans.org> wrote: > Hi,
> I just got the same problem and I cannot find any "fix permissions" > action in my repo settings...
> this is the error I get : >>darcs failed: Couldn't write `0000000712-f48d53f7c843024b0da9edcc59fc12045a2c144a21f23da67fd150b627e6183 2' >>in subdir inventories to sources:
> On Apr 8, 1:07 am, Thomas Hartman <thomashartm...@googlemail.com> > wrote: >> Yikes.
>> OK, I am still on it. This time I will add a per repo "fix >> permissions" action first, and attempt to solve the underlying issue >> after, since it keeps coming up.
>> cheers, thomas.
>> On Wed, Apr 7, 2010 at 12:48 AM, Daniel Dickison
>> <danieldicki...@gmail.com> wrote: >> > I just created a fresh repo and pushing the initial set of patches >> > failed. Not sure what I should be looking for in the _darcs directory >> > (via scp). If it makes any difference, I did enable wiki so there are >> > 3 patches on the server related to that...
>> > On Mar 29, 3:10 pm, Thomas Hartman <thomashartm...@googlemail.com> >> > wrote: >> >> 1) Folks, I believe the permissions related problems are resolved as I >> >> described, using the umask setting in darcs prefs.
>> >> What I haven't done is to implement a per-repository "fix permissions" >> >> one off action I proposed above, as I am actually hoping this is no >> >> longer necessary since the underlyin problem has been fixed.
>> >> If affected users would test and report any issues I would be most >> >> obliged. Thanks!
>> >> 2) I am not sure if this is useful, but you can manipulate the darcs >> >> settings files via scp, e
>> >> to examine what you have, and scp upload to modify what's on patch tag.
>> >> Is anybody already doing this? I would be curious about common use cases.
>> >> Cheers, thomas.
>> >> On Fri, Mar 26, 2010 at 2:51 PM, Thomas Hartman
>> >> <thomashartm...@googlemail.com> wrote: >> >> > Hi, no this is still a problem being worked on.
>> >> > On Tue, Mar 23, 2010 at 12:20 PM, Hacker_Zero <edu...@gmail.com> wrote: >> >> >> Well, I was the same problem with darc's write permissions and I >> >> >> solved it creating a new repository and pushing it first time before >> >> >> add the wiki. However, recently I add a new repository member and he >> >> >> hasn't that write access. I attemped to solved it by applying the >> >> >> umask 0002 but i don't know the way to cahnge de darcs configuration >> >> >> files at patch-tag server :S. Is there any way to solve it or I have >> >> >> to wait for a update?
>> >> >> Thanks in advance :)
>> >> >> -- >> >> >> You received this message because you are subscribed to the Google Groups "patch-tag-users" group. >> >> >> To post to this group, send email to patch-tag-users@googlegroups.com. >> >> >> To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. >> >> >> For more options, visit this group athttp://groups.google.com/group/patch-tag-users?hl=en.
>> > -- >> > You received this message because you are subscribed to the Google Groups "patch-tag-users" group. >> > To post to this group, send email to patch-tag-users@googlegroups.com. >> > To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. >> > For more options, visit this group athttp://groups.google.com/group/patch-tag-users?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "patch-tag-users" group. > To post to this group, send email to patch-tag-users@googlegroups.com. > To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/patch-tag-users?hl=en.
> On Apr 8, 1:07 am, Thomas Hartman <thomashartm...@googlemail.com> > wrote:
> > Yikes.
> > OK, I am still on it. This time I will add a per repo "fix > > permissions" action first, and attempt to solve the underlying issue > > after, since it keeps coming up.
> > cheers, thomas.
> > On Wed, Apr 7, 2010 at 12:48 AM, Daniel Dickison
> > <danieldicki...@gmail.com> wrote: > > > I just created a fresh repo and pushing the initial set of patches > > > failed. Not sure what I should be looking for in the _darcs directory > > > (via scp). If it makes any difference, I did enable wiki so there are > > > 3 patches on the server related to that...
> > > On Mar 29, 3:10 pm, Thomas Hartman <thomashartm...@googlemail.com> > > > wrote: > > >> 1) Folks, I believe the permissions related problems are resolved as I > > >> described, using the umask setting in darcs prefs.
> > >> What I haven't done is to implement a per-repository "fix permissions" > > >> one off action I proposed above, as I am actually hoping this is no > > >> longer necessary since the underlyin problem has been fixed.
> > >> If affected users would test and report any issues I would be most > > >> obliged. Thanks!
> > >> 2) I am not sure if this is useful, but you can manipulate the darcs > > >> settings files via scp, e
> > >> to examine what you have, and scp upload to modify what's on patch tag.
> > >> Is anybody already doing this? I would be curious about common use cases.
> > >> Cheers, thomas.
> > >> On Fri, Mar 26, 2010 at 2:51 PM, Thomas Hartman
> > >> <thomashartm...@googlemail.com> wrote: > > >> > Hi, no this is still a problem being worked on.
> > >> > On Tue, Mar 23, 2010 at 12:20 PM, Hacker_Zero <edu...@gmail.com> wrote: > > >> >> Well, I was the same problem with darc's write permissions and I > > >> >> solved it creating a new repository and pushing it first time before > > >> >> add the wiki. However, recently I add a new repository member and he > > >> >> hasn't that write access. I attemped to solved it by applying the > > >> >> umask 0002 but i don't know the way to cahnge de darcs configuration > > >> >> files at patch-tag server :S. Is there any way to solve it or I have > > >> >> to wait for a update?
> > >> >> Thanks in advance :)
> > >> >> -- > > >> >> You received this message because you are subscribed to the Google Groups "patch-tag-users" group. > > >> >> To post to this group, send email to patch-tag-users@googlegroups.com. > > >> >> To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. > > >> >> For more options, visit this group athttp://groups.google.com/group/patch-tag-users?hl=en.
> > > -- > > > You received this message because you are subscribed to the Google Groups "patch-tag-users" group. > > > To post to this group, send email to patch-tag-users@googlegroups.com. > > > To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. > > > For more options, visit this group athttp://groups.google.com/group/patch-tag-users?hl=en.
