This is causing major problems: users are uncommenting the backports
repositories and getting errors because the repo is not created yet. Bumping
this up to major because it affects a large number of people. The solution (IMO)
is to create the archive but not add anything to it until dapper opens. Please
advise the Documentation team on what solution is going to be adopted for
dapper, so that we can ensure a note is present in the documentation (which
currently simply explains how to activate breezy-backports).
This is causing major problems: users are uncommenting the backports
repositories and getting errors because the repo is not created yet. Bumping
this up to major because it affects a large number of people. The solution (IMO)
is to create the archive but not add anything to it until dapper opens. Please
advise the Documentation team on what solution is going to be adopted for
dapper, so that we can ensure a note is present in the documentation (which
currently simply explains how to activate breezy-backports).