/srv/irclogs.ubuntu.com/2020/08/12/#ubuntu-devel.txt

seb128rbalint, hey, https://launchpad.net/ubuntu/+source/vim/2:8.2.0716-3ubuntu2 ... why is it a good idea disabling test? would be nice to have some description stating if that's a forever delta or wjat's the reason, also do you plan to try to get that change to Debian?08:38
rbasakvorlon: sergiodj asked me to review https://code.launchpad.net/~sergiodj/britney/hints-ubuntu-xenial/+merge/388495 but I've never really understood what you want wrt. these cases. SRU to fix the autopkgtest? badtest the version only? badtest all versions?09:08
rbasakAIUI a fix to the test case in Xenial is available.09:08
rbasakAnd this failure "blocks" the rpcbind SRU from being released09:08
rbasakAny chance of some documentation for when a badtest is acceptable to you please?09:09
xnoxseb128:  it builds fine in debian, maybe with the next merge it will "just work"09:13
* xnox ponders when matrix channel will finally send a message, or maybe that would be never.09:14
seb128xnox, hey, what are you talking about?09:15
seb128xnox, was it my comment about vim?09:18
seb128xnox, basically I was saying that adding undocumented and unforwarded delta just creates debt and increase our workload for futur cycles09:19
xnoxseb128:  please see discussion about vim on riscv64 across all the previous weeks here, on #ubuntu-meeting and ~RISCV =)09:38
xnoxseb128:  this change was not done lightly.09:38
xnoxrbalint:  i did say, you should also open a bug report documenting that tests were disabled for riscv64 and need to be investigated.... and expected for that bug to be referenced in the changelog. such that there are breadcrumbs for others to follow ^09:40
Laneythe changelog could be more verbose, I think that's a fair comment to make09:40
xnoxLaney:  yeap.09:40
cpaelzerslyon: all dpkg tests are green now09:45
cpaelzershould migrate on the next run09:46
seb128xnox, I didn't say that it was done lightly, just that the rational was undocumented in the changelog and that there was no bug reference or forwarding ... but seems you agree so no reason to keep that discussion going :-)09:48
slyoncpaelzer: great!09:56
rbasakTIL: lddtree10:12
rbasakThanks Christian :)10:12
cpaelzeryw rbasak10:12
cpaelzeryou sometimes want -a on it10:12
cpaelzerHi https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4192/+build/19813392 is hanging and it will soon timeout-die10:12
cpaelzerThis is due to bug 189115810:13
ubottubug 1891158 in dee (Ubuntu) "riscv64 build - hang at the end of the build (groovy)" [Medium,Confirmed] https://launchpad.net/bugs/189115810:13
cpaelzerI've added some debug to this build, but even hitting an exit 1 in override_dh_auto_test  will suffer from the hanging process keeping the chroot up10:13
cpaelzerI'm afraid once it died I won't be able to get the full log10:13
cpaelzercan anyone "log into" that builder and get the build log as generated so far?10:14
cpaelzercjwatson: ^^ since you gave me the initial traces to follow when debugging this - maybe you can do that?10:14
cjwatsoncpaelzer: I'm pretty sure if you cancel it you'll get the full log.10:24
cjwatsoncpaelzer: And even if you don't, this is a devirt builder so I can always log in after the fact and get the full log.10:24
cjwatsoncpaelzer: So please try an ordinary cancel first.10:25
cpaelzerthanks cjwatson - I wanted to make sure I ask before I throw away the chance to get to the log - aborting now ...10:25
cpaelzercjwatson: cancel complete, no buildlog there10:30
cpaelzercjwatson: could you log in and throw me the full log somewhere?10:30
Laneycpaelzer: what are you seeing - stray dbus-daemon or something?10:32
cpaelzerLaney: yes seems like that10:38
Laneymmm10:39
cpaelzerI see some timeouts on the test and then it never dies until 24h timeout10:39
Laneyso https://bazaar.launchpad.net/~indicator-applet-developers/dbus-test-runner/trunk.16.10/view/head:/libdbustest/service.c#L181 failed I guess10:39
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/dee/+bug/1891158 is what I know about it so far10:39
ubottuLaunchpad bug 1891158 in dee (Ubuntu) "riscv64 build - hang at the end of the build (groovy)" [Medium,Confirmed]10:39
Laneybecause you see that g_print() but then the daemon is still there10:39
Laneyso that kill must have not worked?10:39
cpaelzeryes I see the g_print10:39
cpaelzerbut the builder still isn't returning10:39
cpaelzerI was adding some debug in the build to look for active processes and open cwds10:40
cpaelzerthat is the build I'd like the log from10:40
cpaelzerjust in case it helps to understand the case10:40
LaneyIt's probably waiting for all of the build's processes to exit, namely that dbus-daemon10:40
LaneyI'm just pointing you at dbus-test-runner because it might be a good place to add some more verbosity10:40
cpaelzerI'd have a mitigation skipping the tests on riscv64, but only would go that route after giving up on understanding what goes on10:40
Laneylike -> here's the PID of the dbus-daemon I spawned, here's the PID of the thing I tried to kill10:41
Laneythen you can match those up an dsee if that's the stray one10:41
cpaelzerfor now getting that full build log of https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4192/+build/19813392 woud be a good next step10:41
cpaelzerbut thanks on the hint for dbus-test-runner - I could throw one wit hmore debug into the PPA as well10:42
cpaelzerjust that I have to ask for full logs is a bit inhibiting :-)10:42
cpaelzeras "alone" I can only see the snippet the build shows while running10:42
* cpaelzer off a bit for lunch10:42
LaneyI wonder if you lowered the timeout on your local system if it would happen to10:43
Laneytoo*10:43
Laneylike, make it 1 second or 0.1 seconds or something, might trigger the same bug10:43
cjwatsoncpaelzer: will do after meeting11:03
cpaelzerback again, and thanks in advance11:17
cpaelzerLaney: it can't be a fraction but -m 1 is already building11:24
cpaelzerand vice versa "just" bumping the timeout could be a fix for riscv builds for now11:25
Laneyright, even if you manage to fix the test runner to fail properly it's still an FTBFS :-)11:31
cpaelzerLaney: ha - timeout = 1 on x86 triggers the same warnings/erorrs, but NOT the hang of the builder11:34
cpaelzerhttps://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4200/+build/19818311 is an example11:34
Laneyinteresting11:34
Laneyperhaps riscv64 does process reaping differently11:35
wgrantLaney, cpaelzer: dbus-test-runner is what generally gets stuck, I haven't worked out why.11:37
wgrantBut there are a couple of packages that were consistently hanging because it didn't die for a while. But they seemed to eventually fix themselves by around maybe September.11:37
cpaelzerwgrant: https://bugs.launchpad.net/ubuntu/+source/dee/+bug/1891158 seems to be a new occasion for this then11:38
ubottuLaunchpad bug 1891158 in dee (Ubuntu) "riscv64 build - hang at the end of the build (groovy)" [Medium,Confirmed]11:38
seb128wooot, sbuild migrated :)11:38
cpaelzerRight now I'm testing if for riscv I need to bump the timeout or skip the test entirely11:39
cpaelzerseb128: yes I did some trigger magic11:39
seb128thanks slyon and cpaelzer for the work unblocking it!11:39
cpaelzertogether with dpkg11:39
cpaelzerwgrant: was there a bug for dbus-test-runner back then?11:39
cpaelzerwgrant: or should I add a task that we keep open to my bug (for documentation purposes) ?11:40
wgrantcpaelzer: Has anyone tried to reproduce it?11:40
cpaelzerI tried to trigger the same on other arches with no luck11:41
wgrantFor something like dee I'd probably just skip the test suite, since it tends to bitrot fairly aggressively.11:41
cpaelzerI can make it happen more likely on riscv64 thou, by reducing the timeout11:41
wgrantBut someone probably should dig into dbus-test-runner at some point.11:41
wgrantYep11:41
cpaelzerI'll add a dbus-test-runner task to my bug then11:41
cpaelzerand try in a riscv64 qemu a bit11:42
cpaelzerwgrant: since I have you here - ever seen https://github.com/dartsim/dart/issues/1482 before?11:43
ahasenackteward: hi, around? Would you like us to merge nginx from debian again, or were you planning on doing that?12:04
rbasakrbalint: o/ I'm reviewing this glibc SRU. In bug 1889190, what's the user story that's broken please? And shouldn't it be fixed in Groovy first?12:09
ubottubug 1889190 in glibc (Ubuntu Focal) "ldconfig is still deferred in libc6.preinst " [Undecided,New] https://launchpad.net/bugs/188919012:09
rbasakrafaeldtinoco: o/ couple of quick queries on your bcache-tools SRU for Xenial please12:54
rafaeldtinocoxenial ?12:55
rbasakOh Bionic sorry12:55
rbasakI have Xenial in my head12:55
rafaeldtinocoah =)12:55
rafaeldtinocosure12:55
rbasakBecause the version number in your upload would clash with a Xenial SRU should that be required12:55
rbasakCan you see if you agree please?12:55
rbasakSecond question - I note this was already accepted into Focal, but I'm puzzled by the dependency on gawk12:55
rafaeldtinocooh12:55
rafaeldtinocorbasak: I missed that, yes12:56
rafaeldtinocojust saw it12:56
rbasakThe code being added calls "awk" by name, which would be subject to update-alternatives12:56
rbasakIf gawk is specifically required, then I'd expect gawk to be called by name explicitly, as well as the depependency12:56
rafaeldtinocorbasak: so I had an issue with awk (mawk vs gawk recently)12:56
rafaeldtinocoyou prefer us to call a specific one ?12:56
rbasakIf you need a specific one, then I'd expect that12:56
rbasakIf you don't need a specific one, then I'm not sure you need the dependency?12:56
rafaeldtinocoI dont think for this case a specific one is needed12:56
rafaeldtinocorbasak: I thought I had a dep for it12:57
rafaeldtinocoit was part of paelzers review12:57
rafaeldtinocoone of his requests iirc12:57
rafaeldtinocounless Im confusing with other revirew12:57
rafaeldtinocolet me check12:57
rbasakIt's not marked Essential so maybe you do need a dependency12:58
rafaeldtinocorbasak: im thinking because of groovy & focal12:58
rafaeldtinoco-Depends: ${misc:Depends}, ${shlibs:Depends}12:58
rafaeldtinoco+Depends: ${misc:Depends}, ${shlibs:Depends}, gawk12:58
rafaeldtinocofor groovy12:58
rafaeldtinocofocal also has it12:59
rafaeldtinocorbasak: ok all 3 have the same change12:59
rafaeldtinocoto debian/control (Depends)12:59
rafaeldtinocoisn't that enough ?12:59
rbasakI would have used "mawk | awk" or something12:59
rafaeldtinocooh13:00
rbasakWhat you have isn't incorrect, but it would cause gawk to get pulled in to an SRU if the user doesn't have it installed I think13:00
rafaeldtinocoI see what you mean13:00
rbasakAlthough13:00
rafaeldtinocomakes sense13:00
rbasaklsb-core depends on it13:00
rbasakAs does byobu13:00
cpaelzerwe have alinged to some common packages already depending on it that way, but we didn't check which ones13:00
rbasakmawk is in the minimal seed13:01
rbasakSo we can always expect that13:01
cpaelzerrbasak: is there a single bug for "please get mysql5.7 into debian (testing)" ?13:01
rbasakcpaelzer: you mean 8.0?13:01
cpaelzeryeah13:01
rbasakThere isn't, but also it would only be unstable, not testing13:02
rafaeldtinocorbasak: with those dependencies and an already done SRU for focal with gawk, should we stick to gawk for bionic just so things are the same ? And I recently had a regression in +1maint because of mawk vs gawk syntax (autopkgtest dependencies though).. I thought the same about alternatives / mawk being the default fort minimum13:04
rbasakrafaeldtinoco: I accepted that Focal is done that way. But if it introduces something undesirable, then we have an opportunity to not do that to users for Bionic here.13:07
rbasakOK13:07
rbasakLeave it as it is.13:07
rafaeldtinocorbasak: I can change, no complains13:08
rafaeldtinocoI thought about uniformity vs fixing it =)13:08
rbasakI'll leave it to you then. I'll accept either way.13:08
rafaeldtinocorbasak: just to confirm13:08
rbasakIt does mean more work for you if one of them turns out to be wrong.13:08
rafaeldtinocohaving mawk would be better13:08
rafaeldtinocoright ?13:08
rafaeldtinocobecause its already part of min installation13:08
rbasakIMHO, using mawk would be better since that's guaranteed to be present on Ubuntu, and wouldn't pull in a dependency - especially in adding that in an SRU.13:09
rbasakRight13:09
rbasakIt's fine to know about a shortcoming and depend on gawk, but in that case gawk needs to be used explicitly rather than assuming which way the update-alternative points13:09
rafaeldtinocoyep13:09
rafaeldtinocoone thing Im afraid now Robie13:09
rafaeldtinocoIm pretty sure I have tested everything with gawk13:10
rbasakRight13:10
rbasakThat's why I'll accept gawk for Bionic :)13:10
rafaeldtinocobut I can call it directly13:10
rafaeldtinocorbasak: should I change a direct call s/awk/gawk and repush ?13:11
rafaeldtinocoto be 100% ?13:11
rbasakSure if you want to do that13:11
rbasakRemember to fix the version string please13:11
rafaeldtinocoalright, ill fix both and ping u back13:11
rafaeldtinocothanks!13:11
rafaeldtinocorbasak: should I use 1.0.8-2ubuntu1 or 1.0.8-2ubuntu1.0 ?13:20
rafaeldtinocoxenial could have a 1.0.8-2ubuntu0.113:21
rbasak1.0.8-2ubuntu0.18.04.1?13:22
rbasakThat would leave 1.0.8-2ubuntu0.16.04.1 for Xenial, etc13:22
rafaeldtinocoperfect13:22
cjwatsoncpaelzer: https://paste.ubuntu.com/p/RhFWhJHW2Z/13:24
rafaeldtinocorbasak: as I had uploaded 1.0.8-2ubuntu0.113:25
rafaeldtinocothis will also solve that correct ?13:25
rafaeldtinocojust checking13:25
rafaeldtinoco(I assume I have to overseed the previous upload to -proposed)13:25
rafaeldtinoco(and should I force push to git-ubuntu pkg also ? the new upload tag ?)13:28
rbasakrafaeldtinoco: yes I will reject the old upload so it will be as if that didn't happen. You can push the new upload tag and delete the old one13:31
rafaeldtinocoperfect. thanks13:31
cpaelzerthanks cjwatson13:33
rafaeldtinocorbasak: taking a few to test it against the test case again13:43
rafaeldtinocojust to make sure =)13:43
rbasakSure13:44
cpaelzerseb128: Laney: in proposed are all kind of things around *compiz* 2:0.8.18 most of them blocked on missing build dep (one epoch away).  I come from a +1 POV, is Desktop handling these and I can go on without looking into it?14:16
* cpaelzer reads old +1 report mails if something was mentioned14:17
cpaelzer"all kind" may be too much14:18
cpaelzerlooking a bit deeper it is down to two things14:18
cpaelzerhttps://launchpad.net/ubuntu/+source/compiz-plugins-experimental/2:0.8.18-114:18
cpaelzerhttps://launchpad.net/ubuntu/+source/compizconfig-python/2:0.8.16-214:18
seb128cpaelzer, I don't think anyone in desktop has been working or interested by those14:18
seb128mitya57 might know better the status14:18
cpaelzerseb128: I'm clearing out packages like these - if I could get a clear "we don't need and are not interestd in those" that woudl be enough14:19
cpaelzermitya57: let me know once you read that14:19
mitya57cpaelzer: Debian decided to use a fork of Compiz 0.8. We are using 0.9 where all code is in a single source, so all those source packages should be deleted/blacklisted.14:20
cpaelzerthank you14:20
cpaelzerwill let that happen then14:20
seb128mitya57, thanks14:21
cpaelzeressentially is a re-occurance of 1844626 - I'll try to ensure it stays non-synced this time14:25
rbalintrbasak, thanks for reviewing glibc, yes the fix is planned to land in groovy next weeks with the other fixes in the upload14:43
=== hellswor1 is now known as hellsworth
rbalintrbasak, with do-release-upgrade the bug did not cause problems in my testing, but it is still reproducible the way listed in the bug14:50
rafaeldtinocorbasak: upload/1.0.8-2ubuntu0.18.04.1 (uploaded) sources file pushed14:58
bdmurraybryyce: node-redis has passed for me multiple times. do you want to add it to long_tests or shall I?15:10
bryycebdmurray, that's great to hear.  I haven't marked long tests before but would love to learn how.15:21
bdmurraybryyce: I tried to write enough down here if its inadequate let me know and I'll give you a hand. https://wiki.ubuntu.com/ProposedMigration#autopkgtests15:23
bryycethanks15:29
seb128rbalint, hey, did you get anywhere with systemd vs plymouth?15:33
cpaelzerrbalint: I was checking the systemd autopkgtests which were flaky retries and which were real issues15:48
cpaelzerrbalint: and it seems all were flaky (most resolved now and src:audit in the queue to be tested)15:48
cpaelzerrbalint: but one remained - plymouth - that seemed to be a genuine issue and I found https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1886886/comments/215:49
ubottuLaunchpad bug 1886886 in plymouth (Ubuntu) "Plymouth 0.9.5 release" [Wishlist,Fix committed]15:49
cpaelzerI wanted to ask what became of this and if you could update the bug if something was e.g. added to systemd/245.7-1ubuntu1 for it15:49
seb128vorlon, hey, could you have a look to the speech-dispatcher-contrib i386 build failure? it seems a fallout from your change you upstreamed to Debian but unsure why it didn't bite us previous cycle?16:02
LocutusOfBorgniedbalski, debian bug opened, and uploaded in Ubuntu groovy16:47
niedbalskiLocutusOfBorg: great, thank you.16:47
LocutusOfBorgplease send upstream your patch16:50
LocutusOfBorg<BTS> Opened #968298 in src:bind9-libs 1:9.11.19+dfsg-1 by Gianfranco Costamagna (locutusofborg) «bind9-libs: SEGFAULT on redundant dhcp server configuration». https://bugs.debian.org/96829816:51
ubottuDebian bug 968298 in src:bind9-libs "bind9-libs: SEGFAULT on redundant dhcp server configuration" [Important,Open]16:51
niedbalskiLocutusOfBorg: iiuc, it would be difficult to land that patch in upstream, only affects stable branches and the code around socket event handling was entirely refactored in most recent releases.16:55
LocutusOfBorgso, it isn't a problem in the last version?16:55
niedbalskiLocutusOfBorg: it is in the version that ubuntu has 9.11.19+dfsg-1, but we are far behind upstream releases in libisc-export, i'd have to check if it is reproducible with current master, but a quick glance at the code, shows a huge delta of changes / complete refactor in that area.17:01
ahasenackLocutusOfBorg: niedbalski: keep in mind we have two sources for bind9 in focal+. bind9-libs builds just the libraries for legacy apps like isc-dhcp who don't work with the latest upstream (9.16.x), isc-dhcp being one17:15
ahasenackthen we have bind9, which is 9.16.x (upstream's latest LTS track), which builds the server and the libraries used by that server, but NOT by isc-dhcp17:16
niedbalskiLocutusOfBorg: ahasenack: okay, thanks. the patch is only required for isc-dhcp (afaik) in focal+, therefore the change in bind9-libs shouldn't affect bind9 itself.17:20
ahasenackcorrect17:20
ahasenackwe had to keep this legacy bind9 code around because of isc-dhcp, debian installer, and bind-dyndb-ldap iirc17:21
ahasenackbut mostly isc-dhcp17:21
niedbalskiahasenack: understood17:22
ahasenackgreat work fixing that, btw17:23
niedbalskiLocutusOfBorg: the debdiff for focal is also attached to the bug, unsure if you'll use that or merge back from groovy17:23
niedbalskiahasenack: thank you a lot for the clarification, somebody was suggesting to verify bind9, but giving this, that won't be required17:23
ahasenackright, it won't affect bind917:24
rbalintcpaelzer, seb128 i plan adding a fix to next systemd upload, will update  the bug, too17:35
rafaeldtinocowaveform: ping (on open-iscsi)18:03
rafaeldtinocoare you uploading gcc-10 patch anytime ? cause I'm merging it to 2.1.1 today, and I think it already contains the fix.18:04
rafaeldtinocojust wanted to sync18:04
=== lfaraone_ is now known as lfaraone
=== rafaeldtinoco_ is now known as rafaeldtinoco
seb128rbalint, thanks18:23
vorlonrbasak: what I /want/ is baseline retesting so that we don't have to add manual hints ;) but in the meantime, the 'force-reset-test' hint, with a version number, is the most semantically correct19:04
vorlonrbasak: where would you want this documented?19:05
waveformrafaeldtinoco, ah - nice - I'll close the bug and wait for the merge, thanks!19:06
rafaeldtinocowaveform: tku!19:06
vorlonseb128: hmm I don't see what these build failures related to speech-dispatcher-kali have to do with my patch to omit speech-dispatcher-festival from the i386 build19:19
xnoxmwhudson: hm rustc has been building for 21h now. Yet in Debian it built in 11h. Do you know what is normal amount of time for rust to build on riscv64?20:04
cjwatsonxnox: That doesn't seem like much of an apples-to-apples comparison, since our builders are emulated but that 11h time is from a native build20:09
xnoxcjwatson: oh, they have native builders?! Where? How? What? I want that!20:10
cjwatsonhttps://people.debian.org/~mafm/posts/2019/20191211_debian-gnulinux-riscv64-port-sponsors-and-build-machines/20:10
cjwatsonA number of Debian's riscv64 buildds are still emulated, but rv-rr44-01 is one of the native ones20:11
cjwatsonThe remark about "frequent lock-ups" there doesn't make me enthusiastic about operating them, but maybe that comment is dated ...20:12
xnoxthanks, and yeah it's just the hifive-unleashed boards not quite datacentre hardware / servergrade.20:15
cjwatsonYeah.  I mean more power to them giving it a go20:21
cjwatsonBut I'm not volunteering to be managing those things :)20:21
seb128vorlon, are we looking at the same thing? https://launchpad.net/ubuntu/+source/speech-dispatcher-contrib/0.10.1-1/+build/1978942120:36
seb128vorlon, dh_gencontrol: error: Requested unknown package speech-dispatcher-festival via -N/--no-package, expected one of: speech-dispatcher-pico speech-dispatcher-baratinoo speech-dispatcher-kali speech-dispatcher-ibmtts20:36
seb128is the error from what I see20:36
seb128vorlon, I think that's because the same source is used to build speech-dsipatch and -contrib20:37
seb128but the binary doesn't exist so the rule should probably be limited to the first one?20:37
vorlonseb128: ah I was looking at the dpkg-shlibdeps warnings, sorry.  Uh so the -N option is still there but the package is no longer built from this source?20:41
vorlonseb128: yeah so the debian/rules special case should just be dropped because speech-dispatcher-festival is commented out in debian/control...20:43
LocutusOfBorg niedbalski the diff you provided is already in unapproved queue20:56
seb128vorlon, ups, my IRC disconnected but I didn't notice ...checking again I think the same content is used to generate speech-dispatcher and speech-dispatcher-contrib sources, there is some debian/rules sed lines to generate one or the other21:05
seb128vorlon, so your fix works for speech-dispatcher but broke -contrib (which you didn't seem to have update/uploaded at the time)21:06
vorlonseb128: ah I see, so the problem is my patch is applied to a source package I didn't submit it to ;)21:06
vorlonso a more complete fix would be to check for the package in the output of dh_listpackages before setting the -N option21:07
seb128right, sort of21:07
seb128of have a 'if source' condition in addition of the ubuntu/i386 ones21:08
vorlonI don't know a sensible interface for checking source package name from within debian/rules; dh_listpackages is easy21:09
tumbleweeddpkg-parsechangelog, probably21:09
seb128vorlon, k21:10
vorlontumbleweed: yeah - which is a hassle :)21:11
vorlonnot a "sensible interface" :)21:11
tumbleweed:)21:11
seb128ifneq (,$(filter speech-dispatcher-festival,$(shell dh_listpackages)))21:11
seb128?21:11
seb128vorlon, do you want to fix/upload or should I try that ^ ?21:12
mwhudsonxnox: hm the one in focal built in 15h https://launchpad.net/ubuntu/+source/rustc/1.41.0+dfsg1+llvm-0ubuntu2/+build/1915733121:14
vorlonseb128: please go ahead21:19
ddstreetvorlon i'm stumped on software-properties migration from groovy-proposed, it complains about unsatisfiable deps for i386 and riscv64, but there are no new binary deps, just python3-launchpadlib, so i'm not sure how any previous versions got promoted...?21:23
ddstreetnot sure if i'm missing something in the process, or if it was just manually approved before21:23
seb128vorlon, k21:26
seb128ddstreet, where do you see that?21:27
seb128https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html has21:27
seb128Will attempt migration (Any information below is purely informational)21:27
seb128"software-properties-common/i386 has unsatisfiable dependency, but it is already uninstallable in the target suite so never mind. "21:27
seb128ddstreet, seems like it's going to migrate on the next publisher?21:27
ddstreetis that what it means?21:27
ddstreetok i misread it then :)21:28
seb128'so never mind'21:28
seb128also 'is purely informational'21:28
ddstreetlol, well never mind i will do then :)21:28
ddstreetthanks!21:29
seb128np!21:29
mwhudsoni kind of love the britney "xx yy zz problem but never mind" messages21:38
mwhudsonalthough they are a bit confusing21:38
mwhudsoni can totally imagine the coding process that leads to them21:39
=== SudoBash is now known as appxprt
=== Enlik is now known as Guest22584

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