Control: tags -1 + confirmed

Hello Steven Chamberlain.

Thanks for your bug report and patch! Very timely as I just spotted
the failure and that it's now a very big problem since sysvinit upload in
sid for non-linux.

I was pondering either your solution (not shipping uuidd in the uuid-runtime
package) or mark the entire uuid-runtime package as linux-any (instead
of any).
As I see it the main point of uuid-runtime package is to provide uuidd
(which is of debatable usefulness I guess), but maybe there's a point
in providing only the uuidgen utility on its own (it does not strictly
require uuidd).

Is there any particular reason you opted to only stop shipping uuidd only?

I don't have a clear convincing argument either way but when I try
to come up with arguments these are the one I can find:

 - uuidgen might be useful to have around on all archs?
 - not touching the debian/control file means I won't risk ending up in NEW.
 - maybe some day someone does upstream porting work on uuidd and then it's
   easy to start shipping it again.
 - still having uuid-runtime package around means it can satisfy the
   Recommends relation in libuuid1, while it's not really satisfying the
   reason for the relation - with is uuidd.

Neither are very convincing arguments but if you can't present any better
then I'll likely go with your patch given I assume it's atleast
somewhat tested and gets the FTBFS problem out of the way.

Either way, thanks for your input so far...

Regards,
Andreas Henriksson

Reply via email to