> Hello Mikhail, > > Am 26.03.24 um 08:37 schrieb Kosolapov Ivan: > > Hello, Carsten! > > I have built a new version of IMSProg (v1.3.3). > > Can you please tell me how I can get this version to you? Do I have to > > upload the new version on mentors.debian or do you get it from GitHub? > > I pulled the git tree from GitHub and build the package from that source. > > I can build an updated version from the same tree again. > The current entries in debian/latest looking an bit odd and chaotic. > > > Can you rebase the last tree commits into one and keep at lest the > following lines in the changelog? (Once the package is within the > archive of course such rebasing should not happen anymore. Have a look > into existing changelog entries from other files for examples how to > write the entries.) > > * New upstream release 1.3.3 > * Initial release (Closes: #1057386) > > The last entry is needed with every new upstream version that is getting > uploaded for automatic closing the ITP bug report if the FTP master
Hi, about rebase of latest tree commits into one I also think can be good, about d/changelog entries instead I'm not sure what you mean.
I suggested it here: https://github.com/bigbigmdm/IMSProg/commit/21f8b17153bba0472c68f14d0382f3d3d50aa0a6#commitcomment-140195336
Because I saw all initial packages in NEW that have uploaded multiple versions have new entry like to be treated as if they were already uploaded into the repository, or are they wrong? (I supposed are correct as are all DDs to upload)
Anyway I'm not completely sure about this since all the packages I added I always made further uploads only after they were accepted by ftp-master
OpenPGP_signature.asc
Description: OpenPGP digital signature
