Hi Aurelien,
On 12-12-2021 12:37, Aurelien Jarno wrote:
Thanks, I'll add the necessary hints once the glibc upload is old
enough.
Those false positives are due to the fact that glibc from experimental
is used, and I do not expect them to appear for glibc in sid. In
addition a few of them after
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 unsatisfiable dependency
>
Hi,
On 22-12-2021 11:54, Sebastian Ramacher wrote:
The autopkgtests of growlight all fail and is unable to migrate. Please
fix them so that the transition can be finished.
I discussed most of this problem with Nick in bug #1001122. The issue is
in notcurses and is supposedly fixed in unstable
:11, Paul Gevers wrote:
I propose we can start the php8.1 transition around Christmas 2021. Does
that work for you Ondřej?
Assuming you were OK with this timing, I propose you go ahead now.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
Hi Nick,
On 22-12-2021 20:42, Paul Gevers wrote:
On 22-12-2021 11:54, Sebastian Ramacher wrote:
The autopkgtests of growlight all fail and is unable to migrate. Please
fix them so that the transition can be finished.
I discussed most of this problem with Nick in bug #1001122. The issue is
Hi Ondřej, PHP PECL Maintainers,
On 31-12-2021 12:50, Ondřej Surý wrote:
Uploaded php 8.1.1 and php-defaults 91 switching the Debian PHP version to PHP
8.1
Thanks.
Will you also upload src:php-imagick, which seems to block some rebuilds
in the current state.
I want to update the ben trans
Hi Nick,
On 01-01-2022 05:17, Nick Black (Public gmail account) wrote:
I see that growlight's autopkgtests are disabled in testing
right now due to the timeout. Can we please remove that, so I
can try something?
No, only in unstable [1]. Testing should still work.
Paul
[1] https://ci.debian.
Hi,
On 31-12-2021 21:25, Paul Gevers wrote:
Hi Ondřej, PHP PECL Maintainers,
On 31-12-2021 12:50, Ondřej Surý wrote:
Uploaded php 8.1.1 and php-defaults 91 switching the Debian PHP
version to PHP 8.1
Thanks.
Will you also upload src:php-imagick, which seems to block some rebuilds
in the
Hi
On 01-01-2022 14:20, Ondřej Surý wrote:
2. Generate all binary packages to debian/control during the build,
but this would then require overrides (which I think doesn’t really
scale)
If you mean (re)generating debian/control during build, that's not
allowed (albeit I can't quickly find a ref
Hi,
Please enlighten me on the details of php packaging that I'm missing and that
we should be aware of for this (and future) transition(s).
Is it true that because the api is already provided in testing that we
now have some packages working with (and pulling in) php7.4 and some
with php8.
Hi,
Back from holidays.
On 01-01-2022 14:20, Ondřej Surý wrote:
Some rebuilds failed, e.g. php-horde-lz4 [6],
The FTBFS is unrelated to PHP 8.1 transition
php-wmerrors [7], owfs [8].
These two need upstream update.
I see no activity and no bug reports. Can somebody please update these
Hi David,
On 08-01-2022 23:09, David Prévot wrote:
I also see some autopkgtest regressions which have this (eg. [1, 2]):
"""
PHPUnit requires the "dom" extension.
"""
where should that get fixed?
There are several php7.4-* packages pulled in those logs, so it’s not
really a surprise that does
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
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 &qu
Hi,
On 09-01-2022 23:22, David Prévot wrote:
This is important because some of these packages are currently allowed to migrate to testing without php-defaults (were it not for the autopgktest failure), and would
break functionality in testing. We need to find out how to fix that.
I assume you
Hi Ondřej,
Found via the transition tracker [0], just in case you forgot about
them, php-geoip [1], php-pinba [2], php-propro [3] php-stomp [4] and
php-apcu-bc [5] are awaiting new uploads from you for the transition and
because of source-only uploads.
Paul
[0] https://release.debian.org/tr
Hi
On 10-01-2022 21:09, Paul Gevers wrote:
Hi Ondřej,
Found via the transition tracker [0], just in case you forgot about
them, php-geoip [1], php-pinba [2], php-propro [3] php-stomp [4] and
php-apcu-bc [5] are awaiting new uploads from you for the transition and
because of source-only
Hi,
On 10-01-2022 21:13, Ondřej Surý wrote:
I thought I filled RM bugs for all of them, but I found only #1003055 for
php-apcu-bc, something must went wrong.
Neither of these support PHP 8.x, and those packages should be removed.
I missed that. I'll remove them from testing already.
I’ll r
Hi,
On 10-01-2022 21:32, Paul Gevers wrote:
Hi,
On 10-01-2022 21:13, Ondřej Surý wrote:
I thought I filled RM bugs for all of them, but I found only #1003055
for php-apcu-bc, something must went wrong.
Neither of these support PHP 8.x, and those packages should be removed.
I missed that
Hi,
On 11-01-2022 17:11, Mattia Rizzolo wrote:
On Tue, Jan 11, 2022 at 05:00:59PM +0100, Diederik de Haas wrote:
*) https://tracker.debian.org/pkg/discover also (still) shows it as a high
priority problem, while the problem is already fixed/addressed.
As I've seen it on t.d.o quite a lot of tim
Hi David,
On 10-01-2022 23:43, David Prévot wrote:
Le 10/01/2022 à 16:44, Paul Gevers a écrit :
On 10-01-2022 21:13, Ondřej Surý wrote:
I thought I filled RM bugs for all of them, but I found only
#1003055 for php-apcu-bc, something must went wrong.
Neither of these support PHP 8.x, and
Hi,
On 11-01-2022 20:52, Paul Gevers wrote:
There seems to be a new (unrelated?) FTBFS, so we need to figure it
out (or drop symfony from testing until then).
If that's OK with you/the team, I can check how much needs to be
removed doesn't seems like a lot of fun yet:
I st
Hi,
On 12-01-2022 15:56, David Prévot wrote:
In unstable (thanks for that), but it fails to migrate to testing, due
to the 'PHPUnit requires the "dom" extension.' issue.
Can’t find this issue. Did it go away by itself, or did you make any
change?
https://ci.debian.net/packages/p/php-doctrin
Dear horde maintainers, Mike,
On 05-12-2021 22:11, Paul Gevers wrote:
Bugs have been filed (with the exception of the horde stack, but they
are aware) of items we're aware of. Let's give the maintainers a month.
I propose we can start the php8.1 transition around Christmas 2021.
Hi Andreas,
On 15-01-2022 03:27, Andreas Beckmann wrote:
please temporarily ignore the autopkgtest failure of pocl on ppc64el.
pocl just gained a first superficial autopkgtest, but it is not built on
ppc64el and therefore not installable ... causing a "regression"
Ack, I will.
I'll add the
Hi,
On 12-01-2022 21:16, Paul Gevers wrote:
Priority
may lay with the mediawiki* regression on i386: "Internal Server Error"
doesn't sound great, and other non-horde package.
Did anybody already take a look at this [1, 2, 3]? It's the last thing
before I'll
Hi,
One more thing.
On 16-01-2022 20:52, Paul Gevers wrote:
It's the last thing
before I'll add a hint to ignore the autopkgtest regressions.
I see in the excuses [1] that some php-* package become uninstallable.
Those need to be fixed. php7.4-common will be removed (of course
Hi Otto,
On 16-01-2022 21:46, Otto Kekäläinen wrote:
Next MariaDB for Bullseye release tracked in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000342
Status: the stable release team decided not to release the latest
MariaDB 10.5.13 even though it was prepared and uploaded for Bullseye.
Ap
Hi,
On 17-01-2022 06:49, Kunal Mehta wrote:
I don't have any i386 hardware, I tried pulling down a i386 Debian
unstable Docker container on my amd64 laptop and installing the
mediawiki+php8.1 packages on that but it didn't trigger the test
failure. Do you have any other suggestions/tips on how
Hi Ondřej,
I checked why e.g. src:php-uploadprogress isn't migrating. I think I
spotted a packaging mistake, probably coming from the toolchain.
php-uploadprogress Depends on php7.4-uploadprogress, but that package
isn't built anymore or provided by any binary package. As the binary
isn't par
Hi,
On 18-01-2022 19:37, Ondřej Surý wrote:
the fix is simple, it was actually cruft from before when uploadprogress didn’t
support PHP 8.1:
https://sources.debian.org/src/php-uopz/7.1.1+6.1.2-5/debian/rules/#L3
https://sources.debian.org/src/php-gnupg/1.5.1-1/debian/rules/#L3
I guess too.
Control: tags -1 moreinfo
Hi Yangfl,
On Thu, 27 Aug 2020 01:35:40 +0100 Simon McVittie wrote:
On Thu, 27 Aug 2020 at 01:01:39 +0100, Simon McVittie wrote:
> If the new library is genuinely
> compatible with the old library, then I think a better way to do this
> would be to introduce an empty,
Hi Simon, Sebastian,
On 16-08-2021 15:44, Simon McVittie wrote:
On Mon, 16 Aug 2021 at 11:10:37 +0200, Sebastian Ramacher wrote:
I've now scheduled binNMUs with reduced build priority. cairocffi,
pyglet and pinta will require source uploads as they build arch: all
binaries with dependencies on
Control: block -1 by 915948
Hi,
On 18-01-2022 21:59, Vagrant Cascadian wrote:
On 2020-12-20, Paul Gevers wrote:
On Thu, 15 Nov 2018 20:49:43 +0100 Paul Gevers wrote:
I think I have found the cause for this issue. Apparently some arch:all
binary packages are not listed in both the binary
Hi Bryce,
On 19-01-2022 10:28, Bryce Harrington wrote:
With [4] applied, I'm seeing the following dumped on armhf:
## https://autopkgtest.ubuntu.com/packages/m/mediawiki/jammy/armhf
cat: /var/log/mediawiki/error.log: No such file or directory
2022-01-19 09:16:57 autopkgtest-lxd-eeoxik autopkgt
Hi Ondřej,
On 18-01-2022 20:31, Paul Gevers wrote:
On 18-01-2022 19:37, Ondřej Surý wrote:
the fix is simple, it was actually cruft from before when
uploadprogress didn’t support PHP 8.1:
https://sources.debian.org/src/php-uopz/7.1.1+6.1.2-5/debian/rules/#L3
https://sources.debian.org/src
Hi Sébastien,
On 18-01-2022 19:25, Sébastien Villemot wrote:
Note that octave-database's autopkgtest on armhf regressed. See
https://ci.debian.net/data/autopkgtest/testing/armhf/o/octave-database/18432401/log.gz
for the log
I’ve tried to reproduce the failure on abel.d.o, but the autopkgtest
s
Hi Kunal,
Thanks for the analysis.
On 20-01-2022 10:56, Kunal Mehta wrote:
I can't tell what it may be trying to encode, but presumably it's either
Main_Page or something used by Main_Page, which I'm guessing should only
take a fraction of a second to encode. I suppose we could test
increasing
Hi Andres,
On 26-01-2022 08:00, Andres Salomon wrote:
Chromium has been updated in sid and bullseye, and I'm in the process
of cleaning up the package further to make it easier to maintain.
Chromium is currently blocked from entering testing. I'm not going to
make any claims about the suitabilit
Package: release.debian.org
Severity: serious
Control: affects -1 src:chromium
This bug is to make sure we don't forget to make a decision on shipping
chromium in bookworm. The decision will depend on how chromium updates
are handled between filing this bug and approximately the freeze, both
i
Hi,
On 03-02-2022 04:24, M. Zhou wrote:
Some time ago the rakudo tracker is set up
https://release.debian.org/transitions/html/rakudo.html
At that time packages like raku-tap-harness depends on
raku-api-2021.09 , which is provided by rakudo 2021.09
Now that rakudo 2021.12 has landed onto uns
Hi again,
On 03-02-2022 09:16, Paul Gevers wrote:
As with all required rebuilds, you can request them (preferably using
$(reportbug release.debian.org). I'll schedule the rebuilds shortly for
this round.
I didn't check well. These are arch:all binaries which can't be properly
Hi,
On 05-02-2022 15:54, Dominique Dumont wrote:
On Thursday, 3 February 2022 09:16:54 CET Paul Gevers wrote:
I'm slightly surprised that perl6-readline isn't picked up by the
tracker. We'll need to check why that is.
I've a possible explanation.
Thanks for thinking alo
Hi Niko,
On 09-02-2022 22:49, Niko Tyni wrote:
Not sure about the format but hope the attached will do. Each line has
the package to be rescheduled, and then a list of packages that need
to be pulled from unstable. I haven't checked whether the lists are
absolutely minimal for this, but a few to
Hi Alex,
On 10-02-2022 13:21, Alex wrote:
I was wondering why the condition for the perl-5.34 transition has the
"depends" in the condition, but not the "recommends"?
I think because we never did that in the past, I *assume* the tracker
was based on the previous one.
The "collectd" package
Hi Jonas,
On 11-02-2022 12:08, Jonas Smedegaard wrote:
(I tried to get the package auto-kicked from testing by filing
release-critical bug#958117 but evidently that didn't work.)
That would work if uglifyjs was not a key-package. We can only remove it
if that's no longer the case, and then au
Control: forwarded -1
https://release.debian.org/transitions/html/ruby3.0-default.html
Hi Antonio, Lucas
On 15-02-2022 21:31, Antonio Terceiro wrote:
I saw that this was already added to the list of planned transitions,
thanks for that. according to
https://release.debian.org/transitions/html/
Hi,
On 17-02-2022 13:42, Lucas Kanashiro wrote:
Can I prepare a ruby-defaults upload targeting unstable just switching
the default to ruby3.0 and keeping ruby2.7?
I first want to see the new tracker packages (should be available soon,
but I'm not sure I have time until this evening to look).
Control: tags -1 confirmed
On 17-02-2022 13:42, Lucas Kanashiro wrote:
Can I prepare a ruby-defaults upload targeting unstable just switching
the default to ruby3.0 and keeping ruby2.7?
Please go ahead.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
Hi Lucas, Antonio,
On 17-02-2022 20:11, Lucas Kanashiro wrote:
I just uploaded ruby-defaults/1:3.0 to unstable, it should be available
soon.
I started scheduling jobs. I already noticed some that *didn't* pick up
the new dependency, can you have a look:
https://buildd.debian.org/status/packa
Hi,
On 18-02-2022 21:18, Lucas Kanashiro wrote:
https://buildd.debian.org/status/package.php?p=graphviz
https://buildd.debian.org/status/package.php?p=hivex
I am not sure about graphviz
Sorry, my mistake. I didn't schedule this one (yet) because of libwebp7.
but for hivex I submitted a MR t
Hi,
On 18-02-2022 21:23, Paul Gevers wrote:
Also the autopkgtest regressions don't look pretty yet, did you
already have a look:
https://qa.debian.org/excuses.php?package=ruby-defaults
I'll try to take a look at this list and see what's going on.
coderay seems to have a patch
Hi Antonio,
Thanks for taking care.
On 24-02-2022 02:43, Antonio Terceiro wrote:
diaspora-installer can just be removed, it's already on the autoremoval
list.
also fails without the new ruby-defaults.
I'm not seeing that. The 2022-02-24 01:38:19 UTC reference run on amd64
passed.
I retr
Dear colleagues,
The Release Team would like to propose a bookworm freeze timeline. Don't
worry, the timeline is a plan, if serious (timing) issues come up we
will adapt. However, before making the plan public in a wider audience,
we'd like to know from you if you already foresee clashes in ti
Hi Victor,
On 02-03-2022 14:55, Victor Seva wrote:
So I think We will need to allow both to migrate in order to fix this
situation.
Is this also an issue for users, or is this only an issue for the test?
It seems to me that this may also impact users, which means this is a
missing *versioned
Hi Andreas,
On 03-03-2022 11:28, Andreas Beckmann wrote:
with the recent uploads of src:cub and src:libthrust I've added
autopkgtests, which unfortunately are causing regressions. Please ignore
these for now while I'll try to fine-tune them in the future.
Are you in a hurry to get these versi
Hi
On 27-02-2022 14:07, Antonio Terceiro wrote:
The fix for that is probably non-trivial, so IMO we should remove
diaspora-installer from testing to let the transition complete.
diaspora-installer was removed, and ruby-defaults migrated to testing.
Under the assumption that you haven't seen a
Control: reassign -1 ftp.debian.org
Hi Georges,
On 04-03-2022 20:47, Georges Khaznadar wrote:
Hello, the package cwiid has not been maintained upstream for
twelve years, and the reported bugs show that it is not usable
currently: most constructs are deprecated since the end of life
of Python2.
Hi Wouter,
On 09-03-2022 10:49, Wouter Verhelst wrote:
I uploaded a fix for two security issues in NBD to unstable yesterday,
but forgot to set the severity to "high".
Please adjust so that the package doesn't need to wait for 5 days.
age-days 2 nbd/1:3.24-1 hint added. Would that suffice?
P
Hi Andreas,
On 08-03-2022 03:02, Andreas Beckmann wrote:
On 03-03-2022 11:28, Andreas Beckmann wrote:
with the recent uploads of src:cub and src:libthrust I've added
autopkgtests, which unfortunately are causing regressions. Please
ignore these for now while I'll try to fine-tune them in the f
Hi,
On 07-03-2022 23:36, Lucas Kanashiro wrote:
I uploaded ruby-defaults/1:3.0+1 removing ruby2.7 support.
Thanks for that. It looked like the transition was nearly over, but
britney (rightfully) refuses to remove src:ruby2.7. It took me some
time, but it's because some packages depend on ru
Hi,
On 16-03-2022 22:18, Lucas Kanashiro wrote:
The problem is that it did not migrated yet, some regressions were reported.
If you mean autopkgtest regressions found by ci, than those should be
dealt with now.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
Dear Sebastian, Kurt,
On 19-03-2022 12:33, Adam D Barratt wrote:
Upload details
==
Package: openssl
Version: 1.1.1n-0+deb10u1
Explanation: new upstream release
We're seeing a regression in buster in the autopkgtest of gnutls28 with
the new version of openssl on all tested archit
Hi mips porters,
On Sun, 12 Dec 2021 21:51:28 +0100 Paul Gevers wrote:
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:gcc-defaults-mipsen has been trying to
migrate
Hi Otto,
On 24-03-2022 04:41, Otto Kekäläinen wrote:
On Thu, Mar 17, 2022 at 4:09 AM Paul Gevers wrote:
..
2023-01-12 - Milestone 1 - Transition and toolchain freeze
2023-02-12 - Milestone 2 - Soft Freeze
2023-03-12 - Milestone 3 - Hard Freeze - for key packages and
Hi lumin,
On 14-03-2022 02:30, Matthias Klose wrote:
On 13.03.22 21:59, M. Zhou wrote:
I have not tested by myself, but I heard from an archlinux
developer that this API bump breaks a lot packages. And
some upstreams decided to disable or drop tbb support as
a result. I guess we can take simila
Hi Sylvestre,
On 18-10-2021 22:42, Sylvestre Ledru wrote:
So, please share your plans with us.
My target is to have 2 versions for the next release. Realistically,
because of all the use
cases (ex: ghc), it is hard to have all packages focusing only one
version of llvm.
You recently added llv
Hi Victor,
On 22-01-2023 16:08, Victor Westerhuis wrote:
This is bug #971739, I think, but I cannot find online what steps to
take next. Should I switch the dependency to python3-sphinx:native? Or
is this something that can be overridden someway?
I think for now (if you want progress) it's be
Control: tags -1 moreinfo
On 23-01-2023 20:02, Sven Joachim wrote:
[ Reason ]
1. Pasting in vim is broken on some terminal emulators[1]
Remedy: Declare versioned Breaks against vim-common in ncurses-{base,term}
2. Stack buffer overflow in "tic -I" on crafted input[2]
Remedy: Cherry-pic
Hi Guillem,
On 25-01-2023 22:17, Guillem Jover wrote:
BTW, I had in mind doing a call for
translations and a final upload including _only_ those, but reading
the above, I'm wondering whether that would be welcome/acceptable? If
not, then no problem, and I'll not bother translators now, and simpl
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 Salvatore,
On 28-01-2023 17:48, Salvatore Bonaccorso wrote:
[On a related note, if you, release team can unblock an let 6.1.7-1
still migrate to testing earlier that that, that would be welcome so
we have several important fixes in already for testing. Though there
is a regressions for i386.
Dear all,
As I hope you are all aware, we are rapidly approaching of the release
of Debian 12 'bookworm'. This means that we also want to get the release
notes [1, 2] for bookworm into shape and translated.
Following the process that I proposed and used during the buster and
bullseye release
Hi,
As a Release Team member, I'm leave a small note here.
On Thu, 15 Apr 2021 18:12:17 +0200 Bastian Blank wrote:
I would like to propose a release goal:
It has been a while since we did release goals in the formal way. I
recommend instead to discuss this in a bigger audience and get tract
Source: cross-toolchain-base-mipsen
Version: 21
Severity: serious
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s) and mips* porter(s),
Please consider this an official warning for the mipsel and mips64el
ports. Several key packages that a
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: rm
Hi Adam,
As discussed in bug #1027825, #1014503 and #1004729 (and probably
more), bind-dyndb-ldap is currently broken in bullseye and because of
its use of unstable internal detai
Hi Ian,
On 05-02-2023 14:06, Ian Jackson wrote:
Sorry again for being an idiot, but where should we have checked, to
avoid such a mistake in the future ? I thought this kind of thing
would appear on tracker but
https://tracker.debian.org/pkg/xen
doesn't show it now.
ocaml is a bit weird,
Control: tags -1 bullseye
Hi Mike,
On 07-02-2023 12:14, Mike Gabriel wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: debian-rem...@lists.debian.org
nmu x11vnc_0.9.16-7 . ANY . bullseye . -m "Rebuild against libvncs
Hi Jonas,
On 08-02-2023 19:31, Jonas Smedegaard wrote:
omething seems wrong in autopkgtests for rust-ureq: status is listed as
"Test in progress" on all arches, except ppc64el and s390x that had
failed, seemingly due to choking on the src:rust-rustls package recently
switching from arch-any to a
Hi Peter,
These questions are better addressed at the Release Team, who is
responsible for the rules of migration. The Debian CI team merely offers
infrastructure to run autopkgtests.
On 08-02-2023 04:03, Peter Colberg wrote:
For a package in unstable that has reached an age of 5 days and
ot
Hi Peter,
On 09-02-2023 02:39, Peter Colberg wrote:
@Release Team, besides [2], did I miss documentation that explains the
rules of migration? If not, how may I contribute to the documentation?
[2]
https://release.debian.org/doc/britney/solutions-to-common-policy-issues.html#britney-complains-
Control: reassign -1 debci-collector
Control: retitle -1 missing filename sanitizing
Hi Jonas,
On 08-02-2023 21:20, Paul Gevers wrote:
So it's either the timing was extremely unfortunate and your package hit
something unknown on our infrastructure, or it's actually the package
that
Hi Jonas,
On 09-02-2023 23:59, Jonas Smedegaard wrote:
I can only interpret that as the test environment on thos arches being
broken. Please don't punish the package for that :-(
I think your interpretation it wrong. librust-rustls-dev Depends on
librust-ring-0.16+default-dev which is only a
Hi,
Disclaimer, I may be misunderstanding how things work, because I only
judge it on observations and some comments in threads here and there.
On 11-02-2023 00:43, Adrian Bunk wrote:
I would be curious whether there is any technical reason why most
Go libraries are binary-all but most Rust l
Control: severity -1 normal
Control: tags -1 moreinfo
Hi Jonas,
On 12-02-2023 09:19, Jonas Smedegaard wrote:
Package: release.debian.org
Severity: important
^
Please don't do this with bugs against release.debian.org. It makes our
flow worse instead of helping.
The pack
Hi Adrian,
On 14-02-2023 14:25, Adrian Bunk wrote:
This will require a hint from the release team I have not yet requested,
since installability of binary-all packages is tested on amd64 and arm64
but there is no requirement that a binary-all package is installable on
arm64 and several are not.[
Control: tags -1 moreinfo
Control: severity -1 normal
Hi Daniel,
On 16-02-2023 01:11, Daniel Leidert wrote:
I ask you to
find a reasonable approach to deal with this for the Bookworm release.
That's not how we normally work. Please come with concrete proposals and
we can evaluate them.
Pau
Control: tags -1 confirmed
On 13-02-2023 20:45, Andreas Beckmann wrote:
src:nvidia-graphics-drivers recently moved from non-free to
non-free-firmware since the firmware-nvidia-gsp binary package was moved
to that section, too.
Ack.
Tracker reports
autopkgtest for nvidia-graphics-drivers/n/
Hi Steve,
On 16-02-2023 11:56, Steve McIntyre wrote:
Thanks, that did! But I wasn't paying enough attention and forgot to
also ask for the related:
unblock grub-efi-amd64-signed/1+2.06+8
unblock grub-efi-arm64-signed/1+2.06+8
unblock grub-efi-ia32-signed/1+2.06+8
Could you also add those pleas
Control: tags -1 confirmed
Dear Otto,
On 12-02-2023 08:14, Otto Kekäläinen wrote:
MariaDB 10.11 is the latest stable and long-term supported (until
2028) version of a popular database software. Having it included in
Debian Bookworm would serve users best, both immediately and in the
long run wh
Dear Release Team colleagues, dear Boot team colleagues,
I just sent out a bits from the RT where I'm claiming that bookworm is
in a good state. And now I'm going to be extremely bold now: aim for the
shortest freeze in Debian history. What do people think of the idea to
start picking a releas
Hi all,
On 18-02-2023 00:57, Steve McIntyre wrote:
On Fri, Feb 17, 2023 at 11:44:47PM +0100, Cyril Brulebois wrote:
That'd mean end of March, beginning April at the soonest.
it's probably best to
add 2-4 extra weeks to that.
+1
Thanks kibi and Sledge for the feedback. With such a time li
+ * creator.py: add new non-free-firmware component (Closes: #1029803)
+ * debian/tests: Add adduser dependency, fix test to not assume vim-tiny
+matches for vim. (from bookworm branch)
+
+ -- Paul Gevers Wed, 22 Feb 2023 16:09:19 +0100
+
command-not-found (20.10.1-1) unstable; urgency=med
Dear Ted,
On 16-02-2023 23:24, Theodore Ts'o wrote:
But, if the Debian Release team would like to override my position, my
suggestion would be to just change the default for /etc/mke2fs.conf
for *everyone* running Debian bookworm, and with the understanding
that this will be reverted in Debian t
Hi Otto,
On my daily updated system, I today saw this:
The following NEW packages will be installed:
libdbd-mariadb-perl
The following packages have been kept back:
mariadb-server
The following packages will be upgraded:
chromium chromium-common chromium-driver chromium-sandbox
glib-networ
Control: tags -1 moreinfo
Hi,
On 20-02-2023 13:09, Dominic Hargreaves wrote:
If the release team would be willing to grant an exception to the policy
to get this done, we can get this wrapped up inside a week I expect.
Can you please confirm that everything is ready to do this? I.e. there
is
Hi Otto,
On 23-02-2023 17:08, Otto Kekäläinen wrote:
What does apt upgrade -o Debug::pkgDepCache::Marker=1 -o
Debug::pkgDepCache::AutoInstall=1 -o Debug::pkgProblemResolver=1
yield?
In this situation we need to debug what versions apt is seeing and how
it is resolving them [1].
paul@mulciber
Hi all,
On 23-02-2023 02:21, Chris Knadle wrote:
I'd like to know the status of mumble-server on armhf and arm64 and
whether it can be restored for those architectures, because mumble
server is commonly run on that hardware and is one one of the base
expected programs for the FreedomBox projec
Dear David,
On 08-02-2023 13:53, David Prévot wrote:
[ Tests ]
I didn’t test it thoroughly (I doubt to have much time for at least
another week), but it passes
There are issues with the installability of src:symfony packages as can
be seen from the autopkgtests [1]:
php-symfony-security-bun
Control: tags 994758 - bookworm-ignore
Hi Adrian,
Thanks for caring.
On 25-02-2023 14:30, Adrian Bunk wrote:
With the bookworm-ignore for #994758,
I'll admit that I misjudged that bug; with this message I'll clear the
bookworm-ignore tag.
bullseye and bookworm
will ship libsgutils2-2 pac
201 - 300 of 1548 matches
Mail list logo
