Hello, i did nmu because... 1) riscv64 porting is finishing and they need to
build as many packages as possible (this one was blocking a lot of packages) 2)
im in vac now for more than one week, and i wont have access to laptop or so
Sorry for the rush and indeed feel free to change everything as
Hi Nicholas,
Quoting Nicholas D Steeves (2023-09-16 14:06:00)
> Oh my, yes, it seems I forgot to add the new pipewire -dev package to the
> fluidsynth -dev package. 'not sure how that happened, but my mistake! Isn't
> only waiting 48h a bit rushed for an NMU though?
the number of delayed days a
Hi Gianfranco,
Oh my, yes, it seems I forgot to add the new pipewire -dev package to the
fluidsynth -dev package. 'not sure how that happened, but my mistake!
Isn't only waiting 48h a bit rushed for an NMU though? I can of course
import your fix and upload in the next 48h, and I'd like to improv
Control: tags 1051819 + patch
Control: tags 1051819 + pending
Dear maintainer,
I've prepared an NMU for fluidsynth (versioned as 2.3.3-2.1) and
uploaded it.
Regards.
diff -Nru fluidsynth-2.3.3/debian/changelog fluidsynth-2.3.3/debian/changelog
--- fluidsynth-2.3.3/debian/changelog 2023-09-13
Control: affects -1 + src:ardour src:blockattack src:calf src:chocolate-doom
src:crispy-doom src:denemo src:fluidsynth-dssi src:freedink src:frotz
src:gambas3 src:gargoyle-free src:gst-plugins-bad1.0 src:jag src:pianobooster
src:planetblupi src:qsynth src:qtads src:scummvm src:toppler src:ufoai
5 matches
Mail list logo