[02:11] jtaylor: sounds like a good idea, as tumbleweed said, get #ubuntu-release approval first [02:58] micahg: It's up to the SRU team now. [03:11] ScottK: this was for Quantal :) [03:11] that is if I read backscroll correctly [03:59] Oh. [03:59] In that case, Ubuntu Archive would deal with removals. [04:04] ScottK: jtaylor: oh, sorry, I was referencing hdf5, not cpuid === jacky is now known as JackyAlcine === JackyAlcine is now known as jacky [13:07] why would it need release approval? [13:08] hello all, I have a question. With regards software that requires of a library released separate with its core features [13:08] it doesn't need approval, but wouldn't hurt to let it be known that you'd like it synced before autosyncs start [13:09] does one package all that in one debian source package? [13:09] keffie_jayx: a debian source package correlates to a tarball that an upstream releases [13:10] tumbleweed: ok that would make two then [13:10] and it would make one a build dependency and dependecy of the other [13:10] good [13:10] thanks [13:10] that works [13:11] I was confused since sometimes i seee only one dsc generation multiple binary packages [13:11] that's pretty common [13:12] especially for libraries. there'll be a separate -dev package, and possibly a -tools / -bin package, possibly a -doc, etc. [13:18] thanks tumbleweed === jbicha is now known as Guest1276 === Guest1276 is now known as jbicha1 === jbicha1 is now known as jbicha_ [18:30] jtaylor: uploads before the release opens should be done with release team coordination ;) === yofel_ is now known as yofel === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away