Your message dated Sun, 16 Jun 2024 16:46:37 +0200
with message-id <141a85f2-0764-4b89-9231-6c71fed22...@debian.org>
and subject line Re: silxs autopkgtest
has caused the Debian Bug report #980088,
regarding britney adds reference link for removed packages
to be marked as done.
This
Your message dated Sun, 16 Jun 2024 15:40:44 +0200
with message-id <0fd3fa3b-f126-4e19-be09-f6f956602...@debian.org>
and subject line Re: britney-tests-live-data/live-2012-05-09 fails randomly
has caused the Debian Bug report #803633,
regarding britney-tests-live-data/live-2012-05-09
Your message dated Tue, 19 Mar 2024 20:34:38 +0100
with message-id
and subject line Re: Bug#1064428: [Britney] does not migrate new arch:all
packages after initial migration of same source
has caused the Debian Bug report #1064428,
regarding [Britney] does not migrate new arch:all packages after
- If any binary being taken over is arch-dependent, britney declares the
binary from the taking-over source "cruft" in the taken-over source's verdict.
If cruft is allowed, the binNMU migrates. If cruft is not allowed, the binNMU
is blocked.
I hope this helps. Thanks for taking a look!
. That
difference in behavior is what I really wanted to raise, but preventing Britney
from being in this situation at all in Debian might be an acceptable path for
Debian.
I think that with further discussion, we're not whether it's advisable to
delete the section of `'_should_upgrade_srcarch
/me is drinking coffee now *and* looking at test bug-709460
On 29-02-2024 8:43 a.m., Paul Gevers wrote:
but I exposed it in the bug-709460 test
case while trying to enable britney to check architecture-independent
packages. Currently the behavior is masked in that case because britney
skips
sed it in the bug-709460 test
case while trying to enable britney to check architecture-independent
packages. Currently the behavior is masked in that case because britney
skips the -doc package due to it being arch-indep. If this _is_ expected
behavior, bug-709460 is currently passing erroneously.
Wh
src:pkga while src:pkgb is blocked, but I
think it's a niche case that is acceptable to not support. What would be
bad is if bin:takeover from src:pkgb migrates without src:pkgb (bug 709460).
but I exposed it in the bug-709460 test
case while trying to enable britney to check architecture
ge entirely.
On Wed, Feb 21, 2024, at 11:59 PM, Paul Gevers wrote:
> On 21-02-2024 23:50, Dalton Durst wrote:
>
> > If the
> > package were binNMU'd, though, britney would migrate everything
> > including the arch:all package if it passed checks.
>
> In Debian, binNMU-in
that
that's ok, but the hint is obviously wrong in that case.
If the
package were binNMU'd, though, britney would migrate everything
including the arch:all package if it passed checks.
In Debian, binNMU-ing a arch:all package is known to not work. I don't
know if this bug is the reason why it doesn't
Package: release.debian.org
Severity: normal
Usertags: britney
Consider the following situation:
test-src migrated after its amd64 and i386 binaries appeared. It also
has architecture-independent binaries that miraculously only showed up
after migration was complete (maybe someone hinted through
Package: release.debian.org
Severity: normal
Usertags: britney
Consider the following situation:
* pkga produces takeover and pkga1
- it is already in testing
* pkgb is taking over takeover and also produces pkgb1
- it is not a candidate for migration because it is missing a build
arding release.debian.org: britney thinks ghostscript B-D on libz-dev:native
is unsatisfiable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the p
Your message dated Thu, 4 Jan 2024 16:33:53 +0100
with message-id
and subject line Re: Bug#693068: release.debian.org: arch-specific dependency
should invalidate arch-specific candidate
has caused the Debian Bug report #696680,
regarding [britney] excuses should be clearer for arch-specific
-team/britney2/-/commit/2fd6c59460c0e78bb50a34938dbc05637abf27b2
Currently I'm seeing it also/instead being unreproducible.
This remains. I have now 10 different possible end states of britney.
I'm trying to add sorted() to a bunch of for loops on sets. It seems I'm
able to make it more
Hi,
On Sun, 01 Nov 2015 10:42:49 +0100 Emilio Pozuelo Monfort
wrote:
If run in a loop, live-2012-05-09 will eventually fail with:
AssertionError: NUNINST OUT OF SYNC
The problem is with hurd-i386 (fucked/break arch in this test) and I've
seen problems such as:
E: [Sun Nov 1 10:31:41 2015]
Hi release managers,
A few days ago sioyek was uploaded to unstable. It builds on all architectures
where its dependencies are available according to buildd. However, its
migration to testing is blocked because britney seems to think that
sphinx:native is not satisfiable on any architecture
best to switch to B-D
python3-spinx:native or accept that your package can't be cross-build
for now (and drop the :native), until britney is fixed.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
Hi release managers,
A few days ago sioyek was uploaded to unstable. It builds on all
architectures where its dependencies are available according to buildd.
However, its migration to testing is blocked because britney seems to
think that sphinx:native is not satisfiable on any architecture
Your message dated Sat, 8 Oct 2022 22:04:06 +0200
with message-id <455de46d-3f7b-4a7e-9745-ea63fd9e1...@debian.org>
and subject line Re: dak: Crash with RecursionError: maximum recursion depth
exceeded
has caused the Debian Bug report #1010660,
regarding britney: Crash with Recursio
Hi,
tl;dr: we need to cook up a similar patch as
bd375fdd85b4e00b89fb087760369bb6f3df0a20 for the migration phase of britney.
We recently experienced this problem in Debian too.
Traceback (most recent call last):
File "/srv/release.debian.org/britney/code/b2/britney.py",
On 09 juin 2022 10:30, Paul Gevers wrote:
> Hi Christian,
Hi paul,
[...]
>>> RecursionError: maximum recursion depth exceeded
>
> Seems like Ubuntu also ran into the issue and (temporarily) applied
> https://git.launchpad.net/~ubuntu-release/britney/+git/britn
Hi Christian,
On Fri, 2022-05-06 at 12:41 +0200, Christian Marillat wrote:
I'm using britney (last commit normally)
2ccce826090ebc3f2cbdb26df3c5b0817f7a7cc2
You can download data used for this crash here :
https://www.deb-multimedia.org/tests/britney-2022-05-06.tar.xz
Since may 2, 2022 I
Processing control commands:
> reassign -1 release.debian.org
Bug #1010660 {Done: Christian Marillat }
[release.debian.org] britney: Crash with RecursionError:
Ignoring request to reassign bug #1010660 to the same package
> retitle -1 britney: Crash with RecursionError: maximum recursion
Control: reassign -1 release.debian.org
Control: retitle -1 britney: Crash with RecursionError: maximum recursion depth
exceeded
On Fri, 2022-05-06 at 12:41 +0200, Christian Marillat wrote:
> I'm using britney (last commit normally)
> 2ccce826090ebc3f2cbdb26df3c5b0817f7a7cc2
britney is no
Am Sun, May 22, 2022 at 07:43:35PM +0530 schrieb Nilesh Patra:
> >I've just commited a patch thet ignores the not yet packaged test
> >dependency which causes the test failure. In any case r-bioc-scater
>
> Then please make an upload.
On 22 May 2022 7:05:18 pm IST, Andreas Tille wrote:
>Hi Graham,
>
>Am Sun, May 22, 2022 at 09:09:01AM +0200 schrieb Graham Inggs:
>> It looks like the only blocker now is waiting for r-bioc-scater [1] to age:
>>
>> Too young, only 2 of 5 days old
>>
>> It doesn't get 2-day migration because
Hi Graham,
Am Sun, May 22, 2022 at 09:09:01AM +0200 schrieb Graham Inggs:
> It looks like the only blocker now is waiting for r-bioc-scater [1] to age:
>
> Too young, only 2 of 5 days old
>
> It doesn't get 2-day migration because its autopkgtest regressed in
> testing, sometime around
Hi Nilesh
It looks like the only blocker now is waiting for r-bioc-scater [1] to age:
Too young, only 2 of 5 days old
It doesn't get 2-day migration because its autopkgtest regressed in
testing, sometime around 2021-09-23 [2].
I'll file a separate bug for that.
Regards
Graham
[1]
Hi Nilesh
On Sat, 21 May 2022 at 07:03, Nilesh Patra wrote:
It looks like britney has already figured these out:
> r-bioc-annotationdbiset ignore for r-bioc-annotationhub (version in
> unstable passes)
> r-bioc-scran/beachmat Please run tests with new version of bio
Hi Graham,
I did some work to cleanup the rest stuff meanwhile, and need
your help to ignore some of the CI temporarily to complete the migration; and
also because unstable counterparts pass.
I have pasted a list at the end of this email, please see to it.
--
Best,
Nilesh
Package
Hi Paul,
Am Thu, May 19, 2022 at 01:07:59PM +0200 schrieb Paul Gevers:
> @tille, removals are work for *us*, they are not free lunch. Please fix the
> package that prevent migration.
There is no clean fix. The packages featuring r-bioc-api-3.15 just need
some new predependencies. These are
On 19 May 2022 2:25:23 pm IST, Andreas Tille wrote:
>Am Thu, May 19, 2022 at 01:41:12PM +0530 schrieb Nilesh Patra:
>>
>> I think we can workaround these anyway by editing the DESCRIPTION file --
>> maybe I'll do so and upload either late in the night today or early morning
>> Tom.
>
>I do
Hi,
On 19-05-2022 10:55, Andreas Tille wrote:
Am Thu, May 19, 2022 at 01:41:12PM +0530 schrieb Nilesh Patra:
I think we can workaround these anyway by editing the DESCRIPTION file -- maybe
I'll do so and upload either late in the night today or early morning Tom.
I do not think that editing
Hi Nilesh,
Am Thu, May 19, 2022 at 01:41:12PM +0530 schrieb Nilesh Patra:
>
> I think we can workaround these anyway by editing the DESCRIPTION file --
> maybe I'll do so and upload either late in the night today or early morning
> Tom.
I do not think that editing DESCRIPTION is the prefered
Am Thu, May 19, 2022 at 09:40:23AM +0200 schrieb Paul Gevers:
> Package: release.debian.org
> User: release.debian@packages.debian.org
> Usertag: britney
>
> Hi,
>
> On 11-05-2022 12:34, Graham Inggs wrote:
> > Yes, please go ahead.
> >
> > Tracke
Hi,
On 19 May 2022 1:10:23 pm IST, Paul Gevers wrote:
>Package: release.debian.org
>User: release.debian@packages.debian.org
>Usertag: britney
>
>Hi,
>
>On 11-05-2022 12:34, Graham Inggs wrote:
>> Yes, please go ahead.
>>
>> Tracker is at:
>>
Hi
On Thu, 19 May 2022 at 09:45, Paul Gevers wrote:
> There's three package still waiting for an upload, r-bioc-progeny,
> r-bioc-monocle and r-bioc-scater. When is the ETA for those?
In addition, there is r-bioc-grohmm which I happened to notice dropped
off the tracker during the transition.
Package: release.debian.org
User: release.debian@packages.debian.org
Usertag: britney
Hi,
On 11-05-2022 12:34, Graham Inggs wrote:
Yes, please go ahead.
Tracker is at:
https://release.debian.org/transitions/html/r-api-bioc-3.15.html
There's three package still waiting for an upload, r
Your message dated Thu, 19 May 2022 09:29:10 +0200
with message-id <878rqygeux.fsf...@christian.marillat.net>
and subject line Re: Bug#1010660: Acknowledgement (britney: Crash with
RecursionError: maximum recursion depth exceeded)
has caused the Debian Bug report #1010660,
regarding b
Hi,
On 09-01-2022 20:39, Paul Gevers wrote:
Hi Peter,
On 09-01-2022 13:41, Peter Michael Green wrote:
https://tracker.debian.org/pkg/rust-gtk says "Rejected due to piuparts
regression - https://piuparts.debian.org/sid/source/r/rust-gtk.html;
but when I follow that link it says
Hi Peter,
On 09-01-2022 13:41, Peter Michael Green wrote:
https://tracker.debian.org/pkg/rust-gtk says "Rejected due to piuparts
regression - https://piuparts.debian.org/sid/source/r/rust-gtk.html; but
when I follow that link it says "successfully-tested 0.14.3-1". This has
been the case for
https://tracker.debian.org/pkg/rust-gtk says "Rejected due to piuparts
regression - https://piuparts.debian.org/sid/source/r/rust-gtk.html; but
when I follow that link it says "successfully-tested 0.14.3-1". This has
been the case for several days so it doesn't appear to be a transient
issue
Hi,
Just for documenting purposes (I may look into this soon), I reported
this two weeks ago in bug #1000972.
"""
ruby-jaeger-client is on my radar because it doesn't migrate for a
long time. I was very puzzled by the output of britney:
> ruby-jaeger-client/amd64 has unsati
Your message dated Thu, 9 Dec 2021 21:26:00 +0100
with message-id
and subject line Re: britney doesn't properly reschedule migration-reference/0
runs anymore
has caused the Debian Bug report #982401,
regarding britney doesn't properly reschedule migration-reference/0 runs anymore
to be marked
Your message dated Thu, 9 Dec 2021 21:13:56 +0100
with message-id <584feddb-1d29-95d4-eaf2-058c8cd00...@debian.org>
and subject line Re: Bug#973277: tracker.debian.org: Please provide the
relevant links to debcheck
has caused the Debian Bug report #973277,
regarding britney should in
Your message dated Thu, 15 Apr 2021 14:55:18 +0200
with message-id <27d837dd-4aed-9a9b-870e-cb62206e4...@debian.org>
and subject line Re: britney: add ALWAYSFAIL autopkgtest results to excuses for
ones own package
has caused the Debian Bug report #908726,
regarding britney: add ALWA
Package: release.debian.org
X-Debbugs-CC: hert...@debian.org
User: release.debian@packages.debian.org
Usertags: britney
Hi myself,
I believe that since the patch to remember results for a particular
trigger from older versions of the reverse dependency britney2 doesn't
properly refreshes
Hi,
On 21-01-2021 02:23, Paul Wise wrote:
>> Passing packages that are still shown are those where an update
>> happened since the successful run, so they are more or less
>> "pending". I realize that probably nobody realizes this.
>
> It is very non-obvious from the output, I'd suggest putting
On Wed, 2021-01-20 at 19:26 +0100, Paul Gevers wrote:
> Passing packages that are still shown are those where an update
> happened since the successful run, so they are more or less
> "pending". I realize that probably nobody realizes this.
It is very non-obvious from the output, I'd suggest
Hi Paul
On 20-01-2021 06:26, Paul Wise wrote:
> The excuses page is often very verbose because of the autopkgtest
> results, especially for packages with lots of reverse dependencies.
>
> For packages where all the results are Pass, those packages could be
> left out of the excuses altogether,
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: britney
The excuses page is often very verbose because of the autopkgtest
results, especially for packages with lots of reverse dependencies.
For packages where all the results are Pass, those
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: britney
Severity: normal
Britney should avoid testing old autopkg when the source package is
renamed and the new package takes over all binary packages.
This bug is a reminder to look into this behaviour
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: britney
trying: golang-github-spf13-cobra
skipped: golang-github-spf13-cobra (2, 17, 1)
got: 31+0: a-14:a-0:a-0:a-0:i-16:m-0:m-0:p-0:s-1
* amd64: golang-etcd-server-dev, golang-github
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: britney
The excuses on <https://tracker.debian.org/pkg/ghostscript> say:
* ghostscript unsatisfiable Build-Depends(-Arch) on amd64: libz-dev:native
* ghostscript unsatisfiable Build-Depends
Your message dated Thu, 23 Jul 2020 13:33:33 +
with message-id <1595507670047.69...@mnec.gr>
and subject line Microsoft Account team.
has caused the Debian Bug report #145257,
regarding [britney] migrations can break build-depends
to be marked as done.
This means that you
Your message dated Thu, 23 Jul 2020 13:33:33 +
with message-id <1595507670047.69...@mnec.gr>
and subject line Microsoft Account team.
has caused the Debian Bug report #145257,
regarding [britney] migrations can break build-depends
to be marked as done.
This means that you
Your message dated Thu, 23 Jul 2020 13:33:33 +
with message-id <1595507670047.69...@mnec.gr>
and subject line Microsoft Account team.
has caused the Debian Bug report #145257,
regarding [britney] migrations can break build-depends
to be marked as done.
This means that you
Your message dated Thu, 23 Jul 2020 13:33:33 +
with message-id <1595507670047.69...@mnec.gr>
and subject line Microsoft Account team.
has caused the Debian Bug report #145257,
regarding [britney] migrations can break build-depends
to be marked as done.
This means that you
Your message dated Fri, 14 Feb 2020 21:01:30 +0100
with message-id
and subject line Re: britney: blocks arch:all packages on non-installability on
CI archs
has caused the Debian Bug report #918620,
regarding britney: blocks arch:all packages on non-installability on CI archs
to be marked as done
Your message dated Thu, 6 Feb 2020 12:54:47 +0100
with message-id <20200206115444.ga4...@debian.org>
and subject line Re: britney crashes when trying removal multiple times
has caused the Debian Bug report #945471,
regarding britney crashes when trying removal multiple times
to be marked a
Paul Gevers:
> Control: tags -1 patch
> Control: forwarded -1
> https://salsa.debian.org/release-team/britney2/compare/31e32782...c9e8751c
>
> Hi all
>
> On 28-11-2019 10:28, Paul Gevers wrote:
>> With the addition of arm64 as a CI architecture, the situation got
>> worse. E.g.
Control: tags -1 patch
Control: forwarded -1
https://salsa.debian.org/release-team/britney2/compare/31e32782...c9e8751c
Hi all
On 28-11-2019 10:28, Paul Gevers wrote:
> With the addition of arm64 as a CI architecture, the situation got
> worse. E.g.
Processing control commands:
> tags -1 patch
Bug #918620 [release.debian.org] britney: blocks arch:all packages on
non-installability on CI archs
Added tag(s) patch.
> forwarded -1
Unknown command or malformed arguments to command.
--
918620: https://bugs.debian.org/cgi-bin/bugreport.c
On Mon, Nov 25, 2019 at 03:21:47PM +0100, Ivo De Decker wrote:
> The root cause is that items that migrate due to the easy hint, are tried
> again during the main run. This started with commit
> 6174d2c3f9590eba90f9c6dd613a553edd3a80e6
>
> After this commit, the 'selected' items are no longer
Processing commands for cont...@bugs.debian.org:
> retitle 918620 britney: blocks arch:all packages on non-installability on CI
> archs
Bug #918620 [release.debian.org] console-setup: autopkgtest delayed due to
binary-all package not installable on amd64
Changed Bug title to 'britney:
Processing control commands:
> owner -1 !
Bug #918620 [release.debian.org] console-setup: autopkgtest delayed due to
binary-all package not installable on amd64
Owner recorded as Paul Gevers .
> affects -1 src:q2-demux
Bug #918620 [release.debian.org] console-setup: autopkgtest delayed due to
Control: owner -1 !
Control: affects -1 src:q2-demux
On Mon, 07 Jan 2019 21:42:20 +0200 Adrian Bunk wrote:
> https://tracker.debian.org/pkg/console-setup
>
> console-setup-freebsd/amd64 unsatisfiable Depends: vidcontrol
> console-setup-freebsd/amd64 unsatisfiable Depends: kbdcontrol
>
Package: release.debian.org
Severity: serious
User: release.debian@packages.debian.org
Usertags: britney
Hi,
When a removal is done during an easy hint, the removal is tried again
afterwards, causing a crash.
There is a testcase for this in the testsuite (test takeover-removal-easy
Your message dated Wed, 13 Nov 2019 20:59:00 +
with message-id <4e1708e6-9e55-9883-601f-3ac328666...@thykier.net>
and subject line Re: Bug#944190: release.debian.org: Allow britney to consider
installability of dependencies of essential packages
has caused the Debian Bug report #
Niels,
Thanks for working on this so swiftly.
On Sun, Nov 10, 2019 at 11:25:00PM +, Niels Thykier wrote:
> I have attached the following patch that passes the provided test and
> (AFAICT) does what we want. Please feel free to review it; I will come
> back to this in a few days.
I have
supposed to happen is that:
>
> * Britney "should" rewrite the relation on "libsystemd0" as
>"libsystemd0 | libelogin0" when building the BinaryPackageUniverse
>(actually as libsystemd0//arch | libsystemd0//arch
> tuples).
>
>- This is
Processing control commands:
> tags -1 confirmed patch
Bug #944190 [release.debian.org] release.debian.org: Allow britney to consider
installability of dependencies of essential packages
Added tag(s) confirmed.
--
944190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944190
Debian
it. I hope it is helpful
and I have not missed something.
> What is supposed to happen is that:
>
> * Britney "should" rewrite the relation on "libsystemd0" as
>"libsystemd0 | libelogin0" when building the BinaryPackageUniverse
>(actually as
Package: release.debian.org
Severity: important
User: release.debian@packages.debian.org
Usertags: britney
britney doesn't run autopkg tests for binNMUs. E.g. for a library transition,
britney only runs the tests triggered by the library package, it doesn't run the
autopkg tests for all
do not inadvertently regress on this area when
>> refactoring code.
>
> I will happily look at that. I am busy until Sunday, but will look at it
> then.
>
> Many thanks.
>
> Mark
>
I looking forward to your test case as it will make this issue a lot
easier to deb
Neils,
On Fri, Nov 08, 2019 at 07:03:00AM +, Niels Thykier wrote:
> Hi Mark
>
> Thanks for the investigative work and the patch.
>
> I have not had time to review the patch yet in details and hope to have
> a look this weekend.
Thanks.
> Could I convince you to add a small test case for
Hi Mark
Thanks for the investigative work and the patch.
I have not had time to review the patch yet in details and hope to have
a look this weekend.
Could I convince you to add a small test case for this problem to our
britney2-tests repo (https://salsa.debian.org/debian/britney2-tests)
that
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: britney
Tags: patch
Dear Release Team,
Whilst investigating why britney has not migrated src:elogind 241.3-1+debian1 to
bullseye, I discovered that the negative dependencies of the dependencies
Your message dated Wed, 23 Oct 2019 19:34:00 +
with message-id <89d8512b-b9d0-175e-c18e-fbe55a6e4...@thykier.net>
and subject line Re: Bug#942104: release.debian.org: Will fail if "Suite" field
is missing
has caused the Debian Bug report #942104,
regarding britney: fails
Processing commands for cont...@bugs.debian.org:
> retitle 942104 britney: fails if Release file missing "Suite" field
Bug #942104 [release.debian.org] release.debian.org: Will fail if "Suite" field
is missing
Changed Bug title to 'britney: fails if Release file missi
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: britney
Hi Eriberto,
Thanks for talking about the issues you have, I could not have guessed.
On 10-09-2019 17:53, Eriberto Mota wrote:
> I was using a test over a DKMS package (lime-forensics). I removed
&g
Some recent bugs that seem to have been caused by this:
#898245 src:flask-limiter-> python-aniso8601
#932507 src:python-crontab-> python-croniter
#932509 src:pyrsample-> python-xarray
Your message dated Thu, 7 Mar 2019 21:26:58 +0100
with message-id <3d832409-b18d-0186-55dc-91e3e6b0b...@debian.org>
and subject line Re: ftp.debian.org: britney doesn't ensure main being
self-contained
has caused the Debian Bug report #219978,
regarding [britney] main being self-con
Processing commands for cont...@bugs.debian.org:
> retitle 145257 [britney] build-depends not taken into consideration for
> arch:all packages
Bug #145257 [release.debian.org] [britney] build-depends not taken into
consideration
Bug #184812 [release.debian.org] [britney] dephelper v
Your message dated Mon, 25 Feb 2019 20:31:00 +
with message-id
and subject line Re: Britney crashes in _compute_groups when attempting
migration
has caused the Debian Bug report #901248,
regarding Britney crashes in _compute_groups when attempting migration
to be marked as done.
This means
-schema-validator/2.3.1-3 (in unstable and testing)
Britney is using RC bugs to determine if package may migrate from
unstable to testing. If an RC bug is only in unstable and not in
testing, the package is not allowed to migrate. However, in the above
case simplejson is listed in both
https
package: piuparts.debian.org
severity: wishlist
x-debbugs-cc: debian-release@lists.debian.org,
piuparts-de...@lists.alioth.debian.org
Hi Ivo & Niels,
On Sat, Jan 19, 2019 at 06:34:19PM +0100, Ivo De Decker wrote:
> > > > currently britney uses piuparts regressions comparing
Beckmann wrote:
currently britney uses piuparts regressions comparing testing vs. sid to
block migrations. That's fine, since we should have few false positives
in sid nowadays.
It would be nice if we could use a similar scheme like autopkgtests uses
to delay migration for other tests, like sid-strict
Holger Levsen:
> Hi,
>
> Andreas sent this to the piuparts-devel list while I think it's more
> appropriate to discuss this on debian-release@
>
Hi Holger,
Thanks for forwarding this idea. :)
> On Thu, Jan 10, 2019 at 02:38:38PM +0100, Andreas Beckmann wrote:
>>
Hi,
Andreas sent this to the piuparts-devel list while I think it's more
appropriate to discuss this on debian-release@
On Thu, Jan 10, 2019 at 02:38:38PM +0100, Andreas Beckmann wrote:
> currently britney uses piuparts regressions comparing testing vs. sid to
> block migrations. That'
Iain Lane:
> Hey Niels,
>
> Thanks for the mail!
>
Hi Iain,
Thanks for your reply. :)
> On Sun, Dec 30, 2018 at 07:13:00PM +, Niels Thykier wrote:
>> Otherwise, check your britney configuration. If the path set for the
>> "TESTING" configur
Hi Niela!
Am So., 30. Dez. 2018 um 20:19 Uhr schrieb Niels Thykier :
>
> Hi,
>
> I am writing to you, because I know that you are (or have been) involved
> in setting up or maintaining a britney instance for a Debian derivative.
> If you are no longer involving please let me k
Hey Niels,
Thanks for the mail!
On Sun, Dec 30, 2018 at 07:13:00PM +, Niels Thykier wrote:
> Otherwise, check your britney configuration. If the path set for the
> "TESTING" configuration points to a standard APT mirror (with a Release
> file) you are unaffected by this m
Your message dated Sat, 5 Jan 2019 14:35:14 +0100
with message-id <20190105133511.juc74w5ghu4fz...@debian.org>
and subject line Re: britney: handling of binNMUs in tpu broken
has caused the Debian Bug report #916209,
regarding britney: handling of binNMUs in tpu broken
to be marked a
Hi Niels,
On Sun, 30 Dec 2018, Niels Thykier wrote:
> We are considering to deprecate the "legacy package layout" and remove
> the "--control-files" option.
In Kali we are using neither of those features.
http://git.kali.org/gitweb/?p=britney2.git has our brit
Hi,
I am writing to you, because I know that you are (or have been) involved
in setting up or maintaining a britney instance for a Debian derivative.
If you are no longer involving please let me know who to contact
instead (where applicable).
We are considering to deprecate the "legacy pa
Package: release.debian.org
Severity: serious
User: release.debian@packages.debian.org
Usertags: britney
When {testing,stable}-proposed-updates has a binary-only item (binNMU or
missing build that arrived later), britney will use the binaries from unstable
instead, possibly migrating them
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: britney
Severity: wishlist
Owner: elb...@debian.org
Hi Raphael,
On 13-09-18 09:15, Raphael Hertzog wrote:
> On Wed, 12 Sep 2018, Paul Gevers wrote:
>> Hi
>>
>> On 12-09-18 18:35, Niels
On Sun, 19 Jul 2015 18:38:38 +0200 Niels Thykier wrote:
> This bug is a reminder to look into this and patch Britney as
> necessary to handle this situation correctly (or document why the
> current practise is correct, if this is the case).
It seems that at least the autopkg
1 - 100 of 380 matches
Mail list logo
