Please add ebuild for lsvpd-1.0.4, will attach ebuild. Reproducible: Always
Created attachment 110939 [details] lsvpd-1.0.4 ebuils
lsvpd has been tested on x86, ppc, and ppc64.
I am the maintainer for this package on sourceforge, I can maintain this package here as well.
Created attachment 113425 [details] lsvpd-1.1.0.ebuild This is the latest lsvpd ebuild. As I mentioned earlier I am happy to maintain this package.
Not sure how long this normally takes, but I have offered to maintain this, the offer still stands. I would just like to see something here about the hold up...
To speed up review and inclusion, it is always good to include some basic program information. I had to open the ebuild and follow links to find out what lsvpd was. Please consider reading the following document: http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=3 In addition to points already described in that document, please remove cd ${S} from src_compile, it is redundant. Adding your service to the default runlevel without user interaction is definately not allowed. You can hint at the possibility using elog instead of calling rc-update directly. Please consider whether your db version depend needs to be *that* specific (this seems unlikely to me). Also, a package is a DEPEND (build-time dependency) or RDEPEND (run-time dependency). It is never both, so you will need to look at your dependencies again. The COPYING file in your lsvpd tarball contains GPL-2, yet you specify two licenses in the ebuild. Could you clarify that?
Thank you for your feedback. COPYING should have contained the LGPL as well, I have corrected the omission. The reason for both licenses is the code for the user programs (vpdupdate, lsvpd, etc.) is GPL while the code for libvpd is LGPL. I have included this clarification in the COPYING file as well. I don't know if the db version needs to be that specific because I have not tested this code with any other version. This is the version we have to support for inclusion with other distros. I will try linking with the newer versions of libdb and adjust the dependency appropriately. I have added this comment block to the top of the ebuild: # lsvpd is used to collect system vpd and store it in a single place for easy # access. The package provides the vpdupdate utility to take a snapshot # of all the available system vpd when it is run. lsvpd, lscfg, lsmcode, and # lsvio all display various pieces of the vpd, for instance, lsvpd dumps all # available system vpd, one value per line with a 2 letter id code before the # value. lscfg presents the same information in a more human readable format. I am currently preparing a new release and I will submit the updated ebuild when that release is ready.
(In reply to comment #7) > I have added this comment block to the top of the ebuild: Actually I meant that for the bug report, not the ebuild itself. Please do not add that to the ebuild as comments. It will not be lost however, I'll add it to the metadata.xml file in the ebuild directory as a 'longdescription'. > I am currently preparing a new release and I will submit the updated ebuild > when that release is ready. Okay. Would you happen to know whether this utility works on older Compaq and newer HP Proliant hardware? It would ease testing if it did (and could earn your ebuild an ~amd64 keyword).
Created attachment 118690 [details] lsvpd-1.2.0 ebuild Here is the latest lsvpd ebuild. I believe that I have included all of your requested changes (if I missed anything please let me know). Unfortunately I do not have access to any Proliant or Compaq hardware.
Created attachment 126837 [details] lsvpd-1.3.1 ebuild SOrry for the long silence, this is the newest ebuild for lsvpd.
Created attachment 133062 [details] lsvpd-1.3.5 ebuild Here is the newest ebuild for lsvpd. The project has been split into two, the programs remain in lsvpd and the library has moved to libvpd (I will open a new entry for libvpd in a moment and add a dependency here). Here is the newest ebuild for lsvpd.
from http://sourceforge.net/project/showfiles.php?group_id=44427 lsvpd 1.4.0 November 16, 2007 the version 1.4.0 has released, please give a version bump.
Created attachment 137626 [details, diff] from lsvpd-1.3.5 to 1.4.0.ebuild to Eric Munson: please view this patch, with changes: 1. SRC_URI with mirror://sourceforge/, this could give users freedom to use any mirror of sourceforge; 2. test ebuilds always use "~arch" first; 3. the src_compile and src_install are the default, both can be killed.
Created attachment 140575 [details] lsvpd 1.5.0 ebuild Newest ebuild addresses concerns listed above and updates to newest code available.
Created attachment 140578 [details] lsvpd 1.5.0 ebuild Take 2 Sorry about the spam, forgot to add the Header line to this ebuild.
Created attachment 141181 [details] lsvpd 1.5.0 ebuild take 3 Changes http to mirror for fetching source
Is there still any user interest in this package? There hasn't been a new release since 2008 and I've got a feeling this tools might have been rendered obsolete by sys-apps/lshw long ago.
umm, don't know where you looked, but last upstream release was just in may 2016: https://sourceforge.net/projects/linux-diag/files/lsvpd-new/1.7.7/. My usage case for it was niche & short-lived, but still valid; lshw does not include the other lsvpd package tools for modifying PPC VPD data.
(In reply to Robin Johnson from comment #18) > umm, don't know where you looked The Web page of the project, which still lists 1.6.4 (released on 2008-04-25) as the most recent version. > My usage case for it was niche & short-lived, but still valid; lshw does not > include the other lsvpd package tools for modifying PPC VPD data. Noting the use of the past tense, I reckon you aren't interested in maintaining this package?
(In reply to Marek Szuba from comment #19) > (In reply to Robin Johnson from comment #18) > > > umm, don't know where you looked > The Web page of the project, which still lists 1.6.4 (released on > 2008-04-25) as the most recent version. Sourceforge > > > My usage case for it was niche & short-lived, but still valid; lshw does not > > include the other lsvpd package tools for modifying PPC VPD data. > Noting the use of the past tense, I reckon you aren't interested in > maintaining this package? I don't have any PPC hardware anymore. The PPC VPD stuff will be relevant again when the Talos secure workstations are released. I think just bump it as needed for the moment
Well, Talos seems to be going nowhere at the moment - the crowdfunding campaign has reached only 14% of the goal and the Web site seems not to have been updated for months (it still contains a link to the crowdfunding campaign even though said campaign ended on the 14th of January 2017). I think we should close this as WONTFIX for now and revive it if/when needed.
Please add this ebuild so that PowerPC users (including many Talos/Blackbird owners) can run the lsmcode and vpdupdate utilities. The tools were last updated to version 1.7.10 in October 2019. URL: https://sourceforge.net/projects/linux-diag/files/lsvpd-new/ Example usage: https://wiki.raptorcs.com/w/index.php?title=Getting_System_Information&oldid=2935#System_Firmware_versions
Created attachment 605164 [details] lsvpd 1.7.10 ebuild This worked for me. I'm not sure how to handle the following preamble to the license from the COPYING file: Special Exception: As a special exception, IBM gives permission to link the code of portions of this program against the librtas library, and distribute linked combinations including the two. You must obey the GNU General Public License in all respects for all of the code used other than librtas.
