On Tuesday 09 September 2008 14:53:16 Eugene V. Lyubimkin wrote:
> Ben Finney wrote:
[snip]
> > Only by getting the package and unpacking it (as I'm sure you know,
> > the package can be unpacked and inspected without installing it).
>
> Both these methods require:
> 1) knowledge about where to loo
Andrei Popescu wrote:
> On Tue,09.Sep.08, 15:53:16, Eugene V. Lyubimkin wrote:
>
> [...]
>
>> README.Debian contains notes about important changes that made in
>> Debian's variant of package for a long time of package' lifecycle.
>> NEWS.Debian is especially good for upgrading. Changelog is for
>
On Tue,09.Sep.08, 15:53:16, Eugene V. Lyubimkin wrote:
[...]
> README.Debian contains notes about important changes that made in
> Debian's variant of package for a long time of package' lifecycle.
> NEWS.Debian is especially good for upgrading. Changelog is for
> developers and geek users as it
"Eugene V. Lyubimkin" <[EMAIL PROTECTED]> writes:
> Ben Finney wrote:
> > Are you proposing that, in addition to the changelog and the
> > README.Debian and the NEWS.Debian and the package control files,
> > that there should be *yet another* place where the package
> > maintainer is expected to d
"Eugene V. Lyubimkin" <[EMAIL PROTECTED]> writes:
> (suppose) I'm a system administrator. I have received new production
> mail server. My only choice is a stable well-maintained distribution.
> Last release for RedHat contains exim 1.5.19, and Debian version is
> 1.5.18. I know about recently fo
Ben Finney wrote:
> "Eugene V. Lyubimkin" <[EMAIL PROTECTED]> writes:
[snip]
But how can users know about this changes in Debian packages?
>>> By the existing README.Debian and NEWS.Debian conventions (for
>>> persistent and version-sensitive changes, respectively).
>>>
>> Have non-Debian user
Neil Williams wrote:
> On Tue, 2008-09-09 at 14:57 +0300, Eugene V. Lyubimkin wrote:
>>> BTS and online changelogs linked from the PTS ?
>> For upstream, for Debian people - enough. My proposal is to make
>> user-oriented list. Long changelog entries with some inner packaging
>> info and other stuf
"Eugene V. Lyubimkin" <[EMAIL PROTECTED]> writes:
> Ben Finney wrote:
> > "Eugene V. Lyubimkin" <[EMAIL PROTECTED]> writes:
> >
> >> Many of Debian packages have a patches that fixes some important
> >> bugs which have not accepted by upstream for some reasons, some
> >> of them also contains imp
On Tue, 2008-09-09 at 14:57 +0300, Eugene V. Lyubimkin wrote:
> > BTS and online changelogs linked from the PTS ?
> For upstream, for Debian people - enough. My proposal is to make
> user-oriented list. Long changelog entries with some inner packaging
> info and other stuff and viewing dozen of pat
Neil Williams wrote:
> On Tue, 2008-09-09 at 14:33 +0300, Eugene V. Lyubimkin wrote:
>> Reinhard Tartler wrote:
[snip]
>>> http://patch-tracking.debian.net/package/ffmpeg-debian
>> Well, how can users go this site? Is it described in debian policy,
>> devreference, some user docs?
>
> It could be
On Tue, 2008-09-09 at 14:33 +0300, Eugene V. Lyubimkin wrote:
> Reinhard Tartler wrote:
> > "Eugene V. Lyubimkin" <[EMAIL PROTECTED]> writes:
> >
> >> I failed to fetch a human-readable patch info for psi in testing from
> >> patch-tracking.debian.net, for example.
> >
> > Okay, take another exam
Reinhard Tartler wrote:
> "Eugene V. Lyubimkin" <[EMAIL PROTECTED]> writes:
>
>> I failed to fetch a human-readable patch info for psi in testing from
>> patch-tracking.debian.net, for example.
>
> Okay, take another example then:
> http://patch-tracking.debian.net/package/ffmpeg-debian
Well, how
Ben Finney wrote:
> "Eugene V. Lyubimkin" <[EMAIL PROTECTED]> writes:
>
>> Many of Debian packages have a patches that fixes some important
>> bugs which have not accepted by upstream for some reasons, some of
>> them also contains improvements, Debian-specific or not.
> […]
>
>> But how can user
On Tue, Sep 09, 2008 at 08:29:00AM +0100, Matthew Johnson wrote:
> I concur. patch-tracking.debian.net is the way forward. Integrating it
> with as many other services as possible is, of course, always good
See #497410 and #498313.
Cheers.
--
Stefano Zacchiroli -*- PhD in Computer Science \ Pos
On Tue Sep 09 08:34, Reinhard Tartler wrote:
> BTH, I think the maintainer's time is way better spend with
> documententing their patches properly.
>
I concur. patch-tracking.debian.net is the way forward. Integrating it
with as many other services as possible is, of course, always good
Matt
--
"Eugene V. Lyubimkin" <[EMAIL PROTECTED]> writes:
> I failed to fetch a human-readable patch info for psi in testing from
> patch-tracking.debian.net, for example.
Okay, take another example then:
http://patch-tracking.debian.net/package/ffmpeg-debian
When looking at the individual patches, you
"Eugene V. Lyubimkin" <[EMAIL PROTECTED]> writes:
> Many of Debian packages have a patches that fixes some important
> bugs which have not accepted by upstream for some reasons, some of
> them also contains improvements, Debian-specific or not.
[…]
> But how can users know about this changes in D
Sune Vuorela wrote:
> On 2008-09-08, Eugene V. Lyubimkin <[EMAIL PROTECTED]> wrote:
>> My proposal is make the new file named, for example, debian/divergences, =
[snip]
> I think you are trying to overengineer something.
> I really prefer the documentation of debian patches in the patch itself.
>
On 2008-09-08, Eugene V. Lyubimkin <[EMAIL PROTECTED]> wrote:
> My proposal is make the new file named, for example, debian/divergences, =
> containing
> important for end users changes made in Debian package. Suggested format =
> may be the same
> we are using now to display lists in packages' lon
Hi -devel!
Many of Debian packages have a patches that fixes some important bugs which
have not
accepted by upstream for some reasons, some of them also contains improvements,
Debian-specific or not. Many maintainers in process of preparing Lenny release
cherry-picked important fixes and backport
20 matches
Mail list logo
