Re: How to get package in main with the same version to upgrade over a mentors.debian.net version?
stappers@stappers.nl (Geert Stappers) writes:
> On Thu, Jun 03, 2004 at 09:19:43PM +0200, Jeroen van Wolffelaar wrote:
>> On Thu, Jun 03, 2004 at 08:48:55PM +0200, Remco Seesink wrote:
>> > Hello,
>> >
>> > I am preparing an updated package with an unsolved security bug.
>> > I would like to upload it to mentors.debian.net, but when it
>> > gets uploaded to main it will have the same version number as the
>> > one on mentors. I would to know if there is a way to upload to
>> > mentors and be sure it gets upgraded when it enters main.
>> >
>> > I had this problem before, but now it is worse because of the security
>> > bug.
>> >
>> > I looked at the policy and the reverse problem seems to be solved
>> > by using epochs. An negative epoch is not the way right? And how do
>> > I apply an epoch? Yada complains when I try to put an Version: field
>> > somewhere.
>> >
>> > Is there an other way to do it without having to bump the debian version?
>> > Or is that exactly what I should do?
>>
>> The proper way is to simply not upload to mentors.d.n with 'official'
>> debian revision numbers. Assuming the offical version will be 1.0-1, use
>> for example 1.0-1~mentors1 (if mentors.d.n accepts ~ in version
>> numbers), or alternatively 1.0-0mentors1 (decrease debian-revision by
>> one, append a mentor-specific part).
>
> Gee, I real need to find back that document that wrote to use
>
> 1.0-0.1, 1.0-0.2, 1.0-0.3 etc for non official debian packages.
That would be a NMU of a non native debian package.
1.0-0.0.1 would be a recompile binary only NMU of a non-native debian
package.
See policy.
1.0-0.0.0.1 would be free but 1.0-0mentors1 or 1.0-1~mentors is nicer.
MfG
Goswin
Reply to: