is not a debian format archive как исправить
Не устанавливается пакет драйвера принтера на Linux Mint
Хочу установить драйвер на принтер canon на linux mint, выдает ошибку, у меня горит пукан уже.
И покажи вывод команды file cndrvcups-common_3.21-1_amd64.deb
По вики всё делали?
С архитектурой не промахнулись?
https://help.ubuntu.ru/wiki/canon_capt вот по этой делаю первый вариант с sh не получился скачал deb пакеты и установил жму печать принтер ничего не печатает.
То есть позапускали непонятные скрипты, не вникая, а теперь ничего не понятно.
Там ссылка на драйверы. После установки, в браузере наберите
Там настройте ваш принтер.
жму печать, но не печатает пишет выполнено и все почему так.
Хрустальный шар в ремонте, к сожалению.
Проверяйте настройки принтера.
потому что Linux Mint там свои глюки добавлены ставь Ubuntu
Ситуация аналогичная только устанавливаю на оригинальную ubuntu 20.04.02. Уже не первый год пользуюсь этой wiki страничкой (при переустановки системы, железо не менялось) всегда всё проходило гладко.
Сегодня скрипт выдал: dpkg-deb: ошибка: ‘cndrvcups-common_3.21-1_amd64.deb’ is not a Debian format archive
На file cndrvcups-common_3.21-1_amd64.deb ответ: cndrvcups-common_3.21-1_amd64.deb: HTML document, ASCII text, with very long lines
Возможно проблема с wiki-страничкой(скриптом) или Ubunta уже не-та?
dpkg-deb: error: ‘packages-microsoft-prod.deb’ is not a Debian format archive #3752
Comments
epomatti commented Nov 5, 2019
Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.
Details
Following the procedure I download this file:
Then I get the following when installing it:
My Ubuntu version (fully updated):
The text was updated successfully, but these errors were encountered:
We are unable to convert the task to an issue at this time. Please try again.
The issue was successfully created but we are unable to update the comment at this time.
dagood commented Nov 5, 2019 •
It works for me, maybe you hit a network or short-lived error and you ended up with an incomplete file or the error page’s html on disk? Try looking at the file contents, and downloading the file on another machine to try to make sure it’s not a proxy issue or something like that.
For me, in a Docker container:
epomatti commented Nov 5, 2019
@dagood oh boy that is exactly what happened, file was empty 0kb.
Tried downloading it again from within the WSL but got the same error, but downloading it from outside Windows got the correct file with 4kb. Thanks.
dagood commented Nov 5, 2019
Cool, thanks for confirming. 🙂
epomatti commented Nov 5, 2019
Well thought, here is the output: ERROR: cannot verify packages.microsoft.com’s certificate
dagood commented Nov 5, 2019
Interesting. I don’t quite know enough in this area. I do see a bunch of issues reported for other downloads online that suggest the WSL config in particular is somewhat fragile about this—having out of date or incomplete certificate authorities and stuff around that. I’ll leave it alone for now, thanks for the extra info.
epomatti commented Nov 5, 2019
If that is the case adding it to the store should do the trick. I’ll try it tomorrow.
epomatti commented Nov 7, 2019
@dagood solved it following this answer. Just had the same problem downloading the GoLang SDK.
After that I was able to download it directly from my WSL Ubuntu.
dagood commented Nov 7, 2019
leecow commented Nov 7, 2019 •
I wouldn’t expect them to have specific insights into WSL. I do agree we should do some work in this area and perhaps adjust docs and install instructions.
epomatti commented Nov 10, 2019
I tried adding the NuGet certificate manually as I did above but no bueno.
dagood commented Nov 11, 2019
I’d recommend looking at similar issues at https://github.com/microsoft/WSL/issues and filing one there to get at the root cause. I’d use a wget example for simplicity. A lot more people with relevant expertise there.
Going after the NuGet restore, I’m worried you might end up disabling a security feature in NuGet’s http client. (Not 100% sure that’s what you’d end up doing to work around that, but maybe. It also might not be possible to add a workaround on that end anyway.)
downloading and installing error: package is not a debian format archive
I’m a newbie to Linux and Ubuntu, and I’m trying to install a package called libstdc++2.10-glibc2.2 I first use wget
What am I doing wrong?
2 Answers 2
There is no package by the name of libstdc++2.10-glibc2.2. You can check this by going to the URL that you have mentioned in the question: http://packages.ubuntu.com/dapper/libstdc++2.10-glibc2.2.
When you run wget for the above URL, you end up downloading the web page (check the wget command output which states that you are downloading text/html).
In general you should install from the package management system (using the Software Centre or Synaptic or Muon or apt-get etc), instead of downloading deb files this way. Why do you want to install libstdc++2.10-glibc2.2? Are you actually using Ubuntu 6.06 Dapper Drake?
Not the answer you’re looking for? Browse other questions tagged package-management dpkg or ask your own question.
Related
Hot Network Questions
Subscribe to RSS
To subscribe to this RSS feed, copy and paste this URL into your RSS reader.
site design / logo © 2021 Stack Exchange Inc; user contributions licensed under cc by-sa. rev 2021.9.16.40232
By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.
Ubuntu Wiki
DebuggingInstallationIssues
This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages.
Introduction
This page lists some general issues that users might encounter while performing updates of their system. Apport will usually detect these failures and file a bug in Launchpad. These bugs can be identified by the bug tag ‘apport-package’ and can occur on nearly any package.
There are usually log file attached to the report which differs depending on the kind of install/upgrade:
Package install/upgrade: DpkgTerminalLog
Distribution upgrade: VarLogDistupgradeMain and VarLogDistupgradeApttermlog
Detailed informations about debugging updatemanager can be found at DebuggingUpdateManager.
Documented below are the most commonly reported issues. For each case there is a description and a sample report and when applicable there is a workaround or fix and the master report it should be marked a duplicate of.
Known issues
Corrupted package archive
These errors indicates a corrupted archive (.deb or files on disk) The root cause of the corruption may be a bad network connection, faulty hardware, hardware shutdown.
For those report the common workaround and stock response is:
sudo apt-get clean
sudo apt-get update
Then try performing the update again. This will likely resolve your issue. If so please set the bug’s status to Invalid. Thanks in advance!
Not a Debian format archive
Corrupted filesystem tarfile
—fsys-tarfile
The ‘short read’ error happens when trying to install a partially downloaded package. The front-end verify the integrity of the archive, but it is not the case if dpkg is invoked directly.
An input/output error is likely to mean filesystem corruption, hardware problems or no space left on hard disk. The typical errors are:
The suggestion is to run a manual fsck and look whether the hard drive or storage device is operating correctly (dmesg may contain helpful information too)
TODO: Write a standard response
Exec format error
Empty files or files filed with garbage are left on the hard drive. The file causing the dpkg error is one of /var/lib/dpkg/info/PACKAGE_NAME.p*
This error can occur either during installation or removal of the package.
During installation of a package
During removal of a package
Workaround A: Finish the install
Workaround B: Remove the package and reinstall
Then reinstall the package
Note: Change the package by the one which failed (check the log file)
triggers ci file contains unknown directive syntax
This is the same kind of issue than the one above. It means that the trigger file is empty or corrupted. The file is /var/lib/dpkg/info/PACKAGE.triggers This error can occur during installation or removal of a package.
During installation of a package
Workaround
lzma : decoder error
files list file missing final newline / contains empty filename
Typically these errors take the form :
files list file for package packagename contains empty filename
or
files list file for package packagename is missing final newline
Inconsistent state
Package in bad inconsistent state
Workaround A:
Please open a Terminal from the menu Applications->Accessories->Terminal and type or copy and paste the row below:
give your user password when requested, you don’t see nothing when you type it, then press enter.
Workaround B:
Then to reinstall :
sudo apt-get install flashplugin-installer
package is already installed and configured
Conditions of this failure are unknown. Please provide any additional informations in the master report.
Workaround A:
Workaround B:
Other issues
Can’t access archive
The source of this error is not clearly identified and needs further investigation (see comment #3 of the master report)
No space left on device
Bug 105113 was a request to detect this prior to performing any updates.
Bug 312491 was a request to report to the user when running out of disk space.
This error is self-explanatory.
DbDriver «config» is locked
/var/lib/defoma/locked exists
Under certain circumstances font packages failed to install with the following error:
Workaround
/etc/defoma/hints/FONTNAME.hints: Unable to open, or empty
Under certain circumstances font packages failed to install with the following error:
This is due to a corrupted hint file.
Workaround
To workaround it, open a terminal and run the following commands:
Non-bugs
Common issues arising from hardware failures, common invalid bugs for this category.
If the installation failed with no reason with an exit status 139, that the configuration script is trivial and there is no other report of this kind for that package, then this is very likely a memory corruption error.
The error from the term.log will show something like this:
There is not much we can do except the advice below:
Thanks for your report.
This looks like a hardware issue. Could you run memtest on your system? (boot a live CD / USB key and select test memory)
The reporter will most of the time says that the test reports error. If so, then close the report.
Note : an exit status 139 can also appear on other scenarios that aren’t related to faulty memory modules. For example, if you install a Hardy guest on a Lenny host using Xen, and then try an apt-get upgrade on the Hardy guest, that will fail with a segfault and an exit status 139 if you forget to disable /lib/tls as advised in the Xen Faq
Other resources
Add section ‘How to triage’ and merge the one from DebuggingUpdateManager
DebuggingInstallationIssues (последним исправлял пользователь andrew-wippler 2014-11-17 18:12:57)
The material on this wiki is available under a free license, see Copyright / License for details.
Восстановление Debian
Решил обновить свой Debian 7.1 wheezy до jessie, для этого я вводил:
После этого обновлялась целая куча пакетов, происходило всё это довольно долго, но в итоге в конце всего этого вылезла куча ошибок. Система не обновилась и осталась прежней, но теперь при aptitude-update вот такой вот гемор:
Вот мой sources.list :
Таких веток нет о чём и говорит error 404. Зайди браузером и убедись в этом. Стоило сначала сделать aptitude safe-upgrade, и отыкать варианты с минимумом обновлений, чтобы не всё сломалось сразу. И что значит система осталась прежней? Ты хотел убунту получить или новые обои?
Вроде там их нету. Попробуй с разными вариантами веток.
Вроде бы особо ничего и не сломалось, или я еще не полностью вник. Нет, я хотел обновится с стабильной версии до тестируемой. Но в итоге осталась стабильная (wheezy), и при aptitude update ошибки. собственно говоря, я их в выхлопе выкинул. Каким образом мне всё в прежнее состояние вернуть?
Как ты определил, что остался wheezy?
Зачем в прежнее состояние? Удали из конфигурацию несуществующие ветки и всё будет в порядке.
То есть, нужно из sources.list удалить всё лишнее?
хмм.. не помню где читал, но::
чтоб полностью обновиться, нужно сначала обновить apt, dpkg и несколько других файлов.. на заметку, чтоб скопом все не обновил..
насчет веток.. не все ветки существуют для определенной версии..
Удаляешь всю парашу из листа и добавляешь.
Сорцы рекомендую закомментить, они обычно не нужны. И в дальнейшем рекомендую использовать stable/testing/sid, чтобы не заморачиваться с ветками.
имхо, лучше не мешать ветки..
В каком месте я мешаю их?
Я не много мешаю ветки, но у меня настроен apt-pinning.
а я разве сказалъ?? просто заметка..
Зачем мне каждый релиз менять имена? Поставил стэйбл и у меня он всегда. Имена на сервере ещё можно как-то понять.
поставил стейбл, одно обновление и кирдык, уже научен..
Возможно что-то с руками и что такое «Кирдык»? Системник взорвался чтоле?
Что ты этим постом имел в виду?
Зачем Вам серверная ОСь, ставьте Бубунту.
В принципе можно на выбор apt или aptitude, но я обоими пользовался поэтому вот так.
поставил стейбл, одно обновление и кирдык, уже научен..
Это ты не научен, а бредишь.
aptitude update && apt-get update
aptitude upgrade && apt-get upgrade