[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#982164: RFS: geda-gaf/1.10.2-2 [ITA] -- GPL EDA -- Electronics design software

Kai-Martin Knaak kirjoitti 8.2.2021 klo 16.16:
> On Sun, 7 Feb 2021 11:13:53 +0200 Juhani Numminen
> <juhaninumminen0@gmail.com> wrote:
>> Please also close these two bugs in your changelog:
> done.


>> The mentors.d.n page shows that the packages still depend on python2,
>> so are you first making the package name change python->python2
>> (#966736) and only later switching to python3 (#936593)?
> yes.
> I know, migration to python3 is inevitable. However, the transition
> from geda-gaf-1.8 to 1.10 involved large amounts of python code. I
> talked to upstream (Roland Lutz): Migration to python3 will be a little
> tedious and non-trivial. It will be the main focus of upcoming
> development, non the less.
>> If that's the
>> case, we need to unmerge #966736 and #936593.
> Beeing new to Debian package maintenance, I am unsure how to proceed on
> this. Should I act on the bugs? Am I allowed to set tags? If so which
> would be appropriate?

Yes, you are allowed to act on them. I don't think there is a need to
set any tags right now. I did the unmerge I mentioned so the two bugs
can now be closed or left open independent of each other.

In the changelog you'll need to remove "Closes: #936593" as in fact
this upload does not drop python2 depends, while you should add a 
line explaining that unversioned python dependency has been converted
to python2, and Closes: #966736.

Another thing. There is a removal of fam in progress.[1] Please edit
Build-Depends so that you don't introduce a dependency on libfam-dev.

The xorn executable is not too well suited to be in libgeda47 because
its name does not change with SONAME which would make library
transitions difficult.[2] So perhaps put xorn live in geda-utils then?

[1] https://bugs.debian.org/966273
[2] https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#shared-library-support-files


Reply to: