/srv/irclogs.ubuntu.com/2017/04/26/#launchpad.txt

=== chihchun_afk is now known as chihchun
=== cpaelzer_ is now known as cpaelzer
=== JanC is now known as Guest5365
=== JanC_ is now known as JanC
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
xnoxI have lp: git alias setup. However, pushing to lp:~team/project/repo-name does not work10:09
xnoxI had to change the remote to lp:~team/project/+git/repo-name10:10
* xnox is sad10:10
xnoxalso i guess i cannot use private branches for recipes?!10:20
cjwatsonxnox: Why do you feel you need to specify the repository name?11:02
cjwatsonxnox: In most cases the correct thing to do is to use the default repository for the team/project combination, i.e. lp:~team/project11:03
cjwatsonxnox: lp:~team/project/repo-name will never work for git, because that's a namespace stolen en masse by bzr11:03
cjwatsonxnox: Recipes may indeed only be built from public code at this time.  This restriction may be lifted in the future, but it requires some quite complex work.11:04
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
xnoxcjwatson, i feel the need to specify the repository name due to (a) bzr habbits (b) because i'm starting a new sub-components in the project, and don't want to register a separate project.11:34
xnoxalso it seems weird that i need to always specify target when creating git branch merge proposals, e.g. refs/heads/master -> i would have thought such a default could be pre-populated?11:35
xnoxalso thinking about ubuntu-seeds migration to git, i'm thinking we want to have just11:36
xnoxlp:~ubuntu-core-dev/ubuntu-seeds/+git/platform11:36
xnoxlp:~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu11:36
xnoxlp:~lubuntu-dev/ubuntu-seeds/+git/lubuntu11:36
xnoxetc11:36
xnoxand have branches inside those repositories for all the releases.11:36
cjwatsonxnox: The need to specify the target ref is a bug, yes - we need better picker logic there11:40
cjwatsonxnox: Goodness, that's a silly layout11:40
xnoxcjwatson, what layout would be good? given we have different ACLs11:40
cjwatsonxnox: For ubuntu-seeds, there's no good reason for anything other than a single repository per team.11:40
xnoxoh, so you mean like11:40
xnoxlp:~ubuntu-core-dev/ubuntu-seeds11:41
xnoxlp:~lubuntu-dev/ubuntu-seeds11:41
xnoxlp:~xubuntu-dev/ubuntu-seeds11:41
cjwatsonI'd do lp:~ubuntu-core-dev/ubuntu-seeds with platform.artful, ubuntu.artful etc. branches.11:41
xnoxand that's it? =)11:41
xnoxack.11:41
cjwatsonAnd also, make lp:~ubuntu-core-dev/ubuntu-seeds in fact be lp:ubuntu-seeds (i.e. the target default)11:41
cjwatsonThat way object sharing works better for the others11:41
cjwatsonThat said, check that that proposed layout works properly with germinate11:42
xnoxsometimes i wish we just had one repository for ubuntu-seeds full stop.11:42
cjwatsonI'm not convinced I was thinking straight when I did the trivial git support for it, and thus I'm not sure it supports branches in the sensible way.11:42
xnoxack11:43
cjwatsonSo that may need some thought, *before* you push anything :)11:43
xnoxre:pdiffs i always thought we want them for e.g. security pocket13:35
xnoxnot necessoraly for $devel or ppas13:35
=== chihchun is now known as chihchun_afk
mapreriis there any useful way to debug installability problems inside build chroots like https://launchpadlibrarian.net/317155258/buildlog_ubuntu-artful-ppc64el.libkf5kface_16.12.3-0ubuntu1+mpr1_BUILDING.txt.gz ?16:37
mapreri sbuild-build-depends-libkf5kface-dummy : Depends: libopencv-dev (>= 3.1.0) but it is not going to be installed16:37
mapreriE: Unable to correct problems, you have held broken packages.16:37
mapreri=> FAIL and nothing else, ain't so useful :(16:37
mapreriI think new enough sbuild also has a "debug apt problems" flag that could be useful here ^^16:38
cjwatsonmapreri: easiest way is typically to use chdist16:51
mapreri:(16:52

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!