Control: tags -1 + patch - moreinfo
Hello,
anarcat, le sam. 19 janv. 2019 12:42:44 -0500, a ecrit:
> On Thu, Jan 03, 2019 at 10:16:13AM +0100, Samuel Thibault wrote:
> > Oops, this bug was erroneously closed because its mention was remaining
> > in the sphinxbase changelog.
>
> So after
user debian-rele...@lists.debian.org
usertag nn + bsp-2019-01-ca-montreal
tags -1 -patch +moreinfo
thank you
On Thu, Jan 03, 2019 at 10:16:13AM +0100, Samuel Thibault wrote:
> Oops, this bug was erroneously closed
Control: reopen -1
Control: affects -1 + sphinxbase
Oops, this bug was erroneously closed because its mention was remaining
in the sphinxbase changelog.
Samuel Thibault, le lun. 29 oct. 2018 01:01:34 +0100, a ecrit:
> I looked deeper in fs.py, and I found that in the succeeding
> case, the main loop inside share_files sees _sphinbase.so before
> _sphinxbase.so.0.0.0, and thus renames it, and in the failing case, that
> loop sees
Control: reassign -1 dh-python
Control: tags -1 + patch
Samuel Thibault, le mar. 16 oct. 2018 22:13:59 +0200, a ecrit:
> Samuel Thibault, le mar. 16 oct. 2018 03:04:16 +0200, a ecrit:
> > This is driving me crazy :)
> >
> > I have uploaded the VM images on
> >
Samuel Thibault, le mar. 16 oct. 2018 03:04:16 +0200, a ecrit:
> Samuel Thibault, le ven. 12 oct. 2018 04:12:08 +0200, a ecrit:
> > I'm thinking... My chroots have a lib -> usr/lib symlink. Could it be
> > that python somehow gets lost between /lib/python* and /usr/lib/python*,
> > and
Samuel Thibault, le ven. 12 oct. 2018 04:12:08 +0200, a ecrit:
> I'm thinking... My chroots have a lib -> usr/lib symlink. Could it be
> that python somehow gets lost between /lib/python* and /usr/lib/python*,
> and dependending on e.g. inode number or directory order, we could have
> one way or
Samuel Thibault, le ven. 12 oct. 2018 03:27:47 +0200, a ecrit:
> Samuel Thibault, le ven. 12 oct. 2018 03:02:32 +0200, a ecrit:
> > Samuel Thibault, le ven. 12 oct. 2018 00:55:47 +0200, a ecrit:
> > > Samuel Thibault, le ven. 12 oct. 2018 00:38:39 +0200, a ecrit:
> > > > To be sure, I have
Samuel Thibault, le ven. 12 oct. 2018 03:02:32 +0200, a ecrit:
> Samuel Thibault, le ven. 12 oct. 2018 00:55:47 +0200, a ecrit:
> > Samuel Thibault, le ven. 12 oct. 2018 00:38:39 +0200, a ecrit:
> > > To be sure, I have installed a VM from scratch with stretch (default
> > > install, just not the
Samuel Thibault, le ven. 12 oct. 2018 00:55:47 +0200, a ecrit:
> Samuel Thibault, le ven. 12 oct. 2018 00:38:39 +0200, a ecrit:
> > To be sure, I have installed a VM from scratch with stretch (default
> > install, just not the graphical desktop task), created a chroot with
> > pbuilder there, and
Samuel Thibault, le ven. 12 oct. 2018 00:38:39 +0200, a ecrit:
> To be sure, I have installed a VM from scratch with stretch (default
> install, just not the graphical desktop task), created a chroot with
> pbuilder there, and ran in it, and got the issue there too...
Doing the same with a VM
Samuel Thibault, le ven. 12 oct. 2018 00:38:39 +0200, a ecrit:
> To be sure, I have installed a VM from scratch with stretch (default
> install, just not the graphical desktop task)
Not completely default actually, I installed in french.
Samuel
Samuel Thibault, le jeu. 11 oct. 2018 19:02:10 +0200, a ecrit:
> Emilio Pozuelo Monfort, le jeu. 11 oct. 2018 18:33:10 +0200, a ecrit:
> > Weird. I just did:
> >
> > sudo cowbuilder --update
> > debcheckout sphinxbase
> > cd sphinxbase
> > pdebuild
> >
> > And it was fine. No idea what we're
Emilio Pozuelo Monfort, le jeu. 11 oct. 2018 18:33:10 +0200, a ecrit:
> Weird. I just did:
>
> sudo cowbuilder --update
> debcheckout sphinxbase
> cd sphinxbase
> pdebuild
>
> And it was fine. No idea what we're doing differently.
Ok. I have run it on a chroot on the barriere porter machine,
On 11/10/2018 14:03, Samuel Thibault wrote:
> Emilio Pozuelo Monfort, le jeu. 11 oct. 2018 10:08:45 +0200, a ecrit:
>> On 11/10/2018 03:21, Samuel Thibault wrote:
>>> Samuel Thibault, le mer. 10 oct. 2018 18:33:18 +0200, a ecrit:
Emilio Pozuelo Monfort, le mer. 10 oct. 2018 18:27:18 +0200, a
Emilio Pozuelo Monfort, le jeu. 11 oct. 2018 10:08:45 +0200, a ecrit:
> On 11/10/2018 03:21, Samuel Thibault wrote:
> > Samuel Thibault, le mer. 10 oct. 2018 18:33:18 +0200, a ecrit:
> >> Emilio Pozuelo Monfort, le mer. 10 oct. 2018 18:27:18 +0200, a ecrit:
> >>> debian/tmp/usr/lib/python3*
Samuel Thibault, le mer. 10 oct. 2018 18:33:18 +0200, a ecrit:
> Emilio Pozuelo Monfort, le mer. 10 oct. 2018 18:27:18 +0200, a ecrit:
> > debian/tmp/usr/lib/python3* usr/lib
> >
> > That is causing both the python3.6/ and python3.7/ contents to be moved to
> > usr/lib,
>
> D'oh!
>
> Thanks for
Emilio Pozuelo Monfort, le mer. 10 oct. 2018 18:27:18 +0200, a ecrit:
> debian/tmp/usr/lib/python3* usr/lib
>
> That is causing both the python3.6/ and python3.7/ contents to be moved to
> usr/lib,
D'oh!
Thanks for the fix, I have pushed it to our tree.
Samuel
Control: reassign -1 src:sphinxbase
On Tue, 25 Sep 2018 23:55:56 +0200 Andreas Beckmann wrote:
> Followup-For: Bug #903698
>
> There is still something broken in python3-sphinxbase:
>
> The package ships
> /usr/lib/python3/dist-packages/sphinxbase/_sphinxbase.so.0.0.0
> ans the dangling
Followup-For: Bug #903698
There is still something broken in python3-sphinxbase:
The package ships
/usr/lib/python3/dist-packages/sphinxbase/_sphinxbase.so.0.0.0
ans the dangling symlink
/usr/lib/python3.6/site-packages/sphinxbase/_sphinxbase.so ->
_sphinxbase.so.0.0.0
Andreas
Followup-For: Bug #903698
Control: tag -1 sid buster
Since this bug seems to require more than one supported python 3.x
version to show up, I'm tagging it sid+buster, because we have only
one python 3.x version in (old)stable.
Please fix the tags if I misunderstood something.
Andreas
Control: reassign -1 dh-python
Control: affect -1 sphinxbase
AFAIU the issue is in dh_python3 then, thus reassigning for now.
Samuel Thibault, le sam. 14 juil. 2018 22:52:16 +0200, a ecrit:
> Paul Gevers, le ven. 13 juil. 2018 13:46:45 +0200, a ecrit:
> > I think this is caused by the fact that
Paul Gevers, le ven. 13 juil. 2018 13:46:45 +0200, a ecrit:
> I think this is caused by the fact that we loop over $pyver in the
> d/rules file, but apparently that is broken for multiple python3 versions.
I don't think that's the problem: I tried to pause after the
dh_install step, and we have
Source: sphinxbase
Version: 0.8+5prealpha+1-2
Severity: serious
Hi all,
sphinxbase is currently involved in the python3.7 "transition"¹. I
noticed that sphinxbase was rebuild, but that is was still listed in the
"bad" category. I took a look at the amd64 build log² and spotted the
following some
24 matches
Mail list logo
