Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#851678: RM: openchange -- RoQA; incompatible with updated samba

0 views
Skip to first unread message

Andreas Beckmann

unread,
Jan 17, 2017, 9:40:02 AM1/17/17
to
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.d...@packages.debian.org
Usertags: rm

Hi,

I'm not perfectly convinced about this RM request, but something should
happen with openchange in stable:

* openchangeproxy (1:2.2-5) is uninstallable in stable (#838671)
samba-libs has a Breaks: openchangeproxy (<< 1:2.2-6) that stems from
the first samba 4.2 upload to jessie-security:

samba (2:4.2.10+dfsg-0+deb8u1) jessie-security; urgency=high

* Revert the change to made libsamba-debug a library, allowing openchange
to link to Samba 4.2
* Add Breaks against openchangeproxy that uses an API and ABI that has changed

* openchange FTBFS in stable (I just mentioned this in #838671)
(the version in stable was most likely built against samba 2:4.1.13+dfsg-4)

* openchange was removed from unstable due to incompatibility with
newer samba versions

* downside: openchange builds a lot more packages than just openchangeproxy
these are all still installable in stable (according to piuparts)


Andreas

Paul Wise

unread,
Jan 17, 2017, 6:30:02 PM1/17/17
to
On Tue, Jan 17, 2017 at 10:26 PM, Andreas Beckmann wrote:

> I'm not perfectly convinced about this RM request, but something should
> happen with openchange in stable:

At $work we rely on openchange but not openchangeproxy. We know it was
removed from stretch and later but were assuming we could use it on
jessie, once we have migrated from wheezy. The wheezy to jessie
migration is blocked by some regression bugs in jessie Linux CIFS
support that we are in the process of debugging. Once we have fixed
that, we would like to start migrating systems to jessie. Post-jessie
we don't yet have a strategy but are looking into options.

> * openchangeproxy (1:2.2-5) is uninstallable in stable (#838671)
> samba-libs has a Breaks: openchangeproxy (<< 1:2.2-6) that stems from
> the first samba 4.2 upload to jessie-security:

I guess this could be fixed by a new upload that either drops
openchangeproxy or fixes the API/ABI usage.

> * openchange FTBFS in stable (I just mentioned this in #838671)
> (the version in stable was most likely built against samba 2:4.1.13+dfsg-4)

This looks like the API issue in openchangeproxy mentioned in the
samba changelog from the build log messages you posted.

This is the openchange bug and patch for this specific FTBFS:

https://github.com/openchange/openchange/issues/249
https://github.com/openchange/openchange/commit/73a49af50bf0a496cfe62f49e60a662f1d04d685.patch

> * openchange was removed from unstable due to incompatibility with
> newer samba versions

Unfortunately the openchange project is dead upstream so it won't be
coming back.

> * downside: openchange builds a lot more packages than just openchangeproxy
> these are all still installable in stable (according to piuparts)

At $work we rely on openchangeclient and several of the -dev packages.

--
bye,
pabs

https://wiki.debian.org/PaulWise

Paul Wise

unread,
Jan 21, 2017, 3:10:02 AM1/21/17
to
Control: retitle -1 jessie-pu: package openchange/1:2.2-5+deb8u1
Control: release.d...@packages.debian.org
Control: usertags -1 - rm + pu

On Wed, 18 Jan 2017 07:21:49 +0800 Paul Wise wrote:

> This looks like the API issue in openchangeproxy mentioned in the
> samba changelog from the build log messages you posted.

> This is the openchange bug and patch for this specific FTBFS:

> https://github.com/openchange/openchange/issues/249
> https://github.com/openchange/openchange/commit/73a49af50bf0a496cfe62f49e60a662f1d04d685.patch

I've tested that this fixes the FTBFS in openchange.

I'm unable to test that openchangeproxy still works but the patch looks
like a fairly straight forward update to the newer samba APIs.

The rest of the binary packages still work fine in my tests. 

I've attached a patch for a pu to the openchange package in jessie.
openchange_2.2-5_2.2-5+deb8u1.debdiff
signature.asc

Debian Bug Tracking System

unread,
Jan 21, 2017, 3:10:03 AM1/21/17
to
Processing control commands:

> retitle -1 jessie-pu: package openchange/1:2.2-5+deb8u1
Bug #851678 [release.debian.org] RM: openchange -- RoQA; incompatible with updated samba
Changed Bug title to 'jessie-pu: package openchange/1:2.2-5+deb8u1' from 'RM: openchange -- RoQA; incompatible with updated samba'.
> release.d...@packages.debian.org
Unknown command or malformed arguments to command.

> usertags -1 - rm + pu
Unknown command or malformed arguments to command.


--
851678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Andreas Beckmann

unread,
Jan 21, 2017, 4:20:02 AM1/21/17
to
On 2017-01-21 09:03, Paul Wise wrote:
> Control: retitle -1 jessie-pu: package openchange/1:2.2-5+deb8u1

Thanks for taking over!

>> https://github.com/openchange/openchange/issues/249
>> https://github.com/openchange/openchange/commit/73a49af50bf0a496cfe62f49e60a662f1d04d685.patch
>
> I've tested that this fixes the FTBFS in openchange.
>
> I'm unable to test that openchangeproxy still works but the patch looks
> like a fairly straight forward update to the newer samba APIs.

But openchangeproxy will still not be installable in jessie since
samba-libs has

Conflicts: openchangeproxy (<< 1:2.2-6)

Lowering this to (<< 1:2.2-5+deb8u1) would require another samba upload
to jessie (or piggybacking it on the next security upload).

Since noone has complained about this uninstallability so far in a
production environment, maybe the package is not in wide use ... and
dropping it might be another option.


Andreas

Debian Bug Tracking System

unread,
Jan 21, 2017, 4:40:02 AM1/21/17
to
Processing control commands:

> retitle -1 jessie-pu: package openchange/1:2.2-6+deb8u1
Bug #851678 [release.debian.org] jessie-pu: package openchange/1:2.2-5+deb8u1
Changed Bug title to 'jessie-pu: package openchange/1:2.2-6+deb8u1' from 'jessie-pu: package openchange/1:2.2-5+deb8u1'.

Paul Wise

unread,
Jan 21, 2017, 4:40:02 AM1/21/17
to
Control: retitle -1 jessie-pu: package openchange/1:2.2-6+deb8u1

On Sat, 2017-01-21 at 10:13 +0100, Andreas Beckmann wrote:

> But openchangeproxy will still not be installable in jessie since
> samba-libs has
>
> Conflicts: openchangeproxy (<< 1:2.2-6)

I forgot about that. Since 1:2.2-6 was once in Debian, it would be
probably best to use 1:2.2-6~deb8u1 but that doesn't match what samba
used in the Breaks, so it will have to be 1:2.2-6+deb8u1, which should
be fine since 1:2.2-7 was the latest version in Debian stretch.
I'll change the version number and upload once I have an ack.

http://snapshot.debian.org/package/openchange/

> Lowering this to (<< 1:2.2-5+deb8u1) would require another samba upload
> to jessie (or piggybacking it on the next security upload).

I think that isn't a useful use of samba maintainer/buildd time :)

> Since noone has complained about this uninstallability so far in a
> production environment, maybe the package is not in wide use ... and
> dropping it might be another option.

Ack, though the version change I mention above should be fine though.
signature.asc

Debian Bug Tracking System

unread,
Apr 24, 2017, 5:20:01 PM4/24/17
to
Processing control commands:

> tags -1 + confirmed
Bug #851678 [release.debian.org] jessie-pu: package openchange/1:2.2-6+deb8u1
Added tag(s) confirmed.

Adam D. Barratt

unread,
Apr 24, 2017, 5:20:02 PM4/24/17
to
Control: tags -1 + confirmed

On Sat, 2017-01-21 at 17:26 +0800, Paul Wise wrote:
> Control: retitle -1 jessie-pu: package openchange/1:2.2-6+deb8u1
>
> On Sat, 2017-01-21 at 10:13 +0100, Andreas Beckmann wrote:
>
> > But openchangeproxy will still not be installable in jessie since
> > samba-libs has
> >
> > Conflicts: openchangeproxy (<< 1:2.2-6)
>
> I forgot about that. Since 1:2.2-6 was once in Debian, it would be
> probably best to use 1:2.2-6~deb8u1 but that doesn't match what samba
> used in the Breaks, so it will have to be 1:2.2-6+deb8u1, which should
> be fine since 1:2.2-7 was the latest version in Debian stretch.
> I'll change the version number and upload once I have an ack.
>
> http://snapshot.debian.org/package/openchange/

That sounds okay, although I wonder if it's worth mentioning the unusual
version progression in the changelog.

Regards,

Adam

Paul Wise

unread,
Apr 24, 2017, 10:10:03 PM4/24/17
to
On Mon, 2017-04-24 at 22:12 +0100, Adam D. Barratt wrote:

> That sounds okay, although I wonder if it's worth mentioning the unusual
> version progression in the changelog.

I've rebuilt the package including this additional changelog entry:

  * Use version -6+ instead of -5+ because samba-libs conflicts with
    openchangeproxy (<< 1:2.2-6), making openchangeproxy -5+ uninstallable.

The result has been uploaded and is on its way to pu-new.
signature.asc

Debian Bug Tracking System

unread,
Apr 25, 2017, 5:40:03 PM4/25/17
to
Processing control commands:

> tags -1 + pending
Bug #851678 [release.debian.org] jessie-pu: package openchange/1:2.2-6+deb8u1
Added tag(s) pending.

Adam D. Barratt

unread,
Apr 25, 2017, 5:40:03 PM4/25/17
to
Control: tags -1 + pending

On Tue, 2017-04-25 at 09:46 +0800, Paul Wise wrote:
> On Mon, 2017-04-24 at 22:12 +0100, Adam D. Barratt wrote:
>
> > That sounds okay, although I wonder if it's worth mentioning the unusual
> > version progression in the changelog.
>
> I've rebuilt the package including this additional changelog entry:
>
> * Use version -6+ instead of -5+ because samba-libs conflicts with
> openchangeproxy (<< 1:2.2-6), making openchangeproxy -5+ uninstallable.
>
> The result has been uploaded and is on its way to pu-new.

Thanks; flagged for acceptance.

Regards,

Adam

Debian Bug Tracking System

unread,
May 6, 2017, 10:00:03 AM5/6/17
to
Your message dated Sat, 06 May 2017 14:44:18 +0100
with message-id <1494078258.2...@adam-barratt.org.uk>
and subject line Closing bugs for updates included in 8.8
has caused the Debian Bug report #851678,
regarding jessie-pu: package openchange/1:2.2-6+deb8u1
to be marked as done.

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

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