Source: trilinos
Version: 13.2.0-1
Severity: serious
This is a side-product of a rebuild test against libtbb-dev/experimental
==> CMakeFiles/CMakeError.log <==
Performing C++ SOURCE FILE Test
On Wed, 2022-06-01 at 20:29 +0200, Graham Inggs wrote:
> Control: tags -1 + moreinfo
>
> I noticed some packages in the tracker not appearing in your list;
> e.g. openimageio, pcl and yade. These packages have transitive
> build-dependencies on libtbb-dev through e.g. libopenvdb-dev or
>
On Sat, 2022-05-28 at 12:16 +0200, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
>
> On 2022-05-20 10:36:34 -0400, M. Zhou wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: tran
Hi Paul,
> Not convinced I'm totally right there's no key packages in the list
> above, but let's go this route unless somebody puts up the effort to
> *maintain* the ppc64el parts.
Based on the discussion on -devel, it seems that it's impossible
to keep maintaining the ppc64el support for
Package: wnpp
Severity: wishlist
Owner: Mo Zhou
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: luajit2
* URL : https://github.com/openresty/luajit2
* License : MIT/X
Description : OpenResty's Branch of LuaJIT 2
I'm going to remove ppc64el support from
Yes. If you have time to handle it please go ahead.
I'm suffering from a recent paper submission deadline,
so I'm only able to build and upload some small packages
that can be built on my weak laptop.
The paper deadline is May 19. After that I should be
able to handle this with a proper build
Control: severity -1 important
I've uploaded 1.12 to unstable. Let's see whether the situation has been
changed a little bit for armhf.
Floating point precision is sometimes flaky indeed, but I think this would not
be that fatal.
So changing the severity down to important. If the flaky test no
Package: ftp.debian.org
Severity: normal
The latest rocm-device-libs package is no longer producing arch-indep
binary packages. And we will keep working on arch-specific packages.
The arch:all package is no longer useful and it was not automatically
removed.
Thank you for using reportbug
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
PyTorch 1.12 will need flatbuffers 2.X .
Specifically I'm going to upload flatbuffers 2.0.6+dfsg1 to unstable.
It has three reverse dependencies as per build-rdeps.
vast [already ftbfs
Control: retitle -1 RFP: rapidyaml -- a library to parse and emit YAML, and do
it fast.
Control: owner -1 w...@debian.org
I'm giving up this ITP bug. Any one who is interested in this ITP can take it
over.
Package: wnpp
Severity: wishlist
Owner: Mo Zhou
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: lodepng
Version : git master
Upstream Author : Lode Vandevenne
* URL : https://lodev.org/lodepng/
* License : Zlib
Programming Lang: C
Description
Control: reopen -1
Control: found -1 0.38.1-3
Simply upgrading llvm deps from 11 to 13 leads to regression for
numba. I'm reverting this change back until the upstream source
code can really support a newer version.
Hi,
Thanks for the bug report. I'm aware of the break, and other users have reported
this issue some time before:
https://lists.debian.org/debian-ai/2022/06/msg00060.html
The break is due to onnx 1.12 upgrade.
The pytorch version in the new queue works fine with onnx 1.12,
as mentioned in the
/12818940efdf76cf48b8e2cfea2dfaa5dc11664a
luajit2 (2.1-20220411-5) unstable
Now it should be fine after several hours when we retry the autopkgtest.
On Tue, 2022-06-07 at 22:28 -0700, M. Zhou wrote:
> https://buildd.debian.org/status/package.php?p=luajit
> All green, including ppc64el and s390x
> (arch-specific tra
On Thu, 2022-06-09 at 13:58 +0200, Paul Gevers wrote:
> Hi Mo,
>
> You may want to look at the FTBFS on mipsel for python-lupa.
>
> https://buildd.debian.org/status/fetch.php?pkg=python-lupa=mipsel=1.13%2Bdfsg-1%2Bb2=1654771416=0
Yunqiang Su (@syq) volunteers to look into luajit issues on mips*
On Thu, 2022-06-09 at 10:47 +0200, Paul Gevers wrote:
>
> I think there one more *test* issue, the first test in src:luajit
> doens't explicitly declare dependencies, which means it implicitly has
> has '@'. Quoting [1]:
>
>
> Which means that autopkgtest asks apt to make sure all packages
On Thu, 2022-06-09 at 21:51 -0700, M. Zhou wrote:
>
> > lua-moses autopkgtest failure [2] looks bad (still a segmentation fault):
> > autopkgtest [07:20:14]: test command9: luajit debian/tests/simple.lua
> > autopkgtest [07:20:14]: test command9: [---
&g
Package: wnpp
Severity: normal
Control: affects -1 src:jsonnet
I intend to orphan the jsonnet package, because I'm not interested
in it anymore. The package is currently in good shape.
The package description is:
A data templating language for app and tool developers
.
* Generate config data
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
This bug is follow-up for this thread:
https://lists.debian.org/debian-release/2022/06/msg9.html
The original LuaJIT upstream does not care about IBM architectures, which
causes
ontrol: forwarded -1
> https://release.debian.org/transitions/html/libluajit2-support.html
>
> Hi Mo,
>
> On 05-06-2022 19:30, M. Zhou wrote:
> > So, currently I have a pending commit[2] modifying the dependency
> > template[1],
> > so that src:luajit reverse dep
On Mon, 2022-06-13 at 08:30 +0200, Gürkan Myczko wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Gürkan Myczko
> X-Debbugs-Cc: debian-de...@lists.debian.org
>
> * Package name: ffcv
>Version : 0.0.3
>Upstream Authors: ffcv team
>URL : https://ffcv.io/
> *
Package: wnpp
Severity: normal
Control: affects -1 src:python-fire
I intend to orphan the python-fire package.
This package is in good shape.
I'm just not interested in maintaining this anymore.
The package description is:
Python Fire is a library for automatically generating command line
Package: ftp.debian.org
Severity: normal
This package has been FTBFS for a long period. I have no interest
in bringing it back into good shape.
Thank you for using reportbug
Package: wnpp
Severity: normal
Control: affects -1 src:highwayhash
I intend to orphan the highwayhash package.
It is tensorflow dependency.
This package is in good shape.
I'm no longer interested in maintaining tensorflow dependencies.
The package description is:
Highwayhash provides three
Package: wnpp
Severity: normal
Control: affects -1 src:farmhash
I intend to orphan the farmhash package.
This package is tensorflow dependency.
This package is in good shape.
I'm no longer interested in maintaining tensorflow dependency.
The package description is:
FarmHash provides hash
Package: wnpp
Severity: normal
Control: affects -1 src:nsync
I intend to orphan the nsync package.
This package is tensorflow dependency.
This package is in very good shape.
I'm no longer interested in maintaining tensorflow dependencies.
The package description is:
nsync is a C library that
Package: wnpp
Severity: normal
Control: affects -1 src:vim-julia
I intend to orphan the vim-julia package.
This package is in good shape.
This package is team-maintained, but in fact I'm the only effective maintainer.
I'm no longer interested in maintaining this package.
The package description
Source: gftools
Version: 0.5.2+dfsg-2
Severity: wishlist
Dear maintainer,
I believe the gftools version in unstable is seriously outdated.
And fonts-cascadia-code 2111.01 requires a newer version to successfully build.
Please consider packaging a newer version if possible.
make[1]: Entering
Control: close -1
I'm no longer interested in packaging this.
This package is only useful for pytorch. And I'm no longer
planning to enable this package in pytorch build.
Control: owner -1 w...@debian.org
Control: retitle -1 RFP: pymc3 -- Bayesian statistical modeling and
Probabilistic Machine Learning
I'm no longer interested in packaging this on my own.
Control: close -1
It is not really necessary to package a volatile documentation project.
Looking up through internet is already convenient enough.
Package: wnpp
Severity: normal
Control: affects -1 src:asmjit
I intend to orphan the asmjit package.
This package is in good shape.
This package is a dependency of some optional pytorch dependencies, but I've
forgotten the particular name. Anyway, I'm no longer planning to enable that
optional
Control: reassign -1 src:onetbb
Control: fixed -1 2021.5.0-8
src:tbb has been renamed into src:onetbb. riscv build was already fixed.
On Sat, 2022-06-18 at 09:22 +0800, xiao sheng wen wrote:
> Hi,
> The tbb package had build successed on riscv now.
> libtbb2 is one of it's binary package:
>
On Sun, 2022-06-12 at 21:19 +0200, Paul Gevers wrote:
> Hi Mo,
>
> On 10-06-2022 08:00, M. Zhou wrote:
> > > There are some compilation flags tweakable. I'll try with
> > > qemu to see whether I can make it work.
> >
> > I tried to tweak some compil
architecture from both src:luajit and src:luajit2,
so that malfunctional binary packages are no longer built for it.
On Mon, 2022-06-20 at 22:10 +0200, Paul Gevers wrote:
> Hi Mo,
>
> On 13-06-2022 05:20, M. Zhou wrote:
> > So let's inform the reverse dependencies to remove
On Tue, 2022-06-07 at 21:21 +0200, Paul Gevers wrote:
> Hi Mo,
>
> On 07-06-2022 17:36, M. Zhou wrote:
> > This should be achievable by patching debian/control
> > during build once detected IBM architectures.
>
> This is not allowed. I currently fail to fin
On Tue, 2022-06-07 at 20:03 -0700, M. Zhou wrote:
>
> >
> > Yes, except for the part about patching d/control. We'll have to find
> > another way. An alternative to what I wrote before is a extension of the
> > description to say that the binary is empty on s390
https://buildd.debian.org/status/package.php?p=luajit
All green, including ppc64el and s390x
(arch-specific transitional dummy package)
Seems we are ready to start the rebuild?
On Tue, 2022-06-07 at 20:37 -0700, M. Zhou wrote:
> On Tue, 2022-06-07 at 20:03 -0700, M. Zhou wr
Hi Andrius,
Thank you so much for the help! I was still looking for time slot
to login into a build server to deal with this hard-to-build package.
Nowadays I sort of started to dislike packages that my laptop cannot
easily build within a few minutes :-)
On Mon, 2022-06-13 at 11:57 +0300,
I've filed the RM bug here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014990
Seems that we still have a bunch of blockers -- so this is not likely
happening soon.
On Fri, 2022-07-15 at 20:16 +0200, Graham Inggs wrote:
> Hi
>
> libtbb2 is now gone from testing. Please file a RM bug for
Package: ftp.debian.org
Severity: normal
Tags: +moreinfo
We have (somewhat) done the src:tbb -> src:onetbb transition,
and the old codebase src:tbb is now deprecated. Before we really
remove src:tbb from unstable, we still have some packages not
yet finished the transition.
I'll later file bugs
Source: blender
Severity: important
libtbb2 (src:tbb) has been deprecated (#1014990) in favor of libtbb12
(src:onetbb).
And blender is still one of the reverse dependencies of libtbb2.
Please migrate to the new library.
address this issue in timely manner.
On Thu, 2022-07-28 at 10:15 +0200, Andreas Tille wrote:
> Hi Graham,
>
> Am Thu, Jul 28, 2022 at 09:15:06AM +0200 schrieb Graham Inggs:
> > Hi
> >
> > On Wed, 27 Jul 2022 at 17:57, M. Zhou wrote:
> > > The previous
Package: ftp.debian.org
Severity: normal
I removed bin:onednn-doc from src:onednn because it feels like a maintenance
burden
to me, and this doc package has a very low popcon number. Thus, since we no
longer
build bin:onednn-doc, we need to remove it so that the package can migrate to
testing.
Source: scikit-learn
Version: 1.1.1-1
Severity: serious
Justification: Policy section 4.9 violation
There are loads of similar traceback message saying the documentation build
has failed to retrieve some URL, like this:
```
generating gallery for auto_examples/decomposition... [ 30%]
The previous segfault on armel becomes Bus Error on armel and armhf.
I can build it on Power9, but it seems that the test fails on power8 (our
buildd).
On Wed, 2022-07-27 at 09:56 +0200, Andreas Tille wrote:
> Control: tags -1 unreproducible
> Control: tags -1 moreinfo
> Control: severity -1
The bug should have been fixed in the -13 upload of src:onetbb
The FTBFS occurred because of GCC-11 -> GCC-12 bump.
According to upstream suggestion, we can simply turn off some warnings.
Please let me know if this bug persists.
On Wed, 2022-08-24 at 13:21 -0700, Diane Trout wrote:
> On Fri,
On Sat, 2022-08-27 at 08:55 +0200, Emanuele Rocca wrote:
> On 08/04 09:36, Paul Gevers wrote:
> > We are in the transition of making python3.10 the default Python
> > versions
> > [0]. With a recent upload of python3-defaults the autopkgtest of
> > pytorch
> > fails in testing when that
Package: gcc-12
Version: 12.1.0-8
Severity: important
This bug seems like a regression. GCC-11 has no issue compiling the same source.
https://buildd.debian.org/status/fetch.php?pkg=onetbb=ppc64el=2021.5.0-13=1660844413=0
[183/315] : && /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=.
Source: tbb
Version: 2020.3-2.1
Severity: serious
src:tbb: do not migrate. this source is deprecated in favor of
src:onetbb. The RM bug of src:tbb is filed at
https://bugs.debian.org/1014990
, M. Zhou wrote:
> Control: affects -1 src:onetbb
>
> It's due to a regression bug in GCC-12 that caused linker internal
> error on ppc64el:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017772
> Does not look like something I can look into.
>
> If you need it so
Control: affects -1 src:onetbb
It's due to a regression bug in GCC-12 that caused linker internal
error on ppc64el:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017772
Does not look like something I can look into.
If you need it soon in testing, please go ahead and downgrade compiler
to
Control: tags -1 +pending
Thanks for the patch. It is pending in git repo.
On Mon, 2022-10-24 at 14:44 +0200, наб wrote:
> Package: zfsutils-linux
> Version: 2.1.6-2
> Severity: normal
> Tags: patch
>
> Dear Maintainer,
>
> Please apply the attached patch that fixes trim.
>
> In particular,
Package: zfs-auto-snapshot
Version: 1.2.4-2
Severity: important
Tags: +patch
Dear maintainer,
After the deprecation of which, that command now creates lots of noise
and floods the system mail box. A simple fix is to replace the command.
Thanks. rakudo 2022.07-1 has been uploaded to unstable.
On Sun, 2022-09-25 at 15:49 +0200, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
>
> On 2022-09-22 19:23:13 -0400, M. Zhou wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.deb
Control: fixed -1 2.6.1-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Dear release team,
We would like to upload rakudo 2022.07 to unstable (2022.04).
Hence requesting this transition to rebuild all raku packages.
Ben file:
title = "rakudo";
Thanks. It has been uploaded to unstable.
On Fri, 2022-10-07 at 10:23 +0200, Emilio Pozuelo Monfort wrote:
> Control: tags -1 confirmed
>
> On 03/10/2022 19:22, M. Zhou wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packa
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hi release team,
I'd like to start the transition of simdjson. It has only two reverse
dependencies in testing:
cloudflare-ddns
pcm
Both of them passed my local test with amd64
https://salsa.debian.org/pkg-security-team/imhex
I forgot the current status. In my fuzzy memory there
are some new dependencies to be packaged.
On Sat, 2022-07-30 at 11:07 -0700, Dima Kogan wrote:
> Hi. Is this coming along? What needs to happen to get this into the
> repos? Do you need help?
>
Sure, I think we can ship a snapshot version as long as it works
fine with llvm-14. Could you please verify the snapshot hash
again?
https://github.com/numba/llvmlite/commit/c65b3e662b7b08920172b710419d7a06b660be59
The commit seems missing. If it was close to the master branch,
I can directly
Control: tag -1 +moreinfo
I have tried exactly the same patch half a year ago,
which resulted a massive number of segmentation faults.
Build log can be found in our buildd.
See https://github.com/oneapi-src/oneTBB/issues/777
I'm not sure whether the latest assembly code in
--build -i python{version} -p "3.11 3.10"
returned exit code 13
make: *** [debian/rules:11: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
On Thu, 2022-12-22 at 18:20 -0500, M. Zhou wrote:
> Sure, I think we can ship a snapshot version
Control: fixed -1 2022.07+dfsg-1
Control: close -1
I missed the detail that the compiler ID even changes for different
architecture.. which may not be good.
Is it possible for us to slightly modify the postinst script to
recompile the cache locally when the compiler id mismatches?
The fallback script rakudo-helper.pl can at least make sure
a
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: rak...@packages.debian.org
Control: affects -1 + src:rakudo
Dear release team,
We would like to start the transition for rakudo, updating rakudo
to the latest version in
Package: zfs-dkms
Version: 2.1.6-3
Severity: serious
It was built againt 6.0.0-3-amd64 on my sid machine, but suddenly
stopped working with the recent 6.0.0-5-amd64 kernel.
Sure, just do whatever you see appropriate, since you are the\
future maintainer :-) Thanks for taking it over!
On Mon, 2022-12-19 at 20:03 +0200, Andrius Merkys wrote:
> Hi,
>
> On Sat, 18 Jun 2022 20:04:05 -0700 "M. Zhou"
> wrote:
> > I intend to orphan the asmji
Control: severity -1 important
Control: tags -1 +moreinfo
I'm still not sure about why the upgrade failed, and I could not
reproduce the problem in a clean chroot using the following script:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Dear release team,
There was some minor API updates in the latest version of simdjson,
which resulted an SOVERSION bump from 13 to 14. I've tried to build
its reverse dependencies
Uploaded to unstable. Successfully built on all release archs:
https://buildd.debian.org/status/package.php?p=simdjson
On Sat, 2022-11-19 at 20:19 +0100, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
>
> On 2022-11-18 09:42:10 -0500, M. Zhou wrote:
> > Package: rel
Control: merge 1025214 1025171
The "MAKEFLAGS="--environment-overrides" also caused zfs-dkms FTBFS.
The two bugs above are the same issue, hence the merge.
Control: reassign -1 dkms 3.0.8-2
Control: retitle -1 regression: dkms/3.0.8-2 renders zfs-dkms FTBFS
Control: severity -1 serious
Hi,
Thank you for the information! I can confirm that this is the same issue
that you have encountered. By commenting out the --environment-overrides,
the current
Currently, I'd say PyTorch and TensorFlow are the two most
popular libraries. And I even worry google is trying to
write something new like Jax to replace TensorFlow in some aspects.
On Sat, 2023-01-14 at 11:12 +, Rebecca N. Palmer wrote:
> theano has been mostly abandoned upstream since
Control: severity -1 important
I think this FTBFS mostly stems from the toolchain.
1. before the bug is filed, it builds successfully on amd64
2. On the day I recieved this bug report, I reproduced it
3. after some toolchain updates, I cannot reproduce it anymore
I have uploaded moarvm, nqp, and rakudo to unstable.
They turned green on release architectures.
The ppc64el buildd lags a little bit but I believe the result will be
green as well based on the previous no-change build in experimental.
On Sun, 2023-01-15 at 19:09 +0100, Sebastian Ramacher wrote:
On Sun, 2023-01-29 at 09:03 +0100, Andreas Tille wrote:
>
>
> I have no idea about fmtlib but I noticed:
>
> [2022-09-04] fmtlib 9.1.0+ds1-2 MIGRATED to testing (Debian testing
> watch)
> [2022-09-04] Accepted fmtlib 9.1.0+ds1-2 (source) into unstable
> (Shengjing Zhu)
> [2022-08-27] Accepted
On Mon, 2023-01-30 at 06:46 +0100, Andreas Tille wrote:
> Am Sun, Jan 29, 2023 at 10:22:24AM -0500 schrieb M. Zhou:
>
>
> Since we do not have this module[2] (yet) we should probably exclude all
> tests that need this module, right? If you think its a nice thing to
> have
Feel free to break the pytorch reverse dependencies without a
transition slot -- we do not need the slot in the current status.
The rdeps are already not in testing due to RC bugs and needs
some new patchworks. Manual upload is needed for its rebuild.
On Fri, 2023-01-27 at 20:19 +0800, Aron Xu
For reference, a 8 core + 16GB RAM configuration should be able to finish the
pytorch compilation timely. The build takes roughly an hour. My observation
is based on power9 -- on amd64 it should be something similar.
On Sun, 2023-01-29 at 11:09 +0800, Aron Xu wrote:
> On Fri, Jan 27, 2023 at
Name "zst" for a tool that supports multiple compression formats
is ambiguous. If we could use special characters (of course we
cannot), I think "*z" (wildcard z) will do.
On Wed, 2022-11-02 at 02:38 +0100, Adam Borowski wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Adam Borowski
>
Package: wnpp
Severity: wishlist
Owner: Mo Zhou
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: nvitop
* URL : https://github.com/XuehaiPan/nvitop
* License : Apache-2.0 / GPL-3.0 dual license
Programming Lang: Python
Description : An interactive
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package fish
Not yet uploaded. This package does not have a proper
autopkgtest, manual unblock needed.
[ Reason ]
I cherry picked two upstream fixes. One of them fixes
Control: tags -1 - moreinfo
On Sun, 2023-03-26 at 07:28 +0200, Paul Gevers wrote:
> Control: tags -1 confirmed moreinfo
>
> Hi Mo,
>
> On 25-03-2023 15:39, M. Zhou wrote:
> > Please unblock package fish
> > Not yet uploaded. This package does not have a proper
>
On Sun, 2023-03-26 at 20:31 +0200, Luna Jernberg wrote:
> Not to whine but is the plan to build 3.6.1 that was released yesterday
> aswell?
It's the hard freeze stage for Debian. Introducing a massive change, such
as the full 3.6.1 upgrade will not likely successfully make it in testing
Package: wnpp
Severity: wishlist
Owner: Mo Zhou
X-Debbugs-Cc: debian-de...@lists.debian.org,
pkg-nvidia-de...@lists.alioth.debian.org
* Package name: nvidia-cudnn-frontend
* URL : https://github.com/NVIDIA/cudnn-frontend
* License : MIT (but will enter contrib due to
Package: wnpp
Severity: wishlist
Owner: Mo Zhou
X-Debbugs-Cc: debian-de...@lists.debian.org,
pkg-nvidia-de...@lists.alioth.debian.org
* Package name: nvidia-cutlass
* URL : https://github.com/NVIDIA/cutlass
* License : BSD-3-Clause (has to enter contrib due to non-free
On Sun, 2023-02-19 at 20:55 +0100, Andreas Beckmann wrote:
> On 18/02/2023 19.33, M. Zhou wrote:
> > * License : BSD-3-Clause but has to enter non-free.
>
> Why not contrib? A B-D: nvidia-cuda-toolkit does not require the package
> to be in non-free. BTW, please B-D: n
Package: wnpp
Severity: wishlist
Owner: Mo Zhou
X-Debbugs-Cc: debian-de...@lists.debian.org,
pkg-nvidia-de...@lists.alioth.debian.org
* Package name: nvidia-nccl
* URL : https://github.com/NVIDIA/nccl
* License : BSD-3-Clause but has to enter non-free.
Programming
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: nvidia-cu...@packages.debian.org
Control: affects -1 + src:nvidia-cudnn
Please unblock package nvidia-cudnn. Not yet uploaded to unstable,
just asking for a pre-approval.
[
I'm the previous uploader of src:fish.
The change looks good to me.
Please feel free to go ahead with the nmu once the release managers say OK.
On Mon, 2023-05-01 at 19:13 +0200, Andrej Shadura wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
Source: onetbb
Version: 2021.9.0-1
Severity: serious
I'm aware of this issue. I'm slightly faster than buildd for toolchain
upgrades. The issue will automatically disappear once our amd64 buildd
migrates to gcc-13. The gcc-12 will lead to the FTBFS you see now.
Local sbuild with gcc-13 has no
The issue still exists with armel:
https://buildd.debian.org/status/package.php?p=onetbb
On Wed, 2023-08-02 at 22:46 +0200, Petter Reinholdtsen wrote:
> [M. Zhou]
> > I'm aware of this issue. I'm slightly faster than buildd for
> > toolchain
> > upgrades. The issue will au
Control: fixed -1 2021.9.0-2
I agree.
On Thu, 2023-08-03 at 00:32 +0200, Petter Reinholdtsen wrote:
> [M. Zhou]
> > The issue still exists with armel:
> > https://buildd.debian.org/status/package.php?p=onetbb
>
> If so, this is a duplicate of
> https://bugs.debian.org/1
-1 confirmed
>
> On 2023-08-01 22:07:33 -0700, M. Zhou wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > X-Debbugs-Cc: simdj...@packages.debian.org
> > Control: affec
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: simdj...@packages.debian.org
Control: affects -1 + src:simdjson
Hi release team,
The simdjson upstream has bumped the ABI version along with their
new release. Thus the
Control: tags -1 wontfix
Thanks for reaching out for this issue. I've noticed the Ubuntu updates as well.
I'd personally not prefer to upload zfs-X.Y.99 anytime in the future. Since
debian
is volunteer-based, we don't seem to have more bandwidth than Ubuntu for
dealing with
regressions and
Package: wnpp
Severity: wishlist
Owner: Mo Zhou
X-Debbugs-Cc: debian-de...@lists.debian.org, debian...@lists.debian.org
* Package name: transformers
Upstream Contact: HuggingFace
* URL : https://github.com/huggingface/transformers
* License : Apache-2.0
Description
Control: fixed -1 2.1.11-1
2.1.11-1 has migrated to testing.
On Sun, 2023-05-07 at 22:03 +0200, Paul Gevers wrote:
> Control: tags -1 moreinfo
>
> Hi Mo,
>
> On 27-04-2023 21:31, M. Zhou wrote:
> > So, generally updating the package is simply to update the binary
> > tarball URL in the script, along with the exact version number
101 - 200 of 209 matches
Mail list logo
