Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #922375

Bug#909990: Stange import error for nibabel when trying to import from .pybuild

Show all headers | View raw

On Fri, Oct 12, 2018 at 09:15:37AM -0400, Yaroslav Halchenko wrote:
> > ok... will merge for the next upload to proceed -- we mitigated all
> > known issues, and the beast builds fine all the way down to jessie, so
> > release is coming soon now
> 
> oi... I guess we caused you confusion and unneeded work???

Urgs, yes! While I for sure need to blame myself that I missed to check
the diff between repository and uploads, your naming of branches is
irritating.
 
> I see that you updated debian branch redoing packaging for 2.3.0-1 which was
> uploaded already awhile back, while we use this ad-hoc dist/debian/proper
> branch (should be the default when you clone that repo):

Could you imagine to use a branch named debian?  In my attempt to update
packages mentioned in Debian Med tasks which are not uploaded for a long
time and need fixing Vcs fields (and usually lots of lintian issues) I
migrated pyepl to the "kind of usual" repository layout.  Do you have
some tools that are relying on those unusual names (= did I broke
something when renaming dist/debian/proper to debian in pyepl)?
 
> $> grep Vcs-Git debian/control
> Vcs-Git: https://salsa.debian.org/neurodebian-team/pynifti.git -b dist/debian/proper
> 
> so not yet sure how to proceed with your changes. meanwhile pushed my local
> state of dist/debian/proper

I'd volunteer to check the diff between your current changes and my work
and merge everything - but can I please use a branch named debian? 

Kind regards

       Andreas.

-- 
http://fam-tille.de

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#909990: nibabel: FTBFS (Failed example) Santiago Vila <sanvila@debian.org> - 2018-10-01 01:10 +0200
  Bug#909990: Stange import error for nibabel when trying to import from .pybuild Andreas Tille <andreas@an3as.eu> - 2018-10-08 15:40 +0200
    Bug#909990: Stange import error for nibabel when trying to import from .pybuild Yaroslav Halchenko <debian@onerussian.com> - 2018-10-08 17:30 +0200
      Bug#909990: Stange import error for nibabel when trying to import from .pybuild Andreas Tille <tille@debian.org> - 2018-10-09 10:40 +0200
        Bug#909990: Stange import error for nibabel when trying to import from .pybuild Yaroslav Halchenko <yoh@debian.org> - 2018-10-12 15:20 +0200
          Bug#909990: Stange import error for nibabel when trying to import from .pybuild Yaroslav Halchenko <yoh@debian.org> - 2018-10-12 15:20 +0200
            Bug#909990: Stange import error for nibabel when trying to import from .pybuild Andreas Tille <tille@debian.org> - 2018-10-13 23:20 +0200
              Bug#909990: Stange import error for nibabel when trying to import from .pybuild Yaroslav Halchenko <yoh@debian.org> - 2018-10-14 02:40 +0200
                Bug#909990: Stange import error for nibabel when trying to import from .pybuild Andreas Tille <tille@debian.org> - 2018-10-14 09:20 +0200
                Bug#909990: Stange import error for nibabel when trying to import from .pybuild Yaroslav Halchenko <yoh@debian.org> - 2018-10-18 15:30 +0200
  Bug#909990: New version uploaded - does that problem persist? Andreas Tille <andreas@an3as.eu> - 2018-10-12 13:40 +0200
  Bug#909990: Stange import error for nibabel when trying to import from .pybuild Yaroslav Halchenko <yoh@debian.org> - 2018-10-18 15:30 +0200
    Bug#909990: Stange import error for nibabel when trying to import from .pybuild Andreas Tille <tille@debian.org> - 2018-10-18 16:30 +0200
      Bug#909990: Stange import error for nibabel when trying to import from .pybuild Yaroslav Halchenko <yoh@debian.org> - 2018-10-18 17:10 +0200

csiph-web