The Backports team doesn't have any control over the actual Backports repository's administration on archive.ubuntu.com....
Though I'd like to know why a blank Backports repo can't be made for Breezy to ease the migration pain.
At first, it was reported that Dapper might open <72hrs after
Breezy's release, so I didn't think this was a big concern. However,
more than a week has past, and now I'm growing more and more concerned
about the issue.
mdz, any word on how long it'll be before we start seeing Breezy-backports repositories?
On 10/26/05, Matthew East <
mdke@xxxxxxxxxx> wrote:On Wed, 2005-10-26 at 06:27 -0400, John Dong wrote:
> Mez and I were told that breezy-backports would be created when Dapper
> opens...
Argh, that is painful. Ok we will make sure that is documented for
dapper-backports when the time comes. I'm seeing so many complaints
about this!
Matt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQBDX1vetSaF0w5rBv8RAl5yAJ47Q3kFv53qjj2tmvPmy7XPjdTkGACffP4N
FGvmGqHc2A//Lokr3AlKIPo=
=nt0+
-----END PGP SIGNATURE-----
--
ubuntu-backports mailing list
ubuntu-backports@xxxxxxxxxxxxxxxx
http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
--
ubuntu-backports mailing list
ubuntu-backports@xxxxxxxxxxxxxxxx
http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
|
