Bug#894297: Intent to NMU cyrus-sasl2 (was: [PATCH] cyrus-sasl2: please add build-profile support)

2018-04-20 Thread Ondřej Surý 
Ack, go ahead with NMU.

I'll look into moving cyrus-sasl2 to salsa.d.o in the near future.

Ondrej
-- 
Ondřej Surý 

On Fri, Apr 20, 2018, at 17:04, Roberto C. Sánchez wrote:
> Hi Karsten,
> 
> On Fri, Apr 20, 2018 at 04:51:04PM +0200, Karsten Merker wrote:
> > 
> > - Judging from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799864,
> >   the package changelog and the lack of activity on the
> >   pkg-cyrus-sasl2-debian-devel mailinglist, you appear to be the
> >   only remaining person in the cyrus-sasl2 packaging team.
> > 
> > - You have marked all your packages as "Low-Threshold-NMU" at
> >   https://wiki.debian.org/LowThresholdNmu.
> > 
> > - The patch from bug #894297 is largely noninvasive as it doesn't
> >   touch the actual cyrus-sasl2 codebase, only has any effect
> >   at all if a build-profile is explicitly enabled during building
> >   the package and uses the existing DEB_BUILD_OPTIONS-based
> >   infrastructure in debian/rules.
> > 
> For what it is worth, I still consider myself a member of the team. I
> agree that cyrus-sasl2 is in need of a great deal of attention. This
> semester at school has been very busy, though it is almost over. It will
> probably be at least a few weeks before things calm down enough for me
> to devote a sufficiently large block of time/effort to cyrus-sasl2
> maintenance.
> 
> As far as I am concerned, I welcome your NMU, so please go ahead with
> it.
> 
> Regards,
> 
> -Roberto
> -- 
> Roberto C. Sánchez
> 
> ___
> Pkg-cyrus-sasl2-debian-devel mailing list
> pkg-cyrus-sasl2-debian-de...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-cyrus-sasl2-debian-devel

Bug#894297: Intent to NMU cyrus-sasl2 (was: [PATCH] cyrus-sasl2: please add build-profile support)

2018-04-20 Thread Roberto C . Sánchez 
Hi Karsten,

On Fri, Apr 20, 2018 at 04:51:04PM +0200, Karsten Merker wrote:
> 
> - Judging from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799864,
>   the package changelog and the lack of activity on the
>   pkg-cyrus-sasl2-debian-devel mailinglist, you appear to be the
>   only remaining person in the cyrus-sasl2 packaging team.
> 
> - You have marked all your packages as "Low-Threshold-NMU" at
>   https://wiki.debian.org/LowThresholdNmu.
> 
> - The patch from bug #894297 is largely noninvasive as it doesn't
>   touch the actual cyrus-sasl2 codebase, only has any effect
>   at all if a build-profile is explicitly enabled during building
>   the package and uses the existing DEB_BUILD_OPTIONS-based
>   infrastructure in debian/rules.
> 
For what it is worth, I still consider myself a member of the team. I
agree that cyrus-sasl2 is in need of a great deal of attention. This
semester at school has been very busy, though it is almost over. It will
probably be at least a few weeks before things calm down enough for me
to devote a sufficiently large block of time/effort to cyrus-sasl2
maintenance.

As far as I am concerned, I welcome your NMU, so please go ahead with
it.

Regards,

-Roberto
-- 
Roberto C. Sánchez

Bug#894297: Intent to NMU cyrus-sasl2 (was: [PATCH] cyrus-sasl2: please add build-profile support)

2018-04-20 Thread Karsten Merker 
On Wed, Mar 28, 2018 at 04:53:43PM +0200, Karsten Merker wrote:

[Architeture bootstrapping issues with cyrus-sasl2]
> Cyrus-sasl2 is involved in a circular dependency chain whose
> untangling requires building the package in multiple steps with
> reduced functionality and reduced build-dependencies.  To achieve
> that, debian/rules currently supports passing a number of options
> (no-sql, no-ldap and no-gssapi) in $(DEB_BUILD_OPTIONS).  This
> mechanism has the limitation that it requires manually adjusting the
> build-dependency list based on the options set and makes it hard to
> autobuild the package in a bootstrapping context.  The use of
> build-profiles (https://wiki.debian.org/BuildProfileSpec) would make
> this process quite a bit easier.  Attached is a patch that adds
> build-profile support to the packge while keeping the original
> $(DEB_BUILD_OPTIONS)-based mechanism in place.
> 
> The build profile names follow the "extension namespace" conventions
> from the build profile specification:
> 
> DEB_BUILD_OPTIONS -> build-profile name
> -
> no-sql-> pkg.cyrus-sasl2.nosql
> no-ldap   -> pkg.cyrus-sasl2.noldap
> no-gssapi -> pkg.cyrus-sasl2.nogssapi
> 
> It would be very helpful for our bootstrapping efforts if you could
> upload a version of the cyrus-sasl2 package with this patch applied to
> unstable in the near future.  For a standard build the patch changes
> nothing, so there should be no significant risk in applying it.

Hello Ondřej,

unless you should object, I intend to perform an NMU of cyrus-sasl2
with the patch from bug #894297 under Low-Threshold-NMU rules on
Sunday.

Reasons:

- Judging from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799864,
  the package changelog and the lack of activity on the
  pkg-cyrus-sasl2-debian-devel mailinglist, you appear to be the
  only remaining person in the cyrus-sasl2 packaging team.

- You have marked all your packages as "Low-Threshold-NMU" at
  https://wiki.debian.org/LowThresholdNmu.

- The patch from bug #894297 is largely noninvasive as it doesn't
  touch the actual cyrus-sasl2 codebase, only has any effect
  at all if a build-profile is explicitly enabled during building
  the package and uses the existing DEB_BUILD_OPTIONS-based
  infrastructure in debian/rules.

Regards,
Karsten
-- 
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.