Bug#916758: Accepted emacs 1:26.1+1-3.2 (source amd64 all) into unstable, unstable

2019-02-10 Thread Rob Browning
Holger Levsen writes: > On Mon, Feb 04, 2019 at 02:51:45PM +0100, Andreas Beckmann wrote: >> Holger Levsen writes: >> > I'm really not sure this is a sensible approach. Usually we try to get >> > rid off transitional packages, not to add new ones???! >> >> ... s.t. we can finally drop the tra

Bug#916758: Accepted emacs 1:26.1+1-3.2 (source amd64 all) into unstable, unstable

2019-02-09 Thread Holger Levsen
On Mon, Feb 04, 2019 at 02:51:45PM +0100, Andreas Beckmann wrote: > emacs has had a bad history (from piuparts point of view) of providing > clean upgrade paths to newer versions. All versioned emacs packages were > co-installable and there were no transitional packages provided ever to > ensure up

Bug#916758: Accepted emacs 1:26.1+1-3.2 (source amd64 all) into unstable, unstable

2019-02-04 Thread Andreas Beckmann
On 2019-02-04 12:38, Holger Levsen wrote: > in #916758 you wrote: > > --- begin --- > These were additional emacs variants available in lenny that may have > survived upgrading on a long-grown system. > > I'm doing piuparts tests simulating such long grown systems locally and > would expect to fi

Bug#916758: Accepted emacs 1:26.1+1-3.2 (source amd64 all) into unstable, unstable

2019-02-04 Thread Holger Levsen
Hi Andreas, On Mon, Feb 04, 2019 at 01:00:13AM +, Andreas Beckmann wrote: > Source: emacs > Version: 1:26.1+1-3.2 > Closes: 916758 > Changes: > emacs (1:26.1+1-3.2) unstable; urgency=medium > . >* Non-maintainer upload. > . >* Add more transitional packages for ancient versioned pac