Hi,
On 12-01-2024 16:42, Blake Gilbert wrote:
I am reaching out to you regarding a recent package submission by our
Engine Connectivity Engineering team. We submitted the package CDImage
M-LINUX-WolframEngine.DEB a few months ago to include Wolfram Engine in
Debian packages, and I wanted to
Hi,
On 12-01-2024 16:42, Blake Gilbert wrote:
I am reaching out to you regarding a recent package submission by our
Engine Connectivity Engineering team. We submitted the package CDImage
M-LINUX-WolframEngine.DEB a few months ago to include Wolfram Engine in
Debian packages, and I wanted to
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 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: 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-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-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
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
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,
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 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 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
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
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
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
Oops, should have waited sending...
On 06-01-2024 14:30, Paul Gevers wrote:
On 06-01-2024 14:15, Gioele Barabucci wrote:
Aren't all these problems just inherent in Debian's lack of a mandated
packaging tooling and workflow [1,2]?
Might be, but that doesn't mean that problem goes away.
I
Hi Gioele,
On 06-01-2024 14:15, Gioele Barabucci wrote:
Aren't all these problems just inherent in Debian's lack of a mandated
packaging tooling and workflow [1,2]?
Might be, but that doesn't mean that problem goes away.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
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: 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: 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: 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
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: 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: 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
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 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.
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.
Hi,
On 05-01-2024 18:08, Aurelien Jarno wrote:
I have just given it back, let's see what happens.
Didn't help.
I asked rmadison:
paul@mulciber ~ $ rmadison gcc-mingw-w64-i686-posix --suite=unstable
gcc-mingw-w64-i686-posix | 12.3.0-9+25.3 | unstable | mips64el
gcc-mingw-w64-i686-posix |
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
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
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
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
Hi,
Thanks for reaching out.
On 05-01-2024 07:45, Johannes Schauer Marin Rodrigues wrote:
It would generate the following two stubs (shortened here for brevity):
Package: pkga
Version: 1
Architecture: amd64
Depends: pkgc:any
Multi-Arch: no
Package: pkgb
Version: 1
Architecture: amd64
Hi,
Thanks for reaching out.
On 05-01-2024 07:45, Johannes Schauer Marin Rodrigues wrote:
It would generate the following two stubs (shortened here for brevity):
Package: pkga
Version: 1
Architecture: amd64
Depends: pkgc:any
Multi-Arch: no
Package: pkgb
Version: 1
Architecture: amd64
Hi,
On 04-01-2024 17:28, Chris Hofstaedtler wrote:
On Thu, Jan 04, 2024 at 03:37:21PM +0100, Paul Gevers wrote:
Hi,
On 04-01-2024 15:08, Chris Hofstaedtler wrote:
It would seem that the host runs out of IPC space?
What is IPC space?
https://manpages.debian.org/bookworm/manpages/sysvipc.7
Hi,
On 04-01-2024 17:28, Chris Hofstaedtler wrote:
On Thu, Jan 04, 2024 at 03:37:21PM +0100, Paul Gevers wrote:
Hi,
On 04-01-2024 15:08, Chris Hofstaedtler wrote:
It would seem that the host runs out of IPC space?
What is IPC space?
https://manpages.debian.org/bookworm/manpages/sysvipc.7
Hi,
On 04-01-2024 15:08, Chris Hofstaedtler wrote:
It would seem that the host runs out of IPC space?
What is IPC space? And when does a host run out of it? As I said, this
is one of our most powerful hosts, so I would expect it to run out of
things last.
Does it run more tests in
Hi,
On 04-01-2024 15:08, Chris Hofstaedtler wrote:
It would seem that the host runs out of IPC space?
What is IPC space? And when does a host run out of it? As I said, this
is one of our most powerful hosts, so I would expect it to run out of
things last.
Does it run more tests in
Source: pdns
Version: 4.8.3-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. The failures seem related on the host that runs
the test. ci-worker13 is a beefy
Source: pdns
Version: 4.8.3-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. The failures seem related on the host that runs
the test. ci-worker13 is a beefy
Hi Benjamin,
Sorry for the tremendous delay.
On 18-08-2023 14:56, Benjamin Lotter wrote:
- Did any packages fail to upgrade?
KDE as always kind of broke, but could be reinstalled
I guess you don't have more details? If you do, you might want to file
that information against kde-baseapps.
Hi,
On 03-01-2024 14:02, Georg Faerber wrote:
Thanks for the upload, although I would have appreciated communication
about this upfront.
Of course. As a Release Manager, I would have appreciated a more timely
handeling of an RC issue that blocks other packages. I followed DevRef
guidance:
Hi,
On 03-01-2024 14:02, Georg Faerber wrote:
Thanks for the upload, although I would have appreciated communication
about this upfront.
Of course. As a Release Manager, I would have appreciated a more timely
handeling of an RC issue that blocks other packages. I followed DevRef
guidance:
Hi Simon,
On 03-01-2024 10:34, Simon McVittie wrote:
In the HTML output, under "Additional info" (which if I understand
correctly is meant to be for notes that do not affect migration),
That's the idea, yes.
it
says:
- Additional info:
- uninstallable on arch amd64, not running
Hi Simon,
On 03-01-2024 10:34, Simon McVittie wrote:
In the HTML output, under "Additional info" (which if I understand
correctly is meant to be for notes that do not affect migration),
That's the idea, yes.
it
says:
- Additional info:
- uninstallable on arch amd64, not running
Hi Simon,
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.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
Hi Simon,
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.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
Hi
On 03-01-2024 12:44, Colin Watson wrote:
While at some point you might want to do a bit more abstraction to
reduce code duplication, I think the simplest approach would be to copy
autopkgtest-{build,virt}-lxd to autopkgtest-{build,virt}-incus and do a
little bit of search-and-replace. I've
Hi,
On 03-01-2024 12:55, Antonio Terceiro wrote:
I think that sound reasonable, but I don't know how to sufficiently judge
this. Maybe my co-maintainers have ideas about it?
I think we can use use the smaller of [4GB, 50% of the host RAM], to
avoid killing a host where 4GB is more than what
Hi Stefano,
On 02-01-2024 21:54, Stefano Rivera wrote:
It would be great if you could provide a specification for this file
format, so tools like Debusine can have some confidence that they're
parsing it correctly.
$(man autopkgtest) has a section on OUTPUT FORMAT, isn't that what
you're
Control: reassign -1 autopkgtest
Hi Michael,
On 02-01-2024 22:27, Michael Biebl wrote:
You raise an interesting point though by framing this as an autopkgtest
issue: Maybe the default in autopkgtest-virt-qemu should be bumped.
This value was set in 2014 and systems have significantly more RAM
Hi Dirk,
On 02-01-2024 20:42, Dirk Eddelbuettel 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
I noticed that too over the last few weeks as I tend to keep an eye on my
aggregation at
Hi Dirk,
On 02-01-2024 20:42, Dirk Eddelbuettel 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
I noticed that too over the last few weeks as I tend to keep an eye on my
aggregation at
Source: devicexlib
Version: 0.1.0-2
Severity: serious
Control: close -1 0.8.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
Source: mopac
Version: 22.0.6+dfsg-1
Severity: serious
Control: close -1 22.1.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: devicexlib
Version: 0.1.0-2
Severity: serious
Control: close -1 0.8.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
Source: mopac
Version: 22.0.6+dfsg-1
Severity: serious
Control: close -1 22.1.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: rjava
Version: 1.0-6-1
Severity: serious
Control: close -1 1.0-10-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: rjava
Version: 1.0-6-1
Severity: serious
Control: close -1 1.0-10-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
Hi Michael,
On 02-01-2024 11:04, Michael Biebl wrote:
we are currently trying to get the systemd upstream autopkgtest suite pass
in Debian sid/trixie with qemu and I'm thrilled to see that qemu support
for debci is currently evaluated.
I think you mean for ci.debian.net (debci is a source
Hi
On 01-01-2024 22:33, Bastian Blank wrote:
Do we have serial of the machines?
Do you mean of the system where the VM's run, or of the VM itself? IIRC
the qemu backend of autopkgtest is talking to the VM over serial, but if
you want to be sure, I'll need to check.
Paul
Hi
On 01-01-2024 22:33, Bastian Blank wrote:
Do we have serial of the machines?
Do you mean of the system where the VM's run, or of the VM itself? IIRC
the qemu backend of autopkgtest is talking to the VM over serial, but if
you want to be sure, I'll need to check.
Paul
Source: ocfs2-tools
Version: 1.8.7-1
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the list
Hi,
On 2023-09-27 20:49, Aurelien Jarno wrote:
> On 2023-09-25 17:08, Adrian Bunk wrote:
https://buildd.debian.org/status/logs.php?pkg=gcc-mingw-w64=26.1=s390x=sid
The way the logs are cut might indicate that zani has 37 GB
diskspace that are exhausted?
No there is no disk space issue on
Control: tags -1 pending
Hi Helmut,
On 10-12-2023 16:15, Helmut Grohne wrote:
Packages (such as erlang-cowboy) that have libjs-jquery-tablesorter in
their dependency tree cannot satisfy their cross Build-Depends, because
Architecture: all packages can never satisfy cross Build-Depends unless
Control: tags -1 pending
Hi Helmut,
On 10-12-2023 16:15, Helmut Grohne wrote:
Packages (such as erlang-cowboy) that have libjs-jquery-tablesorter in
their dependency tree cannot satisfy their cross Build-Depends, because
Architecture: all packages can never satisfy cross Build-Depends unless
Control: found -1 4.9-1
Control: severity -1 important
On Fri, 1 Dec 2023 16:53:50 +0100 Emanuele Rocca wrote:
Package: systemtap
Version: 5.0-1
Severity: serious
I have lowered the severity to enable migration, given that 5.0-2 works
around the problem.
The builds on r-b [1] show that
Control: found -1 4.9-1
Control: severity -1 important
On Fri, 1 Dec 2023 16:53:50 +0100 Emanuele Rocca wrote:
Package: systemtap
Version: 5.0-1
Severity: serious
I have lowered the severity to enable migration, given that 5.0-2 works
around the problem.
The builds on r-b [1] show that
Source: tracker-miners
Version: 3.4.6-1
Severity: serious
Control: close -1 3.4.6-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1057617
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and
Source: tracker-miners
Version: 3.4.6-1
Severity: serious
Control: close -1 3.4.6-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1057617
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and
Source: xfce4-power-manager
Version: 4.18.2-1
Severity: serious
Control: close -1 4.18.3-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: xfce4-power-manager
Version: 4.18.2-1
Severity: serious
Control: close -1 4.18.3-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: xfce4-power-manager
Version: 4.18.2-1
Severity: serious
Control: close -1 4.18.3-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 lxc-templates
Control: retitle -1 consider adding security repos by default
Control: affects -1 debci autopkgtest
Hi all,
On 05-11-2023 03:41, Santiago Ruano Rincón wrote:
Is there any reason why `debci setup ...` doen't configure the security
repostories inside the lxc
Control: tags -1 pending
On 01-01-2024 09:50, Paul Gevers wrote:
I'm going to NMU with this patch shortly. @gregor, any reason why you
didn't the upload to DELAYED after you built it already?
I have uploaded the attached changes.
Paul
diff --git a/debian/changelog b/debian/changelog
index
Control: tags -1 pending
On 01-01-2024 09:50, Paul Gevers wrote:
I'm going to NMU with this patch shortly. @gregor, any reason why you
didn't the upload to DELAYED after you built it already?
I have uploaded the attached changes.
Paul
diff --git a/debian/changelog b/debian/changelog
index
Dear all,
On Thu, 23 Nov 2023 18:03:45 +0100 gregor herrmann
wrote:
Currently mat2's test suite fails, maybe due to newer libimage-exiftool-perl
releases. This can be seen on ci.debian.net, but the same failures
occur during the build tests, so the package FTBFS.
I've locally added upstream
Dear all,
On Thu, 23 Nov 2023 18:03:45 +0100 gregor herrmann
wrote:
Currently mat2's test suite fails, maybe due to newer libimage-exiftool-perl
releases. This can be seen on ci.debian.net, but the same failures
occur during the build tests, so the package FTBFS.
I've locally added upstream
Source: benchmark
Control: found -1 benchmark/1.8.3-1
Severity: serious
Tags: sid trixie
Dear maintainer(s),
With a recent upload of benchmark the autopkgtest of pytorch fails in
testing when that autopkgtest is run with the binary packages of
benchmark from unstable. It passes when run with
Source: benchmark
Control: found -1 benchmark/1.8.3-1
Severity: serious
Tags: sid trixie
Dear maintainer(s),
With a recent upload of benchmark the autopkgtest of pytorch fails in
testing when that autopkgtest is run with the binary packages of
benchmark from unstable. It passes when run with
Source: benchmark
Control: found -1 benchmark/1.8.3-1
Severity: serious
Tags: sid trixie
Dear maintainer(s),
With a recent upload of benchmark the autopkgtest of pytorch fails in
testing when that autopkgtest is run with the binary packages of
benchmark from unstable. It passes when run with
Dear s390x porters,
Recently I added isolation-machine [1] support to ci.debian.net on
amd64. At this moment, I think performance wise the only architecture
that qualifies in our infrastructure to add it too is s390x. However,
autopkgtest-build-qemu doesn't know what to do yet. Would any of
701 - 800 of 19951 matches
Mail list logo
