Bug#1065831: document package specifiers for `upgrade`

2024-03-13 Thread Miguel Angel Rojas
Hi all, >> No. Without a package as an argument it won't. Thanks! You're right. Let me write it down here again: - "apt upgrade" (no argument) will never remove a package, only upgrade or install - "apt upgrade pkg_name" will remove, upgrade or install the required package to

Bug#1065831: document package specifiers for `upgrade`

2024-03-13 Thread Miguel Angel Rojas
Hi all, >> (modifiers btw is not a good word. I guess it was never documented so far partly as this is a rather advanced feature and mainly because naming things is hard) yes, we brought it up in our conversation but I agree it was not directly related to the subject as it was an apt advanced

Bug#1065831: document package specifiers for `upgrade`

2024-03-13 Thread Miguel Angel Rojas
Hi there, > If "apt upgrade" is saying that it removes packages, that is a bug, yes. @david: it is not a bug, apparently. To put everything in a nutshell: - "apt upgrade" can remove packages - "apt upgrade" accepts specific packages to be upgraded Therefore, this behaviour is expected

Bug#1065831: apt upgrade : it removes packages when it shouldn't.

2024-03-12 Thread Miguel Angel Rojas
Control: retitle -1 apt upgrade : it removes packages when it shouldn't.

Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)

2024-03-12 Thread Miguel Angel Rojas
which I don't really recommend for the reasons stated above). Anyway, I think some clarification is needed from the developers to shed some light on this. Regards On Tue, Mar 12, 2024 at 3:12 AM Wesley Schwengle wrote: > On Mon, Mar 11, 2024 at 11:32:24PM +0100, Miguel Angel Rojas wrote: > > > I

Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)

2024-03-11 Thread Miguel Angel Rojas
> I see. It looks like `apt upgrade ' behaves as `apt install > '. Which (to me) is unexpected behaviour, as the man page is quite >clear on its behaviour (man 8 apt-get): Well, clearly it shouldn’t. To begin with, “apt install” should mark a package as manual installed while “apt upgrade”

Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)

2024-03-11 Thread Miguel Angel Rojas
u requested. Regards On Mon, Mar 11, 2024 at 5:44 PM Wesley Schwengle wrote: > > Hi Miguel, > > On Mon, Mar 11, 2024 at 05:09:47PM +0100, Miguel Angel Rojas wrote: > > > I do not know, at times I'm also wondering why it doesn't do it, but I > > didn't > > >

Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)

2024-03-11 Thread Miguel Angel Rojas
settled down. I have a feeling that it is the same bug but there is no way to probe it with this transition going on. Regards On Mon, Mar 11, 2024 at 3:04 PM Wesley Schwengle wrote: > > Hello Miguel, > > On Mon, Mar 11, 2024 at 09:50:12AM +0100, Miguel Angel Rojas wrote: > > &

Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)

2024-03-11 Thread Miguel Angel Rojas
Hi Wesley, >This problem isn't because of apt, the problem is that gdb-minimal/gdb > dependencies cannot be satified. A full-upgrade is the equivalent of a > dist-upgrade which will remove packages to resolve the dependencies. The > problem you are facing is the t64 transition[1][2] where not

Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2

2024-02-11 Thread Miguel Angel Rojas
Hi Diederik, > While 'annoying', this is expected behavior. It tries to load the newest (-83) Yes, this is the expected behavior from our Linux kernel. However, I agree with you and these messages are very annoying and should be removed. > It could be it wouldn't be shown if it had already found

Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2

2024-02-11 Thread Miguel Angel Rojas
Hi Diederik, My bad. Let me explain again. Taking into account the firmware errors: - Realtek messages are fixed now. There are no actions to be done here. - iwlwifi: If you are still working on a new version containing the -83 file, that should fix some warning messages but not all of

Bug#1052012: plasma-workspace: sddm presents a white screen with no background nor buttons

2023-09-15 Thread Miguel Angel Rojas
Hi there, Downgrading the following packages: - sddm-themes-breeze - sddm-theme-debian-breeze to version 4:5.27.7-2 makes sddm fully usable again with no issues. It seems some changes have been made on version 4:5.27.8-1 that have broken sddm. I hope this helps. Regards

Bug#1040174: nvidia-driver: Can't upgrade to nvidia-driver-525.116.04-1 on debian unstable: build fails

2023-07-03 Thread Miguel Angel Rojas
Hi there, I can confirm the bug is there. Libraries are not found and NVIDIA driver fails to build. Regards

Bug#934648: Acknowledgement (nvidia-kernel-dkms: Nvidia 418.74 does not build with kernel 5.2.0 (put_user_pages))

2019-08-16 Thread Miguel Angel Rojas
Hi all, It seems the problem is fixed with the new release (418.88) Thanks On Tue, Aug 13, 2019 at 12:42 AM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 934648: >

Bug#799948: Plasma desktop is unable to start (black screen - panic)

2015-10-20 Thread Miguel Angel Rojas
> > > I must first say that I am absolutely not familiar with KDE, the QT > environment and how it works. But the thread that raises the abort > doesn't look like it's in the GL libraries code: > > Maybe there's some context I'm missing. Forgive me for asking, but are > you sure this is due to the

Bug#799948: Plasma desktop is unable to start (black screen - panic)

2015-10-19 Thread Miguel Angel Rojas
Hi Luca,​ Here you have the report you asked about the plasmashell. I do not know if it could be related to a configuration issue, but again very easy to reproduce. Here you have 2 reports (same error in 2 consecutive log on sessions). These crashes are related to the plasmashell (I manually

Bug#800938: Bug#799948: Plasma desktop is unable to start (black screen - panic)

2015-10-18 Thread Miguel Angel Rojas
Hi Luca, Thanks for the quick answer! Here you have both report you asked for. Hopefully it will help us to know where the issue is. Regards On Sun, Oct 18, 2015 at 9:43 PM, Luca Boccassi <luca.bocca...@gmail.com> wrote: > On Sun, 2015-10-18 at 20:16 +0200, Miguel Angel Rojas wrot

Bug#799948: Plasma desktop is unable to start (black screen - panic)

2015-10-18 Thread Miguel Angel Rojas
Hi all, Vladimir is right, same issue here. Indeed, It is weird to me not so many people is currently reporting on it, but it is affecting a lot of programs. Something happens when upgrading to version 0.6.x (I agree at this point) plasma-desktop is also unable to start and panic (black

Bug#693512: [Pkg-utopia-maintainers] Bug#693512: network-manager: Network manager does not remove default routes

2012-11-19 Thread Miguel Angel Rojas
Hi Michael, Thanks for the troubleshooting. I think we have several options here (as far as I see). We can also combined some of them: - Modify ifupdown to be aware of networkmanager installation (as you suggested) - Modify networkmanager to remove/modify/backup /e/n/i interfaces managed

Bug#651229: console-setup: ckbcomp not found when booting

2011-12-07 Thread Miguel Angel Rojas
Hi Anton, I see you point. I am not an expert on this but here are my thoughts: - If ckbcomp could not be called at boot time... why this is inside in /bin/setupcon (which is called at boot time)? Same idea for the other binaries you mentioned - How is the preliminary keymap

Bug#572655: libopenipmi0 depends on non-existing package libglib1.2ldbl

2010-03-05 Thread Miguel Angel Rojas
Package: libopenipmi0 Version: 2.0.16-1.1 Severity: grave # aptitude install libopenipmi0 Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information... Done Initializing package states... Done Reading task descriptions... Done The

Bug#513142: ucf/dbconfig warning when package is installed

2009-01-27 Thread Miguel Angel Rojas
Hi Michael, Here is the version I use (I think is the lastest one): # dpkg -l | grep dbconfig ii dbconfig-common 1.8.40 common framework for packaging database applications Thanks for your quick reply. Today, I've upgrade the rest of the packages you

Bug#513012: Confirmed using old vars in zabbix.conf.php from zabbix developers

2009-01-27 Thread Miguel Angel Rojas
Hi, It is confirmed that variable parameters we are using are not the one zabbix are using right now. The reason why DB_* vars are still working is for compatibility reason for older versions. Here you have the link: http://www.zabbix.com/forum/showthread.php?t=11593 Michael, do