17

No, I agree that one shouldn't have been closed. This is a surprising change since apt-get has been the standard for many years and even experienced users might have been blindsided by it. I had completely misunderstood the situation. I thought that Debian and, by extension Kali, no longer used apt-get and only shipped with apt. I thought this was a new ...


11

The question was put on hold as "unclear" (and later automatically deleted as it was never updated). It is unclear because you failed to include information about the message that you saw on screen. We generally don't like images in questions, but we recognise that it's sometimes difficult to transcribe text that can't easily be copied and pasted into ...


8

Your question seems to have very little to do with Linux. It doesn't matter that you're developing on a Linux machine; the question is about how something in C# works. As explained in the Help Center: If your question is a programming question, requiring knowledge of programming languages other than unix shell scripting languages, ask on Stack Overflow. ...


8

I went ahead and reopened it. I can't guarantee it will remain that way since the original question was indeed more of a programming issue than *nix so I won't insist if others vote to close it again. Still, having a shell-based answer sounds useful so let's see how it goes. Go forth and claim your badges!


6

Ideally, closure (apart from duplicates) should be a temporary state. A question should either be open or deleted. If a question is closed, it means that we aren't confident that we can provide quality answers, so we shouldn't expose those answers to the world. And a question that has no answers and no means to add one is not useful either. So if a question ...


6

I can’t answer for the users who voted to close that question; however I think at least part of the problem comes from the way you’ve framed the question, which doesn’t quite match what you’re saying here. A question about “how to maintain a package with separate patches?” would be fine from my point of view; while it wouldn’t necessarily receive an ...


4

Let's not argue about a specific case, but about the general problem. In general, over the last 30 days, 588 questions were closed. 24 of them were reopened, which sounds low, but only 93 of them were ever edited after being closed; most are just bad questions that get abandoned. Users with 3000 reputation that can vote to close/reopen also have access to ...


4

The closed question will remain closed even if we decide it's not a dupe. It is asking 3 questions at once and that would make it too broad anyway. In any case, if you feel you have something to add with respect to the distinction between "computer terminal" and "virtual console", by all means either add your own answer to the dupe's target (you could ...


3

For what it's worth, I can see why you're frustrated about this. Now I notice how the site behaved, I am really weirded out by it. But I don't think that means we should undo this specific duplicate. It is a good fit for the rest of the duplicate features. The people who write the site features don't necessarily read questions here, on Unix & Linux ...


3

After looking at that question, it would seem that the reason it received so many downvotes is that it was originally very unclear – and the question was closed for that reason. After it was closed, the OP edited the question so that it’s much clearer and more specific. They then self-answered their question, which is usually fine but in this case, the ...


3

If a question is closed and you don't think it's worth reopening, then it's usually not worth editing. Ideally, all closed questions should be either reopened or deleted. One thing that is worth editing about closed questions is their tags. Questions that were missing important tags may have failed to reach the subject experts who would have been able to ...


2

It's an old question, by a user who hasn't visited the site in two years. Its original version was hard to understand, it was closed and then edited to a different question, and it has a single answer which doesn't answer either the original or the edited version. The asker didn't seem to know what they wanted, so it's doubtful what answer would have helped ...


2

That's a feature. In general, there is little point in editing a closed post unless you want to improve it for reopening. If you don't want it to enter the reopen queue, don't edit it. That said, I too am guilty of doing this. It seems that you too are one of those pedantic people who can't stand seeing mistakes in a text without fixing them. I share your ...


2

It's been reopened. You can just flag for mod attention next time (the "flag" link under the post).


1

Your question is on-topic here, and this is the most appropriate site for it. The problem with it is that there isn't enough information to answer. Most distributions' packages are not meant for unprivileged installation. Why do you want to use a distribution package rather than compile the upstream source, if you aren't going to do a system-wide ...


1

The reason I VTC'd is because there is no one way. There's no accepted way. There's not even (IMHO) any universal good way... there's just things that are trade offs. There's not even an accepted way of dealing with OS level packages (see the old flame wars between dpkg/apt and rpm/yum... let alone the old SysV way of pkg files, and let's not forget AIX ...


Only top voted, non community-wiki answers of a minimum length are eligible