[03:16] hi all.. if a package does *not* contain a file it advertises as included, do i ask here or just in #ubuntu? [03:18] and it is most definitely a packaging issue! as i have already checked the checksums as advertised on packages.ubuntu.com [03:19] dodobrain: How do you know the package does not contain the file you believe it includes? [03:20] http://packages.ubuntu.com/trusty/openjdk-7-jre-headless and the filelist http://packages.ubuntu.com/trusty/amd64/openjdk-7-jre-headless/filelist says /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/ext/pulse-java.jar is included [03:21] this file /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/ext/pulse-java.jar is *nowhere to be found on my system* [03:21] and eclipse just shows loads of my projects as broken [03:21] and i have verified that it does *not* include said file in the package file /var/cache/apt/archives/openjdk-7-jre-headless_7u71-2.5.3-0ubuntu0.14.04.1_amd64.deb [03:24] RAOF, so can you verify what i have said as true by simply inspecting the downloaded deb file? [03:24] * RAOF looks [03:26] instead of /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/ext/pulse-java.jar there is /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/ext/icedtea-sound.jar [03:26] and icedtea-sound.jar is present when it is *not* present in the filelist of the package [03:26] how did this happen? i thought the filelist is generated from the actual package itself [03:27] So did I. [03:27] so have you verified what i said? [03:28] Yeah. I can only see pulse-java.jar in openjdk-6-jre [03:29] Well, and libpulse-java, but I don't know if that's what you're after. [03:30] what the heck is libpulse-java [03:30] * dodobrain looks [03:30] The package that contains pulse-java.jar :) [03:30] http://packages.ubuntu.com/search?searchon=contents&keywords=pulse-java.jar&mode=exactfilename&suite=trusty&arch=amd64 [03:30] shows no libpulse-java [03:31] Ah, right. Shiny and new in 14.10, it seems. [03:31] right.. so you guys messed up the lts [03:31] :'( [03:32] that's a bit harsh to say dodobrain [03:32] it is, sadly [03:32] it's entirely possible for that library to have NOT been present when LTS was made/released [03:32] cos for java devs, you just broke stuff [03:32] and then later introduced in Debian, for example [03:32] teward, sorry, it was working fine! [03:33] dodobrain: don't blame MOTU for LTS being messed up, nor is it sane to state that the LTS is entirely broken as a result of your java development being impacted [03:33] nor is it sane to slap everyone with the blame either. [03:33] Ok. [03:34] well, i didn;t say lts was broken.. just that 'stuff' was broken. also, in hindsight, it might have been a bit harsh. but stuff is definitely broken ;) [03:34] Looks like it changed between 7u51-2.4.6-1ubuntu4 and 7u71-2.5.3-0ubuntu0.14.04.1 [03:34] yes, i apt-get upgraded and hit the problem [03:34] RAOF: E:Regression ? [03:34] teward: Looks like it. [03:35] given that icedtea-sound.jar got it. i would say it looks more like the utopic package simply got built for trusty as well [03:36] s/it/in [03:36] Right, it was. [03:36] thank you for your understanding. [03:37] Because we can't reasonably backport Java security fixes :/ [03:37] yep, looks like a backport... and it looks like jdstrand may have been on the radar for that - perhaps this needs to be poked up to the sec team, because it's a security update that broke this? [03:37] now how do we get the actual update going? [03:37] well, 7u72 was released by oracle within hours of 7u71 [03:38] keep in mind openjdk != oracle, just saying [03:39] sure [03:43] dodobrain: Can you please add relevant details to https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1389493 ? [03:43] Ubuntu bug 1389493 in openjdk-7 (Ubuntu) "Package dropped pulse-java.jar, breaking some development environments" [Undecided,New] [03:46] dodobrain: Particularly - I'm not sure what the actual symptom is here, nor how Eclipse or other projects would be impacted. [03:47] essentially the projects within eclipse will show as broken because one of the files (pulse-java.jar) disappeared [03:48] cmdline and other applications will not really be affected [03:49] and eclipse will remain affected *until* user goes into preferences and deletes the existing JRE and adds back the same rooted at /usr/lib/jvm/openjdk-7-amd64 and then set it back as default [03:49] it will not affect those who run eclipse for the very first time *after* getting this update [03:50] And ‘show as broken’ means that they won't build/work? Or is it just cosmetic? [03:50] for everyone else who has run eclispe atleast once before this update, it will 'show' the projects as broken [03:51] and if they don;t dig around enough or don;t know how to, they will always get reports that their project is broken [03:51] 'show as broken' means when you try to run/launch the project executables or unit tests it will say project contains errors [03:56] Ok. That seems like it qualifies as sufficiently dire :( [03:57] yup, i can imagine some people desperately trying to find out why their projects are broken, because eclipse doesn't tell you immediately that there is a problem in the jre and not the project itself [03:57] and restarting eclipse a million times won;t fix it. [03:59] well, it will if you change to a new workspace, but then you'll have to import back all your existing projects into this new workspace (which could trigger re-build of every imported project) [05:08] RAOF, thanks for creating the bug report and adding in useful info. [05:08] Thanks for reporting it. [11:39] hello [11:50] i just adopted a debian package (coinor-ipopt) and made some patches, i would like to get them into ubuntu [11:50] is it possible to get them into older releases like the two LTS releases? [11:50] they close a number of outstanding ubuntu bugs [11:53] ghorn_: hello! First of all, thanks for working on these patches - what you need to do firsthand is fill in a bug targeting this source package on Launchpad with all the details [11:54] ghorn_: the general rule is that once the package gets accepted and released to the current development release, it can be considered for SRUing into the older stable releases if the bugs seem high-priority enough [11:55] ghorn_: if you fill in the bug, please subscribe ubuntu-sponsors to it [11:55] ghorn_: this way we'll know that you want sponsoring of your package upload [11:56] ok [11:56] make a bug report "please sync from debian testing" ? [11:57] or do you mean details on how I want to push this package into older releases? [12:01] sil2100: thanks for answering btw [12:01] ghorn_: a sync request should be enough :) This makes it much easier for us to track then [12:02] sil2100: ok thank you [12:02] yw! [12:04] sil2100: sorry to waste your time, i now see that the package was automatically sync'd into vivid vervet a week ago [12:05] sil2100: i will look into the SRU process === broder_ is now known as broder === Elimin8r is now known as Elimin8er