Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D debexpo
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 42
    • Issues 42
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mentors.debian.net
  • debexpo
  • Issues
  • #58
Closed
Open
Issue created Apr 18, 2019 by Baptiste Beauplat@lyknodeOwner

Should mentors automatically close RFS

It is said on mentors site that:

After you uploaded a package, please close the bug report by sending a mail to nnn-done@bugs.debian.org

So the responsibility to close a RFS is to the DD who uploaded the package.

Currently, a few DD cleanup RFS (manually or with scripts).

Should mentors do this automatically upon removal from mentors? If so, would it cover all removal cases.

Identified removal cases:

  • User removal
  • Admin removal
  • Manual removal (from the server)
  • Automatic removal when uploaded
  • Automatic removal when too old
  • ...
Edited Apr 18, 2019 by Baptiste Beauplat
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking