Package: wnpp
Owner: Roland Mas <[EMAIL PROTECTED]>
Severity: wishlist
* Package name: argyll
Version : 1.0.3
Upstream Author : Graeme Gill <[EMAIL PROTECTED]>
* URL or Web page : http://www.argyllcms.com/
* License : GPLv3
Description : ICC compatible color managemen
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
>
David López Zajara (Er_Maqui) wrote:
> I've tested the lenny live CD on MBP (SantaRosa model),and i have this
> problem. I'm booting with rEFIt.
sorry for the late answer: the problem is know, and already fixed.
expect newer builds with a fixed syslinux version soon.
--
Address:Daniel Ba
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
Le Tue, Sep 09, 2008 at 12:50:23PM +1000, Mark Purcell a écrit :
>
> debian-devel, is there a view, does one need README.source if you
> provide a patch target and use one of the standard patch management
> systems? Seems like this would cover 90% of use cases and add very
> little value!
Hi Mark
Package: dpkg
Version: 1.14.24
Severity: wishlist
Tags: patch
Hi,
during the emDebian meeting in Extremadura we discussed the DEB_VENDOR
variable and how we could make good use of it for emDebian
packages. While discussing it we noticed that DEB_VENDOR, CFLAGS,
CXXFLGAS, LDFLAGS,... will only be
"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
Package: wnpp
Severity: wishlist
Owner: Xavier Oswald <[EMAIL PROTECTED]>
* Package name: libclass-std-utils-perl
Version : 0.0.3
Upstream Author : Damian Conway <[EMAIL PROTECTED]>
* URL : http://search.cpan.org/dist/Class-Std-Utils/
* License : GPL
Programm
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
--
Hi!
Am 7.9.2008 schrieb "Franklin PIAT" <[EMAIL PROTECTED]>:
>I've worked on an upgrade advisor tool for Lenny. The idea is to do some
>sanity check to then warn the users of potential problems (and also
>advertise some best practices). The example below should be quite
>explicit.
Wonderfull id
21 matches
Mail list logo
