On Wed, Apr 10, 2019 at 04:27:09AM +0200, Matthias Klose wrote:
> >> Regarding rails I agree with dropping it from Disco, but this is more
> >> of a call for help to get it in again in Disco+1 if there is a strong
> >> community around it rather than discouraging people from maintaining
> >> langu
On 05.04.19 06:10, Steve Langasek wrote:
> Hi Matthias,
>
> On Thu, Apr 04, 2019 at 02:07:50PM +0200, Matthias Klose wrote:
>> On 04.04.19 01:52, Steve Langasek wrote:
>>> Thanks, Robie, for kicking off this discussion.
>
>>> In regards to rails in particular, I would like to note that the same
>
On 4/9/19 10:53 PM, Matthias Klose wrote:
> On 10.04.19 05:48, Simon Quigley wrote:
>> On 4/9/19 10:15 PM, Matthias Klose wrote:
>>> On 10.04.19 04:37, Simon Quigley wrote:
On 4/9/19 9:27 PM, Matthias Klose wrote:
> rails is ready to migrate, there is no puma package in the release
On 10.04.19 05:48, Simon Quigley wrote:
> On 4/9/19 10:15 PM, Matthias Klose wrote:
>> On 10.04.19 04:37, Simon Quigley wrote:
>>> On 4/9/19 9:27 PM, Matthias Klose wrote:
rails is ready to migrate, there is no puma package in the release pocket.
the
failing puma autopkg test in -pr
On 4/9/19 10:15 PM, Matthias Klose wrote:
> On 10.04.19 04:37, Simon Quigley wrote:
>> On 4/9/19 9:27 PM, Matthias Klose wrote:
>>> rails is ready to migrate, there is no puma package in the release pocket.
>>> the
>>> failing puma autopkg test in -proposed shouldn't be any concern.
>>>
>>> Filed
On 10.04.19 04:37, Simon Quigley wrote:
> On 4/9/19 9:27 PM, Matthias Klose wrote:
>> rails is ready to migrate, there is no puma package in the release pocket.
>> the
>> failing puma autopkg test in -proposed shouldn't be any concern.
>>
>> Filed LP: #1824049 for that.
>>
>> Now we could go on re
On 4/9/19 9:27 PM, Matthias Klose wrote:
> rails is ready to migrate, there is no puma package in the release pocket. the
> failing puma autopkg test in -proposed shouldn't be any concern.
>
> Filed LP: #1824049 for that.
>
> Now we could go on removing puma from -proposed, and then rails should
On 06.04.19 00:14, Steve Langasek wrote:
> Hi Balint,
>
> On Thu, Apr 04, 2019 at 02:45:23PM +0200, Balint Reczey wrote:
>>> This is short-sighted, and greatly influenced by the voices of
>>> language-specific
>>> upstream communities. As seen at several occasions at PyCon: Ask an
>>> upstream
Hi Balint,
On Thu, Apr 04, 2019 at 02:45:23PM +0200, Balint Reczey wrote:
> > This is short-sighted, and greatly influenced by the voices of
> > language-specific
> > upstream communities. As seen at several occasions at PyCon: Ask an
> > upstream
> > community, which Linux distribution they us
On 03.04.19 13:41, Robie Basak wrote:
> I'd like to talk about addressing the difficulty in maintenance of long
> tail language-specific stacks in Ubuntu. For example, right now
> `src:rails` is stuck in disco-proposed[1]. It seems to me that we spend
> a disproportionate amount of effort trying to
Hi Matthias,
On Thu, Apr 04, 2019 at 02:07:50PM +0200, Matthias Klose wrote:
> On 04.04.19 01:52, Steve Langasek wrote:
> > Thanks, Robie, for kicking off this discussion.
> > In regards to rails in particular, I would like to note that the same
> > version of the rails package is present in the
On Thu, Apr 04, 2019 at 02:07:50PM +0200, Matthias Klose wrote:
> This is short-sighted, and greatly influenced by the voices of
> language-specific
> upstream communities. As seen at several occasions at PyCon: Ask an upstream
> community, which Linux distribution they use (majority of hands go
Hi,
On Thu, Apr 4, 2019 at 2:08 PM Matthias Klose wrote:
>
> On 04.04.19 01:52, Steve Langasek wrote:
> > Thanks, Robie, for kicking off this discussion.
> >
> > In regards to rails in particular, I would like to note that the same
> > version of the rails package is present in the bionic, cosmic
On 04.04.19 06:08, Seth Arnold wrote:
> On Wed, Apr 03, 2019 at 12:41:04PM +0100, Robie Basak wrote:
>> 1. If a language-specific package, or stack of packages, is stuck in
>> proposed, and nobody is volunteering to get them migrated, then we are
>> more willing to delete them from the release poc
On 04.04.19 01:52, Steve Langasek wrote:
> Thanks, Robie, for kicking off this discussion.
>
> In regards to rails in particular, I would like to note that the same
> version of the rails package is present in the bionic, cosmic, and disco
> releases. Despite several uploads and syncs/merges from
On Thu, 4 Apr 2019 at 00:41, Robie Basak wrote:
>
> I'd like to talk about addressing the difficulty in maintenance of long
> tail language-specific stacks in Ubuntu. For example, right now
> `src:rails` is stuck in disco-proposed[1]. It seems to me that we spend
> a disproportionate amount of eff
On Wed, Apr 03, 2019 at 12:41:04PM +0100, Robie Basak wrote:
> 1. If a language-specific package, or stack of packages, is stuck in
> proposed, and nobody is volunteering to get them migrated, then we are
> more willing to delete them from the release pocket and release without
> that stack.
Than
Thanks, Robie, for kicking off this discussion.
In regards to rails in particular, I would like to note that the same
version of the rails package is present in the bionic, cosmic, and disco
releases. Despite several uploads and syncs/merges from Debian, no new
version of the rails package that h
I'd like to talk about addressing the difficulty in maintenance of long
tail language-specific stacks in Ubuntu. For example, right now
`src:rails` is stuck in disco-proposed[1]. It seems to me that we spend
a disproportionate amount of effort trying to get this class of package
migrated to the rel
19 matches
Mail list logo
