terminator in buster
Hey all, forwarding this to the proper list. Could I join PAPT on salsa, so I can setup a git project for terminator? https://salsa.debian.org/python-team/applications Regards Markus Weitergeleitete Nachricht Betreff: terminator in buster Datum: Sun, 27 Jan 2019 13:00:15 +0100 Von: Markus Frosch An: Nicolas Valcárcel Scerpella , Julián Moreno Patiño , Emilio Pozuelo Monfort , Python Applications Packaging Team , 918...@bugs.debian.org Hey all, is anyone taking care about the RC bug [2] in terminator[1] for upcoming buster? I plan to do an NMU over the next days, if no one says stop. I've seen that Emilio did some Python 3 work in experimental, is that ready for unstable? What's the upstream work on this? Maybe I'm going to adopt the package as well, since I'm using terminator. Anyone opposes that? Cheers Markus Frosch [1] https://tracker.debian.org/pkg/terminator [2] https://bugs.debian.org/918149 -- mar...@lazyfrosch.de / lazyfro...@debian.org https://lazyfrosch.de signature.asc Description: OpenPGP digital signature
Packaging google-cloud-python
Hi, I'd like to package several client modules from the google-cloud-python repo[0]. The problem ist, each client module includes google/__init__.py and google/cloud/__init__.py, so installing two ore more of these modules would cause conflicts. My idea to tackle this was to introduce some sort of base package that just includes those two files and have all the individual client packages depend on this one. This brings me to the next problem: Upstream does not provide such a base package. Would it be acceptable to make a debian-only base package with no upstream, pulling those to files from one of the upstream packages? Or are there any other options? [0] https://github.com/googleapis/google-cloud-python Regards, Michael
Re: Packaging google-cloud-python
On Sunday, January 27, 2019 02:34:28 PM Michael Fladischer wrote: > Hi, > > I'd like to package several client modules from the google-cloud-python > repo[0]. The problem ist, each client module includes google/__init__.py > and google/cloud/__init__.py, so installing two ore more of these > modules would cause conflicts. > My idea to tackle this was to introduce some sort of base package that > just includes those two files and have all the individual client > packages depend on this one. > This brings me to the next problem: Upstream does not provide such a > base package. Would it be acceptable to make a debian-only base package > with no upstream, pulling those to files from one of the upstream packages? > Or are there any other options? > > [0] https://github.com/googleapis/google-cloud-python Assuming you're packaging for python3 only, I don't think it's a problem: https://www.python.org/dev/peps/pep-0420/ Scott K
Re: Help with setuptools-related build break
On 1/26/19 4:56 PM, Scott Kitterman wrote: On Saturday, January 26, 2019 04:05:50 PM Martin Kelly wrote: Hi, I'm attempting to release a new version of my package python-gmpy2 [1] and am hitting a bug that I can't figure out how to resolve. Specifically, in the latest version under pbuilder, python-setuptools is missing. When I add python-setuptools and python3-setuptools it to the build dependencies, I get the following error: Err http://cdn-fastly.deb.debian.org/debian sid/main amd64 python-pkg-resources all 39.2.0-1 404 Not Found [IP: 151.101.52.204 80] Err http://cdn-fastly.deb.debian.org/debian sid/main amd64 python-setuptools all 39.2.0-1 404 Not Found [IP: 151.101.52.204 80] Err http://cdn-fastly.deb.debian.org/debian sid/main amd64 python3-setuptools all 39.2.0-1 404 Not Found [IP: 151.101.52.204 80] E: Failed to fetch http://cdn-fastly.deb.debian.org/debian/pool/main/p/python-setuptools/python -pkg-resources_39.2.0-1_all.deb: 404 Not Found [IP: 151.101.52.204 80] E: Unable to fetch some packages; try '-o APT::Get::Fix-Missing=true' to continue with missing packages [snip] E: pbuilder-satisfydepends failed. Indeed, this package version does not exist in the repo, so I'm not sure why apt is attempting to install it. Does anyone have some guidance and/or debugging suggestions? Thanks, Martin [1] https://salsa.debian.org/python-team/modules/python-gmpy2 Those are obsolete versions. You need to run pbuilder update. Scott K Thanks, this is what I thought as well, and so I kept running pbuilder update to no avail. I realized that I was using cowbuilder, so the update was happening on a different chroot. After starting from a clean cowbuilder, the problem is gone.
Re: Packaging google-cloud-python
Hi Scott, Am 27.01.2019 um 15:36 schrieb Scott Kitterman: Assuming you're packaging for python3 only, I don't think it's a problem: https://www.python.org/dev/peps/pep-0420/ thanks for this hint. I should pay more attention to PEPs. Digging deeper into the Google SDK dampened my enthusiasm quite a bit, especially the googleapis-common-protos[0] which is autogenerated using two Google internal tools "artman" and "toolbox". Nothing I would want to maintain ... [0] https://pypi.org/project/googleapis-common-protos/ Regards, Michael
