On Thu, Jul 26, 2012 at 05:06:25PM +0200, Sebastian Hilbert wrote: > svn indicates I worked on the control file six weeks ago. Apparently I forgot > to update the changelog
IMHO this was: $ svn diff -r11221:11336 Index: debian/control =================================================================== --- debian/control (Revision 11221) +++ debian/control (Revision 11336) @@ -3,7 +3,7 @@ Priority: optional Maintainer: Debian Med Packaging Team <[email protected]> DM-Upload-Allowed: yes -Uploaders: Andreas Tille <[email protected]> +Uploaders: Andreas Tille <[email protected]>, Sebastian Hilbert <[email protected]> Build-Depends: debhelper (>= 9), python (>= 2.6) Build-Depends-Indep: po-debconf Standards-Version: 3.9.3 Index: debian/changelog =================================================================== --- debian/changelog (Revision 11221) +++ debian/changelog (Revision 11336) @@ -1,3 +1,9 @@ +gnumed-server (16.16-1) unstable; urgency=low + + * New upstream version + + -- Sebastian Hilbert <[email protected]> Thu, 14 Jun 2012 15:01:58 +0200 + gnumed-server (16.15-1) unstable; urgency=low But the last change was done by me regarding the last bugfix release (16.17): ------------------------------------------------------------------------ r11472 | tille | 2012-06-25 22:51:19 +0200 (Mo, 25. Jun 2012) | 2 Zeilen New upstream bugfix release What I wanted to say is: Usually in gnumed-server upgrading the changelog entry is the *only* change which is needed - it is fine for me just doing it for 17.1 and upload to experimental as well. It would just be nice if you would confirm that there is no other change needed. > The version for experimental would be 17.1. Diff says all I did was add > myself > to the changelog (yeah) :-) I somehow suspect that you forgot a `svn commit` and you have some remaining local changes. Please note that I just commited a changelog entry as I would regard it reasonable. Please verify your local changes. > > Just uploaded. > > With regards to 1.2.1 I just noticed that that I made a mistake in the rules > file by forgetting to change the <suggests> to server version 17. It still > suggests v16 for the 1.1 clients. This would be handled as follows: dch -i ... create a new changelog entry 1.2.1-2 -> UNRELEASED and fix the debian/control file. IMHO waiting for 1.2.2 from upstream before uploading is fine because it's just experimental, but its your decision - I'm fine with uploading a fix for this. > In summary gnumed-server 17.1 can be uploaded. OK, package just builds ... > In one of the next bug fix > releases suggests should be changed as noted above. Will now go in and try to > commit a fix. So we agree that the fix has some time as I suggested above. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
