Page MenuHomeSolus

duplicate repositories
Closed, ResolvedPublic

Description

It seems that R2890 and R2689 are duplicate.

I think only pytest-runner uses the last one. Since I'm working on this pkg, I propose to disable the last repo after the update is ready.

Related Objects

Event Timeline

kyrios123 created this task.Dec 2 2017, 9:45 AM

@baimafeima No those are completely different programs.

I have created a list of unused git repos for packages (which means they will no longer get globally pulled). Though they likely should be deactivated in Phab as well.

https://dev.solus-project.com/source/common/browse/master/Scripts/update-packages.sh;c8a8f4af2f859f92c05f116eef5e5df5f24ae8d4$42

Should I also add the replace key in the package.yml of R2689 or is it not necessary if they get deactivated in Phab ?

PS: I would be nice to have D1543 approved so R2890 will become orphan but also because I have a couple of approved packages that depends on this one.

sunnyflunk added a comment.EditedJan 24 2018, 10:42 PM

Should I also add the replace key in the package.yml of R2689 or is it not necessary if they get deactivated in Phab ?

replaces key isn't about Phab, it's for eopkg so is always required (on top of which all packages which depend on the removed package need to be rebuilt to not depend on it as well). eopkg info pkg will only tell you this information before it's deprecated otherwise you have to search for it in the eopkg-index.xml file.

Deactivating is so you don't accidently try to use the wrong one (it won't pull or push changes anymore).

In saying that, I don't think replaces are necessary for this, as it's not a dependency of anything and unlikely to be installed on systems.