Re: Removing Qt 4 from Ubuntu before the 20.04 release
Especially since we (Ubuntu Budgie) are not on the list (and speaking to the team)... no objections. > Does anyone object to this plan? Dustin --- Ubuntu Budgie On Aug 22 2019, at 4:43 pm, Steve Langasek wrote: > On Thu, Aug 22, 2019 at 06:29:45PM -0500, Simon Quigley wrote: > > I would like to completely remove Qt 4 from the Ubuntu archive before > > the 20.04 release. This includes all of KDE 4 and dependencies. > > > > The Debian Qt/KDE Team (which I am a part of) is raising the status of > > the Qt 4 removal bugs to RC[1], and since the Qt 6 work is starting > > upstream in the dev branch in the coming months, now is the time for Qt > > 4 to go. > > > > My timeline for this is to change all of the bugs filed to ask people to > > port[2] to removal bugs, and go over the list of Qt 4 reverse > > dependencies one last time, so the removal can be done at the beginning > > of the 20.04 cycle before the archive opens. This would make 19.10 the > > last release with Qt 4. > > > > Flavors, please check if Qt 4 is on your ISO, and if it is, make plans > > to remove it as soon as you can. Please hop in #ubuntu-qt if you would > > like help porting your favorite application. > > > $ apt-cache show libqtcore4 | grep Task > Task: lubuntu-desktop, ubuntustudio-publishing, ubuntustudio-audio, > ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop > $ > > That's still 4 flavors as of today, FTR. > > Does anyone object to this plan? > > [1] > > https://alioth-lists.debian.net/pipermail/pkg-kde-talk/2019-August/002920.html > > [2] https://bugs.launchpad.net/ubuntu/+bugs?field.tag=qt4-removal > > > -- > Steve Langasek Give me a lever long enough and a Free OS > Debian Developer to set it on, and I can move the world. > Ubuntu Developer https://www.debian.org/ > slanga...@ubuntu.com vor...@debian.org > -- > Ubuntu-release mailing list > Ubuntu-release@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-release > -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
New component-mismatches for source universe -> main
The following universe packages have new reverse dependencies in main or got seeded. They need to get a MainInclusionReport and be promoted, or the reverse dependencies in main need to be dropped: o a52dec: liba52-0.7.4 liba52-0.7.4-dev [Reverse-Depends: Rescued from a52dec, gstreamer1.0-plugins-ugly] o aom: libaom-dev libaom-doc libaom0 [Reverse-Depends: Rescued from aom, gstreamer1.0-plugins-bad] o armadillo: libarmadillo-dev libarmadillo9 [Reverse-Depends: Rescued from armadillo, libgdal20] o arpack: libarpack2 libarpack2-dev libparpack2 libparpack2-dev [Reverse-Depends: Rescued from arpack, libarmadillo-dev, libarmadillo9, libparpack2-dev] o charls: libcharls-dev libcharls2 [Reverse-Depends: libgdal-dev, libgdal20] o chromaprint: libchromaprint-dev libchromaprint1 [Reverse-Depends: Rescued from chromaprint, gstreamer1.0-plugins-bad] o codec2: codec2-examples libcodec2-0.8.1 libcodec2-dev [Reverse-Depends: Rescued from codec2, libavcodec58] o configparser: python-configparser MIR: #1196983 (Fix Released) [Reverse-Depends: python-future (MAIN)] o crystalhd: libcrystalhd-dev libcrystalhd3 [Reverse-Depends: Rescued from crystalhd, libavcodec58] o cython: cython MIR: #299870 (Fix Released) MIR for cython [Reverse-Depends: python-wsaccel] o dlocate: dlocate [Reverse-Recommends: dwww] o double-conversion: libdouble-conversion3 MIR: #1427677 (Fix Released) [Reverse-Depends: libqt5core5a] o dwww: dwww [Reverse-Recommends: libnorm-doc] o eigen3: libeigen3-dev [Reverse-Depends: libvtk6-dev] o enum34: python-enum34 MIR: #1430082 (Fix Released) [Reverse-Depends: python-cryptography (MAIN)] o epiphany-browser: epiphany-browser epiphany-browser-data [Reverse-Depends: epiphany-browser, libreoffice-help-zh-cn (MAIN)] o faad2: libfaad-dev libfaad2 [Reverse-Depends: Rescued from faad2, gstreamer1.0-plugins-bad] o ffmpeg: ffmpeg-doc libavcodec-dev libavcodec58 libavdevice-dev libavdevice58 libavfilter-dev libavfilter7 libavformat-dev libavformat58 libavresample-dev libavresample4 libavutil-dev libavutil56 libpostproc-dev libpostproc55 libswresample-dev libswresample3 libswscale-dev libswscale5 [Reverse-Depends: Rescued from ffmpeg, gstreamer1.0-libav, libavcodec-dev, libavdevice-dev, libavfilter-dev, libavfilter7, libavresample-dev, libchromaprint1] o flite: flite1-dev libflite1 [Reverse-Depends: Rescued from flite, gstreamer1.0-plugins-bad] o fluidsynth: libfluidsynth-dev libfluidsynth1 [Reverse-Depends: Rescued from fluidsynth, gstreamer1.0-plugins-bad] o fonts-dzongkha: fonts-dzongkha [Reverse-Recommends: libreoffice-l10n-dz (MAIN)] o fonts-hosny-thabit: fonts-hosny-thabit [Reverse-Recommends: libreoffice-l10n-ar (MAIN)] o freepats: freepats [Reverse-Recommends: libwildmidi-config] o freexl: libfreexl-dev libfreexl1 [Reverse-Depends: Rescued from freexl, libgdal20] o fyba: libfyba-dev libfyba0 [Reverse-Depends: Rescued from fyba, libgdal20] o game-music-emu: libgme-dev libgme0 [Reverse-Depends: Rescued from game-music-emu, gstreamer1.0-plugins-bad] o gdal: gdal-data libgdal-dev libgdal-doc libgdal-perl-doc libgdal20 [Reverse-Depends: Rescued from gdal, libgdal20, libopencv-imgcodecs3.2] o gdcm: gdcm-doc libgdcm2-dev libgdcm2.8 libvtkgdcm2-dev libvtkgdcm2.8a [Reverse-Depends: Rescued from gdcm, libopencv-imgcodecs-dev, libopencv-imgcodecs3.2, libvtkgdcm2-dev] o geos: libgeos++-dev libgeos-3.7.2 libgeos-c1v5 libgeos-dev libgeos-doc [Reverse-Depends: Rescued from geos, libgdal20, libgeos++-dev, libgeos-c1v5] o gl2ps: libgl2ps-dev libgl2ps-doc libgl2ps1.4 [Reverse-Depends: Rescued from gl2ps, libvtk6.3] o glew: libglew2.1 [Reverse-Depends: libvtk7.1] o gssdp: gir1.2-gssdp-1.2 libgssdp-1.2-0 libgssdp-1.2-dev libgssdp-doc MIR: #388898 (Fix Released) [Reverse-Depends: Rescued from gssdp, libgupnp-igd-1.0-4] o gst-libav1.0: gstreamer1.0-libav gstreamer1.0-libav-dbg [Reverse-Depends: Rescued from gst-libav1.0] [Reverse-Recommends: libreoffice-core (MAIN)] o gst-plugins-bad1.0: gir1.2-gst-plugins-bad-1.0 gstreamer1.0-plugins-bad gstreamer1.0-plugins-bad-dbg gstreamer1.0-plugins-bad-doc libgstreamer-opencv1.0-0 libgstreamer-plugins-bad1.0-0 libgstreamer-plugins-bad1.0-dev [Reverse-Depends: Rescued from gst-plugins-bad1.0, gstreamer1.0-plugins-bad, libgstreamer-plugins-bad1.0-dev] [Reverse-Recommends: libreoffice-core (MAIN)] o gst-plugins-ugly1.0: gstreamer1.0-plugins-ugly gstreamer1.0-plugins-ugly-dbg gstreamer1.0-plugins-ugly-doc [Reverse-Depends: Rescued from gst-plugins-ugly1.0] [Reverse-Recommends: libreoffice-core (MAIN)] o gupnp: gir1.2-gupnp-1.2 libgupnp-1.2-0 libgupnp-1.2-dev libgupnp-doc MIR: #388898 (Fix Released) [Reverse-Depends: Rescued from gupnp, libgupnp-1.2-dev, libgupnp-igd-1.0-4,
Re: [Bug 1823429] Re: linux v4.15 ftbfs on a newer host kernel (e.g. hwe)
Hi, I now also see spamming unrelated bugs issue too. That's fine. Re:message no, the tags are not enough, as there also need to be tasks open against the right packages. Often the same bug link is used for multiple kernel flavours affecting different series and fixed at different uploads so one needs to know package name + version + series. You can see the current sru template verification text in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837700/comments/7 which is more polite and contains more substituted variables with direct information and links as to what needs testing. I believe it is generated by the sru-accept script from the ubuntu-archive-tools and is posted upon publication in the proposed pocket. There are many ways to drive those scripts, so a full message is generated when sourcepackage name is passed to it. https://bazaar.launchpad.net/~ubuntu-archive/ubuntu-archive-tools/trunk/view/head:/sru_workflow.py I am not sure where the kernel sru messages are generated, is it done with the sru_workflow tooling using the latest args / messages? On Fri, 23 Aug 2019, 03:33 Brad Figg, wrote: > Dimitri, > > A couple of things. First, it appears that a number of bugs are getting > spammed incorrectly with this for some unknown reason. We are looking into > why that has happened. Second, this is the same message that we've used for > years and the message does indicate, via the tags to set, which series is > to be tested. If the messages are not clear enough we are happy to make > them more clear. > > Brad > > On Thu, Aug 22, 2019 at 5:28 PM Dimitri John Ledkov > wrote: > >> Hi, >> >> Kernel bug reports appear to be using non standard SRU notifications. >> >> There is never a comment stating the source package name, series, and >> version requesting verification like it is done on regular SRUs. >> >> There is comment as seen below, which makes it impossible to tell what to >> test. >> >> Bug tasks are missing too. If you look at the bug report, you will notice >> no xenial tasks at all. >> >> What am I supposed to test? >> >> -- Forwarded message - >> From: Ubuntu Kernel Bot >> Date: Thu, 22 Aug 2019, 17:29 >> Subject: [Bug 1823429] Re: linux v4.15 ftbfs on a newer host kernel (e.g. >> hwe) >> To: >> >> >> This bug is awaiting verification that the kernel in -proposed solves >> the problem. Please test the kernel and update this bug with the >> results. If the problem is solved, change the tag 'verification-needed- >> xenial' to 'verification-done-xenial'. If the problem still exists, >> change the tag 'verification-needed-xenial' to 'verification-failed- >> xenial'. >> >> If verification is not done by 5 working days from today, this fix will >> be dropped from the source code, and this bug will be closed. >> >> See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how >> to enable and use -proposed. Thank you! >> >> >> ** Tags added: verification-needed-xenial >> >> -- >> You received this bug notification because you are subscribed to a >> duplicate bug report (1831645). >> https://bugs.launchpad.net/bugs/1823429 >> >> Title: >> linux v4.15 ftbfs on a newer host kernel (e.g. hwe) >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823429/+subscriptions >> -- >> Ubuntu-release mailing list >> Ubuntu-release@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-release >> > > > -- > Brad Figg brad.f...@canonical.com http://www.canonical.com > -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: [Bug 1823429] Re: linux v4.15 ftbfs on a newer host kernel (e.g. hwe)
Dimitri, A couple of things. First, it appears that a number of bugs are getting spammed incorrectly with this for some unknown reason. We are looking into why that has happened. Second, this is the same message that we've used for years and the message does indicate, via the tags to set, which series is to be tested. If the messages are not clear enough we are happy to make them more clear. Brad On Thu, Aug 22, 2019 at 5:28 PM Dimitri John Ledkov wrote: > Hi, > > Kernel bug reports appear to be using non standard SRU notifications. > > There is never a comment stating the source package name, series, and > version requesting verification like it is done on regular SRUs. > > There is comment as seen below, which makes it impossible to tell what to > test. > > Bug tasks are missing too. If you look at the bug report, you will notice > no xenial tasks at all. > > What am I supposed to test? > > -- Forwarded message - > From: Ubuntu Kernel Bot > Date: Thu, 22 Aug 2019, 17:29 > Subject: [Bug 1823429] Re: linux v4.15 ftbfs on a newer host kernel (e.g. > hwe) > To: > > > This bug is awaiting verification that the kernel in -proposed solves > the problem. Please test the kernel and update this bug with the > results. If the problem is solved, change the tag 'verification-needed- > xenial' to 'verification-done-xenial'. If the problem still exists, > change the tag 'verification-needed-xenial' to 'verification-failed- > xenial'. > > If verification is not done by 5 working days from today, this fix will > be dropped from the source code, and this bug will be closed. > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > to enable and use -proposed. Thank you! > > > ** Tags added: verification-needed-xenial > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1831645). > https://bugs.launchpad.net/bugs/1823429 > > Title: > linux v4.15 ftbfs on a newer host kernel (e.g. hwe) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823429/+subscriptions > -- > Ubuntu-release mailing list > Ubuntu-release@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-release > -- Brad Figg brad.f...@canonical.com http://www.canonical.com -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: Removing Qt 4 from Ubuntu before the 20.04 release
On Thu, Aug 22, 2019 at 06:29:45PM -0500, Simon Quigley wrote: > I would like to completely remove Qt 4 from the Ubuntu archive before > the 20.04 release. This includes all of KDE 4 and dependencies. > The Debian Qt/KDE Team (which I am a part of) is raising the status of > the Qt 4 removal bugs to RC[1], and since the Qt 6 work is starting > upstream in the dev branch in the coming months, now is the time for Qt > 4 to go. > My timeline for this is to change all of the bugs filed to ask people to > port[2] to removal bugs, and go over the list of Qt 4 reverse > dependencies one last time, so the removal can be done at the beginning > of the 20.04 cycle before the archive opens. This would make 19.10 the > last release with Qt 4. > Flavors, please check if Qt 4 is on your ISO, and if it is, make plans > to remove it as soon as you can. Please hop in #ubuntu-qt if you would > like help porting your favorite application. $ apt-cache show libqtcore4 | grep Task Task: lubuntu-desktop, ubuntustudio-publishing, ubuntustudio-audio, ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop $ That's still 4 flavors as of today, FTR. > Does anyone object to this plan? > > [1] > https://alioth-lists.debian.net/pipermail/pkg-kde-talk/2019-August/002920.html > [2] https://bugs.launchpad.net/ubuntu/+bugs?field.tag=qt4-removal -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Removing Qt 4 from Ubuntu before the 20.04 release
Hello, I would like to completely remove Qt 4 from the Ubuntu archive before the 20.04 release. This includes all of KDE 4 and dependencies. The Debian Qt/KDE Team (which I am a part of) is raising the status of the Qt 4 removal bugs to RC[1], and since the Qt 6 work is starting upstream in the dev branch in the coming months, now is the time for Qt 4 to go. My timeline for this is to change all of the bugs filed to ask people to port[2] to removal bugs, and go over the list of Qt 4 reverse dependencies one last time, so the removal can be done at the beginning of the 20.04 cycle before the archive opens. This would make 19.10 the last release with Qt 4. Flavors, please check if Qt 4 is on your ISO, and if it is, make plans to remove it as soon as you can. Please hop in #ubuntu-qt if you would like help porting your favorite application. Does anyone object to this plan? [1] https://alioth-lists.debian.net/pipermail/pkg-kde-talk/2019-August/002920.html [2] https://bugs.launchpad.net/ubuntu/+bugs?field.tag=qt4-removal -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Re: GNOME 3.33, eoan-proposed and feature freeze
+1 to this plan. Thanks for the heads-up. On Thu, Aug 22, 2019 at 07:30:09PM +0100, Iain Lane wrote: > Greetings release team, > > We've been preparing GNOME 3.33 in a silo, since it involves a couple of > entangled transitions and I didn't want to make the situation in > -proposed worse by doing it directly there. The bulk of it is more or > less ready to go now from my POV. > > Feature freeze is ~now, so I'm messaging to give the release team a > heads up about our plans here. For some components we're likely to miss > the freeze by a few days (mainly due to unwinding said transitions > taking a while, so we didn't get all of the stack updated in time). > > The bulk of the update will be via a binary copy from the silo to > eoan-proposed using bileto. I'd hope this wouldn't make the situation in > -proposed worse, modulo autopkgtest, since the binaries are already > built. I'm at a conference this week (GUADEC), but I'm planning to > publish in the next few days. If anyone wants me to hold off for a bit > due to this causing concerns about eoan-proposed - bearing in mind > feature freeze - please yell. > > Cheers, > > -- > Iain Lane [ i...@orangesquash.org.uk ] > Debian Developer [ la...@debian.org ] > Ubuntu Developer [ la...@ubuntu.com ] > -- > Ubuntu-release mailing list > Ubuntu-release@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-release -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
GNOME 3.33, eoan-proposed and feature freeze
Greetings release team, We've been preparing GNOME 3.33 in a silo, since it involves a couple of entangled transitions and I didn't want to make the situation in -proposed worse by doing it directly there. The bulk of it is more or less ready to go now from my POV. Feature freeze is ~now, so I'm messaging to give the release team a heads up about our plans here. For some components we're likely to miss the freeze by a few days (mainly due to unwinding said transitions taking a while, so we didn't get all of the stack updated in time). The bulk of the update will be via a binary copy from the silo to eoan-proposed using bileto. I'd hope this wouldn't make the situation in -proposed worse, modulo autopkgtest, since the binaries are already built. I'm at a conference this week (GUADEC), but I'm planning to publish in the next few days. If anyone wants me to hold off for a bit due to this causing concerns about eoan-proposed - bearing in mind feature freeze - please yell. Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] signature.asc Description: PGP signature -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
