/srv/irclogs.ubuntu.com/2019/09/10/#ubuntu-devel.txt

LocutusOfBorgstgraber, LP: #1843383 pleeeeeeeeeeease^07:45
ubottuLaunchpad bug 1843383 in lxc (Ubuntu) "lxc, please bump epoch to 1" [Undecided,New] https://launchpad.net/bugs/184338307:45
LocutusOfBorgvorlon, ^^07:45
seb128could people stop doing retries on duplicity/ppc64el build? it's not going to work, the tests need to be fixed08:24
cpaelzershame on me, why must x86 assembly always be so hard - does anyone know if the segement registers FS/GS are adapting size if e.g. in .code64 mode - are they still only 16bit there or bigger?09:58
cpaelzerthere are all kind of uses of the regs https://codesearch.debian.net/search?q=pop%5Ba-z%5D%5Cs*%25fs&literal=0 but usually in .code16 or .code3209:58
cpaelzerwith the new gcc in eoan this particular one using quad words fails https://codesearch.debian.net/show?file=ipxe_1.0.0%2Bgit-20190125.36a4c85-1%2Fsrc%2Farch%2Fx86_64%2Fcore%2Fgdbidt.S&line=16109:59
cpaelzerbut it is in .code64 unlike most of the others09:59
cpaelzergcc seems to be happy with popw and I now wonder if this is a false positive by gcc on FS/GS being 16bit or if this really never changes size09:59
cpaelzerwhat makes this more awkward in .code32 the pushl/popl (32bit) seem to be working10:00
rafaeldtinococpaelzer: amd did something to fs/gs in amd64, abandoning its original purpose since nobody used segmentation anylonger10:35
rafaeldtinocoim not sure what though10:35
cpaelzerI know that it is reused10:35
cpaelzerfor cpu local storgae and such10:35
cpaelzerbut I need the size10:35
rafaeldtinocoI see10:35
cpaelzerI might find the size if I read the related kernel source thou ...10:36
rafaeldtinococpaelzer: so... since you are here..10:36
rafaeldtinocohave u ever seen a HW instruction that does not return10:36
cpaelzeryet so far - always I see code doing 1. switch to 16bit then 2. use small push/pop10:36
rafaeldtinocoand program counter stays in the same address10:36
rafaeldtinocoover and over after preempted by sched10:36
cpaelzeryes I have seen that10:36
rafaeldtinocoand it goes back to that pc and stays there10:36
cpaelzerwhich arch rafaeldtinoco?10:36
rafaeldtinocoetc etc10:36
rafaeldtinocoaarch6410:36
rafaeldtinocoI think huawei microcode for cmpxchg is broken10:37
rafaeldtinoco:o)10:37
cpaelzerthis is exactly the kind of instructions youd expect such a bug10:37
rafaeldtinoco=> 0x0000aaaaaabd4110 <+32>:    stlxr   w2, w1, [x0]10:37
cpaelzernot on e.g. an add10:37
rafaeldtinocoif I move by hand the program counter10:37
rafaeldtinocoit moves and continues10:37
rafaeldtinocountil there is another instruction10:37
rafaeldtinocoof the same kind10:37
rafaeldtinoco:o)10:37
rafaeldtinocoi'll check w/ them in public bug10:37
cpaelzerrafaeldtinoco: https://community.arm.com/developer/tools-software/oss-platforms/f/dev-platforms-forum/5316/issue-with-stxr-in-armv810:38
rafaeldtinococpaelzer: somehow I was expecting a timeout to instruction generating an exception, NMI like10:39
cpaelzerthere it only behaved that way when it was single stepping10:39
rafaeldtinococpaelzer: yep, ive read that10:39
rafaeldtinocolooks like STLXR has some peculiarities10:39
rafaeldtinocoand undefined behavior under certain conditions10:39
rafaeldtinocobut I was expecting some timeout/exception approach10:39
cpaelzerok, then a public bug with the manufacturer seems right10:40
rafaeldtinocoyep, Ill read more about those peculiarities and ask them10:40
rafaeldtinocothx10:40
rafaeldtinoco   0x0000aaaaaabd4108 <+24>:    ldaxr   w1, [x0]10:56
rafaeldtinoco   0x0000aaaaaabd410c <+28>:    orr     w1, w1, #0x110:56
rafaeldtinoco=> 0x0000aaaaaabd4110 <+32>:    stlxr   w2, w1, [x0]10:56
rafaeldtinococpaelzer: does it look weird to you10:56
rafaeldtinocoORring w1 in between ldaxr and stlxr ?10:56
rafaeldtinocox0 is target address, w1 is the value to be written ..10:57
rafaeldtinocoso nope10:57
rafaeldtinocoits just a xor of the value read to be written10:57
rafaeldtinoconm10:57
rafaeldtinocoand then a brunch if not success, got this10:58
rafaeldtinocoomg, armv8 docs have ~4pages for unpredictable errors for ldxar<->stlxr combination11:25
* rafaeldtinoco goes for a coffee11:25
=== cpaelzer__ is now known as cpaelzer
=== ricab is now known as ricab|brb
=== Wryhder is now known as Lucas_Gray
=== grumble is now known as \emph{grumble}
ahasenackrbasak: hi, we have some php deps in universe again: https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#php-defaults12:37
ahasenackphp7.2-dev is in main, for example12:38
=== ricab is now known as ricab|lunch
rbasakahasenack: I think those binary packages are in mismatched components between src:php-defaults and src:php7.312:59
ahasenackrbasak: is this the report? https://people.canonical.com/~ubuntu-archive/component-mismatches12:59
rbasakahasenack: if they're moved to match Disco then I think that'll resolve it12:59
ahasenackif yes, I don't understand its output: it just says "https://people.canonical.com/~ubuntu-archive/component-mismatches" for php7.3 (src)13:00
rbasakahasenack: https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed13:00
ahasenackaha13:00
* ahasenack updates bookmark13:00
rbasakBoth are relevant, but as packages we want are stuck in proposed, the proposed one is needed to make sense of it13:01
ahasenacklooks like they are listed there13:01
cpaelzerahasenack: I work on the list of FTBFS sent by doko - do you mind if i grab squid as you usually work on it?13:23
ahasenackcpaelzer: I have a branch for that already13:24
ahasenackbut maybe your fix is nicer? I'm just dropping that include file, it's not used anymore in that file that failed the build13:24
ahasenackcpaelzer: https://code.launchpad.net/~ahasenack/ubuntu/+source/squid/+git/squid/+ref/eoan-squid-ftbfs-glibc-230 is my fix13:24
ahasenackI wanted to wait a bit for an upstream comment13:24
ahasenackppa at https://launchpad.net/~ahasenack/+archive/ubuntu/squid-ftbfs-glibc-23013:25
=== DarkTrick_ is now known as DarkTrick
cpaelzerahasenack: I haven't started on this one yet13:34
cpaelzerso my branch can't be nicer13:34
cpaelzeri have done dovecot-antispam (no issue), ipxe (fix in upstream review) and dnsmasq (MP is up for review)13:34
cpaelzerahasenack: your fix looks ok to me13:36
cpaelzerwaiting for upstream feedback seems right13:36
cpaelzerlooking for another one in this list then ...13:36
rafaeldtinococpaelzer: i might need to 1:1 w/ you later today (after daily ?)13:53
rafaeldtinocowant to check if out-of-order have caused this issue13:53
cpaelzerbefore would be preferred13:53
rafaeldtinocobefore ?13:53
rafaeldtinoco30 min ?13:53
cpaelzeryes13:53
cpaelzerok for me13:53
rafaeldtinocogood, will ping u tks13:53
cpaelzerin ~37 from now13:53
rafaeldtinoco+113:53
=== ricab|lunch is now known as ricab
rafaeldtinocoHA.. I think I found the issue14:14
rafaeldtinoco#)14:14
rafaeldtinoco\o/14:14
rafaeldtinococpaelzer: nm on 1:1, ill let u free14:17
rafaeldtinoco:o) I have to test a few things now14:17
rafaeldtinocoby re-generating the pkgs so..14:18
cpaelzerhehe14:18
rafaeldtinocowont bother u14:18
cpaelzerok14:18
rafaeldtinocohttps://bugs.launchpad.net/qemu/+bug/1805256/comments/1414:18
ubottuLaunchpad bug 1805256 in qemu (Ubuntu) "qemu-img hangs on high core count ARM system" [Medium,In progress]14:18
rafaeldtinocoif you want to read and review findings14:18
rafaeldtinocoif it makes sense etc14:18
rafaeldtinocobut only if you have extra time what you might not14:18
rafaeldtinocoi think we are missing "volatile" keyword14:18
rafaeldtinocofor some local variables being read_once()14:18
rafaeldtinoco:)14:18
rafaeldtinocooptimization made XOR instruction 0x1 always14:18
rafaeldtinocowhen it might be 0x014:18
rafaeldtinocochanged by other thread14:18
enycHrrrrrrrm,  anybody give me a $clue  why  ubuntu's  libgnutls28-dev   in 14/16/18.04 LTS   seems to WORK for modern TLS negotiation with 'tf5' package client built against  libgnutls-openssl-dev  ,  whereas debian's  similar libgnutls28-dev  doesn't work right ....   I may track down EVENUTALYL  but wondered if anybody was aware that ubuntu patched gnutls defaults for openssl-header apps or14:27
enycwhat-have-you! ....14:27
rafaeldtinococpaelzer: does qemu build ok in arm64 ? (ask you because of s390 firmware cross compilation thing)14:32
rafaeldtinocohow can I bypass the s390 stuff and still generate the builds ?14:33
cpaelzerrafaeldtinoco: you only need the arch part and not the indep part14:33
cpaelzerrafaeldtinoco: see the targets in d/rules14:33
rafaeldtinoco#) alright14:33
rafaeldtinocoyep yep14:33
rafaeldtinocotks14:33
cpaelzerby design/chance indep today is run on x86 on LP and happens to work14:33
cpaelzerthis and a few other packages would break if that would be different14:34
cpaelzerwhich is why the s390x bits use cross compile14:34
rafaeldtinocogotcha14:34
cpaelzerthe x86 bits of indep should use cross as well, then they would work everywhere14:34
ahasenackslashd: hi, is https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1843032 a duplicate of https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1843036 ?14:41
ubottuLaunchpad bug 1843032 in net-snmp (Ubuntu) "Storage graph error" [Undecided,Incomplete]14:41
ubottuLaunchpad bug 1843036 in net-snmp (Ubuntu Disco) "[regression] SNMP missing disks in hrStorageTable" [High,Fix committed]14:41
slashdahasenack, yeah look like this bug is related to the regression I fixed (now found in -proposed)14:49
ahasenackslashd: ok, I'll point the user that way14:50
slashdahasenack, tks14:50
brycevorlon, I gathered from lp #1842969 that the django version should be removed?  I filed #1843355, but wanted to get your confirmation on this course of action before proceeding.15:37
ubottuLaunchpad bug 1842969 in python-django (Ubuntu) "python-django 2.2.4 not for eoan" [Undecided,Confirmed] https://launchpad.net/bugs/184296915:37
vorlonbryce: the block-proposed bug was filed to make sure it didn't accidentally make it into the eoan release, but post-eoan we would want the package still be in -proposed so that it can be released once its revdeps are sorted, without there having to be a new version uploaded to unstable16:00
vorlon... in practice there has been a new version uploaded to unstable16:01
vorlonso we could just remove it16:01
vorlonand close the blocking bug16:01
brycevorlon, ok, what can I do to help with removing it?16:07
tpokorraI am trying to request a sync of mono-complete from Debian unstable to Ubuntu. Now it seems that mono-complete lives from eaon in Universe, but I don't know how to specify that in the requestsync command. I tried: requestsync -d sid mono-complete "eoan universe"16:13
cjwatsontpokorra: you don't need to specify universe16:13
tpokorracjwatson, but it tells me it is a new package then16:13
tpokorrahttps://packages.ubuntu.com/de/eoan/mono-complete says it is in universe16:14
cjwatsonshouldn't - what's the full output?16:14
cjwatsonoh, that's a binary package name16:14
cjwatsonrequestsync works on source package names16:14
cjwatsonthe source package name is 'mono'16:14
cjwatsontpokorra: ^-16:14
cjwatsonalso see https://bugs.launchpad.net/ubuntu/+source/mono/+bug/184178416:15
ubottuLaunchpad bug 1841784 in mono (Ubuntu) "Update to 6.0.0.319 not this cycle" [Wishlist,Triaged]16:15
cjwatsonah, though that's for a newer version than is in unstable16:15
tpokorracjwatson, yes. your hint with the package name solves my issue16:15
tpokorrayes I would like to get the latest version from unstable, with a little patch, into Ubuntu16:16
cjwatsonlooks like a reasonable set of changes to me16:19
cjwatsonrequest the sync and I'll ack it16:19
tpokorracjwatson, that would be great. somehow it is missing the dfsg-5.changelog, but there is only dfsg-4 in unstable16:21
tpokorraperhaps I need to wait, it is only since yesterday16:21
cjwatsontpokorra: it's recent enough that you'll have to wait a bit, yes16:21
tpokorraok. I will come back soon :)16:21
tpokorrathanks you very much for your help, cjwatson!16:22
cjwatsonwill work as soon as https://launchpad.net/debian/+source/mono shows -516:22
tpokorracjwatson, it seems that dsfg-4 has already been submitted to branch eoan-proposed. https://code.launchpad.net/~usd-import-team/ubuntu/+source/mono/+git/mono/+ref/ubuntu/eoan-proposed16:35
tpokorraso is the sync already happening?16:35
dokosforshee, apw: are riscv64 builds broken with 5.3? LP: #184345816:35
ubottuLaunchpad bug 1843458 in cross-toolchain-base-ports (Ubuntu) "linux 5.3 breaks building glibc for riscv64" [High,Confirmed] https://launchpad.net/bugs/184345816:35
rbasak+1 for iptables revert FWIW. It's the job of the distribution to coordinate, and having it move "by accident" and then scramble is hardly coordination.16:38
WoCWhich card would you recommend for OpenCL that has drivers that actually work and won't rape my wallet? pcie x1616:48
ahasenackcjwatson: hi, openssh showed up in our server page as being stuck in migration:16:53
ahasenackopenssh-server/amd64 unsatisfiable Depends: runit-helper (>= 2.8.14~)16:53
ahasenackthat package is in universe16:53
ahasenack+               dh-runit (>= 2.8.8), <-- was added in 8.0p1-516:53
ahasenackLocutusOfBorg: ^ you synced that from debian this past weekend?16:56
WoCCaptain Picard, greetings;)16:58
LocutusOfBorgahasenack, already discussed and MIR opened for runit...17:01
ahasenackLocutusOfBorg: ok, it showed up in our list at https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#ubuntu-server17:02
ahasenackLocutusOfBorg: https://bugs.launchpad.net/ubuntu/+source/dh-runit/+bug/1843236 right?17:02
ubottuLaunchpad bug 1843236 in dh-runit (Ubuntu) "[MIR] runit-helper" [Undecided,New]17:02
Odd_BlokeWoC: Hi, this channel is for the development of Ubuntu itself, so isn't the right forum for that question.  Perhaps try in #ubuntu?  (I would also ask you to reconsider casual use of language pertaining to sexual assault, as a matter of basic decency.)17:14
WoCK ty17:14
stgraberxnox, juliank: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/184346817:56
ubottuLaunchpad bug 1843468 in iptables (Ubuntu) "nftables based iptables wrapper break userspace" [Critical,Triaged]17:56
ahasenackbryce: hi, I just filed https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1843474 which affects us too18:13
ubottuLaunchpad bug 1843474 in fetchmail (Ubuntu) "/usr/bin/fetchmailconf not completely removed" [Undecided,New]18:13
bryceahasenack, ok18:26
juliankThanks stgraber19:09
rbasakI just saw wireguard enter eoan-proposed \o/19:31
sarnoldwoot; do you know off-hand if we're getting the kernel config turned on too?19:39
* rbasak doesn't know19:50
ahasenackbryce: so about that horde error,20:14
ahasenackI found this:20:14
ahasenack /usr/share/php/Horde/Test/Case.php:class Horde_Test_Case extends PHPUnit\Framework\TestCase20:14
ahasenackthat's where that class is being defined20:14
bryceahasenack, right20:14
ahasenackyet I still got20:14
ahasenack /tmp/autopkgtest.y3OCQg/phpunit-stderr:PHP Fatal error:  Uncaught Error: Class 'Horde_Test_Case' not found in /tmp/autopkgtest.y3OCQg/build.dRo/real-tree/Horde_Text_Filter-2.3.6/test/Horde/Text/Filter/LinkurlsTest.php:1120:14
bryceahasenack, what I found is if I added a require Horde/Test/Case.php; at the top of the file, then that error would be resolved (I guess?)20:15
ahasenackdoes this fail with php 7.2?20:15
ahasenackdo we know that?20:15
bryceahasenack, however then I got a slew of errors with all the other tests, that Horde_Text_filter not found20:15
brycechecking...20:16
* ahasenack checks last green20:16
brycelooks like it has been failing since before the transition20:17
ahasenackit passed with phpunit 7.5.320:17
ahasenackwe now have 7.5.620:17
bryceyes you're right, phpunit all 7.5.3-120:18
ahasenackphp-horde-test was the same20:18
ahasenack2.6.3+debian0-3ubuntu120:19
ahasenackthat's what is defining that class20:19
brycephpunit_renamed_phpunit_classes.patch has:20:24
bryce-class Horde_Test_Case extends PHPUnit_Framework_TestCase20:24
bryce+class Horde_Test_Case extends PHPUnit\Framework\TestCase20:24
bryceahasenack, aha think I know what needs done20:26
bryce(wish we had a better tool for managing trigger tweaks...)20:26
ahasenackwhat is it?20:26
ahasenackand that \ hurts my eyes, no idea what is going on with that replacement20:27
brycethe \ is php's namespacing mechanism20:27
bryceso it's moving from a simple class named "PHPUnit_Framework_TestCase" in the top level namespace, to a class called TestCase inside the Framework namespace, which is itself under PHPUnit20:28
bryceahasenack, I've queued up -ansel/amd64 to test my theory, if it works I'll rebuild the rest20:30
ahasenackok20:30
ahasenackbryce: by "queued", do you mean uploaded, or added as a test trigger or something?20:39
ahasenackthis thing is failing in debian ci as well20:40
ahasenackalso an error about an unknown class, just not the same one20:40
ahasenackbryce: the green runs of php-horde-ansel are using libapache2-mod-php7.3, whereas the red one is using libapache2-mod-php7.220:48
ahasenacklibapache2-mod-php comes from php-defaults20:49
ahasenackthe only red in php-defaults is our friend php-horde-text-filter20:50
bryceahasenack, sorry, 'triggered' I suppose is the better term20:59
bryceok looks like the test worked, I'll trigger the rest21:02
bryceinterestingly, even though I only ran -ansel/amd64, everything switched to green which is weird, but I think false positive21:04
ahasenackbryce: hope it's better by tomorrow :)21:23
ahasenackI'm eod'ing, cya21:23
brycecya21:43

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