Source: spaln
Version: 2.4.13f+dfsg-1
Severity: serious
Control: close -1 3.0.2+dfsg-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more
Source: mathgl
Version: 8.0.1-4
Severity: serious
Control: close -1 8.0.1-5
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1063599
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable
Source: plplot
Version: 5.15.0+dfsg2-6
Severity: serious
Control: close -1 5.15.0+dfsg2-7+deb13u1
X-Debbugs-CC: debian-m...@lists.debian.org
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are
Hi,
With debugging on (-ddd to autopkgtest and -d to autopkgtest-virt-qemu):
Unpacking libc6:amd64 (2.37-15~deb13u1) over (2.37-14) ...
Setting up libc6:amd64 (2.37-15~deb13u1) ...
autopkgtest: DBG: timed out on ['/tmp/autopkgtest-qemu.r683hlu9/runcmd']
['su', '-s', '/bin/bash', 'debci', '-c',
Hi,
Currently the autopkgtest of autopkgtest is in a very sad state on amd64
on ci.d.n because of podman-init. The test times out after:
5171s Preparing to unpack .../libc6_2.37-14_amd64.deb ...
5171s Unpacking libc6:amd64 (2.37-14) over (2.37-13) ...
5171s Setting up libc6:amd64 (2.37-14)
Package: ubuntu-dev-tools
Version: 0.199
Severity: normal
File: /usr/bin/reverse-depends
On IRC the request came on how src:zfs-linux Build-Depends on afflib,
hfsplus, so I thew it at $(reverse-depends). (Well, my query was in the
wrong direction but the problem still stands). reverse-depends
Source: 389-ds-base
Version: 2.3.4+dfsg1-1.1
Severity: serious
Control: close -1 2.4.4+dfsg1-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for
Source: gjs
Version: 1.78.1-3
Severity: serious
Control: close -1 1.78.3-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days
Source: linux-apfs-rw
Version: 0.3.5-1
Severity: serious
Control: close -1 0.3.7-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1060898
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and
Source: r-cran-future.apply
Version: 1.11.0+dfsg-1
Severity: serious
Control: close -1 1.11.1+dfsg-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for
Source: seqan-needle
Version: 1.0.2+ds-1
Severity: serious
Control: close -1 1.0.2+ds-2
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more
Source: node-websocket
Version: 1.0.34+~cs10.0.25-1
Severity: serious
Control: close -1 1.0.34+~cs10.0.25-2
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and
Source: iwyu
Version: 8.18-2
Severity: serious
Control: close -1 8.21-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as having
Source: nng
Version: 1.6.0-1
Severity: serious
Control: close -1 1.7.2-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as
Source: rust-gdk-pixbuf-sys
Version: 0.18.0-2
Severity: serious
Control: close -1 0.18.0-3
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than
Source: syncthing
Version: 1.19.2~ds1-3
Severity: serious
Control: close -1 1.27.2~ds4-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than
Source: python-cryptography
Version: 41.0.7-2
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't
Source: nvidia-cuda-samples
Version: 12.1~dfsg-1
Severity: serious
X-Debbugs-CC: li...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:linux
Dear maintainer(s),
With a recent upload of linux the autopkgtest of
Source: nvidia-graphics-drivers
Version: 525.147.05-5
Severity: serious
X-Debbugs-CC: li...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:linux
Dear maintainer(s),
With a recent upload of linux the autopkgtest of
Source: nvidia-graphics-drivers-tesla
Version: 525.147.05-5
Severity: serious
X-Debbugs-CC: li...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:linux
Dear maintainer(s),
With a recent upload of linux the autopkgtest of
Source: nvidia-graphics-drivers-tesla-470
Version: 470.223.02-3
Severity: serious
X-Debbugs-CC: li...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:linux
Dear maintainer(s),
With a recent upload of linux the autopkgtest of
Source: asciiart
Version: 0.0.10-2
Severity: serious
Control: close -1 0.3.0-1
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30
Source: libfreemarker-java
Version: 2.3.31-2
Severity: serious
Control: close -1 2.3.32-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1060940
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
Source: phosh-osk-stub
Version: 0.34.0-1
Severity: serious
Control: close -1 0.36.0-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30
Source: ruby-google-cloud-core
Version: 1.2.0-2
Severity: serious
Control: close -1 1.6.1-1
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for
Source: olive-editor
Version: 20221024+ds-1
Severity: serious
Control: close -1 20230614+ds-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1060206
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between
Source: ruby-semver-dialects
Version: 1.2.1-2
Severity: serious
Control: close -1 1.5.0-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than
Control: reassign -1 src:lfortran 0.36
Mea culpa, I made a mistake in calling my tools and filed the issue
against the wrong package.
On Sun, 4 Feb 2024 19:59:33 +0100 Paul Gevers wrote:
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
You
Source: dh-fortran-mod
Version: 0.37
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
You recently added an autopkgtest to your package dh-fortran-mod, great.
However, it fails. Currently this failure is blocking the migration to
testing [1]. Can
Source: mumble
Version: 1.3.4-4
Severity: serious
Control: close -1 1.5.517-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as
Source: yt-dlp
Version: 2023.11.16-1
Severity: serious
Control: close -1 2023.12.30-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30
Source: ruby-re2
Version: 1.7.0-1
Severity: serious
Control: close -1 2.7.0-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30
Source: python-watchgod
Version: 0.8.2-2
Severity: serious
X-Debbugs-CC: python-an...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python-anyio
Dear maintainer(s),
[I note that python-watchgod has been requested for
Source: orthanc-python
Version: 4.1+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of your package. I noticed
that it regularly fails on several architectures because it currently
blocks glibc.
Source: editorconfig-core
Version: 0.12.6-0.1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of your package. I noticed
that it regularly fails on ci.d.n infrastructure on at least amd64,
armel and armhf. In
Source: libproxy
Version: 0.4.18-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package has an autopkgtest, great. However, it recently started
to fail in testing. The last version dropped python3-libproxy as a
binary, but the test still
Source: adios2
Version: 2.9.2+dfsg1-8
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of your package. I noticed
that it regularly fails. The failures seem related to the host that runs
the test. ci-worker13 is
Source: obs-studio
Version: 29.1.3+dfsg-2
Severity: serious
Control: close -1 30.0.2+dfsg-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1061420
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between
Source: graph-tool
Version: 2.58+ds-1
Severity: serious
Control: close -1 2.59+ds-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1060786
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and
Source: fortunes-it
Version: 2.2-1
Severity: serious
Control: close -1 2.2-2
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30
Source: golang-github-hanwen-go-fuse
Version: 2.1.0+git20220822.58a7e14-1
Severity: serious
Control: close -1 2.4.2-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
Source: libtemplates-parser
Version: 23.0.0-3
Severity: serious
X-Debbugs-CC: gcc...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:gcc-12
Dear maintainer(s),
With a recent upload of gcc-12 the autopkgtest of
Source: libgnatcoll
Version: 23.0.0-3
Severity: serious
X-Debbugs-CC: gcc...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:gcc-12
Dear maintainer(s),
With a recent upload of gcc-12 the autopkgtest of libgnatcoll fails in
Hi,
On 27-01-2024 15:41, Paul Gevers wrote:
Indeed, autopkgtest doesn't look at d/control at all. Both
autopkgtest-pkg-python and autopkgtest-pkg-pybuild are things that
autodep8 deals with and it needs to do the right thing. Reassigning.
This seems to be problematic (note
Control: reassign -1 autodep8
Hi Jérémy,
On 27-01-2024 14:41, Jérémy Lal wrote:
Testsuite: autopkgtest-pkg-python, autopkgtest-pkg-pybuild
tests two different things, and having both is nice.
Ack.
However it seems autopkgtest doesn't consider the field can have multiple
values,
it only
Source: haskell-misfortune
Version: 0.1.2.1-3
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't
Source: roundcube
Version: 1.6.6+dfsg-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
Source: nanobind
Version: 1.8.0-3
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed
Source: stellarium
Version: 23.3-1
Severity: serious
Control: close -1 23.4-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as
Hi zeha,
On 26-01-2024 10:21, Chris Hofstaedtler wrote:
I see this "works", but now the tests fail after one try on the
problematic worker and then are never retried. Can this please be
fixed?
What do you have in mind? I think you need to wait until issue 166 [1]
is fixed, which I guess
Source: box64
Version: 0.2.4+dfsg-1
Severity: serious
Control: close -1 0.2.6+dfsg-2
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than
Source: pmacct
Version: 1.7.7-1
Severity: serious
Control: close -1 1.7.8-1
X-Debbugs-CC: Boyuan Yang
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable
Source: r-cran-ggally
Version: 2.1.2-2
Severity: serious
Control: close -1 2.2.0-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1059385
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and
Hi,
On 21-01-2024 21:06, julien.pu...@gmail.com wrote:
Would kicking the mathcomp-analysis package out of testing allow the
migration of the rest of the Coq-related packages and at least give a
coherent set there?
It seems src:mathcomp-analysis is a leaf package that can easily be
removed
Source: nitime
Version: 0.10.2-1
Severity: serious
Control: close -1 0.10.2-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as
Source: coq
Version: 8.17.0+dfsg-1
Severity: serious
Control: close -1 8.18.0+dfsg-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30
Hi Chris,
On 19-01-2024 23:00, Chris Lamb wrote:
Just to mention that I have been looking into this, but I am a little
stymied as it seems to work okay here. What is very curious is that
the directory listing works (ie. we can infer that zzuf, zzz-to-char,
zzzeeksphinx, etc. has been obtained
Source: pyocd
Version: 0.13.1+dfsg-3
Severity: serious
Control: close -1 0.36.0-1
X-Debbugs-CC: Alexandre Detiste
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
Source: gmsh
Version: 4.8.4+ds2-3
Severity: serious
Control: close -1 4.11.1+ds1-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days
Source: suitesparse, octave
Control: found -1 suitesparse/1:7.5.1+dfsg-1
Control: found -1 octave/8.4.0-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of suitesparse the autopkgtest of octave fails in
Source: rust-cargo-auditable
Version: 0.6.1-2
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency (or actually, the right version if I
Hi,
On 18-01-2024 05:50, Otto Kekäläinen wrote:
Hi oldstable release managers,
(I'm not one of them).
I got email after my upload 11 days ago that 10.5.23 was accepted in
oldstable-proposed-updates but I don't see any updates under 'News' at
https://tracker.debian.org/pkg/mariadb-10.5 yet.
Source: path.py
Version: 16.7.1-1
Severity: serious
Control: close -1 16.9.0-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as
Source: python-anyio
Version: 3.7.0-1
Severity: serious
Control: close -1 4.1.0-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days
Source: bpfcc
Version: 0.26.0+ds-1
Severity: serious
Control: close -1 0.29.1+ds-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than
Hi
On 14-01-2024 18:46, Guillem Jover wrote:
I think that would be great, I guess the message from the hook could
give some very basic and generic guidance, and point to this page for
more in-depth explanation of what to do, what else to check etc. But in
any case an initial version sounds
Hi,
On 14-01-2024 17:43, Guillem Jover wrote:
https://wiki.debian.org/Teams/ReleaseTeam/Transitions
but it looks like that one is targeted more to maintainers that start
or drive the transitions instead of someone that might upload a
package which is part or affected by that transition?
Hi Guillem
On 10-01-2024 02:23, Guillem Jover wrote:
I've had for a while a new hook for dupload that adds a transitions
check for Debian hosts, for sourceful uploads targeting unstable (to
avoid disrupting buildd or porter uploads, or uninteresting suites).
I've just finished polishing it, and
Source: rasdaemon
Version: 0.6.8-1.1
Severity: serious
Control: close -1 0.8.0-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1059484
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and
Source: i2pd
Version: 2.45.1-1
Severity: serious
Control: close -1 2.49.0-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as
Source: gitlab-shell
Version: 14.20.0+ds1-2
Severity: serious
Control: close -1 14.23.0+ds1-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more
Source: terminado
Version: 0.17.1-1
Severity: serious
Control: close -1 0.18.0-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days
Source: mesa
Version: 23.2.1-1
Severity: serious
Control: close -1 23.3.3-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1056116
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable
Source: django-filter
Version: 23.5-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertag: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting issues with your packages. Normally your build
dependencies shouldn't be removed from testing without removal all
Source: collectd
Version: 5.12.0-15
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertag: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting issues with your packages. Normally your build
dependencies shouldn't be removed from testing without removal all
Source: tmuxp
Version: 1.31.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of your package. I noticed
that it regularly fails. I'm seeing a pattern that it happens more often
on our amd64 host ci-worker13
Hurray,
On 13-01-2024 21:39, Debian Bug Tracking System wrote:
minicoredumper (2.0.7-3) unstable; urgency=medium
.
* Fix autopackage test due to stderr output (Closes: #1059553)
That worked. The test now passes nicely.
Thank you.
Paul
OpenPGP_signature.asc
Description: OpenPGP
Hi Abou,
On 12-01-2024 22:44, Abou Al Montacir wrote:
Well, maybe I just didn't spot this issue before. But because of the
/usr-merged work of helmut, I'm much more aware of diversions so they'd
trigger me much more then they used to.
Makes sense, but I'm not sure I understand why diverted
Hi Abou,
On 11-01-2024 20:40, Abou Al Montacir wrote:
But this is the case of all lpk files where the binary package provide a
Manually compilable package while the source one provides a Compile As > Needed package file.
Don't we want them to be the same? Why do we even ship the files twice?
Hi,
On 12-01-2024 08:51, Debian Bug Tracking System wrote:
minicoredumper (2.0.7-2) unstable; urgency=medium
.
* Fix autopackage test due to missing dependency (Closes: #1059553)
https://ci.debian.net/data/autopkgtest/testing/amd64/m/minicoredumper/41783082/log.gz
40s Starting
Hi,
On 12-01-2024 12:36, Chris Hofstaedtler wrote:
can you confirm two additional things please:
1) this happens only on the large host?
https://ci.debian.net/packages/p/pdns/testing/s390x/41650331/
Seems it happens on our s390x host too (which has 10 debci workers
running in parallel).
Hi,
On 10-01-2024 11:24, Debian Bug Tracking System wrote:
minicoredumper (2.0.7-1) unstable; urgency=medium
* Fix autopackage test due to missing dependency (Closes: #1059553)
Now it fails with:
37s /tmp/autopkgtest.iUO3a9/build.Ta0/src/debian/tests/coredump: 23:
Source: libextractor
Version: 1:1.11-8
Severity: serious
Control: close -1 1:1.13-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than
Source: emacs-posframe
Version: 1.1.7-3
Severity: serious
Control: close -1 1.4.2-1
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more
Source: emacs-wgrep
Version: 3.0.0-1
Severity: serious
Control: close -1 3.0.0-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days
Hi,
On 08-01-2024 01:45, Aurelien Jarno wrote:
I am still not sure why it got killed on arm64 and not on other debci
workers, there as still swap available. Actually looking at the munin
plot, it seems that the arm64 debci workers stopped using swap around
September 2023 contrary to the other
Hi all,
On 08-01-2024 19:50, Paul Gevers wrote:
Can you tell me how you saw that? I neither spotted that, nor is not
having swap a conscious act, so rather a mistake.
I just checked and it seems that on ci-worker-arm64-08 was not having
swap. We did have /swap created as our other workers
Hi,
On 08-01-2024 01:45, Aurelien Jarno wrote:
I am still not sure why it got killed on arm64 and not on other debci
workers, there as still swap available. Actually looking at the munin
plot, it seems that the arm64 debci workers stopped using swap around
September 2023 contrary to the other
Hi,
On 07-01-2024 18:21, Aurelien Jarno wrote:
Timeout while building:
https://ci.debian.net/packages/g/glibc/unstable/arm64/41516611/
There are indeed many failures with cc1 getting killed, it seems that it
started around 2024-01-02. I haven't spotted any change to the toolchain
nor kernel
Source: pyflakes
Version: 2.5.0-1
Severity: serious
Control: close -1 3.1.0-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1058335
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and
Package: lazarus-src-3.0
Version: 3.0+dfsg1-5
Severity: normal
Hi,
I just did my daily update of my trixie system and spotted the error
below. The fallback works, but that "error" is highlighted in red, so it
catches the eye.
Paul
Unpacking lazarus-src-3.0 (3.0+dfsg1-5) over (3.0+dfsg1-3)
Hi Wouter,
On 06-01-2024 20:51, Wouter Verhelst wrote:
The Release Team considers packages that are out-of-sync between testing and
unstable for more than 30 days as having a Release Critical bug in testing
[1]. Your package src:extrepo has been trying to migrate for 33 days [2].
This should
Source: compyle
Version: 0.8.1-4
Severity: serious
Control: close -1 0.8.1-6
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as
Source: extrepo
Version: 0.11
Severity: serious
Control: close -1 0.12
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as having a
Source: liblouis
Version: 3.27.0-1
Severity: serious
Control: close -1 3.28.0-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1058514
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and
Source: libei
Version: 1.1.0-1
Severity: serious
Control: close -1 1.2.0-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1058218
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable
Hi Simon
On 06-01-2024 12:48, Simon McVittie wrote:
On Sat, 06 Jan 2024 at 10:16:28 +0100, Paul Gevers wrote:
If an explicit dependency on steam-libs:i386 would be valid, I'd be happy
to use that, and remove the steam-libs-i386 binary package as redundant.
We're not there yet, so please hold
Hi,
On 06-01-2024 08:21, Johannes Schauer Marin Rodrigues wrote:
I think it's a bit more complicated than that. Currently, the tool creates 8624
package relationships. If I remember correctly, britney is unable to analyze
cross-architecture relationships?
At least by lack of implementation.
Control: tags -1 pending
Hi,
On 03-01-2024 20:40, Paul Gevers wrote:
On 03-01-2024 20:22, Simon McVittie wrote:
I think all of those are correct?
I think that if apt allows you to install it, chances are that it's a
britney2 bug. I'll try to debug it tomorrow.
I have a first proposal
Hi Steve,
On 05-01-2024 17:36, Rene Engelhard wrote:
Also a problem is that experimental also might already contain totally
unrelated updates like new upstream versions...
I share this worry. Have you thought about how to handle the cases where
you don't have experimental to upload to? How
301 - 400 of 8187 matches
Mail list logo
