I attempted this myself a few years ago, and also ran into a lot of
problems. One of the biggest problems is SVN itself -- it dumps .svn
directories and internal files all over the place, which wreaked havoc on
directories like modprobe.d which didn't properly ignore dot files. You'd
probably hav
> Question is: What do you use to version control permission sensitive
files? Subversion doesn't give a damn about permissions, so even after I
clean up this mess, I think I should probably
> avoid it.
We use Puppet to make sure managed files have proper ownership, permissions
and relevant servi
Phil Pennock wrote:
> Charles Polisher wrote:
> > There's an interesting blog post on this -
> > http://utcc.utoronto.ca/~cks/space/blog/sysadmin/WhyNotEtckeeper?showcomments
> > which observes that with etckeeper & friends you'll be fighting
> > your package management system. Some good point/coun
On 2013-04-20 at 16:17 -0700, Charles Polisher wrote:
> There's an interesting blog post on this -
> http://utcc.utoronto.ca/~cks/space/blog/sysadmin/WhyNotEtckeeper?showcomments
> which observes that with etckeeper & friends you'll be fighting
> your package management system. Some good point/coun
Phil Pennock wrote:
> Edward Ned Harvey (lopser) wrote:
> > I recently thought it would be a good idea to version control the /etc
> > directory. Using subversion, I added and committed ... and all hell
> > broke loose.
>
> Worse than that: there's a contrib wrapper for svn which claims to add
>
On 2013-04-20 at 13:28 +, Edward Ned Harvey (lopser) wrote:
> I recently thought it would be a good idea to version control the /etc
> directory. Using subversion, I added and committed ... and all hell
> broke loose.
Worse than that: there's a contrib wrapper for svn which claims to add
per
On Apr 20, 2013, at 6:41 AM, Graham Dunn wrote:
>> *From: *Edward Ned Harvey (lopser)
>> *Sent: *Saturday, April 20, 2013 9:29 AM
>> *To: *tech@lists.lopsa.org
>> *Reply To: *Edward Ned Harvey (lopser)
>> *Subject: *[lopsa-tech] Version controlling permission sensitive files
>>
>> Question is: W
Chef
On Apr 20, 2013 12:00 PM, "Yves Dorfsman" wrote:
> On 2013-04-20 07:45, Ali Sajid Imami wrote:
>
>> At $WORK, we tend to use a private git repository, and a custom script. We
>> clone the directory to anywhere we like, commit our changes, then push it
>> to
>> github. Then a custom script, p
On 2013-04-20 07:45, Ali Sajid Imami wrote:
At $WORK, we tend to use a private git repository, and a custom script. We
clone the directory to anywhere we like, commit our changes, then push it to
github. Then a custom script, pulls all the stuff down and a puppet run puts
the files in their appro
At $WORK, we tend to use a private git repository, and a custom script. We
clone the directory to anywhere we like, commit our changes, then push it
to github. Then a custom script, pulls all the stuff down and a puppet run
puts the files in their appropriate place.
On Sat, Apr 20, 2013 at 6:41 P
Etckeeper
*From: *Edward Ned Harvey (lopser)
*Sent: *Saturday, April 20, 2013 9:29 AM
*To: *tech@lists.lopsa.org
*Reply To: *Edward Ned Harvey (lopser)
*Subject: *[lopsa-tech] Version controlling permission sensitive files
I recently thought it would be a good idea to version control the /etc
I recently thought it would be a good idea to version control the /etc
directory. Using subversion, I added and committed ... and all hell broke
loose.
It seems, for some god unforsaken reason, during a commit, svn will copy (or
link?) the file being committed, read the temp copy, and then mo
12 matches
Mail list logo
