[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Accepted libdaemons-ruby 1.0.9-1~bpo40+1 (source all i386)

* Alexander Wirt <formorer@debian.org> [080108 05:36]:
> Micah Anderson schrieb am Tuesday, den 08. January 2008:
> > Hash: SHA1
> > 
> > Format: 1.7
> > Date: Mon,  7 Jan 2008 23:08:11 -0500
> > Source: libdaemons-ruby
> > Binary: libdaemons-ruby libdaemons-ruby1.8
> > Architecture: source all i386
> > Version: 1.0.9-1~bpo40+1
> > Distribution: etch-backports
> > Urgency: low
> > Maintainer: Filipe Lautert <filipe@icewall.org>
> > Changed-By: Micah Anderson <micah@debian.org>
> > Description: 
> >  libdaemons-ruby - Ruby daemons library
> >  libdaemons-ruby1.8 - Ruby daemons library
> > Changes: 
> >  libdaemons-ruby (1.0.9-1~bpo40+1) etch-backports; urgency=low
> >  .
> >    * Rebuild for backports.org
> Where is the changelogentry for the upload in testing? 

I guess I do not understand the instructions on the website:

	Include all changelog entries since the last version on backports.org or
	since stable if it’s the first version. 

The last version on backports.org is 1.0.8-1, the next version in
testing is 1.0.9-1, with no versions between. The above sentence from
the contribute page means to me, "Include any changelog entries after
1.0.8-1 up to 1.0.9-1", which is what I did.

However, I can see an ambiguity in those instructions, so if I read it
another way, maybe you want this to include the changelog entries
/including/ 1.0.8-1, even though they are already in backports.org, and
/also/ include the changelog entries from 1.0.9-1, and those should be
included /in/ the *.changes itself (rather than just in the
/usr/share/doc/<package>/changelog.Debian). If I am correct in
clarifying my understanding here, I would like to offer a suggested
re-wording of that requirement so it is unambigous.

> I mean that one: 
> 	libdaemons-ruby (1.0.9-1) unstable; urgency=low
> 	.
> 	[ Filipe Lautert ]
> 	* New upstream version.
> 	* Added 'Dm-Upload-Allowed: yes' field to debian/control file.
> 	.
> 	[ Paul van Tilburg ]
> 	* Added Homepage and Vcs-* fields.
> 	* Bumped standards version to 3.7.3; no changes
> 	* required.
> I really don't want to see changelogs like "Rebuild for backports.org".

I made no changes to the package, other than rebuild it in an etch
environment, had there been changes required, then I would have detailed
what changes were required. 

However, if I am reading you correctly, it seems like you would like
included in the *.changes file the package changelogs, as well as any
backports.org changes that were required to backport the package
(duplicating what is in /usr/share/doc/<package>/changelog.Debian),

Thanks for pointing this out, I would like to make sure I am doing it
correctly, and if this is clarified I'd be happy to suggest some
alternate re-wording of the instructions to make it more explicitly
clear so future people will not fail to read the proper meaning.


Attachment: signature.asc
Description: Digital signature

Reply to: