On Fri, Jun 04, 2004 at 10:03:52AM -0700, Matt Brubeck wrote:
Goswin von Brederlow wrote:
If the current version in the archive is 1.1, and you upload an NMU
of 1.2, that NMU should be 1.2-0.1 (so that a maintainer upload of
1.2-1 supersedes it).
It should be 1.1-0.1 so a
On Tue, Jun 08, 2004 at 11:58:26AM +0200, Geert Stappers wrote:
On Fri, Jun 04, 2004 at 10:03:52AM -0700, Matt Brubeck wrote:
But if the NMU is a new upstream version 1.2, then the correct NMU
version is 1.2-0.1. This is in the Debian Developer's Reference:
If it is absolutely
Hello Geert,
* Geert Stappers [EMAIL PROTECTED] [2004-06-08 15:08]:
[...]
But if the NMU is a new upstream version 1.2, then the correct NMU
version is 1.2-0.1. This is in the Debian Developer's Reference:
If it is absolutely necessary for someone other than the usual main-
tainer
On Fri, Jun 04, 2004 at 10:03:52AM -0700, Matt Brubeck wrote:
Goswin von Brederlow wrote:
If the current version in the archive is 1.1, and you upload an NMU
of 1.2, that NMU should be 1.2-0.1 (so that a maintainer upload of
1.2-1 supersedes it).
It should be 1.1-0.1 so a
On Tue, Jun 08, 2004 at 11:58:26AM +0200, Geert Stappers wrote:
On Fri, Jun 04, 2004 at 10:03:52AM -0700, Matt Brubeck wrote:
But if the NMU is a new upstream version 1.2, then the correct NMU
version is 1.2-0.1. This is in the Debian Developer's Reference:
If it is absolutely
Hello Geert,
* Geert Stappers [EMAIL PROTECTED] [2004-06-08 15:08]:
[...]
But if the NMU is a new upstream version 1.2, then the correct NMU
version is 1.2-0.1. This is in the Debian Developer's Reference:
If it is absolutely necessary for someone other than the usual main-
tainer
On Thu, Jun 03, 2004 at 03:30:12PM -0700, Matt Brubeck wrote:
Geert Stappers wrote:
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
Geert Stappers wrote, Friday, June 04, 2004 7:38 AM:
On Thu, Jun 03, 2004 at 03:30:12PM -0700, Matt Brubeck wrote:
Geert Stappers wrote:
[...]
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.
I don't
Geert Stappers wrote:
Matt Brubeck wrote:
Geert Stappers wrote:
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.
I don't think this is a good idea, because those numbers are used
for non-maintainer
Adam D. Barratt [EMAIL PROTECTED] writes:
Geert Stappers wrote, Friday, June 04, 2004 7:38 AM:
On Thu, Jun 03, 2004 at 03:30:12PM -0700, Matt Brubeck wrote:
Geert Stappers wrote:
[...]
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
On Fri, 2004-06-04 at 16:57, Goswin von Brederlow wrote:
Adam D. Barratt [EMAIL PROTECTED] writes:
[...]
If the current version in the archive is 1.1, and you upload an NMU of 1.2,
that NMU should be 1.2-0.1 (so that a maintainer upload of 1.2-1 supersedes
it).
It should be 1.1-0.1 so a
Goswin von Brederlow wrote:
If the current version in the archive is 1.1, and you upload an NMU
of 1.2, that NMU should be 1.2-0.1 (so that a maintainer upload of
1.2-1 supersedes it).
It should be 1.1-0.1 so a maintainer upload of 1.2 superseeds it.
But if the NMU is a new upstream
On Thu, Jun 03, 2004 at 03:30:12PM -0700, Matt Brubeck wrote:
Geert Stappers wrote:
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
Geert Stappers wrote, Friday, June 04, 2004 7:38 AM:
On Thu, Jun 03, 2004 at 03:30:12PM -0700, Matt Brubeck wrote:
Geert Stappers wrote:
[...]
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.
I don't
Geert Stappers wrote:
Matt Brubeck wrote:
Geert Stappers wrote:
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.
I don't think this is a good idea, because those numbers are used
for non-maintainer
Adam D. Barratt [EMAIL PROTECTED] writes:
Geert Stappers wrote, Friday, June 04, 2004 7:38 AM:
On Thu, Jun 03, 2004 at 03:30:12PM -0700, Matt Brubeck wrote:
Geert Stappers wrote:
[...]
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
Goswin von Brederlow wrote:
If the current version in the archive is 1.1, and you upload an NMU
of 1.2, that NMU should be 1.2-0.1 (so that a maintainer upload of
1.2-1 supersedes it).
It should be 1.1-0.1 so a maintainer upload of 1.2 superseeds it.
But if the NMU is a new upstream
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
On Thu, Jun 03, 2004 at 08:48:55PM +0200, Remco Seesink wrote:
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
Remco Seesink wrote:
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
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
On Thu, Jun 03, 2004 at 12:09:53PM -0700, Matt Brubeck wrote:
Is there an other way to do it without having to bump the debian
version? Or is that exactly what I should do?
Yes, you should bump the debian version.
Use dpkg-buildpackage -v when uploading the package to the archive to
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
Geert Stappers wrote:
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
Hi all,
Thank you all for the suggestions. I am uploading new firebird packages
right now with this method:
or alternatively 1.0-0mentors1 (decrease debian-revision by
one, append a mentor-specific part).
I wanted to prevent confusion in main when debian revisions are missing,
and to keep the
On Fri, Jun 04, 2004 at 04:26:05AM +0200, Remco Seesink wrote:
The manpage of dput doesn't help me with that. Any suggestions how to get
firebird_1.0.3.orig.tar.gz uploaded?
-sa on dpkg-buildpackage (or debuild)
See dpkg-buildpackage(1)
--Jeroen
--
Jeroen van Wolffelaar
[EMAIL PROTECTED]
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
Remco Seesink wrote:
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
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
On Thu, Jun 03, 2004 at 12:09:53PM -0700, Matt Brubeck wrote:
Is there an other way to do it without having to bump the debian
version? Or is that exactly what I should do?
Yes, you should bump the debian version.
Use dpkg-buildpackage -v when uploading the package to the archive to
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
Geert Stappers wrote:
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
[EMAIL PROTECTED] (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
Hi all,
Thank you all for the suggestions. I am uploading new firebird packages
right now with this method:
or alternatively 1.0-0mentors1 (decrease debian-revision by
one, append a mentor-specific part).
I wanted to prevent confusion in main when debian revisions are missing,
and to keep the
34 matches
Mail list logo
