Package: shortwave
Followup-For: Bug #1103551
Thanks! While the original issue was quickly fixed, I got stuck a few
more times and it turned out this time indeed due to missing
dependencies. Just for completeness and on the off chance it may be of
help to someone, here's how I got it working. For
Package: shortwave
Version: 5.0.0-4
Followup-For: Bug #1103551
Note:
Likely a false positive as I expected shortwave to be runnable
standalone. Didn't even know what a Circle app is exactly, so I assume
now it depends on a complete GNOME environment? If so, I should be
surprised if this is the ri
Package: shortwave
Version: 5.0.0-4
Severity: grave
Justification: renders package unusable
Dear Maintainers,
shortwave aborts immediately and whether or not providing command line
arguments:
$ RUST_BACKTRACE=1 shortwave
thread 'main' panicked at src/audio/gstreamer_backend.rs:96:14:
Un
uld cause a lot of problems which we'd want to avoid and
it's not in the interests of the project to pursue it further.
My apologies for the needless controversy.
--
brian m. carlson (they/them)
Toronto, Ontario, CA
signature.asc
Description: PGP signature
kept, although I agree that's undesirable for other reasons.
With a rebuilt version of libcurl3t64-gnutls with those two items
dropped, neither libcurl3t64-gnutls nor git-remote-https (nor
git-imap-send) link against libssl or libcrypto. (I accidentally
rebuilt curl from experimental, but
O_INSTALL_HARDLINKS` to comply with policy. So the defaults
are not necessarily designed for every use, or even to please distros by
default.
--
brian m. carlson (they/them)
Toronto, Ontario, CA
signature.asc
Description: PGP signature
e entire reason libcurl3t64-gnutls has
traditionally existed is for licensing reasons, so if we're going to
link that library with OpenSSL, you might as well just get rid of it
altogether and just use libcurl4t64.
--
brian m. carlson (they/them)
Toronto, Ontario, CA
signature.asc
Description: PGP signature
Source: fltk1.3
Version: 1.3.11-1
Severity: serious
fluid should remain continuously available in testing.
-- System Information:
Debian Release: trixie/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'stable-security'), (500,
'stable-debug'), (500, 'oldstable-securit
Control: fixed -1 2.6.0+dfsg-6
Control: close -1
Manually rebuilt. Marking this as done.
he diverted instance or its own code,
depending on usage. (Their syntax is conveniently very different.)
Likewise for einfo, as also found in epub-utils.
Thanks for checking, though!
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cg
Package: python3-torch-cuda
Version: 2.6.0+dfsg-3
Severity: serious
In [1]: import torch
---
ImportError Traceback (most recent call last)
Cell In[1], line 1
> 1 import torch
File /usr/lib/py
Control: severity -1 important
Lowering the importance since I'm not able to reproduce this issue.
It might be a flaky test.
68.html
[2] If this proves to be totally impossible and the GCC project is
completely intransigent, I will grant an exception, but I can only do so
on behalf of myself.
--
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA
signature.asc
Description: PGP signature
On 2025-02-13 at 01:28:54, Ryan Tandy wrote:
> (CCing the git bug)
>
> On Thu, Feb 13, 2025 at 12:37:01AM +0000, brian m. carlson wrote:
> > Since Git links against libcurl3t64-gnutls, it is now undistributable
> > since it's GPLv2 and OpenSSL is incompatibly licensed
On Fri, 2025-02-07 at 02:10 +0500, Andrey Rakhmatullin wrote:
> On Mon, Jan 27, 2025 at 09:15:06AM +0100, Sebastian Ramacher wrote:
> > Source: pytorch-cuda
> > Version: 2.5.1+dfsg-4
> > Severity: serious
> > X-Debbugs-Cc: sramac...@debian.org
> >
> > pytorch-cuda is involved in the currently ongo
c
ii git-email 1:2.48.0~rc1+next.20250101-1
pn git-gui
pn git-mediawiki
pn git-svn
pn gitk
pn gitweb
-- no debconf information
--
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA
signature.asc
Description: PGP signature
Hi Sudip,
Thank you for fixing this while I'm dealing with other packages.
Please feel free to upload without delay. If you have access to
the git repo, please git push and that will be appreciated :-)
On Sat, 2025-01-25 at 12:42 +, Sudip Mukherjee wrote:
> Control: tags 1092802 + patch
> Co
anges from upstream that fix the issue do
not apply cleanly to unstable or bookworm, but I am about 75% complete
on getting it into unstable. Once that is complete, we will have all
three CVEs resolved in unstable.
--
Loren M. Lang
lor...@north-winds.org
http://www.north-winds.org/
IRC: penguin359
On Thu, Jan 02, 2025 at 02:56:21PM -0800, Loren M. Lang wrote:
> I can take a look at this bug this weekend and submit a patch if you
> don't get to it first.
I've submitted a patch to fix the build failure with this merge request:
https://salsa.debian.org/debian/gnucash/-/merge_
I can take a look at this bug this weekend and submit a patch if you
don't get to it first.
Thanks,
--
Loren M. Lang
lor...@north-winds.org
http://www.north-winds.org/
Public Key: http://www.north-winds.org/lorenl_pubkey.asc
Fingerprint: 7896 E099 9FC7 9F6C E0ED E103 222D F356 A57A
Control: tag -1 pending
Hello,
Bug #1087883 in gh reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/gh/-/commit/60ecaf61cdf0b69893035c888f40a351a
I had contact with upstream and a new versin 0.38 will be released soon
which will fix this bug.
Kind regards,
Martijn van Brummelen
Hi.
I'm not sure if anyone's checking this bug anymore ---since it was
erroneously marked as Done.
With nautilus 47.0-2, and libgtk-4-1 v4.16.3+ds-2, the issue still
persists:
$ nautilus
** Message: 09:01:23.931: Connecting to
org.freedesktop.Tracker3.Miner.Files
MESA-INTEL: warning: ../src/inte
On Wed, 2024-10-30 at 18:07 -0700, Keith Packard wrote:
>
> I've submitted an MR to the gcc-avr repository on salsa:
>
> https://salsa.debian.org/debian/gcc-avr/-/merge_requests/4
>
Thank you. I will be reviewing and testing this evening and then get it
forwarded to my sponsor.
-Steve
le to change my user avatar, I get:
$ gnome-control-center
13:21:17.6387 cc-system-panel[195017]: WARNING: Failed to pick avatar
image: Dismissed by user
That is, the FileChooser doesn't show up, but the control center
assumes the user pressed the Cancel button.
--
John M.
On Mon, 2024-0
IDIA GPU as the primary one (as
per these
instructions:
https://wiki.debian.org/NVIDIA%20Optimus#Using_NVIDIA_GPU_as_the_primary_GPU
).
--
John M.
On Mon, 2024-09-30 at 07:46 -0400, Jeremy Bícha wrote:
>
> Control: reassign -1 src:gtk4 4.16.2+ds-1
> Control: affects -1 src:nautilusContr
08808d602-3
uptodate
printer-driver-hpcups:amd64/unstable 3.22.10+dfsg0-5.1 uptodate
printer-driver-postscript-hp:amd64/unstable 3.22.10+dfsg0-5.1 uptodate
---
John M.
-- System Information:
Debian Release: trixie/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'),
Thank you for your time. You may upload the package to the no delay queue, I
will check it when I have free time.
On September 10, 2024 11:00:47 AM GMT+01:00, Andreas Tille
wrote:
>Control: tags -1 pending
>Thanks
>
>Hi Jose,
>
>your package rep-gtk was showing up in the list of candidates for
upload a fix when I get a
chance, probably over the weekend. Sorry for the noise about slated
autoremovals, meanwhile.
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Was able to reproduce this issue.
Seems to be fixed upstream:
https://github.com/wolfpld/tracy/commit/1a971d867d6fa5bf6dc57d705dcbbc6020031e7a
Updating tracy to newest release should help fix this.
Thanks,
Alan M Varghese (NyxTrail)
On Mon, 29 Jul 2024 20:26:33 -0400 Boyuan Yang wrote
On closer inspection, this seems to be a bug in vamp, rather than
sonic-visualiser.
E.g. consider the following example program:
```C++
#include "vamp-hostsdk/RealTime.h"
#include
#include
int main() {
Vamp::RealTime t1 = Vamp::RealTime(0, 5);
struct timeval tv;
tv.tv_sec = 0;
Hi,
On 2024-04-29 10:28, Bo YU wrote:
Tags: patch
hi,
On Thu, Apr 18, 2024 at 10:00:30PM +0200, Sebastian Ramacher wrote:
checking for libconfig... no
checking for main in -llibconfig... no
configure: error: libconfig library not found
It seems it shuold use libconfig-dev.
Thanks didn't
n overhead would be negligible in practice.
Thanks!
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Andreas Tille writes:
>Build-Depends libthread-pool 4.0.0 which does not build
>for 32bit architectures[1]
I see a fix in experimental:
https://buildd.debian.org/status/package.php?p=libthread-pool&suite=experimental
Why not just reupload it to unstable?
--
Aaron M. Uc
Dear maintainers,
Debian 12.5 stable updated here from the main repo, impossible to
compile nvidia module with dkms on 6.1.0-18.
Same error as everyone else:
ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'__rcu_read_lock'
ERROR: modpost: GPL-incompatible module nvidia.ko
arrange for unaffected architectures' dependency templates to read e.g.
libfltk1.3t64 #MINVER# | libfltk1.3 #MINVER#
Sorry if I missed any relevant discussion; I must confess I haven't
followed -devel in years. :-/
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
ht
The ultimate fix is to update the upstream version (#1059087) but this
is blocked on work in four other packages including two new packages.
An interim fix would be to backport the upstream fix (patch attached).
0001-ignore-universeDomain.patch
Description: Binary data
This is blocking migration https://tracker.debian.org/pkg/golang-golang-x-oauth2
> Migration status for golang-golang-x-oauth2 (0.4.0-1 to 0.15.0-1): BLOCKED:
> Rejected/violates migration policy/introduces a regression
> Issues preventing migration:
> ∙ ∙ autopkgtest for golang-golang-x-oauth2/0
Control: tags -1 +patch
https://salsa.debian.org/apt-team/python-apt/-/merge_requests/90
> --- FAIL: TestTokenSource (0.00s)
> panic: cannot handle unexported field at {*google.Credentials}.universeDomain:
> "golang.org/x/oauth2/google".Credentials
This is fixed upstream
https://github.com/googleapis/google-api-go-client/commit/b3a71bda027d9ff92df3bf76b5ee9ffa55520dd9
so hopefully upd
Source: python-canmatrix
Followup-For: Bug #1056461
This seems to really be a bug in python3-future:
```sh
$ python3-c "import past.builtins"
$ python3.12 -c "import past.builtins"
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/past/builtin
Thank you for your work. No need for the delay.
Kind regards.
Jose M Calhariz
On December 3, 2023 1:14:09 PM GMT+00:00, Tobias Frost wrote:
>Control: tags 1055253 + patch
>Control: tags 1055253 + pending
>
>Dear maintainer,
>
>I've prepared an NMU for amanda (version
ndencies, so the
package will still need a sourceful upload; copying its migration bug
accordingly.
> I am going to file a RM bug when this is autoremoved from testing.
Thanks! To confirm, I don't need to do anything active here, just leave
this bug open at RC severity and reencourage drawxt
On Sun, 2023-09-17 at 14:12 +0200, Ari wrote:
> Have you, maintainers of zfs, considered configuring the packages so
> that it skips trying to build of affected kernels?
> This would at least reduce the time of installing any packages
> drastically - currently my system tries to build it for two ke
am_rtaudio.o] Error 1
```
Attached is a patch that fixes the FTBFS (but is otherwise untested).
No debdiff this time, sorry.
cheers.
Description: Fix FTBFS with RtAudio6
Replace try/catch with check for return code
Author: IOhannes m zmölnig
Origin: Debian
Forwarded: no
Last-Update: 2023-09-09
--
ing directory '/build/mlt-zme0kO/mlt-7.18.0/obj-x86_64-linux-gnu'
```
Attached is a patch that fixes the FTBFS (but is otherwise untested).
No debdiff this time, sorry.
cheers.
Description: Fix FTBFS with RtAudio 6
replace try/catch with check for return codes.
check device.ID instead of d
On Tue, 5 Sep 2023 18:11:55 +0200 "Miguel A. Vallejo"
wrote:
> M. Zhou wrote:
>
> > But after that I noticed that the most important
> > package grub-efi-amd64-signed:amd64 (1+2.06+13,
> > 1+2.12~rc1+7) was not upgraded along with the other
> > grub pac
Same here. But I have some different conclusions after fixing my
machine.
Before my machine becoming unable to boot, the last apt log involves
Start-Date: 2023-09-05 00:09:00
Commandline: apt upgrade
Requested-By: lumin (1000)
Upgrade: libimath-3-1-29:amd64 (3.1.9-2, 3.1.9-3), python3-brlapi:amd
Control: severity 891197 normal
u...@debian.org (Aaron M. Ucko) writes:
> For the time being, we can switch to an embedded copy of classic PCRE by
> dropping the build dependency on libpcre3-dev; that's of course not a
> proper fix, but should at least let us downgrade this bug
If it helps, I opened a pandoc issue about the groff "warning: cannot
select font 'C'" https://github.com/jgm/pandoc/issues/9020
f classic PCRE by
dropping the build dependency on libpcre3-dev; that's of course not a
proper fix, but should at least let us downgrade this bug's severity.
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Sorry for the inconvenience. This is a temporary break due to the
undergoing pytorch 2.0.1 upgrade work.
On Mon, 2023-08-21 at 14:52 +0200, Mattias Ellert wrote:
> Package: python3-torch
> Version: 1.13.1+dfsg-4
> Severity: serious
>
> Importing torch results in failure due to missing symbols:
>
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
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 iss
Hi, I believe my last update fixed the problem can someone double check?
Kind regards
Jose M Calhariz
On July 7, 2023 11:26:22 AM GMT+01:00, Jose M Calhariz
wrote:
>I too think it's a race condition. I made some changes to the test but the
>upload to Debian did not went well.
>
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 iss
I too think it's a race condition. I made some changes to the test but the
upload to Debian did not went well.
On July 6, 2023 2:12:59 PM GMT+01:00, Vincent Lefevre
wrote:
>On 2023-07-05 18:58:13 +0200, Johannes Christ wrote:
>> Is there another way to reproduce this issue?
>
>I'm wondering wh
ercurial
pn subversion
-- no debconf information
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
signature.asc
Description: PGP signature
led. I went with a minimal fix, in part to
facilitate getting it into a stable update if anyone considers that
warranted.
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Source: passwordsafe
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
I saw autopkgtest failure for passwordsafe
133s /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions
less than C++14 are not supported.
133s 27
I tried purging the mono font packages, then supertuxkart and then
reinstalling supertuxkart from scratch.
This way the installation was working fine.
I do not know what happened (why the first installation of supertuxkart did
not work), but I solved the problem.
So you can close this bug I guess
Control: severity -1 important
Control: fixed -1 1.13.1+dfsg-5
I believe these symlinks were deprecated already. These symlinks are removed in
1.13.1+dfsg-5 (experimental).
I'm not able to prepare a 1.13.1+dfsg-4.1 release to only remove these symlinks
within a short time... too busy lately.
So
Control: fixed -1 2.1.11-1
2.1.11-1 has migrated to testing.
andom_value here and in the other unittests/*map.hpp headers to
match the corresponding containers' declarations, per the attached
patch. The relevant platform difference is whether plain char is
signed, as it notably is on x86 but not arm*. (There are other
architectures in each camp.)
--
fix.
Kind regards
Jose M Calhariz
On 3/15/23 18:29, Kamil Jońca wrote:
Jose M Calhariz writes:
On 3/13/23 13:16, Kamil Jońca wrote:
"Debian Bug Tracking System" writes:
Thank you for filing a new Bug report with Debian.
You can follow progress on this Bug here: 1032884:
https://bugs.debian.org/cgi-bin/bugrepo
Hi Barry,
Can you please open a new bug report for this problem?
Kind regards
Jose M Calhariz
On February 23, 2023 9:40:53 PM GMT+00:00, Barry Trent
wrote:
>I applied this update to my one remaining buster machine and now it is
>refusing to connect to my bullseye-based amanda backup
Hi, just to tell that I am working on CVE-2022-37705, currently checking if the
fix work on my workbench.
Kind regards
Jose M Calhariz
On February 15, 2023 11:10:25 PM GMT+00:00, Amanda Trusted
wrote:
>Hi Jose,
>
>Here are the relevant bug fixes -
>[0] CVE - http
Hi,
This is my first security update, can I ask what is the procedure or where is
documented?
Kind regards
Jose M Calhariz
On January 28, 2023 12:59:09 PM GMT+00:00, Salvatore Bonaccorso
wrote:
>Source: amanda
>Version: 1:3.5.1-9
>Severity: grave
>Tags: security upstream
&g
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 I
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 fm
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 9:42
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 wro
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
2-06-30 22:35:01.0 +0200
+++ aubio-0.4.9/debian/changelog2023-01-15 21:40:50.0 +0100
@@ -1,3 +1,10 @@
+aubio (0.4.9-4.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * waf compatibility with Python3.11 (Closes: #1028178)
+
+ -- IOhannes m zmölnig (Debian/GNU) S
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 2018.
r broke the
logic to honor FLTK_SKIP_FLUID (which I've confirmed remains present).
Thanks for the report (reminiscent of [1], FWIW), and sorry for the
trouble!
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855040
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
: build: plugin distutils failed with: exit code=1:
/usr/bin/python3 setup.py build
dh_auto_build: error: pybuild --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
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 pul
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:
https://salsa.debian.org/zfsonlinux-team/zfs/-/blob/master/debian/tests/sbuild-shell-bullseye-to-bookworm.
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 zfs
ere sra-sdk 3.x stands in
terms of architecture support, which may be clearer with upgrades to
3.0.1 in place. I've been working on them, but a power outage last
weekend delayed me; I'll try to wrap them up this weekend.
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
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.
Andreas Beckmann writes:
> during a test with piuparts I noticed your package fails to upgrade from
> 'sid' to 'experimental'.
Good catch, thanks!
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Package: network-manager-gnome
Version: 1.30.0-1
Severity: serious
Justification: Policy 7.4
Dear Maintainer,
'network-manager-gnome' fails to install if libnma-common_1.10.2-1 is also
installed, as both provide the same file:
```
dpkg: error processing archive
/tmp/apt-dpkg-install-u13Ac3/157-
Control:
reassign -1 blueprint-compiler
affects -1 + hydrapaper
--
Greetings,
looking into the build log, I find this:
> Traceback (most recent call last):
> File "/usr/bin/blueprint-compiler", line 37, in
> from blueprintcompiler import main
> File "/usr/lib/python3/dist-packages/bl
ackaging fix (for #624130) and stayed there by inertia.
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
lue:
std::unique_ptr&& is
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
errors in the rare cases where its usage would be problematic.
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Control: fixed -1 2.6.1-1
Adrian Bunk writes:
> Makes sense.
Thanks.
> It would also be useful if fltk1.3 would FTBFS when an input file was
> not found.
Don't worry, I'm already planning to put in such a safeguard at this
point. Sorry for missing this possible failure mode earlier.
--
Aaron M
xport/*/FLTK-Targets-none.cmake \
Got it, thanks, though I'm inclined to use find(1) so I'm not
specifically tied to new cmake.
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
t have been to patch CMake's input, but I want to
make some across-the-board tweaks that are best centralized modulo this
sort of wrinkle.) I'll take a look when I get a chance.
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.
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
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 autopkgtest
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, 2022
The pam-chroot source code from Ed Schmollinger is currently at:
https://github.com/gpjt/pam-chroot
Maybe he is willing to create an GitHub Organization and add you as a
developer.
Or he even is willing switch to Salsa.
Kind regards
Matthias "Maddes" Bücher
tags 1016230 + pending
thanks.
> LN == Lucas Nussbaum [2022-7-29]
[...]
LN> During a rebuild of all packages in sid, your package failed to build
LN> on amd64.
Thanks for the report. It should be fixed by adding a
Build-Depends-Indep on texlive-latex-extra. I'll test and upload a
fixed pa
s I cannot
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 p
1 - 100 of 1111 matches
Mail list logo
