Re: [gentoo-user] attic
On 3/9/23 18:29, Rich Freeman wrote: On Sun, Sep 3, 2023 at 4:44 AM Michael wrote: On Sunday, 3 September 2023 07:49:36 BST William Kenworthy wrote: Hi , I used to be able to get old ebuilds from "the attic" but I cant find it on google - is it still around? Perhaps have a look here at the archives? https://gitweb.gentoo.org/ The archives will only contain data migrated from CVS - so only things from more than a few years ago. You want to look into the main repo for anything recently deleted. * gentoo has moved dev-embedded/reedsolomon to dev-embedded/reedsolo (then removing the old ebuilds) breaking my homeassistant install easiest fix is a local copy until HA catches up. Both CVS and git maintain a record of anything that has been deleted, but they do it differently. The attic directory in CVS contains anything deleted from CVS. In git you need to search the commit history for these files. This can be done via the website, though the search capability is a little limited. I ended up having to search from a local clone because your package name contains an error and the web search found nothing. To find your file, go to: https://gitweb.gentoo.org/repo/gentoo.git/ Go to the search box in the top right and search for: dev-python/reedsolomon (note that the package category is different from what was in your email) Find the commit one commit before the one that removed your package. (ie one that contains your package in its most recent version) If you find the one that deleted your file, then just look at the parent in the commit header and click on that to go back one version where it is still present. Click the tree hash to browse the historical version of the repository that existed before your file was deleted. For example, you can find v1.6.1 of that package at: https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-python/reedsolomon/reedsolomon-1.6.1.ebuild?id=149a131188ebce76a87fd8363fb212f5f1620a02 If the search function is too limiting on the website, here is how to do it from a local checkout. This is what I ended up doing since you had the wrong package name. Note that the first step here requires a few minutes and a few GB of space. My search example is also a bit broader than it would have to be, but you got the package category wrong and searching for "dev-embedded/reedsolomon" turned up nothing. git clone https://anongit.gentoo.org/git/repo/gentoo.git cd gentoo git log --all --full-history --raw --no-merges -- "**/reedsolomon/*" Then browse through the history for the file you're interested in. Suppose you want reedsolomon-1.6.1.ebuild. Easiest way to do that is to find a commit just before it was deleted, so just search the log for that filename. Ignore the first commit where it comes up, which is where the file was deleted (if you examine that commit the file will be missing, since it was deleted). Go to the next one. So reedsolomon-1.6.1.ebuild was deleted in commit beedaf82bd7abd72a654e26627774aef38590149. The next commit in the log search is 149a131188ebce76a87fd8363fb212f5f1620a02, git checkout 149a131188ebce76a87fd8363fb212f5f1620a02 cd dev-python/reedsolomon cat reedsolomon-1.6.1.ebuild You can also see this on the web interface at: https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-python/reedsolomon/reedsolomon-1.6.1.ebuild?id=149a131188ebce76a87fd8363fb212f5f1620a02 The web git interface is capable of displaying past commits. It just can't search for wildcards/etc. Thanks Rich, unfortunately the web interface isn't helpful - I cant just navigate the tree to find commits - "https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-python/reedsolomon/; gives path not found - it looks like you have to know the commit first by downloading the git tree to search it - not friendly at all! the wrong package category was due to trying to wrangle a few ebuilds with the same problem which I confused in the email. I have now found the last of them in an overlay with the distfiles (a similar problem)! This was all self caused - I had years of portage backups (started last time I had a major problem with finding ancient ebuilds) I lost when simplifying/re configuring my systems :( BillK
[gentoo-user] SFP eeprom dumps
Does any one know of a source/file containing the eeprom dumps for sfp and sfp+ optical network modules? I know it's out there but I haven't had any luck finding it through search engines etc. With these files any sfp (especially those designed for universal use) will work with any router/ethernet card (after reflashing the eeprom, the modules are all built to the same specs and only differentiated by the eeprom data about speed and reserved areas, though some are encrypted). If I have the files they can be easily reflashed while plugged into nearly any sfp/sfp+ network card, as well as being able to read the original data for backup. In linux ethtool can do this. Any help/tips would be greatly appreciated, I'm mostly looking for HP/HPE and DELL dumps as those are the cards I'll be using. Thanks, I'm sure somone on this list is geeky enough to know this.
Re: [gentoo-user] dev-db/mysql fails to build, more than one version.
John Covici wrote: > On Sun, 03 Sep 2023 10:48:28 -0400, > Michael Orlitzky wrote: >> On Sun, 2023-09-03 at 09:35 -0500, Dale wrote: >>> Anyone else having this? Is this mysql or is something else causing >>> this and mysql is just a symptom? Given two versions are failing to >>> build, is kinda interesting. >> https://bugs.gentoo.org/912797 >> > Why not use mariadb, its compatible and I know it builds. > Then one day it breaks and I have to switch back. ROFL If I can't get this sorted out tho, that could be a option. I'll keep it in mind. I think the masking of incompatible packages is working. I think. It's still compiling stuff back there. In the mean time, I trying to get some hydraulic fluid out of my tractor that I found out was bad even when I bought it new. No wonder the tractor was being weird. I thought it was taking after me. LOL :-D Thanks for the tip. I may end up going that route if this doesn't work. Dale :-) :-)
Re: [gentoo-user] dev-db/mysql fails to build, more than one version.
On Sun, 03 Sep 2023 10:48:28 -0400, Michael Orlitzky wrote: > > On Sun, 2023-09-03 at 09:35 -0500, Dale wrote: > > > > Anyone else having this? Is this mysql or is something else causing > > this and mysql is just a symptom? Given two versions are failing to > > build, is kinda interesting. > > https://bugs.gentoo.org/912797 > Why not use mariadb, its compatible and I know it builds. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una cov...@ccs.covici.com
Re: [gentoo-user] dev-db/mysql fails to build, more than one version.
On Sun, 2023-09-03 at 09:35 -0500, Dale wrote: > > Anyone else having this? Is this mysql or is something else causing > this and mysql is just a symptom? Given two versions are failing to > build, is kinda interesting. https://bugs.gentoo.org/912797
[gentoo-user] dev-db/mysql fails to build, more than one version.
bindings/xcom/xcom/simset.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/xcom/node_set.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/xcom/xcom_interface.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/xcom/node_list.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/xcom/task_debug.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/xcom/sock_probe.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/xcom/task_net.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/xcom/synode_no.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/xcom/xcom_detector.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/xcom/xcom_input_request.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/xcom/get_synode_app_data.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/xcom/checked_data.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/xcom/xdr_checked_data.c.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/xcom/network/network_provider_manager.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/xcom/network/xcom_network_provider.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/xcom/network/xcom_network_provider_native_lib.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/xcom/network/xcom_network_provider_ssl_native_lib.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/xcom/leader_info_data.cc.o CMakeFiles/mysqlgcs.dir/xdr_gen/xcom_vp_xdr.c.o CMakeFiles/mysqlgcs.dir/src/interface/gcs_logging.cc.o CMakeFiles/mysqlgcs.dir/src/interface/gcs_logging_system.cc.o CMakeFiles/mysqlgcs.dir/src/interface/xplatform/my_xp_cond.cc.o CMakeFiles/mysqlgcs.dir/src/interface/xplatform/my_xp_thread.cc.o CMakeFiles/mysqlgcs.dir/src/interface/xplatform/my_xp_mutex.cc.o CMakeFiles/mysqlgcs.dir/src/interface/xplatform/my_xp_util.cc.o CMakeFiles/mysqlgcs.dir/src/interface/gcs_view.cc.o CMakeFiles/mysqlgcs.dir/src/interface/gcs_types.cc.o CMakeFiles/mysqlgcs.dir/src/interface/gcs_message.cc.o CMakeFiles/mysqlgcs.dir/src/interface/gcs_member_identifier.cc.o CMakeFiles/mysqlgcs.dir/src/interface/gcs_group_identifier.cc.o CMakeFiles/mysqlgcs.dir/src/interface/gcs_psi.cc.o CMakeFiles/mysqlgcs.dir/src/interface/gcs_tagged_lock.cc.o CMakeFiles/mysqlgcs.dir/src/gcs_interface_factory.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/gcs_xcom_communication_interface.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/gcs_xcom_control_interface.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/gcs_xcom_group_management.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/gcs_internal_message_headers.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/gcs_internal_message.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/gcs_xcom_networking.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/gcs_xcom_utils.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/gcs_xcom_state_exchange.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/gcs_xcom_group_member_information.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/gcs_message_stages.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/gcs_xcom_view_identifier.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/gcs_xcom_interface.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/gcs_xcom_notification.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/gcs_message_stage_lz4.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/gcs_xcom_statistics_interface.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/gcs_xcom_proxy.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/gcs_xcom_communication_protocol_changer.cc.o "CMakeFiles/mysqlgcs.dir/__/__/__/extra/lz4/lz4-1.9.4/lib/xxhash.c.o" CMakeFiles/mysqlgcs.dir/src/bindings/xcom/gcs_message_stage_split.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/gcs_xcom_synode.cc.o CMakeFiles/mysqlgcs.dir/src/bindings/xcom/gcs_xcom_expels_in_progress.cc.o /usr/bin/x86_64-pc-linux-gnu-ranlib libmysqlgcs.a make[2]: Leaving directory '/var/tmp/portage/dev-db/mysql-8.0.32-r2/work/mysql_build' [ 17%] Built target mysqlgcs make[1]: Leaving directory '/var/tmp/portage/dev-db/mysql-8.0.32-r2/work/mysql_build' make: *** [Makefile:156: all] Error 2 * ERROR: dev-db/mysql-8.0.32-r2::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=dev-db/mysql-8.0.32-r2::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-db/mysql-8.0.32-r2::gentoo'`. * The complete build log is located at '/var/log/portage/dev-db:mysql-8.0.32-r2:20230903-115316.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-db/mysql-8.0.32-r2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-db/mysql-8.0.32-r2/temp/environment'. * Working directory: '/var/tmp/portage/dev-db/mysql-8.0.32-r2/work/mysql_build' * S: '/var/tmp/portage/dev-db/mysql-8.0.32-r2/work/mysql' I went up quite a bit before the first error, I search for error 1 to find it then go up a ways, just in case. If this is not enough, I can attach the whole thing off list or just go up further. Anyone else having this? Is this mysql or is something else causing this and mysql is just a symptom? Given two versions are failing to build, is kinda interesting. Thoughts? Dale :-) :-) P. S. I'm doing this build in a chroot. However, I did try it once on my live system. Same thing. I can experiment if needed tho, edit ebuild or something.
Re: [gentoo-user] attic
On Sun, Sep 3, 2023 at 4:44 AM Michael wrote: > > On Sunday, 3 September 2023 07:49:36 BST William Kenworthy wrote: > > Hi , I used to be able to get old ebuilds from "the attic" but I cant > > find it on google - is it still around? > > Perhaps have a look here at the archives? > > https://gitweb.gentoo.org/ The archives will only contain data migrated from CVS - so only things from more than a few years ago. You want to look into the main repo for anything recently deleted. > > * gentoo has moved dev-embedded/reedsolomon to dev-embedded/reedsolo > > (then removing the old ebuilds) breaking my homeassistant install > > easiest fix is a local copy until HA catches up. Both CVS and git maintain a record of anything that has been deleted, but they do it differently. The attic directory in CVS contains anything deleted from CVS. In git you need to search the commit history for these files. This can be done via the website, though the search capability is a little limited. I ended up having to search from a local clone because your package name contains an error and the web search found nothing. To find your file, go to: https://gitweb.gentoo.org/repo/gentoo.git/ Go to the search box in the top right and search for: dev-python/reedsolomon (note that the package category is different from what was in your email) Find the commit one commit before the one that removed your package. (ie one that contains your package in its most recent version) If you find the one that deleted your file, then just look at the parent in the commit header and click on that to go back one version where it is still present. Click the tree hash to browse the historical version of the repository that existed before your file was deleted. For example, you can find v1.6.1 of that package at: https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-python/reedsolomon/reedsolomon-1.6.1.ebuild?id=149a131188ebce76a87fd8363fb212f5f1620a02 If the search function is too limiting on the website, here is how to do it from a local checkout. This is what I ended up doing since you had the wrong package name. Note that the first step here requires a few minutes and a few GB of space. My search example is also a bit broader than it would have to be, but you got the package category wrong and searching for "dev-embedded/reedsolomon" turned up nothing. git clone https://anongit.gentoo.org/git/repo/gentoo.git cd gentoo git log --all --full-history --raw --no-merges -- "**/reedsolomon/*" Then browse through the history for the file you're interested in. Suppose you want reedsolomon-1.6.1.ebuild. Easiest way to do that is to find a commit just before it was deleted, so just search the log for that filename. Ignore the first commit where it comes up, which is where the file was deleted (if you examine that commit the file will be missing, since it was deleted). Go to the next one. So reedsolomon-1.6.1.ebuild was deleted in commit beedaf82bd7abd72a654e26627774aef38590149. The next commit in the log search is 149a131188ebce76a87fd8363fb212f5f1620a02, git checkout 149a131188ebce76a87fd8363fb212f5f1620a02 cd dev-python/reedsolomon cat reedsolomon-1.6.1.ebuild You can also see this on the web interface at: https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-python/reedsolomon/reedsolomon-1.6.1.ebuild?id=149a131188ebce76a87fd8363fb212f5f1620a02 The web git interface is capable of displaying past commits. It just can't search for wildcards/etc. -- Rich
Re: [gentoo-user] attic
On Sunday, 3 September 2023 07:49:36 BST William Kenworthy wrote: > Hi , I used to be able to get old ebuilds from "the attic" but I cant > find it on google - is it still around? Perhaps have a look here at the archives? https://gitweb.gentoo.org/ > * gentoo has moved dev-embedded/reedsolomon to dev-embedded/reedsolo > (then removing the old ebuilds) breaking my homeassistant install > easiest fix is a local copy until HA catches up. > > BillK signature.asc Description: This is a digitally signed message part.
[gentoo-user] attic
Hi , I used to be able to get old ebuilds from "the attic" but I cant find it on google - is it still around? * gentoo has moved dev-embedded/reedsolomon to dev-embedded/reedsolo (then removing the old ebuilds) breaking my homeassistant install easiest fix is a local copy until HA catches up. BillK
