New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rear package on ubuntu 14.04 depends on isolinux package (which does not exist) #1403

Closed
gdha opened this Issue Jul 6, 2017 · 9 comments

Comments

Projects
None yet
3 participants
@gdha
Member

gdha commented Jul 6, 2017

  • rear version (/usr/sbin/rear -V): 2.1
  • OS version (cat /etc/rear/os.conf or lsb_release -a): ubuntu 14.04
  • rear configuration files (cat /etc/rear/site.conf or cat /etc/rear/local.conf): OUTPUT=ISO
  • Are you using legacy BIOS or UEFI boot? BIOS
  • Brief description of the issue:
# apt install rear
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 rear : Depends: isolinux but it is not installable
E: Unable to correct problems, you have held broken packages.
  • Work-around, if any:
control:Depends: syslinux[!ppc64el], syslinux-common[!ppc64el], ethtool, ${shlibs:Depends}, lsb-release, xorriso, iproute, iputils-ping, isolinux, dosfstools, binutils, parted, openssl, gawk, attr, bc, ${misc:Depends}

should we remove isolinux from the control file as long as we support ubuntu14.04?

@gdha gdha added the bug label Jul 6, 2017

@gdha

This comment has been minimized.

Show comment
Hide comment
@gdha

gdha Jul 6, 2017

Member

Work-around to get it installed:

# apt-get download rear
# dpkg -i rear_2.1-0_amd64.deb 
Selecting previously unselected package rear.
(Reading database ... 39264 files and directories currently installed.)
Preparing to unpack rear_2.1-0_amd64.deb ...
Unpacking rear (2.1-0) ...
dpkg: dependency problems prevent configuration of rear:
 rear depends on ethtool; however:
  Package ethtool is not installed.
 rear depends on xorriso; however:
  Package xorriso is not installed.
 rear depends on iproute; however:
  Package iproute is not installed.
 rear depends on isolinux; however:
  Package isolinux is not installed.
 rear depends on gawk; however:
  Package gawk is not installed.

dpkg: error processing package rear (--install):
 dependency problems - leaving unconfigured
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Errors were encountered while processing:
 rear

# apt-get -f install

# dpkg  --ignore-depends isolinux -i rear_2.1-0_amd64.deb 
(Reading database ... 40706 files and directories currently installed.)
Preparing to unpack rear_2.1-0_amd64.deb ...
Unpacking rear (2.1-0) over (2.1-0) ...
Setting up rear (2.1-0) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Member

gdha commented Jul 6, 2017

Work-around to get it installed:

# apt-get download rear
# dpkg -i rear_2.1-0_amd64.deb 
Selecting previously unselected package rear.
(Reading database ... 39264 files and directories currently installed.)
Preparing to unpack rear_2.1-0_amd64.deb ...
Unpacking rear (2.1-0) ...
dpkg: dependency problems prevent configuration of rear:
 rear depends on ethtool; however:
  Package ethtool is not installed.
 rear depends on xorriso; however:
  Package xorriso is not installed.
 rear depends on iproute; however:
  Package iproute is not installed.
 rear depends on isolinux; however:
  Package isolinux is not installed.
 rear depends on gawk; however:
  Package gawk is not installed.

dpkg: error processing package rear (--install):
 dependency problems - leaving unconfigured
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Errors were encountered while processing:
 rear

# apt-get -f install

# dpkg  --ignore-depends isolinux -i rear_2.1-0_amd64.deb 
(Reading database ... 40706 files and directories currently installed.)
Preparing to unpack rear_2.1-0_amd64.deb ...
Unpacking rear (2.1-0) over (2.1-0) ...
Setting up rear (2.1-0) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
@schlomo

This comment has been minimized.

Show comment
Hide comment
@schlomo

schlomo Jul 6, 2017

Member

Maybe removing isolinux is an option, although on all other distros our agreement was IIRC that we want to include the dependencies to make the default config work.

Root cause is that Debian split the syslinux package without proving Provides for the old stuff.

I guess as long as we don't use different control files for different Debian versions we won't solve this problem. AFAIK there are no macros in control files that we could use to achieve a similar result to our spec file macros.

Member

schlomo commented Jul 6, 2017

Maybe removing isolinux is an option, although on all other distros our agreement was IIRC that we want to include the dependencies to make the default config work.

Root cause is that Debian split the syslinux package without proving Provides for the old stuff.

I guess as long as we don't use different control files for different Debian versions we won't solve this problem. AFAIK there are no macros in control files that we could use to achieve a similar result to our spec file macros.

@gdha gdha self-assigned this Jul 6, 2017

@gdha gdha added documentation and removed bug labels Jul 6, 2017

@gdha

This comment has been minimized.

Show comment
Hide comment
@gdha

gdha Jul 6, 2017

Member

If we add it to the FAQ page then we are fine I guess

Member

gdha commented Jul 6, 2017

If we add it to the FAQ page then we are fine I guess

@gdha gdha added this to the ReaR v2.2 milestone Jul 6, 2017

@schlomo

This comment has been minimized.

Show comment
Hide comment
@schlomo

schlomo Jul 6, 2017

Member

Yes, and also to the description of the DEB package. We could also add both the new and the old name as Recommends. People doing apt-get install will actually see that.

Member

schlomo commented Jul 6, 2017

Yes, and also to the description of the DEB package. We could also add both the new and the old name as Recommends. People doing apt-get install will actually see that.

@gdha

This comment has been minimized.

Show comment
Hide comment
@gdha

gdha Jul 19, 2017

Member

post-pone to release 2.3

Member

gdha commented Jul 19, 2017

post-pone to release 2.3

@gdha gdha modified the milestones: ReaR v2.3, ReaR v2.2 Jul 19, 2017

@gdha

This comment has been minimized.

Show comment
Hide comment
@gdha

gdha Jul 19, 2017

Member

Added to the FAQ section in the release notes of v2.2

Member

gdha commented Jul 19, 2017

Added to the FAQ section in the release notes of v2.2

@gdha

This comment has been minimized.

Show comment
Hide comment
@gdha

gdha Nov 17, 2017

Member

@schlomo So your suggestion is that we remove isolinux and xorriso from the Depends line and move these two to the Recommends line?
And, furthermore, add some comments about it in the Description part of the control file, right?

Member

gdha commented Nov 17, 2017

@schlomo So your suggestion is that we remove isolinux and xorriso from the Depends line and move these two to the Recommends line?
And, furthermore, add some comments about it in the Description part of the control file, right?

@schlomo

This comment has been minimized.

Show comment
Hide comment
@schlomo

schlomo Nov 18, 2017

Member

I think we can't provide a solution to this problem as long as we only build a single DEB for all Debian versions (or build from the same control file). So the "good" solution would be to expand our build tooling to have different control files - or parts of it - for different Debian version: New and old.

In the mean time we can add all the potential packages to Recommends to show the user that we would recommend to install those as well. Unresolvable Recommends shouldn't harm anybody.

And yes, removing the isolinux and xorriso packages from Depends will allow all Debian distros to install our ReaR package again.

As there is now a Debian maintainer who explicitly does not use our control file for his builds I think that this is the best we can do right now. In any case it only is relevant for those users building themselves or installing from OBS.

Member

schlomo commented Nov 18, 2017

I think we can't provide a solution to this problem as long as we only build a single DEB for all Debian versions (or build from the same control file). So the "good" solution would be to expand our build tooling to have different control files - or parts of it - for different Debian version: New and old.

In the mean time we can add all the potential packages to Recommends to show the user that we would recommend to install those as well. Unresolvable Recommends shouldn't harm anybody.

And yes, removing the isolinux and xorriso packages from Depends will allow all Debian distros to install our ReaR package again.

As there is now a Debian maintainer who explicitly does not use our control file for his builds I think that this is the best we can do right now. In any case it only is relevant for those users building themselves or installing from OBS.

gdha added a commit to gdha/rear that referenced this issue Nov 27, 2017

For Debian and Ubuntu package building and installation we move the p…
…ackages isolinux and xorriso from Depends to Recommends lines

See issue #1403
A word of warning: xorriso and isolinux will NOT install automatically - when not present if required rear will bail out.

And, also story gdha/rear-automated-testing#26 as background
@jsmeix

This comment has been minimized.

Show comment
Hide comment
@jsmeix

jsmeix Nov 28, 2017

Contributor

I assume this issue is fixed via
#1599

Contributor

jsmeix commented Nov 28, 2017

I assume this issue is fixed via
#1599

@jsmeix jsmeix closed this Nov 28, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment