News for hackers. Stuff that matters.
Re:Debian elects new project leader, PPA support proposed by structural on Monday April 20, 2015 @11:46AM (#9408856)
See my other comment, but hosting's the easy part, managing packages from "packaged, this afternoon, works on dev's machine" to "tested and works for a couple thousand people, let's deploy this" is the challenge. The bad ways of doing this involve every team setting up their own repos (differently! ha!) to test things before pushing them up a level. This happens a lot, absent defined structure. So does things like e-mailing packages around, two people bumping a version number to the same thing, and so on.

I completely agree that developers shouldn't be making ops decisions and have scars to prove it.

Re:Debian elects new project leader, PPA support proposed by stephenr on Monday April 20, 2015 @07:26PM (#9411439)
Right yes I understand now, and agree.

I wasn't saying the existing systems are foolproof, but I don't think PPA's add anything to help the problem you're describing.

Ah and I just realise you were originally replying to the bit about "dpkg-scanpackages and a Makefile”!

Re:Debian elects new project leader, PPA support proposed by regularfry on Tuesday April 21, 2015 @12:08PM (#9415011)
In an ideal world, we'd only be getting packages built on integration test passes, and automatically pushed from CI. I've got that for some cases, but it's still a manual push process for others.
Re:Debian elects new project leader, PPA support proposed by xorcist on Monday April 20, 2015 @12:09PM (#9409041)
Why do you run into that situation? Do your developers not have access to your interal repo? Emailing packages around sounds like a symptom of a process problem.