** Description changed:

  [Impact]
  
-  * Creates a log.txt file in whichever directory it is opened. 
-  * Crashes if open in directories which don't have write permissions for the 
user. e.g: running
-    micro /opt/testfile.txt to even read that file crashes it.
+ 1.
+  * Creates a log.txt file in whichever directory it is opened.
+  * Crashes if open in directories which don't have write permissions for
+    the user. e.g: running
+    micro /opt/testfile.txt to even read that file crashes it.
+ 
+ 2.
+  * Micro thinks it's version is 0.0.0-unknown.
  
  [Test Case]
  
-  * open any file using micro from terminal. A log.txt will be created in
- that folder.
+ 1.
+  * open any file using micro from terminal. A log.txt will be created in
+    that folder.
  
-  * Micro will crash giving an error saying: "error opening file: open 
log.txt: permission denied" 
-    if the user calling micro doesn't have write access to the folder of said 
file. 
+  * Micro will crash giving an error saying:
+    "error opening file: open log.txt: permission denied"
+    
+    If the user calling micro doesn't have write access to the folder of
+    said file.
+ 
+ 2.
+  * micro --version gives the output as:
+    Version: 0.0.0-unknown
  
  [Where problems could occur][WIP]
  
-  * Think about what the upload changes in the software. Imagine the change is
-    wrong or breaks something else: how would this show up?
+  * micro 2.0.6-2 will FTBFS if golang-github-zyedidia-tcell-dev isn't
+    equal or above 1.4.8. Which means the package
+    golang-github-zyedidia-tcell also needs to be updated to 1.4.8. The
+    relevant SRU bug for the same can be found here:
+    
https://bugs.launchpad.net/ubuntu/+source/golang-github-zyedidia-tcell/+bug/1908141
  
-  * It is assumed that any SRU candidate patch is well-tested before
-    upload and has a low overall risk of regression, but it's important
-    to make the effort to think about what ''could'' happen in the
-    event of a regression.
- 
-  * This must '''never''' be "None" or "Low", or entirely an argument as to why
-    your upload is low risk.
- 
-  * This both shows the SRU team that the risks have been considered,
-    and provides guidance to testers in regression-testing the SRU.
+ * micro 2.0.6-2 which in present in groovy will also FTBFS in focal as the
+   debhelper-compat required version is 13 and focal has only 12. So it
+   will need to be modified accordingly. Thus, the version of micro in
+   focal will be 2.0.6-3 after the SRU.
  
  [Other Info]
-  
-  * Upstream bug report: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952283
-  *
+ 
+  * Upstream bug report: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952283
+  * Upstream bug report: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953400

** Summary changed:

- SRU Bug for #1870939 [WIP]
+ SRU micro to 2.0.6-3

** Changed in: micro (Ubuntu)
       Status: New => Fix Released

** Changed in: micro (Ubuntu)
   Importance: Undecided => Medium

** Description changed:

  [Impact]
  
  1.
   * Creates a log.txt file in whichever directory it is opened.
   * Crashes if open in directories which don't have write permissions for
-    the user. e.g: running
+    the user. e.g: running
     micro /opt/testfile.txt to even read that file crashes it.
  
  2.
-  * Micro thinks it's version is 0.0.0-unknown.
+  * Micro thinks it's version is 0.0.0-unknown.
  
  [Test Case]
  
  1.
   * open any file using micro from terminal. A log.txt will be created in
-    that folder.
+    that folder.
  
   * Micro will crash giving an error saying:
-    "error opening file: open log.txt: permission denied"
-    
-    If the user calling micro doesn't have write access to the folder of
-    said file.
+    "error opening file: open log.txt: permission denied"
+ 
+    If the user calling micro doesn't have write access to the folder of
+    said file.
  
  2.
-  * micro --version gives the output as:
-    Version: 0.0.0-unknown
+  * micro --version gives the output as:
+    Version: 0.0.0-unknown
  
- [Where problems could occur][WIP]
+ [Where problems could occur]
  
   * micro 2.0.6-2 will FTBFS if golang-github-zyedidia-tcell-dev isn't
-    equal or above 1.4.8. Which means the package
-    golang-github-zyedidia-tcell also needs to be updated to 1.4.8. The
-    relevant SRU bug for the same can be found here:
-    
https://bugs.launchpad.net/ubuntu/+source/golang-github-zyedidia-tcell/+bug/1908141
+    equal or above 1.4.8. Which means the package
+    golang-github-zyedidia-tcell also needs to be updated to 1.4.8. The
+    relevant SRU bug for the same can be found here:
+    
https://bugs.launchpad.net/ubuntu/+source/golang-github-zyedidia-tcell/+bug/1908141
  
  * micro 2.0.6-2 which in present in groovy will also FTBFS in focal as the
-   debhelper-compat required version is 13 and focal has only 12. So it
-   will need to be modified accordingly. Thus, the version of micro in
-   focal will be 2.0.6-3 after the SRU.
+   debhelper-compat required version is 13 and focal has only 12. So it
+   will need to be modified accordingly. Thus, the version of micro in
+   focal will be 2.0.6-3 after the SRU.
  
  [Other Info]
  
   * Upstream bug report: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952283
   * Upstream bug report: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953400

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908080

Title:
  SRU micro to 2.0.6-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/micro/+bug/1908080/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to