Bug#769907: general: non-sysvinit init systems are made of fail
On 19 November 2014 16:12, Gunnar Wolf <gwolf@gwolf.org> wrote:
> Before anything else, Michal: Please remember Debian is a
> volunteer-run project. It is sometimes tempting to reply mails in a
> haste and making ironic remarks to drive your points further. But
> mails such as this one are not welcome in Debian. Please assume good
> faith, and treat everybody with respect.
Note that the ironic remark about my system saying Ubuntu in the
release was after a few mails about the init systems failing in qemu
with freshly bootstrapped system.
I would prefer that people read what they reply to. I admit that
getting carried away and continuing with more ironic remarks is not
constructive, either. Sorry.
>
> Michal Suchanek dijo [Wed, Nov 19, 2014 at 09:34:22AM +0100]:
>> Sure, it's always user error when something fails. Systems upgraded
>> from Ubuntu are not supported, systems upgraded from Debian are not
>> supported, nor are systems freshly bootstrapped and booted inside
>> qemu. Because all these fail.
>
> Upgrading from Ubuntu to Debian is not supported. The two
> distributions share a lot, but differ also a lot, and there will be
> cruft left that can get in the way for anything repeatable. Having
> repeatable results is key for bug resolution.
>
> Ubuntu has several package versions which have never been in a Debian
> Stable release. Upgrades are only supported from Debian - Be it from a
> stable to a newer stable release, or between points in time in testing
> and unstable. We have strict policies to ensure version madness will
> not bite us, but we cannot cover the range of combinations that will
> bite you if you sidegrade from Ubuntu — Or from any other derived distribution.
>
>> However, I had this biased personal opinion that the goal of the
>> Debian project should to remove Debian bugs on systems that do run
>> Debian. Please corect me if this is too disconnected from reality.
>
> You are right. But we can only do so in a way that is connected to
> what the policies dictate. We can only do so while keeping sanity. If,
> for example, you run this script:
>
> for i in $(find /usr/lib)
> do
> echo FOO >> $i if $RANDOM > 25000
> done
>
> I can assure you nobody will attempt to support your system.¹ If the
> user breaks it beyond what we can provide and support, we cannot
> support it.
>
> Again: There are only so many resources available in a volunteer
> project. Of course, you can provide the funding for somebody to get in
> your computer and fix the breakage. But Debian does not support such a
> use case.
>
> ¹ Yes, such trivial modifications can be detectable, and we could tell
> you to reinstall the affected packages, and.... But I guess you get
> my point!
I have no Ubuntu packages in my system but the release string remains.
I did not request that the string be corrected exactly because there
is no reason it should.
Thanks
Michal
Reply to: