Update lsvpd to v1.7.11 - ppc64le

[bugproxy]

[Impact]

 * HWE add support for f1h Logpage version 0002

[Test Case]

 * execute lsvpd utilities against NVME devices with f1h log page capability version 0002, ensure that all fields/data are displayed.

[Regression Potential]

 * The code change to support larger ioctl buffer is backwards compatible with existing kernels and older devices.

[Other Info]

 * Cherrypick from v1.7.11 of https://github.com/power-ras/lsvpd/commit/7af50e08d6e841992b1e8c2d94cdc77633fe8c52.patch which is already shipped in groovy

[Original bug report]

== Comment: #0 - Shivaprasad G. Bhat <email address hidden> - 2020-04-24 02:18:27 ==
---Problem Description---
Update lsvpd package to v1.7.11

Contact Information = <email address hidden>

---Additional Hardware Info---
PowerPC Machines

---uname output---
ppc64le

Machine Type = Power

---Debugger---
A debugger is not configured

---Steps to Reproduce---
 Package update request

Userspace tool common name: lsvpd

The userspace tool has the following bit modes: 64-bit

Userspace rpm: lsvpd

Userspace tool obtained from project website: na

*Additional Instructions for <email address hidden>:
-Post a private note with access information to the machine that the bug is occuring on.
-Attach ltrace and strace of userspace application.

The package sources are hosted on github now.

https://github.com/power-ras/lsvpd.git

Kindly update to latest version.

[Frank Heimes (fheimes)]

Well, packages of Ubuntu releases that are already rolled out usually don't get version upgrades (release date of 20.04 was yesterday - April 23rd).
Are you interested in particular fixes that come with this new release? And if so can you specify their commit IDs so that they might be cherry-picked instead?

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2020-04-24 04:38 EDT-------
Can you cherry-pick these commits ?

7af50e0 nvme: Update config file with f1h Logpage version 0002
a58b0c0 Enable NVME f1h log page VPD information parsing
7c95a52 vpdupdate: Delete vpd.db when program gets aborted

[Dimitri John Ledkov (xnox)]

Is this for 20.10 or 20.04? I hear that you are asking for this (and other tickets to be in both).

Ubuntu practices time-based release process. Meaning the dates of releases are known well in advance. Which includes testing weeks.

Please familiarize with the Groovy Gorilla release schedule to become 20.10 release.
https://discourse.ubuntu.com/t/groovy-gorilla-release-schedule/15531

All dates are Thursdays, as we always release on Thursday (unspecified timezone.... sometimes things go so well we slip into Friday =) )

Important dates are:
* Ubuntu Testing week 29 June - 3 July
* Feature Freeze August 27
* Ubuntu Testing week 31 August - 4 September
* Kernel Freeze 8 October
* Final Freeze 15 October
* Final Release 22 October

The two testing weeks, is when Ubuntu development team, Partners and community pause to focus on testing install media, cloud images, and upgrades. You are invited to participate during that time to report any issues or missing things that you can identify. Please schedule to test installers during those weeks, as we ensure we have up to date installer media.

Please file requests for new packages, as soon as you anticipate that they would be needed. Well ahead of, but no later than, Feature Freeze date of August 27.

Kernel Freeze for patches/features/backports is October 8. But do file requests for backports as soon as you know about that.

As we approach Final Freeze and Final Release, we only fix critical issues that prevent installation or applying updates. As on Final release week, these are the criteria for respining the installer media.

Groovy installation media dailies are already available, you can find them from the QA ISO tracker which always points at latest daily releases & milestones that are being tested at http://iso.qa.ubuntu.com/

Also we are continuously producing daily builds of upcoming point releases for Bionic and Focal. Testing those ahead of point releases is encouraged as well.

Can you please ensure you put the above mentioned dates into account when scheduling your testing and acceptance of 20.10 such that any issues are raised in time for us to fix the GA release before it goes out to customers?

[Frank Heimes (fheimes)]

Yes, this was requested (after consulting) for 20.10 and 20.04 - I added now the nominations.

[Launchpad Janitor (janitor)]

This bug was fixed in the package lsvpd - 1.7.11-0ubuntu1

---------------
lsvpd (1.7.11-0ubuntu1) groovy; urgency=medium

  [ Frédéric Bonnard ]
  * Update URLs from sourceforge to github

  [ Balint Reczey ]
  * debian/watch: Fix URL and upgrade version
  * New upstream release (LP: #1874636)

 -- Balint Reczey <email address hidden> Thu, 28 May 2020 14:46:45 +0200

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2020-05-29 02:58 EDT-------
(In reply to comment #9)
> This bug was fixed in the package lsvpd - 1.7.11-0ubuntu1
>
> ---------------
> lsvpd (1.7.11-0ubuntu1) groovy; urgency=medium
>
> [ Fr?d?ric Bonnard ]
> * Update URLs from sourceforge to github
>
> [ Balint Reczey ]
> * debian/watch: Fix URL and upgrade version
> * New upstream release (LP: #1874636)
>
> -- Balint Reczey <email address hidden> Thu, 28 May 2020 14:46:45 +0200

I see groovy update. Can you please update this package for focal next LTS release?

-Vasant

[Frank Heimes (fheimes)]

Hi Vasant, the update process in Ubuntu prescribes that an update or patch must first land in the current development release, which is currently groovy.
The next step is then to do a stable release update (or SRU) to the next older version, which is focal in this case. (If it needs to be done to even more older releases, then all in between need to be processed first - from new to old - to avoid regressions).
The table on the top of this ticket shows that 'Focal' got already nominated, hence it will be processed next (maybe with a little timely gap to get some experiences from groovy and to be sure that the update work fine, before moving from the development to the next officially released version).
So focal will be processed soon ... thx

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2020-05-29 05:25 EDT-------
(In reply to comment #11)
> Hi Vasant, the update process in Ubuntu prescribes that an update or patch
> must first land in the current development release, which is currently
> groovy.
> The next step is then to do a stable release update (or SRU) to the next
> older version, which is focal in this case. (If it needs to be done to even
> more older releases, then all in between need to be processed first - from
> new to old - to avoid regressions).
> The table on the top of this ticket shows that 'Focal' got already
> nominated, hence it will be processed next (maybe with a little timely gap
> to get some experiences from groovy and to be sure that the update work
> fine, before moving from the development to the next officially released
> version).
> So focal will be processed soon ... thx

Thanks for the clarification!

-Vasant

[Dimitri John Ledkov (xnox)]

These two commits are in focal already:
- a58b0c0 Enable NVME f1h log page VPD information parsing
- 7c95a52 vpdupdate: Delete vpd.db when program gets aborted
Are they not working right?

I will start sru process into focal for:
- 7af50e0 nvme: Update config file with f1h Logpage version 0002

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2020-06-15 22:23 EDT-------
(In reply to comment #15)
> Created attachment 143485 [details]
> lp1874636.debdiff
>
> default comment

Looks good. Thanks you.

-Vasant

[Brian Murray (brian-murray)]

Hello bugproxy, or anyone else affected,

Accepted lsvpd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lsvpd/1.7.10-1ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2020-06-17 01:23 EDT-------
(In reply to comment #17)
> Hello bugproxy, or anyone else affected,
>
> Accepted lsvpd into focal-proposed. The package will build now and be
> available at https://launchpad.net/ubuntu/+source/lsvpd/1.7.10-1ubuntu0.1 in
> a few hours, and then in the -proposed repository.

I have verified and it fixes the issue reported here.

-Vasnat

[Frank Heimes (fheimes)]

Thanks for the quick verification, Vasant!

[Launchpad Janitor (janitor)]

This bug was fixed in the package lsvpd - 1.7.10-1ubuntu0.1

---------------
lsvpd (1.7.10-1ubuntu0.1) focal; urgency=medium

  * Cherrypick upstream commit to support NVME drives with f1h logpage
    version 0002. LP: #1874636

 -- Dimitri John Ledkov <email address hidden> Mon, 15 Jun 2020 18:07:25 +0100

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for lsvpd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2020-06-24 01:45 EDT-------
(In reply to comment #20)
> This bug was fixed in the package lsvpd - 1.7.10-1ubuntu0.1
>
> ---------------
> lsvpd (1.7.10-1ubuntu0.1) focal; urgency=medium
>
> * Cherrypick upstream commit to support NVME drives with f1h logpage
> version 0002. LP: #1874636
>
> -- Dimitri John Ledkov <email address hidden> Mon, 15 Jun 2020 18:07:25 +0100
>
> The verification of the Stable Release Update for lsvpd has completed
> successfully and the package is now being released to -updates.
> Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed
> and will not receive messages about this bug report. In the event that you
> encounter a regression using the package from -updates please report a new
> bug using ubuntu-bug and tag the bug report regression-update so we can
> easily find any regressions.

Thanks! We can close this defect.

-Vasant