Bug#1057386: ITP: imsprog -- linux chip programmer for CH341a devices
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.
* commit 8fa592e6b5eaa5332580ab0b1cbe7dca766dc3dd (HEAD ->
debian/latest, origin/debian/latest)
| Author: Mikhail Medvedev <e-ink-reader@yandex.ru>
| Date: Mon Mar 25 18:33:32 2024 +0300
|
| a new version has been built
|
* commit 21f8b17153bba0472c68f14d0382f3d3d50aa0a6
| Author: Mikhail Medvedev <e-ink-reader@yandex.ru>
| Date: Mon Mar 25 16:23:43 2024 +0300
|
| Release description has been changed
|
* commit d58dc3f6be7de4b2893f5db819875803c86f769b
| Author: Mikhail Medvedev <e-ink-reader@yandex.ru>
| Date: Mon Mar 25 15:17:34 2024 +0300
|
| Modify changelog
|
* commit b9cf508be810d086dfe20a8c1fa3e62c86d02be8
|\ Merge: 347b4bc d8b79c5
| | Author: Mikhail Medvedev <e-ink-reader@yandex.ru>
| | Date: Mon Mar 25 15:14:51 2024 +0300
| |
| | Update upstream source from tag 'v1.3.3'
| |
| | Update to upstream version '1.3.3'
| | with Debian dir d492f797a1719579b5b6fe214f0a075ca9a1903a
| |
| * commit d8b79c5bfeec760c4ab857072f4fca33e8bd5c74 (tag: v1.3.3,
origin/main, origin/HEAD)
| | Author: Mikhail Medvedev <e-ink-reader@yandex.ru>
| | Date: Mon Mar 25 14:47:05 2024 +0300
| |
| | added status register form for 95xxx, 25xxx chips
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
chose to accept the package.
--
Regards
Carsten
Reply to: