Bug#973736: buster-pu: package pulseaudio/12.2-4+deb10u2

[Felipe Sateler]

Hi Salvatore,

Sorry for the delay.


On Sun, Nov 22, 2020, 13:18 Salvatore Bonaccorso  wrote:

> hi stable release managers, hi Felipe,
>
> On Wed, Nov 04, 2020 at 09:33:21AM +0100, Salvatore Bonaccorso wrote:
> > Package: release.debian.org
> > Severity: normal
> > Tags: buster
> > User: release.debian@packages.debian.org
> > Usertags: pu
> > X-Debbugs-Cc: car...@debian.org,fsate...@debian.org
> >
> > Hi SRM, hi Felipe
> >
> > [ Reason ]
> >
> > pulseaudio's deamon.conf uses the (for that version of upstream) the
> > default of yes for flat-volumes. The flat-volumes value enables to
> > 'flat' volumes, the sink volume equal the maximum of the volumes of
> > the inputs connected to it. But this can cause quite some surprised
> > and problems and can hurt ears depending on e.g. headphones values.
> >
> > So some distributions have changed that already in past
> > and upstream did as well in later versions.
> >
> > In unstable the change was done in the 13.0-3 upload.
> >
> > [ Impact ]
> >
> > So far users probably stumpling over the problem have changed away
> > form the default in their configuration.
>
> Any comment on this proposed update? Although I completely see the
> point as it is changing a default in stable, I still wonder if we
> should do it because it has been switched upstream and was a problem
> several times for reporting user.
>


I don't think this change is in scope for a stable update. While I agree it
has been problematic for many users, and that this setting has great
relevance, this same impact makes me doubt it is fit for a stable update.

This is not a bugfix, it is a change in the default value of a setting.
Even if I agree with the new value, I don't think it is the sort of change
people expect in a stable update.

For the RT: this setting changes the behavior of the volume controls.
Current behavior in stable is to move the master volume along with the
loudest app volume (which creates the problem of a single app raising your
volume to very high levels). Current behavior in unstable is to decouple
them: app volume is now relative to the master volume.

This is all based on my understanding of how stable should remain stable. I
have no technical issue with backporting the setting change. Therefore, if
the release team deems the change in setting as appropriate, I won't object
(and very much welcome if you could upload it).

Saludos

Bug#944228: stretch-pu: package phpmyadmin/4:4.6.6-4+deb9u1

[Felipe Sateler]

On Wed, Nov 6, 2019 at 8:51 AM Adam D. Barratt 
wrote:

