While I cannot seem to reproduce thsi with the provided sources.list, my
test case works. I had to delete the DistUpgrade package from the source
tree to get autopkgtest to pick up the installed version (or autopkgtest
here apparently test the source tree, which is wrong).

With 17.10.9:

======================================================================          
                                                      
FAIL: test sources.list rewrite of an obsolete mirror
----------------------------------------------------------------------     
Traceback (most recent call last):                                              
         
  File "/usr/lib/python3/dist-packages/mock/mock.py", line 1305, in patched
    return func(*args, **keywargs)
  File "/tmp/autopkgtest.qMDThe/tree/tests/test_sources_list.py", line 169, in 
test_sources_list_inactive_mirror
    """)               
  File "/tmp/autopkgtest.qMDThe/tree/tests/test_sources_list.py", line 584, in 
_verifySources2Way
    (l, sources_list))
AssertionError: False is not true : unexpected entry 'deb 
http://archive.ubuntu.com/ubuntu stable main # auto generated by 
ubuntu-release-upgrader' in sources.list. got:


With 17.10.10 (--apt-pocket=proposed):

autopkgtest [11:01:33]: test nose-tests: [-----------------------
...
** (nosetests3:6104): WARNING **: Error retrieving accessibility bus address: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not 
provided by any .service files

(nosetests3:6104): Gtk-CRITICAL **: gtk_main_quit: assertion 'main_loops != 
NULL' failed
.....................................äää....
----------------------------------------------------------------------
Ran 44 tests in 11.451s

OK
autopkgtest [11:01:45]: test nose-tests: -----------------------]


** Description changed:

  [Impact]
  Upgrades from unsupported releases do not work if they have some third-party 
repositories in their sources.list, for example a repository with "stable" as 
the suite. u-r-u generates a new sources.list with an Ubuntu entry for "stable".
  
  [Test case]
- On a zesty system, add
- 
-   deb https://example.com/3rd-party/deb/ stable main
- 
- to the sources.list and try to upgrade to artful. It will generate an
- entry:
- 
-   deb https://archive.ubuntu.com/ stable main
- 
- and fail.
- 
- Now run do-release-upgrade --proposed and check that it does not do
- that.
- 
- Alternatively, just rely on the autopkgtest test case testing that.
+ Run the provided test case against 17.10.9 and check that it fails. Run it 
again 17.10.10 and check that it works.
  
  [Regression Potential]
  This affects release upgrades, and if broken, might prevent some release 
updates. It seems unlikely though: The change just checks that the new 
distribution of a sources.list entry is valid before writing it out.
  
  [Original bug report]
  
  During update after release 'zesty' 'end of life' strange error appear:
  
  E:The repository 'http://archive.ubuntu.com/ubuntu stable Release' does
  not have a Release file.
  
  This error prevent upgrade process. There is no entry like 
'http://archive.ubuntu.com/ubuntu stable Release' in my 'sources.list'. I have 
no idea where this entry comes from. During regular packages update try, only 
appears error messages directly related to 'end of life' release state. No 
error like above. I am not sure, but it seems like 
'http://archive.ubuntu.com/ubuntu stable Release' is wrongly formatted and have 
no idea where this comes from as all. Here is my sources list (as is now). As 
could be seen from the sources list my install is from 2014. Over the years I 
make upgrade after 'end of life' release few times without any problems. Now is 
the first time I have such issue.
  Thanks in advance!
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-release-upgrader-core 1:17.04.10
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.10
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Mon Jan 22 15:56:24 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-12 (1289 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to zesty on 2018-01-20 (2 days ago)
  VarLogDistupgradeAptlog:
   Log time: 2018-01-20 03:20:51.814404
   Log time: 2018-01-20 03:20:56.946483
   Log time: 2018-01-20 03:21:25.049488

** Description changed:

  [Impact]
  Upgrades from unsupported releases do not work if they have some third-party 
repositories in their sources.list, for example a repository with "stable" as 
the suite. u-r-u generates a new sources.list with an Ubuntu entry for "stable".
  
  [Test case]
- Run the provided test case against 17.10.9 and check that it fails. Run it 
again 17.10.10 and check that it works.
+ Run the provided autopkgtest tests against 17.10.9 and check that it fails. 
Run it again 17.10.10 and check that it works.
  
  [Regression Potential]
  This affects release upgrades, and if broken, might prevent some release 
updates. It seems unlikely though: The change just checks that the new 
distribution of a sources.list entry is valid before writing it out.
  
  [Original bug report]
  
  During update after release 'zesty' 'end of life' strange error appear:
  
  E:The repository 'http://archive.ubuntu.com/ubuntu stable Release' does
  not have a Release file.
  
  This error prevent upgrade process. There is no entry like 
'http://archive.ubuntu.com/ubuntu stable Release' in my 'sources.list'. I have 
no idea where this entry comes from. During regular packages update try, only 
appears error messages directly related to 'end of life' release state. No 
error like above. I am not sure, but it seems like 
'http://archive.ubuntu.com/ubuntu stable Release' is wrongly formatted and have 
no idea where this comes from as all. Here is my sources list (as is now). As 
could be seen from the sources list my install is from 2014. Over the years I 
make upgrade after 'end of life' release few times without any problems. Now is 
the first time I have such issue.
  Thanks in advance!
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-release-upgrader-core 1:17.04.10
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.10
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Mon Jan 22 15:56:24 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-12 (1289 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to zesty on 2018-01-20 (2 days ago)
  VarLogDistupgradeAptlog:
   Log time: 2018-01-20 03:20:51.814404
   Log time: 2018-01-20 03:20:56.946483
   Log time: 2018-01-20 03:21:25.049488

** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

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

Title:
  Unknown bad source brings up during 'zesty' to 'artful' upgrade and It
  break the process

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1744722/+subscriptions

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

Reply via email to