dispatch-conf

[nihilo]

I've used tkdiffb (a very nice gui diff tool that is part of the tkcvs package) since the etc-update days, and am very happy with it. It works with dispatch-conf too by setting the following in /etc/dispatch-conf.conf:

Code: Select all

diff="tkdiff %s %s"

The equivalent etc-update setting is:

Code: Select all

diff_command="tkdiff %file1 %file2"

If anybody knows how to get dispatch-conf to (A) skip binary files (or automatically use the new version), and (B) use tkdiff for merging files as well, I'd be in heaven.

[rhill]

I get this error trying to run dispatch-conf:

Code: Select all

Traceback (most recent call last):
  File "/usr/sbin/dispatch-conf", line 309, in ?
    d.grind (portage.settings ['CONFIG_PROTECT'])
  File "/usr/sbin/dispatch-conf", line 145, in grind
    confs = filter (f, confs)
  File "/usr/sbin/dispatch-conf", line 135, in f
    self.replace(newconf, conf['current'])
  File "/usr/sbin/dispatch-conf", line 222, in replace
    os.system((DIFF_CONTENTS % (curconf, newconf)) + '>>' + self.config["log-file"])
AttributeError: dispatch instance has no attribute 'config'

Anyone have an idea?

yep. this was a bug in the last portage update that has been fixed. re-emerge portage and it should start working again. there's a bugzilla number for it but i'm way too lazy tonite to look it up.

[rhill]

nihilo:

Oh, and don't let dispatch-conf try to diff binary files (that's the -a flag in your diff line in dispatch-conf.conf). Take that flag out! Otherwise you'll get all sorts of interesting bugs showing up...

is that how you mean or was it something else? i haven't used tkdiffb.

[nihilo]

nihilo:

Oh, and don't let dispatch-conf try to diff binary files (that's the -a flag in your diff line in dispatch-conf.conf). Take that flag out! Otherwise you'll get all sorts of interesting bugs showing up...

is that how you mean or was it something else? i haven't used tkdiffb.

Thanks for the help, but that applies to the standard diff executable and not to the tkdiff program (which doesn't have a man page either )...

[Light]

I get this error trying to run dispatch-conf:

Code: Select all

Traceback (most recent call last):
  File "/usr/sbin/dispatch-conf", line 309, in ?
    d.grind (portage.settings ['CONFIG_PROTECT'])
  File "/usr/sbin/dispatch-conf", line 145, in grind
    confs = filter (f, confs)
  File "/usr/sbin/dispatch-conf", line 135, in f
    self.replace(newconf, conf['current'])
  File "/usr/sbin/dispatch-conf", line 222, in replace
    os.system((DIFF_CONTENTS % (curconf, newconf)) + '>>' + self.config["log-file"])
AttributeError: dispatch instance has no attribute 'config'

Anyone have an idea?

yep. this was a bug in the last portage update that has been fixed. re-emerge portage and it should start working again. there's a bugzilla number for it but i'm way too lazy tonite to look it up.

I would have expected a new release version to solve this, but that doesn't seem to be the case. I'm quite sure I have the latest version (the last few times I did "emerge sync" it didn't give me a newer version) and I also have this problem. The last time I did "emerge sync" was some 12 hours ago.

But I guess I would have to do "emerge portage" to solve this? I might have to give that a try then

[markandrew]

i occasionally have dispatch-conf leaving crap in some config files, eg

Code: Select all

# Disables the magic-sysrq key
#kernel.sysrq = 0
<<<<<<< /etc/sysctl.conf

# set kernel to re-use RAM rather than swap
vm.swappiness = 25
=======
# When the kernel panics, automatically reboot in 3 seconds
#kernel.panic = 3
# Allow for more PIDs (cool factor!); may break some programs
#kernel.pid_max = 999999

# TCP Port for lock manager
#sys.fs.nfs.nlm_tcpport = 0
# UDP Port for lock manager
#sys.fs.nfs.nlm_udpport = 0
>>>>>>> /etc/._cfg0000_sysctl.conf
                                       

in /etc/sysctl.conf - note the lines starting with >>>>> and <<<<

this seems to happen at random and really screws things up; i only notice when erorrs start cascading down the screen at boot, although now i check for it each time i update baselayout (which for some reason is when it all seems to happen). anyone know what causes it?

[mallchin]

Well, dispatch-conf has started to fsck up my config files, mearly running it is enough to break things...

The diff variants (stored in rcs) are making there way into /etc and, naturally, Gentoo spits feathers when it boots....

Has anyone else had this?

*edit*

Just seen your post markandrew, same problem here.

This kinda sux; I use Gentoo in a production enviroment and had I have been using dispatch-conf (as planned) it would have caused me a load of grief....

How come things aren't tested

[squeegy]

Well, dispatch-conf has started to fsck up my config files, mearly running it is enough to break things...

The diff variants (stored in rcs) are making there way into /etc and, naturally, Gentoo spits feathers when it boots....

Has anyone else had this?

*edit*

Just seen your post markandrew, same problem here.

This kinda sux; I use Gentoo in a production enviroment and had I have been using dispatch-conf (as planned) it would have caused me a load of grief....

How come things aren't tested

You answered your own question you're using Gentoo, a noncommercial distribution of Linux, and expecting commercial level perfection. There are many threads on this board that discuss why Gentoo is not great for a production environment. IMO dispatch-conf works very well, I've personally never had any problems.

[nihilo]

I get this error trying to run dispatch-conf:

Code: Select all

Traceback (most recent call last):
  File "/usr/sbin/dispatch-conf", line 309, in ?
    d.grind (portage.settings ['CONFIG_PROTECT'])
  File "/usr/sbin/dispatch-conf", line 145, in grind
    confs = filter (f, confs)
  File "/usr/sbin/dispatch-conf", line 135, in f
    self.replace(newconf, conf['current'])
  File "/usr/sbin/dispatch-conf", line 222, in replace
    os.system((DIFF_CONTENTS % (curconf, newconf)) + '>>' + self.config["log-file"])
AttributeError: dispatch instance has no attribute 'config'

Anyone have an idea?

yep. this was a bug in the last portage update that has been fixed. re-emerge portage and it should start working again. there's a bugzilla number for it but i'm way too lazy tonite to look it up.

I would have expected a new release version to solve this, but that doesn't seem to be the case. I'm quite sure I have the latest version (the last few times I did "emerge sync" it didn't give me a newer version) and I also have this problem. The last time I did "emerge sync" was some 12 hours ago.

But I guess I would have to do "emerge portage" to solve this? I might have to give that a try then

If you still haven't solved this, the solution is to change self.config to self.options on line 222 of the dispatch-conf script, which is the last line quoted in that stack trace you posted ("os.system((DIFF_CONTENTS .... ))").

hth...

[Light]

If you still haven't solved this, the solution is to change self.config to self.options on line 222 of the dispatch-conf script, which is the last line quoted in that stack trace you posted ("os.system((DIFF_CONTENTS .... ))").

hth...

Thanks That seems to have solved the problems for me. I didn't rebuild portage though, this edit is easier.

[chrisstankevitz]

I get this error trying to run dispatch-conf:

Code: Select all

Traceback (most recent call last):
  File "/usr/sbin/dispatch-conf", line 309, in ?
    d.grind (portage.settings ['CONFIG_PROTECT'])
  File "/usr/sbin/dispatch-conf", line 145, in grind
    confs = filter (f, confs)
  File "/usr/sbin/dispatch-conf", line 135, in f
    self.replace(newconf, conf['current'])
  File "/usr/sbin/dispatch-conf", line 222, in replace
    os.system((DIFF_CONTENTS % (curconf, newconf)) + '>>' + self.config["log-file"])
AttributeError: dispatch instance has no attribute 'config'

Anyone have an idea?

yep. this was a bug in the last portage update that has been fixed. re-emerge portage and it should start working again. there's a bugzilla number for it but i'm way too lazy tonite to look it up.

Why was it fixed in such a way as to require a remerge?

Couldn't the gentoo developers fix it in such a way that regular "emerge -Dauv world" updating would automatically fix it?

Just curious,

Chris

[agnitio]

I am also having problems with dispatch-conf ouputting garbage into config-files. Is there any workaround for this?

[mphilips]

When I press "e" to open the newly merged file in my preferred editor I get:

Code: Select all

Traceback (most recent call last):
  File "/usr/sbin//dispatch-conf", line 309, in ?
    d.grind (portage.settings ['CONFIG_PROTECT'])
  File "/usr/sbin//dispatch-conf", line 200, in grind
    os.system(os.environ['EDITOR'] + ' ' + newconf)
  File "/usr/lib/python2.3/UserDict.py", line 19, in __getitem__
    def __getitem__(self, key): return self.data[key]
KeyError: 'EDITOR'

[rhill]

what does

Code: Select all

echo $EDITOR

turn up and can you run that from the command line?

[mphilips]

what does

Code: Select all

echo $EDITOR

turn up and can you run that from the command line?

Code: Select all

/bin/nano

and yes

[gmtl3]

According to the make.conf man page, I can set CONFIG_PROTECT_MASK to a space delimeted list of directories that you want to exempt from config file protection. Here's mine:

Code: Select all

CONFIG_PROTECT_MASK="/usr/X11R6"

So, how come dispatch-conf is still asking me about updating files under /usr/X11R6/lib/*?

[mphilips]

one thing I miss from etc-update is the list of files that need to be modified. I know which files on my system I have modified, and so I would change those and then just scan the list of files one more time and then have etc-update nuke/update all the rest of the files.

I agree, it should at least be an menu option.

[gmtl3]

According to the make.conf man page, I can set CONFIG_PROTECT_MASK to a space delimeted list of directories that you want to exempt from config file protection. Here's mine:

Code: Select all

CONFIG_PROTECT_MASK="/usr/X11R6"

So, how come dispatch-conf is still asking me about updating files under /usr/X11R6/lib/*?

I stole the first bit of code from dispatch-conf and modified it like so

Code: Select all

#!/usr/bin/python -O

#
# dispatch-conf-debug-CONFIG_PROTECT_MASK
#       - figure out why dispatch-conf ingores CONFIG_PROTECT_MASK
#
#  Jeremy Wohl (http://igmus.org)
#
#

from stat import *
from random import *
import os, shutil, sys, string, re, commands, atexit
sys.path = ["/usr/lib/portage/pym"]+sys.path

import portage, dispatch_conf

print portage.settings ['CONFIG_PROTECT_MASK']

Here's the output:

Code: Select all

$ ./cfgProtMaskTest
/etc/gconf /etc/terminfo /usr/X11R6/lib /etc/env.d
$

"/usr/X11R6/lib" is what I had CONFIG_PROTECT_MASK set to in /etc/make.conf. Still not sure why the config files under that subdir weren't auto updated when I ran dispatch-conf.

[tecknojunky]

Can someone please explain the differences between etc-update and dispatch-conf? I've hosed my box using etc-update and I really don't want to do that again. The best way to not screw something up is understanding how it works...

Yup. You can hose your system just as easyly with dispatch-conf.

[vanten]

BTW:

Now edit /etc/dispatc-conf.conf to your liking.

Should be /etc/dispatch-conf.conf
But perhaps everyone allready seen that

[mallchin]

Nothing like dragging up an old topic

[bvrom]

My / (root) partition is getting too full and I'm seeing where I can delete some data. My /etc/config-archive (dispatche-conf's archive that is) has become quite big. Is it safe to remove the contents of this directory? I know my current config files are OK and I have made backups before, so there is currently no need to revert to older /etc files. The manpage and wiki page don't seem to give any info on this.

[bmichaelsen]

I'm totally confused by the output that I am given. So if I know that I have edited the config file what do I do. The - and + everywhere are confuzling the newby.

Can someone please explain the differences between etc-update and dispatch-conf? I've hosed my box using etc-update and I really don't want to do that again. The best way to not screw something up is understanding how it works...

Yup. You can hose your system just as easyly with dispatch-conf.[/quote]
Maybe you guys want to have a look at etc-proposals, it has a built-in help system and although its pretty new, its already in the gentoo sunrise overlay.

[bmichaelsen]

My / (root) partition is getting too full and I'm seeing where I can delete some data. My /etc/config-archive (dispatche-conf's archive that is) has become quite big. Is it safe to remove the contents of this directory? I know my current config files are OK and I have made backups before, so there is currently no need to revert to older /etc files. The manpage and wiki page don't seem to give any info on this.

Its save.