Bug#788657: message every upgrade
In fact it should have a dialog, "The group is no longer used" 1. find all files with it and offer to remove it 2. just remove it 3. do nothing, will remind next upgrade 4. don't warn me again. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87twu9nb9h@jidanni.org
Re: status of #781368 "No trayicon under GNOME Shell"?
On Sunday 14 June 2015 22:23:47 Sandro Knauß wrote: [snip] > > Debian jessie/stable is at 5.3, so in case it'd change anything, maybe > > that patch [1] could be backported? > > I heared that it is planned to make Qt5 available inside backports. But non > the less these are decisions of the KDE/Qt team and should be discussed > there. But as I said, the patch you mentioned is to fix systray inside KDE. I *might* do a backport, but definitely not soon. If anyone else is interested, it should be as easy as recompiling. But For that we need 5.4.2 to enter testing first. -- mathematician, n.: Some one who believes imaginary things appear right before your i's. Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Re: status of #781368 "No trayicon under GNOME Shell"?
Am 14.06.2015 um 22:23 schrieb Sandro Knauß: > Hey, > >>> FWIW I'm building a new version of qtbase which should fix the bug. Will >>> probably hit experimental today. >> >> Did that fix the bug? > > According to the upstream bug, yes. There are some people response, that it > is > fixed with Qt 5.4.2 ( availabe in experimental). Is there an ETA when Qt 5.4 is uploaded to unstable? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: status of #781368 "No trayicon under GNOME Shell"?
Hey, > > FWIW I'm building a new version of qtbase which should fix the bug. Will > > probably hit experimental today. > > Did that fix the bug? According to the upstream bug, yes. There are some people response, that it is fixed with Qt 5.4.2 ( availabe in experimental). > I read in the mentioned blog entry [0] from Martin Grässlin: > > Qt5: Won’t need adjustments starting with Qt 5.4, but with Qt 5.3 this > > commit should be cherry-picked Martin is only taking about a solution for Plasma and the systray. He is not taking about other DE (Gnome,XFCE,...). I discussed with him about that point, because I also thought we was writing about a general solution. > Debian jessie/stable is at 5.3, so in case it'd change anything, maybe > that patch [1] could be backported? I heared that it is planned to make Qt5 available inside backports. But non the less these are decisions of the KDE/Qt team and should be discussed there. But as I said, the patch you mentioned is to fix systray inside KDE. Regards, sandro signature.asc Description: This is a digitally signed message part.
status of #781368 "No trayicon under GNOME Shell"?
Hello all, what is the status of this bug? Lisandro Damián Nicanor Pérez Meyer wrote on the 13th of May: FWIW I'm building a new version of qtbase which should fix the bug. Will probably hit experimental today. Did that fix the bug? I am running Debian stable, but I'm needing a feature from owncloud-client = 1.7, so I've installed the version from testing and am not only without tray icon as you other people were but also without the possibility to minimize ownloud-client (the respective icons and menu entries are missing, respectively greyed out). So the application is kinda usable but it's a hickup in the usual workflow. From the discussion in the bug report I don't understand whether the problem is with the owncloud-client or with Qt or whether it's between the two. owncloud-client 1.6.4 was working though, however I'm not sure what that is telling me... I read in the mentioned blog entry [0] from Martin Grässlin: Qt5: Won’t need adjustments starting with Qt 5.4, but with Qt 5.3 this commit should be cherry-picked Debian jessie/stable is at 5.3, so in case it'd change anything, maybe that patch [1] could be backported? (Currently it is not backported [2]) ? *t [0] http://blog.martin-graesslin.com/blog/2014/06/where-are-my-systray-icons/ [1] https://qt.gitorious.org/qt/qtbase/commit/f1ee10f81ac18789e9a7dc715b464415ba2bc2b8 [2] https://sources.debian.net/src/qtbase-opensource-src/5.3.2%2Bdfsg-4%2Bdeb8u1/src/widgets/util/qsystemtrayicon.cpp/#L675
Bug#788657: libutempter0: doesn't clean up unused/retired utempter group
Hey Felix On Sun, 2015-06-14 at 11:46 +0200, Felix Geyer wrote: > You can't be certain that there are no files on the system that have > been chgrp to that group. > If the group is removed its gid might get reused. Sure,... which is IMHO one of the several general deficiencies of how Debian handles their system users/groups. But the same would apply to many other packages as well, which in fact *do* remove their users/groups at purge, for many of them where it is even much more likely that people actually used it. > The cost of having one more entry in /etc/group is really small so > I've decided not to remove the group on upgrade. > > See also https://wiki.debian.org/AccountHandlingInMaintainerScripts > for some more discussion about the pros and cons of removing > accounts. May I suggest then, that you add an entry to the NEWS file, where you tell that this is no longer used, and people can typically safely remove it if nothing on their system still uses these as owners? Perhaps even giving a example find / -group foo command to look for such files? That way people would have a more likely chance to notice that change and keep their systems consistent with what fresh installations would have. Thanks, Chris. smime.p7s Description: S/MIME cryptographic signature
libkface_14.12.2-2_amd64.changes is NEW
binary:libkface-data is NEW. binary:libkface-dev is NEW. binary:libkface3 is NEW. source:libkface is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will recieve an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1z483z-0005va...@franck.debian.org
Bug#788715: RM: qca-cyrus-sasl -- ROM; moved to src:qca2
Package: ftp.debian.org Severity: normal Hello, Please remove the source package qca-cyrus-sasl. Upstream ships the source code of qca2 plugins in the main tarball now. Therefore src:qca2 has taken over the binary package libqca2-plugin-cyrus-sasl. Thanks, Felix -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150614134804.16451.41940.reportbug@localhost6.localdomain6
Bug#788714: RM: qca2-plugin-gnupg -- ROM; moved to src:qca2
Package: ftp.debian.org Severity: normal Hello, Please remove the source package qca2-plugin-gnupg. Upstream ships the source code of qca2 plugins in the main tarball now. Therefore src:qca2 has taken over the binary package libqca2-plugin-gnupg. Thanks, Felix -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150614134503.16408.85911.reportbug@localhost6.localdomain6
Bug#788713: RM: qca2-plugin-ossl -- ROM; moved to src:qca2
Package: ftp.debian.org Severity: normal Hello, Please remove the source package qca2-plugin-ossl. Upstream ships the source code of qca2 plugins in the main tarball now. Therefore src:qca2 has taken over the binary package libqca2-plugin-ossl. Thanks, Felix -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150614134350.16338.35702.reportbug@localhost6.localdomain6
Processing of libkface_14.12.2-2_amd64.changes
libkface_14.12.2-2_amd64.changes uploaded successfully to localhost along with the files: libkface_14.12.2-2.dsc libkface_14.12.2.orig.tar.xz libkface_14.12.2-2.debian.tar.xz libkface-data_14.12.2-2_all.deb libkface-dev_14.12.2-2_amd64.deb libkface3_14.12.2-2_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1z47um-0002iz...@franck.debian.org
Bug#773462: marked as done (plasma-nm: plasma nm does not save password of new wlan connections anymore)
Your message dated Sun, 14 Jun 2015 14:36:04 +0200 with message-id <557d7534.9050...@debian.org> and subject line Re: plasma-nm: plasma nm does not save password of new wlan connections anymore has caused the Debian Bug report #773462, regarding plasma-nm: plasma nm does not save password of new wlan connections anymore 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 ow...@bugs.debian.org immediately.) -- 773462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773462 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: plasma-nm Version: 0.9.3.4-2 Severity: important I just filled a bug against network manager (Bug#773454), but they told me to fill it against plasma nm, so here we go... When connection to a new wlan, network manager does not store the password and the password needs to be reentered after every reconnect. It does create the wlan config file below /etc/NetworkManager/system-connections , but it does not store the password in it. Manually removing the line psk-flags=1 and adding a line psk=password helps. After restarting the network manager service it can auto connect to the wlan without asking for the password again. This behaviour already exists since about 4 months if I remember right, but it was just faster to edit the files, than reporting the bug. With the first version of network manager where that bug appeared I was able to enter the password by editing the connection in the plasma nm modul. But After the next update of network manager that was not possible anymore, since the ok button stays greyed out forever and it is impossible to save changes, thus editing the config file manually is necesary... I am not using kwallet in my system for anything. Also not for the network manager, and it used to work without it. Below what the generated config file looks like, and afterwards the log output of network manager: [connection] id=FAMILI ARCOS REAL uuid=22c6b842-5513-4b1e-a369-e7190d5951ad type=wifi permissions=user:rmm:; [wifi] ssid=FAMILI ARCOS REAL mode=infrastructure mac-address=C4:85:08:E0:C3:DD security=802-11-wireless-security [wifi-security] key-mgmt=wpa-psk auth-alg=open psk-flags=1 [ipv4] method=auto [ipv6] method=auto Dec 18 08:54:19 RMMbook dbus[1425]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Dec 18 08:54:19 RMMbook NetworkManager[25724]: NetworkManager (version 0.9.10.0) is starting... Dec 18 08:54:19 RMMbook NetworkManager[25724]: Read config: /etc/NetworkManager/NetworkManager.conf Dec 18 08:54:19 RMMbook NetworkManager[25724]: WEXT support is enabled Dec 18 08:54:19 RMMbook NetworkManager[25724]: VPN: loaded org.freedesktop.NetworkManager.vpnc Dec 18 08:54:19 RMMbook NetworkManager[25724]: VPN: loaded org.freedesktop.NetworkManager.openvpn Dec 18 08:54:19 RMMbook NetworkManager[25724]: VPN: loaded org.freedesktop.NetworkManager.pptp Dec 18 08:54:19 RMMbook NetworkManager[25724]: init! Dec 18 08:54:19 RMMbook NetworkManager[25724]: update_system_hostname Dec 18 08:54:19 RMMbook NetworkManager[25724]:interface-parser: parsing file /etc/network/interfaces Dec 18 08:54:19 RMMbook NetworkManager[25724]:interface-parser: finished parsing file /etc/network/interfaces Dec 18 08:54:19 RMMbook NetworkManager[25724]: management mode: unmanaged Dec 18 08:54:19 RMMbook NetworkManager[25
Bug#788657: libutempter0: doesn't clean up unused/retired utempter group
Hi, On Sun, 14 Jun 2015 00:35:31 +0200 Christoph Anton Mitterer wrote: > Package: libutempter0 > Version: 1.1.6-1 > Severity: normal > > > Hi. > > Apparently with this release the group utempter is no longer used. > This doesn't seem to be one of the "base groups" as defined by the > base-passwd package. > > It is however not properly cleaned up, so legacy installations > would keep it forever without any good reason. > > Could you please clean that up in one of the following uploads? You can't be certain that there are no files on the system that have been chgrp to that group. If the group is removed its gid might get reused. The cost of having one more entry in /etc/group is really small so I've decided not to remove the group on upgrade. See also https://wiki.debian.org/AccountHandlingInMaintainerScripts for some more discussion about the pros and cons of removing accounts. Cheers, Felix -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/557d4d6a.7040...@debian.org
Re: Comments regarding cantor_14.12.3-1_amd64.changes
On 07/05/15 15:46, Gergely Nagy wrote: > I see that in your upload of cantor to experimental at the end of > march, a cantor-backend-python package was introduced, as a > transitional oldlibs package. Since this package didn't exist before, > and depends on cantor-backend-python2, which is in stable, I don't > really get why you want a transitional package? Is it for some future > python3 migration? We are working hard on unifying the packaging efforts with Kubuntu, and we thought it was better to avoid producing different binary packages names, as it doesn't help us to maintain this kind of differences. If you think otherwise, please let us know, and we would reupload the package maintaining the differences. Happy hacking, -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." -- Rich Cook Saludos /\/\ /\ >< `/ signature.asc Description: OpenPGP digital signature
