[Pkg-octave-devel] Restoring branches on octave-symbolic :-(

Thomas Weber tweber at debian.org
Tue Jan 4 22:08:53 UTC 2011

On Tue, Jan 04, 2011 at 03:45:53PM -0600, Jordi Gutiérrez Hermoso wrote:
> On 4 January 2011 15:24, Thomas Weber <tweber at debian.org> wrote:
> > On Mon, Jan 03, 2011 at 07:59:22PM -0600, Jordi Gutiérrez Hermoso wrote:
> >> On 3 January 2011 13:39, Thomas Weber <tweber at debian.org> wrote:
> >> > On Sun, Jan 02, 2011 at 10:28:36PM -0600, Jordi Gutiérrez Hermoso wrote:
> >> >> I carelessly did "git push --mirror" in the octave-symbolic repo, and
> >> >> I thought all it would do was push all of my branches. Unfortunately,
> >> >> it also removed all of the branches I hadn't clone locally. Does
> >> >> someone have them and is able to push them?
> >> >
> >> > I don't think the octave-symbolic repo had any branches other than
> >> > 'master'.
> >>
> >> It had a branch for each release. They sort of are still there,
> >> somewhere in the reflog, I think. But whatever, I guess they're not a
> >> big deal, just there for historicity purposes.
> >
> > Okay, I just updated. What we have now is the complete upstream source
> > code. I'm going to remove this now.
> Wait, wait, why?
> I worked hard to get the upstream source into the package. It's much
> nicer to work that way. 

Release-managers will *never* accept such a change so late in the
release cycle. 

> And this should close #607071. I think I'll need your intervention
> with the release managers in order to request a freeze exception in
> order to get octave-symbolic back into squeeze, at least having an
> upload ready.

There's no chance to get the package past the release team with the
current state. What you did was the correct approach during normal
development, but not right now -- we are already past the point where
pure translation updates are accepted:

Anyway, which of the four patches from SVN actually fixes the crash?


More information about the Pkg-octave-devel mailing list