I believe that this is correct. xresprobe is no longer installable on the
latest release because of the complete switch to systemd.
On Wed, Aug 24, 2016 at 8:33 AM, UbuntuH8r <email address hidden> wrote:
> Hi. I'm the Debian dev.
>
> Could it be that the reason for this is because the xresprobe package is
> not available?
>
> Marcia
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1576606
>
> Title:
> isolinux issue
>
> Status in Respin:
> New
>
> Bug description:
> I tested the latest wily package earlier this week, and the isolinux
> dependency does not appear to have "taken" for Xubuntu respins. Xenial
> Xubuntu's has the same problem, i.e. I need to install the isolinux
> package manually and then it works. I tested that out today. Oddly, it
> does work on the regular Ubuntu releases.
>
> Thanks for your excellent work on this package.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/respin/+bug/1576606/+subscriptions
>
I believe that this is correct. xresprobe is no longer installable on the
latest release because of the complete switch to systemd.
On Wed, Aug 24, 2016 at 8:33 AM, UbuntuH8r <email address hidden> wrote:
> Hi. I'm the Debian dev. /bugs.launchpad .net/bugs/ 1576606 /bugs.launchpad .net/respin/ +bug/1576606/ +subscriptions
>
> Could it be that the reason for this is because the xresprobe package is
> not available?
>
> Marcia
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> isolinux issue
>
> Status in Respin:
> New
>
> Bug description:
> I tested the latest wily package earlier this week, and the isolinux
> dependency does not appear to have "taken" for Xubuntu respins. Xenial
> Xubuntu's has the same problem, i.e. I need to install the isolinux
> package manually and then it works. I tested that out today. Oddly, it
> does work on the regular Ubuntu releases.
>
> Thanks for your excellent work on this package.
>
> To manage notifications about this bug go to:
> https:/
>