Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
U
updater
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 35
    • Issues 35
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Turris
  • updater
  • updater
  • Issues
  • #169

Closed
Open
Opened Jan 11, 2017 by Karel Koci@kkoci🤘Owner

Read /etc/opkg/customfeeds.conf in entry.lua

Opkg can be configured with any additional repositories, in such case opkg can install software that updater doesn't know. This shouldn't be happening. For this reason we should read opkg custom feeds in entry script.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Turris OS 3.7
Milestone
Turris OS 3.7 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: turris/updater/updater#169