On Tue, Nov 01, 2005 at 10:16:35PM +, Ciaran McCreesh wrote:
> On Tue, 1 Nov 2005 22:57:13 +0100 Jan Kundr??t <[EMAIL PROTECTED]> wrote:
> | On Tuesday 01 of November 2005 19:25 Ciaran McCreesh wrote:
> | > On Tue, 1 Nov 2005 17:22:29 +0100 Jan Kundr??t <[EMAIL PROTECTED]>
> | > wrote:
> | > |
On Tue, 1 Nov 2005 22:57:13 +0100 Jan Kundrát <[EMAIL PROTECTED]> wrote:
| On Tuesday 01 of November 2005 19:25 Ciaran McCreesh wrote:
| > On Tue, 1 Nov 2005 17:22:29 +0100 Jan Kundrát <[EMAIL PROTECTED]>
| > wrote:
| > | What's wrong with XML format similar to the one that is used for
| > | our GL
On Tuesday 01 of November 2005 19:25 Ciaran McCreesh wrote:
> On Tue, 1 Nov 2005 17:22:29 +0100 Jan Kundrát <[EMAIL PROTECTED]> wrote:
> | What's wrong with XML format similar to the one that is used for our
> | GLSAs?
>
> 1. Portage does not handle XML. Portage will not handle XML in the
> near fu
On Tue, 1 Nov 2005 13:44:17 -0600
Grant Goodyear <[EMAIL PROTECTED]> wrote:
> That seems a bit unfair to me. There's a complete logging facility in
> portage CVS for a version that's probably not going to be released, but
> I believe that the logging stuff is being back-ported to the current
> ve
Okay, it seems that I should have provided many more details.
Quixote is "A simple but powerful Web development framework for Python
programmers". It's very low-level, but at the same time it's
exceedingly sane. When I added quixote to portage it was just going
through its 1.0 release. I'm stil
On Tuesday 01 November 2005 19:32, Stuart Herbert wrote:
> > > 1) Why post to forums.g.o if its on www, why would one check forums
> > > instead of www.
> > Redundancy - to get the attention of those folks that for whatever
> The users I've spoken to about our news situation have expressly stated
>
On Tue, 2005-11-01 at 19:32 +, Stuart Herbert wrote:
> On Tue, 2005-11-01 at 08:56 +0100, Wernfried Haas wrote:
> > On Mon, Oct 31, 2005 at 06:52:04PM -0500, Dan Meltzer wrote:
> > > 1) Why post to forums.g.o if its on www, why would one check forums
> > > instead of www.
> > Redundancy - to ge
On Tuesday 01 November 2005 19:49, Ciaran McCreesh wrote:
> How about "unmaintained and in need of version bumps that no-one is
> going to do"?
Depends on the need. Debian is able to cope with old versions of software
without problems.
If there are no outstanding bugs about the package, a need of
Andrej Kacian wrote: [Tue Nov 01 2005, 01:20:54PM CST]
> > Separate issue. That one's the whole elog thing.
>
> Yes, it is a separate issue, but it's an issue that's been around for far too
> long, and seems to be ignored, despite the apparent importance of emerge
> messages for users.
That seems
Andrej Kacian wrote:
On Tue, 1 Nov 2005 18:18:55 +
Ciaran McCreesh <[EMAIL PROTECTED]> wrote:
| Before this, make pre-install and post-install emerge messages more
| usable, instead of having them lost among thousands of gibberish text
| in batch emerges.
Separate issue. That one's the
Thanks for this. Even if nothing comes of it, I appreciate the help!
Best regards,
Stu
--
On Tue, 2005-11-01 at 01:51 +, Ciaran McCreesh wrote:
> The attached GLEP is a draft proposal for the emerge --news thing that's
> been under discussion. There are still some TODO items. These are calls
On Thu, 2005-09-22 at 16:33 -0400, Daniel Gryniewicz wrote:
> Hi, all.
>
> app-admin/gwcc has security issues, and has been unmaintained upstream
> for 3 years. The Gnome herd is no longer interested in maintaining it.
> I've masked it, and will remove it in a couple of weeks, if no one steps
> f
On Tue, 2005-11-01 at 08:56 +0100, Wernfried Haas wrote:
> On Mon, Oct 31, 2005 at 06:52:04PM -0500, Dan Meltzer wrote:
> > 1) Why post to forums.g.o if its on www, why would one check forums
> > instead of www.
> Redundancy - to get the attention of those folks that for whatever
> reason visit the
On Tue, 1 Nov 2005 18:18:55 +
Ciaran McCreesh <[EMAIL PROTECTED]> wrote:
> | Before this, make pre-install and post-install emerge messages more
> | usable, instead of having them lost among thousands of gibberish text
> | in batch emerges.
>
> Separate issue. That one's the whole elog thing.
On Tue, 1 Nov 2005 12:43:16 -0500 Jon Portnoy <[EMAIL PROTECTED]> wrote:
| However, going around removing things simply because they're
| unmaintained is no good. Unmaintained and broken is a different story.
How about "unmaintained and in need of version bumps that no-one is
going to do"?
--
C
On Tuesday 01 November 2005 18:43, Jon Portnoy wrote:
> You are technically correct in the sense that there is literally no
> policy stating "keep unmaintained stuff in the repository."
All I wanted to say is that we have no policy about it and a fair share of
rotten ebuilds in the repository ref
On Tue, 1 Nov 2005 15:16:27 +0100 Paul de Vrieze <[EMAIL PROTECTED]>
wrote:
| I have one suggestion on an added header. I think that an Overrides:
| header should be added. This is for those messages that make a
| previous message obsolete. Say for example that an upgrade guide to
| modular X was
On Tue, 1 Nov 2005 17:22:29 +0100 Jan Kundrát <[EMAIL PROTECTED]> wrote:
| What's wrong with XML format similar to the one that is used for our
| GLSAs?
1. Portage does not handle XML. Portage will not handle XML in the
near future.
2. Many users do not have an XML parser installed.
3. The stand
On Tue, 1 Nov 2005 14:54:51 +0100 Andrej Kacian <[EMAIL PROTECTED]>
wrote:
| On Tue, 1 Nov 2005 01:51:25 +
| Ciaran McCreesh <[EMAIL PROTECTED]> wrote:
| > The attached GLEP is a draft proposal for the emerge --news thing
| > that's been under discussion. There are still some TODO items.
| > Th
On Tue, 1 Nov 2005 14:32:47 +0100 Jakub Moc <[EMAIL PROTECTED]> wrote:
| What do you mean "they aren't tied to ebuilds"? I don't really
| understand what this feature should do then, it seems. Once again,
| what's wrong with reusing emerge --changelog mechanism for displaying
| this kind of informa
1.11.2005, 18:40:35, Carsten Lohrke wrote:
> On Tuesday 01 November 2005 18:11, Jakub Moc wrote:
>> OK, lets remove perl.
> Such a reply is not an argument, but pointless. As you know as well, Perl is
> not exactly something other packages do not depend on.
As already stated by Flameeyes, we c
On Tue, Nov 01, 2005 at 06:04:08PM +0100, Carsten Lohrke wrote:
> On Monday 31 October 2005 22:44, Petteri Räty wrote:
> > Checked the bugzilla and the two open bugs seem to be version bumps. I
> > think the policy is not to remove working ebuilds from the tree although
> > they are not maintained
On Tuesday 01 November 2005 18:11, Jakub Moc wrote:
> OK, lets remove perl.
Such a reply is not an argument, but pointless. As you know as well, Perl is
not exactly something other packages do not depend on.
Carsten
pgpUegjBwwo3a.pgp
Description: PGP signature
On Monday 31 October 2005 22:44, Petteri Räty wrote:
> Checked the bugzilla and the two open bugs seem to be version bumps. I
> think the policy is not to remove working ebuilds from the tree although
> they are not maintained by anyone.
I follow Petteri's statement, I don't think we should remove
1.11.2005, 18:04:08, Carsten Lohrke wrote:
> On Monday 31 October 2005 22:44, Petteri Räty wrote:
>> Checked the bugzilla and the two open bugs seem to be version bumps. I
>> think the policy is not to remove working ebuilds from the tree although
>> they are not maintained by anyone.
> It's not
On Monday 31 October 2005 22:44, Petteri Räty wrote:
> Checked the bugzilla and the two open bugs seem to be version bumps. I
> think the policy is not to remove working ebuilds from the tree although
> they are not maintained by anyone.
It's not policy to keep unmaintained stuff in the repository
On Tuesday 01 of November 2005 02:51 Ciaran McCreesh wrote:
[...]
What's wrong with XML format similar to the one that is used for our GLSAs?
Are there any advantages in using yet-another-markup-system while we already
have some XML-parsing code in `glsa-check` which does similar job?
(IMHO arg
On Tue, 2005-11-01 at 12:26 +, Ciaran McCreesh wrote:
> On Tue, 01 Nov 2005 13:16:03 +0100 Thierry Carrez <[EMAIL PROTECTED]>
> wrote:
> | For them to know about it, they need to be warned when they do their
> | "emerge -p world" or "emerge -a mysql" that the upgrade is not as easy
> | as it se
On Tue, 2005-11-01 at 08:56 +0100, Wernfried Haas wrote:
> On Mon, Oct 31, 2005 at 06:52:04PM -0500, Dan Meltzer wrote:
> > 1) Why post to forums.g.o if its on www, why would one check forums
> > instead of www.
> Redundancy - to get the attention of those folks that for whatever
> reason visit the
On Tue, 2005-11-01 at 03:21 +, Ciaran McCreesh wrote:
> On Tue, 1 Nov 2005 12:11:37 +0900 pclouds <[EMAIL PROTECTED]> wrote:
> | Just curious how other distros deliver important news to their users?
>
> By sticking out a new "everything is incompatible" release once or
> twice a year.
Yeah, t
On Tue, 2005-11-01 at 12:11 +0900, pclouds wrote:
> Just curious how other distros deliver important news to their users?
Red Hat has you subscribe to RHN, which sends you errata based on your
installed configuration. When you add packages via up2date, Red Hat
knows.
Others just use mailing list
On Tue, Nov 01, 2005 at 02:54:51PM +0100, Andrej Kacian wrote:
> On Tue, 1 Nov 2005 01:51:25 +
> Ciaran McCreesh <[EMAIL PROTECTED]> wrote:
>
> > The attached GLEP is a draft proposal for the emerge --news thing that's
> > been under discussion. There are still some TODO items. These are calls
On Tuesday 01 November 2005 02:51, Ciaran McCreesh wrote:
> The attached GLEP is a draft proposal for the emerge --news thing
> that's been under discussion. There are still some TODO items. These
> are calls for people to weigh in with suggestions. Of course,
> suggestions on other items are good
On Tuesday 01 November 2005 13:39, Jakub Moc wrote:
> Uhm... emerge sync is a *bad* time to display upgrade messages, it's
> simply irrelevant at that time, I'm not upgrading anything at the
> moment and might not be upgrading for next week or so.
If you are not upgrading anything the news is not
1.11.2005, 13:48:06, Ciaran McCreesh wrote:
> | The messages should be displayed when I'm about to upgrade an ebuild
> | which has an upgrade note associated with the new version. Sending
> | mail via cron might be a nice optional feature for those who want to
> | use it.
> Not really a good ide
On Tue, 1 Nov 2005 01:51:25 +
Ciaran McCreesh <[EMAIL PROTECTED]> wrote:
> The attached GLEP is a draft proposal for the emerge --news thing that's
> been under discussion. There are still some TODO items. These are calls
> for people to weigh in with suggestions. Of course, suggestions on oth
On Tue, 01 Nov 2005 08:34:25 -0500 Alec Warner <[EMAIL PROTECTED]>
wrote:
| Personally, I'm for both. E-mailing cron output is a relatively
| simple operation. Adding a red flashy deal to emerge saying hey,
| package X has an unread news item, also simple as long as the
| read/unread format is no
Ciaran McCreesh wrote:
On Tue, 1 Nov 2005 13:39:24 +0100 Jakub Moc <[EMAIL PROTECTED]> wrote:
| Uhm... emerge sync is a *bad* time to display upgrade messages, it's
| simply irrelevant at that time, I'm not upgrading anything at the
| moment and might not be upgrading for next week or so.
It do
1.11.2005, 13:26:57, Ciaran McCreesh wrote:
> On Tue, 01 Nov 2005 13:16:03 +0100 Thierry Carrez <[EMAIL PROTECTED]>
> wrote:
> | For them to know about it, they need to be warned when they do their
> | "emerge -p world" or "emerge -a mysql" that the upgrade is not as easy
> | as it seems. People
On Tue, 1 Nov 2005 13:39:24 +0100 Jakub Moc <[EMAIL PROTECTED]> wrote:
| Uhm... emerge sync is a *bad* time to display upgrade messages, it's
| simply irrelevant at that time, I'm not upgrading anything at the
| moment and might not be upgrading for next week or so.
It doesn't display the messages
On Tue, 01 Nov 2005 13:16:03 +0100 Thierry Carrez <[EMAIL PROTECTED]>
wrote:
| For them to know about it, they need to be warned when they do their
| "emerge -p world" or "emerge -a mysql" that the upgrade is not as easy
| as it seems. People using a cron job to sync are probably a
| significant pa
Two things.
One, if users run --sync in a cronjob, which many do, this preemptive
goes out the window.
Two, an alternative to that, if we are all recoding portage anyways :)
Have portage place a special note next to any items with relevent
news when -a or -p is passed, and then, emerge --news ca
On Tue, 01 Nov 2005 02:21:31 -0700 Duncan <[EMAIL PROTECTED]> wrote:
| I'd suggest we preemptively incorporate an ENewsVersion or similar
| field as well, to be 1.0, with this proposal, but should the format
| ever need changed, that would allow for a format version 1.1 or 2.0
| or whatever. As th
Ciaran McCreesh wrote:
> On Tue, 01 Nov 2005 11:00:22 +0100 Thierry Carrez <[EMAIL PROTECTED]>
> wrote:
> | I'm probably missing something here. Please elaborate on how this GLEP
> | meets the "Preemptive" design goal...
>
> Simple. emerge --sync displays the "you have 12 unread news items"
> mess
maillog: 01/11/2005-11:45:08(+0100): Jakub Moc types
> 1.11.2005, 11:00:22, Thierry Carrez wrote:
>
> > Aren't those messages displayed after the damage is done ? Typical use :
>
> > - emerge --sync run as a daily cron job
> > - emerge -a mysql
> > - great, a new version is there. Typing "Yes"
>
On Tue, 01 Nov 2005 11:00:22 +0100 Thierry Carrez <[EMAIL PROTECTED]>
wrote:
| I'm probably missing something here. Please elaborate on how this GLEP
| meets the "Preemptive" design goal...
Simple. emerge --sync displays the "you have 12 unread news items"
message after it's done. The only changes
On Tue, 1 Nov 2005 09:25:34 +0100 Wernfried Haas <[EMAIL PROTECTED]>
wrote:
| On Tue, Nov 01, 2005 at 01:51:25AM +, Ciaran McCreesh wrote:
| > There is currently no explanation as to why this GLEP should be
| > chosen over ChrisWhite's 42. I will add such a section if anyone
| > requests it.
|
On Tuesday 01 November 2005 08:46, Brian Harring wrote:
> On Tue, Nov 01, 2005 at 08:36:23AM +0900, Chris White wrote:
> > Attached in plain text form is glep 42 for the discussed thread.
> > emerge --news support
> > -
> >
> > As already mentioned by Stuart, in this way users a
1.11.2005, 11:00:22, Thierry Carrez wrote:
> Aren't those messages displayed after the damage is done ? Typical use :
> - emerge --sync run as a daily cron job
> - emerge -a mysql
> - great, a new version is there. Typing "Yes"
> - system gets borken
> - emerge spits out message saying 14 files
On Tuesday 01 November 2005 02:00, Thierry Carrez wrote:
> Ciaran McCreesh wrote:
> > Notification that new relevant news items will be displayed via the
> > ``emerge`` tool in a similar way to the existing "configuration files
> > need updating" messages:
> >
> > * Important: 3 config files in
Ciaran McCreesh wrote:
> Preemptive
> Users should be told of changes *before* they break the user's system,
> not after the damage has already been done.
I think that's one of the key points...
> Notification that new relevant news items will be displayed via the
> ``emerge`` tool in a
Ciaran McCreesh posted <[EMAIL PROTECTED]>, excerpted
below, on Tue, 01 Nov 2005 01:51:25 +:
> ``Version:``
> Initially 1. Incremented every time a non-trivial change is made.
> Changes which require a re-read of the news item should instead use a
> new news item file.
Very good
On Tue, Nov 01, 2005 at 01:51:25AM +, Ciaran McCreesh wrote:
> There is currently no explanation as to why this GLEP should be chosen
> over ChrisWhite's 42. I will add such a section if anyone requests it.
Any reason why you chose bashing Chris' GLEP in another mail and start
your own instead
53 matches
Mail list logo
