![]() ![]()
|
@claydoh
Yes. But Debian and Ubuntu don't mutually replace their 'base-files' with each other every couple of weeks. Think of it this way: In June it's called: Windows 7. In July: Windows 10. In August: Windows 7. Would You accept that? As an administrator managing computers for other people? I'd say, You wouldn't. I wouldn't. Maybe, You would. EDIT: Imagine: You get a support phone call. You ask: What OS/Distribution do You run? Customer/YourMother looks under SystemSettings and sees "Ubuntu", but in reality it is Debian or KDE neon. That's the perfect way to enter into the interpersonal area of preprogammed misunderstanding and ensured failed communication. Simply an avoidably source of customer-support frustration and possible family-internal aggressiveness. |
![]() Registered Member ![]()
|
We are just nit-picking now, really.
fwiw, on my laptop, not updated in some days to a week, I have it that Ubuntu's base-files is replacing neon's, as Ubuntu just released 16.04.3, so it has a newer version number than neon's now. The real bug should be that Neon should set package or archive priorities to prevent this. My two Chromebooks didn't have this happen with GalliumOS's base-files even though it is (X)Ubuntu 16.04 based and has neon added to it on top of that.
claydoh, proud to be a member of KDE forums since 2008-Oct, and KDE user since 2001
|
![]() ![]()
|
@claydoh
I think, the solution should be: 1) Renaming KDE Neon's 'base-files' to 'base-files-neon' 2) Changing its control fields to: "Provides: base, base-files" 3) Using either 'update-alternatives' or pinning and 4) Renaming their archive from 'xenial' to 'xenialkdeneon' to make priority pinning easier. ### "nitpicking"? Really? |
![]() Registered Member ![]()
|
To whom it may concern,
Whenever a user has an issue with an OS, it is only natural for the person to go for an answer. As a user of the product, I am self-entitling myself to be worthy of an answer, although I know it's not the favored attitude. If this section of the forum does not serve the purpose of getting an official answer from the maker, then it is utterly futile (if not downright counterproductive). For a project of this magnitude, communication between maker and user via aforementioned apps or any social app for that matter is anything but appropriate. If anything has been messed up we shall still remain loyal to the project (whether a damn is given or not) but we need to know what's going on here. In all likelihood, the answer is reducible to a post no larger than this one. So it is not like we're asking for any entertainment of considerable length. I confess I had a hard time to decide whether to post or not. Regards, RA
Proud to be powered by Plasma
|
Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot], ourcraft