On Sun, 2015-09-27 at 14:21 -0400, Dave Steele wrote: > On Sun, Sep 27, 2015 at 12:24 PM, Adam D. Barratt > <a...@adam-barratt.org.uk> wrote: > > > > > +cloudprint (0.13-1+deb8u3) UNRELEASED; urgency=medium > > > > Where did you get that version number from? (specifically the "u3" bit.) > > From my attempt to understand updates versioning. It is a Jessie > updates candidate, which is modified from 0.13-1. I was unable to find > documentation leading me to a better understanding of what to put for > either part.
If it was unclear, asking was an option... In any case, this is "first stable upload to Debian 8", so +deb8u1. This is mentioned in https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#bug-security , I'm not entirely sure why it's specifically in the security section and not stable in general. > > I have to admit that I'm not personally particularly keen on the init > > system changes in a stable update - presumably there's nothing wrong > > with the sysvinit support in the package in Jessie? > > I don't have a strong reason for making the systemd change. I can > revert it, if it is deemed necessary. It means a larger patch against > 0.13-1. OTOH, I am getting a fair amount of grief outside of > Jessie/testing/sid for requiring systemd. What do you mean? (Also what's happening outside of Debian isn't really relevant in the majority of cases.) > > +Depends: python-cups, cups, python-daemon, ${misc:Depends}, > > + python (>= 2.7), python-pkg-resources, rsyslog | system-log-daemon, > > + python-requests > > > > Why does the python version need to be explicitly declared? Isn't that > > part of what ${python:Depends} is supposed to do? > > Jessie+ ${python:Depends} defines a dependency which includes a > multiarch reference. This breaks compatibility with outside > distributions that could otherwise run the package just fine (e.g. > Raspberry Pi/Raspbian is a popular target). I maintained a parallel > 'ppa' distribution for some time which only included that change, and > eventually decided the extra work wasn't worth it. Well, it includes a multiarch-dependency because that's how the Python packagers in Debian have arranged things. I have to admit to not being 100% sure of the consequences of dropping it, which makes me uneasy about doing it in stable. > This release will likely be the go-to release for those outside the > supported Debian ecosystem. I'd prefer to leave this as-is. > > > -Depends: cloudprint, ${misc:Depends}, > > - initscripts (>= 2.88dsf-13.3) > > +Depends: cloudprint, ${misc:Depends}, systemd > > > > Why does this need an explicit dependency on systemd? > > To make sure I have told e.g. Raspbian users that there is a > compatibility issue. Looks like I didn't need it. I'm not immediately convinced that adding dependencies in Debian to make sure that users outside of Debian are aware of something really makes sense. Regards, Adam
