You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# ATTENTION: Usually there will be only one matching filename. Most of the reason for using a for loop is unpredictable filenames, such as the apparently used "$currentKernelName_$currentKernelName" pattern, or the "$currentKernelName"'_mainline', etc, patterns.
80
+
# ATTENTION: Usually there will be only one matching filename. Most of the reason for using a for loop is unpredictable filenames, such as the apparently used "$currentKernel_version_$currentKernel_version" pattern, or the "$currentKernel_version"'_mainline', etc, patterns.
81
81
# Expected to begin in the same directory as "make deb-pkg" , Debian package files expected at '../' .
# ATTENTION: Usually there will be only one matching filename. Most of the reason for using a for loop is unpredictable filenames, such as the apparently used "$currentKernelName_$currentKernelName" pattern, or the "$currentKernelName"'_mainline', etc, patterns.
21199
+
# ATTENTION: Usually there will be only one matching filename. Most of the reason for using a for loop is unpredictable filenames, such as the apparently used "$currentKernel_version_$currentKernel_version" pattern, or the "$currentKernel_version"'_mainline', etc, patterns.
21200
21200
# Expected to begin in the same directory as "make deb-pkg" , Debian package files expected at '../' .
21201
-
for currentFile in ../linux-headers-"$currentKernelName"*.deb
21201
+
for currentFile in ../linux-headers-"$currentKernel_version"*.deb
0 commit comments