Re: [(fwd): Debian/Stretch - network-manager_1.4.4-1 and libbluetooth3_5.43-1]
* deloptes[080217, 19:45]: > Ennio-Sr wrote: > > ... > > I don't see dependency between network-manager and bluetooth in jessie > No, the dependency is on 'libbluetooth3' for Stretch version of network-manager (1.6.0-1). No dependencies are shown for previous versions. > Even if NetworkManager is removed, you can still configure network easily. > Mmh, I started to feel lost when the 'route -n' showed no connection and 'ifup eth0' said 'unknown device' or something like that. Then I found older version 1.4.4-1, which is probably Jesiie's. Regards, Ennio -- [Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo. \\?// Fa' qualche cosa di cui non sei capace!" (diceva Henry Miller) ](°|°) [Why use Win$ozz (I say) if ... "even a fool can do that. )=( Do something you aren't good at!" (as Henry Miller used to say) ]
Re: [(fwd): Debian/Stretch - network-manager_1.4.4-1 and libbluetooth3_5.43-1]
Ennio-Sr wrote: > Of course, the deletion of network-manager is announced when you remove > libbluetooth3 but I think it should be stressed by a stronger axplicit > warning, also considering that while removing bluetooth one would not > expect that network-manager will vanish altogether and could not notice > the weak 'Remv network-manager ...' amon others. NetworkManager depends on bluetooth because it can configure network via bluetooth devices such as mobile phone, where you can use the phone as a modem. I don't see dependency between network-manager and bluetooth in jessie $ apt-cache show network-manager Depends: libc6 (>= 2.17), libdbus-1-3 (>= 1.0.2), libdbus-glib-1-2 (>= 0.102), libgcrypt20 (>= 1.6.0), libglib2.0-0 (>= 2.37.3), libgnutls-deb0-28 (>= 3.3.0), libgudev-1.0-0 (>= 165), libmm-glib0 (>= 1.0.0), libndp0 (>= 1.2), libnewt0.52, libnl-3-200 (>= 3.2.21), libnl-genl-3-200 (>= 3.2.21), libnl-route-3-200 (>= 3.2.7), libnm-glib4 (>= 0.9.10.0), libnm-util2 (>= 0.9.10.0), libpolkit-gobject-1-0 (>= 0.101), libreadline6 (>= 6.0), libsoup2.4-1 (>= 2.39.3), libsystemd0, libteamdctl0 (>= 1.9), libuuid1 (>= 2.16), init-system-helpers (>= 1.18~), lsb-base (>= 3.2-14), wpasupplicant (>= 0.7.3-1), dbus (>= 1.1.2), udev, adduser, isc-dhcp-client (>= 4.1.1-P1-4), libpam-systemd, policykit-1 Even if NetworkManager is removed, you can still configure network easily. regards
Re: [(fwd): Debian/Stretch - network-manager_1.4.4-1 and libbluetooth3_5.43-1]
* Cindy-Sue Causey[060217, 00:16]: > On 2/4/17, Ennio-Sr wrote: > > [...] > > Was your email signature attached to wherever this didn't arrive? I > just... I found this in my sp am bucket so maybe that's why it never > arrived where you sent. Maybe the signature is triggering something? I > [...] > Yes, it was, and it's 'pure text', no evil in it ;) Perhaps the addresses I used (shown in the 'apt-cache show' of the two pkgs, are reserved to developers. Theu were rejected with '550 Unroutable address'. > > > [...] > You said that you found what you needed in /var/cache/apt/archives? > The impression I got was that this is where deletions were going to be > made. Is it that you happened to have an older archive dotDeb that is > being left alone because it's pre this deletion thing? > Yes, the older version 1.4.4-1 had been preserved, whereas the new one, 1.6.0-1 had vanished. > Where are you seeing packages deleted from? No, I modified the default behaviour creating the file '01Keep-debs' in '/etc/apt/apt.conf.d' as suggested by the warning during the upgrade. > [...] > > Upon reading that something IMPORTANT was going to start being quietly > deleted as a default, my reaction was something along the lines of... > > An itty-bitty tiny little freakout for a second. > > And pretty much for the kind of reason it sounds like you're saying here. > Well, we don't know the underlying reason of this choice... > The more I think back on it, I specifically monitored dotDeb archive > file deletions for a few days after that message appeared, but I never > saw anything change. I heve no clue to this. > [...] > specifically k/t the fear of being cut off if I don't have the right What does 'k/t' mean? (Sorry, I'm not English mother tongue!) > > Just thinking out loud. I really don't have any other feedback... > except maybe... > > *ACK!* :D > I hope that is not for me! > Cindy :) Regards, Ennio -- [Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo. \\?// Fa' qualche cosa di cui non sei capace!" (diceva Henry Miller) ](°|°) [Why use Win$ozz (I say) if ... "even a fool can do that. )=( Do something you aren't good at!" (as Henry Miller used to say) ]
Re: [(fwd): Debian/Stretch - network-manager_1.4.4-1 and libbluetooth3_5.43-1]
On 2/4/17, Ennio-Srwrote: > Hi all! > I'm forwarding to the list this message which didn't reach the original > destination. I would have to get through bugzilla to report a bug, bat > this is not a bug. Although, I think it might help some onlookers... Was your email signature attached to wherever this didn't arrive? I just... I found this in my sp am bucket so maybe that's why it never arrived where you sent. Maybe the signature is triggering something? I find people in there all the time, and I can never tell what would have sent them there. They're just there. and I pull them out and put them back in my inbox... :) > - Forwarded message from ennio - > > Subject: Debian/Stretch - network-manager_1.4.4-1 and libbluetooth3_5.43-1 > Reply-To: Ennio-Sr > Date: Sat, 4 Feb 2017 20:27:00 +0100 > To: Debian Bluetooth Maintainers > > Cc: Utopia Maintenance Team > > > Hi! > As you certainly know (and I learnt recently), in the oncoming > Debian/Stretch version, the network-manager pkg depends on libbluetooth3 > so that when this package is removed network-manager will be removed as > well. > Now, considering that - if I understand well - the Stretch default > policy will be to delete all downloaded packages once they have beeen > installed (unless you modify default), a newby could have problems to > reconnect. > > AAMOF it happened to me a few days ago when, while struggling to pair an > apple wireless keyboard, I removed all bluetooth related packages and > remained 'isolated' from the world. Luckily enough I had a > network-manager package in the /var/cache/apt/archives and could solve > my problem. You said that you found what you needed in /var/cache/apt/archives? The impression I got was that this is where deletions were going to be made. Is it that you happened to have an older archive dotDeb that is being left alone because it's pre this deletion thing? Where are you seeing packages deleted from? I'm THRILLED you're instead having to go to /var/cache/apt/archives because that means maybe my horde of dotDebs is still safe from some default. Then again, I got back to my first paragraph where maybe you got lucky because you had an old archived compressed file that is "grandfathered in" and won't be touched by this default deletion thing? *ouch, grin* > Of course, the deletion of network-manager is announced when you remove > libbluetooth3 but I think it should be stressed by a stronger axplicit > warning, > also considering that while removing bluetooth one would not expect that > network-manager will vanish altogether and could not notice the weak > 'Remv network-manager ...' amon others. > > Thank you for the nice result of your work. This SOUNDS LIKE this is about something that caught my eye during an upgrade. Something started providing extensive messages during upgrades. I THINK the messages are k/t the package, apt-listchanges. "dpkg -s apt-listchanges" has this description with "changelog" and "NEWS" being the pertinent keywords: Description: package change history notification tool The tool apt-listchanges can compare a new version of a package with the one currently installed and show what has been changed, by extracting the relevant entries from the Debian changelog and NEWS files. Whatever is providing those messages, this topic about default deletions was one of those informative messages I now see these days. One of those messages recently made it sound like *something* was going to start being deleted by default upon upgrades or installs or something like that. That's what caught my attention. The only thing I could think that meant was the .deb archive files. Maybe that was even stated is why I thought that? Upon reading that something IMPORTANT was going to start being quietly deleted as a default, my reaction was something along the lines of... An itty-bitty tiny little freakout for a second. And pretty much for the kind of reason it sounds like you're saying here. The more I think back on it, I specifically monitored dotDeb archive file deletions for a few days after that message appeared, but I never saw anything change. Just for myself in my Shoes and therefore anyone else even close to it, immediately being cut off completely from anything is EXACTLY what first came to mind upon reading that message I saw. People in my Shoes don't have the luxury of just hopping into the car any ol' time of day or night and running down to the library or wherever to gain Internet access long enough to replenish whatever was zapped by any not well known default setting. Yeah, /var/cache/apt/archives is exactly where I thought things were going to start being deleted. In my case, that's a humongous directory specifically k/t the fear of being cut off if I don't have the right backup package to fix accidental
[(fwd): Debian/Stretch - network-manager_1.4.4-1 and libbluetooth3_5.43-1]
Hi all! I'm forwarding to the list this message which didn't reach the original destination. I would have to get through bugzilla to report a bug, bat this is not a bug. Although, I think it might help some onlookers... Regards, Ennio - Forwarded message from ennio - Subject: Debian/Stretch - network-manager_1.4.4-1 and libbluetooth3_5.43-1 Reply-To: Ennio-SrDate: Sat, 4 Feb 2017 20:27:00 +0100 To: Debian Bluetooth Maintainers Cc: Utopia Maintenance Team Hi! As you certainly know (and I learnt recently), in the oncoming Debian/Stretch version, the network-manager pkg depends on libbluetooth3 so that when this package is removed network-manager will be removed as well. Now, considering that - if I understand well - the Stretch default policy will be to delete all downloaded packages once they have beeen installed (unless you modify default), a newby could have problems to reconnect. AAMOF it happened to me a few days ago when, while struggling to pair an apple wireless keyboard, I removed all bluetooth related packages and remained 'isolated' from the world. Luckily enough I had a network-manager package in the /var/cache/apt/archives and could solve my problem. Of course, the deletion of network-manager is announced when you remove libbluetooth3 but I think it should be stressed by a stronger axplicit warning, also considering that while removing bluetooth one would not expect that network-manager will vanish altogether and could not notice the weak 'Remv network-manager ...' amon others. Thank you for the nice result of your work. Best regards, Ennio - End forwarded message - -- [Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo. \\?// Fa' qualche cosa di cui non sei capace!" (diceva Henry Miller) ](°|°) [Why use Win$ozz (I say) if ... "even a fool can do that. )=( Do something you aren't good at!" (as Henry Miller used to say) ]