** Description changed:

  https://github.com/pmem/pmdk-convert/releases/tag/1.5.2
  
  Eoan has kernel 5.2
  
  Debian just uploaded 1.5.2: https://tracker.debian.org/news/1061139
  /accepted-pmdk-convert-152-1-source-into-unstable/
  
  We should check the diff and sync it if no FFe is deemed necessary.
  
  This is the diff the pmdk-convert itself:
  1.5.1..1.5.2 diff:
  https://github.com/pmem/pmdk-convert/compare/1.5.1...1.5.2
  
  Mostly test fixes, but the detail is in this commit, shown in the diff above 
as well:
  
https://github.com/pmem/pmdk-convert/commit/0dbf1d98c353ec91aa9a9944e2ecb6595a5019ae
  
  That tells the build system to fetch the latest pmdk versions of each
  pmdk release. The debian package has these in a separate orig tarball.
  
  Specifically, we are getting the following pmdk updates, when compared
  with the pmdk-convert package we currently have in eoan:
  
  https://github.com/pmem/pmdk/compare/1.5.1...1.5.2
  https://github.com/pmem/pmdk/compare/1.4.2...1.4.3
  https://github.com/pmem/pmdk/compare/1.3.1...1.3.3
  https://github.com/pmem/pmdk/compare/1.2.3...1.2.4
  
  I believe this to not be that relevant, because they are used only for
  conversion tasks from old pool formats. The actual pmdk package, which
  is at 1.6.1 in eoan, is what matters for day-to-day operations, and it
  is not being changed.
  
  In the comments below you can see I tried inspecting all the changes
  listed above and to see if I needed a feature freeze exception, and I
  think I do, so I stopped. But as I said, these updates are only used in
  conversion tasks.
  
  PPA build, with eoan-proposed enabled, and both supported arches as well: 
amd64 and arm64
  https://launchpad.net/~ahasenack/+archive/ubuntu/pmdk-convert-ffe/+packages
+ 
+ Here is a simple test. I created this pool using pmdk from bionic (version 
1.4):
+ $ pmdk-convert --to=1.5 pools-old/pool-obj 
+ This tool will update the pool to the specified layout version.
+ This process is NOT fail-safe.
+ Proceed only if the pool has been backed up or
+ the risks are fully understood and acceptable.
+ Hit Ctrl-C now if you want to stop or Enter to continue.
+ 
+ Starting conversion from v4 (PMDK 1.3, PMDK 1.4) to v5 (PMDK 1.5)
+ Converting from v4 (PMDK 1.3, PMDK 1.4) to v5 (PMDK 1.5)... Done
+ 
+ v5 is also the format used by pmdk 1.6.x:
+ ubuntu@eoan-pmdk-convert:~/test$ pmempool create obj pool-with-pmdk-1.6.1.pool
+ ubuntu@eoan-pmdk-convert:~/test$ pmempool info pool-with-pmdk-1.6.1.pool 
|grep ^Major
+ Major                    : 5

** Description changed:

  https://github.com/pmem/pmdk-convert/releases/tag/1.5.2
  
  Eoan has kernel 5.2
  
  Debian just uploaded 1.5.2: https://tracker.debian.org/news/1061139
  /accepted-pmdk-convert-152-1-source-into-unstable/
  
- We should check the diff and sync it if no FFe is deemed necessary.
- 
  This is the diff the pmdk-convert itself:
  1.5.1..1.5.2 diff:
  https://github.com/pmem/pmdk-convert/compare/1.5.1...1.5.2
+ 
+ This is the source package diff (there are no ubuntu changes):
+ 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/pmdk-convert/commit/?id=ae70671e4ae6ef1d0fd0da611e2e2ad88d3ffafc
  
  Mostly test fixes, but the detail is in this commit, shown in the diff above 
as well:
  
https://github.com/pmem/pmdk-convert/commit/0dbf1d98c353ec91aa9a9944e2ecb6595a5019ae
  
  That tells the build system to fetch the latest pmdk versions of each
  pmdk release. The debian package has these in a separate orig tarball.
  
  Specifically, we are getting the following pmdk updates, when compared
  with the pmdk-convert package we currently have in eoan:
  
  https://github.com/pmem/pmdk/compare/1.5.1...1.5.2
  https://github.com/pmem/pmdk/compare/1.4.2...1.4.3
  https://github.com/pmem/pmdk/compare/1.3.1...1.3.3
  https://github.com/pmem/pmdk/compare/1.2.3...1.2.4
  
  I believe this to not be that relevant, because they are used only for
  conversion tasks from old pool formats. The actual pmdk package, which
  is at 1.6.1 in eoan, is what matters for day-to-day operations, and it
  is not being changed.
  
  In the comments below you can see I tried inspecting all the changes
  listed above and to see if I needed a feature freeze exception, and I
  think I do, so I stopped. But as I said, these updates are only used in
  conversion tasks.
  
  PPA build, with eoan-proposed enabled, and both supported arches as well: 
amd64 and arm64
  https://launchpad.net/~ahasenack/+archive/ubuntu/pmdk-convert-ffe/+packages
  
  Here is a simple test. I created this pool using pmdk from bionic (version 
1.4):
- $ pmdk-convert --to=1.5 pools-old/pool-obj 
+ $ pmdk-convert --to=1.5 pools-old/pool-obj
  This tool will update the pool to the specified layout version.
  This process is NOT fail-safe.
  Proceed only if the pool has been backed up or
  the risks are fully understood and acceptable.
  Hit Ctrl-C now if you want to stop or Enter to continue.
  
  Starting conversion from v4 (PMDK 1.3, PMDK 1.4) to v5 (PMDK 1.5)
  Converting from v4 (PMDK 1.3, PMDK 1.4) to v5 (PMDK 1.5)... Done
  
  v5 is also the format used by pmdk 1.6.x:
  ubuntu@eoan-pmdk-convert:~/test$ pmempool create obj pool-with-pmdk-1.6.1.pool
  ubuntu@eoan-pmdk-convert:~/test$ pmempool info pool-with-pmdk-1.6.1.pool 
|grep ^Major
  Major                    : 5

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

Title:
  Version 1.5.2 needed for kernels >= 5.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pmdk-convert/+bug/1842428/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to