| Summary: | savedconfig.eclass prints extra slashes | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Michael Palimaka (kensington) <kensington> |
| Component: | Eclasses | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED FIXED | ||
| Severity: | trivial | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 686350 | ||
| Bug Blocks: | |||
| Attachments: | Patch | ||
Patch for bug #686350 happens to fix most of these problems. Example: * Checking existence of /etc/portage/savedconfig/x86_64-pc-linux-gnu/sys-kernel/linux-firmware-20190514 ... * Checking existence of /etc/portage/savedconfig/sys-kernel/linux-firmware-20190514 ... * Checking existence of /etc/portage/savedconfig/x86_64-pc-linux-gnu/sys-kernel/linux-firmware-20190514 ... * Checking existence of /etc/portage/savedconfig/sys-kernel/linux-firmware-20190514 ... * Checking existence of /etc/portage/savedconfig/x86_64-pc-linux-gnu/sys-kernel/linux-firmware ... * Checking existence of /etc/portage/savedconfig/sys-kernel/linux-firmware ... * Found /etc/portage/savedconfig/sys-kernel/linux-firmware * Building using saved configfile /etc/portage/savedconfig/sys-kernel/linux-firmware When no file for restoring configuration is found, then output still contains 1 path with double slash: * Checking existence of /etc/portage/savedconfig/x86_64-pc-linux-gnu/sys-kernel/linux-firmware-20190514 ... * Checking existence of /etc/portage/savedconfig/sys-kernel/linux-firmware-20190514 ... * Checking existence of /etc/portage/savedconfig/x86_64-pc-linux-gnu/sys-kernel/linux-firmware-20190514 ... * Checking existence of /etc/portage/savedconfig/sys-kernel/linux-firmware-20190514 ... * Checking existence of /etc/portage/savedconfig/x86_64-pc-linux-gnu/sys-kernel/linux-firmware ... * Checking existence of /etc/portage/savedconfig/sys-kernel/linux-firmware ... * No saved config to restore - please remove USE=savedconfig or * provide a configuration file in //etc/portage/savedconfig/sys-kernel/linux-firmware * Your config file(s) will not be used this time (Patch for bug #686348 fixes first double slash in " * Checking existence of //etc/portage/savedconfig//..." and patch for bug #686350 fixes second double slash in " * Checking existence of //etc/portage/savedconfig//...".) Created attachment 577336 [details, diff]
Patch
Should be fixed now. |
restore_config prints some extra slashes, for example, in linux-firmware: >>> Preparing source in /var/tmp/portage/sys-kernel/linux-firmware-20151207/work/linux-firmware-20151207 ... * Checking existence of //etc/portage/savedconfig//sys-kernel/linux-firmware-20151207 ... * found //etc/portage/savedconfig//sys-kernel/linux-firmware-20151207 * Building using saved configfile //etc/portage/savedconfig//sys-kernel/linux-firmware-20151207