| 1 |
Alec Warner <antarus@g.o> posted 44D0F2E7.3060409@g.o, |
| 2 |
excerpted below, on Wed, 02 Aug 2006 18:45:59 +0000: |
| 3 |
|
| 4 |
> Enrico Weigelt wrote: |
| 5 |
>> * Petteri R?ty <betelgeuse@g.o> schrieb: |
| 6 |
>>> dev-java/saxon-bin is going to be removed from the tree as soon as the |
| 7 |
>>> from sources version dev-java/saxon gets marked stable on arches that |
| 8 |
>>> have saxon-bin stable. I will add a package move and a revision bump so |
| 9 |
>>> that user will have a smooth upgrade. I will also adjust app-text/jing |
| 10 |
>>> to work with the from sources version. |
| 11 |
>> |
| 12 |
>> Are such things also announced separately on some user list ? |
| 13 |
>> The problem I see: from the view of an common user (who's not |
| 14 |
>> reading the dev lists) packages they're using suddenly disappear. |
| 15 |
>> They don't have time to handle it properly. |
| 16 |
>> |
| 17 |
>> There should be an additional flagging (ie. scheduled for masking |
| 18 |
>> or removal), maybe such flags could be put into an separate |
| 19 |
>> database (ie. some textfile available via web or rsync). |
| 20 |
>> |
| 21 |
> |
| 22 |
> Things scheduled for removal (by treecleaners, and I hope by many) enter |
| 23 |
> pmask prior to removal; this is really the current system of notification. |
| 24 |
|
| 25 |
Just to add... 30 days is the usual package mask. As AW states, the idea |
| 26 |
of the mask is so users will have time after masking to save the masked |
| 27 |
ebuild to their overlay and/or file a bug saying they use it, as well as |
| 28 |
that it's a wake-up call for any devs, if they want it saved, to get busy |
| 29 |
and take over maintenance and start fixing the bugs that having remained |
| 30 |
unfixed for so long, got the package masked in the first place. |
| 31 |
|
| 32 |
If a user isn't syncing and updating at least once a month, well... the |
| 33 |
ebuilds and related files remain available from viewCVS, which is open to |
| 34 |
the public, so they can still be retrieved and stuck in an overlay, if |
| 35 |
necessary, and Gentoo devs can of course fix the bugs and return the |
| 36 |
ebuild to the tree, if they believe it's worth it. The files aren't gone |
| 37 |
without a trace, forever. |
| 38 |
|
| 39 |
All that said, IMO these qualify for "announcements" as much as the GLSAs |
| 40 |
normally inhabiting the announce list do. That list isn't "glsa", it's |
| 41 |
"announce" and these are announcements that could affect a number of |
| 42 |
users, so IMO they belong there as well as here. |
| 43 |
|
| 44 |
-- |
| 45 |
Duncan - List replies preferred. No HTML msgs. |
| 46 |
"Every nonfree program has a lord, a master -- |
| 47 |
and if you use the program, he is your master." Richard Stallman |
| 48 |
|
| 49 |
-- |
| 50 |
gentoo-dev@g.o mailing list |
Archives