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
  • #24
Closed
Open
Issue created Feb 25, 2018 by Mattia Rizzolo@mattiaOwner

loss of information should be prevented after removing a package from debexpo / debian mentors

This bug report is based on this thread originating from this post on mentors.debian.org: https://lists.debian.org/debian-mentors/2014/07/msg00300.html

Packages are automatically removed after 20 weeks. They are apparently also removed from debexpo/debian.mentors.org after the RFS bug is closed. While there are good reasons to remove old packages, the removal process is not communicated very clearly to people who use debexpo. Moreover, when old packages are removed they are removed together with sometimes valuable discussions that took place on debexpo/debian.mentors.org.

This unexpected loss of information is undesirable. In https://lists.debian.org/debian-mentors/2014/07/msg00325.html Thibaut Paumard suggests that discussions on prospective packages could be saved as comments with the respective ITP and/or RFS bugs. I support his suggestion. Could debexpo be changed in such a way that this happens automatically?

Originally reported by Guido van Steen at https://alioth.debian.org/tracker/index.php?func=detail&aid=314771&group_id=100127&atid=413115

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