PRs for manpage 'freebsd-update(8)'
This is an experimental report containing PRs for manpage 'freebsd-update(8)' as of Fri May 25 07:39:05 2012 UTC. See notes.
PRs for manpage 'freebsd-update(8)':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2012/02/06 | bin/164834 | cperciva | freebsd-update(8) does not operate on mounted system |
| o | 2012/01/15 | bin/164131 | cperciva | freebsd-update(8) does not check for failed install commands |
| o | 2012/01/05 | bin/163837 | cperciva | freebsd-update(8): i386 lastest.ssl freebsd-update file is invalid |
| o | 2011/10/13 | bin/161540 | cperciva | gzippped kernel is not updated by freebsd-update(8) |
| o | 2010/12/16 | bin/153211 | cperciva | freebsd-update(8) can not fetch updates over a proxy with mandatory authorization |
| o | 2010/12/06 | bin/152856 | cperciva | [patch] allow up to be used instead of update in freebsd-update(8) |
| o | 2010/09/02 | bin/150229 | cperciva | [PATCH] update man page of freebsd-update(8) |
| o | 2010/06/03 | bin/147430 | cperciva | freebsd-update(8) not updating /usr/src/UPDATING |
| o | 2009/11/25 | bin/140863 | cperciva | freebsd-update(8) fails to check that writes will succeed, with hilarious consequences |
| o | 2009/09/25 | bin/139135 | cperciva | freebsd-update(8) misbehaves on upgrade and shows errors. |
| o | 2009/09/18 | bin/138926 | cperciva | [patch] freebsd-update(8): allow unattended upgrade |
| o | 2009/08/07 | bin/137514 | cperciva | freebsd-update(8) doesn't update the system under some circumstances |
| o | 2009/06/16 | bin/135647 | cperciva | freebsd-update(8): forces manual merge of every file in /etc |
| o | 2009/06/10 | bin/135444 | cperciva | freebsd-update(8) failing should be more verbose |
| o | 2009/05/02 | bin/134167 | cperciva | [request] freebsd-update(8) should be able to be run in the background |
| o | 2009/02/11 | bin/131598 | cperciva | freebsd-update(8) doesn't interact well with custom kernels |
| o | 2009/02/04 | bin/131359 | cperciva | freebsd-update(8): freebsd-update tag file not updated after freebsd-update rollback |
| o | 2009/02/04 | bin/131358 | cperciva | freebsd-update(8): Update servers for freebsd-update are out-of-sync |
| o | 2008/12/05 | bin/129431 | cperciva | freebsd-update(8) fetch fails because phttpget fails proxy auth |
| o | 2008/10/31 | bin/128501 | cperciva | freebsd-update(8) does not work on netbooted machines |
| o | 2008/02/12 | bin/120552 | cperciva | freebsd-update(8): freebsd-update - -r should check existence of directories |
Notes
GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '<name>(<section>)' to the Synopsis field. Consider this a prototype of a better search function.
Please give feedback on this report to linimon@FreeBSD.org. Thanks.
Bugs can be in one of several states:
- o - open
- A problem report has been submitted, no sanity checking performed.
- a - analyzed
- The problem is understood and a solution is being sought.
- f - feedback
- Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
- p - patched
- A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
- r - repocopy
- The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
- s - suspended
- The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
- c - closed
- A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.