Report forwarded
to debian-bugs-dist@lists.debian.org, debian@jff-webhosting.net: Bug#913125; Package src:sane-backends.
(Wed, 07 Nov 2018 09:39:07 GMT) (full text, mbox, link).
Acknowledgement sent
to Jörg Frings-Fürst <debian@jff.email>:
New Bug report received and forwarded. Copy sent to debian@jff-webhosting.net.
(Wed, 07 Nov 2018 09:39:07 GMT) (full text, mbox, link).
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: missing requested rename of libsane
Date: Wed, 07 Nov 2018 10:35:45 +0100
Source: sane-backends
Version: 1.0.27-3.1
Severity: serious
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hello,
with the upstream release 1.0.27 are some libraray functions
are removed.
According to Debian Policy 8.6.2, renaming of the SONAME and the
library package name is possible for non-backwards compatible ABI
changes.
As the maintainer of this package, I object to the withdrawal
of my changes by the NMU in version 1.0.27-3.1.
CU
Jörg
- -- System Information:
Debian Release: buster/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing'), (300, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-2-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAlvisfEACgkQCfifPIyh
0l2VKA//corijAhDa3zJq+hG07HzCh2BZszjnzeE3eHWfjQybhuuvq0JwjDiBCUk
PB4V5JbzZ562b0yTaXGySNuT8lOm2BtQrw4CuE+8RXe0Ft3kY91vErEruos6EuNu
85R1IUG24RdaqdSkaxmCjVIQus1LBbxrkKmqJez8Mm0kmnp9cQBOedSQ2EDpJ3Up
1SurzaBSD9RLnYIVtZY+Vuf/kU34gKHHojHUT8pjKtxL5KHVxEoH7tCBkSBiRJTo
sw7qPkGirfQ0L4wjE831CRu6N+1Y5wD7Xf/N6vNuxioa8hr8Jz+sfrBqyWISwuW5
NNbvUvjMhXsDaY3GTW3Nof7695Y7QRGyhlVPiuR1hD6ADb3PGwMaSwVejuYn4eRh
9DTOq4RcaNAgAR15rsYSrLfGvvgTsp9Fcy9t8cBraCEjcR5XZh2d1Zg1WkqMnblX
0iaKcGlPfQZVjXL2A/CbboRE3UvVUuFCWDQWjJ4WcqV2O311D2/wgyYC28p533Qa
JOvJ71jkIZnGlRegSIG8xsQX1rnIowEq1+ogiHneLqan+eFeJunR13w2BB3KgwC2
xHIEU8K25HfI3OLXKIlhOHyPfrWmpLLgKuVy6xQj3+naF8fYJ2/rr6f1qiMNi52w
g0PumwWPPho9G7SKtuA06Ab+CuJm0cEfCHMqEsi1kjT2pgDDRM8=
=7kvt
-----END PGP SIGNATURE-----
Information forwarded
to debian-bugs-dist@lists.debian.org, Jörg Frings-Fürst <debian@jff.email>: Bug#913125; Package src:sane-backends.
(Wed, 07 Nov 2018 10:30:06 GMT) (full text, mbox, link).
Acknowledgement sent
to Gianfranco Costamagna <locutusofborg@debian.org>:
Extra info received and forwarded to list. Copy sent to Jörg Frings-Fürst <debian@jff.email>.
(Wed, 07 Nov 2018 10:30:06 GMT) (full text, mbox, link).
control: tags -1 moreinfo
Hello Jörg
> with the upstream release 1.0.27 are some libraray functions
> are removed.
Can you please share also some examples of such libraries?
Are them public or private?
> According to Debian Policy 8.6.2, renaming of the SONAME and the
> library package name is possible for non-backwards compatible ABI
> changes.
>
> As the maintainer of this package, I object to the withdrawal
> of my changes by the NMU in version 1.0.27-3.1.
>
this seems legit, if you can prove that the ABI changes are affecting
the public library, I would say that a SONAME change is appropriate.
So far, everybody failed at it...
/me is not RT member, no hat on his head
For sure, we should cleanup symbols file wrt the public/private stuff inside them
(cfr: #911597)
Gianfranco
Added tag(s) moreinfo.
Request was from Gianfranco Costamagna <locutusofborg@debian.org>
to 913125-submit@bugs.debian.org.
(Wed, 07 Nov 2018 10:30:06 GMT) (full text, mbox, link).
Information forwarded
to debian-bugs-dist@lists.debian.org, Jörg Frings-Fürst <debian@jff.email>: Bug#913125; Package src:sane-backends.
(Wed, 07 Nov 2018 11:06:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Gianfranco Costamagna <locutusofborg@debian.org>:
Extra info received and forwarded to list. Copy sent to Jörg Frings-Fürst <debian@jff.email>.
(Wed, 07 Nov 2018 11:06:04 GMT) (full text, mbox, link).
To: 913125@bugs.debian.org, debian@jff.email, cbmuser@debian.org
Subject: Re: missing requested rename of libsane
Date: Wed, 7 Nov 2018 12:03:57 +0100
Hello Jörg!
you might feel somewhat lost, at least I'm feeling that way, so I'll try to sum up what changed
(tl;dr, the current status quo seems to be appropriate and I think the package needs no changes right now).
You never answered to what Julien asked you, and his were legit questions:
"libsane was renamed to libsane1 for apparently no good reason. Renames
for library packages should be tied to ABI breakage (and associated
SONAME changes).
Either there was ABI breakage and the SONAME should be bumped (and
Provides: libsane would be wrong), or there wasn't and the package name
change ought to be reverted."
I get your "hey, the soname was wrong and not matching upstream, change it and now they match" idea, and I think it had good reasons,
but the problem is really another.
You can't just change SONAME if you don't have good reasons to do it, and this was the reason for the whole mess.
The flow chart is usually when an upstream library gets ABI breakages:
1) check for ABI changes and in case upstream SONAME didn't change, well this is an upstream issue, so ask them to release
a new library and bump SONAME.
Bumping it in Debian, without upstream doing it, is a mess, because third party libraries might start crashing if they find the linked library in the system, but with different ABI.
2) if upstream didn't change SONAME, and ABI didn't change, upload as-is
in your case, what happened was a contradicting explanation for the renaming.
You said "ABI changed, so the renaming is appropriate", but you started providing the old binary name in the new one.
This is the error that has been pointed out by Release Team, and no answer has been provided for it (as far as I can see).
Claiming an ABI change, and provide the old package, is a good way to tell apt to not enforce the upgrade of reverse-dependencies, and the best way you can have to make reverse-dependencies crash if that code is run :)
So, to sum up, please provide some clear details about ABI changes, and in that case contact upstream to make them aware of the issue.
Otherwise, the current package might be ok as-is.
thanks for understanding, don't hesitate to contact me also privately in case I missed something, or I didn't explain my reasoning
correctly.
Gianfranco
Information forwarded
to debian-bugs-dist@lists.debian.org: Bug#913125; Package src:sane-backends.
(Wed, 07 Nov 2018 12:00:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Jörg Frings-Fürst <debian@jff.email>:
Extra info received and forwarded to list.
(Wed, 07 Nov 2018 12:00:05 GMT) (full text, mbox, link).
Hello,
Am Mittwoch, den 07.11.2018, 11:27 +0100 schrieb Gianfranco Costamagna:
> control: tags -1 moreinfo
>
> Hello Jörg
>
> > with the upstream release 1.0.27 are some libraray functions
> > are removed.
>
> Can you please share also some examples of such libraries?
> Are them public or private?
>
I have build for testing the symbolsfiles from release 1.0.25-4.1
and 1.0.27-4 with --exclude=/sane/ to get only the public symbols.
The resulting diff (diff -Naur symbols_1.0.25-4.1 symbols_1.0.27-4
>1.0.25-4.1_1.0.27-4.diff) is attached.
>
> > According to Debian Policy 8.6.2, renaming of the SONAME and the
> > library package name is possible for non-backwards compatible ABI
> > changes.
> >
> > As the maintainer of this package, I object to the withdrawal
> > of my changes by the NMU in version 1.0.27-3.1.
> >
>
> this seems legit, if you can prove that the ABI changes are affecting
> the public library, I would say that a SONAME change is appropriate.
>
> So far, everybody failed at it...
>
> /me is not RT member, no hat on his head
>
> For sure, we should cleanup symbols file wrt the public/private stuff
> inside them
> (cfr: #911597)
>
> Gianfranco
CU
Jörg
--
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key : 8CA1D25D
CAcert Key S/N : 0E:D4:56
Old pgp Key: BE581B6E (revoked since 2014-12-31).
Jörg Frings-Fürst
D-54470 Lieser
git: https://jff.email/cgit/
Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst
My wish list:
- Please send me a picture from the nature at your home.
Information forwarded
to debian-bugs-dist@lists.debian.org, Jörg Frings-Fürst <debian@jff.email>: Bug#913125; Package src:sane-backends.
(Wed, 07 Nov 2018 12:45:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Michael Biebl <biebl@debian.org>:
Extra info received and forwarded to list. Copy sent to Jörg Frings-Fürst <debian@jff.email>.
(Wed, 07 Nov 2018 12:45:03 GMT) (full text, mbox, link).
Information forwarded
to debian-bugs-dist@lists.debian.org, Jörg Frings-Fürst <debian@jff.email>: Bug#913125; Package src:sane-backends.
(Wed, 07 Nov 2018 12:57:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Michael Biebl <biebl@debian.org>:
Extra info received and forwarded to list. Copy sent to Jörg Frings-Fürst <debian@jff.email>.
(Wed, 07 Nov 2018 12:57:03 GMT) (full text, mbox, link).
On Wed, 7 Nov 2018 13:42:00 +0100 Michael Biebl <biebl@debian.org> wrote:
> I then built 1.0.27 with this symbols file, the result is:
Let me add here, that many of those (new) symbols are not part of the
public API as declared in sane.h, so should probably be hidden upstream
or at least marked as optional downstream. The former is preferrable.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
Information forwarded
to debian-bugs-dist@lists.debian.org, Jörg Frings-Fürst <debian@jff.email>: Bug#913125; Package src:sane-backends.
(Wed, 07 Nov 2018 13:03:02 GMT) (full text, mbox, link).
Acknowledgement sent
to Michael Biebl <biebl@debian.org>:
Extra info received and forwarded to list. Copy sent to Jörg Frings-Fürst <debian@jff.email>.
(Wed, 07 Nov 2018 13:03:03 GMT) (full text, mbox, link).
Am 07.11.18 um 13:53 schrieb Michael Biebl:
> On Wed, 7 Nov 2018 13:42:00 +0100 Michael Biebl <biebl@debian.org> wrote:
>
>> I then built 1.0.27 with this symbols file, the result is:
>
> Let me add here, that many of those (new) symbols are not part of the
> public API as declared in sane.h, so should probably be hidden upstream
> or at least marked as optional downstream. The former is preferrable.
>
Attached is the list of symbols which are part of the ABI but not part
of the public API. Ideally those should not be exported by libsane.so.1
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
Information forwarded
to debian-bugs-dist@lists.debian.org: Bug#913125; Package src:sane-backends.
(Wed, 07 Nov 2018 13:42:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Jörg Frings-Fürst <debian@jff.email>:
Extra info received and forwarded to list.
(Wed, 07 Nov 2018 13:42:04 GMT) (full text, mbox, link).
Information forwarded
to debian-bugs-dist@lists.debian.org, Jörg Frings-Fürst <debian@jff.email>: Bug#913125; Package src:sane-backends.
(Wed, 07 Nov 2018 14:03:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Michael Biebl <biebl@debian.org>:
Extra info received and forwarded to list. Copy sent to Jörg Frings-Fürst <debian@jff.email>.
(Wed, 07 Nov 2018 14:03:04 GMT) (full text, mbox, link).
Am 07.11.18 um 14:40 schrieb Jörg Frings-Fürst:
> and extract the symbols files from the resulting *.deb files.
>
> Both are attached.
The symbols files you attached include the symbols for the backends. You
need to exclude those.
Picking the first symbol in your list as an example:
backend/kvs1025_low.c:AllocateImageBuffer (PKV_DEV dev)
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
Information forwarded
to debian-bugs-dist@lists.debian.org, Jörg Frings-Fürst <debian@jff.email>: Bug#913125; Package src:sane-backends.
(Wed, 07 Nov 2018 14:09:02 GMT) (full text, mbox, link).
Acknowledgement sent
to Michael Biebl <biebl@debian.org>:
Extra info received and forwarded to list. Copy sent to Jörg Frings-Fürst <debian@jff.email>.
(Wed, 07 Nov 2018 14:09:02 GMT) (full text, mbox, link).
Control: severity -1 normal
Am 07.11.18 um 13:42 schrieb Michael Biebl:
> The removal of toupper_ascii is strictly speaking an ABI break, but this
> never was part of the public API (checking the header files of 1.0.25).
> So no bumping the soname for the removal of toupper_ascii is okayish.
Given my findings, I'm downgrading the severity as there is not really
an ABI break.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
Severity set to 'normal' from 'serious'
Request was from Michael Biebl <biebl@debian.org>
to 913125-submit@bugs.debian.org.
(Wed, 07 Nov 2018 14:09:02 GMT) (full text, mbox, link).
Information forwarded
to debian-bugs-dist@lists.debian.org, Jörg Frings-Fürst <debian@jff.email>: Bug#913125; Package src:sane-backends.
(Wed, 07 Nov 2018 14:18:02 GMT) (full text, mbox, link).
Acknowledgement sent
to Michael Biebl <biebl@debian.org>:
Extra info received and forwarded to list. Copy sent to Jörg Frings-Fürst <debian@jff.email>.
(Wed, 07 Nov 2018 14:18:02 GMT) (full text, mbox, link).
Am 07.11.18 um 15:00 schrieb Michael Biebl:
> Am 07.11.18 um 14:40 schrieb Jörg Frings-Fürst:
>
>> and extract the symbols files from the resulting *.deb files.
>>
>> Both are attached.
>
> The symbols files you attached include the symbols for the backends. You
> need to exclude those.
> Picking the first symbol in your list as an example:
>
> backend/kvs1025_low.c:AllocateImageBuffer (PKV_DEV dev)
Or another way to investigate this is to use
objdump -T /usr/lib/x86_64-linux-gnu/libsane.so.1.0.27
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
Information forwarded
to debian-bugs-dist@lists.debian.org: Bug#913125; Package src:sane-backends.
(Wed, 07 Nov 2018 15:51:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Jörg Frings-Fürst <debian@jff.email>:
Extra info received and forwarded to list.
(Wed, 07 Nov 2018 15:51:04 GMT) (full text, mbox, link).
To: Michael Biebl <biebl@debian.org>, 913125@bugs.debian.org, Gianfranco
Costamagna <locutusofborg@debian.org>
Subject: Re: Bug#913125: missing requested rename of libsane
Date: Wed, 07 Nov 2018 16:49:07 +0100
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
severity 913125 serious
thanks
Hi,
Am Mittwoch, den 07.11.2018, 15:05 +0100 schrieb Michael Biebl:
> Control: severity -1 normal
>
> Am 07.11.18 um 13:42 schrieb Michael Biebl:
> > The removal of toupper_ascii is strictly speaking an ABI break, but
> > this
> > never was part of the public API (checking the header files of
> > 1.0.25).
> > So no bumping the soname for the removal of toupper_ascii is
> > okayish.
>
> Given my findings, I'm downgrading the severity as there is not
> really
> an ABI break.
>
- From [1]:
> sanei_init_debug@Base 1.0.25
> - toupper_ascii@Base 1.0.25
> + sanei_lm983x_init@Base 1.0.27-3.1
and
> + sanei_w_word@Base 1.0.27-3.1
> +#MISSING: 1.0.27-3.1# toupper_ascii@Base 1.0.25
CU
Jörg
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913125#27
- --
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key : 8CA1D25D
CAcert Key S/N : 0E:D4:56
Old pgp Key: BE581B6E (revoked since 2014-12-31).
Jörg Frings-Fürst
D-54470 Lieser
git: https://jff.email/cgit/
Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst
My wish list:
- Please send me a picture from the nature at your home.
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAlvjCXMACgkQCfifPIyh
0l2jHA//Xh7KcWQO3+Mb8VFCK/G/Uxf8/JtCHzdoTvbPVAfnnZ7fYKUkbextZv08
yRO7y7FlUUtkuGm8ZjSI8lxmMcu1ih4YJBZ6bl6QMWfRsLbt4nuMiv6kK0ZPwo+7
7B6h1TEC0StdtRGp7K6dXwopa10JNEsLtcy6jfZ7uSDNatI8sOrSEahPszqwDwvs
4oZADVlkMkkHJ1GiiSJMe8RIo6DwF5jz7n4s4pmWyqxkIW2dpfg5OEeiXl0ZKJpe
v/qN5fULSSxIsuvAiJgcSWIcdXLWEH2MHLz00K/9dDfvAKPqiBUNsdIyPdWm+eGl
lCEGM7DAfqWrn7k9oQ+kAxGWYfKmW64NeGMCC5ZyOHfWTSnLeEiVS4kQYwsKPeLp
ATcqP2wafujOeq5jeWyh8TbPNxxbWtFdWj0MwWreU6gfiIVzg7eRIkN8lzxRsSId
ylJDMtn25IRSTEmXOsCDfdSdv5Ydm5JiuZVLb6Tfz5L+d1aq6bQUAGdSe+6i6iKE
Ek7wS08EGHKAMVPdmjSC6Yu3OodPcmY96fnhhvaLTDaxgXJ1iqELHJvHEhQdrNw4
OGSpn5QEW9d6N3Jd1RkZDqc1yGLCzsTG4YY0txgFPGjh2y6IK0igb6rW+aonOA+1
fqILGev8H8YjhbltRWlRR1tvNMa6VPwZog7iiPfj/fpo1M0u16o=
=Cc58
-----END PGP SIGNATURE-----
Severity set to 'serious' from 'normal'
Request was from Jörg Frings-Fürst <debian@jff.email>
to control@bugs.debian.org.
(Wed, 07 Nov 2018 15:51:05 GMT) (full text, mbox, link).
Information forwarded
to debian-bugs-dist@lists.debian.org, Jörg Frings-Fürst <debian@jff.email>: Bug#913125; Package src:sane-backends.
(Wed, 07 Nov 2018 16:00:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Michael Biebl <biebl@debian.org>:
Extra info received and forwarded to list. Copy sent to Jörg Frings-Fürst <debian@jff.email>.
(Wed, 07 Nov 2018 16:00:03 GMT) (full text, mbox, link).
Am 07.11.18 um 16:49 schrieb Jörg Frings-Fürst:
> severity 913125 serious
> thanks
>
> Hi,
>
> Am Mittwoch, den 07.11.2018, 15:05 +0100 schrieb Michael Biebl:
>> Control: severity -1 normal
>
>> Am 07.11.18 um 13:42 schrieb Michael Biebl:
>>> The removal of toupper_ascii is strictly speaking an ABI break, but
>>> this
>>> never was part of the public API (checking the header files of
>>> 1.0.25).
>>> So no bumping the soname for the removal of toupper_ascii is
>>> okayish.
>
>> Given my findings, I'm downgrading the severity as there is not
>> really
>> an ABI break.
>
>
> - From [1]:
>
>> sanei_init_debug@Base 1.0.25
>> - toupper_ascii@Base 1.0.25
>> + sanei_lm983x_init@Base 1.0.27-3.1
>
> and
>
>> + sanei_w_word@Base 1.0.27-3.1
>> +#MISSING: 1.0.27-3.1# toupper_ascii@Base 1.0.25
>
> CU
> Jörg
>
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913125#27
>
Seems you have missed what I wrote there or you deliberately ignored it.
Since you bumped it back to serious, can you please elaborate where the
removal of the private symbol is causing issues?
afaics, toupper_ascii should have been marked as optional to begin with.
Quoting man dpkg-gensymbols
"> optional
> A symbol marked as optional can disappear from the library at any time and that will never cause dpkg-gensymbols to fail. However,
> disappeared optional symbols will continuously appear as MISSING in the diff in each new package revision. This behaviour serves as
> a reminder for the maintainer that such a symbol needs to be removed from the symbol file or readded to the library. When the
> optional symbol, which was previously declared as MISSING, suddenly reappears in the next revision, it will be upgraded back to the
> "existing" status with its minimum version unchanged.
>
> This tag is useful for symbols which are private where their disappearance do not cause ABI breakage. For example, most of C++
> template instantiations fall into this category. Like any other tag, this one may also have an arbitrary value: it could be used to
> indicate why the symbol is considered optional.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
Information forwarded
to debian-bugs-dist@lists.debian.org, Jörg Frings-Fürst <debian@jff.email>: Bug#913125; Package src:sane-backends.
(Fri, 09 Nov 2018 12:27:02 GMT) (full text, mbox, link).
Acknowledgement sent
to Jeremy Bicha <jbicha@debian.org>:
Extra info received and forwarded to list. Copy sent to Jörg Frings-Fürst <debian@jff.email>.
(Fri, 09 Nov 2018 12:27:02 GMT) (full text, mbox, link).
Cc: Jörg Frings-Fürst <debian@jff.email>,
Gianfranco Costamagna <locutusofborg@debian.org>, Michael Biebl <biebl@debian.org>,
Laurent Bigonville <bigon@debian.org>, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Subject: Re: Bug#913125: missing requested rename of libsane
Date: Fri, 9 Nov 2018 07:23:17 -0500
> According to Debian Policy 8.6.2, renaming of the SONAME and the
> library package name is possible for non-backwards compatible ABI
> changes.
Respectfully, the soname was not bumped. If you think that it should
be, why don't you ask the sane-backends developers to do that?
But I agree with the analysis done in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913125#52 and I
think the sane-backends developers will agree that a soname bump isn't
necessary either.
It is unnecessary and unwanted to bump the Debian library package name
when symbols are changed or removed if they are not part of the public
API.
It feels to me like there is widespread agreement that the 1.0.27-3.1
packaging is the best way to handle this (although we should clean up
the symbols files in a future upload). Jörg, what can we do now to
make you happy with this situation so that we can let this version
migrate to Testing and end this dispute we've had for 3 months?
Thanks,
Jeremy Bicha
Reply sent
to Jörg Frings-Fürst <debian@jff.email>:
You have taken responsibility.
(Wed, 14 Nov 2018 14:48:09 GMT) (full text, mbox, link).
Notification sent
to Jörg Frings-Fürst <debian@jff.email>:
Bug acknowledged by developer.
(Wed, 14 Nov 2018 14:48:09 GMT) (full text, mbox, link).
Debbugs is free software and licensed under the terms of the GNU General
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.