> Control: tags -1 + moreinfo
>
> On 2019-11-06 11:23, Felipe Sateler wrote:
> > This update fixes several security issues, plus an important bug.
> > Additionally we fix the metadata reflecting the maintainership change.
> >
> > Here is the changelog, with debdiff attached.
> >
> > phpmyadmin (4:4.6.6-4+deb9u1) stretch; urgency=medium
> >
> >   [ Matthias Blümel ]
> >   * Several security fixes
> > - Cross-site scripting (XSS) vulnerability in
> > db_central_columns.php
> >   (PMASA-2018-1, CVE-2018-7260, Closes: #893539)
> > - Remove transformation plugin includes
> >   (PMASA-2018-6, CVE-2018-19968)
> > - Fix Stored Cross-Site Scripting (XSS) in navigation tree
> >   (PMASA-2018-8, CVE-2018-19970)
> > - Fix information leak (arbitrary file read) using SQL queries
> >   (PMASA-2019-1, CVE-2019-6799, Closes: #920823)
> > - a specially crafted username can be used to trigger a SQL
> > injection attack
> >   (PMASA-2019-2, CVE-2019-6798, Closes: #920822)
> > - SQL injection in Designer feature
> >   (PMASA-2019-3, CVE-2019-11768, Closes: #930048)
> > - CSRF vulnerability in login form
> >   (PMASA-2019-4, CVE-2019-12616, Closes: #930017)
>
> According to the BTS and Security Tracker, at least some of these issues
> affect the package in unstable and aren't currently fixed there. Is that
> correct?
>

Yes, it is correct. This is because in unstable we are aiming for version
4.9, but we are waiting on some NEW packages for that upload to happen.


-- 

Saludos,
Felipe Sateler

Bug#944228: stretch-pu: package phpmyadmin/4:4.6.6-4+deb9u1

[Felipe Sateler]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

This update fixes several security issues, plus an important bug.
Additionally we fix the metadata reflecting the maintainership change.

Here is the changelog, with debdiff attached.

phpmyadmin (4:4.6.6-4+deb9u1) stretch; urgency=medium

  [ Matthias Blümel ]
  * Several security fixes
- Cross-site scripting (XSS) vulnerability in db_central_columns.php
  (PMASA-2018-1, CVE-2018-7260, Closes: #893539)
- Remove transformation plugin includes
  (PMASA-2018-6, CVE-2018-19968)
- Fix Stored Cross-Site Scripting (XSS) in navigation tree
  (PMASA-2018-8, CVE-2018-19970)
- Fix information leak (arbitrary file read) using SQL queries
  (PMASA-2019-1, CVE-2019-6799, Closes: #920823)
- a specially crafted username can be used to trigger a SQL injection attack
  (PMASA-2019-2, CVE-2019-6798, Closes: #920822)
- SQL injection in Designer feature
  (PMASA-2019-3, CVE-2019-11768, Closes: #930048)
- CSRF vulnerability in login form
  (PMASA-2019-4, CVE-2019-12616, Closes: #930017)
  * Set Vcs-* to point to salsa
  * Remove Thijs Kinkhorst and Michal Čihař from Uploaders. Thanks for all
your work!

  [ Juri Grabowski ]
  * Fix Vcs- URLs

  [ William Desportes ]
  * Add debian gitlab pipelines config.

  [ Felipe Sateler ]
  * Set phpMyAdmin team as Maintainer

  [ Michal Čihař ]
  * Fix open_basedir setting for PHP 7 (Closes: #867882).

  > This is the non-security fix. THe default config was not updated for
  > changes in the php-gettext path for 7.0.


 -- Felipe Sateler   Wed, 06 Nov 2019 08:12:18 -0300


Thanks for your consideration

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru phpmyadmin-4.6.6/debian/changelog phpmyadmin-4.6.6/debian/changelog
--- phpmyadmin-4.6.6/debian/changelog   2017-04-07 11:54:26.0 -0300
+++ phpmyadmin-4.6.6/debian/changelog   2019-11-06 08:12:18.0 -0300
@@ -1,3 +1,40 @@
+phpmyadmin (4:4.6.6-4+deb9u1) stretch; urgency=medium
+
+  [ Matthias Blümel ]
+  * Several security fixes
+- Cross-site scripting (XSS) vulnerability in db_central_columns.php
+  (PMASA-2018-1, CVE-2018-7260, Closes: #893539)
+- Remove transformation plugin includes
+  (PMASA-2018-6, CVE-2018-19968)
+- Fix Stored Cross-Site Scripting (XSS) in navigation tree
+  (PMASA-2018-8, CVE-2018-19970)
+- Fix information leak (arbitrary file read) using SQL queries
+  (PMASA-2019-1, CVE-2019-6799, Closes: #920823)
+- a specially crafted username can be used to trigger a SQL injection 
attack
+  (PMASA-2019-2, CVE-2019-6798, Closes: #920822)
+- SQL injection in Designer feature
+  (PMASA-2019-3, CVE-2019-11768, Closes: #930048)
+- CSRF vulnerability in login form
+  (PMASA-2019-4, CVE-2019-12616, Closes: #930017)
+  * Set Vcs-* to point to salsa
+  * Remove Thijs Kinkhorst and Michal Čihař from Uploaders. Thanks for all
+your work!
+
+  [ Juri Grabowski ]
+  * Fix Vcs- URLs
+
+  [ William Desportes ]
+  * Add debian gitlab pipelines config.
+
+  [ Felipe Sateler ]
+  * Set phpMyAdmin team as Maintainer
+
+  [ Michal Čihař ]
+  * Fix open_basedir setting for PHP 7 (Closes: #867882).
+
+
+ -- Felipe Sateler   Wed, 06 Nov 2019 08:12:18 -0300
+
 phpmyadmin (4:4.6.6-4) unstable; urgency=medium
 
   * Build depend on locales-all to ensure en_US.UTF-8 is available (see
diff -Nru phpmyadmin-4.6.6/debian/conf/apache.conf 
phpmyadmin-4.6.6/debian/conf/apache.conf
--- phpmyadmin-4.6.6/debian/conf/apache.conf2016-12-01 04:42:43.0 
-0300
+++ phpmyadmin-4.6.6/debian/conf/apache.conf2019-11-06 08:12:18.0 
-0300
@@ -29,7 +29,7 @@
 
 php_value include_path .
 php_admin_value upload_tmp_dir /var/lib/phpmyadmin/tmp
-php_admin_value open_basedir 
/usr/share/phpmyadmin/:/etc/phpmyadmin/:/var/lib/phpmyadmin/:/usr/share/php/php-gettext/:/usr/share/php/php-gettext/:/usr/share/javascript/:/usr/share/php/tcpdf/:/usr/share/doc/phpmyadmin/:/usr/share/php/phpseclib/
+php_admin_value open_basedir 
/usr/share/phpmyadmin/:/etc/phpmyadmin/:/var/lib/phpmyadmin/:/usr/share/php/php-gettext/:/usr/share/php/php-php-gettext/:/usr/share/javascript/:/usr/share/php/tcpdf/:/usr/share/doc/phpmyadmin/:/usr/share/php/phpseclib/
 php_admin_value mbstring.func_overload 0
 
 
diff -Nru phpmyadmin-4.6.6/debian/control phpmyadmin-4.6.6/debian/control
--- phpmyadmin-4.6.6/debian/c

Bug#933911: buster-pu: package pulseaudio

[Felipe Sateler]

On Tue, Aug 20, 2019 at 4:47 PM Adam D. Barratt 
wrote:

> Control: tags -1 + confirmed
>
> On Thu, 2019-08-15 at 11:28 -0400, Felipe Sateler wrote:
> > Control: tags -1 -moreinfo
> >
> > On Sun, Aug 11, 2019 at 9:53 AM Jonathan Wiltshire 
> > wrote:
> > > Control: tag -1 moreinfo
> > >
> > > Hi,
> > >
> > > On Sun, Aug 04, 2019 at 09:31:37PM -0400, Felipe Sateler wrote:
> [...]
> > > > There is a bug affecting pulseaudio users: #913102. This bug
> > > causes the
> > > > mute state to be incorrectly restored. Some users have asked for
> > > the fix
> > > > (which is now on unstable), to be backported to buster given that
> > > GDM is
> > > > affected by this bug. The upstream patch fixing this issue is
> > > very
> > > > small[1].
>
> Please go ahead; thanks.
>

Done, thank you

-- 

Saludos,
Felipe Sateler

Bug#887736: stretch-pu: package openvswitch/2.6.2~pre+git20161223-3

[Felipe Sateler]

On Tue, Aug 20, 2019 at 6:23 PM Adam D. Barratt 
wrote:

> Control: tags -1 + moreinfo
>
> On Fri, 2018-01-19 at 15:21 +0100, Thomas Goirand wrote:
> > I started maintaining OpenVSwitch long after the Stretch release, and
> > discovered #858418, which is very annoying for OpenVSwitch users.
> >
> > tl;dr: #858418 prevent anyone that has a valid
> > /etc/network/interfaces
> > with OpenVSwitch directive from having a working network at boot. The
> > init script uses a non-documented, not-to-be-used systemd internal,
> > which is miserably failing.
> >
> > After a long discussion with the bug reporter (which can be read on
> > the BTS), I came to the conclusion that he's right, and that the most
> > reasonable and safe way to fix the current situation is to apply the
> > patch he suggested (and which resulting debdiff I attached to this
> > bug).
>
> As I understand things, that fix swaps use of one systemd internal for
> another, which doesn't seem like a great plan.
>
> When this was discussed (some time ago) on IRC, one of the systemd
> maintainers essentially said "don't do that". With apologies for the
> delay in doing so, I've CCed the maintainer list to see if we can find
> a mutually acceptable solution.
>

Both `service` and `invoke-rc.d` wrappers have a few safeguards against
running in unwanted contexts. Have you tried using one of them?

-- 

Saludos,
Felipe Sateler

Bug#933911: buster-pu: package pulseaudio

[Felipe Sateler]

Control: tags -1 -moreinfo

On Sun, Aug 11, 2019 at 9:53 AM Jonathan Wiltshire  wrote:

> Control: tag -1 moreinfo
>
> Hi,
>
> On Sun, Aug 04, 2019 at 09:31:37PM -0400, Felipe Sateler wrote:
> > Package: release.debian.org
> > Severity: normal
> > Tags: buster
> > User: release.debian@packages.debian.org
> > Usertags: pu
> >
> > Dear release team,
> >
> > There is a bug affecting pulseaudio users: #913102. This bug causes the
> > mute state to be incorrectly restored. Some users have asked for the fix
> > (which is now on unstable), to be backported to buster given that GDM is
> > affected by this bug. The upstream patch fixing this issue is very
> > small[1].
> >
> > The full diff is attached.
>
> The attachment looks like the change as it was uploaded to sid; please
> prepare a proposed update to buster and attach a source debdiff and remove
> the moreinfo tag from this bug.
>

Please find the debdiff attached

-- 

Saludos,
Felipe Sateler
diff -Nru pulseaudio-12.2/debian/changelog pulseaudio-12.2/debian/changelog
--- pulseaudio-12.2/debian/changelog	2019-02-14 20:05:41.0 -0300
+++ pulseaudio-12.2/debian/changelog	2019-08-15 11:21:19.0 -0400
@@ -1,3 +1,10 @@
+pulseaudio (12.2-4+deb10u1) buster; urgency=medium
+
+  * Pick upstream patch fixing mute state restoring (Closes: #913102)
+  * Add gbp config for buster branch
+
+ -- Felipe Sateler   Thu, 15 Aug 2019 11:21:19 -0400
+
 pulseaudio (12.2-4) unstable; urgency=medium
 
   [ Jan Graichen ]
diff -Nru pulseaudio-12.2/debian/gbp.conf pulseaudio-12.2/debian/gbp.conf
--- pulseaudio-12.2/debian/gbp.conf	2019-02-14 20:05:41.0 -0300
+++ pulseaudio-12.2/debian/gbp.conf	2019-08-15 11:21:19.0 -0400
@@ -1,2 +1,3 @@
 [DEFAULT]
 pristine-tar = True
+debian-branch = debian/buster
diff -Nru pulseaudio-12.2/debian/patches/series pulseaudio-12.2/debian/patches/series
--- pulseaudio-12.2/debian/patches/series	2019-02-14 20:05:41.0 -0300
+++ pulseaudio-12.2/debian/patches/series	2019-08-15 11:21:19.0 -0400
@@ -2,3 +2,4 @@
 alsa-mixer-Update-to-support-Arctis-Pro-Wireless-headset.patch
 alsa-mixer-Add-support-for-2018-Arctis-7.patch
 Don-t-compile-with-ffast-math.patch
+sink-source-Don-t-change-suspend-cause-when-unlinking.patch
diff -Nru pulseaudio-12.2/debian/patches/sink-source-Don-t-change-suspend-cause-when-unlinking.patch pulseaudio-12.2/debian/patches/sink-source-Don-t-change-suspend-cause-when-unlinking.patch
--- pulseaudio-12.2/debian/patches/sink-source-Don-t-change-suspend-cause-when-unlinking.patch	1969-12-31 21:00:00.0 -0300
+++ pulseaudio-12.2/debian/patches/sink-source-Don-t-change-suspend-cause-when-unlinking.patch	2019-08-15 11:21:19.0 -0400
@@ -0,0 +1,47 @@
+From: Tanu Kaskinen 
+Date: Mon, 10 Jun 2019 14:18:47 +0300
+Subject: sink, source: Don't change suspend cause when unlinking
+
+See the added comments for why this is necessary.
+
+Fixes: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/667
+(cherry picked from commit 7fb85e0a5bfdec339fda9f7584f65cf9ddbd50a1)
+---
+ src/pulsecore/sink.c   | 6 +-
+ src/pulsecore/source.c | 6 +-
+ 2 files changed, 10 insertions(+), 2 deletions(-)
+
+diff --git a/src/pulsecore/sink.c b/src/pulsecore/sink.c
+index 38e8e50..4a0 100644
+--- a/src/pulsecore/sink.c
 b/src/pulsecore/sink.c
+@@ -760,7 +760,11 @@ void pa_sink_unlink(pa_sink* s) {
+ }
+ 
+ if (linked)
+-sink_set_state(s, PA_SINK_UNLINKED, 0);
++/* It's important to keep the suspend cause unchanged when unlinking,
++ * because if we remove the SESSION suspend cause here, the alsa sink
++ * will sync its volume with the hardware while another user is
++ * active, messing up the volume for that other user. */
++sink_set_state(s, PA_SINK_UNLINKED, s->suspend_cause);
+ else
+ s->state = PA_SINK_UNLINKED;
+ 
+diff --git a/src/pulsecore/source.c b/src/pulsecore/source.c
+index 02ae87a..c11d89b 100644
+--- a/src/pulsecore/source.c
 b/src/pulsecore/source.c
+@@ -702,7 +702,11 @@ void pa_source_unlink(pa_source *s) {
+ }
+ 
+ if (linked)
+-source_set_state(s, PA_SOURCE_UNLINKED, 0);
++/* It's important to keep the suspend cause unchanged when unlinking,
++ * because if we remove the SESSION suspend cause here, the alsa
++ * source will sync its volume with the hardware while another user is
++ * active, messing up the volume for that other user. */
++source_set_state(s, PA_SOURCE_UNLINKED, s->suspend_cause);
+ else
+ s->state = PA_SOURCE_UNLINKED;
+ 

Bug#933911: buster-pu: package pulseaudio

[Felipe Sateler]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

Dear release team,

There is a bug affecting pulseaudio users: #913102. This bug causes the
mute state to be incorrectly restored. Some users have asked for the fix
(which is now on unstable), to be backported to buster given that GDM is
affected by this bug. The upstream patch fixing this issue is very
small[1].

The full diff is attached.

[1] 
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/105/diffs?commit_id=7fb85e0a5bfdec339fda9f7584f65cf9ddbd50a1

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/debian/changelog b/debian/changelog
index 02916c2a1..1b9633855 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+pulseaudio (12.2-5) unstable; urgency=medium
+
+  * Pick upstream patch fixing mute state restoring (Closes: #913102)
+
+ -- Felipe Sateler   Sun, 04 Aug 2019 21:18:02 -0400
+
 pulseaudio (12.2-4) unstable; urgency=medium
 
   [ Jan Graichen ]
diff --git a/debian/patches/series b/debian/patches/series
index 3e43a7538..37a72b94f 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -2,3 +2,4 @@ volume-test.patch
 alsa-mixer-Update-to-support-Arctis-Pro-Wireless-headset.patch
 alsa-mixer-Add-support-for-2018-Arctis-7.patch
 Don-t-compile-with-ffast-math.patch
+sink-source-Don-t-change-suspend-cause-when-unlinking.patch
diff --git 
a/debian/patches/sink-source-Don-t-change-suspend-cause-when-unlinking.patch 
b/debian/patches/sink-source-Don-t-change-suspend-cause-when-unlinking.patch
new file mode 100644
index 0..efa780834
--- /dev/null
+++ b/debian/patches/sink-source-Don-t-change-suspend-cause-when-unlinking.patch
@@ -0,0 +1,47 @@
+From: Tanu Kaskinen 
+Date: Mon, 10 Jun 2019 14:18:47 +0300
+Subject: sink, source: Don't change suspend cause when unlinking
+
+See the added comments for why this is necessary.
+
+Fixes: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/667
+(cherry picked from commit 7fb85e0a5bfdec339fda9f7584f65cf9ddbd50a1)
+---
+ src/pulsecore/sink.c   | 6 +-
+ src/pulsecore/source.c | 6 +-
+ 2 files changed, 10 insertions(+), 2 deletions(-)
+
+diff --git a/src/pulsecore/sink.c b/src/pulsecore/sink.c
+index 38e8e50..4a0 100644
+--- a/src/pulsecore/sink.c
 b/src/pulsecore/sink.c
+@@ -760,7 +760,11 @@ void pa_sink_unlink(pa_sink* s) {
+ }
+ 
+ if (linked)
+-sink_set_state(s, PA_SINK_UNLINKED, 0);
++/* It's important to keep the suspend cause unchanged when unlinking,
++ * because if we remove the SESSION suspend cause here, the alsa sink
++ * will sync its volume with the hardware while another user is
++ * active, messing up the volume for that other user. */
++sink_set_state(s, PA_SINK_UNLINKED, s->suspend_cause);
+ else
+ s->state = PA_SINK_UNLINKED;
+ 
+diff --git a/src/pulsecore/source.c b/src/pulsecore/source.c
+index 02ae87a..c11d89b 100644
+--- a/src/pulsecore/source.c
 b/src/pulsecore/source.c
+@@ -702,7 +702,11 @@ void pa_source_unlink(pa_source *s) {
+ }
+ 
+ if (linked)
+-source_set_state(s, PA_SOURCE_UNLINKED, 0);
++/* It's important to keep the suspend cause unchanged when unlinking,
++ * because if we remove the SESSION suspend cause here, the alsa
++ * source will sync its volume with the hardware while another user is
++ * active, messing up the volume for that other user. */
++source_set_state(s, PA_SOURCE_UNLINKED, s->suspend_cause);
+ else
+ s->state = PA_SOURCE_UNLINKED;
+ 

Bug#886294: transition: nodejs

[Felipe Sateler]

On Thu, 4 Jan 2018 18:43:13 +0100 Emilio Pozuelo Monfort
 wrote:
> On 04/01/18 16:28, Jérémy Lal wrote:
> >
> >
> > 2018-01-04 12:09 GMT+01:00 Emilio Pozuelo Monfort  > >:
> >
> > Control: tags -1 confirmed
> >
> > On 04/01/18 02:40, Jérémy Lal wrote:
> > > Package: release.debian.org 
> > > Severity: normal
> > > User: release.debian@packages.debian.org
> > 
> > > Usertags: transition
> > >
> > > nodejs 8.9.3 brings the following improvements for debian:
> > > - a backported openssl 1.1.0 compatibility from nodejs 9.x branch
> > > - hard-to-debug segmentation faults fix (#878674)
> > > - it is an upstream LTS branch
> > >
> > > Julien Puydt and me checked all direct reverse build-deps and i
> > > took care of several issues that appeared with the update:
> > > - test failures caused by the move to openssl 1.1.0
> > > - failures caused by exception names changes in assert module
> > > - failures caused by api that was deprecated long ago then dropped
> > >
> > > There was no major issue with pure javascript modules and
> > > addons depending on nodejs-abi were rebuilt smoothly after the fixes.
> >
> > The ongoing nodejs transition to 6.12.0 hasn't been completed yet due 
> > to a build
> > failure on mips(el) and those segfaults. Given 8.9/experimental seems 
> > to fix all
> > those issues, let's go with that version.
> >
> >
> > Cool. Do you mean i should upload it to unstable now ?

For the record, Jérémy Lal uploaded nodejs a few days ago (although it
is not built on all archs yet, arm64 and armhf are missing).

Saludos

Bug#872023: transition: nodejs

[Felipe Sateler]

Hi,

On Tue, 15 Aug 2017 22:33:13 +0200 Emilio Pozuelo Monfort
 wrote:
> Control: forwarded -1 
> https://release.debian.org/transitions/html/nodejs-abi-48.html
> Control: tags -1 confirmed
>
> On 13/08/17 16:57, Jérémy Lal wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> >
> > Transition from nodejs 4 to nodejs 6, with module abi change from
> > version 46 to version 48.
> > All nodejs c++ addons (build-depending on nodejs-dev) must be rebuilt.
> >
> > Also Julien Puydt rebuilt all node modules packages against nodejs 6
> > to check for failures and report them:
> > - node-chai #868319 fixed upstream
> > - node-argparse #868294 might be fixed upstream
> > - node-evp-bytestokey fails and is deprecated. #868298
> >
> > Also i'm using nodejs 6 from experimental for some time now, and i don't
> > see breakage.
>
> Go ahead.
>

This was uploaded on Tuesday. I think binnmus need to be scheduled.

Thanks

Bug#865122: stretch-pu: package pulseaudio/10.0-1

[Felipe Sateler]

On Tue, Jun 27, 2017 at 9:18 PM, Cyril Brulebois <k...@debian.org> wrote:

> Control: tag -1 confirmed
>
> Felipe Sateler <fsate...@debian.org> (2017-06-27):
> > On Sun, Jun 25, 2017 at 4:56 PM, Cyril Brulebois <k...@debian.org>
> wrote:
> > > The rest looks good but I'd be happy to see an updated debdiff.
> > >
> >
> > Attached. Changed from the earlier diff is only the stable => stretch
> > change.
>
> Sorry for the extra round-trip, but that's usually better to catch
> possible issues early, instead of going through a REJECT once the
> package is in jessie-new…
>

No problem.


>
> (Sometimes the final source debdiff is also different from the
> announced git diff-based changes…)
>
> Feel free to upload; thanks.
>

 Uploaded  a couple days ago, I forgot to notify here though.

-- 

Saludos,
Felipe Sateler

Bug#865122: stretch-pu: package pulseaudio/10.0-1

[Felipe Sateler]

On Sun, Jun 25, 2017 at 4:56 PM, Cyril Brulebois <k...@debian.org> wrote:

> Hi,
>
> Felipe Sateler <fsate...@debian.org> (2017-06-19):
> > pulseaudio (10.0-1+deb9u1) stable; urgency=medium
> >
> >   [ Balint Reczey ]
> >   * Removing myself from Uploaders.
> >
> >   [ Scott Leggett ]
> >   * Move AGPL-3 text into copyright file (Closes: #863082)
> >
> >  -- Felipe Sateler <fsate...@debian.org>  Sun, 18 Jun 2017 12:03:31
> -0400
>
> Please use stretch if you target stretch (especially around the 17-18 of
> June, what “stable” means isn't exactly set in stone).
>

Thanks, I will do so next time.


>
> The rest looks good but I'd be happy to see an updated debdiff.
>

Attached. Changed from the earlier diff is only the stable => stretch
change.




-- 

Saludos,
Felipe Sateler
diff -Nru pulseaudio-10.0/debian/changelog pulseaudio-10.0/debian/changelog
--- pulseaudio-10.0/debian/changelog2017-01-19 20:49:55.0 -0300
+++ pulseaudio-10.0/debian/changelog2017-06-18 12:03:31.0 -0400
@@ -1,3 +1,17 @@
+pulseaudio (10.0-1+deb9u1) stretch; urgency=medium
+
+  [ Balint Reczey ]
+  * Removing myself from Uploaders.
+I made a few changes to the package when it badly needed help
+but now it is well maintained and I haven't contributed to it
+for years. Thanks to everyone in the packaging team and everyone
+who improved the package!
+
+  [ Scott Leggett ]
+  * Move AGPL-3 text into copyright file (Closes: #863082)
+
+ -- Felipe Sateler <fsate...@debian.org>  Sun, 18 Jun 2017 12:03:31 -0400
+
 pulseaudio (10.0-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru pulseaudio-10.0/debian/control pulseaudio-10.0/debian/control
--- pulseaudio-10.0/debian/control  2017-01-19 20:49:55.0 -0300
+++ pulseaudio-10.0/debian/control  2017-06-18 12:03:31.0 -0400
@@ -3,7 +3,6 @@
 Priority: optional
 Maintainer: Pulseaudio maintenance team 
<pkg-pulseaudio-de...@lists.alioth.debian.org>
 Uploaders: Sjoerd Simons <sjo...@debian.org>,
-Balint Reczey <bal...@balintreczey.hu>,
 Felipe Sateler <fsate...@debian.org>
 Build-Depends: debhelper (>= 9.20141010),
 check,
diff -Nru pulseaudio-10.0/debian/copyright pulseaudio-10.0/debian/copyright
--- pulseaudio-10.0/debian/copyright2017-01-19 20:49:55.0 -0300
+++ pulseaudio-10.0/debian/copyright2017-06-18 12:03:31.0 -0400
@@ -606,15 +606,664 @@
 Files: src/utils/qpaeq
 Copyright: 2009  Jason Newton <nev...@gmail.com>
 License: AGPL-3+
- This program is free software: you can redistribute it and/or modify
- it under the terms of the GNU Affero General Public License as
- published by the Free Software Foundation, either version 3 of the
- License, or (at your option) any later version.
- .
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
- GNU Affero General Public License for more details.
+ GNU AFFERO GENERAL PUBLIC LICENSE
+Version 3, 19 November 2007
  .
- On Debian systems, the complete text of the AGPL 3 can be found in
- /usr/share/doc/pulseaudio/AGPL
+  Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+  Everyone is permitted to copy and distribute verbatim copies
+  of this license document, but changing it is not allowed.
+ .
+ Preamble
+ .
+   The GNU Affero General Public License is a free, copyleft license for
+ software and other kinds of works, specifically designed to ensure
+ cooperation with the community in the case of network server software.
+ .
+   The licenses for most software and other practical works are designed
+ to take away your freedom to share and change the works.  By contrast,
+ our General Public Licenses are intended to guarantee your freedom to
+ share and change all versions of a program--to make sure it remains free
+ software for all its users.
+ .
+   When we speak of free software, we are referring to freedom, not
+ price.  Our General Public Licenses are designed to make sure that you
+ have the freedom to distribute copies of free software (and charge for
+ them if you wish), that you receive source code or can get it if you
+ want it, that you can change the software or use pieces of it in new
+ free programs, and that you know you can do these things.
+ .
+   Developers that use our General Public Licenses protect your rights
+ with two steps: (1) assert copyright on the software, and (2) offer
+ you this License which gives you legal permission to copy, distribute
+ and/or modify the software.
+ .
+   A secondary benefit of defending all users' freedom is that
+ improvements made in alternate versions of the program, if they
+ receive widespread use, become

Bug#865122: stretch-pu: package pulseaudio/10.0-1

[Felipe Sateler]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

I'd like to upload a RC fix for pulseaudio that couldn't make it to the
release. The changes are small and impact only package metadata.
Changelog is as follows:

pulseaudio (10.0-1+deb9u1) stable; urgency=medium

  [ Balint Reczey ]
  * Removing myself from Uploaders.

  [ Scott Leggett ]
  * Move AGPL-3 text into copyright file (Closes: #863082)

 -- Felipe Sateler <fsate...@debian.org>  Sun, 18 Jun 2017 12:03:31 -0400

Full debdiff is attached.

-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff --git a/debian/changelog b/debian/changelog
index 4ac5d4ec3..aeaec93f3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,17 @@
+pulseaudio (10.0-1+deb9u1) stable; urgency=medium
+
+  [ Balint Reczey ]
+  * Removing myself from Uploaders.
+I made a few changes to the package when it badly needed help
+but now it is well maintained and I haven't contributed to it
+for years. Thanks to everyone in the packaging team and everyone
+who improved the package!
+
+  [ Scott Leggett ]
+  * Move AGPL-3 text into copyright file (Closes: #863082)
+
+ -- Felipe Sateler <fsate...@debian.org>  Sun, 18 Jun 2017 12:03:31 -0400
+
 pulseaudio (10.0-1) unstable; urgency=medium
 
   * New upstream release
diff --git a/debian/control b/debian/control
index 4c48670f1..70fae9016 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,6 @@ Section: sound
 Priority: optional
 Maintainer: Pulseaudio maintenance team 
<pkg-pulseaudio-de...@lists.alioth.debian.org>
 Uploaders: Sjoerd Simons <sjo...@debian.org>,
-Balint Reczey <bal...@balintreczey.hu>,
 Felipe Sateler <fsate...@debian.org>
 Build-Depends: debhelper (>= 9.20141010),
 check,
diff --git a/debian/copyright b/debian/copyright
index ba94fc61c..141ef2910 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -606,15 +606,664 @@ License: LGPL-2.1+
 Files: src/utils/qpaeq
 Copyright: 2009  Jason Newton <nev...@gmail.com>
 License: AGPL-3+
- This program is free software: you can redistribute it and/or modify
- it under the terms of the GNU Affero General Public License as
- published by the Free Software Foundation, either version 3 of the
- License, or (at your option) any later version.
- .
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
- GNU Affero General Public License for more details.
- .
- On Debian systems, the complete text of the AGPL 3 can be found in
- /usr/share/doc/pulseaudio/AGPL
+ GNU AFFERO GENERAL PUBLIC LICENSE
+Version 3, 19 November 2007
+ .
+  Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+  Everyone is permitted to copy and distribute verbatim copies
+  of this license document, but changing it is not allowed.
+ .
+ Preamble
+ .
+   The GNU Affero General Public License is a free, copyleft license for
+ software and other kinds of works, specifically designed to ensure
+ cooperation with the community in the case of network server software.
+ .
+   The licenses for most software and other practical works are designed
+ to take away your freedom to share and change the works.  By contrast,
+ our General Public Licenses are intended to guarantee your freedom to
+ share and change all versions of a program--to make sure it remains free
+ software for all its users.
+ .
+   When we speak of free software, we are referring to freedom, not
+ price.  Our General Public Licenses are designed to make sure that you
+ have the freedom to distribute copies of free software (and charge for
+ them if you wish), that you receive source code or can get it if you
+ want it, that you can change the software or use pieces of it in new
+ free programs, and that you know you can do these things.
+ .
+   Developers that use our General Public Licenses protect your rights
+ with two steps: (1) assert copyright on the software, and (2) offer
+ you this License which gives you legal permission to copy, distribute
+ and/or modify the software.
+ .
+   A secondary benefit of defending all users' freedom is that
+ improvements made in alternate versions of the program, if they
+ receive widespread use, become available for other developers to
+ incorporate.  Many developers of free software are heartened and

Bug#859022: unblock: stk/4.5.2+dfsg-5

[Felipe Sateler]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hi,

Please unblock source package stk. The update fixes two RC bugs:

 * Use debian RAWWAVE_PATH in stk-demo. (Closes: #858895)
 * Fix link targets for RtAudio and RtMidi header files (Closes: #858957)


Attached is the debdiff between -4 and -5

unblock stk/4.5.2+dfsg-5

-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru stk-4.5.2+dfsg/debian/changelog stk-4.5.2+dfsg/debian/changelog
--- stk-4.5.2+dfsg/debian/changelog 2016-12-24 15:15:56.0 -0300
+++ stk-4.5.2+dfsg/debian/changelog 2017-03-29 10:39:43.0 -0300
@@ -1,3 +1,10 @@
+stk (4.5.2+dfsg-5) unstable; urgency=medium
+
+  * Use debian RAWWAVE_PATH in stk-demo. (Closes: #858895)
+  * Fix link targets for RtAudio and RtMidi header files (Closes: #858957)
+
+ -- Felipe Sateler <fsate...@debian.org>  Wed, 29 Mar 2017 10:39:43 -0300
+
 stk (4.5.2+dfsg-4) unstable; urgency=medium
 
   [ Petter Reinholdtsen ]
diff -Nru stk-4.5.2+dfsg/debian/libstk0-dev.links 
stk-4.5.2+dfsg/debian/libstk0-dev.links
--- stk-4.5.2+dfsg/debian/libstk0-dev.links 2016-12-24 15:15:56.0 
-0300
+++ stk-4.5.2+dfsg/debian/libstk0-dev.links 2017-03-29 10:39:43.0 
-0300
@@ -1,2 +1,2 @@
-usr/include/RtAudio.h usr/include/stk/RtAudio.h
-usr/include/RtMidi.h usr/include/stk/RtMidi.h
+usr/include/rtaudio/RtAudio.h usr/include/stk/RtAudio.h
+usr/include/rtmidi/RtMidi.h usr/include/stk/RtMidi.h
diff -Nru 
stk-4.5.2+dfsg/debian/patches/demo-use-RAWWAVE_PATH-instead-of-hardcoded-string.patch
 
stk-4.5.2+dfsg/debian/patches/demo-use-RAWWAVE_PATH-instead-of-hardcoded-string.patch
--- 
stk-4.5.2+dfsg/debian/patches/demo-use-RAWWAVE_PATH-instead-of-hardcoded-string.patch
   1969-12-31 21:00:00.0 -0300
+++ 
stk-4.5.2+dfsg/debian/patches/demo-use-RAWWAVE_PATH-instead-of-hardcoded-string.patch
   2017-03-29 10:39:43.0 -0300
@@ -0,0 +1,21 @@
+From: Felipe Sateler <fsate...@debian.org>
+Date: Wed, 29 Mar 2017 10:28:40 -0300
+Subject: demo: use RAWWAVE_PATH instead of hardcoded string
+
+---
+ projects/demo/demo.cpp | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/projects/demo/demo.cpp b/projects/demo/demo.cpp
+index c877b4a..3e74769 100644
+--- a/projects/demo/demo.cpp
 b/projects/demo/demo.cpp
+@@ -213,7 +213,7 @@ int main( int argc, char *argv[] )
+ 
+   // Depending on how you compile STK, you may need to explicitly set
+   // the path to the rawwave directory.
+-  Stk::setRawwavePath( "../../rawwaves/" );
++  Stk::setRawwavePath( RAWWAVE_PATH );
+ 
+   // By default, warning messages are not printed.  If we want to see
+   // them, we need to specify that here.
diff -Nru stk-4.5.2+dfsg/debian/patches/series 
stk-4.5.2+dfsg/debian/patches/series
--- stk-4.5.2+dfsg/debian/patches/series2016-12-24 15:15:56.0 
-0300
+++ stk-4.5.2+dfsg/debian/patches/series2017-03-29 10:39:43.0 
-0300
@@ -7,3 +7,4 @@
 demo-needs-rt.patch
 Sort-o-files
 Do-not-override-user-supplied-CXXFLAGS.patch
+demo-use-RAWWAVE_PATH-instead-of-hardcoded-string.patch

Re: Bug#856487: pulseaudio: SIGSEGV upon streaming to bluetooth headset

[Felipe Sateler]

Control: retitle -1 libsbc1: compiling with gcc > 4.9 causes stack corruption

On Fri, Mar 3, 2017 at 3:24 PM, Linus Lüssing <linus.luess...@c0d3.blue> wrote:
> On Fri, Mar 03, 2017 at 01:14:56PM -0300, Felipe Sateler wrote:
>> It has been pointed out to me that this may be unrelated to PIE, but
>> just caused by a newer GCC version. Could you check if disabling PIE
>> makes the binary work again? To do so:
>>
>> apt-get source sbc
>> sudo apt-get build-dep sbc
>> cd sbc-1.3
>> DEB_BUILD_OPTIONS=hardening=-pie dpkg-buildpackage -us -uc
>> sudo dpkg -i ../libsbc1_*.deb
>
> Tried it, but still crashes. I also tried:
>
> 0) dpkg-buildpackage -us -uc
> 1) 
> DEB_BUILD_OPTIONS=hardening=-stackprotectorstrong,-stackprotector,-pie,-fortify
>  dpkg-buildpackage -us -uc
> 2) DEB_BUILD_OPTIONS=hardening=-all dpkg-buildpackage -us -uc
> 3) CC=gcc-5 dpkg-buildpackage -us -uc
>
> But the resulting packages/libraries crash, too.
>
> ~~~
> $ gcc --version
> gcc (Debian 6.3.0-8) 6.3.0 20170221
> $ gcc-5 --version
> gcc-5 (Debian 5.4.1-5) 5.4.1 20170205
> ~~~
>
> What seems to work though:
> ~~~
> $ CC=clang dpkg-buildpackage -us -uc
> [...]
> $ sudo dpkg -i ../libsbc1_*.deb
> ~~~

Thanks for verifying! The problem would not be PIE then. It appears
the custom assembler is not compatible with current gcc versions.

-- 

Saludos,
Felipe Sateler

Re: Bug#856487: pulseaudio: SIGSEGV upon streaming to bluetooth headset

[Felipe Sateler]

On Fri, Mar 3, 2017 at 11:06 AM, Felipe Sateler <fsate...@debian.org> wrote:
> Control: tags -1 - help
> Control: reassign -1 libsbc1 1.3-1+b2
> Control: retitle -1 libsbc1: build with PIE causes stack corruption
> Control: affects -1 pulseaudio
> Control: severity -1 serious
>
>
> On Fri, Mar 3, 2017 at 10:52 AM, Linus Lüssing <linus.luess...@c0d3.blue> 
> wrote:
>> On Thu, Mar 02, 2017 at 08:36:29PM -0300, Felipe Sateler wrote:
>>> Indeed. However, from what I can see the most likely (only?) way to
>>> get there is via a sbc_encode that is called in module-bluez5-device.
>>> However, that part of the code does not look changed since 9.0. Have
>>> you confirmed downgrading to 9.0 fixes the issue?
>>
>> Oh, sorry, good point. I think we are narrowing it down now:
>>
>> It's actually not the pulsaudio upgrade from 9.0 to 10 but the
>> update of libsbc1 from 1.3-1 to 1.3-1+b2, which I did during the
>> same "apt-get dist-upgrade".
>>
>> Downgrading libsbc1 to 1.3-1 is enough to make the crash vanish!
>
> OK. That rebuild was done to enable PIE. So it looks like PIE
> conflicts with the hand-written asm code, at least for armhf. It seems
> to me PIE will have to be disabled there.

It has been pointed out to me that this may be unrelated to PIE, but
just caused by a newer GCC version. Could you check if disabling PIE
makes the binary work again? To do so:

apt-get source sbc
sudo apt-get build-dep sbc
cd sbc-1.3
DEB_BUILD_OPTIONS=hardening=-pie dpkg-buildpackage -us -uc
sudo dpkg -i ../libsbc1_*.deb


Fortunately the library is small so it shouldn't take that long to build.

-- 

Saludos,
Felipe Sateler

Re: Bug#856487: pulseaudio: SIGSEGV upon streaming to bluetooth headset

[Felipe Sateler]

Control: tags -1 - help
Control: reassign -1 libsbc1 1.3-1+b2
Control: retitle -1 libsbc1: build with PIE causes stack corruption
Control: affects -1 pulseaudio
Control: severity -1 serious


On Fri, Mar 3, 2017 at 10:52 AM, Linus Lüssing <linus.luess...@c0d3.blue> wrote:
> On Thu, Mar 02, 2017 at 08:36:29PM -0300, Felipe Sateler wrote:
>> Indeed. However, from what I can see the most likely (only?) way to
>> get there is via a sbc_encode that is called in module-bluez5-device.
>> However, that part of the code does not look changed since 9.0. Have
>> you confirmed downgrading to 9.0 fixes the issue?
>
> Oh, sorry, good point. I think we are narrowing it down now:
>
> It's actually not the pulsaudio upgrade from 9.0 to 10 but the
> update of libsbc1 from 1.3-1 to 1.3-1+b2, which I did during the
> same "apt-get dist-upgrade".
>
> Downgrading libsbc1 to 1.3-1 is enough to make the crash vanish!

OK. That rebuild was done to enable PIE. So it looks like PIE
conflicts with the hand-written asm code, at least for armhf. It seems
to me PIE will have to be disabled there.

-- 

Saludos,
Felipe Sateler

Bug#845304: transition: libxtables12

[Felipe Sateler]

On Tue, 22 Nov 2016 09:29:26 + Simon McVittie  wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-Cc: iptab...@packages.debian.org
> Forwarded: https://release.debian.org/transitions/html/auto-iptables.html
>
> src:iptables contains libxtables, which bumped SONAME recently,
> starting a small uncoordinated transition. For extra confusion,
> libxtables.so.12 was briefly shipped in libxtables11 (#844755);
> after that was fixed, until today's upload, libxtables12 was missing
> the required Breaks/Replaces to take over libxtables.so.12 from
> the versions of libxtables11 that suffered from #844755 (#845278).
>
> At a minimum, this is going to need a round of binNMUs to get
> everything correctly depending on libxtables12.
>
> The auto-generated
> 
> appears to be correct, or here is what reportbug suggested:
>
> title = "libxtables12";
> is_affected = .depends ~ "libxtables11" | .depends ~ "libxtables12";
> is_good = .depends ~ "libxtables12";
> is_bad = .depends ~ "libxtables11";


No idea how to express this in ben syntax, but  Recommends need to be
looked at too. iproute2 has some modules depend on libxtables
(optional, and thus Recommends, not Depends).

Saludos

Bug#810761: wheezy-pu: package stk/4.4.3-2

[Felipe Sateler]

On 14 Jan 2016 20:14, "Adam D. Barratt" <a...@adam-barratt.org.uk> wrote:
>
> Control: tags -1 + pending
>
> On Mon, 2016-01-11 at 21:28 -0300, Felipe Sateler wrote:
> > This update fixes bug 805549 on wheezy. This bug makes the dev package
> > useless for certain uses. Package is uploaded to p-u, diff is attached.
>
> Flagged for acceptance.

Thanks!

Re: Bug#805549: Patch for strech, jessie, wheezy

[Felipe Sateler]

On 12 Jan 2016 03:08, "Adam D. Barratt" <a...@adam-barratt.org.uk> wrote:
>
> On Tue, 2015-12-15 at 13:18 +, Adam D. Barratt wrote:
> > On 2015-12-15 13:04, Felipe Sateler wrote:
> > > Hi,
> > >
> > > Dear release team, I'm copying you to ask if the attached patch would
> > > be OK to upload to stable/oldstable, fixes bug #805549. This error
> > > makes some builds against stk impossible, since there are two headers
> > > missing.
> > >
> > > The version in unstable is a different upstream version, so the patch
> > > is not exactly the same (attached is a patch on a patch, currently we
> > > patch the real file, as the previous patch was accepted upstream).
> >
> > In isolation, the patch looks okay. In order to get approval for actual
> > uploads for stable and oldstable, however, please open a p-u bug for
> > each, including a full source debdiff for a package built and tested on
> > that distribution.
>
> I note that there are now #810760 and #810761. For future reference,
> "[i]n order to get approval", implied opening the bugs _before_ the
> uploads, not afterwards.

Oops. Sorry, will do correctly next time. I suppose I somehow let "built
and tested" also include "uploaded".

Saludos

Bug#810760: jessie-pu: package stk/4.4.4-5

[Felipe Sateler]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

This fixes bug 805549 in jessie. This bug makes the dev package useless
in certain conditions.

Package is already uploaded to p-u, diff is attached.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff --git a/debian/changelog b/debian/changelog
index 258ec0c..2a73017 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+stk (4.4.4-5+deb8u1) jessie; urgency=medium
+
+  [ Hanno Zulla ]
+  * Install missing SKINI.{msg,tbl} include files
+
+ -- Felipe Sateler <fsate...@debian.org>  Fri, 18 Dec 2015 16:33:16 -0300
+
 stk (4.4.4-5) unstable; urgency=medium
 
   * Prepare for new rtaudio and rtmidi
diff --git a/debian/gbp.conf b/debian/gbp.conf
index cec628c..0e268a7 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -1,2 +1,3 @@
 [DEFAULT]
 pristine-tar = True
+debian-branch = debian/jessie
diff --git a/debian/patches/01-makefile.patch b/debian/patches/01-makefile.patch
index 3452268..7fb1106 100644
--- a/debian/patches/01-makefile.patch
+++ b/debian/patches/01-makefile.patch
@@ -64,7 +64,7 @@ Forwarded: no
  
 +install-headers:
 +	install -d $(DESTDIR)/usr/include/stk
-+	cp -r ../include/*.h $(DESTDIR)/usr/include/stk
++	cp -r ../include/* $(DESTDIR)/usr/include/stk
 +
 +install: $(SHAREDLIB) install-headers
 +	install -d  $(DESTDIR)/usr/share/stk
diff --git a/debian/rules b/debian/rules
index 4096934..b309804 100755
--- a/debian/rules
+++ b/debian/rules
@@ -34,6 +34,9 @@ override_dh_auto_configure:
 	mkdir -p src/Release
 	mkdir -p projects/demo/Release
 
+override_dh_auto_install:
+	dh_auto_install
+	rm -f debian/tmp/usr/include/stk/*.bak
 
 override_dh_link:
 	dh_link

Bug#810761: wheezy-pu: package stk/4.4.3-2

[Felipe Sateler]

Package: release.debian.org
Severity: normal
Tags: wheezy
User: release.debian@packages.debian.org
Usertags: pu

This update fixes bug 805549 on wheezy. This bug makes the dev package
useless for certain uses. Package is uploaded to p-u, diff is attached.


Saludos

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff --git a/debian/changelog b/debian/changelog
index 1b2036a..820f37b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+stk (4.4.3-2+deb7u1) wheezy; urgency=medium
+
+  [ Hanno Zulla ]
+  * Install missing SKINI.{msg,tbl} include files
+
+ -- Felipe Sateler <fsate...@debian.org>  Fri, 18 Dec 2015 16:41:38 -0300
 stk (4.4.3-2) unstable; urgency=low
 
   [ Felipe Sateler ]
diff --git a/debian/gbp.conf b/debian/gbp.conf
index cec628c..d3f1da8 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -1,2 +1,4 @@
 [DEFAULT]
 pristine-tar = True
+debian-branch = debian/wheezy
+
diff --git a/debian/patches/01-makefile.patch b/debian/patches/01-makefile.patch
index 26fa351..db34483 100644
--- a/debian/patches/01-makefile.patch
+++ b/debian/patches/01-makefile.patch
@@ -64,7 +64,7 @@ Forwarded: no
  
 +install-headers:
 +	install -d $(DESTDIR)/usr/include/stk
-+	cp -r ../include/*.h $(DESTDIR)/usr/include/stk
++	cp -r ../include/* $(DESTDIR)/usr/include/stk
 +
 +install: $(SHAREDLIB) install-headers
 +	install -d  $(DESTDIR)/usr/share/stk
diff --git a/debian/rules b/debian/rules
index f6a9bb8..809929b 100755
--- a/debian/rules
+++ b/debian/rules
@@ -21,6 +21,10 @@ override_dh_auto_configure:
 	dh_auto_configure -- $(CONFIGURE_FLAGS)
 	mkdir -p src/Release
 
+override_dh_auto_install:
+	dh_auto_install
+	rm -f debian/tmp/usr/include/stk/*.bak
+
 override_dh_installchangelogs:
 	dh_installchangelogs doc/ReleaseNotes.txt
 

Re: Bug#805549: Patch for strech, jessie, wheezy

[Felipe Sateler]

Hi,

Dear release team, I'm copying you to ask if the attached patch would
be OK to upload to stable/oldstable, fixes bug #805549. This error
makes some builds against stk impossible, since there are two headers
missing.

The version in unstable is a different upstream version, so the patch
is not exactly the same (attached is a patch on a patch, currently we
patch the real file, as the previous patch was accepted upstream).
However, it is functionally the same[1].

[1] 
http://anonscm.debian.org/cgit/pkg-multimedia/stk.git/tree/debian/patches/0006-Install-missing-include-files-SKINI.msg-and-SKINI.tb.patch

On 15 December 2015 at 06:38, Hanno Zulla <a...@hanno.de> wrote:
> Hi,
>
> thanks for fixing this in sid's package. I can confirm that it works to
> package supercollider-sc3-plugins.
>
> It would be beneficial if this could be fixed for
>
> strech

This will make it automatically in a few days.

> jessie
> wheezy

These won't, we need release team ACK for this.

> too. Why even back to wheezy? Because supercollider-sc3-plugins is also
> meant to be used by Raspbian, which is packaging their distribution
> based on wheezy and jessie.
>
> Please find an attached patch which will fix this for all three versions
> of the current Debian source package.

-- 

Saludos,
Felipe Sateler
*** stk-4.4.4/debian/patches/01-makefile.patch	2015-09-21 19:17:01.0 +0200
--- stk-4.4.4.patched/debian/patches/01-makefile.patch	2015-12-15 10:19:37.320848851 +0100
***
*** 64,70 
   
  +install-headers:
  +	install -d $(DESTDIR)/usr/include/stk
! +	cp -r ../include/*.h $(DESTDIR)/usr/include/stk
  +
  +install: $(SHAREDLIB) install-headers
  +	install -d  $(DESTDIR)/usr/share/stk
--- 64,70 
   
  +install-headers:
  +	install -d $(DESTDIR)/usr/include/stk
! +	cp -r ../include/* $(DESTDIR)/usr/include/stk
  +
  +install: $(SHAREDLIB) install-headers
  +	install -d  $(DESTDIR)/usr/share/stk

Bug#807621: transition: stk

[Felipe Sateler]

On 10 December 2015 at 20:56, Emilio Pozuelo Monfort <po...@debian.org> wrote:
> Control: tags -1 confirmed
>
> On 11/12/15 00:44, Felipe Sateler wrote:
>> A transition is needed for stk. I have confirmed that both rdeps, csound
>> and lmms, build with the new version that I am about to upload. The
>> package has already gone through binNEW and is in experimental.
>
> Go ahead.

Thanks. Uploaded


-- 

Saludos,
Felipe Sateler

Bug#807621: transition: stk

[Felipe Sateler]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hi,

A transition is needed for stk. I have confirmed that both rdeps, csound
and lmms, build with the new version that I am about to upload. The
package has already gone through binNEW and is in experimental.


Ben file:

title = "stk";
is_affected = .depends ~ "libstk0v5" | .depends ~ "libstk-4.5.0";
is_good = .depends ~ "libstk-4.5.0";
is_bad = .depends ~ "libstk0v5";


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Re: Bug#797463: M-A:same package is broken by binnmu; please do a sourceful upload

[Felipe Sateler]

Control: reassign -1 release.debian.org

On 8 September 2015 at 07:26, Ralf Jung <p...@ralfj.de> wrote:
> This is currently blocking the gcc5 transition from being installed on
> i386-amd64 systems having ffmpeg installed - by far not an uncommon
> setup. As a consequence, I can't install any system update currently.
> For example, I remain vulnerable to critical security issues uncovered
> in iceweasel due to this bug in ffmpeg. Please consider to fix this
> situation ASAP, either by doing a binNMU on i386 (bringing the version
> numbers back in sync) or by doing a sourceful upload.
>
> On a more general note, is there any solution in sight to the issue of
> binNMUs breaking MS:same packages? Really, all binNMUs issued for such
> packages *must* involve all architectures, until a better solution is found.

Dear release team, please schedule binnmus to fix multiarch
coinstallability of ffmpeg.

nmu ffmpeg_7:2.7.2-1 . ANY . -m 'allow co-installs with binnmu-ed ffmpeg'

I don't know if that will cause a +b2 to be built on amd64 and mips*,
though, so:

nmu ffmpeg_7:2.7.2-1 . arm64 armel armhf hurd-any kfreebsd-any powerpc
powerpcspe ppc64 ppc64el s390x sh4 sparc64 x32 . -m 'allow co-installs
with binnmu-ed ffmpeg'


-- 

Saludos,
Felipe Sateler

Bug#791290: sndobj: library transition may be needed when GCC 5 is the default

[Felipe Sateler]

On 25 August 2015 at 04:00, Simon McVittie <s...@debian.org> wrote:
> On Fri, 07 Aug 2015 at 13:22:49 -0300, Felipe Sateler wrote:
>> Sndobj requires a transition. Renamed package has been uploaded to
>> experimental and is in NEW.
>
> Since sndobj does not appear to build-depend on any libraries that need a
> transition, I believe it can be uploaded to unstable any time.

Uploaded to unstable.

-- 

Saludos,
Felipe Sateler

Re: Bug#791014: csound: library transition may be needed when GCC 5 is the default

[Felipe Sateler]

Control: reopen -1
Control: user release.debian@packages.debian.org
Control: usertag -1 + transition
Control: block -1 by 790756
Control: reassign -1 release.debian.org
Control: retitle -1 transition: csound (GCC 5)

On 3 July 2015 at 10:09, Matthias Klose d...@debian.org wrote:
 Package: src:csound
 Version: 6.05~dfsg1-2
 Severity: important
 Tags: sid stretch
 User: debian-...@lists.debian.org
 Usertags: libstdc++-cxx11

 Background [1]: libstdc++6 introduces a new ABI to conform to the
 C++11 standard, but keeps the old ABI to not break existing binaries.
 Packages which are built with g++-5 from experimental (not the one
 from testing/unstable) are using the new ABI.  Libraries built from
 this source package export some of the new __cxx11 or B5cxx11 symbols,
 and dropping other symbols.  If these symbols are part of the API of
 the library, then this rebuild with g++-5 will trigger a transition
 for the library.

 What is needed:

  - Rebuild the library using g++/g++-5 from experimental. Note that
most likely all C++ libraries within the build dependencies need
a rebuild too. You can find the log for a rebuild in
  https://people.debian.org/~doko/logs/gcc5-20150701/
Search for BEGIN GCC CXX11 in the log.

  - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
library API, and are used by the reverse dependencies of the
library.

  - If there are no symbols matching __cxx11 or B5cxx11 in the symbols
forming the library API, you should close this issue with a short
explanation.

  - If there are no reverse dependencies, it should be the package
maintainers decision if a transition is needed.  However this might
break software which is not in the Debian archive, and built
against these packages.

  - If a library transition is needed, please prepare for the change.
Rename the library package, append v5 to the name of the package
(e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you
have a soversion bump and you upload this version instead of the
renamed package.  Prepare a patch and attach it to this issue (mark
this issue with patch), so that it is possible to NMU such a
package. We'll probably have more than hundred transitions
triggered. Then reassign the issue to release.debian.org and
properly tag it as a transition issue, by sending an email to
cont...@bugs.debian.org:

  user release.debian@packages.debian.org
  usertag this issue + transition
  block this issue by 790756
  reassign this issue release.debian.org

The changed package has been uploaded to experimental, and I have
verified the only reverse dep (csoundqt) builds with it.


-- 

Saludos,
Felipe Sateler


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAAfdZj_q8JjGD80o3mh-XcnEevii1fAHqA6=bbhdd64vepu...@mail.gmail.com

Bug#785478: jessie-pu: package node-groove/2.2.6-1

[Felipe Sateler]

On 23 May 2015 at 05:09, Adam D. Barratt a...@adam-barratt.org.uk wrote:
 Control: tags -1 -moreinfo +confirmed

 On Mon, 2015-05-18 at 10:47 -0300, Felipe Sateler wrote:
 On 16 May 2015 at 17:31, Adam D. Barratt a...@adam-barratt.org.uk wrote:
  Control: tags -1 + moreinfo
 
  On Sat, 2015-05-16 at 17:16 -0300, Felipe Sateler wrote:
  Node-groove has a bug that is pretty annoying: a missing check in a loop
  causes an almost-tight loop to run as long as an encoder object is
  attached. More details at the upstream tracker[1]. This is not a
  dealbreaker on multicore machines, but it is still annoying and pretty
  bad in single-core machines.
 
  We think the smallness of the fix and the greatness of the improvement
  makes it good for a stable update.
 
  It may well be, but it needs to be fixed in unstable first.

 The fix in unstable was delayed because Andrew is working on getting
 the new upstream version of node-groove ready. This includes way more
 than just the above fix (and requires new upstream versions of
 dependencies).

 Anyhow, I have uploaded the fix to unstable. The upload should be
 essentially the same as the upload in unstable, modulo the version
 string.

 Please go ahead.

Thanks. Uploaded now.

-- 

Saludos,
Felipe Sateler


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/caafdzj83jstu4qhtf_k37flhvevzbgf2r5ajfhtbuo+8yu+...@mail.gmail.com

Bug#785478: jessie-pu: package node-groove/2.2.6-1

[Felipe Sateler]

On 16 May 2015 at 17:31, Adam D. Barratt a...@adam-barratt.org.uk wrote:
 Control: tags -1 + moreinfo

 On Sat, 2015-05-16 at 17:16 -0300, Felipe Sateler wrote:
 Node-groove has a bug that is pretty annoying: a missing check in a loop
 causes an almost-tight loop to run as long as an encoder object is
 attached. More details at the upstream tracker[1]. This is not a
 dealbreaker on multicore machines, but it is still annoying and pretty
 bad in single-core machines.

 We think the smallness of the fix and the greatness of the improvement
 makes it good for a stable update.

 It may well be, but it needs to be fixed in unstable first.

The fix in unstable was delayed because Andrew is working on getting
the new upstream version of node-groove ready. This includes way more
than just the above fix (and requires new upstream versions of
dependencies).

Anyhow, I have uploaded the fix to unstable. The upload should be
essentially the same as the upload in unstable, modulo the version
string.

-- 

Saludos,
Felipe Sateler


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/caafdzj-_c0hw52to8yywhd67v1xg7saufp8gtzo4ie-k-wn...@mail.gmail.com

Bug#785478: jessie-pu: package node-groove/2.2.6-1

[Felipe Sateler]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

Dear release team,

Node-groove has a bug that is pretty annoying: a missing check in a loop
causes an almost-tight loop to run as long as an encoder object is
attached. More details at the upstream tracker[1]. This is not a
dealbreaker on multicore machines, but it is still annoying and pretty
bad in single-core machines.

We think the smallness of the fix and the greatness of the improvement
makes it good for a stable update. Please find attached the full diff
for the proposed upload.


[1] https://github.com/andrewrk/groovebasin/issues/319

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff --git a/debian/changelog b/debian/changelog
index 1e510e0..fc1c49f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+node-groove (2.2.6-1+deb8u1) UNRELEASED; urgency=medium
+
+  * Backport patch to fix cpu usage
+
+ -- Felipe Sateler fsate...@debian.org  Fri, 15 May 2015 19:05:19 -0300
+
 node-groove (2.2.6-1) unstable; urgency=low
 
   * Update to upstream 2.2.6
diff --git a/debian/gbp.conf b/debian/gbp.conf
new file mode 100644
index 000..fae4302
--- /dev/null
+++ b/debian/gbp.conf
@@ -0,0 +1,2 @@
+[DEFAULT]
+debian-branch = jessie
diff --git a/debian/patches/0001-fix-emitting-buffer-event-too-often.patch b/debian/patches/0001-fix-emitting-buffer-event-too-often.patch
new file mode 100644
index 000..bbc5cb6
--- /dev/null
+++ b/debian/patches/0001-fix-emitting-buffer-event-too-often.patch
@@ -0,0 +1,62 @@
+From: Andrew Kelley superjo...@gmail.com
+Date: Thu, 14 May 2015 09:28:25 -0700
+Subject: fix emitting 'buffer' event too often
+
+no longer burns the CPU
+---
+ src/gn_encoder.cc | 15 +--
+ src/gn_encoder.h  |  1 +
+ 2 files changed, 14 insertions(+), 2 deletions(-)
+
+diff --git a/src/gn_encoder.cc b/src/gn_encoder.cc
+index 0791292..474141f 100644
+--- a/src/gn_encoder.cc
 b/src/gn_encoder.cc
+@@ -93,7 +93,10 @@ static void EventThreadEntry(void *arg) {
+ GNEncoder::EventContext *context = reinterpret_castGNEncoder::EventContext *(arg);
+ while (groove_encoder_buffer_peek(context-encoder, 1)  0) {
+ uv_mutex_lock(context-mutex);
+-uv_async_send(context-event_async);
++if (context-emit_buffer_ok) {
++context-emit_buffer_ok = false;
++uv_async_send(context-event_async);
++}
+ uv_cond_wait(context-cond, context-mutex);
+ uv_mutex_unlock(context-mutex);
+ }
+@@ -180,6 +183,7 @@ HandleValue GNEncoder::Create(const Arguments args) {
+ GNEncoder *gn_encoder = node::ObjectWrap::UnwrapGNEncoder(instance);
+ EventContext *context = new EventContext;
+ gn_encoder-event_context = context;
++context-emit_buffer_ok = true;
+ context-event_cb = PersistentFunction::New(LocalFunction::Cast(args[0]));
+ context-encoder = encoder;
+ 
+@@ -372,7 +376,14 @@ HandleValue GNEncoder::GetBuffer(const Arguments args) {
+ GrooveEncoder *encoder = gn_encoder-encoder;
+ 
+ GrooveBuffer *buffer;
+-switch (groove_encoder_buffer_get(encoder, buffer, 0)) {
++int buf_result = groove_encoder_buffer_get(encoder, buffer, 0);
++
++uv_mutex_lock(gn_encoder-event_context-mutex);
++gn_encoder-event_context-emit_buffer_ok = true;
++uv_cond_signal(gn_encoder-event_context-cond);
++uv_mutex_unlock(gn_encoder-event_context-mutex);
++
++switch (buf_result) {
+ case GROOVE_BUFFER_YES: {
+ LocalObject object = Object::New();
+ 
+diff --git a/src/gn_encoder.h b/src/gn_encoder.h
+index 063bf60..958815e 100644
+--- a/src/gn_encoder.h
 b/src/gn_encoder.h
+@@ -19,6 +19,7 @@ class GNEncoder : public node::ObjectWrap {
+ uv_mutex_t mutex;
+ GrooveEncoder *encoder;
+ v8::Persistentv8::Function event_cb;
++bool emit_buffer_ok;
+ };
+ 
+ GrooveEncoder *encoder;
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..3040e56
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+0001-fix-emitting-buffer-event-too-often.patch

Re: Processed: cloning 781554, reopening -1, retitle -1 to docker.io: release cycle is too fast for stable ...

[Felipe Sateler]

On 4 April 2015 at 04:46, Adam D. Barratt a...@adam-barratt.org.uk wrote:
 Control: reassign -1 src:docker.io

 On Sat, 2015-04-04 at 01:03 +, Debian Bug Tracking System wrote:
 Processing commands for cont...@bugs.debian.org:

  clone 781554 -1
 Bug #781554 {Done: Adam D. Barratt a...@adam-barratt.org.uk} 
 [release.debian.org] RM: docker.io -- RoM; release cycle is too fast for 
 stable
 Bug 781554 cloned as bug 781865
  reopen -1
 Bug #781865 {Done: Adam D. Barratt a...@adam-barratt.org.uk} 
 [release.debian.org] RM: docker.io -- RoM; release cycle is too fast for 
 stable
 Bug reopened
 Ignoring request to alter fixed versions of bug #781865 to the same values 
 previously set
  retitle -1 docker.io: release cycle is too fast for stable
 Bug #781865 [release.debian.org] RM: docker.io -- RoM; release cycle is too 
 fast for stable
 Changed Bug title to 'docker.io: release cycle is too fast for stable' from 
 'RM: docker.io -- RoM; release cycle is too fast for stable'
  severity -1 serious
 Bug #781865 [release.debian.org] docker.io: release cycle is too fast for 
 stable
 Severity set to 'serious' from 'minor'

 Given that having such a bug assigned to release.d.o makes no sense, I
 assume you simply forgot to reassign it.

Yes, sorry, the reassign command was missing.

-- 

Saludos,
Felipe Sateler


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/caafdzj_5aa7pmjfsodx3i6rbsyz9dl2rc+ksvtufa3cpdlp...@mail.gmail.com

Bug#769498: unblock: rtkit/0.11-2

[Felipe Sateler]

On Sat, Nov 15, 2014 at 9:16 AM, Jonathan Wiltshire j...@debian.org wrote:
 Control: tag -1 confirmed

 On Fri, Nov 14, 2014 at 12:08:35AM -0300, Felipe Sateler wrote:
 I write to ask if the attached diff would be an appropriate upload to
 unstable that would be granted an unblock request. It fixes two severity
 important bugs:

 Yes. Please ping when it's in the archive.

I uploaded this today.

Thanks

-- 

Saludos,
Felipe Sateler


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/caafdzj-msg3egzh4dncxdbg5y5y78jg0g6pvs0syzjlyoa6...@mail.gmail.com

Bug#769498: unblock: rtkit/0.11-2

[Felipe Sateler]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Dear release team,

I write to ask if the attached diff would be an appropriate upload to
unstable that would be granted an unblock request. It fixes two severity
important bugs:

#696900 Wrong build-dependency on libpolkit-backend-1-dev
#747568 [rtkit-daemon.service:32] Unknown lvalue 'ControlGroup'

The first should avoid a FTBFS when polkit is updated in unstable
(probably soon after jessie is released), the second avoids a warning
during boot on systemd systems.

Please find attached the diff of the proposed upload against 0.11-1.



-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff --git a/debian/changelog b/debian/changelog
index c32f5f7..8dc7726 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+rtkit (0.11-2) unstable; urgency=medium
+
+  * Remove build dependency on libpolkit-backend-1-dev, it is not used
+(Closes: #696900)
+  * Drop removed ControlGroup stanza (Closes: #747568)
+
+ -- Felipe Sateler fsate...@debian.org  Thu, 13 Nov 2014 23:56:19 -0300
+
 rtkit (0.11-1) unstable; urgency=low
 
   * New upstream release.
diff --git a/debian/control b/debian/control
index 7e6ae4c..b9c317d 100644
--- a/debian/control
+++ b/debian/control
@@ -11,7 +11,6 @@ Build-Depends:
  debhelper (= 7.0.50~),
  libcap-dev,
  libdbus-1-dev,
- libpolkit-backend-1-dev
 Standards-Version: 3.9.5
 Vcs-Git: https://alioth.debian.org/anonscm/git/pkg-multimedia/rtkit.git
 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-multimedia/rtkit.git
diff --git a/debian/patches/0002-Drop-Removed-ControlGroup-stanza.patch b/debian/patches/0002-Drop-Removed-ControlGroup-stanza.patch
new file mode 100644
index 000..763953b
--- /dev/null
+++ b/debian/patches/0002-Drop-Removed-ControlGroup-stanza.patch
@@ -0,0 +1,17 @@
+Description: Drop removed ControlGroup stanza
+ Systemd = 205 do not have this directive anymore.
+ This is not a problem for us because the debian kernel does not have
+ CONFIG_RT_GROUP_SCHED enabled, so rt budgets are not per-cgroup
+Bug-Debian: 747568
+--- a/rtkit-daemon.service.in
 b/rtkit-daemon.service.in
+@@ -27,9 +27,5 @@ CapabilityBoundingSet=CAP_SYS_NICE CAP_D
+ PrivateTmp=yes
+ PrivateNetwork=yes
+ 
+-# Work around the fact that the Linux currently doesn't assign any RT
+-# budget to CPU control groups that have none configured explicitly
+-ControlGroup=cpu:/
+-
+ [Install]
+ WantedBy=graphical.target
diff --git a/debian/patches/series b/debian/patches/series
index cf9a390..1558bca 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
 0001-SECURITY-Pass-uid-of-caller-to-polkit.patch
+0002-Drop-Removed-ControlGroup-stanza.patch

Re: Pulseaudio version in Jessie

[Felipe Sateler]

Hi Niels, Release Team,

On Sat, Sep 13, 2014 at 7:13 AM, Niels Thykier ni...@thykier.net wrote:
 On 2014-09-05 06:32, Felipe Sateler wrote:
 Dear release team,

 I'm writing in order to discuss the status of Pulseaudio for Jessie.
 Pulseaudio currently sits at (upstream) version 5 for jessie.

 [...]
 So, the question is will we be able to ship pulseaudio 6? It is fairly
 clear that the final release will not be on time for the freeze.
 However, the release candidate may be introduced in time. The upstream
 policy after a release candidate is only bug fixes and doc/translation
 updates[3]. So I was thinking maybe an exception for the final release
 could be made if the release candidate arrives early enough. We have
 never managed a freeze I believe there are 2 main questions:



 Hi Felipe / Pulseaudio maintainers,

 I apologise for the tardiness on our part.  Thanks for bringing this
 problem to our attention.

 If I understand you correctly then the consequence of the regression is
 Debian loses support for the following bluethooth devices:

  1. Health devices
 - I do not quite a clear view of what these are.  If you have an
   example it would be nice.

  2. Hands-free devices in Cars

 I presume that the lost support in question is only audio (which for
 the 2. part would still be very bad).

I'm not sure what Health devices are. But HSP support also means most
headphone+mic headsets.



 1. Is such a plan (uploading the RC pre-freeze and the final release
 post-freeze) acceptable?


 For me, such a plan /could/ be acceptable provided that:

  * The new major version of pulseaudio is both API and ABI backwards
compatible!

- A transition would be a deal-breaker for me at this point.

AFAICT, the ABI is maintained. I will check a bit more thoroughly and
report back, but I think this requirement is met.


  * The current issues in the release candidates are not (new) RC bugs.

- Keep in mind that we may need to have pulseaudio reverted to the
  old version should such issues turn out to be worse than
  anticipated.

Of course. But we will not know the current issues in the release
candidate until we have it.


  * You are aware that the Debian RT view of necessary bug fixes do
not always coincide with upstreams view of necessary bug fixes.

- During the freeze we will reviewing all changes and we reserve the
  right to question/reject any (part) of them.

How should I propose such changes? In order to make your work easier,
what should I send to the release list each time I upload a package?


   - Keep in mind that we get more defensive as the freeze
 progresses!

- You may have/want to cherry-pick changes frequently during the
  freeze (at a much faster pace than upstream makes releases).

This sounds reasonable.

- You may have to support a bastard version for Jessie that
  consists of the release candidate plus only (some) of upstreams
  patches.

I would be fine with that. Not sure about the rest of the team.


 2. If so, when would be early enough? That is, until what date could
 the RC be uploaded to Debian?

 [...]

 The sooner the better, although you may want to start with experimental
 to ensure it still builds on all architectures.

 *If* we go down this path (and I am *not* saying the release team is
 ready to commit to it), then I would highly prefer that we adopt the
 noblest of traditions in Open Source:

   /Release early, release often./

 Smaller changes are (often) easier to review and has a higher chance of
 being accepted.

OK. As soon as the upstream release candidate is released I will
upload it to experimental. At that moment I will ping you again in
order to check you are still OK with following the above plan.


Thanks and keep up the good work

-- 

Saludos,
Felipe Sateler


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAAfdZj_AMXrY9PMzHPWiLKZncibdGYvSRnZi=suncqnwdwo...@mail.gmail.com

Pulseaudio version in Jessie

[Felipe Sateler]

Dear release team,

I'm writing in order to discuss the status of Pulseaudio for Jessie.
Pulseaudio currently sits at (upstream) version 5 for jessie.

Bluez was recently updated to version 5 and migrated to testing.
Unfortunately, this means that pulseaudio lost support for bluetooth
headsets in HSP profile[1].

Pulseaudio upstream is closing in on a new release. I asked them about
this and they expect pulseaudio to be released this year, although not
with full certainty, of course[2]. The plan (quoted from [2]):

 My plan (which has not been agreed with
 anyone else, so it's subject to discussion) has been to get that patch
 set merged, fix the blocker bugs and then make the first release
 candidate. From the first release candidate it has usually taken at
 least a month before the final release happens.

The referred patch set is the oFono one, which brings HSP support back.

So, the question is will we be able to ship pulseaudio 6? It is fairly
clear that the final release will not be on time for the freeze.
However, the release candidate may be introduced in time. The upstream
policy after a release candidate is only bug fixes and doc/translation
updates[3]. So I was thinking maybe an exception for the final release
could be made if the release candidate arrives early enough. We have
never managed a freeze I believe there are 2 main questions:

1. Is such a plan (uploading the RC pre-freeze and the final release
post-freeze) acceptable?
2. If so, when would be early enough? That is, until what date could
the RC be uploaded to Debian?

I am more than available if more information is required.

For reference, the past release timelines were:

PA 2.99.1 - November 3 2012
PA 3.0- December 17 2012
44 days


PA 3.99.1 - April 15 2013
PA 4.0- June 4 2014
50 days

PA 4.99.1 - January 23 2014
PA 5.0 - March 3 2014
39 days

[1] http://www.freedesktop.org/wiki/Software/PulseAudio/Notes/5.0/
[2] 
http://lists.freedesktop.org/archives/pulseaudio-discuss/2014-September/021440.html
[3] 
http://lists.freedesktop.org/archives/pulseaudio-discuss/2014-September/021473.html

-- 

Saludos,
Felipe Sateler


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAAfdZj-w=4dzgklvjfosdwck3x5-7hkhoe8gyv0ad6nupiz...@mail.gmail.com

Bug#751258: nmu: stk_4.4.4-5

[Felipe Sateler]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Needs librtaudio-dev = 4.1.1~ds0-2

nmu stk_4.4.4-5 . ALL . -m Rebuild against new rtaudio and rtmidi

-- System Information:
Debian Release: jessie/sid
  APT prefers stable
  APT policy: (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140611135423.8701.18847.reportbug@felipepc

Bug#704032: Csound caught in boost transition

[Felipe Sateler]

Hi all,


I'm in the process of updating csound to version 6 (actually, I
started a bit before this transition), and that has happened a lot
less smoothly than I had hoped. Feel free to remove csound and
qutecsound (the only libcsound rdep) from testing in order to advance
this transition. Csound is FTBFS for reasons unrelated to this
transition in many archs.

-- 

Saludos,
Felipe Sateler


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caafdzj8o7autbpbvy4abtr-rwyhkfyoxacod40ok9zgn0pe...@mail.gmail.com

ACK requested for csound upload

[Felipe Sateler]

Dear release team.

It has been brought to my attention that the csound package had a bug
that I think should be fixed. The bug in question is that a header[1]
that is required for building plugins[2]  was not being installed,
which makes it impossible to build plugins for csound with the current
libcsound64-dev package.

I would consider the bug to render the package unusable for building
plugins, and the fix low-risk (just install the extra file). I have
not yet produced a diff (I'm not on my dev machine), but will involve
just installing the file in debian/rules.

However, given the current late stage of the release, an upload may
not be welcome. Therefore I am requesting the release team's ACK for
such an upload.

I will reply to this mail with a diff once I have produced it.

[1] 
http://anonscm.debian.org/gitweb/?p=pkg-multimedia/csound.git;a=blob;f=H/interlocks.h

[2] 
http://anonscm.debian.org/gitweb/?p=pkg-multimedia/csound.git;a=blob;f=H/csdl.h#l32

--

Saludos,
Felipe Sateler


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAAfdZj9ooy3monK8Dko8Fq65o9qtWR=9jtcsztfdn3ovzwm...@mail.gmail.com

Re: ACK requested for csound upload

[Felipe Sateler]

On Fri, Apr 12, 2013 at 10:57 AM, Felipe Sateler fsate...@debian.org wrote:
 I will reply to this mail with a diff once I have produced it.

This is fixed by the following addition to debian/rules:


diff --git a/debian/rules b/debian/rules
index e6888c5..5e164f6 100755
--- a/debian/rules
+++ b/debian/rules
@@ -223,6 +223,10 @@ install/csladspa::
 install/libcsound64-doc::
rm -f doc/html/*.md5 doc/html/*.map doc/html/*.dot

+# TODO: Remove this install for csound6
+install/libcsound64-dev::
+   install H/interlocks.h -T \
+   $(CURDIR)/debian/tmp/usr/include/csound/interlocks.h

 # Don't ship any executable examples, they don't need to be
 # Currently only arch packages carry examples
-

Can I upload?

--

Saludos,
Felipe Sateler


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caafdzj8chbtnant_ktj4bsxlx_jxg5+budjksuaddusj1h0...@mail.gmail.com

Bug#689988: unblock: csound/1:5.17.11~dfsg-2

[Felipe Sateler]

severity 690828 important
thanks

On 11/12/12, Adam D. Barratt a...@adam-barratt.org.uk wrote:
 On Mon, 2012-10-08 at 16:38 -0300, Felipe Sateler wrote:
 Csound is failing to build due to a new bison uploaded around the
 same time csound was uploaded. A patch fixing this could be produced,
 but I'm taking a while backporting the fix from upstream.
 However, I thought probably bison will not migrate anyway, so maybe
 I should just upload a new version to testing-proposed-updates.

 The bison change got reverted in the meantime, and csound is now built
 everywhere. I've added an unblock for csound - please either close
 #690828 or downgrade it if you'd like to use it to track the fix
 required for the new bison.

Downgrading bug.

Thanks!


-- 

Saludos,
Felipe Sateler


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caafdzj-8kmu1a3qvrgnpmenw9mrrzuy9avn3v8-a6zpvtgj...@mail.gmail.com

Re: Bug#691928: Bison: Downgrade to version 2.4 until wheezy is released?

[Felipe Sateler]

On Nov 1, 2012 3:00 PM, Chuan-kai Lin ck...@debian.org wrote:

 I am planning to downgrade bison in unstable by uploading an older
 bison package with a higher epoch number.  This approach seems to be
 the path of least resistance, unless the release team wants to get
 involved.

 Felipe, is it really necessary to downgrade the unstable version all
 the way back to 2.4?  Testing has bison 1:2.5.dfsg-2.1, which was
 uploaded about a year ago and not affected by #689700.  Unless anyone
 objects, I will bump the version number of bison 1:2.5.dfsg-2.1 to
 2:2.5.dfsg-3 and upload it to unstable tomorrow.

Yes, sorry. I mean the version currently in testing. For some reason I
thought it was 2.4.


 Note that this downgrade is a temporary measure intended to
 accommodate the special circumstances of the freeze.  Once wheezy is
 released and the freeze lifted, I will again upload the latest version
 of bison.  The broken packages will have to support the new behavior
 (or alternatively convince bison upstream that they new behavior is
 broken).

Yes, my upstream has fixed the issue, but the patch apparently got tangled
with other stuff and had some trouble backporting it.

Thanks!

Bison: Downgrade to version 2.4 until wheezy is released?

[Felipe Sateler]

Dear release team,

I'd like to point you to this bug in bison. Certain new features of
Bison 2.6 have caused incompatibilities with 2.4. This has resulted in
at least one package failing to build.

I have set the severity to serious, because it causes other packages
to FTBFS. Please advise with how to proceed for packages that
build-depend on bison (eg, see #689988).


Saludos,
Felipe Sateler


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAAfdZj-rsmJRpe46nTijhg8VcByf6jR6=zhntrtgpzc7t_7...@mail.gmail.com

Bug#689988: unblock: csound/1:5.17.11~dfsg-2

[Felipe Sateler]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hello release team,

Csound is failing to build due to a new bison uploaded around the
same time csound was uploaded. A patch fixing this could be produced,
but I'm taking a while backporting the fix from upstream.
However, I thought probably bison will not migrate anyway, so maybe
I should just upload a new version to testing-proposed-updates.

Please advise on an appropriate course of action.

Saludos,
Felipe Sateler


-- System Information:
Debian Release: 6.0.6
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121008193830.5707.12150.reportbug@sun.GENOA

Re: Freeze exception for csound

[Felipe Sateler]

On Oct 6, 2012 7:53 AM, Niels Thykier ni...@thykier.net wrote:

 On 2012-09-30 00:50, Felipe Sateler wrote:
  Dear release team,
 
  Would you accept a freeze exception for csound version
  1:5.17.11~dfsg-2 (just uploaded), to include the attached patch (no
  other changes)?
 
  The build system wrongly passes the -package csnd flag to the SWIG
  interface wrappers, which causes the csound JNI library to fail to
  load. The patch corrects this issue, and comes from upstream. Not
  fixing this bug means the JNI library provided by libcsnd-java is
  useless.
 

 Unblocked, thanks.


Thanks to you.

 Next time, please consider filing an unblock bug - they are much easier
 for us to track.

Ok, will do.


 ~Niels

Freeze exception for csound

[Felipe Sateler]

Dear release team,

Would you accept a freeze exception for csound version
1:5.17.11~dfsg-2 (just uploaded), to include the attached patch (no
other changes)?

The build system wrongly passes the -package csnd flag to the SWIG
interface wrappers, which causes the csound JNI library to fail to
load. The patch corrects this issue, and comes from upstream. Not
fixing this bug means the JNI library provided by libcsnd-java is
useless.

-- 

Saludos,
Felipe Sateler


0004-swig-java-package.patch
Description: Binary data

Re: Supercollider in wheezy

[Felipe Sateler]

On Sun, Aug 19, 2012 at 5:56 PM, Adam D. Barratt
a...@adam-barratt.org.uk wrote:
 On Wed, 2012-08-15 at 18:23 -0400, Felipe Sateler wrote:
 I write to fix the issue of supercollider in wheezy. Current SC in
 testing is upstream version 3.4.5. Current in sid is 3.5.3. The
 version in wheezy has a FTBFS bug (#674386), so we need to get rid of
 that. Options are:

 1. Upload a fix via tpu.

 Apparently this happened.  Whilst the package does look sane, was that
 actually acked in advance?

No. I was under the impression that the ack has to come after the
upload (because the rt uses the actuall uploaded package for the ack).
The devref even says to wait until the package has built on all archs
before notifying the RT. I was waiting for that before sending a mail.

I went for uploading the fixes to tpu because:

1. There was a fix available so it makes no sense to not fix the package.
2. If 3.5 is going to be allowed to migrate, it should be because it
makes sense to have 3.5 instead of 3.4, and not because of some
unrelated bug.


-- 

Saludos,
Felipe Sateler


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caafdzj9o5e48+yqdcwb2ogvlb-9krmk1wapbkr4h7qvndej...@mail.gmail.com

Supercollider in wheezy

[Felipe Sateler]

Dear Relase Team,

I write to fix the issue of supercollider in wheezy. Current SC in
testing is upstream version 3.4.5. Current in sid is 3.5.3. The
version in wheezy has a FTBFS bug (#674386), so we need to get rid of
that. Options are:

1. Upload a fix via tpu.
2. Migrate 3.5.3 to wheezy (we had uploaded 3.5.2 before the freeze,
but it didn't migrate because it didn't build in some archs. More
details later).
3. Remove sc from wheezy.

We would like to avoid option 3, and we favor option 2.  At [1] there
is a description of the changes since the uploaded 3.5.2 version
before the freeze and the current version in unstable.

We would prefer the 3.5 series over the 3.4 series for the following reasons:

* SC 3.4.x relied optionally on a third-party java-based kit
(SwingOSC) to provide for building user interface widgets. (This
provides standard server- and addon-management interfaces as well as
user-made GUIs. It's not compulsory to have GUIs but it's typically
assumed in tutorials and the official book.) This was never packaged
for debian, so the provision is kinda incomplete. SC 3.5 includes a
QT-based widget system which provides all of this functionality and
with the same programming interface. It's very nice.

* The GEdit plugin sced has been updated to support GEdit version 3,
which is what is in wheezy. (We previously just deactivated the gedit
plugin in wheezy which is a shame as it's a recommended editor for
beginners.)

* The old and overgrown SCons build system has been removed in favour
of Cmake. Requires much less downstream packaging effort.

* User config files are moved to a much more XDG-friendly location:
instead of ~/share/supercollider   it's now
~/.local/share/SuperCollider and ~/.config/SuperCollider.   (Old
config is detected and migration info is output.)

* Other changes, detailed in http://doc.sccode.org/Guides/News-3_5.html


If a migration of sc from sid to testing is unacceptable, we can
upload a fix to t-p-u. However, g++ 4.7 ICEs while building 3.4.
Therefore, the fix would have to include a build-dependency on gcc/g++
4.6 and force its use in debian/rules, besides the fix for the build
failure. Full diff attached.


[1] 
http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2012-July/028351.html

-- 

Saludos,
Felipe Sateler


wheezy.diff
Description: Binary data

Re: Fixing #654506 and #674386 in Wheezy

[Felipe Sateler]

On Wed, Jul 11, 2012 at 8:20 AM, Mehdi Dogguy me...@dogguy.org wrote:
 Hi,

 We would like to fix #654506 and #674386 in Wheezy. Unfortunately, we
 are not able to accept supercollider/1:3.5.2-1 from Unstable since the
 changes are quite large.

I think you mean 1:3.5.3~repack-1? That is what's currently in
unstable, and 1:3.5.2-1 was uploaded before the freeze. Unfortunately,
it couldn't migrate because it failed to build on non-x86 archs. We
are currently working on fixing that. So, in a way, the changes are
not that large ;).

I had planned to mail d-r after we got the last round of fixes ready.
Is there a chance we can convince you to let 3.5.3 migrate to testing?


-- 

Saludos,
Felipe Sateler


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caafdzj9fqaa_znmwvndmeboobzb05zrkkchqgsq-2k4jqrp...@mail.gmail.com

Re: Fixing #654506 and #674386 in Wheezy

[Felipe Sateler]

On Wed, Jul 11, 2012 at 10:30 AM, Mehdi Dogguy me...@dogguy.org wrote:
 On 11/07/12 16:01, Felipe Sateler wrote:

 On Wed, Jul 11, 2012 at 8:20 AM, Mehdi Dogguyme...@dogguy.org
 wrote:

 Hi,

 We would like to fix #654506 and #674386 in Wheezy. Unfortunately,
 we are not able to accept supercollider/1:3.5.2-1 from Unstable
 since the changes are quite large.


 I think you mean 1:3.5.3~repack-1?


 Yes, sorry. It was a bad copy/paste :/


 That is what's currently in unstable, and 1:3.5.2-1 was uploaded
 before the freeze. Unfortunately, it couldn't migrate because it
 failed to build on non-x86 archs. We are currently working on fixing
 that. So, in a way, the changes are not that large ;).


 We don't seem to have the same definition of large. For this specific
 case, the changes between the unblocked version and sid's current
 version look like:

 $ debdiff supercollider_3.5.2-1.dsc supercollider_3.5.3~repack-1.dsc \
   | diffstat | tail -n1
  3040 files changed, 5266 insertions(+), 581639 deletions(-)

 This pretty looks as large. Ignoring the bits that were deleted when
 repacking, the debian/ directory, etc… this leads us to:

  53 files changed, 746 insertions(+), 701 deletions(-)

 which is nicer indeed but still qualifies as large.

I made some local git branches with the upstream source of 3.5.2 and
3.5.3, with patches applied.

Updating to 3.5.3 allowed us to drop all the 3.5.2 patches:
$ git show --stat  3.5.2-withpatches'^' | tail -1
 7 files changed, 135 insertions(+), 100 deletions(-)

So, taking into account this, the stat becomes:

$ git diff 3.5.2-withpatches..3.5.3-withpatches --stat \
   | tail -1
 52 files changed, 631 insertions(+), 198 deletions(-)


However, a big chunk of that is documentation updates:

$ git diff 3.5.2-withpatches..3.5.3-withpatches --stat \
   -- HelpSource/| tail -1
 18 files changed, 439 insertions(+), 131 deletions(-)

That leaves as with a diff of:
 34 files changed, 192 insertions(+), 67 deletions(-)

Of that, most of it is bugfixes, and an un-deprecation of a few methods.



 Why did you import 3.5.3 instead of working on fixing 3.5.2? (I'm not
 sure it is relevant now but that might help us to understand the
 situation better).

Mostly because it allowed us to drop the patches we had. Also,
upstreams release management seems sane enough, commits on the 3.5
branch are mostly cherry-picked from the master branch plus
documentation fixes.




 I had planned to mail d-r after we got the last round of fixes ready.
 Is there a chance we can convince you to let 3.5.3 migrate to
 testing?


 We would prefer targeted fixes based on the version of testing.

I understand. But on the other hand, we would prefer shipping
upstreams latest version, which is why I asked if there was a chance
we could convince you.
In particular, since 3.5 sc has a new Qt based widget system, and
debian does not have any other sc widget system (AFAICT, they were all
third party), wheezy users would not be able to build SC GUIs.
Dan can probably tell of more advantages of 3.5 over 3.4.
That's why I asked if there was a chance that we could convince you. I
wasn't asking if we had clearance yet.


-- 

Saludos,
Felipe Sateler


--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAAfdZj-UXq-p�8pcn4k1mdasroquhgzggodvf6qu5fae8...@mail.gmail.com

Re: Freeze exception for csound?

[Felipe Sateler]

On Sun, Dec 26, 2010 at 22:38, Julien Cristau jcris...@debian.org wrote:
 On Sat, Nov 13, 2010 at 21:13:58 -0300, Felipe Sateler wrote:

 Dear release team,

 Recently, a bug was reported against csound (#603321), which was
 already fixed in upstream CVS. The bug is severity: normal, although
 one could argue for a higher severity given that it segfaults whenever
 using a certain opcode.

 This is not migrating to testing because it ftbfs on sparc.
 https://buildd.debian.org/build.php?pkg=csoundver=1%3A5.12.1~dfsg-6arch=sparcfile=log

I know, I asked the sparc admins to retry on schroeder, since that was
the last buildd that was able to build csound.

-- 

Saludos,
Felipe Sateler


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktinwaoq-x1rpyawnvfg_4oddlaawb266kl6hi...@mail.gmail.com

Re: Freeze exception for csound?

[Felipe Sateler]

On Thu, Dec 16, 2010 at 16:02, Julien Cristau jcris...@debian.org wrote:
 On Sat, Nov 13, 2010 at 21:13:58 -0300, Felipe Sateler wrote:

 Dear release team,

 Recently, a bug was reported against csound (#603321), which was
 already fixed in upstream CVS. The bug is severity: normal, although
 one could argue for a higher severity given that it segfaults whenever
 using a certain opcode.

 Here is the entire patch:

 Description: Acquire bus lock at init time
  Otherwise we get segfaults when trying to use it at perf time
 Origin: upstream, commit:1.40
 Bug-Debian: http://bugs.debian.org/603321
 --- a/OOps/bus.c
 +++ b/OOps/bus.c
 @@ -1056,6 +1056,8 @@
      err = csoundGetChannelPtr(csound, (p-fp), (char*) p-iname,
                                CSOUND_AUDIO_CHANNEL | CSOUND_OUTPUT_CHANNEL);
      if (LIKELY(!err)) {
 +      p-lock = csoundGetChannelLock(csound, (char*) p-iname,
 +                             CSOUND_AUDIO_CHANNEL | CSOUND_OUTPUT_CHANNEL);
        p-h.opadr = (SUBR) chnclear_opcode_perf;
        return OK;
      }


 Would this be acceptable for squeeze? If not, I will not upload to
 leave the window open for a possible RC bug fix via unstable.

 Yes, that would be fine.  Sorry for the delayed answer.


Uploaded. Thanks!


-- 

Saludos,
Felipe Sateler


--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktin-fy1goolj0m81tqz9m47ngunztw=k_uo5e...@mail.gmail.com

Freeze exception for csound?

[Felipe Sateler]

Dear release team,

Recently, a bug was reported against csound (#603321), which was
already fixed in upstream CVS. The bug is severity: normal, although
one could argue for a higher severity given that it segfaults whenever
using a certain opcode.

Here is the entire patch:

Description: Acquire bus lock at init time
 Otherwise we get segfaults when trying to use it at perf time
Origin: upstream, commit:1.40
Bug-Debian: http://bugs.debian.org/603321
--- a/OOps/bus.c
+++ b/OOps/bus.c
@@ -1056,6 +1056,8 @@
 err = csoundGetChannelPtr(csound, (p-fp), (char*) p-iname,
   CSOUND_AUDIO_CHANNEL | CSOUND_OUTPUT_CHANNEL);
 if (LIKELY(!err)) {
+  p-lock = csoundGetChannelLock(csound, (char*) p-iname,
+ CSOUND_AUDIO_CHANNEL | CSOUND_OUTPUT_CHANNEL);
   p-h.opadr = (SUBR) chnclear_opcode_perf;
   return OK;
 }


Would this be acceptable for squeeze? If not, I will not upload to
leave the window open for a possible RC bug fix via unstable.


-- 

Saludos,
Felipe Sateler


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktikt+w7j3jteh-c6id3qrngsrevejd_ajk38p...@mail.gmail.com

Bug#589689: transition to libjack-jackd2-0 breaks many packages

[Felipe Sateler]

On 02/09/10 14:06, Adam D. Barratt wrote:
 On Wed, 2010-09-01 at 09:40 -0400, Felipe Sateler wrote: 
 On 01/09/10 04:10, Reinhard Tartler wrote:
 this package has been tried four times and every time we see a different
 build error:

 #1 (on lebrun):segfault in gcc
 #2 (on schroeder): segfault in python (i.e. scons, the build system)
 #3 (on lebrun):segfault in gcc, but in a different compilation unit as 
 #1
 #4 (on schroeder): sigill in gcc
 [...]
 Please, I'd like to know what to do about this. I have a RC bug on
 csound (#591802) about this build failure and by this point I think this
 is not a bug in csound. Note that I have built the package successfully
 on smetana, and Adrian Knoth also did on a machine of his own. Should I
 upload the package and close the bug?
 
 In the short term, uploading the package built on smetana in order to
 allow the package to migrate (possibly with a gentle nudge from britney)
 is ok.

OK, I'm uploading now.

 
 Longer term, we still need to work out why the package builds happily on
 both porter boxes (having managed to build it successfully myself on
 sperger last night) but not on the buildds, so that we can rebuild it in
 the future for security builds and stable updates.

I think I will need help from sparc-savvy people (or should I say, I can
provide help to sparc-savvy people if necessary? I doubt I have much to
say on the issue).


-- 
Saludos,
Felipe Sateler



-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c7fede3.7090...@debian.org

Bug#589689: transition to libjack-jackd2-0 breaks many packages

[Felipe Sateler]

On 01/09/10 04:10, Reinhard Tartler wrote:
 On Tue, Aug 31, 2010 at 21:14:05 (CEST), Adam D. Barratt wrote:
 
 csound still has an outdated dependency on hppa;
 
 What dependency is that? Where can we look that up?
 
 the newer package in unstable FTBFS on sparc.
 
 this package has been tried four times and every time we see a different
 build error:
 
 #1 (on lebrun):segfault in gcc
 #2 (on schroeder): segfault in python (i.e. scons, the build system)
 #3 (on lebrun):segfault in gcc, but in a different compilation unit as #1
 #4 (on schroeder): sigill in gcc
 
 https://buildd.debian.org/build.php?pkg=csoundarch=sparcver=1:5.12.1~dfsg-5
 
 what's the problem with these buildds?

Please, I'd like to know what to do about this. I have a RC bug on
csound (#591802) about this build failure and by this point I think this
is not a bug in csound. Note that I have built the package successfully
on smetana, and Adrian Knoth also did on a machine of his own. Should I
upload the package and close the bug?

-- 
Saludos,
Felipe Sateler



-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c7e57d4.9050...@debian.org

Bug#589689: Bug#590948: Bug#589689: transition to libjack-jackd2-0 breaks many packages

[Felipe Sateler]

On 03/08/10 17:50, Julien Cristau wrote:
 On Tue, Aug  3, 2010 at 17:31:05 -0400, Felipe Sateler wrote:
 
 This doesn't seem to help (I called dpkg-buildpackage -B and doxygen was
 called). How will dh_listpackages know if we called dpkg-buildpackage -B?

 In 'build', it doesn't.  If you want to do something only if arch-indep
 packages are built, do it in binary-indep or binary.

Jonas,

How do we do this in CDBS?

-- 
Saludos,
Felipe Sateler



-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c597e60.3040...@debian.org

Bug#589689: Bug#590948: Bug#589689: transition to libjack-jackd2-0 breaks many packages

[Felipe Sateler]

On 03/08/10 16:09, Reinhard Tartler wrote:
 On Mon, Aug 02, 2010 at 19:23:59 (EDT), Felipe Sateler wrote:
 
 On 02/08/10 18:26, Adam D. Barratt wrote:
 On Sun, August 1, 2010 12:33, Felipe Sateler wrote:
 Copying this to the appropriate bug...
 [...]
 Indeed. How do you suggest working through this? Facts:

 1. The build hangs unpredictably on a doxygen call.
 2. The doxygen call is in build-indep (so it is not strictly necessary
 for binary only builds, but gets executed anyway).

 I can move the doxygen call away from there into binary-indep, but that
 feels like a hack to me.

 Does the documentation actually differ across architectures?

 No, it doesn't.

  If the doxygen calls are simply for generating the contents of
 libcsound64-doc then arranging for them to only occur when the
 binary-indep packages are being built sounds like a sane solution; if
 I'm missing something obvious, then someone please apply the relevant
 cluebat. :-)

 Well, it feels hacky to build stuff in the binary stage. Also, it seems
 to me that what we are doing is re-hiding a bug that is somewhere else.

 If we really want to do that, please tell me and I'll prepare a new
 upload with that.
 
 Mehdi proposed this approach:
 
 diff --git a/debian/rules b/debian/rules
 index 726227e..626b8d6 100755
 --- a/debian/rules
 +++ b/debian/rules
 @@ -163,7 +163,9 @@ DEB_SCONS_INSTALL_TARGET = install=1
  
  build-indep: build-indep-stamp
  build-indep-stamp:
 +ifneq (,$(findstring libcsound64-doc,$(shell dh_listpackages)))
   doxygen
 +endif
   touch $@
  
  # Put aside upstream cruft before build but after licensecheck
 
 
 TBH, this solution seems acceptable to me.

This doesn't seem to help (I called dpkg-buildpackage -B and doxygen was
called). How will dh_listpackages know if we called dpkg-buildpackage -B?


-- 
Saludos,
Felipe Sateler



-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c588a99.10...@debian.org

Bug#589689: transition to libjack-jackd2-0 breaks many packages

[Felipe Sateler]

On 02/08/10 18:26, Adam D. Barratt wrote:
 On Sun, August 1, 2010 12:33, Felipe Sateler wrote:
 Copying this to the appropriate bug...
 [...]
 Indeed. How do you suggest working through this? Facts:

 1. The build hangs unpredictably on a doxygen call.
 2. The doxygen call is in build-indep (so it is not strictly necessary
 for binary only builds, but gets executed anyway).

 I can move the doxygen call away from there into binary-indep, but that
 feels like a hack to me.
 
 Does the documentation actually differ across architectures?

No, it doesn't.

  If the
 doxygen calls are simply for generating the contents of libcsound64-doc
 then arranging for them to only occur when the binary-indep packages are
 being built sounds like a sane solution; if I'm missing something obvious,
 then someone please apply the relevant cluebat. :-)

Well, it feels hacky to build stuff in the binary stage. Also, it seems
to me that what we are doing is re-hiding a bug that is somewhere else.


If we really want to do that, please tell me and I'll prepare a new
upload with that.

-- 
Saludos,
Felipe Sateler



-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c57538f.10...@debian.org

Bug#589689: transition to libjack-jackd2-0 breaks many packages

[Felipe Sateler]

Copying this to the appropriate bug...

On 01/08/10 11:38, Adam D. Barratt wrote:
 On Fri, July 30, 2010 19:02, Felipe Sateler wrote:
 On 30/07/10 13:25, Adam D. Barratt wrote:
 - ardour: FTBFS on sparc (#590863)
 - csound: FTBFS on hppa (#590948)
 - slv2: FTBFS on hppa (#590976)

 All these three look like problems with the buildd host/toolchain.
 CSound hangs in a doxygen call that has not been modified since the -1
 upload. Trying to build that same documentation in paer gives me
 segmentation faults in doxygen in different stages almost every time (I
 managed to build it after a few retries).
 
 Of the four tries on the buildds, csound hung in doxygen twice and during
 the source build twice, afaics.  That and the fact that it needed several
 tries on paer suggest that even if we it managed to build after another
 attempt or three, the next binNMU or sourceful upload may well have the
 same problem(s).

Indeed. How do you suggest working through this? Facts:

1. The build hangs unpredictably on a doxygen call.
2. The doxygen call is in build-indep (so it is not strictly necessary
for binary only builds, but gets executed anyway).

I can move the doxygen call away from there into binary-indep, but that
feels like a hack to me. I have been trying to build the doxygen
documentation a few times, and it looks like either doxygen is doing
something wrong with pthread mutex calls or the hppa kernel/libc are
doing something wrong with the calls doxygen makes. I'm getting some
assertion failures now too:

doxygen: pthread_mutex_lock.c:62: __pthread_mutex_lock: Assertion
`mutex-__data.__owner == 0' failed.


All hangs and segmentation faults seem to happen inside synchronization
calls (futex calls). I have not been able to reproduce the hang in the
Generating docs for compound ... stage.

 
 The paer sid chroot does not
 have the necessary build deps, so I can't binNMU it myself.
 
 You can, you just need to request that the build-deps be installed.

Not necessary, since the faulty command (doxygen) is already installed
and I do not plan on working around this bug by manually uploading a
package that will have the same problem again.


-- 
Saludos,
Felipe Sateler



signature.asc
Description: OpenPGP digital signature

Bug#589689: transition to libjack-jackd2-0 breaks many packages

[Felipe Sateler]

On 30/07/10 13:25, Adam D. Barratt wrote:
 On Tue, 2010-07-20 at 22:30 +0200, Adrian Knoth wrote:
 It works (on the library level), but the packages need to depend on the
 newly introduced virtual package libjack-0.116 which is provided by
 either libjack0 or libjack-jackd2-0. 

 (to be precise, they'll depend on (libjack-jackd2-0 | libjack-0.116),
 and that's what the binNMUs are for)
 
 On the subject of those binNMUs, they should now all have been
 scheduled.
 
 Looking at unstable and ignoring packages which have built successfully
 and are simply missing uploads, the remaining packages depending on just
 libjack0 are:
 
 - ardour: FTBFS on sparc (#590863)
 - csound: FTBFS on hppa (#590948)
 - slv2: FTBFS on hppa (#590976)

All these three look like problems with the buildd host/toolchain.
CSound hangs in a doxygen call that has not been modified since the -1
upload. Trying to build that same documentation in paer gives me
segmentation faults in doxygen in different stages almost every time (I
managed to build it after a few retries). The paer sid chroot does not
have the necessary build deps, so I can't binNMU it myself.
slv2 hangs in a file copy operation, apparently. Adrian Knoth already
commented on the ardour bug. Should we schedule retries?



-- 
Saludos,
Felipe Sateler



-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c535a0e.9030...@debian.org

Bug#583916: Upcoming jack transition

[Felipe Sateler]

On Sun, Jun 6, 2010 at 10:12, Reinhard Tartler siret...@tauware.de wrote:
 My idea was to have the j-a-c-k (jackd2) package provide the non-virtual
 package libjack0, just like today.  I didn't think it was important
 which libjack implementation apps build against, and this seemed the
 easiest / least disruptive way.

 Well, we prefer (I think adi has expressed this explicitly) to have
 applications built against jackd1. I think the easiest and most obvious
 way for this is to make libjack0 a non-virtual package produced by
 j-a-c-k (jackd1), and have a separate libjack-jackd2-0 package produced
 by the (NEW) jackd2 source package.

To build against jackd1, it is necessary only that jack1 provides the
non-virtual libjack-dev. The name of the library package itself is of
no relevance, I think.


Julien Cristau wrote:
 For the default install, we want to install jackd2 by default as we
 believe that it provides a superiour user experience. However, we want
 to have all applications built against libjack0 from jackd1. Moreover,

 OK as I said above I don't understand this bit...

libjack0 has a clearer ABI as it is pure C. It thus makes it easier to
detect borkage.

--

Saludos,
Felipe Sateler



--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktimpw34tbakdy0l3fga8rsjhfaehy07zuuxyu...@mail.gmail.com

Bug#583916: Upcoming jack transition

[Felipe Sateler]

On Sat, Jun 5, 2010 at 15:36, Julien Cristau jcris...@debian.org wrote:
 On Mon, May 31, 2010 at 18:39:11 +0200, Reinhard Tartler wrote:

 The last transition switched the jack-audio-connection-kit package
 from 'jackd' to 'jackd2'. 'jackd2' is a complete reimplementation of
 jackd in C++ with SMP support. Most importantly however, is an added
 feature that improves interoperability with pulseaudio.  For this
 reason, we decided to make this version the default version for Squeeze.

 During testing, however, we discovered that this transition has been and
 still is a bit problematic.  Besides some more or less known bugs in
 'jackd2', it exposes a lot of additional (internal, C++ only) symbols,
 with which we are not comfortable at all.  Moreover, we have been
 approached by upstream(s) with concerns that our current package does
 not make it easy for 3rd parties (may it be upstream or backports.org)
 to provide replacement packages for other jackd implementations.

 For this reason, we propose to:

  - revert the 'jack-audio-connection-kit' package to the jackd1
    implementation

  - make this package the provider of libjack-dev, however the actual
    daemon will be packaged as 'jackd1' (currently jackd)

  - create a shlibs file that makes application packages depend on
    'libjack0-0.116 | libjack0-0.118+svn3796 (= 1:0.0116)' (or similar).
    This effectively defines a new virtual package 'libjack0-0.116' that
    is provided by any jack implementation that claims to be binary
    compatible with the 0.116 release of the original jack
    implementation.

  - have all packages that are linked against libjack recompiled to pick
    up the new shlibs

  - introduce the jackd2 implementation as a new source package 'jackd2'.
    The binary package name of this jack daemon will be 'jackd2', the
    library package will be 'libjack-jackd2-0' and (of course also)
    provide 'libjack0-0.116'.

  - introduce a new source package 'jackd-defaults' that generates a meta
    package 'jackd' which points to the default jack implementation,
    which will be jackd2 for Debian.

 So I have a few questions about this plan:
 - if all implementations of libjack are binary-compatible, then why do
  we need to change the package name when changing implementations of
  libjack?

Because there can be only one package of a given name... unless I'm
misparsing your question.

 - I understand you want to allow different jackd implementations to
  coexist.  Do we really need 2 implementations of libjack as well?

Yes. The server and the library have an internal API that is not
guaranteed to be compatible across any kind of release. So these two
must be the same upstream version.

 - related to this, the libjack0.symbols file currently has things like
  'jack_client_kill_thr...@base 1.9.5~dfsg-13' which suggest that it is,
  actually, not completely compatible with other implementations (a
  quick check suggests that nothing out of the jack-audio-connection-kit
  source package uses these additional symbols, but..)
 - many packages apparently depend on symbols labelled 0.118.0 or later
  in the symbols file, how does that fly with a 0.116 jackd1?

I believe the symbols file is borked. Client applications are only
allowed to assume functions defined in 0.116 to exist. Extra symbols
are defined as weak, and clients intending to use them must check for
their availability. Clients assuming such symbols exist are broken
according to upstream.

So... libjack *can* have extra symbols added after the 0.116 API, and
it *can* have extra symbols for use for the server. Client
applications cannot assume they exist, though.

-- 

Saludos,
Felipe Sateler



--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktil1etwhungso56wbbtf3qzvn0rmhngno5m-4...@mail.gmail.com

Re: Notes on IRC meeting

[Felipe Sateler]

On Tue, 2010-03-16 at 22:28 +0100, Marc Brockschmidt wrote:
  * liblo: 
- Hanging on sivp, bugs needs to be filed, might be solved by
 removing

Ehm, how does sivp affect liblo? I cannot find a chain from liblo to
sivp...

-- 
Saludos,
Felipe Sateler



--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1268779863.3834.9.ca...@pcfelipe.sateler.com

Bug#548642: transition: liblo

[Felipe Sateler]

On Mon, Mar 1, 2010 at 06:05, Marc 'HE' Brockschmidt h...@ftwca.de wrote:
 Felipe Sateler fsate...@gmail.com writes:
 As far as I can tell, no reverse build-dep of liblo is involved in the
 current ghc or hdf transitions. Can we upload new liblo to unstable and
 schedule binNMUs?

 Yes, I guess so. Please go ahead.

liblo 0.26~repack-3 has been uploaded a few hours ago.

-- 

Saludos,
Felipe Sateler



-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/8a0bda451003020733n7adec2e5scbf7ea2af5acf...@mail.gmail.com

Bug#548642: transition: liblo

[Felipe Sateler]

As far as I can tell, no reverse build-dep of liblo is involved in the
current ghc or hdf transitions. Can we upload new liblo to unstable and
schedule binNMUs?

csound
dssi
fluidsynth-dssi
freej
hexter
jackbeat*
jamin
ll-scope
nekobee
qtractor
rosegarden*
sineshaper*
whysynth
wsynth-dssi
xsynth-dssi


* These packages need sourceful uploads because they build-depend on a
versioned liblo0-dev. Bugs have already been filed for these (530852,
530859 and 571961).

-- 
Saludos,
Felipe Sateler


signature.asc
Description: This is a digitally signed message part

Bug#548642: transition: liblo

[Felipe Sateler]

On Fri, 2009-10-16 at 17:40 -0300, Felipe Sateler wrote:
 On Sun, 2009-09-27 at 16:29 -0400, Felipe Sateler wrote:
  Package: release.debian.org
  Severity: normal
  User: release.debian@packages.debian.org
  Usertags: transition
  
  New upstream liblo bumps SONAME, so we need to transition. Also, we take
  this opportunity to change the -dev package name to unversion it.
  liblo-dev now provides liblo0-dev to avoid breaking too many packages.
  However, rosegarden and sineshaper have versioned build-dependencies on
  liblo0-dev. They both require versions already in oldstable, so a simple
  NMU dropping the versioning is enough for them. All other packages
  should require binNMUs, and the new version is supposed to be API-compatible
  with the old one.
 
 Ping?

Again? Someone in here?


-- 
Saludos,
Felipe Sateler


signature.asc
Description: This is a digitally signed message part

Bug#548642: transition: liblo

[Felipe Sateler]

On Sun, 2009-09-27 at 16:29 -0400, Felipe Sateler wrote:
 Package: release.debian.org
 Severity: normal
 User: release.debian@packages.debian.org
 Usertags: transition
 
 New upstream liblo bumps SONAME, so we need to transition. Also, we take
 this opportunity to change the -dev package name to unversion it.
 liblo-dev now provides liblo0-dev to avoid breaking too many packages.
 However, rosegarden and sineshaper have versioned build-dependencies on
 liblo0-dev. They both require versions already in oldstable, so a simple
 NMU dropping the versioning is enough for them. All other packages
 should require binNMUs, and the new version is supposed to be API-compatible
 with the old one.

Ping?

 
 Direct reverse dependencies:
 
 ardour
 csound
 dssi
 fluidsynth-dssi
 freej
 hexter
 jamin
 ll-scope
 nekobee
 qtractor
 rosegarden*
 sineshaper*
 whysynth
 wsynth-dssi
 xsynth-dssi
 
 
 
 -- System Information:
 Debian Release: squeeze/sid
   APT prefers unstable
   APT policy: (500, 'unstable'), (1, 'experimental')
 Architecture: amd64 (x86_64)
 
 Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash


-- 
Saludos,
Felipe Sateler


signature.asc
Description: This is a digitally signed message part

Bug#548642: transition: liblo

[Felipe Sateler]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

New upstream liblo bumps SONAME, so we need to transition. Also, we take
this opportunity to change the -dev package name to unversion it.
liblo-dev now provides liblo0-dev to avoid breaking too many packages.
However, rosegarden and sineshaper have versioned build-dependencies on
liblo0-dev. They both require versions already in oldstable, so a simple
NMU dropping the versioning is enough for them. All other packages
should require binNMUs, and the new version is supposed to be API-compatible
with the old one.

Direct reverse dependencies:

ardour
csound
dssi
fluidsynth-dssi
freej
hexter
jamin
ll-scope
nekobee
qtractor
rosegarden*
sineshaper*
whysynth
wsynth-dssi
xsynth-dssi



-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Jack Audio Connection Kit transition

[Felipe Sateler]

On Tue, Mar 31, 2009 at 02:19, Adeodato Simó d...@net.com.org.es wrote:
 Maintainers: unless you’re jackbeat or gst-plugins-bad0.10, you need not
 upload for this, though build-depending on libjack-dev in your next
 upload would be nice.

 ---

 Hello, Felipe. I finally found some time to look at your message. I’ve
 moved -release to CC (thanks for the Bcc!), since it’s on-topic there.

 Fellow developers and release team (bcc'ed),

 The Debian Multimedia Maintainers would like to drop the  versioned jack
 library and development packages (that is, libjack0.100.0-{0,dev}). They were
 introduced a long time ago (along with the appropriately renamed library) due
 to perceived instability in the jack library's ABI. For a while now, this is
 no longer necessary, and upstream has catalogued Debian packages of jack
 broken because of that. The debian packages no longer change the soname of 
 the
 library (starting with lenny), and the versioned packages are just dummy 
 ones.
 We want to drop them now. The first thing to be done is to switch the
 build-dependency from libjack0.100.0-dev to libjack-dev. After all packages
 have been changed and uploaded, we can upload a jack without those
 transitional packages (unless I overlooked something and we need the RT ack
 first?).

 Just to be clear: there is ABI/SONAME transition here. Packages that still
 depend on libjack0.100.0-0 use the symlink provided by that package[1]. A
 mere sed -i -e 's/libjack0.100.0/libjack/g' debian/control should be all
 that people need to do.

 I assume you mean “there is NOT ABI/SONAME transition here”, heh.

Indeed.

 So,
 here are my comments on the matter:

  * plan for libjack0.100.0-dev: you can make a j-a-c-k upload to
    unstable dropping this development package immediately, provided
    that you add a “Provides: libjack0.100.0-dev” line to the
    libjack-dev package.

Sounds like a better plan.


    You will have to file two bugs at RC severity against jackbeat and
    gst-plugins-bad0.10; these are the only packages that have a
    *versioned* build-dependency on libjack0.100.0-dev, as far as I can
    see.

    I’ve also checked, and there is no pacakge with versioned
    dependencies on libjack0.100.0-dev.

OK.


  * plan for libjack0.100.0-0: there are 11 source packages left with
    dependencies on this old library. No sourceful uploads are needed
    for this: once you’ve gotten back to me that the plan is good, I
    will provide you with a list of packages and schedule Bin-NMUs; then
    you can do some work of checking if they built successfully
    everywhere, filing bugs, etc. Once all of them have been rebuilt
    (which will make them depend on libjack0), please check with us that
    they’ve migrated to testing, and at that point libjack0.100.0-0 can
    be dropped.

 Sounds good?

Amsynth will require a sourceful upload, since the dependency is not
generated by dpkg-shlibdeps because it dlopens libjack. It is the only
one I saw.


Saludos,
Felipe Sateler


--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Jack Audio Connection Kit transition

[Felipe Sateler]

Fellow developers and release team (bcc'ed),

The Debian Multimedia Maintainers would like to drop the  versioned jack
library and development packages (that is, libjack0.100.0-{0,dev}). They were
introduced a long time ago (along with the appropriately renamed library) due 
to perceived instability in the jack library's ABI. For a while now, this is 
no longer necessary, and upstream has catalogued Debian packages of jack 
broken because of that. The debian packages no longer change the soname of the 
library (starting with lenny), and the versioned packages are just dummy ones. 
We want to drop them now. The first thing to be done is to switch the 
build-dependency from libjack0.100.0-dev to libjack-dev. After all packages 
have been changed and uploaded, we can upload a jack without those 
transitional packages (unless I overlooked something and we need the RT ack 
first?).
Just to be clear: there is ABI/SONAME transition here. Packages that still 
depend on libjack0.100.0-0 use the symlink provided by that package[1]. A 
mere sed -i -e 's/libjack0.100.0/libjack/g' debian/control should be all 
that people need to do.

Here is the dd-list of the 39 affected packages:

Guenter Geiger (Debian/GNU) gei...@debian.org
   ladcca
   lash
   libjackasyn
   meterbridge
   stk

Nacho Barrientos Arias na...@debian.org
   akode (U)

CJ van den Berg c...@vdbonline.com
   pulseaudio (U)

Fathi Boudra f...@debian.org
   arts (U)

Paul Brossier p...@debian.org
   jackbeat (U)

Chris Butler chr...@debian.org
   spiralsynthmodular

Andrea Capriotti capri...@debian.org
   ihu

Adrien Cunin adri2...@ubuntu.com
   djplay

Joost Yervante Damad and...@debian.org
   timidity

Debian allegro packages maintainers 
pkg-allegro-maintain...@lists.alioth.debian.org
   allegro4.2

Debian Multimedia Maintainers 
pkg-multimedia-maintain...@lists.alioth.debian.org
   mhwaveedit

Debian Multimedia Team debian-multime...@lists.debian.org
   ams

Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org
   akode
   arts

Debian VoIP Team pkg-voip-maintain...@lists.alioth.debian.org
   linphone
   portaudio19

Debian Wine Party pkg-wine-pa...@lists.alioth.debian.org
   wine

Sebastian Dröge sl...@debian.org
   gst-plugins-bad0.10 (U)

DSSI Maintainers pkg-dssi-de...@lists.alioth.debian.org
   dssi

Free Ekanayaka fr...@debian.org
   ams (U)
   mhwaveedit (U)

Free Ekanayaka f...@agnula.org
   creox
   horgand

Bartosz Fenski fe...@debian.org
   moc (U)

Jochen Friedrich joc...@scram.de
   darkice

Mike Furr mf...@debian.org
   terminatorx

Bdale Garbee bd...@gag.com
   gnuradio

Debian QA Group packa...@qa.debian.org
   freqtweak
   jack-tools

Brandon Holtsclaw bran...@imbrandon.com
   libvisual-plugins

Mark Hymers m...@debian.org
   dssi (U)

Robert Jordens jord...@debian.org
   bitscope
   jamin
   timemachine

Ove Kaaven o...@arcticnet.no
   wine (U)

Adrian Knoth a...@drcomp.erfurt.thur.de
   mhwaveedit (U)

Kilian Krause kil...@debian.org
   linphone (U)
   portaudio19 (U)

Wesley J. Landaker w...@icecavern.net
   cheesetracker

Faidon Liambotis parav...@debian.org
   linphone (U)

Arthur Loiret arthur.loi...@gmail.com
   wine (U)

Ana Beatriz Guerrero Lopez a...@debian.org
   akode (U)
   arts (U)

Eduardo Marcel Macan ma...@debian.org
   specimen
   zynaddsubfx

Mikael Magnusson mi...@users.sourceforge.net
   portaudio19 (U)

Maintainers of GStreamer packages 
pkg-gstreamer-maintain...@lists.alioth.debian.org
   gst-plugins-bad0.10

Samuel Mimram smim...@debian.org
   linphone (U)

Sam Hocevar (Debian packages) sam+...@zoy.org
   allegro4.2 (U)

Guillaume Pellerin yom...@altern.org
   jackbeat

Pulseaudio maintenance team pkg-pulseaudio-de...@lists.alioth.debian.org
   pulseaudio

Mark Purcell m...@debian.org
   linphone (U)
   portaudio19 (U)

Elimar Riesebieter riese...@lxtec.de
   moc

Felipe Sateler fsate...@gmail.com
   csound

Sjoerd Simons sjo...@debian.org
   gst-plugins-bad0.10 (U)
   pulseaudio (U)

Adeodato Simó d...@net.com.org.es
   arts (U)

Jonas Smedegaard d...@jones.dk
   csound (U)

Jose Carlos Garcia Sogo js...@debian.org
   portaudio19 (U)

Junichi Uekawa dan...@debian.org
   ams (U)
   ecasound2.2
   soundtracker

Modestas Vainius modes...@vainius.eu
   arts (U)

Sune Vuorela deb...@pusling.com
   akode (U)




[1] This actually surprised me. Could someone explain to me why are there 
SONAMEs when they are not actually used? 

% ldd /usr/bin/creox | grep jack
libjack-0.100.0.so.0 = /usr/lib/libjack-0.100.0.so.0 
(0x7f943206f000)
% ls -l /usr/lib/libjack-0.100.0.so.0
lrwxrwxrwx 1 root root 12 2009-03-18 19:03 /usr/lib/libjack-0.100.0.so.0 - 
libjack.so.0
% objdump -p /usr/lib/libjack-0.100.0.so.0 | grep SONAME
  SONAME  libjack.so.0
fel...@pcfelipe:csound%


Saludos,
Felipe Sateler


signature.asc
Description: This is a digitally signed message part.

Re: Freeze exception for csound

[Felipe Sateler]

El 07/11/08 15:04 Adeodato Simó escribió:
 * Felipe Sateler [Thu, 06 Nov 2008 15:28:27 -0300]:
  OK, so I have a fix for the alpha issue (I'm surprised it hadn't failed
  before, it was an alpha-specific fix with a typo).

 Ok, please upload it.

FYI, Jonas uploaded a fix for this, the java issue and the documentation 
issue, which has built successfuly on all archs. I don't know if you 
explicitly track t-p-u. 


Saludos,
Felipe Sateler


signature.asc
Description: This is a digitally signed message part.

Re: Freeze exception for csound

[Felipe Sateler]

El 03/11/08 12:02 Felipe Sateler escribió:
 On Sat, Nov 1, 2008 at 7:27 AM, Adeodato Simó [EMAIL PROTECTED] wrote:
  * Jonas Smedegaard [Wed, 29 Oct 2008 22:58:27 +0100]:
  On Wed, Oct 29, 2008 at 10:34:11PM +0100, Adeodato Simó wrote:
  * Jonas Smedegaard [Tue, 28 Oct 2008 16:46:22 +0100]:
   On Tue, Oct 28, 2008 at 12:34:50PM -0300, Felipe Sateler wrote:
   Since I posted the first mail, an RC bug was filed against csound
   (503633) . I have reuploaded to mentors a fix, but I can't upload to
   t-p-u since I'm not a DD. My co-maintainer (CCed) seems to be busy
   right now.
   Would any of the release team review and upload the changes?
  
   Sorry for being silent lately - you guessed right. I am swamped with
   work (but it seems to loosen up a bit from now on).
  
   I have a moment now, so I'll have a go at releasing for t-p-u!
  
  Upload seen, will be unblocked once it's built for all architectures.
 
  Excellent! :-)
 
  Package failed to buid on alpha and mipsel, is this something you would
  know something about?
 
  
  http://buildd.debian.org/~jeroen/status/package.php?p=csoundsuite=testin
 g

 I don't have time yet to get into the problem (will do on thursday), but a
 quick look suggests that mipsel has something wrong with it's java
 (unfortunately, csound's build system will just disable java instead of
 bombing out with an explanation. Alpha I have no idea what went wrong,
 but is not Java-related (although it would have failed later on about that
 anyway).

OK, so I have a fix for the alpha issue (I'm surprised it hadn't failed 
before, it was an alpha-specific fix with a typo). I still have no clues as 
to why Java is not being picked up in mipsel and alpha: both seem to have an 
existing jni.h and jni_md.h (which is what csound looks for). Perhaps the 
problem is that csound only looks 
in /usr/lib/{java,jvm/java,jvm/java-1.5.0,jvm/default-java}/include. The 
first three are upstream's, the last one is a debian addition. Should I be 
adding more paths?

Saludos,
Felipe Sateler


signature.asc
Description: This is a digitally signed message part.

Re: Freeze exception for csound

[Felipe Sateler]

El 03/11/08 12:04 Andreas Barth escribió:
 * Jonas Smedegaard ([EMAIL PROTECTED]) [081103 15:58]:
  On Mon, Nov 03, 2008 at 03:12:36PM +0100, Thiemo Seufer wrote:
  Jonas Smedegaard wrote:
   On Sat, Nov 01, 2008 at 11:27:34AM +0100, Adeodato Simó wrote:
   * Jonas Smedegaard [Wed, 29 Oct 2008 22:58:27 +0100]:
   
   Package failed to buid on alpha and mipsel, is this something you
would know something about?
   

http://buildd.debian.org/~jeroen/status/package.php?p=csoundsuite=t
   esting
  
   Hmm - no, not me :-(
  
   Perhaps simply drop java support for those two architectures, if noone
   else has a clue right now, to make it into Lenny ASAP?
  
  Regardless of that, there's a missing build dep on gs: Grep in the
  build logs for Error
 
  Thanks - I noticed that as well. But that seems not fatal (only related
  to documentation) so irrelevant for Lenny, right?

 If any of your package fails to build, the makefile needs to notice that
 and stop the build process. If not, the packages is fundamentally
 broken. Besides of that, documentation is important.

The problem would have consequences only if whoever uploads the package 
doesn't have ghostscript installed: the documentation is only in an arch:all 
package. However, I'm not sure we can correctly trap this sort of error: 
doxygen isn't reporting them back to us.
There are other errors ignored (pdflatex likes to return non-zero, though 
non-fatal errors ocurred), but I don't know how to debug those errors 
(doxygen-latex-pdf), and also the pdfs produced seem to be correct.


Saludos,
Felipe Sateler


signature.asc
Description: This is a digitally signed message part.

Re: Freeze exception for csound

[Felipe Sateler]

On Sat, Nov 1, 2008 at 7:27 AM, Adeodato Simó [EMAIL PROTECTED] wrote:
 * Jonas Smedegaard [Wed, 29 Oct 2008 22:58:27 +0100]:

 On Wed, Oct 29, 2008 at 10:34:11PM +0100, Adeodato Simó wrote:
 * Jonas Smedegaard [Tue, 28 Oct 2008 16:46:22 +0100]:

  On Tue, Oct 28, 2008 at 12:34:50PM -0300, Felipe Sateler wrote:
  Since I posted the first mail, an RC bug was filed against csound
  (503633) . I have reuploaded to mentors a fix, but I can't upload to
  t-p-u since I'm not a DD. My co-maintainer (CCed) seems to be busy
  right now.
  Would any of the release team review and upload the changes?

  Sorry for being silent lately - you guessed right. I am swamped with
  work (but it seems to loosen up a bit from now on).

  I have a moment now, so I'll have a go at releasing for t-p-u!

 Upload seen, will be unblocked once it's built for all architectures.

 Excellent! :-)

 Package failed to buid on alpha and mipsel, is this something you would
 know something about?

  http://buildd.debian.org/~jeroen/status/package.php?p=csoundsuite=testing

I don't have time yet to get into the problem (will do on thursday), but a
quick look suggests that mipsel has something wrong with it's java
(unfortunately, csound's build system will just disable java instead of
bombing out with an explanation. Alpha I have no idea what went wrong,
but is not Java-related (although it would have failed later on about that
anyway).

-- 

Felipe Sateler

Re: Freeze exception for csound

[Felipe Sateler]

Since I posted the first mail, an RC bug was filed against csound (503633) . I 
have reuploaded to mentors a fix, but I can't upload to t-p-u since I'm not a 
DD. My co-maintainer (CCed) seems to be busy right now.
Would any of the release team review and upload the changes?


Saludos,
Felipe Sateler


signature.asc
Description: This is a digitally signed message part.

Re: Problems with Lintian refusing to understand Depends: php5-cli | php4-cli

[Felipe Sateler]

Thomas Goirand wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Hi,
 
 My package depends on php5-cli | php4-cli, and it was fine, supporting
 backports to Etch and all. Then Lintian developers decided to remove
 php4 from the loop as php4 is removed from Lenny, so it produced an error.

What error?

 
 I then contacted them, saying that it was more easy for me and everybody
 that the dependency php5-cli | php4-cli was supported, so it would be
 more easy to do backports. So they supported it again. But... it went
 backward again, and I'm very surprised to see that the Lintian
 developpers decided to go back to checking only php5-cli.
 
 I'm a bit stuck with lintian producing an error, and my package can't be
 uploaded. It's a bit silly, as what I wrote as dependency is correct and
 WILL work in Lenny or SID. I don't really wish to change anything before
 Lenny is the new stable, if possible, as the same package works for both
 Lenny and Etch.

Lintian doesn't prevent uploads to sid.


You need to give more context to understand the problem.

-- 

  Felipe Sateler


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Freeze exception for csound

[Felipe Sateler]

El 01/10/08 02:36 Pierre Habouzit escribió:
 On Sun, Sep 28, 2008 at 05:31:03PM +, Felipe Sateler wrote:
  Hi release team. I'd like to ask if an update for csound is possible. It
  brings 2 changes that are the reason for the update request. The first
  one is that the csound library comes with a few plugins, but they weren't
  versioned with the library. This violates policy 8.2, although no bug has
  been filed. This update fixes this by installing them into a versioned
  directory and making the library look for them there. The second one is
  that due to a bug in the build system that we had to work around, we
  accidentally didn't enable gettext translation in the install command,
  which caused the library to be recompiled without translation support
  (csound is built with scons). There are a few other unrelated changes,
  which is why I was hesitant to ask for an update, but csound has been in
  unstable for 59 days now with no newly-reported bugs.

 The full diff is really insane related to the small issues you're
 reporting to be fixed and needing a fix. Is there a way to only backport
 those ?

Yes. The upload should be targeted at testing-proposed-updates?

I have a source package at mentors:
http://mentors.debian.net/debian/pool/main/c/csound/csound_5.08.0.dfsg2-8+lenny1.dsc

Saludos,
Felipe Sateler


signature.asc
Description: This is a digitally signed message part.

Freeze exception for csound

[Felipe Sateler]

Hi release team. I'd like to ask if an update for csound is possible. It 
brings 2 changes that are the reason for the update request. The first one is 
that the csound library comes with a few plugins, but they weren't versioned 
with the library. This violates policy 8.2, although no bug has been filed. 
This update fixes this by installing them into a versioned directory and 
making the library look for them there. The second one is that due to a bug 
in the build system that we had to work around, we accidentally didn't enable 
gettext translation in the install command, which caused the library to be 
recompiled without translation support (csound is built with scons).
There are a few other unrelated changes, which is why I was hesitant to ask 
for an update, but csound has been in unstable for 59 days now with no 
newly-reported bugs.

The relevant changelog entry:

csound (1:5.08.2~dfsg-1) unstable; urgency=low

  [ Jonas Smedegaard ]
  * Rerelease same upstream tarball by more accurate name: Upstream
changelog and other upstream packages indicate that
microversion is stripped from upstream tarballs.
This is also an excuse to adjust dfsg extension to be below upstream
(in case they should decide to rerelease without non-DFSG source).
  * Update CDBS snippets:
+ Update copyright-check.mk to closer match new proposed copyright
  format, optionally break on changes, and cleaup properly.  Update
  copyright-hints.
+ Use new local package-relations.mk to resolve, cleanup and apply
  CDBS-declared (build-)dependencies.
+ Use new local upstream-tarball.mk to implement get-orig-source and
  more.
+ Update README.cdbs-tweaks.
  * Add DEB_MAINTAINER_MODE in debian/rules (thanks to Romain Beauxis).
  * Semi-auto-update debian/control to update dependencies:
  DEB_MAINTAINER_MODE=1 fakeroot debian/rules clean
  * Rewrite watch file.

  [ Felipe Sateler ]
  * Install examples in csound, pd-csound, python-csoundac, libcsnd-java and
tclcsound.
  * Make the csound library package policy compliant:
- Make the plugins versioned (they are tied to the library anyway).
- Split the translations to the csound package.
This should make transitions easier if/when csound changes ABI.
  * Specify useGettext at install time so gettext isn't disabled.
  * Make pd-csound depend on pd as fallback for puredata, to allow using
the alternative pd-extended (Closes: #491966).

 -- Jonas Smedegaard [EMAIL PROTECTED]  Thu, 31 Jul 2008 01:17:52 +0200


Saludos,
Felipe Sateler


signature.asc
Description: This is a digitally signed message part.

Please allow checkinstall in testing

[Felipe Sateler]

After the usual 10 days for low priority packages (which are due today[1]),
I'd like checkinstall to progagate into testing. This is because Sarge
shipped with a version of checkinstall (1.5.3-3), and after it's release an
RC bug[2] was filed against it and later on removed from testing. The
latest checkinstall upload (1.6.1-1) fixes this bug and thus I think it
should go into testing. Checkinstall has no rdepends, so it has no impact
on other packages.

Thanks

[1] It was accepted on Dec 7
[2] Bug #342578

-- 

Felipe Sateler


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]