Re: [ubuntu-studio-devel] Upgrade Notifications for Kubuntu and Ubuntu Studio
https://invent.kde.org/system/distro-release-notifier may help On Thu, Sep 8, 2022 at 3:09 AM Erich Eickmeyer wrote: > > Hi all, > > > In Kubuntu and Ubuntu Studio, we rely on Discover and the Discover Notifier > to run our GUI-based package updates. I don't care if you personally use apt > periodically from the terminal, a case can be made that we expect our users > to use Discover to do their updates. > > > Unfortunately, Discover is very, very flawed. It uses packagekit as its > backend and its upgrader is designed to do one thing: upgrade packages. By > comparison, the Ubuntu Update Manager will give the user the option to remove > unused packages, unused kernels. and even notify of new Ubuntu releases, > which is something that Discover cannot do since it's built to be as > distribution-agnostic as possible. > > > The lack of notification of new releases means when Release Upgrades are > enabled, Kubuntu and Ubuntu Studio users are not notified whether their > systems are set to upgrade to regular releases or LTS releases. This is > especially problematic for users that simply don't know any better. We simply > take for granted that we upgrade our systems, but new users don't necessarily > know that they have to do that, and they don't necessarily pay attention to > release announcements. We can't take that for granted that they automatically > know that or are paying attention; it's not basic knowledge. > > > I have been seeing, with high levels of frequency, users showing-up in the > #kubuntu chat with EOL systems, and users showing up running 20.04 not > understanding why they aren't getting a notification to upgrade to 22.04. We > need to do better from a development standpoint and not let this happen. > Users need to be notified from their systems, not externally. > > > Years ago, update-manager-qt was a thing, and I'm sure update-notifier-qt was > as well. I decided to experiment with both. Unfortunately, I ran into a few > issues, namely that neither exists anymore. Beyond that, using the GTK > equivalents, I ran into a couple of other issues: > > > update-notifier doesn't even show in the system tray when there are updates > on my system, even after a reboot or a relog. Only if I force it by executing > it does it show, but it doesn't go away after running update-manager. > update-manager runs well, but it pops-up a kdialog while running (see > attached screenshot). Perhaps a bug/relic from old days, but definitely > something that needs to be resolved. > > > Honestly, if these things can be resolved and the Qt equivalents can be > resurrected, then it would be a huge boon to the users. Not only would they > have a more robust upgrade management system, but they would also have the > benefit of a Release Upgrade notifier when those times come. > > > Of course, if someone has a better solution and would rather re-invent the > wheel, then sure, but I don't think re-inventing the wheel is ever a good > solution and would rather see collaboration and cooperation first, as is the > Ubuntu spirit. > > > I added ubuntu-devel@ to this discussion since the packages in question are > in "main" and would require the help of some core devs to get some work done. > > > Thanks for hearing me out, > > Erich > > > -- > > Erich Eickmeyer > > Project Leader - Ubuntu Studio > > Member - Ubuntu Community Council > > -- > kubuntu-devel mailing list > kubuntu-de...@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: Upgrade Notifications for Kubuntu and Ubuntu Studio
https://invent.kde.org/system/distro-release-notifier may help On Thu, Sep 8, 2022 at 3:09 AM Erich Eickmeyer wrote: > > Hi all, > > > In Kubuntu and Ubuntu Studio, we rely on Discover and the Discover Notifier > to run our GUI-based package updates. I don't care if you personally use apt > periodically from the terminal, a case can be made that we expect our users > to use Discover to do their updates. > > > Unfortunately, Discover is very, very flawed. It uses packagekit as its > backend and its upgrader is designed to do one thing: upgrade packages. By > comparison, the Ubuntu Update Manager will give the user the option to remove > unused packages, unused kernels. and even notify of new Ubuntu releases, > which is something that Discover cannot do since it's built to be as > distribution-agnostic as possible. > > > The lack of notification of new releases means when Release Upgrades are > enabled, Kubuntu and Ubuntu Studio users are not notified whether their > systems are set to upgrade to regular releases or LTS releases. This is > especially problematic for users that simply don't know any better. We simply > take for granted that we upgrade our systems, but new users don't necessarily > know that they have to do that, and they don't necessarily pay attention to > release announcements. We can't take that for granted that they automatically > know that or are paying attention; it's not basic knowledge. > > > I have been seeing, with high levels of frequency, users showing-up in the > #kubuntu chat with EOL systems, and users showing up running 20.04 not > understanding why they aren't getting a notification to upgrade to 22.04. We > need to do better from a development standpoint and not let this happen. > Users need to be notified from their systems, not externally. > > > Years ago, update-manager-qt was a thing, and I'm sure update-notifier-qt was > as well. I decided to experiment with both. Unfortunately, I ran into a few > issues, namely that neither exists anymore. Beyond that, using the GTK > equivalents, I ran into a couple of other issues: > > > update-notifier doesn't even show in the system tray when there are updates > on my system, even after a reboot or a relog. Only if I force it by executing > it does it show, but it doesn't go away after running update-manager. > update-manager runs well, but it pops-up a kdialog while running (see > attached screenshot). Perhaps a bug/relic from old days, but definitely > something that needs to be resolved. > > > Honestly, if these things can be resolved and the Qt equivalents can be > resurrected, then it would be a huge boon to the users. Not only would they > have a more robust upgrade management system, but they would also have the > benefit of a Release Upgrade notifier when those times come. > > > Of course, if someone has a better solution and would rather re-invent the > wheel, then sure, but I don't think re-inventing the wheel is ever a good > solution and would rather see collaboration and cooperation first, as is the > Ubuntu spirit. > > > I added ubuntu-devel@ to this discussion since the packages in question are > in "main" and would require the help of some core devs to get some work done. > > > Thanks for hearing me out, > > Erich > > > -- > > Erich Eickmeyer > > Project Leader - Ubuntu Studio > > Member - Ubuntu Community Council > > -- > kubuntu-devel mailing list > kubuntu-de...@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: libgit2
On Mon, Feb 16, 2015 at 8:14 PM, Jackson Doak nosk...@ubuntu.com wrote: Just looking through upstream logs, this should be as simple as uploading libgit2-glib 0.22.0 and gitg 3.15.1 unfortunately there's symbol retractions without soname change :( http://paste.ubuntu.com/10271618/ -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
libgit2
it would be very lovely if someone who's interested in gitg could have a look at transitioning libgit2 - libgit2-glib - gitg to libgit2 0.22. 0.21 apparently had stability problems in the editor kate so 0.22 is a minimum requirement there. cheers HS -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: telepathy-qt5 0.9.5
bump :/ On Tue, Dec 9, 2014 at 11:49 AM, Harald Sitter apachelog...@ubuntu.com wrote: ahoy, since apparently there are a heap of excessively intrusive patches in telepathy-qt5 because of ubuntu touch, can someone please refresh the patches against 0.9.5 (and land that)? and can we please not have API patches that aren't upstreamed? cheers. HS -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
telepathy-qt5 0.9.5
ahoy, since apparently there are a heap of excessively intrusive patches in telepathy-qt5 because of ubuntu touch, can someone please refresh the patches against 0.9.5 (and land that)? and can we please not have API patches that aren't upstreamed? cheers. HS -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: are we set for feature freeze?
On Tue, Feb 18, 2014 at 3:02 PM, Rohan Garg rohang...@kubuntu.org wrote: the only things I have on my todo for features at this point is - kubuntu-notification-helper (adding l10n and driver notification) - muon 2.2beta and libqapt2.2 (or something, need apol for that, might need exception) - kde sc 4.13 (as previously discussed we'll land 4.13 which will need a freeze exception) - kubuntu-debug-installer dbgsym handling (might or might not get done in time, also depending on qapt) - plasma modem manager1 (not sure what the status is here, JR?) Add KDE Telepathy 0.7.80 and Alex's KWallet PAM module ( that I intend to block in -proposed till 4.13 is out ) to that. Why the blockage? What does it require from 4.13? HS -- kubuntu-devel mailing list kubuntu-de...@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Re: KDE SC 4.13
On Thu, Jan 16, 2014 at 6:49 AM, Rohan Garg rohang...@kubuntu.org wrote: (if our primary concern are low quality reviews that do not bother to install/upgrade, then I guess 4.12 would be the way to go :P) My main concern are things not working out of the box in the KDE 4.13 RC ( as is often the case with RC's as witnessed in earlier KDE SC releases ). To be honest with half the essential bits frozen (workspace/libs) this seems less likely. The thing is, if the *RC* turns out to have problems we still have time to fix that. As Jonathan pointed out, final actually is due for tagging a week before release (i.e. before our final release freeze), so all the fixes are supposedly available upstream before we freeze and we could manually patch the RC to 4.13 final levels if need be. At the same time we do have time to do a complete u-turn and revert back to SC 4.12 (I'll go ahead and say that this would not take more than a week, then again we have no precedence ^^). So yeah, 4.13(rc) can cause quality problems. However I am counting on our new QC measures to prevent us from releasing a troubled final and we certainly have just enough time to fix any show-stoppers that appear in 4.13rc. KDE SC 4.13 will also feature a new search framework, and some applications like Amarok are likely not to be ported by that time. So we're left in the weird situation where we will have Nepomuk and Baloo on the ISO. Ofcourse, we could just drop Nepomuk from the ISO and then we leave it up to the users to install Nepomuk to get required meta data integration in Amarok. But IMHO that constitutes as loss of out of the box features from previous releases. I guess that's a non-issue as per Myriam's mail. Unless there are other application using nepomuk outside the SC ( bangarang comes to mind, but we don't have that on the ISO - and I am not sure it is maintained still). Actually, Jonathan, what does upstream think about this? Are they confident that we'll have reasonable quality by RC time? Overall it seems a bit risky to push for a RC in a LTS release. If we're worried about support, It's not like we have a proper definition for a Kubuntu LTS release ;) I'll argue that it is in fact less risky because it is LTS. LTS, quite unlike all other releases, get their ISO respun ever so often. Going by 12.04's example we'd have a 14.04.1 in August, containing KDE SC 4.13.3+. Personally I am not worried about support, I just believe that having a newer version for a product that will be relevant for the next 6 years seems more reasonable. If things go wrong we'd look at ~4months with a possibly grave issue and then 68 months of a high quality release. Which all in all does sound rather reasonable to be honest :P HS -- kubuntu-devel mailing list kubuntu-de...@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
phonon-gstreamer 12.04 sru
anyone interessted in SRUing [1] bug #1154630 [2] to 12.04? [1] https://wiki.ubuntu.com/StableReleaseUpdates [2] https://bugs.launchpad.net/ubuntu/+source/phonon-backend-gstreamer/+bug/1154630 HS -- kubuntu-devel mailing list kubuntu-de...@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Re: UDS changes
On Thu, Feb 28, 2013 at 5:03 PM, Aurélien Gâteau agat...@kde.org wrote: AFAIK Kubuntu policy is to get all patches reviewed upstream. That and also a as-few-patches-as-possible policy. There was a bit of slacking there recently so we have a pile of patches that are either not reviewed by upstream or should ultimately be carried upstream in a more scalable version. Nothing too invasive lying around though. HS -- kubuntu-devel mailing list kubuntu-de...@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Re: [kubuntu-devel] Re: UDS changes
On Thu, Feb 28, 2013 at 8:50 PM, Jonathan Riddell j...@jriddell.org wrote: On Thu, Feb 28, 2013 at 11:25:16AM -0500, Scott Kitterman wrote: On Thursday, February 28, 2013 04:35:14 PM Aleix Pol wrote: If Kubuntu wants to strength links with KDE, a good start would be to actually trust KDE maintainers on which are stable versions. What does this mean? Since KDE 4.4 we've shipped every KDE point release. Sometimes we get behind (4.9.5 should be available for all users next week), but we do ship them all. This is probably a reference to not doing stable release updates for each new stable release, like KDevelop (although KDevelop 4.4.1 is in 12.10). This is an issue which has probably just gone away with today's announcement/discussion. For all the problems a rolling release may have/cause it certainly frees up resources to deliver more stable updates. HS -- kubuntu-devel mailing list kubuntu-de...@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
kubuntu packages bzr
ahoy ahoy, the kubuntu crew just noticed that one of our core packages does not have the most recent upload in its bzr branch. I therefore would like to remind everyone that packages maintained by the kubuntu team almost always have a corresponding bzr branch at [1] (core software in particular is located at [2]) which ought to be used. TIA. [1] https://code.launchpad.net/~kubuntu-packagers [2] https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging HS -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
SRU xsettings-kde
Someone please make https://bugs.launchpad.net/ubuntu/+source/xsettings-kde/+bug/1002811 so that it meets with ludicrous requirements. I will not. Kthxbai. -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Qt 4.8 in Ubuntu 11.10 Oneiric Ocelot?
On Mon, Aug 8, 2011 at 2:41 PM, Per Arneng per.arn...@scalebit.com wrote: It seems like kubuntu 11.10 will have Qt 4.8. Actually it won't because it won't be released in time, so it also will not be in Ubuntu 11.10. regards, Harald -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
KDE 4.7 packages
markey apachelogger: the KDE 4.7 packages for 11.04 are outstanding. upgrade was very smooth :) markey upgraded half of our office, and my home box Good job ninjas! Thanks for all your awesome! -- kubuntu-devel mailing list kubuntu-de...@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Kubuntu Alpha 2 and KDE 4.7rc1
Salute mes amis! Perhaps you have noticed that there is no Kubuntu alpha 2 announcement. The reason for this is that we were hard at work to get KDE 4.6.90 (aka 4.7rc1) packaged. Currently we are fixing up some remaining issues and prepare for upload to the Ubuntu archive. Now, KDE 4.6.90 is implementing a partially split source tarball distribution. Meaning what previously was kdegraphics are now okular, gwenview, kolourpaint etc.. For additional information on this change you can surely find sufficient amount of information via Google, so I am not going into detail here. Long story short: KDE stuff may break over the next couple of days, so unless you want to take you chances you might want to hold back on upgrades. regards, Harald -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Fwd: New packaging branches location (was Re: Moving our branches (again)?)
Kubuntu packaging branches moved to a new super project for packaging as to avoid having to register 50 new launchpad projects every year. This includes, but is not limited to: All of core KDE (i.e. KDE SC), Qt, QtWebKit, everything in the Kubuntu package set and various packages in universe that happen to be maintained by Kubuntu. FWIW: branches for which Kubuntu is upstream still have their own project, so do packages that get recipe built (i.e. Project Neon's packaging) as well as those that are full-source branches (of which Kubuntu has only one IIRC). -- Forwarded message -- From: Philip Muskovac yo...@gmx.net Date: Tue, Jun 28, 2011 at 7:21 PM Subject: New packaging branches location (was Re: Moving our branches (again)?) To: kubuntu-de...@lists.ubuntu.com Harald now moved the branches, you can find them under lp:~kubuntu-packagers/kubuntu-packaging/module see https://code.launchpad.net/kubuntu-packaging Philip -- kubuntu-devel mailing list kubuntu-de...@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Touchegg not for mobile!
2011/5/17 Rodrigo Belém rclbe...@gmail.com: I got your point and I agree with you now :-) but I think we should take a look on it later and define default gestures for the main applications. Good point, I'll add a todo item for that. regards, Harald -- kubuntu-devel mailing list kubuntu-de...@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
