En réponse à Sven LUTHER <[EMAIL PROTECTED]>: > > Well, no. It is quite different here. I do build a > > libconfigwin-ocaml-dev package from the cameleon source > > and such a package already exist in the > > archive and is built from the configwin source. > > But if you don't release a newer version of configwin, then > there will be the older version of it compiled from configwin, and a > newer version of it compiled from cameleon. > > > I don't think you can have two packages with the same name > > but provided by different source package. Am I wrong? > > Well, my guessing, is that nothing in the pool itself will block it, > since it is not two package with the same version and the same name, > but > there may be a problem with the override file.
I'm pretty sure that katie would reject it because the pool is managed through a database indexed by (at least) package name. > And what do you want to do, ask for its removal, and put it in a > staging > area while it is removed, and then only upload it ? Yes, that's what we planned. > I would upload it and ask for the removal of the old configwin, and > let > the ftp-master (or whoever is in charge of that) do they work. No need > to muddle the water more with uploading to a staging area. > > (That said, you can do all that and upload to a staging area all the > same). I also want to ensure everything works fine before uploading: people will be able to test and report remaining bugs. Cheers, -------------- Jérôme Marant <[EMAIL PROTECTED]>
