Ошибка filed to find required file

Всем добрый день! Есть deb пакет, в котором в файле data.tar.xz есть папка usr, которая, в свою очередь, содержит папки bin и share. Если извлечь эти папки, приложение работает из любого места и ничего дополнительно не требует. Но, естественно, при запуске нет иконки приложения, ассоциаций файлов и т.п.
В связи с этим вопрос — а как правильно распихать содержимое deb пакета по папкам в альте?

Записан

Читайте на форуме про alien.

Записан

Андрей Черепанов (cas@)

alien -r имя_пакета.deb
В результате получите rpm-пакет, но без зависимостей.

Записан

Делаю от пользователя

alien -r /home/papa/Download/min_1.5.1_amd64.deb
Warning: alien is not running as root!
Warning: Ownerships of files in the generated packages will probably be wrong.

от рута так:

# alien -r /home/papa/Download/min_1.5.1_amd64.deb
Package build failed. Here's the log of the command (cd min-1.5.1; rpmbuild --buildroot='/root/min-1.5.1' -bb --target x86_64 'min-1.5.1-2.spec'):
rpmbuild: сборка пакетов запрещена для привилегированного пользователя

Записан

Делаю от пользователя
alien -r /home/papa/Download/min_1.5.1_amd64.deb
Warning: alien is not running as root!
Warning: Ownerships of files in the generated packages will probably be wrong.


Ну и?

Предупредило:

Warning: alien is not running as root!
alien не запускать как root

Warning: Ownerships of files in the generated packages will probably be wrong.
Владелец файлов в сгенерированных пакетах вероятно будет неправильным.

Проверьте права на файлы и каталоги в сгенерированном *.rpm

Например существующие различия alt и debian
alt linux: UID_MIN=500
debian: UID_MIN=1000

Даже навскидку без словаря:

Ownerships
owner — очевидно что речь идёт о владельце

of files
файлов

in the generated packages
в сгенерированных пакетах

will
will — будущее время

probably
предположение

be wrong
неверно, неправильно

из чего уже можно выстроить фразу и понять смысл.

« Последнее редактирование: 26.01.2017 18:29:56 от Speccyfighter »

Записан

Debian перешли на tar.xz, а alien в Альте об этом не знает и ругается, что tar.gz не найден.

alien -r min_1.5.1_amd64.deb
Warning: alien is not running as root!
Warning: Ownerships of files in the generated packages will probably be wrong.
в архиве нет пункта data.tar.gz

Я попробовал сделать пакет из распакованного каталога, но тоже не выходит, пишет:
Failed to find Requires
И что файл указан дважды: про каждый файл.

Записан

Предупредило:

Warning: alien is not running as root!
alien не запускать как root

Или не запущен как рут? По-моему тут настоящее длительное время.

Записан

Debian перешли на tar.xz, а alien в Альте об этом не знает и ругается, что tar.gz не найден.
alien -r min_1.5.1_amd64.deb
Warning: alien is not running as root!
Warning: Ownerships of files in the generated packages will probably be wrong.
в архиве нет пункта data.tar.gz

gzip: stdin: unexpected end of file
tar: Это не похоже на tar-архив
tar: Завершение работы с состоянием неисправности из-за возникших ошибок
Error executing "ar -p 'min_1.5.1_amd64.deb' data.tar.gz | gzip -dc | tar tf -":  at /usr/share/perl5/Alien/Package.pm line 481.

Я попробовал сделать пакет из распакованного каталога, но тоже не выходит, пишет:
Failed to find Requires
И что файл указан дважды: про каждый файл.

Всё равно у меня на сизифе круче:

$ alien -r min_1.5.1_i386.deb
Warning: alien is not running as root!
Warning: Ownerships of files in the generated packages will probably be wrong.
Package build failed. Here's the log of the command (cd min-1.5.1; rpmbuild --buildroot='/home/user/Загрузки/min-browser/min-1.5.1' -bb --target i386 'min-1.5.1-2.spec'):
Платформы для сборки: i386
Сборка для платформы i386
Processing files: min-1.5.1-2
Finding Provides (using /usr/lib/rpm/find-provides)
Executing: /bin/sh -e /tmp/.private/user/rpm-tmp.01fBlg
find-provides: running scripts (alternatives,debuginfo,lib,pam,perl,pkgconfig,python,python3,shell)
Finding Requires (using /usr/lib/rpm/find-requires)
Executing: /bin/sh -e /tmp/.private/user/rpm-tmp.dMfnws
find-requires: running scripts (cpp,debuginfo,files,lib,pam,perl,pkgconfig,pkgconfiglib,python,python3,rpmlib,shebang,shell,static,symlinks)
lib.req: WARNING: /home/user/Загрузки/min-browser/min-1.5.1/usr/share/min/min: overlinked libraries: /usr/lib/libcups.so.2
lib.req: WARNING: /usr/bin/min: library libnode.so not found
lib.req: WARNING: /usr/bin/min: library libffmpeg.so not found
lib.req: WARNING: /home/user/Загрузки/min-browser/min-1.5.1/usr/bin/min: overlinked libraries: /usr/lib/libcups.so.2
shebang.req.files: executable script /home/user/Загрузки/min-browser/min-1.5.1/usr/share/min/resources/app/node_modules/dexie/tools/release.sh is not executable
shebang.req: /home/user/Загрузки/min-browser/min-1.5.1/usr/share/min/resources/app/node_modules/nlp_compromise/cmd.js: node not found (skip)
/home/user/Загрузки/min-browser/min-1.5.1/usr/share/min/resources/app/node_modules/dexie/tools/release.sh: li'e 8: syntax error near unexpected token `{
/home/user/Загрузки/min-browser/min-1.5.1/usr/share/min/resources/app/node_modules/dexie/tools/release.sh: li'e 8: `update_version() {
shell.req: ERROR: /home/user/Загрузки/min-browser/min-1.5.1/usr/share/min/resources/app/node_modules/dexie/tools/release.sh: /bin/bash --rpm-requires failed
find-requires: ERROR: /usr/lib/rpm/shell.req failed
ошибка: /bin/sh failed
ошибка: Failed to find Requires

Записан

• Silver VIP
• 695 replies

• 9 years ago

  29 November 2013

Unfortunately, Webroot have not provided a way to re-download the web components as far as I know. You’ll need to uninstall, reboot, and reinstall it. Fortunately that should only take a few minutes.

 
Unless someone else has ideas.

—————————————- Business Products Sr. Community Leader and Expert Advisor — WSA-Enterprise administrator over 2000 clients First company to 1000+ WSA endpoints | Power User / Business Ambassador / WSA-C and WSA-E Beta tester Find me on Twitter!

• Author
• Fresh Face
• 2 replies

• 9 years ago

  29 November 2013

• Retired Webrooter
• 7721 replies

• 9 years ago

  29 November 2013

Hello there jmfinkel, 

 
This problem should actually have already been fixed: it was a problem a few weeks ago but a fix has already been released.  For some reason your computer did not receive the fix.  The LLPlugin file is specifically for the Password Manager browser extensions.  

 
There are a couple of options open to you.

 
1) There is a utility specifically for re-installing or removing the Password Manager browser extensions for IE, Chrome and FireFox.  (One run of the utility will look for all 3 browsers.)  You can download this utility HERE.  Note that the URL is directly from Webroot: this is not a third party utility or download.  This will usually fix your issue.

 
If running this utility and re-installing the toolbar fails to fix the problem, or it fails to actually accomplish re-installing, you may have run into the same problem I had a few weeks ago.  Once in a while Chrome is a bit touchy: having removed the toolbar extension it sometimes refuses to allow it to be re-installed.  There was another thread with this problem today by the way, and the solution is simple.  See my reply on HERE for more information.

 
2) You can also submit a Trouble Ticket.  The phone number may not be answered at the moment due to the main offices being closed for U.S. Thanksgiving Holiday weekend., but there are still support techs available and your trouble ticket will be received.  

 
3) You do not need the disk to re-install WSA. Use the links below in my signature area to locate the correct download.  Your CD will not have the most up to date version of the software anyway, but the downloads below do.    This is, however, probably not the best way as the browser extensions are a separate download.

New to the Community? Register now and start posting! «If you don’t learn something new every day, you need to pay more attention. I often get my daily learning here so grab a chair and stay a while!» WSA-Complete (Beta PC), WSA Mobile (Android), WSA Business Mobile (Android) WSA-Endpoint (PC- Some of the time…..)

• Retired Webrooter
• 7721 replies

• 9 years ago

  29 November 2013

New to the Community? Register now and start posting! «If you don’t learn something new every day, you need to pay more attention. I often get my daily learning here so grab a chair and stay a while!» WSA-Complete (Beta PC), WSA Mobile (Android), WSA Business Mobile (Android) WSA-Endpoint (PC- Some of the time…..)

• Gold VIP
• 13734 replies

• 9 years ago

  14 January 2014

Hello SeratonyUnl and Welcome to the Webroot Community Forums!

 
Great to hear the Toolbar fix tool worked for you so maybe you can pull up a chair and stay for a while as we are a great bunch here.

 
Cheers,

 
TH

• 3 replies

• 9 years ago

  15 February 2014

• Gold VIP
• 13734 replies

• 9 years ago

  15 February 2014

@ wrote:
Ok, seems to have worked. Thank you.

Great to hear Mike and your very Welcome! Hat Tip to David for the Idea earlier on in this thread!

 
Cheers,

 
Daniel 😉

• 3 replies

• 9 years ago

  25 February 2014

I set up a create-react-app and I’m trying to run App.js on localhost, but upon doing yarn start I get the following error message:

22:23 $ yarn start
yarn run v1.3.2
$ react-scripts start
Could not find a required file.
  Name: index.html
  Searched in: /Users/-----/Desktop/---/----/hw/HW-REPO/hw-name/public
error Command failed with exit code 1.

I’d already installed yarn with yarn install, so I’m not sure if there’s something wrong with my code or with the file structure.

Here’s the file structure:

app-name
 -client
   --public
     ---index.html
     ---manifest.json
   --src
     ---Components
        ----various folders
     ---App.js
     ---App.test.js
     ---index.js
 -database
 -model
 -gitignore
 -package-lock.json
 -package.json
 -server.js
 -yarn.lock

In my case I opened my wrong folder in vs code and was trying to run npm start from their and npm did not find the index.html in that path, so I looked the correct path and reopened the folder and got no issue. Hope this will help some new beginner.

1

$ yarn start
# yarn run v1.13.0
# warning ........package.json: No license field
$ react-scripts start
# Could not find a required file.
# Name: index.js`

1

Comments

• - hosts: host1
    remote_user: root
    tasks:
     - synchronize:
             src: /etc/httpd
             dest: /mytestfile
  

  Iam getting the following error.Could anyone help

  PLAY [host1] *******************************************************************
  
  TASK [Gathering Facts] *********************************************************
  ok: [13.71.122.117]
  
  TASK [synchronize] *************************************************************
  fatal: [13.71.122.117]: FAILED! => {"changed": false, "failed": true, "msg": "Failed to find required executable rsync in paths: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/sbin"}
          to retry, use: --limit @/ansible/hai_yaml.retry
  
  PLAY RECAP *********************************************************************
  13.71.122.117              : ok=1    changed=0    unreachable=0    failed=1
  

  • rsync is not installed … at least not in the given directories.

• @skothab…thanks for the replay……I have tried that..Even then iam getting same error.

• @arunmohan did you find a solution to this problem ? I have the same problem here: rsync is clearly installed (which rsync and whereis rsync locate it in /usr/bin and apt install rsync tells me everything is already up-to-date. and still getting error Failed to find required executable rsync in paths: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

• rsync was missing on the ansible controller so this suggested solution worked for me! I got the necessity to set also the become: true option, for the task, to avoid permission issues I faced.

Recents