Arch Linux User Repository

If you're upgrading to v47 from a previous version of this icon theme, it will break your custom assigned folder icons because the folder structure of the theme has changed. Simply reassign your custom folder icons.

@That1Calculator James Aaron Erang (iaacornus), the author of the new fork, has confirmed he is going to rename it to Neowaita or possibly something else, so there is no point in linking this package to that repo as it will not take over the MoreWaita project. It is going its own separate way, and it's not going to be named MoreWaita. Please refer to this issue on the GitHub repo that you've linked this package to: https://github.com/MoreWaita-Dev/MoreWaita/issues/1

Please either revert the source of this package to the original MoreWaita repo at https://github.com/somepaulo/MoreWaita or disown the morewaita-git package if you don't want to maintain my project under its original name. Thank you!

@That1Calculator On a side note, I wish you never have to go through any of the reasons I had no time for my hobby project, which is not going anywhere.

@That1Calculator Yes they are. Here it is in their own words if you don't believe me: "At this point i'll create a fork with different name but based on your work but with different path, plans and changeset." https://www.reddit.com/r/gnome/comments/1fkjsdq/comment/lo6knc0/

You want to support the fork, fine by me, just use a different name.

@somepaulo No. They're not even "going in a different direction", they're taking contributions you ignored for months on end. I won't be disowning the package just because you want control back over something you ignored.

@That1Calculator I'm all for forking, I do it myself, but the fork is going in a different direction and apparently taking up a new name as well, according to it's creator's comments on Reddit. So if you want it to be on the AUR, you can easily create a new package instead of hijacking the source of my existing project. So I'm asking once again, please disown this package or revert its source to the original.

@somepaulo I don't know why you're saying "the original developer" as if it isn't you — not sure what strange guilt-tripping card you're trying to play, but you shouldn't have let your package be out of date and orphaned for MONTHS before I picked it up. Switching a dead project to a maintained fork is normal, stop being butthurt that someone forked your repo.

@somepaulo I don't know why you're saying "the original developer" as if it isn't you — not sure what strange guilt-tripping card you're trying to play, but you shouldn't have let your package be out of date and orphaned for MONTHS before I picked it up. Switching a dead project to a maintained fork is normal, stop being butthurt that someone forked your repo.

@That1Calculator No, young man, inappropriate is hijacking a project without so much as asking the actual developer (publicly available here, on GitHub and on Reddit). This package is not release-based, but git-based, so the official release has nothing to do with this, there's the morewaita package for that.

Furthermore, the fact that I didn't have time to add new icons or reply to your issue doesn't mean the project is dead. By the way, I've added your Temp Folder icon (with the respective legacy and symbolic icons) to MoreWaita. So please either disown the package so I can pick it up (and you can make a new one for the fork if you want), or change the repo back to the original.

@somepaulo I find your conduct to be very inappropriate. You asked for an orphan request because I "didn't reply to your message", but you sent the orphan request barely an hour after sending me a message. Furthermore, the last MoreWaita "official" release was a year ago, and there were no commits for 5 months UP UNTIL 3 hours ago.