Hi, > Hi Team, > > Since I was the first time and also the last one who touch the repo. > Could someone who has more experiemce may give me some hints on how to > clean up the current mess in `golang-go.crypto` repo or may clean up > the mess directly?
I can help with that but first you need to decide what to do with the upload to experimental and if you should put it into unstable or not. .. > > There are at least two reverse dependencies failing. Are you planning to > > fix them or shall we just abandon the experimental upload and continue > > with current version? > > > > Gitaly is already broken in debci and has unsatisfiable build > > dependency, it might be reasonable to ignore it for now. The version > > of golang-github-azure-azure-sdk-for-go is very old as the > > debian/watch is misconfigured and unaware of new versions. So to summarize, these broken ones are already broken or very old. The best option would be to fix them to not have broken packages in Debian, but if you are saying that is not the plan, then just ignoring them is a judgement call to make.
