A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64; rv:96.0) Gecko/20100101 
Firefox/96.0
IP Address          : 178.162.222.165
Hostname            : 178.162.222.165.adsl.inet-telecom.org
Old Revision        : 
https://wiki.x2go.org/doku.php/wiki:development:release-howto?rev=1661815404
New Revision        : 
https://wiki.x2go.org/doku.php/wiki:development:release-howto
Date of New Revision: 2022/08/29 23:24
Edit Summary        : Fix syntax.
User                : ionic

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -21,9 +21,9 @@
  |  8  | <code bash>dch -r</code> | Make sure to explicitly use '':w'' in vim 
to save the text. Otherwise, i.e., when quitting via '':x'', your change will 
not be recorded! |
  |  9  | <code bash>git diff</code> | Make sure the output is exactly what you 
expect! |
  |  10  | Remove bug spam for all bug reports closed in this release | This 
process is complicated and must be done on **ymir** (packages.x2go.org) as the 
**debbugs** user, which requires root access. This is ''not'' all required 
information. |
  | ::: | <code>cd /var/lib/debbugs/spool/db-h</code> | Switch to the database 
directory. |
- | ::: | <code>cp -av XX/bugnumberXX.log{,.bak} | Create backup of original 
log. The log file contains all messages that have been sent and received during 
the bug's life cycle, including status changes. |
+ | ::: | <code>cp -av XX/bugnumberXX.log{,.bak}</code> | Create backup of 
original log. The log file contains all messages that have been sent and 
received during the bug's life cycle, including status changes. |
  | ::: | ::: | The directory containing the bug report log is always named 
after the last two digits (0-padded, if necessary) of the bug report number. |
  |  11  | <code>/usr/lib/debbugs/cleanbug bugnumber</code> | This tool will 
interactively list all messages (including status changes) in the report and 
asks whether to keep or discard them. |
  | ::: | ::: | Messages are often contained at least twice, since they are 
received initially and then resent to the bug owner and maintainers, so most 
spam messages must be discarded multiple times. |
  | ::: | ::: | This also includes some status messages, which must be likewise 
discarded to create illogical logs. |


-- 
This mail was generated by DokuWiki at
https://wiki.x2go.org/
_______________________________________________
x2go-commits mailing list
x2go-commits@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-commits

Reply via email to