Resyncing the archive with the seed lists

[Matt Zimmerman]

On Mon, Aug 15, 2005 at 10:25:42AM +0200, Martin Pitt wrote:

> Matt Zimmerman [2005-08-12 12:45 -0700]:
> >  o libdb3-util                                                           {db3}
> > 
> > 	Is this worth seeding?  We still have packages which use db3
> > 	databases.
> 
> Certainly not a big deal since the source is in main anyway.

Please seed it if you haven't already.

> >  o tdsodbc                                                           {freetds}
> > 
> > 	Its source and dependencies are already in main; should probably be
> > 	seeded.  Thoughts?
> 
> Doesn't look scary security-wise, no CANs. No objection.

Please seed if you haven't already.

> >  o ocaml-native-compilers                                              {ocaml}
> > 
> > 	Anyone know anything about ocaml?
> 
> A bit, since I maintain a package written in Ocaml, and I dealt with
> it in my university time. Ocaml programs are usually compiled into
> bytecode and are interpreted by ocaml-base, but for number crunching
> apps you can speed them up a bit by compiling it natively. Not more or
> less critical than ocaml-base, but usually bytecode is enough.

Is it worthwhile to have it in main, given that the source is already there?

> 
> >  o libpolyp0-glib2.0 libpolyp0-glib2.0-dev polypaudio polypaudio-alsa polypaudio-clients polypaudio-x11{polypaudio}
> > 
> > 	The source is in main because gst-plugins0.8 builds with
> > 	libpolyp-dev.  Should we:
> > 
> > 	- Split it?
> > 	- Seed the remaining binaries?
> > 	- Stop building polypaudio support for gstreamer?
> > 
> > 	Martin, Sebastien?
> 
> See other mail, I'd like to see polypaudio back in universe for now. A
> nonexistant upstream and some important bugs make it still
> unappropriate for main IMO.

This is still pending; who will make the necessary changes?

> >  o postgresql postgresql-client postgresql-contrib postgresql-doc {postgresql}
> > 
> > 	Martin?
> 
> We need these in Breezy for a clean Hoary->Breezy upgrade. These are
> now transition packages, postgresql moves your old db structure into
> the new cluster architecture, and the other packages are empty and
> just pull in Dependencies. They can be removed in Breezy+1 (if we
> don't support upgrades with skipping releases), and I will remove them
> in Debian after the Etch release.

There is a section in the supported seed for such packages; please add them
there.

> >  o tk8.3-dev                                                           {tk8.3}
> > 
> > 	Should probably be seeded.  Thoughts?
> 
> Hmm, new programs should probably built against tk8.4-dev?

8.3 and 8.4 aren't 100% compatible I don't think; some packages still use
8.3, and so the source is already in main.  The question is what to do about
the -dev package.

-- 
 - mdz