Re: how to manage d/changelog for updated but not yet sponsored package
* Ben Finney ben+deb...@benfinney.id.au, 2012-02-13, 13:40: I want to keep trace of it in the d/changelog by keeping my first version entry and adding a second entry. Can I do that ? Will it confuse some Debian robots ? It's fine. I consider uploading the package to ‘mentors.debian.net’ a release of the package, since at that point interested people (e.g. reviewers) can rely on it, and the version should refer uniquely to what I uploaded at that time. Be aware, though, that some people disagree (on the grounds that it's not a new version until it enters Debian). I believe that vast majority of sponsors disagree. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120213105345.ga2...@jwilk.net
Re: how to manage d/changelog for updated but not yet sponsored package
Le Mon, Feb 13, 2012 at 11:53:45AM +0100, Jakub Wilk a écrit : * Ben Finney ben+deb...@benfinney.id.au, 2012-02-13, 13:40: I want to keep trace of it in the d/changelog by keeping my first version entry and adding a second entry. Can I do that ? Will it confuse some Debian robots ? It's fine. I consider uploading the package to ‘mentors.debian.net’ a release of the package, since at that point interested people (e.g. reviewers) can rely on it, and the version should refer uniquely to what I uploaded at that time. Be aware, though, that some people disagree (on the grounds that it's not a new version until it enters Debian). I believe that vast majority of sponsors disagree. Note however that the FTP team does not reject such packages. I tend to keep the changelog entries of packages that have been released outside Debian for the public. However, I revert all previous “unstable” entries to “UNRELEASED” to clearly mark that these packages were not in the Debian archive. Have a nice day, Cheers, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120213110711.gd25...@falafel.plessy.net
Re: how to manage d/changelog for updated but not yet sponsored package
Jakub Wilk jw...@debian.org writes:
* Ben Finney ben+deb...@benfinney.id.au, 2012-02-13, 13:40:
I want to keep trace of it in the d/changelog by keeping my first
version entry and adding a second entry. Can I do that ? Will it
confuse some Debian robots ?
It's fine. I consider uploading the package to ‘mentors.debian.net’
a release of the package, since at that point interested people
(e.g. reviewers) can rely on it, and the version should refer
uniquely to what I uploaded at that time.
Be aware, though, that some people disagree (on the grounds that
it's not a new version until it enters Debian).
I believe that vast majority of sponsors disagree.
Personally, I like the middleground best (though, I haven't been
practicsing this yet, but this is how things would work in my ideal
world): upload to mentors.d.n with incremental versions (when it makes
sense; if the reviewer/potential sponsor spots a bug in a version not
announced, that version is safe to resue as far as I'm concerned), but
fold it into one entry when uploading to Debian proper.
${VERSION}-${N}~mentors${X} for mentors, ${VERSION}-${N} for Debian
proper. A little more work on both sides, but we get the best of both
worlds with as little of the worst as possible.
--
|8]
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87sjifgcao.fsf@algernon.balabit
Re: how to manage d/changelog for updated but not yet sponsored package
Hi,
Personally, I like the middleground best (though, I haven't been
practicsing this yet, but this is how things would work in my ideal
world): upload to mentors.d.n with incremental versions (when it makes
sense; if the reviewer/potential sponsor spots a bug in a version not
announced, that version is safe to resue as far as I'm concerned), but
fold it into one entry when uploading to Debian proper.
${VERSION}-${N}~mentors${X} for mentors, ${VERSION}-${N} for Debian
proper. A little more work on both sides, but we get the best of both
worlds with as little of the worst as possible.
VCS repo is very helpful in this case. It eliminates the need to increment
the version of the package. And change log will show real history of package
versions in Debian archive.
Best regards,
Boris
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/771741329135...@web12.yandex.ru
Re: how to manage d/changelog for updated but not yet sponsored package
On 02/13/2012 07:14 AM, Gergely Nagy wrote:
${VERSION}-${N}~mentors${X} for mentors, ${VERSION}-${N} for Debian
proper. A little more work on both sides, but we get the best of both
worlds with as little of the worst as possible.
+1
--
Stephen M. Webb stephen.w...@bregmasoft.ca
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f39019d.20...@bregmasoft.ca
Re: how to manage d/changelog for updated but not yet sponsored package
Boris Pek tehnic...@yandex.ru writes:
Hi,
Personally, I like the middleground best (though, I haven't been
practicsing this yet, but this is how things would work in my ideal
world): upload to mentors.d.n with incremental versions (when it makes
sense; if the reviewer/potential sponsor spots a bug in a version not
announced, that version is safe to resue as far as I'm concerned), but
fold it into one entry when uploading to Debian proper.
${VERSION}-${N}~mentors${X} for mentors, ${VERSION}-${N} for Debian
proper. A little more work on both sides, but we get the best of both
worlds with as little of the worst as possible.
VCS repo is very helpful in this case. It eliminates the need to increment
the version of the package. And change log will show real history of package
versions in Debian archive.
Depends on the situation. If it's a quick update, and I can followup
within moments, then indeed, there is no reason to increment the version
(see my when it makes sense comment above).
But if hours, or even days can pass between iterations, then I much
prefer a new version on mentors. That also has the advantage of me not
neccessarily being a bottle neck, and another sponsor can review it and
perhaps sponsor it too.
--
|8]
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87obt2hpyz.fsf@algernon.balabit
Re: how to manage d/changelog for updated but not yet sponsored package
Le 13/02/2012 à 13:14, Gergely Nagy alger...@balabit.hu écrivit :
${VERSION}-${N}~mentors${X} for mentors, ${VERSION}-${N} for Debian
proper. A little more work on both sides, but we get the best of both
worlds with as little of the worst as possible.
Hi,
This scheme is something I was thinking about doing automatically for
mentors (i.e. upload ${VERSION}-${N}, but get back ${VERSION}-${N}~mentors${X}).
This would avoid the current clobbering of files from one upload to the
other, and would allow us to present diffs between subsequent uploads of
the packages.
Cheers,
--
Nicolas Dandrimont
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87wr7qc3hz@poincare.home.olasd.eu
Re: how to manage d/changelog for updated but not yet sponsored package
Depends on the situation. If it's a quick update, and I can followup within moments, then indeed, there is no reason to increment the version (see my when it makes sense comment above). But if hours, or even days can pass between iterations, then I much prefer a new version on mentors. That also has the advantage of me not neccessarily being a bottle neck, and another sponsor can review it and perhaps sponsor it too. Hmm, another sponsor also could look at commits in VSC to observe changes since last message. Isn't it? Best regards, Boris -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/793591329137...@web12.yandex.ru
Re: how to manage d/changelog for updated but not yet sponsored package
Boris Pek tehnic...@yandex.ru writes: Depends on the situation. If it's a quick update, and I can followup within moments, then indeed, there is no reason to increment the version (see my when it makes sense comment above). But if hours, or even days can pass between iterations, then I much prefer a new version on mentors. That also has the advantage of me not neccessarily being a bottle neck, and another sponsor can review it and perhaps sponsor it too. Hmm, another sponsor also could look at commits in VSC to observe changes since last message. Isn't it? Yeah, if they're willing to do that. Personally, I'd rather use mentors.d.n, than a random $VCS repo (even if that repo is under .d.o), because I'm not interested in installing a new VCS, figuring out where the repo is (ok, its in the mail, and in the VCS-* fields, but it's easier to paste a package name than a repo URI, and if I have access to the VCS-* fields, then I have the sources anyway). I'll look at VCS repos if and when I'm already reviewing a package, and am in contact with the maintainer. But if I'm looking at something new, that I haven't looked at before, I find mentors.d.n more convenient, and I won't check it's VCS repo (if any). -- |8] -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87aa4mhlt1.fsf@algernon.balabit
Re: how to manage d/changelog for updated but not yet sponsored package
Nicolas Dandrimont nicolas.dandrim...@crans.org writes:
Le 13/02/2012 à 13:14, Gergely Nagy alger...@balabit.hu écrivit :
${VERSION}-${N}~mentors${X} for mentors, ${VERSION}-${N} for Debian
proper. A little more work on both sides, but we get the best of both
worlds with as little of the worst as possible.
Hi,
This scheme is something I was thinking about doing automatically for
mentors (i.e. upload ${VERSION}-${N}, but get back
${VERSION}-${N}~mentors${X}).
This would avoid the current clobbering of files from one upload to the
other, and would allow us to present diffs between subsequent uploads of
the packages.
I don't think that's a good idea. My wish with the ~mentors${X} would be
that it's used intentionally, when the maintainer changes something, and
uploads a new version, that gets a new changelog entry.
You can't automate this reliably.
To illustrate, here's a changelog snippet meant for mentors:
my-little-pony (1.0-1~mentors2) unstable; urgency=low
* Use debhelper (= 9) to gain hardened build flags for free.
-- Pony Herder stablemas...@example.org Tue, 07 Feb 2012 10:00:00 +0100
my-little-pony (1.0-1~mentors1) unstable; urgency=low
* Initial upload (Closes: #PONIES)
-- Pony Herder stablemas...@example.org Mon, 06 Feb 2012 14:00:00 +0100
This makes it clear what changed between ~mentors1 and ~mentors2. But
~mentors2 is fairly pointless when uploading to Debian, so this would
get flattened into:
my-little-pony (1.0-1) unstable; urgency=low
* Initial upload (Closes: #PONIES)
-- Pony Herder stablemas...@example.org Tue, 07 Feb 2012 10:00:00 +0100
If you'd automatically turn 1.0-1 into 1.0-1~mentors${X}, you'd have to
do some changelog diffing and altering. That's not going to work.
Plus, it would also prevent the sponsors from building uploading the
maintainer prepared package without modifications. As a sponsor, I don't
want to modify packages I upload, I will review them, suggest or request
modifications, and let the maintainer do it, update my sources, and work
from there. Automatically munging the version would make this
impossible, or at least very inconvenient.
--
|8]
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/8762fahlec.fsf@algernon.balabit
Re: how to manage d/changelog for updated but not yet sponsored package
* Charles Plessy ple...@debian.org, 2012-02-13, 20:07: I consider uploading the package to ‘mentors.debian.net’ a release of the package, since at that point interested people (e.g. reviewers) can rely on it, and the version should refer uniquely to what I uploaded at that time. Be aware, though, that some people disagree (on the grounds that it's not a new version until it enters Debian). I believe that vast majority of sponsors disagree. Note however that the FTP team does not reject such packages. What kind of argument is that? -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120213223622.gb1...@jwilk.net
how to manage d/changelog for updated but not yet sponsored package
Hello List: I am on the edge to put on m.d.n an updated version of one of my not yet sponsored packages: since between the two versions the upstream maintainer kindly integrated some patches that I submitted to him as Debian patches, I want to keep trace of it in the d/changelog by keeping my first version entry and adding a second entry. Can I do that ? Will it confuse some Debian robots ? Thanks in advance, Jerome -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f385be6.20...@rezozer.net
Re: how to manage d/changelog for updated but not yet sponsored package
Jerome BENOIT g62993...@rezozer.net writes: I want to keep trace of it in the d/changelog by keeping my first version entry and adding a second entry. Can I do that ? Will it confuse some Debian robots ? It's fine. I consider uploading the package to ‘mentors.debian.net’ a release of the package, since at that point interested people (e.g. reviewers) can rely on it, and the version should refer uniquely to what I uploaded at that time. Be aware, though, that some people disagree (on the grounds that it's not a new version until it enters Debian). So I'd say: after you've uploaded a version, keep things clear. Make a new version in ‘debian/changelog’ when you're preparing a new upload. -- \ “Contentment is a pearl of great price, and whosoever procures | `\it at the expense of ten thousand desires makes a wise and | _o__) happy purchase.” —J. Balguy | Ben Finney -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87y5s71mnm@benfinney.id.au
