Your message dated Thu, 7 Jan 2010 10:23:13 +0100
with message-id <[email protected]>
and subject line Re: Bug#563164: iceweasel: debian/changelog incomplete
has caused the Debian Bug report #563164,
regarding iceweasel: debian/changelog incomplete
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
563164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563164
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: iceweasel
Severity: minor
Hi,
your debian/changelog is incomplete, a couple of 3.0.* uploads got
dropped when you uploaded 3.5.3-2 to unstable, please add them back.
Regards,
Daniel
--
Address: Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email: [email protected]
Internet: http://people.panthera-systems.net/~daniel-baumann/
--- End Message ---
--- Begin Message ---
On Thu, Dec 31, 2009 at 03:00:39PM +0100, Daniel Baumann wrote:
> Package: iceweasel
> Severity: minor
>
> Hi,
>
> your debian/changelog is incomplete, a couple of 3.0.* uploads got
> dropped when you uploaded 3.5.3-2 to unstable, please add them back.
We are maintaining packages in various branches. These branches happen
to change at some point of time (a package from unstable goes in
testing, then stable...)
The change history (log) for a given package in a given branch is
linear. But when the package switches branch, its old history may vanish:
History of s-p-u and stable-security disappear when testing becomes
stable, history of t-p-u and testing-security disappear when a package
from unstable transitions to testing.
The reason 3.0.* uploads of iceweasel vanished from the changelog is
similar: iceweasel 3.5 was first maintained in experimental. And when
pushing it to unstable, its history replaced the history of the package
in unstable. It's not different from s-p-u and stable-security history
disappearing.
I think there is no need to get in the burden of merging the changelogs,
simply because that would mean creating a fake history of changes. The
version in experimental got in its shape exactly because of the changes
that are listed in the experimental package history, not because of the
changes in the unstable package history. If changes to unstable were
also applied to experimental, they are listed in both history.
All in all, why should we care ?
Cheers,
Mike
--- End Message ---
