Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • D dbscripts
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare
    • Locked Files
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arch LinuxArch Linux
  • dbscripts
  • Merge requests
  • !8

Unbreak the testsuite by supporting pacman 5.1

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Jelle van der Waa requested to merge pacman51 into master Jun 19, 2018
  • Overview 4
  • Commits 2
  • Pipelines 0
  • Changes 3

Created by: eli-schwartz

@pierres Is there a particular reason this was initially done via tmpfs?

Note that the specific error condition there will no longer be triggered by pacman 5.1.1 whenever that lands, but I still consider it sort of bad practice (plus I want to more closely mimic makechrootpkg itself). AFAICT docker creates a new container each time regardless.

If it's especially useful to ensure the /build directory is not persisted between runs (efficiency? I don't know enough about how docker works) I think it makes more sense to use makepkg --clean in the testsuite itself.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: pacman51