This SRU remains blocked on https://lists.ubuntu.com/archives/ubuntu-
release/2022-October/005495.html.
For a straight backport to Jammy, if that is the conclusion, then the
upload also needs an SRU meta-bug really to document the justification
and regression risk mitigation for the backport.
**
@vanvugt what about pipewire in Jammy? Based on the duplicate report,
isn't this a regression in Jammy?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1987631
Title:
Screencast
@vanvugt what about pipewire in Jammy? Based on the duplicate report,
isn't this a regression in Jammy?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1987631
Title:
regression-updates based on duplicate report
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1995358
** Tags added: regression-update
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
regression-updates based on duplicate report
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1995358
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
> Bugs last updated between 2022-10-28 (Friday) and 2022-10-30 (Sunday)
> inclusive
> Date range identified as: "Monday triage"
> LP: #1976110 - Triaged [tmux] - `tmux -d -x ... -y
> ...` does not respect sizing
Utkarsh hasn't managed to get to this yet. Pinged him and
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This sort of change would be appropriate to apply by policy change
across the entire archive, after deliberation across relevant developers
to understand if this is appropriate as a whole, rather than piece by
Thank you for taking the time to file this report and helping to make
Ubuntu better.
I think you're probably affected by this:
https://askubuntu.com/questions/1409105/ubuntu-22-04-ssh-the-rsa-key-
isnt-working-since-upgrading-from-20-04
Since it seems likely to me that this is a local
On Sun, Oct 30, 2022 at 12:00:14PM +, Robie Basak wrote:
> I won't be able to attend our meeting tomorrow due to a company event.
Copy and paste fail. I meant Tuesday.
signature.asc
Description: PGP signature
--
technical-board mailing list
technical-board@lists.ubuntu.com
ht
I won't be able to attend our meeting tomorrow due to a company event.
signature.asc
Description: PGP signature
--
technical-board mailing list
technical-board@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/technical-board
On Thu, Oct 27, 2022 at 09:42:54AM +, Mathew Subin wrote:
> The following dependency is not working / available
>
> https://packages.ubuntu.com/jammy/python3-cryptography
>
>
> * python3-cffi-backend-api-max (>= 9729)
> Package not available
>
> * python3-cffi-backend-api-min (<=
On Tue, Oct 11, 2022 at 09:58:36AM +0300, Timo Aaltonen wrote:
> Christopher James Halse Rogers kirjoitti 28.9.2022 klo 10.07:
> >It's not entirely clear to me what you want to do here.
> >
> >If you need to fix some bugs in Jammy, and updating to thermald 2.5.0 is
> >basically the same as
Hi,
On Wed, Oct 12, 2022 at 05:49:00PM +1300, GJB wrote:
> this module is packaged with a binary built by the following source linked
> on this page
I'm not sure exactly what you're asking, but you can see the sources
used to build libapache2-mod-xsendfile for Ubuntu 22.04 (Jammy) here:
Is there a specific user story that you're looking to fix here? Eg.
crash reports in specific apps? What are you planning to rebuild to use
the newly versioned symbols? If possible, I'd like to see these verified
in proposed at the same time.
On the specific fix, there is quite a bit of noise
Thank you for contributing this fix!
This looks fine; just one comment. Upstream adds a test. But it looks to
me like it won't run because the quilt patch can't handle the executable
bit. Looks like there's a workaround in debian/tests/control for another
case of the same issue. Please could you
kipping November 1.
>
> On Wed, Jun 08, 2022 at 12:30:08PM +0100, Robie Basak wrote:
> > Hi,
> >
> > I'm sure you're aware that Steve's availability to attend TB meetings is
> > limited at the moment. He's offline at the moment, and needs the meeting
> >
On Thu, Oct 06, 2022 at 02:34:40PM -, Corey Reichle wrote:
> > Socket activation provides a smoother (runtime) UX for users
>
> SSHD configuration is not a user issue, but a systems administration
> issue.
Maybe, but more important is the UX for users of ssh clients who aren't
trying to
On Thu, Oct 06, 2022 at 01:04:05PM -, Corey Reichle wrote:
> If the point is to increase density, then sshd should just be off, and
> not automatically started, unless it's required for work.
Socket activation provides a smoother (runtime) UX for users, and is
well established as a mechanism
I'm not sure about this. What's the pattern that users can expect to see
across all packages that provide socket activated services in Ubuntu in
the future? I think there are three options here: "always", "sometimes"
and "never". We could ensure that there's _always_ a generator that
creates the
** Tags added: ssh-socket-activation
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1991592
Title:
openssh-server should ship a systemd generator to generate ssh socket
** Tags added: ssh-socket-activation
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1990863
Title:
conversion from sshd service to socket is too bumpy
Status in openssh
** Tags added: socket-activation ssh
** Tags removed: socket-activation ssh
** Tags added: ssh-socket-activation
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1991199
Public bug reported:
On Jammy and earlier, simply running "sshd -i" worked.
Now, it fails silently, and running it with "-d" gives me:
Missing privilege separation directory: /run/sshd
This directory is normally created with "RuntimeDirectory=sshd" as
defined in
In terms of risk, touching apt is always going to be high risk because
users need apt to revert or upgrade away from any regression. QA is
therefore essential. Normally I'd like this to "bake" in the development
release first, but given the nature of the bug, that's probably not
going to give us
Hello Jeremy, or anyone else affected,
Accepted apt into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.4.8 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello elatllat, or anyone else affected,
Accepted apt into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.4.8 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
In terms of risk, touching apt is always going to be high risk because
users need apt to revert or upgrade away from any regression. QA is
therefore essential. Normally I'd like this to "bake" in the development
release first, but given the nature of the bug, that's probably not
going to give us
On Wed, Sep 28, 2022 at 01:19:35PM -, Jonathan Kamens wrote:
> 1) Nobody reads the release notes.
That's where we document edge case issues that can't be handled
automatically. Maybe we can handle this automatically, which is why I
invited Steve to take a look. But if it turns out that we
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Feedback on this is appreciated as we do want to make the
transition as smooth as possible.
I would warn though that just overwriting configuration files with
"known good" ones following a release upgrade, as
[mysql-8.0]- mysql_secure_installation can not set root
> password and end…*
> Here I was very careful when I've noticed that it's mysql issue. I have
> added workaround for it in the comment sections.
> @Robie Basak , @Lena Voytek
> could you take a look at this bug an
Hello Renan, or anyone else affected,
Accepted ubuntu-advantage-tools into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-advantage-
tools/27.11.1~22.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing
On Mon, Sep 26, 2022 at 02:34:43PM -0400, Sergio Durigan Junior wrote:
> ### https://pad.lv/1890263 - +(In Progress) [php-defaults] - release
> upgrade does not move to the new php apache mod
>
> Last comment was from Christian, who said that they're waiting for Robie
> to sync with Steve on
On Thu, Sep 22, 2022 at 11:32:05PM +0200, Ghislain Adnet wrote:
> in fact /etc/mysql/mariadb.cnf does not exist as there is a mysql server and
> not a mariadb one.
mariadb-common ships /etc/mysql/mariadb.cnf.
> I have a perconna mysql server running and i want to install mytop that
> require a
On Thu, Sep 22, 2022 at 05:28:27PM +0100, Robie Basak wrote:
> Again, note that I'm still speculating here because I don't follow the
> exact sequence of events which is causing the third party packaging to
> trip up here. If there's something we're doing wrong then we should fix
> it,
On Thu, Sep 22, 2022 at 06:21:34PM +0200, Ghislain Adnet wrote:
> So perhaps we could see it another way :
> in this particular case i think that a client library, if it find an existing
> /etc/mysql/my.cnf, should not do anything as it is there adn so everything it
> need is okay.
> There is no
On Thu, Sep 22, 2022 at 05:10:05PM +0200, nobody wrote:
>* What outcome did you expect instead?
>
>installing a client library should not require anything on the server side
> and should not modify server configuration of mariadb or other mysql flavors
> (imho ;p)
Both MySQL/MariaDB
Package: libdebuginfod-common
Version: 0.187-2
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic
Hi,
libdebuginfod-common sets DEBUGINFOD_URLS to a reasonable default (after
prompting appropriately because it's a privacy leak otherwise).
But Debian Policy 9.9 says: "Programs
Package: libdebuginfod-common
Version: 0.187-2
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic
Hi,
libdebuginfod-common sets DEBUGINFOD_URLS to a reasonable default (after
prompting appropriately because it's a privacy leak otherwise).
But Debian Policy 9.9 says: "Programs
The test plan looks good - thanks!
On reviewing the patch itself, it looks quite complex. We took a look
upstream to see if there were any further fixes on the commit being
cherry-picked, and found at least one. See
The test plan looks good - thanks!
On reviewing the patch itself, it looks quite complex. We took a look
upstream to see if there were any further fixes on the commit being
cherry-picked, and found at least one. See
> We can't really store reasons for why something is kept back.
How about:
When something is scored down because it is not phased, make a note.
When the scoring is all done, take the list of held back packages, and
identify all those that have a note against them. Then print (up to) two
lists:
** Changed in: openldap (Ubuntu)
Status: Invalid => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1983618
Title:
New upstream microrelease 2.5.13
Status
** Changed in: openldap (Ubuntu)
Status: Invalid => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to openldap in Ubuntu.
Matching subscriptions: Ubuntu Server/Client Support Team
Apparently upstream don't want us to cherry-pick the fix. It's probably
fine legally, but I don't think it's worth getting into that given that
I was only volunteering my time to try and help.
Setting Won't Fix since it seems that this is unlikely to get fixed in
Jammy then. I've not checked the
Upstream fix here:
https://github.com/josephwright/beamer/commit/f769f2ff60f3ade9b920f743ff65b46e5013758a
** Summary changed:
- Bug in beamer with fix in v3.66
+ beamer fails to handle the xcolor package options
** Also affects: texlive-base (Ubuntu Jammy)
Importance: Undecided
On Thu, Sep 15, 2022 at 10:41:26AM -0700, Bryce Harrington wrote:
> > > LP: #1964829 - Triaged [apache2] - AH02808 when
> > > using long (> 96 chars) ProxyPass worker name
> >
> > Fix Released for the development release. SRU tasks remain open, but I noted
> > that there
Nothing significant to note. Mostly work in progress, or minor metadata tweaks.
Nothing new added to the backlog.
Bugs last updated between 2022-09-09 (Friday) and 2022-09-11 (Sunday) inclusive
Date range identified as: "Monday triage"
Found 10 bugs
> LP: #1979879 - *+Fix Released [samba]
According to https://bz.apache.org/bugzilla/show_bug.cgi?id=53218 this
was fixed upstream in 2.4.53. Kinetic has 2.4.54-2ubuntu1 so this is
presumed fixed in Kinetic, and bug tasks remain open for Focal and
Jammy.
** Changed in: apache2 (Ubuntu)
Status: Triaged => Fix Released
--
You
Hello iBug, or anyone else affected,
Accepted openssh into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:8.2p1-4ubuntu0.6 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
I'm not doubting that the revert was correct for upstream. But we have a
different context in a stable release, where users may be relying on
behaviours that upstream are at liberty to change in their main
development branch, but we are not in our stable releases. Further, we
can't just assume
I'm not doubting that the revert was correct for upstream. But we have a
different context in a stable release, where users may be relying on
behaviours that upstream are at liberty to change in their main
development branch, but we are not in our stable releases. Further, we
can't just assume
Hello Kangarooo, or anyone else affected,
Accepted sudo into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/sudo/1.9.9-1ubuntu2.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This is definitely a bug that we want to fix in Focal. But is this
particular code change the correct way to do it?
Won't reverting this commit regress the fix that was introduced by the
commit in the first place? I think this needs a proper analysis of the
possible implications for unaffected
This is definitely a bug that we want to fix in Focal. But is this
particular code change the correct way to do it?
Won't reverting this commit regress the fix that was introduced by the
commit in the first place? I think this needs a proper analysis of the
possible implications for unaffected
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
According to the upstream bug, this is the upstream commit to master:
https://github.com/squid-
cache/squid/commit/752fa2083698a88533ef23d88490f43f153f7a4c
It looks like this was fixed in 5.5-1, so marking Fix
Hi Erich,
On Fri, Sep 09, 2022 at 05:32:45PM -0700, Erich Eickmeyer wrote:
> You may have seen my post and discussion in the MLs of ubuntu-devel, kubuntu-
> devel and ubuntu-studio-devel (really, those with the Plasma desktops)
> lacking
> a way to be notified when a new Ubuntu version is
On Fri, Sep 09, 2022 at 11:53:31AM +0200, Philipp Kewisch wrote:
> On 9/9/22 11:27 AM, Robie Basak wrote:
> >On Thu, Sep 08, 2022 at 03:37:39PM +0200, Philipp Kewisch wrote:
> >>2022-11-24 Nominations close, send to Mark for shortlisting
> >>2022-12-01 Voting announced
&
The correct logic shouldn't be hard to write, unless I'm missing
something? So can we just do it right, and as soon as is necessary? If
it's obviously correct, I don't think we need to wait for upstream
acceptance, but equally it shouldn't take them long to review it either.
Because the parameters
The verification of the Stable Release Update for dmidecode has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for dmidecode has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1535768
Title:
pkexec tty hijacking via TIOCSTI ioctl
Status in
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1535768
Title:
pkexec tty hijacking via TIOCSTI ioctl
The verification of the Stable Release Update for python-openstackclient
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that
The Test Plan also says:
> * Additionally if possible test that integration in an English based
locale still works.
Was this done please?
And which version of the package was tested?
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to
That's a good question. I think it's up to Simon and the Foundations
team what they want to do there. There is far less of a risk to users
either way in Kinetic, because it hasn't been released yet. So I have no
preference for Kinetic, though it does make sense to revert to me.
--
You received
Hi,
On Tue, Dec 21, 2021 at 05:33:17PM +0100, Lucas Nussbaum wrote:
> Source: google-authenticator
> Version: 20191231-2
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20211220 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all
Hi,
On Tue, Dec 21, 2021 at 05:33:17PM +0100, Lucas Nussbaum wrote:
> Source: google-authenticator
> Version: 20191231-2
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20211220 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all
An upload of openssl to jammy-proposed has been rejected from the upload
queue for the following reason: "See discussion in LP: #1979639".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
Thanks everyone for the discussion. As there have been no further
comments, I think it's appropriate to make a decision. I'll reject the
openssl upload from Jammy, and mark that task Won't Fix. We won't update
the default configuration in Jammy. Third parties who ship software
intended for Jammy
In #ubuntu-security just now:
14:44 sarnold: please could we have a definitive nack if you
don't want bug 1981807 in the security pocket? Looking at the previous
IRC conversation, it looks like it was a "decision pending review".
--
You received this bug notification because you are a member
In #ubuntu-security just now:
14:44 sarnold: please could we have a definitive nack if you
don't want bug 1981807 in the security pocket? Looking at the previous
IRC conversation, it looks like it was a "decision pending review".
--
You received this bug notification because you are a member
> For that reason, I do apologize for the large diff, and I hope this is
a good explanation for that and the bugs fixes covered in the diff.
Rather than filing separate bug reports for each of these, I'd rather
get it all taken care of with at once here.
Please see
Is there any possibility that passing through this environment variable
when we previously did not will change behaviour in such a way that a
user treats that as a regression? For example, if some user has a
setting that causes some app to now break, when it didn't before?
Your upload changes the
An upload of sudo to jammy-proposed has been rejected from the upload
queue for the following reason: "The mode of debian/source_sudo.py is
changed but this is not explained in the changelog or SRU information".
--
You received this bug notification because you are a member of Ubuntu
Touch
Progress to fix this in Jammy is still blocked on a test plan.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1937110
Title:
dhcp option 121 & 249
Status in subiquity:
Hi,
[cutting out the Cc list since I don't know if they want this traffic]
FreeCAD 0.20.1 is available as a stable snap, and 0.21-g2b5452d1 is
available in edge. These are published officially by upstream.
You can install with:
"sudo snap install freecad"
...and then you'll have 0.20.1
The verification of the Stable Release Update for xdg-utils has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for openldap has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
The verification of the Stable Release Update for epiphany-browser has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for calamares-settings-
ubuntu has completed successfully and the package is now being released
to -updates. Subsequently, the Ubuntu Stable Release Updates Team is
being unsubscribed and will not receive messages about this bug report.
In the event
** Changed in: cyrus-sasl2 (Ubuntu Jammy)
Assignee: Andreas Hasenack (ahasenack) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1912256
Title:
> For focal we can only test the current kernel (hwe-5.15 has not yet
picked up the lastest jammy changes because of the upcoming point
release)
It seems odd to release an SRU without the ability to test what it is
fixing. If it turns out not to fix it, we'd have to be doing an SRU
again for no
https://wiki.ubuntu.com/StableReleaseUpdates#tzdata says "Uploads should
also be made to any releases supported via ESM". I see a bug task but
nothing in the queue. What are your plans on this, please?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Hello Jason, or anyone else affected,
Accepted tzdata into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2022c-0ubuntu0.22.04.0 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Jason, or anyone else affected,
Accepted tzdata into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2022c-0ubuntu0.18.04.0 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Jason, or anyone else affected,
Accepted tzdata into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2022c-0ubuntu0.20.04.0 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
tus: check if contract has updated and notify user to run "ua refresh"
Date: 2022-08-09 18:30:09.532116+00:00
Changed-By: Lucas Albuquerque Medeiros de Moura
Signed-By: Robie Basak
https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/27.10.1~16.04.1
Sorry, changesfile not availabl
On Mon, Aug 29, 2022 at 07:30:26PM -0700, Bryce Harrington wrote:
> Does mysql require both /etc/mysql/conf.d/ and /etc/mysql/mysql.conf.d/?
> The packaging seems to suggest this is so, but is that redundant?
IIRC, conf.d/ is for the client library which is shared by everything.
mysql.conf.d/ is
On Wed, Aug 17, 2022 at 04:00:19PM -0600, Dan Bungert wrote:
> I hereby apply for core-dev.
Today, the DMB voted to approve Dan's core dev application.
Congratulations, Dan, and thank you for your previous and continued
contributions!
On behalf of the DMB,
Robie
signature.asc
Description:
On Thu, Aug 18, 2022 at 08:28:29AM -0700, Steve Langasek wrote:
> I'm concerned that this requires subscription to the package in Debian for
> this to not fall off the radar. We have merges.ubuntu.com which tracks
> which packages need to be updated, and the standing assumption is that the
>
On Wed, Aug 17, 2022 at 05:43:33PM +0100, Luca Boccassi wrote:
> ... We are not going to completely overhaul
> our development and maintenance practices and commit to a ton of extra
> work (forever)...
As far as I can tell, it's a gross misrepresentation of the
There's further discussion in the ubuntu-devel ML thread.
In addition to that though, I notice that mkosi in Jammy does refer to
/usr/bin/systemd-repart. Will the Jammy packaged mkosi therefore change
behaviour if you start shipping it in Ubuntu?
--
You received this bug notification because
On Wed, Aug 17, 2022 at 03:09:45PM +0100, Luca Boccassi wrote:
> The difference is that here it's the upstream maintainers asking for
> this, not just users. From our point of view, not including repart in
> Jammy was an oversight - there was really no reason to keep it
> disabled, other than we
> Fixing this is nice for the users, but OTOH very low severity and
would cause a package download and update on almost every Ubuntu in the
world. Therefore we will mark this as block-proposed and keep it in
focal-proposed so that a later real update (security or functional) will
pick this up from
On Wed, Aug 17, 2022 at 02:02:57PM +0100, Luca Boccassi wrote:
> It's really a lot of work for nothing,
> given the risk is really zero - it's a new command line program that is
> inhert and doesn't do anything until it's called manually...
On this point, I disagree.
On Wed, Aug 17, 2022 at 02:02:57PM +0100, Luca Boccassi wrote:
> > > Unfortunately, they're currently blocked on this because 22.04
> > doesn't
> > > ship systemd-repart. The upstream CI uses Github Actions which runs
> > on
> > > Ubuntu Jammy and will do so until the next Ubuntu LTS is released.
Hello Marco, or anyone else affected,
Accepted gnome-shell into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/42.4-0ubuntu0.22.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Marco, or anyone else affected,
Accepted gnome-shell into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/42.4-0ubuntu0.22.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Marco, or anyone else affected,
Accepted gnome-shell into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/42.4-0ubuntu0.22.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Marco, or anyone else affected,
Accepted gnome-shell into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/42.4-0ubuntu0.22.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
601 - 700 of 17396 matches
Mail list logo
