You are not logged in.
Hey everyone, recently made the switch to #! Linux from windows 10, but i messed up during the network/source step i believe. And I am assuming that is the reason for me not being able to properly download various package such as java or print function. I have looked on the forums, and I have followed one of the suggestions which was to go into the source list and re-add in one the source however, I am not sure if i did that correctly. I also installed synaptics in order to fix the many broken packages which really didn't do much because they kept redirecting to previous builds/packages. I tried going on other forums to see if they had similar issues but i couldn't enter their commands into the terminal successfully. Any help on this would be much appreciated, thanks!
*Please tell me what i need to copy/paste or grab a screenshot
**Also, when i looked on synaptics, it said the bl-welcome was out of date but i was unable to upgrade it, is it a bug?
Last edited by kaboomist (2015-12-30 17:10:14)
Offline
Hi kaboomist it sounds as if you didn't enable a Debian mirror during installation. (The default is "yes".)
Others have had the same problem, for a solution see here for example:
https://forums.bunsenlabs.org/viewtopic.php?id=707
or here:
https://forums.bunsenlabs.org/viewtopic.php?id=227
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Huh, guess that fresh re-install didnt register for me when i was reading that post, i was busy trying to do that funky source list thing. Thanks for the links, esp. the second one!
Offline
so you went for the re-install?
btw, the source list thing isn't funky at all (or at least you are going to have a hard time with bunsenlabs, if editing a config file is beyond your comfort zone).
what i do find funky is that apt-get goes into lock up once something went wrong:
"You have held broken packages..."
- and one always has to fix that first before moving on.
anyhoos, would you agree that this thread could be marked [Solved] now?
Offline
what i do find funky is that apt-get goes into lock up once something went wrong:
"You have held broken packages..."
- and one always has to fix that first before moving on.
Just for the record, that should *never* happen in a pure Debian stable system.
That situation will only be encountered with testing/unstable or FrankenDebian systems.
Offline
^ i'm not quite sure i agree with you.
i mean, either: "it shouldn't happen" or "it never happens" but "it should never happen" does not compute in my brain.
but i'm not just splitting hairs; it is my experience that this can very well happen if e.g. the internet connection breaks down during install, or other ... quirks - on a pure debian stable system.
i mean, op's problem proves that, no?
Offline