Bug 194488 - app-backup/backup-manager-0.7.5 ~amd64 keyword request
Bug#: 194488 Product:  Gentoo Linux Version: unspecified Platform: AMD64
OS/Version: Linux Status: RESOLVED Severity: enhancement Priority: P2
Resolution: FIXED Assigned To: amd64@gentoo.org Reported By: cyril.mougel@gmail.com
Component: Ebuilds
URL: 
Summary: app-backup/backup-manager-0.7.5 ~amd64 keyword request
Keywords:  KEYWORDREQ
Status Whiteboard: 
Opened: 2007-10-02 09:42 0000
Description:   Opened: 2007-10-02 09:42 0000
I have test an ebuild with keyword : ~amd64 and the compilation works.

The programm has no problem after compilation.

Please release it the 0.7.5 version with keyword ~amd64

Reproducible: Always

------- Comment #1 From Wulf Krueger (RETIRED) 2008-03-02 13:48:00 0000 -------
Andrej, when testing this, I get lots of missing binaries. Is that ok or are
those really missing deps? If those are optional deps, could you maybe add a
post-install message about them? And is there any test plan for this?

Cyril, your input to the above questions would help, too, of course. :-)

which: no zip in
(/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.2:/opt/blackdown-jdk-1.4.2.03/bin:/opt/blackdown-jdk-1.4.2.03/jre/bin)
which: no gpg in
(/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.2:/opt/blackdown-jdk-1.4.2.03/bin:/opt/blackdown-jdk-1.4.2.03/jre/bin)
which: no lzma in
(/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.2:/opt/blackdown-jdk-1.4.2.03/bin:/opt/blackdown-jdk-1.4.2.03/jre/bin)
which: no dar in
(/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.2:/opt/blackdown-jdk-1.4.2.03/bin:/opt/blackdown-jdk-1.4.2.03/jre/bin)
which: no rsync in
(/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.2:/opt/blackdown-jdk-1.4.2.03/bin:/opt/blackdown-jdk-1.4.2.03/jre/bin)
which: no mkisofs in
(/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.2:/opt/blackdown-jdk-1.4.2.03/bin:/opt/blackdown-jdk-1.4.2.03/jre/bin)
which: no growisofs in
(/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.2:/opt/blackdown-jdk-1.4.2.03/bin:/opt/blackdown-jdk-1.4.2.03/jre/bin)
which: no dvd+rw-format in
(/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.2:/opt/blackdown-jdk-1.4.2.03/bin:/opt/blackdown-jdk-1.4.2.03/jre/bin)
which: no cdrecord in
(/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.2:/opt/blackdown-jdk-1.4.2.03/bin:/opt/blackdown-jdk-1.4.2.03/jre/bin)
which: no mysqldump in
(/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.2:/opt/blackdown-jdk-1.4.2.03/bin:/opt/blackdown-jdk-1.4.2.03/jre/bin)
which: no svnadmin in
(/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.2:/opt/blackdown-jdk-1.4.2.03/bin:/opt/blackdown-jdk-1.4.2.03/jre/bin)

------- Comment #2 From Andrej Kacian (RETIRED) 2008-03-02 16:48:55 0000 -------
Those come from near the top of /usr/sbin/backup-manager, calls similar to:

zip=$(which zip) || true

The script simply searches for various tools it might need, without checking if
there are any jobs configured to use them.

I was wondering if I should add those as optional deps, but decided against it
in the end. The application gives nice verbose errors if it is missing some of
them, such as:

actions.sh:                             error "The BM_TARBALL_FILETYPE conf key
is set to \"zip\" but zip is not installed."


Do you think the optional deps are needed here (via USE flags) ?

------- Comment #3 From Santiago M. Mola 2008-03-05 09:00:46 0000 -------
(In reply to comment #2)
> 
> Do you think the optional deps are needed here (via USE flags) ?
> 

I don't think so, this kind of USE flags are evil. A pkg_postinst message can
always help.

------- Comment #4 From Steve Dibb 2008-06-03 14:27:41 0000 -------
added ~amd64