On Mon, Feb 10, 2020 at 6:18 AM Dmitry Smirnov wrote: > On Saturday, 8 February 2020 1:49:20 PM AEDT Paul Wise wrote: > > There is one attribute of how Debian does things that clashes with > > being able to do this; service maintainers need to be able to update > > code on a different schedule to Debian stable and even backports > > time-frames. > > When service maintainers build their services from upstream repositories
There is more to services than just upstream code, for example for the Debian wiki, we install the python-moin package, checkout the git repo to /srv/wiki.debian.org/ and we also have the private code and configs for the anti-spam system. My comment here mostly refers to the additional git repos that service maintainers store configuration, additional scripts and other service-specific code rather than to the upstream packages the services might be based on. I do acknowledge that some services do need to use fast-moving upstream projects though. https://salsa.debian.org/debian/wiki.debian.org/ > I think ideally service maintainers should be package co-maintainers. But > when there is a large burden to maintain either (the service and the > package), I understand how people might focus just on one thing. > But again, if everything we do here is about providing packaged software, > when it is ever the right thing not to use our own packages? > Certainly we don't trust upstream more than our fellow developers, right? Using packaged software could be the ideal situation, but I think that reality is more complicated and that we aren't able to use packaged software for a number of debian.org services. -- bye, pabs https://wiki.debian.org/PaulWise
