Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hi RMs,
Small transition of RocksDB to version 7.8.3 as the affected packages
are limited to balboa and sortmerna. Both build fine on amd64 with
this new RocksDB version.
While version 7
Processing changes file: libreoffice_7.0.4-4+deb11u5_all-buildd.changes
ACCEPT
Processing changes file: libreoffice_7.0.4-4+deb11u5_ppc64el-buildd.changes
ACCEPT
Processing changes file: libreoffice_7.0.4-4+deb11u5_source.changes
ACCEPT
Processing commands for cont...@bugs.debian.org:
> package release.debian.org
Limiting to bugs with field 'package' containing at least one of
'release.debian.org'
Limit currently set to 'package':'release.debian.org'
> tags 1027298 = bullseye pending
Bug #1027298 [release.debian.org] bullseye-p
package release.debian.org
tags 1027298 = bullseye pending
thanks
Hi,
The upload referenced by this bug report has been flagged for acceptance into
the proposed-updates queue for Debian bullseye.
Thanks for your contribution!
Upload details
==
Package: libreoffice
Version: 7.0.4-4
Processing control commands:
> tags -1 + confirmed
Bug #1028054 [release.debian.org] bullseye-pu: package
macromoleculebuilder_3.2+dfsg-2+deb11u1
Added tag(s) confirmed.
--
1028054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028054
Debian Bug Tracking System
Contact ow...@bugs.debian.or
Control: tags -1 + confirmed
On Fri, 2023-01-06 at 16:08 +0200, Andrius Merkys wrote:
> On 2023-01-06 15:18, Adam D. Barratt wrote:
> > Hmmm. How did it manage to build initially, then?
> >
> > https://buildd.debian.org/status/fetch.php?pkg=macromoleculebuilder&arch=amd64&ver=3.2%2Bdfsg-2&stamp=1
Hello,
On Thu 05 Jan 2023 at 01:13PM GMT, Simon McVittie wrote:
> 3. If the ftp team prioritize NEW review of unstable packages higher than
>experimental packages (do they?) then that would be
>counter-productive under the proposed policy, and they'd have to
>stop doing that (and perh
On 2023-01-06 15:18, Adam D. Barratt wrote:
Hmmm. How did it manage to build initially, then?
https://buildd.debian.org/status/fetch.php?pkg=macromoleculebuilder&arch=amd64&ver=3.2%2Bdfsg-2&stamp=1608131113&raw=0
appears to be the version in bullseye currently, and only mentions
docbook-xsl on
El 21/9/22 a las 13:47, Ondřej Surý escribió:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu bind-dyndb-ldap_11.6-3 . ANY . bullseye . -m "rebuild for
bind9_9.16.33-1~deb11u1"
Hi,
after the bind9_9.16.33-1~deb11u1 is release to b
El 23/9/22 a las 10:21, Timo Aaltonen escribió:
Paul Gevers kirjoitti 22.9.2022 klo 22.26:
So, Timo, is the package in bullseye broken with the security update and does
it need a fix, or is it fine?
It needs a rebuild, [...]
I think it's really broken:
https://bugs.debian.org/cgi-bin/bugre
On Fri, 2023-01-06 at 13:38 +0200, Andrius Merkys wrote:
> macromoleculebuilder needs docbook-xsl to build, or it FTBFS
> (#1027828).
> However, in bullseye it does not pull this package in during the
> build,
> thus docbook-xsl has to be added as explicit build dependency.
>
Hmmm. How did it m
Sebastian Ramacher writes ("Re: Bug#1012496: Proposed inkscape reversion NMU"):
> On 2023-01-06 11:24:45 +, Ian Jackson wrote:
> > Hi.
> >
> > inkscape is currently uninstallable in sid on some release arches,
> > due to an FTBFS which seems to be an upstream problem [1].
> > This is blocking
Your message dated Fri, 6 Jan 2023 13:05:04 +0100
with message-id
and subject line Re: Bug#1027289: transition: libcamera
has caused the Debian Bug report #1027289,
regarding transition: libcamera
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Hi.
inkscape is currently uninstallable in sid on some release arches,
due to an FTBFS which seems to be an upstream problem [1].
This is blocking builds for packages that build-depend on inkscape. [5]
I'm assuming that the previous version in testing was OK. [0]
Mattia, you suggested[2] that you
for completeness: I'm aware of the build failures (currently i386 and
armel) and will handle them. For i386 I've prepared a patch and for
armel I will request the removal.
* Jochen Sprickerhof [2023-01-06 12:11]:
Package: release.debian.org
Severity: normal
User: release.debian@packages.d
Hi ian
On 2023-01-06 11:24:45 +, Ian Jackson wrote:
> Hi.
>
> inkscape is currently uninstallable in sid on some release arches,
> due to an FTBFS which seems to be an upstream problem [1].
> This is blocking builds for packages that build-depend on inkscape. [5]
> I'm assuming that the previ
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
macromoleculebuilder needs docbook-xsl to build, or it FTBFS (#1027828).
However, in bullseye it does not pull this package in during the build,
thus docbook-xsl has
Processing control commands:
> affects -1 + src:pcl
Bug #1028052 [release.debian.org] transition: pcl
Added indication that 1028052 affects src:pcl
--
1028052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028052
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: p...@packages.debian.org
Control: affects -1 + src:pcl
Hi Release Team,
I would like to transition to the new pcl version prepared in
experimental. I'm fine with the auto g
On Fri, 6 Jan 2023 at 12:00, Sebastiaan Couwenberg wrote:
> is_good doesn't match what's currently used for builds with php8.2:
>
> phpapi-20220829
This has just been merged, thanks Adrian!
[1] https://salsa.debian.org/release-team/transition-data/-/merge_requests/36
On 7/14/22 15:23, Paul Gevers wrote:
https://release.debian.org/transitions/html/php8.2.html
[...]
title = "php8.2";
is_affected = .depends ~ "phpapi-20210902" | .depends ~
"phpapi-20210903";
is_good = .depends ~ "phpapi-20210903";
is_bad = .depends ~ "phpapi-20210902";
Tracker file set up
On Thu, Jan 05, 2023 at 02:29:42PM +0100, Sebastian Ramacher wrote:
>
> From recent memory and assuming there are no issues with d/copyright,
> binary-NEW uploads to experimental have been processed swiftly.
This is also my experience that binary-NEW uploads for
library SONAME bumps are handled v
On Fri, Jan 06, 2023 at 10:18:16AM +0100, Moritz Muehlenhoff wrote:
>...
> We might consider to set some expectation for oldstable-security, though e.g
> state that
> oldstable-security updates stop three months after the release of stable or
> so.
>
> Chromium is very fast-paced in toolchain ch
On 6 January 2023 1:26:05 pm IST, "Rebecca N. Palmer"
wrote:
>Should this go ahead before the freeze? I think yes if the new dask works,
>but am open to disagreement.
The version of dask is same since few months. What do you mean by new dask?
>skbio #1017574
This has been fixed in latest
On Fri, Jan 06, 2023 at 08:41:50AM +0100, Paul Gevers wrote:
> Dear Chromium team, Security team,
>
> On 27-01-2022 17:15, Moritz Muehlenhoff wrote:
> > On Wed, Jan 26, 2022 at 09:38:42PM +0100, Paul Gevers wrote:
> > > > So, I'm proposing the following: we unblock chromium from
> > > > testing, w
Should this go ahead before the freeze? I think yes if the new dask
works, but am open to disagreement.
Issues this would fix:
python3.11 #1023965: We're currently ignoring these test failures.
Mystery autopkgtest failure (fails without any listed individual test
failure, started 2022-11-13)
On 1/6/23 08:23, Paul Gevers wrote:
On 06-01-2023 07:39, Sebastiaan Couwenberg wrote:
What's your plan to deal with these entanglements?
I have bumped the priority of php8.2 on ppc64el and s390x as a start.
Thanks, gtk+3.0 is also blocking several packages on s390x.
Kind Regards,
Bas
--
28 matches
Mail list logo
