Your message dated Sun, 27 Nov 2011 14:45:58 +0400 with message-id <[email protected]> and subject line Re: Bug#650159: busybox: Please set CONFIG_DEFAULT_MODULES_DIR and CONFIG_DEFAULT_DEPMOD_FILE to the appropriate defaults has caused the Debian Bug report #650159, regarding busybox: Please set CONFIG_DEFAULT_MODULES_DIR and CONFIG_DEFAULT_DEPMOD_FILE to the appropriate defaults to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 650159: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650159 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: busybox Version: 1:1.19.3-3 Severity: normal The default config has CONFIG_DEFAULT_MODULES_DIR and CONFIG_DEFAULT_DEPMOD_FILE set to empty strings (in /debian/config/pkg/{deb,static}) to enable automatic build process. They should be rather set to "/lib/modules", respectively "modules.dep", which are the defaults when asked to define them while building with them not defined. This seems to not affect the package itself because those symbols are only used below modutils/ dir which does not build objects in the default configuration. But rebuilding the package with modutils enabled currently yields defunct modprobe / depmod executables for instance.
--- End Message ---
--- Begin Message ---On 27.11.2011 08:25, Jens Stimpfle wrote: > Package: busybox > Version: 1:1.19.3-3 > Severity: normal > > > The default config has CONFIG_DEFAULT_MODULES_DIR and > CONFIG_DEFAULT_DEPMOD_FILE set to empty strings (in > /debian/config/pkg/{deb,static}) to enable automatic build process. They > should be rather set to "/lib/modules", respectively "modules.dep", > which are the defaults when asked to define them while building with > them not defined. > > This seems to not affect the package itself because those symbols are > only used below modutils/ dir which does not build objects in the > default configuration. But rebuilding the package with modutils enabled > currently yields defunct modprobe / depmod executables for instance. These symbols can not be defined without enabling module utils, which are not enabled. So the request can't be satisfied. Hence closing the bug. Thanks, /mjt
--- End Message ---
