You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please make sure the version of deb-get you are using is up to date:
(excerpt)
...
Preparing to unpack .../deb-get_0.4.0-1_all.deb ...
Unpacking deb-get (0.4.0-1) over (0.4.0-1) ...
Setting up deb-get (0.4.0-1) ...
...
Done.
Expected behavior
deb-get update is resilient against missing information in GitHub packages when the source website changes and the commands return no data or garbage data.
Actual behavior
deb-get update throws an error because yet another package returns no data. This one is deborah, whatever that is.
[!] ERROR! Missing required information of github package deborah:
URL=
VERSION_PUBLISHED=
This error has existed for an unknown amount of time, because it was masked by the error in #997.
This is a recurring problem (#997#962#822) because deb-get doesn't gracefully handle the entirely foreseeable and obvious case where the fragile commands used to fill those variables returns nothing or returns garbage. It downloads data from external websites, not versioned APIs. Why is it not resilient against this? Why can't it WARN me and continue processing the rest of the package data? Updates still work, but installs don't. So now there are only 39 packages that users can install from scratch using deb-get.
Has not changed appreciably since #997, but I'll be glad to re-run if you think that has anything to do with this known and common error that you don't acknowledge, respond to Issues about, or say anything about like "hey, a fix is coming!"
Should we expect 2 more months before this mole is whacked without fixing the mallet/game/whatever updating deb-get for resilience is in this metaphor?
The text was updated successfully, but these errors were encountered:
KlfJoat
changed the title
"Missing required information of github package **deborah**"
"Missing required information of github package deborah"
Apr 16, 2024
Please make sure the version of
deb-get
you are using is up to date:(excerpt)
Done.
Expected behavior
deb-get update
is resilient against missing information in GitHub packages when the source website changes and the commands return no data or garbage data.Actual behavior
deb-get update
throws an error because yet another package returns no data. This one isdeborah
, whatever that is.This error has existed for an unknown amount of time, because it was masked by the error in #997.
This is a recurring problem (#997 #962 #822) because
deb-get
doesn't gracefully handle the entirely foreseeable and obvious case where the fragile commands used to fill those variables returns nothing or returns garbage. It downloads data from external websites, not versioned APIs. Why is it not resilient against this? Why can't it WARN me and continue processing the rest of the package data? Updates still work, but installs don't. So now there are only 39 packages that users can install from scratch usingdeb-get
.Steps to reproduce
Run
deb-get update
. Look at error on screen.System information
Has not changed appreciably since #997, but I'll be glad to re-run if you think that has anything to do with this known and common error that you don't acknowledge, respond to Issues about, or say anything about like "hey, a fix is coming!"
Should we expect 2 more months before this mole is whacked without fixing the mallet/game/whatever updating
deb-get
for resilience is in this metaphor?The text was updated successfully, but these errors were encountered: