gmane.linux.debian.devel.pkg-utopia

Bug#504918: [Debian Wiki] Update of"NewInLenny" : Upgrade over SSH issue

Michael Biebl — 2008-12-01T23:18:15

_______________________________________________ Pkg-utopia-maintainers mailing list Pkg-utopia-maintainers< at >lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-utopia-maintainers

Bug#504918: [Debian Wiki] Update of"NewInLenny" : Upgrade over SSH issue

Stuart Prescott — 2008-12-01T22:56:44

Hi Franklin, yes, indeed. These are indeed related bugs. In message #10 of #474352, the maintainer notes that this bug should be fixed now, or at least mitigated [ "minimize the downtime (with ethernet it's a matter of seconds)"]. Depending on the ssh settings and the user's reaction to seeing the upgrade hang, that may or may not work out OK. If it is a wireless connection, however, the downtime can be much longer and my experience is that it is likely to hang. Possibly -- but would they use network manager in such a situation? (I don't know). My feeling is that it would be fairly uncommon to upgrade over ssh for machines that actually used network manager; the intersection of upgrade-over-ssh and users of network manager (which is a desktop-centric tool) would seem small. As such, I had thought it was probably just a "document that you shouldn't do this" situation rather than an RC bug in network-manager. In the same way that upgrading over telnet or within a gdm session is not suppor

Bug#504918: [Debian Wiki] Update of"NewInLenny" : Upgrade over SSH issue

Michael Biebl — 2008-12-01T22:44:56

Processed: [Debian Wiki] Update of"NewInLenny" : Upgrade over SSH issue

Debian Bug Tracking System — 2008-12-01T22:12:02

Processing commands for control< at >bugs.debian.org: Bug#504918: Updating to lenny failed when NetworkManager got updated Severity set to `grave' from `normal' Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)

Bug#504918: [Debian Wiki] Update of"NewInLenny" : Upgrade over SSH issue

Frank Lin PIAT — 2008-12-01T19:35:15

severity 504918 grave -- [BCC Stuart Prescott: "stuart+debian AT nanonanonano net"] Hello Stuart, (I hope you are the right "Stuart") You added the following comment on the wiki page: On Mon, 2008-12-01 at 18:27 +0000, Debian Wiki wrote: [..] I didn't found a bug report from you. However I fount those two bug that are similar. * Network-manager shouldn't stop the network during an upgrade http://bugs.debian.org/474352 * Updating to lenny failed when NetworkManager got updated http://bugs.debian.org/504918 It looks like it could hurt many user that upgrade [lots of] desktops over ssh. Franklin

Processed: your mail

Debian Bug Tracking System — 2008-12-01T19:12:13

Processing commands for control< at >bugs.debian.org: Bug#504918: Updating to lenny failed when NetworkManager got updated Warning: Unknown package 'networkmanager' Bug reassigned from package `networkmanager' to `network-manager'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)

Bug#503652: Bug#503652: Do not restartpommed when restarting dbus

Julien BLACHE — 2008-11-30T10:24:24

Hi, Yep, I was concerned about keeping it in the loop for insserv. I'll do that. JB.

Bug#503652: Bug#503652: Do not restartpommed when restarting dbus

Michael Biebl — 2008-11-30T02:01:04

Bug#276105: marked as done (dbus-1: installation fails on upgrade from woody -> sarge)

Debian Bug Tracking System — 2008-11-30T01:54:03

Your message dated Sun, 30 Nov 2008 02:52:11 +0100 with message-id <4931F1CB.2030308< at >debian.org> and subject line Closing this bug report has caused the Debian Bug report #276105, regarding dbus-1: installation fails on upgrade from woody -> sarge to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner< at >bugs.debian.org immediately.)

Bug#507318: python-dbus: dbus-python.pcrequires dbus-1

Luca Bruno — 2008-11-29T23:44:08

Bug#503652: Do not restart pommed whenrestarting dbus

Julien BLACHE — 2008-11-29T19:18:56

Hi, Same if I demote it to Should-Start? No, DBus is disabled if it's not available at startup. That's something I can change (and probably should). Now, the whole restart issue around DBus has been discussed already and I really hope we'll see some movement towards sanity in the near future. JB.

dbus_1.2.4-1_amd64.changes ACCEPTED

Debian Installer — 2008-11-29T18:32:03

Accepted: dbus-1-doc_1.2.4-1_all.deb to pool/main/d/dbus/dbus-1-doc_1.2.4-1_all.deb dbus-x11_1.2.4-1_amd64.deb to pool/main/d/dbus/dbus-x11_1.2.4-1_amd64.deb dbus_1.2.4-1.diff.gz to pool/main/d/dbus/dbus_1.2.4-1.diff.gz dbus_1.2.4-1.dsc to pool/main/d/dbus/dbus_1.2.4-1.dsc dbus_1.2.4-1_amd64.deb to pool/main/d/dbus/dbus_1.2.4-1_amd64.deb dbus_1.2.4.orig.tar.gz to pool/main/d/dbus/dbus_1.2.4.orig.tar.gz libdbus-1-3_1.2.4-1_amd64.deb to pool/main/d/dbus/libdbus-1-3_1.2.4-1_amd64.deb libdbus-1-dev_1.2.4-1_amd64.deb to pool/main/d/dbus/libdbus-1-dev_1.2.4-1_amd64.deb Override entries for your package: dbus-1-doc_1.2.4-1_all.deb - optional doc dbus-x11_1.2.4-1_amd64.deb - optional x11 dbus_1.2.4-1.dsc - source devel dbus_1.2.4-1_amd64.deb - optional devel libdbus-1-3_1.2.4-1_amd64.deb - optional libs libdbus-1-dev_1.2.4-1_amd64.deb - optional libdevel Announcing to debian-devel-changes< at >lists.debian.org Thank you for your contribution to Debian.

