Re: RFS: oggfix
- To: debian-mentors@lists.debian.org
- Subject: Re: RFS: oggfix
- From: Gunter Königsmann <gunter@peterpall.de>
- Date: Tue, 06 Dec 2011 08:52:49 +0100
- Message-id: <[🔎] 4EDDC9D1.4060706@peterpall.de>
- In-reply-to: <20110627093146.GB3110@l04.local>
- References: <20101130230337.GD79388@l04.local> <4D60304A.3030708@peterpall.de> <20110501170954.GB95740@l04.local> <1304926069.26802.7.camel@localhost> <20110510100736.GI2225@l03.local> <1305049449.26579.1.camel@localhost> <20110625204559.GC1654@l04.local> <315296795.18413.1309124469090.JavaMail.open-xchange@oxltgw14.schlund.de> <20110627093146.GB3110@l04.local>
On 27.06.2011 11:31, Michael Tautschnig wrote:
Hi,
[...]
Ok, I wouldn't bother much about the above, but one thing does stop me from
uploading: why are you setting the version number in such a way that Debian is
upstream? This doesn't seem to be accurate. IMHO you should be using 0.9.1-1
as
version number!?
Never found out what the version number ought to be.
0.9.1-1 sounds exactly right. Thanks for that, too!
This is explained in full detail in the Debian Policy [1].
Hope this helps,
Michael
[1] http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version
Did try to change the version number to 0.9.1-1 - which sounded great
for a non-native debian package. But this meant running into all kinds
of warnings. (debuild claims my native package has a version number that
contains a dash!)
As far as I understand the Debian Policy states that if a package is
deemed to be "native" depends on the version number. But it seems like
there has to be another criterion, too.
Do you know what this criterion would be?
I did try to read the Policy and experimented for a long time before
another urgent project started keeping me constantly busy for months -
so this time I have to say sorry for the delay.
In the meantime parts of the Debian Policy has changed and I have
altered the package again as to no more get lintian or other warnings
except that I have the wrong version number. As soon as the version
number is fixed I can upload the package again with the new standards
version and all.
Thanks a lot,
and kind regards,
Gunter.
Reply to: