On Sat, 11 Jul 2020, Henrique de Moraes Holschuh wrote:
> On Sat, 11 Jul 2020, Niels Thykier wrote:
> > This is a heads up about my intention to remove debhelper compat levels
> > 5 and 6. This is also an intention to do a MFB for this removal now at
>
> ...
>
> >
On Sat, 11 Jul 2020, Niels Thykier wrote:
> This is a heads up about my intention to remove debhelper compat levels
> 5 and 6. This is also an intention to do a MFB for this removal now at
...
> Henrique de Moraes Holschuh
>freepats
Oh wow, I haven't looked at this pack
Hi,
This is a heads up about my intention to remove debhelper compat levels
5 and 6. This is also an intention to do a MFB for this removal now at
severity important, which will be bumped to RC later.
With the current rate of migration as well as the current number of RC
bugs in testing, I
On 5/22/19 2:28 PM, Adam Borowski wrote:
> On Wed, May 22, 2019 at 02:06:03PM +0200, Simon Richter wrote:
>> I just did a very annoying backport. The reason it was annoying was that
>> two of the packages involved specified a debhelper compat level of 11.
>>
>> So in order to do the backport, I fir
On Wed, May 22, 2019 at 04:53:57PM +0200, Marc Haber wrote:
> >> So in order to do the backport, I first had to get debhelper 11 (or 12).
> >
> >You make it sound so hard, but in my own experience it really isn't.
>
> I totally feel with Simon, especially in the later part of a stable
> release ba
On Wed, 22 May 2019 14:59:18 +0200, Mattia Rizzolo
wrote:
>On Wed, May 22, 2019 at 02:06:03PM +0200, Simon Richter wrote:
>> So in order to do the backport, I first had to get debhelper 11 (or 12).
>
>You make it sound so hard, but in my own experience it really isn't.
I totally feel with Simon,
On Wed, May 22, 2019 at 02:06:03PM +0200, Simon Richter wrote:
> So in order to do the backport, I first had to get debhelper 11 (or 12).
You make it sound so hard, but in my own experience it really isn't.
> The debhelper 12 package itself has a compat level of 12, which means I
> couldn't compi
On Wed, May 22, 2019 at 02:06:03PM +0200, Simon Richter wrote:
> I just did a very annoying backport. The reason it was annoying was that
> two of the packages involved specified a debhelper compat level of 11.
We have debhelper 12 already available:
| debhelper | 12.1.1~bpo9+1 | stretch-bac
On Wed, May 22, 2019 at 02:06:03PM +0200, Simon Richter wrote:
> I just did a very annoying backport. The reason it was annoying was that
> two of the packages involved specified a debhelper compat level of 11.
>
> So in order to do the backport, I first had to get debhelper 11 (or 12).
>
> The d
On Wed, May 22, 2019 at 02:06:03PM +0200, Simon Richter wrote:
> I just did a very annoying backport. The reason it was annoying was that
> two of the packages involved specified a debhelper compat level of 11.
>
> So in order to do the backport, I first had to get debhelper 11 (or 12).
[...]
> -
Hi,
I just did a very annoying backport. The reason it was annoying was that
two of the packages involved specified a debhelper compat level of 11.
So in order to do the backport, I first had to get debhelper 11 (or 12).
The debhelper 12 package itself has a compat level of 12, which means I
cou
debhelper dependency to
> >>>> Standards-Version ?
> >>> There are packages which may break with newer debhelper, but can be
> >>> easily updated to the current policy.
> >>>
> >>
> >> Also, there are packages that deliberately hold
There are packages which may break with newer debhelper, but can be
>>> easily updated to the current policy.
>>>
>>
>> Also, there are packages that deliberately hold back on adopting new
>> debhelper compat levels because they want to be backportable as-
[forced change to debhelper v6 compat]
> Do not follow the advice of that sponsor, look for a different sponsor
> instead. Only ever update the debhelper dependency if you really use a
> feature of the new version.
Now, as this raised some comments on IRC, lets clarify it a bit:
- compat mode v
14 matches
Mail list logo
