dokojtaylor, any idea about https://launchpad.net/ubuntu/+source/python-scipy/0.16.1-1build2/+build/8871562 ?00:08
* mwhudson sighs01:06
mwhudsonINFO: pkgstripfiles: waiting for lock (libgolang-github-pborman-uuid1-dbgsym) ...01:06
mwhudson^ what does this mean?01:06
mwhudsonoh wait, this is what doko was complaining about01:07
dokomwhudson, please wait until pkgbinarymangler is published, then cancel and give back the builds01:10
mwhudsondoko: this is local, but ok01:10
mwhudsonah seems it is published01:11
ubottuLaunchpad bug 1535949 in debhelper (Ubuntu) "handling of -dbgsym packages breaks pkgbinarymangler" [High,Confirmed]01:11
mwhudsondistro development feels like juggling a sack of cats sometimes01:11
mwhudsondoko: new pkgbinarymangler seems to fix it indeed, thanks01:15
dokoahh, no, this looks worse, packages can not be uploaded01:22
dokopitti, https://bugs.launchpad.net/bugs/153594901:23
ubottuLaunchpad bug 1535949 in debhelper (Ubuntu) "handling of -dbgsym packages breaks pkgbinarymangler" [Critical,Confirmed]01:23
mwhudsonwaaiittt a minute01:38
mwhudsondoes sbuild not override PATH?01:38
dokopitti, slangasek: 1535949 still needs to get resolved. however I'm afk now. cancelled all looping builds01:50
dokocancelled all affected builds. please give all cancelled builds back once the issue is fixed02:00
mapreriI just got a reject from a archive@u.c for an upload I did to debian and got synced:02:05
maprerisigil-dbgsym_0.9.2+dfsg+dfsg-2_powerpc.deb: control file lists name as 'sigil-dbgsym', which isn't in changes file.02:05
mapreriuh, just had the same failure for ppc64el and armhf now02:06
sarnoldmapreri: I think you get to ignore that https://bugs.launchpad.net/bugs/153594902:06
ubottuLaunchpad bug 1535949 in debhelper (Ubuntu) "handling of -dbgsym packages breaks pkgbinarymangler" [Critical,Confirmed]02:06
maprerioh, I received that mail too, but didn't read it (subscribed to dh bugs through debian's pts02:06
mapreriok, thank you.  guess somebody else will take care of fixing dh and retry all the affected uploads (or the build)02:09
pittiGood monring06:26
pittidoko: we still have the previous patch to disable dbgsyms, and I didn't notice any in my local sbuild, but I'll look; argh06:28
pittislangasek: FYI, I figured out the "apt pinning compatible apt-get source" to also work for linux now, so audit and friends went in06:39
cpaelzergood morning06:42
pittidoko: fixed debhelper uploaded07:06
pittidoko: and all 70 "failed to upload" builds retried08:02
LocutusOfBorgpitti, <308:23
LocutusOfBorgBTW while I'm highlighting you, you retried libquazip test against marble-proposed, but it didn't start for s390x08:25
LocutusOfBorgso the migration is still stuck I think08:25
pittiLocutusOfBorg: yep, it's on my radar; s390x has some trouble ATM, I'm working on a fix to at least see the error message, and will then do a mass-retry08:27
LocutusOfBorgthanks, double thanks08:31
cpaelzerpitti: LocutusOfBorg: all of what I saw so far with s390x was packaging and stuff which you guys are way++ more experienced - but if it every seems to come down to s390 instructions or other real close-to-HW issues let me know08:35
cpaelzersame is true if the dasd/eckd disk design ever troubles you08:36
ginggsmorning all! There are now only a handful of ubuntu-specific packages still using python-support LP: #1535318 . Most of them haven't been touched in several years.  Do we want to fix them or remove them?  pitti: system-config-date has your name on it :)08:36
ubottuLaunchpad bug 1535318 in system-config-date (Ubuntu) "deprecation of python-support" [Undecided,New] https://launchpad.net/bugs/153531808:36
pittiginggs: indeed Debian dropped pysupport recently, so we absolutely shoudl fix it08:37
pittiginggs: having a tracking bug for the remaining Ubuntu ones would be really useful indeed08:37
pittiah, that :)08:37
pittiquite a few more than I expected08:37
pittibut I think a lot of them should be in Debian too, and thus either be merges or removals08:37
pittiDepends: python, python-support (>= 0.90.0), python-gtk2, python-gnome2, gksu08:38
pittiginggs: that really smells like a remova ;)08:38
ginggspitti: no, only the ones I have linked to debian bugs are in debian08:38
pittiginggs: e. g. python-cogent is only blocked on the arm64 FTBFS (https://launchpad.net/ubuntu/+source/python-cogent/1.5.3-10/+build/8774183) which is again blocked on some blast FTBFS08:45
ginggsyeah, ncbi-tools6, arm64 built fine in Debian08:46
ginggsbut in ubuntu we get a gcc internal compiler error08:47
ginggsis removing the old arm64 binaries for ncbi-tools6 and python-cogent an option?08:48
LocutusOfBorgmapreri, ^^^^08:49
pittiginggs: it has a bunch of reverse dependencies, so we need to find out which and remove them all08:51
ginggspitti: yeah, i do see them with 'reverse-depends'.  do we have an equivalent for 'dak rm' in ubuntu?09:18
pittiginggs: if that auto-removes reverse depends, then no09:18
ginggsit can tell you what will be removed09:19
pittistgraber: can I override /usr/share/lxc/config/ubuntu.common.conf in /etc/ somewhere?09:20
pittistgraber: I edit it on the LXC autopkgtest instances, but every dist-upgrade that includes lxc resets it09:21
pittistgraber: oh, I suppose I could at least use /usr/share/lxc/config/common.conf.d/README09:29
pittiwell, without the README obviously09:29
alkisgmitya57: hi, have you ever considered making an ubuntu flavor with gnome-flashback as the default session? I think edubuntu will have its last release ever in 16.04, so an ubuntu-flashback flavor would fill a big gap there...10:32
highvoltagealkisg: out of curiousity, what would suck a flavour use for file browser, viewing images, login manager, etc?10:38
alkisghighvoltage: the gap I'm thinking is "as much close to ubuntu as possible, but for clients without 3d/compositing abilities"10:39
alkisgSo I would like it if it used whatever ubuntu uses (which afaik gnome-flashback already does)10:39
highvoltagewouldn't ubuntu-mate fit that use case well?10:41
Laneydoko: file conflict in libxapian-1.3-5 update10:42
alkisgubuntu-mate is basically an older gnome which is now maintained by a few students, I'm not sure it's a better choice than upstream gnome + ubuntu + a thin layer (=flashback, menus etc)10:42
Laneydoko: bug #153609310:43
ubottubug 1536093 in xapian1.3-core (Ubuntu) "package libxapian-1.3-5 (not installed) failed to install/upgrade: trying to overwrite '/usr/share/xapian-core/stopwords/dutch.list', which is also in package libxapian-1.3-4 1.3.3-0ubuntu2" [Undecided,Confirmed] https://launchpad.net/bugs/153609310:43
highvoltagealkisg: gnome-flashback is also not upstream gnome (despite the name)10:43
alkisghighvoltage: yes, but it's a thin layer, it is something maintainable by a couple of devs, unlike ubuntu-mate which as years go by and gnome2 gets extremely out of date, will require many more devs...10:44
=== _salem is now known as salem_
=== alkisg is now known as alkisg_away
=== cpaelzer is now known as cpaelzer_afk
mapreriLocutusOfBorg: what particular line are you highlighting to me?11:47
=== jincreator is now known as jincreator_
LocutusOfBorg[09:36:34] <ubottu> Launchpad bug 1535318 in system-config-date (Ubuntu) "deprecation of python-support" [Undecided,New] https://launchpad.net/bugs/153531811:54
ubottuLaunchpad bug 1535318 in sadms (Ubuntu) "deprecation of python-support" [Undecided,New]11:54
LocutusOfBorgI know you like to kill python-support with fire, don't you? :P11:54
=== cpaelzer_afk is now known as cpaelzer
=== salem_ is now known as _salem
mapreriLocutusOfBorg: packages in ubuntu-only are so outdated and without love in every possible way...  (looking at the dh_python2 transition tracker in ubuntu)12:06
mapreriI think for now I'll not be involved in getting rid of pysupport from ubuntu12:07
mapreri... and then you notice packages with Maintainer: a DD in a ubuntu-only package, and wonder how that can happen :|12:10
rbasakThere are plenty of packages in Debian that are rotting too.12:11
rbasakPopular packages end up in sync.12:11
=== _salem is now known as salem_
=== _salem is now known as salem_
stgraberpitti: right, common.conf.d is most likely the way to go for you12:46
pittistgraber: still seems strange to put them into /usr, but I can work with that; certainly much better than changing the deb-shipped file :)12:49
=== pat_ is now known as Guest33510
=== salem_ is now known as _salem
=== _salem is now known as salem_
tjaaltonare upgrades from lts + lts-backport-stack supported to next lts only?13:42
rbasaktjaalton: if you're not aware of the page, https://wiki.ubuntu.com/Kernel/LTSEnablementStack might have an answer.13:44
tjaaltonI am aware, and point 12. mentions something about "issues", but no clear wording about "don't do that"13:45
tjaaltonsomeone upgraded from 14.04.3 to vivid and things broke, no surprises there13:47
rbasakYes, I think that's a serious issue. I had a similar use case explode on me. I filed a bug about it.13:47
* rbasak looks13:47
tjaaltonthe page probably should have a command for reverting back to stock trusty packages13:47
rbasakbug 125284313:48
ubottubug 1252843 in update-manager (Ubuntu) "Permits upgrade from an LTS system on an HWE stack to a broken system" [High,Triaged] https://launchpad.net/bugs/125284313:48
rbasakMy use case was to initially install 12.04.(something), and then eventually decide to roll up to 13.10 or something because I needed some newer package. And the install exploded.13:49
tjaaltonlooks like it's still an issue13:50
=== Zic_ is now known as Zic
=== beisner- is now known as beisner
=== ]reed[ is now known as [reed]
=== mapreri_ is now known as mapreri
=== ChrisTownsend1 is now known as ChrisTownsend
xnoxdoko, btrfs-tools has ice on arm64 in ubuntu =( https://launchpadlibrarian.net/234669123/buildlog_ubuntu-xenial-arm64.btrfs-tools_4.4-1_BUILDING.txt.gz14:35
xnoxdoko, the build-log looks like it has a clean gcc dump too.14:35
dokoxnox, work around is to build with -O2 instead of -Os14:49
xnoxdoko, =(14:54
xnoxdoko, is it a known bug?14:54
slangasekpitti: nice!15:01
dokoxnox, https://bugs.linaro.org/show_bug.cgi?id=200115:10
ubottubugs.linaro.org bug 2001 in General "[5 Regression] ICE in final_scan_insn, at final.c:3020 on aarch64-linux-gnu" [Major,Unconfirmed]15:11
=== enrico___ is now known as enrico
dokobarry, tumbleweed, jtaylor: http://people.canonical.com/~ubuntu-archive/transitions/html/python3.5-only.html   a few packages left15:14
xnoxdoko, tah.15:16
ginggs_doko, pitti: looks like that arm64 bug is the same in ncbi-tools6? https://launchpad.net/ubuntu/+source/ncbi-tools6/6.1.20120620-10  "pseed3.c: In function 'seedEngineCore':15:17
ginggs_pseed3.c:631:1: error: could not split insn"15:17
jtaylordoko: scipy will get a new upstream soon, I may check the failure then15:17
jtaylordoko: though I'll be only partially available in the next 10 days, so if someone else wants to fix it go ahead15:17
barrydoko: cool.  we're still sprinting for the next 2 days15:18
sergiusenshi there pitti, I'm trying to use adt with lxd and getting http://paste.ubuntu.com/14582679/ is there anything obvious I'm missing?15:26
pittisergiusens: nothign obvious, I think15:27
pittisergiusens: if you do "lxc launch images:ubuntu/xenial/amd64 x1", wait a bit (boot should take < 5 s), and "lxc exec x1 bash"15:27
pittisergiusens: I suppose it fails to boot, can you check journalctl?15:27
jtayloris there a docker update planned for xenial? given the issues we have in trusty and the next version 1.10 will have large changes in its internal layout I think it would be best to have it as new as possible (or not at all)15:28
sergiusenspitti, launching works just fine15:28
sergiusensI've been using lxd for a bit now for playing with random things15:28
sergiusensand to confirm, lxc exec for bash worked just fine15:29
pittisergiusens: and "runlevel" says something like "5 N"?15:31
sergiusenspitti, ah, it indeed says unknown15:32
pittisergiusens: so something went wrong with booting the container15:32
pittisergiusens: checkig "runlevel" is the least common denominator that I found for handling arbitary testbeds15:33
sergiusenspitti, there are a couple of failing services15:33
pittisergiusens: what does "systemctl status" say? degraded, or still booting?15:33
sergiusenspitti, 'starting'15:34
sergiusenspitti, 3 units failed, which is the amount of failures I saw when running systemctl15:34
sergiusensif it is of any worth http://paste.ubuntu.com/14582730/15:35
pittisergiusens: yeah, I get that too, that's just unpriv container limitations15:36
pittisergiusens: so for me I get "State: degraded" (which is "booted, but some failed units"), and runlevel "N 5"15:37
pittiand the same three failed units15:37
pittisergiusens: can you pastebin "journalctl"?15:37
sergiusenspitti, http://paste.ubuntu.com/14582749/15:38
sergiusenspitti, oh, now I recall bridging the containers to my network card, not sure it should affect booting, but it will affect adt :-)15:39
pittisergiusens: it doesn't care much about networking as long as your tests don't; but of course that will blow up if you run --apt-upgrade or install test deps15:43
sergiusenspitti, yeah, I will certainly hit that15:44
pittinetworking.service: Start operation timed out. Terminating.15:44
pittiFailed to start Raise network interfaces.15:44
pittisergiusens: so, that15:44
pittisergiusens: and previously the unit was still starting, until it hit the timeout15:44
pittiso it didn't yet appear in --failed15:44
sergiusenspitti, great, I'll look into this later, thanks for all the pointers!15:46
Laneydoko: https://launchpadlibrarian.net/234703765/xapian1.3-core_1.3.4-0ubuntu3_1.3.4-0ubuntu4.diff.gz should be libxapian-1.3-415:52
dokoohh crap15:53
=== dannf` is now known as dannf
=== rickspencer3_ is now known as rickspencer3
=== alkisg_away is now known as alkisg
=== cpaelzer_ is now known as cpaelzer_afk
RAOFcjwatson: I seem to recall at some point you making the buildd chroot tarballs available over lpapi. Is that me confabulating, or is this possible? (This is cf: jenkaaaaaaas).17:41
pittiRAOF: serach for "chroot_url" on https://launchpad.net/+apidoc/1.0.html17:46
RAOFpitti: Maha! Thanks!17:46
RAOFAlso, thanks for the apidoc link :)17:46
pitti$ wget -q -O- https://api.launchpad.net/1.0/ubuntu/xenial/amd64/chroot_url17:47
pittiRAOF: ^ imagine these two lines swapped around :)17:47
pittiRAOF: (-: ɐᴉlɐɹʇsn∀ ɹoɟ ɹǝpɹo ʇɥƃᴉɹ ǝɥʇ uᴉ ǝɹɐ ʎǝɥʇ 'ʎllɐnʇɔɐ17:47
sergiusensxnox, hey, btw, when should my upload rights become effective?17:50
RAOFWell, that's sad. I don't think I can slurp a vivid-overlay chroot out of that :)17:53
xnoxsergiusens, i dunno =) i don't think i've acted upon doing so, yet.17:54
cjwatsonRAOF: That's just the same as the vivid chroot.17:54
xnoxsergiusens, i will not get around to do it today, sorry. added a todo for tomorrow.17:55
RAOFcjwatson: ...of course it is. HAH!17:56
sergiusensxnox, ah, I was just wondering what the time lines were; no worries17:56
* RAOF knew that. Or would have, had he thought about it for any extended period of time.17:56
Laneyxnox: you can't do PPU anyway, need to ask TB person for that17:56
xnoxLaney, right that's i thought.17:56
xnoxand all of them expired, unless stgraber was back-doored in17:57
Laneyhttps://launchpad.net/~techboard/+members lies17:57
stgraberTB terms have been extended a bit so we have time to deal with elections17:58
caribouxnox: while you're at it, might think of changing my access as well :-)18:02
caribouor whoever can18:02
=== lifeless_ is now known as lifeless
=== xnox_ is now known as xnox
=== DrKranz is now known as DktrKranz
=== funkyHat_ is now known as funkyHat
=== dasjoe_ is now known as dasjoe
=== pfsmorigo is now known as Guest2202
=== fginther` is now known as fginther
=== cpaelzer_afk is now known as cpaelzer_
=== ochosi_ is now known as ochosi
=== mbarnett` is now known as mbarnett
=== nopf_ is now known as nopf
=== salem_ is now known as _salem
mightyiamYo, I'm on 16.04 and some package doesn't upgrade22:33
mightyiampython3-xapian1.3 is partially installed22:33
mightyiamSome dependency issue22:34
mightyiamBut libxapian-1.3-5 is marked for installation22:37
sarnoldmightyiam: file a bug against the xapian1.3-core source package with ubuntu-bug xapian1.3-core -- include the copy-and-paste output inlcyuding the file-overwrite attempt and the killed paste command22:39

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