Re: Bug#667589: Do we build metapackages for wheezy?
Hi,
I just uploaded Debian Med and Debian Science packages since octave
progressed to testing. I *could* upload Debian Edu packages as well and
as I told you a lot of work should be done on these packages anyway.
However, as I told you in this thread, it is not really clear to me how
exactly you want to proceed. Please clarify how this should be handled
for the different releases and let me know this plan or just find a
volunteer who is doing the needed steps in the tasks (which is basically
a "s/octave3\.2/octave/" and "make dist").
Kind regards
Andreas.
On Thu, Apr 05, 2012 at 11:57:03PM +0200, Andreas Tille wrote:
> On Thu, Apr 05, 2012 at 11:06:57PM +0200, Mike Gabriel wrote:
> > >In the mean time please provide patches to BTS and tag the reports
> > >patch.
>
> I do not see a real advantage to do the extra effort to create patches
> if it is clear that nobody else than people who are using the Vcs
> (whatever it is or might be) will finally apply the patch and upload.
>
> > My suggestion would be... Leave SVN for squeeze, do not commit
> > wheezy changes there. Let us migrate SVN to Git and work on wheezy
> > via Git.
>
> Fine for me. Alternatively we could decide to maintain debian-edu
> metapackages (tasks files) in the Blends SVN where all other tasks
> files are residing (but this definitely does not solve your problem
> to support different releases at the same time - so probably Git is
> the better idea.)
>
> Kind regards
>
> Andreas.
--
http://fam-tille.de
Reply to: