d-i for disco uploaded but it now FTBFS because it cannot locate ca-certificate-udeb.
For some reasons, I didn't notice before hand but ca-certificates (deb)[1] is found in "main" but ca-certificates (udeb)[2] in 'Universe' and I suspect the build failure is due to the fact that the builder doesn't look in 'universe' for it, as it needs to be in 'main'
@archive-admin
Since ca-certificate is already in 'main' can we promote its udeb into 'main' as well ?
Without the need of a MIR ?
Note: We tried to rebuild ca-certificates w/ no change and see if the new udeb would be in 'main' but it remained in 'universe' so this will definitely require an archive admin manipulation.
I already pinged them on #ubuntu-release (Freenode)
d-i for disco uploaded but it now FTBFS because it cannot locate ca-certificate- udeb.
For some reasons, I didn't notice before hand but ca-certificates (deb)[1] is found in "main" but ca-certificates (udeb)[2] in 'Universe' and I suspect the build failure is due to the fact that the builder doesn't look in 'universe' for it, as it needs to be in 'main'
@archive-admin
Since ca-certificate is already in 'main' can we promote its udeb into 'main' as well ?
Without the need of a MIR ?
Note: We tried to rebuild ca-certificates w/ no change and see if the new udeb would be in 'main' but it remained in 'universe' so this will definitely require an archive admin manipulation.
I already pinged them on #ubuntu-release (Freenode)
[1] - http:// archive. ubuntu. com/ubuntu/ pool/main/ c/ca-certificat es/ archive. ubuntu. com/ubuntu/ pool/universe/ c/ca-certificat es/
[2] - http://
- Eric