Re: [gentoo-dev] Changelogs

2005-07-27 Thread Alec Warner
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jason Stubbs wrote: > On Wednesday 27 July 2005 11:05, Alec Warner wrote: > >>Recent discussion on this ML and on the portage-ml as well as >>#gentoo-portage regarding pkg_warn() and the basic concept behind it. >>We talked about adding new functional

Re: [gentoo-dev] Changelogs

2005-07-27 Thread Jason Stubbs
On Wednesday 27 July 2005 11:05, Alec Warner wrote: > > Recent discussion on this ML and on the portage-ml as well as > #gentoo-portage regarding pkg_warn() and the basic concept behind it. > We talked about adding new functionality, about adding a warning section > to the ebuild or to the metadat

Re: [gentoo-dev] Changelogs

2005-07-27 Thread Donnie Berkholz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alec Joseph Warner wrote: | solution is done now, in the changelog, to be viewed by users. Metadata | ideas were not liked because metadata is not versioned and the parsing | would not be easy. The metadata dtd explicitly supports versioning. It loo

Re: [gentoo-dev] Changelogs

2005-07-27 Thread Alec Joseph Warner
Maurice van der Pot wrote: On Tue, Jul 26, 2005 at 10:05:49PM -0400, Alec Warner wrote: Recent discussion on this ML and on the portage-ml as well as #gentoo-portage regarding pkg_warn() and the basic concept behind it. We talked about adding new functionality, about adding a warning section

Re: [gentoo-dev] Changelogs

2005-07-27 Thread Maurice van der Pot
On Tue, Jul 26, 2005 at 10:05:49PM -0400, Alec Warner wrote: > Recent discussion on this ML and on the portage-ml as well as > #gentoo-portage regarding pkg_warn() and the basic concept behind it. > We talked about adding new functionality, about adding a warning section > to the ebuild or to the m

Re: [gentoo-dev] app-text/pstotext in danger of becoming security masked

2005-07-27 Thread Ned Ludd
On Wed, 2005-07-27 at 11:23 +0200, Stefan Cornelius wrote: > app-text/pstotext has a serious remote vulnerability that allows to > execute arbitrary commands on a vulnerable system. It appears to be > unmaintained at the moment. > > If anyone out there is able to take this on and patch it (honest

Re: [gentoo-dev] Re: Changelogs

2005-07-27 Thread Georgi Georgiev
maillog: 27/07/2005-10:00:52(-0400): Alec Joseph Warner types > I would be very supportive of A. Just a note in the gentoo changelog > saying Warning: this upgrade could cause problems, see the project > homepage for details. +1 here -- /Georgi Georgiev / "...[Linux's] capacity to talk

Re: [gentoo-dev] Re: Changelogs

2005-07-27 Thread Jason Stubbs
On Wednesday 27 July 2005 22:19, Alec Joseph Warner wrote: > Gentoo is a distribution and there is some responsibility to provide users > upgrade paths when packages switch versions. Gentoo isn't just portage, > IMHO. Perhaps the first thing you've ever said that I've agreed with right off the b

Re: [gentoo-dev] Re: Changelogs

2005-07-27 Thread Alec Joseph Warner
Simon Stelling wrote: Alec Joseph Warner wrote: to get you upgrade information. While I can see a great benefit in putting important information into the changelog, I really can't see why portage should provide functions to read a changelog, when nearly all packages provide the same informati

Re: [gentoo-dev] Re: Changelogs

2005-07-27 Thread Simon Stelling
Alec Joseph Warner wrote: >> to get you upgrade information. While I can see a great benefit in >> putting important information into the changelog, I really can't see why >> portage should provide functions to read a changelog, when nearly all >> packages provide the same information on their home

Re: [gentoo-dev] Re: upgrade's and rc-scripts

2005-07-27 Thread Nathan L. Adams
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian D. Harring wrote: > Vapier had suggested yanking (on unmerge, not replacement) any > config_protected file that has the same md5/mtime as what it was > originally merged with. As and end-user, that would be mana from heaven. :) Nathan -B

Re: [gentoo-dev] Re: Changelogs

2005-07-27 Thread Alec Joseph Warner
Simon Stelling wrote: Hi, Duncan wrote: and see what's up, or one can visit the website and check it out there, but for such a critical part of a Gentoo machine's infrastructure, one would certainly wish for something a bit easier than either of these. Erm, is that a joke? You want an ea

Re: [gentoo-dev] Re: Changelogs

2005-07-27 Thread Alin Nastac
Michael Cummings wrote: >On Wed, 27 Jul 2005 14:13:12 +0200 >Simon Stelling <[EMAIL PROTECTED]> wrote: > > >>Please don't make portage a news reader. >> >> > >Compelling - I tend to agree. It'd be nice if some python-wise >individual(group) wrote a tool that could interact with the portage a

Re: [gentoo-dev] Re: Changelogs

2005-07-27 Thread Michael Cummings
On Wed, 27 Jul 2005 14:13:12 +0200 Simon Stelling <[EMAIL PROTECTED]> wrote: > > Please don't make portage a news reader. Compelling - I tend to agree. It'd be nice if some python-wise individual(group) wrote a tool that could interact with the portage api enough to get the update list to see wha

Re: [gentoo-dev] Re: Changelogs

2005-07-27 Thread Simon Stelling
Hi, Duncan wrote: > and see what's up, or one can visit the website and check it out there, > but for such a critical part of a Gentoo machine's infrastructure, one > would certainly wish for something a bit easier than either of these. Erm, is that a joke? You want an easier way than browsing t

Re: [gentoo-dev] Re: Changelogs

2005-07-27 Thread Michael Cummings
On Tue, 26 Jul 2005 21:16:53 -0700 Duncan <[EMAIL PROTECTED]> wrote: > > Maybe what's needed to address #2 is simply to include a separate > portage changelog file, somewhere within the tree, possibly as its own > package, or in the profiles root dir, along with the global > package.mask, and use.

[gentoo-dev] app-text/pstotext in danger of becoming security masked

2005-07-27 Thread Stefan Cornelius
app-text/pstotext has a serious remote vulnerability that allows to execute arbitrary commands on a vulnerable system. It appears to be unmaintained at the moment. If anyone out there is able to take this on and patch it (honestly, patch is small), that would be much appreciated, the bug number i