On Wed, Jun 07, 2023 at 05:35:21PM +0200, Mattia Rizzolo wrote:
> Today we had a Backporters meeting, and indeed we don't have any
> opposition to this latest proposal, thank you for the prods, and I'm
> happy that this topic is finally coming to a close!
Thanks!
> Please do email us a bit more
Hi!
Thank you for your time on this.
On Wed, Mar 01, 2023 at 04:22:13PM +0100, Mattia Rizzolo wrote:
> > > So I think we are starting to get to the crux of the difference in
> > > viewpoints from the TB to the backporters team. Due to the past history
> > > of some perceived dysfunction within
On Tue, Mar 22, 2022 at 04:46:45PM -0400, Dan Streetman wrote:
> > However the equivalent text you have now only says "The mission of the
> > Ubuntu Backporters Team is to maintain the backports pocket of all
> > stable Ubuntu releases." with no mention of that.
> >
> > In fact that's the case for
On Tue, Mar 22, 2022 at 04:10:38PM -0400, Dan Streetman wrote:
> The team has had previous discussions around governance, yes, and of
> course those discussions played a part in forming this document. I
> don't really know what exactly you mean by any/all discussions being
> 'incorporated' into
On Mon, Mar 21, 2022 at 12:44:43PM -0400, Dan Streetman wrote:
> I see this charter as the one and only official document (except where
> the charter specifically delegates to other document(s)) for guiding
> what the team does and how the team does it. It supersedes any
> previous discussion. Is
On Mon, Mar 21, 2022 at 10:21:19AM -0400, Dan Streetman wrote:
> The Ubuntu Backports team has drafted a Charter and we request that
> you review it and, if you approve, please provide your approval
> ("ratification") by email. If you have any concerns or comments,
> please let us know.
Related
Dear Backporters Team,
Thank you for your work in restoring the team and a functional process,
and congratulations on your recent announcement on the reopening of the
backports pocket.
There is one thing I'd like to wrap up relating to the reboot please. In
my email that kicked this off
Hi Iain,
Perhaps I see the situation differently from you. From my perspective,
this is an extraordinary intervention "from above" by consensus from
Ubuntu developers. The backporters team has been unable to act for an
extended period of time, and when threatened with closure, nobody from
the
On Wed, Jul 28, 2021 at 10:53:37AM -0400, Thomas Ward wrote:
> I volunteered via IRC in #ubuntu-devel to ddstreet. I think that got buried
> though...
Great. Thank you!
signature.asc
Description: PGP signature
--
ubuntu-backports mailing list
ubuntu-backports@lists.ubuntu.com
Modify settings
Hi Mattia,
Thank you for organising getting things going!
I'll stay out of any decisions since I won't be a member of the new
team. I'd like to suggest, though, that you try and keep discussion in
ubuntu-devel@ if possible. IMHO, keeping ubuntu-backports@ discussions
separately in its own list
On Thu, Jul 22, 2021 at 05:00:26PM -0400, Dan Streetman wrote:
> So as far as next steps based on your proposal, it seems like:
I detailed the next steps specifically in my proposal but focused on
slightly different things, so I appreciate you laying out your
perspective also. What you suggest
Hi Mattia,
Thank you for your support, and for volunteering for the second role!
On Wed, Jul 21, 2021 at 12:56:07PM +0200, Mattia Rizzolo wrote:
> > [1] To be clear, I believe that the current process requires
> > sponsorship/upload of a suitable backport, and the backporters team only
> >
Thank you for volunteering! As we have at least one qualified person
committed, I'd be very happy to see the backports pocket continue. As a
concrete proposal, I suggest we do this by reforming ~ubuntu-backporters
as follows.
In particular I wanted to enumerate a specific transition plan and the
[Dropping random extra Ccs; let's not just spam all the lists, please.
If you want people on other MLs to be aware of this thread, I think it's
sufficient to just send one email to point to it]
On Mon, Jul 19, 2021 at 11:25:48AM -0700, Erich Eickmeyer wrote:
> When was the last time this was
Hi Erich,
On Mon, Jul 19, 2021 at 10:18:36AM -0700, Erich Eickmeyer wrote:
> TL;DR: Don't sunset the backports, but reform the process.
Ubuntu is a meritocracy. We invite anybody, from any company, to
participate in any aspect of the project.
I would be happy to see the backports process stay,
On Mon, Jul 19, 2021 at 10:17:44AM -0400, Jeffrey Lane wrote:
> Would it be worthwhile, (or possible) to keep it open quietly for
> special cases?
We can certainly leave ourselves open for the backports process to
restart if someone steps up and adapts it into something workable.
Similarly, I'm
On Mon, Jul 19, 2021 at 05:16:30PM +0200, Gunnar Hjalmarsson wrote:
> If I have upload rights for a package, I can also upload to the SRU queue.
> When doing so, I'm supposed to take pains that the upload and related bug
> report comply with the SRU policy, to facilitate the review by an SRU team
On Mon, Jul 19, 2021 at 10:42:06AM -0400, Thomas Ward wrote:
> Have we actually confirmed this though, Robie? If I remember right, I was
> able to push something to -backports with my coredev once, and it didn't
> complain on the upload permissions side of things. Unless I am forgetting
>
On Mon, Jul 19, 2021 at 02:33:58PM +0100, Iain Lane wrote:
> The best way forward would be if someone had the spoons for that.
> happy to help review, but I'm not likely to drive it, sorry. In the
> absence of any of this happening, I would support notifying folks that
> the current process is
On Mon, Jul 19, 2021 at 02:24:30PM +0200, Mattia Rizzolo wrote:
> I don't remember teward's proposals from 2 years ago...
For reference, here's that thread:
https://lists.ubuntu.com/archives/ubuntu-devel/2019-January/040575.html
and, from the following month:
Dear Ubuntu Developers,
As far as I am aware, the Ubuntu Backports Team has been inactive for
years now, and backports requests and uploads just languish in
Launchpad. Thomas Ward last proposed an effort to revitalise it over two
years ago, but with no response. I believe he's no longer available
(still subject to SRU team approval, etc)
** Changed in: apache2 (Ubuntu Trusty)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to Precise Backports.
https://bugs.launchpad.net/bugs/1422417
Title:
No action for the main apache2 package. This affects the Trusty
backports project only.
** Changed in: apache2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to trusty-backports.
Matching
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Does this issue affect the backport only, or does it also affect haproxy
on Trusty or the release the backport was from?
Since you've reported this as affecting the backport I'll reassign to
the backports
Louis,
I can't sponsor your debdiff into backports, but be careful of ordering
issues in your patch. clean() should be defined before the trap is set,
and tmp should be defined before any point that clean() could be called.
In general you should quote "$tmp" as well in case it ends up with
spaces
As discussed, this bug needs a justification against SRU policy to make
any progress, so marking this as Incomplete for Trusty. Alternatively
(sorry I failed to mention this on IRC) you can seek a backport via the
backports pocket so users can opt in to using it. See
** Package changed: haproxy (Ubuntu) = trusty-backports
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to trusty-backports.
Matching subscriptions: ubuntu-backporters
https://bugs.launchpad.net/bugs/1472713
Title:
HAProxy 1.5.3
Thank you for taking the time to report this bug and helping to make
Ubuntu better. In case you are not familiar,
https://wiki.ubuntu.com/UbuntuBackports documents the process that needs
to be followed for this. Volunteers welcome.
** Package changed: bcache-tools (Ubuntu) = trusty-backports
**
** Changed in: squid3 (Ubuntu)
Status: New = Triaged
** Changed in: squid3 (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to Precise Backports.
https://bugs.launchpad.net/bugs/1175049
** Also affects: maverick-backports
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to maverick-backports.
https://bugs.launchpad.net/bugs/986649
Title:
puppet agent can't obtain catalogs
To
30 matches
Mail list logo
