Re: dh_python2 removing empty directories
On Fri, 19 Jul 2019, Andrey Rahmatullin wrote: I'm running dh_python2 in a package on a non-standard directory path so it will handle byte compilation, etc. However, it seems to be removing empty directories from the directory tree. Is there any way to avoid this behavior? From Python package dirs or outside them? Well, outside of the standard python package dirs, but inside the non-standard path that I'm passing to dh_python2. If it's a place where modules are stored, why do you need empty dirs there? It's a bit disorganized, unfortunately. There is also data stored there. Scott
Re: dh_python2 removing empty directories
On Fri, Jul 19, 2019 at 01:57:11PM -0400, Scott Talbert wrote: > > > I'm running dh_python2 in a package on a non-standard directory path so it > > > will handle byte compilation, etc. However, it seems to be removing empty > > > directories from the directory tree. Is there any way to avoid this > > > behavior? > > From Python package dirs or outside them? > > Well, outside of the standard python package dirs, but inside the > non-standard path that I'm passing to dh_python2. If it's a place where modules are stored, why do you need empty dirs there? -- WBR, wRAR signature.asc Description: PGP signature
Re: dh_python2 removing empty directories
On Fri, 19 Jul 2019, Andrey Rahmatullin wrote: I'm running dh_python2 in a package on a non-standard directory path so it will handle byte compilation, etc. However, it seems to be removing empty directories from the directory tree. Is there any way to avoid this behavior? From Python package dirs or outside them? Well, outside of the standard python package dirs, but inside the non-standard path that I'm passing to dh_python2. Scott
Re: dh_python2 removing empty directories
On Fri, Jul 19, 2019 at 01:32:47PM -0400, Scott Talbert wrote: > I'm running dh_python2 in a package on a non-standard directory path so it > will handle byte compilation, etc. However, it seems to be removing empty > directories from the directory tree. Is there any way to avoid this > behavior? From Python package dirs or outside them? -- WBR, wRAR signature.asc Description: PGP signature
dh_python2 removing empty directories
I'm running dh_python2 in a package on a non-standard directory path so it will handle byte compilation, etc. However, it seems to be removing empty directories from the directory tree. Is there any way to avoid this behavior? Thanks, Scott
Re: Use debhelper-compat instead of debian/compat
Hi, čt 18. 7. 2019 v 19:41 odesílatel Craig Small napsal: > One question though, what happens if the package compat level is not the latest? I will keep the old one. pá 19. 7. 2019 v 5:43 odesílatel Dmitry Shachnev napsal: > So this change is safe to do for packages whose compat level is ≥ 9. yes: https://github.com/onovy/onovy-mass/blob/master/checks/debhelper-compat#L11 čt 18. 7. 2019 v 20:34 odesílatel Scott Kitterman napsal: > Only if you leave compat at the same value for the package. Don't mass update the value. of course. I even check if d/compat and d/control have same version: https://github.com/onovy/onovy-mass/blob/master/checks/debhelper-compat#L16 -- Best regards Ondřej Nový
Re: Use debhelper-compat instead of debian/compat
On Fri, Jul 19, 2019 at 08:41:04AM +1000, Craig Small wrote: > Why not, it's a simple change and will get them all into line. > > One question though, what happens if the package compat level is not the > latest? debhelper currently Provides: debhelper-compat (= 9), debhelper-compat (= 10), debhelper-compat (= 11), debhelper-compat (= 12). So this change is safe to do for packages whose compat level is ≥ 9. -- Dmitry Shachnev signature.asc Description: PGP signature