Bug#503652: Do not restart pommed whenrestarting dbus

Sjoerd Simons — 2008-11-29T18:21:26

Sorry for the late reply dbus restarts pommed because it has dbus in Required-Start in the init scripts lsb headers. If you remove that it won't restart it. I assume that your handling of dbus restarts also means it can start without dbus running initially ? Sjoerd

Processing of dbus_1.2.4-1_amd64.changes

Archive Administrator — 2008-11-29T18:30:23

dbus_1.2.4-1_amd64.changes uploaded successfully to localhost along with the files: dbus_1.2.4-1.dsc dbus_1.2.4.orig.tar.gz dbus_1.2.4-1.diff.gz dbus-1-doc_1.2.4-1_all.deb dbus_1.2.4-1_amd64.deb dbus-x11_1.2.4-1_amd64.deb libdbus-1-3_1.2.4-1_amd64.deb libdbus-1-dev_1.2.4-1_amd64.deb Greetings, Your Debian queue daemon

Bug#502217: hal-info: IBM ThinkPad X31(2672-PG9) needs s3_bios and s3_mode in the video quirks

The Anarcat — 2008-11-29T17:04:01

Bug#500119: Bug#500119: Better way toavoid both knetworkmanager and nm-applet are started in parallel

Otavio Salvador — 2008-11-25T11:38:39

Yes. I fully agree to get it fixed in lenny and that will allow more freedom for our users. I'm waiting for your reply about the tasksel inclusion or not...

Bug#500119: Bug#500119: Better way toavoid both knetworkmanager and nm-applet are started in parallel

Otavio Salvador — 2008-11-25T11:37:21

The .desktop change of nm-applet I'm ok with. And this is really recommended to be done to allow it to be used by other compatible desktops. Agree. But install it in tasksel is a completely different history.

Bug#500119: Bug#500119: Better way toavoid both knetworkmanager and nm-applet are started in parallel

Andrew Lee — 2008-11-25T09:37:30

Additional comments from Xfce maintainer: 15:23 -!- Irssi: Join to #debian-xfce was synced in 1 secs 15:23 < AndrewLee> hello 15:46 < AndrewLee> Any xfce maintainer here? 15:47 < Corsac> yup, but see topic 15:47 < Corsac> and I'm livin 16:15 < AndrewLee> Corsac: Does xfce-desktop task included a wifi configuration GUI? 16:19 < AndrewLee> I'd like to change a line in nm-applet.desktop to make it works for all kind windowmanager and desktop enviroment except in KDE. 16:19 < AndrewLee> So I'd like to ask xfce maintainer if this change is okay to xfce? 16:47 < Corsac> no we don't include anything atm 16:47 < Corsac> I'm testing wicd at the moment, which seems to work fine 16:47 < Corsac> and upstream is kind-of working on airconfig, which works fine too 16:47 < Corsac> but that will be for squeeze 16:48 < Corsac> are you working on lenny or squeeze for that change? 16:48 < Corsac> (anyway, I still think you should drop the OnlyShowIn=GNOME for the moment) 16:48 < Corsac> not sure if that means it'll be autostar

Bug#500119: Bug#500119: Better way toavoid both knetworkmanager and nm-applet are started in parallel

Andrew Lee — 2008-11-25T08:54:10

Hello Otavio, Otavio Salvador wrote: I agree with you. We need disscuss this to have a best option. And it shouldn't be related in #500119, but in tasksel. I will reply in another email without cc to 500119< at >bugs.debian.org Are we agreed to get #500119 fixed in lenny? At least our users who install network-manager-gnome manually on their custom system can benefit from this fix. -Andrew

Bug#500119: Bug#500119: Better way toavoid both knetworkmanager and nm-applet are started in parallel

PCMan — 2008-11-25T07:50:40

If you don't install nm and nm-applet, it doesn't matter what's inside nm-applet.desktop. Fixing the incorrect desktop file won't break any existing things and has no relationship with your question. If a user don't want the dependencies brought by nm, he/she shouldn't get it installed. Besides, the reason why nm has so many dependencies is understandable. To get your Linux desktop correctly connected to the internet is very difficult and can be very complicated. That's why nm is so complicated. So personally I think nm is still an acceptable option even for lightweight desktops since it works quite well. Some might argue that wicd can do this well and it's small, too. However, it's written in python, and that "small" program need python and its libs, which are not thin at all. Network manager is still a reasonable and sensible option if you need to manage your connections with GUI. The point is, whether the installer for lxde flavor includes nm or not, it'll never works for the users even when they really

Bug#500119: Bug#500119: Better way toavoid both knetworkmanager and nm-applet are started in parallel

Otavio Salvador — 2008-11-24T23:33:48

This is somewhat complicate to decide. I see two sides in this question: 1) adding Network Manager for LXDE we'll give a more ready to use desktop for laptop users and give some extra bonus for regular users; 2) LXDE seems to fit very well with users wanting a low-resource environment and Network Manager is not thin (it bring a lot of libraries and consumes resources); So personally I'm unsure which is the best option. From my POV I believe we shouldn't add Network Manager on lxde-desktop task since it's quite easy to do it and we can make the installation fat for a user that is limited regarting space, memory and cpu power. What others think about it?