search

archlinuxcn / repo

Arch Linux CN Repository
1.51k stars 291 forks source link

Vote: How to handle orphaned packages that are still used? #1676

Closed yan12125 closed 4 years ago

yan12125 commented 4 years ago

问题类型 / Type of issues

受影响的软件包 / Affected packages

In some cases, orphaned packages are listed in repo_depends of other packages. With current lilacbot, orphaned packages are just removed if nobody adopts them in 14 days, and thus packages using them are broken. Users can no longer install broken packages solely from [archlinuxcn], and the repo_depends field become invalid - it contains non-existent packages.

For example, lib32-libmng is orphaned and then removed on May 20, 2019 [1]. After that date, lib32-qt4 is broken until lib32-libmng is re-added on Apr 10, 2020 [2].

I'd like to propose changes to the policy and code, so that packages depending on orphaned packages will continue to work. Here are some possible approaches:

Please discuss and vote for the option you prefer or propose other options, thanks!

Related issues and pull requests:

[1] dedbaec [2] 8f535d9

yuyichao commented 4 years ago

Leaving the package up for adoption while in the meantime send any build failures to the maintainer of the dependent?

yan12125 commented 4 years ago

Leaving the package up for adoption while in the meantime send any build failures to the maintainer of the dependent?

Sounds good!

oldherl commented 4 years ago

I would like lilac to comment on the orphaning request (github issue) about any repo_depends on it and don't delete the package until all dependencies are removed or the orphaning package is now maintained by others. Lilac should notify all the maintainers of packages that depends on the orphaning package as soon as the orphaning starts, because some packages might not get update and/or rebuilds in the 14-day period,

lilydjwg commented 4 years ago

Things to do when the package being orphaned is dependent:

Anything else?

yan12125 commented 4 years ago

"packaging errors" include build failures and nvchecker errors, right?

lilydjwg commented 4 years ago

On Sat, Jun 13, 2020 at 10:07:36PM -0700, Chih-Hsuan Yen wrote:

"packaging errors" include build failures and nvchecker errors, right?

Yes.

-- Best regards, lilydjwg

lilydjwg commented 4 years ago

I'm starting working on this, tracked by https://github.com/archlinuxcn/misc_scripts/issues/18.