Path: csiph.com!3.eu.feeder.erje.net!feeder.erje.net!news.unit0.net!news.mixmin.net!news.albasani.net!tahina.priv.at!bofh.it!news.nic.it!robomod From: Andreas Tille Newsgroups: linux.debian.devel.mentors,linux.debian.maint.python Subject: Re: [RFC] python-cobra, python3-sbml5 Date: Sun, 05 Apr 2020 12:30:01 +0200 Message-ID: References: X-Original-To: Nilesh Patra X-Mailbox-Line: From debian-mentors-request@lists.debian.org Sun Apr 5 10:20:45 2020 Old-Return-Path: X-Amavis-Spam-Status: No, score=-5 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, MEDS2=2] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -4.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) X-Mailing-List: archive/latest/102227 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20200405102025.GO7599@an3as.eu Approved: robomod@news.nic.it Lines: 37 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-mentors@lists.debian.org, Debian Python X-Original-Date: Sun, 5 Apr 2020 12:20:25 +0200 X-Original-Message-ID: <20200405102025.GO7599@an3as.eu> X-Original-References: <20200405061355.GI7599@an3as.eu> Xref: csiph.com linux.debian.devel.mentors:43514 linux.debian.maint.python:12428 On Sun, Apr 05, 2020 at 03:40:56PM +0530, Nilesh Patra wrote: > > > '_libsbml' file which corresponds to libsbml (with python3-sbml5 as a > > > provide) package. When I dug into looking at libsbml, I noticed that the > > > relevant file (libsbml.py) which throws error > > > is generated with swig-3.0 by the upstream [3] > > > > I admit I'm absolutely naive about swig - but if libsbml.py is really > > autogenerated what about re-generating it with swig-4? > > I think there's a miscommunication here. The file in the archive(on doing > $apt source python3-sbml5) is generated with swig-4 already, while it's > generated with swig-3 upstream. > Hence the issue. Ahhh, so it is regenerated in the Debian package build process but it conflicts with other parts of the upstream code? Did I now understood correctly? I wonder if we should exclude this kind of autogenerated code inside the source tarball since we are repackaging the source anyway to exclude some files for policy reasons. I'm doing so in other source tarballs for instance with cython files to be absolutely sure that this code is regenerated. This would probably not solve the build issue but might be a good idea in general. What do you think? Kind regards Andreas. > > > [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955656 > > > > > > [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955656#10 > > > > > > [3]: https://salsa.debian.org/med-team/libsbml/-/blob/master/src/bindings/python/libsbml.py?expanded=true&viewer=simple -- http://fam-tille.de