All Activity
- Earlier
-
Can't emerge json
>>> Emerging (5 of 😎 dev-ruby/json-2.9.0::ruby-kit
* json-2.9.0-20b501a.tar.gz BLAKE2B SHA512 size 😉 ... [ ok ]
>>> Unpacking source...
* Running unpack phase for all ...
>>> Unpacking json-2.9.0-20b501a.tar.gz to /var/tmp/portage/dev-ruby/json-2.9.0/work/all
>>> Source unpacked in /var/tmp/portage/dev-ruby/json-2.9.0/work
mv: cannot stat '/var/tmp/portage/dev-ruby/json-2.9.0/work/all/flori-json-*': No such file or directory -
ele o funtoo não encontra minha partição /
# == IMPORTANT ==============================================================
# The 3 lines below need to be *uncommented* and adjusted for your system
# ===========================================================================
UUID=B3CB-8D49 /boot vfat noauto,noatime 1 2
UUID=ff672182-6c5c-469a-a2ab-3f84adf4960c / ext4 noauto,noatime 0 1
# ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 nov 30 14:53 1416eb78-590c-45b8-9e73-276e4b67e507 -> ../../dm-2
lrwxrwxrwx 1 root root 15 nov 30 14:53 B3CB-8D49 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 10 nov 30 14:53 deda9aea-f756-42b7-beaa-f987a7347687 -> ../../dm-0
lrwxrwxrwx 1 root root 10 nov 30 14:53 e7acd477-d7a9-47cd-b9e0-a5de3ccb92c0 -> ../../dm-1
blkid
/dev/mapper/data-swap: UUID="e7acd477-d7a9-47cd-b9e0-a5de3ccb92c0" TYPE="swap"
/dev/nvme0n1p1: UUID="B3CB-8D49" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="cb618eb8-f40b-403d-af77-b5cc1d489a88"
/dev/nvme0n1p2: UUID="3uzJuv-f09M-Z2W2-OMn2-3iKg-V3Nv-wz4oBF" TYPE="LVM2_member" PARTLABEL="root" PARTUUID="ff672182-6c5c-469a-a2ab-3f84adf4960c"
/dev/mapper/cryptswap: LABEL="cryptswap" UUID="1416eb78-590c-45b8-9e73-276e4b67e507" TYPE="swap"
/dev/mapper/data-root: UUID="deda9aea-f756-42b7-beaa-f987a7347687" BLOCK_SIZE="4096" TYPE="ext4" -
I dont getit
-
I cant install kde
-
>> Emerging (1 of 34) dev-libs/nspr-4.36::dev-kit
* nspr-4.36.tar.gz BLAKE2B SHA512 size 😉 ... [ ok ]
>>> Unpacking source...
>>> Unpacking nspr-4.36.tar.gz to /var/tmp/portage/dev-libs/nspr-4.36/work
>>> Source unpacked in /var/tmp/portage/dev-libs/nspr-4.36/work
>>> Preparing source in /var/tmp/portage/dev-libs/nspr-4.36/work/nspr-4.36 ...
* Applying nspr-4.23-prtime.patch ...
patching file pr/src/misc/prtime.c
Hunk #1 FAILED at 1621.
Hunk #2 FAILED at 1677.
2 out of 2 hunks FAILED -- saving rejects to file pr/src/misc/prtime.c.rej [ !! ]
* ERROR: dev-libs/nspr-4.36::dev-kit failed (prepare phase):
* patch -p1 failed with /var/tmp/portage/dev-libs/nspr-4.36/files/nspr-4.23-prtime.patch
*
* Call stack:
* ebuild.sh, line 93: Called src_prepare
* environment, line 1553: Called default
* phase-functions.sh, line 855: Called default_src_prepare
* phase-functions.sh, line 920: Called __eapi6_src_prepare
* environment, line 204: Called eapply '/var/tmp/portage/dev-libs/nspr-4.36/files/nspr-4.23-prt
ime.patch' '/var/tmp/portage/dev-libs/nspr-4.36/files/nspr-4.8.4-darwin-install_name.patch' '/var/tmp/portage/
dev-libs/nspr-4.36/files/nspr-4.8.9-link-flags.patch' '/var/tmp/portage/dev-libs/nspr-4.36/files/nspr-4.9.5_ns
pr_config.patch'
* environment, line 719: Called _eapply_patch '/var/tmp/portage/dev-libs/nspr-4.36/files/nspr-4
.23-prtime.patch'
* environment, line 657: Called __helpers_die 'patch -p1 failed with /var/tmp/portage/dev-libs
/nspr-4.36/files/nspr-4.23-prtime.patch'
* isolated-functions.sh, line 112: Called die
* The specific snippet of code:
* die "$@"
*
* If you need support, post the output of `emerge --info '=dev-libs/nspr-4.36::dev-kit'`,
* the complete build log and the output of `emerge -pqv '=dev-libs/nspr-4.36::dev-kit'`.
* The complete build log is located at '/var/tmp/portage/dev-libs/nspr-4.36/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-libs/nspr-4.36/temp/environment'.
* Working directory: '/var/tmp/portage/dev-libs/nspr-4.36/work/nspr-4.36/nspr'
* S: '/var/tmp/portage/dev-libs/nspr-4.36/work/nspr-4.36'
>>> Failed to emerge dev-libs/nspr-4.36, Log file:
>>> '/var/tmp/portage/dev-libs/nspr-4.36/temp/build.log'
* Messages for package x11-drivers/nvidia-drivers-550.78-r1:
* These NVIDIA drivers are designed to work with Linux 6.3 or earlier.
* Messages for package dev-libs/nspr-4.36:
* ERROR: dev-libs/nspr-4.36::dev-kit failed (prepare phase):
* patch -p1 failed with /var/tmp/portage/dev-libs/nspr-4.36/files/nspr-4.23-prtime.patch
*
* Call stack:
* ebuild.sh, line 93: Called src_prepare
* environment, line 1553: Called default
* phase-functions.sh, line 855: Called default_src_prepare
* phase-functions.sh, line 920: Called __eapi6_src_prepare
* environment, line 204: Called eapply '/var/tmp/portage/dev-libs/nspr-4.36/files/nspr-4.23-prt
ime.patch' '/var/tmp/portage/dev-libs/nspr-4.36/files/nspr-4.8.4-darwin-install_name.patch' '/var/tmp/portage/
dev-libs/nspr-4.36/files/nspr-4.8.9-link-flags.patch' '/var/tmp/portage/dev-libs/nspr-4.36/files/nspr-4.9.5_ns
pr_config.patch'
* environment, line 719: Called _eapply_patch '/var/tmp/portage/dev-libs/nspr-4.36/files/nspr-4
.23-prtime.patch'
* environment, line 657: Called __helpers_die 'patch -p1 failed with /var/tmp/portage/dev-libs
/nspr-4.36/files/nspr-4.23-prtime.patch'
* isolated-functions.sh, line 112: Called die
* The specific snippet of code:
* die "$@"
*
* If you need support, post the output of `emerge --info '=dev-libs/nspr-4.36::dev-kit'`,
* the complete build log and the output of `emerge -pqv '=dev-libs/nspr-4.36::dev-kit'`.
* The complete build log is located at '/var/tmp/portage/dev-libs/nspr-4.36/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-libs/nspr-4.36/temp/environment'.
* Working directory: '/var/tmp/portage/dev-libs/nspr-4.36/work/nspr-4.36/nspr'
* S: '/var/tmp/portage/dev-libs/nspr-4.36/work/nspr-4.36'
livecd ~ #
-
-
d4g33z reacted to a post in a topic:
Funtoo Continues in "Hobby Mode"
-
morphmex reacted to a post in a topic:
Funtoo Continues in "Hobby Mode"
-
lostin8 reacted to a post in a topic:
Funtoo Continues in "Hobby Mode"
-
f2dmarques joined the community -
Note -- hosting is being continued. All existing users should have received emails by this point.
-
I went with Hostinger. Apparently, they are not closing down hosting now? It's kinda too late. It's not like we had a couple months to decide on what to do. I feel like I just got evicted.
-
grouche reacted to a post in a topic:
Funtoo Continues in "Hobby Mode"
-
Hi @radek, what do you mean with too late? If It is related with the last @drobbins announcement what I understand he is saying is that he will continue maintaining funtoo just for himself, so I don't expect too much updates, just the packages he uses. Updating is not just increase the PV and it requieres take a look to changelog, for changes, new dependencies or functionalities as well than some testing so in that scenario using funtoo would be like having a base system you would need to maintain by your own. In conclusion unless you have much more time than even knowledge, keep using it is not a realistic option. I have been thinking about it since Daniel said he was done, considering doing It by my own. And even I have started installing a LFS to build my own distro, since I can't find anotherone as confortable as Funtoo is for me, but I just don't have time for that. I started using gentoo when it was just a release candidate, and move to funtoo as soon as Daniel made it public. There is no other distro I would like to use. But there is no option, at least for now. All I can do is say a huge thank you to @drobbins for everything he has given me over the past 20+ years (more than half my life) and wish him the best both personally and professionally.
-
zayer reacted to a post in a topic:
Funtoo Continues in "Hobby Mode"
-
I wont install funtoo again....
-
I've decided to keep Funtoo Linux going in a limited capacity. Borrowing a phrase from Cameron Kaiser, developer of TenFourFox (a Firefox fork for PowerPC Macs) Funtoo Linux will be entering "Hobby Mode". Here is what that means: Funtoo Linux will continue as a personal project of mine, maintained for myself. You will still be able to ego sync and get periodic updates. You can still use it if you want to. I use Funtoo in various capacities personally so I might as well allow others to continue to use it too, if they want. Community development resources -- bug tracker and community code repositories will remain offline. Forums and wiki will be moved to read-only mode. Funtoo logins will go away at some point. Discord will continue to be used to some degree, but please move all community discussion to Reddit for self-support, not Discord. That's where you can ask other Funtoo Linux users for help going forward. If you would like to keep a Funtoo container, please contact me at drobbins@funtoo.org and I will make arrangements to keep yours going. These were previously going away at the end of this month. I will be keeping sufficient infrastructure online to maintain some container hosting. If you want a new Funtoo container, contact me to get on a waiting list for some new infrastructure I am working on. Funds will be used to support Oleg to work on these future projects that will be available to the public at some point. If you care about the fate of Funtoo and community Open Source projects (and Oleg), this is a great way to demonstrate support. If you are interested in making a major, meaningful technical contribution to Funtoo Linux, please contact me privately via email to discuss it. I am always open to co-creation and supporting collaboration from serious contributors, but can't spend the time and energy to keep the doors open for this 24/7 as there is significant overhead in running a community project. My YouTube Channel may receive some content in the relatively near future, so if you are interested in following future developments or getting more detail on my views on Open Source, please follow me there. The latest changes from harvester/2024-07 have just been merged into official Funtoo and the tree was updated today, with continued periodic updates to follow about once a week or so.
-
I just found out about this now, in mid August. Have you found anything remotely close?
-
Iam sad. I have been used funtoo since 2017. I hope you find someone to keep the projekt alive. But from some time your small team was unable to keep packages up to date and maintained bugs. I will wait to end of august. And if nothing positive happens migrate to Vanilla Linnux
-
I'm so sorry to see this. Funtoo has been the perfect distro for me for ten years now and I truly appreciate all that @drobbins and the other project members have done to develop and maintain it. But time is the only truly non-renewable resource. If it doesn't make you happy or pay the bills then you're right to move on. Wishing you all the best in whatever comes next.
-
nrc reacted to a post in a topic:
All Good Things Must Come to an End...
-
miku joined the community -
I almost finished development of netif replacement and here you go.
-
It's sad. It's very sad...
-
lego12239 reacted to a post in a topic:
All Good Things Must Come to an End...
-
I'm devastated, but I have no one but myself to blame. Sorry, Dan.
-
zayer reacted to a post in a topic:
All Good Things Must Come to an End...
-
AdiosKid reacted to a post in a topic:
All Good Things Must Come to an End...
-
digit changed their profile photo -
It is sad. But I understand. Perhaps (I hope), the funtoo community can arrange something to keep a community run funtoo going. ... I had only just got back into funtoo in the past year. Oh well.
-
I've not used Funtoo or anything Gentoo-based in years, but it did help shape me as a Linux user. I started my Linux journey with Mandrake 9.x on a 233 MHz Pentium II back in the late 90s/early 2000s which was my DC++/Direct Connect hub server machine, followed by various bouts with Ubuntu flavors, Funtoo after that, Void after I got tired of Funtoo for that moment, and now I've landed on Arch Linux. I'm very comfortable on Arch, and it's all thanks to Funtoo and indirectly Gentoo as well. @drobbinsThanks for helping me learn how Linux works. I'll forever be grateful to you and your team of volunteers. I assume you're ending Funtoo to concentrate on Moccachino OS? I know you merged Funtoo's base with Sabayon and you and the Sabayon developer started developing a new, more containerized distro called Moccachino OS. If that's true, once it's in a stable state I'll gladly try it out. I have several test machines that I could play with it on. Regards, Shiggitay
-
The unexpected but expected news about the end of the Funtoo Linux project took us by surprise. My small working infrastructure of a software developer and linux user is tied to Funtoo. For a while I will be able to maintain it on my own, thanks to the experience I have gained over the last 16 years. But there are some hard choices ahead. I'm sadly, as I'm used to Funtoo's endemic approach and tools. It has not been a bad 16 years. I hope that the repositories with tools will not be deleted and the web-site with documentation will survive long enough to help users. What is BDFL's opinion on this? @drobbins thx for the Funtoo
-
tmnhy joined the community -
Well, shit. I have 30 days to find a new hosting provider and move all my stuff over? 🤯 Someone please make some suggestions. I haven't even looked at providers in forever. I don't even know where to start and I just started a business and need to keep Processwire, Opencart, and Postfix/Nginx running and all that.
-
All good things must come to an end. I've decided to end the Funtoo Linux project. Funtoo started as a philosophy to create a fun community of contributors building something great together. For me, it's no longer that so I need to move on to other things. There is not a successor BDFL for Funtoo nor am I interested in trying to find one, or hand the project off to someone else. You can expect the project to wind down through August. If you have a Funtoo container, it will continue to be online through the end of August so you have time to find another hosting solution if you need one.
