Re: Please allow gnome-commander v1.2.3-1 get in for etch
On 2/27/07, Marc 'HE' Brockschmidt <he@ftwca.de> wrote:
Teodor <mteodor@Gmail.com> writes:
> I've head some problems with the current version of gnome-commander
> (1.2.0-3) from etch that seams to be fixed with the current version
> from unstable.
The changes between the gnome-commander in etch and the one in sid are
quite big. As we are in a freeze, every change to the source code is
reviewed line-by-line by the release team before allowing packages to
etch. That's simply not possible in this case. If the maintainer would
be able to provide a single patch for the issue, I would be happy to
allow this in through testing-proposed-updates, but not the complete new
upstream version.
In the changelog (and the upstream site) it can be seen that v1.2.3
was released on December 12, 2006 but none was noticed it to request a
hint for etch. No bug was reported against this version since then.
Michael, what is your opinion about this? Is it stable enough for
inclusion in etch?
gnome-commander (1.2.3-1) unstable; urgency=low
* New upstream release
-- Michael Vogt <mvo@debian.org> Tue, 12 Dec 2006 10:25:21 +0100
gnome-commander (1.2.2-1) unstable; urgency=low
* New upstream release (closes: #401228)
-- Michael Vogt <mvo@debian.org> Mon, 11 Dec 2006 09:49:10 +0100
gnome-commander (1.2.0-3.2) unstable; urgency=medium
Reply to: