-
Notifications
You must be signed in to change notification settings - Fork 10
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
"Can't create backup status file" #2
Comments
I've wrote `kpkg`, a little shell wrapper around dpkg. It get rid of that,
and add automatical download feature, apt-get like.
2017-05-20 9:36 GMT+02:00 Kevin Boone <notifications@github.com>:
… Seen when installing a new package. This seems to be a defect in the
Busybox dpkg implementation. A directory gets created,
/var/lib/dpkg/udeb.status.backup, which dpkg then tries to delete as a
file. The workaround is to delete the directory manually.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFYuM-t5RkgFxH_RPbEtqbaK8pKoe8UVks5r7pgZgaJpZM4NhOLY>
.
|
HI
Would be willing to share this? Is it in a repository somewhere?
Best wishes
Kevin
…On 05/20/2017 09:24 AM, giuliolunati wrote:
I've wrote `kpkg`, a little shell wrapper around dpkg. It get rid of that,
and add automatical download feature, apt-get like.
2017-05-20 9:36 GMT+02:00 Kevin Boone ***@***.***>:
> Seen when installing a new package. This seems to be a defect in the
> Busybox dpkg implementation. A directory gets created,
> /var/lib/dpkg/udeb.status.backup, which dpkg then tries to delete as a
> file. The workaround is to delete the directory manually.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#2>, or mute the thread
>
<https://github.com/notifications/unsubscribe-auth/AFYuM-t5RkgFxH_RPbEtqbaK8pKoe8UVks5r7pgZgaJpZM4NhOLY>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>, or
mute the thread
<https://github.com/notifications/unsubscribe-auth/AJ71Xj1Q7Z0xkfKa_46sI5j2Kln7a6EYks5r7qMigaJpZM4NhOLY>.
|
Pushed it in source/misc, see kpkg-help.txt
`kpkg -i` works around `dpkg -i` bug
Nite!
Giulio
Il 20/mag/2017 14:27, "Kevin Boone" <notifications@github.com> ha scritto:
… HI
Would be willing to share this? Is it in a repository somewhere?
Best wishes
Kevin
On 05/20/2017 09:24 AM, giuliolunati wrote:
> I've wrote `kpkg`, a little shell wrapper around dpkg. It get rid of
that,
> and add automatical download feature, apt-get like.
>
> 2017-05-20 9:36 GMT+02:00 Kevin Boone ***@***.***>:
>
> > Seen when installing a new package. This seems to be a defect in the
> > Busybox dpkg implementation. A directory gets created,
> > /var/lib/dpkg/udeb.status.backup, which dpkg then tries to delete as a
> > file. The workaround is to delete the directory manually.
> >
> > —
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly, view it on GitHub
> > <#2>, or mute the thread
> >
> <https://github.com/notifications/unsubscribe-auth/AFYuM-t5RkgFxH_
RPbEtqbaK8pKoe8UVks5r7pgZgaJpZM4NhOLY>
> > .
> >
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#2 (comment)>, or
> mute the thread
> <https://github.com/notifications/unsubscribe-auth/AJ71Xj1Q7Z0xkfKa_
46sI5j2Kln7a6EYks5r7qMigaJpZM4NhOLY>.
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFYuM7C0QqbWf3tn9x6ntdWXic9GWHzaks5r7txHgaJpZM4NhOLY>
.
|
Hi, |
Which error in kpkg?
However:
`rm -r /var/lib/dpkg/status.udeb.bak`
Il mar 3 apr 2018, 21:52 blumey <notifications@github.com> ha scritto:
… Hi,
I attempted to bypass this issue by using the kpkg shell but it did not
work. How you delete the directory manually, as you suggest?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFYuMwA0bYl4d9c_OuYDH-JL185vKwF8ks5tk9MYgaJpZM4NhOLY>
.
|
Hi Guilo, I was unable to copy and paste the kpkg bypass code into my terminal enumerator so I ended up typing the code by hand. The first time I did this the terminal quit out once I entered line 153 (I believe it was esoc) and the second time it showed some new command patterns, but did recognize any command with kpkg. Maybe it's just my own human error inputing the code. |
Try this
Il mer 4 apr 2018, 00:09 blumey <notifications@github.com> ha scritto:
… Hi Guilo,
I was unable to copy and paste the kpkg bypass code into my terminal
enumerator so I ended up typing the code by hand. The first time I did this
the terminal quit out once I entered line 153 (I believe it was esoc) and
the second time it showed some new command patterns, but did recognize any
command with kpkg. Maybe it's just my own human error inputing the code.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFYuMzZ2FUGHx7Xob10r8I63C04CgMoHks5tk_MIgaJpZM4NhOLY>
.
|
That worked thank you! Another question, once I have the packages installed, how do I get them running (so that they can be used)? I am new to Android so I am not well-versed on the command language. For example, how to do I start engaging with the gnuchess package? |
@kevinboone @giuliolunati Would you be able to help me configure and run the packages I have downloaded? I do not know the commands to do so. |
Seen when installing a new package. This seems to be a defect in the Busybox dpkg implementation. A directory gets created, /var/lib/dpkg/udeb.status.backup, which dpkg then tries to delete as a file. The workaround is to delete the directory manually.
The text was updated successfully, but these errors were encountered: