[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1035387: marked as done (csound: Regression from Bullseye: K opcodes not initialized at init time)

Your message dated Wed, 21 Aug 2024 10:34:22 +0000
with message-id <E1sgifW-00BIh9-4k@fasolo.debian.org>
and subject line Bug#1035387: fixed in csound 1:6.18.1+dfsg-3
has caused the Debian Bug report #1035387,
regarding csound: Regression from Bullseye: K opcodes not initialized at init time
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1035387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035387
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: csound
Version: 1:6.18.1+dfsg-1
Tags: fixed-upstream, upstream

See https://github.com/csound/csound/issues/1707

I'd like to NMU a fix once things settle down on the upstream side and
I'd like to file an unblock request (or a stable update request if
this misses the bookworm release).

I'm not a member of the multimedia team, but I am familiar with the csound packaging.
Are you okay with me doing an NMU and  submitting a merge request on salsa once we settle on a fix on the upstream github issue?

You can declare an opcode something like

opcode inittest,K,0

According o the docs, the output parameter is copied both at k-time
and at i-time.  It turns out in csound 6.14 (bullseye) it's always
copied at i-time even if declared as 'k' not 'K'.  But that in 6.18
it's only copied as k-time.  If you are using the opcode as a state
machine, triggering reinits, etc, that can totally break your
orchestra.

--- End Message ---
--- Begin Message --- 
Source: csound
Source-Version: 1:6.18.1+dfsg-3
Done: IOhannes m zmölnig (Debian/GNU) <umlaeute@debian.org>

We believe that the bug you reported is fixed in the latest version of
csound, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1035387@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU) <umlaeute@debian.org> (supplier of updated csound package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 21 Aug 2024 10:32:24 +0200
Source: csound
Architecture: source
Version: 1:6.18.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
Changed-By: IOhannes m zmölnig (Debian/GNU) <umlaeute@debian.org>
Closes: 1035387 1074894
Changes:
 csound (1:6.18.1+dfsg-3) unstable; urgency=medium
 .
   * Fix function signatures and types for liblo API (Closes: #1074894)
   * Cherry-pick upstream to initialize K-opcodes at init-time (Closes: #1035387)
   * Refresh patches with 'gbp pq'
Checksums-Sha1:
 a74b0edde0561c9271776646dde83380e74a50aa 3384 csound_6.18.1+dfsg-3.dsc
 08543fd40da3a089f323cbbdc4039b3899589dea 58000 csound_6.18.1+dfsg-3.debian.tar.xz
Checksums-Sha256:
 07747fdefa725d140dcaa78abe544c72735907ef75a2e0878ce328caa767927e 3384 csound_6.18.1+dfsg-3.dsc
 43377ca160ff1368b821d16c44efde928c15338070d2f8d01e423c10b6fe400d 58000 csound_6.18.1+dfsg-3.debian.tar.xz
Files:
 5e9758f62ed595c0876edb9c907656ee 3384 sound optional csound_6.18.1+dfsg-3.dsc
 80b9fced4afd678f160ceddf6f081dd6 58000 sound optional csound_6.18.1+dfsg-3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAmbFwFYACgkQtlAZxH96
NvibUw/8CSaEEAXRF0hS/TW7KkbaSmfXFw+YQSHNmCW/0HFIenLw3Kxwyb4KX4if
gLszUNlUxSnvyEkcUFEhMTfwPlKYhN8mqO8wNLM6hEgsHw46WBFzSWvQWljukUNf
AX2n4fpZZ3EDxxtFwEjUz1h2DMchJbbJ1+30cr4eqk6tXz3tqSTQSP9QdsxH9yd1
Z0IkDYftGg67TF6ZO09wki0GfU7nOQSt3mhJwne7a/R5XtS+TWUdyGAtd8t3b3pK
yNH+ntdwkRb+w2anksX+m/cjRhgM3PbwxkGl5zYHmHo6rFDo28Uu7h8RpbvfK2+0
PdyszH+aVUX9Nh99e/KMZ1t7D613aOjK70mS1qdVxUj6ioWQCFzEtkZpPHZPjBHa
biJV2E2wb9YhFRC2tGpJ2T+Xiqj5ovdLZy3llPQ6/uSpbxrr62Y8X21xpUMOd5Kf
6UhuuaphPhUDj1PIkYWiTBsaAL6aepk6QADYWKfvOYrKI3UEG+z/8pbKU58rmkci
z/2lp1N+OuwxARqqftmXMUiSy9pHVmkaCWtEb5s7UbA2xdxUohZgGYowa3PGHOi3
xZTSUZgBRcKwNMYolhU92PG3nZJdsucGBovqsG4L3gB2RCJXUU7tRUqZQ2pKzO6S
7HSbu/9OaaHJ63Yxgg1GC5oiieO9X8uqCYlflH/KvQlvEIQhT9w=
=46OO
-----END PGP SIGNATURE-----

Attachment: pgp9LY8fySPy7.pgp
Description: PGP signature


--- End Message ---
Reply to: