Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • aports aports
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 726
    • Issues 726
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 375
    • Merge requests 375
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • alpine
  • aportsaports
  • Issues
  • #13321

Closed
Open
Created Dec 17, 2021 by Henrik Riomar@HRioDeveloper

busybox upgrade from 1.34.1-r4 -> 1.34.1-r5 error printouts

The following is seen when upgrading Busybox from 1.34.1-r4 -> 1.34.1-r5 on edge:

(1/34) Upgrading busybox (1.34.1-r4 -> 1.34.1-r5)
Executing busybox-1.34.1-r5.post-upgrade
stat: can't stat 'usr/bin/last': No such file or directory
stat: can't stat 'usr/bin/who': No such file or directory
(2/34) Upgrading ssl_client (1.34.1-r4 -> 1.34.1-r5)

from 511351f2

-# CONFIG_WHO is not set
+CONFIG_WHO=y

-# CONFIG_LAST is not set
+CONFIG_LAST=y

Is this a common issue in our Busybox packaging when we enable new applets?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking