On Wed, May 02, 2018 at 11:09:46PM +0200, Paul Gevers wrote:
> tl;dr: migration from unstable to testing is influenced by the results
> of autopkgtest tests of your own package as well as those of your
> reverse dependencies.
AWESOME
Thank you to everone who worked and works on this!
--
chee
Paul Gevers writes ("Re: Dealing with ci.d.n for package regressions"):
> On 03-05-18 14:12, Ian Jackson wrote:
> > 3. "Required age increased by 10 days because of autopkgtest"
> > seems to appear when either (i) when there are tests that should be
> > run but which haven't completed and (ii) when
Mattia Rizzolo writes ("Re: Dealing with ci.d.n for package regressions"):
> On Thu, May 03, 2018 at 10:38:45PM +0200, Paul Gevers wrote:
> > Just add it as a test dependency in one of your tests?
>
> Just to share a bit that doesn't seem to be of public knowledge:
> .dsc have a Testsuite-Triggers
Ian Jackson writes ("Re: Dealing with ci.d.n for package regressions"):
> I hadn't realissed that _test_ dependencies would trigger retests, as
> well as actual package dependencies.
Having read Mattia's message, and looking at the Testsuite-Triggers
line which is autogenerated in dgit.dsc, I see
On Fri, May 04, 2018 at 11:55:56AM +0100, Ian Jackson wrote:
> Mattia Rizzolo writes ("Re: Dealing with ci.d.n for package regressions"):
> > On Thu, May 03, 2018 at 10:38:45PM +0200, Paul Gevers wrote:
> > > Just add it as a test dependency in one of your tests?
> >
> > Just to share a bit that do
On Fri, 2018-05-04 at 12:08:31 +0100, Ian Jackson wrote:
> Ian Jackson writes ("Re: Dealing with ci.d.n for package regressions"):
> > I hadn't realissed that _test_ dependencies would trigger retests, as
> > well as actual package dependencies.
>
> Having read Mattia's message, and looking at the
Hi!
On Mon, 2018-04-30 at 20:23:15 +, Nick Terrell wrote:
> On Fri, 27 Apr 2018, Guillem Jover wrote:
> [...]
> > * Format stability: Although it's supposedly frozen now, it has
> > changed quite often in recent times. AFAIR it was also mentioned at
> > least in the past that the target was ma
Hi!
On Fri, 2018-04-27 at 07:02:12 +0200, Guillem Jover wrote:
> The following is a quick run-down of the items from [F], not all
> being important from Debian's perspective, but being for dpkg's:
> * License: Permissive (dual BSD + GPL-2), which makes universal
> availability possible.
Unfort
James Clarke writes ("Re: Dealing with ci.d.n for package regressions"):
> On Fri, May 04, 2018 at 11:55:56AM +0100, Ian Jackson wrote:
> > Is that documented somewhere ? I can't find it here
> > https://manpages.debian.org/stretch/dpkg-dev/dpkg-source.1.en.html
> > https://manpages.debian.org
Paul Gevers writes ("Dealing with ci.d.n for package regressions"):
> As I just announced on d-d-a¹, we have enabled autopkgtest usage for
> unstable-to-testing migration.
I observe that the tests done for this are done without building the
source, where this is a feature advertised by the test su
Package: wnpp
Severity: wishlist
Owner: Sruthi Chandran
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-turbolinks
Version : 5.1.1
Upstream Author : packagethief, sstephenson
* URL : https://github.com/turbolinks/turbolinks#readme
* License : E
Julien Cristau schrieb:
> I expect nothing much different from previous ESR cycles: stretch will
> move to 60 after 52 goes EOL in September.
Exactly.
Cheers,
Moritz
Package: wnpp
Severity: wishlist
Owner: Steffen Moeller
* Package name: soapsnp
* URL : http://soap.genomics.org.cn/soapsnp.html
* License : GPL
Description : resequencing utility that can assemble consensus sequence
of genomes
Packaging team-maintained on https://
Quoting Moritz Mühlenhoff :
Julien Cristau schrieb:
I expect nothing much different from previous ESR cycles: stretch will
move to 60 after 52 goes EOL in September.
Exactly.
How will we deal with breaking extensions?
E.g. I'm using xul-ext-scrapbook a lot. AFAIK, upstream does
not provide
Package: wnpp
Severity: wishlist
Owner: Kyle Robbertze
* Package name: hashcheck
Version : 1.0.0
Upstream Author : Kyle Robbertze
* URL : https://gitlab.com/paddatrapper/hashcheck
* License : GPL-3+
Programming Lang: C++
Description : verifies the file
Package: wnpp
Severity: wishlist
Owner: Steffen Moeller
* Package name: soapaligner
* URL : http://soap.genomics.org.cn/soapaligner.html
* License : GPL
Programming Lang: C
Description : aligner of short reads of next generation sequencers
Package team-maintained
On 04/05/18 17:42, W. Martin Borgert wrote:
> Quoting Moritz Mühlenhoff :
>> Julien Cristau schrieb:
>>> I expect nothing much different from previous ESR cycles: stretch will
>>> move to 60 after 52 goes EOL in September.
>>
>> Exactly.
>
> How will we deal with breaking extensions?
>
> E.g. I'
Chris Lamb wrote:
> I can hack together quick things like:
I just noticed that UDD has lintian results, so you can just write
this as:
(Spoilers: I'm not a SQL programmer)
SELECT source, CASE (SELECT COUNT(*) FROM lintian
WHERE package = source AND package_type = 'source' AND
tag = 'te
On 2018-05-04 at 12:22, Emilio Pozuelo Monfort wrote:
> On 04/05/18 17:42, W. Martin Borgert wrote:
>> How will we deal with breaking extensions?
>>
>> E.g. I'm using xul-ext-scrapbook a lot. AFAIK, upstream does not
>> provide a post-XUL version. Probably other extensions will face the
>> same
Hi,
Am 04.05.18 um 18:38 schrieb The Wanderer:
...
>> I guess so, yes. There's not much we can do if there is no support
>> for newer versions.
>
> Though please do take note of other applications which may still work
> with them.
>
> Even leaving other Mozilla-based browsers aside, ISTR there b
W. Martin Borgert schrieb:
> Quoting Moritz Mühlenhoff :
>> Julien Cristau schrieb:
>>> I expect nothing much different from previous ESR cycles: stretch will
>>> move to 60 after 52 goes EOL in September.
>>
>> Exactly.
>
> How will we deal with breaking extensions?
Same as all previous extensi
On 2018-05-04 21:12, Moritz Mühlenhoff wrote:
> Same as all previous extension breakages incurred by ESR transitions;
> not at all. Apart from enigmail those are all not updated along
> in stable, this doesn't scale at all. If you want your extensions
> to be kept compatible, get them from the Mozi
On Fri, May 04, 2018 at 10:52:26PM +0200, W. Martin Borgert wrote:
> On 2018-05-04 21:12, Moritz Mühlenhoff wrote:
> > Same as all previous extension breakages incurred by ESR transitions;
> Why?
because this is what the modern web has become in 2018. go gopher go!
--
cheers,
Holger, SC
W. Martin Borgert schrieb:
> On 2018-05-04 21:12, Moritz Mühlenhoff wrote:
>> Same as all previous extension breakages incurred by ESR transitions;
>> not at all. Apart from enigmail those are all not updated along
>> in stable, this doesn't scale at all. If you want your extensions
>> to be kept
> On May 4, 2018, at 6:22 AM, Guillem Jover wrote:
>
> Hi!
>
> On Fri, 2018-04-27 at 07:02:12 +0200, Guillem Jover wrote:
>> The following is a quick run-down of the items from [F], not all
>> being important from Debian's perspective, but being for dpkg's:
>
>> * License: Permissive (dual BSD
On Fri, 2018-05-04 at 23:16 +0200, Mattia Rizzolo wrote:
> Yavor,
>
> On Fri, May 04, 2018 at 04:06:05PM +0300, Yavor Doganov wrote:
> > Andreas Tille wrote:
> > > What's the correct way to fix the symbols file to work with both
> > > versions of gcc?
> Guess what, C++ is more complex than C.
So
Hello,
On Fri, May 04 2018, Moritz Mühlenhoff wrote:
> Same as all previous extension breakages incurred by ESR transitions;
> not at all. Apart from enigmail those are all not updated along in
> stable, this doesn't scale at all. If you want your extensions to be
> kept compatible, get them from
On Fr, Mai 04, 2018 at 09:12:39 +0200, Moritz Mühlenhoff wrote:
Same as all previous extension breakages incurred by ESR transitions;
not at all. Apart from enigmail those are all not updated along
in stable, this doesn't scale at all. If you want your extensions
to be kept compatible, get them f
❦ 4 mai 2018 23:22 +0200, Moritz Mühlenhoff :
>> Why? We have now a huge breakage for all XUL extensions, but
>> were there problems of a similar scale before? Do we have to
>> expect similar breakages in the future with the new API?
>
> Sure, plenty of addons needed updates to remain compatibl
29 matches
Mail list logo
