On Sat, Oct 28, 2023 at 12:13 AM László Böszörményi (GCS)
wrote:
>
> Hi David,
>
> On Sat, Oct 28, 2023 at 6:39 AM David Aguilar wrote:
> > This step in the build log looks suspicious:
> >
> > sed -i 's|env python|env python3|' \
> >
> >
Hi Lucas,
This step in the build log looks suspicious:
sed -i 's|env python|env python3|' \
/<>/debian/git-cola/usr/lib/python3*/site-packages/cola/widgets/spellcheck.py
Two notes:
- The PKGBUILDDIR pattern looks like a template variable that was
not replaced. The << >> parts seem to be
On 0, Bernd Zeimetz wrote:
> Package: git-cola
> Version: 1.3.5.28-1
> Severity: serious
>
> git-cola ships private modules, they should be installed to
> /usr/share/git-cola
> according to the policy [1], if there is not a good reason to install them
> system-wide. As the modules are not used
On 0, Bernd Zeimetz wrote:
> Package: git-cola
> Version: 1.3.5.28-1
> Severity: grave
Grave? :'(
Ouch! Lesson learned.
See below...
> git-cola breaks the python modules help:
>
> 0 b...@think:~$ python2.5
> Python 2.5.4 (r254:67916, Feb 18 2009, 03:00:47)
> [GCC 4.3.3] on linux2
> Type "
On 0, Bernd Zeimetz wrote:
> David Aguilar wrote:
> >
> > Thanks Bernd.
> > What should I do about the .pyc/.pyo files?
> >
> > I'm assuming that I shouldn't generate them and should instead
> > let Debian generate them?
>
> Right, that
On Mon, Mar 16, 2009 at 7:25 AM, Bernd Zeimetz wrote:
> Package: git-cola
> Version: 1.3.5.28-1
> Severity: serious
>
> git-cola ships private modules, they should be installed to
> /usr/share/git-cola
> according to the policy [1], if there is not a good reason to install them
> system-wide. As
6 matches
Mail list logo
