Bug#753487: RFS: stda/1.3.1-1 -- new upstream release (package already in Debian)
Hi,
On Tue, 26 Aug 2014, Eriberto wrote:
Hi,
I saw you made a new revision (-2) of your package. However, the
1.3.1-1 not exist in Debian. So you must change 'unstable' by
'UNRELEASED' in d/changelog when saying about 1.3.1-1.
Done.
Well, but a short description is not a complete sentence, why should one put
a dot there? In my opinion it should stay as it is - see for example: [1]
http://sources.debian.net/src/tcputils/0.6.2-9/debian/control/
[2] http://sources.debian.net/src/cutils/1.6-3.1/debian/control/
Or maybe a semicolon ';' can be put at the end..
It is a rule of writting, a suggestion, not a Debian rule. You can use
semicolon too. Note that have several issues in several packages in
Done - I put a semicolon.
Debian. So, I can use them to justify all problems in a package. Sorry
but my intent is help you to release a package with good conditions.
Yes, and that's wath I respect much.
Ok, how about hosting a repository of the stda-package on Alioth within the
collab-maint project: would you like to support this? Otherwise I'll create
a git-repository within the GNU Savannah's hosting service - what do you
think?
Yes, I can be your advocate to get access to collab-maint. But you can
use an external service too.
Starting to use external GIT repository means that I need to change my
work flow and to integrate the .git-tree in my present source-tree (also
adjusting Makefile, etc) and how to structure the branches and tags before
pushing changes. So, I'm currently tying to find out what is a common way
to do so when preparing a debian package (e.g. [1]). If you know some
documentation describing the standard procedures or good practices, this
will be very helpful.
[1] http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.html
Cheers,
Eriberto
A new package is uploaded:
dget -x http://mentors.debian.net/debian/pool/main/s/stda/stda_1.3.1-2.dsc
Thanks,
Dimitar
Reply to: